Pedro González Serrano

It's relevant in my case

Hi @smortex My original plan was to rebase #1163 after #1146 merge... and then doing the same with #1164 , that would fit git / github keeping changes atomic... but...

@smortex I haven't managed to gess how to "foce-push x into y", what I've done is - Rebase new-templates (#1146) into current master (`git rebase -i upstream/master`) - Rebase ilm_policies...

Many thanks @bastelfreak , both for the comment and for your support on IRC... I hope everything will came together now

@smortex , @bastelfreak Everything should be fine right now (all branches rebased updating reference on each commit) Please let me know if there is something missing/needed

I guess I'm hitting a similar issue caused by backend servers being injected in different order among haproxy's instances. It was driving me nuts. Our case is consisteng hasing on...

Maybe because we're wrapping it in docker (https://github.com/sbitio/docker-wkhtmltox), but still doesn't work (image sizes are are plain explicative if you try my example)

It doesn't work either using that container (and container is somehow broken): ~~~ niteman@teg:~/tmp$ ls -lah total 8,0K drwxr-xr-x 2 niteman niteman 4,0K mar 13 15:07 . drwxr-xr-x 49 niteman...

Hi, just asking, is there any chances this reaching official repo soon? May I help somehow?

My theory (not a js guy sorry) is that https://github.com/johannesjo/super-productivity/commit/c35523d8e6e9e8d548ad5b189a3bf49101d6314a caused a regression breaking the fix of https://github.com/johannesjo/super-productivity/pull/3247 I'll suggest reverting for now... unfortunately, snap doesn't allow me to go...