Blog: https://addshore.com
Twitter: https://twitter.com/addshore
Meta: https://meta.wikimedia.org/wiki/User:Addshore
Wikitech: https://wikitech.wikimedia.org/wiki/User:Addshore
🦓🐝
Blog: https://addshore.com
Twitter: https://twitter.com/addshore
Meta: https://meta.wikimedia.org/wiki/User:Addshore
Wikitech: https://wikitech.wikimedia.org/wiki/User:Addshore
🦓🐝
The best place would be in the long description of the keycloak command itself.
MR merged, and will be fixed in the next release
Thanks for the write up @Chicocvenancio
Thanks
I'll try and review the patch today :)
Just had a chat with @Mitar on IRC about a possible approach to this and they will write something up here now! :) Wikimedia-Hackathon-2022
Adding @ItamarWMDE who is the staff engineer for the Wikidata side of things :)
Looking at the data, it doesn't look like we are getting any more RC entries than we have done in the past 3 years
OOOh, nice, yeah this should get fixed.
Just trying to figure out the status of this feature from the comments.
Would anyone in the know be able to write a summary?
Flagging this with folks so that it gets prioritized
Just a note for the end of the day, looks like killing the node and letting the service come up on a fresh node worked out :)
Lets hope its all green in the morning
Webservice looks like it may have already been on k8s?
It definitely is now though:)
In T303317#7828185, @ItamarWMDE wrote:I'd still be happy to hear what @Addshore thinks of it, though, just as a sanity check.
@zeljkofilipin do let me know if the binary that I sent you on slack works!
Then we can merge it and release the fix :)
From the other task
Done in https://gitlab.wikimedia.org/repos/releng/cli/-/merge_requests/183 and released in v0.13.1
Will be in v0.13.0
Will be in v0.13.0
Will be in v0.13.0
Will be in v0.13.0
Will be in v0.13.0
Will be in v0.13.0
Will be in v0.13.0
Range: 0 to 99 so the highest value I could set would be 99.
For now I'll set it to 0 which means replication should always be startable.
The down side to this will be slightly increased disk usage. but folks are always able to clear these logs themselves or cleanup the whole dev env..