I recently got into some trouble with bad code. I created a loop using for i in range(1000): to paginate JSON results, but forgot to increment a variable, so it ran 1000 times. Each iteration was logging 1000 features, resulting in 1000 websocket messages.
This was just a dry run, but my browser became unresponsive, so I restarted it and then noticed the websockets were still flying... with no way for me to cancel the job.
I think generally users should be able to see in the UI where jobs/dry runs associated with their account are running and be able to cancel them easily.
I recently got into some trouble with bad code. I created a loop using
for i in range(1000):to paginate JSON results, but forgot to increment a variable, so it ran 1000 times. Each iteration was logging 1000 features, resulting in 1000 websocket messages.This was just a dry run, but my browser became unresponsive, so I restarted it and then noticed the websockets were still flying... with no way for me to cancel the job.
I think generally users should be able to see in the UI where jobs/dry runs associated with their account are running and be able to cancel them easily.