Forwarded.
On Mon, May 4, 2020 at 6:15 AM Charles Givre <cgi...@gmail.com> wrote: > HI Ted, Vova, > My PR is still blocked by the MapR repos. After reverting back to the > HTTP repo (which does seem to be working) we're now getting the following > error: > > [ERROR] Failed to execute goal on project drill-format-mapr: Could not > resolve dependencies for project > org.apache.drill.contrib:drill-format-mapr:jar:1.18.0-SNAPSHOT: Could not > transfer artifact com.mapr.hadoop:maprfs:jar:6.1.0-mapr from/to > mapr-releases (http://repository.mapr.com/maven/): GET request of: > com/mapr/hadoop/maprfs/6.1.0-mapr/maprfs-6.1.0-mapr.jar from mapr-releases > failed: Premature end of Content-Length delimited message body (expected: > 67,884,262; received: 47,333,376) -> [Help 1] > 3146 > < > https://github.com/apache/drill/pull/2067/checks?check_run_id=642773818#step:6:3146>[ERROR] > > 3147 > < > https://github.com/apache/drill/pull/2067/checks?check_run_id=642773818#step:6:3147>[ERROR] > To see the full stack trace of the errors, re-run Maven with the -e switch. > 3148 > < > https://github.com/apache/drill/pull/2067/checks?check_run_id=642773818#step:6:3148>[ERROR] > Re-run Maven using the -X switch to enable full debug logging. > 3149 > < > https://github.com/apache/drill/pull/2067/checks?check_run_id=642773818#step:6:3149>[ERROR] > > 3150 > < > https://github.com/apache/drill/pull/2067/checks?check_run_id=642773818#step:6:3150>[ERROR] > For more information about the errors and possible solutions, please read > the following articles: > 3151 > < > https://github.com/apache/drill/pull/2067/checks?check_run_id=642773818#step:6:3151>[ERROR] > [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > 3152 > < > https://github.com/apache/drill/pull/2067/checks?check_run_id=642773818#step:6:3152>[ERROR] > > 3153 > < > https://github.com/apache/drill/pull/2067/checks?check_run_id=642773818#step:6:3153>[ERROR] > After correcting the problems, you can resume the build with the command > 3154 > < > https://github.com/apache/drill/pull/2067/checks?check_run_id=642773818#step:6:3154>[ERROR] > mvn <args> -rf :drill-format-mapr > 3155 > < > https://github.com/apache/drill/pull/2067/checks?check_run_id=642773818#step:6:3155>##[error]Process > completed with exit code 1. > > Thanks for your help on quickly addressing this issue. > -- C > > > On May 4, 2020, at 2:48 AM, Vova Vysotskyi <vvo...@gmail.com> wrote: > > > > Hi Ted, > > > > Thanks for your help! It looks like for http protocol this issue was > > resolved. > > > > Kind regards, > > Volodymyr Vysotskyi > > > > > > On Mon, May 4, 2020 at 4:19 AM Charles Givre <cgi...@gmail.com> wrote: > > > >> Hi Ted, > >> Thanks for your help. You can view the logs here: > >> https://github.com/apache/drill/pull/2067 < > >> https://github.com/apache/drill/pull/2067> in the CI stuff. > >> -- C > >> > >> > >> > >> > >>> On May 3, 2020, at 9:16 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: > >>> > >>> I will pass the word. > >>> > >>> Do you have logs? > >>> > >>> > >>> On Sun, May 3, 2020 at 4:15 PM Charles Givre <cgi...@gmail.com> wrote: > >>> > >>>> Hi Ted, > >>>> Thanks for looking into this so quickly. Unfortunately, I re-ran the > CI > >>>> jobs from github and it is still producing the same errors. > >>>> Best, > >>>> --C > >>>> > >>>>> On May 3, 2020, at 5:58 PM, Ted Dunning <ted.dunn...@gmail.com> > wrote: > >>>>> > >>>>> It appears that the certificate issue is resolved. > >>>>> > >>>>> Can somebody verify this by doing a compilation? > >>>>> > >>>>> I have to add that based on the number of off-line and on-list pings > I > >>>> got > >>>>> about this issue I can say that there were quite a few people > compiling > >>>>> Drill on a Sunday morning. That bodes well, I think, for community > >>>> health. > >>>>> > >>>>> > >>>>> > >>>>> On Sun, May 3, 2020 at 11:27 AM Ted Dunning <ted.dunn...@gmail.com> > >>>> wrote: > >>>>> > >>>>>> > >>>>>> I just got word back that the team is looking at the issue. > >>>>>> > >>>>>> Not surprisingly, their first look indicates that the issue isn't > what > >>>> it > >>>>>> appears to be (i.e. not a bad cert) > >>>>>> > >>>>>> > >>>>>> > >>>> > >>>> > >> > >> > >
