Commit graph

12688 commits

Author SHA1 Message Date
Joey Hess
314ce317bf
update 2025-09-05 15:48:43 -04:00
Joey Hess
171b427eb8
update 2025-09-05 14:07:40 -04:00
Joey Hess
9a2013a2e7
update 2025-09-05 14:06:15 -04:00
Joey Hess
d8f40288f1
update 2025-09-05 11:21:38 -04:00
Joey Hess
1230ac83e9
copyFile 2025-09-05 11:17:14 -04:00
Joey Hess
cb6f28282a
on libraries 2025-09-04 18:09:57 -04:00
Joey Hess
2b2e76e73f
format 2025-09-04 16:56:19 -04:00
Joey Hess
10fcd61966
fix format 2025-09-04 16:40:59 -04:00
Joey Hess
7b711ffd3b
Revert "try to fix format issue on website"
This reverts commit 764b47d7d4.
2025-09-04 16:40:50 -04:00
Joey Hess
764b47d7d4
try to fix format issue on website 2025-09-04 16:38:55 -04:00
Joey Hess
807ae0ad26
Merge branch 'master' of ssh://git-annex.branchable.com 2025-09-04 16:31:25 -04:00
Joey Hess
eff0c509f7
more 2025-09-04 16:31:09 -04:00
yarikoptic
d67f578049 added project 2025-09-04 20:13:07 +00:00
Joey Hess
033e4b086f
audit all openFd and dupping for close-on-exec
Made all uses of openFd and dup set the close-on-exec flag, with a few
exceptions when starting a git-annex daemon.

Made openFdWithMode be used everywhere, rather than openFd.
Adding a new parameter to it ensures I checked everything.
And will help to make sure this gets considered in the future when
opening fds.

In lockPidFile, the only thing that keeps the pid file locked, once
daemonize re-runs the command in a new session, is that the fd is
inherited.

In Utility.LogFile.redir, the new fd it dups to does not have the
close-on-exec flag set, because this is used to set up the stdout and
stderr fds, which need to be inherited by child processes.

Same in Assistant.startDaemon where the browser gets started with the
original stdout and stderr.

This does nothing about uses of openFile and similar!

Sponsored-By: mycroft
2025-09-04 16:01:41 -04:00
Joey Hess
e1dcf98b78
analysis 2025-09-04 14:46:44 -04:00
Joey Hess
b2b055a634
analysis 2025-09-04 14:23:13 -04:00
Joey Hess
d44fd44c92
comment 2025-09-04 13:32:12 -04:00
Joey Hess
67f00027d1
avoid relatedTemplate ever returning ""
add: Fix crash adding filenames that are exactly 21 bytes long and begin
with a utf-8 character.

Also longer filenames that start with "....." would cause the same crash.

I also audited for other calls to truncateFilePath that could truncate it
to "". Most use pathmax so are not a problem. Backend.Utilities.genKeyName
could possibly truncate it like that, but appends the md5 so would not be a
problem either.

Sponsored-by: Kevin Mueller
2025-09-04 13:02:46 -04:00
yarikoptic
4b037dda81 Added a comment 2025-09-04 02:06:22 +00:00
yarikoptic
5347627025 Added a comment: odd odd filesystem 2025-09-02 15:06:43 +00:00
guardcat
da4237182e 2025-09-02 10:42:04 +00:00
guardcat
25834e7c79 2025-09-02 10:21:27 +00:00
guardcat
8e032545d8 2025-09-02 10:02:44 +00:00
guardcat
4654097a97 2025-09-02 09:32:38 +00:00
guardcat
bb0690a254 2025-09-02 09:30:30 +00:00
guardcat
9a32b46103 2025-09-02 08:32:27 +00:00
Joey Hess
1d51a0b0ad
comments 2025-08-29 11:42:33 -04:00
yarikoptic
5771a4c83a initial report from ducky 2025-08-29 14:35:04 +00:00
Joey Hess
a82d531433
fix test suite breakage
640bc43c38 broke a test. Change that test
to not use encryption=shared. Which required some refactoring.

