Alex Eagle
Alex Eagle
https://github.com/aspect-build/rules_py/issues/303 seems related - I see you aren't using a `py_pytest_main` so I'm not sure if the workaround there is useful.
I happened to reproduce this today while working on the Python course and debugging for a client.
@garymm yes you're right, my change closing this issue is specific to pytest.
@fmeum I'm sure you have informed guidance on what's the correct approach here.
Fixed by #1053 - however that assumes that callers of the `extract` mode propagate the new `default_env` when spawning a `tar` action.
@walkerburgin sorry we dropped the thread here, could you summarize what the next steps should be, if any?
Also, if there's a doc-only change, it should reflect an identical edit to an example/ or e2e/ test code change, so we know it's load-bearing and functional. I'm closing PRs...
I'm not certain we should merge this; created it mostly as the alternative to discuss. Feels to me that we should have global guidance across the whole Bazel ecosystem about...
Yeah your Java example is like what I did with https://github.com/aspect-build/rules_js/pull/2044 - the hard thing for me is how hopeless the project of finding every action that needs an `env`...
thanks @plobsing - sorry for the churn