-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[chore] Small fixes #15230
[chore] Small fixes #15230
Conversation
- Ensure we start the handler - Ensure fetch message ID is < 128
@@ -294,7 +294,6 @@ func (c *Compute) createFetcher() func(ctx context.Context, req *wasmpb.FetchReq | |||
) | |||
|
|||
messageID := strings.Join([]string{ | |||
req.Metadata.WorkflowId, | |||
req.Metadata.WorkflowExecutionId, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Context: the workflow execution ID is already unique and the message ID maximum is 128, so we were exceeding it.
I see you updated files related to
|
AER Report: CI Core ran successfully ✅AER Report: Operator UI CI ran successfully ✅ |
86c5cb0
* [chore] Small fixes - Ensure we start the handler - Ensure fetch message ID is < 128 * Fix tests
Requires
Supports