-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Spaces fixes #165
Spaces fixes #165
Conversation
@thosjleeper added this fix for us in aws.s3 so this works now
space_list returns a data.frame of the contents and space_delete does what it says on the tin
Just added space_location and a small fix I missed from R CMD CHECK. |
Add documentation page at |
Looking good.
Yeah i think so, looks good. We can see what users are confused by and add more details later. Are there other things you're adding here? |
All good now! Thanks. |
@amoeba i can't get space_create("new_space_name", config=httr::verbose()) -> PUT /new_space_name/ HTTP/1.1
-> Host: nyc3.digitaloceanspaces.com
-> User-Agent: libcurl/7.54.0 r-curl/3.2 httr/1.3.1
-> Accept-Encoding: gzip, deflate
-> Accept: application/json, text/xml, application/xml, */*
-> Content-Length: 0
->
<- HTTP/1.1 400 Bad Request
<- Date: Mon, 06 Aug 2018 23:46:23 GMT
<- Content-Length: 153
<- Content-Type: text/plain; charset=utf-8
<- with some headers stripped out for brevity. so i'm getting a 400 client error. Does it work for you? |
Did you build a copy of aws.s3 from the latest on the |
used latest from github |
Okay, thanks for testing this out. I'll take a look in the AM and see if I was just hallucinating. |
thanks |
I had a sec just now to test. Works for me. Our implementation doesn't catch any errors > library(analogsea)
> Sys.setenv("DO_SPACES_REGION"="nyc3",
+ "DO_SPACES_ACCESS_KEY"="...",
+ "DO_SPACES_SECRET_KEY"="...")
> # List my spaces
> spaces()
named list()
> space_create("test-for-scott")
New space test-for-scott created successfully Session Info
And the space I made shows up on the website just fine. Our our versions of aws.s3 and aws.signature the same? |
will check, thanks |
same versionsPackages -------------
package * version date source
.py 0.0.16 <NA> local
analogsea * 0.6.5.9110 <NA> local
aws.s3 0.3.19 2018-08-06 Github (cloudyr/aws.s3@874f6a7)
aws.signature 0.4.4 2018-07-27 CRAN (R 3.5.1)
base * 3.5.1 2018-07-19 local
base64enc 0.1-3 2015-07-28 CRAN (R 3.5.0)
commonmark 1.5 2018-04-28 CRAN (R 3.5.0)
compiler 3.5.1 2018-07-19 local
curl 3.2 2018-03-28 CRAN (R 3.5.0)
datasets * 3.5.1 2018-07-19 local
devtools 1.13.6 2018-06-27 CRAN (R 3.5.0)
digest 0.6.15 2018-01-28 CRAN (R 3.5.0)
graphics * 3.5.1 2018-07-19 local
grDevices * 3.5.1 2018-07-19 local
httr 1.3.1 2017-08-20 CRAN (R 3.5.0)
jsonlite 1.5 2017-06-01 CRAN (R 3.5.0)
magrittr 1.5 2014-11-22 CRAN (R 3.5.0)
memoise 1.1.0 2017-04-21 CRAN (R 3.5.0)
methods * 3.5.1 2018-07-19 local
R6 2.2.2 2017-06-17 CRAN (R 3.5.0)
Rcpp 0.12.18 2018-07-23 CRAN (R 3.5.1)
rlang 0.2.1 2018-05-30 CRAN (R 3.5.0)
roxygen2 6.1.0 2018-07-27 CRAN (R 3.5.0)
rstudioapi 0.7 2017-09-07 CRAN (R 3.5.0)
rtichoke 0.2.1 <NA> local
ssh 0.2 2018-06-04 CRAN (R 3.5.0)
stats * 3.5.1 2018-07-19 local
stringi 1.2.4 2018-07-20 CRAN (R 3.5.0)
stringr 1.3.1 2018-05-10 CRAN (R 3.5.0)
testthat * 2.0.0 2017-12-13 CRAN (R 3.5.0)
tools 3.5.1 2018-07-19 local
utils * 3.5.1 2018-07-19 local
withr 2.1.2 2018-03-15 CRAN (R 3.5.0)
xml2 1.2.0 2018-01-24 CRAN (R 3.5.0)
yaml 2.2.0 2018-07-25 CRAN (R 3.5.1) Still not workfing for me, can you do |
Here's the doubly-verbose output:
I've found debugging by throwing |
hugh, seems that I was running into invalid regions https://www.digitalocean.com/docs/platform/availability-matrix/#product-availability-by-datacenter-region suggests nyc3 is not available, with the following avail: ams3, sfo2, sgp1 i imagine we should change the default to one of those 3? |
I think this is just due to today's spaces outage, and I think it might fix itself. IIRC nyc3 was the first and only availability region and I haven't ehard anything that indicates it's going away. Incident details: https://status.digitalocean.com/incidents/bbyt03t1vm88 I'll do some digging. |
hmm, if that's right that nyc3 is just out temporarily, then I guess I don't know why it was failing on my end before. Anyway, seems to be working now |
i can work on #150 and then I think we're very close to getting this off to cran |
Sounds great, let me know if you want a hand or a second set of eyes. |
Kinda-grabbag-of-a-PR here:
aws.s3 got some fixes, not sure if they're on CRAN yet, but now things that broke now work!
space_create
works and is now re-enabledspaces_object_put
works w/ multipartspaces_object_delete
works now and is now re-enabledAlso added:
DO_SPACES_REGION
env var, to address Cannot change "spaces_base" variable, spaces different region support #163space_delete
andspace_list()
which are two API calls we hadn't doneFixes #163
More to come as I make time!