Skip to content

No provider-level retry / rate-limit handling #58

@djthorpe

Description

@djthorpe

No 429, Retry-After, or rate-limit logic anywhere in production code
Every provider API returns 429 under load; callers have no recovery path
Add shared retry middleware wrapping the Generator interface; inspect HTTP status + Retry-After header; insertion point: manager/generator.go Chat()/Ask() call paths

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions