Fixes env vars in languages other than Python

[mishushakov]

Changelog:

• closes Environment Variables are not Accessible when running R code in sandbox E2B#665
• runs a code cell to set env variables if any env variables are set (either sandbox-level or per cell)
• note: os.environ.set_envs_for_execution function might no longer be required?

Example:

import { Sandbox } from "@e2b/code-interpreter";

const sbx = await Sandbox.create({ debug: true });

const code = await sbx.runCode(`console.log(process.env.TEST);`, {
  language: "javascript",
  envs: { TEST: "hello" },
});

console.log(code.logs);

Before:

{
  stdout: [ "undefined\n" ],
  stderr: [],
}

After:

{
  stdout: [ "hello\n" ],
  stderr: [],
}

[linear]

E2B-1977 Environment Variables are not Accessible when running R code in sandbox

[mishushakov]

os.environ.set_envs_for_execution function might no longer be required?

[jakubno]

Well, it tries to solve a more general issue. If you only set envs then you have a problem with changing a variable during a runtime, which is also a global variable.

Try this code, if it works (it's from test, which was for some reason commented out)

sbx = await AsyncSandbox.create(envs={"FOO": "bar", "SBX": "value"})

await sbx.run_code(
    "import os; os.environ['FOO'] = 'bar'; os.environ['RUNTIME_ENV'] = 'async_python_runtime'"
)
result = await sbx.run_code("import os; os.getenv('FOO')", envs={"FOO": "baz"})
assert result.text == "baz"

# This can fail if running in debug mode (there's a race condition with the restart kernel test)
result = await sbx.run_code("import os; os.getenv('RUNTIME_ENV')")
assert result.text == "async_python_runtime"

result = await sbx.run_code("import os; os.getenv('SBX')")
assert result.text == "value"

result = await sbx.run_code("import os; os.getenv('FOO')")
assert result.text == "bar"

[mishushakov]

I think the current limitation will be that any env variable that you pass through envs will either be removed or reset to global value, this is breaking current implementation, but i think more of an edge-case

[mishushakov]

Basically, this

await sbx.run_code("import os; os.environ['FOO'] = 'bar'")

# Will be bar
await sbx.run_code("import os; os.getenv('FOO')")

# Will be baz
await sbx.run_code("import os; os.getenv('FOO')", envs={"FOO": "baz"})

# Will be "None" or the value set in Sandbox.create
# Alternatively, I can make it keep the value from previous step
await sbx.run_code("import os; os.getenv('FOO')")

[mlejva]

@mishushakov can you add tests for this case? it would be good to catch if setting env var breaks

[mishushakov]

yes, these will be in a separate PR as otherwise we would be unable to merge this (the CI is using deployed template version)