-
Notifications
You must be signed in to change notification settings - Fork 28.4k
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
[SPARK-27262][R] Add explicit UTF-8 Encoding to DESCRIPTION #23823
Conversation
I got this warning when following the recommended approach to generating documentation: ``` Warning message: roxygen2 requires Encoding: UTF-8 ``` As can be seen in [other](https://github.com/tidyverse/tidyverse/blob/master/DESCRIPTION) [`tidyverse`](https://github.com/tidyverse/dplyr/blob/master/DESCRIPTION) [`DESCRIPTION`s](https://github.com/tidyverse/readr/blob/master/DESCRIPTION), this is standard practice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are *not * running the latest roxygen in the lab, there might be more of these
Jenkins, ok to test |
ok to test |
@felixcheung not sure if this helps/what you're getting at, but here are all the things that look like R package descriptions in Apache: https://github.com/search?q=org%3Aapache+RoxygenNote&type=Code |
^^ @MichaelChirico and they are all spark (except 1 mxnet) my comment is about spark's test environment. |
Test build #102495 has finished for PR 23823 at commit
|
Test build #4557 has finished for PR 23823 at commit
|
Is the second one the real failure? |
I think leaving to ASCII locale actually makes more sense (for now). IIRC, Jenkins uses ASCII encoidng as default (see #22782). |
Yes this is a real error. I’m not opposed to keeping it ASCII.
|
Given the current situation and the above advices, shall we close this PR for now, @MichaelChirico ? |
I'm not quite sure I follow, is this correct:
Therefore:
|
@MichaelChirico thanks for digging through this. Is there a way to get R to run as UTF-8? that might make it possible to keep the R and Roxygen version in our environment and not create new warning there or when running newer R/Roxygen. |
UTF-8 is done as of https://issues.apache.org/jira/browse/SPARK-27177. Looks SBT masters are not done yet, and I am not sure if they are all to be done. At least PR builders are done. Let me retrigger the test and see if that fixes cc @shaneknapp FYI. |
retest this please |
@MichaelChirico, mind filing a JIRA? It's minor but think it's good to track since it's related with another JIRA. |
Test build #103797 has finished for PR 23823 at commit
|
for merge, let's target master, and not branch-2.4 |
Retest this please. |
Test build #103854 has finished for PR 23823 at commit
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank. you, @MichaelChirico , @srowen , @HyukjinKwon , @felixcheung .
+1, LGTM. Merged to master.
Hi, @MichaelChirico . I need your Apache JIRA ID in order to assign it to you. What is your ID? |
Hey everyone, sorry to have checked out for a bit there. Thanks @dongjoon-hyun for filing the JIRA. I commented on the created issue to link my ID to GH: |
Thank you, @MichaelChirico . I assigned the issue to you. |
Hi, All.
|
Yes, I think sbt master isn't handled yet per https://issues.apache.org/jira/browse/SPARK-27177?focusedCommentId=16798307&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16798307 Let's revert. |
BTW, looks after the locale is swtiched to UTF-8 in PR builder, I see weird broken characters in the Jenkins UI like:
in R logs ... not sure if it's an issue to me or in general but thought it's good to note here before I forget. |
I see. Thank you for reverting, @HyukjinKwon . |
…ncoding to DESCRIPTION ### What changes were proposed in this pull request? This PR proposes to reenable CRAN check disabled at #27460. Given the tests #27468, seems we should also port #23823 together. ### Why are the changes needed? To check CRAN back. ### Does this PR introduce any user-facing change? No. ### How was this patch tested? It was tested at #27468 and Jenkins should test it out. Closes #27472 from HyukjinKwon/SPARK-30737. Authored-by: HyukjinKwon <[email protected]> Signed-off-by: HyukjinKwon <[email protected]>
…ncoding to DESCRIPTION ### What changes were proposed in this pull request? This PR proposes to reenable CRAN check disabled at #27460. Given the tests #27468, seems we should also port #23823 together. ### Why are the changes needed? To check CRAN back. ### Does this PR introduce any user-facing change? No. ### How was this patch tested? It was tested at #27468 and Jenkins should test it out. Closes #27472 from HyukjinKwon/SPARK-30737. Authored-by: HyukjinKwon <[email protected]> Signed-off-by: HyukjinKwon <[email protected]> (cherry picked from commit b95ccb1) Signed-off-by: HyukjinKwon <[email protected]>
…ncoding to DESCRIPTION ### What changes were proposed in this pull request? This PR proposes to reenable CRAN check disabled at #27460. Given the tests #27468, seems we should also port #23823 together. ### Why are the changes needed? To check CRAN back. ### Does this PR introduce any user-facing change? No. ### How was this patch tested? It was tested at #27468 and Jenkins should test it out. Closes #27472 from HyukjinKwon/SPARK-30737. Authored-by: HyukjinKwon <[email protected]> Signed-off-by: HyukjinKwon <[email protected]> (cherry picked from commit b95ccb1) Signed-off-by: HyukjinKwon <[email protected]>
What changes were proposed in this pull request?
I got this warning when following the recommended approach to generating documentation:
As can be seen in other
tidyverse
DESCRIPTION
s, this is standard practiceThis PR adds
Encoding: UTF-8
toR/pkg/DESCRIPTION
How was this patch tested?
Pass the Jenkins without warning.