[jira] [Commented] (YETUS-1122) pylint: provide option to ignore 'bad-option-value'
[ https://issues.apache.org/jira/browse/YETUS-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420431#comment-17420431 ] Akira Ajisaka commented on YETUS-1122: -- Thank you [~aw] for adding the option. I think we need to write a release note for this issue because the default behavior will change. > pylint: provide option to ignore 'bad-option-value' > --- > > Key: YETUS-1122 > URL: https://issues.apache.org/jira/browse/YETUS-1122 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Affects Versions: 0.13.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.14.0 > > > This flag would be a work-around for > https://github.com/PyCQA/pylint/issues/3312 . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-1118) Add .asf.yaml to asf-site branch to deploy website
[
https://issues.apache.org/jira/browse/YETUS-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17402089#comment-17402089
]
Akira Ajisaka commented on YETUS-1118:
--
Yetus is affected: https://infra-reports.apache.org/site-source/
> Add .asf.yaml to asf-site branch to deploy website
> --
>
> Key: YETUS-1118
> URL: https://issues.apache.org/jira/browse/YETUS-1118
> Project: Yetus
> Issue Type: Task
> Components: website and documentation
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
>
> Git web site publishing to be done via .asf.yaml only as of July 1st.
> {quote}
> h2. How to publish via .asf.yaml:
> Publishing via .asf.yaml is described at:
> https://s.apache.org/asfyamlpublishing
> You can also see an example .asf.yaml with publishing and staging
> profiles for our own infra web site at:
> https://github.com/apache/infrastructure-website/blob/asf-site/.asf.yaml
> In short, one puts a file called .asf.yaml into the branch that needs to
> be published as the project's web site, with the following two-line
> content, in this case assuming the published branch is 'asf-site':
> {noformat}
> publish:
>whoami: asf-site
> {noformat}
> It is important to note that the .asf.yaml file MUST be present at the
> root of the file system in the branch you wish to publish. The 'whoami'
> parameter acts as a guard, ensure that only the intended branch is used
> for publishing.
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (YETUS-1118) Add .asf.yaml to asf-site branch to deploy website
Akira Ajisaka created YETUS-1118:
Summary: Add .asf.yaml to asf-site branch to deploy website
Key: YETUS-1118
URL: https://issues.apache.org/jira/browse/YETUS-1118
Project: Yetus
Issue Type: Task
Components: website and documentation
Reporter: Akira Ajisaka
Assignee: Akira Ajisaka
Git web site publishing to be done via .asf.yaml only as of July 1st.
{quote}
h2. How to publish via .asf.yaml:
Publishing via .asf.yaml is described at:
https://s.apache.org/asfyamlpublishing
You can also see an example .asf.yaml with publishing and staging
profiles for our own infra web site at:
https://github.com/apache/infrastructure-website/blob/asf-site/.asf.yaml
In short, one puts a file called .asf.yaml into the branch that needs to
be published as the project's web site, with the following two-line
content, in this case assuming the published branch is 'asf-site':
{noformat}
publish:
whoami: asf-site
{noformat}
It is important to note that the .asf.yaml file MUST be present at the
root of the file system in the branch you wish to publish. The 'whoami'
parameter acts as a guard, ensure that only the intended branch is used
for publishing.
{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (YETUS-1106) Detect CMake test changes
[ https://issues.apache.org/jira/browse/YETUS-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YETUS-1106: - Flags: (was: Important) > Detect CMake test changes > - > > Key: YETUS-1106 > URL: https://issues.apache.org/jira/browse/YETUS-1106 > Project: Yetus > Issue Type: Bug > Components: Precommit >Affects Versions: 0.13.0 >Reporter: Gautham Banasandra >Assignee: Gautham Banasandra >Priority: Critical > Fix For: 0.14.0 > > Original Estimate: 24h > Time Spent: 2h 10m > Remaining Estimate: 21h 50m > > test4tests uses a regex match to detect if there are any changes under *test* > directory, by following the directory structure of a maven project. However, > the tests in CMake are conventionally put under a directory named *tests*. > This causes the regex match in test4tests to fail and thus results in a -1 > overall score in the case of CMake. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (YETUS-1116) Documentation for blank-test incorrect
[
https://issues.apache.org/jira/browse/YETUS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated YETUS-1116:
-
Priority: Minor (was: Trivial)
> Documentation for blank-test incorrect
> --
>
> Key: YETUS-1116
> URL: https://issues.apache.org/jira/browse/YETUS-1116
> Project: Yetus
> Issue Type: Bug
> Components: website and documentation
>Reporter: Michel Onstein
>Priority: Minor
> Fix For: 0.14.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The documentation incorrectly lists `{{.yetus/blanks-eol.txt}}` as the
> default ignore file for the blank-tabs-test. It should be
> `{{.yetus/blanks-tabs.txt}}`.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (YETUS-1116) Documentation for blank-test incorrect
[
https://issues.apache.org/jira/browse/YETUS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated YETUS-1116:
-
Component/s: website and documentation
> Documentation for blank-test incorrect
> --
>
> Key: YETUS-1116
> URL: https://issues.apache.org/jira/browse/YETUS-1116
> Project: Yetus
> Issue Type: Bug
> Components: website and documentation
>Reporter: Michel Onstein
>Priority: Trivial
> Fix For: 0.14.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The documentation incorrectly lists `{{.yetus/blanks-eol.txt}}` as the
> default ignore file for the blank-tabs-test. It should be
> `{{.yetus/blanks-tabs.txt}}`.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (YETUS-1116) Documentation for blank-test incorrect
[
https://issues.apache.org/jira/browse/YETUS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17400870#comment-17400870
]
Akira Ajisaka commented on YETUS-1116:
--
Merged into master.
> Documentation for blank-test incorrect
> --
>
> Key: YETUS-1116
> URL: https://issues.apache.org/jira/browse/YETUS-1116
> Project: Yetus
> Issue Type: Bug
>Reporter: Michel Onstein
>Priority: Trivial
> Fix For: 0.14.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The documentation incorrectly lists `{{.yetus/blanks-eol.txt}}` as the
> default ignore file for the blank-tabs-test. It should be
> `{{.yetus/blanks-tabs.txt}}`.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (YETUS-1116) Documentation for blank-test incorrect
[
https://issues.apache.org/jira/browse/YETUS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka resolved YETUS-1116.
--
Fix Version/s: 0.14.0
Resolution: Fixed
> Documentation for blank-test incorrect
> --
>
> Key: YETUS-1116
> URL: https://issues.apache.org/jira/browse/YETUS-1116
> Project: Yetus
> Issue Type: Bug
>Reporter: Michel Onstein
>Priority: Trivial
> Fix For: 0.14.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The documentation incorrectly lists `{{.yetus/blanks-eol.txt}}` as the
> default ignore file for the blank-tabs-test. It should be
> `{{.yetus/blanks-tabs.txt}}`.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Deleted] (YETUS-1110) SITUS JUDI QQ TERPERCAYA
[ https://issues.apache.org/jira/browse/YETUS-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka deleted YETUS-1110: - > SITUS JUDI QQ TERPERCAYA > > > Key: YETUS-1110 > URL: https://issues.apache.org/jira/browse/YETUS-1110 > Project: Yetus > Issue Type: Task >Reporter: AGOGO QIU >Priority: Major > > AGOGOQIU SITUS JUDI QQ DominoQQ TERPERCAYA N0.1 seIndonesia yang menerima > deposit menggunakan Pulsa Tanpa Potongan. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (YETUS-1106) Detect CMake test changes
[ https://issues.apache.org/jira/browse/YETUS-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned YETUS-1106: Assignee: Gautham Banasandra > Detect CMake test changes > - > > Key: YETUS-1106 > URL: https://issues.apache.org/jira/browse/YETUS-1106 > Project: Yetus > Issue Type: Bug > Components: Precommit >Affects Versions: 0.13.0 >Reporter: Gautham Banasandra >Assignee: Gautham Banasandra >Priority: Critical > Original Estimate: 24h > Time Spent: 2h 10m > Remaining Estimate: 21h 50m > > test4tests uses a regex match to detect if there are any changes under *test* > directory, by following the directory structure of a maven project. However, > the tests in CMake are conventionally put under a directory named *tests*. > This causes the regex match in test4tests to fail and thus results in a -1 > overall score in the case of CMake. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (YETUS-1106) Detect CMake test changes
[ https://issues.apache.org/jira/browse/YETUS-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YETUS-1106. -- Fix Version/s: 0.14.0 Resolution: Fixed Merged. Thank you [~gautham]! > Detect CMake test changes > - > > Key: YETUS-1106 > URL: https://issues.apache.org/jira/browse/YETUS-1106 > Project: Yetus > Issue Type: Bug > Components: Precommit >Affects Versions: 0.13.0 >Reporter: Gautham Banasandra >Assignee: Gautham Banasandra >Priority: Critical > Fix For: 0.14.0 > > Original Estimate: 24h > Time Spent: 2h 10m > Remaining Estimate: 21h 50m > > test4tests uses a regex match to detect if there are any changes under *test* > directory, by following the directory structure of a maven project. However, > the tests in CMake are conventionally put under a directory named *tests*. > This causes the regex match in test4tests to fail and thus results in a -1 > overall score in the case of CMake. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (YETUS-1102) Add an option to comment to GitHub PR
[ https://issues.apache.org/jira/browse/YETUS-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YETUS-1102: - Component/s: Precommit > Add an option to comment to GitHub PR > - > > Key: YETUS-1102 > URL: https://issues.apache.org/jira/browse/YETUS-1102 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Fix For: 0.14.0 > > Time Spent: 3h > Remaining Estimate: 0h > > In YETUS-994, the Yetus comments have been replaced with GitHub Statuses. > However, it is not useful for some Hadoop developers. I want to add an option > to enable the previous behavior. > CC: [~ayushsaxena], [~ste...@apache.org], and [~ahussein]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-1102) Add an option to comment to GitHub PR
[ https://issues.apache.org/jira/browse/YETUS-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310066#comment-17310066 ] Akira Ajisaka commented on YETUS-1102: -- bq. I'm assuming Hadoop is (still) doing integration tests instead of unit tests or the filehandle leak still there. Lowering the parallelism is just putting another band-aid on top of a gushing wound. I think your assumption is right. However, I don't think the integration tests can be disabled because they are very important in distributed systems like Apache Hadoop and have discovered a lot of actual bugs. bq. It is sort of pointless to hold Yetus back because of one project that has an awful QA track record anyway. * As a Yetus developer: Yeah, agreed that it is pointless to hold Yetus back for one broken project. * As a Hadoop developer: If Yetus continues to drop the old options such as GitHub PR comments, Hadoop may drop Yetus in the near future because I think it's easier to maintain the scripts rather than fixing the super broken testing. Ideally we must fix the broken testing, but it is too costly. > Add an option to comment to GitHub PR > - > > Key: YETUS-1102 > URL: https://issues.apache.org/jira/browse/YETUS-1102 > Project: Yetus > Issue Type: Improvement >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Fix For: 0.14.0 > > Time Spent: 3h > Remaining Estimate: 0h > > In YETUS-994, the Yetus comments have been replaced with GitHub Statuses. > However, it is not useful for some Hadoop developers. I want to add an option > to enable the previous behavior. > CC: [~ayushsaxena], [~ste...@apache.org], and [~ahussein]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-1102) Add an option to comment to GitHub PR
[ https://issues.apache.org/jira/browse/YETUS-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309534#comment-17309534 ] Akira Ajisaka commented on YETUS-1102: -- Unfortunately, even if we could split the modules, it's not easy to increase the parallelism because the tests will become flaky due to some resource collision. Recently I've decreased the parallelism from 4 to 2 in HDFS-15731. > Add an option to comment to GitHub PR > - > > Key: YETUS-1102 > URL: https://issues.apache.org/jira/browse/YETUS-1102 > Project: Yetus > Issue Type: Improvement >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Fix For: 0.14.0 > > Time Spent: 3h > Remaining Estimate: 0h > > In YETUS-994, the Yetus comments have been replaced with GitHub Statuses. > However, it is not useful for some Hadoop developers. I want to add an option > to enable the previous behavior. > CC: [~ayushsaxena], [~ste...@apache.org], and [~ahussein]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (YETUS-1102) Add an option to comment to GitHub PR
[ https://issues.apache.org/jira/browse/YETUS-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YETUS-1102. -- Fix Version/s: 0.14.0 Resolution: Fixed Merged the PR to main branch. > Add an option to comment to GitHub PR > - > > Key: YETUS-1102 > URL: https://issues.apache.org/jira/browse/YETUS-1102 > Project: Yetus > Issue Type: Improvement >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Fix For: 0.14.0 > > Time Spent: 3h > Remaining Estimate: 0h > > In YETUS-994, the Yetus comments have been replaced with GitHub Statuses. > However, it is not useful for some Hadoop developers. I want to add an option > to enable the previous behavior. > CC: [~ayushsaxena], [~ste...@apache.org], and [~ahussein]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (YETUS-1105) Xml check fails since JDK 15
Akira Ajisaka created YETUS-1105:
Summary: Xml check fails since JDK 15
Key: YETUS-1105
URL: https://issues.apache.org/jira/browse/YETUS-1105
Project: Yetus
Issue Type: Bug
Components: Precommit
Reporter: Akira Ajisaka
Nashorn has been removed since JDK 15, so jrunscript fails.
{noformat}
$ java -version
openjdk version "15.0.2" 2021-01-19
OpenJDK Runtime Environment AdoptOpenJDK (build 15.0.2+7)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 15.0.2+7, mixed mode, sharing)
$ jrunscript -e "XMLDocument(arguments[0])" pom.xml > output.txt
script engine for language js can not be found
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (YETUS-1102) Add an option to comment to GitHub PR
[ https://issues.apache.org/jira/browse/YETUS-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17297039#comment-17297039 ] Akira Ajisaka commented on YETUS-1102: -- bq. It has gone up by 5-6 hours since I last looked a few years ago. There are many new features and new tests introduced in the few years, and sometimes we have to run all the unit tests for drastic changes (e.g., protocol buffers upgrade). Therefore the timeout is extended. > Add an option to comment to GitHub PR > - > > Key: YETUS-1102 > URL: https://issues.apache.org/jira/browse/YETUS-1102 > Project: Yetus > Issue Type: Improvement >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Time Spent: 2.5h > Remaining Estimate: 0h > > In YETUS-994, the Yetus comments have been replaced with GitHub Statuses. > However, it is not useful for some Hadoop developers. I want to add an option > to enable the previous behavior. > CC: [~ayushsaxena], [~ste...@apache.org], and [~ahussein]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (YETUS-1104) checkmake failing to build
[ https://issues.apache.org/jira/browse/YETUS-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YETUS-1104. -- Fix Version/s: 0.14.0 Resolution: Fixed Merged the PR. Thank you, [~aw]. > checkmake failing to build > -- > > Key: YETUS-1104 > URL: https://issues.apache.org/jira/browse/YETUS-1104 > Project: Yetus > Issue Type: Bug > Components: build >Affects Versions: 0.13.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Blocker > Fix For: 0.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > > checkmake container is failing to build -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (YETUS-1102) Add an option to comment to GitHub PR
[ https://issues.apache.org/jira/browse/YETUS-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned YETUS-1102: Assignee: Akira Ajisaka > Add an option to comment to GitHub PR > - > > Key: YETUS-1102 > URL: https://issues.apache.org/jira/browse/YETUS-1102 > Project: Yetus > Issue Type: Improvement >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In YETUS-994, the Yetus comments have been replaced with GitHub Statuses. > However, it is not useful for some Hadoop developers. I want to add an option > to enable the previous behavior. > CC: [~ayushsaxena], [~ste...@apache.org], and [~ahussein]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-1102) Add an option to comment to GitHub PR
[ https://issues.apache.org/jira/browse/YETUS-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17293775#comment-17293775 ] Akira Ajisaka commented on YETUS-1102: -- While you think bringing comment back is a step backward, the current situation is not good for us. Even the annotations are working as expected, the github comments are still useful for us because: - The comment notifies us that the build is finished. The GitHub status does not notify. - The elapsed times are included in the comment. They are important metrics for long running job. - We can view the history of build summary by just scrolling the screen of the PR. > Add an option to comment to GitHub PR > - > > Key: YETUS-1102 > URL: https://issues.apache.org/jira/browse/YETUS-1102 > Project: Yetus > Issue Type: Improvement >Reporter: Akira Ajisaka >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In YETUS-994, the Yetus comments have been replaced with GitHub Statuses. > However, it is not useful for some Hadoop developers. I want to add an option > to enable the previous behavior. > CC: [~ayushsaxena], [~ste...@apache.org], and [~ahussein]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (YETUS-1102) Add an option to comment to GitHub PR
Akira Ajisaka created YETUS-1102: Summary: Add an option to comment to GitHub PR Key: YETUS-1102 URL: https://issues.apache.org/jira/browse/YETUS-1102 Project: Yetus Issue Type: Improvement Reporter: Akira Ajisaka In YETUS-994, the Yetus comments have been replaced with GitHub Statuses. However, it is not useful for some Hadoop developers. I want to add an option to enable the previous behavior. CC: [~ayushsaxena], [~ste...@apache.org], and [~ahussein]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (YETUS-1099) shelldocs --lint option fails
[
https://issues.apache.org/jira/browse/YETUS-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated YETUS-1099:
-
Description:
shelldocs --lint options fails:
{noformat}
hadoop-mirror git:(HADOOP-16747) ✗ ./dev-support/bin/shelldocs --lint -i
./hadoop-common-project/hadoop-common/src/main/bin/start-all.sh
Traceback (most recent call last):
File
"/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
line 477, in
main()
File
"/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
line 468, in main
message = funcs.lint()
File
"/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
line 273, in lint
value = getfuncs[attr]()
TypeError: 'str' object is not callable
{noformat}
Here the result of "getfuncs[attr]" is "self.replacetext" and its type is "str"
or "NoneType". These types cannot call "()" and that's why the error occurs.
was:
shelldocs --lint options fails:
{noformat}
hadoop-mirror git:(HADOOP-16747) ✗ ./dev-support/bin/shelldocs --lint -i
./hadoop-common-project/hadoop-common/src/main/bin/start-all.sh
Traceback (most recent call last):
File
"/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
line 477, in
main()
File
"/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
line 468, in main
message = funcs.lint()
File
"/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
line 273, in lint
value = getfuncs[attr]()
TypeError: 'str' object is not callable
{noformat}
> shelldocs --lint option fails
> -
>
> Key: YETUS-1099
> URL: https://issues.apache.org/jira/browse/YETUS-1099
> Project: Yetus
> Issue Type: Bug
> Components: ShellDocs
>Affects Versions: 0.13.0
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Blocker
> Time Spent: 10m
> Remaining Estimate: 0h
>
> shelldocs --lint options fails:
> {noformat}
> hadoop-mirror git:(HADOOP-16747) ✗ ./dev-support/bin/shelldocs --lint -i
> ./hadoop-common-project/hadoop-common/src/main/bin/start-all.sh
> Traceback (most recent call last):
> File
> "/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
> line 477, in
> main()
> File
> "/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
> line 468, in main
> message = funcs.lint()
> File
> "/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
> line 273, in lint
> value = getfuncs[attr]()
> TypeError: 'str' object is not callable
> {noformat}
> Here the result of "getfuncs[attr]" is "self.replacetext" and its type is
> "str" or "NoneType". These types cannot call "()" and that's why the error
> occurs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (YETUS-1099) shelldocs --lint option fails
Akira Ajisaka created YETUS-1099:
Summary: shelldocs --lint option fails
Key: YETUS-1099
URL: https://issues.apache.org/jira/browse/YETUS-1099
Project: Yetus
Issue Type: Improvement
Components: ShellDocs
Affects Versions: 0.13.0
Reporter: Akira Ajisaka
Assignee: Akira Ajisaka
shelldocs --lint options fails:
{noformat}
hadoop-mirror git:(HADOOP-16747) ✗ ./dev-support/bin/shelldocs --lint -i
./hadoop-common-project/hadoop-common/src/main/bin/start-all.sh
Traceback (most recent call last):
File
"/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
line 477, in
main()
File
"/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
line 468, in main
message = funcs.lint()
File
"/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
line 273, in lint
value = getfuncs[attr]()
TypeError: 'str' object is not callable
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (YETUS-1099) shelldocs --lint option fails
[
https://issues.apache.org/jira/browse/YETUS-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated YETUS-1099:
-
Issue Type: Bug (was: Improvement)
> shelldocs --lint option fails
> -
>
> Key: YETUS-1099
> URL: https://issues.apache.org/jira/browse/YETUS-1099
> Project: Yetus
> Issue Type: Bug
> Components: ShellDocs
>Affects Versions: 0.13.0
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Blocker
>
> shelldocs --lint options fails:
> {noformat}
> hadoop-mirror git:(HADOOP-16747) ✗ ./dev-support/bin/shelldocs --lint -i
> ./hadoop-common-project/hadoop-common/src/main/bin/start-all.sh
> Traceback (most recent call last):
> File
> "/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
> line 477, in
> main()
> File
> "/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
> line 468, in main
> message = funcs.lint()
> File
> "/Users/aajisaka/git/hadoop-mirror/patchprocess/apache-yetus-0.13.0/bin/../lib/shelldocs/shelldocs.py",
> line 273, in lint
> value = getfuncs[attr]()
> TypeError: 'str' object is not callable
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (YETUS-1094) Load the personality file before loading plugins
[ https://issues.apache.org/jira/browse/YETUS-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YETUS-1094. -- Resolution: Won't Fix According to the comments in the PR, "personality_plugins" should not be used and it will be removed in the future. The plugins should be set by "--plugins" option instead. Closing. > Load the personality file before loading plugins > > > Key: YETUS-1094 > URL: https://issues.apache.org/jira/browse/YETUS-1094 > Project: Yetus > Issue Type: Bug > Components: Precommit >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Blocker > Time Spent: 40m > Remaining Estimate: 0h > > The plugins written in the personality file are not loaded while trying > 0.13.0-RC4. https://gist.github.com/aajisaka/aca2e08ba91d1a13466f40abb4c87bd5 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (YETUS-1094) Load the personality file before loading plugins
[ https://issues.apache.org/jira/browse/YETUS-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YETUS-1094: - Summary: Load the personality file before loading plugins (was: Load the personality file at first) > Load the personality file before loading plugins > > > Key: YETUS-1094 > URL: https://issues.apache.org/jira/browse/YETUS-1094 > Project: Yetus > Issue Type: Bug > Components: Precommit >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Blocker > Time Spent: 10m > Remaining Estimate: 0h > > The plugins written in the personality file are not loaded while trying > 0.13.0-RC4. https://gist.github.com/aajisaka/aca2e08ba91d1a13466f40abb4c87bd5 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (YETUS-1094) Load the personality file at first
Akira Ajisaka created YETUS-1094: Summary: Load the personality file at first Key: YETUS-1094 URL: https://issues.apache.org/jira/browse/YETUS-1094 Project: Yetus Issue Type: Bug Components: Precommit Reporter: Akira Ajisaka Assignee: Akira Ajisaka The plugins written in the personality file are not loaded while trying 0.13.0-RC4. https://gist.github.com/aajisaka/aca2e08ba91d1a13466f40abb4c87bd5 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (YETUS-1077) Remove jython completely
[ https://issues.apache.org/jira/browse/YETUS-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YETUS-1077. -- Fix Version/s: 0.14.0 Assignee: Akira Ajisaka Resolution: Fixed Committed to main. > Remove jython completely > > > Key: YETUS-1077 > URL: https://issues.apache.org/jira/browse/YETUS-1077 > Project: Yetus > Issue Type: Task > Components: build >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > Fix For: 0.14.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Follow-up task of YETUS-1046. Jython is still in LICENSE and pom.xml. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (YETUS-1077) Remove jython completely
Akira Ajisaka created YETUS-1077: Summary: Remove jython completely Key: YETUS-1077 URL: https://issues.apache.org/jira/browse/YETUS-1077 Project: Yetus Issue Type: Task Components: build Reporter: Akira Ajisaka Follow-up task of YETUS-1046. Jython is still in LICENSE and pom.xml. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-1059) Bring back github comments mode
[ https://issues.apache.org/jira/browse/YETUS-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223412#comment-17223412 ] Akira Ajisaka commented on YETUS-1059: -- Agreed. I saw GitHub Status only successes from Yetus in https://github.com/apache/hadoop/pull/2348 I'll test and check the status failures from Yetus. Thanks. > Bring back github comments mode > --- > > Key: YETUS-1059 > URL: https://issues.apache.org/jira/browse/YETUS-1059 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Affects Versions: 0.13.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > > Github insists that app tokens are only good for an hour which makes them > useless for incredibly large projects or incredibly broken repositories. On > systems that don't have a way to programmatically get a new token (looking at > you, Jenkins), test-patch fails to write statuses. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-1059) Bring back github comments mode
[ https://issues.apache.org/jira/browse/YETUS-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223409#comment-17223409 ] Akira Ajisaka commented on YETUS-1059: -- Can we add an option to always write the comment instead of updating the commit status? Adding comments seems better for Apache Hadoop developers for now (HADOOP-17297). > Bring back github comments mode > --- > > Key: YETUS-1059 > URL: https://issues.apache.org/jira/browse/YETUS-1059 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Affects Versions: 0.13.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > > Github insists that app tokens are only good for an hour which makes them > useless for incredibly large projects or incredibly broken repositories. On > systems that don't have a way to programmatically get a new token (looking at > you, Jenkins), test-patch fails to write statuses. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (YETUS-1010) Add git...@yetus.apache.org in the web site
Akira Ajisaka created YETUS-1010: Summary: Add git...@yetus.apache.org in the web site Key: YETUS-1010 URL: https://issues.apache.org/jira/browse/YETUS-1010 Project: Yetus Issue Type: Bug Components: website and documentation Reporter: Akira Ajisaka git...@yetus.apache.org is used for GitHub notifications but not listed in https://yetus.apache.org/mailinglists/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Moved] (YETUS-1009) Variable url is declared twice in github_finalreport function
[
https://issues.apache.org/jira/browse/YETUS-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka moved HADOOP-17291 to YETUS-1009:
---
Component/s: (was: precommit)
Precommit
Key: YETUS-1009 (was: HADOOP-17291)
Project: Yetus (was: Hadoop Common)
> Variable url is declared twice in github_finalreport function
> -
>
> Key: YETUS-1009
> URL: https://issues.apache.org/jira/browse/YETUS-1009
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
>Reporter: Akira Ajisaka
>Priority: Minor
> Labels: newbie
>
> https://github.com/apache/yetus/blob/b4c3c5f08eec06aaf8955cd4022043d772e14258/precommit/src/main/shell/test-patch.d/github.sh#L739-L742
> {code}
> declare url
> declare logurl
> declare comment
> declare url
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (YETUS-1008) Add .asf.yaml to allow GitHub to JIRA integration
[ https://issues.apache.org/jira/browse/YETUS-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned YETUS-1008: Assignee: Akira Ajisaka > Add .asf.yaml to allow GitHub to JIRA integration > - > > Key: YETUS-1008 > URL: https://issues.apache.org/jira/browse/YETUS-1008 > Project: Yetus > Issue Type: Improvement > Components: build >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > > Adding .asf.yaml to create GitHub PR links to the corresponding JIRA issues > automatically. > This is similar to HADOOP-17234 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (YETUS-1007) Logging when adding GitHub commit statuses
[ https://issues.apache.org/jira/browse/YETUS-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned YETUS-1007: Assignee: Akira Ajisaka > Logging when adding GitHub commit statuses > -- > > Key: YETUS-1007 > URL: https://issues.apache.org/jira/browse/YETUS-1007 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Major > > There are no error messages in the console when test-patch fails to add > GitHub commit status for some reason. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (YETUS-1007) Logging when adding GitHub commit statuses
[ https://issues.apache.org/jira/browse/YETUS-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YETUS-1007: - Summary: Logging when adding GitHub commit statuses (was: Logging when adding GitHub commit status) > Logging when adding GitHub commit statuses > -- > > Key: YETUS-1007 > URL: https://issues.apache.org/jira/browse/YETUS-1007 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Reporter: Akira Ajisaka >Priority: Major > > There are no error messages in the console when test-patch fails to add > GitHub commit status for some reason. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (YETUS-1008) Add .asf.yaml to allow GitHub to JIRA integration
Akira Ajisaka created YETUS-1008: Summary: Add .asf.yaml to allow GitHub to JIRA integration Key: YETUS-1008 URL: https://issues.apache.org/jira/browse/YETUS-1008 Project: Yetus Issue Type: Improvement Components: build Reporter: Akira Ajisaka Adding .asf.yaml to create GitHub PR links to the corresponding JIRA issues automatically. This is similar to HADOOP-17234 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (YETUS-1007) Logging when adding GitHub commit status
Akira Ajisaka created YETUS-1007: Summary: Logging when adding GitHub commit status Key: YETUS-1007 URL: https://issues.apache.org/jira/browse/YETUS-1007 Project: Yetus Issue Type: Improvement Components: Precommit Reporter: Akira Ajisaka There are no error messages in the console when test-patch fails to add GitHub commit status for some reason. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (YETUS-977) docker.sh fails to add environment variables that contains spaces
[ https://issues.apache.org/jira/browse/YETUS-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YETUS-977. - Resolution: Invalid Rethinking this, it does not fail. > docker.sh fails to add environment variables that contains spaces > - > > Key: YETUS-977 > URL: https://issues.apache.org/jira/browse/YETUS-977 > Project: Yetus > Issue Type: Bug > Components: Precommit >Reporter: Akira Ajisaka >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (YETUS-977) docker.sh fails to add environment variables that contains spaces
Akira Ajisaka created YETUS-977: --- Summary: docker.sh fails to add environment variables that contains spaces Key: YETUS-977 URL: https://issues.apache.org/jira/browse/YETUS-977 Project: Yetus Issue Type: Bug Components: Precommit Reporter: Akira Ajisaka -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (YETUS-976) MAVEN_OPTS in Dockerfile is not honored
[
https://issues.apache.org/jira/browse/YETUS-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka reassigned YETUS-976:
---
Assignee: Akira Ajisaka
> MAVEN_OPTS in Dockerfile is not honored
> ---
>
> Key: YETUS-976
> URL: https://issues.apache.org/jira/browse/YETUS-976
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
>
> In Hadoop branch-2.10 {{MAVEN_OPTS}} is set as follows:
> {noformat}
> ENV MAVEN_OPTS -Xms256m -Xmx1536m -Dhttps.protocols=TLSv1.2
> -Dhttps.cipherSuites=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
> {noformat}
> but facing the following error in build:
> {noformat}
> [ERROR] Unresolveable build extension: Plugin
> org.apache.felix:maven-bundle-plugin:2.5.0 or one of its dependencies could
> not be resolved: Failed to read artifact descriptor for
> org.apache.felix:maven-bundle-plugin:jar:2.5.0: Could not transfer artifact
> org.apache.felix:maven-bundle-plugin:pom:2.5.0 from/to central
> (https://repo.maven.apache.org/maven2): Received fatal alert:
> protocol_version -> [Help 2]
> {noformat}
> It seems that {{-Dhttps.protocols=TLSv1.2}} is not in {{MAVEN_OPTS}}.
> https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/3/artifact/out/patch-mvninstall-root.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (YETUS-976) MAVEN_OPTS in Dockerfile is not honored
Akira Ajisaka created YETUS-976:
---
Summary: MAVEN_OPTS in Dockerfile is not honored
Key: YETUS-976
URL: https://issues.apache.org/jira/browse/YETUS-976
Project: Yetus
Issue Type: Bug
Components: Precommit
Reporter: Akira Ajisaka
In Hadoop branch-2.10 {{MAVEN_OPTS}} is set as follows:
{noformat}
ENV MAVEN_OPTS -Xms256m -Xmx1536m -Dhttps.protocols=TLSv1.2
-Dhttps.cipherSuites=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
{noformat}
but facing the following error in build:
{noformat}
[ERROR] Unresolveable build extension: Plugin
org.apache.felix:maven-bundle-plugin:2.5.0 or one of its dependencies could not
be resolved: Failed to read artifact descriptor for
org.apache.felix:maven-bundle-plugin:jar:2.5.0: Could not transfer artifact
org.apache.felix:maven-bundle-plugin:pom:2.5.0 from/to central
(https://repo.maven.apache.org/maven2): Received fatal alert: protocol_version
-> [Help 2]
{noformat}
It seems that {{-Dhttps.protocols=TLSv1.2}} is not in {{MAVEN_OPTS}}.
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/3/artifact/out/patch-mvninstall-root.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (YETUS-974) start-build-env.sh fails
[
https://issues.apache.org/jira/browse/YETUS-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated YETUS-974:
Component/s: (was: Precommit)
build
> start-build-env.sh fails
>
>
> Key: YETUS-974
> URL: https://issues.apache.org/jira/browse/YETUS-974
> Project: Yetus
> Issue Type: Bug
> Components: build
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Critical
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> Exception information:
> Traceback (most recent call last):
> File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 209, in
> main
> status = self.run(options, args)
> File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 335,
> in run
> prefix=options.prefix_path,
> File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 732, in
> install
> **kwargs
> File "/usr/lib/python2.7/dist-packages/pip/req/req_install.py", line 886,
> in install
> spinner=spinner,
> File "/usr/lib/python2.7/dist-packages/pip/utils/__init__.py", line 736, in
> call_subprocess
> % (command_desc, proc.returncode, cwd))
> InstallationError: Command "/usr/bin/python -u -c "import setuptools,
> tokenize;__file__='/tmp/pip-build-zR9pmu/isort/setup.py';exec(compile(getattr(tokenize,
> 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))"
> install --record /tmp/pip-MhGoG4-record/install-record.txt
> --single-version-externally-managed --compile" failed with error code 1 in
> /tmp/pip-build-zR9pmu/isort/
> Converted retries value: Retry(total=0, connect=None, read=None,
> redirect=None) -> Retry(total=Retry(total=0, connect=None, read=None,
> redirect=None), connect=None, read=None, redirect=None)
> Converted retries value: Retry(total=0, connect=None, read=None,
> redirect=None) -> Retry(total=Retry(total=0, connect=None, read=None,
> redirect=None), connect=None, read=None, redirect=None)
> Starting new HTTPS connection (1): pypi.python.org
> "GET /pypi/pip/json HTTP/1.1" 301 122
> Starting new HTTPS connection (1): pypi.org
> "GET /pypi/pip/json HTTP/1.1" 200 23544
> You are using pip version 8.1.1, however version 20.1.1 is available.
> You should consider upgrading via the 'pip install --upgrade pip' command.
> The command '/bin/bash -o pipefail -c pip2 install -v astroid==1.6.5
>configparser==4.0.2 pylint==1.9.2
> python-dateutil==2.7.3 && rm -rf /root/.cache' returned a non-zero code: 1
> {noformat}
> Recently isort 5.0.0 is released and dropped Python 2 support.
> https://timothycrosley.github.io/isort/docs/major_releases/introducing_isort_5/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (YETUS-974) start-build-env.sh fails
Akira Ajisaka created YETUS-974:
---
Summary: start-build-env.sh fails
Key: YETUS-974
URL: https://issues.apache.org/jira/browse/YETUS-974
Project: Yetus
Issue Type: Bug
Components: Precommit
Reporter: Akira Ajisaka
Assignee: Akira Ajisaka
{noformat}
Exception information:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 209, in main
status = self.run(options, args)
File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 335, in
run
prefix=options.prefix_path,
File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 732, in
install
**kwargs
File "/usr/lib/python2.7/dist-packages/pip/req/req_install.py", line 886, in
install
spinner=spinner,
File "/usr/lib/python2.7/dist-packages/pip/utils/__init__.py", line 736, in
call_subprocess
% (command_desc, proc.returncode, cwd))
InstallationError: Command "/usr/bin/python -u -c "import setuptools,
tokenize;__file__='/tmp/pip-build-zR9pmu/isort/setup.py';exec(compile(getattr(tokenize,
'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))"
install --record /tmp/pip-MhGoG4-record/install-record.txt
--single-version-externally-managed --compile" failed with error code 1 in
/tmp/pip-build-zR9pmu/isort/
Converted retries value: Retry(total=0, connect=None, read=None, redirect=None)
-> Retry(total=Retry(total=0, connect=None, read=None, redirect=None),
connect=None, read=None, redirect=None)
Converted retries value: Retry(total=0, connect=None, read=None, redirect=None)
-> Retry(total=Retry(total=0, connect=None, read=None, redirect=None),
connect=None, read=None, redirect=None)
Starting new HTTPS connection (1): pypi.python.org
"GET /pypi/pip/json HTTP/1.1" 301 122
Starting new HTTPS connection (1): pypi.org
"GET /pypi/pip/json HTTP/1.1" 200 23544
You are using pip version 8.1.1, however version 20.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
The command '/bin/bash -o pipefail -c pip2 install -v astroid==1.6.5
configparser==4.0.2 pylint==1.9.2 python-dateutil==2.7.3
&& rm -rf /root/.cache' returned a non-zero code: 1
{noformat}
Recently isort 5.0.0 is released and dropped Python 2 support.
https://timothycrosley.github.io/isort/docs/major_releases/introducing_isort_5/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (YETUS-967) Switch everything to https://downloads.apache.org
[ https://issues.apache.org/jira/browse/YETUS-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150097#comment-17150097 ] Akira Ajisaka commented on YETUS-967: - Hi [~aw], can I take this issue over? I created a patch, and after that, I found that you are already assigned. > Switch everything to https://downloads.apache.org > - > > Key: YETUS-967 > URL: https://issues.apache.org/jira/browse/YETUS-967 > Project: Yetus > Issue Type: Improvement > Components: build, website and documentation >Affects Versions: 0.12.0, 0.13.0 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > > https://downloads.apache.org has replaced https://www.apache.org/dist -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (YETUS-972) Make javadoc phase and goal configurable in maven.sh
[
https://issues.apache.org/jira/browse/YETUS-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka reassigned YETUS-972:
---
Assignee: Akira Ajisaka
> Make javadoc phase and goal configurable in maven.sh
>
>
> Key: YETUS-972
> URL: https://issues.apache.org/jira/browse/YETUS-972
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
>
> In maven javadoc tests, the command is hard-coded to {{mvn javadoc:javadoc}}.
> HDFS-15424 requires {{mvn process-sources javadoc:javadoc-no-fork}} command
> and I'd like to make the goal and the phase configurable.
> Please see HDFS-15424 for the detail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (YETUS-972) Make javadoc phase and goal configurable in maven.sh
Akira Ajisaka created YETUS-972:
---
Summary: Make javadoc phase and goal configurable in maven.sh
Key: YETUS-972
URL: https://issues.apache.org/jira/browse/YETUS-972
Project: Yetus
Issue Type: Bug
Components: Precommit
Reporter: Akira Ajisaka
In maven javadoc tests, the command is hard-coded to {{mvn javadoc:javadoc}}.
HDFS-15424 requires {{mvn process-sources javadoc:javadoc-no-fork}} command and
I'd like to make the goal and the phase configurable.
Please see HDFS-15424 for the detail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (YETUS-959) Dead link in precommit-advanced
[ https://issues.apache.org/jira/browse/YETUS-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17074760#comment-17074760 ] Akira Ajisaka commented on YETUS-959: - Generated and pushed document: https://github.com/apache/yetus/commit/cf89b022d26a084e77962ff12843129560e266c5 The dead links have been fixed: https://yetus.apache.org/documentation/in-progress/precommit-advanced/ > Dead link in precommit-advanced > --- > > Key: YETUS-959 > URL: https://issues.apache.org/jira/browse/YETUS-959 > Project: Yetus > Issue Type: Bug > Components: website and documentation >Affects Versions: 0.11.1 >Reporter: Nick Dimiduk >Assignee: Akira Ajisaka >Priority: Major > Fix For: 0.12.0 > > Time Spent: 2h > Remaining Estimate: 0h > > On [precommit-advanced > |https://yetus.apache.org/documentation/0.11.1/precommit-advanced/], down > under Personalities > Module & Profile Determination, there's a link > [modules|https://yetus.apache.org/documentation/0.11.1/precommit-advanced/precommit-glossary.md#genericoutside-definitions] > that returns a 404. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (YETUS-947) Support github actions as a robot
[ https://issues.apache.org/jira/browse/YETUS-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YETUS-947: Component/s: build > Support github actions as a robot > - > > Key: YETUS-947 > URL: https://issues.apache.org/jira/browse/YETUS-947 > Project: Yetus > Issue Type: New Feature > Components: build >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.12.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Github Actions should be looked at and added as a robot if it works out ok. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (YETUS-895) Add ZStandard Compression support in Hadoop precommit
[ https://issues.apache.org/jira/browse/YETUS-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YETUS-895: Component/s: Precommit > Add ZStandard Compression support in Hadoop precommit > - > > Key: YETUS-895 > URL: https://issues.apache.org/jira/browse/YETUS-895 > Project: Yetus > Issue Type: Improvement > Components: Precommit >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Major > Fix For: 0.12.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > ZStandard Compression is gaining traction. Hadoop has ZStandard Compression > codec support but it appears Yetus precommit personality for Hadoop doesn't > yet support it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (YETUS-942) yetus-dl for specific versions is broken
[ https://issues.apache.org/jira/browse/YETUS-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YETUS-942: Component/s: build > yetus-dl for specific versions is broken > > > Key: YETUS-942 > URL: https://issues.apache.org/jira/browse/YETUS-942 > Project: Yetus > Issue Type: Bug > Components: build >Affects Versions: 0.11.0, 0.11.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Blocker > Fix For: 0.12.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Looks like they've removed the asc files from the mirrors for some reason, so > now yetus-dl doesn't work. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-960) Yetus build env cannot execute pylint2
[
https://issues.apache.org/jira/browse/YETUS-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071102#comment-17071102
]
Akira Ajisaka commented on YETUS-960:
-
This issue is broken by the latest version of configparser, not broken by
YETUS-955.
> Yetus build env cannot execute pylint2
> --
>
> Key: YETUS-960
> URL: https://issues.apache.org/jira/browse/YETUS-960
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Critical
>
> {noformat}
> $ ./start-build-env.sh
> (snip)
> aajisaka@9035ba61ece3:~/yetus$ pylint2
> Traceback (most recent call last):
> File "/usr/local/bin/pylint2", line 11, in
> sys.exit(run_pylint())
> File "/usr/local/lib/python2.7/dist-packages/pylint/__init__.py", line 15,
> in run_pylint
> from pylint.lint import Run
> File "/usr/local/lib/python2.7/dist-packages/pylint/lint.py", line 67, in
>
> from pylint import checkers
> File "/usr/local/lib/python2.7/dist-packages/pylint/checkers/__init__.py",
> line 45, in
> from pylint.config import OptionsProviderMixIn
> File "/usr/local/lib/python2.7/dist-packages/pylint/config.py", line 49, in
>
> import configparser
> ImportError: No module named configparser
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (YETUS-960) Yetus build env cannot execute pylint2
[
https://issues.apache.org/jira/browse/YETUS-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka reassigned YETUS-960:
---
Assignee: Akira Ajisaka
> Yetus build env cannot execute pylint2
> --
>
> Key: YETUS-960
> URL: https://issues.apache.org/jira/browse/YETUS-960
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Critical
>
> {noformat}
> $ ./start-build-env.sh
> (snip)
> aajisaka@9035ba61ece3:~/yetus$ pylint2
> Traceback (most recent call last):
> File "/usr/local/bin/pylint2", line 11, in
> sys.exit(run_pylint())
> File "/usr/local/lib/python2.7/dist-packages/pylint/__init__.py", line 15,
> in run_pylint
> from pylint.lint import Run
> File "/usr/local/lib/python2.7/dist-packages/pylint/lint.py", line 67, in
>
> from pylint import checkers
> File "/usr/local/lib/python2.7/dist-packages/pylint/checkers/__init__.py",
> line 45, in
> from pylint.config import OptionsProviderMixIn
> File "/usr/local/lib/python2.7/dist-packages/pylint/config.py", line 49, in
>
> import configparser
> ImportError: No module named configparser
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (YETUS-955) Update many of the binaries in Dockerfile
[ https://issues.apache.org/jira/browse/YETUS-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071092#comment-17071092 ] Akira Ajisaka edited comment on YETUS-955 at 3/30/20, 4:02 PM: --- pip2 wants to install configparser as the dependency of pylint but the latest version (5.0.0) but the version is only for Python 3.6+. Setting the version to 4.0.2 should work. was (Author: ajisakaa): pip2 wants to install configparser but the latest version (5.0.0) but the version is only for Python 3.6+. Setting the version to 4.0.2 should work. > Update many of the binaries in Dockerfile > - > > Key: YETUS-955 > URL: https://issues.apache.org/jira/browse/YETUS-955 > Project: Yetus > Issue Type: New Feature > Components: build, Precommit >Affects Versions: 0.11.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.12.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > We haven't updated the Dockerfile in a while, so probably time to do that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (YETUS-955) Update many of the binaries in Dockerfile
[ https://issues.apache.org/jira/browse/YETUS-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YETUS-955: Comment: was deleted (was: pip2 wants to install configparser as the dependency of pylint but the latest version (5.0.0) is only for Python 3.6+. Setting the version to 4.0.2 should work.) > Update many of the binaries in Dockerfile > - > > Key: YETUS-955 > URL: https://issues.apache.org/jira/browse/YETUS-955 > Project: Yetus > Issue Type: New Feature > Components: build, Precommit >Affects Versions: 0.11.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.12.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > We haven't updated the Dockerfile in a while, so probably time to do that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-960) Yetus build env cannot execute pylint2
[
https://issues.apache.org/jira/browse/YETUS-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071093#comment-17071093
]
Akira Ajisaka commented on YETUS-960:
-
pip2 wants to install configparser as the dependency of pylint but the latest
version (5.0.0) is only for Python 3.6+. Setting the version to 4.0.2 should
work.
> Yetus build env cannot execute pylint2
> --
>
> Key: YETUS-960
> URL: https://issues.apache.org/jira/browse/YETUS-960
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
>Reporter: Akira Ajisaka
>Priority: Critical
>
> {noformat}
> $ ./start-build-env.sh
> (snip)
> aajisaka@9035ba61ece3:~/yetus$ pylint2
> Traceback (most recent call last):
> File "/usr/local/bin/pylint2", line 11, in
> sys.exit(run_pylint())
> File "/usr/local/lib/python2.7/dist-packages/pylint/__init__.py", line 15,
> in run_pylint
> from pylint.lint import Run
> File "/usr/local/lib/python2.7/dist-packages/pylint/lint.py", line 67, in
>
> from pylint import checkers
> File "/usr/local/lib/python2.7/dist-packages/pylint/checkers/__init__.py",
> line 45, in
> from pylint.config import OptionsProviderMixIn
> File "/usr/local/lib/python2.7/dist-packages/pylint/config.py", line 49, in
>
> import configparser
> ImportError: No module named configparser
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (YETUS-955) Update many of the binaries in Dockerfile
[ https://issues.apache.org/jira/browse/YETUS-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071092#comment-17071092 ] Akira Ajisaka edited comment on YETUS-955 at 3/30/20, 4:02 PM: --- pip2 wants to install configparser as the dependency of pylint but the latest version (5.0.0) is only for Python 3.6+. Setting the version to 4.0.2 should work. was (Author: ajisakaa): pip2 wants to install configparser as the dependency of pylint but the latest version (5.0.0) but the version is only for Python 3.6+. Setting the version to 4.0.2 should work. > Update many of the binaries in Dockerfile > - > > Key: YETUS-955 > URL: https://issues.apache.org/jira/browse/YETUS-955 > Project: Yetus > Issue Type: New Feature > Components: build, Precommit >Affects Versions: 0.11.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.12.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > We haven't updated the Dockerfile in a while, so probably time to do that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-955) Update many of the binaries in Dockerfile
[ https://issues.apache.org/jira/browse/YETUS-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071092#comment-17071092 ] Akira Ajisaka commented on YETUS-955: - pip2 wants to install configparser but the latest version (5.0.0) but the version is only for Python 3.6+. Setting the version to 4.0.2 should work. > Update many of the binaries in Dockerfile > - > > Key: YETUS-955 > URL: https://issues.apache.org/jira/browse/YETUS-955 > Project: Yetus > Issue Type: New Feature > Components: build, Precommit >Affects Versions: 0.11.1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 0.12.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > We haven't updated the Dockerfile in a while, so probably time to do that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (YETUS-960) Yetus build env cannot execute pylint2
Akira Ajisaka created YETUS-960:
---
Summary: Yetus build env cannot execute pylint2
Key: YETUS-960
URL: https://issues.apache.org/jira/browse/YETUS-960
Project: Yetus
Issue Type: Bug
Reporter: Akira Ajisaka
{noformat}
$ ./start-build-env.sh
(snip)
aajisaka@9035ba61ece3:~/yetus$ pylint2
Traceback (most recent call last):
File "/usr/local/bin/pylint2", line 11, in
sys.exit(run_pylint())
File "/usr/local/lib/python2.7/dist-packages/pylint/__init__.py", line 15, in
run_pylint
from pylint.lint import Run
File "/usr/local/lib/python2.7/dist-packages/pylint/lint.py", line 67, in
from pylint import checkers
File "/usr/local/lib/python2.7/dist-packages/pylint/checkers/__init__.py",
line 45, in
from pylint.config import OptionsProviderMixIn
File "/usr/local/lib/python2.7/dist-packages/pylint/config.py", line 49, in
import configparser
ImportError: No module named configparser
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (YETUS-960) Yetus build env cannot execute pylint2
[
https://issues.apache.org/jira/browse/YETUS-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated YETUS-960:
Component/s: Precommit
> Yetus build env cannot execute pylint2
> --
>
> Key: YETUS-960
> URL: https://issues.apache.org/jira/browse/YETUS-960
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
>Reporter: Akira Ajisaka
>Priority: Critical
>
> {noformat}
> $ ./start-build-env.sh
> (snip)
> aajisaka@9035ba61ece3:~/yetus$ pylint2
> Traceback (most recent call last):
> File "/usr/local/bin/pylint2", line 11, in
> sys.exit(run_pylint())
> File "/usr/local/lib/python2.7/dist-packages/pylint/__init__.py", line 15,
> in run_pylint
> from pylint.lint import Run
> File "/usr/local/lib/python2.7/dist-packages/pylint/lint.py", line 67, in
>
> from pylint import checkers
> File "/usr/local/lib/python2.7/dist-packages/pylint/checkers/__init__.py",
> line 45, in
> from pylint.config import OptionsProviderMixIn
> File "/usr/local/lib/python2.7/dist-packages/pylint/config.py", line 49, in
>
> import configparser
> ImportError: No module named configparser
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (YETUS-895) Add ZStandard Compression support in Hadoop precommit
[ https://issues.apache.org/jira/browse/YETUS-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned YETUS-895: --- Assignee: Akira Ajisaka > Add ZStandard Compression support in Hadoop precommit > - > > Key: YETUS-895 > URL: https://issues.apache.org/jira/browse/YETUS-895 > Project: Yetus > Issue Type: Improvement >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Major > > ZStandard Compression is gaining traction. Hadoop has ZStandard Compression > codec support but it appears Yetus precommit personality for Hadoop doesn't > yet support it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (YETUS-804) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/YETUS-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reopened YETUS-804: - > Please delete old releases from mirroring system > > > Key: YETUS-804 > URL: https://issues.apache.org/jira/browse/YETUS-804 > Project: Yetus > Issue Type: Bug >Reporter: Sebb >Priority: Major > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > i.e. 0.6.0, 0.7.0, 0.8.0 > It's unfair to expect the 3rd party mirrors to carry old releases. > However you can still link to the archives for historic releases. > Please also update your release procedures (if relevant) > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (YETUS-804) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/YETUS-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YETUS-804. - Resolution: Done > Please delete old releases from mirroring system > > > Key: YETUS-804 > URL: https://issues.apache.org/jira/browse/YETUS-804 > Project: Yetus > Issue Type: Bug >Reporter: Sebb >Priority: Major > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > i.e. 0.6.0, 0.7.0, 0.8.0 > It's unfair to expect the 3rd party mirrors to carry old releases. > However you can still link to the archives for historic releases. > Please also update your release procedures (if relevant) > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (YETUS-804) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/YETUS-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YETUS-804. - Resolution: Not A Problem Closing. > Please delete old releases from mirroring system > > > Key: YETUS-804 > URL: https://issues.apache.org/jira/browse/YETUS-804 > Project: Yetus > Issue Type: Bug >Reporter: Sebb >Priority: Major > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > i.e. 0.6.0, 0.7.0, 0.8.0 > It's unfair to expect the 3rd party mirrors to carry old releases. > However you can still link to the archives for historic releases. > Please also update your release procedures (if relevant) > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-804) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/YETUS-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070873#comment-17070873 ] Akira Ajisaka commented on YETUS-804: - bq. Please also update your release procedures (if relevant) Already updated by YETUS-226 > Please delete old releases from mirroring system > > > Key: YETUS-804 > URL: https://issues.apache.org/jira/browse/YETUS-804 > Project: Yetus > Issue Type: Bug >Reporter: Sebb >Priority: Major > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > i.e. 0.6.0, 0.7.0, 0.8.0 > It's unfair to expect the 3rd party mirrors to carry old releases. > However you can still link to the archives for historic releases. > Please also update your release procedures (if relevant) > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-804) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/YETUS-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070862#comment-17070862 ] Akira Ajisaka commented on YETUS-804: - 0.6.0, 0.7.0, and 0.8.0 have been removed. https://downloads.apache.org/yetus/ > Please delete old releases from mirroring system > > > Key: YETUS-804 > URL: https://issues.apache.org/jira/browse/YETUS-804 > Project: Yetus > Issue Type: Bug >Reporter: Sebb >Priority: Major > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > i.e. 0.6.0, 0.7.0, 0.8.0 > It's unfair to expect the 3rd party mirrors to carry old releases. > However you can still link to the archives for historic releases. > Please also update your release procedures (if relevant) > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (YETUS-958) precommit-basic docs contains merge conflict marker
[ https://issues.apache.org/jira/browse/YETUS-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned YETUS-958: --- Assignee: Akira Ajisaka > precommit-basic docs contains merge conflict marker > --- > > Key: YETUS-958 > URL: https://issues.apache.org/jira/browse/YETUS-958 > Project: Yetus > Issue Type: Bug > Components: website and documentation >Affects Versions: 0.11.1 >Reporter: Nick Dimiduk >Assignee: Akira Ajisaka >Priority: Major > Attachments: Screen Shot 2020-03-26 at 3.54.03 PM.png > > > Down at the bottom of > [precommit-basic|http://yetus.apache.org/documentation/0.11.1/precommit-basic/], > in the Docker section, there are merge conflict markers that appear to have > come in with YETUS-109. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (YETUS-959) Dead link in precommit-advanced
[ https://issues.apache.org/jira/browse/YETUS-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned YETUS-959: --- Assignee: Akira Ajisaka > Dead link in precommit-advanced > --- > > Key: YETUS-959 > URL: https://issues.apache.org/jira/browse/YETUS-959 > Project: Yetus > Issue Type: Bug > Components: website and documentation >Affects Versions: 0.11.1 >Reporter: Nick Dimiduk >Assignee: Akira Ajisaka >Priority: Major > > On [precommit-advanced > |https://yetus.apache.org/documentation/0.11.1/precommit-advanced/], down > under Personalities > Module & Profile Determination, there's a link > [modules|https://yetus.apache.org/documentation/0.11.1/precommit-advanced/precommit-glossary.md#genericoutside-definitions] > that returns a 404. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-933) Release 0.12.0
[ https://issues.apache.org/jira/browse/YETUS-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070760#comment-17070760 ] Akira Ajisaka commented on YETUS-933: - Hi [~busbey], how is the release process going? > Release 0.12.0 > -- > > Key: YETUS-933 > URL: https://issues.apache.org/jira/browse/YETUS-933 > Project: Yetus > Issue Type: Task > Components: website and documentation >Affects Versions: 0.12.0 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 0.12.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (YETUS-957) maven.sh fails to parse maven version
[ https://issues.apache.org/jira/browse/YETUS-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YETUS-957: Summary: maven.sh fails to parse maven version (was: maven.sh fails to parse maven_version) > maven.sh fails to parse maven version > - > > Key: YETUS-957 > URL: https://issues.apache.org/jira/browse/YETUS-957 > Project: Yetus > Issue Type: Bug > Components: Precommit > Environment: Maven 3.5.0 or upper (After MNG-3507) >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Critical > Fix For: 0.12.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > In the recent version of Maven, "mvn version" contains control character and > failed to parse the version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-957) maven.sh fails to parse maven_version
[ https://issues.apache.org/jira/browse/YETUS-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17067353#comment-17067353 ] Akira Ajisaka commented on YETUS-957: - I tried Maven 3.7.0-SNAPSHOT and '-B' option. It worked as expected. > maven.sh fails to parse maven_version > - > > Key: YETUS-957 > URL: https://issues.apache.org/jira/browse/YETUS-957 > Project: Yetus > Issue Type: Bug > Components: Precommit > Environment: Maven 3.5.0 or upper (After MNG-3507) >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Critical > Time Spent: 10m > Remaining Estimate: 0h > > In the recent version of Maven, "mvn version" contains control character and > failed to parse the version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-957) maven.sh fails to parse maven_version
[
https://issues.apache.org/jira/browse/YETUS-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17067337#comment-17067337
]
Akira Ajisaka commented on YETUS-957:
-
Thanks [~michael-o] and [~aw] for your comments!
* I'd like to work around this issue in Maven 3.5.x and 3.6.x because Yetus
cannot force the maven versions of the users.
* I'll add ${MAVEN_ARGS[@]} to include '--batch-mode' option.
> maven.sh fails to parse maven_version
> -
>
> Key: YETUS-957
> URL: https://issues.apache.org/jira/browse/YETUS-957
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
> Environment: Maven 3.5.0 or upper (After MNG-3507)
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Critical
>
> In the recent version of Maven, "mvn version" contains control character and
> failed to parse the version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (YETUS-957) maven.sh fails to parse maven_version
[ https://issues.apache.org/jira/browse/YETUS-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned YETUS-957: --- Assignee: Akira Ajisaka > maven.sh fails to parse maven_version > - > > Key: YETUS-957 > URL: https://issues.apache.org/jira/browse/YETUS-957 > Project: Yetus > Issue Type: Bug > Components: Precommit > Environment: Maven 3.5.0 or upper (After MNG-3507) >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka >Priority: Critical > > In the recent version of Maven, "mvn version" contains control character and > failed to parse the version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-957) maven.sh fails to parse maven_version
[
https://issues.apache.org/jira/browse/YETUS-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17066475#comment-17066475
]
Akira Ajisaka commented on YETUS-957:
-
{noformat}
$ maven_version=$(MAVEN_OPTS="-Dorg.fusesource.jansi.Ansi.disable=true" mvn
--offline --version 2>/dev/null | head -n 1 2>/dev/null | cut -d' ' -f3
2>/dev/null)
{noformat}
or
{noformat}
$ maven_version=$(mvn --offline --version 2>/dev/null | string | head -n 1
2>/dev/null | cut -d' ' -f3 2>/dev/null)
{noformat}
seems good. I sent an email to maven-dev ML to ask the best way to handle this
issue.
> maven.sh fails to parse maven_version
> -
>
> Key: YETUS-957
> URL: https://issues.apache.org/jira/browse/YETUS-957
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
> Environment: Maven 3.5.0 or upper (After MNG-3507)
>Reporter: Akira Ajisaka
>Priority: Critical
>
> In the recent version of Maven, "mvn version" contains control character and
> failed to parse the version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (YETUS-957) maven.sh fails to parse maven_version
[ https://issues.apache.org/jira/browse/YETUS-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YETUS-957: Environment: Maven 3.5.0 or upper (After MNG-3507) (was: Maven 3.6.0+) > maven.sh fails to parse maven_version > - > > Key: YETUS-957 > URL: https://issues.apache.org/jira/browse/YETUS-957 > Project: Yetus > Issue Type: Bug > Components: Precommit > Environment: Maven 3.5.0 or upper (After MNG-3507) >Reporter: Akira Ajisaka >Priority: Critical > > In the recent version of Maven, "mvn version" contains control character and > failed to parse the version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-957) maven.sh fails to parse maven_version
[
https://issues.apache.org/jira/browse/YETUS-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17066452#comment-17066452
]
Akira Ajisaka commented on YETUS-957:
-
In Maven 3.6.0,
{noformat}
$ maven_version=$(mvn --offline --version 2>/dev/null | head -n 1 2>/dev/null)
$ maven_version=${maven_version##* }
$ echo ${maven_version} > maven_version
$ cat -v maven_version
3.6.0^[[m
{noformat}
> maven.sh fails to parse maven_version
> -
>
> Key: YETUS-957
> URL: https://issues.apache.org/jira/browse/YETUS-957
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
> Environment: Maven 3.6.0+
>Reporter: Akira Ajisaka
>Priority: Critical
>
> In the recent version of Maven, "mvn version" contains control character and
> failed to parse the version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (YETUS-957) maven.sh fails to parse maven_version
Akira Ajisaka created YETUS-957: --- Summary: maven.sh fails to parse maven_version Key: YETUS-957 URL: https://issues.apache.org/jira/browse/YETUS-957 Project: Yetus Issue Type: Bug Components: Precommit Environment: Maven 3.6.0+ Reporter: Akira Ajisaka In the recent version of Maven, "mvn version" contains control character and failed to parse the version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-956) github_write_comment returns 0 even when failed to write comment
[
https://issues.apache.org/jira/browse/YETUS-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17066441#comment-17066441
]
Akira Ajisaka commented on YETUS-956:
-
example: 404 error but return 0
{noformat}
aajisaka@e23da33c36eb:~/hadoop$ curl -X POST -H "Accept:
application/vnd.github.v3.full+json" -H "Content-Type: application/json"
"${githubauth[@]}" -d @"${restfile}" --location
"https://api.github.com/repos/aajisaka/testing/issues/100/comments;
{
"message": "Not Found",
"documentation_url":
"https://developer.github.com/v3/issues/comments/#create-a-comment;
}
aajisaka@e23da33c36eb:~/hadoop$ echo $?
0
{noformat}
> github_write_comment returns 0 even when failed to write comment
>
>
> Key: YETUS-956
> URL: https://issues.apache.org/jira/browse/YETUS-956
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
>Reporter: Akira Ajisaka
>Priority: Minor
>
> curl returns 0 even when 4XX is returned.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (YETUS-956) github_write_comment returns 0 even when failed to write comment
Akira Ajisaka created YETUS-956: --- Summary: github_write_comment returns 0 even when failed to write comment Key: YETUS-956 URL: https://issues.apache.org/jira/browse/YETUS-956 Project: Yetus Issue Type: Bug Components: Precommit Reporter: Akira Ajisaka curl returns 0 even when 4XX is returned. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-948) patches to patches confuse find_changed_files
[ https://issues.apache.org/jira/browse/YETUS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17045298#comment-17045298 ] Akira Ajisaka commented on YETUS-948: - Thank you for pinging me. I like riddles. (not only awk) :) > patches to patches confuse find_changed_files > - > > Key: YETUS-948 > URL: https://issues.apache.org/jira/browse/YETUS-948 > Project: Yetus > Issue Type: Bug > Components: Precommit >Affects Versions: 0.12.0 >Reporter: Allen Wittenauer >Priority: Critical > Attachments: awk-output.txt, input.patch > > > If a patch has patches to other patches in a source tree, there is a good > chance that find_changed_files is going to get completely confused. See > below for more. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (YETUS-941) Hadoop checkstyle URL is incorrect
[ https://issues.apache.org/jira/browse/YETUS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YETUS-941: Affects Version/s: 0.11.1 > Hadoop checkstyle URL is incorrect > -- > > Key: YETUS-941 > URL: https://issues.apache.org/jira/browse/YETUS-941 > Project: Yetus > Issue Type: Bug > Components: Precommit >Affects Versions: 0.11.1 >Reporter: Siyao Meng >Assignee: Akira Ajisaka >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In this yetus run: > https://github.com/apache/hadoop/pull/1846#issuecomment-588020487 > It shows the checkstyle result URL is > https://builds.apache.org/job/hadoop-multibranch/job/PR-1846/4/artifact/out//home/jenkins/jenkins-slave/workspace/hadoop-multibranch_PR-1846@2/out/maven-patch-checkstyle-root.txt > But the above URL is invalid. It should actually be: > https://builds.apache.org/job/hadoop-multibranch/job/PR-1846/4/artifact/out/maven-patch-checkstyle-root.txt > I am not sure if this project is the right place to post this bug jira. > Please advise. :) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-941) Hadoop checkstyle URL is incorrect
[ https://issues.apache.org/jira/browse/YETUS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039750#comment-17039750 ] Akira Ajisaka commented on YETUS-941: - Thanks [~smeng] for the report. I think this is a bug in Yetus. I'll create a PR shortly. > Hadoop checkstyle URL is incorrect > -- > > Key: YETUS-941 > URL: https://issues.apache.org/jira/browse/YETUS-941 > Project: Yetus > Issue Type: Bug > Components: Precommit >Reporter: Siyao Meng >Assignee: Akira Ajisaka >Priority: Major > > In this yetus run: > https://github.com/apache/hadoop/pull/1846#issuecomment-588020487 > It shows the checkstyle result URL is > https://builds.apache.org/job/hadoop-multibranch/job/PR-1846/4/artifact/out//home/jenkins/jenkins-slave/workspace/hadoop-multibranch_PR-1846@2/out/maven-patch-checkstyle-root.txt > But the above URL is invalid. It should actually be: > https://builds.apache.org/job/hadoop-multibranch/job/PR-1846/4/artifact/out/maven-patch-checkstyle-root.txt > I am not sure if this project is the right place to post this bug jira. > Please advise. :) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (YETUS-941) Hadoop checkstyle URL is incorrect
[ https://issues.apache.org/jira/browse/YETUS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned YETUS-941: --- Assignee: Akira Ajisaka > Hadoop checkstyle URL is incorrect > -- > > Key: YETUS-941 > URL: https://issues.apache.org/jira/browse/YETUS-941 > Project: Yetus > Issue Type: Bug > Components: Precommit >Reporter: Siyao Meng >Assignee: Akira Ajisaka >Priority: Major > > In this yetus run: > https://github.com/apache/hadoop/pull/1846#issuecomment-588020487 > It shows the checkstyle result URL is > https://builds.apache.org/job/hadoop-multibranch/job/PR-1846/4/artifact/out//home/jenkins/jenkins-slave/workspace/hadoop-multibranch_PR-1846@2/out/maven-patch-checkstyle-root.txt > But the above URL is invalid. It should actually be: > https://builds.apache.org/job/hadoop-multibranch/job/PR-1846/4/artifact/out/maven-patch-checkstyle-root.txt > I am not sure if this project is the right place to post this bug jira. > Please advise. :) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (YETUS-937) Fix Release Doc Maker link in README.md
[ https://issues.apache.org/jira/browse/YETUS-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned YETUS-937: --- Assignee: alfonso > Fix Release Doc Maker link in README.md > --- > > Key: YETUS-937 > URL: https://issues.apache.org/jira/browse/YETUS-937 > Project: Yetus > Issue Type: Improvement > Components: website and documentation >Affects Versions: 0.11.1 >Reporter: alfonso >Assignee: alfonso >Priority: Minor > Fix For: 0.12.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Release Doc Maker like is broken > I've made a pr > https://github.com/apache/yetus/pull/85 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (YETUS-937) Fix Release Doc Maker link in README.md
[ https://issues.apache.org/jira/browse/YETUS-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038221#comment-17038221 ] Akira Ajisaka edited comment on YETUS-937 at 2/17/20 10:22 AM: --- Merged into master. Thanks [~alfonso_men]. was (Author: ajisakaa): Merged into trunk. Thanks [~alfonso_men]. > Fix Release Doc Maker link in README.md > --- > > Key: YETUS-937 > URL: https://issues.apache.org/jira/browse/YETUS-937 > Project: Yetus > Issue Type: Improvement > Components: website and documentation >Affects Versions: 0.11.1 >Reporter: alfonso >Priority: Minor > Fix For: 0.12.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Release Doc Maker like is broken > I've made a pr > https://github.com/apache/yetus/pull/85 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (YETUS-937) Fix Release Doc Maker link in README.md
[ https://issues.apache.org/jira/browse/YETUS-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YETUS-937. - Fix Version/s: 0.12.0 Resolution: Fixed Merged into trunk. Thanks [~alfonso_men]. > Fix Release Doc Maker link in README.md > --- > > Key: YETUS-937 > URL: https://issues.apache.org/jira/browse/YETUS-937 > Project: Yetus > Issue Type: Improvement > Components: website and documentation >Affects Versions: 0.11.1 >Reporter: alfonso >Priority: Minor > Fix For: 0.12.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Release Doc Maker like is broken > I've made a pr > https://github.com/apache/yetus/pull/85 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (YETUS-937) Fix Release Doc Maker link in README.md
[ https://issues.apache.org/jira/browse/YETUS-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YETUS-937: Summary: Fix Release Doc Maker link in README.md (was: fix *Release Doc Maker* link) > Fix Release Doc Maker link in README.md > --- > > Key: YETUS-937 > URL: https://issues.apache.org/jira/browse/YETUS-937 > Project: Yetus > Issue Type: Improvement > Components: website and documentation >Affects Versions: 0.11.1 >Reporter: alfonso >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Release Doc Maker like is broken > I've made a pr > https://github.com/apache/yetus/pull/85 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (YETUS-931) golangci.sh is not executable
Akira Ajisaka created YETUS-931: --- Summary: golangci.sh is not executable Key: YETUS-931 URL: https://issues.apache.org/jira/browse/YETUS-931 Project: Yetus Issue Type: Bug Components: Precommit Reporter: Akira Ajisaka Assignee: Akira Ajisaka -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-897) Remove duplicate jdk.tools dependency from audience-annotations module
[
https://issues.apache.org/jira/browse/YETUS-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015537#comment-17015537
]
Akira Ajisaka commented on YETUS-897:
-
I think 0.12.0 will be released in this month.
https://lists.apache.org/thread.html/r10dc2eac7ba6f64f5c694369d527978fc65343d26d26dde6d31a5898%40%3Cdev.yetus.apache.org%3E
> Remove duplicate jdk.tools dependency from audience-annotations module
> --
>
> Key: YETUS-897
> URL: https://issues.apache.org/jira/browse/YETUS-897
> Project: Yetus
> Issue Type: Bug
> Components: Audience Annotations
>Reporter: Martin Todorov
>Assignee: Priyank Bagrecha
>Priority: Major
> Fix For: 0.12.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Hi,
> A transitive dependency of our Gradle project requires {{compile group:
> 'org.apache.yetus', name: 'audience-annotations', version: '0.10.0'}}. It
> appears we may be hitting a [bug in
> Gradle|https://github.com/gradle/gradle/issues/10058] in that it quite
> possibly doesn't handle {{system}}-scoped and {{optional}} dependencies
> properly.
> I had a look at your project's {{pom.xml}} files and there are actually
> issues with it as well.
> Consider the following snippet:
> {code:java}
>
>
> jdk1.8
>
> (,1.8]
>
>
>
>
> jdk.tools
> jdk.tools
> system
>
> true
>
>
>
>
>
>
>
> jdk.tools
> jdk.tools
> system
>
> true
>
>
> {code}
> What's the point in both having the {{jdk.tools}} dependencies define in a
> profile and then also in the main {{}} section? If you move
> this dependency into the profile and remove the one from the main
> {{}} section, and make the profile activated via a system
> property, or activate it through your {{settings.xml}} via the
> {{activeProfile}} section, this should be okay.
> I agree that theoretically, this is bad Maven practice, because it breaks
> build portability, but on the other hand, you're already breaking build
> portability by declaring a {{system}}-scoped dependency.
> Is it really necessary to depend on the {{tools.jar}}? If you're using a JDK
> to build the code, you should always have it on your classpath? What seems to
> be the issue that you're trying to solve, (which I appear to be missing)?
> I haven't gone through all of your project's {{pom.xml}} files, but I suspect
> the same fix might be required elsewhere as well.
> Please, advise!
> Many thanks in advance!
> Kind regards,
> Martin
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (YETUS-897) Remove duplicate jdk.tools dependency from audience-annotations module
[
https://issues.apache.org/jira/browse/YETUS-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16993267#comment-16993267
]
Akira Ajisaka commented on YETUS-897:
-
The released artifacts will not be updated. This will only be fixed with 0.12.0.
> Remove duplicate jdk.tools dependency from audience-annotations module
> --
>
> Key: YETUS-897
> URL: https://issues.apache.org/jira/browse/YETUS-897
> Project: Yetus
> Issue Type: Bug
> Components: Audience Annotations
>Reporter: Martin Todorov
>Assignee: Priyank Bagrecha
>Priority: Major
> Fix For: 0.12.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Hi,
> A transitive dependency of our Gradle project requires {{compile group:
> 'org.apache.yetus', name: 'audience-annotations', version: '0.10.0'}}. It
> appears we may be hitting a [bug in
> Gradle|https://github.com/gradle/gradle/issues/10058] in that it quite
> possibly doesn't handle {{system}}-scoped and {{optional}} dependencies
> properly.
> I had a look at your project's {{pom.xml}} files and there are actually
> issues with it as well.
> Consider the following snippet:
> {code:java}
>
>
> jdk1.8
>
> (,1.8]
>
>
>
>
> jdk.tools
> jdk.tools
> system
>
> true
>
>
>
>
>
>
>
> jdk.tools
> jdk.tools
> system
>
> true
>
>
> {code}
> What's the point in both having the {{jdk.tools}} dependencies define in a
> profile and then also in the main {{}} section? If you move
> this dependency into the profile and remove the one from the main
> {{}} section, and make the profile activated via a system
> property, or activate it through your {{settings.xml}} via the
> {{activeProfile}} section, this should be okay.
> I agree that theoretically, this is bad Maven practice, because it breaks
> build portability, but on the other hand, you're already breaking build
> portability by declaring a {{system}}-scoped dependency.
> Is it really necessary to depend on the {{tools.jar}}? If you're using a JDK
> to build the code, you should always have it on your classpath? What seems to
> be the issue that you're trying to solve, (which I appear to be missing)?
> I haven't gone through all of your project's {{pom.xml}} files, but I suspect
> the same fix might be required elsewhere as well.
> Please, advise!
> Many thanks in advance!
> Kind regards,
> Martin
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (YETUS-897) Remove duplicate jdk.tools dependency from audience-annotations module
[
https://issues.apache.org/jira/browse/YETUS-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated YETUS-897:
Summary: Remove duplicate jdk.tools dependency from audience-annotations
module (was: Incorrect usage of Maven profile)
> Remove duplicate jdk.tools dependency from audience-annotations module
> --
>
> Key: YETUS-897
> URL: https://issues.apache.org/jira/browse/YETUS-897
> Project: Yetus
> Issue Type: Bug
> Components: Audience Annotations
>Reporter: Martin Todorov
>Assignee: Priyank Bagrecha
>Priority: Major
> Fix For: 0.12.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Hi,
> A transitive dependency of our Gradle project requires {{compile group:
> 'org.apache.yetus', name: 'audience-annotations', version: '0.10.0'}}. It
> appears we may be hitting a [bug in
> Gradle|https://github.com/gradle/gradle/issues/10058] in that it quite
> possibly doesn't handle {{system}}-scoped and {{optional}} dependencies
> properly.
> I had a look at your project's {{pom.xml}} files and there are actually
> issues with it as well.
> Consider the following snippet:
> {code:java}
>
>
> jdk1.8
>
> (,1.8]
>
>
>
>
> jdk.tools
> jdk.tools
> system
>
> true
>
>
>
>
>
>
>
> jdk.tools
> jdk.tools
> system
>
> true
>
>
> {code}
> What's the point in both having the {{jdk.tools}} dependencies define in a
> profile and then also in the main {{}} section? If you move
> this dependency into the profile and remove the one from the main
> {{}} section, and make the profile activated via a system
> property, or activate it through your {{settings.xml}} via the
> {{activeProfile}} section, this should be okay.
> I agree that theoretically, this is bad Maven practice, because it breaks
> build portability, but on the other hand, you're already breaking build
> portability by declaring a {{system}}-scoped dependency.
> Is it really necessary to depend on the {{tools.jar}}? If you're using a JDK
> to build the code, you should always have it on your classpath? What seems to
> be the issue that you're trying to solve, (which I appear to be missing)?
> I haven't gone through all of your project's {{pom.xml}} files, but I suspect
> the same fix might be required elsewhere as well.
> Please, advise!
> Many thanks in advance!
> Kind regards,
> Martin
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (YETUS-897) Incorrect usage of Maven profile
[
https://issues.apache.org/jira/browse/YETUS-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16993195#comment-16993195
]
Akira Ajisaka edited comment on YETUS-897 at 12/11/19 5:03 AM:
---
Committed to master. Thanks [~carlspring] for the report and thanks
[~pbagrecha]] for the contribution!
was (Author: ajisakaa):
Committed to master. Thanks [~carlspring] for the report and thanks
[~carlspring] for the contribution!
> Incorrect usage of Maven profile
>
>
> Key: YETUS-897
> URL: https://issues.apache.org/jira/browse/YETUS-897
> Project: Yetus
> Issue Type: Bug
> Components: Audience Annotations
>Reporter: Martin Todorov
>Assignee: Priyank Bagrecha
>Priority: Major
> Fix For: 0.12.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Hi,
> A transitive dependency of our Gradle project requires {{compile group:
> 'org.apache.yetus', name: 'audience-annotations', version: '0.10.0'}}. It
> appears we may be hitting a [bug in
> Gradle|https://github.com/gradle/gradle/issues/10058] in that it quite
> possibly doesn't handle {{system}}-scoped and {{optional}} dependencies
> properly.
> I had a look at your project's {{pom.xml}} files and there are actually
> issues with it as well.
> Consider the following snippet:
> {code:java}
>
>
> jdk1.8
>
> (,1.8]
>
>
>
>
> jdk.tools
> jdk.tools
> system
>
> true
>
>
>
>
>
>
>
> jdk.tools
> jdk.tools
> system
>
> true
>
>
> {code}
> What's the point in both having the {{jdk.tools}} dependencies define in a
> profile and then also in the main {{}} section? If you move
> this dependency into the profile and remove the one from the main
> {{}} section, and make the profile activated via a system
> property, or activate it through your {{settings.xml}} via the
> {{activeProfile}} section, this should be okay.
> I agree that theoretically, this is bad Maven practice, because it breaks
> build portability, but on the other hand, you're already breaking build
> portability by declaring a {{system}}-scoped dependency.
> Is it really necessary to depend on the {{tools.jar}}? If you're using a JDK
> to build the code, you should always have it on your classpath? What seems to
> be the issue that you're trying to solve, (which I appear to be missing)?
> I haven't gone through all of your project's {{pom.xml}} files, but I suspect
> the same fix might be required elsewhere as well.
> Please, advise!
> Many thanks in advance!
> Kind regards,
> Martin
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (YETUS-897) Incorrect usage of Maven profile
[
https://issues.apache.org/jira/browse/YETUS-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka resolved YETUS-897.
-
Fix Version/s: 0.12.0
Assignee: Priyank Bagrecha
Resolution: Fixed
Committed to master. Thanks [~carlspring] for the report and thanks
[~carlspring] for the contribution!
> Incorrect usage of Maven profile
>
>
> Key: YETUS-897
> URL: https://issues.apache.org/jira/browse/YETUS-897
> Project: Yetus
> Issue Type: Bug
> Components: Audience Annotations
>Reporter: Martin Todorov
>Assignee: Priyank Bagrecha
>Priority: Major
> Fix For: 0.12.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Hi,
> A transitive dependency of our Gradle project requires {{compile group:
> 'org.apache.yetus', name: 'audience-annotations', version: '0.10.0'}}. It
> appears we may be hitting a [bug in
> Gradle|https://github.com/gradle/gradle/issues/10058] in that it quite
> possibly doesn't handle {{system}}-scoped and {{optional}} dependencies
> properly.
> I had a look at your project's {{pom.xml}} files and there are actually
> issues with it as well.
> Consider the following snippet:
> {code:java}
>
>
> jdk1.8
>
> (,1.8]
>
>
>
>
> jdk.tools
> jdk.tools
> system
>
> true
>
>
>
>
>
>
>
> jdk.tools
> jdk.tools
> system
>
> true
>
>
> {code}
> What's the point in both having the {{jdk.tools}} dependencies define in a
> profile and then also in the main {{}} section? If you move
> this dependency into the profile and remove the one from the main
> {{}} section, and make the profile activated via a system
> property, or activate it through your {{settings.xml}} via the
> {{activeProfile}} section, this should be okay.
> I agree that theoretically, this is bad Maven practice, because it breaks
> build portability, but on the other hand, you're already breaking build
> portability by declaring a {{system}}-scoped dependency.
> Is it really necessary to depend on the {{tools.jar}}? If you're using a JDK
> to build the code, you should always have it on your classpath? What seems to
> be the issue that you're trying to solve, (which I appear to be missing)?
> I haven't gone through all of your project's {{pom.xml}} files, but I suspect
> the same fix might be required elsewhere as well.
> Please, advise!
> Many thanks in advance!
> Kind regards,
> Martin
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (YETUS-927) GITHUB_PASSWD environment variable is not effective
Akira Ajisaka created YETUS-927:
---
Summary: GITHUB_PASSWD environment variable is not effective
Key: YETUS-927
URL: https://issues.apache.org/jira/browse/YETUS-927
Project: Yetus
Issue Type: Bug
Components: Precommit
Reporter: Akira Ajisaka
Assignee: Akira Ajisaka
The Yetus web site
(http://yetus.apache.org/documentation/in-progress/precommit-bugsystems/#github-specific)
says:
{quote}The password or OAuth token is provided via the --github-password or
GITHUB_PASSWD environment variable.{quote}
but the environment variable is not effective and we have to pass the password
or token by --github-password option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (YETUS-927) GITHUB_PASSWD environment variable is not effective
[
https://issues.apache.org/jira/browse/YETUS-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated YETUS-927:
Description:
The Yetus web site
(http://yetus.apache.org/documentation/in-progress/precommit-bugsystems/#github-specific)
says:
{quote}The password or OAuth token is provided via the --github-password or
GITHUB_PASSWD environment variable.{quote}
but the environment variable is not effective and we have to provide the
password or token by --github-password option.
was:
The Yetus web site
(http://yetus.apache.org/documentation/in-progress/precommit-bugsystems/#github-specific)
says:
{quote}The password or OAuth token is provided via the --github-password or
GITHUB_PASSWD environment variable.{quote}
but the environment variable is not effective and we have to pass the password
or token by --github-password option.
> GITHUB_PASSWD environment variable is not effective
> ---
>
> Key: YETUS-927
> URL: https://issues.apache.org/jira/browse/YETUS-927
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
>
> The Yetus web site
> (http://yetus.apache.org/documentation/in-progress/precommit-bugsystems/#github-specific)
> says:
> {quote}The password or OAuth token is provided via the --github-password or
> GITHUB_PASSWD environment variable.{quote}
> but the environment variable is not effective and we have to provide the
> password or token by --github-password option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (YETUS-452) Python 3 compatibility for releasedocmaker and shelldocs
[ https://issues.apache.org/jira/browse/YETUS-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reopened YETUS-452: - I'd like to reopen this because Python 2.x is EoL at the end of 2019. > Python 3 compatibility for releasedocmaker and shelldocs > > > Key: YETUS-452 > URL: https://issues.apache.org/jira/browse/YETUS-452 > Project: Yetus > Issue Type: New Feature >Reporter: Ajay Yadav >Priority: Major > > Ubuntu 16.04 has released and it defaults to Python 3 [See [release notes | > https://wiki.ubuntu.com/XenialXerus/ReleaseNotes#Python_3] ]. > It will be nice if we can support both Python 2.6+ and Python 3.x -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (YETUS-557) Investigate switching to jdk.javadoc.doclet
[ https://issues.apache.org/jira/browse/YETUS-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926484#comment-16926484 ] Akira Ajisaka commented on YETUS-557: - bq. Or is this failing even with jdk11 targeting jdk8? Yes. The old doclet package has been removed since JDK10 and this is failing with JDK11 targeting JDK8. > Investigate switching to jdk.javadoc.doclet > --- > > Key: YETUS-557 > URL: https://issues.apache.org/jira/browse/YETUS-557 > Project: Yetus > Issue Type: Task > Components: Audience Annotations >Affects Versions: 0.6.0 >Reporter: Allen Wittenauer >Priority: Major > > It looks like there is a newer API available for building Javadoc doclets. > This might help remove our dependency on tools.jar. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (YETUS-907) Building website in the project provided container fails.
[
https://issues.apache.org/jira/browse/YETUS-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913909#comment-16913909
]
Akira Ajisaka commented on YETUS-907:
-
+1, thanks.
> Building website in the project provided container fails.
> -
>
> Key: YETUS-907
> URL: https://issues.apache.org/jira/browse/YETUS-907
> Project: Yetus
> Issue Type: Bug
> Components: website and documentation
>Affects Versions: 0.11.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 0.11.0
>
> Attachments: YETUS-907.0.patch
>
>
> Attempting to use the project provided container fails when running {{mvn
> site site:stage}} after a successful install.
> Looks like a problem with a ruby gem not having a fixed version and getting
> ahead of our ruby install.
> {code}
> Fetching sassc 2.0.1
> Installing sassc 2.0.1 with native extensions
> Gem::InstallError: sassc requires Ruby version >= 2.3.3.
> An error occurred while installing sassc (2.0.1), and Bundler cannot continue.
> Make sure that `gem install sassc -v '2.0.1' --source 'https://rubygems.org/'`
> succeeds before bundling.
> In Gemfile:
> middleman was resolved to 4.3.4, which depends on
> middleman-core was resolved to 4.3.4, which depends on
> sassc
> ^Cbusbey@17deb44cd1d7:~/yetus$ ruby --version
> ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]
> busbey@17deb44cd1d7:~/yetus$
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (YETUS-362) Attached patch in jira is not used by jenkins if there is a corresponding pull request.
[ https://issues.apache.org/jira/browse/YETUS-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka resolved YETUS-362. - Resolution: Done This issue seems to be fixed via GitBox integration. Please feel free to reopen this if you disagree. > Attached patch in jira is not used by jenkins if there is a corresponding > pull request. > --- > > Key: YETUS-362 > URL: https://issues.apache.org/jira/browse/YETUS-362 > Project: Yetus > Issue Type: Bug >Affects Versions: 0.2.0 >Reporter: Akira Ajisaka >Assignee: Casey Brotherton >Priority: Major > > When a patch is attached in HDFS-9263, Jenkins precommit downloads the other > patch in the corresponding github pull request. Jenkins should download the > attached patch instead of the patch in github if the precommit is triggered > by jira. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (YETUS-893) Update the link to doclet javadoc
Akira Ajisaka created YETUS-893: --- Summary: Update the link to doclet javadoc Key: YETUS-893 URL: https://issues.apache.org/jira/browse/YETUS-893 Project: Yetus Issue Type: Improvement Components: website and documentation Reporter: Akira Ajisaka There are some old links "https://java.sun.com/javase/6/docs/jdk/api/javadoc/doclet/; in java source files. They can be updated to "https://docs.oracle.com/javase/8/docs/jdk/api/javadoc/doclet/;. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
