Test case for cron-expression: "at 02:20 on sunday"

[paha77]

See: #440 (comment)

[deitch]

Great, thanks. Please sign your commits with git commit -s

[paha77]

Great, thanks. Please sign your commits with git commit -s

✅

[deitch]

Kicked off CI, hopefully it goes red, and then we can try to solve.

[deitch]

And it does pass. It should have turned red. Which means, at least , that the lower-level processing is working correctly.

How can we recreate it?

[paha77]

Is it possible to turn on debugging / logging?

I have

DB_DUMP_DEBUG: true

in my docker-compose.yml but there's nothing in the logs.

[deitch]

Try DB_DEBUG=true. See the var in configuration doc.

Also needs rebase, but shouldn't affect anything.

[deitch]

Anything interesting out of debugging? I really would like to see this replicated and fixed.

[paha77]

DB_DEBUG=true

With this option I get this message after starting the container:

backup-mysql-1  | time="2025-05-29T04:15:22Z" level=debug msg="starting dump"

Of course I have to wait until Sunday to see if anything happens and is written in the log.

[deitch]

Here is my trick for things like this. I spin up a VM, change the clock, and run the program there. Make it Sunday at 0150 inside the VM. Just be sure to disable ntpd so it doesn't change it back on you.

[paha77]

Quite strange, it seems to be working now, the backup was made at 2:00 on Sunday, sorry. You can close the PR or if you'd like to habe a further test case, you can merge it. Thank you again for your support.

[deitch]

It isn't the first strange and unexplained thing I have seen in software, I am sure it won't be the last. 😁

I will merge it in. The extra test always is good.