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

dp_make error with conflicted v1.2.0 (but not v1.1.0) #31

Open
leslem opened this issue Apr 6, 2023 · 1 comment
Open

dp_make error with conflicted v1.2.0 (but not v1.1.0) #31

leslem opened this issue Apr 6, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@leslem
Copy link
Collaborator

leslem commented Apr 6, 2023

I'm using the dp_make.R template provided by dpcode_add. I have a very minimal version of dp_make.R so far. You can view it at <our BMS GitHub instance URL>/emeryl1/dp_bb2121mm003/blob/main/dp_make.R (but note that I had to add a comma at the end of line 38, which I haven't pushed to origin yet). When I first tried to source dp_make.R according to the dp_journal workflow, it failed with this error at the first conflict_prefer call:

> source("./dp_make.R")

Attaching package: ‘lubridate’

The following objects are masked from ‘package:base’:

    date, intersect, setdiff, union

[conflicted] Will prefer dplyr::filter over any other package.
Error: 'verbose' is not an exported object from 'namespace:R.utils'

Something in conflicted is disagreeing with something in daapr, because running any conflict_prefer call fails with the same error when I've sourced enough parts of my dp_journal. I noticed that conflicted has a very recent new version, so I tried downgrading to the previous version (renv::install("[email protected]")) and now I can source dp_make.R without the error.

I haven't tracked down the specific cause of the error, but it needs further investigation and I recommend sticking to conflicted v1.1.0 for now.

@camorosi camorosi added this to daapr Apr 14, 2023
@camorosi camorosi moved this to Backlog in daapr Apr 14, 2023
@camorosi camorosi added the bug Something isn't working label Aug 1, 2024
@camorosi
Copy link
Collaborator

camorosi commented Aug 1, 2024

Adding that this is still an issue. Also reported here: r-lib/conflicted#105 but removing the library(R.utils) call didn't fix, so sticking to downgrading for now. Edit to add: seems to be an issue with drake but not targets, but this requires additional investigation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Backlog
Development

No branches or pull requests

2 participants