Bug #9064
closed
Klever developer instances are not developer ones
Added by Evgeny Novikov almost 6 years ago.
Updated almost 6 years ago.
Description
Klever developer instances assume quite many debug options enabled, but deployment scripts do not activate any. This is a very old issue.
- Related to Bug #9090: Create production instances of Klever locally if necessary added
- Related to Feature #9094: Optimize creature of single Klever experimental instance added
- Status changed from New to Resolved
Fixed in branch fix-9064.
- Related to Feature #9095: Fail earlier if some Klever experimental instances exist added
- 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.
Also available in: Atom
PDF