You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in HostContext where a client is created to retrieve hub information. The client is then closed in a fire-and-forget way, with any errors ignored
client.close.catch(/* do nothing */)
We would like to understand
Is there any reason for the current behavior (fire-and-forget) while ignoring errors?
If we are going to change to wait with await client.close(), do we need to catch errors in order to keep the behavior of swallowing all errors from client.close()?
Is it possible to for the client have proper clean-up in the close() method in the exceptional cases?
* Improve TestResources docs and logging
Resolves#1388Resolves#1407
Also ignores cached service principal if it no longer exists. I ran into this while testing since I cleaned up old SPs.
* Add ADP test sub to look-up
Co-authored-by: Heath Stewart <[email protected]>
continuing the discussion at #1390 (comment)
There are three places
azure-sdk-for-js/packages/@azure/eventhubs/processor/lib/hostContext.ts
Line 246 in 29fad66
azure-sdk-for-js/packages/@azure/eventhubs/processor/lib/hostContext.ts
Line 252 in 29fad66
azure-sdk-for-js/packages/@azure/eventhubs/processor/lib/hostContext.ts
Line 259 in 29fad66
in HostContext where a client is created to retrieve hub information. The client is then closed in a fire-and-forget way, with any errors ignored
We would like to understand
await client.close()
, do we need to catch errors in order to keep the behavior of swallowing all errors fromclient.close()
?close()
method in the exceptional cases?azure-sdk-for-js/packages/@azure/eventhubs/client/lib/eventHubClient.ts
Lines 134 to 158 in 94e6116
The text was updated successfully, but these errors were encountered: