fix Bitget Classic account reads - #1027
Merged
Merged
Conversation
Reported in #951; reimplemented on the maintainer-owned branch and credited in CONTRIBUTORS.md.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Summary
USDT-FUTURESparametersCONTRIBUTORS.mdand README for the diagnosis proposed in fix: read Bitget USDT-M and UTA account state #951Root cause
CCXT 4.5.38 defaults unscoped Bitget private reads to Spot. Those calls can succeed while omitting Classic USDT-M funds and several open-order namespaces, so the prior single-account model could report plausible but incomplete state.
Verification
pnpm exec vitest run services/uta/src/domain/trading/brokers/ccxt/CcxtBroker.spec.ts services/uta/src/domain/trading/brokers/ccxt/exchanges/bitget.spec.ts services/uta/src/domain/trading/brokers/ccxt/exchanges/bitget.ccxt.spec.ts services/uta/src/domain/trading/brokers/presets.spec.ts— 168 passednpx tsc --noEmitpnpm -F @traderalice/uta-broker-ccxt typecheckpnpm test— 4,046 passed, 9 skippedpnpm -F @traderalice/guardian-runtime build && pnpm test:e2e— 30 passed, 3 skippedpnpm broker-packs:build && pnpm broker-packs:verify— all five darwin-arm64 artifacts verifiedNo configured Bitget Classic/demo account was available in the local runtime, so private venue reads were not independently repeated. The deterministic suite exercises the real CCXT 4.5.38 routing implementation; #951's read-only Classic venue evidence remains external corroboration rather than this PR's local acceptance.
Boundary touch
Trading account reads and logical sub-account topology. Bitget Classic writes still use the existing CCXT endpoints, but multi-compartment UTA safety now requires an explicit
subAccountIdfor staged writes. This PR does not enable CCXToptions.utaor any Bitget v3 route.Non-goals