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

bug(class): declared classes not stored in last tick #278

Open
1 task done
apoorvsadana opened this issue Sep 22, 2024 · 4 comments
Open
1 task done

bug(class): declared classes not stored in last tick #278

apoorvsadana opened this issue Sep 22, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@apoorvsadana
Copy link
Contributor

Is there an existing issue?

  • I have searched the existing issues

Description of bug

store_block is only called during ticks as here. They aren't stored during on_block_time which causes it changes to not reflect. We should store the declared classes in on_block_time

Steps to reproduce

No response

@apoorvsadana
Copy link
Contributor Author

Should be solved in #271

@cchudant
Copy link
Member

I think the issue you're referring to is something else: the verify_apply step of block import does the store block, we don't need it in block prod
I have fixed another thing which was related to forcing db flush for block production at every block, I believe that's what you're referring to.
Pending block in block prod does not use the block import pipeline yet, and that's why the store block is there
it will use the block improt and i'm also adding the ability to continue the last pending block on start-up, as well as the ability to save the tx pool to disk

@apoorvsadana
Copy link
Contributor Author

I see. I will explain the behaviour I saw which is why I thought this was the issue

  • If a class is declared in any tick except the last one, I am able to get the class using starkli i.e. its stored inside the DB
  • If a class is declared in the last tick (I can force this to happen if tick time = block time, in my case it was actually tick time = 2*block time which shouldn't be possible, created issue bug(mempool): tick time <= block time #277), then getting the class from starkli was failing

Does this also explain the db flush issue?

@cchudant
Copy link
Member

ah, no it was because i forgot to save the declared class when closing a block. It's fixed yes

@antiyro antiyro added the bug Something isn't working label Sep 25, 2024
@antiyro antiyro changed the title bug: declared classes not stored in last tick bug(class): declared classes not stored in last tick Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Ready
Development

No branches or pull requests

3 participants