You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During event creation, the web client/Admin UI creates an infinite loop when warning the user about not being able to change access rules due to another episode processing in the same series.
As a result event creation cannot be finished while the other event is still processing. In addition, the browser will have a spike in CPU usage until the event creation dialog is closed.
To Reproduce
This behaviour can be reproduced on stable.opencast.org:
Create a new series names "Test Series"
Upload a new event "Test Event 1" into this series and let the processing start
Now while "Test Event 1" is still processing, create another event in "Test Series"
Proceed in the event creation dialog up until the "Access policy" tab, where the warning should now be spammed indefinitely
Expected behavior
The warning should only be shown once.
Screenshots
User environment:
Device: PC
OS: Debian 12
Browser Chrome
Version 126.0.6478.126
Additional context
This behaviour was observed with the new Admin UI, I haven't tested whether this also happens with the old Admin UI.
The text was updated successfully, but these errors were encountered:
Describe the bug
During event creation, the web client/Admin UI creates an infinite loop when warning the user about not being able to change access rules due to another episode processing in the same series.
As a result event creation cannot be finished while the other event is still processing. In addition, the browser will have a spike in CPU usage until the event creation dialog is closed.
To Reproduce
This behaviour can be reproduced on stable.opencast.org:
Expected behavior
The warning should only be shown once.
Screenshots
User environment:
Additional context
This behaviour was observed with the new Admin UI, I haven't tested whether this also happens with the old Admin UI.
The text was updated successfully, but these errors were encountered: