-
Notifications
You must be signed in to change notification settings - Fork 62
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
board_register()
fails with error "argument is of length zero"
#529
Comments
Can you please provide more detail about exactly what you are trying to do and what happens, including your environment? A good error report will include:
For example, here is an error report that I filed internally about The code: library(pins)
board <- board_rsconnect(
server = "https://connect.rstudioservices.com",
key = Sys.getenv("RSTUDIOSERVICES_CONNECT_API_KEY")
)
board %>%
pin_read("andrie/white_glove_calendar_data") The error message:
The result of
And then provide your The more information you provide, the easier it will be for us to help you. |
Thanks Andrie for you quick response! Please see details below, I think it is because of the 3.5.0 env, I tested in 3.6, it worked. The code:
The error message:
|
Can you please check the |
You are right, apologies for the confusion.
|
I think you should try one of two things: With the legacy API, use library(pins)
rsc_key = Sys.getenv("RSCONNECT_KEY")
board_register_rsconnect( server = "https://rstudiocondev.xxxx.com",
key = rsc_key ) But it's probably a good time to switch to the new API: library(pins)
board <- board_rsconnect(
server = "https://rstudiocondev.xxxx.com",
key = Sys.getenv("RSCONNECT_KEY")
)
board %>%
pin_write(...) |
Thanks! the connection worked, however the pin_write failed this time: Code:
Error:
traceback:
however, board seems to be a pin board
|
Yes, that's because you've inserted an argument into the code that breaks the Try: board <- board_rsconnect(server = "rstudiocondev.xxxx.com",
key = "key")
board %>% pin_write(a,
name = "a",
description = "a"
) |
Thanks Andrie! I got a new error, I think this is something from my side, but just want to confirm before I talk to someone else. Thank you so much for your help! board %>% pin_write(a,
name = "a",
description = "a")
|
Could you please post how you got the "Error in rsc_check_status(req) : Not Found (HTTP 404)." resolved? |
Hi, I was not able to get the HTTP error resolved, instead, I installed an earlier version of the pins package. |
Can you please open a support ticket so we can take a look? Please tell the support team to add me to the ticket. |
I think we should re-open this issue. |
@Yogeshwara If you're seeing that error, it might be worth checking to see if you have anything like a reverse proxy or Web Application Firewall in front of Connect that may be causing an issue. We saw something similar in #539, which turned out to be a WAF rule blocking certain types of API request. |
I am having the same error when using board_rsconnect to pin files to RSConnect. We have opened a support ticket and asked for Andrie to be added. Code library(pins)
api_key <- keyring::key_get("pins", "api_key")
rsconnect_board <- board_rsconnect(key=api_key, server="https://my.server.com")
data <- iris
pin_name <- "reprex_pin"
rsconnect_board %>% pin_write(data, pin_name) Error
Traceback
Session Info
|
@MattNickodemus it would be worth checking your Connect server environment for proxies and web application firewalls. We've had some reports of WAFs in particular blocking some of the Connect API calls that pins uses. |
@sellorm Our IT team checked the Connect server environment and there are no issues with proxies or firewalls. We installed a previous version of the pins package and that resolved the issue. However, we would like to be able to run the latest version. @andrie, we still have an open ticket with @rstudio but they have asked that we resolve the issue here. |
@MattNickodemus your problem doesn't appear to be related to this issue, so I'd recommend creating a new issue. |
The root cause of the issue here is that |
Always do it in the board generation, not earlier. Fixes #529
board_register()
fails with error "argument is of length zero"
Always do it in the board generation, not earlier. Fixes #529
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
Hi! I'm using the board_rsconnect to pin files to RSConnect in R version 3.5. Since this week, I'm seeing this error when calling board_rsconnect. Wondering if there's anything changed. Thanks!
The text was updated successfully, but these errors were encountered: