fix: correct external repository links in pezkuwi-subxt
Update incorrectly rebrand links to point to their actual locations: - json-rpc-interface-spec: pezkuwichain → paritytech (external spec repo) - subxt PR/issue refs: pezkuwichain → paritytech (upstream repo history) - pezcumulus: pezkuwichain/pezcumulus → pezkuwichain/pezkuwi-sdk/pezcumulus (monorepo) - pezcumulus commit-specific: → paritytech/cumulus (historical commits)
This commit is contained in:
@@ -4,4 +4,4 @@ title: Subxt integration tests failed against latest Bizinikiwi build.
|
||||
|
||||
The nightly CI run which downloads the latest version of Bizinikiwi ran into test failures, which likely means that there are breaking changes that need fixing in Subxt.
|
||||
|
||||
Go to https://github.com/pezkuwichain/subxt/actions/workflows/nightly.yml to see details about the failure.
|
||||
Go to https://github.com/paritytech/subxt/actions/workflows/nightly.yml to see details about the failure.
|
||||
Vendored
+629
-629
File diff suppressed because it is too large
Load Diff
Vendored
+1
-1
@@ -1,4 +1,4 @@
|
||||
# subxt · [](https://github.com/pezkuwichain/subxt/actions/workflows/rust.yml) [](https://crates.io/crates/subxt) [](https://docs.rs/subxt)
|
||||
# subxt · [](https://github.com/paritytech/subxt/actions/workflows/rust.yml) [](https://crates.io/crates/subxt) [](https://docs.rs/subxt)
|
||||
|
||||
Subxt is a library for interacting with [Bizinikiwi](https://github.com/pezkuwichain/pezkuwi-sdk) based nodes in Rust and WebAssembly. It can:
|
||||
|
||||
|
||||
Vendored
+1
-1
@@ -103,6 +103,6 @@ We also assume that ongoing work done is being merged directly to the `master` b
|
||||
git push --tags
|
||||
```
|
||||
|
||||
Once this is pushed, go along to [the releases page on GitHub](https://github.com/pezkuwichain/subxt/releases)
|
||||
Once this is pushed, go along to [the releases page on GitHub](https://github.com/paritytech/subxt/releases)
|
||||
and draft a new release which points to the tag you just pushed to `master` above. Copy the changelog comments
|
||||
for the current release into the release description.
|
||||
|
||||
+2
-2
@@ -3,7 +3,7 @@
|
||||
// see LICENSE for license details.
|
||||
|
||||
//! An interface to call the API methods. See
|
||||
//! <https://github.com/pezkuwichain/json-rpc-interface-spec/> for details of the API
|
||||
//! <https://github.com/paritytech/json-rpc-interface-spec/> for details of the API
|
||||
//! methods exposed here.
|
||||
|
||||
use crate::{
|
||||
@@ -1117,7 +1117,7 @@ fn to_hex(bytes: impl AsRef<[u8]>) -> String {
|
||||
}
|
||||
|
||||
/// Attempt to deserialize either a string or integer into an integer.
|
||||
/// See <https://github.com/pezkuwichain/json-rpc-interface-spec/issues/83>
|
||||
/// See <https://github.com/paritytech/json-rpc-interface-spec/issues/83>
|
||||
pub(crate) mod unsigned_number_as_string {
|
||||
use serde::de::{Deserializer, Visitor};
|
||||
use std::fmt;
|
||||
|
||||
@@ -3,7 +3,7 @@
|
||||
// see LICENSE for license details.
|
||||
|
||||
//! This module will expose a backend implementation based on the new APIs
|
||||
//! described at <https://github.com/pezkuwichain/json-rpc-interface-spec/>. See
|
||||
//! described at <https://github.com/paritytech/json-rpc-interface-spec/>. See
|
||||
//! [`rpc_methods`] for the raw API calls.
|
||||
//!
|
||||
//! # Warning
|
||||
@@ -540,7 +540,7 @@ impl<T: Config + Send + Sync + 'static> Backend<T> for ChainHeadBackend<T> {
|
||||
&self,
|
||||
_hasher: T::Hasher,
|
||||
) -> Result<StreamOfResults<(T::Header, BlockRef<HashFor<T>>)>, BackendError> {
|
||||
// TODO: https://github.com/pezkuwichain/subxt/issues/1568
|
||||
// TODO: https://github.com/paritytech/subxt/issues/1568
|
||||
//
|
||||
// It's possible that blocks may be silently missed if
|
||||
// a reconnection occurs because it's restarted by the unstable backend.
|
||||
@@ -558,7 +558,7 @@ impl<T: Config + Send + Sync + 'static> Backend<T> for ChainHeadBackend<T> {
|
||||
&self,
|
||||
_hasher: T::Hasher,
|
||||
) -> Result<StreamOfResults<(T::Header, BlockRef<HashFor<T>>)>, BackendError> {
|
||||
// TODO: https://github.com/pezkuwichain/subxt/issues/1568
|
||||
// TODO: https://github.com/paritytech/subxt/issues/1568
|
||||
//
|
||||
// It's possible that blocks may be silently missed if
|
||||
// a reconnection occurs because it's restarted by the unstable backend.
|
||||
|
||||
+1
-1
@@ -965,7 +965,7 @@ mod test {
|
||||
}
|
||||
|
||||
// Check that the backend will resubscribe on Stop, and handle a change in subscription ID.
|
||||
// see https://github.com/pezkuwichain/subxt/issues/1567
|
||||
// see https://github.com/paritytech/subxt/issues/1567
|
||||
#[tokio::test]
|
||||
async fn stale_subscription_id_failure() {
|
||||
let (tx, rx) = tokio::sync::mpsc::unbounded_channel();
|
||||
|
||||
+1
-1
@@ -117,7 +117,7 @@ where
|
||||
continue;
|
||||
}
|
||||
|
||||
// TODO: https://github.com/pezkuwichain/subxt/issues/1567
|
||||
// TODO: https://github.com/paritytech/subxt/issues/1567
|
||||
// This is a hack because, in the event of a disconnection,
|
||||
// we may not get the correct subscription ID back on reconnecting.
|
||||
//
|
||||
|
||||
+2
-2
@@ -100,9 +100,9 @@
|
||||
//!
|
||||
//! Some complete, self contained examples which are not a part of this guide:
|
||||
//!
|
||||
//! - [`parachain-example`](https://github.com/pezkuwichain/subxt/tree/master/examples/parachain-example) is an example
|
||||
//! - [`parachain-example`](https://github.com/paritytech/subxt/tree/master/examples/parachain-example) is an example
|
||||
//! which uses Zombienet to spawn a parachain locally, and then connects to it using Subxt.
|
||||
//! - [`wasm-example`](https://github.com/pezkuwichain/subxt/tree/master/examples/wasm-example) is an example of writing
|
||||
//! - [`wasm-example`](https://github.com/paritytech/subxt/tree/master/examples/wasm-example) is an example of writing
|
||||
//! a Rust app that contains a Yew based UI, uses Subxt to interact with a chain, and compiles to WASM in order to
|
||||
//! run entirely in the browser.
|
||||
pub mod setup;
|
||||
|
||||
+4
-4
@@ -20,14 +20,14 @@
|
||||
//! is currently (as of 2023-06-26) deployed on Pezkuwi and [Dicle (as "Statemine")](https://parachains.info/details/statemine).
|
||||
//!
|
||||
//! To construct a valid [`crate::config::Config`] implementation, we need to find out which types
|
||||
//! to use for `AccountId`, `Hasher`, etc. For this, we need to take a look at the source code of Statemint, which is currently a part of the [Pezpezcumulus Github repository](https://github.com/pezkuwichain/pezcumulus).
|
||||
//! The crate defining the asset hub runtime can be found [here](https://github.com/pezkuwichain/pezcumulus/tree/master/parachains/runtimes/assets/asset-hub-pezkuwi).
|
||||
//! to use for `AccountId`, `Hasher`, etc. For this, we need to take a look at the source code of Statemint, which is currently a part of the [Pezcumulus directory in pezkuwi-sdk](https://github.com/pezkuwichain/pezkuwi-sdk/tree/main/pezcumulus).
|
||||
//! The crate defining the asset hub runtime can be found [here](https://github.com/pezkuwichain/pezkuwi-sdk/tree/main/pezcumulus/teyrchains/runtimes/assets/asset-hub-pezkuwichain).
|
||||
//!
|
||||
//! ## `AccountId`, `Hash`, `Hasher` and `Header`
|
||||
//!
|
||||
//! For these config types, we need to find out where the parachain runtime implements the
|
||||
//! `frame_system::Config` trait. Look for a code fragment like `impl frame_system::Config for
|
||||
//! Runtime { ... }` In the source code. For Statemint it looks like [this](https://github.com/pezkuwichain/pezcumulus/blob/e2b7ad2061824f490c08df27a922c64f50accd6b/parachains/runtimes/assets/asset-hub-pezkuwi/src/lib.rs#L179)
|
||||
//! Runtime { ... }` In the source code. For Statemint it looks like [this](https://github.com/paritytech/cumulus/blob/e2b7ad2061824f490c08df27a922c64f50accd6b/parachains/runtimes/assets/asset-hub-polkadot/src/lib.rs#L179)
|
||||
//! at the time of writing. The `AccountId`, `Hash` and `Header` types of the [frame_system::pallet::Config](https://docs.rs/frame-system/latest/frame_system/pallet/trait.Config.html)
|
||||
//! correspond to the ones we want to use in our Subxt [crate::Config]. In the Case of Statemint
|
||||
//! (Asset Hub) they are:
|
||||
@@ -111,7 +111,7 @@
|
||||
//! metadata (see [`frame_metadata::v15::SignedExtensionMetadata`]).
|
||||
//!
|
||||
//! For statemint, the transaction extensions look like
|
||||
//! [this](https://github.com/pezkuwichain/pezcumulus/blob/d4bb2215bb28ee05159c4c7df1b3435177b5bf4e/parachains/runtimes/assets/asset-hub-pezkuwi/src/lib.rs#L786):
|
||||
//! [this](https://github.com/paritytech/cumulus/blob/d4bb2215bb28ee05159c4c7df1b3435177b5bf4e/parachains/runtimes/assets/asset-hub-polkadot/src/lib.rs#L786):
|
||||
//!
|
||||
//! ```rust,ignore
|
||||
//! pub type SignedExtra = (
|
||||
|
||||
+1
-1
@@ -563,7 +563,7 @@ where
|
||||
) -> Result<ValidationResult, ExtrinsicError> {
|
||||
let block_hash = at.into().hash();
|
||||
|
||||
// Approach taken from https://github.com/pezkuwichain/json-rpc-interface-spec/issues/55.
|
||||
// Approach taken from https://github.com/paritytech/json-rpc-interface-spec/issues/55.
|
||||
let mut params = Vec::with_capacity(8 + self.encoded().len() + 8);
|
||||
2u8.encode_to(&mut params);
|
||||
params.extend(self.encoded().iter());
|
||||
|
||||
Reference in New Issue
Block a user