TW
Yes, the current git code (and the next release) has migration code.
Just in case you didn't read it already: try ssh (+ attic on remote side), could be more efficient.
Because you then have a remote process that can work with the repo data on the remote side. Avoiding to pump some stuff over the network connection. With a just...
3 potential remedies for this: - use a remote attic process (ssh: repo url - not always possible) - do checkpoints less often (already possible: use `attic create --checkpoint-interval NNNN`)...
@wkoszek attic's codebase currently can't cope in a good way with configurations that have little cpu/memory AND a big data set to backup. The problem is that attic keeps the...
Looks like there is an invalid segment entry header (that usually contains a 32bit crc, a 32bit total entry size [header size + data size] and a 8bit tag). As...
The size check in repository.py line 498 needs to get fixed to make it raise a documented/appropriate exception: ``` if size > MAX_OBJECT_SIZE or size < self.header_fmt.size: ``` That will...
close due to inactivity?
``` $ python3 -c 'for i in range(1000000): print(i)' | less Traceback (most recent call last): File "", line 1, in BrokenPipeError: [Errno 32] Broken pipe ``` I pressed "q"...
https://docs.python.org/3.5/whatsnew/3.5.html#whatsnew-pep-471