Lex Neva
Lex Neva
There's a really good argument for doing it @roman-vynar's way: what if the service (port 222) isn't HTTP? Then you might run a sidecar health-check service that exposes health over...
I tested this out and it works perfectly. Thank you, @roman-vynar!
Yup! And if the information you need isn't there, feel free to add more debug logging.
Oh, I see you aren't a contributor yet. If you'd like, I can add you, which would allow you to push commits to this branch and others. Want in?
Nah, doing a PR against a branch just makes everything complicated. I added you, you're a contributor now. Feel free to push to this branch.
Oh I get it now! I was too caught up in the splitting part, but this is about the satins that _don't_ get split. We're flattening the rails but that...
> Looking at it, it actually does add rungs to uncut satins - if they have more nodes than only the start and end. So the solution to the problem...
Funny, I wrote the above without noticing your latest commit. Looks like you're way ahead of me once again. ;) I like your solution a lot. I'm going to remove...
Love it!
It would be especially neat if we could do some kind of analysis in Troubleshoot to detect a design that's too complex, then send them to that doc.