Skip to content
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

[CAPPL-320] hex decode workflowName when logged via beholder #15815

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

agparadiso
Copy link
Contributor

@agparadiso agparadiso commented Dec 30, 2024

Description

This pr introduces a fix to hex decode the workflow name whenever we log it via beholder
CAPPL-320

Requires

Supports

@agparadiso agparadiso marked this pull request as ready for review December 30, 2024 14:26
@agparadiso agparadiso requested review from a team as code owners December 30, 2024 14:26
@agparadiso agparadiso changed the title fix: hex decode workflowName when logged via beholder [CAPPL-320] hex decode workflowName when logged via beholder Dec 30, 2024
Copy link
Contributor

github-actions bot commented Dec 30, 2024

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

@agparadiso agparadiso force-pushed the CAPPL-320_decode_workflow_name branch from eb46205 to 1f831d9 Compare December 30, 2024 16:03
@@ -298,9 +299,19 @@ func (c *Compute) createFetcher() func(ctx context.Context, req *wasmpb.FetchReq
return nil, fmt.Errorf("workflow execution ID %q is invalid: %w", req.Metadata.WorkflowExecutionId, err)
}

// best effort to decode the workflow name
Copy link
Collaborator

Choose a reason for hiding this comment

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

is there a reason why this repeated code is not put in a single place? no obvious place for it to go?

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