Closed MatthieuStigler closed 2 years ago
Hi @MatthieuStigler you have to switch your rgee-tests bucket from bucket-level
to fine-grained level
. A fully tutorial about how to do this and why is here: https://r-spatial.github.io/rgee/articles/rgee05.html.
Please check if your SaK is working perfectly, running:
# remotes::install_github("r-spatial/rgee") Install rgee v.1.3
library(rgee)
ee_Initialize("csaybar")
SaK_file <- "/home/csaybar/Downloads/SaK_rgee.json" # PUT HERE THE FULLNAME OF YOUR SAK.
# Assign the SaK to a EE user.
ee_utils_sak_copy(
sakfile = SaK_file,
users = c("csaybar", "ryali93") # Unlike GD, we can use the same SaK for multiple users.
)
# Validate your SaK
ee_utils_sak_validate()
oh, sorry about this, I missed that part of the documentation! I changed the access control, and now it runs fine!
I also tried the ee_utils_sak_validate()
function, it does not work when I don't specify bucket
(given that some buckets have the previous uniform control behavior), but it does when I specify ee_utils_sak_validate(bucket = "rgee-tests")
As a side note, if one tries ee_utils_sak_validate(bucket = "wrong")
, some error messages come very early, but the test still takes a minute?
ee_utils_sak_validate(bucket = "wrong")
── SaK validator ───────────────────────────────────────────────────────────────────────────── The test should take ~1 min. Please wait. ──
http_403 The project to be billed is associated with an absent billing account.
An ERROR raised when rgee tries to write in your GCS bucket.
http_403 Unspecified error
An ERROR raised when rgee tries to read your GCS bucket.
ERROR in Earth Engine servers: Unable to write to bucket wrong (permission denied).
ee_monitoring was forced to stop before getting results
An ERROR raised when rgee tries to sync GEE & GCS.
Error in `abort_http()`:
! http_404 No such object: wrong/demo_data.csv
Run `rlang::last_error()` to see where the error occurred.
Hi @MatthieuStigler can you show us the message error when run ee_utils_sak_validate()
.
As a side note, if one tries ee_utils_sak_validate(bucket = "wrong"), some error messages come very early, but the test still takes a minute?
You're right, there is no reason for continuous checking if a previous check fails, we will fix it soon!
When I try to replicate the example in
ee_as_sf()
, using via="gcs", I get a strange error message: _Error inabort_http()
: ! http400 Cannot update access control for an object when uniform bucket-level access is enabled. Strangely enough, the task goes through and shows as completed. Should I have used a different type of control access for that bucket on google cloud storage?Thanks!
Code:
And using
rlang::last_error()
shows:Created on 2022-02-15 by the reprex package (v2.0.1)