Post Run action inputs become null

[kevinchen-pimq]

Describe the bug

Post Run action inputs become null.

Happen when workflow file looks like this.

workflow --call--> action --call--> action

To Reproduce Steps to reproduce the behavior:

1. fork https://github.com/kevinchen-pimq/action-input-poc
2. Run POC workflow

Expected behavior

Inputs value should not be null.

Runner Version and Platform

Version of your runner?

2.308.0

OS of the machine running the runner? OSX/Windows/Linux/...

  Ubuntu
  20.04.6
  LTS

What's not working?

Please include error messages and screenshots. workflow run: https://github.com/kevinchen-pimq/action-input-poc/actions/runs/5973798158

Case 1: workflow --call--> action test-post-run-input Post run is as expected.

Case 2: workflow --call--> action extra-step --call--> action test-post-run-input Post run test-post-run-input inputs become null.

Job Log Output

If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.

https://github.com/kevinchen-pimq/action-input-poc/actions/runs/5973798158

Runner and Worker's Diagnostic Logs

If applicable, add relevant diagnostic log information. Logs are located in the runner's _diag folder. The runner logs are prefixed with Runner_ and the worker logs are prefixed with Worker_. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.

[kevinchen-pimq]

related #2009

[jenseng]

A related problem (I think) is that an outer input of the same name can bleed into / overwrite an inner one during the post phase. I've run into a problem when using nested local actions with actions/cache where my actions have a path input. The outer path ends up clobbering the actions/cache one during its post phase, so it uses the wrong value when it tars up and caches things. Because the path is different, the cache entry gets a different version and contents, so it can't actually be used by later jobs.

E.g. this simplified example demonstrates the problem here

[github-actions[bot]]

This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 15 days.

[jenseng]

This bug is still present

[iampat]

ping!