fixed a bug that meant file order was not being saved correctly in sessions! sorry for the trouble! it also tries to guess if you are at the end of the current search, and if so, it will not do an auto re-fetch and will clear the page without producing the popup message the 'show some random pairs' button on the duplicates page is nicer-the 'did not find any pairs' notification is a popup rather than an annoying error dialog, and when there is nothing found, it also clears the page of thumbs. I will keep investigating here for more issues and trigger another sibling reset for everyone in the future this problem is likely the cause of some of our weird sibling issues on clients that processed certain repository updates extremely quickly. the bug was worse when this was on a local tag service via the manage siblings dialog. 'delete A->B') and added ('add A->C') in the same transaction, and in a heap of fun other situations besides, that mostly resulted in the newly added sibling being forgotten. I fixed a critical bug in tag sibling storage when a 'bad' tag's mapping is removed (e.g. There are new unit tests to make sure this won't happen again. I have fixed that, and I have fixed some issues it caused for IPFS. Some Linux users, in particular, it just broke for, due to a SQLite version issue. The new content-based processing tracking had a couple more issues. I will keep working here and will trigger a new sibling reprocess in the future just as 450 did so we can fix more PTR issues. 'delete A->B, then add A->C') in the same transaction. It was causing some tag siblings to be forgotten, particularly on local tag services, and particularly when a tag had a sibling removed and added (e.g. If you have a big database, it will take a minute to update this week. I had a great week cleaning code and fixing bugs.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |