# Known Issues and Fixes

This page outlines the known issues associated with the platform and provides guidance on how to
resolve or work around them.

## Definition validation

### Issue

When uploading a definition to IXP, a similar error message appears
`'utf-8' codec can't decode byte 0x00 in position 557: invalid start byte`.

### Cause

There are 2 possible causes for this:

1. A non-text file was included in the `content` directory.
    This can commonly occur on macOS operating systems,
    where directories can contain a `.DS_STORE` metadata file.
2. The text files/names are not encoded in `utf-8`.

### Solution

For the first cause, delete these non-text files from the directory.

On macOS, you can try different tools which do not include the `.DS_STORE` file,
for example <https://www.keka.io/en/>.

For the second cause, simply change the encoding to `utf-8`.

## Log export

### Issue

Exported exercise logs contain files which were not uploaded during the exercise.

### Cause

This issue occurs when one user is assigned to multiple exercises.
If this user uploads a file during any of the exercises,
logs from all the exercises will contain the uploaded file as if it was uploaded by the team
the user is assigned to.

### Solution

When this occurs, it is quite easy to identify and fix it.
To identify files which were incorrectly added to the logs,
simply check that the files in `logs/team-X/uploaded-files/` exist in `logs/file_infos.jsonl`.
If a file does not exist in `logs/file_infos.jsonl`, it can be safely deleted from the logs
as it was not uploaded during that exercise.

## Conclusion

If you require further assistance, don't hesitate to report issues to us. The
[Report issue](report-issue.md) page includes instructions on how to report bugs.
