Idea

Clair A avatar image
9 Likes"
Clair A suggested Phil BoBo edited

Fix exception with a User Library

Hi,

We reported this bug to the dev team back in April, but so far it was not fixed. I have been told that fixing it has a low priority compared to other bugs which affect more people. So I post it here to see if other users in the community would like to see it fixed with a higher priority. If yes, please vote for it.

Here is a gif of this bug.

gif1.gif

If you want to reproduce it, follow the steps below:

- Open the attached model Base model.fsm.

- Right click on the Processor and add it to a new user library.

- Create a new model.

- Drag & drop a source, the processor from your user library, a sink, and "A" connect them.

- Reset & Run, an exception will be thrown:

time: 36.199861 exception: Error: Invalid assign to reference at assign labels activity "Assign Labels" in process flow "Processor1 Process"
bug reportuser library
gif1.gif (672.1 KiB)
base-model.fsm (31.7 KiB)
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

1 Comment

Phil BoBo avatar image
1 Like"
Phil BoBo commented Phil BoBo edited

The issue is that coupling nodes can have a flag that says whether they are to be preserved when you duplicate an object. This feature enables the references in a pasted object, such as Groups, ProcessFlows, etc. to be the same as the copied object.

The OnEntry listener for the Event-triggered Source is being preserved when you add the Processor to the User Library. The flag on that node is set to preserve the coupling. Adjusting that flag generally for all event listeners could potentially break something else.

To work around this issue, you can delete that listener node on the object in the user library.

1631029159412.png

Fixing the "bug" is complicated because it could affect other features that may expect that this coupling is preserved.

This bug wasn't marked low priority simply because of the amount of people it affects as you said. The amount of people affected by a bug is one criteria used when triaging bugs. Additional criteria include severity, complication, and ease of workaround. This bug has an easy workaround, does not cause severe data loss or crashing, and is complicated to fix, which could lead to causing other bugs if changed.

· 3
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Clair A avatar image Clair A commented ·
Thanks for the workaround @Phil BoBo !
0 Likes 0 ·
Yokota T avatar image Yokota T commented ·

@Phil BoBo

Has this bug been fixed?
I tried to reproduce the behavior with FlexSim 24.0.4 but could not.

0 Likes 0 ·
Phil BoBo avatar image Phil BoBo ♦♦ Yokota T commented ·

Yes, this appears to be working properly now. It was likely fixed in 23.0.9 or 23.0.13, which had fixes related to instanced process flows in user libraries.

1 Like 1 ·

Your Opinion Counts

Share your great idea, or help out by voting for other people's ideas.