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

"cadence workflow show" panic with cron workflow #5078

Open
rkumpf opened this issue Feb 7, 2023 · 0 comments
Open

"cadence workflow show" panic with cron workflow #5078

rkumpf opened this issue Feb 7, 2023 · 0 comments

Comments

@rkumpf
Copy link

rkumpf commented Feb 7, 2023

Version of Cadence server, and client(which language)

  • Server version: 0.25.0
  • Client version: 0.19.1
  • Client language: Go

Describe the bug
The cadence workflow show command gives panic: reflect.Value.Interface: cannot return value obtained from unexported field or method on a cron workflow that was terminated prior to its first scheduled run. The problem does not occur with server version 0.24.0.

To Reproduce
Is the issue reproducible?

  • Yes

Steps to reproduce the behavior:

  1. Start a cron workflow.
  2. Terminate the cron workflow before its first scheduled run.
  3. Use the CLI to show the workflow details:
cadence --address localhost:7933 --do my-domain workflow show --wid my-workflow-id --rid 69f34234-d8d6-4871-b18b-703bad74c8bc --of 69f34234-d8d6-4871-b18b-703bad74c8bc.json

The CLI result is:

panic: reflect.Value.Interface: cannot return value obtained from unexported field or method

Expected behavior
The workflow details should be successfully shown, as in this redacted output from an identical workflow using the 0.24.0 server:

  1  WorkflowExecutionStarted     {WorkflowType:{Name:Redacted}, TaskList:{Name:redacted}, Input:["redacted"],                                              
                                   ExecutionStartToCloseTimeoutSeconds:1800, TaskStartToCloseTimeoutSeconds:10, ContinuedFailureDetails:[],                         
                                   LastCompletionResult:[], OriginalExecutionRunID:69f34234-d8d6-4871-b18b-703bad74c8bc,                                            
                                   Identity:1@redacted@@3ba23188-828a-4e1b-a292-2f731f9150ec,                       
                                   FirstExecutionRunID:69f34234-d8d6-4871-b18b-703bad74c8bc, Attempt:0,                                                             
                                   CronSchedule:0 0 * * *, FirstDecisionTaskBackoffSeconds:86304,                                                                 
                                   Header:{...}}                                                 
  2  WorkflowExecutionTerminated  {Reason:Because, Details:[],                                                                           
                                   Identity:1@redacted@@3ba23188-828a-4e1b-a292-2f731f9150ec}                       

Additional context
The issue was detected through workflow replay automation. After running a set of tests, all workflow data is exported to check for compatibility in a later build. The export works correctly with server build 0.24.0 and fails with server build 0.25.0.

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

No branches or pull requests

1 participant