-
Notifications
You must be signed in to change notification settings - Fork 1k
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
More Model Module Docs #2623
More Model Module Docs #2623
Conversation
There seems to be some clippy errors in the CI. Could you have a look? |
( yep. but AFK ) |
New error is in unintended eval of markdown block. will look into fix
|
To have text highlighting without execution you can use the following:
|
I'm removing the 2 offending text blocks for the moment. I can compile just fine locally and am not sure where the discrepancy lies between my machine and the CI system. Elide the issue for the moment. |
This error is unrelated to my PR. I believe it may have been introduced in #2618 error: failed to run custom build command for `pyo3-build-config v0.22.6`
Error: failed to run custom build command for `pyo3-build-config v0.22.6`
Caused by:
process didn't exit successfully: `D:\a\candle\candle\target\debug\build\pyo3-build-config-54d91561316d6713\build-script-build` (exit code: 1)
--- stdout
cargo:rerun-if-env-changed=PYO3_CONFIG_FILE
cargo:rerun-if-env-changed=PYO3_NO_PYTHON
cargo:rerun-if-env-changed=PYO3_ENVIRONMENT_SIGNATURE
cargo:rerun-if-env-changed=PYO3_PYTHON
cargo:rerun-if-env-changed=VIRTUAL_ENV
cargo:rerun-if-env-changed=CONDA_PREFIX
cargo:rerun-if-env-changed=PATH
--- stderr
error: cannot set a minimum Python version 3.11 higher than the interpreter version 3.9 (the minimum Python version is implied by the abi3-py311 feature)
warning: build failed, waiting for other jobs to finish... |
Bumped the gh-action ci to python 3.11/ |
from pyo3: https://github.com/PyO3/pyo3/blob/main/.github/workflows/ci.yml
|
|
As per Discord discussion, continuing to update the model docs.