I haven't read the discussion but this seems like the obvious answer considering the flag only needs to be set during test.
Presumably this might miss some edge case (where something else also needs the flag?) though an explicit allow of the mockito agent in the jvm arg would have solved for that.
I think a better question is if there is an operating framework that would remove Microsoft's ability to sanction individuals on the whim of the current US administration in lieu of the appropriate EU institutions.
Microsoft's partnership/JV with 21Vianet in China shows that it can be done (with limitations on features) and this is probably the right direction to go.
It's actually more than a few minutes. I can't speak for other places, but generally there will be an agent that is monitoring many inbound chats, and in a lot of cases the resolution can likewise be automated.
In the past this was managed by a fairly deep call queue, and has saved fairly significant amount of $ vs receiving and resolving everything manually.
Indeed we have internal clients (vs paying customers) but overall this has been quite successful for us.
Docs are a bit sparse, hard to tell what support is like for these but seems a bit limited/new:
- job dependencies, success/failure conditions, retry logic, etc etc
- process/user impersonation/delegation
- custom calendars and execution times "ie last business friday of the month"
And those workers don't want to do those jobs, for that $, anyway. A friend of mine with a farm in Quebec, Canada says even if you can find folks to do the work and pay them well, they often aren't reliable. Better all round to use temporary workers
Presumably this might miss some edge case (where something else also needs the flag?) though an explicit allow of the mockito agent in the jvm arg would have solved for that.