BUG: wrangler publish fails with error about control characters
See original GitHub issueI’ve been following the instructions on the Workers Chat Demo repo (https://github.com/cloudflare/workers-chat-demo) and when I run wrangler publish
an error is returned - “Control characters (codes < 0x1f and 0x7f) are not allowed in comments, use \u000d instead”.
Steps to reproduce (on Windows 10):
- Clone https://github.com/cloudflare/workers-chat-demo to c:\projects\workers-chat-demo
- Open up cmd.
npm install -g wrangler
(I’m running 2.0.6)cd \projects\workers-chat-demo
wrangler login
wrangler publish
Issue Analytics
- State:
- Created a year ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Wrangler can panic if global user configuration contains non ...
Hi, came her from #390 and was able to resolve issue by deleting \r from within email and api_key string in global default.toml...
Read more >1427471 – oc export yaml controls chars are not allowed
errorString=yaml: control characters are not allowed) but it works with -o json. Version-Release number of selected component (if applicable): How reproducible: ...
Read more >Cloud Data Fusion release notes
This page documents production updates to Cloud Data Fusion. Check this page for announcements about new or updated features, bug fixes, known issues, ......
Read more >Trifacta Release Notes - Trifacta Documentation
Release 5.0 of Trifacta® Wrangler Enterprise delivers major enhancements to the ... particular, this issue affects columns containing special characters.
Read more >Wrangler publish fails because of exceeding size while gzip ...
This failure is due to the startup time limit of 200ms. It sounds like your code is spending more than 200ms to parse...
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
And the unit test I wrote for that only had a single line, so of course it passed! I’ll fix this up right away.
Spot the mistake: https://github.com/cloudflare/wrangler2/blob/a0e0f5f7d5f16bce6a0c9b53536b90399f8c345d/packages/wrangler/src/parse.ts#L79