-
Notifications
You must be signed in to change notification settings - Fork 100
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
Update Thrift package #397
Conversation
Signed-off-by: Milan Lukac <[email protected]>
This is a very simple change, could we get workflow approval for tests to run please? |
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 change LGTM.
Thanks for the review and approval! All tests fail on an seemingly unrelated error though, any advice? |
@m1n0 interesting! I checked out your branch and tried the unit tests and everything passed. Looks like something changed on github that results in these failures. [edit 12 Jun 2024 15:05:45] Here are the results from running the unit tests on Python 3.11
|
Looks like this is caused by a broader issue in virtualenv that is affecting many other developers: pypa/virtualenv#2735 The solution is to force github actions to rebuild its virtualenvs (rather than caching them). I'm not quite clear how to force that since I can't see the GH Actions panel for this repo anymore. But this should be enough information to fix things, @kravets-levko |
Yep, the tests are failing because [edit 12 Jun 2024 15:10:44] It would be good to implement this pattern so that caches are rebuilt per-pull request. If this were in place today then a contributor could workaround the bug by closing and reopening their pull request with a new branch name. Which is...inelegant...but wouldn't block awaiting repository maintainer interaction. |
Thanks everyone! |
Resolves #394