- theme.scss and figures draw with the extension's --calc-… tokens; light/dark pair plus the high-contrast button; a11y highlight style for html - figure labels split so none leaves its viewBox in any language - _quarto-fr.yml: French cross-reference prefixes - notes extension synced to 2.8.18 - conv/: Parts IV, V and VI logged, pasted terminal output redacted Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
69 lines
4.3 KiB
Markdown
69 lines
4.3 KiB
Markdown
# Conversation Log — Part VI — Replay It Over Syncthing · Steps 39–47 (turns 68–)
|
||
|
||
<!-- nav -->
|
||
> [⬅ Previous: Part V](05-part-V.md) · [Index](../conv.md) · Next: *(not started yet)* ➡
|
||
>
|
||
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · [Part I](01-part-I.md) · [Part II](02-part-II.md) · [Part III](03-part-III.md) · [Part IV](04-part-IV.md) · [Part V](05-part-V.md) · **Part VI**
|
||
<!-- /nav -->
|
||
|
||
---
|
||
|
||
## [68] Student
|
||
|
||
> no, i'll do each step
|
||
|
||
**Tutor:** Offer of shortcuts withdrawn and recorded as a standing preference. Opened Part VI and set up Step 39: copy `05-dynamic-filesystem` to the server, repoint the container at it, clear the board, run sensor on the laptop and the two dynamic services in the container, then `Configure.java`.
|
||
|
||
## [69] Student
|
||
|
||
> 2minutes and still nothing, don't know what went wrong
|
||
|
||
(`Configure.java` printed "Wired: consoleIn -> rot13 -> consoleOut" on the laptop; the two `docker exec` commands on the server appeared to return.)
|
||
|
||
## [69] Tutor — actions taken
|
||
|
||
- Read the laptop replica: `rot13/inbox` and `consoleOut/inbox` each held a `TOPIC` (02:29:15), `consoleIn/outbox` held the input (02:29:33), and **`rot13/outbox` was empty** — so ROT13 produced nothing.
|
||
- Gave three ordered checks: container running and whether the `TOPIC` reached `/srv/syncthing/course-message-board/rot13/inbox/`; a write probe inside the container (the `--user` change being the prime suspect, as in Part III); and watching one service start in the foreground to see whether it stays attached.
|
||
|
||
## [70] Student
|
||
|
||
> skip temp step 39, serv is busy with syncthing
|
||
|
||
**Tutor:** Step 39 parked with a bookmark — when the server is free, check first whether the server's `rot13/inbox` ever receives the `TOPIC`. Moved on to Step 40.
|
||
|
||
## [71] Student
|
||
|
||
> that means there is no information processing of our architecture performing on the data, but that doesn't mean that the data doesn't go through several process to travel from input -> rot13
|
||
|
||
**Tutor:** ✅ the step's point. Sharpened the distinction: a **transport hop** (Syncthing, even a relay) adds no participant that knows the topology and contradicts nothing; an **architectural hop** (a mediator of ours) adds a component that must know both names and sits in the availability chain. The honest claim is about knowledge and reaction, not about packets.
|
||
|
||
## [72] Student
|
||
|
||
> i'd say that the text part are Event, text has been entered, text has been rot13ed, but route are created betwwen process, topic messages are sent
|
||
|
||
**Tutor:** ✅ `TEXT` messages are Events, with the past-tense naming the step suggests (`ConsoleIn/E/text`, `ROT13/E/crypted`). `ROUTE` and `TOPIC` are **Intent**: they report nothing and describe nothing currently true, they request behaviour. Named the trap: publishing an Intent is itself something that happened, but classification follows the message's content, not its existence.
|
||
|
||
## [73] Student
|
||
|
||
> we can imagine a process that verify that everyhting is correctly wired, in this case this process would asked to rot13 "are you subsrcibed to consolein?" or "what are your subscriptions?" which display the current state of the subscription of rot13
|
||
|
||
**Tutor:** Right content, wrong shape: *asking* is a call, and a call needs the asker to know the component and to wait. Status is **published** — `ROT13/S/subscriptions` whenever the wiring changes — so the reader needs a topic, not a component, and ROT13 never learns who audits it. Forward link to Step 71, retained Status vs non-retained Events. Added the division of labour: Event = happened (useless if you were not listening), Status = true now (what a newcomer needs), Intent = please make it so.
|
||
|
||
## [74] Student
|
||
|
||
> consoleIn is the writer for its outbox, rot13 for rot13/outbox
|
||
|
||
**Tutor:** ✅ ownership correct. Re-asked the second half with Step 47's distinction in hand: UUIDs prevent filename collisions, writer authority decides who owns a logical resource, and the rule bites hardest for Status.
|
||
|
||
## [75] Student
|
||
|
||
> a subscriber can't know which component published the event
|
||
|
||
---
|
||
|
||
<!-- nav -->
|
||
> [⬅ Previous: Part V](05-part-V.md) · [Index](../conv.md) · Next: *(not started yet)* ➡
|
||
>
|
||
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · [Part I](01-part-I.md) · [Part II](02-part-II.md) · [Part III](03-part-III.md) · [Part IV](04-part-IV.md) · [Part V](05-part-V.md) · **Part VI**
|
||
<!-- /nav -->
|