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

Problem: memiavl result is different when replaying write-ahead-log #995

Merged
merged 2 commits into from
Jul 3, 2023

Conversation

yihuang
Copy link
Collaborator

@yihuang yihuang commented Jun 30, 2023

Solution:

👮🏻👮🏻👮🏻 !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! 👮🏻👮🏻👮🏻

PR Checklist:

  • Have you read the CONTRIBUTING.md?
  • Does your PR follow the C4 patch requirements?
  • Have you rebased your work on top of the latest master?
  • Have you checked your code compiles? (make)
  • Have you included tests for any non-trivial functionality?
  • Have you checked your code passes the unit tests? (make test)
  • Have you checked your code formatting is correct? (go fmt)
  • Have you checked your basic code style is fine? (golangci-lint run)
  • If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
  • If your changes affect the client infrastructure, have you run the integration test?
  • If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
  • If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
  • If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

Thank you for your code, it's appreciated! :)

@codecov
Copy link

codecov bot commented Jun 30, 2023

Codecov Report

Merging #995 (61f02a0) into master (8dbdee7) will decrease coverage by 0.02%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master     #995      +/-   ##
==========================================
- Coverage   33.06%   33.04%   -0.03%     
==========================================
  Files         126      126              
  Lines       19999    19999              
==========================================
- Hits         6612     6608       -4     
- Misses      12329    12334       +5     
+ Partials     1058     1057       -1     
Flag Coverage Δ
integration_tests 20.66% <33.33%> (-0.02%) ⬇️
integration_tests_byzantine 9.62% <33.33%> (ø)
integration_tests_gov 9.95% <33.33%> (ø)
integration_tests_grpc 9.93% <33.33%> (ø)
integration_tests_ibc 24.74% <33.33%> (ø)
integration_tests_ledger 9.82% <33.33%> (ø)
integration_tests_slow 9.82% <33.33%> (-0.03%) ⬇️
integration_tests_solomachine 9.62% <33.33%> (ø)
integration_tests_upgrade 9.93% <33.33%> (ø)
unit_tests 10.97% <33.33%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
app/app.go 91.05% <33.33%> (-0.73%) ⬇️

@yihuang yihuang force-pushed the fix-empty-value branch from 8dc6b52 to 61f02a0 Compare July 3, 2023 01:19
@yihuang yihuang marked this pull request as ready for review July 3, 2023 01:20
@yihuang yihuang requested a review from a team as a code owner July 3, 2023 01:20
@yihuang yihuang requested a review from mmsqe July 3, 2023 01:24
@yihuang yihuang enabled auto-merge July 3, 2023 01:35
@yihuang yihuang added this pull request to the merge queue Jul 3, 2023
Merged via the queue into crypto-org-chain:master with commit 07e1a8f Jul 3, 2023
@yihuang yihuang deleted the fix-empty-value branch July 3, 2023 01:53
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.

2 participants