Hello Maximilian,
many, many thanks for debugging this issue further and for sharing your
workaround!
It works for me, too.
On Sat, 19 Dec 2020 19:04:40 +0100 Maximilian Stein wrote:
> So, right now, I do have a workaround, although I don't where the
> problem is exactly (i.e., in gitlab or in
Hi folks,
I just found a workaround for that issue. Apparently, the issue is a
missing type check/type confusion in "etag" (or in the invocation of
this lib). With the patch attached to this mail, artifacts can be
uploaded again.
To debug the issue, I added a begin/resuce block around the failing
Hello,
On Tue, 18 Aug 2020 20:37:09 +0200 Maximilian Stein wrote:
> Since the upgrade to above mentioned version, artifact uploads from
> gitlab runners fail with an error 500.
the same error (with the same stacktrace) also occurs on my gitlab instance
after the upgrade of the Debian package (f
Package: gitlab
Version: 13.2.3-2+fto10+1
Severity: normal
Dear Maintainer,
Since the upgrade to above mentioned version, artifact uploads from
gitlab runners fail with an error 500.
Snippet from the job log:
---
Uploading artifacts...
time="2020-08-18T19:42:06+02:00" level=error msg="Docker ex
4 matches
Mail list logo
