Open planetchili opened 1 year ago
I have the same problem that for me on some machines for some reason the stack trace is off by one line. While this is not really an issue in most cases because it is clear where the exception actually comes from, this can be many misleading at times.
I find that when I look at the snippets, the line indicated is always the next line (skipping whitespace) after the one containing the call.
I see that this is not the case in the screenshots provided in the repo readme. Is there any way to get the resolver to indicate the correct line?