We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start a run with one replica using dstack apply:
dstack apply
Scale the run to two replicas using the scaling script:
python scale_run.py --project <project> --run-name <run-name> --token <token> --replicas 2
Observe the following:
No logs to display.
dstack stats
Scale the run back to one replica using the scaling script:
python scale_run.py --project <project> --run-name <run-name> --token <token> --replicas 1
Scale the run back to two replicas again:
Terminated
dstack ps
running
Use stop button on the run page and observe that it doesn't do anything.
Go to runs list, choose run and use stop button. Observe that it works.
0.18.42
The text was updated successfully, but these errors were encountered:
@movchan74, thanks for reporting these bugs. You can track the progress of the fixes in sub-issues.
Sorry, something went wrong.
No branches or pull requests
Steps to reproduce
Start a run with one replica using
dstack apply
:Scale the run to two replicas using the scaling script:
Observe the following:
No logs to display.
).dstack stats
confirms two replicas are running.Scale the run back to one replica using the scaling script:
Observe the following:
No logs to display.
).dstack stats
still shows two replicas running, though only one should remain.Scale the run back to two replicas again:
Observe the following:
No logs to display.
).dstack stats
shows two replicas running.Terminated
, whiledstack ps
correctly displays its status asrunning
.Use stop button on the run page and observe that it doesn't do anything.
Go to runs list, choose run and use stop button. Observe that it works.
Actual behaviour
dstack stats
does not update correctly when scaling down to one replica (it still shows two).Terminated
when scaling back up.Expected behaviour
dstack stats
should correctly reflect the actual number of running replicas after scaling down.dstack version
0.18.42
Server logs
Additional information
dstack ps
correctly shows the replica status, but the Sky UI does not match.The text was updated successfully, but these errors were encountered: