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

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

                Author: ASF GitHub Bot
            Created on: 18/Mar/20 21:40
            Start Date: 18/Mar/20 21:40
    Worklog Time Spent: 10m 
      Work Description: rohdesamuel commented on pull request #11128: 
[BEAM-9524] Fix for ib.show() executing indefinitely
URL: https://github.com/apache/beam/pull/11128#discussion_r394655524
 
 

 ##########
 File path: 
sdks/python/apache_beam/runners/interactive/caching/streaming_cache.py
 ##########
 @@ -153,7 +153,8 @@ def __init__(
     self._coder = coder
     self._labels = labels
     self._is_cache_complete = (
-        is_cache_complete if is_cache_complete else lambda: True)
+        is_cache_complete if is_cache_complete else lambda _: True)
+    self._pipeline_id = labels[-1].split('_')[-1]
 
 Review comment:
   Yeah the pipeline id is just a pointer to the pipeline, which is guaranteed 
to be unique and constant.
 
----------------------------------------------------------------
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: 405757)
    Time Spent: 50m  (was: 40m)

> ib.show() spins forever when cells are re-executed
> --------------------------------------------------
>
>                 Key: BEAM-9524
>                 URL: https://issues.apache.org/jira/browse/BEAM-9524
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-py-interactive
>            Reporter: Sam Rohde
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>




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

Reply via email to