Populaarsed: Andmed uuendatud 31. oktoober 2026

Kategooriad

Internet1361
Suhtlus321
Heli ja video903
Graafika ja disain543
Kontor ja tootlikkus1120
Arendustööriistad3139
Tehisintellekt534
Turvalisus ja privaatsus388
Süsteemitööriistad3126
Mängud524
Haridus ja teadus239
Võrk ja IT283

hellogrok-cli 0.1.20 allalaadimine

Console-only CLI of hellogrok, a local proxy that makes Grok Build custom model channels work with common API formats, native Web tools, isolated authentication, and automatic configuration recovery.

See on vanem versioon. Uusim versioon on 0.1.41. hellogrok-cli 0.1.41 · Avaldatud:

Paigaldusfailid 0.1.20

ArhitektuurTüüpUlatusFaili suurusAllalaadimineSHA256
64-bitine Portatiivne — — github.com VirusTotal
ARM64 Portatiivne — — github.com VirusTotal

Link ja SHA256 pärinevad Windowsi paketihalduri (winget) kogukonna manifestist. Võrdle allalaaditud faili räsi enne selle käivitamist.

Muudatuste loend

Added
- Per-channel absorb layer for transient upstream soft failures. While the upstream response headers have not been sent, retryable failures (busy/overloaded 503, 429, retryable 5xx, response-header timeouts) are retried inside the proxy with exponential backoff (2s–30s, honoring an upstream Retry-After up to 60s) for up to 90 seconds by default (absorb_retry_max_secs, absorb_retry_backoff_cap_secs). Grok Build's native 15-attempt retry budget stays untouched during the window; only when the window is exhausted does the failure pass through, still retryable. Transport errors are not absorbed so Grok Build's first-retry HTTP/1.1 client rebuild keeps working. UP absorb log lines record each wait.
- Synthesized 30-second Retry-After on retryable busy/overloaded 5xx passthroughs that carried none, pacing Grok Build's own retries. Upstream Retry-After headers are preserved.
- Opt-in dead-channel breaker (dead_channel_fail_fast, default off; dead_channel_fail_threshold, default 6). Only dial-level failures (connection refused, DNS, TLS handshake) count, because those can never succeed on retry; after the streak the proxy answers a non-retryable 503 proxy_circuit_open with X-Should-Retry: false, with one probe allowed after a 5-minute cooldown and any upstream response closing the breaker.
Changed
- The circuit breaker no longer fast-fails soft failures. Busy 503, 429, timeouts, transport resets, and error-body read failures pass through as retryable (or are absorbed first), so Grok Build keeps its complete native retry budget. X-Should-Retry: false is reserved for deterministic failures whose retries cannot succeed (authentication, permission, billing, quota, invalid request/model).

https://github.com/hellowind777/hellogrok/blob/HEAD/CHANGELOG.md#0120-2026-08-30

Populaarseim: VPN ja puhverserver

Vaata kõiki
  1. OpenVPNVPN ja puhverserver · OpenVPN, Inc.
  2. nginxVPN ja puhverserver · nginx
  3. Proton VPNVPN ja puhverserver · Proton AG
  4. TailscaleVPN ja puhverserver · Tailscale Inc.
  5. NetbirdVPN ja puhverserver · NetBird GmbH
  6. v2rayNVPN ja puhverserver · 2dust
  7. v2ray-coreVPN ja puhverserver · v2fly
  8. Zed Attack ProxyVPN ja puhverserver · ZAP
  9. WindscribeVPN ja puhverserver · Windscribe Limited
  10. sing-boxVPN ja puhverserver · SagerNet

Veel väljaandjalt hellowind777

Vaata kõiki
  • hellogrokVPN ja puhverserver · hellowind777

Sildid

Jaga