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

Ruoyun Huang commented on BEAM-5793:
------------------------------------

Update:

I created a testing PR, [https://github.com/apache/beam/pull/6759.]   Verified 
two things: 

1) `docs` build target indeed is triggered in jenkins (previously I didn't 
notice there is 'full log' option). 

2) and ....  it passes on Jenkins.  
[Link|https://builds.apache.org/job/beam_PreCommit_Python_Commit/1985/] 

I verified both my Desktop and Jenkins use the same version of sphinx (1.6.5). 

 

 

Thanks Micah for the discussions. Given this result, it is more likely to be 
some settings messed up on my Desktop (and so does Scott's ). :( 

 

Instead of digging into this further, for now I shall just pause and do some 
manual fix when building my PRs.

 

 

> Python sdk docs target fails in flink_streaming_impulse_source
> --------------------------------------------------------------
>
>                 Key: BEAM-5793
>                 URL: https://issues.apache.org/jira/browse/BEAM-5793
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py-core
>            Reporter: Ruoyun Huang
>            Assignee: Micah Wylde
>            Priority: Minor
>
> gradle scan result: [https://gradle.com/s/w4icffibxs72a]
> Error message: 
> projects/beam2/sdks/python/apache_beam/io/flink/flink_streaming_impulse_source.py:docstring
>  of 
> apache_beam.io.flink.flink_streaming_impulse_source.FlinkStreamingImpulseSource.from_runner_api_parameter:11:Unexpected
>  indentation.
>  
> Root cause seems to be that there are two annotations for a single function. 
> And sphinx does not like that. 



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

Reply via email to