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: work around segfault with >100 jobs in google life sciences backend #1451
fix: work around segfault with >100 jobs in google life sciences backend #1451
Changes from 1 commit
d802477
bf5fdfe
4ae4df8
9728ada
344f8d4
9a7815b
d8fa333
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.
@vsoch do we authenticate this way in the other places as well? Or can there maybe be an auth object for the entire life science executor object instead creating a special one here in the retry?
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.
We go about it different ways, but I suspect under the hood since both are using the default application credentials (exported to the environment as
GOOGLE_APPLICATION_CREDENTIALS
) the methods are similar. We use the discovery API clients to authenticate clients that are attached to the entire class, e.g., heresnakemake/snakemake/executors/google_lifesciences.py
Lines 136 to 165 in 417f40d
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.
The request object is generated ultimately from one of those services - either directly or as a result of doing like pipelines.run() so I'm curious why the request object isn't coming with its own http already (or maybe some of them are but not consistently?) E.g., pipelines.run() here is the one that was originally giving us trouble:
snakemake/snakemake/executors/google_lifesciences.py
Line 831 in bf5fdfe
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.
In my first attempt I tried passing the credentials created here:
snakemake/snakemake/executors/google_lifesciences.py
Line 150 in 417f40d
To
google_auth_httplib2.AuthorizedHttp
in_retry_request
, but it did not like those credentials giving this error:AttributeError: '_JWTAccessCredentials' object has no attribute 'before_request'
which led me to this issue, where I found to usegoogle.auth
for the credentials.