-
Notifications
You must be signed in to change notification settings - Fork 637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IndexOutOfBounds if output collection of multi-instance is modified #9143
Labels
area/ux
Marks an issue as related to improving the user experience
kind/bug
Categorizes an issue or PR as a bug
severity/high
Marks a bug as having a noticeable impact on the user with no known workaround
version:1.3.8
version:8.1.0-alpha1
Marks an issue as being completely or in parts released in 8.1.0-alpha1
version:8.1.0
Marks an issue as being completely or in parts released in 8.1.0
Milestone
Comments
We'll mark it for next release, ideally before - the result here is that the instance is blacklisted (all instances for this process presumably) which is still not observable for users, and looking at the logs doesn't give you much of an idea of what to fix either. There is no known workaround at the moment, but this might be because we still haven't root caused the issue. |
pihme
added a commit
that referenced
this issue
Apr 19, 2022
10 tasks
pihme
added a commit
that referenced
this issue
Apr 20, 2022
ghost
pushed a commit
that referenced
this issue
Apr 26, 2022
9178: Fix ArrayOutOfBounds / collection has wrong type errors by raising an incident r=pihme a=pihme ## Description * Move updating of outbound collection into behavior class * Some refactorings (mostly renames) * Check for index out of bounds, implement tests for it * Check for outbound collection is not an array, implement tests for it ## Related issues closes #9143 Co-authored-by: pihme <pihme@users.noreply.github.com>
pihme
added a commit
that referenced
this issue
Apr 26, 2022
ghost
pushed a commit
that referenced
this issue
Apr 26, 2022
9178: Fix ArrayOutOfBounds / collection has wrong type errors by raising an incident r=pihme a=pihme ## Description * Move updating of outbound collection into behavior class * Some refactorings (mostly renames) * Check for index out of bounds, implement tests for it * Check for outbound collection is not an array, implement tests for it ## Related issues closes #9143 Co-authored-by: pihme <pihme@users.noreply.github.com>
ghost
pushed a commit
that referenced
this issue
Apr 26, 2022
9178: Fix ArrayOutOfBounds / collection has wrong type errors by raising an incident r=pihme a=pihme ## Description * Move updating of outbound collection into behavior class * Some refactorings (mostly renames) * Check for index out of bounds, implement tests for it * Check for outbound collection is not an array, implement tests for it ## Related issues closes #9143 Co-authored-by: pihme <pihme@users.noreply.github.com>
ghost
pushed a commit
that referenced
this issue
Apr 26, 2022
9178: Fix ArrayOutOfBounds / collection has wrong type errors by raising an incident r=pihme a=pihme ## Description * Move updating of outbound collection into behavior class * Some refactorings (mostly renames) * Check for index out of bounds, implement tests for it * Check for outbound collection is not an array, implement tests for it ## Related issues closes #9143 Co-authored-by: pihme <pihme@users.noreply.github.com>
github-actions bot
pushed a commit
that referenced
this issue
Apr 26, 2022
(cherry picked from commit e0b6ce5)
github-actions bot
pushed a commit
that referenced
this issue
Apr 26, 2022
(cherry picked from commit e0b6ce5)
ghost
pushed a commit
that referenced
this issue
Apr 27, 2022
ghost
pushed a commit
that referenced
this issue
Apr 27, 2022
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/ux
Marks an issue as related to improving the user experience
kind/bug
Categorizes an issue or PR as a bug
severity/high
Marks a bug as having a noticeable impact on the user with no known workaround
version:1.3.8
version:8.1.0-alpha1
Marks an issue as being completely or in parts released in 8.1.0-alpha1
version:8.1.0
Marks an issue as being completely or in parts released in 8.1.0
Describe the bug
I deployed a BPMN process with a parallel multi-instance embedded subprocess. The multi-instance subprocess defines an output collection to collect the results of the iterations. If the output collection is modified during the iteration (e.g. the size of the output collection is reduced) then multi-instance can't be completed. The processing fails with an
IndexOutOfBounds
exception. The concrete exception may change depending on the modification.To Reproduce
test-multi-instance-output-collection.bpmn.txt
results
results
when the multi-instance is active (e.g. set the variable to[]
- an empty array)Expected behavior
An incident is created if the output element can't be added to the output collection. The incident is visible to the user and allows to fix the issue manually by modifying the output collection.
Log/Stacktrace
Full Stacktrace
Environment:
The text was updated successfully, but these errors were encountered: