[listenbrainz-android] 14dependabot[bot] opened pull request #172 (03main…dependabot/gradle/io.sentry.android.gradle-3.8.0): Bump io.sentry.android.gradle from 3.7.0 to 3.8.0 https://github.com/metabrainz/listenbrainz-androi…
So that stuff doesn’t get lost across timelines/metabrainz messages
2023-06-07 15859, 2023
zas
reosarevok: so, if you have 2 containers C1 & C2 running 'image:tag' with id 1, once you retrieved 'image:tag' with id 2 and used it for C1, C2 would have his image listed as id 1 rather than its name, so basically search by name isn't reliable. And that's perhaps what is happened with your script.
lucifer the webview works amazing but lags a lot for me
2023-06-07 15803, 2023
akshaaatt
It basically took 5-10secs to load every single screen and then around 10secs to redirect
2023-06-07 15851, 2023
Zhele joined the channel
2023-06-07 15817, 2023
Zhele has quit
2023-06-07 15834, 2023
Zhele joined the channel
2023-06-07 15826, 2023
lucifer
akshaaatt: yeah, i had marked it as draft so that you could take over and make any changes you want later. feel free.
2023-06-07 15820, 2023
yvanzo
O’Moin
2023-06-07 15814, 2023
lucifer
akshaaatt: it works quite fast for me even in the emulator.
2023-06-07 15825, 2023
lucifer
i am not sure why it lags in your case.
2023-06-07 15839, 2023
Zhele has quit
2023-06-07 15826, 2023
Zhele joined the channel
2023-06-07 15824, 2023
q3lont joined the channel
2023-06-07 15829, 2023
rozlav joined the channel
2023-06-07 15851, 2023
zas
all containers were stopped on kiki & herb
2023-06-07 15851, 2023
reosarevok
zas: so is the point that while we usually had one container per server for a service, now we have several or?
2023-06-07 15804, 2023
reosarevok
moin yvanzo :) Seems we need to update the update script
2023-06-07 15859, 2023
zas
reosarevok: technically you can have multiple containers for a service, even on the same node. It is just about them to not conflict (different ports and names).
2023-06-07 15838, 2023
reosarevok
Sure, it's just we have never had this issue before the update, so I was wondering what changed :)
2023-06-07 15854, 2023
reosarevok
(that we'd now have a C1 and a C2 to conflict)
2023-06-07 15803, 2023
yvanzo
reosarevok: containers update script?
2023-06-07 15835, 2023
reosarevok
Yeah. It broke when trying to update beta because it was expecting to get back the container name but got the id instead
the script compares a container name with a container id
2023-06-07 15840, 2023
reosarevok
But that used to be both container names
2023-06-07 15857, 2023
reosarevok
zas said that: "if you have 2 containers C1 & C2 running 'image:tag' with id 1, once you retrieved 'image:tag' with id 2 and used it for C1, C2 would have his image listed as id 1 rather than its name, so basically search by name isn't reliable. And that's perhaps what is happened with your script."
2023-06-07 15830, 2023
yvanzo
We don't have 2 containers running the same image tag on paco.
I looked in more details for BB, the container looks fine (tried restarting it too) but requests don't seem to hit it.
2023-06-07 15836, 2023
monkey
Help please :)
2023-06-07 15848, 2023
monkey
aren't working*
2023-06-07 15829, 2023
yvanzo
There are new beta images atm but the containers are still running the old image, no longer matching the image beta tag, so it’s expected that the image for the container is listed with an id instead.
2023-06-07 15849, 2023
yvanzo
Thanks!
2023-06-07 15856, 2023
yvanzo
Something to start with :)
2023-06-07 15852, 2023
reosarevok
Yeah, the image was generated, just not updated
2023-06-07 15826, 2023
reosarevok
But that's the same process we've always followed and this used to work
2023-06-07 15839, 2023
reosarevok
Which makes me assume the change must be in the new setup from yesterday
But I'm keen on aligning with MB, no reason to be off by one
2023-06-07 15855, 2023
reosarevok
Oh, ok, so just starting from 1 and there's no "default" no privs flag
2023-06-07 15801, 2023
reosarevok
I mean, we don't have a 0 flag :)
2023-06-07 15809, 2023
reosarevok
It's just 0 if there's nothing we would call a priv
2023-06-07 15813, 2023
monkey
I guess 1 is the default no special privs
2023-06-07 15819, 2023
reosarevok
(so, they just use the site normally)
2023-06-07 15831, 2023
monkey
That's how I read 'ACCESS_THE_ENTITY'
2023-06-07 15832, 2023
reosarevok
Yeah. I don't think that's wrong either, as long as you document it somewhere
2023-06-07 15834, 2023
yvanzo
reosarevok: I just ran the script again and it worked fine.
2023-06-07 15837, 2023
monkey
= read
2023-06-07 15845, 2023
reosarevok
yvanzo: huh, ok :) Maybe I should have just retried :D
2023-06-07 15810, 2023
reosarevok
"retry until it works" is not the most ideal approach, but hey, if it works for our selenium tests 🤣
2023-06-07 15811, 2023
yvanzo
atj, zas: Might it be that docker-server-configs working copy at paco was not up-to-date when reosarevok tried to update beta?
2023-06-07 15812, 2023
monkey
zas thanks for checking. Mystery. I swear test.LB and test.BB were working yesterday after the consul migration, I checked them
2023-06-07 15802, 2023
reosarevok
monkey: do you have a constants file? I'd put the constants in that file already if so, so that everyone has a clear view of the meanings from the get go :)
2023-06-07 15803, 2023
yvanzo
Since the script that failed is the one that zas patched in the PR. The error message was possibly about the consul container being stopped.
2023-06-07 15843, 2023
zas
monkey: I keep searching, the problem is real, that's just not that
2023-06-07 15853, 2023
monkey
Yep
2023-06-07 15829, 2023
reosarevok
yvanzo: ok, I guess I'll continue with a prod release then for now and see if it all works, unless you have anything against it? :)
2023-06-07 15840, 2023
reosarevok
Well, after a brief check that beta works :)
2023-06-07 15806, 2023
monkey
reosarevok: Good call. We don't have a central constants file yet but there's a good place for it
