David Keijser

:+1: for aligning the reporting style. The first seems to be the most common style currently (used by e.g mesos_slave_mem also) but the 2nd feels a bit cleaner imho.

I need to explore this a bit more myself but I wanted to get some ideas from what others might be doing already. Having async specific (or rather future specific)...

I don't think the await syntax should be a problem it was introduced in 3.4 (Or there about) IIRC, and before that there was the 'yield from' stuff that should...

So turns out there was two issues `Future[T]` does not work in python3.6 and `IsolatedAsyncioTestCase` was only added in 3.8 I'll update with some more tests etc later :)

It happens when trying to use webauthn with debug on ``` !!! Touch the flashing U2F device to authenticate... !!! Traceback (most recent call last): File "/home/keis/src/github.com/arthepsy/pan-globalprotect-okta/./gp-okta.py", line 660, in...

With these changes it should be up to date with that api change I think but something is still not working. I'll probably poke at it some more between meetings...

yes, that's the same thing I'm seeing there's some activity and the fido2 calls as far as I can tell are working but then I get that "Invalid Passcode/Answer" from...

w00t that's awesome! Want me to update this PR with that, or perhaps it's easier for you to open a new one instead?

Tested with both python2.7 and 3.9

bump :)