question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failed parsing log: Unexpected token { in JSON at position 153

See original GitHub issue

From Discord #cml (comment)

$ cml-runner --cloud=aws --cloud-region=us-east-1 --cloud-type=t2.large
-- Logs begin at Sat 2021-07-24 20:03:53 UTC, end at Sun 2021-07-25 11:15:20 UTC. --
Jul 25 11:10:02 ip-172-31-4-59 systemd[1]: Started cml.service.
Jul 25 11:10:17 ip-172-31-4-59 cml.sh[12772]: Preparing workdir /tmp/tmp.vnyMsh2f6x/.cml/cml-ds05uj5g8d...
Jul 25 11:10:17 ip-172-31-4-59 cml.sh[12772]: Launching gitlab runner
Jul 25 11:10:19 ip-172-31-4-59 cml.sh[12772]: EC2 id i-085cbd9f31fb95232
Jul 25 11:10:19 ip-172-31-4-59 cml.sh[12772]: Failed parsing log: Unexpected token { in JSON at position 153

https://github.com/iterative/cml/blob/b5c1afb285918ec08cdff89d373213bfdc6b80b6/src/cml.js#L203

Maybe related to the changes on https://github.com/iterative/cml/pull/583#discussion_r657404794

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

2reactions
dacbdcommented, Jun 10, 2022

perhaps its time close with https://github.com/iterative/cml/pull/1030 ?

1reaction
0x2b3bfa0commented, Jan 21, 2022
Read more comments on GitHub >

github_iconTop Results From Across the Web

Error "Uncaught SyntaxError: Unexpected token with JSON ...
Your code turns the object into a string (by calling .toString() ) in order to try to parse it as JSON text. The...
Read more >
What Is JSON and How to Handle an “Unexpected Token” Error
Learn what JSON is and how you can deal with errors occurring when parsing JSON data, such as "Unexpected Token < in JSON...
Read more >
Cannot parse tsconfig.json: Unexpected token / in ... - GitHub
Cannot parse tsconfig.json: Unexpected token / in JSON at position 324. Please help provide information about the failure if this is a bug....
Read more >
Troubleshoot 'Uncaught SyntaxError: Unexpected token u in ...
The 'Uncaught SyntaxError: Unexpected token u in JSON at position 0' error is caused when the client has been asked to execute JSON.parse() ......
Read more >
SyntaxError: JSON.parse: bad parsing - JavaScript | MDN
JSON.parse() parses a string as JSON. This string has to be valid JSON and will throw this error if incorrect syntax was encountered....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found