-
-
Notifications
You must be signed in to change notification settings - Fork 636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash with "Filesystem changed" #15310
Comments
Once this error happens, even reverting the dependency addition keeps the error happening afterwards. I did somehow reset this status in prior attempts but could not catch the exact reset condition yet. |
It looks like the issue is that you are running Pants with The
... having said that, it looks like the After that issue is resolved, you should get a useful stacktrace out, and can re-open this issue if it's not clear. |
Yeah, I'm now trying Python 3.9 as the pants runtime. |
And using Python 3.9, it reveals my human mistake on a typo in one of BUILD files with a kind error message. 👍🏼 😱 🙏🏼 |
The [`etype` argument to `format_exception`](https://docs.python.org/3/library/traceback.html#traceback.format_exception) has been ignored since Python `3.5`, and is removed in Python `3.10`. Fixes #15310. [ci skip-build-wheels]
Describe the bug
git clone https://github.com/lablup/backend.ai
cd backend.ai
git reset --hard be2e624fb6d989bc54daea839288f40ada9e8374
:dist
dependency to apex_binary()
target.Without it, pants works fine.
./pants-local
which runs pants from a separately cloned pants working copy.RUST_BACKTRACE=1 ./pants run src/ai/backend/cli:cli
The error message is repeated until the user interrupts with SIGINT (Ctrl+C).
Pants version
The master branch (ba9dc62) with a Linux aarch64 patch based on a comment of #12183.
Running pants from sources using
export PY=$(pyenv prefix 3.10.4)/bin/python
.OS
Ubuntu 20.04.4 LTS as UTM (v3.1.5) virtual machine on macOS 12.3.1 at Apple M1 Max.
Additional info
Might be related with #14466 but not sure.
The text was updated successfully, but these errors were encountered: