Skip to content

Conversation

@lina-temporal
Copy link
Contributor

What changed?

  • Tasks now also retain a taskVersion, used to invalidate an immediately-scheduled task.
  • The inline immediate task execution optimization has been enabled.
  • A few bugs found during testing related to improper validation have been fixed as a result of this.

How did you test it?

  • Features, functional, unit tests. This fixes some existing stuff, and I've added a new test for something that was specifically broken without these changes.

@lina-temporal lina-temporal requested review from a team as code owners January 7, 2026 02:51
Base automatically changed from chasm-listmatchingsched to main January 7, 2026 17:10
@lina-temporal lina-temporal force-pushed the chasm-cleanup-sched-tasks branch from d1a995a to 0aceb11 Compare January 7, 2026 21:54
@lina-temporal lina-temporal requested a review from yycptt January 7, 2026 21:55
Copy link
Member

@yycptt yycptt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not super familiar with the buffered start logic but the rest LGTM.

}
scheduler.Backfillers[id] = chasm.NewComponentField(ctx, backfiller)

backfiller.scheduleTask(ctx, chasm.TaskScheduledTimeImmediate)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just checking, using chasm.TaskScheduledTimeImmediate or not give the same behavior right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, same behavior, and backfills reschedule themselves at particular points of time when backing off.

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.

3 participants