#metabrainz

/

      • reosarevok
        aerozol: yeah, the usual response is "only do stuff if it's actually causing issues"
      • aerozol
        👍
      • reosarevok
        Usually I extend that to "if someone is already been reported, check for other spammers on the same IP and ban them too"
      • But more than that is just asking for doom and despair
      • aerozol
        Marking the users as spamer is okay, but searching for each forum user as well… (not to mention my bug where I can’t open the forum in multiple tags)
      • *tabs
      • kuno has quit
      • ansh has quit
      • Pratha-Fish has quit
      • kuno joined the channel
      • reosarevok
        Didn't I send you a userscript to link to the forum user from the editor page?
      • If not I can send it :)
      • saumon has quit
      • Pratha-Fish_ joined the channel
      • ansh_ joined the channel
      • saum0n joined the channel
      • Pratha-Fish_ is now known as Pratha-Fish
      • ansh_ is now known as ansh
      • aerozol
        reosarevok: ooh no that would be handy thanks. Though whenever I open a new forum window I have to alt+f5… (yes, I should fix that)
      • Should we add it to the userscripts wiki page? It seems harmless enough
      • reosarevok
        It's not mine, so I shouldn't :)
      • Honestly, we should implement parts of it at least in MB
      • aerozol
        np
      • reosarevok
        I'll get to it... eventually
      • aerozol
        :D
      • We had an article written about using Picard that’s popped up in a few places: https://www.popsci.com/diy/musicbrainz-picard-g...
      • Not a very accurate one… is it worth my time to email them ask them to make some changes mayhem? (mainly that people need to try cluster + lookup before pressing ‘scan’)
      • mayhem
        it can never hurt to reach out
      • yvanzo
        bitmap: appended (bugfixes and enabled by default) to MBS-12107 in the blog post
      • BrainzBot
        MBS-12107: Replication with dbmirror2 https://tickets.metabrainz.org/browse/MBS-12107
      • aerozol
        mayhem: cool, I spotted some other mistakes in there so I’m going to
      • nice to have an article though!
      • yvanzo
        reosarevok: updated the ticket list in the blog post
      • mayhem
        indeed!
      • yvanzo
        bitmap, reosarevok: I published the blog post in private so that the URL won't change if the day change before we publish it publicly.
      • reosarevok
        Thanks
      • Checking it
      • Seems good
      • Did you manage to test the PR?
      • yvanzo
        bitmap, reosarevok: I will start tagging git repos too.
      • reosarevok
        We can finish it tomorrow if need be, anyway :) Just wondering
      • Ok, thanks :)
      • yvanzo
        reosarevok: not yet
      • but your comments look good
      • reosarevok
        Announce we're back via MB twitter is done, right? (it's still not crossed in the doc)
      • Or are you waiting because you only count it after the blog post? :)
      • yvanzo
        yes
      • for website & API only
      • reosarevok: yes, I didn't cross because dumps and replication are not back yet
      • reosarevok
        Gotcha
      • yvanzo
        actually it should be tweeted about when publishing about the blog post
      • reosarevok
        What's our current expectation for those things?
      • I thought "Wait for replication packet to be produced" was ready :)
      • yvanzo
        It is crosssed
      • reosarevok
        Yeah I meant re: "dumps and replication are not back yet" :)
      • Anyway, clearly dumps are not done
      • aerozol
        reosarevok: I can have a quick pass over the ‘report a user’ wiki, would you rather I edit the wiki direct or do a word doc? I’ll probably just try make it a bit shorter/quicker to read
      • reosarevok
        Wiki direct is fine tbh
      • yvanzo
        yes because replication requires either dump or upgrade steps
      • aerozol
        Cool, I’ll message you when it’s done and you can roll back whatever you want
      • reosarevok
        Oh, ok, in that sense :) Got it!
      • aerozol: cool. Probably in the morning, but :)
      • petitminion has quit
      • saum0n has quit
      • saum0n joined the channel
      • yvanzo
        and the upgrade steps start with: just recreate the database from a fresh dump instead if you prefer
      • reosarevok
        Yeah, makes sense
      • Sophist_UK has quit
      • yvanzo
        bitmap, reosarevok: tagged both git repos, prepared releases in jira too
      • reosarevok
        Thanks!
      • yvanzo
        reosarevok: now that PR :)
      • reosarevok
        yvanzo: thanks! It's ok if you want to sleep and check it in the morning too really
      • Your choice :)
      • bitmap
        yvanzo: thanks++
      • I'm about to eat but working on the json dumps DB upgrade in the background
      • yvanzo
        reosarevok: It's just the last missing piece to have the blog post ready.
      • reosarevok
        Sure :)
      • yvanzo
        bitmap: Updated the upgrade steps for when dumps are ready.
      • Also update the blog post to say that beta will be updated tomorrow (rather then rushed tonight)
      • Going now, good evening!
      • bitmap
        yvanzo: looks good, will publish when dumps are finished. have a good night!
      • zas
        on trille, a docker container named brainzbot-plugins-prod is looping on restart due to an error "/bin/sh: 1: manage.py: not found" since a while. I stopped the container.
      • not sure who deployed it, but there's a repo https://github.com/metabrainz/brainzbot-plugins which is archived
      • aerozol
        reosarevok: for when you’re up, I did some small updates to the Edit Note wiki, and went to town on the How to Report an Editor wiki. Change as you wish
      • resoarevok: I also created MBS-13085
      • BrainzBot
        MBS-13085: Rename 'Reveal my email address' report text https://tickets.metabrainz.org/browse/MBS-13085
      • zas
        I truncated logs & emptied caches on trille to reclaim a bit of disk space