This is somehow a corner case, since you probably won't encounter it unless you are switching between Toaster modes. It is a bug nonetheless, so there it goes. Steps to reproduce: 1. Start toaster in build (managed) mode and visit the all builds page 2. Stop toaster 3. Source the environment script 4. Start Toaster in analysis (interactive) mode 5. If you are redirected to the no builds state, type this url in your browser localhost:8000/toastergui/builds The page fails to load. This is the trace: Environment: Request Method: GET Request URL: http://127.0.0.1:8000/toastergui/builds/?count=10&orderby=updated%3A-&page= 1 Django Version: 1.6 Python Version: 2.7.6 Installed Applications: ('django.contrib.staticfiles', 'django.contrib.humanize', 'orm', 'toastermain', 'south', 'bldviewer', 'toastergui', 'bldcontrol') Installed Middleware: ('django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware') Traceback: File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py" in get_response 114. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/home/yocto/master/bitbake/lib/toaster/toastergui/views.py" in builds 3139. (filter_string, search_term, ordering_string) = _search_tuple(request, Build) File "/home/yocto/master/bitbake/lib/toaster/toastergui/views.py" in _search_tuple 216. raise BaseException("Invalid ordering model:" + str(model) + str(invalid)) Exception Type: BaseException at /toastergui/builds/ Exception Value: Invalid ordering model:<class 'orm.models.Build'>(u'updated', ['bitbake_version', 'build_name', 'buildartifact', 'buildrequest', 'completed_on', 'cooker_log_path', 'distro', 'distro_version', 'errors_no', 'helptext_build', u'id', 'layer_version_build', 'logmessage', 'machine', 'outcome', 'package', 'project', 'started_on', 'target', 'task_build', 'timespent', 'variable_build', 'warnings_no'])
This is a side-effect of using cookies to store the page state. Since in managed mode we have server-side session support, we need to switch the implementation to use session to remember user search/orderby preferences. This is doable after we split the applications for managed mode and analysis mode in 1.9. Deferring bug to 1.9, after the build and analysis mode applications are split.
Moved to Michael, to be included in the UI frontend refactoring.
Since 7449 was not implemented, please confirm this bug is obsolete too.
Please recheck this during 2.1
This should be fixed by the work that has been done to consolidate the two modes and re-use a proper project for analysis mode/command line builds.
obsolete.