Skip to content

Conversation

@raresgaia123
Copy link
Collaborator

Description

Since having one config for the entire configuration couldn't handle partial worlds update, we implemented per world configuration tasks. Config runner takes care of scheduling and canceling the tasks based on some diffs between old and new config. Also, config runner will orchestrate processing configs based on what it needs to cancel. Updated the code with proper error handlers for cancelling tasks so it properly propagates to parent task. With this, world configuration can be tracked individually, making easier to implement retry on failure in the future.

Type of Change

  • Bug Fix
  • New Feature
  • Breaking Change
  • Refactor
  • Documentation
  • Other (please describe)

Checklist

  • I have read the contributing guidelines
  • Existing issues have been referenced (where applicable)
  • I have verified this change is not present in other open pull requests
  • Functionality is documented
  • All code style checks pass
  • New code contribution is covered by automated tests
  • All new and existing tests pass

@raresgaia123 raresgaia123 marked this pull request as draft November 6, 2025 13:04
Refactored pipeline code and moved world info related stuff into config_runner. With this, config_runner will be responsible of computing worlds to add and to remove and it will be used for when we refactor the code to handle per world configuration.
Since having one config for the entire configuration couldn't handle partial worlds update, we implemented per world configuration tasks. Config runner takes care of scheduling and canceling the tasks based on some diffs between old and new config. Also, config runner will orchestrate processing configs based on what it needs to cancel. Updated the code with proper error handlers for cancelling tasks so it properly propagates to parent task. With this, world configuration can be tracked individually, making easier to implement retry on failure in the future.
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.

1 participant