Metadata key contains illegal characters
See original GitHub issueSeeing many of these per day:
Error: Failed to "modifyAckDeadline" for 202 message(s).
Reason: Metadata key "@" contains illegal characters
Maybe related: https://github.com/googleapis/nodejs-datastore/issues/415
Environment details
- OS: GKE
- Node.js version: 10.10.x
- npm version:
@google-cloud/pubsub
version: 0.30.0
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Metadata key contains illegal characters · Issue #415 - GitHub
This fix includes grpc/grpc-node#962 which is a work around for a bad metadata keys problem that many customer see across several libraries ( ......
Read more >Class Metadata.Key<T> - gRPC on GitHub
Key for metadata entries. Allows for parsing and serialization of metadata. Valid characters in key names. Only the following ASCII characters are allowed ......
Read more >Metadata key contains illegal characters - Bountysource
Metadata key contains illegal characters.
Read more >00057: Layer name contains invalid characters—ArcGIS Pro
A layer in the map or selection of layers being shared has a name that contains URL or XML reserved characters that are...
Read more >Restrictions and limitations in OneDrive and SharePoint
PST files when Known Folder Move is turned on. 28 July 2020: Added note to invalid characters about saving Office files with folder...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@callmehiphop we’ve rolled back to 0.29.0. Just wanted to make sure you guys were aware that the grpc-js library change affected the pubsub client too. But I guess you’re on it. Thanks!
Hi @mahaben,
This error comes from Node.js
http2
stack (https://github.com/nodejs/node/issues/28632) and we don’t have any solution at this moment, but we made sure we only print a warning and not an error. Make sure you update your dependencies.Starting from
@grpc/grpc-js
v0.5.2 this error is changed to warning so it should not crash your code.We keep trying to catch and debug it, but since it’s something happening in Node.js core, it might take more time.