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

Can't connect if server doesn't add production flag to well-known discovery (and tibble is not installed?) #59

Closed
m-mohr opened this issue Dec 21, 2020 · 5 comments
Labels
bug Something isn't working

Comments

@m-mohr
Copy link
Member

m-mohr commented Dec 21, 2020

I recently was made aware of an issue with the R client:

image

I was able to track it down that the difference is:

  1. the user had not installed tibble and
  2. the server did not had the production flag in GET /.well-known/openeo

So I think the issue is in or around this line:

return(table[c("api_version", "production", "url")])

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.

@m-mohr m-mohr added the bug Something isn't working label Dec 21, 2020
@m-mohr 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
@flahn
Copy link
Member

flahn commented Dec 22, 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?

@flahn
Copy link
Member

flahn commented Dec 22, 2020

e824f6f should fix this (referenced the wrong issue unfortunately)

@m-mohr
Copy link
Member Author

m-mohr commented Dec 22, 2020

I got this image:
image

So likely this in "text":

{
  "versions": [
    {
      "api_version": "1.0.0",
      "url": "http://localhost/api/v1"
    }
  ]
}

Would be great if you could check this, thank you!

@flahn
Copy link
Member

flahn commented Mar 5, 2021

@m-mohr is this issue still open or did the mentioned commit solve this?

@m-mohr
Copy link
Member Author

m-mohr commented Mar 5, 2021

Was an issue in a study project. I never tried it myself. Let's close for now, thanks.

@m-mohr m-mohr closed this as completed Mar 5, 2021
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
None yet
Development

No branches or pull requests

2 participants