Handle unexpected endpoint closures in script

moonbeam-foundation / xcm-sdk

The Moonbeam XCM SDK enables developers to easily transfer assets between chains, either between parachains or between a parachain and the relay chain, within the Polkadot/Kusama ecosystem. With the SDK, you don't need to worry about determining the multilocation of the origin or destination assets or which extrinsics are used on which networks to

MIT License

14 stars 9 forks source link

Description

We had some unexpected endpoint closures that we were not handling in the endpoint monitoring script, which resulted in a stop in the exectution, like in this one: https://github.com/moonbeam-foundation/xcm-sdk/actions/runs/10008210142/job/27664427373#step:8:70

In this PR I consider those closures as failing endpoints

Checklist

[x] If this requires a documentation change, I have created a PR that updates the mkdocs/docs directory
[x] If this requires it, I have updated the Readme
[x] If necessary, I have updated the examples
[x] I have verified if I need to create/update unit tests
[x] I have verified if I need to create/update acceptance tests
[x] If necessary, I have run acceptance tests on this branch in CI

moonbeam-foundation / xcm-sdk

Handle unexpected endpoint closures in script #310

Description

Checklist

🦋 Changeset detected