funkwhale issueshttps://dev.funkwhale.audio/groups/funkwhale/-/issues2023-12-02T13:56:53Zhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2246Listenings sync with lb2023-12-02T13:56:53ZpetitminionListenings sync with lb- forum : https://forum.funkwhale.audio/d/406-listening-synchronization-with-listenbrainz- forum : https://forum.funkwhale.audio/d/406-listening-synchronization-with-listenbrainzpetitminionpetitminionhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/1457Broadcast and display listenings and favorites2023-12-02T13:37:01ZGeorg KrauseBroadcast and display listenings and favoritesBroadcast user listenings and favorites to followersBroadcast user listenings and favorites to followershttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/1670II-2 Calculate AcoustID of the tracks in import process2023-12-02T13:36:13ZJuniorJPDJII-2 Calculate AcoustID of the tracks in import processThis would allow us to do loads of things after that even if track doesn't have musicbrainz ID.
The examples of possibilities after this is implemented:
- extension of !1394 / #1218 to tracks not having mbid
- uploading AcoustID for tra...This would allow us to do loads of things after that even if track doesn't have musicbrainz ID.
The examples of possibilities after this is implemented:
- extension of !1394 / #1218 to tracks not having mbid
- uploading AcoustID for tracks with mbid to the upstream
- automatic grabbing of track's missing metadata and mbid if wanted
- automatic genre categorization
https://pypi.org/project/pyacoustid/petitminionpetitminionhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2253Release docker build fails2023-11-30T11:14:34ZGeorg KrauseRelease docker build failsJob [#200534](https://dev.funkwhale.audio/funkwhale/funkwhale/-/jobs/200534) failed for 0840aeb943be6e92797b6911447937d2d9443066:Job [#200534](https://dev.funkwhale.audio/funkwhale/funkwhale/-/jobs/200534) failed for 0840aeb943be6e92797b6911447937d2d9443066:1.4.0https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2252New Nginx templates don't work in Docker container2023-11-29T21:03:11ZCiarán Ainsworthsporiff@funkwhale.audioNew Nginx templates don't work in Docker container<!--
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
-->
Related to !2623. New changes to nginx templates don't work for Docker container behind reverse proxy. This appears to be a missing host (`funkwhale-front`). This occurs in both the Docker template and the reverse-proxy template.
## Steps to reproduce
<!--
Describe the steps to reproduce the issue, like:
1. Visit the page at /artists/
2. Type that
3. Submit
-->
1. Upgrade to 0c2f9c8d or later
2. Restart the container
## What happens?
<!--
Describe what happens once the previous steps are completed.
-->
The container fails to start due to an nginx error.
## What is expected?
<!--
Describe the expected behaviour.
-->
The container should start as expected.
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: 1.3.4+git.0c2f9c8d
<!--
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
-->
```log
nginx: [emerg] host not found in upstream "funkwhale-front" in /etc/nginx/conf.d/default.conf:75
```1.4.0https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/798Allow LDAP users to login via Subsonic API2023-11-29T15:42:39ZmarioAllow LDAP users to login via Subsonic API<!--
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?
LDAP users cannot log in / generate Subsonic API password
## What are the possible drawbacks or issues with the requested changes?
<!--
-->
## Context
![Screenshot_2019-04-13_at_21.11.24](/uploads/c846c1f823d2335c5de7b456746a529d/Screenshot_2019-04-13_at_21.11.24.png)
<!--
-->0.19AgateAgatehttps://dev.funkwhale.audio/funkwhale/blog.funkwhale.audio/-/issues/11Prepare Feature highlights for 1.4.02023-11-28T19:42:42ZGeorg KrausePrepare Feature highlights for 1.4.0As discussed today with @Sporiff we thought it might be helpful to have some blogposts highlighting features that are either shipped or prepared with the upcoming 1.4.0 release in order to explain better, what we are actually doing and p...As discussed today with @Sporiff we thought it might be helpful to have some blogposts highlighting features that are either shipped or prepared with the upcoming 1.4.0 release in order to explain better, what we are actually doing and planning to do.
Those are things we already merged:
* Prohibit the creation of new users using django's `createsuperuser` command in favor of our own CLI entry point. Run `funkwhale-manage fw users create --superuser` instead. (funkwhale/funkwhale#1288)
* Add a management command to generate dummy notifications for testing
* Cache radio queryset into redis. New radio track endpoint for api v2 is /api/v2/radios/sessions/{radiosessionid}/tracks (funkwhale/funkwhale#2135)
* New management command to update Uploads which have been imported using --in-place and are now stored in s3 (funkwhale/funkwhale#2156)
* Maloja: Submit album artists and duration and allow to disable server side metadata fixing
We do have more things merged which are the basements for new features, if you want me to list them to, let me know.
I am handing this over to our @funkwhale/communications team :)Ciarán Ainsworthsporiff@funkwhale.audioCiarán Ainsworthsporiff@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2248Rate Limiting endpoint fails when unauthenticated2023-11-28T18:20:43Ztheit8514Rate Limiting endpoint fails when unauthenticated<!--
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 https://docs.funkwhale.audio/swagger/
2. Configure the remote server
3. Attempt to execute /api/v1/rate-limit/
## What happens?
<!--
Describe what happens once the previous steps are completed.
-->
Swagger reports a 500 error. In the api logs the server attempts to convert the source IP address to an ident field which is int() type.
```
2023-11-10 17:29:53,281 django.request ERROR Internal Server Error: /api/v1/rate-limit/
Traceback (most recent call last):
File "/venv/lib/python3.10/site-packages/asgiref/sync.py", line 534, in thread_handler
raise exc_info[1]
File "/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 38, in inner
response = await get_response(request)
File "/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 233, in _get_response_async
response = await wrapped_callback(request, *callback_args, **callback_kwargs)
File "/venv/lib/python3.10/site-packages/asgiref/sync.py", line 479, in __call__
ret: _R = await loop.run_in_executor(
File "/venv/lib/python3.10/site-packages/asgiref/current_thread_executor.py", line 40, in run
result = self.fn(*self.args, **self.kwargs)
File "/venv/lib/python3.10/site-packages/asgiref/sync.py", line 538, in thread_handler
return func(*args, **kwargs)
File "/usr/lib/python3.10/contextlib.py", line 79, in inner
return func(*args, **kwds)
File "/venv/lib/python3.10/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view
return view_func(*args, **kwargs)
File "/venv/lib/python3.10/site-packages/django/views/generic/base.py", line 70, in view
return self.dispatch(request, *args, **kwargs)
File "/venv/lib/python3.10/site-packages/rest_framework/views.py", line 509, in dispatch
response = self.handle_exception(exc)
File "/venv/lib/python3.10/site-packages/rest_framework/views.py", line 469, in handle_exception
self.raise_uncaught_exception(exc)
File "/venv/lib/python3.10/site-packages/rest_framework/views.py", line 480, in raise_uncaught_exception
raise exc
File "/venv/lib/python3.10/site-packages/rest_framework/views.py", line 506, in dispatch
response = handler(request, *args, **kwargs)
File "/app/funkwhale_api/common/views.py", line 151, in get
return response.Response(serializers.RateLimitSerializer(data).data, status=200)
File "/venv/lib/python3.10/site-packages/rest_framework/serializers.py", line 555, in data
ret = super().data
File "/venv/lib/python3.10/site-packages/rest_framework/serializers.py", line 253, in data
self._data = self.to_representation(self.instance)
File "/venv/lib/python3.10/site-packages/rest_framework/serializers.py", line 522, in to_representation
ret[field.field_name] = field.to_representation(attribute)
File "/venv/lib/python3.10/site-packages/rest_framework/serializers.py", line 522, in to_representation
ret[field.field_name] = field.to_representation(attribute)
File "/venv/lib/python3.10/site-packages/rest_framework/fields.py", line 915, in to_representation
return int(value)
ValueError: invalid literal for int() with base 10: '192.168.225.90'
```
## What is expected?
<!--
Describe the expected behaviour.
-->
The rate-limit api should return the unauthenticated rate-limit values.
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: 1.3.3
<!--
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.4.0Georg KrauseGeorg Krausehttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2208OpenGraph Meta tags missing2023-11-28T13:26:46ZDistopicoOpenGraph Meta tags missing<!--
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 `/library/tracks/3696/` e.g https://music.distopico.info/library/tracks/3696/
2. Open browser console
3. Check that meta tags are missing, for example `og:image` etc
-->
## What happens?
<!--
Describe what happens once the previous steps are completed.
-->
`<meta ..>` tags are missing even looks like are already defined: https://dev.funkwhale.audio/funkwhale/funkwhale/-/blob/develop/api/funkwhale_api/music/spa_views.py?ref_type=heads but is not coming from SSR o CSR, use to work before upgrade to 1.3.1 from 1.2.x
<!--
Describe the expected behaviour.
-->
![screenshot-2023-08-16_08-56-36](/uploads/8c23058f6b073868c52cadbbc5ae015f/screenshot-2023-08-16_08-56-36.png)
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: 1.3.x
In debian instalation
<!--
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/1538Connect loglevel and debug mode2023-11-24T14:09:20ZGeorg KrauseConnect loglevel and debug modeCopy and pasted from !1327:
I indeed think its useful to have `loglevel=debug` even without `debug=true`, since the latter will show error messages to the users and might expose information. So we should add documentation for this. But ...Copy and pasted from !1327:
I indeed think its useful to have `loglevel=debug` even without `debug=true`, since the latter will show error messages to the users and might expose information. So we should add documentation for this. But I still think its a good idea to set `loglevel=debug` automatically when `debug=true`, which still allows to set the loglevel however you want if debug mode is turned off.1.4.0Georg KrauseGeorg Krausehttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2251Embed fails to load2023-11-23T12:18:18ZCiarán Ainsworthsporiff@funkwhale.audioEmbed fails to load<!--
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 a track on Funkwhale and select **Embed**
2. Copy the embed code
3. Paste the resulting iframe into a web page
<!--
Describe the steps to reproduce the issue, like:
1. Visit the page at /artists/
2. Type that
3. Submit
-->
## What happens?
<!--
Describe what happens once the previous steps are completed.
-->
The embed player fails to load any content.
## What is expected?
<!--
Describe the expected behaviour.
-->
The embed player should show the track and enable people to play it.
## Context
<!--
The version of your instance can be found on the footer : Source code (x.y)
-->
**Funkwhale version(s) affected**: >= 1.3.3
<!--
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
-->
There appear to be two issues. The first was reported in the Support room and the second in my testing.
1. There appears to be a CSS issue for some users (on a Docker installation, possibly related to the new template)
![image](/uploads/1d6ab9ed31e29ff832f719d73d5d0b0c/image.png)
2. I get a Javascript error when attempting to load the track.
```
TypeError: source.test is not a function
getAudioSources https://tanukitunes.com/embed.html?&type=track&id=59745:85
fetchTracks https://tanukitunes.com/embed.html?&type=track&id=59745:171
fetchTracks https://tanukitunes.com/embed.html?&type=track&id=59745:165
embed.html:183:17
<anonymous> https://tanukitunes.com/embed.html?&type=track&id=59745:183
TypeError: source.test is not a function
getAudioSources https://tanukitunes.com/embed.html?&type=track&id=59745:85
fetchTracks https://tanukitunes.com/embed.html?&type=track&id=59745:171
fetchTracks https://tanukitunes.com/embed.html?&type=track&id=59745:165
async* https://tanukitunes.com/embed.html?&type=track&id=59745:182
embed.html:183:17
<anonymous> https://tanukitunes.com/embed.html?&type=track&id=59745:183
(Async: promise callback)
<anonymous> https://tanukitunes.com/embed.html?&type=track&id=59745:182
```1.4.0https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2085IV - 5 New version of the nodeinfo endpoint (nodeinfo 2.1)2023-11-23T10:57:51ZpetitminionIV - 5 New version of the nodeinfo endpoint (nodeinfo 2.1)https://forum.funkwhale.audio/d/217-nodeinfo-21/10
Specification: https://dev.funkwhale.audio/funkwhale/funkwhale/-/blob/develop/docs/specs/nodeinfo21/index.mdhttps://forum.funkwhale.audio/d/217-nodeinfo-21/10
Specification: https://dev.funkwhale.audio/funkwhale/funkwhale/-/blob/develop/docs/specs/nodeinfo21/index.md1.4.0Georg KrauseGeorg Krausehttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/1939Nginx config files need diffing and updating2023-11-23T10:43:18ZJuniorJPDJNginx config files need diffing and updatingWe have 4 nginx config files which differ. At least diffing and updating need to be done.
!2039 is blocked by this as I suppose
`deploy/nginx.template` - ~~I suppose this one is config deployed by ansible?~~ Used for manual installati...We have 4 nginx config files which differ. At least diffing and updating need to be done.
!2039 is blocked by this as I suppose
`deploy/nginx.template` - ~~I suppose this one is config deployed by ansible?~~ Used for manual installations
`docker/nginx/conf.dev` - I suppose this one is config used by docker dev setup?
`front/docker/funkwhale.conf.template` - actual one used in frontend docker container
`deploy/docker.proxy.template` - ???
Another one: https://dev.funkwhale.audio/funkwhale/ansible/-/blob/master/templates/nginx.conf.j2 For our ansible deployments1.4.0Georg KrauseGeorg Krausehttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2232pin lb-matching-tools and troi deps2023-11-23T09:46:15Zpetitminionpin lb-matching-tools and troi deps<!--
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:
-->petitminionpetitminionhttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2217Archive old changelog2023-11-18T17:22:26ZGeorg KrauseArchive old changelogRight now our Changelog file is super long and contains a lot of entries that are quite old. We shouldn't remove them, but find a way to archive old entries.
My current proposal would be to only keep the current major version (eg 1.0 an...Right now our Changelog file is super long and contains a lot of entries that are quite old. We shouldn't remove them, but find a way to archive old entries.
My current proposal would be to only keep the current major version (eg 1.0 and above) in the CHANGELOG.md and move older entries to the `changes` directory, where we can name them either `CHANGELOG.{version}.md`. The naming schema is open for discussions.
@funkwhale/development1.4.0Ciarán Ainsworthsporiff@funkwhale.audioCiarán Ainsworthsporiff@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2235Update Website links in Funkwhales UI2023-11-18T15:01:32ZGeorg KrauseUpdate Website links in Funkwhales UIIn the Funkwhale source code we have the following links:
* https://funkwhale.audio/en_US/apps
* https://funkwhale.audio/en_US/code-of-conduct
* https://funkwhale.audio/support-us
* https://funkwhale.audio/help
* https://funkwhale.audio...In the Funkwhale source code we have the following links:
* https://funkwhale.audio/en_US/apps
* https://funkwhale.audio/en_US/code-of-conduct
* https://funkwhale.audio/support-us
* https://funkwhale.audio/help
* https://funkwhale.audio/#get-started
Check if they still work after the relaunch or update them accordingly1.4.0Ciarán Ainsworthsporiff@funkwhale.audioCiarán Ainsworthsporiff@funkwhale.audiohttps://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/1852Eventually wrong openapi specs2023-11-16T10:37:52ZGeorg KrauseEventually wrong openapi specsGenerating our API specification returns some warnings, which means there are incorrect specifications generated.
- [ ] Warning #0: AlbumViewSet: AlbumFilter: Unable to guess choice types from values, filter method's type hint or find "...Generating our API specification returns some warnings, which means there are incorrect specifications generated.
- [ ] Warning #0: AlbumViewSet: AlbumFilter: Unable to guess choice types from values, filter method's type hint or find "tag" in model. Defaulting to string.
- [ ] Warning #1: AlbumViewSet: AlbumCreateSerializer: could not resolve serializer field "RelatedField('uuid', allow_null=True, queryset=<AttachmentQuerySet []>, queryset_filter=<function <lambda>>, required=False, serializer=None, write_only=True)". Defaulting to "string"
- [ ] Warning #2: AlbumViewSet: AlbumCreateSerializer: could not resolve serializer field "RelatedField('id', filters=<function AlbumCreateSerializer.<lambda>>, queryset=<ArtistQuerySet []>, required=True, serializer=None)". Defaulting to "string"
- [ ] Warning #3: ArtistViewSet: ArtistFilter: Unable to guess choice types from values, filter method's type hint or find "tag" in model. Defaulting to string.
- [ ] Warning #4: ChannelViewSet: ChannelFilter: Unable to guess choice types from values, filter method's type hint or find "tag" in model. Defaulting to string.
- [ ] Warning #5: ChannelViewSet: ChannelCreateSerializer: could not resolve serializer field "RelatedField('uuid', allow_null=True, queryset=<AttachmentQuerySet []>, queryset_filter=<function <lambda>>, required=False, serializer=None, write_only=True)". Defaulting to "string"
- [ ] Warning #6: ChannelViewSet: ChannelUpdateSerializer: could not resolve serializer field "RelatedField('uuid', allow_null=True, queryset=<AttachmentQuerySet []>, queryset_filter=<function <lambda>>, required=False, serializer=None, write_only=True)". Defaulting to "string"
- [ ] Warning #7: LibraryFollowViewSet: LibraryFollowSerializer: could not resolve serializer field "RelatedField('uuid', LibrarySerializer(): Defaulting to "string"
- [ ] Warning #8: AdminSettings: GlobalPreferenceSerializer: unable to resolve type hint for function "get_identifier". Consider using a type hint or @extend_schema_field. Defaulting to string.
- [ ] Warning #9: AdminSettings: GlobalPreferenceSerializer: unable to resolve type hint for function "get_default". Consider using a type hint or @extend_schema_field. Defaulting to string.
- [ ] Warning #10: AdminSettings: GlobalPreferenceSerializer: could not resolve serializer field "PreferenceValueField()". Defaulting to "string"
- [ ] Warning #11: AdminSettings: GlobalPreferenceSerializer: unable to resolve type hint for function "get_verbose_name". Consider using a type hint or @extend_schema_field. Defaulting to string.
- [ ] Warning #12: AdminSettings: GlobalPreferenceSerializer: unable to resolve type hint for function "get_help_text". Consider using a type hint or @extend_schema_field. Defaulting to string.
- [ ] Warning #13: AdminSettings: GlobalPreferenceSerializer: unable to resolve type hint for function "get_additional_data". Consider using a type hint or @extend_schema_field. Defaulting to string.
- [ ] Warning #14: AdminSettings: GlobalPreferenceSerializer: unable to resolve type hint for function "get_field". Consider using a type hint or @extend_schema_field. Defaulting to string.
- [ ] Warning #15: PluginViewSet: Serializer: Component name "" contains illegal characters. Only "A-Z a-z 0-9 - . _" are allowed. Furthermore, "-" and "." are discoursed due to potential tooling issues. This likely leads to an invalid schema.
- [ ] Warning #16: TrackViewSet: TrackFilter: Unable to guess choice types from values, filter method's type hint or find "tag" in model. Defaulting to string.
- [ ] Warning #17: TrackViewSet: TrackFilter: Unable to guess choice types from values, filter method's type hint or find "artist" in model. Defaulting to string.
- [ ] Warning #18: UploadViewSet: UploadForOwnerSerializer: could not resolve serializer field "RelatedField('uuid', LibraryForOwnerSerializer(): Defaulting to "string"
- [ ] Warning #20: UserViewSet: UserWriteSerializer: could not resolve serializer field "RelatedField('uuid', queryset=<AttachmentQuerySet []>, queryset_filter=<function UserWriteSerializer.<lambda>>, serializer=None, write_only=True)". Defaulting to "string"https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/1849Provide generated openapi specs2023-11-16T10:37:33ZGeorg KrauseProvide generated openapi specsThis is an ongoing effort to provide automatically generated, up-to-date and valid specification of our API.
Currently we already went most of the way, its still a lot to do.
The advantage is that developers of tools using our API hav...This is an ongoing effort to provide automatically generated, up-to-date and valid specification of our API.
Currently we already went most of the way, its still a lot to do.
The advantage is that developers of tools using our API have more accurate, up to date information and implementation of clients should be easier. Additionally we can generate client libraries which can be used by a variety of tools.
The library we are using is [drf-spectacular](https://drf-spectacular.readthedocs.io/en/latest/), which does a great job. The latest version for the develop branch can be found [here](https://docs.funkwhale.audio/swagger/?url=https://dev.funkwhale.audio/funkwhale/funkwhale/-/jobs/artifacts/develop/raw/docs/schema.yml?job%3Dbuild_docs).1.4.0https://dev.funkwhale.audio/funkwhale/funkwhale-android/-/issues/148Funkwhale authentication page failing to redirect back to app on Android 142023-11-15T07:52:20ZAMoonRabbitFunkwhale authentication page failing to redirect back to app on Android 14**Describe the bug**
With the release of Android 14, it has been noted that the Funkwhale Android app can no longer authenticate successfully.
**How to reproduce**
1. Enter pod URL and tap the LOG IN button
2. Use the auth button at ...**Describe the bug**
With the release of Android 14, it has been noted that the Funkwhale Android app can no longer authenticate successfully.
**How to reproduce**
1. Enter pod URL and tap the LOG IN button
2. Use the auth button at the bottom of the page
3. See infinite loading, or the session opens an identical browser session with infinite loading.
**Expected behavior**
When you tap the Authorise button at the bottom of the page, the session should be handed back to the Android app to complete authentication.
**Actual behavior**
Redirection back to the application does not occur, instead either remaining in the browser session or opening an additional browser session.
**Environment details**
- Device: Google Pixel 6a
- Android version: Android 14
- App version: 0.2.1-1
**Logs**
Logs taken from Android 14
[FunkwhaleAndroidADB.txt](/uploads/f95277af5d5ad005eb4fdca700534886/FunkwhaleAndroidADB.txt)https://dev.funkwhale.audio/funkwhale/funkwhale/-/issues/2247service "typesense" refers to undefined network internal: invalid compose pro...2023-11-13T08:13:00ZGeorg Krauseservice "typesense" refers to undefined network internal: invalid compose projectThere is no such thing as a network `internal`
https://dev.funkwhale.audio/funkwhale/funkwhale/-/blob/develop/deploy/docker-compose.yml?ref_type=heads#L102There is no such thing as a network `internal`
https://dev.funkwhale.audio/funkwhale/funkwhale/-/blob/develop/deploy/docker-compose.yml?ref_type=heads#L1021.4.0petitminionpetitminion