Skip to content

Build(deps-dev): Bump @types/node from 22.14.0 to 24.0.8#82

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/types/node-24.0.8
Closed

Build(deps-dev): Bump @types/node from 22.14.0 to 24.0.8#82
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/types/node-24.0.8

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Jul 1, 2025

Bumps @types/node from 22.14.0 to 24.0.8.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 22.14.0 to 24.0.8.
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-version: 24.0.8
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Jul 1, 2025

The reviewers field in the dependabot.yml file will be removed soon. Please use the code owners file to specify reviewers for Dependabot PRs. For more information, see this blog post.

@dependabot dependabot Bot requested a review from joelteply July 1, 2025 01:02
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 1, 2025
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Jul 8, 2025

Superseded by #87.

@dependabot dependabot Bot closed this Jul 8, 2025
@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/types/node-24.0.8 branch July 8, 2025 00:05
joelteply added a commit that referenced this pull request May 31, 2026
…headless fix (#1505)

Iterating on the moment-of-truth test. With #1504 (socket discovery)
landed, the next concrete break surfaced:

  AIRC daemon attach stream stopped: failed to attach to airc daemon:
  attach requires a channel in the owner-core model

Per `airc-daemon/src/server.rs:274` + `airc-ipc/src/request.rs:144`
docstring: the owner-core router subscribes PER CHANNEL — no global
fan-out table. AttachRequest.channel is mandatory; clients attach
once per room they care about. Continuum was sending
`AttachRequest::default()` (no channel), which worked under an
earlier model the substrate has since left behind.

### What ships

- `discover_default_channel()` — parses `airc room` stdout for the
  scope's current room `channel: <uuid>` line + returns the UUID.
  Honors `$AIRC_DEFAULT_CHANNEL` env override (UUID) for tests +
  multi-room operators pinning the first attach. Robust to
  whitespace + alt-capitalization (`Channel:`, `CHANNEL:`); fails
  loud (UnparseableChannel error) if airc renames the field.

- `AircModule::attach_channel: Option<RoomId>` new field, populated
  by `discover_and_construct` alongside the socket path. `initialize`
  spawns the daemon attach only when BOTH a socket AND a channel
  are available — partial degradation rather than boot failure.

- `inbound_attach::spawn_daemon_attach` + `run_daemon_attach` take a
  `channel: RoomId` and put it in `AttachRequest.channel = Some(_)`.
  Single caller updated; no other code paths.

- 4 new unit tests for the parser (typical airc room output, alt
  capitalization + whitespace, missing channel line, non-UUID after
  label) — 7 discovery tests total.

### Verification (manual end-to-end on this branch)

  $ rm -f /tmp/hctest.sock && \
    target/release/continuum-core-server /tmp/hctest.sock > boot.log 2>&1 &
  $ grep -E "Discovered airc" boot.log
  Discovered airc daemon socket via `airc ipc-endpoint`
    socket_path="/Users/joel/.airc/runtime/airc-machine-…-v5.sock"
  Discovered airc default channel via `airc room`
    channel=11c1a7ac-cb85-5ca0-a5b4-2847280ea3fa

  # No more "attach requires a channel in the owner-core model" warning.

  $ cargo test --release --lib --features metal,accelerate airc::discovery
  test result: ok. 7 passed; 0 failed.

### Next concrete break revealed (follow-up #82, not in this PR)

The attach now connects + passes the channel gate. Next-layer error:
  `AIRC daemon attach stream stopped: failed to read airc daemon
   event: Semantic(None, "missing field 'event'")`
CBOR Response variant shape changed between continuum's pinned
airc-ipc SHA (428f9281…) and the live daemon. Likely fix: SHA bump
in src/workers/Cargo.toml after the AttachRequest channel change
lands on airc canary. Tracked separately so this PR can ship the
single, complete fix for break #2.

### Pattern

Iterate-on-moment-of-truth: each fix uncovers the next layer; each
PR is one well-scoped substrate change with end-to-end verification
+ a tracked follow-up for the next surfaced break. Three breaks
revealed so far (1504, this PR, #82); breaks 1 + 2 fixed.

### Follow-ups (filed)

- airc-side: `airc room --print-channel` flag (mirror the `airc
  ipc-endpoint` pattern) so continuum's stdout parser can be
  replaced with a stable contract. Note in the parser docstring.
- continuum #82: CBOR Response shape mismatch / SHA bump.
- continuum: multi-room attach (one daemon_attach task per channel
  when continuum rooms become first-class — currently single-room).

### References

- airc owner-core model: `airc-daemon/src/server.rs:274`,
  `airc-ipc/src/request.rs:144` (AttachRequest docstring),
  `airc-lib/tests/common/mod.rs` (model description).
- continuum#1504 — sibling PR (socket discovery) — this PR's
  prerequisite, already landed on canary.
- airc#1095 — sibling PR (`airc ipc-endpoint`), pending Windows CI.
- Memories: `headless-rust-must-work-soon`, `continuum-thesis-airc-
  is-the-medium`, `every-error-is-an-opportunity-to-battle-harden`,
  `agent-review-as-acceptable-approval`.
- ALPHA-GAP §0A line 706 — headless target.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants