Skip to content

Add #490 to KNOWN_ISSUES.md (missed at v0.0.113)#499

Merged
aallan merged 1 commit into
mainfrom
docs-known-issues-490
Apr 20, 2026
Merged

Add #490 to KNOWN_ISSUES.md (missed at v0.0.113)#499
aallan merged 1 commit into
mainfrom
docs-known-issues-490

Conversation

@aallan

@aallan aallan commented Apr 20, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Owner

Summary

Process note

Per the repo rule: new issues generated during a PR review must be added to ROADMAP.md or KNOWN_ISSUES.md as part of that same PR — main being protected means we can't drive-by-fix later, and leaving issues un-listed creates a gap between the tracker and the curated docs. This PR retroactively closes that gap for #490.

Test plan

  • python scripts/check_limitations_sync.py — still consistent (28 entries)
  • Pre-commit hooks pass

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

  • Documentation
    • Updated known issues documentation to record an identified garbage collection optimisation behaviour that may inadvertently affect certain opaque handle types. Whilst this behaviour is confirmed safe through conservative validation mechanisms deployed in the collection process, it may increase processing overhead and potentially lead to spurious mark retention during memory management operations in certain scenarios.

@aallan
Add #490 (array_fold over-rooting) to KNOWN_ISSUES.md
4bc3216 
Flagged during the #489 CodeRabbit review as a benign but wasteful
behavior: the ADT-rooting heuristic treats every i32 accumulator that
is not Bool/Byte as a GC-managed heap pointer, which over-roots
host-managed opaque handles (Map, Set, Regex, Decimal).  Conservative
GC rejects out-of-range values so nothing is corrupted, but it can
cause spurious mark retention under memory pressure.

Sits in the Bugs section alongside #346/#347/#348 (the existing
GC-opaque-handle cluster).

Co-Authored-By: Claude <noreply@anthropic.invalid>
@coderabbitai

coderabbitai Bot commented Apr 20, 2026 •
edited
Loading

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 1445af0c-946f-4d6e-901f-b9f7815602e6

📥 Commits

Reviewing files that changed from the base of the PR and between eeb7688 and 4bc3216.

📒 Files selected for processing (1)
  • KNOWN_ISSUES.md
📝 Walkthrough

Walkthrough

A documentation update to KNOWN_ISSUES.md introducing a new bug entry describing how the array_fold heuristic may over-root host-managed opaque handles (Map, Set, Regex, Decimal) as Vera heap pointers, which conservative GC rejects but increases mark work.

Changes

Cohort / File(s) Summary
Known Issues Documentation
KNOWN_ISSUES.md		 Added a new bug entry documenting that array_fold heuristic over-roots host-managed opaque handles; conservative GC safely rejects out-of-range values but this increases work and spurious mark retention.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly references the specific issue (#490) being documented and clearly indicates the action (adding to KNOWN_ISSUES.md) with context about the version milestone.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs-known-issues-490

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov

codecov Bot commented Apr 20, 2026 •
edited
Loading

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.27%. Comparing base (eeb7688) to head (4bc3216).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files 
@@           Coverage Diff           @@
##             main     #499   +/-   ##
=======================================
  Coverage   90.27%   90.27%           
=======================================
  Files          58       58           
  Lines       20276    20276           
  Branches      236      236           
=======================================
  Hits        18304    18304           
  Misses       1968     1968           
  Partials        4        4
Flag Coverage Δ
javascript 52.58% <ø> (ø)
python 95.05% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@aallan aallan merged commit 8c3eef9 into main Apr 20, 2026
19 checks passed
@aallan aallan deleted the docs-known-issues-490 branch April 20, 2026 15:34
@coderabbitai coderabbitai Bot mentioned this pull request May 5, 2026
Merged
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@aallan