Skip to content

Classify private-safe account-facts publish failures - #331

Merged
Pigbibi merged 2 commits into
mainfrom
codex/binance-publish-error-codes-20261002
Oct 2, 2026
Merged

Pigbibi merged 2 commits into
mainfrom
codex/binance-publish-error-codes-20261002

Conversation

@Pigbibi

@Pigbibi Pigbibi commented Oct 2, 2026

Copy link
Copy Markdown
Collaborator

Purpose

Classify the existing account-facts POST failure without printing private response bodies, URLs, tokens, identifiers or exception messages.

Changes

  • Only known receiver status/code pairs become fixed diagnostic labels.
  • Response reads stay bounded to 4097 bytes with a 4096-byte parse limit.
  • Network, timeout and invalid acknowledgements get fixed stop codes.
  • No retry, redirect, payload validation or success semantics change.

Validation

Synthetic cases cover known HTTP failures, unexpected/private/oversized response bodies, malformed acknowledgements and transport failures. Runtime publishing is still stopped pending readback of the earlier write outcome.

Pigbibi and others added 2 commits October 2, 2026 23:17
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
@Pigbibi
Pigbibi merged commit d9fe471 into main Oct 2, 2026
1 check passed
@Pigbibi
Pigbibi deleted the codex/binance-publish-error-codes-20261002 branch October 2, 2026 15:53
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.

1 participant