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

change syscall.Exec for command.Run to avoid a complete replacement of the current Go process with another #322

Merged
merged 1 commit into from
Oct 24, 2022

Conversation

fabricematrat
Copy link
Contributor

What was changed

change syscall.Exec for command.Run to avoid a complete replacement of the current Go process with another for external plugin execution.

Fixes #321

Why?

If I register a headers provider plugin, this plugin will be spawn and started. Then I execute an external plugin, the current code will replace the current Go process with another by calling syscall.Exec. The side effect is that the app.After will never be called and the header provide plugin will stay and will not be stopped

Checklist

  1. Closes
    [Bug] Running external plugin will leave processes started like header provider plugin running #321

  2. How was this tested

export TEMPORAL_CLI_PLUGIN_HEADERS_PROVIDER=tctl-authorization
tctl yo
check that tctl-authorization is not running anymore

  1. Any docs updates needed

@CLAassistant
Copy link

CLAassistant commented Oct 18, 2022

CLA assistant check
All committers have signed the CLA.

@feedmeapples feedmeapples merged commit 198fc05 into temporalio:main Oct 24, 2022
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.

[Bug] Running external plugin will leave processes started like header provider plugin running
3 participants