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

ASF GitHub Bot commented on FLINK-10072:
----------------------------------------

rickhofstede commented on issue #6503: [FLINK-10072] [docs] Syntax and 
consistency issues in "The Broadcast State Pattern"
URL: https://github.com/apache/flink/pull/6503#issuecomment-411703560
 
 
   @yanghua 
   
   Since you've reviewed my commits, let me please ask you the following. It 
appears that Travis doesn't like the last two commits in this pull request. 
This seems odd to me, since they introduce no functional changes to the code at 
all. Can you comment on what is going wrong there, such that I can fix it?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Syntax and consistency issues in "The Broadcast State Pattern"
> --------------------------------------------------------------
>
>                 Key: FLINK-10072
>                 URL: https://issues.apache.org/jira/browse/FLINK-10072
>             Project: Flink
>          Issue Type: Bug
>          Components: Documentation, Streaming
>    Affects Versions: 1.5.2
>            Reporter: Rick Hofstede
>            Priority: Trivial
>              Labels: pull-request-available
>
> There are several issues in the documentation for "[The Broadcast State 
> Pattern|https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/state/broadcast_state.html]":
>  # Indentation mixes up whitespace and tabs, causing the markdown layout to 
> be crippled (especially related to indentation),
>  # Broken (nested) list layout, causing multi-item lists to be rendered as 
> single-item lists, and
>  # inconsistent list layout.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to