Repository navigation
Conversation
Adds a fork section, marked with `<!-- fork:start -->` / `<!-- fork:end -->`, at the top of `CONTRIBUTING.md`. Upstream's guide below it is unchanged (diff: 14 insertions, 0 deletions), which keeps upstream syncs conflict-free here. The section says: - this is a fork of pingdotgg/t3code, used to develop the CLIProxyAPI usage-hub integration and send it upstream (e.g. pingdotgg#27901) - changes that aren't fork-specific belong upstream - PRs here target `main`, and the maintainer picks the merge method - upstream syncs must be merged with a merge commit, never squashed or rebased The description comes from the README and the fork-only branches (`fix/hub-routes-clients`, `feat/hub-account-names`, `fix/limit-recovery-on-usage`). The fork's `main` itself has no fork-only commits: it is 3593 commits behind upstream `main`. Verified: docs-only. I didn't run `vp run check:changed` (no install in this clone). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Closing: Cujuju already has 3 or more open PRs here, which is the limit for contributors who are not vouched. Once one of them is merged or closed, open this again. See the open PR limit. |
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
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.
A stalled OTLP collector could make
t3 serveaccumulate overlapping trace exports. The Effect exporter launched another request whenever a batch filled, even while earlier requests were still waiting. The encoded bodies and HTTP client copies stayed live, and serializing each batch added CPU load during the outage.The server now allows one trace export in flight, gives each flush a 10-second deadline, and keeps up to 1,000 pending spans. Overflow is counted in a warning. The local NDJSON sink still receives the spans.
Evidence
On Windows, I ran the affected nightly source with an isolated SQLite backup and sent the same 6,000 read requests to each version while a loopback collector withheld its response. All 6,000 completed in both runs.
CPU profiles showed OTLP encoding and Undici buffer copies during the backlog. The live service logged OTLP trace connection timeouts. The isolated runs establish the exporter failure mode. The cause of the remaining gap to the historical multi-gigabyte JS heap is unverified.
The 11.45 GiB SQLite backup held 4.22 GiB of free pages, and turn-item projections occupied 3.86 GiB. Offline vacuum reduced a copy to 6.97 GiB, passed SQLite's quick check, and preserved the counted projection and event rows. T3 already has offline compaction and event pruning.
Two regression cases fail with the stock exporter and pass with this change. The tests cover congestion, timeout and recovery, and shutdown flush.
vp run check:changedpassed.gpt-6.2-sol via Codex.