Shows times in the future

[cyperbg]

For some reason Chia Plot Status shows times in the future.
I am plotting with madMAx43v3r/chia-plotter and using this command for logs: 2>&1 | tee /home/$(whoami)/.chia/mainnet/plotter/chia-plotter-$(uuid).log;

Any idea why?

[grayfallstown]

What field is in the future? Started, Finished or ETA?
Can you please post a screenshot and the log to that entry? I also need the file created at and file last modified at values from that file on your filesystem.

[milkolori]

I have the same issue. I am also using madMAx for plotting, and in my case I have a single log file that contains multiple plots created in few days. Initily when I start the process everithing looks ok, until the next day, maybe something goes wrong when the day is changed. I am attaching a screenshot, you can see in Ubuntu menu bar that the current date is June 17 8:42 AM, but the most top row in the log shows Jun 18th for start date.

[grayfallstown]

Ok, I will take a closer look.

What it does is it takes the log file creation date as the start date of the first log. Each log after that takes the start date of the one before and adds the total plot creation times of the log before.

Do the Total Time values in your Chia Plot Status table all make sense?

[cyperbg]

What field is in the future? Started, Finished or ETA?
Can you please post a screenshot and the log to that entry? I also need the file created at and file last modified at values from that file on your filesystem.

Started and Finished are in the future.
ETA seems fine.
Total time is also fine.
Runtime is also wrong, it shows merely seconds, when it should be minutes. And it changes from 7 seconds to 37 seconds, then back to 7 seconds.

Screenshots: https://imgur.com/a/S8EsVq3

[grayfallstown]

Runtime is also wrong, it shows merely seconds, when it should be minutes.
And it changes from 7 seconds to 37 seconds, then back to 7 seconds.

Runtime is derived from start date and current time. If the start date is in the future, the runtime calculation turns negative which will mess up what you see in the GUI.
It will not show anything negative in the gui as the runtime was never supposed to be negative.
Lets say the calculated runtime is -2m 07s. It will only show the seconds part, as as the minutes part is not bigger than 0. It is lower than 0. When it refreshes 30s later, runtime will be -1m 37s. Again, it will not show the minus or the minutes, so 37s. That is why it jumps.

The problem is not the runtime calculation. The problem is the start date being in the future.

The thing is, I take the log file creation timestamp and add the total time taken of each finished log to get the started date of the current plot. I do however omit the fractions. So if the total time is 5323.3s each, I will only use the 5323s in my calculations. Because of that after 24h of plotting, the start date should be a few seconds in the past which no one would notice. Not over an hour into the future.

If the chia-plotter log had timestamps, it would solve this problem easily, as I could just rely on the logs to get the start date and finish date. Once madMAx43v3r/chia-plotter#455 is merged this problem solves it self.

I do not understand why the time ends up in the future yet.

[grayfallstown]

I cannot reproduce it yet.
Are you guys using the finaldir parameter to move the plot to the dest dir?

[milkolori]

In my case I am using different dirs for temp1, temp2 and dest, but the the final dir is sub directory of the temp dir, if you rely on the paths that may be an issue

chia_plot -n -1 -t $TEMP_1 -2 $TEMP_2 -d $DEST -f $FARMER_KEY -p $POOL_KEY -r $THREADS > $LOG_FILE 2>&1