Jeff McAffer
Jeff McAffer
Worthwhile seeing what's going on here. Is this a limitation of Licensee (i.e., working backwards from the text to know V2.0+) or is it an effort to keep license selection...
There is some level of support for this now depending on your identity provider. Need to look at all the scenarios and see if they are covered.
Great one. The new security advisories work *may* address this though I'm not sure that forks are informed. @jhutchings1 may know
Would also like an API.
would include some level of cleaning issue and PR history as well.
FWIW, I too had the problem. I removed all the non-windows stuff from the `build` script (just leaving the `tsc` call) but still got the following. I believe I followed...
I've since deleted the repo so can't check. Ultimately I just followed the instructions. While I did have to hack to remove the non-Windows script bits, I didn't do anything...
We are seeing something very similar but with different outcomes (we're using 3.4.1). Once the queues get messed up they detach and reattach. Sometimes we see traces like the OP....
Thanks @mbroadst. Really appreciate you help here. We are standing up a production service and hitting this a lot. I noticed a few things that might help figuring this out....