Release: 2.1.0.110 (Canary) 2025-02-28

[kenkendk]

@jberry02

Clicking on “Repair” results in the message:
“”"
The remote files are newer (3/12/2025 6:00:00 AM) than the local
database (3/12/2025 2:00:00 AM), this is likely because the
database is outdated. Consider deleting the local database and
run the repair operation again.
“”"

Thanks for reporting. There is a switch in 2.1.0.111 called --repair-ignore-outdated-database that will make the check become a warning. The underlying issue was not fixed.

@ts678

Remote file times are 4 hours ahead, likely due to UTC. Local 2:30 isn’t here yet.
I’m not sure what time zone the unit tests run in, e.g. UTC+1 might not see this…

Exactly. I am on UTC+1 so I do not see the issue, and our CI is running on UTC so no help there either.

I have made a fix for the issue you reported on this.

@ts678

I’m not certain about this (need developer help), but the Canary and Beta releases lack some of the urgent fixes that led to 2.1.0.5 Stable. Not sure if that will be fixed.

The canary builds fixed the problems that discovered in 2.1.0.4 before they were known, so there is no need to merge these fixes into the canary builds. For the beta builds I have currently set it up so anyone on experimental or beta is seeing the 2.1.0.5 release.

@ts678

First stuck tab remains inconsistent in status data:

Did you see if this state was caused by incorrect data reported to the browser or a bug in the UI code? Usually the stuck state is fixed with a reload of the page, but I have not yet figured out if the problem is that the server sends the wrong state or if the frontend is showing it wrong.

@jberry02

Maybe the issue is with displaying the new UI when remote? Or maybe only when remote and prompting for the password?

That would explain why I have not been able to reproduce it. If you log out and try to open the browser, can you look in the developer tools to see if there is some kind of error message?

@Taomyn

Will the live log come back or has it moved elsewhere?

Yes, that will be back. I have registered [an issue for it].(Support "live log" area · Issue #136 · duplicati/ngclient · GitHub)

@Taomyn

Could “today” and “yesterday” be used again for “Last successful backup”, and the “Next schedule run”?

Yes, thanks. I have also registered an issue for that.

@jberry02

Side question - with the new UI how does one get to the “live log”?

I missed that part. It will be added soon.

@jberry02

the new interface needed more clarity as to what value should be set

Thanks for reporting. I have added an issue for that.

@webipsum

In the settings, there is no Brazilian Portuguese language in the drop-down menu. Is there a plan to include it?

Yes. I need to get the whole Transifex translation store set up, so we can get translations for all the languages that are currently supported in Duplicati.

@webipsum

I have 4 backups configured. When I run a backup, the date/time does not appear automatically. I need to refresh your browser to see the date/time of the backup performed.

Thanks for reporting. I have created an issue.

@Taomyn

Do scheduled jobs override any other running non-job tasks?

Anything that is running from the WebUI is put into the runner queue and processed one at a time. So as long as the repair job is running it will prevent scheduled backups from running, but they will be queued and run as soon as the repair job is finished.

@ts678

For some reason status bar reverted to just Loading

Ok, I have created an issue for that.

@ts678

This proves that the Repair refusal doesn’t go away when local time catches UTC.

This should be fixed in 2.1.0.112.

@ts678

But if Recreate hadn’t finished, you wouldn’t have a database to give complaints.

Good point. But even a recreate should create logs in the database logs?
Since it is also not showing the backup attempt (which is logged elsewhere) I am thinking that something is preventing the display of messages from the local database.
Do you see any errors from the Developer tools? Can you look in the database in the table “Operation” or “LogData” to see if anything is there?

@Taomyn

The operation Backup has failed with error: Detected 306 file(s) in FilesetEntry without corresponding FileLookup entry DatabaseInconsistencyException: Detected 306 file(s) in FilesetEntry without corresponding FileLookup entry

I don’t recall seeing that problem before. It means that some entries are listed but there is no path to the entries, which is fairly problematic. Not sure I can debug this properly, but if you can create a bugreport database, then I can see if there is some pattern that I can find that explains it.