Link state errors to the operation that established the relevant state
還沒有人認領這個 Issue。
評估
研究方向
Start with the E_A3_07_ScannerOutputStage example and trace how verifier provenance metadata reaches the error DTO and extension link. Check how state transitions and @StateSet/@StateRefinement information are currently represented, then verify the acceptance cases: preserved origins, separate receiver origins, constructor origins, and no link for ambiguous branches. Confirm that existing verification results remain unchanged.
由索引模型根據 Issue 內容生成。
描述
Problem
A state error points to the rejected call, but often leaves the developer searching for the earlier operation that established the receiver's relevant state. In E_A3_07_ScannerOutputStage, preview.setTiling(...) fails at line 59 because preview.setTilingMode(MODE_COPY_FROM_METADATA) at line 53 left its tiling state at startTiling. Intervening compression calls make that connection harder to spot.
Proposed first version
Track the source location of the call or construction that establishes a receiver's state in a particular @StateSet. Carry that origin through operations that preserve that state set. When a state error occurs, include a clickable “State established here” location only when the origin is unambiguous. Record the user-code call site after resolving the resulting state, rather than the location of the @StateRefinement declaration.
Start with straight-line code and a known resulting state. For the scanner example, the link should lead to line 53. If the origin cannot be established reliably, keep the current error without a link.
This needs verifier provenance metadata carried to the error DTO and an extension link to display it. Existing source mappings alone do not provide a reliable transition history. The feature is deterministic and does not require an LLM.
Acceptance criteria
- Calls affecting another state set do not replace the tiling origin.
- Two receivers, such as
archiveandpreview, retain separate origins. - Constructor-established states can point to construction where applicable.
- Branches with different possible origins, or transitions whose resulting state cannot be resolved reliably, do not produce a misleading single link.
- Existing verification results remain unchanged.
Priority and scope
Lower priority, technically difficult enhancement. A conservative first version is preferable to guessing an origin in complex control flow.
- 主要語言
- Java
- 星號
- 67
- 分支
- 36
- 平均合併
- 7 天 48 分鐘
- 30 天內合併 PR
- 2
環境準備
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
liquid-java/liquidjava 的其他 Issue
-
難度 4/5 3-5 天 新手友好度 48/100
liquid-java/liquidjava#297 ·
-
難度 4/5 3-5 天 新手友好度 55/100
liquid-java/liquidjava#296 ·
-
難度 4/5 3-5 天 新手友好度 48/100
liquid-java/liquidjava#295 ·
-
Add a flag -a to show all verification conditions sent to the smt solver可能重新可做 @CatarinaGamboa 於 118 天前認領，目前沒有進行中的 PR。 未關閉enhancement
liquid-java/liquidjava#240 · 已指派 1 人 ·
-
enhancement ide
難度 3/5 1-2 天 新手友好度 45/100
liquid-java/liquidjava#206 ·
查看 liquid-java/liquidjava 的全部 Issue
相似的 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 78/100
-
feature triaged
難度 1/5 1 小時以內 新手友好度 75/100
Graylog2/graylog2-server#27549 ·
維護者通常 1 天內回覆
-
component/zeebe kind/bug
難度 1/5 1 小時以內 新手友好度 90/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
UniversalMediaServer/UniversalMediaServer#6356 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 85/100
googleapis/google-cloud-java#14533 ·
維護者通常 1 天內回覆