-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Update LightGBM to 4.5.0 #7320
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
Comments
@boneatjp LightGBM 4.5.0 will be supported, they just made some breaking changes we haven't fixed on our end yet. I'll leave this issue open, but change it to reflect that we will be updating to 4.5.0 this release. |
Since there is a known vulnerability in LightGBM <= 4.5.0 (see microsoft/LightGBM#6750), it would be good if the reference is updated to 4.6.0, which fixes the problem. We also tried updating LightGBM to version 4.6.0 manually, but ran into access violations when using it with the .net wrapper. As the Severity of this vulnerability is flagged as high, that might put some additional priority on the matter. |
Thanks for checking. I've tried with LightGBM 4.6.0. It won't change a bit. Hope things go better in the future. |
Thanks for taking care of this! Is there any estimation on when this fix will be released? Will it be backported to 4.0.x or only be available for the 5.0. version of ML.NET? |
System Information (please complete the following information):
Describe the bug
Since ML.NET 4.0 uses LightGBM 3.3.5, I install LightGBM v4.5.0 by NuGet, but still having a problem with that version.
To Reproduce
Steps to reproduce the behavior:
It has been a problem using LightGBM v4.5.0 with ML.NET. Releasing v4.0, I hoped to go better with LightGBM v4.5.0, well, no progress has been done, I guess. Is this something that you don't care about? Well, I think I've already reported this problem but not getting any efort.
I wish someone check this problem and if those of you working on ML.NET sticks with LightGBM v3.3.5 explane why LihgtGBM v4.5.0 won't be supported with the latest version of ML.NET.
The text was updated successfully, but these errors were encountered: