MaarkssDN/Birthub-360 / .agents/skills/async-ordering-tests
async-ordering-tests
VerifiedTest async ordering - event-loop / queue / channel ordering assertions, JS Promise microtask vs macrotask ordering, Python `asyncio.gather` vs `asyncio.wait_for` semantics, Go goroutine + channel happens-before relationships, async/await re-entrancy. Use deterministic schedulers (sinon fake timers, asyncio test mode) to remove run-to-run variance. Use when a callback fires twice, a later response overwrites an earlier one, or a cancelled parent task leaves a child still running - bugs where completion order, not shared memory, is the defect.
| File | Kind | Size |
|---|---|---|
| .tessl-plugin/plugin.json | config | 684 B |
| SKILL.md | skill md | 7.7 KB |
| evals/cancellation-propagation/criteria.json | config | 3.1 KB |
| evals/cancellation-propagation/task.md | markdown | 2.6 KB |
| evals/microtask-before-macrotask/criteria.json | config | 3.2 KB |
| evals/microtask-before-macrotask/task.md | markdown | 2.3 KB |
| evals/stale-response-overwrite/criteria.json | config | 3.1 KB |
| evals/stale-response-overwrite/task.md | markdown | 2.1 KB |
evals/cancellation-propagation/task.md
View on GitHub# Cancelling an upload leaves chunks in flight
## Problem Description
`src/upload.js` uploads a file as a sequence of chunks and accepts an
`AbortSignal` so the user can cancel. Support has seen cancelled uploads
continue to consume bandwidth, which suggests the signal is not reaching the
per-chunk work, or that further chunks start after the cancel.
The existing test aborts before the upload begins. That is the easy case and
it tells us nothing about a cancel that arrives while a chunk is in flight.
## Output Specification
Add `src/upload.test.js` covering cancellation that arrives mid-upload:
that the in-flight chunk is told to stop, that no further chunk is started,
that the caller sees an abort rather than a normal completion, and that
cleanup runs.
Run `npm test` before you finish; it must pass.
Leave `src/upload.basic.test.js` in place.
## Input Files
Extract the following files before beginning.
=============== FILE: package.json ===============
{
"name": "uploader",
"version": "2.0.4",
"private": true,
"scripts": {
"test": "node --test"
}
}
=============== FILE: src/upload.js ===============
'use strict';
class AbortError extends Error {
constructor() {
super('The operation was aborted');
this.name = 'AbortError';
}
}
async function uploadAll(chunks, { signal, uploadChunk, onCleanup }) {
const receipts = [];
try {
for (const chunk of chunks) {
if (signal.aborted) {
throw new AbortError();
}
const receipt = await uploadChunk(chunk, signal);
if (signal.aborted) {
throw new AbortError();
}
receipts.push(receipt);
}
return receipts;
} finally {
if (onCleanup) {
onCleanup({ uploaded: receipts.length, aborted: signal.aborted });
}
}
}
module.exports = { uploadAll, AbortError };
=============== FILE: src/upload.basic.test.js ===============
'use strict';
const test = require('node:test');
const assert = require('node:assert/strict');
const { uploadAll } = require('./upload');
test('uploads every chunk when not cancelled', async () => {
const started = [];
const receipts = await uploadAll(['a', 'b'], {
signal: new AbortController().signal,
uploadChunk: async (chunk) => {
started.push(chunk);
return `receipt-${chunk}`;
},
});
assert.deepEqual(started, ['a', 'b']);
assert.deepEqual(receipts, ['receipt-a', 'receipt-b']);
});
test('rejects when aborted before it starts', async () => {
const controller = new AbortController();
controller.abort();
await assert.rejects(
() => uploadAll(['a'], { signal: controller.signal, uploadChunk: async () => 'x' }),
{ name: 'AbortError' },
);
});
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |