Click or drag to resize

Known Errors and Problems

This section lists real errors or inadequacies. A consistent prioritisation does not take place.

  • The first launch of Vishnu after a Windows restart may take a very long time - up to 45 seconds, before the splash screen even appears. Background: Windows checks all newly loaded EXEs and DLLs for viruses.

  • The Vishnu-Installer (ClickOnce) was deactivated after migration to .Net 7. A better solution must be found here in the long term (see also Collection of Ideas).

  • The VSIX-Templates to support the creation of your own Vishnu-Checkers and User controls have been made functional again after migration to .Net 7, but raise error messages during the generation of new projects. Nevertheless, everything works.

  • If the log directory is on a network drive and the network is temporarily unavailable Vishnu terminates immediately.

  • An exclusive-or problem may occur with workers. Error messages and OK messages can sometimes occur with higher-level jobs, if the causative sub-nodes do not trigger at exactly the same time (see ...\VishnuHome\Tests\TestJobs\Testprotokoll.xls and there CheckDependentNodeLogic). There is a workaround via Escalators.

  • The implementation of the simple threshold logic (Treshold) in Vishnu only allows discrete, predefined threshold values. Operators can be TR10, TR20, TR30, ... , TR80, TR90 and therefore only analogue percentage values. An operator with variable percentage values would be better.

  • There is not yet a solution for the automated truncation of log files of the CheckerHistoryLoggers. The log files simply continue to grow indefinitely.

  • ProductionJobProvider revise

    The ProductionJobProvider is still spaghetti code - structure it and use json job descriptions as additional option.

  • Screen display

    Vishnu is no longer centered after the first switch to the jobs view and back, but with the same top left corner as the jobs view previously displayed.

    If the switch SizeOnVirtualScreen is set t true, If Vishnu currently extends over several screens (SizeOnVirtualScreen is true) and then you save the screen display, Vishnu will still only be displayed on the last active screen after retart.

See also