Nested runs of `ie` utilize the same environment state file
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- bash, go, markdown
- Domain
- cli, testing-qa
Research direction
Trace how ie creates, writes, and restores the temporary environment state file during command execution, then reproduce the issue with the three-step markdown scenario shown. Done means a nested ie invocation no longer destroys the outer run's state and the final echo still sees VAR=foo.
Written by the indexing model from the issue text.
Description
To keep track of environment variables created by executing commands, we save them into a temporary file named /tmp/env-var after the execution of each command so that we can restore the environment variables during the execution of the next command. This means that if ie were to execute a doc that has a codeblock which calls ie, the state file will be overwritten from the nested invocation of ie which can break steps that come after invoking ie in a scenario.
This can be replicated with a markdown file scenario that has these 3 steps:
export VAR=foo
ie <any-execution-command> <scenario>
echo $VAR # Should break because the previous command deletes the environment state.
This isn't a critical issue for most scenarios, but it will prevent us from having our specs execute correctly because they rely on invoking ie to showcase new features.
- Dominant language
- Go
- Stars
- 40
- Forks
- 27
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/InnovationEngine
-
Azure/InnovationEngine#262 · 1 reaction · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/InnovationEngine#259 ·
-
bug enhancement
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Azure/InnovationEngine#258 ·
-
enhancement innovation engine
Azure/InnovationEngine#256 · 1 reaction · 1 assignee ·
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
Azure/InnovationEngine#252 · 1 comment ·
All issues in Azure/InnovationEngine
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100