Open Chriscbr opened 4 months ago
@skyrpex should the Wing Console call stop()
on the simulator and wait for it to finish when the user presses Ctrl + C so that the simulation state is saved?
This may fix the problem where containers seem to keep running after the Wing Console is stopped
@skyrpex should the Wing Console call
stop()
on the simulator and wait for it to finish when the user presses Ctrl + C so that the simulation state is saved?
Yeah, will check how the console is handling the interrupt signal...
Hi,
This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
I tried this:
I wrote an app that has some state (a bucket and counter):
Then I ran
wing it
in my terminal, and called the function a few times, which increased the counter and added files to the bucket.I pressed ctrl + C in my terminal to stop the simulation.
Later, I ran
wing it
again to start the simulation again.This happened:
The counter is back to 0 and the bucket is empty
I expected this:
The last state I had for the simulator was saved
Is there a workaround?
No response
Anything else?
No response
Wing Version
0.59.12
Node.js Version
20.11.0
Platform(s)
MacOS
Community Notes