[MGNLUI-6736] Frozen admincentral after restart (after major vaadin update) Created: 09/Jun/21 Updated: 18/Oct/22 Resolved: 06/Aug/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2.7 |
| Fix Version/s: | 6.2.12 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | VN-Testing, maintenance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 7h | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| 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)
[X]*
(Converted to MGNLUI-6810) Remove from known issues docu
[Ashraf Khamis]
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Bug DoR: |
[X]*
Steps to reproduce, expected, and actual results filled
[X]*
Affected version filled
[X]*
Verify with 8.13.1
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Vaadin push issues | ||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
Steps to reproduce
Expected resultsUI responds. Actual resultsProgress bar is pending infinitely (most of the times, although this should be tested repetitively). WorkaroundRefresh the browser tab. Development notesThis is caused by UI#push calls before the push connection is established (in our case findbar results). |
| Comments |
| Comment by Christoph Meier [ 08/Aug/21 ] |
|
fgrilli - It is indeed possible that this issue is responsible for some of the "arbitrary" failures - which very often (if not always) appear on AssetsCoreFunctionalTests. |
| Comment by Christoph Meier [ 11/Aug/21 ] |
|
fgrilli - F.Y.I. There is still a high chance that the very first test, which is run, fails. Especially after I did restart the webapp. expect.findBar().openApp("Assets"); When I then re-run the #addSubFolders with many repetitions, but without restarting the webapp, the method passes always. I'm not really sure how to interpret this - but at least it indicates that something is still fishy. If we tackle all the tickets of type bug in the test-fwk - we hopefully can get rid of the "arbitrary" failures. |
| Comment by Roman Kovařík [ 11/Aug/21 ] |
|
cmeier could you try the same with 6.2.6 webapp? |