Skip to content

GitLab

Switch branch/tag
  1. 23 Sep, 2015 1 commit
  3. 15 Sep, 2015 1 commit
  5. 14 Sep, 2015 1 commit
  7. 13 Sep, 2015 1 commit
  9. 12 Sep, 2015 6 commits
  11. 11 Sep, 2015 2 commits
  13. 04 Sep, 2015 2 commits
  15. 03 Sep, 2015 1 commit
  17. 02 Sep, 2015 1 commit
  19. 30 Aug, 2015 1 commit
  21. 29 Aug, 2015 6 commits
  23. 28 Aug, 2015 2 commits
  25. 27 Aug, 2015 2 commits
  27. 25 Aug, 2015 1 commit
  29. 24 Aug, 2015 2 commits
  31. 21 Aug, 2015 1 commit
  33. 17 Aug, 2015 1 commit
  35. 16 Aug, 2015 1 commit
  37. 15 Aug, 2015 1 commit
  39. 13 Aug, 2015 2 commits
  41. 12 Aug, 2015 1 commit
    • Juan Batiz-Benet's avatar
      cmds/add: use dagutils.Editor, like patch · 978c9fa1
      Juan Batiz-Benet authored 
      This changes the pin behavior. It uses the filenames given through
the api, and allows files to be streamed faltly (not a hierarchy),
which is easier for other things (like vinyl in node-ipfs-api land).
Files can also be entirely out of order, and the garbage intermediate
directories will not be pinned (gc-ed later).

The changes also mean the output of add has changed slightly-- it
no longer shows the local path added, but rather the dag path
relative to the added roots. This is a small difference, but changes
tests.

The dagutils.Editor creates a lot of chaff (intermediate objects)
along the way. Wonder how we might minimize the writes to the
datastore...

This commit also removes the "NilRepo()" part of the --only-hash
mode. We need to store at least in an in-mem repo/datastore because
otherwise the dagutils.Editor breaks.

License: MIT
Signed-off-by: default avatarJuan Batiz-Benet <juan@benet.ai>
      978c9fa1
  43. 05 Aug, 2015 3 commits
    • Juan Batiz-Benet's avatar
      get: fix bug + improvements · f105ce43
      Juan Batiz-Benet authored 
      up until now there has been a very annoying bug with get, we would
get halting behavior. I'm not 100% sure this commit fixes it,
but it should. It certainly fixes others found in the process of
digging into the get / tar extractor code. (wish we could repro
the bug reliably enough to make a test case).

This is a much cleaner tar writer. the ad-hoc, error-prone synch
for the tar reader is gone (with i believe was incorrect). it is
replaced with a simple pipe and bufio. The tar logic is now in
tar.Writer, which writes unixfs dag nodes into a tar archive (no
need for synch here). And get's reader is constructed with DagArchive
which sets up the pipe + bufio.

NOTE: this commit also changes this behavior of `get`:
When retrieving a single file, if the file exists, get would fail.
this emulated the behavior of wget by default, which (without opts)
does not overwrite if the file is there. This change makes get
fail if the file is available locally. This seems more intuitive to
me as expected from a unix tool-- though perhaps it should be
discussed more before adopting.

Everything seems to work fine, and i have not been able to reproduce
the get halt bug.

License: MIT
Signed-off-by: default avatarJuan Batiz-Benet <juan@benet.ai>
      f105ce43
    • Juan Batiz-Benet's avatar
      sharness/t009-get: fix space/tabs · 741cf7e7
      Juan Batiz-Benet authored 
      License: MIT
Signed-off-by: default avatarJuan Batiz-Benet <juan@benet.ai>
      741cf7e7
    • Juan Batiz-Benet's avatar
      unixfs/tar: cleaned up reader code · b8589286
      Juan Batiz-Benet authored 
      License: MIT
Signed-off-by: default avatarJuan Batiz-Benet <juan@benet.ai>
      b8589286