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

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

Browse source
This commit is contained in:
Joey Hess 2019-01-11 17:25:56 -04:00
commit c1c976d1fa
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 120 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/bugs/No_MonadFail_instance/comment_1_444dd4bf522e93f1cbee562d748a781a._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="alogic0@d8fbd9f5b547237a650aa1d5605c2d3592496916"
nickname="alogic0"
avatar="http://cdn.libravatar.org/avatar/9498ef776e93104a14ea86b734a5f0cf"
subject="it's fixed"
date="2019-01-11T00:54:01Z"
content="""
Try to build the latest version, obtained by
```git clone git://git-annex.branchable.com/ git-annex```
"""]]

9
doc/bugs/No_MonadFail_instance/comment_2_b578bcc04c23407342830ef9bd27f755._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="6yearold@36d59212c29d2959d6532d6db7928f01541bcf83"
nickname="6yearold"
avatar="http://cdn.libravatar.org/avatar/0227e5d5eaceb8ae2f751df38d421764"
subject="comment 2"
date="2019-01-11T06:28:31Z"
content="""
Can we get a new release containing this fix?
"""]]

84
doc/bugs/v7_unlock_big_file__58___out_of_memory.mdwn Normal file
View file

@ -0,0 +1,84 @@
### Please describe the problem.
In v7 repos unlocking files larger then RAM, causes out of memory error on subsequent commands.
### What steps will reproduce the problem?
Just create new repository, add big file, unlock it, try to run `git annex status`. See full actions list below.
### What version of git-annex are you using? On what operating system?
Tested on:
- 7.20181206-gc4b6115f7
- 7.20181212-g7d51b0c10
### Please provide any additional information below.
[[!format sh """
$ git --version
git version 2.20.1
$ git annex version
git-annex version: 7.20181212-g7d51b0c10
build flags: Assistant Webapp Pairing S3(multipartupload)(storageclasses) WebDAV Inotify DBus DesktopNotify TorrentParser MagicMime Feeds Testsuite
dependency versions: aws-0.20 bloomfilter-2.0.1.0 cryptonite-0.25 DAV-1.3.3 feed-1.0.0.0 ghc-8.4.4 http-client-0.5.13.1 persistent-sqlite-2.8.2 torrent-10000.1.1 uuid-1.3.13 yesod-1.6.0
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 BLAKE2B256E BLAKE2B256 BLAKE2B512E BLAKE2B512 BLAKE2B160E BLAKE2B160 BLAKE2B224E BLAKE2B224 BLAKE2B384E BLAKE2B384 BLAKE2S256E BLAKE2S256 BLAKE2S160E BLAKE2S160 BLAKE2S224E BLAKE2S224 BLAKE2SP256E BLAKE2SP256 BLAKE2SP224E BLAKE2SP224 SHA1E SHA1 MD5E MD5 WORM URL
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav adb tahoe glacier ddar hook external
operating system: linux x86_64
supported repository versions: 5 7
upgrade supported from repository versions: 0 1 2 3 4 5 6
$ git init
Initialized empty Git repository in /home/user/Temp/Annex/bug/.git/
$ git annex init --version=7
init ok
(recording state in git...)
$ ls -lh
total 16G
-rw-r--r-- 1 user user 16G Jan 9 23:00 big-file
$ git annex status
? big-file
$ git annex add
add big-file ok
(recording state in git...)
$ git annex status
A big-file
$ git annex sync
commit
[master (root-commit) ef57173] git-annex in user@user-thinkpad:~/Temp/Annex/bug
1 file changed, 1 insertion(+)
create mode 120000 big-file
ok
$ git annex status
$ git status
On branch master
nothing to commit, working tree clean
$ git annex unlock big-file
unlock big-file ok
(recording state in git...)
$ git annex status
fatal: Out of memory, realloc failed
git-annex: git status failed
git-annex: status: 1 failed
$ git status
fatal: Out of memory, realloc failed
"""]]
### 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)
Git Annex is unique piece of Art, there is nothing like it.

16
doc/todo/wishlist__58___--dry-run_option_for_all_commands/comment_3_411cabdfebe353d35f8dc78364f4a507._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="git-annex.branchable.com@1c3a8a83c15a19620a0a1a2e653d7c662fc8fe50"
nickname="git-annex.branchable.com"
avatar="http://cdn.libravatar.org/avatar/fd46557ea8b9b21ae4ce66517076fbcb"
subject="get dry-run-ish option"
date="2019-01-11T16:18:13Z"
content="""
You can find out what would be done by a get (ish), but running something like this:
git annex find --not --in here <path>
..which will show files which are known about but aren't in this annexed copy.
I've been using this to see what needs to be 'got' to a location.
It does, however, need an annex repo to have a remote set up if you wish to check against it, as they aren't automatically bi-directional (which makes sense as firewalls and similar may not make this possible).
"""]]