funkwhale issueshttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues2023-07-06T17:03:55Zhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/343Starting radio doesn't clear the queue2023-07-06T17:03:55ZjovuitStarting radio doesn't clear the queue<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers ...<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers untouched, they won't be displayed in your final message.
Please do not edit the following line, it's used for automatic classification
-->
Starting a radio doesn't clear the queue. Thus the whole current queue will be played before the radio actually starts. I think starting a radio should clear the current queue.
Or maybe give the choice to the user, in the same way as "Play all" and "add to queue"https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2063Funkwhale connection interrupted every so often - Requires network reset/page...2023-07-02T20:36:13ZAMoonRabbitFunkwhale connection interrupted every so often - Requires network reset/page refresh
## Steps to reproduce
Set music to play with either a radio playlist, or other. Needs to be at least an hours worth.
## What happens?
Music playback tends to stop within the first few minutes of the currently playing track. Console w...
## Steps to reproduce
Set music to play with either a radio playlist, or other. Needs to be at least an hours worth.
## What happens?
Music playback tends to stop within the first few minutes of the currently playing track. Console will then start to fill up with HTTP2 protocol 206 errors suggesting partial data transmission. Initially I had been refreshing the page to then be able to continue playing music, but I have since found that simply switching my VPN off and on again (and vice versa, it happens without the VPN) will resolve the 206 errors and playback will resume.
This could be network related so will do some more testing when I am at home. Other than the python errors I am not seeing anything in the logs which correlate with this issue. What makes me unsure is that everything else on the host is still communicating fine over the VPN/Internet(when VPN not in use).
## What is expected?
Continuous, uninterrupted playback as long as network is stable.
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: 1.3.0-rc3
**Browser**: Edge Chromium Debian 109.0.1518.70
Test with PiVPN connected, and also disconnected.
Raising this just to keep tabs on it. I have not yet fully dismissed environment network issues so it may not be Funkwhale related.
**Browser console logs:** [music.udongein.reisen-1674876828423.log](/uploads/6adc6c3c3862a9a72a1702ef82b3b621/music.udongein.reisen-1674876828423.log)
**Funkwhale Logs:**
[_funkwhale-front-1_logs.txt](/uploads/04063791c6495c06008822edc63717da/_funkwhale-front-1_logs.txt)
[_funkwhale-api-1_logs.txt](/uploads/5bd57cf98be4531f43ae8d91c66b52f5/_funkwhale-api-1_logs.txt)
<!--
If relevant, share additional context here like:
- Browser type and version (for front-end bugs)
- Instance configuration (Docker/non-docker, nginx/apache as proxy, etc.)
- Error messages, screenshots and logs
-->1.3.0Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2173Custom nginx config doens't work as documented2023-06-27T12:29:24ZGeorg KrauseCustom nginx config doens't work as documentedhttps://docs.funkwhale.audio/administrator/installation/docker.html#override-default-nginx-templates
The second step doesn't work, as reported [in the forum](https://forum.funkwhale.audio/d/349-help-with-13-upgrade-using-traefik-as-reve...https://docs.funkwhale.audio/administrator/installation/docker.html#override-default-nginx-templates
The second step doesn't work, as reported [in the forum](https://forum.funkwhale.audio/d/349-help-with-13-upgrade-using-traefik-as-reverse-proxy-not-nginx/2)
The first URL points to a symlink, which is displayed in the raw format instead of loading the content of the target.
The second file just simply doesn't exist.
We should fix both of them1.3.1Georg KrauseGeorg Krausehttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2136Prune skipped uploads is OOM killed2023-06-27T11:41:48ZnoutsPrune skipped uploads is OOM killed<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue re...<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue respect our guidelines.
To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers untouched, they won't be displayed in your final message.
Please do not edit the following line, it's used for automatic classification
-->
## Steps to reproduce
1. Set a job to import in-place
```
python manage.py import_files <lib_id> "/usr/local/src/funkwhale/data/music/" --recursive --async --noinput --in-place --prune --skip-checks
```
2. Wait for a looong time until you reach a lot a Skipped uploads (due to the known in-place import bug). Something like 1Million Skipped
3. Try to clean skipped_uploads using
```
python manage.py prune_skipped_uploads --force FORCE --skip-checks
```
## What happens?
The prune command starts to consume all available ram, and is finally being OOM killed by linux.
## What is expected?
The prune command handles ram usage and terminates without issue even after a very long time.
## Context
I used to have the import and prune command running daily via cronjob. The prune command failed (because of typo on my side) and the import kept running for days (months?).
Now I have 1.222 Millions uploads in that library, of which 1.119 Millions are skipped uploads.
Trying to clean them using the webUI times out on nginx or is being OOM killed like the cli.
I've try setting docker-compose resources limit, but the container ends up being killed anyway after consuming all of its allocated ram.
I'm running the funkwhale multi-container docker-compose, inside a Proxmox VM.
VM is dedicated to run funkwhale with 4 vCpu and 8Go ram. Average usage of ram is around 4Go. So the prune command eats up to 4Go alone. I've try shutting down funkwhale on running the command directly with : `docker compose run --rm api python manage.py prune_skipped_uploads --force FORCE` (so nothing starts except postgres,redis and api) but it eats up all the 8Go available...
Allocating 32Go of ram might solve the issue, though I don't have that kind of machine XD
I don't have logs to share, even with setting `--verbosity 3` on the prune command.
My Funkwhale is super slow as you can expect. I've disabled import and prune jobs for now.
**Funkwhale version(s) affected**: 1.2.10
---
I'll be glad to test stuff and provide logs and stats. Although, I think the quickest solution to unblock my users might be to run a script calling the API and deleting skipped_uploads by batch of 50 (I've try that but my coding skills handling oauth stuff are not enough it seems), so if someone have a beginning of a script I could adapt, it's highly appreciated.1.3.1petitminionpetitminionhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2159Old embed codes not working after update to 1.3.02023-06-26T10:06:58ZAsier Iturralde SarasolaOld embed codes not working after update to 1.3.0<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue re...<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue respect our guidelines.
To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers untouched, they won't be displayed in your final message.
Please do not edit the following line, it's used for automatic classification
-->
## Steps to reproduce
<!--
Describe the steps to reproduce the issue, like:
-->
1. Create an embed code using a pod that uses Funkwhale < 1.3.0. As an example, here it is one created in our instance, Baleafunk.eus, a year ago:
`<iframe src="https://baleafunk.eus/front/embed.html?&type=track&id=225" scrolling="no" width="100%" height="150" frameborder="no"></iframe>`
Note that the URL is /front/embed.html
2. Use that embed code in a website. For example: https://iametza.eus/saioa/hodeia-ez-da-existitzen-2x03-sakananet-sare-mankomunatua/
3. Update the pod to Funkwhale 1.3.0.
## What happens?
<!--
Describe what happens once the previous steps are completed.
-->
The embedded player stops working. If I remove "/front" from the URL of the embed code, it works again. Funkwhale 1.3.0 creates embed codes with a URL that doesn't have that in the path: `baleafunk.eus/embed.html?&type=track&id=225`
## What is expected?
<!--
Describe the expected behaviour.
-->
The old embedded player should work after the update. It should be backwards compatible.
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: x.y
<!--
If relevant, share additional context here like:
- Browser type and version (for front-end bugs)
- Instance configuration (Docker/non-docker, nginx/apache as proxy, etc.)
- Error messages, screenshots and logs
-->
- Tested with Firefox and Chrome.
- Funkwhale 1.3.0, after updating from 1.2.8.
- Docker installation with nginx as a reverse proxy.
- I can reproduce the bug using various pods that use Funkwhale 1.2.8, 1.2.9 and 1.3.0.1.3.1Georg KrauseGeorg Krausehttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2169Embedded player might be broken with passed base-url2023-06-26T09:56:31ZGeorg KrauseEmbedded player might be broken with passed base-urlThe following discussion from !2489 should be addressed:
- [ ] @georgkrause started a [discussion](https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/2489#note_53222): (+1 comment)
> @wvffle I get the following:
...The following discussion from !2489 should be addressed:
- [ ] @georgkrause started a [discussion](https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/2489#note_53222): (+1 comment)
> @wvffle I get the following:
>
> ```
> SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data embed.html:169:17
> <anonymous> http://localhost:8080/embed.html?&type=track&id=120&b=https://demo.funkwhale.audio/:169
> (Async: promise callback)
> <anonymous> http://localhost:8080/embed.html?&type=track&id=120&b=https://demo.funkwhale.audio/:168
> ```
There might be a `//` in the URL
* works: `http://localhost:8080/embed.html?&type=track&id=120&b=https://demo.funkwhale.audio`
* doesn't: `http://localhost:8080/embed.html?&type=track&id=120&b=https://demo.funkwhale.audio/`1.3.1Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2151Refused to load spa-manifest.json2023-06-26T07:18:03ZDaniel JellerRefused to load spa-manifest.json<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue re...<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue respect our guidelines.
To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers untouched, they won't be displayed in your final message.
Please do not edit the following line, it's used for automatic classification
-->
## Steps to reproduce
<!--
Describe the steps to reproduce the issue, like:
1. Visit the page at /artists/
2. Type that
3. Submit
-->
Load the funkwhale starting page in a browser and look at the browser console log.
## What happens?
<!--
Describe what happens once the previous steps are completed.
-->
The browser fails to load `spa-manifest.json` because, even though Funkwhale is configured to use `https`, it tries to get the json file via `http`.
The related log output (domain is replaced with example.com) is:
```
library:1 Refused to load manifest from 'http://funkwhale.example.com/api/v1/instance/spa-manifest.json' because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'manifest-src' was not explicitly set, so 'default-src' is used as a fallback.
Mixed Content: The page at 'https://funkwhale.example.com/serviceWorker.js' was loaded over HTTPS, but requested an insecure resource 'http://funkwhale.example.com/api/v1/instance/spa-manifest.json'. This request has been blocked; the content must be served over HTTPS.
serviceWorker.js:1 Uncaught (in promise) TypeError: Failed to fetch
at ce.fetch (serviceWorker.js:1:3904)
at p._handleInstall (serviceWorker.js:1:8431)
at p._handle (serviceWorker.js:1:7902)
at async p._getResponse (serviceWorker.js:1:6959)
fetch @ serviceWorker.js:1
_handleInstall @ serviceWorker.js:1
_handle @ serviceWorker.js:1
```
## What is expected?
<!--
Describe the expected behaviour.
-->
Funkwhale loads `spa-manifest.json`
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: 1.3.0
<!--
If relevant, share additional context here like:
- Browser type and version (for front-end bugs)
- Instance configuration (Docker/non-docker, nginx/apache as proxy, etc.)
- Error messages, screenshots and logs
-->
MS Edge Version 114.0.1823.37 (Official build) (64-bit)
Instance run on Docker.1.3.1Georg KrauseGeorg Krausehttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/1585Resources blocked due to MIME type mismatch (Caddy)2023-06-21T14:07:52ZJanekResources blocked due to MIME type mismatch (Caddy)Trying to access a newly setup instance from latest Firefox, seeing "Loading Funkwhale..." forever with multiple messages like this in the console:
```
The resource from “https://DOMAIN/front/js/chunk-index-vendors.ca8affd0.js” was block...Trying to access a newly setup instance from latest Firefox, seeing "Loading Funkwhale..." forever with multiple messages like this in the console:
```
The resource from “https://DOMAIN/front/js/chunk-index-vendors.ca8affd0.js” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff).
```https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2160Stuck to "Loading Funkwhale..." message after upgrade to 1.3.0 from 1.2.92023-06-21T14:07:51ZRaph MazzoniStuck to "Loading Funkwhale..." message after upgrade to 1.3.0 from 1.2.9<!--
Hello and welcome to our issue tracker! We appreciate you taking the time to help us make Funkwhale even better :smile:
Before you begin, here are some helpful tips for submitting an issue:
* If you need help setting up or using ...<!--
Hello and welcome to our issue tracker! We appreciate you taking the time to help us make Funkwhale even better :smile:
Before you begin, here are some helpful tips for submitting an issue:
* If you need help setting up or using Funkwhale, try asking in our
[forum's support board](https://forum.funkwhale.audio/support) or our [support
chat room](https://riot.im/app/#/room/#funkwhale-support:tchncs.de).
* If you think you've found a bug but aren't sure, you can ask in one of the above channels
first. Once you're confident it's a bug, go ahead and create an issue for us to investigate.
Select the **Bug** template in the **Description** dropdown menu. This template contains
helpful tips for creating your report.
* For smaller additions and enhancements, please file a feature request.
Select the **Feature Request** template in the **Description** dropdown
menu. This template contains helpful tips for creating your request.
* If you have ideas for new features or use cases, consider opening a thread in our
[forum](https://forum.funkwhale.audio/t/development). This enables us to
discuss the feature, its use cases, and the development effort it requires.
We always like hearing ideas from our community. If you're still not sure, click
the **Create issue** button and we'll work with you to sort out the issue.
Happy listening! :whale:
-->
Hi ! It's a non docker install (yunohost)
After successful upgrade to 1.3.0 from 1.2.9 I'm stuck with "Loading Funkwhale..." Message.
I've follow the upgrade process in the official documentation but the line :
<code>sudo -u funkwhale -H -E /srv/funkwhale/virtualenv/bin/pip install -r api/requirements.txt</code>
don't pass because the requirements.txt file is no longer in this place (or in the archive ?).
Well, I've installed two python modules with pip : drf_spectacular and dj_rest_auth
for pass the next step of this upgrade process :
<code>sudo -u funkwhale -H -E /srv/funkwhale/virtualenv/bin/python api/manage.py collectstatic --no-input </code>
which terminated without error.
On startup the funkwhale target is loaded but dead. Beat, Server and worker are up with no error.
My browser debuger :
Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML spec.
Any Idea ?
Regardshttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2163Facing error when generate an Embed code towards Flac track with 1.3.02023-06-21T09:36:40ZNaiveTubFacing error when generate an Embed code towards Flac track with 1.3.0## Steps to reproduce
**1.** I‘ve deployed a funkwhale website with docker and nginx correctly: [fun.wyy.sh](https://fun.wyy.sh/) <br>
**2.** Visit an audio content page that is a Flac files:[Flac files page](https://fun.wyy.sh/library/t...## Steps to reproduce
**1.** I‘ve deployed a funkwhale website with docker and nginx correctly: [fun.wyy.sh](https://fun.wyy.sh/) <br>
**2.** Visit an audio content page that is a Flac files:[Flac files page](https://fun.wyy.sh/library/tracks/1) <br>
**3.** Choose to generate embed code and there is an error prompt called "**An unknown error occurred while loading this track.** " existed in the preview area. <br>
## What happens?
**In the firefox panel the specific error is:** <br>
[](**TypeError: URL constructor: /api/v1/listen/982b342d-b058-48e2-a538-ffbe9d605ca2/?upload=ff608887-d6f4-4b93-93ce-dde95a3cb222 is not a valid URL. <br>
getAudioSources https://fun.wyy.sh/embed.html?&type=track&id=1:76 <br>
fetchTracks https://fun.wyy.sh/embed.html?&type=track&id=1:157 <br>
fetchTracks https://fun.wyy.sh/embed.html?&type=track&id=1:151 <br>
async* https://fun.wyy.sh/embed.html?&type=track&id=1:168 <br>
- ![Snipaste_2023-06-16_09-46-32](/uploads/479f1cc2f25c18a6783696f36265c2b4/Snipaste_2023-06-16_09-46-32.png)
## What is expected?
**1.** Visit an audio content page that is a MP3 files: [MP3 files page](https://fun.wyy.sh/library/tracks/2) <br>
**2.** Choose to generate embed code and it just works as expected. Music in Flac format should have been functioning normally in the same method. <br>
- ![Snipaste_2023-06-16_09-44-52](/uploads/a5113db4d2e9088763f2b1ccf046145f/Snipaste_2023-06-16_09-44-52.png) <br><br>
**I'd like to know whether it's a bug or it's just can't function normally when generate an embed code from Flac music files. Thanks very much!**
## Context
**Funkwhale version(s) affected**: 1.3.0 <br>
**Browser type and version**: Both in the latest version of Firefox and Chrome <br>
**Instance configuration**:Deployed by Docker Container <br><br>1.3.1Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2166[Docker] The is no 1.3.02023-06-19T09:47:06ZElrondo46[Docker] The is no 1.3.0Where is this version in docker hub ???Where is this version in docker hub ???https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2144Sidebar draws ontop of Now Playing screen2023-06-19T07:11:43ZAMoonRabbitSidebar draws ontop of Now Playing screen<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue re...<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue respect our guidelines.
To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers untouched, they won't be displayed in your final message.
Please do not edit the following line, it's used for automatic classification
-->
## Steps to reproduce
1. Start playing music
2. Open the Now Playing view by clicking on the bottom bar
3. Note the sidebar remains on top
## What happens?
Sidebar remains ontop and obscures the album art and now playing info.
## What is expected?
Previous versions, nowplaying view drew on top of all elements.
## What have you tried?
I have cleared site cache and data via browser tools and hard refreshed the page.
Temporarily removed CSS customisations.
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: 1.3.0-rc6
**Browser in use**: Edge (Chromium) 113.0.1774.57 (installed as a PWA)
![image](/uploads/08fe2995a877bfdc1c3eca3bf2019d66/image.png)
<!--
If relevant, share additional context here like:
- Browser type and version (for front-end bugs)
- Instance configuration (Docker/non-docker, nginx/apache as proxy, etc.)
- Error messages, screenshots and logs
-->1.3.0Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2127Create playlist button2023-06-19T07:11:43ZJulian-Samuel GebührCreate playlist button<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue re...<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue respect our guidelines.
To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers untouched, they won't be displayed in your final message.
Please do not edit the following line, it's used for automatic classification
-->
## Steps to reproduce
Click the "Create Playlist" button at `/library/playlists/`
![image](/uploads/ccf7b0849bbcc66eeb62bd89702d0f8e/image.png)
<!--
Describe the steps to reproduce the issue, like:
1. Visit the page at /artists/
2. Type that
3. Submit
-->
Might be related to #1961
## What happens?
Nothing
## What is expected?
I can create a playlist :)
## Context
**Funkwhale version(s) affected**: 1.3.0-rc5 (docker via [MASH](https://github.com/mother-of-all-self-hosting/mash-playbook#))
<!--
If relevant, share additional context here like:
- Browser type and version (for front-end bugs)
- Instance configuration (Docker/non-docker, nginx/apache as proxy, etc.)
- Error messages, screenshots and logs
-->1.3.0Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/1982'Show read notifications' switch overlapping language selector menu2023-06-19T07:11:43ZKeunes'Show read notifications' switch overlapping language selector menu<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue re...<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue respect our guidelines.
To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers untouched, they won't be displayed in your final message.
Please do not edit the following line, it's used for automatic classification
-->
## Steps to reproduce
1. Open the Notifications page (`/notifications`)
2. Click on the user icon to open the personalised menu
3. hover mouse on Language menu entry
<!--
Describe the steps to reproduce the issue, like:
1. Visit the page at /artists/
2. Type that
3. Submit
-->
## What happens?
The language sub-menu appears, but the switch to 'Show read notifications' overlaps the language menu.
<!--
Describe what happens once the previous steps are completed.
-->
## What is expected?
The notifications switch is hidden behind the menu
<!--
Describe the expected behaviour.
-->
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: 1.2.8+git.34b99f29
Multi-container Docker
![Screenshot_from_2022-11-24_22-34-07](/uploads/b96c1d796c3112b45e091101dca6a861/Screenshot_from_2022-11-24_22-34-07.png)
<!--
If relevant, share additional context here like:
- Browser type and version (for front-end bugs)
- Instance configuration (Docker/non-docker, nginx/apache as proxy, etc.)
- Error messages, screenshots and logs
-->1.3.0Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2056Notification count is bumping up whenever unread notifications are shown2023-06-19T07:11:42ZKasper Sewerynwvffle@funkwhale.audioNotification count is bumping up whenever unread notifications are shown<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue re...<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue respect our guidelines.
To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers untouched, they won't be displayed in your final message.
Please do not edit the following line, it's used for automatic classification
-->
## Steps to reproduce
1. Get a notification
2. Note the number on the notification counter
3. Display notification list
4. Note the number on the notification counter
## What happens?
The notification counter is bumped up.
When notifications are mixed up (#2057), it adds the total number of notifications in unread section to the notification count whenever the section is shown.
<!--
Describe what happens once the previous steps are completed.
-->
## What is expected?
<!--
Describe the expected behaviour.
-->
The notification counter should display the true number of notifications.
## Context
I also had a single read notification, that might be also the case.
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: develop
<!--
If relevant, share additional context here like:
- Browser type and version (for front-end bugs)
- Instance configuration (Docker/non-docker, nginx/apache as proxy, etc.)
- Error messages, screenshots and logs
-->
![image](/uploads/bee15237b99d8de1d810daf81dff299d/image.png)1.3.0Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2106Deleting ranked item n in playback queue removes the n-1 one2023-06-19T07:11:42ZNicolas DeriveDeleting ranked item n in playback queue removes the n-1 oneWhen removing items in the playback queue in 1.3.0, clicking on the button at the end of the track line removes the previous item, not the chosen one.
![Capture_vidéo_du_23-03-2023_16_12_45](/uploads/db8ebee17a8ea27974c19dd4b5ea7a96/...When removing items in the playback queue in 1.3.0, clicking on the button at the end of the track line removes the previous item, not the chosen one.
![Capture_vidéo_du_23-03-2023_16_12_45](/uploads/db8ebee17a8ea27974c19dd4b5ea7a96/Capture_vidéo_du_23-03-2023_16_12_45.webm)
It also seems that ordering tracks is impacted, as moving a given track moves the previous one to the destination place, leaving the chosen one in place (I'm ready to also provide a video if needed). But clicking on the chosen item properly plays it (or restart it).
That seems pretty new to me, I don't remember having this problem with 1.2.8.1.3.0Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/1981'Donate' notification 'Got it' button not working if reminder option 'Never' ...2023-06-19T07:11:42ZKeunes'Donate' notification 'Got it' button not working if reminder option 'Never' is selected<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue re...<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue respect our guidelines.
To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers untouched, they won't be displayed in your final message.
Please do not edit the following line, it's used for automatic classification
-->
## Steps to reproduce
1. Click user menu --> Notifications (`/notifications`)
2. In the 'Donate' notification, change the drop-down for the reminder from '60 Days' to 'Never'
3. Click the 'Got it!' button
<!--
Describe the steps to reproduce the issue, like:
1. Visit the page at /artists/
2. Type that
3. Submit
-->
## What happens?
Side menu goes away; notification reappears on refresh.
<!--
Describe what happens once the previous steps are completed.
-->
## What is expected?
The Donate notification goes away; side menu remains visible.
<!--
Describe the expected behaviour.
-->
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: 1.2.8+git.34b99f29
Multi-container Docker1.3.0Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2057Read and unread notifications get mixed up2023-06-19T07:11:42ZKasper Sewerynwvffle@funkwhale.audioRead and unread notifications get mixed up<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue re...<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue respect our guidelines.
To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers untouched, they won't be displayed in your final message.
Please do not edit the following line, it's used for automatic classification
-->
## Steps to reproduce
1. Get a notification and mark it as read
2. Get another notification
3. Go to notification page
4. Toggle 'Show read notifications' switch a couple of times
## What happens?
Read notifications are mixed with unread notifications after few clicks and read notifications are empty.
## What is expected?
Read notifications should not move to the unread section
## Context
**Funkwhale version(s) affected**: develop
<!--
If relevant, share additional context here like:
- Browser type and version (for front-end bugs)
- Instance configuration (Docker/non-docker, nginx/apache as proxy, etc.)
- Error messages, screenshots and logs
-->1.3.0Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2093Invitation Code field cannot be left empty despite default text2023-06-19T07:11:42ZAMoonRabbitInvitation Code field cannot be left empty despite default text<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue re...<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue respect our guidelines.
To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers untouched, they won't be displayed in your final message.
Please do not edit the following line, it's used for automatic classification
-->
## Steps to reproduce
<!--
Describe the steps to reproduce the issue, like:
1. Visit the page at /artists/
2. Type that
3. Submit
-->
1. Manage Users > Invitations
2. Leave field empty and click "Get a new invitation"
3. Error appears saying field must not be empty
![Screenshot_from_2023-02-25_20-40-18](/uploads/acb2ea54be6689f9eb197c01cf084732/Screenshot_from_2023-02-25_20-40-18.png)
## What happens?
No invitation code is generated, instead there is an error because the field was left empty.
## What is expected?
A random invitation code should be generated as per the default field text "Leave empty for a random code".
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: 1.3.0-rc3
<!--
If relevant, share additional context here like:
- Browser type and version (for front-end bugs)
- Instance configuration (Docker/non-docker, nginx/apache as proxy, etc.)
- Error messages, screenshots and logs
-->1.3.0Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2052Disable visualizer button on browsers that do not support WebGL2023-06-19T07:11:42ZKasper Sewerynwvffle@funkwhale.audioDisable visualizer button on browsers that do not support WebGL<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue re...<!--
Hi there! You are reporting a bug on this project, and we want to thank you!
If it's the first time you post here, please take a moment to read our Code of Conduct
(https://funkwhale.audio/code-of-conduct/) and ensure your issue respect our guidelines.
To ensure your bug report is as useful as possible, please try to stick
to the following structure. You can leave the parts text between `<!- ->`
markers untouched, they won't be displayed in your final message.
Please do not edit the following line, it's used for automatic classification
-->
## Steps to reproduce
<!--
Describe the steps to reproduce the issue, like:
1. Visit the page at /artists/
2. Type that
3. Submit
-->
## What happens?
Switching to the visualizer fails with `Uncaught TypeError: this.gl is null` error.
## What is expected?
Visualizer button should be disabled with a tooltip stating that this browser does not support WebGL
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: develop
**Browser**: Librewolf
<!--
If relevant, share additional context here like:
- Browser type and version (for front-end bugs)
- Instance configuration (Docker/non-docker, nginx/apache as proxy, etc.)
- Error messages, screenshots and logs
-->1.3.0Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audio