linux/poky.git/bitbake/lib/toaster/toastermain, branch yocto-2.2.3

bitbake: toaster: settings set ALLOWED_HOSTS to * in debug mode

2016-11-16T11:38:51+00:00

As of Django 1.8.16, Django is rejecting any HTTP_HOST header that is not on the ALLOWED_HOST list. We often need to reference the toaster server via a fqdn, if we start it via webport=0.0.0.0:8000 for instance, and are hitting the server from a laptop. This change does reduce the protection from a DNS rebinding attack, however, if you are running the toaster server outside a protected network, you should be using the production instance. [YOCTO #10578] (Bitbake rev: 59a3f391ac5ac194f30d11a39676356464269d55) Signed-off-by: brian avery Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: tests Rename test settings to python compliant name and fix import

2016-06-15T07:35:06+00:00

Use underscore instead of dash in the file name for the test settings. Also fix the import of the settings module. (Bitbake rev: 0bdfcafdd1e2ebc10dc0cd343c8bb77f09a71c90) Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: read timezone files in binary mode

2016-06-02T07:24:04+00:00

Used 'rb' mode to open files to avoid unicode error when code runs on python 3: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 44: invalid start byte [YOCTO #9584] (Bitbake rev: 1414866b84fe1fd674ea79500cd62eda3aa30b33) Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

bitbake: toaster: Add a specific test settings file

2016-05-20T09:09:02+00:00

When running certain tests we want a particular database specified. When bitbake toaster ui is being tested pass it these test settings so that it uses the same database as the unit tests running. (Bitbake rev: c52e34cac4362ba0a3cb3ea1fcb639e1d802aa85) Signed-off-by: Michael Wood Signed-off-by: Elliot Smith Signed-off-by: Richard Purdie

bitbake: toaster: Remove DATABASE_URL being passed around as an environment var

2016-05-20T09:09:02+00:00

We don't need to pass the DATABASE_URL around and read it back if we setup the django framework in the correct way. We make the default sqlite database path a full path so that the database isn't being assumed to be in CWD. Also add some more useful comments on the database settings. This is preparation work to migrate the build tests and be able to trigger builds on differently configured databases. (Bitbake rev: 973c740404ca6a09feea250d3433075995067fe0) Signed-off-by: Michael Wood Signed-off-by: Elliot Smith Signed-off-by: Richard Purdie

bitbake: toaster: use 'in' instead of has_key

2016-05-14T22:05:15+00:00

Dictionary method has_key is deprecated in python 2 and absent in python 3. Used ' in ' statement to make the code working on both python 2 and python 3. [YOCTO #9584] (Bitbake rev: 3d7ad7ba0d1a6f688ae885817c049f2a8ced11b5) Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

bitbake: bin, toaster: Fix print and exception syntax

2016-05-11T09:34:30+00:00

This updates the print "" syntax to print() and fixes some exception handling syntax such that its compatible with python v2 and v3. (Bitbake rev: 58304fcce9727fd89564436771356c033ecd22a3) Signed-off-by: Richard Purdie

bitbake: bitbake: Update logger.warn() -> logger.warning()

2016-05-11T09:34:30+00:00

python deprecated logger.warn() in favour of logger.warning(). This is only used in bitbake code so we may as well just translate everything to avoid warnings under python 3. Its safe for python 2.7. (Bitbake rev: 676a5f592e8507e81b8f748d58acfea7572f8796) Signed-off-by: Richard Purdie

bitbake: toaster: Enable Image Customisation feature

2016-02-10T13:29:22+00:00

Remove environment variable to toggle Image customisation feature (Bitbake rev: 2e9c86229b8f924a5b62987f4b166f63392f12e8) Signed-off-by: Michael Wood Signed-off-by: brian avery Signed-off-by: Richard Purdie

bitbake: toastergui: fix error and warning counts for builds

2016-01-15T16:30:01+00:00

The error and warning counts displayed for builds were counts of the errors and warnings objects associated with a build. Because these values were being derived on the fly, it was not possible to sort by them. Previously, the 3rd party django-aggregate-if library was used to add aggregate fields to Build objects and should then have been used to populate the "all builds" and "project builds" tables. However, at some point the templates had changed so that the error and warning counts were coming from the properties on the Build model and not from these aggregates. This meant that it was not possible to sort by these fields. Django 1.8 supports conditional aggregates in annotation fields on querysets. This means we can remove django-aggregate-if, use the new Django 1.8 feature to derive errors_no and warnings_no fields as annotations, then use those annotation fields in the templates. This makes the "builds" tables sortable again. [YOCTO #8738] (Bitbake rev: 9be7c5c18b325f6ed40bc431ac408db242007eb1) Signed-off-by: Elliot Smith Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie