Rémi Thériault
Rémi Thériault
Alright, this is a much simplified version which now also support "by". So this is what I have so far: ``` r library(datawizard) describe_missing(airquality, select = "Ozone:Temp") #> variable n_missing...
The `check-test-warnings` workflow is failing because `test-report.brmsfit` generates a warning, > Global state has changed
It seems this issue arises simply from calling the `brms::brms()` function. Just running the test with: ```r model
Since there were no reactions to my post for two months, I have opened a new issue on Stan Discourse: https://discourse.mc-stan.org/t/global-state-has-changed-warning/36591
Here's the response of Bob Carpenter, one of the core Stan developers, on Stan Discourse: > I looked up this error and it seems to arise when a test from...
> Let's see if there is any upstream change that takes care of this. If not, we need to think about an alternative strategy to figure out that our code...
ACTUALLY, we just found the source of the issue on stan. It is due of our use of `testthat::set_state_inspector()` in file `tests/testthat/helper-state.R`. Do we need this?
@IndrajeetPatil how exactly do I "restrict" this check to easystats packages in file `tests/testthat/helper-state.R`? My naive intuition would be to just comment this whole file to stop the warning... but...
I'm thinking replacing `packages = .packages(all.available = TRUE)` with `packages = easystats::easystats_packages()`
Ok thanks. Note: the warning persists even when only mentioning the `easystats` packages.