funkwhale issueshttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues2024-03-23T04:18:09Zhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2295Server Error when loading library pages in a new tab2024-03-23T04:18:09ZSophie WServer Error when loading library pages in a new tab<!--
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. Open a library page (for an artist, track, or album) in a new tab from the front-end.
2. Wait for that new tab to load.
Alternatively,
1. Navigate to a library page for an artist, track, or album
2. Refresh the browser page
3. Wait for the page to reload
## What happens?
<!--
Describe what happens once the previous steps are completed.
-->
The relevant library page fails to load, instead returning a Server Error 500 code.
![image](/uploads/012661ad8d5a6c366a9ddebdd4c70f63/image.png)
When the error occurs, the Funkwhale API container logs show a python stacktrace from the create_connection function in urllib3.
Attached is an example API log when trying to open track 744 of the instance in a new tab. <br>
_Note: The instance domain has been replace with '[instance.domain]'_
[api_-_error.log](/uploads/f86a36878d52cc92f2944ff94d203406/api_-_error.log)
## What is expected?
<!--
Describe the expected behaviour.
-->
The relevant library page will load normally, in the same way as it does when navigated to within an existing browser tab.
## Context
The issue only seems to occur when opening pages in a new tab. The same pages load correctly within an existing funkwhale tab.
The error occurred across all browsers I tried (Edge, Firefox, and Chrome on Windows 10; Chrome and Firefox on Android)
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
Funkwhale Version 1.4.0<br>
Instance type: Docker
<!--
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
-->https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2294Add support for YouTube feeds2024-03-12T04:15:08ZLoren BurkholderAdd support for YouTube feeds<!--
Hi there! You are about to share feature request or an idea, 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 yo...<!--
Hi there! You are about to share feature request or an idea, 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 we can deal with your idea or request, 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
-->
## What is the problem you are facing?
<!--
Describe the problem you'd like to solve, and why we need to add or
improve something in the current system to solve that problem.
Be as specific as possible.
-->
I'd like to subscribe to certain podcasts that are distributed via YouTube (e.g. LTT's WAN Show). YouTube does allow you to create a feed for individual channels and playlists (for example, [this](https://www.youtube.com/feeds/videos.xml?playlist_id=PL8mG-RkN2uTw7PhlnAr4pZZz2QubIbujH) is the WAN Show playlist feed), but Funkwhale's RSS client doesn't properly recognize these feeds.
## What are the possible drawbacks or issues with the requested changes?
<!--
Altering the system behaviour is not always a free action, and it can impact
user experience, performance, introduce bugs or complexity, etc..
If you think about anything we should keep in mind while
examining your request, please describe it in this section.
-->
Since YouTube distributes videos, Funkwhale would have to either convert the videos to audio or add a video player for these podcasts (similar to how Spotify embeds video for some podcasts).https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2293Embed player with long title : controls not shown when width is set to a fixe...2024-03-08T14:34:19ZGuillaume VandenhoveEmbed player with long title : controls not shown when width is set to a fixed size## Steps to reproduce
1. Upload a track with a relatively long title (>80 characters)
2. Embed the track with a fixed width (e.g 800px). For height it does not matter : even if you increase default height (150px), you just get a gray b...## Steps to reproduce
1. Upload a track with a relatively long title (>80 characters)
2. Embed the track with a fixed width (e.g 800px). For height it does not matter : even if you increase default height (150px), you just get a gray background
## What happens?
You don't see the controls
## What is expected?
You see the widget as expected
## Context
You can try with the following file : https://sonotheque.cemea.org/library/tracks/65
Embedded with `width=800px` (and `height=150px`, the default value) it looks like this :
![Screenshot_from_2024-03-06_17-17-56](/uploads/da4c605da518b71c46ab08793a8f5391/Screenshot_from_2024-03-06_17-17-56.png)
If I reduce the size of the h1 enough (with dev tools), I can see the controls again, albeit a bit cut off :
![Screenshot_from_2024-03-06_17-20-35](/uploads/29f491de08f7ab82f8450e914ad9aede/Screenshot_from_2024-03-06_17-20-35.png)
Embedded with `width=800px` (and `height=400px`) it looks like this : (tested on an empty HTML file to make sure nothing is interfering) :
![Screenshot_from_2024-03-06_16-55-03](/uploads/fd64b8088d6985c7584cf2baf6a367ae/Screenshot_from_2024-03-06_16-55-03.png)
**Funkwhale version(s) affected**: 1.4.0, 1.4.2
This happens on Firefox 123.0 on Linux, Chromium 121 on Linux, and Firefox 123.0 on Windows.https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2291update tag field CICharField2024-02-27T22:30:52Zpetitminionupdate tag field CICharField`WARNINGS:
tags.Tag.name: (fields.W905) django.contrib.postgres.fields.CICharField is deprecated. Support for it (except in historical migrations) will be removed in Django 5.1.
HINT: Use CharField(db_collation="…") with a case-i...`WARNINGS:
tags.Tag.name: (fields.W905) django.contrib.postgres.fields.CICharField is deprecated. Support for it (except in historical migrations) will be removed in Django 5.1.
HINT: Use CharField(db_collation="…") with a case-insensitive non-deterministic collation instead.`petitminionpetitminionhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2290update postgresql2024-03-01T04:17:00Zpetitminionupdate postgresql`django.db.utils.NotSupportedError: PostgreSQL 12 or later is required (found 11.22).`
We probably might want to upgrade to the newest version of postgres ?`django.db.utils.NotSupportedError: PostgreSQL 12 or later is required (found 11.22).`
We probably might want to upgrade to the newest version of postgres ?https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2289Issues with tauri app2024-02-27T10:46:10ZGeorg KrauseIssues with tauri appI do have some minor issues:
- The player info doesn't update, it always shows 0:00 | 0:00
- The orange progress bar is always at 100%
- When a track finishes, the next one doesn't play, only the first second is played.
![screenshot](/...I do have some minor issues:
- The player info doesn't update, it always shows 0:00 | 0:00
- The orange progress bar is always at 100%
- When a track finishes, the next one doesn't play, only the first second is played.
![screenshot](/uploads/49e82e88b13e586a2f9fae1ee8aa1d49/screenshot.jpg)
Log when playback of next track fails:
```
** (funkwhale:182083): WARNING **: 11:45:03.382: atk-bridge: get_device_events_reply: unknown signature
WebKit wasn't able to find a WebVTT encoder. Subtitles handling will be degraded unless gst-plugins-bad is installed.
```Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2288Issues starting App Image2024-02-27T10:33:52ZGeorg KrauseIssues starting App ImageReported by @petitminion on Matrix:
petitminion
11:40
in my kubuntu system with plasma 5.27 funkwhale: symbol lookup error: /tmp/.mount_FunkwhdoTj5q/usr/lib/libpango-1.0.so.0: undefined symbol: hb_ot_layout_get_horizontal_baseline_tag_...Reported by @petitminion on Matrix:
petitminion
11:40
in my kubuntu system with plasma 5.27 funkwhale: symbol lookup error: /tmp/.mount_FunkwhdoTj5q/usr/lib/libpango-1.0.so.0: undefined symbol: hb_ot_layout_get_horizontal_baseline_tag_for_script
maybe https://github.com/AppImageCommunity/pkg2appimage/commit/f2df956789f36204213876c96500c8b05595e43bKasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2287Follow-up from "feat: add tauri" - Create a login/register page2024-02-27T08:41:59ZKasper Sewerynwvffle@funkwhale.audioFollow-up from "feat: add tauri" - Create a login/register pageThe following discussion from !2701 should be addressed:
- [ ] @wvffle started a [discussion](https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/2701#note_61260): (+3 comments)
> I think it would be a good idea to de...The following discussion from !2701 should be addressed:
- [ ] @wvffle started a [discussion](https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/2701#note_61260): (+3 comments)
> I think it would be a good idea to design a full page instance chooser screen and a login/register screen in similar style. Currently, when you navigate to the login page of an instance, you can click on any link and exit the login flow.Mathieu JourdanMathieu Jourdanhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2286Playback of federated tracks fails when track has spaces in path filename2024-02-27T08:41:21ZsvaloPlayback of federated tracks fails when track has spaces in path filename<!--
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. Subscribe to a public channel like `plus4_allstars@stereo.kenobit.it`
2. Try to listen to a track
## What happens?
<!--
Describe what happens once the previous steps are completed.
-->
Track does not play, errors are shown in nginx error log.
```log
2024/02/19 16:29:53 [error] 531592#531592: *320559 open() "/webapp/funkwhale/site/data/media/federation_cache/tracks/dd/02/75/5tarbuck%20-%20Dungeon%20and%20Underground%20-%20Pets%20Rescue%20Soundtrack%20-%20Plus/4-all-stars.mp3" failed (2: No such file or directory), client: 151.14.38.31, server: music.valo.space, request: "GET /api/v1/listen/b863333e-335e-45c4-9bbb-8be144467c95/?upload=2d2b7c4e-bad1-4b3d-b684-fc1ec3961f84&token=eyJ1c2VyX2lkIjoxLCJ1c2VyX3NlY3JldCI6IjQxM2UxNDYwLTk5ZTUtNDM1Ni04N2YwLWY3OGUwNDM1NjJhOCIsInNjb3BlcyI6WyJyZWFkOmxpYnJhcmllcyJdfQ%3A1rc4TV%3AelBSxI9PRUbEi2XjizjukC5NJKdg1h48hQhavmxCVqk HTTP/2.0", upstream: "http://127.0.0.1:5000/api/v1/listen/b863333e-335e-45c4-9bbb-8be144467c95/?upload=2d2b7c4e-bad1-4b3d-b684-fc1ec3961f84&token=eyJ1c2VyX2lkIjoxLCJ1c2VyX3NlY3JldCI6IjQxM2UxNDYwLTk5ZTUtNDM1Ni04N2YwLWY3OGUwNDM1NjJhOCIsInNjb3BlcyI6WyJyZWFkOmxpYnJhcmllcyJdfQ%3A1rc4TV%3AelBSxI9PRUbEi2XjizjukC5NJKdg1h48hQhavmxCVqk", host: "music.valo.space", referrer: "https://mydomain/channels/plus4_allstars@stereo.kenobit.it"
```
but track exists here:
```bash
/webapp/funkwhale/site/data/media/federation_cache/tracks/dd/02/75/5tarbuck - Dungeon and Underground - Pets Rescue Soundtrack - Plus/4-all-stars.mp3
```
Note that nginx tries to access track with url-encoded path while the file is available as unencoded path.
## What is expected?
<!--
Describe the expected behaviour.
-->
Track plays
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
It seems that playing a track from a federated instance when the track contains a space in path is not working due to difference on how the track is saved and retrieved.
Commenting the line https://dev.funkwhale.audio/funkwhale/funkwhale/-/blob/develop/api/funkwhale_api/music/views.py#L487 and trying again to play a track after restart leads to a working track playing.
Note: I don't have any clue about funkwhale behaviour and DB but I noticed that it may be necessary to remove the upload or the track from the DB before attempting to play it again after code change because it seems that somehow the track path on filesystem is saved the first time. If the path is wrong the track won't play regardless of code change, while if the track plays then it works regardless of the code change.
**Funkwhale version(s) affected**: 1.4.0rc2
<!--
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
-->
Funkwhale installed from archive, using uwsgi + nginx
[mydomain.conf](/uploads/f1fb173d2ca059aec6994653e550811e/mydomain.conf) is nginx confighttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2285Execute Tests in CI2024-02-21T10:57:03ZGeorg KrauseExecute Tests in CIAs soon as we start writing Rust code for the Desktop/Mobile App, we are also going to write tests. We should execute them in CI.
Acceptance criteria:
- [ ] XUnit test reporting
- [ ] Coverage reportingAs soon as we start writing Rust code for the Desktop/Mobile App, we are also going to write tests. We should execute them in CI.
Acceptance criteria:
- [ ] XUnit test reporting
- [ ] Coverage reporting1.5.0Georg KrauseGeorg Krausehttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2283Drop Python 3.92024-02-05T14:14:05ZGeorg KrauseDrop Python 3.9The support window ends before the release of Funkwhale 1.8.0The support window ends before the release of Funkwhale 1.8.01.8.0https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2282Drop Python 3.82024-02-05T14:12:00ZGeorg KrauseDrop Python 3.8It wont be supported by the data of release of %"1.6.0"It wont be supported by the data of release of %"1.6.0"1.6.0https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2281Remove deprecated funkwhaleVersion from subsonic2024-02-02T08:50:01ZGeorg KrauseRemove deprecated funkwhaleVersion from subsonicIn !2695 we deprecated the `funkwhaleVersion` subsonic API field in favor of the opensubsonic field `serverVersion`. We need to remove the deprecated API fieldIn !2695 we deprecated the `funkwhaleVersion` subsonic API field in favor of the opensubsonic field `serverVersion`. We need to remove the deprecated API field1.7.0https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2280Playback issues in Webkit browsers on iOS2024-02-07T09:40:58ZCiarán Ainsworthsporiff@funkwhale.audioPlayback issues in Webkit browsers on iOSWe've received reports in the support channel about issues with playback
when using iOS devices. The web app seems to be unable to load content
and instead proceeds to skip to the next track.
> Does anyone use Funkwhale on an IOS phone ...We've received reports in the support channel about issues with playback
when using iOS devices. The web app seems to be unable to load content
and instead proceeds to skip to the next track.
> Does anyone use Funkwhale on an IOS phone (apple), by connecting
> through the web browser. it seems that the buffering time is quite
> low, and keeps skipping songs. Not sure what causes this as it works
> perfectly fine on my PC. So I select a song, it trys to load for about
> 3 seconds then skips to the next song and does the same thing all the
> way through the playlist.
The issue is partially alleviated by quickly **pausing** and then
**playing** the track, however the time frame for this is only a
couple of seconds. The browser typically skips playback within the
first 2 seconds.
> I tried in my phone clicking pause and play. The timeframe is rather
> quick, like less than 2 seconds it feels like, however even if I do
> get in there to pause the song, it still skips and pauses on the next
> song. If I press play on the next song it does the same thing etc.
The issue occurs independent of filetype, and affects transcoded (MP3)
tracks as well as other file type.
This issue seems to have appeared since the migration away from Howler,
but it's difficult to say when it first appeared. The issue does
**not** appear to affect desktop webkit-based browsers (tested in
Safari Version 17.3).https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2278Pytest optimization2024-01-29T11:08:32ZpetitminionPytest optimizationPytest is very slow. Seems like `docker compose -f dev.yml run --rm api pytest /sometest` load all the fixture in `conftest.py` and this is what take a looot of time. I investigated a little and I think it's specifically the factories re...Pytest is very slow. Seems like `docker compose -f dev.yml run --rm api pytest /sometest` load all the fixture in `conftest.py` and this is what take a looot of time. I investigated a little and I think it's specifically the factories related fixtures that take a long time. Commenting this 5 fixture the load time of the test env goes from 60s to less than 1...
```
factories
preferences
logged_in_client
superuser_api_client
logged_in_api_client
```
https://docs.pytest.org/en/6.2.x/cache.html#the-new-config-cache-object
https://docs.pytest.org/en/6.2.x/reference.html#std-fixture-cache
I tried mounting the pytest cache into the api container but it doesn't speedup the process. Fixture are suppose to be cache tho' : https://docs.pytest.org/en/6.2.x/fixture.html#fixtures-can-be-requested-more-than-once-per-test-return-values-are-cached. Maybe the issue comes from the fact that the register is a generator ?
In some case `--reuse-db` can be usefull.
ref : https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/2317#note_61277petitminionpetitminionhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2277Api v2 transition documentation2024-01-30T10:58:56ZpetitminionApi v2 transition documentationWe should formalize a way to migrate to api v2 in the backend code.
The related files will be duplicated :
- urls_v2.py
- view_v2.py
- test_view_v2.py
This should be write in the dev documentation.
Radio api v2 do not follow this, it...We should formalize a way to migrate to api v2 in the backend code.
The related files will be duplicated :
- urls_v2.py
- view_v2.py
- test_view_v2.py
This should be write in the dev documentation.
Radio api v2 do not follow this, it should be update.
ref : https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/2317#note_61308petitminionpetitminionhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2275III-1 Implement collection feature2024-03-22T21:05:59ZpetitminionIII-1 Implement collection feature- forum : https://forum.funkwhale.audio/d/214-whats-wrong-with-libraries-and-a-path-to-fix-them/
- spec : https://docs.funkwhale.audio/develop/specs/collections/index.html- forum : https://forum.funkwhale.audio/d/214-whats-wrong-with-libraries-and-a-path-to-fix-them/
- spec : https://docs.funkwhale.audio/develop/specs/collections/index.htmlpetitminionpetitminionhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2274Implement new Upload API2024-02-05T12:43:36ZGeorg KrauseImplement new Upload APISpec: https://docs.funkwhale.audio/develop/specs/upload-process/index.html#backend-behaviorSpec: https://docs.funkwhale.audio/develop/specs/upload-process/index.html#backend-behaviorGeorg KrauseGeorg Krausehttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2273Update docs to get code from release assets2024-01-15T08:33:36ZGeorg KrauseUpdate docs to get code from release assetsThe following discussion from !2698 should be addressed:
- [ ] @georgkrause started a [discussion](https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/2698#note_60825): (+5 comments)
> Currently the download URL for t...The following discussion from !2698 should be addressed:
- [ ] @georgkrause started a [discussion](https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/2698#note_60825): (+5 comments)
> Currently the download URL for those assets would be:
>
> ```
> $git-ref=release-assets # might be develop, stable or a tag name
> $component=api|front
> $last-tag=1.4.0
> https://dev.funkwhale.audio/api/v4/projects/17/packages/generic/funkwhale/$git-ref/funkwhale-$component-$last-tag.zip
> ```
>
> @Sporiff I think for the docs we need to change this in order to make sure we can download with a fixed URL, right? Should we remove the version from the filename for this?
The correct URL now is `https://dev.funkwhale.audio/api/v4/projects/17/packages/generic/funkwhale/$git-ref/funkwhale-$component.zip`1.5.0https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2272FUNKWHALE_API_HOST hard-coded in the front dockerfile2024-01-11T10:02:27ZMagetiFUNKWHALE_API_HOST hard-coded in the front dockerfile<!--
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 the docker-compose.yml from https://dev.funkwhale.audio/funkwhale/funkwhale/-/blob/stable/deploy/docker-compose.yml and configure the .env according to the documentation
2. change the name of the "api" container (to "funkwhale-api", for example)
3. launch the docker compose
<!--
Describe the steps to reproduce the issue, like:
1. Visit the page at /artists/
2. Type that
3. Submit
-->
## What happens?
The "front" container does not start, because the "api" container does not exists since its name was changed.
Even if I configure the env variable `FUNKWHALE_API_IP` to the new name (eg. `funkwhale-api`), it does not work.
Even if I add "FUNKWHALE_API_IP=funkwhale-api" to the `environment` section of the docker-compose.yml, it does not work.
<!--
Describe what happens once the previous steps are completed.
-->
## What is expected?
I want to be able to change the name of each container.
It works for every container, except for the `api` one.
<!--
Describe the expected behaviour.
-->
## Context
I may be wrong, but hard-coding these two environment variables (`FUNKWHALE_API_HOST` and `FUNKWHALE_API_PORT`) in the [front dockerfile](https://dev.funkwhale.audio/funkwhale/funkwhale/-/blob/develop/front/Dockerfile?ref_type=heads#L28) may be the culprit.
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: 1.3.0 and newer.
<!--
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
-->