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
Describe the bug
When launching the app, a log file is created which is used to update the logging widget, giving the user valuable feedback on processing progress. However, it has been observed that after accessing the app, the log from previous runs (or other runs) can be seen. This is not ideal.
Expected behavior
The log widget should be clear when first accessing the deployed app. It should be clear for every single user and each time the user accesses the app (also for website resets).
We might need a mechanism to catch a new run or website refresh and force the log file to be reset.
Screenshots
The old log can be seen when first accessing the website:
The text was updated successfully, but these errors were encountered:
Describe the bug
When launching the app, a log file is created which is used to update the logging widget, giving the user valuable feedback on processing progress. However, it has been observed that after accessing the app, the log from previous runs (or other runs) can be seen. This is not ideal.
Expected behavior
The log widget should be clear when first accessing the deployed app. It should be clear for every single user and each time the user accesses the app (also for website resets).
We might need a mechanism to catch a new run or website refresh and force the log file to be reset.
Screenshots
The old log can be seen when first accessing the website:
The text was updated successfully, but these errors were encountered: