Dear all, and especially @sweaglesw some Treebankers here at UW are running into an error when they have the “is a constituent” filter on. Specifically, here is the reported behavior and workaround:
" When trying to save after applying “is a constituent” filter (which shows up as “span = [x] to [y]”), the terminal responds to prompt /save?{number of parse}&accepted=1 with segmentation fault (core dumped) (errored) as opposed to writing tsdb relation 'decision' with [#] tuples (in case of successfully accepting the tree). It will not allow me to go back or exit through the browser, giving error unexpected http code: 0= , hinting that the treebanker itself has stopped running and needs to be restarted. After re-running the treebanker, I see that progresses on that particular sentence was not saved, and other filters will have to be reselected for the sentence again. The filter does narrow down the interpretations as aid, but must be removed or otherwise sentence cannot be saved. I have been using it in this way as well, helping to narrow, but removed before saving."
And a couple of screen shots:
If this isn’t a known bug, we definitely wanted to bring it to your attention. If there’s something we can do on our end (better than the described workaround) that would be good to know, too!