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
This issue is a note for the future. This should be backlogged for now...
For now, if we have a deployment with the same name on the server as in ExternalStorage, we just show the one we have on disk that has been downloaded. This is to prevent showing inconsistent state of the download situation.
In the future, we should have a Deployments object that can reflect that there is some subset of files still needing to be downloaded from the server.
If you want to see the metadata of a deployment on the server that has been updated with the same name, just delete the deployment on the device, and it should update accordingly.
The text was updated successfully, but these errors were encountered:
This issue is a note for the future. This should be backlogged for now...
For now, if we have a deployment with the same name on the server as in ExternalStorage, we just show the one we have on disk that has been downloaded. This is to prevent showing inconsistent state of the download situation.
In the future, we should have a Deployments object that can reflect that there is some subset of files still needing to be downloaded from the server.
If you want to see the metadata of a deployment on the server that has been updated with the same name, just delete the deployment on the device, and it should update accordingly.
The text was updated successfully, but these errors were encountered: