Merge branch 'master' of ssh://git-annex.branchable.com

doc/bugs/S3_fsck_from_chunked_file__through_publicurl_fails.mdwn

@@ -0,0 +1,33 @@
+### Please describe the problem.
+
+When running fsck (fast or slow) from an S3 remote that has anonymous access and git-annex publicurl set, it fails only on the files that get chunked into multiple parts because they exceed the configured chunk size for the remote.
+
+
+### What steps will reproduce the problem?
+
+- create repo
+- annex a file
+- set AWS creds as env vars
+- initremote S3 special remote with chunk size smaller than the file size and publicurl
+- push data (authenticated) to the S3 remote, ensure it get chunked.
+- unset AWS auth vars (and remove .git/annex/creds if necessary)
+- fsck from remote should fail on chunked file
+
+
+### What version of git-annex are you using? On what operating system?
+
+git-annex version: 10.20250417-gfd493804c004f7facb4b99d4bf21ed49a081c5cf
+
+### Please provide any additional information below.
+
+[[!format sh """
+# If you can, paste a complete transcript of the problem occurring here.
+# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
+
+
+# End of transcript or log.
+"""]]
+
+### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
+
+Yes indeed! :D 

doc/todo/p2phttp__58___listen_on_unix_domain_sockets/comment_2_e075c37cbeab627a6a96dcfb1525e21d._comment

@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="matrss"
+ avatar="http://cdn.libravatar.org/avatar/cd1c0b3be1af288012e49197918395f0"
+ subject="comment 2"
+ date="2025-07-03T11:07:06Z"
+ content="""
+Unfortunately I wasn't able to make use of the multiple repositories feature because Forgejo stores repositories in nested directories (`<username-or-organisation>/<repository>`). Even if I was able to use that feature, using unix sockets would still feel cleaner and avoid some security concerns around running the p2phttp server with `--wideopen` (as-is it is accessible to all local users, with unix sockets permissions could be used to restrict it; but this is more of a theoretical concern, I am not aware of anyone running a Forgejo-aneksajo server on a host with untrusted users).
+
+According to <https://stackoverflow.com/questions/22621623/warp-binding-to-unix-domain-sockets> it should be possible to use warp's runSettingsSocket with a unix socket, instead of runSettings. I am not familiar enough with Haskell or git-annex to judge if there are other obstacles though...
+"""]]