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
This is a really interesting bug but I seem to be able to hit it consistently. Running steampipe locally in a container works perfectly. However when I try to use steampipe query to connect to a remote service then I'm getting killed after a couple seconds with "Error: failed to load schemas: sql: expected 8 destination arguments in Scan, not 9"
2022-08-10 13:40:38.172 UTC [TRACE] steampipe: no modfile exists in workspace folder - NOT creating pseudoresources and only loading resource files from top level folder
2022-08-10 13:40:38.174 UTC [TRACE] steampipe: parse complete after 1 decode passes
2022-08-10 13:40:38.175 UTC [TRACE] steampipe: parse complete after 1 decode passes
2022-08-10 13:40:38.175 UTC [TRACE] steampipe: telemetry.Init service 'steampipe', tracingEnabled: false, metricsEnabled: false
2022-08-10 13:40:38.175 UTC [TRACE] steampipe: metrics and tracing disabled' - returning
Welcome to Steampipe v0.15.4
For more information, type .help
2022-08-10 13:40:38.629 UTC [TRACE] steampipe: ensureSessionSearchPath
2022-08-10 13:40:38.629 UTC [TRACE] steampipe: updated the required search path to [omitted]
2022-08-10 13:40:38.629 UTC [TRACE] steampipe: session search path will be updated to [omitted]
2022-08-10 13:40:38.754 UTC [TRACE] steampipe: CreatePreparedStatements
Error: failed to load schemas: sql: expected 8 destination arguments in Scan, not 9
2022-08-10 13:40:42.262 UTC [TRACE] steampipe: cancel handler exiting
2022-08-10 13:40:42.262 UTC [TRACE] steampipe: DbClient.Close &{0 0xc0003047b0 0 {0 0} [] map[] 0 1 0xc00009ea80 false map[0xc0001007e0:map[0xc0001007e0:true]] map[] 1 1 0 0 0 0 0 0 0x108f180}
Both the local and remote steampipe are the same version. The service process runs on Linux and the query process runs on MacOS. Connecting to a remote service instead of local is the only other difference I see in the working and non-working configuration.
Steampipe version (steampipe -v)
v0.15.4
The text was updated successfully, but these errors were encountered:
Thanks for reporting this @zfLQ2qx2 ... I can confirm that I'm seeing the same problem testing against my cloud database:
~/src/steampipe.io $ steampipe query --workspace-database postgresql://e-gineer:redacted@e-gineer-scratch.usea1.db.steampipe.io:9193/redacted
Welcome to Steampipe v0.16.0-rc.9
For more information, type .help
>
Error: failed to load schemas: sql: expected 8 destination arguments in Scan, not 9
~/src/steampipe.io $
It also fails in the shorthand version for cloud:
~/src/steampipe.io $ steampipe query --workspace-database e-gineer/scratch
Welcome to Steampipe v0.16.0-rc.9
For more information, type .help
>
Error: failed to load schemas: sql: expected 8 destination arguments in Scan, not 9
@e-gineer Great! I was about to write that this seemed specific to the steampipe client, I downloaded a generic postgres client and I had no issues running queries. How long until your change makes a release?
Describe the bug
This is a really interesting bug but I seem to be able to hit it consistently. Running steampipe locally in a container works perfectly. However when I try to use steampipe query to connect to a remote service then I'm getting killed after a couple seconds with "Error: failed to load schemas: sql: expected 8 destination arguments in Scan, not 9"
steampipe query --workspace-database postgres://steampipe:xxx@hhh:9193/steampipe
2022-08-10 13:40:38.172 UTC [TRACE] steampipe: no modfile exists in workspace folder - NOT creating pseudoresources and only loading resource files from top level folder
2022-08-10 13:40:38.174 UTC [TRACE] steampipe: parse complete after 1 decode passes
2022-08-10 13:40:38.175 UTC [TRACE] steampipe: parse complete after 1 decode passes
2022-08-10 13:40:38.175 UTC [TRACE] steampipe: telemetry.Init service 'steampipe', tracingEnabled: false, metricsEnabled: false
2022-08-10 13:40:38.175 UTC [TRACE] steampipe: metrics and tracing disabled' - returning
Welcome to Steampipe v0.15.4
For more information, type .help
Error: failed to load schemas: sql: expected 8 destination arguments in Scan, not 9
2022-08-10 13:40:42.262 UTC [TRACE] steampipe: cancel handler exiting
2022-08-10 13:40:42.262 UTC [TRACE] steampipe: DbClient.Close &{0 0xc0003047b0 0 {0 0} [] map[] 0 1 0xc00009ea80 false map[0xc0001007e0:map[0xc0001007e0:true]] map[] 1 1 0 0 0 0 0 0 0x108f180}
Both the local and remote steampipe are the same version. The service process runs on Linux and the query process runs on MacOS. Connecting to a remote service instead of local is the only other difference I see in the working and non-working configuration.
Steampipe version (
steampipe -v
)v0.15.4
The text was updated successfully, but these errors were encountered: