-
Notifications
You must be signed in to change notification settings - Fork 33.5k
[Bug]: Type issue in GPT pools #25516
Copy link
Copy link
Closed as not planned
Labels
P1High — major feature broken, no workaroundHigh — major feature broken, no workaroundcomp/agentCore agent loop, run_agent.py, prompt builderCore agent loop, run_agent.py, prompt builderprovider/openaiOpenAI / Codex Responses APIOpenAI / Codex Responses APIsweeper:implemented-on-mainSweeper: behavior already present on current mainSweeper: behavior already present on current maintype/bugSomething isn't workingSomething isn't working
Metadata
Metadata
Assignees
Labels
P1High — major feature broken, no workaroundHigh — major feature broken, no workaroundcomp/agentCore agent loop, run_agent.py, prompt builderCore agent loop, run_agent.py, prompt builderprovider/openaiOpenAI / Codex Responses APIOpenAI / Codex Responses APIsweeper:implemented-on-mainSweeper: behavior already present on current mainSweeper: behavior already present on current maintype/bugSomething isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for issues without a type.
Bug Description
Trigger: Every outbound request to a GPT-family provider (OpenAI
gpt-, OpenRouter, etc.) fails immediately with this error before any HTTP request is made.*Full traceback points to:
gateway/provider_pool/credential_pool.pyline 277, in function_exhausted_until(entry, entry.last_error_code)Root cause: Pool entry serialization via
to_dict()/from_dict()round-tripslast_status_atas an ISO string (e.g."2026-05-11T08:23:20.891066+00:00") instead of a Unix epoch float. When the entry is reloaded from disk and_exhausted_untilis called,str + intraisesTypeError.The existing
_parse_absolute_timestamp()helper already handles ISO strings, epoch ms, and float epochs — it just was not being applied tolast_status_aton the rehydrated entry.Steps to Reproduce
Use a GPT codex pool and have one hit its limits
Expected Behavior
No error
Actual Behavior
Errror
Affected Component
Agent Core (conversation loop, context compression, memory)
Messaging Platform (if gateway-related)
Telegram
Debug Report
Have no access right now, but the fix above fixed it for meOperating System
Ubuntu
Python Version
No response
Hermes Version
No response
Additional Logs / Traceback (optional)
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?