Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -332,7 +332,7 @@
Check which JVM was chosen, in [filename]`target/devloop/daemon.log`. On a stock JDK, structural changes can't be hot-swapped at all.

The application won't start, or the daemon seems stuck::
The `start` command names the reason, and prints the tail of [filename]`target/devloop/app.log`. If the daemon itself is wedged, run `.vaadin/vaadin-dev shutdown`, and the next command starts a fresh one.
The `start` command names the reason, and prints the tail of [filename]`target/devloop/app.log`. If the daemon itself is wedged, `shutdown` can't reach it either: it exits `70` and names the pid to kill. Kill that pid, then `start` spawns a fresh daemon.

Check failure on line 335 in articles/building-apps/agentic-development/dev-loop-tutorial.adoc

View workflow job for this annotation

GitHub Actions / lint

[vale] reported by reviewdog 🐶 [Vale.Spelling] Use 'PID' instead of 'pid'. Raw Output: {"message":"[Vale.Spelling] Use 'PID' instead of 'pid'.","location":{"path":"articles/building-apps/agentic-development/dev-loop-tutorial.adoc","range":{"start":{"line":335,"column":215},"end":{"line":335,"column":218}}},"severity":"ERROR","code":{"value":"Vale.Spelling"}}

Check warning on line 335 in articles/building-apps/agentic-development/dev-loop-tutorial.adoc

View workflow job for this annotation

GitHub Actions / lint

[vale] reported by reviewdog 🐶 [Vaadin.Terms] Prefer 'stop', 'exit', 'cancel', or 'end' over 'Kill'. Raw Output: {"message":"[Vaadin.Terms] Prefer 'stop', 'exit', 'cancel', or 'end' over 'Kill'.","location":{"path":"articles/building-apps/agentic-development/dev-loop-tutorial.adoc","range":{"start":{"line":335,"column":205},"end":{"line":335,"column":209}}},"severity":"WARNING","code":{"value":"Vaadin.Terms"}}

Check warning on line 335 in articles/building-apps/agentic-development/dev-loop-tutorial.adoc

View workflow job for this annotation

GitHub Actions / lint

[vale] reported by reviewdog 🐶 [Vaadin.Terms] Prefer 'stop', 'exit', 'cancel', or 'end' over 'kill'. Raw Output: {"message":"[Vaadin.Terms] Prefer 'stop', 'exit', 'cancel', or 'end' over 'kill'.","location":{"path":"articles/building-apps/agentic-development/dev-loop-tutorial.adoc","range":{"start":{"line":335,"column":199},"end":{"line":335,"column":203}}},"severity":"WARNING","code":{"value":"Vaadin.Terms"}}

Check failure on line 335 in articles/building-apps/agentic-development/dev-loop-tutorial.adoc

View workflow job for this annotation

GitHub Actions / lint

[vale] reported by reviewdog 🐶 [Vale.Spelling] Use 'PID' instead of 'pid'. Raw Output: {"message":"[Vale.Spelling] Use 'PID' instead of 'pid'.","location":{"path":"articles/building-apps/agentic-development/dev-loop-tutorial.adoc","range":{"start":{"line":335,"column":192},"end":{"line":335,"column":195}}},"severity":"ERROR","code":{"value":"Vale.Spelling"}}

For everything else, see <<{articles}/flow/configuration/live-reload/dev-loop-cli#troubleshooting,Troubleshooting>> in the reference, or the [filename]`reference.md` installed next to the skill, which documents every outcome the dev loop can report.

Expand Down
4 changes: 2 additions & 2 deletions articles/flow/configuration/live-reload/dev-loop-cli.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,7 @@
Makes the edits on disk live. Blocks until the outcome is terminal. `--no-restart` stops after the compile gate, which is useful when you want compile errors without touching the running application.

