Bump custodian from 2024.6.24 to 2024.10.16

[dependabot]

Bumps custodian from 2024.6.24 to 2024.10.16.

Release notes

Sourced from custodian's releases.

v2024.10.16

See changes at https://materialsproject.github.io/custodian

v2024.10.15

See changes at https://materialsproject.github.io/custodian

v2024.10.14

See changes at https://materialsproject.github.io/custodian

Changelog

Sourced from custodian's changelog.

2024.10.16

• Add a update_incar option in VaspJob which updates parameters from a previous vasprun.xml.

2024.10.15

• Bug fix for pip installation.

2024.10.14

• PR #342 from @​esoteric-ephemera (#342) Minor update to the logic of the auto_nbands check for VaspErrorHandler. This check sees if the number of bands has been updated by VASP, and currently it only checks to see if that updated number is very large. However, there are cases where the user specifies an NBANDS that is incompatible with their parallelization settings, as NBANDS must be divisible by $(\mathrm{ranks}) / (\mathrm{KPAR} \times \mathrm{NCORE})$. In these cases, VASP increases the number of bands to ensure the calculation can still proceed. This can happen in MP's band structure workflows with uniform $k$-point densities. However, since the current auto_nbands handler applies no corrections to the job, these otherwise successful runs are killed. This PR adds logic to ensure that the calculation is rerun with a higher number of bands appropriate to the parallelization setting. This is kinda redundant, since VASP already does this. But I think it has to occur this way because VaspErrorHandler is monitoring the job and flags it for an auto_nbands error. Another implementation concern: it's generally safer to decrease the number of bands since this requires a lower energy cutoff to converge each band. It might be safer to decrease NBANDS as a fix

Commits

• ec043b1 Update dev docs
• 24c14a4 Update changelog.
• c4357d3 Add a update_incar option for VaspJob. Allows for updating of incar
• 649c402 Update dev docs
• 669a09a Update changelog.
• d0e1660 Fix installation (#351)
• 2af34f4 Fix ruff.
• 8cbd590 Update dev docs
• e286d16 Update changelog.
• db7ec55 Drop py39 support.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)