You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running dx serve after initiating a new app logs a panic during compilation, and the status of the serve command is not clear.
Steps To Reproduce
Steps to reproduce the behavior:
Installed dx with cargo install dioxus-cli (0.5.4 on crates.io)
Created a new Dioxus application
> dx new
✔ 🤷 Which sub-template should be expanded? · Fullstack
🤷 Project Name: releasetool
✔ 🤷 Should the application use the Dioxus router? · true
✔ 🤷 How do you want to create CSS? · Vanilla
Panic after "Waiting to start building the project..."
-> A panic is usually not a good signal
Panic excerpt from log above:
\ ⚙️ Compiling dioxus-fullstack 0.5.0 (git+https://github.com/DioxusLabs/dioxus#44471f4918529fd15a143854984ce3b3d58c07a9\ ⚙️ Compiling releasetool 0.1.0 (path+file:///C:/a/releasetool)
build desktop done
- 💼 Waiting to start building the project... Dioxus @ v0.5.4 [03:39:29]
> Hot Reload Mode: RSX
> Watching: [ src, assets, Cargo.toml, Dioxus.toml ]
> Custom index.html: None
> Serve index.html on 404: True
> Build Features: [ server ]
> Build Profile: Debug
> Build took: 81333 millis
Listening on 127.0.0.1:8080
thread 'main' panicked at C:\Users\a\.cargo\git\checkouts\dioxus-1e619ce595d3799d\44471f4\packages\fullstack\src\serve_config.rs:111:37:
Failed to find index.html. Make sure the index_path is set correctly and the WASM application has been built.: Os { code: 2, kind: NotFound, message: "The system cannot find the file specified." }
stack backtrace:
It seemed like the build hung on the latest step: / ⚙️ Compiling releasetool 0.1.0 (I killed it after 10 minutes), but in hindsight, it might have completed compilation since this is the serve command 😅
I expected the status of serve to be clear, so I can act accordingly
It wasn't clear immediately whether something still was going on, or whether something had failed, or whether the build was actually completed
Whether still going on: The tool shows a long compilation log, not dissimilar to cargo build, but the latest "compiling" step is never shown to have completed. This makes sense with respect to all other "compiling" steps, but since this command (serve) is intended to run forever, it could be useful to also show whether the step was completed, not just made some form of progression
Something has failed: in the middle of the compilation log, something panicked, but the build went on: I wasn't sure when the program seemed to hang, whether that was causing it (or whether it actually could continue)
Whether the build completed: since this is the serve command, it may very well have succeeded regardless, but only in the middle of the wall of logs you will find this:
- 💼 Waiting to start building the project... Dioxus @ v0.5.4 [03:39:29]
> Hot Reload Mode: RSX
> Watching: [ src, assets, Cargo.toml, Dioxus.toml ]
> Custom index.html: None
> Serve index.html on 404: True
> Build Features: [ server ]
> Build Profile: Debug
> Build took: 81333 millis
Listening on 127.0.0.1:8080
Perhaps this should always stay at the top (or bottom) of the window, instead only show the log stream in the lower part of the window
I've only two screenshots which were both taken after rerunning the dx serve command a few times. They both show the tool output after running dx serve
A:
B:
Environment:
Dioxus version: 0.5.0
Rust version: rustc 1.75.0 (82e1608df 2023-12-21)
OS info: Windows 11 x64
App platform: fullstack
Questionnaire
I'm interested in fixing this myself but don't know where to start
I would like to fix and I have a solution
I don't have time to fix this right now, but maybe later
The text was updated successfully, but these errors were encountered:
The underlying bug is a duplicate of #2090 but the TUI is admittedly not very clear. However, we've totally revamped how do we the CLI and should be better and catching and relaying panics.
Problem
Running
dx serve
after initiating a new app logs a panic during compilation, and the status of theserve
command is not clear.Steps To Reproduce
Steps to reproduce the behavior:
dx
withcargo install dioxus-cli
(0.5.4 on crates.io)cd releasetool
dx serve
Output in gist (too long for github issue): https://gist.github.com/foresterre/3630ef11472c4fdc1523af2397f73818
Expected behavior
Observed effects:
Panic excerpt from log above:
/ ⚙️ Compiling releasetool 0.1.0
(I killed it after 10 minutes), but in hindsight, it might have completed compilation since this is theserve
command 😅serve
to be clear, so I can act accordinglycargo build
, but the latest "compiling" step is never shown to have completed. This makes sense with respect to all other "compiling" steps, but since this command (serve
) is intended to run forever, it could be useful to also show whether the step was completed, not just made some form of progressionserve
command, it may very well have succeeded regardless, but only in the middle of the wall of logs you will find this:Rerunning
dx serve
Rerunning the whole thing
screenshots
I've only two screenshots which were both taken after rerunning the
dx serve
command a few times. They both show the tool output after runningdx serve
A:
B:
Environment:
Questionnaire
The text was updated successfully, but these errors were encountered: