Skip to content

fix(inbound): tell tinyeventqueues which bus name serves its storage - #8326

Closed
M3gA-Mind wants to merge 1 commit into
tinyhumansai:mainfrom
M3gA-Mind:fix/eventqueues-storage-callback
Closed

M3gA-Mind wants to merge 1 commit into
tinyhumansai:mainfrom
M3gA-Mind:fix/eventqueues-storage-callback

Conversation

@M3gA-Mind

@M3gA-Mind M3gA-Mind commented Oct 23, 2026 •

Copy link
Copy Markdown
Collaborator

Do not merge yet. This has to land together with the registry record moving to tinyeventqueues v0.2.0. Merging it while the registry still points at v0.1.3 breaks inbound events in release builds.

What it changes

The tinyeventqueues module keeps its queues in host storage and needs the bus name that serves that storage. It refuses to load without one ("host callback destination is required: set storage_callback in the module configuration"). Today the host never sends it, so the module fails closed and every inbound queue call fails (Q-H2).

inbound::module_config now adds "storage_callback" (tinystoragedrivers_bus::STORAGE_INTERFACE, ai.tinyhumans.tinystorage.Storage) next to queues and pipeline. This is the value #8309 already sends TinyMCP. The module parses it with tinybus::BusName::new and connects through tinystoragedrivers_busproxy::connect_storage_at.

#8309's arm in modules::ops::module_config is never reached for this module: the event_queues::MODULE_ID branch above it returns inbound::module_config first. That is why the key goes here.

Why the merge order matters

  • tinyeventqueues v0.1.3, which the registry pins now, declares Settings with #[serde(deny_unknown_fields)] and has no storage_callback field. A release build would reject this config.
  • v0.2.0 (and the gitlink a719a6e that source builds use) accepts the key and requires it.

So this commit and the registry/gitlink move to v0.2.0 belong in one merge.

Test

inbound::settings::tests::the_module_config_is_what_the_storage_grant_declares asserts the blob carries storage_callback = "ai.tinyhumans.tinystorage.Storage".

@coderabbitai

coderabbitai Bot commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

M3gA-Mind added a commit to M3gA-Mind/openhuman that referenced this pull request Oct 23, 2026
…age bus

- registry record: version, release URL and the full v0.2.1 asset set:
  16 archives (Arch is published for x86_64 only, as
  `archlinux-rolling-x86_64`), up from 11. Every digest is the GitHub
  asset digest, equal to the release checksum.toml.
- vendor/tinyeventqueues -> a8d1e306a5 (tag v0.2.1, tinyeventqueues main);
  CONTRACT_VERSION stays (0, 2)
- inbound/settings.rs: module_config now carries `storage_callback`, the
  storage host's bus name, plus its settings_tests assertion. This is
  W2's change from tinyhumansai#8326 (7ad45b7). It has to ship in the same change
  as the record: v0.1.3 refuses unknown config keys, and v0.2.1 refuses to
  load without this one. The host still derives the scope and grant from
  the authenticated caller.
- Cargo.lock and crates/openhuman-app/Cargo.lock: tinyeventqueues and
  tinyeventqueues-bus 0.1.3 -> 0.2.1 (workspace version is the only
  manifest change)
@M3gA-Mind

Copy link
Copy Markdown
Collaborator Author

Superseded by #8327, which carries this change (storage_callback for tinyeventqueues plus its test) together with the tinyeventqueues v0.2.1 re-pin, so the two land in one merge.

@M3gA-Mind M3gA-Mind closed this Oct 23, 2026
@M3gA-Mind
M3gA-Mind deleted the fix/eventqueues-storage-callback branch October 23, 2026 21:13
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.

1 participant