David S

I'm having this issue as well, the provided Curl command results in a 404 error message being dumped into the target file, which makes the shell login mildly unhappy.

This is still happening. Now the URL in the cURL script at https://docs.docker.com/compose/completion/#bash is pointing to v2.6.1, but it remains a 404. Edit: Starting in the >2.0.0-tagged Docker Compose repo,...

I'd like to see this feature added as well.

/remove-lifecycle stale The documentation appears to have been updated to not mention Bash completion anymore at all. Can anyone else verify?

I used the autodiscovery functionality to connect to my Jellyfin server. However, it appears you are correct, judging by the server listing in Swiftfin, it says HTTP and not HTTPS...

I also noticed that on the Servers screen, where it shows my autodiscovered server, it's showing "http:jellyfin.mydomain.com", missing the // in the protocol. Could this be the reason it's failing...

I just ran into this as well. The watched status is instantly removed when playback is started, whereas I'd prefer to be able to either have it not mark it...

Just to add onto this, I noticed that UI elements pinned to the bottom-center of the screen (the dragonriding vigor UI, the NPC speech bubbles, etc) are appearing much lower...