fix(scan): fix clocked and scheduled scan not working

[psyray]

Fixes #181

Periodic and schedule scan are now working again.

There was also an UTC time problem.
So the timezone offset is gathered from the user browser and start datetime of the scan are send to beat in UTC if there's an interval

Tested and working

Thanks to @yogeshojha for his work on yogeshojha/rengine#1313 and yogeshojha/rengine#1328

[0b3ud]

I have tested the features mentioned above

• Both periodic scan and scheduled scan seem to work for me

• The scans always ran at the expected time

Only 'one issue' I've noticed and that is the time shown is in UTC but maybe it is normal :

[AnonymousWP]

I have tested the features mentioned above

• Both periodic scan and scheduled scan seem to work for me
• The scans always ran at the expected time

Only 'one issue' I've noticed and that is the time shown is in UTC but maybe it is normal :

I think we should be able to fetch the system date/time from the system quite easily.

[psyray]

I have tested the features mentioned above

• Both periodic scan and scheduled scan seem to work for me
• The scans always ran at the expected time

Only 'one issue' I've noticed and that is the time shown is in UTC but maybe it is normal :

I think we should be able to fetch the system date/time from the system quite easily.

I've already did this but it's not reliable as the UI could be in one timezone and the celery in another (for distributed configuration).
So we must rely on the UTC time instead of the local time of the UI

[AnonymousWP]

I have tested the features mentioned above

• Both periodic scan and scheduled scan seem to work for me
• The scans always ran at the expected time

Only 'one issue' I've noticed and that is the time shown is in UTC but maybe it is normal :

I think we should be able to fetch the system date/time from the system quite easily.

I've already did this but it's not reliable as the UI could be in one timezone and the celery in another (for distributed configuration). So we must rely on the UTC time instead of the local time of the UI

Hmm, maybe we should set the time on container level then. Also, if we're not going to implement it at all, then at least mention it's UTC, like so:

10:27pm (UTC)

Can just be hardcoded.

[psyray]

I have tested the features mentioned above

• Both periodic scan and scheduled scan seem to work for me
• The scans always ran at the expected time

Only 'one issue' I've noticed and that is the time shown is in UTC but maybe it is normal :

I think we should be able to fetch the system date/time from the system quite easily.

I've already did this but it's not reliable as the UI could be in one timezone and the celery in another (for distributed configuration). So we must rely on the UTC time instead of the local time of the UI

Hmm, maybe we should set the time on container level then.

Not possible we will have problem with Celery in the future, for sure.

Also, if we're not going to implement it at all, then at least mention it's UTC, like so:

10:27pm (UTC)

Can just be hardcoded.

I will do that

[psyray]

Done

[AnonymousWP]

Approving & merging for now, although I can hardly imagine there's no way of doing this in a practical way. Perhaps in the future we'll come up with a solution.