Missing Credentials Error when deploying to Vercel

[archiewood]

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

• High - I'm not able to use Evidence until this bug is fixed
• Medium - I'm able to use Evidence, but a feature I need to use is not working
• Low - I'm able to keep using Evidence as normal, but flagging this for the team to fix

Expected Behavior
It should deploy.

Workarounds
Use Netlify or Evidence Cloud to deploy.

Environment Information
Package versions: v15.0.1

Database:

• Postgres
• BigQuery
• Snowflake
• Redshift
• MySQL
• SQLite
• DuckDB
• CSV
• Other (please specify)

[mcrascal]

To reproduce:

1. Building Evidence from a sub directory, called reports (need to confirm it does work in root)
2. Using duckdb where the database file is checked into the repo, per the docs

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.

[archiewood]

I repro'ed the error when building in root last week, using this repo.

[archiewood]

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:

[archiewood]

reproduced in template project: https://template-azyx44stb-evidence-dev.vercel.app/

vs netlify: https://main--evidence-template.netlify.app/

[archiewood]

This appears to be a duckdb specific issue. Snowflake does not exhibit the same behaviour.

[ItsMeBrianD]

/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.

[archiewood]

I’d at least try opening an issue with duckdb? They are pretty responsive and helpful.

[mcrascal]

@ItsMeBrianD

Good find

• Open issue over on ddb and flag this for those folks
• Docs update (e.g. a warning that currently Vercel can't build sites with duckdb due to an incompatibility in their build env)
• Avoid building non-R builds in branches that start with r/ duckdb/duckdb#763 if time

[archiewood]

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

[ItsMeBrianD]

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

[ItsMeBrianD]

We can track this here: duckdb/duckdb-node#15
Going to update docs and move on for the time being

[michaelwallabi]

FYI, the issue with GLIBC can be resolved by using duckdb-lambda-x86, as mentioned in the duckdb bug above. I've not tried with Evidence yet but have used this to deploy node based duckDB in Vercel successfully.