yaml.reader.ReaderError: unacceptable character, special characters are not allowed
See original GitHub issueAfter tgcf live i got:
raise ReaderError(self.name, position, ord(character),
yaml.reader.ReaderError: unacceptable character #x0082: special characters are not allowed
in "tgcf.config.yml", position 225
tgcf.config.yml:
plugins:
filter:
text:
blacklist: ["тест"]
problem in the word “тест”, in previous versions everything is ok
Issue Analytics
- State:
- Created 2 years ago
- Comments:14 (8 by maintainers)
Top Results From Across the Web
Python-yaml : yaml.reader.ReaderError: unacceptable character
The allowed character range explicitly excludes the surrogate block ... Any such characters must be presented using escape sequences.
Read more >ruamel.yaml.reader.ReaderError: unacceptable character ...
ReaderError : unacceptable character #x0000: special characters are not ... The App will read the existing yml file and only change values it ......
Read more >"unacceptable character #x0000" error on adding docker ...
... python interpreter: Failed to up Docker Compose services: yaml.reader.ReaderError: unacceptable character #x0000: special characters are not allowed in ...
Read more >[Satellite 5.4] cobbler service fails with ReaderError ...
[Satellite 5.4] cobbler service fails with ReaderError: unacceptable character #x0000: special characters are not allowed in "<string>", ...
Read more >yaml/reader.py · aroundthecode/ruamel.yaml - Gemfury
reader.index - the number of the current character. ... ReaderError( self.name, position, ord(character), 'unicode', 'special characters are not allowed', ) ...
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 Free
Top 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
My config https://del.dog/rughackegy.txt Log https://del.dog/vacyllanar.txt Messages in source https://i.imgur.com/IyZEEsT.png Messages in destination https://i.imgur.com/Zf9LDwI.png I think you solved this issue.
By the way, the shell is more colorful now, even the errors look nice 😃
hi @cat157 this error is now solved. From v0.2.8 onwards
click here Update to the latest version