Skip to content
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

Timeout issues #9

Open
bananamufu opened this issue Aug 5, 2021 · 7 comments
Open

Timeout issues #9

bananamufu opened this issue Aug 5, 2021 · 7 comments
Labels
bug Something isn't working help wanted Extra attention is needed
Milestone

Comments

@bananamufu
Copy link

bananamufu commented Aug 5, 2021

Hi,

I'm getting timeouts errors when I try to generate the metadata using npx dataverse-gen. If I reduce the fetched entities to like below 10, it goes through sometimes, however sometimes it times out even on only one entity fetched. The entity it fails on is different basically every time.

Any help would be appreciated.

Kind regards,
Tom

Fetching CDS metadata for account
Fetching CDS metadata for activityparty
Fetching CDS metadata for activitypointer
Fetching CDS metadata for annotation

Error:Exception in execute:connect ETIMEDOUT ip:443
Stack:Error: connect ETIMEDOUT ip:443
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)
{"errno":"ETIMEDOUT","code":"ETIMEDOUT","syscall":"connect","address":"ip","port":443}```
@sefarov92
Copy link

Hi, any update on this? Thank you

@scottdurow
Copy link
Owner

When you get the timeout - how long does the fetching metadata step wait approximately before you see the error? Is there anything else happening on the server at that time such as importing solutions?

@sefarov92
Copy link

It happens when fetching more than 10 entities, immediately throws error while fetching CDS Metadata - Error:Exception in execute:connect ETIMEDOUT Stack:Error: connect ETIMEDOUT at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) {"errno":-4039,"code":"ETIMEDOUT","syscall":"connect","address":"","port":443} and there was no importing or publishing activity was running on the instance.

@scottdurow
Copy link
Owner

Thanks for the info - so this looks like a different error to the op issue - does it consistently happen every time?

@sefarov92
Copy link

Yeah so far, it keeps happening even with different instance or machine, when we try to get more than 10 entities metadata.

@scottdurow
Copy link
Owner

What OS are you using - and what version of node?
It seems odd that it is so consistent for 10 entities - and it times out immediately rather than waiting for the default OS timeout before terminating.

@sefarov92
Copy link

Sorry took some time to reply. It's not consistently breaking on 10 entities, it just breaks when we supply more than 10 entities, e.g., if we supply 20 entity names in dataverse-gen.json. It will crash while retrieving the 15th entity metadata, and if we re-run this, it will crash again while retrieving the 4th entity metadata, but it will never completely retrieve those 20 entity metadata, no matter how many times we try. Tested with Win10 latest build, Node 14.18.3, and 16.14.2.

@scottdurow scottdurow added the bug Something isn't working label Jun 14, 2022
@scottdurow scottdurow added this to the v2 milestone Jun 14, 2022
@scottdurow scottdurow added the help wanted Extra attention is needed label Nov 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants