JOJ/JOJ3
25
6
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

Update FAQ: JOJ3 usage

manuel 2025-09-27 22:42:38 +08:00
parent 8959111ab6
commit 914317ed57
1 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
FAQ%3A-JOJ3-usage.md

@ -1,7 +1,20 @@
# FAQ JOJ3
**Q: I pushed my code, then what?**
**Q: my program exits with a "weird" error status and a number. What does it mean?**
A: Check the `Issues` tab in your Gitea repository, you should have received a new issue with all the details related to your last commit. This will be updated on the next push for this task, don't close it. You can also check the `Actions` tab to check more detailed logs of the run, however these information is unlikely useful to students.
**Q: Gitea shows a "red cross" and I have no idea where it comes from, what should I do?**
A: A "red cross" means something "serious" happened, e.g. failed to pass health check or the source code could not compile or your program crashed while only running code is accepted. There could be many reasons... To find out your problem, check the newly updated/opened issue, carefully read the provided information, and fix your problem accordingly. Usually submissions with a red cross are considered as failed and are not graded.
**Q: Health check reports non-ASCII charcaters, but I cannot see any, it must be wrong!**
A: While JOJ3 and health check could have bugs, we have not seen any false positive so far, i.e. all files reported with non-ASCII characters indeed featured UTF-8 characters. Depending on the file having non-ASCII characters Gitea might highlight them. There are many other ways to detect non-ASCII characters, for instance in (n)vim you can search for the pattern `[^\x00-\x7F]`. If you're not using (n)vim search online for more examples.
**Note.** Most common non-ASCII characters are Chinese characters, the Chinese equivalent to `-` or `:` can be tricky to spot.
**Q: My program exits with a "weird" error status and a number. What does it mean?**
A: A working program should return with status (or code) 0. If something unexpected is happening JOJ or the OS might be sending a *signal* to your program. To understand what went wrong, run the following command `kill -L`. It lists all the signal names in a table. Check the name of the signal corresponding to the number you see in your Gitea issue and run a quick online search.