Issue 1299

[kykrueger]

closes #1299

Fixes issue with bad state of async_response.
Fixes issue that timeouts are not triggered when set to longer than 60s.

[salesforce-cla]

Thanks for the contribution! Before we can merge this, we need @kykrueger to sign the Salesforce Inc. Contributor License Agreement.

[kykrueger]

I've signed the CLA

[bcantoni]

Close and reopen PR to run CLA check again.

[bcantoni]

@kykrueger thanks for putting this PR together! As a first time contributor we had to click a button to run all the checks here and those are done now. You are all set from the CLA perspective. If you look at the build results it looks like you have one black formatting issue and one by pi type issue to fix.

In parallel, @jacalata could you give this a review?

[kykrueger]

Alright, I'll run black over it once. Are you using the defaults or the --preview flag?

[jacalata]

Defaults

[kykrueger]

@jacalata @bcantoni that should do it

[kykrueger]

@jacalata @bcantoni the mypy failures are not functionally related to the PR. Do you have a suggestion?

[kykrueger]

To push this along I've added a check to see if exceptions are returned from the blocking request. This was already returned before this PR, but the type hinting didn't reveal the possibility.

When making my changes, I fixed a pyright error where it had complained that Exceptions could be returned, but were not hinted. This broke the checks for mypy.

Now the returned exceptions will be raised. Before a typeerror would have probably occurred, but now the proper exception will be raised.

[kykrueger]

@bcantoni @jacalata could I get a review and restart of the builds?

[jacalata]

This looks great, thanks! I'd like to add some tests with it, but if I don't get round to that I'll merge it this week anyway.

[kykrueger]

Thanks!

[kykrueger]

@jacalata , I adjusted the settings of my config for Black to match those of your tests.
Now that we both have 120 as the line length, I expect all builds to pass.

[kykrueger]

@bcantoni @jacalata could you give an Update on what is holding up this ticket?
FYI: I just rebased on main

[mzappitello]

is there any update on this PR? our workflows ran into the same error described by @kykrueger and we had to revert back to v0.25.