Please describe the problem.
This is a followup on ?internal server error: unknown UUID on webapp. In that issue, webapps previous to 20130929 would crash with internal server error: unknown UUID. This was fixed at that date, but some problems remain, namely that the remote that is recognized on the commandline doesn't show up in the webapp.
markov is able to push to marcos, but not the reverse because markov is hidden behind a NAT. git annex sync seems to do the right thing accordingly on both ends (which is: marcos doesn't try to push to markov but markov pushes to marcos).
What steps will reproduce the problem?
See ?internal server error: unknown UUID on webapp. I didn't do any further changes other than upgrade git-annex on both ends.
What version of git-annex are you using? On what operating system?
marcos is now running Version: 4.20131105-g8efdc1a Build flags: Assistant Webapp Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash
markov is now running the wheezy backport, 4.20131002~bpo70+1.
Please provide any additional information below.
On marcos
Here's the output of git annex status on marcos:
anarcat@marcos:books$ git annex status
repository mode: direct
trusted repositories: 0
semitrusted repositories: 3
00000000-0000-0000-0000-000000000001 -- web
a75cbbf7-e055-423e-b375-443e0552c9e2 -- here (anarcat@marcos:/srv/books)
aa500f29-42d9-4777-ae02-4a2c3d47db44 -- anarcat@markov:~/books
untrusted repositories: 0
transfers in progress: none
available local disk space: 7.04 gigabytes (+1 megabyte reserved)
local annex keys: 736
local annex size: 3.92 gigabytes
annexed files in working tree: 721
size of annexed files in working tree: 3.92 gigabytes
bloom filter size: 16 mebibytes (0.1% full)
backend usage:
SHA256E: 1457
# End of transcript or log.
Here's a screenshot of the idle webapp on marcos:
You can clearly see that the webapp doesn't see the markov remote.
When markov transfers stuff, marcos sees the transfers happening, but marks it as going to the unknown remote:
Clicking on that link is what was previously triggering ?internal server error: unknown UUID on webapp but now yields a "Unknown remote" error.
On markov:
Here is a screenshot from markov that shows it knows about both repositories and seem to behave properly:
And here's the output of git annex status on markov:
anarcat@desktop008:books$ git annex status
repository mode: indirect
trusted repositories: 0
semitrusted repositories: 3
00000000-0000-0000-0000-000000000001 -- web
a75cbbf7-e055-423e-b375-443e0552c9e2 -- origin (anarcat@marcos:/srv/books)
aa500f29-42d9-4777-ae02-4a2c3d47db44 -- here (anarcat@markov:~/books)
untrusted repositories: 0
transfers in progress:
downloading Patrick K. O'Brien/Philip's Atlas of World History, Concise Edition (115)/Philip's Atlas of World History, Concise Edition - Patrick K. O'Brien.pdf from origin
available local disk space: 93.25 gigabytes (+1 megabyte reserved)
temporary directory size: 50.07 megabytes (clean up with git-annex unused)
local annex keys: 708
local annex size: 3.81 gigabytes
known annex keys: 721
known annex size: 3.92 gigabytes
bloom filter size: 16 mebibytes (0.1% full)
backend usage:
SHA256E: 1429
Finally, note that you sometimes see desktop008 above: it turns out I am running git annex from my workstation, which NFS-mounts the /home directory of markov into /srv/musique. --anarcat
Yesterday, I made the webapp register ssh remotes it creates. They then show up in the webapp when run in a repository where that ssh remote is not enabled.
You can also manually register a ssh remote. First set up the git remote
as usual. Then run git annex initremote type=git name=foo
location=$url.
marcov does not show up in the webapp because there is no configured git remote for it.
This is a slightly confusing corner of the webapp. The webapp will show repositories that do not have a configured remote, but it only does it for special remotes. ssh repos, being regular git remotes, don't currently show up in the webapp unless that repository is actually set up as a remote.
It should certainly not show it as "unknown"; it would be much better to use the full repo description here, since it does not have a remote name. (Unless the description is really long!)
I think you'll also get the "unknown uuid" screen even for a special remote that is not configured in the local repository. So that needs to be fixed.
Finally, it would probably be good for the webapp to show ssh repos that don't have remotes as existing, and let the user enter a ssh address to configure them. The problem with trying to do this is it actually has no idea that this is a ssh repo. It could just as easily be a local directory. The UI to configure it would be pretty elaborate.
i hit that thing again, utterly confused. it happens all the time with my laptop, which has access to my workstation, but not the other way around. so from the POV of my laptop, things make sense somehow, but from the workstation, the laptop doesn't show up at all, and when there's a transfer, it says it's into the unknown.
really confusing... surely there's a way to show the remote name at least...
Yesterday, I made the webapp register ssh remotes it creates.
They then show up in the webapp when run in a repository where that ssh remote is not enabled.
You can also manually register a ssh remote. First set up the git remote as usual. Then run
git annex initremote type=git name=foo location=$url.So, this bugs titular issue is fixed, but the issue of it displaying "unknown" rather than the remote description is not yet fixed. Will retitle this bug appropriately, and leave open until that gets fixed.