beat.web issueshttps://gitlab.idiap.ch/beat/beat.web/-/issues2022-03-04T09:39:15Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/577Cleanup yearly supervision command2022-03-04T09:39:15ZFlavio TARSETTICleanup yearly supervision commandThe yearly supervison command needs a rewrite to improve clarityThe yearly supervison command needs a rewrite to improve clarityCode cleanuphttps://gitlab.idiap.ch/beat/beat.web/-/issues/567Dead code removal2020-09-28T09:20:24ZSamuel GAISTDead code removalSome code in this repository is no longer used.
For example scripts/scheduler.py. It has been replaced with Django management commands to take advantage of the ZMQ communication system.
Therefore, everything that is unused should be re...Some code in this repository is no longer used.
For example scripts/scheduler.py. It has been replaced with Django management commands to take advantage of the ZMQ communication system.
Therefore, everything that is unused should be removed.Code cleanuphttps://gitlab.idiap.ch/beat/beat.web/-/issues/563Code deduplication2020-09-09T09:41:33ZSamuel GAISTCode deduplicationThere are several places in beat/beat.web> where there is code duplication.
For example all interactive management commands follow the same structure and re-implement the `get_input_data`. This is typically a case where there should be ...There are several places in beat/beat.web> where there is code duplication.
For example all interactive management commands follow the same structure and re-implement the `get_input_data`. This is typically a case where there should be a base class for that.
This would have avoided a mix of raw_input and input usage because of Python 2 VS Python 3 implementations.Code cleanuphttps://gitlab.idiap.ch/beat/beat.web/-/issues/553toolchain created locally does not show up correctly on beat.web2022-03-04T09:39:11ZAmir MOHAMMADItoolchain created locally does not show up correctly on beat.webThis toolchain [1.json](/uploads/49903eb5d5e5223a6f191a8656049ba8/1.json) also available here: https://www.idiap.ch/software/beat/platform/toolchains/amohammadi/livdet/1/#viewer does not show up correctly in the web platform but looks ok...This toolchain [1.json](/uploads/49903eb5d5e5223a6f191a8656049ba8/1.json) also available here: https://www.idiap.ch/software/beat/platform/toolchains/amohammadi/livdet/1/#viewer does not show up correctly in the web platform but looks ok in beat.editor:
![image](/uploads/dfbfc0c76547e04de4db701dacb356c9/image.png)https://gitlab.idiap.ch/beat/beat.web/-/issues/536Some of the Models defined in django are not well documented2019-09-05T11:36:57ZZohreh MOSTAANISome of the Models defined in django are not well documentedThe "swagger.yaml" file that includes the beat.web api information that can be rendered into the sphinx documentation does not include complete information for all the models included in a response object. Some of the basic ones are show...The "swagger.yaml" file that includes the beat.web api information that can be rendered into the sphinx documentation does not include complete information for all the models included in a response object. Some of the basic ones are shown though which means that the package produces this yaml file is working as expected.
It seems that those objects which are not shown, are not well documented in the code and because there are several layers of inheritance for each class, it is difficult to find where exactly the problem lies.
With a brief discussion with @samuel.gaist we tried something fast but it did not work. It required a deeper dive into the implementation.https://gitlab.idiap.ch/beat/beat.web/-/issues/533Strange behaviour concerning a POST method that needed to be GET.2019-08-22T15:38:08ZZohreh MOSTAANIStrange behaviour concerning a POST method that needed to be GET.In the `api.py` file for `report`, there are two classes that have POST methods which in fact should have been GET.
`ReportRSTCompileView` and `ReportRSTCompileAnonView`. The definitions are here:
https://gitlab.idiap.ch/beat/beat.web/b...In the `api.py` file for `report`, there are two classes that have POST methods which in fact should have been GET.
`ReportRSTCompileView` and `ReportRSTCompileAnonView`. The definitions are here:
https://gitlab.idiap.ch/beat/beat.web/blob/master/beat/web/reports/api.py
Both of the mentioned classes are using another method `compileTextItem` defined in `models.py`. This function is not readable and it raises an exception error `"Error in ReportRSTCompileView: The Python docutils library isn't installed."` which does not seem to belong here. The definition is here:
https://gitlab.idiap.ch/beat/beat.web/blob/master/beat/web/reports/models.pyhttps://gitlab.idiap.ch/beat/beat.web/-/issues/494Move plot generation code into beat.cmdline2018-03-15T08:47:16ZJaden DIEFENBAUGHMove plot generation code into beat.cmdlineThis ties in with beat.cmdline#16: moving the plotting code there will let users of beat.cmdline/beat.editor use the same plot generation functionality as found in beat.web.This ties in with beat.cmdline#16: moving the plotting code there will let users of beat.cmdline/beat.editor use the same plot generation functionality as found in beat.web.https://gitlab.idiap.ch/beat/beat.web/-/issues/493[experiments] Cannot start a new experiment if site is empty2018-01-16T10:07:28ZAndré Anjos[experiments] Cannot start a new experiment if site is emptyIf the platform has no experiments registered (as it was the case for the staging platform a few instants ago), the bar which contains the "New" button is not displayed on the experiment list page. The only way to create a new experiment...If the platform has no experiments registered (as it was the case for the staging platform a few instants ago), the bar which contains the "New" button is not displayed on the experiment list page. The only way to create a new experiment in these conditions is to go to the toolchains list package and start a new experiment from there.https://gitlab.idiap.ch/beat/beat.web/-/issues/484[backend] Not all available resources are being utilised2017-12-04T10:47:12ZAndré Anjos[backend] Not all available resources are being utilisedFor some reason, there are experiments being scheduled and get stuck on apparent lack of resources. Meanwhile, there are idle computers on the system that seem to not take any jobs:
![image](/uploads/f0771efaf35e733b2fa76b7821a9b7f1/ima...For some reason, there are experiments being scheduled and get stuck on apparent lack of resources. Meanwhile, there are idle computers on the system that seem to not take any jobs:
![image](/uploads/f0771efaf35e733b2fa76b7821a9b7f1/image.png)Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/483[experiments] Not allowed to share unfinished experiments2017-12-04T10:46:41ZPavel KORSHUNOV[experiments] Not allowed to share unfinished experimentsI forked the experiment, modified an algorithm, started the experiment, and tried to share it with @sebastien.marcel but got the error that "This experiment is not done yet", then it went to "page not found" page.
Here is the experiment...I forked the experiment, modified an algorithm, started the experiment, and tried to share it with @sebastien.marcel but got the error that "This experiment is not done yet", then it went to "page not found" page.
Here is the experiment:
https://www.beat-eu.org/platform/experiments/pkorshunov/pkorshunov/speech-pad-simple/1/speech-pad_lbp_hist_ratios_lr-pa_aligned-rr4/
Here is the error, when tried to share it:
![Screen_Shot_2017-12-04_at_11.11.13](/uploads/8e927c930758d1f1805658c26c8abf36/Screen_Shot_2017-12-04_at_11.11.13.png)https://gitlab.idiap.ch/beat/beat.web/-/issues/482[experiments] Environment "previous" relationship is not honoured by experime...2017-12-04T10:47:30ZAndré Anjos[experiments] Environment "previous" relationship is not honoured by experiment configuratorThe "Environment" objects have a "Previous Version" entry that point to environments they are suceeding. This information should be used by the experiment configurator to select reasonable defaults when the user forks an experiment that ...The "Environment" objects have a "Previous Version" entry that point to environments they are suceeding. This information should be used by the experiment configurator to select reasonable defaults when the user forks an experiment that uses outdated environments.
My recollection is that was the case, but if I fork an experiment using "Scientific Python (0.1.0)", the default selector does not point to "Scientific Python (1.0.0)". It would be great if that was the case.
Example: https://www.beat-eu.org/platform/experiments/pkorshunov/pkorshunov/speech-pad-simple/1/speech-pad_lbp_hist_ratios_lr-pa_aligned/
Just fork it and check the default environment on the Global Parameters.Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/480[search] Table sorting seems broken2017-12-04T10:47:47ZAndré Anjos[search] Table sorting seems brokenApparently, table sorting does not seem to work correctly at the Search web page with respect to some (numerical) columns. The table ordering seems consistent for text based columns though.
How to reproduce: If I search for "eigenface" ...Apparently, table sorting does not seem to work correctly at the Search web page with respect to some (numerical) columns. The table ordering seems consistent for text based columns though.
How to reproduce: If I search for "eigenface" then filter the search so to be able to get the EER displayed for all experiments, then click on EER does not seem to correctly rank the results.
I'm using Safari on OSX (this may be -part of- the issue).
Here is a sample of the result:
![Screen_Shot_2017-11-29_at_14.10.59](/uploads/d4c1d88295a47563aad34abb7cba53dd/Screen_Shot_2017-11-29_at_14.10.59.png)
As you can see the EER column is selected in ascending mode, but the value 0.07... comes befomre 0.06.
@philip.abbet: can you check if a fix is possible?Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/477In the experiment list view, experiments that participate on Reports are not ...2017-09-28T08:42:03ZAndré AnjosIn the experiment list view, experiments that participate on Reports are not flaggedIn the experiments list view, we have an icon that indicates if an experiment has an associated attestation-lock or a public attestation. That gives the user a notion if the assets of the said experiment are locked (frozen).
Experiments...In the experiments list view, we have an icon that indicates if an experiment has an associated attestation-lock or a public attestation. That gives the user a notion if the assets of the said experiment are locked (frozen).
Experiments that participate in a report are also "locked" (frozen assets), but that information is not shared on the experiment list view. It would be nice if one could see this information as well.Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/476C++ environment has no documentation2017-09-28T08:43:21ZAndré AnjosC++ environment has no documentationThe current version of the C++ environment at the production platform has no associated documentation.
We should explain there what it is and maybe have links to the different software toolkits and instructions on how to produce a binar...The current version of the C++ environment at the production platform has no associated documentation.
We should explain there what it is and maybe have links to the different software toolkits and instructions on how to produce a binary that is compatible with it.Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/475New version or fork of algorithm with RST URL gets buggy documentation2017-09-27T14:52:17ZAndré AnjosNew version or fork of algorithm with RST URL gets buggy documentationIf you fork or copy an algorithm that has documentation in restructured text format containing an URL such as `My test <http://example.com>`, the copy or fork will end-up with `&lt;` and `&gt;` characters in the place of `<` and `>` and ...If you fork or copy an algorithm that has documentation in restructured text format containing an URL such as `My test <http://example.com>`, the copy or fork will end-up with `<` and `>` characters in the place of `<` and `>` and will produce an annoying warning.
Example: Try to fork `tutorial/dct/3` (https://www.beat-eu.org/platform/algorithms/tutorial/dct/3/), then, edit the fork documentation.Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/474Instructions for publishing attestations not very clear2017-09-27T14:40:18ZJaden DIEFENBAUGHInstructions for publishing attestations not very clearHello,
I got an email from beat saying that the attestation of my experiment is about to expire.
"More details: http://www.beat-eu.org/platform/attestations/232222665/"
The message informs me that if I don't take any action, the attestat...Hello,
I got an email from beat saying that the attestation of my experiment is about to expire.
"More details: http://www.beat-eu.org/platform/attestations/232222665/"
The message informs me that if I don't take any action, the attestation will be deleted [soon].
But it does not tell me what actions I could take.
The link on the "more details" line takes me to the attestation of the experiment in question.
Here again, I see the following information at the beginning of the page:
"
Created 5 months, 3 weeks ago, Jan. 5, 2017, 5:28 p.m.
Expires in 5 days, 6 hours from now, on July 4, 2017, 5:28 p.m. (unlock it to make it permanent)
Experiment: sbhatta/ivana7c/simple-antispoofing-updated/1/replay2-antispoofing-lbp-histograms
Description: Face antispoofing using comparison of LBP histograms
"
The second line says "unlock it to make it permanent", but I could not understand what "unlock it" means.
Finally, someone explained to me that I have to click on the yellow-star-wheel to "Publish" it.
Overall, I found the instructions not very clear.
I would expect the text "unlock it to make it permanent" to be an active link, which would lead to
the appropriate action.
Regards
Sushilhttps://gitlab.idiap.ch/beat/beat.web/-/issues/464Chrome headless for more stable & CI-supported E2E testing2017-08-06T16:44:50ZJaden DIEFENBAUGHChrome headless for more stable & CI-supported E2E testingE2E testing currently uses a locally-installed browser and cannot be ran on a headless CI. Using a locally-installed browser is:
1. annoying
2. resource-intensive
3. not feasible on CI
Chrome has recently started to support running the ...E2E testing currently uses a locally-installed browser and cannot be ran on a headless CI. Using a locally-installed browser is:
1. annoying
2. resource-intensive
3. not feasible on CI
Chrome has recently started to support running the browser headlessly, which will fix these issues. However, it's not very well supported yet (still Alpha~Beta stage). This is a tracking issue for widespread support.
See:
- https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md
- https://www.chromestatus.com/feature/5678767817097216https://gitlab.idiap.ch/beat/beat.web/-/issues/463db IntegrityError when adding user from Django admin with non-default account...2017-08-06T16:44:51ZJaden DIEFENBAUGHdb IntegrityError when adding user from Django admin with non-default account settings#### What
Going to the Django admin page for the Users model and creating a new user always fails if any combination of the four options under "Account Settings # 1" are unchecked.
#### Configs
- local development (SQLite backend)
- Cle...#### What
Going to the Django admin page for the Users model and creating a new user always fails if any combination of the four options under "Account Settings # 1" are unchecked.
#### Configs
- local development (SQLite backend)
- Clean `./bin/django install` db on master branch
#### Traceback
```
Internal Server Error: /admin/auth/user/add/
Traceback (most recent call last):
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 149, in get_response
response = self.process_exception_by_middleware(e, request)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 147, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/admin/options.py", line 541, in wrapper
return self.admin_site.admin_view(view)(*args, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 149, in _wrapped_view
response = view_func(request, *args, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/views/decorators/cache.py", line 57, in _wrapped_view_func
response = view_func(request, *args, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/admin/sites.py", line 244, in inner
return view(request, *args, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 67, in _wrapper
return bound_func(*args, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper
return view(request, *args, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 63, in bound_func
return func.__get__(self, type(self))(*args2, **kwargs2)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 67, in _wrapper
return bound_func(*args, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 149, in _wrapped_view
response = view_func(request, *args, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 63, in bound_func
return func.__get__(self, type(self))(*args2, **kwargs2)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 184, in inner
return func(*args, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/auth/admin.py", line 128, in add_view
extra_context)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/admin/options.py", line 1437, in add_view
return self.changeform_view(request, None, form_url, extra_context)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 67, in _wrapper
return bound_func(*args, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 149, in _wrapped_view
response = view_func(request, *args, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 63, in bound_func
return func.__get__(self, type(self))(*args2, **kwargs2)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 184, in inner
return func(*args, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/admin/options.py", line 1379, in changeform_view
self.save_related(request, form, formsets, not add)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/admin/options.py", line 1015, in save_related
self.save_formset(request, form, formset, change=change)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/admin/options.py", line 1003, in save_formset
formset.save()
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/forms/models.py", line 645, in save
return self.save_existing_objects(commit) + self.save_new_objects(commit)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/forms/models.py", line 775, in save_new_objects
self.new_objects.append(self.save_new(form, commit=commit))
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/forms/models.py", line 913, in save_new
obj.save()
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/models/base.py", line 708, in save
force_update=force_update, update_fields=update_fields)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/models/base.py", line 736, in save_base
updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/models/base.py", line 820, in _save_table
result = self._do_insert(cls._base_manager, using, fields, update_pk, raw)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/models/base.py", line 859, in _do_insert
using=using, raw=raw)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/models/manager.py", line 122, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/models/query.py", line 1039, in _insert
return query.get_compiler(using=using).execute_sql(return_id)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 1060, in execute_sql
cursor.execute(sql, params)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/backends/utils.py", line 79, in execute
return super(CursorDebugWrapper, self).execute(sql, params)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/backends/utils.py", line 64, in execute
return self.cursor.execute(sql, params)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/utils.py", line 95, in __exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/backends/utils.py", line 64, in execute
return self.cursor.execute(sql, params)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/backends/sqlite3/base.py", line 323, in execute
return Database.Cursor.execute(self, query, params)
IntegrityError: UNIQUE constraint failed: accounts_accountsettings.owner_id
[21/Apr/2017 15:39:18] "POST /admin/auth/user/add/ HTTP/1.1" 500 255813
```
#### Django error page
[IntegrityError_at_admin_auth_user_add_.htm](/uploads/0842213a9f0d290b38112c0e0cbd1401/IntegrityError_at__admin_auth_user_add_.htm)https://gitlab.idiap.ch/beat/beat.web/-/issues/461[experiments] Little misleading web interface2017-08-06T16:44:51ZTeodors EGLITIS[experiments] Little misleading web interfaceI find the web interface a little misleading when you set up an experiment.
After one chooses a block, 4 buttons appear that enables you to modify parameters, view algorithm, etc. The black button means "Modify algorithm parameters speci...I find the web interface a little misleading when you set up an experiment.
After one chooses a block, 4 buttons appear that enables you to modify parameters, view algorithm, etc. The black button means "Modify algorithm parameters specifically for this block":
![beat_s1](/uploads/4f90b6d3b0a2328d9067aa12fc0b4844/beat_s1.png)
After you "open" the menu, icon changes, intuitively it feels that pressing the button would just close the algorithm parameter selection menu (for 2 months I assumed this), but in reality this means "reset algorithm on this block to their default values":
![beat_s2](/uploads/b7fe95af199721920534e8dd2b3e35cf/beat_s2.png)
IMHO it would be convenient that the user can close the "algorithm parameter selection menu" without parameter reset (imagine that you are working with a large size toolchain with 10-15 blocks, and you want to change the slot count for each of the blocks - if you must keep open all the menus, the already complicated algorithm setup page becomes non-transparent).
Also, an additional fifth button for reset should be introduced for each block.https://gitlab.idiap.ch/beat/beat.web/-/issues/459Django IOError & associated meltdown2017-08-06T16:44:51ZJaden DIEFENBAUGHDjango IOError & associated meltdown#### Info
Django will randomly start crashing with this error, and I'll need to restart the server. It can happen when Django is trying to open the database, when I refresh the page, when an AJAX call is made, etc. It sounds like there's...#### Info
Django will randomly start crashing with this error, and I'll need to restart the server. It can happen when Django is trying to open the database, when I refresh the page, when an AJAX call is made, etc. It sounds like there's some file descriptor leak (some code not properly closing file descriptors), but I don't know.
I thought I fixed it with `ulimit -n 2048` (increasing the file descriptor limit to 2048), but recently it's been happening again. There's no reliable way to reproduce it, or reliable timing - I may not have it for a few days, or get it several times an hour. It's happened over the last couple months (started maybe around Christmas break? Don't remember exactly).
I develop on my own laptop on Arch Linux.
#### Raw data
Django Error page: [django_io_error.html](/uploads/347be48a0a7f87d71ccbe374598d6976/django_io_error.html)
Traceback 1:
```sh
Traceback (most recent call last):
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/wsgiref/handlers.py", line 85, in run
self.result = application(self.environ, self.start_response)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/staticfiles/handlers.py", line 64, in __call__
return super(StaticFilesHandler, self).__call__(environ, start_response)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/core/handlers/wsgi.py", line 177, in __call__
response = self.get_response(request)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/staticfiles/handlers.py", line 54, in get_response
return self.serve(request)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/staticfiles/handlers.py", line 47, in serve
return serve(request, self.file_path(request.path), insecure=True)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/staticfiles/views.py", line 40, in serve
return static.serve(request, path, document_root=document_root, **kwargs)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/views/static.py", line 68, in serve
response = FileResponse(open(fullpath, 'rb'), content_type=content_type)
IOError: [Errno 24] Too many open files: u'/home/blackcap/Code/beat.web/beat/web/reports/static/reports/app/data/table_itemcontent.json'
[23/Feb/2017 15:10:37] "GET /static/reports/app/data/table_itemcontent.json?v1.1.5 HTTP/1.1" 500 59
```
Traceback 2 (right after 1):
```sh
Internal Server Error: /api/v1/plotters/
Traceback (most recent call last):
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 123, in get_response
File "/home/blackcap/Code/beat.web/beat/web/navigation/middleware.py", line 62, in process_request
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/utils/functional.py", line 204, in inner
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/utils/functional.py", line 351, in _setup
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/auth/middleware.py", line 22, in <lambda>
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/auth/middleware.py", line 10, in get_user
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/auth/__init__.py", line 167, in get_user
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/auth/__init__.py", line 59, in _get_user_session_key
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/sessions/backends/base.py", line 48, in __getitem__
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/sessions/backends/base.py", line 198, in _get_session
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/contrib/sessions/backends/cached_db.py", line 45, in load
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/models/manager.py", line 122, in manager_method
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/models/query.py", line 381, in get
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/models/query.py", line 240, in __len__
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/models/query.py", line 1074, in _fetch_all
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/models/query.py", line 52, in __iter__
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 846, in execute_sql
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/backends/base/base.py", line 231, in cursor
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/backends/base/base.py", line 204, in _cursor
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/backends/base/base.py", line 199, in ensure_connection
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/utils.py", line 95, in __exit__
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/backends/base/base.py", line 199, in ensure_connection
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/backends/base/base.py", line 171, in connect
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/db/backends/sqlite3/base.py", line 207, in get_new_connection
OperationalError: unable to open database file
[23/Feb/2017 15:10:38] "GET /api/v1/plotters/ HTTP/1.1" 500 64611
```
Traceback 3:
```sh
Internal Server Error: /reports/user/test/
Traceback (most recent call last):
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 149, in get_response
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 147, in get_response
File "/home/blackcap/Code/beat.web/beat/web/reports/views.py", line 81, in for_author
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/shortcuts.py", line 45, in render_to_response
using=using)
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/template/loader.py", line 114, in render_to_string
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/template/engine.py", line 231, in render_to_string
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/template/engine.py", line 190, in get_template
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/template/engine.py", line 157, in find_template
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/template/loaders/base.py", line 40, in get_template
File "/home/blackcap/Code/beat.env.web/usr/lib/python2.7/site-packages/django/template/loaders/filesystem.py", line 24, in get_contents
IOError: [Errno 24] Too many open files: '/home/blackcap/Code/beat.web/beat/web/templates/reports/report.html'
[23/Feb/2017 15:10:52] "GET /reports/user/test/ HTTP/1.1" 500 64762
```