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

Unavailable chain endpoints Mon, Sep 30 2024, 3:32:47 am #10966

Closed
polkadot-js-bot opened this issue Sep 30, 2024 · 3 comments
Closed

Unavailable chain endpoints Mon, Sep 30 2024, 3:32:47 am #10966

polkadot-js-bot opened this issue Sep 30, 2024 · 3 comments
Labels

Comments

@polkadot-js-bot
Copy link

cc @polkadot-js/notifications

Some configured endpoints are not available.

Check the nightly cron output (or via yarn ci:chainEndpoints locally) and disable the chains (either with isDisabled or isUnreachable) until the issue is resolved. The output as found from the test includes:

 x /home/runner/work/apps/apps/packages/apps-config/src/ci/chainEndpoints.spec.ts:66:22
   Krest @ wss://krest.unitedbloc.com/

	 testCodeFailure / ERR_TEST_FAILURE

	 Connection error

 x /home/runner/work/apps/apps/packages/apps-config/src/ci/chainEndpoints.spec.ts:66:22
   Turing Network @ wss://rpc.turing.oak.tech

	 testCodeFailure / ERR_TEST_FAILURE

	 Connection error

 x /home/runner/work/apps/apps/packages/apps-config/src/ci/chainEndpoints.spec.ts:87:24
   RegionX Cocos @ wss://cocos-node.regionx.tech

	 testCodeFailure / ERR_TEST_FAILURE

	 Connection timeout

 x /home/runner/work/apps/apps/packages/apps-config/src/ci/chainEndpoints.spec.ts:66:22
   Rhala Testnet @ wss://rhala-node.phala.network/ws

	 testCodeFailure / ERR_TEST_FAILURE

	 Connection error

 x /home/runner/work/apps/apps/packages/apps-config/src/ci/chainEndpoints.spec.ts:66:22
   BridgeHub @ wss://sys.ibp.network/bridge-hub-paseo

	 testCodeFailure / ERR_TEST_FAILURE

	 Connection error

 x /home/runner/work/apps/apps/packages/apps-config/src/ci/chainEndpoints.spec.ts:87:24
   Ideal Network @ wss://idn0-testnet.idealabs.network

	 testCodeFailure / ERR_TEST_FAILURE

	 Connection timeout

 x /home/runner/work/apps/apps/packages/apps-config/src/ci/chainEndpoints.spec.ts:87:24
   Polkadex @ wss://polkadex.public.curie.radiumblock.co/ws

	 testCodeFailure / ERR_TEST_FAILURE

	 Connection timeout

 x /home/runner/work/apps/apps/packages/apps-config/src/ci/chainEndpoints.spec.ts:87:24
   Subspace Gemini 3g Nova @ wss://nova.gemini-3g.subspace.network/ws

	 testCodeFailure / ERR_TEST_FAILURE

	 Connection timeout

 x /home/runner/work/apps/apps/node_modules/@polkadot/dev-test/cjs/env/suite.js
   check endpoints

	 subtestsFailed / ERR_TEST_FAILURE
@piggydoughnut
Copy link
Contributor

Completed via #10958

@tugytur
Copy link
Contributor

tugytur commented Oct 1, 2024

@piggydoughnut would it be possible to show the IP of each failed endpoint in the output? Yesterday a bunch of the IBP1 endpoints were removed. The IBP has a geodns setup and it's hard to know for us where the runner is physically running and to which IBP location it's resolving.

I suspect it's a issue with a IBP member and that one geodns configuration, IBP2 results were fine. If everything is fine both geodns domains should be pointing at the same location in theory.

@polkadot-js-bot
Copy link
Author

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.

@polkadot-js polkadot-js locked as resolved and limited conversation to collaborators Oct 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants