-
Notifications
You must be signed in to change notification settings - Fork 1
[GCP-5388] Storage: Blob.exists() does not work within Batch context #1
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
base: master
Are you sure you want to change the base?
Conversation
|
Overall, solution looks good, just couple of comments related to test coverage:
|
| os.path.join("docs", ""), | ||
| os.path.join("docs", "_build", "html", ""), | ||
| ) | ||
| ) |
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.
Is there any changes in nox file, if not, please remove this file from the the PR.
emar-kar
left a comment
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.
Checked noxfile chgs and as I see there was a correction to pass black session.
@emar-kar You probably meant, |
|
@mf2199, @emar-kar, @sumit-ql, I think we have some problems with our |
IPR: 5388
Not very beautiful (that's how I see), but looks like it's the only easy solution. For now,
exists()don't do requests while in batch context. It only adds request into list, which will be processed on exiting batch context. Soexists()returnsTrueafter adding request into batch list, but it doesn't wait for requests to be processed. I've added object to pass it as target object into request (it will bind future request to this object) and to get result after exiting context