Skip to content

[Scheduled Actions] CHASM Backfill task #8167

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

lina-temporal
Copy link
Contributor

What changed?

  • Backfill task ported to CHASM.

How did you test it?

  • built
  • run locally and tested manually
  • covered by existing tests
  • added new unit test(s)
  • added new functional test(s)

@lina-temporal lina-temporal requested a review from a team as a code owner August 7, 2025 23:55
_ chasm.TaskAttributes,
_ *schedulespb.BackfillerTask,
) error {
defer func() { backfiller.Attempt++ }()
Copy link
Member

Choose a reason for hiding this comment

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

do we need to check Attempt in Validate(), I see there's a TODO for that in today's hsm implementation.

serviceerror.NewInternal("Scheduler tree missing node"),
err)
}
logger := newTaggedLogger(b.BaseLogger, scheduler)
Copy link
Member

Choose a reason for hiding this comment

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

I am thinking if CHASM framework should provide a logger via maybe the Context and tag the entity key and shardID by default.

Component has no way to get shardID and looks like have to store the entity key (namespace & business ID) as part of it's state.

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.

2 participants