Skip to content
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

Warning message: NAs introduced by coercion to integer range #2708

Closed
studerus opened this issue Apr 26, 2017 · 2 comments
Closed

Warning message: NAs introduced by coercion to integer range #2708

studerus opened this issue Apr 26, 2017 · 2 comments
Labels
bug an unexpected problem or unintended behavior

Comments

@studerus
Copy link

The simple command:

filter(iris, Sepal.Length > 5)

leads to the following warning message:

Warning message:
In (function (x, table, nomatch = NA_integer_, incomparables = NULL)  :
  NAs introduced by coercion to integer range

I could replicate the warning only under 32 bit windows 10, but not 64 bit windows 10. This is my session info:

R version 3.4.0 (2017-04-21)
Platform: i386-w64-mingw32/i386 (32-bit)
Running under: Windows >= 8 x64 (build 9200)

Matrix products: default

locale:
[1] LC_COLLATE=German_Switzerland.1252  LC_CTYPE=German_Switzerland.1252   
[3] LC_MONETARY=German_Switzerland.1252 LC_NUMERIC=C                       
[5] LC_TIME=German_Switzerland.1252    

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base     

other attached packages:
[1] bindrcpp_0.1

loaded via a namespace (and not attached):
 [1] compiler_3.4.0    magrittr_1.5      assertthat_0.2.0  R6_2.2.0          tools_3.4.0      
 [6] glue_1.0.0        dplyr_0.5.0.9004  tibble_1.3.0.9001 yaml_2.1.14       Rcpp_0.12.10     
[11] rlang_0.0.0.9018  bindr_0.1       
@hadley
Copy link
Member

hadley commented May 2, 2017

@krlmlr do you happen to have a 32-bit windows that you could check this on?

@hadley hadley added bug an unexpected problem or unintended behavior data frame labels May 2, 2017
@hadley
Copy link
Member

hadley commented May 2, 2017

(@studerus in the future, we prefer devtools::session_info())

@lock lock bot locked as resolved and limited conversation to collaborators Jun 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

2 participants