Ok, here's what I'm getting from doing a backup-list with LATEST Unsorted
Mon, 27 Jun 2016 22:13:02 GMT Wed, 29 Jun 2016 09:45:30 GMT Fri, 01 Jul 2016 10:39:30 GMT Sat, 02 Jul 2016 09:29:31 GMT Sun, 03 Jul 2016 09:34:06 GMT Mon, 04 Jul 2016 09:32:58 GMT Tue, 05 Jul 2016 09:36:50 GMT Sorted Fri, 01 Jul 2016 10:39:30 GMT Mon, 04 Jul 2016 09:32:58 GMT Mon, 27 Jun 2016 22:13:02 GMT Sat, 02 Jul 2016 09:29:31 GMT Sun, 03 Jul 2016 09:34:06 GMT Tue, 05 Jul 2016 09:36:50 GMT Wed, 29 Jun 2016 09:45:30 GMT Looks like the sort is doing something unexpected. The sort result out of order. On Monday, June 27, 2016 at 10:42:47 AM UTC-7, Daniel Farina wrote: > > On Mon, Jun 27, 2016 at 10:13 AM <[email protected] <javascript:>> > wrote: > >> I've come across a problem and I don't know if it's a bug or not. I'm >> using wal-e version 0.9.1. >> >> So my latest seems to be on the 27th of June but when I do a backup fetch >> LATEST, it starts restoring the tar partitions for >> base_0000000200000A1700000051_00000040 >> which the command above shows as Jun 15th. So the question is why is it not >> restoring the version for the 27th, but restoring the version from the 15th? >> >> >> My storage is azure blob storage. >> > That's strange. The two code paths (for listing and finding LATEST) are > the same. Here is the code in base.py: > > elif query == 'LATEST': > all_backups = list(iter(self)) > > if not all_backups: > return > > assert len(all_backups) > 0 > > all_backups.sort(key=lambda bi: bi.last_modified) > yield all_backups[-1] > > Perhaps you can instrument the code to see if anything strange is going on > there? > -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
