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
Using .malloysql file with Duckdb connection (+ httpfs extension) it is possible to query files on S3 API compatible storage (in this case Cloudflare R2) and also S3 itself.
Unfortunately several errors show up (or not) and it seems that the longer I wait between each try to run the cell with code, the more errors i can get. Code in cell works randomly - sometimes success at first try, sometimes 1 or 2 or 3 errors from the list:
1st error: TransactionContext Error: cannot start a transaction within a transaction
2nd error: The worker process has died, and has been restarted. This is possibly the result of a database bug. Please consider filing an issue with as much detail as possible at https://github.com/malloydata/malloy-vscode-extension/issues. You many want to use an external NodeJS process to increase the amount of available memory by setting vscode://settings/malloy.nodePath
4th - success or not working at all (pop up window with 'channel closed' message)
I managed to get all above errors with code below. I also connected to S3 using IAM role and with 4 tries i only once get an error no 3 (i will recheck next week).
To Reproduce
Using malloysql file with language set to Malloy SQL:
What happens?
Using .malloysql file with Duckdb connection (+ httpfs extension) it is possible to query files on S3 API compatible storage (in this case Cloudflare R2) and also S3 itself.
Unfortunately several errors show up (or not) and it seems that the longer I wait between each try to run the cell with code, the more errors i can get. Code in cell works randomly - sometimes success at first try, sometimes 1 or 2 or 3 errors from the list:
1st error: TransactionContext Error: cannot start a transaction within a transaction
2nd error: The worker process has died, and has been restarted. This is possibly the result of a database bug. Please consider filing an issue with as much detail as possible at https://github.com/malloydata/malloy-vscode-extension/issues. You many want to use an external NodeJS process to increase the amount of available memory by setting vscode://settings/malloy.nodePath
3rd - error (not always): Progress handler for token vscode-notebook-cell:/c%3A/Users/Wasyl/Desktop/Malloy/try/test.malloysql#W0sZmlsZQ%3D%3D already registered
4th - success or not working at all (pop up window with 'channel closed' message)
I managed to get all above errors with code below. I also connected to S3 using IAM role and with 4 tries i only once get an error no 3 (i will recheck next week).
To Reproduce
Using malloysql file with language set to Malloy SQL:
--connection: duckdb
CREATE SECRET (
TYPE R2,
KEY_ID 'token',
SECRET 'secret',
ACCOUNT_ID 'id'
)
OS:
Windows 10
Malloy Client:
local VSCode
Malloy Client Version:
pre-release 0.3.1734534022
Database Connection:
DuckDB
The text was updated successfully, but these errors were encountered: