fetch: wpt tests that are failing

描述

import { fetch, setGlobalOrigin } from 'undici'
import assert from 'assert'

setGlobalOrigin('http://localhost:3000')

const controller = new AbortController();
const signal = controller.signal;
controller.abort();

const log = [];

await Promise.all([
	fetch('../resources/data.json', { signal }).then(
		() => assert_unreached("Fetch must not resolve"),
		() => log.push('fetch-reject')
	),
	Promise.resolve().then(() => log.push('next-microtask'))
]);

assert.deepStrictEqual(log, ['fetch-reject', 'next-microtask']);

貢獻者指南

技術棧

javascript

領域

backend

議題類型

bug

難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。

3

預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。

1-2 days

活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。

stale

清晰度議題是否清楚說明預期改動、驗收標準和下一步。

clear

前置要求

JavaScriptNode.jsfetch APIAbortController

新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。

45

研究方向

Examine the fetch implementation in lib/fetch/index.js, specifically the abort handling at lines 126 and 304. Understand the flow of signal.aborted checks and promise rejection timing. Consider the microtask queue order and whether the fetch function resolves before the next microtask. Look at the original issue #1664 (comment) for context. Write a fix that ensures fetch rejects synchronously (or in the current microtask) when signal is already aborted.