At startup "the broker is not reachable yet" is the normal case — a container comes up in seconds, the overlay tunnel a moment later. Exiting delegated the retry to the container runtime, which read as a crash-loop to every restart-counting health check and every person watching. Serve mode now retries with capped backoff, aloud, indefinitely; a pinned-certificate mismatch still refuses at once, and one-shot commands (emit, invoke, run) still fail fast.
Proven by the built-store-cross-node bed, which asserts the joined consumer's container-runtime restart count is zero. Resolves hq issue 058.
At startup "the broker is not reachable yet" is the normal case — a container comes up in seconds, the overlay tunnel a moment later. Exiting delegated the retry to the container runtime, which read as a crash-loop to every restart-counting health check and every person watching. Serve mode now retries with capped backoff, aloud, indefinitely; a pinned-certificate mismatch still refuses at once, and one-shot commands (emit, invoke, run) still fail fast.
Proven by the built-store-cross-node bed, which asserts the joined consumer's container-runtime restart count is zero. Resolves hq issue 058.
At startup 'the broker is not reachable yet' is the normal case — a
container comes up in seconds, the overlay tunnel a moment later.
Exiting delegated the retry to the container runtime, which read as a
crash-loop to every restart-counting health check and every person
watching docker ps. Serve mode now retries with capped backoff, aloud,
indefinitely; a pinned-certificate mismatch still refuses at once, and
one-shot commands (emit, invoke, run) still fail fast.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
At startup "the broker is not reachable yet" is the normal case — a container comes up in seconds, the overlay tunnel a moment later. Exiting delegated the retry to the container runtime, which read as a crash-loop to every restart-counting health check and every person watching. Serve mode now retries with capped backoff, aloud, indefinitely; a pinned-certificate mismatch still refuses at once, and one-shot commands (emit, invoke, run) still fail fast.
Proven by the built-store-cross-node bed, which asserts the joined consumer's container-runtime restart count is zero. Resolves hq issue 058.