Allow selecting seconds/milliseconds for "Start" and "End" in Task list |
||||
Issue descriptionUse case: cancel all tasks schedule quickly one after another, but one specific task. Using start and end with second/millisecond precision one can select all tasks prior to a given one and cancel then, then do the same for tasks after. With just minute-precision there could be dozens of tasks that were scheduled during a given minute thus, the user has to cancel dozen of tasks manually. Example: http://screen/EWLMwgpXvBV (sorry, internal only) P.S. To avoid adding more clicks into the time selector UI, one can make the field editable to allow entering values manually. OTH, this will require adding another button to invoke the time picker. P.P.S. To allow cancelling tasks with micro-second precision, one would also need to have a way to see micro-second precision creation time of the task. Perhaps this info can be added as a tooltip to all timestamps in the UI. If this is too hard, just being able to use seconds would already be a big help.
,
Jul 30
,
Jul 30
It would be very hard to use low resolution because of the way the DB is setup. As a workaround, you could just cancel everything, then retry the task you wanted? Would this be good enough? What is the use case exactly? This feels like a one-off.
,
Jul 31
This was one-off, but may come in handy for others. P3 sounds about right.
,
Jul 31
Second-level precision is already possible (not pretty, but possible): Simply change the st and et params in the URL: https://chromium-swarm.appspot.com/tasklist?c=name&c=state&c=created_ts&c=bot&c=modified_ts&c=duration&et=1532952309000&l=100&s=created_ts%3Adesc&st=1532952307000 The magic number is just milli seconds since epoch. I like to use the JS console: var d = new Date([Time string or arguments]) d.getTime() I recall explicitly locking the times to the nearest second because the backend doesn't really differentiate on sub-second timing, as maruel@ mentioned in #c3 If that's good enough, feel free to close the bug. Else we can consider adding in an actual UI widget for it.
,
Jul 31
That's good enough for me. Thanks for the recipe. |
||||
►
Sign in to add a comment |
||||
Comment 1 by serg...@chromium.org
, Jul 30