[listenbrainz-server] dependabot-preview[bot] opened pull request #1217 (master…dependabot/pip/eventlet-0.30.0): Bump eventlet from 0.29.1 to 0.30.0 https://github.com/metabrainz/listenbrainz-serv...
[listenbrainz-server] dependabot-preview[bot] opened pull request #1218 (master…dependabot/pip/flask-testing-0.8.1): Bump flask-testing from 0.8.0 to 0.8.1 https://github.com/metabrainz/listenbrainz-serv...
[listenbrainz-server] dependabot-preview[bot] opened pull request #1219 (master…dependabot/pip/unidecode-1.1.2): Bump unidecode from 1.1.1 to 1.1.2 https://github.com/metabrainz/listenbrainz-serv...
[listenbrainz-server] dependabot-preview[bot] opened pull request #1220 (master…dependabot/pip/setproctitle-1.2.1): Bump setproctitle from 1.1.10 to 1.2.1 https://github.com/metabrainz/listenbrainz-serv...
[listenbrainz-server] dependabot-preview[bot] opened pull request #1222 (master…dependabot/pip/flask-socketio-5.0.1): Bump flask-socketio from 4.3.2 to 5.0.1 https://github.com/metabrainz/listenbrainz-serv...
Hi! I have a question about musicbrainzngs: When a release has more than 500 tracks and you look it up, the data is incomplete (no work-level-rels among others). Other than the number of tracks, is there a way to tell from the output that the request is too big?