[ 
https://issues.apache.org/jira/browse/BEAM-10702?focusedWorklogId=472555&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-472555
 ]

ASF GitHub Bot logged work on BEAM-10702:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 19/Aug/20 17:49
            Start Date: 19/Aug/20 17:49
    Worklog Time Spent: 10m 
      Work Description: jkff edited a comment on pull request #12619:
URL: https://github.com/apache/beam/pull/12619#issuecomment-676569143


   Alright, we now have 2 failing precommits both due to known issues: Python 
with BEAM-10697, and PythonDocs because it doesn't exist at 2.24. Looks like 
BEAM-10697 is resolved, but not cherrypicked into 2.24. @youngoli  Do you want 
to ignore it for this PR or should we wait for someone to cherrypick a fix and 
rebase on that?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 472555)
    Time Spent: 6h 10m  (was: 6h)

> Embedded job endpoint artifact service unzips PIP files, making them 
> non-installable
> ------------------------------------------------------------------------------------
>
>                 Key: BEAM-10702
>                 URL: https://issues.apache.org/jira/browse/BEAM-10702
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-core
>    Affects Versions: 2.22.0
>            Reporter: Eugene Kirpichov
>            Assignee: Eugene Kirpichov
>            Priority: P2
>          Time Spent: 6h 10m
>  Remaining Estimate: 0h
>
> For details see this thread: 
> https://lists.apache.org/thread.html/r36931794495dc2745c39e11410577931a0a8cfb07a48253eaeda3246%40%3Cuser.beam.apache.org%3E
> The thread also contains a solution. I'll send a PR - filing the JIRA just to 
> track.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to