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.

Sign up for GitHub

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

Jump to bottom

Record resolving order in the sequencer and start modules based on that #240

Closed
rpanic opened this issue Dec 10, 2024 · 0 comments · Fixed by #245
Closed

Record resolving order in the sequencer and start modules based on that #240

rpanic opened this issue Dec 10, 2024 · 0 comments · Fixed by #245
Assignees
@ejMina226

Comments

@rpanic
Copy link
Member

rpanic commented Dec 10, 2024

Currently, the order that sequencer modules are resolved can be different in which they are started, which can lead to problems on dependencies not being initialized properly.
We can fix this by recording the order that modules are resolved and starting them based on that.
@rpanic rpanic moved this to Backlog in Main Board Dec 10, 2024
@ejMina226 ejMina226 self-assigned this Dec 10, 2024
@ejMina226 ejMina226 moved this from Backlog to In Progress in Main Board Dec 10, 2024
@ejMina226 ejMina226 linked a pull request Dec 13, 2024 that will close this issue
Record resolving order in the sequencer and start modules based on that #245
Merged
@ejMina226 ejMina226 moved this from In Progress to In Review in Main Board Dec 13, 2024
@github-project-automation github-project-automation bot moved this from In Review to Done in Main Board Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ejMina226 ejMina226

Labels
None yet
Projects
Main Board
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Record resolving order in the sequencer and start modules based on that proto-kit/framework
2 participants
@rpanic @ejMina226