-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
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
add "save" button #594
Comments
also, a |
if the concern is, that this could end up in too frequent data transfer, perhaps an intelligent save that only saves services in which the data has changed could be envisioned. |
webbrowser
webserver
director-v2
|
Hi @sanderegg, from what I understood from PM1, this is not high priority for this sprint. I'll move it down in the PM2 board. Related work is the new messaging from the backend to the frontend and that is also needed for s4l lite release, so I'll add that to the PM2 board (if I find the issue). For the specifics of starting/stopping dynamic services, we should do more testing before if goes to production (I can help with that). |
Hi @elisabettai , I created an issue and is now linked here: |
@newton1985 can we close this one? |
@sanderegg - do I understand correctly that we're dropping the request for this feature in favor of selective start/stop? Also, stopping a service triggers data transfer to storage, correct? |
When you stop the service, the service's state (usually the workspace) is transferred. All ongoing pending output ports are also waited to finish before closing. |
Ok, great then yes close this one. |
@newton1985 as the owner of the issue you have the final say. |
Just wanted to chime in (since I followed this issue) that the new stop
feature is super cool!
…On Tue, Feb 28, 2023, 8:49 AM Sylvain ***@***.***> wrote:
@newton1985 <https://github.com/newton1985> as the owner of the issue you
have the final say.
Stopping a service triggers full saving of the service, yes.
—
Reply to this email directly, view it on GitHub
<#594 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGVUURQEUDV5FB6OXJMEPRDWZWUYJANCNFSM5NWZRA6A>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Long story short
It would be great to have a save button that allows data to be written to S3 without having to close the study. This would also provide users with quick feedback in case there is some issue communicating with storage.
Expected behaviour
I expect that clicking this button would cause the study data to be stored to S3, but without interrupting use of the study.
Actual behaviour
There is no save button (yet).
Steps to reproduce
n/a
Note: your environment was attached but will not be displayed
The text was updated successfully, but these errors were encountered: