Files
tasks/chasm/test_task_test.go
Rodrigo ZhouandGitHub 48c8df4427 [CHASM] Set tree as dirty after executing pure task (#10405)
## What changed?
Set tree as dirty as executing pure task

## Why?
After executing an invalid pure task, the transaction needs to clean up
the tasks and possibly generate a new physical task for the next valid
pure task.

## 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)

## Potential risks
2026-05-28 15:42:35 -07:00

26 lines
565 B
Go

// TODO: move this to chasm_test package
package chasm
import (
commonpb "go.temporal.io/api/common/v1"
"google.golang.org/protobuf/proto"
"google.golang.org/protobuf/reflect/protoreflect"
)
type (
TestSideEffectTask = commonpb.Payload
TestDiscardableSideEffectTask struct{}
TestOutboundSideEffectTask struct{}
TestPureTask commonpb.Payload
)
// ProtoReflect implements [protoreflect.ProtoMessage].
func (t *TestPureTask) ProtoReflect() protoreflect.Message {
return (*commonpb.Payload)(t).ProtoReflect()
}
var _ proto.Message = (*TestPureTask)(nil)