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

Transactions from a previous software version should be skipped #13487

Closed
tinker-michaelj opened this issue May 23, 2024 · 0 comments · Fixed by #13527
Closed

Transactions from a previous software version should be skipped #13487

tinker-michaelj opened this issue May 23, 2024 · 0 comments · Fixed by #13527
Assignees
Milestone

Comments

@tinker-michaelj
Copy link
Collaborator

Description

Post-v0.49.7 upgrade, records were created for expired transactions that were submitted before the upgrade and reached consensus after.

These records should not have been created; instead the expired transactions should have been completely skipped since they were created by an earlier software version. (C.f. here in mono-service.)

Steps to reproduce

Do an analogous upgrade.

Additional context

No response

Hedera network

mainnet

Version

v0.49.7

Operating system

None

@github-project-automation github-project-automation bot moved this to 📋 Backlog in Services Team May 23, 2024
@netopyr netopyr moved this from 📋 Backlog to Blocked in Services Team May 23, 2024
@netopyr netopyr moved this from Blocked to 📋 Backlog in Services Team May 23, 2024
@netopyr netopyr moved this from 📋 Backlog to 👷🏼‍♀️ In Progress in Services Team May 24, 2024
@netopyr netopyr added this to the v0.50 milestone May 24, 2024
@mhess-swl mhess-swl moved this from 👷🏼‍♀️ In Progress to 👀 In Review in Services Team May 25, 2024
@github-project-automation github-project-automation bot moved this from 👀 In Review to ✅ Done in Services Team May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants