Cole Tobin

Got the same thing in 1.0.0.2140933513: ``` Unhandled coroutine throwable java.util.NoSuchElementException: Sequence is empty. at kotlin.sequences.SequencesKt___SequencesKt.first(_Sequences.kt:111) at me.fornever.avaloniarider.rider.ProjectModelNodeExKt$getProjectContainingFile$2.invoke(ProjectModelNodeEx.kt:51) at me.fornever.avaloniarider.rider.ProjectModelNodeExKt$getProjectContainingFile$2.invoke(ProjectModelNodeEx.kt:40) at com.jetbrains.rd.util.reactive.SourceExKt$adviseUntil$1$1.invoke(SourceEx.kt:27) at com.jetbrains.rd.util.reactive.SourceExKt$adviseUntil$1$1.invoke(SourceEx.kt) at com.jetbrains.rd.util.reactive.IOptPropertyView$DefaultImpls.advise(Interfaces.kt:118) at com.jetbrains.rd.util.reactive.IOptProperty$DefaultImpls.advise(Interfaces.kt) at com.jetbrains.rd.util.reactive.OptProperty.advise(Property.kt:27)...

On Debian Bullseye, compiled with `-DUSE_SYSLOG -DDEBUG`, we only get this in `/var/log/messages`: ``` Jun 15 11:41:02 raspberrypi umtprd: [uMTPrd - Info] uMTP Responder Jun 15 11:41:02 raspberrypi umtprd: [uMTPrd...

Raspbian also does not include a `gcc-multilib` package for some reason, so I'm unable to test compiling a 32 bit binary on a 64 bit system.

I see I can do `Type = LinearEquation`, but I think the system could be simplified. If you want a horizontal line, set `Slope` to 0, and if you want...

Yeah. I figured that out. I still think it'd be nice to have a line annotation where I go, "Here's `X`, `Y`, and `Slope`. Figure out what line gives `b`...

It doesn't seem too hard. I'd be willing to make a patch that would allow that, but I don't think it'd be wise to break the API of `LineAnnotation`. Any...

I think infinity is ugly too, but that's how it was taught to me in school: a vertical line is just one with an infinite slope. As for a convenience...

I wonder if it could be reworked so `Type == LinearEquation` could use either `Intercept` *or* `X` and `Y`? So initially, all would be `double.NaN`, then when rendering, if the...

I am currently able to work around this by doing: ```cs LineAnnotation a = new() { ... }; ChartModel.Annotations.Add(a); a.EnsureAxes(); //

I haven't been investigating this, but I've still experienced this. I think it might be a race condition? Because even with my fix above, if I spam calls to remove...