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

Feature/51/subscription to minimal consensus #55

Merged

Conversation

blazejkrzak
Copy link

@blazejkrzak blazejkrzak commented Apr 15, 2021

This changes will allow estabilish Pandora subscription to Orchestrator

- tests fail, but no panics
- epochs are mocked, but subscription mock does not work
- right now method name is parsed ok, but array is not
- tests does not pass but orchestratorServer have minimal implementation
- for some reason notifier fails
- for some reason notifier fails
- for some reason notifier fails.. one of the msg during the handshake of subscription is empty and it produces err
- some kind of fallback on unmarshaling the result which is empty, TODO: debug if this really happen in prod env
- still backend gives me error when trying to subscribe
@atif-konasl atif-konasl self-requested a review April 19, 2021 08:14
- for some reason using publicFilterApi solves the subscription problem
- channel does not receive minimal consensus when listening to subscription
- subscription channel does not work yet
- orchestrator mocked in stress ethash is not passed everywhere
- moved to simplier struct, but test still fails on epoch 2
- execution engine should work with orchestrator
Copy link

@atif-konasl atif-konasl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall Review:
RP looks good but few vital concerns are:

  1. Subscriber should have retry option.
  2. Subscriber should not be maintained in PandoraSealer. Because, remote sealer only does sealing task.
  3. When pandora restarts every time, subscriber always starting from epoch 0 which is not ideal solution. Epoch should be latest according to its latest canonical block saved blockchain.
  4. For testing our implementation, we should not add/remove code in exiting implementation.
  5. We should maintain new package for our implementation, because we are implementing on top of active geth repo.

Travis CI Not Passed

consensus/ethash/pandora.go Outdated Show resolved Hide resolved
consensus/ethash/pandora.go Outdated Show resolved Hide resolved
eth/filters/api.go Outdated Show resolved Hide resolved
eth/filters/api.go Outdated Show resolved Hide resolved
@blazejkrzak
Copy link
Author

about concerns:

  1. yes
  2. yes
  3. yes
  4. yes
  5. yes
    But only point no 4 will be fixed in next commits.
    All the other stuff will be done during refactor. I plan to do so after we have working solution

@blazejkrzak blazejkrzak linked an issue Apr 27, 2021 that may be closed by this pull request
@blazejkrzak blazejkrzak changed the title [WIP] Feature/51/subscription to minimal consensus Feature/51/subscription to minimal consensus Apr 27, 2021
@blazejkrzak blazejkrzak merged commit a593d10 into epic/pandora-consensus Apr 28, 2021
@blazejkrzak blazejkrzak linked an issue Apr 28, 2021 that may be closed by this pull request
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.

[EPIC] Provide pandora consensus engine Move InsertMinimalConsensusInfo to subscription
2 participants