Klever

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

Nobody has button "upload job". Button "upload jobs" is used for a single job upload also. If administrator doesn't have an access to upload jobs then he would get and error "You don't have an access to upload jobs" if he try to upload any job. Buttons in main menu are fixed. Rejected.

Let's Vladimir will do this after his vacation.

Implemented in bridge-2.0.

Vladimir Gratinskiy wrote:

As admin now doesn't have population rights, there is no need to populate manager user (as manager is already exists if population page is loaded). So this form can be deleted from population page.

This is a good idea. Indeed, for the most of Klever instances Manager and Service user are populated in advance by means of manage.py task PopulateUsers that is invoked automatically by deployment scripts. For the rest instances we can easily request to follow this way as well.

Fixed in "bridge-2.0".

When opening a page pointing to a non-existing job, e.g. http://localhost:8998/jobs/100/, Bridge 2.0 raises the following exception:

No job found matching the query
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/django/views/generic/detail.py", line 51, in get_object
    obj = queryset.get()
  File "/usr/lib/python3.6/site-packages/django/db/models/query.py", line 403, in get
    self.model._meta.object_name
jobs.models.DoesNotExist: Job matching query does not exist.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/django/core/handlers/base.py", line 126, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/usr/lib/python3.6/site-packages/django/views/generic/base.py", line 69, in view
    return self.dispatch(request, *args, **kwargs)
  File "/usr/lib/python3.6/site-packages/django/utils/decorators.py", line 62, in _wrapper
    return bound_func(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view
    return view_func(request, *args, **kwargs)
  File "/usr/lib/python3.6/site-packages/django/utils/decorators.py", line 58, in bound_func
    return func.__get__(self, type(self))(*args2, **kwargs2)
  File "/home/novikov/work/klever/bridge/tools/profiling.py", line 185, in dispatch
    response = getattr(super(), 'dispatch')(request, *args, **kwargs)
  File "/usr/lib/python3.6/site-packages/django/views/generic/base.py", line 89, in dispatch
    return handler(request, *args, **kwargs)
  File "/usr/lib/python3.6/site-packages/django/views/generic/detail.py", line 105, in get
    self.object = self.get_object()
  File "/usr/lib/python3.6/site-packages/django/views/generic/detail.py", line 54, in get_object
    {'verbose_name': queryset.model._meta.verbose_name})
django.http.response.Http404: No job found matching the query

That exception was caught. But anyway in birdge-2.0 I've fixed it so default "Page not found" will be shown (not only for jobs, but for all "Detail" views). Later I'll add custom pages for "not found" and "forbidden" errors. And will change some errors processing.

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