You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was setting up a dev environment and ran into some issues by following the directions (trying to, anyways). I'm open to have missed/misread something, though.
Here's what I ran into with 30 minutes of at-least-sorta-trying:
"To run tests that do not require a backend: pytest -m core" raises "no module found pyarrow.tests" (22053 deselected, 1 error in 9.12s) (probably due to my choice of conda-lock/?)
same issue as above after just download-data → pytest -m sqlite
pyarrow is installed, so that's not it(?)
just up postgres does not work (docker not found; output below)
just up postgres
docker compose up --wait postgres
sh: 1: docker: not found
error: Recipe `up` failed on line 94 with exit code 127
Tasks
I think this is all of them so far:
update conda install --file command (probably mamba as well)
confirm just is installed correctly with the previous command or provide directions to install it correctly
confirm just docs-preview is the correct command to preview docs
confirm that the pyarrow.tests module error when running core, sqlite, postgres (and possibly others) tests for the first time on a fresh environment after following the environment setup guide does not occur (guide addresses potential user error, tests do not rely on pyarrow, etc; dev's choice)
either confirm that docker and other deps are installed during the environment setup or note docker and/or other deps should be installed by the user before running just up <backend> (a small blurb about how to do that effectively without permanently infecting your computer with docker would be helpful but not required)
There's probably more, but this is what I ran into this morning. Let me know if you need anything else. Thanks!
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
I think some docs-related packages also may not be there in the Conda environment files (I think @chloeh13q ran into pydantic not being there the other day). Seems we need to make sure these are up-to-date.
conda/ no longer exists (used conda install --file conda-lock/linux-64-3.11.lock, not sure if I was supposed to do that)
conda/ is there, but maybe, if you were thinking about conda-lock, it was removed in 9.0 (see #8242).
just up postgres does not work (docker not found; output below)
Please describe the issue
I was setting up a dev environment and ran into some issues by following the directions (trying to, anyways). I'm open to have missed/misread something, though.
Here's what I ran into with 30 minutes of at-least-sorta-trying:
Setting up an environment
source: https://ibis-project.org/contribute/01_environment
conda/
no longer exists (usedconda install --file conda-lock/linux-64-3.11.lock
, not sure if I was supposed to do that)just
not installed through conda method (needed toconda install just
)just docs-preview
did not work (probably missing from conda-lock) (output below)just docs-preview output:
Contribute to the Ibis codebase
source: https://ibis-project.org/contribute/02_workflow
pytest -m core
" raises "no module found pyarrow.tests" (22053 deselected, 1 error in 9.12s
) (probably due to my choice of conda-lock/?)just download-data
→ pytest -m sqlitejust up postgres
does not work (docker not found; output below)Tasks
I think this is all of them so far:
conda install --file
command (probablymamba
as well)just
is installed correctly with the previous command or provide directions to install it correctlyjust docs-preview
is the correct command to preview docspyarrow.tests
module error when running core, sqlite, postgres (and possibly others) tests for the first time on a fresh environment after following the environment setup guide does not occur (guide addresses potential user error, tests do not rely on pyarrow, etc; dev's choice)just up <backend>
(a small blurb about how to do that effectively without permanently infecting your computer with docker would be helpful but not required)There's probably more, but this is what I ran into this morning. Let me know if you need anything else. Thanks!
Code of Conduct
The text was updated successfully, but these errors were encountered: