-
Notifications
You must be signed in to change notification settings - Fork 2k
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
"Error in if (is_http) { : argument is of length zero" in shinytest #708
Comments
And I have tested it: #620 leads to
probably because
if (is.null(url_scheme)) {
url_scheme <- ""
} In summary, I think |
Request:
Response:
And the content resolves to
where |
I think the main problem that I am having with regard to this is that is does not reproduce consistently, so I cannot make any hard statements on whether #620 would solve this (I seem to remember it did not, but from looking at the code I am unable to say why it wouldn't) and/or whether url_scheme <- "" works (I believe it should not, and require at least resp$headers <- NULL as well). It may also be that my failing At least, I think I have given enough information in #708 (comment) for you to see that if even the user does everything correct (i.e., does not forget a protocol or something), |
This sounds more like a bug in shinytest to me. Why are those fields |
I am
shinytest
ing a Shiny app, and while each test runs fine on its own, one specific test fails when run in a long sequence of some 20 other tests.The error message is
and is related to this:
httr/R/request.R
Lines 159 to 167 in 2cd5ed8
I don't have a reprex yet, but I could investigate that
url_scheme
isNULL
becauseresp$url
is empty (I cannot yet say if it'scharacter(0)
or""
, though, as they look the same in the onestop()
output that I have). Interestingly,req$url
looks very resonable:Here is some more output from
So I while I am investigating while this request may be failing, I wonder if
resp$url
should ever be empty ifreq$url
is a valid URL, and if so, ifhttr
should handle that. I am aware of #620, but I feel this is a rather symptomatic fix (and not released yet, anyway).The text was updated successfully, but these errors were encountered: