Andrei Băncioiu

The following contribution of @MWFIAE can serve as a starting point for adjusting the `ResultsParser` of `sdk-core`: ``` /** * Custom ResultsParser that is needed until elrond correctly implements relayedTransactions....

~~Normally, the "completion detection" issues should be resolved once **sdk-core**'s `TransactionWatcher` is updated to be compatible with **sdk-network-provider**'s transaction status adjustment: https://github.com/multiversx/mx-sdk-js-network-providers/pull/41.~~ We will apply that as a non-breaking change...

@juliancwirko, thanks a lot for the report and for the provided details :raised_hands: We'll handle this as soon as possible :pray:

> in my sc for function argument. @juliancwirko, to narrow down a bit the issue, do you think you can specify how is the function called? E.g. using the `contract.methods`...

Workaround: do not unwrap the enum values. That is, drop the `...` from `...customEnumNamesAsStrings.map((enumName)`. Actually, this should be the correct way of passing the (optional) variadic values. We'll analyze now...

Yes, but in v12, it worked just as you've said (while it wouldn't have worked in the way it works for v13) - this is a breaking change (from v12...

@juliancwirko, a more detailed analysis of the issue is here: https://github.com/multiversx/mx-sdk-js-core/pull/441. For `optional`, you might be interested into [this comment](https://github.com/multiversx/mx-sdk-js-core/pull/441#issuecomment-2063482203) - it includes several ways to tackle the issue. Furthermore,...

Thank you! We will leave the issue open for ~1 month.

Hello @ctindogaru, thank you for the report :pray: Currently, `mxpy contract test` only runs the JSON-base scenarios (previously called Mandos Tests). On the other hand, `cargo test` only runs the...

Hello @ctindogaru, Currently, `mxpy` does not run any Rust unit test. Also, `cargo test` does not run any scenario (ex-mandos). Does it answer the question? We will adjust `mxpy` to...