ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
torch.utils.data.DataLoader exposes a documented timeout argument that bounds how long the main process waits for a batch from worker processes when num_workers is greater than zero. Exceeding this limit raises a RuntimeError in the main process, but the timeout does not transmit a cancellation signal to the worker itself. The worker process and any in-fligh
I'm working with InfluxDB 2.x and trying to handle timeouts and cancellation consistently across the HTTP query API and write path. My goal is to reliably distinguish a server-side max-query-time termination from a client-side cancellation or a write timeout, but the error surfaces don't seem to line up. From what I can tell, a Flux query that exceeds the co
The goal is to guarantee that a test method that exceeds its @Timeout limit has its executing thread interrupted, preventing any lingering side‑effects such as resource leaks or inconsistent state. Currently, JUnit 5’s TimeoutExtension records a failure but does not call Thread.interrupt() on the test thread, leaving the thread to continue running after the
Goal Gracefully handle request cancellations and timeouts when calling commerce backends through Vue Storefront’s SDK/middleware layer. Constraints Vue Storefront routes all storefront calls through a server‑side middleware that wraps an HTTP client (commonly axios). The timeout and cancellation behavior is therefore defined by the client configuration and t
When building a utility that accepts an optional AbortSignal and internally combines it with AbortSignal.timeout(ms) using AbortSignal.any , the caller needs to know whether the resulting rejection came from a manual abort or from the timeout. TypeScript can type the signal parameter, but it cannot enforce that the implementation checks signal.aborted or for
When using Vala’s async methods with a GCancellable to implement a timeout, the cancellation check occurs only at yield points ( await statements). If the async method contains a long-running synchronous loop or computation, firing the timeout source will set the cancellable flag, but the method cannot be interrupted until it reaches the next yield point. Th
Cross-platform HTTP timeout and cancellation in libgdx I am evaluating libgdx’s HTTP abstraction for a cross-platform project targeting Desktop, Android, and HTML5. The goal is to enforce a request deadline and abort in-flight requests when the user navigates away, without leaving sockets or XHR handles pending. libgdx exposes HttpRequest.setTimeout and Http
Goal: Ensure that data fetching in Nuxt 3 handles both navigation‑initiated cancellation and request timeouts uniformly, especially during server‑side rendering where no client‑side AbortSignal is available. Currently, useFetch automatically forwards an AbortSignal when the navigating component is destroyed, but it does not apply a default timeout; during SS
When executing a Python script via Spyder’s Run command, the IDE can enforce an execution timeout (Preferences → General → Advanced) and also respond to user‑initiated cancellation such as pressing Ctrl+C in the IPython console or clicking the Stop toolbar button. The goal is to clarify whether these two mechanisms operate independently, whether one takes pr
pytorch
influxdb
junit
libgdx
spyder