Repository navigation
Added file status component. - #18
Merged
Merged
Conversation
bergie
added a commit
that referenced
this pull request
Oct 8, 2026
Work document #18 makes plain-ESM browser operation a CI-gated guarantee. This guard keeps the browser-reachable packages (@noflo/noflo, @noflo/graph, @noflo/fbp, @noflo/as-component) free of Node-isms: no node: imports, eval(), new Function, or require(), and no Node process global access outside a reviewed allowlist of files whose uses are runtime-guarded. The process check matches only known Node-global members so the FBP process-entity vocabulary (process.component and friends) does not trip it. Comments are stripped with a string-aware scanner that preserves original line numbers. Server-side packages (@noflo/loader-node, @noflo/fbp-spec-runner) are out of scope by design. Wired into npm test as check:browser.
bergie
added a commit
that referenced
this pull request
Oct 9, 2026
Work document #28 (proposed): the isomorphic FBP Protocol 2.0 runtime for NoFlo over Reticulum, superseding the noflo-runtime-base / noflo-runtime-websocket lineage — Reticulum-only, protocol-2.0-only, capabilities as the 0x02 mask instead of protocol: strings. Isomorphic per the no-build browser contract (work document #18): plain ESM, no Node builtins in the runtime core; the application supplies its own Reticulum instance with platform-appropriate interfaces (TCP on servers, WebSocket/WebRTC in browsers), matching @reticulum/core's subpath-import design. Dependencies: the 2.x engine (@noflo/noflo, @noflo/graph), the wire format (@noflo/fbp-protocol), the transport (@reticulum/core), and @reticulum/lxmf for the offline telemetry drops (wired behind a subpath export when telemetry lands). The smoke test pins that the entrypoint and its full dependency graph import cleanly.
bergie
added a commit
that referenced
this pull request
Oct 9, 2026
Phase 2 of work document #28: RegistryProtocol, the Two-Step Cache server side, driven end-to-end through the runtime core in tests. The runtime consumes an application-supplied catalog — the same philosophy as the engine's application-supplied component registry (work documents #6/#16): signatures are ready at handoff, and the handler derives the wire state from them. A signature is exactly the 0x24 detail shape (declared kind plus the full port field set), valid with no implementation behind it, so manifest/sidecar-sourced stubs flow through unmodified. - 0x20 syncs answer 0x21 on hash match, 0x22 manifest otherwise — the runtime always answers (work document #4 update #18) - 0x23 details answer with only the requested known components; unknown names are omitted, and an empty response is an answer - 0x25 source writes and 0x27 installs map onto optional catalog hooks (source and signature are orthogonal, so a write never relabels a component); missing hooks surface as unsupported events - every catalog change re-derives sig_hash values and the registry_hash through the protocol package's canonical serializations Supporting changes: the runtime core now accepts async handlers (WebCrypto hashing is async), capturing rejections as error events like synchronous throws; @noflo/fbp-protocol re-exports its ComponentDetail/PortInfo/ ManifestEntry typedefs from the entrypoint so dependents can type against them.
bergie
added a commit
that referenced
this pull request
Oct 9, 2026
Work document #28 (proposed): the isomorphic FBP Protocol 2.0 runtime for NoFlo over Reticulum, superseding the noflo-runtime-base / noflo-runtime-websocket lineage — Reticulum-only, protocol-2.0-only, capabilities as the 0x02 mask instead of protocol: strings. Isomorphic per the no-build browser contract (work document #18): plain ESM, no Node builtins in the runtime core; the application supplies its own Reticulum instance with platform-appropriate interfaces (TCP on servers, WebSocket/WebRTC in browsers), matching @reticulum/core's subpath-import design. Dependencies: the 2.x engine (@noflo/noflo, @noflo/graph), the wire format (@noflo/fbp-protocol), the transport (@reticulum/core), and @reticulum/lxmf for the offline telemetry drops (wired behind a subpath export when telemetry lands). The smoke test pins that the entrypoint and its full dependency graph import cleanly.
bergie
added a commit
that referenced
this pull request
Oct 9, 2026
Phase 2 of work document #28: RegistryProtocol, the Two-Step Cache server side, driven end-to-end through the runtime core in tests. The runtime consumes an application-supplied catalog — the same philosophy as the engine's application-supplied component registry (work documents #6/#16): signatures are ready at handoff, and the handler derives the wire state from them. A signature is exactly the 0x24 detail shape (declared kind plus the full port field set), valid with no implementation behind it, so manifest/sidecar-sourced stubs flow through unmodified. - 0x20 syncs answer 0x21 on hash match, 0x22 manifest otherwise — the runtime always answers (work document #4 update #18) - 0x23 details answer with only the requested known components; unknown names are omitted, and an empty response is an answer - 0x25 source writes and 0x27 installs map onto optional catalog hooks (source and signature are orthogonal, so a write never relabels a component); missing hooks surface as unsupported events - every catalog change re-derives sig_hash values and the registry_hash through the protocol package's canonical serializations Supporting changes: the runtime core now accepts async handlers (WebCrypto hashing is async), capturing rejections as error events like synchronous throws; @noflo/fbp-protocol re-exports its ComponentDetail/PortInfo/ ManifestEntry typedefs from the entrypoint so dependents can type against them.
AsherBond
pushed a commit
to AsherBond/noflo
that referenced
this pull request
Oct 12, 2026
Allow to specify the preferred network interface.
AsherBond
pushed a commit
to AsherBond/noflo
that referenced
this pull request
Oct 12, 2026
Work document noflo#18: browser operation of the 2.x core is now verified, not just assumed. The browser/ fixture consumes @noflo/noflo, @noflo/graph, and @noflo/fbp as plain ES modules from static files resolved through a native import map — no bundler, no build step — and runs the static-registry flow end to end: graph construction over the native graph model, network start against a ComponentLoader backed by the name-to-ESM-URL registry, packet flow through two components, live component registration via a registry change event (noflo#6 live surface), and network stop. Progress is published on window.__fixtureResult and the page status element. A zero-dependency static server (browser/serve.mjs) serves the repo root so the import map reaches workspace sources directly. Playwright drives Chromium, Firefox, and WebKit against it in a new CI job; verified locally with headless Chrome (all seven phases complete).
AsherBond
pushed a commit
to AsherBond/noflo
that referenced
this pull request
Oct 20, 2026
… loud (work document noflo#48) Implements the invariant the three-shape verification re-opened: the Network must not lose messages silently under any scheduling. Three surfaces, all engine-level and wire-safe (the 0x0f STRANDED tracefile encoding stays bracket-shaped; the data-shaped entries ride the JS event bus pending the freeze discussion): - The closedown residue census: when the closedown predicate fires, the component's undeliverable data residue (per port, per scope, via the new InPort.strandedData()) is emitted as a component 'stranded' event and logged with named counts — the moment the strand became final, not a debug dump at shutdown. Standing IIP buffers are excluded: an unconsumed initial is configuration re-delivered per run (noflo#46), not stranded work. - The control-stream replacement clobber: when a control port's latest-stream rule discards a buffered stream holding packets, the InPort dispatches a stranded report naming the discarded counts — the bang-vs-corpus hazard from the noflo-jekyll verification becomes diagnosable at the replacement moment instead of as a downstream strand. - The unattached-outport send: a send into an outport with no attached sockets vanishes by contract, but the vanish now dispatches a stranded report and logs — the noflo#35 update noflo#18 footgun becomes visible. The component-side answer for legs that must not drop is required: true (escalates in checkRequired). The Network forwards component stranded events onto its event bus; bracket-shaped entries record to Flowtrace under the existing 0x0f encoding, data-shaped entries stay on the JS surface. Three new deterministic pins in spec/wd48-anomaly.js: the closedown census, the replacement clobber, and the unattached-fail-leg drop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.