avoid os.Setenv calls in runServ, add env vars to gitcmd.Env instead #3772
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Using
os.Setenv()
is the middle of a running program is very unsafe, specially if some vars are set conditionally (their effect will remain until the program is running)I think the only reason we set these env vars is because of running the git command
gitcmd.Run()
.Please correct me if I'm wrong.
For the
gitcmd.Run()
, we just need to add vars togitcmd.Env
, without effecting the global env vars.EDIT: I realized this part of program does not stay running (and there is no concurrency) because it's compiled to a
serv
binary and runs for each operation.But it's still cleaner this way and a better practice in general.