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

[WIP] Feature/l15 faucet #86

Open
wants to merge 37 commits into
base: release/l15
Choose a base branch
from
Open

Conversation

blazejkrzak
Copy link

@blazejkrzak blazejkrzak commented Aug 26, 2021

This pr is for the faucet-specific implementation. It is run in l15 prod namespace

New() for pandora.go
- Start() happy path for connection wait
- Start() happy path for done event
- Start() happy path for subscription err ch
- Start() happy path for seal request
- Start() failure path for seal request
- Start() happy path for seal request (still failing, TODO present)
- Start() happy path for seal request
- Start() happy path for seal request without any changes, fail path for sharding request
- Start() fail path for sharding request
- Start() covered with all ifs within
- Start() covered with all ifs within
- Fmt now pass
- Remove todo
- added skip on facebook test and golang binding test
- added skip on facebook test and golang binding test
Try to support ubuntu 18.04
Fix in test about epochInfo turned to cache
Added faucet support and docker build
Frontend changes
Faucet is now able to synchronize
- refactored a bit confirmation logic, but still need to remove it
- little refactor
- little refactor, lint
- little refactor, lint, lint
Copy link

@meta-bot meta-bot left a comment

Choose a reason for hiding this comment

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

I've several questions about the advance header validation and block validation. I think it must be resolved before accepting the merge.

core/blockchain.go Show resolved Hide resolved
core/blockchain.go Show resolved Hide resolved
@frozeman
Copy link
Owner

Can you explain your thinking on the block verification flow @blazejkrzak ?

- very hardcoded, insecure state
- rollback of insecure state
- change of the faucet title
- move dockerfile creation to root directory
- content and visual changes
- removed facebook handler
- visual changes of html
@blazejkrzak
Copy link
Author

we are far ahead of this changeset in develop candidate. I will either:

@rryter
Copy link

rryter commented Oct 27, 2021

I updated the tweet template to look like this:

Screenshot 2021-10-27 at 11 28 47

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.

5 participants