Sponsored-by: Joshua Antonishen
2025-08-27 12:26:50 -04:00
yarikoptic
00d64bce36 issue resolved 2025-08-26 12:58:20 +00:00
yarikoptic
e241d08fc2 report on failing test 2025-08-26 11:41:58 +00:00
yarikoptic
b58301e876 Added a comment 2025-08-25 21:30:56 +00:00
yarikoptic
6c14dcfcad Added a comment 2025-08-25 16:56:00 +00:00
yarikoptic
a9e146d30b Added a comment 2025-08-25 16:55:33 +00:00
yarikoptic
02df4deead initial report on copy to be stuck 2025-08-25 16:48:56 +00:00
Lukey
b71f0f2e33 Added a comment 2025-08-23 06:51:16 +00:00
Joey Hess
98d4f07057
tahoe: Support tahoe-lafs command versions newer than 1.16
tahoe start was deprecated and removed in 2020.

This feels like a very janky way to run a daemon, but it does work.

Sponsored-by: k0ld
2025-08-22 12:35:53 -04:00
Joey Hess
bc18b11cb8
prevent changing onlyencryptcreds of existing remote
That would break accessing data already stored in the remote, the same
as changing encryption type would do.

Sponsored-by: Jack Hill
2025-08-21 13:50:39 -04:00
Joey Hess
6b63fb7ea2
Don't allow the type of encryption of an existing special remote to be changed.
eg, git-annex enableremote foo encryption=none will not remove encryption,
and other encryption= settings don't change the type of encryption used.
Either of which would render data stored in a special remote inaccessible.

Probably fixes reversion introduced in
71f78fe45d.
That commit got rid of the hasEncryptionConfig check, which I think would
have detected this before. I've not gone back to verify that.

Sponsored-by: mycroft
2025-08-21 13:41:00 -04:00
Joey Hess
afff2bb47d
onlyencryptcreds=yes
initremote: When onlyencryptcreds=yes is used along with embedcreds=yes,
and encryption is enabled, only encrypt the embedded creds, without
encrypting the content of the special remote.

Useful for exporttree=yes/importtree=yes remotes.

Sponsored-by: Joshua Antonishen
2025-08-20 15:14:01 -04:00
Joey Hess
8122195ac8
bug 2025-08-20 14:58:44 -04:00
Joey Hess
e38afbcd43
bug 2025-08-20 14:35:27 -04:00
Joey Hess
0f36cd1613
fixed 2025-08-20 13:36:39 -04:00
Joey Hess
fd89e611b2
error out when another branch has been manually merged into the adjusted branch
This avoids losing the merge commit when re-running git-annex adjust in the
adjusted branch.

It also makes git-annex sync error out, rather than displaying a warning
and exiting successfully.

Sponsored-by: Leon Schuermann on Patreon
2025-08-20 13:28:03 -04:00
Joey Hess
16463f8f02
Merge branch 'master' of ssh://git-annex.branchable.com 2025-08-20 12:31:35 -04:00
jcjgraf
9d1f47a45b Added a comment: Reproduce Issue 2025-08-18 19:02:35 +00:00
Joey Hess
8991c75d04
bug 2025-08-15 18:11:19 -04:00
Joey Hess
0b388c0924
warn and refuse to autoenable a special remote when name is in use
Improve behavior when there are special remotes configured with
autoenable=yes with names that conflict with other remotes.

The use of remoteList' is to avoid using the cached remote list in the case
where there are two special remotes both configured to autoenable and both
with the same name. Once the 1st is autoenabled, this makes reload the
remote list and so see the 1st, and so refuse to autoenable the second.

This adds a little bit of overhead, but it should be sufficiently small not
to need optimising.

Sponsored-by: Dartmouth College's OpenNeuro project
2025-08-14 11:05:42 -04:00
Joey Hess
5323e0c20b
followup 2025-08-14 10:15:29 -04:00
Joey Hess
b5808c6413
close 2025-08-14 09:56:15 -04:00