Skip to content

Qualify the complete Emscripten callback catalog for static Worker Pyodide assets #780

Closed

Description

@kamilio

Poe2 integration CI found an unhandled initialization rejection while production buffered-shell Python assertions passed. Stack: reportUndefinedSymbols → addFunction → convertJsFunctionToWasm → static asset registry CompileError.

Pinned Pyodide 314.0.6 first requested the vi adapter, then vii. The recipe admitting only loader helpers/ccall/empty module omitted the initialization callback signature catalog.

Poe2 now authenticates the glue's exact size/SHA256, extracts its finite literal .sig annotations, normalizes wasm32 pointers to i32, and builds static import/re-export callback modules with the pinned padded ULEB encoding. All assets are statically precompiled; runtime admission still compares complete bytes. No dynamic compilation/unsafeEval/global engine patch is granted.

The focused production Worker test now passes with zero unhandled rejections. Please include the full callback catalog in the documented static asset recipe and upstream qualification, including an unhandled-error gate.

Reproduction: https://github.com/poe-internal/poe2/actions/runs/35409396941/job/105805774321
Clean startup qualification: https://github.com/poe-internal/poe2/actions/runs/35409969068/job/105807463304 (later failed because a newly deployed temporary probe returned404 before readiness)
Integration PR: https://github.com/poe-internal/poe2/pull/14982

Activity

  1. changed the title [-]Qualify Emscripten's startup vi callback adapter for static Worker Pyodide assets[/-] [+]Qualify the complete Emscripten callback catalog for static Worker Pyodide assets[/+] on Sep 19, 2026
  2. kamilio commented on Sep 19, 2026

    @kamilio
    MemberAuthor

    The complete 96-signature catalog has now passed hosted Cloudflare qualification, beyond Miniflare startup: native Python/source imports, device metadata, positioned I/O and truncation, finalization/fresh globals, and independent canonical 9 MiB and 100 MiB hash readback. Unknown/altered runtime Wasm remains rejected; no runtime compilation grant was added.

    Evidence: https://github.com/poe-internal/poe2/actions/runs/35410198572 at aa0b37b10d44a44c3b10c34938ae52b3b58ddebc. All runtime and storage cases passed; the job failed only when its final harness directory removal omitted required conditional versions. Corrected directory cleanup and the restored Worker binding/flag/temporary secret/probe audit passed in https://github.com/poe-internal/poe2/actions/runs/35411441873 at 257e51a7d270ec340f219a6bfbb77ba01b7fe727. The later source changes only bound test fan-out and formatting; runtime catalog code is unchanged.

    The current preview runs the original application entrypoints with this catalog. #781 separately tracks measured remote I/O latency.

  3. poe-code-agent commented on Sep 19, 2026

    @poe-code-agent
    Contributor

    Issue was resolved by #3eae1df

    Update poe-code via npm install -g [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions