Process completed with exit code 18.

note: �run_ends_schema� was declared here

note: �value_schema� was declared here

note: �key_schema� was declared here

note: �using NifRes<AdbcDeleteOnGC>::val_type = struct AdbcDeleteOnGC� {aka �struct AdbcDeleteOnGC�} declared here

required from here

note: �using NifRes<ArrowArrayStreamRecord>::val_type = struct ArrowArrayStreamRecord� {aka �struct ArrowArrayStreamRecord�} declared here

required from here

Process completed with exit code 18.

note: �run_ends_schema� was declared here

note: �value_schema� was declared here

note: �key_schema� was declared here

note: �using NifRes<AdbcDeleteOnGC>::val_type = struct AdbcDeleteOnGC� {aka �struct AdbcDeleteOnGC�} declared here

required from here

note: �using NifRes<ArrowArrayStreamRecord>::val_type = struct ArrowArrayStreamRecord� {aka �struct ArrowArrayStreamRecord�} declared here

required from here

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Using `length/1` is expensive, prefer comparing against an empty list.

Nested modules could be aliased at the top of the invoking module.

Nested modules could be aliased at the top of the invoking module.

Nested modules could be aliased at the top of the invoking module.

�run_ends_schema� may be used uninitialized [-Wmaybe-uninitialized]

�value_schema� may be used uninitialized [-Wmaybe-uninitialized]

�key_schema� may be used uninitialized [-Wmaybe-uninitialized]

�void* memset(void*, int, size_t)� clearing an object of type �using NifRes<AdbcDeleteOnGC>::val_type = struct AdbcDeleteOnGC� {aka �struct AdbcDeleteOnGC�} with no trivial copy-assignment; use assignment or value-initialization instead [-Wclass-memaccess]

�void* memset(void*, int, size_t)� clearing an object of non-trivial type �using NifRes<ArrowArrayStreamRecord>::val_type = struct ArrowArrayStreamRecord� {aka �struct ArrowArrayStreamRecord�}; use assignment or value-initialization instead [-Wclass-memaccess]

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Using `length/1` is expensive, prefer comparing against an empty list.

Nested modules could be aliased at the top of the invoking module.

Nested modules could be aliased at the top of the invoking module.

Nested modules could be aliased at the top of the invoking module.

�run_ends_schema� may be used uninitialized [-Wmaybe-uninitialized]

�value_schema� may be used uninitialized [-Wmaybe-uninitialized]

�key_schema� may be used uninitialized [-Wmaybe-uninitialized]

�void* memset(void*, int, size_t)� clearing an object of type �using NifRes<AdbcDeleteOnGC>::val_type = struct AdbcDeleteOnGC� {aka �struct AdbcDeleteOnGC�} with no trivial copy-assignment; use assignment or value-initialization instead [-Wclass-memaccess]