When uploading a .algo file that contains a faulty problem.py (e.g. when importing packages that are not set as a requirement in the algobattle.toml) via the upload dialogue, the mask goes through without displaying an error and a new problem is displayed in the list of all problems.
When viewing this newly created problem, the description and schema are not displayed, suggesting that something failed, but what exactly failed cannot be seen by the uploading person, as the appropriate error message is only displayed in the server logs. It would be nice if the user could get feedback that the problem creation did not actually succeed, even better if a concrete reason could be given.
When uploading a
.algofile that contains a faultyproblem.py(e.g. when importing packages that are not set as a requirement in thealgobattle.toml) via the upload dialogue, the mask goes through without displaying an error and a new problem is displayed in the list of all problems.When viewing this newly created problem, the description and schema are not displayed, suggesting that something failed, but what exactly failed cannot be seen by the uploading person, as the appropriate error message is only displayed in the server logs. It would be nice if the user could get feedback that the problem creation did not actually succeed, even better if a concrete reason could be given.