Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 20 Mar 2017 19:35:41 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13057559.1490023681000.69439.1490038541757@Atlassian.JIRA>
In-Reply-To: <JIRA.13057559.1490023681000@Atlassian.JIRA>
References: <JIRA.13057559.1490023681000@Atlassian.JIRA> <JIRA.13057559.1490023681450@jira-lw-us.apache.org>
Subject: [jira] [Commented] (AMBARI-20502) Configuration Markdown Not
 Properly Parsed By Some Editors
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 20 Mar 2017 19:35:46 -0000


    [ https://issues.apache.org/jira/browse/AMBARI-20502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933369#comment-15933369 ] 

Hadoop QA commented on AMBARI-20502:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12859586/AMBARI-20502.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/11086//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11086//console

This message is automatically generated.

> Configuration Markdown Not Properly Parsed By Some Editors
> ----------------------------------------------------------
>
>                 Key: AMBARI-20502
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20502
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: trunk
>
>         Attachments: AMBARI-20502.patch
>
>
> Some markdown displays, like GitHub, don't properly display the configuration markdown. Sections appear as:
> {code}
> ####Alerts & Notifications | Property Name | 10 Hosts | ~50 Hosts | ~100 Hosts | 500+ Hosts | | --- | --- | --- | --- | --- | | alerts.execution.scheduler.threadpool.size.core | 2 | 2 | 4 | 4 | | alerts.execution.scheduler.threadpool.size.max | 2 | 2 | 8 | 8 | | alerts.execution.scheduler.threadpool.worker.size | 400 | 2000 | 4000 | 20000 | | alerts.cache.enabled | false | false | false | true | | alerts.cache.flush.interval | 10 | 10 | 10 | 10 | | alerts.cache.size | 50000 | 50000 | 100000 | 100000 | ####Jetty API & Agent Thread Pools | Property Name | 10 Hosts | ~50 Hosts | ~100 Hosts | 500+ Hosts | | --- | --- | --- | --- | --- | | client.threadpool.size.max | 25 | 35 | 50 | 65 | | agent.threadpool.size.max | 25 | 35 | 75 | 100 |
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)