4 GC-corpus gap fixtures fail node parity on main (URL pathname set, NextRequest query, native call path arg, numeric element group)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- nextjs, typescript
- Domain
- compilers
Research direction
Start by running the four gap fixtures (test_gap_gc_store_ic_generic_receivers, test_gap_gc_next_request_import, test_gap_gc_11789_native_call_args, test_gap_repsel_element_group_numeric) on main and comparing with node output, in default and PERRY_GC_FORCE_EVACUATE=1 mode. The issue suggests the URL pathname failure is a setter/accessor store path, but the other three are not bisected yet. Done means all four match node parity in both modes, and the moving-GC and stress corpora are green again.
Written by the indexing model from the issue text.
Description
Four gap fixtures fail node parity on main (verified base 99224e67b4, fresh full-runtime build), in both default and moving-GC mode (PERRY_GC_FORCE_EVACUATE=1). As a result, the moving-GC corpus (3 FAIL) and the stress corpus (28 FAIL, the same 4 fixtures across 7 arms) are red on main. None of them needs a collection to fail.
| Fixture | main rc | Symptom |
|---|---|---|
test_gap_gc_store_ic_generic_receivers |
0 | URL pathname writes leave pathname /; href stays https://example.com/?x=1 |
test_gap_gc_next_request_import |
0 | NextRequest query parameters read as missing |
test_gap_gc_11789_native_call_args |
1 | TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string before any GC |
test_gap_repsel_element_group_numeric |
1 | TypeError: Cannot read properties of undefined (reading 'y') |
Found while verifying the qstypeof3 PR, whose output for each fixture is byte-identical to main's. Raw stdout and stderr for both arms are kept on qb6 under /root/claude-lanes/qstypeof3g-results/baseline-failures/ and url-diagnose/.
The URL pair suggests a setter/accessor store path on URL objects; the other two look unrelated. Not bisected.
- Dominant language
- Rust
- Stars
- 4.9k
- Forks
- 166
- Avg merge
- 3h 23m
- Merged PRs (30d)
- 911
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PerryTS/perry
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
Maintainers usually reply within 1 day
Similar issues
-
documentation P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug good first issue priority:high
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Konfirm-xyz/konfirm-contracts#163 ·
Maintainers usually reply within 1 day
-
area:gc-repack-output bug factory:dogfood factory:triaged priority:p3 type:bug type:ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gitbutlerapp/grit#1161 · 1 comment ·
Maintainers usually reply within 1 day
-
feature performance
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
lance-format/lance#10137 ·
Maintainers usually reply within 2 days
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 85/100