[MGNLGROOVY-230] Long running groovy scripts update the ui strangely Created: 18/May/22 Updated: 17/Apr/23 Resolved: 17/Apr/23 |
|
| Status: | Closed |
| Project: | Magnolia Groovy Module |
| Component/s: | None |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | 4.0.0, 3.0.5 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Carlos Cantalapiedra | Assignee: | Dai Ha |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | 3.5h | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
|||||||||||||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||||||||||||
| Template: |
|
|||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
|||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
|||||||||||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
|||||||||||||||||||||||||
| Date of First Response: | ||||||||||||||||||||||||||
| Epic Link: | Support | |||||||||||||||||||||||||
| Sprint: | DevX 35 | |||||||||||||||||||||||||
| Story Points: | 2 | |||||||||||||||||||||||||
| Team: | ||||||||||||||||||||||||||
| Work Started: | ||||||||||||||||||||||||||
| Approved: |
Yes
|
|||||||||||||||||||||||||
| Description |
|
There is a strange UI bug when running a long groovy script in the groovy app. Any logs produced get repeated every second or so. For example, for the following script: print "1" Thread.sleep(2000) print "2" Thread.sleep(2000) print "3" Thread.sleep(2000) print "4" Thread.sleep(2000) print "5" Thread.sleep(4000) print " End" The output message looks like: Running script, please wait... 1 12 12 123 123 1234 1234 12345 12345 and once the script has ended, all the outputs above are removed and then the correct "12345 End" is shown. Tho this is just a simple example for succeeding on reproducing this issue when running more complex scripts that prints out node paths that are being modified in some way it's difficult to gauge the progress of these scripts. |