`stop --at` handles "yesterday 10:15" wrongly

[MaxG87]

I noticed I had an unstopped frame from yesterday. I got lazy and did not want to type the full date. So I tried to do watson stop --at "yesterday 10:15" instead.

I would have expected the following behaviour:

• either stopping the frame, setting the stop time to 2022-03-16, 10:15
• or rejecting the time specification as invalid

What happened is that the frame was stopped today, 2022-03-17 at 10:15. I find it very unfortunate, that a part of the human readable timestamp is ignored.

Not sure what your opinion is on that, but I thought I might create a bug ticket.