asharpe

aws/session-manager-plugin#94 appears to address the issue with SSH reporting a bad packet length, at least in some cases. The test applied was to intentionally shut down an EC2 instance while...

It looks like the python version handles this already - https://github.com/nginxinc/crossplane/blob/master/crossplane/ext/lua.py

Apologies, this feature already exists - https://github.com/nginxinc/nginx-go-crossplane/blob/main/parse.go#L52

On reflection, this is a bug in the parser which is not solved by ignoring the directive. ~~When the directive is ignored, the parser will still eat the config and...

So I haven't actually addressed the bug here, it still stands. A config file which illustrates the issue I have is ``` http { server { header_filter_by_lua_block { cors_allow_for([[some\.domain\.name$]]) }...

My current thinking is that `*_by_lua` are already handled as strings, `*_by_lua_file` are just directives with args, it's just `*_by_lua_block` that's causing an issue. This change moves the logic into...

My workaround was to edit `/etc/netplan/50-cloud-init.yaml` in the lima VM to add an external nameserver, eg. ``` --- /etc/netplan/50-cloud-init.yaml 2025-04-08 12:08:39.361620679 +1000 +++ /etc/netplan/50-cloud-init.yaml 2025-04-08 10:14:33.399934631 +1000 @@ -6,6 +6,7...

See #167