Fix 'undefineds' time unit for long running cells

[isofew]

Hi, I found that when a cell runs for more than 1000 seconds, the displayed time unit will become 'undefineds'. (See the following screenshot)

It seems to be due to an index error in frontend/components/RunArea.js I fixed the loop index bound so it won't further increase when already at the largest time unit (seconds)

[fonsp]

Yay! Thank you for debugging and fixing this yourself! I guess it was trying show 1.2 kilosecond :)

And cool to hear that you are doing long running computations with Pluto! Maybe you would like to comment on your experience here? #116 or #229

[isofew]

Yay! Thank you for debugging and fixing this yourself! I guess it was trying show 1.2 kilosecond :)

And cool to hear that you are doing long running computations with Pluto! Maybe you would like to comment on your experience here? #116 or #229

Thanks for the reference, I'll check out the threads and see how can I contribute there.

By the way I also noticed another bug related to long running cells: when the cell finished, the bar on its left is still in a running state and the time measurement won't display. I know it's finished because all dependent cells returned and I can interact normally, see example below:

Do you have some idea what the problem might be?

[fonsp]

Is this after your fix?

[isofew]

Is this after your fix?

No it's before the fix.

Ah it's most likely a connection issue, I saw this error message in the terminal:

_ Warning: Reading WebSocket client stream failed for unknown reason:
_   exception =
_    KeyError: key Symbol("1ndjz3w") not found
_    Stacktrace:
_     [1] getindex at ./dict.jl:467 [inlined]
_     [2] putclientupdates! at /home/zhixing/julia/depot/packages/Pluto/upwxH/src/webserver/PutUpdates.jl:59 [inlined]
...

So during the many minutes of running, my browser briefly disconnected with the server (that's not running locally) with the message gone missing?