Skip to content
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

chore: Updating latest requirements to fix broken CI #4683

Merged
merged 3 commits into from
Oct 24, 2024

Conversation

franciscojavierarceo
Copy link
Member

What this PR does / why we need it:

Updating latest requirements to fix broken CI

Which issue(s) this PR fixes:

Master CI is broken

Misc

Signed-off-by: Francisco Javier Arceo <[email protected]>
@franciscojavierarceo franciscojavierarceo requested a review from a team as a code owner October 24, 2024 12:33
@franciscojavierarceo
Copy link
Member Author

@tokoko can you reproduce this issue locally? I'm not able to reproduce this linter error.

@tokoko
Copy link
Collaborator

tokoko commented Oct 24, 2024

no, I'm usually running lowest python version locally though (3.9), maybe it is 3.11-specific.

@franciscojavierarceo
Copy link
Member Author

I tried it with 3.11 and wasn't able to reproduce...

@dmartinol any chance you can check this out?

@@ -458,7 +460,7 @@ multidict==6.1.0
# via
# aiohttp
# yarl
mypy==1.11.2
mypy==1.13.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

revert this one.
I think the issue is due to this change in 1.11.2

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh nice, thank you!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually I'll just patch the issue

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Going to patch it in a separate PR actually. Let's merge this and fix master.

@dmartinol can you review?

Signed-off-by: Francisco Javier Arceo <[email protected]>
Signed-off-by: Francisco Javier Arceo <[email protected]>
@franciscojavierarceo franciscojavierarceo merged commit d95ed18 into master Oct 24, 2024
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants