axios shim: response.status and response.data are undefined on live HTTPS GET

[proggeramlug]

What happened

await axios.get(<live URL>) resolves to a response object whose .status and .data are both undefined, instead of the actual HTTP status and body.

What you expected

status should be 200 (or whatever the upstream returns) and data should be the parsed/decoded body, matching node's axios behaviour.

Minimal reproduction

import axios from 'axios';

async function main(): Promise<void> {
  const r = await axios.get(
    'https://api.bsky.app/xrpc/app.bsky.feed.searchPosts?q=perry&limit=1',
    { timeout: 10000, validateStatus: () => true },
  );
  console.log('status:', r.status);
  console.log('data type:', typeof r.data);
  process.exit(0);
}
main().catch((e) => { console.log('err:', e); process.exit(1); });

Command:

perry compile repro.ts -o repro
./repro

Observed output:

status: undefined
data type: undefined

Expected: status: 200, data type: object (or string).

The same code under Node 20 + tsx returns the real response and 33 bookmarks for that endpoint.

Environment

• Perry version: 0.5.395
• Host OS: macOS 26.4 (arm64)
• Target: native
• Installed via: cargo (~/.cargo/bin/perry)

Diagnostic output

Compiles clean. When the listener's fetch loop hits await axios.get(…) later in the program, Perry prints [PERRY WARN] js_box_get: null box pointer #0 shortly before exiting — possibly a related downstream symptom in the await chain when the response object lacks expected fields.

Found while compiling skelpo-listener — the seven-channel fetch path runs to completion (no crash) but every channel returns 0 items because every HTTP response has undefined status/data.

[proggeramlug]

Fixed in v0.5.459 (commit ab0a7c0 — auto-closed by the commit message's closes #340 reference).

Three layered defects, fixed across 5 files:

1. crates/perry-stdlib/src/axios.rs queued Ok(handle as u64) to the promise resolver without NaN-boxing — the awaiter saw a subnormal float (bits=1), not a POINTER_TAG'd handle. Property access on a subnormal silently returned undefined. Fix: NaN-box with POINTER_TAG ((handle as u64) | 0x7FFD_0000_0000_0000) at all 5 axios methods (get/post/put/delete/patch).
2. crates/perry-runtime/src/object.rs::js_object_get_field_ic_miss bailed at obj < 0x10000 for handle receivers, never reaching HANDLE_PROPERTY_DISPATCH. Added a small-handle guard that routes 1..0x100000 to the dispatcher.
3. crates/perry-stdlib/src/common/dispatch.rs::js_handle_property_dispatch had no axios arm. Added: when with_handle::<AxiosResponseHandle>(handle) returns true and property is status/data/statusText, dispatch to js_axios_response_status/_data/_status_text.

Plus a defensive small-handle guard in the codegen's PropertyGet IC fast path (crates/perry-codegen/src/expr.rs) via select so handle receivers cleanly miss to the slow path without SIGSEGV — also fixes a latent crash that was masked by the dispatcher returning undefined.

Verified: your literal repro now prints status: 200 / data type: string (was undefined / undefined). The [PERRY WARN] js_box_get: null box pointer #0 you saw is also resolved (it was a downstream symptom of the undefined response.data being chained into a fetch loop). Parity 190/190 — no regressions.