You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a complex report. But it seems that the following signs could be attributed to complications that originally arose from a too large git object db (1GB).
unexpected disconnect while reading sideband packet, the remote end hung up unexpectedly
OP reports that running git gc and creating a new GIN repo got them going again.
A likely cause of the underlying problem (db too large), is the use of the text2git setup that is prominently promoted in the handbook. This led to large SVG (like fmriprep produces by default) to be committed to Git: https://neurostars.org/t/datalad-push-to-gin-errors/24051/15
There is another entangled issue in that report on (verification of content error), but this is less clear and not the topic for this issue.
There is also a statement on an incompatibility of the GIN CLI with git-annex v10 onwards. This would limit GIN users re flexibly switching tools. git-annex v10 was released Jan 2022 (15 months ago).
TODO (not necessarily to be performed in this order)
Inform OP/Add reference to this issue at origin
Clarifying Qs asked or not needed
Nature of the issue is understood
Inform OP about resolution
The text was updated successfully, but these errors were encountered:
Origin: https://neurostars.org/t/datalad-push-to-gin-errors/24051
This is a complex report. But it seems that the following signs could be attributed to complications that originally arose from a too large git object db (1GB).
unexpected disconnect while reading sideband packet
,the remote end hung up unexpectedly
OP reports that running
git gc
and creating a new GIN repo got them going again.A likely cause of the underlying problem (db too large), is the use of the
text2git
setup that is prominently promoted in the handbook. This led to large SVG (like fmriprep produces by default) to be committed to Git: https://neurostars.org/t/datalad-push-to-gin-errors/24051/15There is another entangled issue in that report on (
verification of content error
), but this is less clear and not the topic for this issue.There is also a statement on an incompatibility of the GIN CLI with git-annex v10 onwards. This would limit GIN users re flexibly switching tools. git-annex v10 was released Jan 2022 (15 months ago).
TODO (not necessarily to be performed in this order)
The text was updated successfully, but these errors were encountered: