Skip to content

[WIP] Fix deserialization issues for Gemini API responses#72

Closed
Copilot wants to merge 1 commit into
63-sometimes-failed-deserialize-gemini-api-responsesfrom
copilot/fix-gemini-api-deserialization
Closed

[WIP] Fix deserialization issues for Gemini API responses#72
Copilot wants to merge 1 commit into
63-sometimes-failed-deserialize-gemini-api-responsesfrom
copilot/fix-gemini-api-deserialization

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 31, 2026

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.


This section details on the original issue you should resolve

<issue_title>sometimes Failed deserialize Gemini API responses</issue_title>
<issue_description>I haven't found out cause of this problem yet.

guess causes

  • not enough struct field for deserialize
  • llm problems(e.g. api limit)
    • fix: be parsable more details of api errors
    • (temp): when failing parse a response, parse response as de and print raw response.</issue_description>

<agent_instructions>pls fix</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@Uliboooo exmaple
:) ggw commit -m gemini/gemini-3-flash-preview
⠏ LLM call finished.
Error: Llm(ChatCompletion("Deserialization error: error decoding response body"))
```</body></comment_new>
</comments>

Copilot AI linked an issue Mar 31, 2026 that may be closed by this pull request
Copilot stopped work on behalf of Uliboooo due to an error March 31, 2026 09:11
Copilot AI requested a review from Uliboooo March 31, 2026 09:11
@Uliboooo Uliboooo closed this Mar 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

sometimes Failed deserialize Gemini API responses

2 participants