aerozol: re https://docs.google.com/document/d/1aPeAM0wQyPW... you write about adding more columns but honestly i couldn't get it to work well. the pages are already way too narrow (why does an electronic document have wide margins anyway?) and i can't change it or anything
aerozol: there are quite a lot of "aerozol to create tickets" in https://docs.google.com/document/d/1bz32duq95jS... so I assume this is not for me to do (but if you want I can create those tickets and link them in the doc for you to edit. would they be MBS or DESIGN?)
(I always find it near impossible to figure out the common-chunks errors)
We get a surprisingly high amount of "The “X” relationship between “Foo” and “Bar” already exists." errors
Does that show even if the relationship editor itself detects and blocks the rels?
Or are these dupes getting through to perl somehow?
kellnerd
I've seen this kind of error in the relationship editor.
It probably should not be logged in sentry as it is a recoverable user error.
Oh, wait no, it shows "This relationship already exists.", sorry :)
outsidecontext
yvanzo, reosarevok: weblate 5.1 is out and allows customization of the translation workflow per language. That means we have the ability to e.g. introduce a translate -> review worklfow for languages where there is a large enough translator team (and interest to work this way)
it's not yet on our instance, but will be updated in the next days usually.
bitmap
reosarevok: I think it's legit, I'll check once I'm awke and caffeinated
tux0r has quit
yellowhatpro_ has quit
reosarevok
outsidecontext: sounds good :) For now I think most of our "teams" are currently one-person affairs, but it would be nice to expand that...
outsidecontext
reosarevok: yes, that's also why I argued for this not being needed. actually I think we probably first need to build up something like "teams", that also use e.g. the forums to coordinate.
But if there are 1-3 users that actively translate a language and that then also act as reviewers I think this would work well.
reosarevok: where do you see the high number of relationship-already-exists errors? I only see one with two users and another with one user
but I believe it's possible to trigger this if the relationship gets added in another tab/session, whether by the same user or a different one
I'm not actually sure how to reproduce the first release-editor one, but the "loop" bindingHandler is known to be buggy
the url one is kinda expected due to the way the function is written...there's a race condition where a concurrent transaction can use the url before the DELETE obtains a lock
this is tricky to fix but I'll open a ticket
basically delete_unused_urls needs to use `SELECT ... FOR UPDATE`, and whichever transaction is inserting the conflicting row should use `SELECT ... FOR SHARE` ... I think
reosarevok
bitmap: I see a few every time I check sentry, so I guess it's a few a week?
bitmap
ah probably my search query isn't finding them
reosarevok
Maybe I'm remembering it wrong, also possible :D
mayhem
reosarevok: due to flight delay i can make the meeting. My summary: summit.
reosarevok
Ok
mayhem
All the things I can share, lucifer also knows about, so I'm sure he'll share
reosarevok
"mayhem says: just the right amount of chocolate"
mayhem
I'm hoping to work half days this week, that is it for me.
reosarevok: yvanzo: given that the RemoveEmpty script works on URLs I'm not sure we really need delete_unused_url and associated triggers?
reosarevok
Possibly not? The main benefit I guess is that they are gone immediately rather than after a day, but
That's mostly just relevant to spam I guess
bitmap
that's the only benefit I can see, but doesn't seem worth maintaining much to me
reosarevok
I would not be too bothered if we dropped it, yes
bitmap
I mean, the RemoveEmpty script probably has a race condition too, but it's fine if that crashes; if delete_unused_url crashes it brings the whole transaction with it (probably applying some innocuous edit)
reosarevok
Does the RemoveEmpty script restart if crashed?
bitmap
no but we could at least add some exception handling
yvanzo
the question was: wouldn't [this added relationship attribute] be redundant with the work’s language [attribute]?
reosarevok
And I'm confused how that could be redundant given it's not connected to works in anyway :)
*any way
yvanzo
To follow the example provided in the ticket, one can add a work and set the language to English.
reosarevok
But the relationship is artist-artist, voice actor to character
yvanzo
Maybe more examples are needed to explain how it can be needed.
reosarevok
Well, all the Disney films for example will have different actors voicing the (singing) characters in Spanish and in English :)
yvanzo
Ok, IIUC, it’s the whole relationship “voice of” that would be redundant with artist-recording relationships (I expected but doesn’t seem to exist) on a period of time.
(There is no relationship to say that an artist A interpreted a character C on a recording R.)
MonkeyPython
uhm
reosarevok
Yeah, we cannot have that right now because that would be a 3-point relationship :)
Hope you're ready for more of the good old talking to your screen rather than to physical people
I have two written reviews:
mayhem didn't send anything specific, but basically said "GSoC summit" and "we ate all the chocolate"
Living the life
And aerozol said:
MonkeyPython
lol
reosarevok
'''
I had something big on earlier this month… hmm what was it… nope, can’t remember.
Anyway, since the last meeting I:
Made some tiny PRs - a small step for devs, a giant leap for aerozol-kind - to add new players to the ListenBrainz-enabled apps list, which is looking nice and healthy now (https://listenbrainz.org/add-data/)
Did some work on a nice MeB OBS/streaming overlay that would probably not work and we would end up having to use zoom instead (huh, that’s a weird thing to imagine)
Spent a ton of time on a plane (hmm, why was I on a plane??) sanitizing and trying to make sense of 2017 survey data
Some interesting mockups and discussion on MBS-13292 + MBS-11748 (to be continued)
Spent a whole weekend writing notes and drafting an enormous blog post on something big that happened early this month… strange… nope still not ringing any bells