Roger Lipscombe

I've looked into a couple of options: 1. Putting this in `proc_lib:spawn_opt` -- that's brittle, 'cos `init_p` is exported as-is, relied on by a few other things, and I have...

I have the same problem. If I use `source

I fixed this in my build by passing the correct private key as a secret, and then configuring git to use it. ``` docker build \ --ssh default \ --secret...

This also seems to be the cause of crashes in the erlang-ls extension in VS Code when browsing the OTP 27 source code.

I just checked with a project over Remote-SSH, and the colouring doesn't work there, either.

Cut down repro: ``` Expected = [[],[]]. Bytes = . {ok, Actual, _} = redo_redis_proto:parse([], {raw, Bytes}). % Nope! Actual = Expected. ```

So, thinking it might be a problem with the ``, rather than ``, I tried the following: ``` t('', 1000); ``` ...which returns: ``` ``` ...which is still wrong. Where...

I've been wracking my brains for ways to wrap `cowboy_router:compile` or the `cowboy_router` middleware, or to wrap the individual handlers, but I can't come up with anything that doesn't feel...

After some thought, I've come up with the following, which doesn't require any cowboy changes: - Replace the current `Handler` with a tuple, `{Handler, HandlerOpts}` - Replace the current `HandlerOpts`...

The parse transform only works on explicit calls to ets:fun2ms and dbg:fun2ms, based on a (very) brief skim of the code, so I don't see the need for complicating it...