Report bugs and problems of Viivi < Viivi's Cell < Entrance
Please report bugs and problems of Viivi when you find them to improve it.
Thank you very much in advance for your cooperation.
Currently, fixing problems of Viivi IDE has higher priority.
Please note that problems of Viivi kernel,
except for important ones,
will be worked on after Viivi IDE is all fixed.
And note that, as well as the copyright of the original body of Viivi, the copyright of the parts of Viivi modified based on users' reports still belong to the author ilma <ilma@viivi.io>.
The following items are common for all kinds of reports:
For each specific kind of problem, see one of the corresponding cases below:
When it is a bug that Viivi could not predict,
a JVM Exception is directly shown as
Exception in thread ...
.
Following this, the contents on the JVM stack are shown as well.
Please send me a copy of all the output.
When Viivi recognizes it as a system error,
a system-error message with a system-error ID F#####
is shown.
Please send me a copy of all the output.
With no exceptions or system errors,
you may find the evaluation results or the IDE behaviors strange.
(For example, the resulted value is different from that on the textbook;
the response of the IDE is not that you expected; and so on.)
Please tell me BOTH of
"the evaluation-result or IDE-response actually occurred on Viivi"
and "the right evaluation-result or IDE-response that you expected".
Report bugs and problems of Viivi < Viivi's Cell < Entrance
Exhibited on 2010/10/24
Updated on 2022/03/02
Copyright(C) 2003-2022 ilma <ilma@viivi.io> All rights reserved.