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
{{ message }}
This repository has been archived by the owner on Feb 24, 2020. It is now read-only.
Running git bisect points to the following commit:
a5ad61df3b0d636115d3543c82befc0c84ffdb48 is the first bad commit
commit a5ad61df3b0d636115d3543c82befc0c84ffdb48
Author: Derek Gonyeo <derek.gonyeo@coreos.com>
Date: Mon Oct 19 18:04:15 2015 -0700
*: refactored library functions, added struct with common fields
The library was refactored so that all the exposed functions were
attached to a struct containing the information about the current
context. This makes using the library much cleaner.
The Registry struct had some of its fields renamed to be consistent with
the new struct in the library.
The functions for acquiring and releasing the lock were also moved from
acbuild/acbuild.go to the new struct.
:040000 040000 0b4c18665811cff0026264baf86df63fafcc05ee 55039ab1fead9942c9614bbbe9f739b6f657cf0d M acbuild
:040000 040000 a0e24013e636d4e8189af2c8d6d87acb0f914996 ce69a0ba1fd044cde549f7320f8aeef1f6ca40ee M lib
:040000 040000 3a03acbd4d502a348d419705fb0f1257906a7060 d0ac54b87df26184a5bc3c884b8bc8c36fa50363 M registry
The text was updated successfully, but these errors were encountered:
Sorry about that! There's two things at play here:
There's a bug in the github.com/coreos/ioprogress library that I fixed a couple week ago, but it appears that it's languishing in code review.
The logic for the numbers to draw in the uncompressing progress bar that's enabled with the --debug flag isn't correct, and the refactor commit you're on changed it so that the --debug flag is properly passed through to the part of the code that draws this. I'll disable that for now.
cgonyeo
pushed a commit
to cgonyeo/acbuild
that referenced
this issue
Oct 23, 2015
The recent refactor resulted in the registry being correctly passed the
debug value, which exposed an issue with an additional progress bar that
was being drawn when uncompressing a dependency.
The panic was a combination of the logic drawing the bar passing the
ioprogress library a number that was too small for the total size, and
the ioprogress library not having a patch to be able to handle incorrect
numbers.
This commit removes the uncompressing bar, and updates the ioprogress
library.
Fixescontainers#56
I've got a pull request in to fix this, but until that gets merged if you remove the --debug flag from the run command that should be a viable workaround.
After updating to the lastest master this morning, I started getting the following error:
Running git bisect points to the following commit:
The text was updated successfully, but these errors were encountered: