*sigh* execute failed: ERROR: relation "cover_art_archive.index_listing" does not exist
_lucifer
alastairp: should i update beta as well?
alastairp
yeah, go for it
_lucifer
done :D
ruaok
yay, for releasing stuff on your first full day.
!m _lucifer
BrainzBot
You're doing good work, _lucifer!
yvanzo
alastairp: Sorry, it seems it cannot be implemented with consul-template 0.16 being used by LB containers, it does not support keyOrDefault either.
alastairp
yvanzo: ok, no problem. I'll finish the consul-template 0.18 PR today and we'll release that too
yvanzo
Only solution that worked for listenbrainz-websockets-test is to hardcode "rabbitmq-prince" in template for now.
alastairp
thanks for folowing up the cause
yvanzo
Hi roger_that, I can try to help you with if you provide more info please: raw log excerpt (please use pastebin or gist) and the output of "admin/configure show".
roger_that has quit
ruaok
alastairp: quick question: where it the config.py file that is used by jenkins for testing?
alastairp
ruaok: in LB? I think it's just copied from the example file
I have one more endpoint to add, but I will do so in another PR, this one is large enough already.
_lucifer
thanks outsidecontext!
atj
shivam-kapila: atj
shivam-kapila
gotcha thanks
atj
Anyone seeing "Failed process was running: CREATE INDEX recording_idx_name ON recording (name);" when attempting to import the sample data into the docker db instance?
shivam-kapila: TBH I think the cleaning up should be done server-side befoere sending through websockets. Where can I see the code you talk about in "even after serialising it as a Listen in frontend"?
I can see that track_metadata doesn't have recording_msid in the WS listen (it's instead one level up)
shivam-kapila
its top level
and there are a lot of things like SUPPORTED_KEYS, date, dedup_tag etc which we dont need
That line does no transformation, it's just a typescript hint about what it should expect the type to be.
So as far as I know we don't transfrom or sanitize the arriving WS message
atj
yvanzo: thanks appreciate you checking, it must be something on my side. I seem to spend more time battling with getting the docker instances working than actually doing any coding, so it's a bit frustrating!
shivam-kapila
Mr_Monkey: oh okay my bad. Is there a better way to discard these unnecessary keys rather than deleting them individually
Mr_Monkey
That should be done server-side to avoid sending a whole bunch of data we don't need
and also to fix the original issue which is the misplaced recording_msid key
shivam-kapila
okay. IIRC ruaok had some concerns about doing this server side when _lucifer was onto it.
_lucifer
that was the original intent. but it adds another serializing/deserializing step so it was decided to do on the client side
shivam-kapila
Imo we can move the recording_msid to the required position and add a comment that ws message contains a lot of unnecessary info. Does this sound okay?
_lucifer
it is intended to use protobuf or some other solution and then do this server side
shivam-kapila
_lucifer: how does the above solution sound to you?
_lucifer
shivam-kapila: sounds good to me. but Mr_Monkey might have a better solution
Mr_Monkey
Can't really think of anything better to do if we don't want to handle it server-side.
We're already deserializing so there's that.
shivam-kapila
okay. I will add a comment till then and also add a test for moving keys in the ws message
atj
Is JSON sent over the WS connection?
_lucifer
yes
shivam-kapila
yep
atj
So you're instantiating an object from JSON sent by via WS?
s/by//
alastairp
atj: did you sort out the docker+mac issue?
atj
alastairp: no not yet
alastairp
I've seen errors importing the full MB database before when the docker machine didn't have enough memory allocated to it
that is, shared buffers * 4 was > memory allocated to docker VM
atj
alastairp: I left it for a while to reduce the risk of me throwing my Macbook out of the window :)
alastairp: thanks, good point, I've bumped the memory up to 5GB
shivam-kapila
> So you're instantiating an object from JSON sent by via WS?
atj: yeah
atj
shivam-kapila: on that line you linked to you have "json as Listen', where is the JS Listen object defined? (sorry might be a stupid question)