Closed mgirlich closed 1 year ago
We see
checking tests ...
Running ‘testthat.R’ ERROR Running the tests in ‘tests/testthat.R’ failed. Last 13 lines of output: 5. └─base::lapply(...) 6. └─bcdata (local) FUN(X[[i]], ...) 7. ├─rlang::new_quosure(...) 8. └─dbplyr::partial_eval(x, data = dbplyr::lazy_frame()) 9. └─dbplyr::partial_eval(get_expr(call), data, get_env(call), error_call = error_call) 10. └─dbplyr:::partial_eval_call(call, data, env) 11. └─base::lapply(call[-1], partial_eval, data = data, env = env) 12. └─dbplyr (local) FUN(X[[i]], ...) 13. └─dbplyr:::partial_eval_sym(call, data, env) 14. └─cli::cli_abort("Object {.var {name}} not found.", call = NULL) 15. └─rlang::abort(message, ..., call = call, use_cli_format = TRUE) [ FAIL 3 | WARN 0 | SKIP 101 | PASS 63 ] Error: Test failures Execution halted
The problems comes from this change in dbplyr
Variables that are neither found in the data nor in the environment now produce an error (@mgirlich, #907).
We plan to release dbplyr soon so it would be great if you could fix this issue.
Thanks @mgirlich - do you have a planned release date?
Closed by #305
We see
checking tests ...
The problems comes from this change in dbplyr
We plan to release dbplyr soon so it would be great if you could fix this issue.