CatQuest: nothing abnormal on our side afaik, regarding community.mb.o
outsidecontext: there's no urge, if you think you can provide a fix, please do. It's a long-standing issue and users will be happy if it is fixed.
ruaok
zas: then why do you keep pressing me about it?
zas
ruaok: i don't ;) (or it wasn't my intention at all)
ruaok
ok. :)
zas
outsidecontext: i'll make a blog post announcing imminent release, asking translators to update
pulkit6559 has quit
alastairp: about jenkins, i didn't deploy it, i think it was gentlecat, and i don't know much about it. I just discovered dockerized jenkins is running docker... (containers running containers running containers... where are we going...)
alastairp: what do you need exactly?
alastairp
yes, I remember talking with him about it when it was set up
zas: we're using a feature in docker-compose.yml which requires a newer version of docker than that which is installed in the current image
however, because it's connecting to the docker server on williams (via a volume docker.sock), we're actually acting with a more recent version of docker
so the only recommendation that I have is to update the docker client in the jenkins container some time for compatibility reasons (my PR), I expect that everything should continue working fine
Leo_Verto has quit
pulkit6559 joined the channel
Leo_Verto joined the channel
bitmap has quit
bitmap joined the channel
reosarevok
Hey ruaok, come on, zas has the right to a free press
Leo_Verto has quit
Leo_Verto joined the channel
alastairp
Mr_Monkey: hello?
Mr_Monkey
Howdy alastairp
alastairp
remind me again, you showed me how to set dev mode _and_ set the env variable when building webpack?
I have to do both, right?
Mr_Monkey
Right. Here's what we now do on LB, a combination of two things:
> invariant.js:39 Uncaught Invariant Violation: Objects are not valid as a React child (found: object with keys {error, success}).
which I'm not surprised by, but this code was before my time. I'm sure all I need to do is dereference something, right?
michelv has quit
so, I fixed it by printing out {this.state.errorMsg.error} instead, but that seems a bit sketchy, what if by some unknown error, this json no longer has a 'error' key? Can I catch this?
I guess it's just clear that I don't understand jsx :)
Leo_Verto has quit
Leo_Verto joined the channel
Mr_Monkey
Woop, just saw this. Let me see…
alastairp: You can do this: `{ this.state.errorMsg && this.state.errorMsg.error }
if `.error`is undefined, it won't create any node there.
Also we want to make sure `errorMsg`is defined, otherwise calling `errorMsg.error` will throw.
I it grows from there and becomes more complexe, create a getter in your class that will return the right sub-property or null.
For now, I think you could wrap the entire `<p>` tag like this `{this.state.errorMsg && <p ...` and in it use `{this.state.errorMsg.error }` directly
Dr-Flay joined the channel
CatQuest
[19:21] <reosarevok> Hey ruaok, come on, zas has the right to a free press
🤣
Dr-Flay has left the channel
bitmap
alastairp: would 18.06.0-ce work? I could update to that inside the image
oh I guess you already mentioned it is (it's the same version running on the host)
alastairp
bitmap: the jenkins container uses alpine, not ubuntu
but it looks like they have pretty good forward/backward compatibility between the api
(see for example us using client v 1.12 and server v 1.43242 or somethign
pristine_ has quit
Mr_Monkey: thanks :)
I fixed it, I'm going to make a PR and tag you to review it
