mirror of
https://github.com/NikkeTryHard/zerogravity.git
synced 2026-04-25 15:15:59 +03:00
[GH-ISSUE #78] 继续反馈1.3.8版本关于gemini-3-pro-image的问题 #69
Labels
No labels
bug
enhancement
enhancement
notice
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/zerogravity#69
Loading…
Add table
Add a link
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?
Originally created by @szansonhuang on GitHub (Feb 25, 2026).
Original GitHub issue: https://github.com/NikkeTryHard/zerogravity/issues/78
diagnostic.zip
14-31-03_gemini-3-pro-image-137e189b.zip
@NikkeTryHard commented on GitHub (Feb 26, 2026):
Homie update: work is done and shipped from the private source branch
fix/issue-78-context-guardand PRNikkeTryHard/zerogravity-src#165(now closed per request after rebase/cleanup).What was fixed for the gemini-3-pro-image flow:
generate_imageprompt (instead of dropping it via.is_some()), so image follow-up can actually run.Verification run:
cargo test --bin zerogravity mitm::proxy::testscargo test --bin zerogravity chunk_path_retains_generate_image_prompt_for_followupcargo buildcargo clippy --all-targetsNote: there is a separate long-running integration-test behavior (
responses_tool_result_without_captured_calls_fails_fast) that is independent from this image-flow root fix.@NikkeTryHard commented on GitHub (Feb 26, 2026):
Closing as fixed based on the implemented and validated source changes referenced above. If any remaining symptom appears, open a new issue with fresh trace bundle and we’ll isolate it as a separate regression.