-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[R]: on_rosetta()
should not error
#38752
Comments
assignUser
pushed a commit
that referenced
this issue
Nov 17, 2023
### Rationale for this change We should never allow rosetta checking from causing an error ### What changes are included in this PR? ~Wrap rosetta checking in a tryCatch~ our use of `try()` wasn't doing what we thought, it actually needs to have `silent = TRUE` specified to _not_ error. ### Are these changes tested? I tested them locally by manipulating the system call to a mangled command that doesn't exist, observing the error on load, then wrapping in trycatch. We might consider adding a test in CI, though there would be considerable complexity for something like that ### Are there any user-facing changes? No, though we will need to pull it into any point release * Closes: #38752 Authored-by: Jonathan Keane <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
37 tasks
thisisnic
pushed a commit
to thisisnic/arrow
that referenced
this issue
Nov 23, 2023
### Rationale for this change We should never allow rosetta checking from causing an error ### What changes are included in this PR? ~Wrap rosetta checking in a tryCatch~ our use of `try()` wasn't doing what we thought, it actually needs to have `silent = TRUE` specified to _not_ error. ### Are these changes tested? I tested them locally by manipulating the system call to a mangled command that doesn't exist, observing the error on load, then wrapping in trycatch. We might consider adding a test in CI, though there would be considerable complexity for something like that ### Are there any user-facing changes? No, though we will need to pull it into any point release * Closes: apache#38752 Authored-by: Jonathan Keane <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
assignUser
pushed a commit
to thisisnic/arrow
that referenced
this issue
Nov 28, 2023
### Rationale for this change We should never allow rosetta checking from causing an error ### What changes are included in this PR? ~Wrap rosetta checking in a tryCatch~ our use of `try()` wasn't doing what we thought, it actually needs to have `silent = TRUE` specified to _not_ error. ### Are these changes tested? I tested them locally by manipulating the system call to a mangled command that doesn't exist, observing the error on load, then wrapping in trycatch. We might consider adding a test in CI, though there would be considerable complexity for something like that ### Are there any user-facing changes? No, though we will need to pull it into any point release * Closes: apache#38752 Authored-by: Jonathan Keane <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
raulcd
pushed a commit
that referenced
this issue
Nov 28, 2023
### Rationale for this change We should never allow rosetta checking from causing an error ### What changes are included in this PR? ~Wrap rosetta checking in a tryCatch~ our use of `try()` wasn't doing what we thought, it actually needs to have `silent = TRUE` specified to _not_ error. ### Are these changes tested? I tested them locally by manipulating the system call to a mangled command that doesn't exist, observing the error on load, then wrapping in trycatch. We might consider adding a test in CI, though there would be considerable complexity for something like that ### Are there any user-facing changes? No, though we will need to pull it into any point release * Closes: #38752 Authored-by: Jonathan Keane <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
assignUser
pushed a commit
to assignUser/arrow
that referenced
this issue
Dec 1, 2023
### Rationale for this change We should never allow rosetta checking from causing an error ### What changes are included in this PR? ~Wrap rosetta checking in a tryCatch~ our use of `try()` wasn't doing what we thought, it actually needs to have `silent = TRUE` specified to _not_ error. ### Are these changes tested? I tested them locally by manipulating the system call to a mangled command that doesn't exist, observing the error on load, then wrapping in trycatch. We might consider adding a test in CI, though there would be considerable complexity for something like that ### Are there any user-facing changes? No, though we will need to pull it into any point release * Closes: apache#38752 Authored-by: Jonathan Keane <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
dgreiss
pushed a commit
to dgreiss/arrow
that referenced
this issue
Feb 19, 2024
### Rationale for this change We should never allow rosetta checking from causing an error ### What changes are included in this PR? ~Wrap rosetta checking in a tryCatch~ our use of `try()` wasn't doing what we thought, it actually needs to have `silent = TRUE` specified to _not_ error. ### Are these changes tested? I tested them locally by manipulating the system call to a mangled command that doesn't exist, observing the error on load, then wrapping in trycatch. We might consider adding a test in CI, though there would be considerable complexity for something like that ### Are there any user-facing changes? No, though we will need to pull it into any point release * Closes: apache#38752 Authored-by: Jonathan Keane <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug, including details regarding any error messages, version, and platform.
This is happening on CRAN's M1: https://www.stats.ox.ac.uk/pub/bdr/M1mac/arrow.out
I thought that this was already wrapped in
tryCatch
, but it appears not. We should do thisComponent(s)
R
The text was updated successfully, but these errors were encountered: