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
{{ message }}
This repository has been archived by the owner on Jul 27, 2022. It is now read-only.
Calling getVaultgetQuota etc, all block the main process, the first time they're called.
If this is intentional, then can this please be documented, alongside an explanation, as blocking the event loop like this without any warning is unnerving.
The text was updated successfully, but these errors were encountered:
I see what you mean -- most of those are require statements (so they're only blocked on file I/O) although some of them call into Java code inside Edge. Did you have a specific problem with one of these, or is it more of a general observation?
I'm fairly new to the apigee platform, however as a Node.js developer, when I see code like that, alarm bells start ringing. It was more of a general observation, especially if Apigee ever allow running of native Node.js under v8, it will cause problems in the future.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
https://github.com/apigee/apigee-access/blob/master/lib/index.js#L208
https://github.com/apigee/apigee-access/blob/master/lib/index.js#L217
https://github.com/apigee/apigee-access/blob/master/lib/index.js#L220
https://github.com/apigee/apigee-access/blob/master/lib/index.js#L233
https://github.com/apigee/apigee-access/blob/master/lib/index.js#L239
https://github.com/apigee/apigee-access/blob/master/lib/index.js#L245
Calling
getVault
getQuota
etc, all block the main process, the first time they're called.If this is intentional, then can this please be documented, alongside an explanation, as blocking the event loop like this without any warning is unnerving.
The text was updated successfully, but these errors were encountered: