ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Develop a client that can gracefully handle cancellation and timeout scenarios when retrieving package metadata from the PyPI JSON API. Constraints and Uncertainty The API returns a 404 Not Found with a JSON body containing "Not found" for non‑existent packages, and a 429 Too many requests when the rate limit (~60 req/min) is exceeded. No timeout header
When applying a timeout to a ceylon.concurrent.Future using orElseAfter in Ceylon 1.3.3, the implementation cancels the underlying task with cancel(true) . The language tour notes that the actual stopping of the computation depends on the executor and may differ between the JVM and JavaScript backends, leaving the cancellation behavior unspecified. Developer
Neo4j manages transaction lifecycles through dbms.transaction.timeout configurations and driver-level settings. While the system is designed to terminate long-running operations, there is uncertainty regarding how the engine handles resource cleanup when a client abruptly closes a session versus a natural timeout expiration. When a client-side session is clo
The Slack Web API enforces a strict 3-second timeout for all HTTP requests. If the receiving server fails to respond within this window, Slack returns a 500-series error. This constraint presents a challenge for tasks that require complex processing or multiple external API calls before acknowledging the request. When using the Events API, Slack utilizes an
The goal is to allow a Liquibase update operation to be halted after a user‑defined duration, ensuring that any partially applied changeset can be rolled back or left in a known state. Currently Liquibase executes each changeset within a database transaction when supported, but it does not expose a timeout property for the whole update; users must rely on JD
I'm configuring an HTTP route retry policy in Envoy (assuming 1.27+ syntax) and want predictable behavior when an upstream service responds too slowly. My route sets a request timeout and a retry policy with num_retries and a retry_on list containing 5xx and gateway-error . The uncertainty: it's unclear whether an upstream request that exceeds the configured
I have several long-running async endpoints in a FastAPI application (assume FastAPI 0.1xx on Starlette, served by Uvicorn) and I want requests to stop doing work when either a client disconnects or a time budget is exceeded. My understanding is that FastAPI exposes no per-request timeout setting, so the behavior has to come from somewhere else. The pieces I
I am designing a Go service where each incoming HTTP request spawns a chain of calls: a database query, an outbound API request, and a cache write. I want a single deadline to govern the whole chain, but I also want individual stages to have their own stricter limits where needed. My current assumption is that I would derive a base context with context.WithT
Goal Determine precisely when a renpy.timeout is cancelled during a choice menu. The intended behavior is to allow the player to make a selection before the timeout triggers, but the documentation does not specify whether the timer is cleared on mouse hover, mouse down, or mouse up. Constraints & Uncertainty The interaction between renpy.timeout and auto
pypi
neo4j
slack
go
renpy