You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Event POST requests are not retried after transient 5xx responses #528
EventDispatcher configures retries for 500/502/503/504, but does not include POST in urllib3's allowed_methods, so event POSTs do not receive the status retries intended by #445 and #475. A local HTTP server returning 503 on its first request and 200 thereafter, exercised with the production EventDispatcher class and a real requests adapter on master 7649661, receives two requests for GET (success) but only one for POST (logged dispatch failure); the batch processor has already removed the batch before dispatch. Would you accept a PR adding POST to the retryable methods, preserving the existing retry count and backoff, with a regression test using a real HTTP adapter? If so, could you provide the FSSDK ticket reference required by the PR workflow?
Hi alexcastgonz (@pcbeingused333), thanks for raising this. If you are interested in contributing please read CONTRIBUTING.md. FSSDK is our internal ticket flow, external PRs are managed seperately.
Activity
FarhanAnjum-opti commentedon Nov 16, 2026
Hi alexcastgonz (@pcbeingused333), thanks for raising this. If you are interested in contributing please read CONTRIBUTING.md. FSSDK is our internal ticket flow, external PRs are managed seperately.