Situation: A Codio assessment runs a student's script. If that script prints something html-like it is not shown within the Assessment output in the Codio Guide.
Example: Suppose in Python the student prints the type of something (e.g. type(1) ). Then Python outputs something with angle brackets, in this case:
But that is not seen within the Codio guide. I think because the Codio guide is trying to interpret it as html.
This may not actually be a rare problem. When code does not work as you expect a basic debugging strategy is to print out variables and their types, to ensure they are as you think. This is particularly common with a dynamically types programming language like Python. So I could see students running into this.
Of course, the immediate solution is to encourage students to debug their code on the command line rather than by rerunning Guide assessment scripts.