#metabrainz

/

      • ruaok
        yeah, I love love that. big and always easy to get in there.
      • 2019-01-24 02414, 2019

      • iliekcomputers
        i get the feeling you like that place ruaok :P
      • 2019-01-24 02429, 2019

      • ruaok
        yeah.
      • 2019-01-24 02431, 2019

      • Mr_Monkey
        Roger roger.
      • 2019-01-24 02434, 2019

      • iliekcomputers
        off by a second.
      • 2019-01-24 02435, 2019

      • iliekcomputers
        :D
      • 2019-01-24 02429, 2019

      • Mr_Monkey
        I pushed on listen-page-player with some playback imporvements (only JS, so no merge issues, i swear !)
      • 2019-01-24 02435, 2019

      • ruaok
        zas: we're motivating at 14:15
      • 2019-01-24 02445, 2019

      • zas
        k
      • 2019-01-24 02405, 2019

      • ruaok
        I cherry picked the spotify STFU branch and will commit this branch
      • 2019-01-24 02400, 2019

      • iliekcomputers
      • 2019-01-24 02410, 2019

      • iliekcomputers
        why'd you remove the currently-playing permission?
      • 2019-01-24 02423, 2019

      • code_master5 joined the channel
      • 2019-01-24 02402, 2019

      • ruaok
        if I did it, then it was a merge conflict, sorry.
      • 2019-01-24 02419, 2019

      • ruaok
        please add it back in, that would cover the error.
      • 2019-01-24 02425, 2019

      • ruaok
        also, please add a check/test for this.
      • 2019-01-24 02429, 2019

      • iliekcomputers
        oh, no worries. I think that might be the reason for the error.
      • 2019-01-24 02432, 2019

      • iliekcomputers
        yes, sure.
      • 2019-01-24 02447, 2019

      • code_master5
        iliekcomputers: I guess blocked user shouldn't be allowed to comment. Right? 🤔
      • 2019-01-24 02459, 2019

      • code_master5
        on reviews?
      • 2019-01-24 02410, 2019

      • iliekcomputers
        blocked users can't make reviews right?
      • 2019-01-24 02417, 2019

      • code_master5
        iliekcomputers: Yeah!
      • 2019-01-24 02425, 2019

      • iliekcomputers
        then, yea.
      • 2019-01-24 02431, 2019

      • iliekcomputers
        shouldn't be able to comment either.
      • 2019-01-24 02409, 2019

      • code_master5
        I thought so too! But then I thought .. like.. poor blocked users! 🤣
      • 2019-01-24 02422, 2019

      • ruaok
        wooo, I haz listens!
      • 2019-01-24 02429, 2019

      • ruaok
        I still have a couple of other things to resolve in my setup, but they seem pretty simple.
      • 2019-01-24 02457, 2019

      • ruaok
        we will need to rejigger some bits of spotify UI -- the spotify integration now takes on a new and more complex meaning.
      • 2019-01-24 02412, 2019

      • ruaok
        e.g. right now we link and force users to record listens in order to play on the listen page.
      • 2019-01-24 02427, 2019

      • ruaok
        that isn't cool -- the user should be able to choose either or, or both.
      • 2019-01-24 02439, 2019

      • ruaok
        but that is for the afternoon. i can do stuff like that, no problem.
      • 2019-01-24 02403, 2019

      • iliekcomputers
        want me to work on anything in the meanwhile?
      • 2019-01-24 02429, 2019

      • ruaok
        if you have nothing to do, think about what I just said above.
      • 2019-01-24 02457, 2019

      • ruaok
        we need to move the "link spotify" feature out of the realm of "import" and more into "something to use with LB".
      • 2019-01-24 02412, 2019

      • ruaok
        makes sense?
      • 2019-01-24 02417, 2019

      • iliekcomputers
        yeah.
      • 2019-01-24 02408, 2019

      • iliekcomputers
        we should take permissions accordingly as well.
      • 2019-01-24 02402, 2019

      • iliekcomputers
        if the user doesn't want import, we shouldn't ask for permission to see their recently played
      • 2019-01-24 02448, 2019

      • code_master5
        iliekcomputers: One thing is bugging me for quite some time! Suppose a user deletes his/her review. What happens to the comments on that review? Should they also be deleted?
      • 2019-01-24 02423, 2019

      • Mr_Monkey
        ruaok, zas I'm at the market
      • 2019-01-24 02440, 2019

      • ruaok
        iliekcomputers: exactly that.
      • 2019-01-24 02442, 2019

      • ruaok
      • 2019-01-24 02439, 2019

      • iliekcomputers jelly
      • 2019-01-24 02401, 2019

      • iliekcomputers
        build on `listen-page-player` fixed.
      • 2019-01-24 02456, 2019

      • Sophist_UK joined the channel
      • 2019-01-24 02413, 2019

      • Sophist-UK has quit
      • 2019-01-24 02440, 2019

      • MajorLurker has quit
      • 2019-01-24 02407, 2019

      • MajorLurker joined the channel
      • 2019-01-24 02439, 2019

      • ruaok
        ohh, thanks.
      • 2019-01-24 02444, 2019

      • ruaok wants to see what the fix was
      • 2019-01-24 02446, 2019

      • iliekcomputers
      • 2019-01-24 02450, 2019

      • iliekcomputers
      • 2019-01-24 02426, 2019

      • ruaok
        yeah, I would've needed help on that anyway.
      • 2019-01-24 02431, 2019

      • iliekcomputers
        soooo, when we link the user's spotify account, do we give them a list of features they can opt in too?
      • 2019-01-24 02433, 2019

      • ruaok
        why is it active_section now?
      • 2019-01-24 02444, 2019

      • ruaok
        Mr_Monkey: ^^
      • 2019-01-24 02401, 2019

      • iliekcomputers
        ruaok: I think that makes it easier to understand
      • 2019-01-24 02413, 2019

      • ruaok
        ah, I see. I certainly didn't get it at first. :)
      • 2019-01-24 02416, 2019

      • ruaok
        thanks for fixing.
      • 2019-01-24 02445, 2019

      • ruaok
        wrt to `soooo, when we link the user's spotify account, do we give them a list of features they can opt in too?`
      • 2019-01-24 02412, 2019

      • ruaok
        Mr_Monkey said that we need to have all those perms to just play full length tracks from spotify
      • 2019-01-24 02431, 2019

      • ruaok
        so, there are two classes of perms then: listen & record.
      • 2019-01-24 02419, 2019

      • ruaok
        so we should enable people to chose either or both sets.
      • 2019-01-24 02435, 2019

      • iliekcomputers
        sounds good to me.
      • 2019-01-24 02452, 2019

      • ruaok
        that said, we're complicating the spotify setup that we were hoping to release.
      • 2019-01-24 02412, 2019

      • ruaok
        I wonder if it makes sense to hold off on that -- I don't like the idea of pushing a release and then changing things right away.
      • 2019-01-24 02431, 2019

      • ruaok
        AAAAAND... people may need to tweak their perms for the next release and re-connect.
      • 2019-01-24 02437, 2019

      • ruaok
        thoughts, iliekcomputers?
      • 2019-01-24 02454, 2019

      • iliekcomputers
        asking people to reauth two times isn't really ideal imo
      • 2019-01-24 02440, 2019

      • iliekcomputers
        we can hold off on the release. (although we'll probably need a long test cycle for this feature too)
      • 2019-01-24 02427, 2019

      • iliekcomputers
        why do we need birthdate and email?
      • 2019-01-24 02452, 2019

      • Mr_Monkey
        iliekcomputers: Somehow, Spotify needs it to verify if the user is a free or premium account
      • 2019-01-24 02458, 2019

      • Mr_Monkey
        …
      • 2019-01-24 02405, 2019

      • iliekcomputers
        :|
      • 2019-01-24 02407, 2019

      • ruaok
        I don't think it needs to be soo long. The listen recording is the thing that was tricky to get right. I think we're good on that.
      • 2019-01-24 02421, 2019

      • ruaok
        a week might suffice.
      • 2019-01-24 02409, 2019

      • iliekcomputers
        ruaok: yea, the play feature isn't data critical, so it _should_ be okay even if we find bugs there. (but we'll try to not have bugs :D)
      • 2019-01-24 02412, 2019

      • iliekcomputers
        sounds good to me.
      • 2019-01-24 02439, 2019

      • ruaok
        so, for the perms nonsense, we should add a note: "In order to play full length tracks, spotify requires a permission to ask for your birthday. We're not going to look at the data -- see the code here: ,<link to code>. Sorry, but this is not our choice. Proceed or Cancel"
      • 2019-01-24 02453, 2019

      • ruaok
        iliekcomputers: great.
      • 2019-01-24 02416, 2019

      • ruaok
        but lets see if we can put these features to bed today.
      • 2019-01-24 02436, 2019

      • Mr_Monkey
        Let me double check the perms.
      • 2019-01-24 02441, 2019

      • ruaok visualizes Mr_Monkey tucking the feature in and gentle kissing it on the firehead
      • 2019-01-24 02450, 2019

      • iliekcomputers
        :D
      • 2019-01-24 02451, 2019

      • ruaok
        *forehead
      • 2019-01-24 02446, 2019

      • ruaok
      • 2019-01-24 02458, 2019

      • ruaok
        my follow server is refusing connections because it cannot connect.
      • 2019-01-24 02401, 2019

      • ruaok
        e3d95f7352f3 rabbitmq:3.6.5 "docker-entrypoint.s…" 15 hours ago Up 7 minutes 4369/tcp, 5671-5672/tcp, 25672/tcp listenbrainz_rabbitmq_1
      • 2019-01-24 02459, 2019

      • ruaok
      • 2019-01-24 02436, 2019

      • ruaok
        any ideas, iliekcomputers?
      • 2019-01-24 02442, 2019

      • iliekcomputers
        any changes in your docker-compose.yml?
      • 2019-01-24 02421, 2019

      • ruaok
        my repo has no local changes compared to our branch
      • 2019-01-24 02449, 2019

      • iliekcomputers
        okay, weird.
      • 2019-01-24 02422, 2019

      • iliekcomputers
        can you `docker exec -it listenbrainz_web_1 bash` and then try `python manage.py run_follow_server` there?
      • 2019-01-24 02404, 2019

      • outsidecontext has quit
      • 2019-01-24 02451, 2019

      • ruaok
        yes, that works.
      • 2019-01-24 02404, 2019

      • ruaok
        and going into the follow_server can also connect to rabbitmq. very odd.
      • 2019-01-24 02408, 2019

      • iliekcomputers
        dockerize?
      • 2019-01-24 02410, 2019

      • ruaok
        the server doesn't connect, loops, the connects and starts as expected.
      • 2019-01-24 02428, 2019

      • ruaok
        but upon connecting something goes wrong, I think.
      • 2019-01-24 02401, 2019

      • yokel has quit
      • 2019-01-24 02452, 2019

      • iliekcomputers
      • 2019-01-24 02403, 2019

      • iliekcomputers
        Adding a few debugs here might help
      • 2019-01-24 02430, 2019

      • yokel joined the channel
      • 2019-01-24 02457, 2019

      • ruaok
        WEBSOCKETS_SERVER_URL = 'http://localhost:8081'
      • 2019-01-24 02410, 2019

      • ruaok
        isn't actually correct, no? because the web_1 container tries localhost and it doesn't work.
      • 2019-01-24 02421, 2019

      • ruaok
        WEBSOCKETS_SERVER_URL = 'http://follow_server:8081' ?
      • 2019-01-24 02455, 2019

      • iliekcomputers
        Right, but I guess that won't work from the browser
      • 2019-01-24 02408, 2019

      • iliekcomputers
        Two config values?
      • 2019-01-24 02456, 2019

      • ruaok
        why is it working for you and Mr_Monkey? is it?
      • 2019-01-24 02415, 2019

      • ruaok
        > web_1 | 2019-01-24 15:21:55,438 INFO 172.18.0.1 - - [24/Jan/2019 15:21:55] "GET /socket.io/?EIO=3&transport=polling&t=1548343315286-144 HTTP/1.1" 404 -
      • 2019-01-24 02428, 2019

      • ruaok
        these lines in the web_1 container are bugging me.
      • 2019-01-24 02451, 2019

      • ruaok
        are we using polling? they go 404 for web_1, but when I use it on the command line, it works.
      • 2019-01-24 02436, 2019

      • iliekcomputers
        I get those errors too
      • 2019-01-24 02445, 2019

      • iliekcomputers
        There is a bug somewhere in this branch
      • 2019-01-24 02449, 2019

      • iliekcomputers
        Lemme loom
      • 2019-01-24 02451, 2019

      • iliekcomputers
        Look
      • 2019-01-24 02454, 2019

      • ruaok
        lol
      • 2019-01-24 02406, 2019

      • ruaok
        can you review the merge I did after midnight?
      • 2019-01-24 02412, 2019

      • ruaok
        I suspect that is where the bug is.
      • 2019-01-24 02452, 2019

      • iliekcomputers
        Sure, on it.
      • 2019-01-24 02429, 2019

      • ruaok
        we found a problem wrt to connecting to websockets on the client side.
      • 2019-01-24 02450, 2019

      • iliekcomputers
        noice, what was it?
      • 2019-01-24 02452, 2019

      • Mr_Monkey
        We changed what properties are passed to the template, and web_sockets_server_url isn't one of them anymore
      • 2019-01-24 02403, 2019

      • iliekcomputers
        ohhh
      • 2019-01-24 02430, 2019

      • ruaok
        trying fix now
      • 2019-01-24 02412, 2019

      • ruaok
        fix looks good. pushed.
      • 2019-01-24 02411, 2019

      • iliekcomputers
        the data being sent by the js is incorrect.
      • 2019-01-24 02414, 2019

      • iliekcomputers
        let me fix.
      • 2019-01-24 02425, 2019

      • iliekcomputers
        but otherwise works for me too.
      • 2019-01-24 02425, 2019

      • reosarevok
        "Enhance any landscape with our world class signature firepits!"
      • 2019-01-24 02430, 2019

      • reosarevok
        Sometimes we get interesting spam
      • 2019-01-24 02443, 2019

      • iliekcomputers
        pushed latest commit fixing the event listeners on the js client.
      • 2019-01-24 02453, 2019

      • iliekcomputers
      • 2019-01-24 02423, 2019

      • ruaok
        I see listens arriving the client now, great.
      • 2019-01-24 02428, 2019

      • ruaok
        but there are too many arriving
      • 2019-01-24 02438, 2019

      • ruaok
      • 2019-01-24 02439, 2019

      • iliekcomputers
        one playing_now and one listen, i guess?
      • 2019-01-24 02454, 2019

      • iliekcomputers
        let me add more logs
      • 2019-01-24 02420, 2019

      • ruaok
        that would be ideal, yes.
      • 2019-01-24 02445, 2019

      • ruaok
        are those retransmits because of an incorrect ack, maybe?
      • 2019-01-24 02451, 2019

      • iliekcomputers
        pushed again.
      • 2019-01-24 02419, 2019

      • iliekcomputers
        oooh it sent the now-playing notification
      • 2019-01-24 02422, 2019

      • iliekcomputers
        twice
      • 2019-01-24 02459, 2019

      • iliekcomputers
        i guess i forgot to add dedup for playing now...
      • 2019-01-24 02401, 2019

      • iliekcomputers
        on it.
      • 2019-01-24 02445, 2019

      • kepstin
        ah, fixed a typo in my javascript, https://magicisrc-beta.kepstin.ca/ is working now as a proof of concept against test.musicbrainz.org
      • 2019-01-24 02420, 2019

      • kepstin
        hopefully I can get the isrc submission stuff working again over the weekend :)
      • 2019-01-24 02443, 2019

      • ruaok
        iliekcomputers: ping me when you have a sec. we have a UI issue to discuss.
      • 2019-01-24 02459, 2019

      • iliekcomputers
        i'm here.