You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When running a benchmark and selecting json, as output or as an export format, the process fails if the database encounters errors with the following error message: Error: invalid character ',' looking for beginning of value
No messages related to this error by enabling debug logs.
Powerpipe version (powerpipe -v)
Powerpipe v1.0.1
To reproduce
Execute a benchmark in Powerpipe with json output or export:
powerpipe benchmark run my_benchmark --output=none --export=findings.json
or
powerpipe benchmark run my_benchmark --output=json
Expected behavior
Powerpipe should handle database errors and return a valid output.
Additional context
This issue occurs due to Steampipe returning error messages. Examples of Steampipe errors that can trigger this behavior include:
server error: FATAL: the database system is in recovery mode (SQLSTATE 57P03)
failed to connect to `user=steampipe database=steampipe`
Using CSV as output I was able to get an output of the powerpipe execution, including the errors, but the format is also broken.
The text was updated successfully, but these errors were encountered:
Thank you @sbldevnet for raising this. I will take a look and try to get a fix. Do you have reproduction steps that I can run to replicate this situation easily?
@pskrbasu I don't have any deterministic steps. I got that behavior by limiting a steampipe container with low CPU and running a benchmark similar to the AWS Foundational Security Best Practices one with 3 AWS connections.
Describe the bug
When running a benchmark and selecting
json
, as output or as an export format, the process fails if the database encounters errors with the following error message:Error: invalid character ',' looking for beginning of value
No messages related to this error by enabling debug logs.
Powerpipe version (
powerpipe -v
)Powerpipe v1.0.1
To reproduce
Execute a benchmark in Powerpipe with
json
output or export:or
Expected behavior
Powerpipe should handle database errors and return a valid output.
Additional context
This issue occurs due to Steampipe returning error messages. Examples of Steampipe errors that can trigger this behavior include:
server error: FATAL: the database system is in recovery mode (SQLSTATE 57P03)
failed to connect to `user=steampipe database=steampipe`
Using CSV as output I was able to get an output of the powerpipe execution, including the errors, but the format is also broken.
The text was updated successfully, but these errors were encountered: