[bug] as a host, I can neither view nor upload audio files

expected behaviour

users should be able to upload audio files according to their user group status, and be able to view uploaded content.

problem description

The upload and display of audio files currently seems to work only with superuser or proko-status. As a host or host+, I can neither view uploaded files nor do new uploads. I checked the user group permissions in steering, and they seem to be okay (cc @eigenwijsje )

steps to reproduce

1. log in as host or host+
2. upload an audio file for one episode (or for the default media source if applicable)
3. the uploader accepts the input, but then does not show success or failure of the upload. after logging off and in again, also no file is shown. also files that have been previously uploaded into the same spot are not shown. also files that a superuser has uploaded into the same episode do not show up in dashboard once I log in as host/host+.

test environment

this bug has been reported by the ProKos and was reproduced by Maggie on dashboard.aura.radio (Firefox, tested on 17.9.2024). Can some else validate this?

assigned to @kmohrf

changed milestone to %1.0-alpha5 — Capable Capybara

added P1 To Do bug labels

assigned to @kmohrf

giving this a P1 because this has been working already, and it makes the core workflow for hosts unusable

marked this issue as related to dashboard#273 (closed)

marked this issue as related to dashboard#228 (closed)

This is strange:

Looking at the tank logs, I only see successful entries, like this (35 times each for today):

tank  | 2024-09-17T16:04:50.644931484Z [ --- ] 2024/09/17 18:04:50.643898 importer: worker(2) starting job(491/208) ...
tank  | 2024-09-17T16:04:55.233886480Z [ --- ] 2024/09/17 18:04:55.233727 importer: worker(2) successfully completed job(491/208)

I just uploaded a file and it disappears from the dashboard once it finishes.

But, the files are all in the filesystem...

This might help:

I am getting these responses:

I think this is a bug in tank. My local dashboard initiates the following requests:

1. upload the file (multiple requests via flow API)
2. wait for the tank file import state to become done or return a 404 response (GET http://10.243.243.70/tank/api/v1/files/50/import?waitFor=done&showId=34)
3. fetch the file record from tank (GET http://10.243.243.70/tank/api/v1/files/50)
4. set the file title attribute (PATCH http://10.243.243.70/tank/api/v1/files/50)
5. create a playlist (POST http://10.243.243.70/tank/api/v1/playlists)
6. set Show.playlist_id based on the created playlist (PATCH http://10.243.243.70/steering/api/v1/shows/34/)
7. add the uploaded file to Playlist.entries (PUT http://10.243.243.70/tank/api/v1/playlists/9)

All of these requests are successful. Specifically, when the file, playlist, and playlist entries are created the showId seems to be assigned correctly because it is part of each of the responses sent by tank.

What ultimately fails is a simple GET http://10.243.243.70/tank/api/v1/playlists/9 request to the playlist that has just been created. Instead tank responds with a 403 response:

{
  "error": "you are not allowed to access playlist: 9"
}

moved from dashboard#313 (moved)

assigned to @eigenwijsje and unassigned @kmohrf

added Doing label and removed To Do label

Moving this where it actually belongs...

closed

moved to steering#247 (closed)

removed Doing label