Ryan

Facing the same error on MacOS, same installation method. The language server works great for a few minutes, then starts throwing this error on every keystroke - haven't been able...

I noticed you mentioned that nvim is doing something weird with the initialization, so I think this may be related: Running `:LspRestart` always fails, but it gives a different error....

Hey there @HoytRen, you should be able to create the PR from your fork without needing to first pass unit tests - and then we can check out what is...

```go type HealthResponse struct { StateService bool `json:"state_service"` ShareService bool `json:"share_service"` DASStatus DasStateResponse `json:"das_status"` HeaderSyncing bool `json:"header_syncing"` } ``` @renaynay were you thinking something like this? Thoughts: - should it...

Yes, makes sense - two things: 1. Should we maybe put this in a `/status` endpoint, and keep `/health` as a `{"status": "ok"}`? I noticed that the rpc at your...

Not worth pursuing until the refactorings, so removing from the roadmap for now

I am starting to become really conflicted about how the interface between the cmd/flags and the node subpackages should look. These flags and their parsing are clearly logically closer to...

`FAIL: TestFullReconstructFromLights (32.60s)`

@renaynay The main issue currently seems to be with how the config works in `core/testing.go` - haven't been able to figure it out yet though

@renaynay There are now only 4 tests that are failing, but I can't figure out why yet. 3 of them pass when run individually, but get a context timeout when...