-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hanging when calling initialize #636
Comments
PETOSS-293 |
Thanks for raising an issue, a ticket has been created to track your request |
Hey @JakeCoxon i have tried calling await xero.initialize() and it is printing the response and not hanging on my end. i have on the latest version of xero node @5.0.1. could you please be on the latest xero-node version and let us know if the xero.initialize() call is still failing? |
I have the same hanging issue, but am attempting to run via bun. It looks like there's an issue with the version of openid-client being used in xero-node. Are there any plans on the roadmap to upgrade openid-client in xero-node to the latest (currently 5.6.5)? |
Hey @STEVEOO6 @JakeCoxon We have upgraded the openid-client to its latest version in our new xero-node v7.0.0. Could you please be on the latest xero-node version and let us know incase of any issues? |
SDK you're using (please complete the following information):
Describe the bug
await xero.initialize()
hangs and never recovers. I tracked it down to the call togot
inside openid-client. I can verify this by manually calling the following code using the same version[email protected]
that xero-node usesI can see that the request returns status 200 but reading the response from the stream hangs. Fetching the URL using node-fetch returns the expected response.
got seems to have problems when reading from cache. Presumably this is in combination with something on my machine since I assume many people would be reporting this bug otherwise.
Anyway
[email protected]
doesn't usegot
and I can verify that that works fine for meSo upgrading to
[email protected]
should solve this issueThe text was updated successfully, but these errors were encountered: