Lars Kellogg-Stedman

Thanks, that was very helpful. I've identified the culprit, but I remain confused. First, the entire configuration is available [here](https://github.com/larsks/firenvim-neovim-crash). There is a file `lua/firenvim.lua` that causes firenvim to crash...

> Is this some sort of naming conflict? Indeed, if I name it anything else, everything works as expected.

> Have you been able to use your neovim config (with a file named firenvim.lua) on previous neovim versions? No, this was all part of ditching my old `init.vim` configuration...

The [custom openapi example in the documentation](https://github.com/kubernetes-sigs/kustomize/blob/master/examples/customOpenAPIschema.md) suggests strongly that the `openapi` keyword merges in the custom schema rather than **completely replacing** the compiled-in schema. We should update the example...

@snuggie12 I've implemented something like that [here](https://github.com/nerc-project/openshift-schemas).

Or like this, trying to connect to a local packet BBS: ``` [0L] N1LKS>KZ2X-1:(SABME cmd, p=1) [0.1] N1LKS>KZ2X-1:(SABME cmd, p=1) [0.3] KZ2X-1>N1LKS:(UA res, f=1) Stream 5: Connected to KZ2X-1. (v2.2)...

It looks like this is definitely a direwolf problem; I see the same behavior using [agwterm](https://www.soundcardpacket.org/6AGWPrograms.aspx). I've open an issue at .

I'm back. I wanted to share this output from setting `AGWPE_DEBUG=true`; the **response** from the remote seems to be handled as a new connection rather than as a reply to...

I'm using the recently released direwolf 1.7. I see the same behavior with the prior release as well.

I'm collecting fixes in https://github.com/larsks/openapi2jsonschema. I've merged this patch into that repository.