Composite OR error weirdness

[wiebe@CARYA]

This used to work in LV18, now in LV20 (and 21 beta) this brakes in some situations:

I'm sure there's some logic behind it, but AFAIC, it should just work...

The error in\error out + OR is the simplest situation where it breaks, even in a new VI.

The problem is only there for 1 input. Extracting the node unbreaks the wire.

[TiTou]

Could it be related to this issue discussed on LAVA that resulted in bug ID 1289111 ?

LabVIEW is not correctly determining when it needs to recompile/save the VI when switching between RT and Windows

[wiebe@CARYA]

---

@TiTou wrote:

Could it be related to this issue discussed on LAVA that resulted in bug ID 1289111 ?

LabVIEW is not correctly determining when it needs to recompile/save the VI when switching between RT and Windows

---

That LAVA content is hidden (from me).

But there's no RT involved at all.

[Hooovahh]

This was posted publicly a little while ago where it was ignored, and then forgotten by the author (me).  No CAR or bug was assigned.

[altenbach]

---

wiebe@CARYA wrote:
That LAVA content is hidden (from me).

But there's no RT involved at all.

---

It shows once you log in. (Not sure why Lava is configured that way, but it will prevent finding it using a google search 😞 )

I agree that's quite a different problem. (At first glance it resembles this report, but probably not the same cause)

[wiebe@CARYA]

---

@Hooovahh wrote:

This was posted publicly a little while ago where it was ignored, and then forgotten by the author (me).  No CAR or bug was assigned.

---

Let's hope it gets some attention now...

[Darin.K]

Almost certainly related to the feature which is supposed to break wire branches instead of the entire wire.

[Christina_R]

I've created Bug 1518595 to track this issue.