What happens?

When creating a persistent HTTP secret on either an in-memory or a file persistent database, the secret will cause any HTTP interaction within it's scope to fail with INTERNAL Error: ExtraValueInfo type mismatch

To Reproduce

Example from motherduck.com, added persistent, first call works

duckdb -c "
CREATE PERSISTENT SECRET http (
    TYPE HTTP,
    EXTRA_HTTP_HEADERS MAP {
        'Authorization': 'Bearer sk_test_VePHdqKTYQjKNInc7u56JBrQ'
    }
);
select unnest(data) as customers 
from read_json('https://api.stripe.com/v1/customers')"

Rerun (duckdb must be restarted)

duckdb -c "select unnest(data) as customers 
from read_json('https://api.stripe.com/v1/customers')"

Result:

INTERNAL Error: ExtraValueInfo type mismatch
This error signals an assertion failure within DuckDB. This usually occurs due to unexpected conditions or errors in the program's logic.
For more information, see https://duckdb.org/docs/dev/internal_errors

OS:

MacOS

DuckDB Version:

v1.1.0 fa5c2fe

DuckDB Client:

DuckDB CLI

Hardware:

No response

Full Name:

Michael Simons

Affiliation:

Neo4j, Inc.

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have not tested with any build

Did you include all relevant data sets for reproducing the issue?

Yes

Did you include all code required to reproduce the issue?

• Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

• Yes, I have