Skip to content

Conversation

@Didayolo
Copy link
Member

@Didayolo Didayolo commented Aug 28, 2025

Test

Deployed at https://codabench-test.lri.fr/

Manual intervention

1. MinIO migration (depending on setup) (#1964)

If you are running MinIO locally (defined by .env and docker-compose.yml, you may require to follow the following MinIO upgrade instructions, to duplicate and mirror your buckets and convert them to the new format:
https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-migrate-fs-gateway.html

2. Rebuild all containers (#2025)

docker compose build && docker compose up -d

3. Django migration (#1955)

docker compose exec django ./manage.py migrate

4. Collect static files (#1982)

docker compose exec django ./manage.py collectstatic --no-input

Changes

Obada Haddad and others added 30 commits May 28, 2025 10:36
…container to launch containers on host instead of inside the container
…ll to the submission container launch options, changed volume mounting option for podman
…r datasets, menu updates, new serializer created for datasets
…reate page added, some minor style updates, datasets public api permission updated to allow anonymous access
@ObadaS
Copy link
Collaborator

ObadaS commented Oct 3, 2025

This concerns #1955

@ihsaan-ullah
Hello, I update the develop branch on the test server, rebuild all docker images, then ran docker compose exec django ./manage.py migrate, however, when I upload a competition, I can not see it in the new menu. I tried multiple time on my local instance and on the test server, with different competitions. The competitions are created and can be accessed if you know the link, but it is not showing in the new page, even when pressing Organizing checkbox
image

Also, we are losing some functionality with the new page, since we can't publish/unpublish, edit or delete competitions quickly from the page. Do you think it could be added back ?
image

If you are not sure where to add it, I think the way Codalab does it is a good start.
image

@ihsaan-ullah
Copy link
Collaborator

@ObadaS #1955 is about datasets page.

I haven't changed competitions functionality in this PR. But in the Competitions page only public competitions are shown (https://codabench-test.lri.fr/competitions/public/?page=1). Do you think.

Maybe I don't understand the problem you want to point to. If that is the case please add more details so that I can debug on my side

@ObadaS
Copy link
Collaborator

ObadaS commented Oct 3, 2025

After reading your comment, I tried to publish a competition I uploaded, and it appeared on the page. How can I see all the private competitions that I have uploaded ?

@ObadaS
Copy link
Collaborator

ObadaS commented Oct 3, 2025

Nevermind, I figured it out, the pages were moved to the dropdown menu. I was confused because we usually upload new bundles from the page where we manage everything, so I thought I should be seeing the new competition I uploaded from the same page I uploaded it from

@ihsaan-ullah
Copy link
Collaborator

After reading your comment, I tried to publish a competition I uploaded, and it appeared on the page.

This is expected behaviour

How can I see all the private competitions that I have uploaded ?

Your competitions (public or private) can be meanaged from Menu -> My Resources -> Competitions
Screenshot 2025-10-03 at 6 37 51 PM

@ihsaan-ullah
Copy link
Collaborator

We can always improve the flow/UI if there is any confusion

Didayolo and others added 3 commits October 7, 2025 14:27
Podman updates & More Competition container security
Added command to enable podman containers to not be shutdown after the user logs out
@Didayolo
Copy link
Member Author

Didayolo commented Oct 7, 2025

We can always improve the flow/UI if there is any confusion

It is just a matter of getting used to it. Maybe we could communicate about the change.

Personally I love this new interface, generally it's lighter and more intuitive.

@Didayolo
Copy link
Member Author

Didayolo commented Oct 8, 2025

@ObadaS

On the test server, using the podman_main queue on Mini-AutoML:

Pull for image: codalab/codalab-legacy:py39 returned a non-zero exit code! Check if the docker image exists on docker hub. Command '['podman', 'pull', 'codalab/codalab-legacy:py39']' returned non-zero exit status 125.

Obada Haddad added 8 commits October 8, 2025 11:59
…colorize them. Also added an easier way to change logs to DEBUG INFO WARNING etc from the .env file, and made it possible to generate JSON logs with Loguru
…ation easier (one place to configure instead of every file where it's called
@ObadaS
Copy link
Collaborator

ObadaS commented Oct 8, 2025

@ObadaS

On the test server, using the podman_main queue on Mini-AutoML:

Pull for image: codalab/codalab-legacy:py39 returned a non-zero exit code! Check if the docker image exists on docker hub. Command '['podman', 'pull', 'codalab/codalab-legacy:py39']' returned non-zero exit status 125.

I checked on the machine, it is a simple disk space problem. I have erased all the images for now
image

I might need to add more disk though if we want to run more tests on different competitions with different images since there is not a lot of space on the VM

@Didayolo Didayolo merged commit d26ef68 into master Oct 14, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Release PR develop --> master

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants