#metabrainz

/

      • d4rkie has quit
      • 2021-02-03 03403, 2021

      • Nyanko-sensei joined the channel
      • 2021-02-03 03435, 2021

      • repo has quit
      • 2021-02-03 03444, 2021

      • spuniun has quit
      • 2021-02-03 03446, 2021

      • kloeri has quit
      • 2021-02-03 03425, 2021

      • spuniun joined the channel
      • 2021-02-03 03411, 2021

      • kloeri joined the channel
      • 2021-02-03 03454, 2021

      • repo joined the channel
      • 2021-02-03 03445, 2021

      • sampsyo has quit
      • 2021-02-03 03413, 2021

      • sampsyo joined the channel
      • 2021-02-03 03414, 2021

      • ephemer0l has quit
      • 2021-02-03 03432, 2021

      • ephemer0l_ joined the channel
      • 2021-02-03 03409, 2021

      • BrainzGit
        [listenbrainz-server] jdaok opened pull request #1270 (master…LB-806-connection): LB-806: Importer connection https://github.com/metabrainz/listenbrainz-server…
      • 2021-02-03 03421, 2021

      • BrainzGit
        [musicbrainz-server] reosarevok opened pull request #1890 (master…MBS-11360): MBS-11360: Work around unconsistent name for RG type https://github.com/metabrainz/musicbrainz-server/…
      • 2021-02-03 03405, 2021

      • reosarevok
        bitmap, yvanzo ^ guess we never tested the alias form for RGs. Also why the hell do we do this :D
      • 2021-02-03 03444, 2021

      • reosarevok
        Maybe we should hotfix after all tho, this is not only an annoyance but literally blocks alias editing for RGs. Not that people do it much, but.
      • 2021-02-03 03454, 2021

      • reosarevok grumbles
      • 2021-02-03 03424, 2021

      • BestSteve has quit
      • 2021-02-03 03428, 2021

      • BestSteve joined the channel
      • 2021-02-03 03410, 2021

      • NirriN joined the channel
      • 2021-02-03 03434, 2021

      • NirriN has quit
      • 2021-02-03 03443, 2021

      • scory joined the channel
      • 2021-02-03 03416, 2021

      • NirriN joined the channel
      • 2021-02-03 03416, 2021

      • nawcom has quit
      • 2021-02-03 03410, 2021

      • nawcom joined the channel
      • 2021-02-03 03444, 2021

      • NirriN has quit
      • 2021-02-03 03453, 2021

      • scory has quit
      • 2021-02-03 03449, 2021

      • yvanzo
        reosarevok: reviewed PRs 1887, 1888 and 1890; These are the only ones to be applied as hotfix?
      • 2021-02-03 03436, 2021

      • ruaok
        moooin!
      • 2021-02-03 03435, 2021

      • reosarevok
        yvanzo: I'd say so :)
      • 2021-02-03 03425, 2021

      • yvanzo
        reosarevok: I updated docker server configs for Italian localization (forgot to do it on Monday).
      • 2021-02-03 03444, 2021

      • reosarevok
        Thanks
      • 2021-02-03 03402, 2021

      • Gazooo7949440 has quit
      • 2021-02-03 03405, 2021

      • sampsyo has quit
      • 2021-02-03 03445, 2021

      • Gazooo7949440 joined the channel
      • 2021-02-03 03415, 2021

      • yvanzo
        reosarevok: I would be happy to merge them asap (maybe just after adding a test for rym on recording).
      • 2021-02-03 03401, 2021

      • sampsyo joined the channel
      • 2021-02-03 03422, 2021

      • reosarevok
        yvanzo: how would we test rym on recording?
      • 2021-02-03 03430, 2021

      • reosarevok
        (there's no recording URL to test)
      • 2021-02-03 03449, 2021

      • yvanzo
        reosarevok: just with any RYM URL (single release for example) and only_valid_...: []
      • 2021-02-03 03434, 2021

      • yvanzo
        (single release or work)
      • 2021-02-03 03421, 2021

      • reosarevok
        But shouldn't only_valid still include work or whatever?
      • 2021-02-03 03449, 2021

      • reosarevok
        Since that will be valid
      • 2021-02-03 03433, 2021

      • reosarevok
        Or does input_entity_type change the results of only_valid_entity_types ?
      • 2021-02-03 03458, 2021

      • yvanzo
        Oh right :P
      • 2021-02-03 03415, 2021

      • reosarevok
        And as such, we're already testing all others :D
      • 2021-02-03 03424, 2021

      • reosarevok
        (so is there anything to add?)
      • 2021-02-03 03438, 2021

      • reosarevok
        I mean I could make one input_entity_type: 'recording' but
      • 2021-02-03 03443, 2021

      • yvanzo
        reosarevok: You’re right, denying recording for known URL patterns is already tested, and there is nothing else that would potentially match it on RYM. Approved :)
      • 2021-02-03 03424, 2021

      • reosarevok
        Ok :)
      • 2021-02-03 03447, 2021

      • reosarevok
      • 2021-02-03 03400, 2021

      • yvanzo
        reosarevok: The test for 1890 could be added later on as we just hand-tested it.
      • 2021-02-03 03401, 2021

      • reosarevok
        I expect that'd require a selenium test or something?
      • 2021-02-03 03412, 2021

      • reosarevok
        I'm still not sure why the hell that's hardcoded to "rg", by the way
      • 2021-02-03 03425, 2021

      • yvanzo
        Hand-testing is ok at release time, having a CI test is to avoid regressions in the future.
      • 2021-02-03 03417, 2021

      • reosarevok
        But I guess it's not sensible to look into changing that now *even if it was doable* (and it might not be, maybe we have stuff in edit data json or somewhere also stored as "rg")
      • 2021-02-03 03431, 2021

      • reosarevok
        So probably better to just do this for now
      • 2021-02-03 03445, 2021

      • reosarevok
        I should make sure nothing breaks with RG alias edit display just in case
      • 2021-02-03 03402, 2021

      • reosarevok
        Seems to work fine
      • 2021-02-03 03411, 2021

      • reosarevok
        If you want to merge then that's ok with me
      • 2021-02-03 03451, 2021

      • reosarevok
        (I'd also be ok with waiting for bitmap but these are small changes so there's probably no need)
      • 2021-02-03 03435, 2021

      • reosarevok
        yvanzo: merge these to master, then master into beta, then beta into prod?
      • 2021-02-03 03442, 2021

      • reosarevok
        Then release both beta and prod?
      • 2021-02-03 03421, 2021

      • BrainzGit
        [musicbrainz-server] yvanzo merged pull request #1887 (master…MBS-11357): MBS-11357: Allow linking RateYourMusic to release groups https://github.com/metabrainz/musicbrainz-server/…
      • 2021-02-03 03445, 2021

      • BrainzGit
        [musicbrainz-server] yvanzo merged pull request #1888 (master…MBS-11358): MBS-11358: Allow alias sort name to be blank https://github.com/metabrainz/musicbrainz-server/…
      • 2021-02-03 03405, 2021

      • BrainzGit
        [musicbrainz-server] yvanzo merged pull request #1890 (master…MBS-11360): MBS-11360: Work around unconsistent name for RG type https://github.com/metabrainz/musicbrainz-server/…
      • 2021-02-03 03419, 2021

      • yvanzo
        reosarevok: There's probably no need for such small fixes and it will unblock users 6h earlier at least.
      • 2021-02-03 03416, 2021

      • reosarevok
        Ok
      • 2021-02-03 03423, 2021

      • reosarevok
        I can do the release
      • 2021-02-03 03429, 2021

      • reosarevok
        Unless you want to :)
      • 2021-02-03 03408, 2021

      • yvanzo
        reosarevok: Yes please, I just updated translations in master, that's it. (POT files do not need to be updated/pushed again.)
      • 2021-02-03 03422, 2021

      • reosarevok
        Ok!
      • 2021-02-03 03435, 2021

      • reosarevok
        Do we need a new tag too?
      • 2021-02-03 03451, 2021

      • yvanzo
        2021-02-03-hotfixes
      • 2021-02-03 03400, 2021

      • reosarevok
        Ok
      • 2021-02-03 03420, 2021

      • yvanzo
        But no need of a new blog post, we will just amend it, so you can set the same tag message as for v-2021-02-01.
      • 2021-02-03 03435, 2021

      • yvanzo
        oops, tag should be: v-2021-02-03-hotfixes
      • 2021-02-03 03410, 2021

      • yvanzo
        script/tag.sh will let you customize these details
      • 2021-02-03 03441, 2021

      • reosarevok
        Ok
      • 2021-02-03 03449, 2021

      • reosarevok
        Yeah, I know :) Thans
      • 2021-02-03 03452, 2021

      • reosarevok
        Thanks even :D
      • 2021-02-03 03406, 2021

      • reosarevok
        Let's start with beta
      • 2021-02-03 03445, 2021

      • Rohan_Pillai joined the channel
      • 2021-02-03 03455, 2021

      • reosarevok
      • 2021-02-03 03411, 2021

      • reosarevok
        Thought I broke something, but "There were unauthenticated packages and -y was used without --allow-unauthenticated"
      • 2021-02-03 03432, 2021

      • reosarevok
        Have you gotten this before?
      • 2021-02-03 03410, 2021

      • Rohan_Pillai has quit
      • 2021-02-03 03409, 2021

      • yvanzo
        reosarevok: not the first time yarn's signature gets broken, it's yearly, at least.
      • 2021-02-03 03425, 2021

      • iliekcomputers
        shameless plug, but if it helps the environment, worth it. we should consider using Stripe Climate. https://stripe.com/en-ie/climate
      • 2021-02-03 03431, 2021

      • yvanzo
        reosarevok: docker/yarn_pubkey.txt needs to be updated
      • 2021-02-03 03423, 2021

      • reosarevok
        yvanzo: hmm, ok. Where do I get the latest pubkey from?
      • 2021-02-03 03423, 2021

      • reosarevok
        iliekcomputers: how does this work? We don't get a lot of payments I expect, but
      • 2021-02-03 03458, 2021

      • iliekcomputers
        I'm not sure what volume of donations we get via stripe, i figure it's not a large fraction, but it essentially earmarks 1-5% of that volume for carbon capture, based on what we choose.
      • 2021-02-03 03450, 2021

      • reosarevok
        I expect it's close to nothing but I'd be in favor of doing this I guess if we already have this set up anyway
      • 2021-02-03 03454, 2021

      • reosarevok
        yvanzo: the one in https://classic.yarnpkg.com/en/docs/nightly/ seems to match what we have
      • 2021-02-03 03403, 2021

      • reosarevok
      • 2021-02-03 03412, 2021

      • reosarevok
        Oh nvm, only the start is the same
      • 2021-02-03 03415, 2021

      • reosarevok
        Let's see
      • 2021-02-03 03402, 2021

      • yvanzo
        they use to update the subkey only
      • 2021-02-03 03421, 2021

      • yvanzo
        check keyservers maybe
      • 2021-02-03 03447, 2021

      • yvanzo
        check also issues for yarn on github
      • 2021-02-03 03419, 2021

      • CatQuest make a kniting refrence noone thinks is funny
      • 2021-02-03 03446, 2021

      • reosarevok
        Yeah, that new key worked
      • 2021-02-03 03453, 2021

      • reosarevok
        CatQuest: knitting seems hard.
      • 2021-02-03 03457, 2021

      • reosarevok
        (unrelated to puns, but)
      • 2021-02-03 03437, 2021

      • reosarevok
        Updating beta
      • 2021-02-03 03429, 2021

      • Mr_Monkey
        Continuing on this *thread*: What do pirates knit with?
      • 2021-02-03 03436, 2021

      • Mr_Monkey
        YARRRRN !
      • 2021-02-03 03413, 2021

      • reosarevok
        Updating prod
      • 2021-02-03 03408, 2021

      • kuno
        hm, I cannot authenticate with ListenBrainz via OAuth? the OAuth flow only gives me access to the MusicBrainz API, not ListenBrainz?
      • 2021-02-03 03409, 2021

      • shivam-kapila
        kuno: for accessing any of the *brainz projects you only neex a musicbtainz account
      • 2021-02-03 03419, 2021

      • shivam-kapila
        need*
      • 2021-02-03 03406, 2021

      • kuno
        I have a MusicBrainz account, and I authenticated it with via OAuth. So I have a refresh token and an access token. But it seems the access token doesn't work with the ListenBrainz API endpoints.
      • 2021-02-03 03413, 2021

      • iliekcomputers
        kuno: yeah, the ListenBrainz API doesn't support OAuth. you need to use the ListenBrainz user token in listenbrainz.org/user/profile
      • 2021-02-03 03428, 2021

      • shivam-kapila
        You will need a LB user token in that case
      • 2021-02-03 03430, 2021

      • iliekcomputers
      • 2021-02-03 03401, 2021

      • kuno
        iliekcomputers: and presumably that token is not available via some API, so I cannot automate obtaining that token using my OAuth credentials.
      • 2021-02-03 03434, 2021

      • iliekcomputers
        not right now, it isn't. would appreciate a ticket about it though.
      • 2021-02-03 03439, 2021

      • iliekcomputers
        what are you trying to do?
      • 2021-02-03 03414, 2021

      • kuno
        I'm trying to make it easy to submit to listenbrainz in my media player by using 'Login with MusicBrainz' button
      • 2021-02-03 03428, 2021

      • kuno
        it's not terribly important, because I'm the only user of it ;)
      • 2021-02-03 03427, 2021

      • iliekcomputers
        ah.
      • 2021-02-03 03402, 2021

      • iliekcomputers
        yep, that's not possible right now. Most clients just ask the user to input their token from the link right now.
      • 2021-02-03 03422, 2021

      • iliekcomputers
        but as you said, it's not the easiest way of authentication ig
      • 2021-02-03 03407, 2021

      • kuno
        I guess my OAuth stuff isn't wasted, I'll still need it later to get user tags/ratings.
      • 2021-02-03 03421, 2021

      • alastairp
        yeah, we've talked a few times about moving user accounts to metabrainz and then allowing that as an oauth provider for all services. I'd really like to see it happen
      • 2021-02-03 03400, 2021

      • alastairp
        see that for example, CB and MeB.org are oauth providers. so you can go officebrainz -> MeB -> musicBrainz -> auth -> auth -> auth
      • 2021-02-03 03416, 2021

      • alastairp
        but it's silly to have these multiple hops in place for everything
      • 2021-02-03 03401, 2021

      • alastairp
        (hi kuno! how are you??)
      • 2021-02-03 03423, 2021

      • kuno
        good :)
      • 2021-02-03 03449, 2021

      • reosarevok
        yvanzo: all done AFAICT :)
      • 2021-02-03 03456, 2021

      • reosarevok
        Tagged too.
      • 2021-02-03 03401, 2021

      • reosarevok
        Wanna update the blog?
      • 2021-02-03 03401, 2021

      • yvanzo
        reosarevok: Cool, thanks.
      • 2021-02-03 03444, 2021

      • kuno
        iliekcomputers: https://tickets.metabrainz.org/browse/LB-811 (and woops, created with the wrong user)
      • 2021-02-03 03445, 2021

      • BrainzBot
        LB-811: Submit listens with OAuth
      • 2021-02-03 03456, 2021

      • iliekcomputers
        thank you!
      • 2021-02-03 03403, 2021

      • alastairp
        in hindsight, I think that I should have added oauth as the main auth mechanism, but it was late and we wanted to get something working so I just hacked it
      • 2021-02-03 03414, 2021

      • alastairp
        related, I saw https://news.ycombinator.com/item?id=25978185 a few days ago which seems line an interesting idea
      • 2021-02-03 03437, 2021

      • yvanzo
        reosarevok: I updated the git tag and added tickets with (hotfixed) mention from https://tickets.metabrainz.org/secure/ReleaseNote…
      • 2021-02-03 03451, 2021

      • yvanzo
        Also credited the bug reporter ^
      • 2021-02-03 03403, 2021

      • yvanzo
        Updating MB Docker is not needed as bugs were in editing interface only (and mirrors are read-only).
      • 2021-02-03 03440, 2021

      • reosarevok
        Neat. Thanks!
      • 2021-02-03 03441, 2021

      • reosarevok
        !m yvanzo
      • 2021-02-03 03441, 2021

      • BrainzBot
        You're doing good work, yvanzo!
      • 2021-02-03 03426, 2021

      • BrainzGit
        [listenbrainz-server] MonkeyDo merged pull request #1255 (master…jenkins-js-reporter): Use checkstyle eslint reporter format for Jenkins https://github.com/metabrainz/listenbrainz-server…
      • 2021-02-03 03425, 2021

      • sumedh joined the channel
      • 2021-02-03 03412, 2021

      • atj
        I'm seeing connections to sockets.listenbrainz.org being blocked due to a lock of a CORS policy header, is that a known issue?
      • 2021-02-03 03417, 2021

      • atj
        *lack
      • 2021-02-03 03434, 2021

      • atj
        Sorry, should of checked the bug tracker first, it's LB-624