Project

General

Profile

Bug #9064

Klever developer instances are not developer ones

Added by Evgeny Novikov about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Urgent
Category:
Deployment
Target version:
Start date:
07/05/2018
Due date:
% Done:

0%

Estimated time:
Detected in build:
svn
Platform:
Published in build:

Description

Klever developer instances assume quite many debug options enabled, but deployment scripts do not activate any. This is a very old issue.


Related issues

Related to Klever - Bug #9090: Create production instances of Klever locally if necessaryClosed07/11/2018

Actions
Related to Klever - Feature #9094: Optimize creature of single Klever experimental instanceClosed07/11/2018

Actions
Related to Klever - Feature #9095: Fail earlier if some Klever experimental instances existClosed07/11/2018

Actions

History

#1

Updated by Evgeny Novikov about 1 year ago

  • Related to Bug #9090: Create production instances of Klever locally if necessary added
#2

Updated by Evgeny Novikov about 1 year ago

  • Related to Feature #9094: Optimize creature of single Klever experimental instance added
#3

Updated by Evgeny Novikov about 1 year ago

  • Status changed from New to Resolved

Fixed in branch fix-9064.

#4

Updated by Evgeny Novikov about 1 year ago

  • Related to Feature #9095: Fail earlier if some Klever experimental instances exist added
#5

Updated by Evgeny Novikov about 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.

Also available in: Atom PDF