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

Update FAQ: JOJ3 usage

manuel 2025-10-04 10:57:11 +08:00
parent 10a9e842b8
commit 02796075c2
1 changed files with 12 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
FAQ%3A-JOJ3-usage.md

@ -1,20 +1,17 @@
# JOJ3 FAQ
## JOJ usage
**Q: I pushed my code, then what?**
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: After pushing my code and reading the issue I have a question, what should I do?
A: Ask your question to the right people. If your question is related to your program or code, then ask to your teaching team, i.e. don't contact JOJ developers. Only directly contact JOJ developers if you are sure the issue is related to JOJ and not to its setup. In particular, always discuss first with your teaching team and only contact JOJ developers if the teaching team is unable to help. In such as case report your issue on Mattermost in [JOJ support channel](https://focs.ji.sjtu.edu.cn/mm/joj/channels/town-square).
Never ask to both your teaching team and JOJ developers **at the same time**, this will waste not only your time but also the one of the people trying to help you.
**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.
**: I failed the health check, how bad is it?**
**Q: I failed the health check, how bad is it?**
A: This is very bad, it means your work has been rejected even before being checked! The health check ensures you don't mess your repository too much and blocks you in case you did something very bad. So check the details, and follow the provided guidance to fix your issue. If you think the problem is not on your side, then contact your teaching team for further support.
@ -32,6 +29,14 @@ A: A working program should return with status (or code) 0. If something unexpec
A: When running test cases two things can happen: (i) you pass, ie. your output matches the expected sample or (ii) you failed, ie. there are differences between your output and the expected sample. Extra lines are marked with `+` while missing ones appear with a `-`.
## Communication
**Q: After pushing my code and reading the issue I have a question, what should I do?**
A: Ask your question to the right people. If your question is related to your program or code, then ask to your teaching team, i.e. don't contact JOJ developers. Only directly contact JOJ developers if you are sure the issue is related to JOJ and not to its setup. In particular, always discuss first with your teaching team and only contact JOJ developers if the teaching team is unable to help. In such as case report your issue on Mattermost in [JOJ support channel](https://focs.ji.sjtu.edu.cn/mm/joj/channels/town-square).
**Note.** Never ask to both your teaching team and JOJ developers **at the same time**, this will waste not only your time but also the one of the people trying to help you.
**Q: I found a bug, what should I do?**
A: First make sure this is really a bug, then open an issue in course-support to report it. We will come back to you for more details if necessary. You can also directly contact us on Mattermost in [JOJ comments and feedback channel](https://focs.ji.sjtu.edu.cn/mm/joj/channels/off-topic) for quick question and only fill in a full bug report once the bug is confirmed.