This website requires JavaScript.
Explore
Help
Sign In
novox
/
mesh-tools
Watch
6
Star
0
Fork
0
Code
Issues
Pull Requests
Actions
Packages
Projects
Releases
Wiki
Activity
Files
7b4428c51067e7d77998f636ea2657911529da10
mesh-tools
/
node-tools
/
internal
T
History
jochen
7b4428c510
Name the worker a piece of work came from, so a bundle taking two is handed each to its own handler
2026-10-09 10:12:39 +02:00
..
alive
Say the node tools are there, every minute (hq to-be 45 Phase 1, S11)
2026-10-06 10:06:29 +02:00
announce
Wait for every runtime discovery hears from, and name the ones it misses
2026-10-05 15:36:10 +02:00
bus
Name the worker a piece of work came from, so a bundle taking two is handed each to its own handler
2026-10-09 10:12:39 +02:00
console
Rank a search the same whatever order discovery heard things in
2026-10-07 20:27:26 +02:00
launch
Carry a bundle's seat traffic under its own name and kind, and start a module as its own account (hq ADR 0259)
2026-10-09 10:12:39 +02:00
meshtest
Check the tool runtime's own code before it merges, every test on a bus of its own (hq ADR 0237)
2026-10-06 22:04:46 +02:00
runtime
Carry a bundle's seat traffic under its own name and kind, and start a module as its own account (hq ADR 0259)
2026-10-09 10:12:39 +02:00
wire
node-tools in Go: the node's runtime, launch-only, wire-compatible with the TypeScript (hq ADR 0193)
2026-10-03 21:21:52 +02:00