Ryan comments

Results 7 comments of


                                            Ryan

Moving test out of init

bump, any reason this can't go in?

Query to information_schema.columns selects columns from all schemas

It doesn't add the columns to the new schema, since it thinks they already exist. I was able to resolve my issue by removing the `schema-v1`. But it wasn't immediately...

Query to information_schema.columns selects columns from all schemas

Looks like there is a `table_schema` key that you can check against, so something like `if (!tableColumns[type].some(row => row.column_name === field && row.table_schema === currentSchema)`

fix: timed out fetching a new connection from the connection pool.

Is this ready to merge?

fix: timed out fetching a new connection from the connection pool.

Looks like this has stalled out again, we are seeing this issue on our live app

initializeWasm fails from browser import on latest version (3.2.0)

Seems related to web crypto: https://github.com/automerge/automerge/blob/main/javascript/HACKING.md#getrandom-support

initializeWasm fails from browser import on latest version (3.2.0)

Can force automerge-repo to use 3.2.0: `import { initializeWasm } from "https://esm.sh/@automerge/automerge-repo/slim?deps=@automerge/[email protected]";`

Ryan

Moving test out of __init__

Query to information_schema.columns selects columns from all schemas

Query to information_schema.columns selects columns from all schemas

fix: timed out fetching a new connection from the connection pool.

fix: timed out fetching a new connection from the connection pool.

initializeWasm fails from browser import on latest version (3.2.0)

initializeWasm fails from browser import on latest version (3.2.0)

Moving test out of init