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
LPS-117287 Web Content article Publish button stops working #171
Conversation
To conserve resources, the PR Tester does not automatically run for every pull. If your code changes were already tested in another pull, reference that pull in this pull so the test results can be analyzed. If your pull was never tested, comment "ci:test" to run the PR Tester for this pull. |
ci:test:sf |
ci:test:relevant |
❌ ci:test:sf - 0 out of 1 jobs passed in 3 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-117287 1 Failed Jobs:For more details click here.
|
Jenkins Build:test-portal-source-format#3681 |
@PablitoBonito See #171 (comment), that's an example of what I was talking about today 🙂 . CI is complaining about source formatting, but reporting an unintelligible error. /cc @john-co |
ci:test:sf |
✔️ ci:test:sf - 1 out of 1 jobs passed in 2 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-117287 1 Successful Jobs:For more details click here. |
Hi @kenjiheigel, possibly a flaky out of memory issue with CI on the previous SF error?
|
Taking a closer look, it might be network issue related trying to load maven?
cc/ @kenjiheigel |
Jenkins Build:test-portal-source-format#3777 |
ci:forward |
CI is automatically triggering the following test suites:
The pull request will automatically be forwarded to the user
|
Skipping previously passed test suites: |
All required test suite(s) passed. |
Pull request has been successfully forwarded to brianchandotcom#91893 |
(For posterity) same failure as reported here. |
This is a bugfix, see description in https://issues.liferay.com/browse/LPS-117287
The issue is caused by CKEditor and AlloyEditor(s) on the same page. There is a race condition on navigate (back or Publish), and CKEditor instance may delete
CKEDITOR
global object before AlloyEditor instances are destroyed. This is the same fix as in React-based Editor and AlloyEditor.The race scenario causes Publish button to sporadically stops working, and this PR fixes it. But, the console error in ticket description does not match this scenario. The error that happens is
The error in ticket description is
I sporadically got this error when quickly navigating before page loads, and this PR does not fix it. But, this error looks unrelated to the problem of this ticket:
CKEDITOR
, happens around every 20+ navigations, while undefined happens every 3-4 times and can be reliably provokedCKEDITOR
happens once when navigating away from page, and breaks a lot of UI.I gave up on trying to find the root cause of
data
issue, as it looks to be deep in base CKeditor. I think we can ignore it for now.