Retire parser-gem frozen-string warning filter when upstream fixes it #489
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#489
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
parser-3.3.12.0 Buffer#reencode_string (buffer.rb:97) mutates literal strings, spamming Ruby 4.0 deprecation warnings under RUBYOPT=-w. A scoped Warning filter was added in plugins/os-sdlc/tests/test_helper.rb on 2026-08-23. When whitequark/parser ships a Ruby-4.0-compatible release, upgrade and delete the filter.
Tasks
Acceptance criteria
no filter needed; warning wall absent on verbose runs.
Origin
Frozen 2026-08-23: upstream parser gem is still 3.3.12.0 (2026-07-16); no release, issue, or PR fixes the Buffer#reencode_string literal mutation. Nothing actionable until a newer parser ships. Filter in tests/test_helper.rb stays in place.