beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-1852) dead links on beam website
Date Thu, 06 Apr 2017 15:25:42 GMT


ASF GitHub Bot commented on BEAM-1852:

GitHub user ssisk opened a pull request:

    [BEAM-1852] Fix ICLA link

    The link at under "CONTRIBUTOR LICENSE AGREEMENTS" now
links to the pdf version, and this commit changed the link in core beam:

You can merge this pull request into a Git repository by running:

    $ git pull fix-icla-link

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #203
commit d7d4fc93bc58b434ccec9360f315a8ce5273a4fc
Author: Stephen Sisk <>
Date:   2017-04-06T15:20:31Z

    Fix ICLA link


> dead links on beam website
> --------------------------
>                 Key: BEAM-1852
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: website
>            Reporter: Stephen Sisk
>            Assignee: Stephen Sisk
> Output from rake: 
> Checking 270 external links...
> Ran on 98 files!
> - ./content/subdir/blog/2017/02/01/graduation-media-recap.html
>   *  External link
failed: response code 0 means something's wrong.
>              It's possible libcurl couldn't connect to the server or perhaps the request
timed out.
>              Sometimes, making too many requests at once also breaks things.
>              Either way, the return message (if any) from the server is: Peer certificate
cannot be authenticated with given CA certificates
> [stephen note: I could not confirm this manually, but that error seems.. interesting]
> - ./content/subdir/contribute/contribution-guide/index.html
>   *  External link failed: 404 No error
> [stephen note: manually confirmed this]

This message was sent by Atlassian JIRA

View raw message