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

Make penpal-runtime's TrustedReserves more connfigurable (#3564) (patch for 1.8.0) #3625

Merged
merged 1 commit into from
Mar 11, 2024

Conversation

bkontur
Copy link
Contributor

@bkontur bkontur commented Mar 8, 2024

Backport of #3564

Expected patches for (1.8.0):

  • penpal-runtime 0.16.1

The current `penpal` runtime utilizes the `EthereumLocation` parameter,
which is employed for XCM emulated integration tests concerning the
Rococo <> ETH bridge. It includes a hard-coded chainId for the Ethereum
testnet utilized in Rococo. The `EthereumLocation` serves the purpose of
aligning with the `TrustedReserves`. However, due to this hard-coded
configuration, reusing `penpal` for testing various environments such as
Kusama/Polkadot versus Ethereum bridge becomes unfeasible.

This PR introduces the capability to easily customize the asset location
for `TrustedReserves` without needing to know anything about Ethereum.


## TODO
- [x] fix integration tests with
`System::set_storage(CustomizableAssetFromSystemAssetHub::key(),
<whatever-location-is-needed>)` @claravanstaden
- [ ] ~~maybe add some helper function/macro to support `set_storage`
for other runtimes (that we could reuse)~~
- [ ] Release patch for: `penpal-runtime` + emulated crate with
`set_storage` support (if needed)
  - [ ] backport to 1.7.0
  - [ ] backport to 1.8.0

---------

Co-authored-by: Clara van Staden <[email protected]>
# Conflicts:
#	cumulus/parachains/runtimes/testing/penpal/Cargo.toml

# Conflicts:
#	Cargo.lock
#	cumulus/parachains/runtimes/testing/penpal/Cargo.toml
@bkontur bkontur added the R0-silent Changes should not be mentioned in any release notes label Mar 8, 2024
Copy link
Contributor

@acatangiu acatangiu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why all the Cargo.lock changes?

@bkontur
Copy link
Contributor Author

bkontur commented Mar 9, 2024

why all the Cargo.lock changes?

I think, because actual Cargo.lock has not been pushed after the last patch-release from release-crates-io-v1.8.0.
@Morganamilo right? I think it would be better for next patch-release if you could push also actual Cargo.lock.

E.g. actual version of asset-hub-rococo-integration-tests in this branch is really 0.1.0 so the Cargo.lock change is correct:

[[package]]
name = "asset-hub-rococo-integration-tests"
- version = "1.0.0"
+ version = "0.1.0"

You can try it with checkout of release-crates-io-v1.8.0 and run cargo build and it will automatically change Cargo.lock

> git checkout release-crates-io-v1.8.0
>
> git status
On branch release-crates-io-v1.8.0
Your branch is up to date with 'origin/release-crates-io-v1.8.0'.

nothing to commit, working tree clean

>
> cargo build
>
> git status 
On branch release-crates-io-v1.8.0
Your branch is up to date with 'origin/release-crates-io-v1.8.0'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   Cargo.lock

@bkontur bkontur requested a review from acatangiu March 10, 2024 21:57
@acatangiu acatangiu merged commit 25f345c into release-crates-io-v1.8.0 Mar 11, 2024
129 of 138 checks passed
@acatangiu acatangiu deleted the bko-patch-penpal-1.8.0 branch March 11, 2024 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R0-silent Changes should not be mentioned in any release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants