FAQ

October 20, 2026
Contents

> I lost my Webhook secret or deploy key, how do I recover them?

Recovering your keys is easy, just visit the secret recovery page. You will send an email and receive your credentials back, also via email. You will get everything back in less than 5 minutes. If it doesn’t work look at the “Still having problems?” section

> What is this leaderboard about?

This leaderboard tracks and displays the performance of students on the programming exercises offered in the course. It ranks users based on their runtimes. The better you parallelize and optimize your code, the higher you will rank.

> How often is the leaderboard updated?

The leaderboard is updated every time a student pushes an update to their repository. Of course there is a delay between your push and the grader running your code, so please allow a few minutes of slack. Once the grader has picked up your submission a green blinking dot will appear next to your username in the leaderboard. Old results will be visible until new results are available.

> How are medals awarded?

Medals are awarded separately for each task once its leaderboard has at least 10 submissions. All submissions count toward the medal cutoffs, including incorrect results, but only correct results can earn medals.

Let N be the number of submissions for that task. The cumulative rank cutoffs are:

MedalCutoffAwarded to ranks
GoldG = max(1, round(5% × N))1 through G
SilverS = max(G + 1, round(10% × N))G + 1 through S
BronzeB = max(S + 1, round(20% × N))S + 1 through B

Cutoffs are rounded to the nearest whole number, with halves rounded up. Each tier has at least one place available. For example, with 10 submissions, the cutoffs are 1, 2, and 3: first place earns gold, second silver, and third bronze. A tier can remain empty if there are too few correct results. Medals reflect the current standings and may change as results are updated.

> Why is my result not changing after I submit a new solution?

If you’ve waited a few minutes and your result is still not changing, it’s possible that the specific assignment you pushed to has a cooldown timer. It can happen that if you push too many times in a short period of time, the grader will delay the grading of your submission until the cooldown timer elapsed. If after 10-15 minutes your result is still not changing (check the hash of your commit), please make sure that you’re pushing to the correct branch (usually main or master). If the problem persists, have a look at “Still having problems?” section

> Can I see more detailed informations about my run?

Yes, you can view more details (like stdout and stderr) by clicking on your row (your username) in the leaderboard. Use it to understand what’s happening during the execution of your code.

> How do I submit my project?

Please follow the instructions in the How to submit your project page.

> What does Execution timed out after X seconds mean?

This means that your code took too long to run. The grader has a timeout limit for each assignment, this limit is usually permissive enough to allow a basic parallel implementation to run. If you believe your code is correct and should run in time, look at Still having problems?

> How do I download artifacts from the grader?

You can download the artifacts in a zip file by going to the artifact page and inserting the secret key you received when you submitted your project.

> Still having problems?

If you still have a problem you can’t solve, please write it either on the “Programmazione di sistemi embedded e multicore” telegram group (you can find the link here) or send an email to mcp [at] francescodb.it. The telegram group is usually the fastest way to get help.