onepub-dev / onepub-dev/critical_test
json chunk error
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
nginx-le/shared$ critical_test
Logging all output to /tmp/critical_test/unit_test.log
Unhandled exception:
FormatException: Unexpected character (at character 127)
...2282}Sending 978 nginx: [emerg] unexpected end of file, expecting ";" or "}
0 _ChunkedJsonParser.fail (dart:convert-patch/convert_patch.dart:1405:5)
#1 _ChunkedJsonParser.parse (dart:convert-patch/convert_patch.dart:935:48)
#2 _parseJson (dart:convert-patch/convert_patch.dart:40:10)
#3 JsonDecoder.convert (dart:convert/json.dart:506:36)
#4 JsonCodec.decode (dart:convert/json.dart:157:41)
#5 jsonDecode (dart:convert/json.dart:96:10)
#6 ProcessOutput.processOutput (package:critical_test/src/process_output.dart:77:17)
#7 _runTestScript. (package:critical_test/src/run.dart:208:48)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running critical_test and inspecting /tmp/critical_test/unit_test.log to reproduce the JSON parsing failure. Read package:critical_test/src/process_output.dart around line 77 and src/run.dart around line 208, then trace how the nginx output is decoded. Done means the failing output is handled without the FormatException and the relevant test command completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100