![]() ![]() Our 'Pillow' image-loading library uses libwebp, and they rolled out an update themselves this week. You probably noticed your chrome/firefox updated this week, which was fixing it. I hope to have this done in the next few weeks.Ī remote execution (very bad) vulnerability was recently discovered in the main webp library. My aim is to get rid of the lagtastic 'move files now' entirely so no file migration blocks other use. The next step here is to implement automatic background file migration for always-on checking so we can have these rules apply without regular user intervention. If you set a tight limit and then import many files, it will blow over that limit (at least until you open up migrate database and hit 'move files now' again to rebalance). ![]() Also, it won't yet enforce these rules outside of the 'move files now' button. It isn't perfectly precise, so if your space is tight, give it a little padding (although remember that drives should be at least 10% free space anyway!). The idea here is that if you have a 2TB drive and a 500GB one, then rather than having to keep playing with the weights to ensure the 500GB doesn't get too full, you can now set the 500GB location with a 450GB limit and hydrus will allocate that space and no more. So, in migrate database, if you have multiple locations set for your files, you can now, for all but one, set a 'max size', limiting the total mass of files it will store. There is a security fix in this release, and users who run from source will want to rebuild their venvs this week. File storage locations can now have max size limits. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |