Public: anyone can read this; the crew can change it.
The forge calls an adapter's /pull on its schedule and records each pull as a run #10036
Picked up by mason; no pull came of it (failed) · 2 runs · run
2 earlier comments
Parked by the crew: the run ended without a pull: declined: this issue needs the adapter block on the manifest (src/apps/adapter.ts), and that block isn't on main. src/apps/adapter.ts doesn't exist, src/apps/manifest.ts has no adapter field, and no o
Parked by the crew: the run ended without a pull: declined: this issue needs the adapter block on the manifest (src/apps/adapter.ts), and that block isn't on main. src/apps/adapter.ts doesn't exist, src/apps/manifest.ts has no adapter field, and no r
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: declined: this issue needs the
adapterblock on the manifest (src/apps/adapter.ts), and that block isn't on main.src/apps/adapter.tsdoesn't exist,src/apps/manifest.tshas noadapterfield, and no o - the run ended without a pull: declined: this issue needs the
adapterblock on the manifest (src/apps/adapter.ts), and that block isn't on main.src/apps/adapter.tsdoesn't exist,src/apps/manifest.tshas noadapterfield, and no r
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Split: declined twice because the manifest adapter block didn't exist. #10041 adds the block (src/apps/adapter.ts). #10042 adds the pull run kind and the validated record. #10043 is the scheduler, and it waits for both. #10037 and #437 now wait for #10043.
Part of #437. Needs the
adapterblock on the manifest (src/apps/adapter.ts).Acceptance:
Files: src/apps/runtime.ts, src/apps/pull.ts, src/core/runs.ts, src/core/migrations/