David Calavera
David Calavera
> I think cargo-lambda should follow this common pattern. I'm all for this. I forgot that cargo-init was a thing.
I bumped into this problem too on a Windows build, and I really have no idea how to reproduce it, because it only happens in CI. If anyone is interested...
Can you point to some official documentation, or examples that show the right payload?
I don't have experience with either of those services. Any contributions are very welcome.
@dadgar we're investigating using Nomad at Netlify for a large heterogeneous deployment. Solving this issue would help us tremendously to decide whether to use Nomad. Is there anything we can...
for what I see in the Axum discussions, if we bind to `[::]:port` ipv4 and ipv6 should work, and we don't need the extra flag: https://github.com/tokio-rs/axum/discussions/834#discussioncomment-2302918
on second thought, maybe having the flag is good, but we should set the default that makes more sense for most people, which is probably binding to `[::]`
> I don't know why Rustfmt / format fails with the following error. Running cargo fmt locally reports no changes. Try running `make fmt` locally and pushing again.
This doesn't work on Windows unfortunately:  We might want to find a way to provide the default value conditionally to the OS.
You're probably right @aldanor