ref(api): establish transport boundary for API client - #641
Merged
Abhijeet Prasad (AbhiPrasad) merged 1 commit intoAug 4, 2026
Merged
Conversation
Braintrust HTTP mechanics currently live inside logger.py, coupling transport to logging and leaving no isolated foundation for a resource-oriented API client. Establish this boundary first so retries, structured errors, and endpoint services can be centralized in follow-up work without mixing those behavior changes into the initial refactor.
Luca Forstner (lforst)
approved these changes
Aug 4, 2026
Abhijeet Prasad (AbhiPrasad)
deleted the
abhi-ref-639-prepare-api-client-transport
branch
August 4, 2026 16:39
Abhijeet Prasad (AbhiPrasad)
added a commit
that referenced
this pull request
Aug 4, 2026
builds on top of #641 Add operation-level retry policies, bounded status and transport retries, and structured API errors while leaving legacy HTTPConnection call sites unchanged. Include real-socket coverage for retry safety, Retry-After handling, deadlines, custom transports, and session lifecycle. Next, add BraintrustClient bootstrap, endpoint routing, and the resource service facade on top of this transport.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Braintrust HTTP mechanics currently live inside logger.py, coupling transport to logging and leaving no isolated foundation for a resource-oriented API client. Establish this boundary first so retries, structured errors, and endpoint services can be centralized in follow-up work without mixing those behavior changes into the initial refactor.