-
Notifications
You must be signed in to change notification settings - Fork 110
Issues: ChainSafe/gossamer
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Make candidate backing subsystem code concurrent
S-subsystems-backing
issues related to polkadot host backing subsystem functionality.
#4070
opened Jul 4, 2024 by
axaysagathiya
bug(Westend): Complex changes across multiple modules. Possibly will require additional research.
P-critical
this must be fixed immediately or contributors or users will be severely impacted.
S-sync-westend
related to particular network syncing.
T-bug
this issue covers unexpected and/or wrong behaviour.
Storage root must match that calculated
at #17274469
C-complex
#4064
opened Jun 26, 2024 by
EclesioMeloJunior
BABE for Full Node MVP
Epic
Issue used to track development status of a complex feature, aggregates several issues
Implement warp sync provider
A-design
issue requires design work to think about how it would best be accomplished.
C-complex
Complex changes across multiple modules. Possibly will require additional research.
S-network
issues related to the dot/network package.
T-feat
this issue/pr is a new feature or functionality.
#4053
opened Jun 19, 2024 by
EclesioMeloJunior
Implement warp sync request handler
A-design
issue requires design work to think about how it would best be accomplished.
C-complex
Complex changes across multiple modules. Possibly will require additional research.
S-network
issues related to the dot/network package.
T-feat
this issue/pr is a new feature or functionality.
#4052
opened Jun 19, 2024 by
EclesioMeloJunior
3 tasks
test(dot/parachain/backing): Investigate on how to mock overseer for integration tests
S-subsystems-backing
issues related to polkadot host backing subsystem functionality.
S-tests
issue related to adding new tests.
#4029
opened Jun 10, 2024 by
axaysagathiya
refactor: Consider different implementation of the type ServiceRegistry
#4019
opened Jun 8, 2024 by
EmilGeorgiev
TestInstance_ParachainHostSessionInfo
test fails in CI Frequently
P-high
#4016
opened Jun 7, 2024 by
axaysagathiya
test(dot/parachain/backing): new leaf view doesnt clobber old
#4014
opened Jun 6, 2024 by
axaysagathiya
test(dot/parachain/backing): observes backing even if not a parachain validator
S-subsystems-backing
issues related to polkadot host backing subsystem functionality.
S-tests
issue related to adding new tests.
#4012
opened Jun 6, 2024 by
axaysagathiya
test(dot/parachain/backing): retry on failed PoV fetching.
S-subsystems-backing
issues related to polkadot host backing subsystem functionality.
S-tests
issue related to adding new tests.
#4011
opened Jun 6, 2024 by
axaysagathiya
test(dot/parachain/backing): The order of validity votes is correct in issues related to polkadot host backing subsystem functionality.
S-tests
issue related to adding new tests.
backedCandidate
S-subsystems-backing
#4010
opened Jun 6, 2024 by
axaysagathiya
test(dot/parachain/backing): if the validation of the candidate has failed this does not stop the work of this subsystem and so it is not fatal to the node.
S-subsystems-backing
issues related to polkadot host backing subsystem functionality.
S-tests
issue related to adding new tests.
#4009
opened Jun 6, 2024 by
axaysagathiya
test(dot/parachain/backing): if we have already issued a statement (in this case issues related to polkadot host backing subsystem functionality.
S-tests
issue related to adding new tests.
Invalid
) about a candidate we will not be issuing a Seconded
statement on it.
S-subsystems-backing
#4008
opened Jun 6, 2024 by
axaysagathiya
test(dot/parachain/backing): if we are asked to second an invalid candidate we can still second a valid one afterwards.
S-subsystems-backing
issues related to polkadot host backing subsystem functionality.
S-tests
issue related to adding new tests.
#4007
opened Jun 6, 2024 by
axaysagathiya
test(dot/parachain/backing): Issuing conflicting statements on the same candidate should be a misbehavior.
S-subsystems-backing
issues related to polkadot host backing subsystem functionality.
S-tests
issue related to adding new tests.
#4006
opened Jun 6, 2024 by
axaysagathiya
test(dot/parachain/backing): the candidate reaches quorum successfully.
#4004
opened Jun 6, 2024 by
axaysagathiya
test(dot/parachain/backing): Write integration tests
Epic
Issue used to track development status of a complex feature, aggregates several issues
S-subsystems-backing
issues related to polkadot host backing subsystem functionality.
S-tests
issue related to adding new tests.
#4002
opened Jun 5, 2024 by
axaysagathiya
2 of 13 tasks
(pkg/trie): Merkle proof verifications
C-complex
Complex changes across multiple modules. Possibly will require additional research.
S-trie
issues related to the pkg/trie package.
T-feat
this issue/pr is a new feature or functionality.
#4001
opened Jun 3, 2024 by
dimartiro
(pkg/trie): Merkle proof generation
C-complex
Complex changes across multiple modules. Possibly will require additional research.
S-trie
issues related to the pkg/trie package.
T-feat
this issue/pr is a new feature or functionality.
#4000
opened Jun 3, 2024 by
dimartiro
(pkg/trie): Implement TrieDB recorder
C-complex
Complex changes across multiple modules. Possibly will require additional research.
S-trie
issues related to the pkg/trie package.
T-feat
this issue/pr is a new feature or functionality.
#3999
opened Jun 3, 2024 by
dimartiro
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.