-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[R-package] Warnings of CRAN Package #6221
Comments
Thanks @shiyu1994 . I was worried about that 😭 This is exactly what I was asking about in #6212 (comment), and a fix for it (#6216) is already on 11 days is not a lot of time :/ And the current state of I really do not want to do another 3.3.x R-only patch release... they're a lot of effort and they confuse users. Here's my proposal:
What do you think? Also could we change the maintainer in |
I totally agree with the proposal. I think it is more important to keep the package available even somehow slower. |
@shiyu1994 I'm happy to say that I think I have a more permanent solution that could resolve the issues CRAN previously rejected the R package for (#5987). Put up a PR here: #6226. If we move forward with that approach in the next few days, I can submit try to submit a v4.2.0 of the R package to CRAN. If reviews take too long or if some significant issue is found, I'll put up another PR limiting the R package to 2 threads everywhere, so we can continue working on this without the time pressure of CRAN archival. |
The latest release of the R package has passed all checks: #6191 (comment) So I think this can safely be closed. Thanks @shiyu1994 for the help! |
I received an email from CRAN this reporting warnings of our CRAN package which are required to be fixed by Dec 12.
It seems that both warnings are from lightgbm_R.cpp
The text was updated successfully, but these errors were encountered: