-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
[skip vbump] upversion to 0.4.0 #300
Conversation
Unit Tests Summary 1 files 19 suites 28s ⏱️ Results for commit 371f13f. ♻️ This comment has been updated with latest results. |
I removed |
Got a NOTE when checking against R-oldrelease:
But no NOTES in R-release and R-devel: I think we're good to go. |
Submitted to CRAN. Awaiting Feedback. |
Got automated feedback not passing under Debian:
|
I see @insightsengineering/nest-core-dev what do you think? |
I found this same problem on #299 , I explored it a bit and I think it is a problem with roxygen @examplesIf, see also #248. I don't think changing datasets will reduce computing time. We might be able to reduce (more)time if instead of having each method create a new card and reporter we reused one. It might be harder to follow individual methods examples but it will probably make the examples faster. |
It turns out, we have the same message in our r-hub action as well in the main branch (Debian == gcc12): After investigation, I decided to just remove the second The pipeline is now completed without NOTE: What I did was:
|
It would be the best to use profiler tools to identify performance bottlenecks. I think that you are guessing here.
Currently the main performance bottleneck is converting rtables to flextable (which is btw happening outside of this package). Hance I would rather remove / shorten rtables related example. |
I'd have to check, but it could be because of the output render formats. flextable renders in all the formats easily, I'm not sure about rtables. |
data.frame needs to be converted to display it in the document. There are several design pitfalls, the most serious:
|
Yeah that's exactly it. Probably not worth to postpone the release because of that but I think it's important. Also posting this just to show you how to handle "examples takes too long" type of problems. |
It is not justv about TableBlock. Plots for example are saved into file during PictureBlock initialization. I'm not a fan to do these changes now as we already know that the whole package needs to be revisited. |
Thanks @pawelru! Your advise will come in handy moving forward if we run into this type of issue again when submitting to CRAN. Also, as you mentioned, refactoring the examples is not worth to postpone the release, especially we're thinking about refactoring teal.reporter with this issue I will move forward with the release. |
Submitted. Awaiting CRAN feedback. |
Related to #296