issues Search Results · language:Dune language:JavaScript language:JavaScript language:PHP language:JavaScript
Filter by
24.6M results
Category
stdlib · php-src-strict
Problem
After sort() / asort() / arsort() mutates an array by reference, indexed access and foreach observe the sorted order,
but var_export($array) (and compliance ...
area:vm
enhancement
implementation-ready
phase-4:stdlib
stdlib
Category
stdlib · php-src-strict
Problem
Builtins that take (array $array, callable $callback) reject inline closure/arrow callbacks with TypeError: Argument #1
($array) must be of type array, Closure ...
area:vm
enhancement
implementation-ready
phase-4:stdlib
stdlib
Part of: #1
Problem Statement
A dense field of overlapping leaves looks right on screen because fills composite in painter s order — but a pen plotter
can t paint fills, it draws strokes. To plot the ...
needs-triage
size:feature
Part of: #1
Problem Statement
The Harness is only as convincing as the first real Sketch that runs on it. I want a non-trivial generative piece — a
flowing field of overlapping leaves/petals, organic ...
needs-triage
size:feature
Describe the bug
In src/Pages/Projects/SubmitProject.js, the Remove image button inside the project image upload section has aria-label=
button — a meaningless value that provides no useful description ...
Problem
The observability/dashboard contract exists, but full receipt capture is not yet consistently automated across the k6
proof path.
Current docs/assets observed:
- tools/k6-proofs/METRICS.md ...
needs:owner
proofs:integration
proofs:k6
ISSUES
上周有 24 个新 issue。 24 个 issue 已经被关闭,0 个 issue 仍然保持打开状态。
CLOSED ISSUES
:heart: #3202 项目周报 (2026 年 6 月 13 日 - 2026 年 6 月 20 日), by taro-bot2[bot] :heart: #3201 项目周报 (2026 年 6 月 13 日 - 2026 年 6
月 ...
weekly-digest
Problem
The k6 PROOFS scaffold is real, but there is not yet a clearly documented and verified golden path from one low-risk row
through:
k6 run → postprocess/evidence-writer → candidate artifact directory ...
needs:owner
proofs:integration
proofs:k6
Problem
Several row manifests reference scenario names that do not currently exist under tools/k6-proofs/scenarios/, so the
manifest registry is ahead of runnable k6 coverage.
Byte snapshot from main@a509640e0bdde9d54501f68ae291c22bc67bcf83: ...
needs:owner
proofs:coordination
proofs:k6
Problem
The current GitHub Actions workflow dispatch surface is stale against the checked-in k6 scenario tree, so the
documented/visible workflow choices are not reliable proof entrypoints.
Byte snapshot ...
needs:owner
proofs:integration
proofs:k6

Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.