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

point to commit that may fix this

Browse source
This commit is contained in:
Joey Hess 2020-09-14 18:30:41 -04:00
parent ddf963d019
commit c87f73f638
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
doc/bugs/concurrent_git-annex-copy_to_s3_special_remote_fails/comment_4_af2e6683949d6168ff4ca606085cf870._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2020-09-14T21:32:05Z"
content="""
Thinking about this, one thing in git-annex that might somehow involve
unsafe memory access would be if Remote.S3's use of runResourceT returns
a value that depends on a resource that then gets freed.
[[!commit ddf963d0194acf9f6f059fa37f3e89e59d682de9]] should avoid all ways that might possibly have happened,
so if anyone has a way to reproduce this reliably, it would be good to know
if it still happens after that fix.
"""]]