Gewild: Data bygewerk 27 Oktober 2026

Kategorieë

Internet1 356
Kommunikasie321
Klank en video898
Grafika en ontwerp539
Kantoor en produktiwiteit1 124
Ontwikkelaarsgereedskap3 134
KI-gereedskap529
Sekuriteit en privaatheid385
Stelselgereedskap3 114
Speletjies523
Onderwys en wetenskap239
Netwerk en IT284

hellogrok-cli 0.1.20 aflaai

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.

Dit is ’n ouer weergawe. Die nuutste weergawe is 0.1.41. hellogrok-cli 0.1.41 · Vrygestel:

Installeerlêers 0.1.20

ArgitektuurTipeBestekLêergrootteAflaaiSHA256
64-bis Draagbaar — — github.com VirusTotal
ARM64 Draagbaar — — github.com VirusTotal

Die skakel en SHA256 kom uit die gemeenskapsmanifes van die Windows-pakketbestuurder. Vergelyk die hashwaarde van die afgelaaide lêer voordat u dit laat loop.

Vrystellingsnotas

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

Gewildste in VPN en instaanbediener

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

Meer van hellowind777

Sien alles
  • hellogrokVPN en instaanbediener · hellowind777

Etikette

Deel