Skip to content

Evaluator uses deprecated dask options #642

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

Open
lilyminium opened this issue Mar 27, 2025 · 0 comments · May be fixed by #657
Open

Evaluator uses deprecated dask options #642

lilyminium opened this issue Mar 27, 2025 · 0 comments · May be fixed by #657

Comments

@lilyminium
Copy link
Contributor

lilyminium commented Mar 27, 2025

We're using deprecated dask options which will eventually get removed:

/data/homezvol3/lilyw7/miniforge3/envs/evaluator-test-env-openff/lib/python3.11/site-packages/dask_jobqueue/core.py:266: FutureWarning: job_extra has been renamed to job_extra_directives. You are still using it (even if only set to []; please also check config files). If you did not set job_extra_directives yet, job_extra will be respected for now, but it will be removed in a future release. If you already set job_extra_directives, job_extra is ignored and you can remove it.
warnings.warn(warn, FutureWarning)
/data/homezvol3/lilyw7/miniforge3/envs/evaluator-test-env-openff/lib/python3.11/site-packages/dask_jobqueue/core.py:285: FutureWarning: env_extra has been renamed to job_script_prologue. You are still using it (even if only set to []; please also check config files). If you did not set job_script_prologue yet, env_extra will be respected for now, but it will be removed in a future release. If you already set job_script_prologue, env_extra is ignored and you can remove it.
warnings.warn(warn, FutureWarning)
/data/homezvol3/lilyw7/miniforge3/envs/evaluator-test-env-openff/lib/python3.11/site-packages/dask_jobqueue/slurm.py:55: FutureWarning: project has been renamed to account as this kwarg was used wit -A option. You are still using it (please also check config files). If you did not set account yet, project will be respected for now, but it will be removed in a future release. If you already set account, project is ignored and you can remove it.
warnings.warn(warn, FutureWarning)

@mattwthompson mattwthompson linked a pull request Apr 23, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant