diff options
| author | JP Ungaretti <19893438+jungaretti@users.noreply.github.com> | 2023-01-24 02:49:17 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-01-24 11:49:17 +0100 |
| commit | 4362da7c5e81ed1c96663381ffe8d552d226ef14 (patch) | |
| tree | 2318a46067329768b16e8be4d98d25a2590b9903 /numpy/array_api/_array_object.py | |
| parent | 04823c1a95e23c55432a78c7c7414c040279c2e1 (diff) | |
| download | numpy-4362da7c5e81ed1c96663381ffe8d552d226ef14.tar.gz | |
DEV: Fix shell configuration in devcontainer (#23076)
This PR moves our repo setup to onCreateCommand from postCreateCommand in order to resolve a race condition between conda init and the default shell in VS Code. You can test this new devcontainer.json by creating a codespace for my fork/branch: https://github.com/codespaces/new?hide_repo_select=true&ref=jungaretti%2Fupdate-devcontainer&repo=576410652
postCreateCommand doesn't block interaction with your codespace. You can use other terminals and move around editors while it runs. On the other hand, onCreateCommand runs before you interact with your codespace. You won't be able to open a terminal until it finishes. onCreateCommand is a better choice for running our setup script because we need to run conda init before using the terminal.
Diffstat (limited to 'numpy/array_api/_array_object.py')
0 files changed, 0 insertions, 0 deletions