-
Notifications
You must be signed in to change notification settings - Fork 3
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
VIDCS-3205: Fix deps security issues with resolutions #7
Conversation
"wrap-ansi": "7.0.0", | ||
"path-to-regexp": "^0.1.12", | ||
"express": "^4.21.2", | ||
"axios": "^1.7.4", | ||
"cross-spawn": "^7.0.5", | ||
"rollup": "^4.22.4", | ||
"vite": "^5.4.11", | ||
"nanoid": "^3.3.8" |
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.
Unfortunately we have dependencies that do not have a compatible version which updates these internal dependencies so we have to use yarn resolutions to override those versions instead.
await pageOne.waitForSelector('.publisher', { state: 'visible' }); | ||
await pageTwo.waitForSelector('.subscriber', { state: 'visible' }); | ||
const screenshareButton = await pageOne.getByTestId('ScreenShareIcon'); |
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.
I think this was failing sometimes because we weren't connected so the screenshare button wasn't available yet.
For now this fix waits until a subscriber is visible for tab 2 which means we're obviously already connected and publishing & subscribing - then starts screensharing from page one
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.
LGTM! 🚀
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.
LGTM! 💪 🚀
since the relevant CI checks pass I will merge this PR in |
What is this PR doing?
How should this be manually tested?
What are the relevant tickets?
Resolves VIDCS-3205
[ ] Resolves a
Known Issue
.[ ] If yes, did you remove the item from the
docs/KNOWN_ISSUES.md
?[ ] Resolves an item reported in
Issues
.If yes, which issue? Issue Number?
[ ] If yes, did you close the item in
Issues
?