#metabrainz

/

      • v6lur has quit
      • 2023-01-09 00925, 2023

      • BrainzGit
        [listenbrainz-server] 14jivteshsingh closed pull request #2331 (03master…add-listen): [LB-1157]: Interface to manually add a listen https://github.com/metabrainz/listenbrainz-server…
      • 2023-01-09 00945, 2023

      • BrainzGit
        [listenbrainz-server] 14jivteshsingh opened pull request #2332 (03master…new-listen): New listen https://github.com/metabrainz/listenbrainz-server…
      • 2023-01-09 00935, 2023

      • BrainzGit
        [listenbrainz-server] 14jivteshsingh opened pull request #2333 (03master…submit-listen): Submit listen https://github.com/metabrainz/listenbrainz-server…
      • 2023-01-09 00942, 2023

      • BrainzGit
        [listenbrainz-server] 14jivteshsingh closed pull request #2332 (03master…new-listen): New listen https://github.com/metabrainz/listenbrainz-server…
      • 2023-01-09 00945, 2023

      • BrainzGit
        [listenbrainz-server] 14jivteshsingh reopened pull request #2331 (03master…add-listen): [LB-1157]: Interface to manually add a listen https://github.com/metabrainz/listenbrainz-server…
      • 2023-01-09 00937, 2023

      • BrainzGit
        [listenbrainz-server] 14jivteshsingh closed pull request #2333 (03master…submit-listen): Submit listen https://github.com/metabrainz/listenbrainz-server…
      • 2023-01-09 00951, 2023

      • serialata has quit
      • 2023-01-09 00943, 2023

      • jivte has quit
      • 2023-01-09 00906, 2023

      • jivte joined the channel
      • 2023-01-09 00911, 2023

      • jasje joined the channel
      • 2023-01-09 00910, 2023

      • vibhoo_24 joined the channel
      • 2023-01-09 00948, 2023

      • vibhoo_24 has quit
      • 2023-01-09 00932, 2023

      • jivte has quit
      • 2023-01-09 00951, 2023

      • jasje has quit
      • 2023-01-09 00904, 2023

      • Shelly joined the channel
      • 2023-01-09 00926, 2023

      • Shelly has quit
      • 2023-01-09 00934, 2023

      • zas
        atj: ping me when around
      • 2023-01-09 00909, 2023

      • yvanzo
        Thank you akshaaatt!
      • 2023-01-09 00937, 2023

      • Hellow1 joined the channel
      • 2023-01-09 00914, 2023

      • Hellow1
        Hey! Has anyone of the nice people in here recources about different metadata containers for audio. I need a reccource that compares the properties of the most popular ones. All I can find are comparisons between either file types or audio coding formats.
      • 2023-01-09 00940, 2023

      • Hellow1
        If anyone could help me out there, that would be lovely!
      • 2023-01-09 00953, 2023

      • Hellow1
        or if you don't have reccources, but experties in audio metadata a reccomendation would do just as well. My criterias are: advanced content, popularity and support for different codec features
      • 2023-01-09 00951, 2023

      • Hellow1 has quit
      • 2023-01-09 00949, 2023

      • Hellow1 joined the channel
      • 2023-01-09 00914, 2023

      • Hellow1 has quit
      • 2023-01-09 00901, 2023

      • Hellow1 joined the channel
      • 2023-01-09 00914, 2023

      • BrainzGit
        [musicbrainz-server] 14reosarevok opened pull request #2801 (03master…MBS-12806): MBS-12806: Do not show "Play on LB" button for empty releases https://github.com/metabrainz/musicbrainz-server/…
      • 2023-01-09 00908, 2023

      • jivte joined the channel
      • 2023-01-09 00943, 2023

      • jivte
        lucifer: Hey I fetched the latest code from listebrainz-server main repo and am getting weird errors like reactdom/client is not defined and snapshot errors
      • 2023-01-09 00959, 2023

      • jivte
        can u please tell how to resolve them
      • 2023-01-09 00901, 2023

      • mayhem
        jivte: have you done a ./develop.sh build?
      • 2023-01-09 00918, 2023

      • jivte
        in the initial setup i did or after fetching the latest code i have to do also
      • 2023-01-09 00953, 2023

      • mayhem
        then how do you start your dev server?\
      • 2023-01-09 00957, 2023

      • jivte
        ./develop.sh up -d
      • 2023-01-09 00926, 2023

      • jivte
        using this command then restarting containers in docker :)
      • 2023-01-09 00948, 2023

      • mayhem
        does the static_builder container start up and start building static assets? if not, try
      • 2023-01-09 00959, 2023

      • mayhem
        ./develop.sh up web static_builder
      • 2023-01-09 00906, 2023

      • mayhem
        and see if that improves things
      • 2023-01-09 00953, 2023

      • lucifer
        jivte: as mayhem mentioned, you'll need to do a `./develop.sh build`. this is needed whenever a dependency is updated or added.
      • 2023-01-09 00925, 2023

      • Hellow1 has quit
      • 2023-01-09 00922, 2023

      • Hellow1 joined the channel
      • 2023-01-09 00945, 2023

      • monkey
        jivte: To run tests and update snapshots, run this command: `./test.sh fe -u`(see https://listenbrainz.readthedocs.io/en/latest/dev…)
      • 2023-01-09 00917, 2023

      • jivte
        monkey: it was showing wierd errors
      • 2023-01-09 00919, 2023

      • mayhem
        lucifer: I <3 coverart on playlists. happy!
      • 2023-01-09 00910, 2023

      • yvanzo
        alastairp: Is it be fine to close/ignore AB from SEC?
      • 2023-01-09 00921, 2023

      • lucifer
        :)
      • 2023-01-09 00931, 2023

      • alastairp
        yvanzo: hi, let me have a look at the list of issues
      • 2023-01-09 00945, 2023

      • alastairp
        javascript sec, almost certainly (pretty much only used for build)
      • 2023-01-09 00900, 2023

      • yvanzo
        Ok, no problem for me, just wanted to unload it for you :)
      • 2023-01-09 00902, 2023

      • alastairp
        we do have some python code still running, is it possible to keep sec for those?
      • 2023-01-09 00914, 2023

      • yvanzo
        Yes, sure.
      • 2023-01-09 00958, 2023

      • alastairp
        I think that's the best solution for now then. I'll go through and manually close AB SEC JS tickets
      • 2023-01-09 00904, 2023

      • alastairp
        is that enough acronyms? bingo!
      • 2023-01-09 00918, 2023

      • yvanzo
        LGTM
      • 2023-01-09 00919, 2023

      • yvanzo
        TY
      • 2023-01-09 00902, 2023

      • alastairp
        😭
      • 2023-01-09 00951, 2023

      • yvanzo
        alastairp: for what is worth, I used to set a warning message before archiving repository since people are sometimes missing the repository status: https://github.com/metabrainz/musicbrainz-vm#read…
      • 2023-01-09 00917, 2023

      • atj
        zas: ping
      • 2023-01-09 00918, 2023

      • alastairp
        understood, I know many people do this with the repos, good idea to add
      • 2023-01-09 00924, 2023

      • yvanzo
        (people including me)
      • 2023-01-09 00932, 2023

      • zas
        atj: hey, happy new year
      • 2023-01-09 00941, 2023

      • yvanzo
        happy new year atj
      • 2023-01-09 00953, 2023

      • alastairp
        mayhem: I got another maker/electronics friend the same cushion case and his response was identical to yours :)
      • 2023-01-09 00916, 2023

      • atj
        zas, yvanzo: happy new year :)
      • 2023-01-09 00942, 2023

      • zas
        atj: we have to configure a virtual network to let J5 servers to access main PG database. Basically, as previously discussed, we need an alternative to internal (physical) network for machines outside it.
      • 2023-01-09 00959, 2023

      • atj
        J5?
      • 2023-01-09 00904, 2023

      • alastairp
        jackson five
      • 2023-01-09 00915, 2023

      • alastairp
        (spark cluster)
      • 2023-01-09 00919, 2023

      • zas
        Jackson Five servers ;) marlon, michael, ...
      • 2023-01-09 00921, 2023

      • atj
        heh, I was thinking Jurassic 5
      • 2023-01-09 00937, 2023

      • atj
        got it
      • 2023-01-09 00916, 2023

      • yvanzo
        zas, atj: Is docker-container-dashboard still a thing?
      • 2023-01-09 00911, 2023

      • zas
        To achieve that, I see 2 approaches, either rely on Hetzner virtual networks (we already use them, dependency over Hetzner), or our own stuff (more complex).
      • 2023-01-09 00957, 2023

      • atj
        yvanzo: yes it's still a thing, just don't have enough time at the moment so not a top priority
      • 2023-01-09 00953, 2023

      • yvanzo
        so it is not deployed, right?
      • 2023-01-09 00903, 2023

      • atj
        yvanzo: no not at present
      • 2023-01-09 00912, 2023

      • yvanzo
        Ok, closing SEC tickets then, thanks :)
      • 2023-01-09 00918, 2023

      • zas
        I tend to prefer first approach, because we tested the tech, it works, not much overhead, and simpler.
      • 2023-01-09 00941, 2023

      • atj
        zas: I don't see a straightforward custom approach so I'd tend to agree
      • 2023-01-09 00922, 2023

      • zas
        But the idea is to include all machines we have in Ansible to it, likely on a 10.X.X.X network
      • 2023-01-09 00923, 2023

      • atj
        we already depend on Hetzner anyway
      • 2023-01-09 00928, 2023

      • atj
        this would replace the existing internal network interfaces I assume?
      • 2023-01-09 00911, 2023

      • zas
        Yes, likely
      • 2023-01-09 00936, 2023

      • zas
        but at first, we'll have both co-existing
      • 2023-01-09 00900, 2023

      • atj
        ok, this should be fun :)
      • 2023-01-09 00909, 2023

      • zas
        Extra routing/firewalling ruls will be needed
      • 2023-01-09 00915, 2023

      • zas
        yup
      • 2023-01-09 00931, 2023

      • zas
        can we set a day this week to work on that?
      • 2023-01-09 00928, 2023

      • mayhem
        alastairp: yes, that thing is terrifying. But I think I need to buy another pillow so it looks like its about to blow. its a bit scary now. not really terrifying.
      • 2023-01-09 00921, 2023

      • alastairp
        mayhem: hah, good point. I didn't know how large the ikea inserts were
      • 2023-01-09 00927, 2023

      • zas
      • 2023-01-09 00951, 2023

      • atj
        zas: sure, tomorrow or friday is looking best at the moment
      • 2023-01-09 00949, 2023

      • zas
        ok, tomorrow works for me
      • 2023-01-09 00901, 2023

      • atj
        so a new vlan and new subnet to add to netplan
      • 2023-01-09 00912, 2023

      • atj
        plus firewall configuration
      • 2023-01-09 00949, 2023

      • zas
        yes, and perhaps some extra routing rules to let internal networks communicate
      • 2023-01-09 00929, 2023

      • zas
        thanks to Ansible the deployment (once configured properly) should be easy
      • 2023-01-09 00956, 2023

      • zas
        btw, J5 servers already use a vSwitch to communicate
      • 2023-01-09 00901, 2023

      • BrainzGit
        [critiquebrainz] 14dependabot[bot] opened pull request #480 (03master…dependabot/npm_and_yarn/json5-2.2.3): build(deps): Bump json5 from 2.2.1 to 2.2.3 https://github.com/metabrainz/critiquebrainz/pull…
      • 2023-01-09 00938, 2023

      • zas
        we'll see whether we use a new one or just extend this one
      • 2023-01-09 00944, 2023

      • yvanzo
        bitmap, monkey: The latest SEC tickets are about the two major versions of json5; The closed duplicate tickets were just not distinguishing between these two versions.
      • 2023-01-09 00908, 2023

      • monkey
        I was just looking into that
      • 2023-01-09 00910, 2023

      • mayhem
        shit. I failed to pay atj his 1 GBP last year.
      • 2023-01-09 00916, 2023

      • mayhem
        lets hope he doesn't sue us.
      • 2023-01-09 00925, 2023

      • Hellow1 has quit
      • 2023-01-09 00935, 2023

      • atj
        I'm not sure you got your moneys worth anyway...
      • 2023-01-09 00936, 2023

      • alastairp
        did he send the invoice?
      • 2023-01-09 00945, 2023

      • jivte
        lucifer: mayhem: Hey even after running the staic-builder command i am getting this error (error TS2307: Cannot find module 'react-dom/client' or its corresponding type declarations.)
      • 2023-01-09 00951, 2023

      • mayhem
        alastairp: a phew, no invoice. saved!
      • 2023-01-09 00955, 2023

      • lucifer
        jivte: try `./develop.sh build` and `./test.sh fe -b`
      • 2023-01-09 00942, 2023

      • jasje joined the channel
      • 2023-01-09 00959, 2023

      • Hellow1 joined the channel
      • 2023-01-09 00908, 2023

      • jivte
        lucifer: thanks that errors are gone
      • 2023-01-09 00922, 2023

      • piwu has quit
      • 2023-01-09 00942, 2023

      • piwu joined the channel
      • 2023-01-09 00927, 2023

      • Hellow1 has quit
      • 2023-01-09 00954, 2023

      • Hellow1 joined the channel
      • 2023-01-09 00902, 2023

      • serialata joined the channel
      • 2023-01-09 00910, 2023

      • vibhoo_24 joined the channel
      • 2023-01-09 00946, 2023

      • Thuraabtech joined the channel
      • 2023-01-09 00911, 2023

      • serialata has quit
      • 2023-01-09 00958, 2023

      • Thuraabtech has quit
      • 2023-01-09 00923, 2023

      • Hellow1 has quit
      • 2023-01-09 00923, 2023

      • jivte
        lucifer: the snapshots got updated but the FreshReleases renders user fresh releases page correctly 1 snapshot also gets updated which we don't want
      • 2023-01-09 00940, 2023

      • jivte
        anything i could do to undo this
      • 2023-01-09 00942, 2023

      • mayhem
        we earned $665.55 from our GitHub sponsors last year. Thanks sponsors!!
      • 2023-01-09 00925, 2023

      • mayhem
        and $34.95 from interest on $400k in the bank. sigh.
      • 2023-01-09 00922, 2023

      • lucifer
        jivte: undo the code changes in that file and regenerate snapshots
      • 2023-01-09 00912, 2023

      • vibhoo_24 has quit
      • 2023-01-09 00927, 2023

      • jivte
        i didn't change anything in fresh releases but don't know why snapshots gets updated
      • 2023-01-09 00908, 2023

      • vibhoo_24 joined the channel
      • 2023-01-09 00919, 2023

      • vibhoo_24
        lucifer: OpenAPI spec is generated and all tests are passing.Have a look when you are free.
      • 2023-01-09 00939, 2023

      • Hellow1 joined the channel
      • 2023-01-09 00901, 2023

      • Hellow1 has quit
      • 2023-01-09 00909, 2023

      • Maxr1998_ joined the channel
      • 2023-01-09 00930, 2023

      • vibhoo_24 has quit
      • 2023-01-09 00957, 2023

      • Hellow1 joined the channel
      • 2023-01-09 00922, 2023

      • Maxr1998 has quit
      • 2023-01-09 00914, 2023

      • Sophist-UK has quit
      • 2023-01-09 00932, 2023

      • BrainzGit
        [metabrainz.org] 14mayhem merged pull request #380 (03master…remove-coc-file): Delete CODE_OF_CONDUCT.md https://github.com/metabrainz/metabrainz.org/pull…
      • 2023-01-09 00945, 2023

      • vibhoo_24 joined the channel
      • 2023-01-09 00907, 2023

      • BrainzGit
        [metabrainz.org] 14mayhem merged pull request #381 (03master…link-coc-to-conflict-policy): Link CoC to conflict policy doc https://github.com/metabrainz/metabrainz.org/pull…
      • 2023-01-09 00943, 2023

      • BrainzGit
        [metabrainz.org] release 03v-2023-01-09.0 has been published by 14github-actions[bot]: https://github.com/metabrainz/metabrainz.org/rele…
      • 2023-01-09 00924, 2023

      • Hellow1 has quit
      • 2023-01-09 00958, 2023

      • BrainzGit
        [musicbrainz-android] 14dependabot[bot] opened pull request #177 (03master…dependabot/gradle/androidx.test-runner-1.5.2): Bump runner from 1.5.1 to 1.5.2 https://github.com/metabrainz/musicbrainz-android…
      • 2023-01-09 00906, 2023

      • BrainzGit
        [musicbrainz-android] 14dependabot[bot] opened pull request #178 (03master…dependabot/gradle/androidx.test.ext-junit-1.1.5): Bump junit from 1.1.4 to 1.1.5 https://github.com/metabrainz/musicbrainz-android…
      • 2023-01-09 00910, 2023

      • BrainzGit
        [musicbrainz-android] 14dependabot[bot] opened pull request #179 (03master…dependabot/gradle/androidx.test.espresso-espresso-intents-3.5.1): Bump espresso-intents from 3.5.0 to 3.5.1 https://github.com/metabrainz/musicbrainz-android…
      • 2023-01-09 00921, 2023

      • BrainzGit
        [musicbrainz-android] 14dependabot[bot] opened pull request #180 (03master…dependabot/gradle/com.google.code.gson-gson-2.10.1): Bump gson from 2.10 to 2.10.1 https://github.com/metabrainz/musicbrainz-android…
      • 2023-01-09 00927, 2023

      • BrainzGit
        [musicbrainz-android] 14dependabot[bot] opened pull request #181 (03master…dependabot/gradle/androidx.test.espresso-espresso-core-3.5.1): Bump espresso-core from 3.5.0 to 3.5.1 https://github.com/metabrainz/musicbrainz-android…