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 <[email protected]> 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 <[email protected]> wrote: > > > > I will pass the word. > > > > Do you have logs? > > > > > > On Sun, May 3, 2020 at 4:15 PM Charles Givre <[email protected]> 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 <[email protected]> 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 <[email protected]> > >> 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) > >>>> > >>>> > >>>> > >> > >> > >
