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

Remove NotConcrete error #3867

Merged

Conversation

chungquantin
Copy link
Contributor

@chungquantin chungquantin commented Mar 27, 2024

Description

polkadot address: 19nSqFQorfF2HxD3oBzWM3oCh4SaCRKWt1yvmgaPYGCo71J

@chungquantin chungquantin requested a review from a team as a code owner March 27, 2024 16:34
@chungquantin chungquantin requested a review from ggwpez March 28, 2024 13:09
- prdoc is not essential for a cleanup issue
- Remove `InvalidAssetNonConcrete` type because this is unused if there is no `NotConcrete` type in asset transfer.
@franciscoaguirre franciscoaguirre added the R0-silent Changes should not be mentioned in any release notes label Mar 29, 2024
Copy link
Contributor

@franciscoaguirre franciscoaguirre left a comment

Choose a reason for hiding this comment

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

👍 Should be good to merge after CI passes

@chungquantin
Copy link
Contributor Author

@franciscoaguirre the integration tests keeps failing at transaction_recrusion_limit_works() and I saw it logged stack limit error. Guess it is not related to the changes in this request right?

running 1 test
test transact_recursion_limit_works ... FAILED
failures:
failures:
    transact_recursion_limit_works
test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 4 filtered out; finished in 2.18s
--- TRY 6 STDERR:        xcm-executor-integration-tests transact_recursion_limit_works ---
Mar 30 02:18:31.373 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExceedsStackLimit    
Mar 30 02:18:31.373 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.373 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.373 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.373 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.373 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.373 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.373 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.373 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.373 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.374 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.375 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExceedsStackLimit    
Mar 30 02:18:31.375 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.375 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.375 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.375 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.375 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.375 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.375 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.376 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.376 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
Mar 30 02:18:31.376 ERROR xcm::pallet_xcm::execute: XCM execution failed with error ExpectationFalse    
thread 'transact_recursion_limit_works' panicked at polkadot/xcm/xcm-executor/integration-tests/src/lib.rs:146:9:
assertion `left == right` failed
  left: 0
 right: 10
stack backtrace:
   0: rust_begin_unwind
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:645:5
   1: core::panicking::panic_fmt
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/panicking.rs:72:14
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
   4: environmental::using
   5: core::ops::function::FnOnce::call_once
   6: core::ops::function::FnOnce::call_once
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/ops/function.rs:250:5

@acatangiu
Copy link
Contributor

acatangiu commented Apr 15, 2024

Try merging master, unrelated CI errors should go away now

@paritytech-cicd-pr
Copy link

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable 3/3
Logs: https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/5928921

@chungquantin
Copy link
Contributor Author

@acatangiu I think this PR is still impacted by the CI

@ggwpez
Copy link
Member

ggwpez commented Apr 15, 2024

Yes please fix the issue as pinged by the bot: #3867 (comment)

PS: Dont know why the error index is hard-coded, no wonder it fails. I would personally just do Err(crate::Error::<Test>::TooManyReserves.into()) instead of hard-coding error indices...

@acatangiu
Copy link
Contributor

Yes please fix the issue as pinged by the bot: #3867 (comment)

PS: Dont know why the error index is hard-coded, no wonder it fails. I would personally just do Err(crate::Error::<Test>::TooManyReserves.into()) instead of hard-coding error indices...

Yes, good idea!

@chungquantin you can locally test this with cargo test -p pallet-xcm - fix the tests to pass locally, then should also pass in CI

@chungquantin
Copy link
Contributor Author

@acatangiu @ggwpez I have updated the code to resolve issues with CI.

@liamaharon
Copy link
Contributor

/tip small

@liamaharon liamaharon added this pull request to the merge queue Apr 18, 2024
Copy link

@liamaharon A referendum for a small (20 DOT) tip was successfully submitted for @chungquantin (19nSqFQorfF2HxD3oBzWM3oCh4SaCRKWt1yvmgaPYGCo71J on polkadot).

Referendum number: 681.
tip

Copy link

The referendum has appeared on Polkassembly.

Merged via the queue into paritytech:master with commit d591b16 Apr 18, 2024
132 of 136 checks passed
@chungquantin chungquantin deleted the chungquantin/remove_not_concrete branch April 18, 2024 07:12
sandreim pushed a commit that referenced this pull request Apr 18, 2024
# Description
- Link to issue: #3651

polkadot address: 19nSqFQorfF2HxD3oBzWM3oCh4SaCRKWt1yvmgaPYGCo71J
UnableToDecode,
/// XCM encoded length is too large.
/// Returned when an XCM encoded length is larger than `MaxXcmEncodedSize`.
#[codec(index = 26)]
Copy link
Member

@ggwpez ggwpez Apr 18, 2024

Choose a reason for hiding this comment

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

Not what i meant by:

I would personally just do Err(crate::Error::<Test>::TooManyReserves.into()) instead of hard-coding error indices

...

Please remove the hard-coded indices here:

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh I saw your suggestion. Should I revert and follow your aproach?

Copy link
Contributor

Choose a reason for hiding this comment

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

no revert required, you could do a followup PR

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Gotcha thanks @acatangiu @ggwpez

@chungquantin chungquantin restored the chungquantin/remove_not_concrete branch April 18, 2024 11:14
@chungquantin chungquantin deleted the chungquantin/remove_not_concrete branch April 18, 2024 11:18
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.

6 participants