You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/04 13:45:05 UTC

[GitHub] [beam] damccorm opened a new issue, #19855: StopOnExitJobServer interrupt handler errors

damccorm opened a new issue, #19855:
URL: https://github.com/apache/beam/issues/19855

   When I cancelled a job using FlinkRunner, I got the error: `TypeError: stop() takes exactly 1 argument (3 given)` which is an error with this line: [https://github.com/apache/beam/blob/c5f43342f914fc8ff367b86fb9294c38436ed3ce/sdks/python/apache_beam/runners/portability/job_server.py#L87](https://github.com/apache/beam/blob/c5f43342f914fc8ff367b86fb9294c38436ed3ce/sdks/python/apache_beam/runners/portability/job_server.py#L87)
   
   However, it appears the job server was closed successfully, presumably on exit. Which raises the question, why do we attempt to handle interrupts at all?
   
   Imported from Jira [BEAM-8310](https://issues.apache.org/jira/browse/BEAM-8310). Original Jira may contain additional context.
   Reported by: ibzib.


-- 
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.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org