ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Symptom When a Teleport client cancels an SSH connection request—either by exceeding a context deadline or by explicit cancellation—the SSH session on the server may remain active until the server‑side idle timeout expires. Goal Determine whether Teleport provides a mechanism to terminate an established SSH session immediately when the client‑side request co
The goal is to characterize the runtime behavior of Electron's ipcRenderer.invoke when the corresponding ipcMain.handle never transmits a reply. This scenario arises in long-running or faulted main-process handlers where no explicit resolution occurs. Understanding whether the promise remains pending, rejects after an implicit timeout, or causes renderer res
Handlebars synchronous rendering limitation The goal is to allow a host application to cancel or time‑out a Handlebars template render without producing incomplete or corrupted output. Handlebars compiles and executes templates synchronously; helpers must return a value immediately. If a helper returns a Promise, the rendered output contains the literal stri
Context Symfony HttpClient executes upstream calls with its own timeout configuration ( timeout , max_duration , stream timeout) that operates independently of the enclosing HTTP request lifecycle. When a client disconnects early—closing the browser tab, cancelling a fetch, or hitting a reverse-proxy timeout—the inbound Symfony request terminates, but the ou
Goal Verify the blocking duration and timeout semantics when a second Liquibase update command runs while a first holds the DATABASECHANGELOGLOCK in Liquibase 4.27. Constraints The lock is a single row with LOCKED=1 and LOCKGRANTED timestamp. A second CLI or Spring Boot process against the same schema must block or fail. The lock scope follows the configured
Developers using Turbo Drive often need to limit how long a page visit can wait for a server response, especially when dealing with unreliable backends or long‑running endpoints. The current implementation relies on the Fetch API and provides no default timeout; a visit proceeds until the network layer signals failure or the server replies. To impose a limit
Problem On Sulu 2.5 (Symfony 6.x), a full rebuild of the search index via bin/websiteconsole sulu:search:index (or the admin reindex action) is terminated partway through large content trees. The process appears to be stopped by PHP's max_execution_time rather than by any Sulu-level timeout, and no partial-progress or cancellation message is surfaced in the
I'm designing a networking layer in Swift using Combine (iOS 15+) where requests are wrapped with .timeout(_:scheduler:) so subscribers receive an error if no value arrives in time. My goal is to guarantee that when a timeout fires, the underlying work — for example a URLSession.DataTaskPublisher request — stops consuming resources rather than continuing in
Goal: Enable automatic expiration of idle Reflex component state stored in server‑side sessions to bound memory usage during long‑lived WebSocket connections. Constraint: Reflex does not expose a built‑in configuration option for state timeout; implementing expiration requires custom session‑store middleware, which may interfere with the framework’s internal
ssh
electron
handlebars
symfony
turbo
php
apple
reflex