lab: install each checkout where its lock file is, check out mesh-tools-go, and have lab_check catch both (issue 624) #268

Merged
mesh-admin merged 1 commits from fix/624-lab-run-installs-what-each-checkout-has into main 2026-10-13 11:11:58 +00:00
Contributor

Issue 624 (the lab module's lab_run fails at setup: npm ci in a checkout without a package-lock.json).

Cause: run.sh ran npm ci at the root of mesh-sdk, mesh-tools and mesh-lab. mesh-tools keeps its package in node-tools/ and has no lock file at its root, so every run failed with EUSAGE in 9 s (run-2026-10-13T09-49-42-305Z on shanks).

Fix (modules/lab):

  • installPlan / installStep install where a package-lock.json is: the root, or each directory one level down. They build there with npm run build --if-present for the SDK and the base, and the lab is only installed. A package.json with no lock file fails the run, naming it. A checkout with nothing installable fails the run.
  • REPOSITORIES gains mesh-tools-go, which genesis builds at its base step since issue 616 from the repository beside mesh-tools. The run exports MESH_LAB_REPOS (its checkouts, side by side), which the genesis-keeps-its-bus bed serves from its forge.
  • lab_check also runs setupProblems. Every repository a run clones must answer a main branch on the forge, and the npm ones are shallow-cloned and held to the same install rule. A run's setup failure is found by the check, before a run.

Tests (modules/lab/test/runs.test.ts, new test script; they fail on main, where none of this exists): the install plan for a root lock, a node-tools lock and an unlocked package.json. The generated shell is run against a fake npm for those layouts: where it installs and builds, and that it fails loud with nothing installed. The script clones mesh-tools-go and exports MESH_LAB_REPOS. 7 pass. runs.ts and the test type-check with strict tsc. index.ts type-checks against a stub of the SDK's tools types. merge-check.sh with MESH_CHECK_MODULES=lab passes its Go parts here; the TypeScript part runs in the TypeScript toolchain on the build seat.

Fixes issue 624.

Issue 624 (the lab module's lab_run fails at setup: `npm ci` in a checkout without a package-lock.json). **Cause**: run.sh ran `npm ci` at the root of mesh-sdk, mesh-tools and mesh-lab. mesh-tools keeps its package in `node-tools/` and has no lock file at its root, so every run failed with EUSAGE in 9 s (run-2026-10-13T09-49-42-305Z on shanks). **Fix** (modules/lab): - `installPlan` / `installStep` install where a package-lock.json is: the root, or each directory one level down. They build there with `npm run build --if-present` for the SDK and the base, and the lab is only installed. A package.json with no lock file fails the run, naming it. A checkout with nothing installable fails the run. - `REPOSITORIES` gains `mesh-tools-go`, which genesis builds at its base step since issue 616 from the repository beside mesh-tools. The run exports `MESH_LAB_REPOS` (its checkouts, side by side), which the genesis-keeps-its-bus bed serves from its forge. - `lab_check` also runs `setupProblems`. Every repository a run clones must answer a main branch on the forge, and the npm ones are shallow-cloned and held to the same install rule. A run's setup failure is found by the check, before a run. **Tests** (`modules/lab/test/runs.test.ts`, new `test` script; they fail on main, where none of this exists): the install plan for a root lock, a node-tools lock and an unlocked package.json. The generated shell is run against a fake npm for those layouts: where it installs and builds, and that it fails loud with nothing installed. The script clones mesh-tools-go and exports MESH_LAB_REPOS. 7 pass. runs.ts and the test type-check with strict tsc. index.ts type-checks against a stub of the SDK's tools types. merge-check.sh with MESH_CHECK_MODULES=lab passes its Go parts here; the TypeScript part runs in the TypeScript toolchain on the build seat. Fixes issue 624.
mesh-admin added 1 commit 2026-10-13 09:55:12 +00:00
Install each lab checkout where its lock file is, check out mesh-tools-go, and have lab_check catch both (hq issue 624)
mesh/merge-gate head c6a9c52dc7f2 merged into trunk 45d01e77c26d — pass: builds lab → shanks; no bus step; every machine composes with the change as it did…
mesh/repo-check head c6a9c52dc7f2 merged into trunk 45d01e77c26d — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
mesh/delivery delivered
c6a9c52dc7
lab_run ran npm ci at the root of mesh-sdk, mesh-tools and mesh-lab; mesh-tools keeps its package in
node-tools/ with no lock file at its root, so every run failed at its setup in nine seconds. A run now
installs (and, for the SDK and the base, builds) where a package-lock.json is: the root, or each
directory one level down; a package.json with no lock file fails the run naming it. It checks out
mesh-tools-go, which genesis builds since issue 616, and tells the beds where its checkouts are
(MESH_LAB_REPOS). lab_check asks the forge for every repository a run clones and applies the same install
rule to the ones it installs, so a run's setup failure is found before a run.
Author
Contributor

Delivery novox/mesh-catalog@c6a9c52dc7f2 — delivered since 2026-10-13T11:14:05Z

Delivery plan — builds lab → shanks; no bus step

  • tier 0: lab
  • shanks: receives lab
  • lab keeps data (ADR 0233): what it holds is backed up before it moves
  • grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before lab is judged on its first machine

Machines

  • lab on shanks: passed — healthy 1 times over 53s
  • lab on the rest running it: sent

Transitions

  • 2026-10-13 09:55 (new) → proposed (announced): novox/mesh-catalog#268's head announced
  • 2026-10-13 10:02 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-13 10:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-13 11:12 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-13 11:12 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
  • 2026-10-13 11:14 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@c6a9c52dc7f2` — **delivered** since 2026-10-13T11:14:05Z **Delivery plan** — builds lab → shanks; no bus step - tier 0: lab - shanks: receives lab - lab keeps data (ADR 0233): what it holds is backed up before it moves - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before lab is judged on its first machine **Machines** - lab on shanks: passed — healthy 1 times over 53s - lab on the rest running it: sent **Transitions** - 2026-10-13 09:55 (new) → proposed (announced): novox/mesh-catalog#268's head announced - 2026-10-13 10:02 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-13 10:02 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-13 11:12 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-13 11:12 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-13 11:14 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Author
Contributor

Merge check at c6a9c52d
Judged: head c6a9c52dc7f2 merged into trunk 45d01e77c26d; read beside it: mesh-controller 584aa2d7d7a5, mesh-controller-main 584aa2d7d7a5, mesh-host 7a41e120635b, mesh-tools 954e1a53eef9

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (run 2) (modules: lab)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) (run 2)

Delivery plan — builds lab → shanks; no bus step

  • tier 0: lab
  • shanks: receives lab
  • lab keeps data (ADR 0233): what it holds is backed up before it moves
  • grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before lab is judged on its first machine

Run by the build seat on shanks as build-1791885339231142959 (builds --log build-1791885339231142959).

restarted: handed out 2 times; an earlier hand-out did not finish here, so this run started from the beginning

--- the gate: lab
lab: ok, keeps work (cache); WARNING: runtime-env ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-13T09:54:29Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-13T09:54:29Z

modules the change moves:
  - lab (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): lab
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.003s
words: 12 retired words and 70 daemons' lines, none in the 46255 strings of 714 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.012s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.012s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 66, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.216s
modules/lab is TypeScript: merge-check-typescript.sh type-checks and tests it
--- its merge-check-typescript.sh (typescript toolchain)
type-checking modules/lab (TypeScript)
testing modules/lab (TypeScript)
✔ a checkout with a lock file at its root is installed there (2.35394ms)
✔ a checkout whose package lives one directory down is installed there, as mesh-tools' node-tools (0.847691ms)
✔ a package.json with no lock file is named, never installed (0.514817ms)
✔ a run installs and builds mesh-tools in node-tools, where its lock file is (17.91819ms)
✔ a run installs a checkout with its lock file at the root there, and builds only when asked (4.475188ms)
✔ a run fails at its setup, naming the checkout, when nothing of it can be installed (12.366798ms)
✔ a run checks out mesh-tools-go and says where its checkouts are (0.697679ms)
ℹ tests 7
ℹ suites 0
ℹ pass 7
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 131.660055
**Merge check** at `c6a9c52d` Judged: head `c6a9c52dc7f2` merged into trunk `45d01e77c26d`; read beside it: mesh-controller `584aa2d7d7a5`, mesh-controller-main `584aa2d7d7a5`, mesh-host `7a41e120635b`, mesh-tools `954e1a53eef9` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (run 2) (modules: lab) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) (run 2) **Delivery plan** — builds lab → shanks; no bus step - tier 0: lab - shanks: receives lab - lab keeps data (ADR 0233): what it holds is backed up before it moves - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before lab is judged on its first machine Run by the build seat on shanks as `build-1791885339231142959` (`builds --log build-1791885339231142959`). ``` restarted: handed out 2 times; an earlier hand-out did not finish here, so this run started from the beginning --- the gate: lab lab: ok, keeps work (cache); WARNING: runtime-env ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339) long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 1 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-13T09:54:29Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-13T09:54:29Z modules the change moves: - lab (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): lab --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.003s words: 12 retired words and 70 daemons' lines, none in the 46255 strings of 714 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/secrets 0.012s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 66, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.216s modules/lab is TypeScript: merge-check-typescript.sh type-checks and tests it --- its merge-check-typescript.sh (typescript toolchain) type-checking modules/lab (TypeScript) testing modules/lab (TypeScript) ✔ a checkout with a lock file at its root is installed there (2.35394ms) ✔ a checkout whose package lives one directory down is installed there, as mesh-tools' node-tools (0.847691ms) ✔ a package.json with no lock file is named, never installed (0.514817ms) ✔ a run installs and builds mesh-tools in node-tools, where its lock file is (17.91819ms) ✔ a run installs a checkout with its lock file at the root there, and builds only when asked (4.475188ms) ✔ a run fails at its setup, naming the checkout, when nothing of it can be installed (12.366798ms) ✔ a run checks out mesh-tools-go and says where its checkouts are (0.697679ms) ℹ tests 7 ℹ suites 0 ℹ pass 7 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 131.660055 ```
mesh-admin left a comment
Author
Contributor

Verdict: approve at c6a9c52dc7

The install rule is right for every repository a run clones. On main: mesh-lab and mesh-sdk each hold package.json and package-lock.json at their root, so installPlan returns {install:[root], unlocked:[]} for both and the root alone is installed and built. mesh-tools has no package.json at its root at all and keeps its package in node-tools/, which holds both package.json and package-lock.json; installPlan correctly finds nothing at the root, then finds the lock one level down and returns {install:[node-tools], unlocked:[]} — this is exactly the checkout that broke lab_run before this fix. mesh-controller, mesh-host and mesh-catalog have no package.json anywhere in their tree (verified against their main branches), and mesh-tools-go (private; its forge tree is only Dockerfile, README.md and module.json, no package.json) is also package-free. All four are correctly left out of NPM_REPOSITORIES, so installStep is never invoked on them — they pass through a run's build step untouched, with no install attempted and nothing to fail on. That answers check 2: a Go repository with no package.json passes a run cleanly because it is never asked to install, not because an empty install silently "succeeds".

The 7 tests in modules/lab/test/runs.test.ts fail on main and pass at the head. I copied the new test file onto a worktree of main (45d01e77c2): it fails to even load, with 'SyntaxError: The requested module "../tools/runs.ts" does not provide an export named "NPM_REPOSITORIES"' (0 of 7 run), which matches main's runs.ts hard-coding npm ci at the root of mesh-sdk, mesh-tools and mesh-lab — the exact bug issue 624 reports. At the head, node --test --experimental-strip-types 'test/*.test.ts' gives: "tests 7 / pass 7 / fail 0 / cancelled 0". I also type-checked tools/index.ts, tools/runs.ts and the test file with a strict tsc (module/moduleResolution NodeNext, target ES2022, --strict, --types node, plus --allowImportingTsExtensions for the test's .ts import) against a real built copy of @novox/mesh-sdk: no errors. The forge's own checks on this head agree: mesh/merge-gate — "head c6a9c52dc7 merged into trunk 45d01e77c2 — pass: builds lab → shanks; no bus step; every machine composes with the change as it did…" (success), and mesh/repo-check — "head c6a9c52dc7 merged into trunk 45d01e77c2 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…" (success).

lab_check stays read-only. The added setupProblems only runs git ls-remote --heads (a read) against every REPOSITORIES entry, and for the three NPM_REPOSITORIES it does a depth-1 clone into its own ${work}/check-setup scratch directory, which it rm -rfs both before and after the loop. It writes nothing to the forge, to the run's own working tree, or to any mesh-owned state — only to a throwaway directory under the lab's own work dir, exactly as the pre-existing mesh-lab check-clone under ${work}/check already did.

One non-blocking observation: installPlan and installStep disagree on the hypothetical case where a checkout's root has an unlocked package.json and a subdirectory has a locked one — installPlan keeps scanning and would report that subdirectory as installable, while installStep's shell exits before ever looking at subdirectories once it sees the root's unlocked package.json. lab_check would still flag this case as broken (its unlocked-root problem fires either way), and none of the seven repositories in REPOSITORIES hit this shape today, so it does not affect this fix, but it is worth tightening if a repository ever grows that layout.

I cloned mesh-catalog (this PR's head), mesh-lab, mesh-sdk, mesh-tools, mesh-controller and mesh-host over HTTPS from the forge to verify the above; mesh-tools-go is private and I did not clone it, confirming its lack of a package.json instead through the forge's contents and git-trees API (3 files total, non-recursive and recursive both agree, no package.json).

Verdict: approve at c6a9c52dc7f2a3e0975a0a631d54a621b1198d96 The install rule is right for every repository a run clones. On main: mesh-lab and mesh-sdk each hold package.json and package-lock.json at their root, so installPlan returns {install:[root], unlocked:[]} for both and the root alone is installed and built. mesh-tools has no package.json at its root at all and keeps its package in node-tools/, which holds both package.json and package-lock.json; installPlan correctly finds nothing at the root, then finds the lock one level down and returns {install:[node-tools], unlocked:[]} — this is exactly the checkout that broke lab_run before this fix. mesh-controller, mesh-host and mesh-catalog have no package.json anywhere in their tree (verified against their main branches), and mesh-tools-go (private; its forge tree is only Dockerfile, README.md and module.json, no package.json) is also package-free. All four are correctly left out of NPM_REPOSITORIES, so installStep is never invoked on them — they pass through a run's build step untouched, with no install attempted and nothing to fail on. That answers check 2: a Go repository with no package.json passes a run cleanly because it is never asked to install, not because an empty install silently "succeeds". The 7 tests in modules/lab/test/runs.test.ts fail on main and pass at the head. I copied the new test file onto a worktree of main (45d01e77c26d): it fails to even load, with 'SyntaxError: The requested module "../tools/runs.ts" does not provide an export named "NPM_REPOSITORIES"' (0 of 7 run), which matches main's runs.ts hard-coding `npm ci` at the root of mesh-sdk, mesh-tools and mesh-lab — the exact bug issue 624 reports. At the head, `node --test --experimental-strip-types 'test/*.test.ts'` gives: "tests 7 / pass 7 / fail 0 / cancelled 0". I also type-checked tools/index.ts, tools/runs.ts and the test file with a strict tsc (module/moduleResolution NodeNext, target ES2022, --strict, --types node, plus --allowImportingTsExtensions for the test's `.ts` import) against a real built copy of @novox/mesh-sdk: no errors. The forge's own checks on this head agree: `mesh/merge-gate` — "head c6a9c52dc7f2 merged into trunk 45d01e77c26d — pass: builds lab → shanks; no bus step; every machine composes with the change as it did…" (success), and `mesh/repo-check` — "head c6a9c52dc7f2 merged into trunk 45d01e77c26d — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…" (success). lab_check stays read-only. The added setupProblems only runs `git ls-remote --heads` (a read) against every REPOSITORIES entry, and for the three NPM_REPOSITORIES it does a depth-1 clone into its own `${work}/check-setup` scratch directory, which it `rm -rf`s both before and after the loop. It writes nothing to the forge, to the run's own working tree, or to any mesh-owned state — only to a throwaway directory under the lab's own work dir, exactly as the pre-existing mesh-lab check-clone under `${work}/check` already did. One non-blocking observation: installPlan and installStep disagree on the hypothetical case where a checkout's root has an unlocked package.json *and* a subdirectory has a locked one — installPlan keeps scanning and would report that subdirectory as installable, while installStep's shell exits before ever looking at subdirectories once it sees the root's unlocked package.json. lab_check would still flag this case as broken (its unlocked-root problem fires either way), and none of the seven repositories in REPOSITORIES hit this shape today, so it does not affect this fix, but it is worth tightening if a repository ever grows that layout. I cloned mesh-catalog (this PR's head), mesh-lab, mesh-sdk, mesh-tools, mesh-controller and mesh-host over HTTPS from the forge to verify the above; mesh-tools-go is private and I did not clone it, confirming its lack of a package.json instead through the forge's contents and git-trees API (3 files total, non-recursive and recursive both agree, no package.json).
mesh-admin merged commit 19ecad261c into main 2026-10-13 11:11:58 +00:00
mesh-admin deleted branch fix/624-lab-run-installs-what-each-checkout-has 2026-10-13 11:11:59 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#268