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

gossamer: compatibility issues #407

Open
radkomih opened this issue Apr 26, 2024 · 3 comments
Open

gossamer: compatibility issues #407

radkomih opened this issue Apr 26, 2024 · 3 comments
Assignees

Comments

@radkomih
Copy link
Collaborator

radkomih commented Apr 26, 2024

Setup:

  • Gosemble runtime configured with babe and grandpa
  • Gossamer host
@radkomih
Copy link
Collaborator Author

radkomih commented Jun 5, 2024

With Gossamer node in polkadot.js:

test extrinsic call

 target=runtime message=RUNTIME API: TransactionPaymentApi_query_info	ext_logging_log_version_1	pkg=runtime module=wazero
2024-04-14T18:43:27+03:00 CRITICAL target=runtime message=invalid 'NextConfigDescriptor' type	ext_logging_log_version_1	pkg=runtime module=wazero
2024-04-14T18:43:28+03:00 WARN     target=runtime message=RUNTIME API: Metadata_metadata	ext_logging_log_version_1	pkg=runtime module=wazero
2024-04-14T18:43:28+03:00 WARN     target=runtime message=RUNTIME API: TaggedTransactionQueue_validate_transaction	ext_logging_log_version_1	pkg=runtime module=wazero
2024-04-14T18:43:28+03:00 CRITICAL target=runtime message=invalid 'NextConfigDescriptor' type	ext_logging_log_version_1	pkg=runtime module=wazero
2024-04-14T18:43:28+03:00 WARN     failed to create listener (method=author_submitAndWatchExtrinsic): handling submitted extrinsic: running runtime function: wasm error: unreachable

send some amount from an account with zero balance

2024-04-10T13:55:53+03:00 WARN     failed to create listener (method=author_submitAndWatchExtrinsic): handling submitted extrinsic: running runtime function: wasm error: unreachable
wasm stack trace:
	.(github.com/LimeChain/gosemble/frame/balances.Module).Withdraw(i32,i32,i32,i32,i32,i32,i32,i32,i32,i32,i64,i64,i32)
	.(github.com/LimeChain/gosemble/frame/transaction_payment/extensions.chargeTransaction).WithdrawFee(i32,i32,i32,i32,i32,i32,i64,i64,i64,i64)
	.(github.com/LimeChain/gosemble/frame/transaction_payment/extensions.ChargeTransactionPayment).withdrawFee(i32,i64,i64,i32,i32,i32,i32,i32,i32,i32,i32,i32,i32)
	.(github.com/LimeChain/gosemble/frame/executive.module).ValidateTransaction(i32,i32,i32,i32,i32,i32,i32,i32,i32,i32,i32,i32,i32,i32,i32,i32)
	.TaggedTransactionQueue_validate_transaction.command_export(i32,i32) i64	pkg=rpc/subscription

this happens from time to time

2024-04-09T17:50:33+03:00 CRITICAL target=runtime message=Timestamp must be updated once in the block	ext_logging_log_version_1	pkg=runtime module=wazero

@radkomih radkomih changed the title fix(babe): metadata and test coverage gossamer: compatibility issues Jun 6, 2024
@radkomih
Copy link
Collaborator Author

radkomih commented Jun 6, 2024

Events does not show up in the "recent events" section of the UI

@radkomih
Copy link
Collaborator Author

radkomih commented Jun 6, 2024

Certain storage items seem to have incorrect metadata (in polkadot-js)

babe.authorVrfRandomness: Option<[u8;32]> - <unknown>
babe.epochStart: (u64,u64) - <unknown>
babe.nextEpochConfig: Option<SpConsensusBabeBabeEpochConfiguration> - <unknown>
babe.initialized: Option<Option<SpConsensusBabeDigestsPreDigest>> - null
babe.underConstruction: [u8;32] - <unknown>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants