Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Fix
dev.deprecated
and refine its unit tests #647Fix
dev.deprecated
and refine its unit tests #647Changes from 3 commits
385b5b9
49d51de
12a646d
1998adb
8819902
07d52f3
890ed14
4ea8d1b
5da8026
d69055a
3fa8f13
bcc5001
fadaf14
5e58909
1483615
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 would need to patch this as well. Because currently the code is being pushed from my fork, and as such it is not "in code owner" repo, therefore no warning would be issue. And this is passing in my fork, could confirm my assumption
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.
that should be easy, no?
monkeypatch.setenv("GITHUB_REPOSITORY", "materialsvirtuallab/monty")
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 is a good fix, and I'm thinking if we could make it better:
_is_in_owner_repo
to always returnTrue
(I'm still experimenting on this) such that we don't need to hard code the repo name ("materialsvirtuallab/monty"
). Even when we hard code the repo name, unit test would still fail in forks.CI
variable as well, such that unit test wouldn't fail locally.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 experimented on patching
_is_in_owner_repo
and did not have much luck, then I decide to patchsubprocess
instead in bcc5001 (which is closer to the real-world scenario too):And everything is working as expected so far.