[bookbrainz-site] 14MonkeyDo merged pull request #921 (03master…dependabot/npm_and_yarn/cookiejar-2.1.4): chore(deps): bump cookiejar from 2.1.3 to 2.1.4 https://github.com/metabrainz/bookbrainz-site/pul…
2023-01-25 02501, 2023
zas
discourse is down, upgrade didn't go well, on it
2023-01-25 02551, 2023
BrainzGit
[bookbrainz-site] 14MonkeyDo merged pull request #920 (03master…dependabot/npm_and_yarn/superagent-8.0.8): chore(deps): bump superagent from 7.1.1 to 8.0.8 https://github.com/metabrainz/bookbrainz-site/pul…
2023-01-25 02507, 2023
BrainzGit
[bookbrainz-site] 14MonkeyDo merged pull request #916 (03master…dependabot/npm_and_yarn/classnames-2.3.2): chore(deps): bump classnames from 2.3.1 to 2.3.2 https://github.com/metabrainz/bookbrainz-site/pul…
2023-01-25 02541, 2023
BrainzGit
[bookbrainz-site] 14MonkeyDo merged pull request #917 (03master…dependabot/npm_and_yarn/babel/preset-react-7.18.6): chore(deps-dev): bump @babel/preset-react from 7.16.7 to 7.18.6 https://github.com/metabrainz/bookbrainz-site/pul…
2023-01-25 02527, 2023
BrainzGit
[bookbrainz-site] 14MonkeyDo merged pull request #918 (03master…dependabot/npm_and_yarn/swagger-ui-express-4.6.0): chore(deps): bump swagger-ui-express from 4.3.0 to 4.6.0 https://github.com/metabrainz/bookbrainz-site/pul…
2023-01-25 02544, 2023
zas
still on discourse upgrade, it resumed, there's an upgrade from pg12 to pg13 that went bad
2023-01-25 02544, 2023
reosarevok
bitmap, yvanzo: I think I figured out why my first instinct is to just blank the PR template: the entirety of the content that shows when a PR loads is part of the long introductory welcome to MBS comment
2023-01-25 02559, 2023
reosarevok
So it's like "newbie stuff, go away" :D
2023-01-25 02511, 2023
reosarevok
And it's a lot easier to clear all than to carefully remove only the long comment
reosarevok: that's an interesting point. I see that you can have mutiple templates, maybe there's a case for a "beginners" one (the default), and a "reo" one
2023-01-25 02502, 2023
Lotheric
reidel1!Y
2023-01-25 02507, 2023
zas
Freso: around? the discourse upgrade is everything but smooth, I may need your help
2023-01-25 02537, 2023
zas
the migration was stuck in between, mostly because of following
reosarevok: good question. I guess we started and never got around to fixes?
2023-01-25 02552, 2023
alastairp
the changes look pretty small, probably something I can fix this week
2023-01-25 02544, 2023
serial-ata joined the channel
2023-01-25 02502, 2023
reosarevok
Thanks
2023-01-25 02511, 2023
reosarevok
mayhem: looking at that Wikidata survey. "Please estimate the number of people using your tool / application"
2023-01-25 02525, 2023
reosarevok
zas: ^ maybe you're a good option for this too :)
2023-01-25 02550, 2023
reosarevok
I can list number of editors but I guess we would kinda care more about number of data users, which of course we don't know, but do we have a way to get a general ballpark?
2023-01-25 02541, 2023
reosarevok
I guess maybe it's on zas' summit presentation
2023-01-25 02520, 2023
zas
how do you define 'data users' ?
2023-01-25 02533, 2023
reosarevok
No clue :D
2023-01-25 02540, 2023
reosarevok
But I can say we get 10 billion queries per year
2023-01-25 02546, 2023
reosarevok
(from your presentation)
2023-01-25 02556, 2023
zas
yes
2023-01-25 02559, 2023
reosarevok
But that we have no way to estimate how many of them interact with any Wikidata-related stuff
2023-01-25 02515, 2023
reosarevok
I think that'll be good enough tbh
2023-01-25 02533, 2023
zas
this discourse upgrade is an unexpected mess...
2023-01-25 02540, 2023
zas
making progress though
2023-01-25 02547, 2023
reosarevok
Is this the 3.0 one?
2023-01-25 02551, 2023
zas
yup
2023-01-25 02545, 2023
mayhem
reosarevok: I normally say: 1 going on 20k.
2023-01-25 02512, 2023
reosarevok
I'm not sure what that means :D
2023-01-25 02512, 2023
mayhem
One developer and 20k yearly users.
2023-01-25 02516, 2023
reosarevok
Oh
2023-01-25 02529, 2023
mayhem
Let them sort it out for their own use.
2023-01-25 02534, 2023
reosarevok
Good thing we're not doctors
2023-01-25 02545, 2023
reosarevok
Anyway, sent the survey :)
2023-01-25 02514, 2023
reosarevok
It was actually interesting, unsurprisingly they have a very clear idea of what is a mess in their DB, I'd bet they have a less clear idea of how to fix it
2023-01-25 02518, 2023
reosarevok
#relatable
2023-01-25 02531, 2023
zas
I had to fix duplicated keys manually in the database, and I disabled oauth plugin for now, after fighting to upgrade from pg12 to pg13. I may need help to fix the oauth thing though.
2023-01-25 02547, 2023
reosarevok
So it's mostly "this is a list of things we know are a mess, how much does each of them affect your org?"
2023-01-25 02537, 2023
reosarevok
I haven't touched the discourse stuff at all tbh. Who has? Just you and Freso?
We need to update this plugin, it uses a deprecated feature it seems
2023-01-25 02523, 2023
outsidecontext
zas: I could probably take a look. My Ruby fu is a bit rusty, but at least I have a discourse development setup already running and some experience with its plugin system. How urgent is it? I could take a look later this week
2023-01-25 02550, 2023
zas
btw, the metabrainz/discourse-musicbrainz-auth repo was archived few months ago, but it is clearly used by our discourse instance (proof: it blocks the upgrade), I unarchived it.
2023-01-25 02559, 2023
serial-ata has quit
2023-01-25 02513, 2023
zas
outsidecontext: well, rather urgent urgent, if we can fix it now, I don't have to revert the upgrade, but to be frank, I'm not sure this is possible, I have no idea which changes it needs to work again
2023-01-25 02556, 2023
outsidecontext
zas: I see. Ok, let me power up the discourse thing. I see the new method is to use omniauth. I used this once. Let me check this and I'll get back to you
2023-01-25 02528, 2023
zas
k thanks!
2023-01-25 02544, 2023
vibhoo_24 joined the channel
2023-01-25 02540, 2023
outsidecontext
you know that when you created a local dev user for some system with these "easy to remember credentials", but a few weeks later you don't and none of the obvious choices works?
2023-01-25 02546, 2023
zas
oh yes... ;)
2023-01-25 02504, 2023
vibhoo_24 has quit
2023-01-25 02543, 2023
vibhoo_24 joined the channel
2023-01-25 02536, 2023
vibhoo_24 has quit
2023-01-25 02533, 2023
atj
i'm a rubyist, just had a look and it seems involved
2023-01-25 02528, 2023
zas
yup, if we can't find a solution very quickly, I'll have to roll back the upgrade. So any help is welcome.
2023-01-25 02546, 2023
atj
honestly I don't think this is something we test on prod
2023-01-25 02502, 2023
atj
we need to write a new clas that inherits from Auth::Authenticator
2023-01-25 02506, 2023
atj
*class
2023-01-25 02509, 2023
zas
This change doesn't stand out from changelog, because the actual removal happened in intermediary version (2.9.x) and suggested upgrade was from 2.8.14 to 3.0.0.
I'll start the process, and we'll postponed upgrade to 3.x until this is solved. We also need a way to actually test those upgrades.
2023-01-25 02558, 2023
DeepT joined the channel
2023-01-25 02547, 2023
jasje joined the channel
2023-01-25 02533, 2023
DeepT
am I doing something wrong here? I am using strawberry v1.0.9 on void linux, it shows that I am logged in to listenbrainz, and I have had 0 tracks scrobbled
2023-01-25 02548, 2023
DeepT
I have been logged in for at least a month and have listened to plenty of music
2023-01-25 02505, 2023
mayhem
hmm. what is your username on LB DeepT ?
2023-01-25 02540, 2023
outsidecontext
zas: I think I get this to run today, have the plugin now loading here locally, currently updating it
Scrobbler Libre.fm error: Error transferring https://libre.fm/2.0/ - server replied: (499)
2023-01-25 02505, 2023
DeepT
oh thats for libre. i need to wake up and stop clogging the chat with nonsense
2023-01-25 02506, 2023
DeepT
:P
2023-01-25 02524, 2023
mayhem
seemed to have done the trick. :)
2023-01-25 02515, 2023
DeepT
ya sorry for the bother
2023-01-25 02517, 2023
DeepT has left the channel
2023-01-25 02524, 2023
jasje_ joined the channel
2023-01-25 02531, 2023
jasje has quit
2023-01-25 02532, 2023
jasje_ is now known as jasje
2023-01-25 02559, 2023
zas
grrrr, trying to revert discourse back to v2.8.14 is a pain too ... they upgraded to ruby 3.1 and apparently previous stable versions don't work with it. So I have to downgrade discourse_docker (at our own risk). Setting version to v2.8.14 (as documented) doesn't work, I have to use commit id instead. Everything takes ages. Lesson: we need to test future upgrades, even between stable versions.
2023-01-25 02519, 2023
Pratha-Fish
CatQuest: hello there, before I run off to sleep, would you like to discuss the IRC documentation updates?
zas: I'm a bit thrown back here as well :( there is an open issue for newer omniauth oauth2 that affects the MB oauth setup: https://github.com/omniauth/omniauth-oauth2/issue… . there is a workaround, but needs more changes
2023-01-25 02559, 2023
zas
on my side, reverting is also a pure mess, it looks like we are stuck in the middle of nowhere
2023-01-25 02528, 2023
ssam has quit
2023-01-25 02503, 2023
Pratha-Fish
^ping alastairp for the docs (If you're free that is :D)
Sophist-UK: yes, forums are down due to a failing upgrade, we are on it (since hours)
2023-01-25 02520, 2023
Sophist-UK
Ok - thx.
2023-01-25 02528, 2023
Sophist-UK
These things happen.
2023-01-25 02541, 2023
Sophist-UK
Just wanted to make sure someone knew.
2023-01-25 02552, 2023
mayhem
!m zas
2023-01-25 02552, 2023
BrainzBot
You're doing good work, zas!
2023-01-25 02502, 2023
Sophist-UK
mayhem: Unfortunately if I did that for every time zas did good work, BrainzBot would likely have a nervous breakdown from having to repeat it so often.
2023-01-25 02522, 2023
arcctgx joined the channel
2023-01-25 02541, 2023
arcctgx
Hi, community.metabrainz.org seems to be down right now. Is it a known issue, or is it just a problem on my end?
2023-01-25 02512, 2023
elomatreb[m]
it's a known issue, the admins are working on it
2023-01-25 02544, 2023
ssam joined the channel
2023-01-25 02513, 2023
jasje has quit
2023-01-25 02552, 2023
arcctgx
elomatreb[m]: Thank you. Hopefully it's nothing too serious.
2023-01-25 02512, 2023
jasje_ has quit
2023-01-25 02531, 2023
mayhem
Sophist-UK: true dat!
2023-01-25 02553, 2023
vibhoo_24 joined the channel
2023-01-25 02500, 2023
zas
I'm running out of options with discourse, something broke and starting from a fresh install using backups doesn't look an option before we can fix oauth plugin. I tried to restore previous version, and it fails to start properly even when using pg data backup (and the process is hacky, because previous stable is somehow now unsupported (it was out 3 weeks ago) because docker_discourse moved to ruby 3.1 (and previous stable runs on 2.7).
2023-01-25 02539, 2023
zas
I managed to use previous docker image (it requires changes to launcher script which assumed stable=latest stable discourse repo)
2023-01-25 02502, 2023
zas
but even after full rebuild of all containers, something is missing
2023-01-25 02547, 2023
zas
each rebuild or pg data copy takes a long time, which slows down attempts
2023-01-25 02523, 2023
zas
I'm trying yet another rebuild right now
2023-01-25 02549, 2023
zas
but the real solution lies in upgrading the oauth plugin and complete the move to 3.0
2023-01-25 02519, 2023
mayhem
why not skip the oauth plugin, bring the site back up and let us have moment to think about it?
2023-01-25 02500, 2023
mayhem
not sure people who have accounts with oauth will be able to log in. maybe the accounts can be recovered via email?
