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
package.json: Update @patternfly/react-console #647
package.json: Update @patternfly/react-console #647
Conversation
github-actions
bot
commented
Mar 31, 2022
•
edited by KKoukiou
edited by KKoukiou
- Blocked on Bug - [VncConsole] - [Release 4.49.8 broke VncConsole causing random disconnects] patternfly/patternfly-react#8373
fc67bfd
to
3ea6308
Compare
Please manually check features related to these files:
|
Seems ok, but we need to validate that the "unexpected connection close" messages from the inline console are legit, and accept them. |
The disconnect messages appear during Anything else after that doesn't produce these messages any more. I had expected these during the reboot, or from the end of the test where it forcibly stops the cockpit session (as the test doesn't log out cleanly), but that's not it. Switching between VM overview and details reproduces these. However, at this point this is too deep inside the react-console code that I can make sense of it quickly. |
I debugged a bit and found the was introduced between version |
journalct error comes from cockpit-ws: connection unexpectedly closed by peer
|
package.json
Outdated
@@ -53,7 +53,7 @@ | |||
}, | |||
"dependencies": { | |||
"@patternfly/patternfly": "4.183.1", | |||
"@patternfly/react-console": "4.49.3", | |||
"@patternfly/react-console": "4.53.14", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is now on 4.92.54
so feels worthy to retry.
3ea6308
to
b791913
Compare
b791913
to
c622bd5
Compare
So this is still broken. |
Sent a PR upstream to fix the react-console. patternfly/patternfly-react#8374 |
version 4.93.10 got released, which should hopefully contain the fix. As this is all conflict-y, let's just close this and let our workflows build a fresh PR? |
Impatient as I am, I triggered the workflow manually and got PR #884. Crossing fingers! 🤞 |