Debug a failure

Describe the problem#

Open Mirr Code in the project and explain what you were doing when the problem occurred. Paste the original error text after removing any secrets.

For example, to investigate CSV processing:

When I upload a CSV, the header row is treated as data.
Fix the handling of files with and without a header.
Read the upload code, explain the cause, then fix it and add tests for both cases.

For a terminal error, include the command and its output. For a screen issue, describe the button you pressed and the result you expected.

Investigate without changing code#

You do not have to request a fix immediately. Add “Do not edit files; explain the cause and possible solutions” when you only want an investigation. Use @ to include a particular file.

Check the fix#

Ask Mirr Code to repeat the action that failed and run the relevant tests. For the example above, that means checking the rows produced from a CSV with a header and one without.

Summarize the files changed and checks run.
Include anything you could not verify directly.

If a company system or external service cannot be accessed, you can pass the reproduction steps and findings to its maintainer.

If Mirr Code itself will not start or respond, see Troubleshooting.