funkwhale issueshttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues2023-07-07T10:47:18Zhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2179Embed: An unknown error occurred while loading this artist.2023-07-07T10:47:18ZtusooaEmbed: An unknown error occurred while loading this artist.<!--
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:
-->
I got "An unknown error occurred while loading this artist." when I try to open up the embed.
JavaScript console:
```
TypeError: track.album is null
fetchTracks https://[redacted]/embed.html?type=artist&id=1:164
fetchTracks https://[redacted]/embed.html?type=artist&id=1:159
async* https://[redacted]/embed.html?type=artist&id=1:176
embed.html:177:17
<anonymous> https://[redacted]/embed.html?type=artist&id=1:177
(Async: promise callback)
<anonymous> https://[redacted]/embed.html?type=artist&id=1:176
```https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2178Starting a radio does not clear the queue.2023-07-07T04:03:35ZKasper Sewerynwvffle@funkwhale.audioStarting a radio does not clear the queue.UI/UX is inconsistent in some cases. One of such cases is playing an album, track or playlist. When user does so, it clears the queue and enqueues the desired thing by default. However when it comes to radios, when we start a radio, the ...UI/UX is inconsistent in some cases. One of such cases is playing an album, track or playlist. When user does so, it clears the queue and enqueues the desired thing by default. However when it comes to radios, when we start a radio, the radio tracks are being enqueued without clearing previous queue.
Although we already have an issue that is titled exactly the same, this issue is about inconsistency in the UX rather than a bug. If you read through #343, you can conclude that this behavior is desired and by design. In my opinion in somewhat hurts the UX and should be changed.https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2177Can't follow funkwhale channel or user from pleroma2023-10-27T04:24:19ZtusooaCan't follow funkwhale channel or user from pleroma<!--
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:
-->
0. Follow a funkwhale (1.3.1) channel or user from Pleroma (2.5.2)
1. It gets stuck at "request sent"
See also: https://git.pleroma.social/pleroma/pleroma/-/issues/2539https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2175Bad Fediverse federation upon server migration2023-07-29T11:07:00ZMarcel CostaBad Fediverse federation upon server migration<!--
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. Migrate from a working server to a new one following [the backup restoration guide](https://docs.funkwhale.audio/administrator/upgrade/backup.html#restore-a-backup).
2. Trying to see a track from another Fediverse software server (tried Mastodon and Akkoma).
## What happens?
I have migrated one instance that was working ok and now federation is malfunctioning.
Inside our server everything is ok, but from mastodon and akkoma, when trying to see a track by its URL they don't show up. In addition, when following a channel from akkoma it sticks in "Waiting for confirmation".
<!--
Describe what happens once the previous steps are completed.
-->
## What is expected?
<!--
Describe the expected behaviour.
-->
Songs should appear when searched in other Fediverse software (in order to boost them and share them). It worked before the server migration.
## 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
-->
**Server OS version**: ubuntu-20.04-x86_64
I have looked some logs in the server and found nothing that points me to what's happening, but I may be missing the correct ones!
Thanks in advance for any help you can provide and for the amazing job you are doing. Funkwhale is filling a demand so much needed, in my opinion.https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2174Renovate improvements2023-07-06T09:04:18ZGeorg KrauseRenovate improvementsDuring the use of renovate we got a few improvements that would help us:
* maybe we want to add a higher priority on the stable branch, and merge the stable branch in develop everyweek. This would deduplicate the amount of renovate MRs....During the use of renovate we got a few improvements that would help us:
* maybe we want to add a higher priority on the stable branch, and merge the stable branch in develop everyweek. This would deduplicate the amount of renovate MRs. (by @jooola)
* Reduce the noise for some packages, eg boto by using https://docs.renovatebot.com/noise-reduction/https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2171update frontend to radio session track api v22024-01-26T15:14:56Zpetitminionupdate frontend to radio session track api v2following https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/2430.following https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/2430.https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2170Run integration tests against current API and front2023-06-22T04:23:20ZKasper Sewerynwvffle@funkwhale.audioRun integration tests against current API and frontThe following discussion from !1795 should be addressed:
- [ ] @wvffle started a [discussion](https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/1795#note_53178): (+5 comments)
> The tests are now run entirely on `de...The following discussion from !1795 should be addressed:
- [ ] @wvffle started a [discussion](https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/1795#note_53178): (+5 comments)
> The tests are now run entirely on `demo.funkwhale.audio`, right? Is there a way to run them against API and and frontend that are in the repo?https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2167Speed-up frontend related pipeline2023-06-21T08:23:27ZGeorg KrauseSpeed-up frontend related pipelineThe following discussion from !1795 should be addressed:
- [ ] @wvffle started a [discussion](https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/1795#note_53159): (+1 comment)
> Couldn't we have a common `prepare_fro...The following discussion from !1795 should be addressed:
- [ ] @wvffle started a [discussion](https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/1795#note_53159): (+1 comment)
> Couldn't we have a common `prepare_front` step that would install the dependencies and use it to save the time on installing dependencies for `lint_front`, `test_front` and `test_integration`?https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2165"Accountless report categories" allow sending reports to other instances on b...2023-06-19T07:57:32ZInex Code"Accountless report categories" allow sending reports to other instances on behalf of the service userWhen there are active accountless report categories, the instance can be anonymously used to send ActivityPub spam to other instances by reporting federating content. The better behavior would be to only allow reporting local content ano...When there are active accountless report categories, the instance can be anonymously used to send ActivityPub spam to other instances by reporting federating content. The better behavior would be to only allow reporting local content anonymously.
I got a heads-up from the admin of another instance when during an authorized penetration testing automated tools created a dozen of reports on their content.https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2158No sound when launch track2024-02-06T07:27:51ZGerald BigotNo sound when launch track<!--
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. Launch "Play" button : no sound and no timer
## What happens?
<!--
Describe what happens once the previous steps are completed.
-->
## What is expected?
<!--
Describe the expected behaviour.
-->
Play track with sound
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: 1.2.10
<!--
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
-->
Mozilla Firefox and Chromium
Apache2 as proxyGeorg KrauseGeorg Krausehttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2152`.ui.positive.message` colored wrong in dark theme since version 1.3.02023-06-09T08:45:19ZJulian Rademacher`.ui.positive.message` colored wrong in dark theme since version 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. Visit the page at /artists/
2. Type that
3. Submit
-->
1. Visit the page at /about
2. Switch theme to dark if light theme is applied
3. Make sure you are logged in
## What happens?
<!--
Describe what happens once the previous steps are completed.
-->
In element `.signup-form.content` ("Sign up") `.ui.positive.message` seems to be colored wrong in dark theme.
## What is expected?
<!--
Describe the expected behaviour.
-->
Element `.ui.positive.message` should be colored in another way.
## 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
-->
- tested on Google Chrome version 114.0.5735.90
- self hosted with [YunoHost](https://yunohost.org/)
![about](/uploads/1ccb9e7f7b2cef8c41d814d32a65176c/about.png)https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2143II-4 Improve Funkwhale tagging and genre discovery2024-02-10T16:13:01ZpetitminionII-4 Improve Funkwhale tagging and genre discoveryAdd a full list of genre tags and implement new discovery pages for similarly tagged content. This feature introduces a prepopulated set of genre and subgenre tags to improve the Funkwhale content discovery mechanics. These can be used t...Add a full list of genre tags and implement new discovery pages for similarly tagged content. This feature introduces a prepopulated set of genre and subgenre tags to improve the Funkwhale content discovery mechanics. These can be used to improve the following: • Genre and subgenre tag searching in the frontend • Content radios • Recommendations listed on track/album/artist pages. Users can continue to use custom tags, but these base genre tags will be configured to benefit from aliasing to associate similar tags and make discovering related content easier. (€ 1250)
endpoints :
https://musicbrainz.org/ws/2/genre/all
https://musicbrainz.org/ws/2/genre/db325bd7-ae64-40bd-966a-a3af3cef8bb9
- forum : https://forum.funkwhale.audio/d/259-improve-genre-tag-system-by-following-mb-metodology/11
- spec : https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/2592
- blocked by : https://tickets.metabrainz.org/browse/MBS-12368 https://github.com/metabrainz/musicbrainz-server/pull/2518petitminionpetitminionhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2141IV-1 GDPR : Add ability to retrieve uploaded files (rate limited endpoint/adm...2024-02-02T18:20:13ZpetitminionIV-1 GDPR : Add ability to retrieve uploaded files (rate limited endpoint/admin approval)https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2140IV-1 GDPR : Redirect a profile to a new account2023-12-05T13:56:58ZpetitminionIV-1 GDPR : Redirect a profile to a new accountRedirect a profile to a new account using Webfinger and moving users to the new profile, do this recursively for channels and collections
* Implement API for moving files when a user redirects their account (only collections)
* Channels...Redirect a profile to a new account using Webfinger and moving users to the new profile, do this recursively for channels and collections
* Implement API for moving files when a user redirects their account (only collections)
* Channels move separately given that they might be owned by multiple peoplehttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2139IV-1 GDPR : Data protection policy2023-05-26T11:03:34ZpetitminionIV-1 GDPR : Data protection policyProvide a mechanism for linking to a data protection policy + provide a default template for how Funkwhale the software stores informationProvide a mechanism for linking to a data protection policy + provide a default template for how Funkwhale the software stores informationhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2138IV-1 GDPR : Provide a mechanism for extracting uploaded data (MVP)2023-12-20T00:16:43ZpetitminionIV-1 GDPR : Provide a mechanism for extracting uploaded data (MVP)
* RSS feeds
* Download channel/profile data
* Listenings
* Favorites
* Collections
* Playlists
* RSS feeds
* Download channel/profile data
* Listenings
* Favorites
* Collections
* Playlistshttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2132Simplify emit definitions2023-05-19T07:24:53ZGeorg KrauseSimplify emit definitions@wvffle wrote:
> we can now write emit definitions (`Events` type in our code) in much more cleaner way:
>
> ```diff
> interface Events {
> - (e: 'submit', value: string): void
> + submit: [value: string]
> }
> ```@wvffle wrote:
> we can now write emit definitions (`Events` type in our code) in much more cleaner way:
>
> ```diff
> interface Events {
> - (e: 'submit', value: string): void
> + submit: [value: string]
> }
> ```https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2131Replace duplicated script tags with defineOptions2023-12-12T08:35:06ZGeorg KrauseReplace duplicated script tags with defineOptionsWe can replace the duplicated `<script>` tags with `defineOptions`We can replace the duplicated `<script>` tags with `defineOptions`1.5.0Kasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2130Use imported types in props2023-05-17T11:38:16ZGeorg KrauseUse imported types in propsWe can now safely use the imported types in props. We already have the TODOs for that, so I'd do it either in this MR or create an issue for itWe can now safely use the imported types in props. We already have the TODOs for that, so I'd do it either in this MR or create an issue for itKasper Sewerynwvffle@funkwhale.audioKasper Sewerynwvffle@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2128Document typesense2023-05-16T12:03:58ZpetitminionDocument typesenseAdd typesense doc
1. Docker setup :
To enable typesense we must :
- Setup TYPESENSE_API_KEY in env file
- run : `docker compose --profile typesense -f dev.yml up`
2. Debian setup :
\\to doAdd typesense doc
1. Docker setup :
To enable typesense we must :
- Setup TYPESENSE_API_KEY in env file
- run : `docker compose --profile typesense -f dev.yml up`
2. Debian setup :
\\to dopetitminionpetitminion