#metabrainz

/

      • suvid[m]
        Oh yea I'll check for that as well
      • Thanks for reminding
      • Though it should be responsive by default but I'll still check for it
      • Hi lucifer monkey
      • I have updated the PR with the screenshots on desktop and mobile view as well
      • I had one more query
      • I created the branch `importer-UI` from the branch `main-importer` but I had created the PR #3317 that merges to main instead of `main-importer`
      • Now when I go to edit option in the PR, I don't see the option to set `main-importer` as the branch it merges to from the list of branches
      • suvid[m] uploaded an image: (87KiB) < https://matrix.chatbrainz.org/_matrix/media/v3/download/matrix.org/WCMdvOpHQRwzqscYTDMRjYUN/image.png >
      • lucifer[m]
        suvid: yes you can't do that because `main-importer` is a branch on your github fork not the metabrainz repo.
      • suvid[m]
        lucifer[m]: oh
      • sol first `main-importer` will have to be merged to main and then only `importer-UI` would be merged right?
      • lucifer[m]
        yes.
      • holycow23[m] has quit
      • holycow23[m] joined the channel
      • holycow23[m]
        Hey lucifer is the entire DB present on wolf?
      • lucifer[m]
        MB or LB?
      • holycow23[m]
        MB
      • lucifer[m]
        yup it us
      • * yup it is
      • holycow23[m] sent a code block: https://matrix.chatbrainz.org/_matrix/media/v3/download/chatbrainz.org/CPEJqgOKURPdafYrYraIWXUH
      • holycow23[m]
        * ````>>>... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)
      • * ```>>> spark.sql("select count(*) from listens l, recording_artist ra where l.recording_mbid = ra.recording_mbid").show()... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)
      • * ```... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)
      • Shouldn't the 2 be equal?
      • lucifer[m]
        no, because in this query filter for listens which have a matching recording mbid in recording artist table. that filters out listens which don't have a recording mbid.
      • holycow23[m]
        yeah but shouldn't all the listens have a mbid?
      • i mean if not all atleast like the most of it
      • right now roughly 10% of the listens have a matching mbid
      • lucifer[m]
        no, all listens have a msid but not all listens have a mbid.
      • ah that is probably because your spark wolf setup only has the sample dumps.
      • again, MB db on wolf is not the same as your spark setup on wolf.
      • MB db has the full dataset, your spark setup only sample.
      • holycow23[m]
        so the discrepancy is fine right
      • lucifer[m]
        yes
      • holycow23[m]
        is there a possibility to get the entire db or like some more content cause the results are too small to test and verify
      • mamanullah7[m] joined the channel
      • mamanullah7[m]
        hey monkey lucifer any update?
      • lucifer[m]
        Not yet.
      • mamanullah7[m]
        lucifer: np
      • i was using wrong endpoint for refreshing access token
      • `Refresh your access token by sending a refresh request to /api/v1/oauth/token` i'll try to debug i'll let u know if its resolved!
      • petitminion joined the channel
      • rayyan_seliya123
        <rayyan_seliya123> "hey lucifer just wanted to..." <- Hey lucifer: if u by mistake missed my chat 🙂
      • lucifer[m]
        [@rayyan_seliya123:matrix.org](https://matrix.to/#/@rayyan_seliya123:matrix.org) take a look at how Spotify search is implemented in BrainzPlayer and then try to implement search using this endpoint the same way.
      • the Spotify player in BrainzPlayer is using Spotify api search directly but the process should overall be similar.
      • <holycow23[m]> "is there a possibility to get..." <- I can try importing the entire metadata in your wolf cluster, sure.
      • rayyan_seliya123
        lucifer[m]: lucifer: sure I will look onto Spotify how it is implemented and will update you after that I was thinking to move all my commits or backend file changes to this new pr and close the previous one is it good to you ??
      • lucifer[m]
        [@rayyan_seliya123:matrix.org](https://matrix.to/#/@rayyan_seliya123:matrix.org) you can have the api and the frontend change in 1 PR. And leave the indexer changes in the old PR.
      • rayyan_seliya123
        lucifer[m]: Okk sure !! But there is one change in my `handler.py` file which I wanted to do but coz of the issues I faced I am unable to do so ! For that change I would have to push the entire handler.py. File in this pr 🥲 or we can edit it later would be fine ?
      • holycow23[m]
        <lucifer[m]> "I can try importing the entire..." <- I will test it out for a little more if needed will let you know
      • Hey ansh and monkey , could you help me with the stats section related to 'Top Listeners' from my [proposal](https://community.metabrainz.org/t/gsoc-2025-development-of-advanced-user-statistics-visualizations/750040)? Should I go ahead with the implementation method I described there, or would you suggest a different approach?
      • lucifer[m]
        [@rayyan_seliya123:matrix.org](https://matrix.to/#/@rayyan_seliya123:matrix.org) check out your old branch and update the handler file in that PR. Then rebase your current branch on the old branch and it should work fine.
      • rayyan_seliya123
        lucifer[m]: Sure I will try this !
      • petitminion has quit