BrokenPipeError in long-running process

[nkruglikov]

It seems that if the mystem process dies for some reason (e. g. OS kills it), the wrapper crashes with the BrokenPipeError. I think that such behavior is unwanted, but I am not sure this could be fixed easily. I fixed it in my long-running process with catching the BrokenPipeError on Mystem.lemmatize call and recreating a Mystem object if needed.

The traceback:

  File "/usr/local/lib/python3.5/dist-packages/pymystem3/mystem.py", line 264, in lemmatize
    infos = self.analyze(text)
  File "/usr/local/lib/python3.5/dist-packages/pymystem3/mystem.py", line 249, in analyze
    result.extend(self._analyze_impl(line))
  File "/usr/local/lib/python3.5/dist-packages/pymystem3/mystem.py", line 280, in _analyze_impl
    self._procin.write(text)
BrokenPipeError: [Errno 32] Broken pipe

P. S. I have also noticed similar behavior in interactive Jupyter Notebook scenario. If you kill a cell which uses a Mystem object, later calls to its lemmatize methods lead to BrokenPipeError, so you need to recreate the object.

[alexanderpanchenko]

sorry for the late response and thanks for reporting this issue. I am currently also not sure how this can be fixed, but any ideas or better pull requests with fixes are welcome.

[vasinkd]

I believe simple catching of BrokenPipeError and mysteminstance.close(), mysteminstance.start() can solve this. Just tried to kill mystem process and follow this steps, it helps.

[alexanderpanchenko]

from what I see now, normally yes. could you send a PR please

…

On 19 Oct 2018, at 14:05, Kirill Vasin ***@***.***> wrote: Wouldn't simple catching of BrokenPipeError and mysteminstance.close(), mysteminstance.start() solve this? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#21 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABY6vrUf28odQhOkSrOLNUjzWp_EjyGUks5umcAigaJpZM4TkOWd>.