If a scratch container is corrupted, the user who owns it will be unable to log in due to null pointer exceptions. The system should at least be tolerant of this fact or preferably recover from it silently.
Checks to be done on each step of the load process (where assumptions on the existence of objects in containers is made) and report errors when they happen so that corrections can be made. With the error identified, corrections may be able to be made.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1884952
Originator: NO
This is also the case for any container, particularly those that a user may have opened when logged out and will open on the next login.
Logged In: YES
user_id=1884952
Originator: NO
Related to:
https://sourceforge.net/tracker/index.php?func=detail&aid=1969220&group_id=223442&atid=1058583
Logged In: YES
user_id=1884952
Originator: NO
Checks to be done on each step of the load process (where assumptions on the existence of objects in containers is made) and report errors when they happen so that corrections can be made. With the error identified, corrections may be able to be made.
Logged In: YES
user_id=2056382
Originator: YES
Container corruption being far less likely now, this bug is less critical.