swalkinshaw
commented
2 years ago This is a good point... it's tough to have a nice UI while also displaying all relevant info. And in this case pip's normal output is not very nice, so trellis-cli just hides it behind a spinner. I'm not sure how possible it is to make a custom UI since I'm guessing pip doesn't provide any programmatic output like that.
So I think there's three options:
- show nothing until complete (what it does now)
- show the current output under a spinner
- show the current output after some threshold? say 1 minute to literally match up with the text
strarsis
Terms
Summary
The
Installing dependencies (this can take a minute...)step can take quite a while apparently (with slower internet connections).Motivation
Why are we doing this?
Knowing the progress would be very helpful, in order to detect stalling. The additional note
this can take a minuteis colloquial, but for low internet bandwidths the process takes significantly longer than just a minute.What use cases does it support?
Workstations with slow internet connection (or I/O, CPU, anything that may slow down the installation).
What is the expected outcome?
The dev knows how much time this
trellis initstep takes, whether something stalled, whether the internet connection is fast enough.Potential conflicts / foreseeable issues
None really. If the detailed progress really bothers, a CLI switch could be used to turn this on.
Additional Context
As
pipis used internally, showing its progress (how many dependencies installed of how many need to be installed, download progress, installation progress) or some part of it should be sufficient.