-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Show only datasets used #1309
Show only datasets used #1309
Conversation
@llrs-roche R CMD CHECKs are failiing. Can you review? |
Triggering the tests again, as they were mainly dependency setup, then I'll try to fix them locally |
Unit Tests Summary 1 files 70 suites 1h 10m 16s ⏱️ Results for commit 0d62e91. ♻️ This comment has been updated with latest results. |
Stuff like that is visible in the dependency installation for documentation build ℹ Creating lockfile '.github/pkg.lock'
✖ Creating lockfile '.github/pkg.lock' [6.2s]
Error:
! error in pak subprocess
Caused by error:
! Could not solve package dependencies:
* deps::.: dependency conflict
* any::sessioninfo: dependency conflict
---
Backtrace:
1. pak::lockfile_create(c(deps, extra_deps), lockfile = ".github/pkg.lock", …
2. pak:::remote(function(...) { …
3. err$throw(res$error)
---
Subprocess backtrace:
1. base::withCallingHandlers(cli_message = function(msg) { …
2. get("lockfile_create_internal", asNamespace("pak"))(...)
3. prop$stop_for_solution_error()
4. private$plan$stop_for_solve_error()
5. pkgdepends:::pkgplan_stop_for_solve_error(self, private)
6. base::throw(new_error("Could not solve package dependencies:\n", msg, …
7. | base::signalCondition(cond)
8. global (function (e) …
Execution halted
Error: Process completed with exit code 1. |
I'll compare the Docs/ Pkgdown docs dependency problems with the check run, that could solve the dependencies: https://github.com/insightsengineering/teal.modules.clinical/actions/runs/12687811698/job/35577032936?pr=1309 |
Unit Test Performance DifferenceTest suite performance difference
Additional test case details
Results for commit 231d18d ♻️ This comment has been updated with latest results. |
The the initial lock files are identical. but on the Docs run when the DESCRIPTION file is modified I see:
teal.slice: main at |
@pawelru there seems to be a problem on the Docs/Pkgdown github actions. The action is failing when the required versions are available on the main branch of their repositories (and it continues beyond the specific Modify DESCRIPTION) |
This is quite strange I'm comparing the outcome of check and docs: check logs
docs logs
Note that the first two steps are identical. In the first step we do |
I have rerun this and it just works ¯_(ツ)_/¯. Don't ask me why https://github.com/insightsengineering/teal.modules.clinical/actions/runs/12687811632 |
@m7pr I removed the Rstudio changes on Rproj, but see the explanation about its implications and behavior. |
Pull Request
Fixes #1307
Only
tm_g_ci
andtm_g_barcart_simple
didn't have the datanames of the module configurable.I modified
tm_g_ci
andtm_g_barcart_simple
so that only the datasets used are displayed on the module.See the examples below where the
b
dataset is not shown on this PR.`tm_g_ci` example
`tm_g_barchart_simple` example
I don't think the documentation of these modules needs to be updated. (The only change on the documentation is to fix a typo)