Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unpin XGBoost Version upon XGBoost package update
See original GitHub issueNow that the XGBoost versioning issue has been merged, they will be updating the pip package to version 1.3.0.post0. This issue tracks removing our XGBoost version limitations once the new package is released.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
1.4.0 Release Candidate · Issue #6793 · dmlc/xgboost - GitHub
We are about to release version 1.4.0 of XGBoost. In the next two weeks, we invite everyone to try out the release candidate...
Read more >Installation Guide — xgboost 1.7.2 documentation
Installation Guide . XGBoost provides binary packages for some language bindings. The binary packages support the GPU algorithm ( gpu_hist ) on...
Read more >Installation Guide — xgboost 0.90 documentation
This page gives instructions on how to build and install XGBoost from scratch on ... GPU support works with the Python package as...
Read more >Building From Source — xgboost 1.7.2 documentation
This page gives instructions on how to build and install XGBoost from the source code on ... Some distros package a compatible gcc...
Read more >Installation Guide — xgboost 0.72.1 documentation
See Installing R package with GPU support for special instructions for R. An up-to-date version of the CUDA toolkit is required. From the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@bchen1116 1.3.1 is released, should we uncap for this?
@chukarsten @dsherry
I found this: https://discuss.xgboost.ai/t/n-jobs-1-no-longer-uses-all-cores/1955/2 while looking into XGBoost that indicates it might be a good idea to try to unpin XGBoost (since the version we have, 1.2.1, falls within the package versions that seem to be suffering from this) if we can.