8000 Add ability to set XML parsing options by rybesh · Pull Request #12 · noflo/noflo · GitHub
[go: up one dir, main page]

Skip to content

Add ability to set XML parsing options - #12

Merged
bergie merged 7 commits into
noflo:masterfrom
rybesh:master
Mar 8, 2012
Merged

bergie merged 7 commits into
noflo:masterfrom
rybesh:master

Conversation

@rybesh
@rybesh rybesh commented Jan 13, 2012
Copy link
Copy Markdown
Contributor

Small patch adding an "options" port to ParseXML.

bergie added a commit that referenced this pull request Mar 8, 2012
Add ability to set XML parsing options
@bergie
bergie merged commit d2640df into noflo:master Mar 8, 2012
AsherBond pushed a commit to AsherBond/noflo that referenced this pull request Oct 12, 2026
AsherBond pushed a commit to AsherBond/noflo that referenced this pull request Oct 12, 2026
Work document noflo#12, following the reticulum-js reference setup:

- per-workspace test:deno runs the ESM specs under deno test
  --no-check, with narrowed permissions on the core package
  (--allow-read=spec,src --allow-env) and --allow-all on packages
  that touch the filesystem or spawn processes
- per-workspace test:bun runs bun test with explicit spec globs so
  fixtures are not picked up as tests
- root test:deno and test:bun aggregate with --workspaces
  --if-present
- CI gains parallel deno and bun jobs next to the canonical Node
  job, mirroring the reticulum-js workflow
bergie added a commit that referenced this pull request Oct 16, 2026
…tion set before consuming

The collector consumed the originating message in an activation that then
waited for the inner component's outputs. Inside a network — where the
inner output arrives on a later bounded-edge delivery — that deadlocks:
new arrivals fire fresh process contexts, an IP consumed by a waiting
activation never comes back, and the collector's activation stays pending
forever with the inner output buffered, so the wrapped component never
closes and the network never ends. The standalone direct-socket specs
passed only because the burst completed before the collector's first
precondition check.

The collector now has-checks the message, the fields config, and every
mapped inner output stream (or the error stream) before any get, so the
message stays buffered until the collector can fire with both.

Found via a flowtrace of a wrapped component running inside a network
(work document #36 update #12).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0