-
Notifications
You must be signed in to change notification settings - Fork 5
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
[Bug]: @google-cloud/storage versions above 7.0.0 are broken #800
Comments
Same issue here also using Deno. I have submitted a fix: googleapis/gax-nodejs#1696 |
The quick patch for this issue is ready to land. We plan to ship it tomorrow. |
This is amazing!! Thank you!!! I did find a work around and submitted it as above, but since this is an upstream library I pretty much would have to wait for google to accept it which may never happen... and it really seems like a bug since it's not something particularly unusual they are doing. If you can patch it in Deno that would be much better. |
A fix has been submitted denoland/deno#27891 In the meatime, you could upgrade to the canary build |
@komondor Interestingly, this issue doesn't appear when running locally:
Runs with no errors, unlike the example in the PR you linked. |
The patch landed on production. Now I confirmed that this simple app works fine on Deno Deploy: import "npm:[email protected]";
Deno.serve(() => {
return new Response("ok");
}); |
Problem description
When using @google-cloud/storage with an
npm:
specifier, deployment fails with this message:Seems to have something to do with google-logging-utils trying to read
process.env
.However, this runs fine locally, the error only happens on Deploy. Version 6.12.0 still works, this error only happens on versions 7.0.0 and above.
Steps to reproduce
Playground with repro: https://dash.deno.com/playground/long-seahorse-77
Expected behavior
Should deploy without errors, like locally or on lower versions.
Environment
Only happens on Deploy.
Possible solution
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: