#metabrainz

/

      • CatQuest has quit
      • 2019-07-16 19722, 2019

      • CatQuest joined the channel
      • 2019-07-16 19722, 2019

      • CatQuest has quit
      • 2019-07-16 19746, 2019

      • CatQuest joined the channel
      • 2019-07-16 19705, 2019

      • Nyanko-sensei joined the channel
      • 2019-07-16 19703, 2019

      • D4RK-PH0ENiX has quit
      • 2019-07-16 19708, 2019

      • CatQuest has quit
      • 2019-07-16 19742, 2019

      • Nyanko-sensei has quit
      • 2019-07-16 19720, 2019

      • D4RK-PH0ENiX joined the channel
      • 2019-07-16 19754, 2019

      • bitmap
        reosarevok: MBS-4073 seems fine to me for next schema change
      • 2019-07-16 19755, 2019

      • BrainzBot
        MBS-4073: Highlight pending changes to labels in sidebar https://tickets.metabrainz.org/browse/MBS-4073
      • 2019-07-16 19710, 2019

      • bitmap
        +1 to closing MBS-4107
      • 2019-07-16 19710, 2019

      • BrainzBot
        MBS-4107: I18n - Internationalise the MusicBrainz website https://tickets.metabrainz.org/browse/MBS-4107
      • 2019-07-16 19723, 2019

      • bitmap
        the Number.prototype.toLocaleString stuff should resolve MBS-4118, though I'm certain we don't use it everywhere we should and it needs to be tested in more languages to be sure
      • 2019-07-16 19723, 2019

      • BrainzBot
        MBS-4118: Localise number formats https://tickets.metabrainz.org/browse/MBS-4118
      • 2019-07-16 19741, 2019

      • bitmap
        the vote reports thing seems like a nice idea. why don't you think unreviewed edits should be marked as such more visibly in the listings? (just curious)
      • 2019-07-16 19750, 2019

      • bitmap
        re: speeding up the applied edit count predicate, an index on (editor, status) might help there but would need to test, perhaps on queen
      • 2019-07-16 19754, 2019

      • ferbncode
        spellew: thanks! I'll take a look :)
      • 2019-07-16 19719, 2019

      • yvanzo
        mo’’in’
      • 2019-07-16 19703, 2019

      • Nyanko-sensei joined the channel
      • 2019-07-16 19706, 2019

      • D4RK-PH0ENiX has quit
      • 2019-07-16 19737, 2019

      • Darkloke joined the channel
      • 2019-07-16 19713, 2019

      • ruaok
        reosarevok: on MBS-4219 -- not yet, but maybe early next year?
      • 2019-07-16 19713, 2019

      • BrainzBot
        MBS-4219: Show similar collections on collection pages https://tickets.metabrainz.org/browse/MBS-4219
      • 2019-07-16 19738, 2019

      • Nyanko-sensei has quit
      • 2019-07-16 19714, 2019

      • D4RK-PH0ENiX joined the channel
      • 2019-07-16 19746, 2019

      • reosarevok
        bitmap: I don't necessarily think it should not be marked, but on the other hand, given we still don't even show the vote tally in the listings (just "My vote: None"), that's quite a jump. Maybe showing the tally as 0 Yes 0 No would be enough?
      • 2019-07-16 19700, 2019

      • reosarevok
        I guess if we do that we can also add like a special border or something to "0 Yes 0 No" :)
      • 2019-07-16 19711, 2019

      • nawcom has quit
      • 2019-07-16 19719, 2019

      • nawcom joined the channel
      • 2019-07-16 19752, 2019

      • Gazooo joined the channel
      • 2019-07-16 19757, 2019

      • CatQuest joined the channel
      • 2019-07-16 19757, 2019

      • CatQuest has quit
      • 2019-07-16 19757, 2019

      • CatQuest joined the channel
      • 2019-07-16 19718, 2019

      • zas
        ruaok, bitmap, yvanzo, iliekcomputers: pink is ready (meant to replace queen), I still have few minor things to fix, but the system is ready, docker is installed, monitoring is working (I still have to figure out how to collect data from adaptec hardware raid). It required many small changes since hardware isn't exactly the same (mainly network interfaces and hardware raid).
      • 2019-07-16 19732, 2019

      • zas
        please test if you can log in
      • 2019-07-16 19705, 2019

      • zas
        bitmap: you can start configuring it to replace queen (that should be removed before we can order bowie's replacement)
      • 2019-07-16 19732, 2019

      • zas
        when floyd (new bowie) will be plugged in: I'll set it up, then we switch to pink as main database server, move stuff from bowie to floyd, when done, we toggle floyd becomes master again
      • 2019-07-16 19706, 2019

      • ruaok
        confirmed. I logged in and can sudo.
      • 2019-07-16 19733, 2019

      • zas
        :)
      • 2019-07-16 19710, 2019

      • CatQuest
        but can you log in and do judo? 🤔
      • 2019-07-16 19731, 2019

      • CatQuest
        "(meant to replace queen),"
      • 2019-07-16 19731, 2019

      • CatQuest
        whaaaaaat? nooooo
      • 2019-07-16 19700, 2019

      • CatQuest
        ಠ_ಠ it's going ot b one of those days isn't it -__-
      • 2019-07-16 19759, 2019

      • Freso
        CatQuest: queen and bowie are being replaced due to needed hardware upgrades. Being replaced by pink and floyd respectively.
      • 2019-07-16 19706, 2019

      • zas
        Freso: I upgraded discourse
      • 2019-07-16 19721, 2019

      • leeijaw has quit
      • 2019-07-16 19746, 2019

      • D4RK-PH0ENiX has quit
      • 2019-07-16 19747, 2019

      • ruaok
        alastairp: ping
      • 2019-07-16 19701, 2019

      • iliekcomputers
        I love New servers
      • 2019-07-16 19709, 2019

      • iliekcomputers
        Mostly because of new server names
      • 2019-07-16 19725, 2019

      • iliekcomputers
        pink.metabrainz <3
      • 2019-07-16 19727, 2019

      • alastairp
        ruaok: hi
      • 2019-07-16 19733, 2019

      • alastairp
        how long do you need?
      • 2019-07-16 19755, 2019

      • ruaok
        maybe 10-15 minutes?
      • 2019-07-16 19706, 2019

      • alastairp
        perfect, let's do it
      • 2019-07-16 19709, 2019

      • ruaok
        I think I may have sorted my question now, but a headcheck would still be good.
      • 2019-07-16 19714, 2019

      • ruaok
        ok.
      • 2019-07-16 19750, 2019

      • ruaok
        as you might recall, I run a query on the MB data to fetch tracks that have release type album and insert that into the MSB DB.
      • 2019-07-16 19714, 2019

      • ruaok
        then I parallel walk both that table and the MSB recordings in sorted order to find matches.
      • 2019-07-16 19728, 2019

      • ruaok
        that part is working nicely and artist clusters are being voted on. all good.
      • 2019-07-16 19703, 2019

      • ruaok
        my concern now is to pick matches against recordings so that all MSB recordings with the same text end up on the same MB release.
      • 2019-07-16 19705, 2019

      • yvanzo
        zas: Offending key for IP in .ssh/known_hosts (line matches bootsie)
      • 2019-07-16 19719, 2019

      • ruaok
        yvanzo: delete the old one. they re-used the IP.
      • 2019-07-16 19753, 2019

      • ruaok
        alastairp: because I want to avoid scattering MSB recordings across disparate releases for a given artist.
      • 2019-07-16 19721, 2019

      • ruaok
        so, my current thinking is to find the first released release for each release group and match against that if the MSB recording does not specify a releae.
      • 2019-07-16 19711, 2019

      • alastairp
        from MusicBrainz you get only a list of recordings, no release names?
      • 2019-07-16 19712, 2019

      • ruaok
        the thinking is that people who want to listen to other people's listens would most likely want to listen to the album release recording as the first release.
      • 2019-07-16 19742, 2019

      • ruaok
        I'm working now to get release names, in part to ensure that MSB recordings get clustered on one release and not across a pile of them.
      • 2019-07-16 19754, 2019

      • ruaok
        my previous approach did not involve release names at all.
      • 2019-07-16 19717, 2019

      • ruaok
        and that approach matched recordings in a willy nilly manner that doesn't make for nice data clusters.
      • 2019-07-16 19724, 2019

      • ruaok
        (or a nice user experience)
      • 2019-07-16 19755, 2019

      • alastairp
        > 12:31 PM <ruaok> my concern now is to pick matches against recordings so that all MSB recordings with the same text end up on the same MB release.
      • 2019-07-16 19715, 2019

      • alastairp
        is this messybrainz recordings without a release name provided, or those ones too?
      • 2019-07-16 19725, 2019

      • ruaok
        without.
      • 2019-07-16 19750, 2019

      • ruaok
        next I will need to consider ones that have releases provided.
      • 2019-07-16 19755, 2019

      • alastairp
        right, sure
      • 2019-07-16 19719, 2019

      • ruaok
        but I find that taking small steps is making the whole thing manageable in my head. otherwise it quickly gets out of head and out of hand.
      • 2019-07-16 19728, 2019

      • ruaok
        does that approach make sense?
      • 2019-07-16 19735, 2019

      • alastairp
        do you want to use context to help here? e.g. user a listens to track 1, 2, 3 in order, find where they appear in a release?
      • 2019-07-16 19741, 2019

      • alastairp
        I suspect that's a pretty complex process though
      • 2019-07-16 19754, 2019

      • alastairp
        oh, drat. I guess messybrainz doesn't have temporal info :(
      • 2019-07-16 19725, 2019

      • alastairp
        but yes, getting the first release that a track appears on is a good safe start
      • 2019-07-16 19730, 2019

      • alastairp
        it's what I would do
      • 2019-07-16 19749, 2019

      • yvanzo
        ruaok: thanks
      • 2019-07-16 19701, 2019

      • yvanzo
        zas: confirmed too (login and sudo)
      • 2019-07-16 19716, 2019

      • ruaok
        alastairp: yeah, MSB is a very strange slice of data to work with.
      • 2019-07-16 19734, 2019

      • ruaok
        we did a great piece of handwaving back then in london. :)
      • 2019-07-16 19745, 2019

      • ruaok
        ok, then I will work towards that and see what I get out of it.
      • 2019-07-16 19756, 2019

      • alastairp
        "let's do something and hope that it's useful for us"
      • 2019-07-16 19720, 2019

      • ruaok
        I suspect that this first pass is going to match a lot of data. once I am happy with that, I can look at other data and find candidates for merging into the clusters that have been found already.
      • 2019-07-16 19727, 2019

      • ruaok
        THAT.
      • 2019-07-16 19735, 2019

      • ruaok
        it is useful, but tricky.
      • 2019-07-16 19703, 2019

      • ruaok
      • 2019-07-16 19737, 2019

      • D4RK-PH0ENiX joined the channel
      • 2019-07-16 19712, 2019

      • alastairp
        ruaok: are you just matching track names, or combining artist too?
      • 2019-07-16 19719, 2019

      • ruaok
        both.
      • 2019-07-16 19722, 2019

      • alastairp
        great
      • 2019-07-16 19734, 2019

      • ruaok
        one single value to too shit.
      • 2019-07-16 19746, 2019

      • Freso
        Are you matching tracks that don’t appear on type:albums at all? (Or one step at a time and this will be done later?)
      • 2019-07-16 19742, 2019

      • ruaok
        later.
      • 2019-07-16 19747, 2019

      • Freso nod
      • 2019-07-16 19709, 2019

      • CatQuest
        :C
      • 2019-07-16 19709, 2019

      • travis-ci joined the channel
      • 2019-07-16 19709, 2019

      • travis-ci
        phw/picard#119 (master - ddb628c : Sambhav Kothari): The build passed.
      • 2019-07-16 19709, 2019

      • travis-ci
      • 2019-07-16 19709, 2019

      • travis-ci
      • 2019-07-16 19709, 2019

      • travis-ci has left the channel
      • 2019-07-16 19704, 2019

      • Darkloke has quit
      • 2019-07-16 19758, 2019

      • leeijaw joined the channel
      • 2019-07-16 19709, 2019

      • ruaok
        oh alastairp....
      • 2019-07-16 19733, 2019

      • ruaok
        you do not need access to the database on frank for running aidanlw17's stuff, right?
      • 2019-07-16 19750, 2019

      • alastairp
        no, I was planning on making a duplicate database
      • 2019-07-16 19756, 2019

      • ruaok
        great.
      • 2019-07-16 19759, 2019

      • alastairp
        so that we can play around with it before touching prod
      • 2019-07-16 19700, 2019

      • ruaok
        4TB disk ok?
      • 2019-07-16 19713, 2019

      • ruaok
        32GB of ram or 64gb?
      • 2019-07-16 19715, 2019

      • alastairp
        likely, how large is the database now?
      • 2019-07-16 19729, 2019

      • alastairp
        how much ram does frank have?
      • 2019-07-16 19731, 2019

      • ruaok
        you're asking me??
      • 2019-07-16 19742, 2019

      • alastairp
        iliekcomputers: got an estimate of the size of the ab database?
      • 2019-07-16 19708, 2019

      • ruaok
        frank has 2TB drives.
      • 2019-07-16 19715, 2019

      • alastairp
        so 4 is plenty
      • 2019-07-16 19720, 2019

      • alastairp
        and how much ram does frank have?
      • 2019-07-16 19721, 2019

      • ruaok
        128GB of ram.
      • 2019-07-16 19731, 2019

      • ruaok
        I trust annoy is ram intensive, no?
      • 2019-07-16 19731, 2019

      • alastairp
        I almost spat out my tea
      • 2019-07-16 19733, 2019

      • alastairp
        really?
      • 2019-07-16 19739, 2019

      • alastairp
        nah, annoy uses mmap
      • 2019-07-16 19743, 2019

      • alastairp
        so it's all on disk
      • 2019-07-16 19752, 2019

      • ruaok
        131719944 according to free
      • 2019-07-16 19752, 2019

      • alastairp
        unless linux caches it
      • 2019-07-16 19716, 2019

      • ruaok
        here is where I am going with this.
      • 2019-07-16 19719, 2019

      • alastairp
        if it's not a huge increase in price to go to 64, then that'd be ok
      • 2019-07-16 19722, 2019

      • ruaok
        hetzner has server auctions.
      • 2019-07-16 19735, 2019

      • ruaok
        no minimum duration, no setup fees.
      • 2019-07-16 19703, 2019

      • alastairp
        (what's the catch?)
      • 2019-07-16 19732, 2019

      • ruaok
      • 2019-07-16 19735, 2019

      • ruaok
        that?
      • 2019-07-16 19750, 2019

      • ruaok
        the catch is that you can't do many add ons or order multiples of the machines.
      • 2019-07-16 19756, 2019

      • ruaok
        which we don't care about.
      • 2019-07-16 19712, 2019

      • alastairp
        oh wow, sounds good
      • 2019-07-16 19714, 2019

      • ruaok
        and for 2 months -> 100›€? venga!
      • 2019-07-16 19732, 2019

      • ruaok
        zas: take your time with the server migrations. I'll get alastairp setup with server bidding outside our rack.
      • 2019-07-16 19749, 2019

      • alastairp
        ah right, because we don't need frank db means that it doesn't have to be in the rack?
      • 2019-07-16 19702, 2019

      • ruaok
        yerp.
      • 2019-07-16 19706, 2019

      • alastairp
        great, thanks
      • 2019-07-16 19710, 2019

      • ruaok
        I didn't think of this before.
      • 2019-07-16 19716, 2019

      • ruaok
        can you do the bare machine setup on this beast?
      • 2019-07-16 19723, 2019

      • alastairp
        sure