Klever developer instances are not developer ones
Klever developer instances assume quite many debug options enabled, but deployment scripts do not activate any. This is a very old issue.
Updated by Evgeny Novikov over 1 year ago
- Status changed from Resolved to Closed
Tests passed, so, I merged the branch to master in b33a51eb.
Everybody should use Klever developer instances and Klever experimental instances in the right way! The former is intended just for preliminary evaluation of, say, a newer version of a verification back-end or a new rule specification. Klever developer instances are installed with many debug options enabled, that can help to debug much but also slows down some operations. One shouldn't create large Klever developer instances. For large experiments it is necessary to create production large Klever experimental instances, one or more. In ideal these instances should be immediately dropped after experiments will finish since they don't support updates.