You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A screenshot that you have tested with "Try this API".
N/A
Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.
N/A
A step-by-step description of how to reproduce the issue, based on the linked reproduction.
N/A
A clear and concise description of what the bug is, and what you expected to happen.
Hey folks, we recently got some new logging code added to gcp-metadata in order to track down a very hard to debug issue with the metadata service on GCE returning malformed responses:
Would it be possible to accelerate pulling in that new dependency version and cutting a release of this nodejs code so that we can get access to the new logs in our environment?
A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **
N/A
The text was updated successfully, but these errors were encountered:
Issue was opened with an invalid reproduction link. Please make sure the repository is a valid, publicly-accessible github repository, and make sure the url is complete (example: https://github.com/googleapis/google-cloud-node)
Please make sure you have searched for information in the following guides.
A screenshot that you have tested with "Try this API".
N/A
Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.
N/A
A step-by-step description of how to reproduce the issue, based on the linked reproduction.
N/A
A clear and concise description of what the bug is, and what you expected to happen.
Hey folks, we recently got some new logging code added to gcp-metadata in order to track down a very hard to debug issue with the metadata service on GCE returning malformed responses:
And it was released in gcp-metadata 7.0.0.
Would it be possible to accelerate pulling in that new dependency version and cutting a release of this nodejs code so that we can get access to the new logs in our environment?
A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **
N/A
The text was updated successfully, but these errors were encountered: