David Watrous
David Watrous
This isn't just a matter of dataActions, though that is also true. Custom actions like "Microsoft.Batch/batchAccounts/pools/write" aren't properly checked. Submitted a PR to disable this client-side checking until it can...
@rfernand2 Thanks for the detailed report, and glad you were able to find a workaround. That's definitely odd behavior. I don't know of any way this would be related to...
I'm seeing the same issue on 10.15.6 - we need to enable notarization on the .dmg. We'll look into this. This isn't a great answer, but there is a work-around...
A better work-around until we can get the app notarized: Right click (or control-click) on the BatchExplorer application and select open. This will still display a warning, but you should...
Just wanted to follow up to say we're aware of the issue and plan to address it. It's unfortunately not a quick fix, as Batch Explorer communicates directly with the...
Hi @varunsampat30, Unfortunately I haven't had much luck trying to reproduce this issue, and the logs aren't being very helpful here either. I do see a couple of timeout errors...
On the pool overview, can we tweak the message slightly? Something like: "This pool's image is nearing its end-of-life date of $DATE. After this date, new nodes may not function...
/azp run BatchExplorer - CI
/azp run BatchExplorer - CI
/azp run BatchExplorer - CI