beetbox / beetbox/beets

musicbrainz host, https and ratelimit config options are ignored

Open
#4,518 6 comments 0 reactions 0 assignees View on GitHub
bug musicbrainz
Dominant language
Python
Stars
15.7k
Forks
2.1k
Avg merge
4d 21h
Merged PRs (30d)
31

Description

### Problem

While trying to make the `mbsync` plugin work with a selfhosted server, I noticed that the ratelimiting was not respected.
Further looking into the issue, I noticed that none of the requests were appearing in my server logs.
Not only that, but when watching the logs while doing a normal import on a fresh installation without any plugins, nothing appears either.

Edit for clarification: Beets continues to work, but sends requests to musicbrainz.org as if I didn't edit the config.

### Setup

* OS: multiple tried, behavior was consistent between NixOS and Arch Linux
* Python version: tried 3.10.5 and 3.10.8 respectively
* beets version: 1.6.0
* Turning off plugins made problem go away (yes/no): no

My configuration (output of `beet config`) is:

```yaml
# beet -c poc.yml config

musicbrainz:
host: mbserver.example.org
https: yes
ratelimit: 100

```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue with the `musicbrainz` configuration shown and inspect the `beet config` output while tracing requests made during a normal import and through the `mbsync` plugin. Done means the configured host, HTTPS setting, and ratelimit are honored, including for a self-hosted server, rather than requests going to musicbrainz.org.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.