Commit graph

42268 commits

Author SHA1 Message Date
pat
901c89b287 2022-09-10 21:07:30 +00:00
pat
cc97119880 2022-09-10 21:04:30 +00:00
pat
244827ebc6 2022-09-10 21:00:18 +00:00
pat
7edb7cd491 2022-09-10 20:59:30 +00:00
pat
12a8af17bf 2022-09-10 20:15:52 +00:00
pat
d104ac5a87 2022-09-10 20:14:51 +00:00
jgoerzen
e92dfbce72 Added a comment 2022-09-10 00:38:17 +00:00
jgoerzen
0d265841d4 Added a comment 2022-09-10 00:37:45 +00:00
jgoerzen
29a80ceed1 2022-09-10 00:37:09 +00:00
jgoerzen
aee5e0c6fc Added a comment 2022-09-10 00:32:57 +00:00
nick.guenther@e418ed3c763dff37995c2ed5da4232a7c6cee0a9
cc053c820e Added a comment 2022-09-09 20:46:31 +00:00
nick.guenther@e418ed3c763dff37995c2ed5da4232a7c6cee0a9
a2dd58e9d4 Added a comment 2022-09-09 20:45:13 +00:00
Joey Hess
483e85fe5f
Merge branch 'master' of ssh://git-annex.branchable.com 2022-09-09 16:08:13 -04:00
Joey Hess
d2c842e9a1
don't force use of conduit in withUrlOptionsPromptingCreds
Use curl for downloads from git remotes when annex.url-options and other
git configs are set.

If the url needs a password, curl will fail, and git credential will not be
used to prompt for it. But the user can set --netrc in url-options and
put the password in the netrc file.

This also means that url-options settings like -4 will take effect.
That was the case before commit 1883f7ef8f
forced conduit to be used.
2022-09-09 16:07:32 -04:00
HiDefender
914729d8e4 Added a comment: Using git-annex on NTFS with WSL2 2022-09-09 19:24:56 +00:00
Joey Hess
247c0e59cf
comment 2022-09-09 15:15:54 -04:00
Joey Hess
511e711bed
close 2022-09-09 14:53:26 -04:00
Joey Hess
c2184e2295
Merge branch 'master' of ssh://git-annex.branchable.com 2022-09-09 14:46:55 -04:00
Joey Hess
c62fe5e9a8
avoid redundant prompt for http password in git-annex get that does autoinit
autoEnableSpecialRemotes runs a subprocess, and if the uuid for a git
remote has not been probed yet, that will do a http get that will prompt
for a password. And then the parent process will subsequently prompt
for a password when getting annexed files from the remote.

So the solution is for autoEnableSpecialRemotes to run remoteList before
the subprocess, which will probe for the uuid for the git remote in the
same process that will later be used to get annexed files.

But, Remote.Git imports Annex.Init, and Remote.List imports Remote.Git,
so Annex.Init cannot import Remote.List. Had to pass remoteList into
functions in Annex.Init to get around this dependency loop.
2022-09-09 14:43:43 -04:00
Joey Hess
9621beabc4
cache credentials in memory when doing http basic auth to a git remote
When accessing a git remote over http needs a git credential prompt for a
password, cache it for the lifetime of the git-annex process, rather than
repeatedly prompting.

The git-lfs special remote already caches the credential when discovering
the endpoint. And presumably commands like git pull do as well, since they
may download multiple urls from a remote.

The TMVar CredentialCache is read, so two concurrent calls to
getBasicAuthFromCredential will both prompt for a credential.
There would already be two concurrent password prompts in such a case,
and existing uses of `prompt` probably avoid it. Anyway, it's no worse
than before.
2022-09-09 14:20:32 -04:00
jgoerzen
7e6b2de2c5 2022-09-09 17:28:06 +00:00
yarikoptic
9811a02b67 Added a comment 2022-09-09 16:51:47 +00:00
Joey Hess
adb2f5cc00
comment 2022-09-09 12:39:28 -04:00
Joey Hess
28fc8d491f
comment 2022-09-09 12:30:46 -04:00
yarikoptic
22a311ef46 reporting flaky tests on ndoli 2022-09-08 15:01:50 +00:00
nick.guenther@e418ed3c763dff37995c2ed5da4232a7c6cee0a9
2c4c56ea50 Added a comment: git-credential-netrc 2022-09-08 02:02:40 +00:00
nick.guenther@e418ed3c763dff37995c2ed5da4232a7c6cee0a9
4f3a33d824 2022-09-08 01:10:06 +00:00
nick.guenther@e418ed3c763dff37995c2ed5da4232a7c6cee0a9
d8c98399e1 Added a comment 2022-09-08 00:28:32 +00:00
nick.guenther@e418ed3c763dff37995c2ed5da4232a7c6cee0a9
e1984e2c67 Added a comment 2022-09-07 23:22:40 +00:00
yarikoptic
f895adbb05 initial todo on multiple passwords entry for get 2022-09-06 21:02:01 +00:00
jgoerzen
d23318ae4f Added a comment 2022-09-05 23:57:01 +00:00
jgoerzen
aa4ba3fc7c Added a comment 2022-09-05 22:01:24 +00:00
jgoerzen
403dca7c42 Added a comment 2022-09-05 18:44:01 +00:00
Joey Hess
4a1908f12c
Merge branch 'master' of ssh://git-annex.branchable.com 2022-09-05 14:36:32 -04:00
Joey Hess
99a17e6185
comment 2022-09-05 14:35:24 -04:00
jgoerzen
764fa6e230 Added a comment 2022-09-05 18:29:31 +00:00
Joey Hess
bd7b760cf0
comment 2022-09-05 14:00:50 -04:00
Joey Hess
8a4cfd4f2d
use getSymbolicLinkStatus not getFileStatus to avoid crash on broken symlink
Fix crash importing from a directory special remote that contains a broken
symlink.

The crash was in listImportableContentsM but some other places in
Remote.Directory also seemed like they could have the same problem.

Also audited for other places that have such a problem. Not all calls
to getFileStatus are bad, in some cases it's better to crash on something
unexpected. For example, `git-annex import path` when the path is a broken
symlink should crash, the same as when it does not exist. Many of the
getFileStatus calls are like that, particularly when they involve
.git/annex/objects which should never have a broken symlink in it.

Fixed a few other possible cases of the problem.

Sponsored-by: Lawrence Brogan on Patreon
2022-09-05 13:46:32 -04:00
Joey Hess
600d3f7141
Merge branch 'master' of ssh://git-annex.branchable.com 2022-09-05 13:20:44 -04:00
Joey Hess
ff0490c7c6
fix build 2022-09-05 13:20:23 -04:00
Joey Hess
61b60f9e46
update 2022-09-05 10:44:45 -04:00
Lukey
7dd6e38945 Added a comment 2022-09-05 09:35:18 +00:00
Lukey
6e99fbc2e5 Added a comment 2022-09-05 09:07:05 +00:00
jgoerzen
fa01f0bab9 Added a comment 2022-09-05 01:14:53 +00:00
jgoerzen
661f452dfa Added a comment 2022-09-05 01:01:59 +00:00
jgoerzen
3159a28f88 2022-09-05 00:59:39 +00:00
jgoerzen
e7de6fffc1 2022-09-05 00:17:03 +00:00
jgoerzen
47a5853da8 Added a comment 2022-09-04 22:31:14 +00:00
jgoerzen
95e4021c09 2022-09-04 13:12:55 +00:00
tomdhunt
241b275f63 2022-09-04 04:39:20 +00:00