Unable to deploy wasm contracts with newer rust version

[ghost]

After the merge of PR #293 , which was expected to resolve the issue mentioned in nearcore issue #9143, it seems that the problem persists when using the latest main hash as a dependency. This issue aims to track the investigation and resolution of this persistent error.

[mrLSD]

It's more context about the issue:

Example PR: aurora-is-near/release-repository/pull/2

It was updated toolchain from nightly-2023-03-15 to stable.
And it was cargo update.

Tests fail with a Deserialization error.

cc: @shariffdev

[mrLSD]

@shariffdev any progress on that issue?

[ghost]

@mrLSD

I apologize for the delay in getting back to you. I have conducted a more in-depth investigation into the issue raised in the PR. During this analysis, I encountered some unusual behavior; however, I was able to successfully execute the tests, which seem to be functioning properly now and address the logging issue you mentioned earlier.

As an interim solution, I managed to devise a workaround that appears to be stable for the time being. Here are the steps I took to rectify the issue:

• Compile the NEAR sandbox from the source (or you can actually retrieve the sandbox inside the release-repository after building the project should be here -> release-repository/target/debug/build/near-sandbox-utils-xxxx/out/near-sandbox)
• Run your tests using the compiled sandbox.

Please note, this is a temporary solution and not a final resolution. I wanted to ensure that the tests could run without any hitches as I look more into it.

You can run the test using the following command:

NEAR_SANDBOX_BIN_PATH="./near-sandbox"  cargo t

I have attached my screenshot below and as you can see; it silences the log messages as well.

[mrLSD]

Tjanja. When do you planing release solution, when things works out of the box?

[ghost]

@mrLSD A fix is in the process currently, I will notify you when the fix is out.

[ghost]

@mrLSD We have a PR in progress which should be able to fix the problems mentioned in the PR.

[ghost]

This issue has been resolved, you can wait for 0.8.0 release or you can use latest commit. I am closing this issue

[mrLSD]

Thanks @shariffdev !
Is there any schedule for the release date?

[ghost]

Hey @mrLSD a new version has been released, you are good to update to 0.8.0