The issue is that for me those different accounts appear in different windows, and they don;t show online/offline status or if the message was lost into the ether or actually received.
2025-10-01 27416, 2025
monkey[m]
So I'm just typing and hoping you received it.
2025-10-01 27424, 2025
LupinIII
just write "ping" and if there is no reply in a resonable time, that name is not online
2025-10-01 27436, 2025
LupinIII
:sweatdrop:
2025-10-01 27409, 2025
LupinIII
sorry for the inconvenience
2025-10-01 27414, 2025
MonkeyPython[m] joined the channel
2025-10-01 27414, 2025
MonkeyPython[m]
alternatively use this one
2025-10-01 27436, 2025
LupinIII
thats the onewith an avatar, it should be the matrix one
reosarevok: ping also for if you got imput on wording here
2025-10-01 27428, 2025
LupinIII
monkey should I create a pull for the db-relationship branch so we can compare and such or should I wait until I've done all the works (many small pushes etc...)
2025-10-01 27449, 2025
LupinIII
this fro mthe db-relationship branch
2025-10-01 27425, 2025
monkey[m]
Sorry, don't understand the question.
2025-10-01 27444, 2025
LupinIII
I'm working on editing author (and work) .md pages so the list of relationships can be moved to the db directly, and I was wondering if this work (on the separate branch from the regualr style editing) should we create pull-request for that?
2025-10-01 27418, 2025
LupinIII
so you cna review the work. or should I wait until I've finsihed that db-relationship work and submit the pull then
I see. Yes you can open a PR, there's absolutely no harm in that (can be closed without affected the underlying branch) and it will give us a preview link if we need it
I've been working further on the recording edit form, I got length checks working yesterday and today I started with repeatable validation (for ISRCs in the case of recordings)
my laptop keeps having hardware issues and I might have to replace it, but I'll look at the tests in the evening
2025-10-01 27449, 2025
reosarevok[m]
For what it's worth, yvanzo, I made the changes we talked about last week to the reports PR and they did help, thanks :) (I've kept it in the background after that because the React changes take priority for now)
I was hoping to have a few more small things reviewed this week and put beta out finally on Monday
2025-10-01 27423, 2025
SigHunter joined the channel
2025-10-01 27428, 2025
reosarevok[m]
yvanzo: if you have some time to look into that PR by bitmap before Monday in case you find some issues, that'd be sweet. But if too busy / not available, I think it should be fine as-is
2025-10-01 27448, 2025
yvanzo[m]
<bitmap[m]> "my laptop keeps having hardware..." <- monkey uses and recommended https://frame.work
2025-10-01 27450, 2025
reosarevok[m]
I did do some testing and look through it, at least
2025-10-01 27409, 2025
reosarevok[m]
bitmap: remind me, did the people asking for it test it on test at some point too or?
2025-10-01 27421, 2025
reosarevok[m]
If not we could put it on test until Monday if that makes sense
2025-10-01 27456, 2025
lucifer[m]
* Or [@monkey, * @monkey:chatbrainz.org](https://matrix.to/#/@monkey:chatbrainz.org) or
2025-10-01 27428, 2025
bitmap[m]
sanojjonas did try it out, looking at the PR comments
2025-10-01 27419, 2025
bitmap[m]
reosarevok: let me know if there's anything specific you'd like in the next beta otherwise I'll just check the recent ones
2025-10-01 27422, 2025
reosarevok[m]
Was that after you made it recursive?
2025-10-01 27435, 2025
bitmap[m]
yep
2025-10-01 27403, 2025
reosarevok[m]
Re: reviewing: the recent ones seem fine to check, mostly small and easy I hope.
the failures are weird but maybe it was running the wrong test image or something
2025-10-01 27414, 2025
zas[m]
bitmap: can you check what is going on with patton, it has very bad response times on mb website, not sure why. Perhaps just load-related, but performance is heavily impacted compared to other servers
2025-10-01 27422, 2025
reosarevok[m]
I guess it might be too rushed to put the captcha stuff in beta on Monday but otoh if only tests are missing and you're looking into those today...
2025-10-01 27447, 2025
reosarevok[m]
We could always release it to beta later in the week. It should be safe to release to beta first then prod as usual, right? It won't cause prod issues
2025-10-01 27459, 2025
monkey[m]
<yvanzo[m]> "monkey uses and recommended..." <- Indeed.
2025-10-01 27400, 2025
yvanzo[m]
reosarevok[m]: Not necessarily, we are just missing CI tests, the stuff worked well on test.mb.o.
zas[m]: I just made some local changes to /root/docker-server-configs to increase the number of plackup workers for the website, will commit them properly later if it helps
2025-10-01 27442, 2025
reosarevok[m]
I think bitmap has cover art set up locally, so he probably can
2025-10-01 27401, 2025
reosarevok[m]
Or used to anyway?
2025-10-01 27414, 2025
reosarevok[m]
Other than that, we could put it on test I guss?
2025-10-01 27418, 2025
reosarevok[m]
I guess, too
2025-10-01 27408, 2025
yvanzo[m]
reosarevok[m]: No as we don't have a CAA test instance, it would use the actual archive.
2025-10-01 27448, 2025
reosarevok[m]
Hmm. So any images uploaded from test end up in the main archive? Because I'm sure I've seen people test there :/
2025-10-01 27449, 2025
bitmap[m]
HACKING-IMG.md contains what I previously followed for local CAA/EAA development, though those weren't written for mb-docker either.
2025-10-01 27425, 2025
yvanzo[m]
reosarevok[m]: That would probably be a concern, I didn't check the details though.
2025-10-01 27455, 2025
bitmap[m]
yvanzo[m]: there is an ssssss container running on isaac which test.mb should be uploading images to. (I haven't tested it recently, though)
2025-10-01 27433, 2025
bitmap[m]
I set this up when we were testing the EAA, but it should work for the CAA too
2025-10-01 27435, 2025
yvanzo[m]
That would be great, I thought it wasn't working at some point.
2025-10-01 27400, 2025
reosarevok[m]
yvanzo: I can put updating that PR as the next thing to do once I'm done with recording, anyway (or once I get stuck and I'm waiting for help 😅)
2025-10-01 27412, 2025
reosarevok[m]
And then we can decide how best to test it
2025-10-01 27447, 2025
yvanzo[m]
That would be great, don't hesitate to ping us about the recording edit form.
2025-10-01 27440, 2025
reosarevok[m]
Well, the main thing rn is that I get the feeling https://github.com/metabrainz/musicbrainz-server/… actually broke showing errors for form row text lists entirely (it's broken in prod afaict, I tried to submit an invalid ISRC and it reloaded but with no error shown)
2025-10-01 27440, 2025
reosarevok[m]
It does have FieldErrors for FormRowTextList itself but I guess the actual errors would be set on the specific sub-fields and those don't currently display errors AFAICT
2025-10-01 27420, 2025
reosarevok[m]
So I'm thinking whether to change TextListRow to actually accept the full subfield first and use FieldErrors too, see if that brings the errors back
2025-10-01 27438, 2025
reosarevok[m]
But if either of you think the issue is elsewhere do let me know :)
2025-10-01 27439, 2025
bitmap[m]
reosarevok[m]: that makes sense to me
2025-10-01 27404, 2025
bitmap[m]
and flip includeSubFields to false on the repeatable FieldErrors (but not sure we set any errors on the repeatable itself)
2025-10-01 27427, 2025
reosarevok[m]
Ok, I'll try to do that tomorrow :)
2025-10-01 27433, 2025
reosarevok[m]
Let's see if it helps
2025-10-01 27424, 2025
reosarevok[m]
bitmap, yvanzo: anything else for today? :)
2025-10-01 27449, 2025
bitmap[m]
that's a fin for me
2025-10-01 27450, 2025
LupinIII
reosarevok[m]: ping
2025-10-01 27412, 2025
yvanzo[m]
Let’s wrap it up.
2025-10-01 27424, 2025
bitmap[m] goes back to debugging his laptop for now (and restoring data from an external hdd he accidentally formatted 😭)
2025-10-01 27453, 2025
reosarevok[m]
Thank you both!
2025-10-01 27458, 2025
reosarevok[m]
Good luck, bitmap
2025-10-01 27433, 2025
reosarevok[m]
LupinIII (IRC): pong. If it's about the pastee I'll put it in my list for tomorrow morning :)
