search

polkadot-js / apps

Basic Polkadot/Substrate UI for interacting with a Polkadot and Substrate node. This is the main user-facing application, allowing access to all features available on Substrate chains.
https://dotapps.io
Apache License 2.0
1.76k stars 1.55k forks source link

Unavailable chain endpoints Mon, Feb 5 2024, 3:02:47 am #10245

Closed polkadot-js-bot closed 9 months ago

polkadot-js-bot commented 10 months ago

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
   Frequency @ wss://0.rpc.frequency.xyz

     testCodeFailure / ERR_TEST_FAILURE

     Connection error

 x /home/runner/work/apps/apps/packages/apps-config/src/ci/chainEndpoints.spec.ts:66:22
   HydraDX @ wss://rpc.hydradx.cloud

     testCodeFailure / ERR_TEST_FAILURE

     Connection error

 x /home/runner/work/apps/apps/packages/apps-config/src/ci/chainEndpoints.spec.ts:77:17
   Moonbeam @ wss://moonbeam.api.onfinality.io/public-ws

     testCodeFailure / ERR_TEST_FAILURE

     Invalid/non-hex response

 x /home/runner/work/apps/apps/packages/apps-config/src/ci/chainEndpoints.spec.ts:66:22
   Automata @ wss://api.ata.network

     testCodeFailure / ERR_TEST_FAILURE

     Connection error

 x /home/runner/work/apps/apps/packages/apps-config/src/ci/chainEndpoints.spec.ts:77:17
   Bittensor @ wss://entrypoint-finney.opentensor.ai:443

     testCodeFailure / ERR_TEST_FAILURE

     Invalid/non-hex response

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

     subtestsFailed / ERR_TEST_FAILURE
TarikGul commented 9 months ago

Completed via https://github.com/polkadot-js/apps/pull/10290

polkadot-js-bot commented 9 months ago

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.