Putting such a course online is a complex task, and bugs could arise from the many different software and hardware platforms involved. If you experience trouble, before doing anything, check the News tab, we will inform you if we are currently experiencing problems on our side. If it is not the case, please go to case A and identify the paragraph that best describes your situation, and then follow the instructions.

Case A: Frequent difficulties with the FUN platform or the Courseware

It is possible that you experience minor inconveniences, here is the regularly updated list of the most common ones with usual solutions when they exist.

• Page loading is slow.

  The platform may simply be handling a lot of students at the moment. Just be patient, or delay your learning session until the situation improves. If it is really unbearable, go to case B.

• Video loading is slow.

  The platform may simply be handling a lot of students at the moment. Just be patient, or delay your learning session until the situation improves. If it is really unbearable, go to case B, or try downloading the videos and slides, so that you can browse them offline.

• The videos won't play.

  If no video plays, go to case B. If just one, try reloading the page and waiting a bit. You can also try downloading the video to play it on your computer. If nothing worked, go directly to case C.

• There is a mistake in the video or subtitles.

  Then use the discussion field underneath that video to tell us. Note that some errors are sometimes present in the video so that we can have you correct them in the exercises, so please check them first :-).

• The pages won't load.

  If no page loads, go to case B. If just one page fails to load, try selecting another tab (for instance, if a problem won't load, try going to and back from the video page). If that doesn't work, it is probable that the FUN platform is experiencing some incident, just retry later, or go to case B.

• The automatic grader hangs at some point and never terminates.

  If it is the case for all problems go to case B. If not, it is probable that the FUN platform is experiencing some incident and that some necessary file, such as the test bench, fails to load. In this case, just retry later, and if it persist, go to case B.

• The problems take a lot of time to be checked.

  The problems are checked by your computer, in your browser, by embedding the OCaml compiler converted to JavaScript and running specific test benches for each problem. That is why we recommend that you use a reasonnably powerful desktop machine. Also, if you are a Web developer, it may be that you let the JavaScript debugger open while on an exercise page. This is known to cause a major slow down.If you really think something is wrong, read the next point.

• There is a problem with the automatic correction or the subject of a problem.

  If you think that the correction report is wrong, or that the text is missing something, use the discussion field underneath that problem to tell us.

• Your problem is not one of the previous ones.

  Then continue to case B.

Case B: Rare difficulties or software interactions with the FUN platform

There are a lot of components that run this MOOC, including human ones, and in rare cases, they might interact in a wrong way. For instance, we might update a problem because someone detected a mistake in the corrector, and the fun server may forget to notify your Web browser that something has to be reloaded. So here are recommendations that you should follow for everything to run as smoothly as possible, and an emergency reset procedure that you can try before submitting a bug report.

• The problem happens while doing something for the first time.

  1. We recommend that you use a desktop computer, not a tablet or a smartphone.
  2. We recommend that you use a recent version of Mozilla Firefox or Google Chrome.
  3. Before doing anything else, try running a recommended environment.
  4. If that solves the problem, but you think that your platform should be supported, feel free to still file a bug report as described in case C.
  5. If not, continue to the next item.

• A problem happens while doing something and that usually works.

  1. Try hard-reloading the page with Ctrl-Shift-R (Command-Shift-R on MacOSX).
  2. Try clear the cache of your browser and reload the page.
  3. Try rebooting your browser.
  4. Wait a few hours and retry.
  5. If nothing worked, continue to case C.

Case C: Bugs that should be reported to us

If none of the previous tricks worked for you, feel free to file a bug report, following the procedure below, so that we won't miss it.

1. Go to the Discussion tab.
2. Select the Bug Reports category.
3. See if your problem happened to someone else.
4. If not, click the New Post button.
5. Select the Bug Reports category.
6. Explain your problem providing as many details as possible: browser, version, page address, debug messages if any, etc..