You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure how exactly data frames work, but it seems that it expects a production flag and throws an error is there's no such flag available. The flag is optional in the API, so it seems to be a bug in the R client.
Edit: Feedback from the user indicates that the issue may also exist for tibbles.
The text was updated successfully, but these errors were encountered:
m-mohr
changed the title
Can't connect if tibble is not installed and server doesn't add production flag to well-known discovery
Can't connect if server doesn't add production flag to well-known discovery (and tibble is not installed?)
Dec 21, 2020
I stumbled onto similar issues sometimes on other occassions. It seems that sometimes the JSON message is parsed incorrect, e.g. I expect it parsed as data.frame object and it is parsed as a list. But to check this hypothesis, I would need the JSON hat is to be returned at GET /.well-known/openeo, can you provide it?
I recently was made aware of an issue with the R client:
I was able to track it down that the difference is:
production
flag inGET /.well-known/openeo
So I think the issue is in or around this line:
openeo-r-client/R/coerce-functions.R
Line 132 in fccbe70
I'm not sure how exactly data frames work, but it seems that it expects a
production
flag and throws an error is there's no such flag available. The flag is optional in the API, so it seems to be a bug in the R client.Edit: Feedback from the user indicates that the issue may also exist for tibbles.
The text was updated successfully, but these errors were encountered: