Up to standards ✅

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

Sorry for the errors that slipped in the code. I worked on another branch on multiple features at once before importing the code I thought was relevant. It is clearly not the most efficient/foolproof way of working.

I fixed those and ran a courseless/taskless job by calling a synchronous job. However this is not yet possible in the current state of INGInious. Do you have in mind a way for you or other reviewers to check the feature is working as expected.

I also had another question :

• While creating a ClientNewJob message in client.py, should the task problems dictionary passed be a None or an empty dict ? Both work opposed to the environment parameters that have to be a dict.

• While creating a ClientNewJob message in client.py, should the task problems dictionary passed be a None or an empty dict ? Both work opposed to the environment parameters that have to be a dict.

It's probably safer to default to an empty dictionary and maybe enforce it. The getinput API at the end is not meant to handle a None object.

Well well well, I realize by testing the code that empty /task and /course/common folders are still mounted. This may become confuse as if you put your run file in /task/ or /course/common/ it won't be accessible.

There is a choice to be made here:

• Either not mounting those useless folders but in this case it's worth making sure they exists in the base container to avoid breaking the other scripts. I'm not sure how much it impacts existing code.
• Either documenting it. I think it would be OK at this stage.

In both cases it's worth adding docs under a Developers documentation/Extensions/Taskless jobs section. This should specify the valid paths for the entrypoints and how to use the client.