-
Notifications
You must be signed in to change notification settings - Fork 65
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 #884
package.json: Update @patternfly/react-console #884
Conversation
54f21bb
to
a8ec9e1
Compare
Please manually check features related to these files:
|
a8ec9e1
to
2b86395
Compare
Hmm, tests look very messy here -- unrelated to react-console, but perhaps due to some other npm updates that rode along? One round of retry to compare. |
and "protection checks" need the same treatment as cockpit-project/cockpit-podman#1158 |
The pixel test diffs seem real. But glad to see that the console crash seems fixed, thanks @KKoukiou ! |
The pixel test diff on the External console test is valid, some info were added for Suse how to launch virt-viewer. |
2b86395
to
6de36d1
Compare
6de36d1
to
93dd3a5
Compare
The podman version (3.4.4) on Ubuntu 22.04 has issues with pipes and stops before piping the full tarball over (at ~ 25M of ~ 250M). This makes the protection checks fail, which means we can't land node_modules updates. For now pin it to 20.04 until we figured out the issue on 22.04.
pixel review diff -- so the gap between a numeric input and the unit got smaller. I liked the previous version a bit better, but I suppose this isn't the place to second-guess PF updates. The failed protection checks are expected -- that workflow runs from main. I have a lot of faith that the fix will work, we can ignore the failure here. still some failures here though -- retrying. Thank you! |
It seems rawhide has a regression with iSCSI:
But I'll let this slip here, let's investigate that separately. Thanks! |
No description provided.