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

wf_request problem #49

Closed
vegvarizs opened this issue Dec 20, 2019 · 15 comments · Fixed by #52
Closed

wf_request problem #49

vegvarizs opened this issue Dec 20, 2019 · 15 comments · Fixed by #52

Comments

@vegvarizs
Copy link

Hi,
after successfully completing the wf_set_key command using my uid as user identity, the wf_request command terminates with an error message (using a sample request list) :
Error in FUN(X[[i]], ...) : argument is missing, with no default
Calls: sourceWithProgress ... eval -> eval -> wf_request -> which -> vapply -> FUN
In addition: Warning messages:
1: In default_backend_auto() :
Selecting ‘env’ backend. Secrets are stored in environment variables
2: In default_backend_auto() :
Selecting ‘env’ backend. Secrets are stored in environment variables
3: In default_backend_auto() :
Selecting ‘env’ backend. Secrets are stored in environment variables
4: In default_backend_auto() :
Selecting ‘env’ backend. Secrets are stored in environment variables
Execution halted

What can be the problem?

Bests,
Zsolt

@eliocamp
Copy link
Collaborator

@vegvarizs, There's a small but in the current version when your system doesn't support keyrings. See here: #46
You can try installing [this](https://github.com/khufkens/ecmwfr/pull/47] pull request version with

remotes::install_github("khufkens/ecmwfr", ref = remotes::github_pull(47))

@vegvarizs
Copy link
Author

Thanks, I have installed it, but the same problem prevails. The libsodium is also installed on my Ubuntu. Still experiencing.

@khufkens
Copy link
Member

Have you used keyring package in another context so the environmental variables are mixed up?

@vegvarizs
Copy link
Author

Yes! Should I remove it and reinstall ecmwfr?

@khufkens
Copy link
Member

Just try, but be sure to reinstall keyring as well.

@vegvarizs
Copy link
Author

Done: the warning messages about the backend environment disappeared, but the message:

Error in FUN(X[[i]], ...) : argument is missing, with no default
Calls: sourceWithProgress ... eval -> eval -> wf_request -> which -> vapply -> FUN
Execution halted

is still there.
I am using this request:
wf_request(request = request, user = uid, transfer = TRUE, job_name = "vzs.test", path = ".")

@khufkens
Copy link
Member

Drop the . from the job name and use an explicit path name. Then try again. I don't think this is an authentication error.

@vegvarizs
Copy link
Author

vegvarizs commented Dec 26, 2019 via email

@khufkens
Copy link
Member

Could you run the example code as listed in the documents for me and provide all the code as you run it. (see https://khufkens.github.io/ecmwfr/articles/cds_vignette.html)

Also provide the system you use both in terms of software and hardware. With just a vague error message and no knowledge of what you run I can't do much but guess toward the problem.

# Specify the data set
request <- list("dataset"        = "reanalysis-era5-pressure-levels",
                "product_type"   = "reanalysis",
                "variable"       = "temperature",
                "pressure_level" = "850",
                "year"           = "2000",
                "month"          = "04",
                "day"            = "04",
                "time"           = "00:00",
                "area"           = "70/-20/30/60",
                "format"         = "netcdf",
                "target"         = "era5-demo.nc")

# Start downloading the data, the path of the file
# will be returned as a variable (ncfile)
ncfile <- wf_request(user = "2088", # <-- your USER ID HERE
                      request = request,   
                      transfer = TRUE,  
                      path = "~",
                      verbose = FALSE)

@vegvarizs
Copy link
Author

vegvarizs commented Jan 2, 2020 via email

@khufkens
Copy link
Member

khufkens commented Jan 2, 2020

You run a rather old version of R, lots changed between 3.4 and 3.6.

I would upgrade and try again. This seems like a likely cause as my unit tests (using the code above) come out clean on 3.6. Previously they ran on 3.4 but since a little while it is 3.6 by default.

@vegvarizs
Copy link
Author

vegvarizs commented Jan 2, 2020 via email

@eliocamp
Copy link
Collaborator

eliocamp commented Jan 2, 2020

I installed R 3.4.4 and using the CRAN version of the package I didn't get any error. But I can reproduce using the development version. I'll look into it.

@eliocamp
Copy link
Collaborator

eliocamp commented Jan 2, 2020

There! It was a trailing comma in one function call. It seems that R 3.4.4 treats it as expecting another argument while R 3.6 doesn't.

@vegvarizs
Copy link
Author

vegvarizs commented Jan 2, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants