-
Notifications
You must be signed in to change notification settings - Fork 112
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
chore(dot/sync): Introduce
Fragment
type to FullSync
strategy
#4320
opened Nov 7, 2024 by
EclesioMeloJunior
Regression test and merge feat/parachain
C-chaotic
Unpredictable nature of this task/changes makes its chaotic.
S-tests
issue related to adding new tests.
T-feat
this issue/pr is a new feature or functionality.
T-refactor
this issue/pr covers refactoring of existing code.
#4317
opened Nov 5, 2024 by
P1sar
Change type of group id from issues related to polkadot host backing subsystem functionality.
ParaID
to CoreIndex
S-subsystems-backing
#4316
opened Nov 5, 2024 by
axaysagathiya
feat(prospective-parachains) implement Fragment Chain
A-tooBig
issue or PR needs to be broken down to smaller parts.
C-complex
Complex changes across multiple modules. Possibly will require additional research.
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.
#4314
opened Nov 4, 2024 by
EclesioMeloJunior
5 tasks
feat(prospective-parachains) handle Complex changes across multiple modules. Possibly will require additional research.
S-subsystems-common
GetProspectiveValidationData
signal
C-complex
#4313
opened Nov 4, 2024 by
EclesioMeloJunior
feat(prospective-parachains) handle Minor changes changes, no additional research needed. Good first issue/review.
S-subsystems-common
GetMinimumRelayParents
signal
C-simple
#4312
opened Nov 4, 2024 by
EclesioMeloJunior
feat(prospective-parachains) handle Complex changes across multiple modules. Possibly will require additional research.
S-subsystems-common
GetHypotheticalMembership
signal
C-complex
#4311
opened Nov 4, 2024 by
EclesioMeloJunior
1 task
feat(prospective-parachains) handle Complex changes across multiple modules. Possibly will require additional research.
S-subsystems-common
GetBackableCandidates
signal
C-complex
#4310
opened Nov 4, 2024 by
EclesioMeloJunior
1 task
feat(prospective-parachains) handle Complex changes across multiple modules. Possibly will require additional research.
S-subsystems-common
CandidateBacked
signal
C-complex
#4309
opened Nov 4, 2024 by
EclesioMeloJunior
1 task
feat(prospective-parachains): handle Complex changes across multiple modules. Possibly will require additional research.
S-subsystems-common
IntroduceSecondedCandidate
signal
C-complex
#4308
opened Nov 4, 2024 by
EclesioMeloJunior
4 tasks
Reassess GRANDPA integration
C-chaotic
Unpredictable nature of this task/changes makes its chaotic.
S-grandpa
issues related to block finality.
T-investigation
this issue/pr is an investigation, probably related to some bug with unknown causes.
#4306
opened Nov 4, 2024 by
P1sar
feat(prospective-parachains): handle Complex changes across multiple modules. Possibly will require additional research.
S-subsystems-common
ActiveLeaves
signal
C-complex
#4305
opened Nov 4, 2024 by
EclesioMeloJunior
7 tasks
feat(prospective-parachains): subsystem skeleton
C-simple
Minor changes changes, no additional research needed. Good first issue/review.
S-subsystems-common
#4304
opened Nov 4, 2024 by
EclesioMeloJunior
10 tasks
(feat/parachain): Implement code for FetchChunks recovery strategy
S-subsystems-availability
issues related to polkadot host availability subsystem functionality.
#4301
opened Nov 1, 2024 by
edwardmack
(feat/parachain): Implement code for FetchSystematicChunks recovery strategy
S-subsystems-availability
issues related to polkadot host availability subsystem functionality.
#4300
opened Nov 1, 2024 by
edwardmack
(feat/parachain): Implement code for FullFetch recovery strategy
S-subsystems-availability
issues related to polkadot host availability subsystem functionality.
#4299
opened Nov 1, 2024 by
edwardmack
(feat/parachain): Implement logic for determining and launching recovery strategy
S-subsystems-availability
issues related to polkadot host availability subsystem functionality.
#4298
opened Nov 1, 2024 by
edwardmack
feat(dot/parachain): create skeleton for Availability Recovery subsystem
S-subsystems-availability
issues related to polkadot host availability subsystem functionality.
#4297
opened Nov 1, 2024 by
edwardmack
7 tasks
Update issues related to polkadot host backing subsystem functionality.
GetBackableCandidates
struct and logic to process it
S-subsystems-backing
#4296
opened Oct 31, 2024 by
axaysagathiya
2 tasks
Investigation/design for Availability Recovery subsystem
S-subsystems-availability
issues related to polkadot host availability subsystem functionality.
T-investigation
this issue/pr is an investigation, probably related to some bug with unknown causes.
#4295
opened Oct 31, 2024 by
timwu20
5 tasks done
Gossamer persists default config and CLI flags in config file
P-high
this should be addressed ASAP.
S-cli
issue related to Gossamer CLI.
T-bug
this issue covers unexpected and/or wrong behaviour.
#4293
opened Oct 30, 2024 by
haikoschol
feat(overseer): check if header supports parachain consensus
C-simple
Minor changes changes, no additional research needed. Good first issue/review.
S-subsystems-overseer
issues related to Polkadot host overseer functionality.
#4292
opened Oct 30, 2024 by
EclesioMeloJunior
feat(statement-distribution): implement V2 task responder
S-subsystems-backing
issues related to polkadot host backing subsystem functionality.
#4285
opened Oct 29, 2024 by
EclesioMeloJunior
Westend sync stalls at block #2318338
A-debug
issue requires detective debug work to figure out what's going wrong.
C-chaotic
Unpredictable nature of this task/changes makes its chaotic.
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.
#4281
opened Oct 28, 2024 by
haikoschol
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.