-
Notifications
You must be signed in to change notification settings - Fork 38
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
Possible regression in new CRAN release? #114
Comments
I am trying to move the package to using the current version of libyaml in an unmodified state. The issue is introduced in change aedd27c. |
Thanks! glad it appears fixed! Can we inform CRAN there'll be a patched release for yaml sometime in the near future? |
I just submitted it. Your clear test case made short work of it. |
excellent, thanks for the quick turnaround!! |
Np. I'm surprised the test cases didn't catch this one. At least there's a new test. |
it happens. feel free to test against our suite as well in the future. it's in a weird gap in CRAN policies because we only Suggest yaml so there's no enforcement except when something like this happens. I think devtools will run against suggests in their revdep tooling, if you're using that |
The new version is up on CRAN. |
As reported in Rdatatable/data.table#5339
There's an apparent change of behavior that may be a bug. Not clear if working as intended and I don't see anything obviously related in the ChangeLog:
r-yaml/inst/CHANGELOG
Lines 1 to 26 in 969ee12
Note the new
...
. Note thata = 1
is not necessary to trigger the...
, but helps illustrate that the...
always comes at the end, regardless of other keys in the input.The text was updated successfully, but these errors were encountered: