Upgrade conformance tests to v1.0.3

[srikrsna-buf]

v1.0.3 of the conformance runner adds cases to cover trailers only responses. The changes to the conformance clients follows the changes done to the reference client.

This also changes the conformance tests for callback clients to handle cancellation tests. For unary we rely on global error handler to fail the process and streaming we rely on no of responses as a check.

fetch on node is not throwing an error on the response reader, instead it silently ends the stream. This resulted in a different error code for cancellation errors. nodejs/undici#1940

[timostamm]

fetch on node is not throwing an error on the response reader, instead it silently ends the stream.

When a signal passed to fetch is aborted? It would be good to know whether this is expected behavior by the spec, and whether it's a known issue, and is already fixed in one of the more recent Node versions. Can you find out and add a comment in the source?

[srikrsna-buf]

@timostamm I couldn't find any issue related to this but was able to pinpoint the timing:

async function run() {
    const controller = new AbortController();
    const res = await fetch("https://example.com/", { signal: controller.signal });
    controller.abort();
    const reader = res.body?.getReader();
    console.log(await reader?.read())
}

run();

This prints { value: undefined, done: true }. If the abort is called after getReader then read throws an error.

Running the same code on chrome throws an AbortError.

[srikrsna-buf]

Sorry, found it: nodejs/undici#1940

[timostamm]

Nice, but can you split up the changes into separate PRs? At least the fix for gRPC trailers-only responses needs to be in a separate PR so that changes and fixes are understandable from reading the changelog of a release.

[timostamm]

I agree with this. It's more precise than a known-failing list.

[timostamm]

LGTM!