If after the exception described in #131419 occurs, I try closing the project, an assertion error occurs (see the stack
Created attachment 59300 [details]
The reason is that the creation of MethodImpl instance was broken: there was an exception in constructor (see issue
#131419). There fore the visibility field was not initialized and was left null.
When writing such object to persistence, an exception occurs.
Judging by code, if assertions are off (which is the case in the end user variant), then null is stored to persistence
correctly and restored upon reopen; so user won't see this assertion or related exception.
That's why I leave it a P3.
Assertion is P2 bug
Code model IMHO has a serious implementation bug:
"There are no factory for code mode objects".
All objects are constructed by constructor that has too many responsibilities such as rendering object parameters,
putting on repository, registering in project.
Assertion/error on any phase of constructing object results in an intermediate state of model/repository.
The bug is example of this. Object was put on repository but rendering was failed and object wasn't created.
So the bug is a consequence of #131419.
The fix for #131419 resolve such situation.
I believe that bug fixed.
cannot reproduce this bug
verified in trunk (Build 200804230004)
Please provide information about changeset which fixed this issue in main. Without this information it cannot be
backported into NB 6.1 Patch 1.
fixed in relese61_fixes branch by backporting of IZ 131419 fix