--silent seems bugged, with json format
See original GitHub issue{
"format": "json",
"recurse": true,
"silent": true,
"concurrency": 100,
"skip": "www.googleapis.com"
}
- `linkinator URL``` all results still returned
- `linkinator --silent URL``` all results still returned
format=csv seems to work
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
JSON format not correct - Power Platform Community - Microsoft
Solved: I was able to call my WCF service from a stream. I now have the following problem. My WCF service returns a...
Read more >Option to silently ignore any lines with invalid JSON · Issue #682
I primarily use jq to extract and filter messages from our application logs, which are JSON. However, occasionally the system will ...
Read more >Bug detective — When returning JSON goes wrong - Medium
In this case, it is outputting the $data array in a JSON format, because of the json_encode call. If everything goes well, you...
Read more >Bug #1405873 “-json output not valid when -class filter used”
The result of which is not a valid JSON object, which is sometimes missing required commas and is always missing the enclosing array...
Read more >jQuery $.ajax failing silently, no error messages, and server ...
It seems perfectly formed, I used $.parseJSON() in my success function, logged the result to the console, and you can see the perfectly...
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
running it from the command line, with --silent passed, and either cli param and/or config for JSON output, the JSON output still has valid links (status 200, or state: ‘OK’ and probably skipped)
🎉 This issue has been resolved in version 2.10.1 🎉
The release is available on:
Your semantic-release bot 📦🚀