Closed philipstarkey closed 6 years ago
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Merged in cbillington/lyse/bugfix3 (pull request #33)
Fixes issue #27: lyse broken after analysis loop crash
Approved-by: Jan Werkmann jan.wrk.fb@gmail.com
→ \<\<cset c2d9fb371c6a13ad6a21fd8478c838124ae75994>>
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Fixes issue #27
Made analysis loop continue if it encounters an uncaught error, but raise the error in a thread with a serious sounding warning about lyse possibly being in an inconsistent state.
→ \<\<cset a99a3dd7413b17d92916df3e565159aa12064227>>
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Merged in cbillington/lyse/bugfix3 (pull request #33)
Fixes issue #27: lyse broken after analysis loop crash
Approved-by: Jan Werkmann jan.wrk.fb@gmail.com
→ \<\<cset c2d9fb371c6a13ad6a21fd8478c838124ae75994>>
Original report (archived issue) by Shaun Johnstone (Bitbucket: shjohnst, GitHub: shjohnst).
If the main analysis queue crashes, there's no way to restart it, other than restarting lyse. It would be nice if it could automatically re-spawn if it dies.
At the very least, fixing issue #24 would help to make the restarting of lyse less painful, however you would still lose your dataframe.