GitHub tag not detected

Hello,

I have been using a private GitHub repository to submit on the leaderboard. I made a new release along with a new tag for the final submission as I did for all my previous submissions, but this time the release has not been detected by the grand-challenge server. Do you have any insight of why ? Should I create a new algorithm because I have reached some limitation on the number of allowed containers ? I have a bunch of inactive containers which I don't know how to delete...

Thanks, Simon

We were unable to clone your repo. The repo you're trying to build from has used all of its LFS bandwidth. Please purchase more data packs on GitHub for this repo so that we can clone it, then try again.

Hello,

Thank you for your answer. I just bought a 50GB datapack and made the Final Phase Submission release. Do you have to manually re-run something ? I don't see anything happening

We received the webhook at 0740 UTC, same message:

Cloning into '/tmp/tmpeoegkfzl'... Note: switching to '3c3b59b5bffe70057a322abb3a2a1ee971bb7cbb'.

You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example:

git switch -c

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

Downloading training/artifact/unet_r231-d5d2fc3d.pth (124 MB) Error downloading object: training/artifact/unet_r231-d5d2fc3d.pth (d5d2fc3): Smudge error: Error downloading training/artifact/unet_r231-d5d2fc3d.pth (d5d2fc3df432115933491f115b283e94d1f5c841c0e82f6e7bd2d65d3ccde69f): batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

You can see below that the storage should be sufficient. I paid the package at 01:16AM PDT (on my receipt), which is 08:16 UTC, later than your 07:40 UTC message. Maybe you could try again ? I don't really know what else you can do except wait and try again 😅

Indeed, you need to have enough credits when you tag the repo as grand challenge gets the webhook and attempts to build the image seconds after the tag is created. Now you have enough credits, you can tag the image again and the platform should be able to clone the repo.

Hello

I made a new release (same commit) and it worked. However the build failed with the following error. :

Build started on Fri May 6 22:45:18 UTC 2022 Building the Docker image in /codebuild/output/src156318813/src... unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /codebuild/output/src156318813/src/Dockerfile: no such file or directory Build completed on Fri May 6 22:45:19 UTC 2022 Saving the Docker image... Error response from daemon: reference does not exist

Is there something to update somewhere for the new codebase architecture to be well detected ?

The error message is in what you posted (unable to evaluate symlinks in Dockerfile path). It is unable to evaluate symlinks in the Dockerfile path. Your Dockerfile must be at the root of your repo.

Unfortunately, that is not the case with the template repository we are supposed to use (link)

In the mail we received, it is mentionned After the deadline, we will train your submissions and get back to you with the results.. Does it mean we don't have to do anything on the grand-challenge website ? (i.e. we don't have to use the Submit button nor to care about the docker image to be built)

Hi Simon,

My apologies for the unclarity and that I did not catch this sooner. For the Final Phase submission, it's indeed sufficient to follow the submission instructions that you received via e-mail. You indeed do not have to do anything on the grand-challenge website.

Best, Luuk

Thank you Luuk, in any case I had to add bandwith for git-lfs so this post was not entirely pointless ^^