-
Notifications
You must be signed in to change notification settings - Fork 97
Move chunk_size to argument and retry_on_failure = TRUE #879
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
Merged
Merged
Changes from all commits
Commits
Show all changes
51 commits
Select commit
Hold shift + click to select a range
4fb4f84
Merge pull request #868 from ldecicco-USGS/develop
ldecicco-USGS acbed0e
Merge pull request #869 from ldecicco-USGS/develop
ldecicco-USGS 7f6b6c5
set to character (we convert later)
ldecicco-USGS cd79c5f
Merge branch 'develop' of github.com:DOI-USGS/dataRetrieval into develop
ldecicco-USGS 32599cd
getting ready for CRAN release
ldecicco-USGS 76f55a1
test more things
ldecicco-USGS f79d3c8
Rebuilt triggers re-documenting
ldecicco-USGS e5a7788
Merge pull request #876 from ldecicco-USGS/develop
ldecicco-USGS 7439c40
deal with missing x,y in csv
ldecicco-USGS 144b8da
Merge branch 'main' of github.com:DOI-USGS/dataRetrieval into develop
ldecicco-USGS 85087d9
retry_on_failure = TRUE
ldecicco-USGS 99309d8
added chunking to daily
ldecicco-USGS 01d15f8
Adding chunk_size as named argument
ldecicco-USGS ebc0c46
retry on error
ldecicco-USGS bd4f18f
Merge branch 'develop' of github.com:DOI-USGS/dataRetrieval into develop
ldecicco-USGS 2f04f3d
clean up docs
ldecicco-USGS 863bef5
Update version
ldecicco-USGS c31924a
Add ...s
ldecicco-USGS 522786e
Rejigger parameters
ldecicco-USGS 1710692
generalize the tests more
ldecicco-USGS c6771e0
Cleanup install pipeline
ldecicco-USGS ff87ae8
att attach argument
ldecicco-USGS 8228252
?
ldecicco-USGS aa67bbe
Add first pass of read_waterdata_ratings
ldecicco-USGS c4aaca0
Clean up docs
ldecicco-USGS 005a2a0
Add to docs
ldecicco-USGS 58083ee
Added new reference lists
ldecicco-USGS bf2cbc5
Update R/read_waterdata_ratings.R
ldecicco-USGS 3343503
Using file_type more effectively
ldecicco-USGS c1cda89
Merge branch 'develop' of github.com:ldecicco-USGS/dataRetrieval into…
ldecicco-USGS 1a00759
Re-running docs with some updates from the API
ldecicco-USGS e2257af
Remove more tests that hit NWIS
ldecicco-USGS b95ee1f
Added data_type to comma, field_measurements_series_id to field measu…
ldecicco-USGS 6fc79d5
clean up dots
ldecicco-USGS d583fbf
Add token message
ldecicco-USGS 8be0492
use httr2 for download
ldecicco-USGS b0cd06e
does this work?
ldecicco-USGS 2cf55c1
Move into docker folder
ldecicco-USGS dca100f
?
ldecicco-USGS b56d783
wrong symbol
ldecicco-USGS d66f077
rebuild docker
ldecicco-USGS 1f51661
try to build docker again
ldecicco-USGS aa39d97
try again
ldecicco-USGS c9a2699
?
ldecicco-USGS a815d46
?
ldecicco-USGS 8aa0b9b
test python
ldecicco-USGS 57d6d09
Take out some old vignettes
ldecicco-USGS 5d25c06
?
ldecicco-USGS 02ff92a
?
ldecicco-USGS 56c78b8
Can I get below 1 Gb image?
ldecicco-USGS 1aadab4
call testthat instead of devtools
ldecicco-USGS File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,10 +12,8 @@ docs | |
| /doc/ | ||
| /Meta/ | ||
| /Temp/ | ||
| /public/ | ||
| vignettes/*.html | ||
| vignettes/*.R | ||
|
|
||
|
|
||
| /.quarto/ | ||
|
|
||
| **/*.quarto_ipynb | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unrelated but a question: do you know if
hydrologic_unit_codesfrom the monitoring-location endpoint is a single or comma parameter? I was just testing out passing a list of HUC8s in drpy, and I got an answer, but the count was way small and I don't even know what was actually used.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I last asked about that, huc's were not going to be comma parameters "any time soon" (so maybe someday?).
Remember HUCs are tricky. Our sites have a many combination of number of digits. So I think the issue was if you asked for c("012345", "012346"), you would only get those 2 HUCs, even if there were tons of sites with "01234567" and "01234678" for instance.
In dataRetrieval we send the HUC requests to a POST and that allows us to take advantage of the work the API developers put in to make HUCs special so that it really is going is as c("012345%", "012346%")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh wait! I forgot I set up the huc POST stuff specifically:
https://github.com/DOI-USGS/dataRetrieval/blob/develop/R/construct_api_requests.R#L498