Open gagolews opened 6 years ago
Strangely enough, I got notified that some other CRAN team member couldn't replicate these errors on his system..
H Marek,
That does not look like a stringi error and may have been caused by someone running the example code while the google server was down? I sadly don’t have a Windows machine to test but my main use for stringi in that package was for string processing. I’ll try to reproduce the error today but it seems like your update should not affect the package. Thanks, derek
On Wed, Mar 14, 2018 at 6:00 AM Marek Gagolewski notifications@github.com wrote:
Strangely enough, I got notified that some other CRAN team member couldn't replicate these errors on his system..
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/DerekYves/placement/issues/6#issuecomment-372966012, or mute the thread https://github.com/notifications/unsubscribe-auth/APwNq-jMxWSZl2kLyVHNRvaAEAevRK5Mks5teOo0gaJpZM4Sm5-Z .
Hi!
I'm trying to push a newer stringi version to CRAN. It's available at:
Even though the changes between v1.1.6 and v1.1.7 are very cosmetic (mods to the C/C++ code -- removed #pragmas suppressing some warnings and changing the order of the parameters to some class constructor affecting the Windows-only build), I got a response from the CRAN team that your package errored during check:
Is the error likely to be on the stringi side?
Cheers!