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

Package build fails if WHO API is down #118

Closed
zkabat opened this issue Sep 1, 2016 · 3 comments
Closed

Package build fails if WHO API is down #118

zkabat opened this issue Sep 1, 2016 · 3 comments
Milestone

Comments

@zkabat
Copy link
Contributor

zkabat commented Sep 1, 2016

The example in heterogeneity.Rmd needs get_who_mr() function to generate results. If WHO API is down, the build fails with an error "No data returned." It takes a while to find reason for the failure so I have two suggestions:

  • Generate more informative error message if it is not possible to get data from WHO API
  • Get some mortality table offline to the package so that the API downtime does not affect the package development
@pierucci
Copy link
Owner

pierucci commented Sep 2, 2016

Yeah this API problem is starting to be an issue. I also got an email from CRAN yesterday asking me about this.

The error message could indeed be more specific, I'll do that in the rgho package.

For the API problem we can do the following things:

  • Do nothing and hope WHO fixes the issue. This approach is only OK if 1)GHO uptime is great, 2)WHO is reactive to fix issues, and 3)we can communicate with WHO IT in case there is a problem. Given that 1)this is not the first time their server fails, 2) the server has been down for more than 48h now and 3)WHO GHO team never answered any of my emails in the last months, I don't think this is a great idea.
  • Modify the vignettes and the tests so they do not fail if the GHO server is down. I don't like this idea because it just hides the problem. The fact is that when the server is down the functionnality is broken for the users, so we need to find a solution because it makes the package unusable.
  • Cache GHO mortality data. We can do that using package supplementary data that we would download from the GHO server, or by running a mirror server. While this would solve the problem, this raises questions about how to keep the data up to date, and also about engaging our responsability. And also legal questions about use of their data maybe?

So I think we're going toward caching data, but we need the think more about the consequences.

For the current episode of failing tests I still hope WHO will do something about it today...

@pierucci
Copy link
Owner

pierucci commented Sep 2, 2016

Seems to be fixed now...

https://travis-ci.org/pierucci/heemod

@pierucci
Copy link
Owner

pierucci commented Sep 4, 2016

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

No branches or pull requests

2 participants