Skip to content

Conversation

@mrubens
Copy link
Collaborator

@mrubens mrubens commented Mar 17, 2025

Trying to make it so we don't get a ton of these PRs in parallel when we merge stuff


Important

Remove branch-suffix: timestamp in update-contributors.yml to use a single branch for updates, preventing multiple parallel PRs.

  • Behavior:
    • Removes branch-suffix: timestamp from update-contributors.yml to use a single branch for updates.
    • Prevents multiple parallel PRs by using a consistent branch name update-contributors.

This description was created by Ellipsis for 94f176b. It will automatically update as commits are pushed.

@changeset-bot
Copy link

changeset-bot bot commented Mar 17, 2025

⚠️ No Changeset found

Latest commit: 94f176b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@dosubot dosubot bot added size:XS This PR changes 0-9 lines, ignoring generated files. enhancement New feature or request labels Mar 17, 2025
@mrubens mrubens merged commit 8569c46 into main Mar 17, 2025
17 checks passed
@mrubens mrubens deleted the single_update_contributors_branch branch March 17, 2025 17:02
@github-project-automation github-project-automation bot moved this from New to Done in Roo Code Roadmap Mar 17, 2025
hassoncs pushed a commit to hassoncs/Roo-Code that referenced this pull request Aug 4, 2025
The `rootTask` and `parentTask` properties in the `Task` class were
incorrectly initialized, preventing sub-tasks from properly reporting
their results back to the main Orchestrator task. This commit fixes
the initialization to ensure correct task hierarchy and result propagation.

The issue is with how TypeScript handles `readonly` properties when they have explicit initializers. Let me demonstrate:

```typescript
readonly rootTask: Task | undefined
readonly parentTask: Task | undefined
```

```typescript
readonly rootTask: Task | undefined = undefined
readonly parentTask: Task | undefined = undefined
```

When you declare a `readonly` property with an explicit initializer like `= undefined`, TypeScript treats this as a **definitive assignment** that happens at the class field level, **before** the constructor runs.

Here's what happens:

1. Class is instantiated
2. Constructor runs
3. `this.parentTask = parentTask` successfully assigns the parent task
4. Property now contains the actual parent task reference

1. Class is instantiated
2. **TypeScript immediately sets `this.parentTask = undefined` due to the field initializer**
3. Constructor runs
4. `this.parentTask = parentTask` tries to assign, but TypeScript may optimize this away or the field initializer takes precedence
5. Property remains `undefined` even though we tried to assign it

Fixes RooCodeInc#1742
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants