mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

display new empty repos in maxsize table

Browse source 
A new repo that has no location log info yet, but has an entry in
uuid.log has 0 size, so make RepoSize aware of that.

Note that a new repo that does not yet appear in uuid.log will still not
be displayed.

When a remote is added but not synced with yet, it has no uuid.log
entry. If git-annex maxsize is used to configure that remote, it needs
to appear in the maxsize table, and the change to Command.MaxSize takes
care of that.
This commit is contained in:
Joey Hess 2024-08-22 07:03:22 -04:00
parent a643699b7b
commit 3fe67744b1
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 23 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

15
doc/todo/git-annex_proxies.mdwn
View file

@ -35,21 +35,6 @@ Planned schedule of work:
* `git-annex assist --rebalance` of `balanced=foo:2`
sometimes needs several runs to stabalize.
* Bug:
git init foo
cd foo
git-annex init
git commit --allow-empty -m foo
cd ..
git clone foo bar
cd foo
git remote add bar ../bar
git-annex maxsize bar
Now `git-annex maxsize` will omit displaying bar. This is because the
DB got written without it.
* Concurrency issues with RepoSizes calculation and balanced content:
* What if 2 concurrent threads are considering sending two different