-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
mgr/dashboard: Language dropdown box is partly hidden on login page #45429
Conversation
When clicking on the language dropdown combobox on the login page, the menu is partly hidden because it is partly rendered out of the visible area. Additionally the scrollbars are displayed. Fixes: https://tracker.ceph.com/issues/54591 Signed-off-by: Volker Theile <vtheile@suse.com>
jenkins test dashboard |
1 similar comment
jenkins test dashboard |
jenkins test dashboard |
Is there any chance to get rid of those unit tests that are using this proprietary applitools tool? Why removing:
If we stay on these tools, someone with an account at applitools.com must fix the PR issues. |
Sure. What visual regression testing tool you would suggest instead?
I just sent you an invite to the Applitools web.
These failures are due to breaking changes in browsers (Chrome 99.0 and Firefox 98.0) and they need to be manually inspected and approved.
You're writing this in Github, which is a propietary tool that requires you to create an account. Same applies for Transifex, Cypress, etc.
That's what's happening, but we don't have a 24/7 team to fix test issues. |
jenkins test dashboard |
jenkins test dashboard |
I have none to suggest. But i'm asking myself whether they are really needed. According to my feeling they make more troubles than they help.
Thanks
I think there is a difference. It's my own choice as a contributor to create an GitHub or Transifex account to participate on the project. But i am forced to create an account at Applitools if there are problems with a PR, otherwise i'm not able to check what happens and the PR will not get merged. The sad thing is when if comes out that the code of the PR is not responsible for the failure of the Applitools tests. It is really intransparent process. IMO a PR should be merged even if there are Applitools test failures.
As said above, in this case Applitools failures should not block PRs from getting merged. |
jenkins test dashboard |
@votdev applitools tests are not blocking any merging (not "required" by Github), we just need to ensure that the failures are unrelated. |
When clicking on the language dropdown combobox on the login page, the menu is partly hidden because it is partly rendered out of the visible area. Additionally the scrollbars are displayed.
Before:
After:
Fixes: https://tracker.ceph.com/issues/54591
Signed-off-by: Volker Theile vtheile@suse.com
Checklist
Show available Jenkins commands
jenkins retest this please
jenkins test classic perf
jenkins test crimson perf
jenkins test signed
jenkins test make check
jenkins test make check arm64
jenkins test submodules
jenkins test dashboard
jenkins test dashboard cephadm
jenkins test api
jenkins test docs
jenkins render docs
jenkins test ceph-volume all
jenkins test ceph-volume tox
jenkins test windows