Skip to content

Conversation

@pdoerner
Copy link
Contributor

@pdoerner pdoerner commented Nov 25, 2025

What changed?

Cherry-picking a few fixes

Why?

So that history service can run with chasm enabled in a test cell

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)

yycptt and others added 4 commits November 25, 2025 09:37
## What changed?
- Use immutable chasm context to access node when doing validations

## Why?
- Validation doesn't change component state and nothing needs to be
persisted.
- Some parts of the system skips persistence when component access fail
on validation step, if node is marked dirty, a dirty mutable state panic
will be triggered upon releasing the execution lock.

## How did you test it?
- [x] built
- [ ] run locally and tested manually
- [ ] covered by existing tests
- [x] added new unit test(s)
- [ ] added new functional test(s)
…onent root (#8595)

# What changed?
- Only add the Workflow root CHASM component if no root component
already exists.
- I think the overall feature should probably also be behind a feature
flag.

## Why?
- CHASM Scheduler functional tests are broken without this fix
(scheduler mutable states 'become' chasmworkflows)
…8638)

## What changed?
Changed the condition to check whether the root component of the chasm
tree has been initialized for new workflows

## Why?
The root component is never actually empty since we are using
`NewEmptyTree` which sets a root component with no type

## How did you test it?
- [x] built
- [ ] run locally and tested manually
- [ ] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)
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.

4 participants