Issues on first trial
Hi, I just tried the Dashboard and Aura for the first time. Here's a list of things I ran into:
Show management
-
When the fixtures are not imported into steering (which the docs list as an optional step) there's no way to create new shows and the UI is completely empty.
-
After creating the show, there's a button "Switch to emission management". Clicking the button leads to a blank page for me (Header/Footer as usual, but main area all white). -
Clicking on the edit button next to logo, selecting an image and clicking upload leads to no changes on the screen. Reloading the page still says (none set) below Logo. Click the edit button next to Logo again however shows the image I uploaded previously as Current logo.
Files and playlists
Things seem to work as they should! I could add files and playlists.
-
I added a file that does not contain MP3 tags. For such a file I would expect that the filename is shown somewhere, but the table only contains empty Artist, Album and Title columns, which are not helpful for non-music focused shows where you usually would upload interviews or other snippets that often have no ID3 tags.
Calendar
I could create a new, single occurrence and select a playlist. Nice!
-
The Calendar screen does not show which radio show is currently selected, unless you actively click the "Select a radio show" dropdown. It would be better to show the active show somewhere so that you know what you are doing. -
When creating another schedule in the calendar and selecting "Weekly repetition", a popup comes up that says " Error: Could not load timeslots. Status code: 400 Bad request
". When checking the browser network tab, I see that the actual server response of the POST request to/steering/api/v1/shows/2/schedules
was{ message: "Start and until dates mustn't be the same", code: "no-same-day-start-and-end" }
. This message is not shown on screen, so there was no way for a regular user to act accoringly. Also, in the form it was not clear to me that the end date was the end of the repetition, a note there would be useful. -
I then clicked on the single occurrence schedule I created earlier and clicked on add a repetition with the default settings (next day, same time). I was shown a message on the main screen that says: " Konfliktbehebung für neues Programm. von Invalid Date, %{tstart} bis %{tend} Keine Konflikte mehr zu beheben!
". The message seems to contain unreplaced tokens. I then clicked on the green button ("Accept resolution" or so). Then, a popup appeared that says: "Error: could not load timeslots. Status code: 500 Internal Server Error". I again checked the browser network tab, but this time it did only show "Server Error (500)" without further info. The docker logs contain this stacktrace:
Click to expand
steering | ERROR:django.request:Internal Server Error: /api/v1/shows/3/schedules/ steering | Traceback (most recent call last): steering | File "/usr/local/lib/python3.9/site-packages/django/core/handlers/exception.py", line 47, in inner steering | response = get_response(request) steering | File "/usr/local/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response steering | response = wrapped_callback(request, *callback_args, **callback_kwargs) steering | File "/usr/local/lib/python3.9/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view steering | return view_func(*args, **kwargs) steering | File "/usr/local/lib/python3.9/site-packages/rest_framework/viewsets.py", line 125, in view steering | return self.dispatch(request, *args, **kwargs) steering | File "/usr/local/lib/python3.9/site-packages/rest_framework/views.py", line 509, in dispatch steering | response = self.handle_exception(exc) steering | File "/usr/local/lib/python3.9/site-packages/rest_framework/views.py", line 469, in handle_exception steering | self.raise_uncaught_exception(exc) steering | File "/usr/local/lib/python3.9/site-packages/rest_framework/views.py", line 480, in raise_uncaught_exception steering | raise exc steering | File "/usr/local/lib/python3.9/site-packages/rest_framework/views.py", line 506, in dispatch steering | response = handler(request, *args, **kwargs) steering | File "/steering/program/views.py", line 487, in create steering | resolution = Schedule.resolve_conflicts(request.data, pk, show_pk) steering | File "/steering/program/models.py", line 739, in resolve_conflicts steering | schedule = Schedule.instantiate_upcoming(sdl, show_pk, schedule_pk) steering | File "/steering/program/models.py", line 327, in instantiate_upcoming steering | first_date = parse_date(str(sdl["dstart"])) steering | KeyError: 'dstart' dashboard | 10.23.1.104 - - [03/May/2022:17:54:57 +0200] "POST /steering/api/v1/shows/3/schedules/ HTTP/1.1" 500 156 "https://aura.rdlnet.de/calendar" "Mozilla/5.0 (X11; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0" "10.23.1.1"
That's it for now! Feel free to ask further questions, I can try to reproduce things of course. I just thought for now that I'd write down all issues in this first 30 minute tryout after getting Aura to work. I did not file individual issues for now because I am not sure where everything belows and also some of these things might already be known.
Thanks! Franz