issues Search Results · language:Dune language:Python language:Java language:JavaScript language:Java language:Go
Filter by
60.8M results
Upstream testing failure
Workflow: CI Upstream Run: 27888281361 Date: Sun Jun 21 00:30:41 UTC 2026
Meowdy! Upstream testing has failed.
Please check the workflow run for details.
This issue was automatically ...
testing
QA並列テストで見つかった軽微バグ(P3)と堅牢性ギャップのまとめ。個別Issue化は重いため集約。すべて staging chore/...orphan-clean-base の shogi_v4.html を node v22
で実行確認(D-02のみ非到達のlatent)。
D-01 報告書で賞金0円が「▲0円」表示
- downloadReport() の var prizeDisplay= ...
On two accounts (two separate services), emails saying the account has been hacked, the sender sends (from this last
one, was a Brazil IP address). The DKIM validates as the From email address (which is ...
Problem
Ruby hash filter helpers yield key/value pairs to one-parameter blocks. Vibescript s Hash#select and Hash#reject
currently pass the key as the first block argument and the value as the second, ...
概要
JSON.stringify(state) が循環参照で TypeError を投げると、quota 判定の外で notifyError に落ち、ユーザーへの alert が出ないまま保存に失敗する。
重大度
P2(エッジだが、保存失敗が無通知だとデータ消失に直結)
再現手順(node実行で確認・T6)
- state に循環参照を作って save() → TypeError、alert ...
Problema
O docs-check já faz declaração dispara validação em vários pontos ad-hoc: resolução de ponteiro de contexto
(validate_router), regras de Spec por status, tier T0/T1, gate por host do remote (ADR-0006). ...
What problem would this solve?
Enable users to have colour palette presets, speed, page size, or any other per-device config presets. This may save
some time with the cli args.
Proposed solution
one ...
enhancement
A mortal judging process was launched at 2026-06-21T00:30:21Z.
- gate (node): value-gate.claude.v1
- atom (claim): atom.local-preview.v0
- prompt_hash: bd2e876fdf4c1246…
This issue opened at the ...
概要
rounds: Number(s.rounds)||4 の正規化が不十分で、-3 や 2.7 がそのまま保持され、0 は || により 4 に化ける。
重大度
P2(不正な回戦数で表示・進行ロジックが乱れる)
再現手順(node実行で確認・T10)
- state.rounds に -3 / 2.7 / 0 を与えてロード → それぞれ -3 / 2.7 / 4 になる。
期待 ...
概要
normalizeState が entry_no 不在の参加者に index+1 を補完するため、別レコードの明示 entry_no=1 と衝突して重複が発生する。nextEntryNoForClass は既存の重複を検知しない。
重大度
P2(受付番号の重複表示・取り違えの恐れ)
再現手順(node実行で確認・T27)
- entry_no 明示と未設定が混在する players ...

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.