Results 29 comments of Lawrence D'Anna

@kdaily > Have you seen this behavior in the wild with an actual request? Yes, I encountered it when I was writing some unit tests for my application using s3mock.

um, sorry I didn't respond to that question @kdaily. No actual AWS endpoints don't generate responses like that one as far as I know.

thanks for responding! What you've got would work, but I think returning an error directly from `First()` and `Next()` would be more go-like and easier to use. What do you...

doesn't adding a new method to the interface also break the API?

I just tried it again in a fresh environment and I still get the erorr ubuntu 24.04, python 3.12.3 ``` certifi==2024.7.4 charset-normalizer==3.3.2 colorama==0.4.6 conan==2.5.0 distro==1.8.0 fasteners==0.19 idna==3.7 Jinja2==3.1.4 MarkupSafe==2.1.5 patch-ng==1.17.4...

I have added a dockerfile to the example run `docker build .` and it should reproduce

well, I found a workaround ``` def build_requirements(self): # when this recipe is being used as a build tool, hide all of its # requirements to avoid graph cycle errors...

Yea, but couldn't the (FP, LR) pair be stored at the end (highest address) of the stack frame, like a normal C function would do? That wouldn't alter the calling...

Ugh, that's unfortunate. Well if y'all ever make an ABI1 I guess it could be fixed there :/