Closed archiewood closed 1 year ago
To reproduce:
Suspicion is that this is a file path issue arising because of the subdirectory setting in vercel and the way we're reading the ddb instance. See below -- @archiewood repro'd without changing root directory.
I repro'ed the error when building in root last week, using this repo.
Looked into this in a bit more detail:
if I get vercel to run printenv DATABASE && printenv DUCKDB_FILENAME
during the build process, it successfully returns
But then later in the build:
reproduced in template project: https://template-azyx44stb-evidence-dev.vercel.app/
vs netlify: https://main--evidence-template.netlify.app/
This appears to be a duckdb specific issue. Snowflake does not exhibit the same behaviour.
/lib64/libm.so.6: version 'GLIBC_2.29' not found (required by /vercel/path0/node_modules/duckdb/lib/binding/duckdb.node)
Looks like this is related to the environment that vercel is running builds in; I'm not entirely sure how to proceed with this.
I’d at least try opening an issue with duckdb? They are pretty responsive and helpful.
@ItsMeBrianD
Good find
One thing I don't understand. I'm reasonably sure that duckdb projects used to build on vercel pre SK1.0? ie with v 14.0.0 or similar
I did a test on vercel to see which version of glibc
is being used, looks like it's ldd (GNU libc) 2.26
; so this might be a "duckdb upgraded their dep", rather than a SK breaking change
We can track this here: duckdb/duckdb-node#15 Going to update docs and move on for the time being
Bug Description
When attempting to deploy with duckdb to Vercel, Evidence fails to read in the database configuration.
Netlify does not have this issue.
Slack thread
Severity
Expected Behavior It should deploy.
Workarounds Use Netlify or Evidence Cloud to deploy.
Environment Information Package versions: v15.0.1
Database: