Oct 19 2022
@bd808 hi Bryan. I understand that you're worried about scope creep here. Sorry about that. My initial thought was, since we're moving to the new cloud platform, it would make sense to take that opportunity and get the modern runtime.
Oct 17 2022
Oct 14 2022
Is there any way to use the MS-supplied image on labs k8s?
Oct 8 2022
This is being addressed here T311466: Create a kubernetes container with mono and dotnet
Oct 7 2022
Hi! My tool is written in dotnet and requires donet 6 which you don't have an image for. So it is not possible to migrate at the moment.
Oct 21 2020
This definitely has nothing to do with PWB. I get this error by just running the bare query like I said above
I experience the same error intermittently with my bot. To test this I wrote code that sends the same query in a loop and sometimes it gets the correct reply from the server while sometimes this happens:
Dec 6 2017
I tested it and it works. Thanks a lot, that was really quick!
Dec 2 2017
Nov 26 2016
@Tgr, I would argue it's a self-deceit. The current grant list page is too complicated. If it was a simple "allow read-only access only" setting - then maybe your argument would be valid.
Instead the current grant list page is hard to use (a user is supposed to hover every checkbox to figure out what it does and decide if they need it) and confusing (it lists even the rights that are not actually available to the user). I'm pretty sure almost no one will use it as intended. Instead, most of the users are going to check every checkbox on that page and forget about it. And nothing can be done about it. So adding the 'grant all existing rights' checkbox is not going to change anything security-wise.
Nov 23 2016
@Tgr, could you please elaborate on what you mean by "unhealthy habits"?
Nov 11 2016
Nov 8 2016
@Anomie thank you very much for the clarification!
@Anomie So, essentially every extension that uses custom rights is broken for bots now. I kinda have a feeling this should've been addressed somehow before deploying action = login deprecation.
Aug 14 2016
Aug 30 2015
I would advocate for the removal of the workaround from T2295, it would make everything cleaner.
Dec 22 2014
Dec 14 2014
In my point of view, it would've been better to use something like L<nowiki>'</nowiki>''homme'' est (or L'<nowiki></nowiki>''homme'' est) than to implement all that half-broken hackery from T2295