Klever

The problem was in console start job decision. There were no checks if logger formatters are empty strings (it was in javascript only). I'v added new checks in fix_9028.

Now it works, so, I merged the branch to master in 4a72a3d4.

Now I get another exception when starting a job decision through a command-line interface:

[28.Jun.2018 15:45:26] 'NoneType' object is not subscriptable
Traceback (most recent call last):
  File "/var/www/klever-bridge/bridge/CustomViews.py", line 61, in dispatch
    return getattr(super(), 'dispatch')(request, *args, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/django/views/generic/base.py", line 89, in dispatch
    return handler(request, *args, **kwargs)
  File "/var/www/klever-bridge/bridge/CustomViews.py", line 94, in post
    return JsonResponse(self.get_context_data())
  File "/var/www/klever-bridge/jobs/views.py", line 502, in get_context_data
    self.request.user, self.kwargs['job_id'], jobs.utils.GetConfiguration(**getconf_args).configuration
  File "/var/www/klever-bridge/service/utils.py", line 815, in __init__
    self.job_scheduler = self.__get_scheduler()
  File "/var/www/klever-bridge/service/utils.py", line 895, in __get_scheduler
    return Scheduler.objects.get(type=self.data[0][1])
TypeError: 'NoneType' object is not subscriptabl

The command to run is:

./src/utils/bin/start-solution.py --rundata job-decision-conf.json "Testing environment model specifications" --host localhost:8998 --username manager --password manager

Also, I attached job-decision-conf.json.

As far as you are planning large changes, we can't include them into Klever 1.0. So, let's just live with a small issue.

This issue is not strictly bound with purposes of 2.0 that targets verification of C software.

Done in branch "fix_9028". Now it's much easier to track what is wrong in configuration. Error logs are clearer.

Tests passed, so, I merged the branch to master in 1d74aff6f.

Please, do not forget to migrate your local databases!