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

Bump gtest from v1.0.2 to v1.1.1 #2

Closed
wants to merge 2 commits into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Feb 20, 2024

Bumps gtest from v1.0.2 to v1.1.1.

Release notes

Sourced from gtest's releases.

v1.1.1

Release v1.1.1 changes

  • Crates versions bumped to "v1.1.1", runtime spec version bumped to 1110;
  • Weights of extrinsic and WASM calls updated, schedule version bumped to 1110.

Update requirements

Name Character
JS clients ⚪ Insubstantial
Programs ⚪ Insubstantial
Node bin ⚪ Insubstantial

User-space

📚 New testing function has been added to gtest that allows to assert that message panicked with specific string (#3670);

[!TIP] Check out following gtest API snapshot:

 let panic_msg = "panic!";
- assert_eq!(result.log().len(), 1);
-     assert!(matches!(
-         result.log()[0].reply_code(),
-         Some(ReplyCode::Error(ErrorReplyReason::Execution(
-             SimpleExecutionError::UserspacePanic
-        )))
-     ));
-     let payload = String::from_utf8(result.log()[0].payload().into())
-         .expect("Unable to decode panic message");
-     assert!(payload.contains(&format!("panicked with '{panic_msg}'")));
+ result.assert_panicked_with(panic_msg);

📖 New CLI util implementing keystore/keyring has been added: gring (#3619);


📚 Crates.io bug with gtest on v1.1.0 version fixed (#3704);

Runtime

📚 Programs code reinstrumentation failure no longer supposed to be unreachable so from now on handled as succeeded error case (#3690);

[!NOTE] This increases stability of the protocol and adds more recovery cases from some state invalidity.


📖 Added ability to decline a voucher issued for you, marking it expired (#3725);

[!TIP] This significantly increases UX of signless apps.

Full Changelog: gear-tech/gear@v1.1.0...v1.1.1

... (truncated)

Changelog

Sourced from gtest's changelog.

FROM debian:12-slim

ARG RELEASE_VERSION

RUN apt-get update &&
apt-get install -y curl sudo xz-utils &&
rm -rf /var/lib/apt/lists/*

RUN if [ -z "$RELEASE_VERSION" ]; then
curl --proto '=https' --tlsv1.2 -sSf https://get.gear.rs/install.sh | bash -s -- --to /usr/local/bin/ ;
else
curl --proto '=https' --tlsv1.2 -sSf https://get.gear.rs/install.sh | bash -s -- --tag ${RELEASE_VERSION} --to /usr/local/bin/ ;
fi

RUN gear --version

CMD ["gear"]

Commits
  • 33ee05d feat(runtime): Add ability to decline given voucher (#3725)
  • 1f87dab feat(crates-io): update substrate deps on crates-io (#3704)
  • 890bcb0 Bump versions
  • 6a89dc8 Fix Cargo.lock
  • e4d381c feat(keyring): introduce gring (#3619)
  • 166af4b refactor!(pallet-gear): Make re-instrumentation fallible (#3690)
  • ae68e05 feat(gtest): Add option to check for if a message panicked on RunResult (#3670)
  • c8c09fc chore(runtime): Update weights (#3677)
  • 719c7a8 chore(runtime): Bump versions after v1.0.5 release (#3679)
  • 7cc01c7 fix(core-processor): fix double value charge when program terminated (#3678)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

clearloop and others added 2 commits February 20, 2024 18:57
Bumps [gtest](https://github.com/gear-tech/gear) from v1.0.2 to v1.1.1.
- [Release notes](https://github.com/gear-tech/gear/releases)
- [Changelog](https://github.com/gear-tech/gear/blob/master/docker/Dockerfile-release)
- [Commits](gear-tech/gear@d02d306...33ee05d)

---
updated-dependencies:
- dependency-name: gtest
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
Copy link
Author

dependabot bot commented on behalf of github Feb 20, 2024

The following labels could not be found: A4-insubstantial.

Copy link
Author

dependabot bot commented on behalf of github Feb 20, 2024

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/cargo/gtest-v1.1.1 branch February 20, 2024 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant