-
I get "Error: Error processing schema: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data" for valid JSON, even as simple as `{}`.
Seems to be when a `$schema` key is absent? Ev…
-
I think it would also be great to have the report as JSON too. That might make post-processing results easier.
ctron updated
1 month ago
-
This issue is all about ensuring we are as close to Redis as possible. The command in focus for this issue is `JSON.GET`.
Go through the [official documentation](https://redis.io/docs/latest/commands…
-
This issue is all about ensuring we are as close to Redis as possible. The command in focus for this issue is `JSON.SET`.
Go through the [official documentation](https://redis.io/docs/latest/commands…
-
The HTML report is great but I would love to see a programmatically aimed report based on JSON. See this example (just food for thought):
```
[
{
"difference": "d1",
"row": …
-
_This ticket is part of epic #2626_
## About this feature
### Detailed description
This is step 1 in creating scheduled reports. While generating a report, we need to create a JSON.
With every s…
-
When I run an nvbench-based benchmark, like:
```
thrust.bench.transform.basic.base -d 0 --stopping-criterion entropy --json baseline.json
```
it prints a nice markdown report at the end, summariz…
-
After running the default flow on Mistral in vLLM, there is a large (>100MB) report json in the directory I ran the commands. This seems quite heavy-weight, especially for a json file.
Instead, I …
mgoin updated
2 weeks ago
-
The [LULA](https://github.com/defenseunicorns/lula) project needs to consume our scan reports in JSON format.
-
This file should be in the branch base directory and should contain the data schema