Repository navigation
Fix phantom balance status reporting - #2
Conversation
Currently, if the attempt budget is exhausted without reaching CORROBORATION_MIN_AGREE, the fallback logic selects the most conservative snapshot and returns it but leaves its status as "OK". This causes `main.py` to accept this potentially phantom balance as a valid result. This commit adds `chosen["status"] = "ERROR"` to the fallback logic so that uncorroborated balances are correctly flagged as errors and excluded from the successful totals. Co-authored-by: privatekey7 <[email protected]>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Fixes the issue where phantom balances resurfaced by ensuring uncorroborated fallback snapshots return
status="ERROR"rather than"OK".PR created automatically by Jules for task 6051294480269583184 started by @privatekey7