Open shackra opened 7 years ago
Yeah, we don't handle these cases very well. Whenever rope barfs like this, we should bundle up the error information into the response to the client. And the client should do something helpful with it.
Could you attach a snippet of code that shows this problem, along with the location at which you're calling extract
?
@shackra I've just pushed up a new version of traad that and emacs-traad that should help with this issue. The traad changes don't directly address the diagnostics issue you raised; they're really just an improvement in the internal implementation.
However, the better-progress-reporting
branch on emacs-traad should better information when things go bad. Could you try these out and let me know if they work for you?
Sure, will try it this Friday and I will come back with much feedback as possible
Did you ever try this again?
Calling
traad-extract-method
inside any random portion of Python code cause this error without making the user aware something wrong happened.