ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Context Postman applies a global request-timeout default that can be overridden per request. Both the user-initiated Cancel button and a timeout expiration surface as error states in the Tests tab rather than as normal responses. Scripts can detect the absence of a response code and inspect error messaging, but the exact error shape is not part of a stable c
Determine whether Envoy interprets an incoming HTTP/2 CANCEL frame as a request deadline expiration that should be forwarded to the upstream via the x‑envoy‑upstream‑rq‑timeout header and result in a graceful connection shutdown aligned with the route’s idle timeout and the current xDS lease. Observations suggest that Envoy v1.22 handles CANCEL frames on a b
AskTimeoutException behavior When using akka.pattern.ask with a Timeout , the framework throws an AskTimeoutException if the target actor fails to send a reply before the deadline. This exception is the primary signal for timeout handling in Akka applications. Cancellation after actor termination Actors may schedule work via a Cancellable . The cancel() meth
I am designing timeout and cancellation handling for a GraphQL HTTP API and need to pin down one behavior before committing to an architecture. When a timeout middleware such as Apollo Server's timeout plugin fires, the client receives a generic Internal Server Error with a message like Request timeout exceeded , but it is unclear what happens to resolver ex
When building interactive applications that call the Stack Overflow API, developers need a reliable way to abort long‑running requests—for example, when a user navigates away or cancels a search. The API documentation mentions rate‑limit headers and standard HTTP status codes, but it does not specify whether clients can signal cancellation through a dedicate
When using Akka’s ask pattern, a Future is returned that completes with a Failure if the actor does not reply within the specified timeout. However, if the actor sends a reply after the timeout has elapsed, the Future is already failed and the reply is not observed by the caller. The documentation notes that such late replies are “dropped,” but it does not e
The RSpec timeout feature introduced in version 3.8 allows a global limit to be set for each example, causing a Timeout::Error when exceeded. Currently this limit does not automatically apply to child example groups; each group or example must declare its own timeout metadata to obtain a different limit. This lack of inheritance can lead to inconsistent time
Goal: Identify a reliable way to detect when a Ruby connection pool is approaching exhaustion before threads experience timeout‑induced latency spikes. Constraints: The connection_pool gem only raises a Timeout::Error after the per‑checkout timeout expires and does not emit warnings or metrics; developers must either poll pool.available_size or rescue except
Goal We want to bound a query and paginate a dataset that exceeds Axios’s default limits. Constraints Axios 1.5.0 sets timeout to 0, maxRedirects to 5, and changes validateStatus behavior. The transformResponse array now runs in order, allowing header extraction. Streaming responses require manual piping. Unresolved Questions Should we explicitly set maxRedi
stackoverflow
rspec
ruby
axios