First, make sure you are using a modern web browser, preferably Mozilla Firefox or Google Chrome. Although our objective is to support all modern browsers, rapid development prevents us from doing extensive testing across many platforms; hence, we are sticking with the aforementioned two browsers for now.
Make sure you refresh your browser cache (`Ctrl+F5`) before logging in, especially if a new version has been deployed. The refresh will prevent older pieces of the application from lingering in your cache. This is just a precaution.
Sometimes a component on a page does not refresh itself correctly. The application is a complex system of components and is still under development. If you make an action and do not see the results in a reasonable while, refresh the page.
ReCodEx provides multiple ways for a user to register and log in. Currently there are two options: a local ReCodEx account or an account bound to the CAS service. The preferred way of registration and authentication is using the CAS service and using a local account only in special circumstances. CAS authentication provides more features, such as automatic binding of users to SIS groups.
The system's login mechanism is prepared for this option. The only prerequisite is that your email address in the local account must be the same as the one in CAS. If this is the case, binding the accounts is quite easy, just log in using CAS and the system will automatically bind those two accounts. Also please note that when binding your local account your password will be cleared and if you want to use it further, you have to change it.
Before we start let us define debug vs. regular submissions. The results of a debug submission contain evaluation results, the execution log and the outputs of executed programs. And the results of a regular submission contain only the results needed for proper assignment of points (aka. evaluation results).
With this being said, all submissions made by students for an assignment are regular and even submissions of reference exercise solutions are regular. As a supervisor you should be able to do something called resubmitting a user solution; this feature should be available on every page of a particular submission. On resubmitting, debug outputs and execution log are turned on by default and can be found in the results archive. Please note that resubmitting all solutions for an assignment is just a regular submission without debug information.
For some particular languages ReCodEx provides mappings of exit codes from internal runners to messages. Full tables of codes can be found on [separate page](https://github.com/ReCodEx/wiki/wiki/Exit-Code-Mappings).
