Night-mode styling, French cross-references, and the log through Part VI
- 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>
This commit is contained in:
1 parent
afb816f459
commit
f7fa60ba81
62 files changed
+3552
-852
No files matched your search
@@ -3,7 +3,7 @@
|
||||
<!-- nav -->
|
||||
> ⬅ Previous: *(none)* · [Index](../conv.md) · [Next: Part I ➡](01-part-I.md)
|
||||
>
|
||||
> All parts: **Setup & Step 0** · [Part I](01-part-I.md) · [Part II](02-part-II.md) · [Part III](03-part-III.md)
|
||||
> All parts: **Setup & Step 0** · [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](06-part-VI.md)
|
||||
<!-- /nav -->
|
||||
|
||||
---
|
||||
@@ -309,5 +309,5 @@ java --version
|
||||
<!-- nav -->
|
||||
> ⬅ Previous: *(none)* · [Index](../conv.md) · [Next: Part I ➡](01-part-I.md)
|
||||
>
|
||||
> All parts: **Setup & Step 0** · [Part I](01-part-I.md) · [Part II](02-part-II.md) · [Part III](03-part-III.md)
|
||||
> All parts: **Setup & Step 0** · [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](06-part-VI.md)
|
||||
<!-- /nav -->
|
||||
+3
-3
@@ -3,7 +3,7 @@
|
||||
<!-- nav -->
|
||||
> [⬅ Previous: Setup & Step 0](00-setup-and-step-0.md) · [Index](../conv.md) · [Next: Part II ➡](02-part-II.md)
|
||||
>
|
||||
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · **Part I** · [Part II](02-part-II.md) · [Part III](03-part-III.md)
|
||||
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · **Part I** · [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](06-part-VI.md)
|
||||
<!-- /nav -->
|
||||
|
||||
---
|
||||
@@ -15,7 +15,7 @@
|
||||
then, after being asked to actually run the command:
|
||||
|
||||
```
|
||||
[matsune@nitro5 ProcessControl]$ java --version
|
||||
[#user@#laptop ProcessControl]$ java --version
|
||||
openjdk 25.0.4.1 2026-08-18
|
||||
OpenJDK Runtime Environment (build 25.0.4.1)
|
||||
OpenJDK 64-Bit Server VM (build 25.0.4.1, mixed mode, sharing)
|
||||
@@ -740,5 +740,5 @@ Read section 10 (lines 644–694) to see it in the README's words. Note that the
|
||||
<!-- nav -->
|
||||
> [⬅ Previous: Setup & Step 0](00-setup-and-step-0.md) · [Index](../conv.md) · [Next: Part II ➡](02-part-II.md)
|
||||
>
|
||||
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · **Part I** · [Part II](02-part-II.md) · [Part III](03-part-III.md)
|
||||
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · **Part I** · [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](06-part-VI.md)
|
||||
<!-- /nav -->
|
||||
+2
-2
@@ -3,7 +3,7 @@
|
||||
<!-- nav -->
|
||||
> [⬅ Previous: Part I](01-part-I.md) · [Index](../conv.md) · [Next: Part III ➡](03-part-III.md)
|
||||
>
|
||||
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · [Part I](01-part-I.md) · **Part II** · [Part III](03-part-III.md)
|
||||
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · [Part I](01-part-I.md) · **Part II** · [Part III](03-part-III.md) · [Part IV](04-part-IV.md) · [Part V](05-part-V.md) · [Part VI](06-part-VI.md)
|
||||
<!-- /nav -->
|
||||
|
||||
---
|
||||
@@ -503,5 +503,5 @@ Each time it moved *away* from the capabilities. It never disappeared. (Bookmark
|
||||
<!-- nav -->
|
||||
> [⬅ Previous: Part I](01-part-I.md) · [Index](../conv.md) · [Next: Part III ➡](03-part-III.md)
|
||||
>
|
||||
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · [Part I](01-part-I.md) · **Part II** · [Part III](03-part-III.md)
|
||||
> All parts: [Setup & Step 0](00-setup-and-step-0.md) · [Part I](01-part-I.md) · **Part II** · [Part III](03-part-III.md) · [Part IV](04-part-IV.md) · [Part V](05-part-V.md) · [Part VI](06-part-VI.md)
|
||||
<!-- /nav -->
|
||||
+116
-9
@@ -1,9 +1,9 @@
|
||||
# Conversation Log — Part III — Make It Actually Distributed · Steps 19–27 (turns 45–)
|
||||
|
||||
<!-- nav -->
|
||||
> [⬅ Previous: Part II](02-part-II.md) · [Index](../conv.md) · Next: *(not started yet)* ➡
|
||||
> [⬅ Previous: Part II](02-part-II.md) · [Index](../conv.md) · [Next: Part IV ➡](04-part-IV.md)
|
||||
>
|
||||
> 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**
|
||||
> 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** · [Part IV](04-part-IV.md) · [Part V](05-part-V.md) · [Part VI](06-part-VI.md)
|
||||
<!-- /nav -->
|
||||
|
||||
---
|
||||
@@ -60,12 +60,12 @@ Repeat on every other machine you'll use. For Step 21 you need **at least two**,
|
||||
## [46] Student
|
||||
|
||||
```
|
||||
[matsune@nitro5 ProcessControl]$ sudo pacman -S synchting
|
||||
[#user@#laptop ProcessControl]$ sudo pacman -S synchting
|
||||
[sudo] password for matsune:
|
||||
error: target not found: synchting
|
||||
[matsune@nitro5 ProcessControl]$ pacman -Ql syncthing | grep systemd
|
||||
[#user@#laptop ProcessControl]$ pacman -Ql syncthing | grep systemd
|
||||
error: package 'syncthing' was not found
|
||||
[matsune@nitro5 ProcessControl]$
|
||||
[#user@#laptop ProcessControl]$
|
||||
```
|
||||
|
||||
## [46] Tutor — actions taken
|
||||
@@ -96,9 +96,9 @@ pacman -Ql syncthing | grep systemd
|
||||
## [47] Student
|
||||
|
||||
```
|
||||
[matsune@nitro5 ProcessControl]$ syncthing --version
|
||||
[#user@#laptop ProcessControl]$ syncthing --version
|
||||
syncthing v2.1.5 "Hafnium Hornet" (go1.27.0-X:nodwarf5 linux-amd64) syncthing@archlinux 2026-09-08 10:28:56 UTC [libsqlite3, noupgrade]
|
||||
[matsune@nitro5 ProcessControl]$
|
||||
[#user@#laptop ProcessControl]$
|
||||
```
|
||||
|
||||
## [47] Tutor — actions taken
|
||||
@@ -259,8 +259,115 @@ Noted, nothing built. Back to the Syncthing detour for Steps 19–20.
|
||||
|
||||
---
|
||||
|
||||
## [53] Student (2026-10-05)
|
||||
|
||||
> Hi, i'm ready to take back from where i left
|
||||
|
||||
## [53] Tutor — actions taken
|
||||
|
||||
- Read-only checks of the Syncthing detour's state: `systemctl --user is-enabled syncthing.service` → **enabled**, `is-active` → **active**, and the web GUI answers on `http://127.0.0.1:8384` (HTTP 200). So the service was started since turn [47].
|
||||
- Read `~/.local/state/syncthing/config.xml`: one device, this machine (`nitro5`), and no shared folder configured yet. Step 21 items 2–4 are therefore still open.
|
||||
- Schedule check against `Schedule.md`: Parts II–VIII were due 29 Sep by my inferred mapping; today is 5 Oct, so this part is 6 days past that date — more than the two days that call for a word about it. The next sessions are 06 Oct "Now You Do It" and 13 Oct "Graded Exercise I".
|
||||
|
||||
## [53] Tutor — reply
|
||||
|
||||
Welcome back. Syncthing is running now (enabled, active, GUI up), so that half of the detour is done. Still open: a second device and a shared folder, plus the Step 20 question.
|
||||
|
||||
**Schedule, honestly:** Part III was due 29 Sep by my reading of the plan; it is 5 Oct. The sessions ahead are "Now You Do It" tomorrow and **Graded Exercise I on 13 Oct**, where your own system and report are presented. Parts IV–VIII (steps 28–53) are what turn the five awkward mediators into the dynamic version the graded exercise wants you to defend, and Part IX (MQTT) is the transport the group work uses. You are free to keep going at your pace, and you can work ahead whenever you like, but if only one thing fits before the 13th, the rewind in Part IV is worth more than finishing Syncthing.
|
||||
|
||||
That gives you a choice for right now:
|
||||
|
||||
- **(a) Finish Part III properly:** pair a second device, share one folder, run the `hello.txt` test (Step 22), then distribute the five processes across two machines (Step 24) and count what one keystroke costs (Step 25).
|
||||
- **(b) Park Syncthing at "it runs"** and jump to Part IV, the rewind, where the mediators get questioned and the services start subscribing for themselves. The filesystem transport keeps working locally for every later step; only the "two computers" demonstration waits.
|
||||
|
||||
**Either way, two small things first:**
|
||||
1. The Step 20 question is still open: why is Syncthing **not** a message broker, even though our messages travel through it?
|
||||
2. If you pick (a): which second machine, and does it have Syncthing yet?
|
||||
|
||||
**Progress record**
|
||||
- Current step: 19–20 (Part III); Syncthing installed, enabled and running
|
||||
- Last observed result: service active, GUI on `http://127.0.0.1:8384`, one device (`nitro5`), no shared folder yet
|
||||
- Unresolved problem: six days past the inferred due date for Parts II–VIII; Graded Exercise I on 13 Oct
|
||||
- Next action: student answers the broker question and picks (a) finish Part III or (b) park Syncthing and start Part IV
|
||||
|
||||
---
|
||||
|
||||
## [54] Student
|
||||
|
||||
> i go with (a), concerning the open question: syncthing is a file synchroniser, it doesn't send any notification or anything, but the apeparence of a file can be used as a trigger, i can also try to install java in a separate docker and then delete it at the end of the tutorial (if it is possible)
|
||||
|
||||
## [54] Tutor — actions taken
|
||||
|
||||
- Read-only check of the live Syncthing config: devices `nitro5`, `homeserver`, `Nothing Phone`; folders Camera, Documents (`/mnt/data/Documents`), Downloads, Music, Pictures, Videos, all `sendreceive`. The course material therefore already replicates to the homeserver, since it lives under `/mnt/data/Documents`.
|
||||
- Read README lines 1415–1491 (Step 24 "Distribute the Five Processes") to give the two-machine split.
|
||||
|
||||
## [54] Tutor — reply
|
||||
|
||||
Step 20 answered correctly, folder choice (a) noted, and the Docker idea works. Sharpened the broker answer, gave the two-machine split for Step 24 and the container shape, and asked for the Step 22 result first.
|
||||
|
||||
**Progress record**
|
||||
- Current step: 21–22 (Part III)
|
||||
- Last observed result: three paired devices; Step 20 answered (Syncthing replicates, our own WatchService is the trigger)
|
||||
- Unresolved problem: dedicated folder not created yet; Java on the homeserver pending (Docker plan)
|
||||
- Next action: student creates the shared folder, runs the `hello.txt` test, and checks a JDK image in Docker
|
||||
|
||||
---
|
||||
|
||||
## [55] Student (2026-10-06)
|
||||
|
||||
Reported the Docker container created on the homeserver with `-v ~/course-message-board:/board -v ~/pc-src:/src:ro`, container id `3830338da4a9`, and "got that" for the file copy.
|
||||
|
||||
Earlier in the same exchange: `rm -rf ~/'…'` failed with permission denied (Docker had created that tree as root), and `find ~ -type d -path '*03-static-filesystem'` found nothing on the server, which corrected my claim that the Documents replica was already there.
|
||||
|
||||
## [55] Tutor — actions taken
|
||||
|
||||
- Wrote `~/course-message-board/hello.txt` on the laptop (one line, a timestamp) as the laptop half of Step 22's replication test. The folder holds Syncthing's `.stfolder` marker, so Syncthing owns it.
|
||||
- Left the observation on the server side to the student, and asked for two container checks (`ls /src`, `ls -la /board`).
|
||||
|
||||
## [55] Tutor — reply
|
||||
|
||||
Asked for: `docker exec pc-java ls /src` and `ls -la /board`, then the Step 22 round trip — `hello.txt` is already written on the laptop, the student checks it appears on the server and deletes it there, and I confirm the deletion arrives here.
|
||||
|
||||
**Progress record**
|
||||
- Current step: 22 (Part III)
|
||||
- Last observed result: container `pc-java` running on the homeserver; `hello.txt` written on the laptop at 00:01
|
||||
- Unresolved problem: replication not yet demonstrated in either direction; `/src` and `/board` contents inside the container unverified
|
||||
- Next action: student reports `ls /src`, `ls -la /board`, whether `hello.txt` arrived, then deletes it on the server
|
||||
|
||||
---
|
||||
|
||||
## [56] Student
|
||||
|
||||
Asked for the log to be redacted — anything sensitive marked with `#` — and pasted the diagnosis output from the server (redacted here):
|
||||
|
||||
```
|
||||
#user@#homeserver:~$ ls -ld ~/course-message-board
|
||||
drwxr-xr-x 2 root root 4096 Oct 5 23:46 ~/course-message-board
|
||||
ls: cannot access '~/course-message-board/.stfolder': No such file or directory
|
||||
user=#uid:#gid # docker inspect -f 'user={{.Config.User}}' pc-java
|
||||
uid=#uid(#user) gid=#gid(#user) groups=#groups
|
||||
```
|
||||
|
||||
## [56] Tutor — actions taken
|
||||
|
||||
- Redacted the whole log: account names, host names and `/home/<user>` paths in `conv/01-part-I.md` and `conv/03-part-III.md` are now `#user`, `#laptop`, `#homeserver`, `~`. Recorded the rule in memory so later turns are redacted as they are written.
|
||||
- Read the diagnosis: on the server `~/course-message-board` is **root-owned and holds no `.stfolder`**, so Syncthing never created it — it is the empty directory Docker made on the first run with my broken placeholder. The container runs as the student's uid, hence the `AccessDeniedException`.
|
||||
- Conclusion: the container is mounting the wrong directory, and the replica that actually received `hello.txt` lives at a path we have not identified yet.
|
||||
|
||||
## [56] Tutor — reply
|
||||
|
||||
Explained the decoy directory, and asked for `sudo find / -xdev -name '.stfolder' -printf '%h\n'` on the server to locate the real replica, plus `ls -ld` on it to decide which user the container should run as.
|
||||
|
||||
**Progress record**
|
||||
- Current step: 24 (Part III), blocked on the mount path
|
||||
- Last observed result: `~/course-message-board` on the server is root-owned with no `.stfolder`; container user is the student's uid
|
||||
- Unresolved problem: the real path of the replicated folder on the server is unknown
|
||||
- Next action: student locates the folder with the `.stfolder` search, reports it and its ownership
|
||||
|
||||
---
|
||||
|
||||
<!-- nav -->
|
||||
> [⬅ Previous: Part II](02-part-II.md) · [Index](../conv.md) · Next: *(not started yet)* ➡
|
||||
> [⬅ Previous: Part II](02-part-II.md) · [Index](../conv.md) · [Next: Part IV ➡](04-part-IV.md)
|
||||
>
|
||||
> 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**
|
||||
> 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** · [Part IV](04-part-IV.md) · [Part V](05-part-V.md) · [Part VI](06-part-VI.md)
|
||||
<!-- /nav -->
|
||||
@@ -0,0 +1,36 @@
|
||||
# Conversation Log — Part IV — Rewind · Steps 28–34 (turns 62)
|
||||
|
||||
<!-- nav -->
|
||||
> [⬅ Previous: Part III](03-part-III.md) · [Index](../conv.md) · [Next: Part V ➡](05-part-V.md)
|
||||
>
|
||||
> 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** · [Part V](05-part-V.md) · [Part VI](06-part-VI.md)
|
||||
<!-- /nav -->
|
||||
|
||||
---
|
||||
|
||||
## [62] Student
|
||||
|
||||
> so after test, after a ctrl+d, the console in is still working, but nothing is output anymore, i'd say that the subscription to topic which is interupt, explaining why nothing is output because consoleout don't receive anything from rot13 and rot13 don't receive anything from consolein
|
||||
|
||||
## [62] Tutor — actions taken
|
||||
|
||||
- Read `04-dynamic-in-jvm/DynamicQueueRot13.java` lines 37–52 (`runConsoleIn`) and 120–140 (`main`) to check the mechanism behind the observation.
|
||||
- Earlier in Part IV: corrected who publishes `TOPIC` (it is `main()`, lines 122–133, not ConsoleIn) and what the dynamic version changes (ROT13 takes straight from `consoleIn.outbox`; `rot13.inbox` now carries control messages only).
|
||||
|
||||
## [62] Tutor — reply
|
||||
|
||||
Corrected the mechanism: nothing is interrupted — `runConsoleIn` returns on EOF, so the producer is gone while both subscriber threads are still blocked in `take()` on sources that will never produce again. `main`'s `Thread.currentThread().join()` is what keeps the JVM alive. Also answered the second half: with no mediator, only the three capabilities are left in the data path, plus a startup-only dependency on the configurator publishing `TOPIC`. Then set Steps 31–34 as the next reading.
|
||||
|
||||
**Progress record**
|
||||
- Current step: 30 done → 31–34 (Part IV)
|
||||
- Last observed result: dynamic in-JVM version runs; after `Ctrl+D` the producer thread has returned and the two subscribers wait forever
|
||||
- Unresolved problem: none
|
||||
- Next action: student reads Steps 31–34 and answers the milestone question (who knows whom, where the topology lives, what drives the interaction)
|
||||
|
||||
---
|
||||
|
||||
<!-- nav -->
|
||||
> [⬅ Previous: Part III](03-part-III.md) · [Index](../conv.md) · [Next: Part V ➡](05-part-V.md)
|
||||
>
|
||||
> 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** · [Part V](05-part-V.md) · [Part VI](06-part-VI.md)
|
||||
<!-- /nav -->
|
||||
@@ -0,0 +1,54 @@
|
||||
# Conversation Log — Part V — Replay the Dynamic Idea Across Processes · Steps 35–38 (turns 63–67)
|
||||
|
||||
<!-- nav -->
|
||||
> [⬅ Previous: Part IV](04-part-IV.md) · [Index](../conv.md) · [Next: Part VI ➡](06-part-VI.md)
|
||||
>
|
||||
> 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** · [Part VI](06-part-VI.md)
|
||||
<!-- /nav -->
|
||||
|
||||
---
|
||||
|
||||
## [63] Student
|
||||
|
||||
> for when its due part 5?
|
||||
|
||||
**Tutor:** By the inferred mapping, Parts II–VIII all sit in the 22 Sep week, due 29 Sep, and Part IX was due 06 Oct — so a week behind. Gave the real dates instead (06 Oct "Now You Do It", 13 Oct Graded Exercise I) and a table of what each remaining part contributes, noting that Parts VI and VII are the ones the graded exercise leans on.
|
||||
|
||||
## [64] Student
|
||||
|
||||
> finish reading 35
|
||||
|
||||
**Tutor:** Read Step 35 (lines 2180–2218): same dynamic idea across processes — one permanent control mailbox per service, `TOPIC` arrives, the service then watches that directory directly. Re-posed the question without answering it.
|
||||
|
||||
## [65] Student
|
||||
|
||||
> now each service must be able to watch into others outbox if configured
|
||||
|
||||
**Tutor:** Half right — the mediator already watched another service's outbox with the old helper. Corrected to the real constraint from Step 36: a service must watch its control inbox **and** a changing set of sources at once, which one blocking `watch(topic, receiver)` cannot do. That is why `ConfigurableMediator` accepted only one `ROUTE`.
|
||||
|
||||
## [66] Student
|
||||
|
||||
> 1. the idea is manage access via key, register add a new folder to watch and create the key to access it, while key.cancel breaks the connection to a folder when we want it unsubscribe
|
||||
> 2. the queue has the advantage to keep the order of arrival
|
||||
|
||||
**Tutor:** (1) ✅ with the detail that `FileSubscriptions` keeps both maps, `name → key` and `key → name`, so an event can be traced back to its mailbox. (2) Order is real but secondary; the reasons are that `observe()` must stay responsive for every directory, and that `record IncomingMessage(String mailbox, Message message)` lets one loop decide control-vs-data and change its own subscriptions.
|
||||
|
||||
## [67] Student
|
||||
|
||||
> i have 5 ;-; (`find messageBoard-dynamic -name '*.msg' | wc -l` → 5)
|
||||
|
||||
## [67] Tutor — actions taken
|
||||
|
||||
- Listed the five files with their types: two `TEXT hello` in `consoleIn/outbox` (one stranded from before `Configure.java` ran), one `TEXT uryyb` in `rot13/outbox`, and two `TOPIC` Intents in `rot13/inbox` and `consoleOut/inbox`.
|
||||
|
||||
## [67] Tutor — reply
|
||||
|
||||
The count was right and the step's claim holds: **2 application publications** per flowing input (against 4 mediated), plus 2 one-time Intents and 1 line published before any subscription existed. Noted that `consoleOut/inbox` carries no payload at all now, and gave the ledger across Steps 18 / 27 / 38 (4 / 4 / 2 publications; 5 / 5 / 3 processes in the data path). Part V complete.
|
||||
|
||||
---
|
||||
|
||||
<!-- nav -->
|
||||
> [⬅ Previous: Part IV](04-part-IV.md) · [Index](../conv.md) · [Next: Part VI ➡](06-part-VI.md)
|
||||
>
|
||||
> 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** · [Part VI](06-part-VI.md)
|
||||
<!-- /nav -->
|
||||
@@ -0,0 +1,68 @@
|
||||
# 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 -->
|
||||
Reference in new issue
Block a user