`stop` / `restart [--jvm-args "<flags>"]` / `shutdown`::
Stop the application; stop and start it again; or stop the daemon along with the application it owns. `--jvm-args` adds flags such as `-Xmx2g` or `--add-exports` to the application JVM -- see <<#configuration,Configuration>>. Use `restart` after changing anything the running JVM can't absorb, such as [filename]`package.json` or [filename]`vite.config.ts`. Use `shutdown` if the daemon seems wedged -- the next command starts a fresh one.
Stop the application; stop and start it again; or stop the daemon along with the application it owns. `--jvm-args` adds flags such as `-Xmx2g` or `--add-exports` to the application JVM -- see <<#configuration,Configuration>>. Use `restart` after changing anything the running JVM can't absorb, such as [filename]`package.json` or [filename]`vite.config.ts`. `shutdown` stops a daemon that's running normally; one that doesn't answer at all doesn't respond to it either -- see <<#troubleshooting,Troubleshooting>>.

`--help`::
The full usage text, including every option and environment variable. Answers without starting a daemon, which is what makes it useful when the loop isn't working.
Expand Down Expand Up @@ -342,7 +342,7 @@
Check the daemon log for which JVM was chosen. Without a JetBrains Runtime, structural changes can't be hot-swapped at all. See <<hotswap-agent#,Live Reload with HotswapAgent>> for how to install one.

The daemon seems wedged::
Run `shutdown`. Any later command starts a fresh daemon.
A killed daemon leaves a stale handshake, and every command but `status`/`ping` reaps it and spawns a fresh daemon without being asked. A daemon that's still running but not answering doesn't get reaped that way -- it still holds the daemon lock, so a fresh daemon can't come up beside it. Every command, `shutdown` included, waits a few seconds and then exits `70`, naming the pid to kill. Kill it yourself, then `start` spawns a fresh daemon.

Check warning on line 345 in articles/flow/configuration/live-reload/dev-loop-cli.adoc

View workflow job for this annotation

GitHub Actions / lint

[vale] reported by reviewdog 🐶 [Vaadin.Terms] Prefer 'stop', 'exit', 'cancel', or 'end' over 'Kill'. Raw Output: {"message":"[Vaadin.Terms] Prefer 'stop', 'exit', 'cancel', or 'end' over 'Kill'.","location":{"path":"articles/flow/configuration/live-reload/dev-loop-cli.adoc","range":{"start":{"line":345,"column":392},"end":{"line":345,"column":396}}},"severity":"WARNING","code":{"value":"Vaadin.Terms"}}

Check warning on line 345 in articles/flow/configuration/live-reload/dev-loop-cli.adoc

View workflow job for this annotation

GitHub Actions / lint

[vale] reported by reviewdog 🐶 [Vaadin.Terms] Prefer 'stop', 'exit', 'cancel', or 'end' over 'kill'. Raw Output: {"message":"[Vaadin.Terms] Prefer 'stop', 'exit', 'cancel', or 'end' over 'kill'.","location":{"path":"articles/flow/configuration/live-reload/dev-loop-cli.adoc","range":{"start":{"line":345,"column":386},"end":{"line":345,"column":390}}},"severity":"WARNING","code":{"value":"Vaadin.Terms"}}

Check failure on line 345 in articles/flow/configuration/live-reload/dev-loop-cli.adoc

View workflow job for this annotation

GitHub Actions / lint

[vale] reported by reviewdog 🐶 [Vale.Spelling] Use 'PID' instead of 'pid'. Raw Output: {"message":"[Vale.Spelling] Use 'PID' instead of 'pid'.","location":{"path":"articles/flow/configuration/live-reload/dev-loop-cli.adoc","range":{"start":{"line":345,"column":379},"end":{"line":345,"column":382}}},"severity":"ERROR","code":{"value":"Vale.Spelling"}}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💬 The wedged-daemon entry opens with two sentences of mechanism and hides the fix at the end.

The reader arrives at “The daemon seems wedged” with a hung loop and needs the action. The entry starts with a different case (a killed daemon) that does self-heal: “every command but status/ping reaps it and spawns a fresh daemon without being asked.” Read as the answer, that sends the reader off re-running commands and waiting.

Suggested order, action first:

Every command, shutdown included, waits a few seconds and then exits 70, naming the pid of the daemon. Kill that pid, then start spawns a fresh daemon. shutdown can't help: a daemon that's running but not answering still holds the daemon lock, so no fresh daemon can come up beside it. (A daemon that was killed is different — it leaves a stale record that the next command clears by itself.)

dev-loop-cli.adoc:345 · clarity



== Further Detail
Expand Down
Loading