Open davidanthoff opened 4 years ago
There are various explanations for this one, if we exclude incorrect client behaviour, right? Either we are not properly processing some text update from the client and end up with an incorrect document content, or maybe we are missing a line offset computation somewhere?
I think we should add an incredibly verbose error message to get_offset
, one that stays just this side of telling us what text was called (i.e. offset position and that searches for the location/frequency of unicode characters). For the beta at least...
Nothing for us to do before we get some results from this, moving to Next
From crash reporting here.