Skip to content
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

Roxygen2 new version C stack usage issue with S4 methods #597

Closed
sylvainschmitt opened this issue Feb 21, 2017 · 3 comments
Closed

Roxygen2 new version C stack usage issue with S4 methods #597

sylvainschmitt opened this issue Feb 21, 2017 · 3 comments

Comments

@sylvainschmitt
Copy link

Hello,

For a week I've got issue to use Roxygen2 to write my package documentation with devtools::document function. Searching for an answer I tried to upload and document the last stable version off the package. And surprise documentation doesn't work anymore I got the same issue :

Error: C stack usage 7972080 is too close to the limit

So I checked and the only change is that I were using the 4.0.1 version on my last stable version of the package and now Roxygen2 is on 6.0.1 version. nevertheless when I install the old version I can't document my old stable version. When I use the traceback function it appears it is due to an infinite loop when trying to document code S4 method. Any idea for the reason, or maybe for a solution to get my documentation in waiting ?

@sylvainschmitt
Copy link
Author

After a lot of search it appears it is due to the import of spThin (>= 0.1.0) package in my DESCRIPTION file. I'll try to figure out what the issue with the SpThin package because I need the dependency and S4 methods documentation. But if you have any idea I'm interested..

PS : I tried reinstalling the package but it didn't change anything

@hadley
Copy link
Member

hadley commented Mar 7, 2017

Please provide a reproducible example. For this problem, that will be a minimal package that demonstrates the problem.

@sylvainschmitt
Copy link
Author

Thank you for looking at it. I tried to reproduce the error by creating a minimal package importing spThin package and using the thin function. And it didn't throw any error when documenting with devtools::document() . Whereas for my current package in development the issue is still here and disappear as soon as I remove spThin from Imports filed in DESCRIPTION file. So I need to search more deeply what's really creating the error in my current package in development. I come back to you as soon as I get it.

@hadley hadley closed this as completed Aug 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants