Two issues fixed:
1. Alipay.SupportedTypes() returned ["alipay_direct"] and Wxpay returned
["wxpay_direct"], but the frontend sends payment_type="alipay"/"wxpay".
The registry lookup failed with "payment method (alipay) is not
configured". Fix: return the base types ["alipay"]/["wxpay"].
2. When multiple providers support the same payment type (e.g. EasyPay
and Alipay direct both handle "alipay"), only the last-registered
provider's instances were reachable — the registry mapped one type to
one provider key, and SelectInstance queried by that single key.
Fix: bypass the registry in invokeProvider and let SelectInstance
query across all providers when providerKey is empty. The selected
instance's own ProviderKey (now included in InstanceSelection) is
used to create the correct provider, enabling true cross-provider
load balancing.
Closes#1592
When an Anthropic API key's credit balance is depleted, the upstream
returns HTTP 400 with message containing "credit balance". Previously,
the 400 handler only checked for "organization has been disabled",
so credit-exhausted accounts kept being scheduled — every request
returned the same error.
Treat this case identically to 402 (Payment Required): call
handleAuthError → SetError to stop scheduling the account until
an admin manually recovers it after topping up credits.
Closes#1586
- Add docs/PAYMENT.md and docs/PAYMENT_CN.md with full payment setup guide
- Mark Sub2ApiPay as deprecated in ecosystem tables (payment is now built-in)
- Add built-in payment system to features list in all 3 READMEs
The test request was using maxOutputTokens: 1, which caused Google API to
generate only 1 token. When decoded, this single token produced "It" as the
response, making it look like an error.
Changed:
- Content: "." → "Test connection" (more meaningful prompt)
- MaxTokens: 1 → 10 (enough tokens to verify connection is working)
This fixes the issue where account test always showed "It" in the response,
which was actually just the truncated output from the single-token generation.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Upstream removed sora feature (090_drop_sora.sql) but left i18n keys
and wire.go references. Clean up:
- Remove entire sora i18n block from en.ts and zh.ts (~190 lines)
- Remove sora nav key and unused 'data' settings tab key
- Remove sora_client_enabled from settings (fork-specific)
- Remove SoraMediaCleanupService from wire.go
The API client's error interceptor was dropping the reason and metadata
fields from backend error responses. This caused PaymentView to miss
specific error codes (TOO_MANY_PENDING, CANCEL_RATE_LIMITED) and fall
back to generic error messages.
Stripe payment path was setting expiresAt to empty string, causing
PaymentStatusPanel to fall back to hardcoded 30-minute default when
the popup redirect switches to the waiting view.
The built-in payment system replaces the old external purchase subscription
iframe approach. Remove purchase_subscription_enabled/url from admin settings
interface and form defaults, as the Payment tab now handles this functionality.
Kept in stores/app.ts fallback to match backend DTO response structure.
Add a full payment and subscription system supporting EasyPay (Alipay/WeChat),
Stripe, and direct Alipay/WeChat Pay providers with multi-instance load balancing.
**Bug Fix**: TLS fingerprint routing was disabled by default
- isTLSFingerprintRoutingEnabled() was checking NodeTLSProxy.Enabled (default: false)
- Should check TLSFingerprint.Enabled (default: true)
- This caused all Antigravity requests to lack proper TLS fingerprinting
**Changes**:
- Use correct config flag: s.cfg.Gateway.TLSFingerprint.Enabled
- Add cloudcode-pa.googleapis.com and daily sandbox variant to default routing list
- Requests now properly emulate Claude CLI (Node.js 24.x) TLS fingerprint
**Impact**:
- Antigravity API requests now use JA3/JA4 fingerprinting to avoid 503 monitoring blocks
- Proper TLS handshake matching real Claude IDE behavior
- Fixes 'context deadline exceeded' and intermittent 503 errors
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Reduce max retry attempts from 60 to 10 (exponential backoff prevents pile-up)
- Replace fixed 1s delays with exponential backoff: 1s, 2s, 4s, 8s, 16s, 32s
- Add ±10% jitter to prevent thundering herd effect
- Cap max wait at 32 seconds to avoid excessive delays
- Improves response time when API is temporarily unavailable
Before: ~60s worst case (60 * 1s fixed delays)
After: ~10s worst case (exponential backoff with cap)
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Downgrade Go from 1.26.2 to 1.25 (stable, avoids compiler crash on Alpine)
- Reorganize protobuf generated files into language_server_pb/ subdirectory
- Update go.mod and go.sum to match new Go version
- Docker build now completes successfully and pushes to registry
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
