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

Investigate IPv6 issues withexpo start --web option #39

Closed
jonas-jonas opened this issue Aug 23, 2022 · 1 comment
Closed

Investigate IPv6 issues withexpo start --web option #39

jonas-jonas opened this issue Aug 23, 2022 · 1 comment
Labels
stale Feedback from one or more authors is required to proceed.

Comments

@jonas-jonas
Copy link
Member

Node 18 changed the lookup order for localhost to prefer IPv6 over IPv4 (see nodejs/node#40537). Expo seems to only bind to IPv4 for now, which results in ECONNREFUSED errors when using wait-on to check for readyness of the React-native web server. This means, that the Kratos E2E tests can not be run on Node >= 18 because the ready-checks will never return true.

Initial investigation did not yield a way to set the IP address that the expo server listens on.
Neither --host :: nor --localhost worked. This might be fixed by upgrading expo CLI though.
That should be investigated in this issue.

Copy link

github-actions bot commented Jan 1, 2025

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas on how you could contribute towards resolving it;
  • leave a comment and describe in detail why this issue is critical for your use case;
  • open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

@github-actions github-actions bot added the stale Feedback from one or more authors is required to proceed. label Jan 1, 2025
@github-actions github-actions bot closed this as completed Feb 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Feedback from one or more authors is required to proceed.
Projects
None yet
Development

No branches or pull requests

1 participant