search

taskforcesh / issues

Taskforce.sh issues
6 stars 0 forks source link

Wrong timestamp in job options in taskforce.sh UI #133

Open TubbyStubby opened 1 year ago

TubbyStubby commented 1 year ago

image

Timestamp field is showing current time instead of when the job was created at and changes when you refresh the page. Although created column is correct.

manast commented 1 year ago

Are you sure about this? I cannot reproduce it, and basically, the options are just copied directly from the Job so it would be very strange unless there was a bug in BullMQ itself.

TubbyStubby commented 1 year ago

yup I can confirm that it is still happening. Another example taken just now - image

timestamp - 1689112273798 (Tue Jul 11 2023 21:51:13 GMT+0000, basically current time) Created At - a month ago (this is correct)

I checked the timestamp value in Redis its correct over there - 1685558910145 (Wed May 31 2023 18:48:30 GMT+0000) Although not a major issue for us right now, we came across this while we were debugging something and wanted to check job creation time.

manast commented 1 year ago

Can you go to Redis and fetch the job manually (HGETALL bull:myqueue:myjobid) to see if the timestamp is different than the one shown in Taskforce? it must be the same, we are really not touching the options before showing them. In that case, either the clock was wrong when the job was added, or there is a bug in BullMQ (although that sounds also quite unlikely).

manast commented 1 year ago

Actually, I am thinking that maybe we should not even store that timestamp in the options field as it becomes redundant since the job will get a timestamp field when it is added to Redis. That opts.timestamp is only useful for overriding the actual time, which I do not think it is a very useful scenario. What do you think?