ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When using AbortSignal.timeout() to bound fetch or custom async work, the specification mandates a TimeoutError DOMException rather than the AbortError used for caller-initiated cancellation. This distinction is intentional, yet many retry policies treat any abort-derived rejection as non-retryable, causing timeouts to be classified as permanent failures ins
Goal: enforce a server-side deadline for long-running Remix loaders while responding correctly when a client aborts a navigation fetch. Remix passes the incoming Request to server loaders, and request.signal is an AbortSignal that flips to aborted when the browser cancels the request. Remix has no built-in declarative loader timeout, so a deadline must be ad
Goal: verify whether Opera’s Fetch API retains the AbortSignal.reason value in the resulting error object when a request is terminated by a timeout‑initiated abort compared with an explicit controller.abort() call. Constraints: the behavior may differ between Opera Desktop and Opera Android builds due to differing Chromium upstream versions, and network‑modi
Three.js provides LoadingManager to coordinate loader progress, but individual loaders such as TextureLoader and GLTFLoader expose only onLoad, onProgress, and onError callbacks without a built‑in timeout or abort mechanism. Applications that need to cancel a long‑running load must currently discard the result and manually clean up any partially created reso
Ghost’s HTTP server treats each request as cancelable when the underlying socket emits a 'close' or 'end' event, allowing middleware to abort processing early. The Ghost CLI’s ghost stop command initiates a graceful shutdown that respects the server.shutdownTimeout setting (default 5000 ms) introduced in Ghost 5.0. However, the Admin API does not yet honor t
Goal Determine whether a NestJS HTTP server route protected by TimeoutInterceptor can automatically cancel an outbound HttpService request when the server-side timeout fires. Constraints and uncertainty TimeoutInterceptor aborts the inbound response using Node’s AbortController , but it does not automatically attach that signal to outbound clients. HttpServi
Goal: ensure that aborting a GLTFLoader request also updates LoadingManager progress and cleans up any associated callbacks. Constraints: LoadingManager does not provide a built‑in abort mechanism; developers must manually attach an AbortSignal to each loader and manage progress events to avoid orphaned callbacks or memory leaks. Questions: Should LoadingMan
Context Since Puppeteer 20.0.0, page.goto , page.waitForNavigation , page.waitForSelector , and page.waitForXPath accept an AbortSignal as the first argument, so in-flight work can be cancelled with an AbortController . This is a change from 19.x, where cancellation required racing promises manually. The discrepancy When a timeout (for example via page.setDe
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
remix
opera
threejs
ghost
nestjs