clockworklabs / clockworklabs/SpacetimeDB
Consider running dotnet publish without quiet mode
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Here the dotnet publish command is ran in quiet mode, which makes it harder to see when any problem occurs in the process. (in my case it was a miserably slow download speed for wasi-sdk.20.tar.gz file)
I think the output of dotnet publish shouldn't be hidden at all, or maybe provide a --verbose flag to show it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at crates/cli/src/tasks/csharp.rs:60 and inspect how the dotnet publish command is invoked and its output is suppressed. Determine whether the intended completion is always-visible publish output or a verbosity option, then verify that publish failures and slow downloads provide useful output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100