Skip to main content

Ask another session what it is doing

Two sessions are registered: laptop-api (you are here) and server-ci (on another machine).

In laptop-api​

Ask server-ci on the bus what it is working on and whether it touched the migrations.

The model calls:

send { "from": "laptop-api", "to": "server-ci", "body": "What are you working on? Did you touch the migrations? Reply to laptop-api." }

The bus returns {"id": 42}. The message is queued, not read. Say "reply to <name>" in the body so the other side knows where to answer.

In server-ci​

If server-ci is a push session, the message appears on its own within about 5 seconds as a ← bus-push: line. The model summarizes it, replies with send, and acks with session=server-ci ids=[42].

If it is a plain session, nothing happens until someone asks it to look:

Check the bus.

It calls inbox with session=server-ci, shows the message, replies, and acks.

Back in laptop-api​

Any replies on the bus?

The model calls inbox with session=laptop-api and shows the reply. A plain session does not poll in a loop. Ask again later, or run this session with push too.