6 ms·

If I'm reading this correctly, then AWS Support dropped the ball here but this isn't a bug in lambda. This is the documented behavior of the lambda runtime. Th

If I'm reading this correctly, then AWS Support dropped the ball here but this isn't a bug in lambda. This is the documented behavior of the lambda runtime. The document is long, and the examples seem contrived, so anyone is free to correct me but as I understand it the lambda didn't crash, after you returned 201, your lambda instance was put to sleep. You aren't guaranteed that any code will remain running after your lambda "ends". I am not sure why AWS Support was unable to communicate this OP. If you are using Lambda with a function URL, you aren't guaranteed that anything after you return your http response remains running. I believe Lambda has some callbacks/signals you can listen to, to ensure your function properly cleans up before the Lambda is frozen, but if you want the lambda to return as fast as possible it seems you are better off having your service publish to an SQS queue instead.

Everdred2dx 1y ago
Yep. I've ran into this using Bugsnag for reporting on unhandled exceptions in Python-based lambda functions. The exception handler would get called, but because the library is async by default the HTTP request wouldn't make it out before the runtime was torn down. I sympathize with OP because debugging this was painful, but I'm sorry to say this is sort of just a "you're holding it wrong" situation.
semiquaver 1y ago
This document is bizarre. The author is so confidently verbose about something they are clearly misunderstanding, and have been told as much dozens of times. It’s humbling, in a way, to think of times I’ve felt this strongly about something and to consider the possibility I could have been this wrong.
- tough 1y ago
  stubbornness is a very human thing
  - Zambyte 1y ago
    The juxtaposition between this reply and the sibling > It's pretty clearly written by GPT. is quite funny
    - tough 1y ago
      ChatGPT is totally onboard on going on with your nonsense and expand on it tho
- johnfn 1y ago
  It's pretty clearly written by GPT.
  - x3n0ph3n3 1y ago
    Can you share some of the tell-tale signs you pick up on? Edit: I see he's the CTO of an AI company.
    - johnfn 1y ago
      It's never a slam-dunk with AI-generated content, but some of the signs I notice are: - Constant bulleted lists with snappy, non-punctuated items. - Single word sentences to emphasize a point ("It was disciplined. Technical. Forensic.") - The phrasing. e.g. the part about submitting to Reddit: "This response was disproportionate to the activity involved: a first-time technical post, written with precision, submitted to the relevant forum, and not yet visible to any other user." Who on earth says "written with precision" about their own writing? To be clear, I don't think it's a fabricated account. I also don't think it was a one-shot. OP probably iterated on it with GPT for quite some time.
    - appreciatorBus 1y ago
      He’s already added an entry about the whole incident to his resume: https://lyons-den.com/CV/David_Lyon_CTO_CV_2025.pdf https://lyons-den.com/CV/David_Lyon_CTO_CV_2025.pdf EDIT: he has added three(!) separate mentions of the same incident to his résumé
      - tczMUFlmoNk 1y ago
        At least it is helpfully located in the "Thought Leadership" section as an early flag for the reader.
      - redleader55 1y ago
        This guy is obviously the most senior person in a small startup. To me personally, calling yourself a CTO with a CV entry that amounts to what an L5 in a FAANG does in a half, is a bit ridiculous. What title would HN recommend for such a position, instead?
happytoexplain 1y ago
Consider that this conversation is even being had - that you are even in the situation to be writing what you are writing. "Failure" != "Bug"
encomiast 1y ago
> I am not sure why AWS Support was unable to communicate this OP. Maybe we should be asking why the OP was not able to hear what AWS was telling them. I think there is a fairly troublesome cognitive bias that gets flipped on when people are telling you that you're wrong — especially when all your personal branding and identity seems to be about you being right.
cldcntrl 1y ago
> If I'm reading this correctly, then AWS Support dropped the ball here but this isn't a bug in lambda. This is the documented behavior of the lambda runtime. AWS Support is generally ineffective unless you're stuck on something very simple at a higher level of the platform (e.g. misunderstanding an SDK API). Even with their higher tier support - where you can summon a subject matter expert via Chime almost instantly - they're often clueless, and will confidently pass you misleading or incorrect information just to get you off the line. I've successfully used them as a very expensive rubber ducky, but that's about it.

Everdred2dx 1y ago

Yep. I've ran into this using Bugsnag for reporting on unhandled exceptions in Python-based lambda functions. The exception handler would get called, but because the library is async by default the HTTP request wouldn't make it out before the runtime was torn down. I sympathize with OP because debugging this was painful, but I'm sorry to say this is sort of just a "you're holding it wrong" situation.

semiquaver 1y ago

This document is bizarre. The author is so confidently verbose about something they are clearly misunderstanding, and have been told as much dozens of times. It’s humbling, in a way, to think of times I’ve felt this strongly about something and to consider the possibility I could have been this wrong.

tough 1y ago
stubbornness is a very human thing
- Zambyte 1y ago
  The juxtaposition between this reply and the sibling > It's pretty clearly written by GPT. is quite funny
  - tough 1y ago
    ChatGPT is totally onboard on going on with your nonsense and expand on it tho
johnfn 1y ago
It's pretty clearly written by GPT.
- x3n0ph3n3 1y ago
  Can you share some of the tell-tale signs you pick up on? Edit: I see he's the CTO of an AI company.
  - johnfn 1y ago
    It's never a slam-dunk with AI-generated content, but some of the signs I notice are: - Constant bulleted lists with snappy, non-punctuated items. - Single word sentences to emphasize a point ("It was disciplined. Technical. Forensic.") - The phrasing. e.g. the part about submitting to Reddit: "This response was disproportionate to the activity involved: a first-time technical post, written with precision, submitted to the relevant forum, and not yet visible to any other user." Who on earth says "written with precision" about their own writing? To be clear, I don't think it's a fabricated account. I also don't think it was a one-shot. OP probably iterated on it with GPT for quite some time.
  - appreciatorBus 1y ago
    He’s already added an entry about the whole incident to his resume: https://lyons-den.com/CV/David_Lyon_CTO_CV_2025.pdf https://lyons-den.com/CV/David_Lyon_CTO_CV_2025.pdf EDIT: he has added three(!) separate mentions of the same incident to his résumé
    - tczMUFlmoNk 1y ago
      At least it is helpfully located in the "Thought Leadership" section as an early flag for the reader.
    - redleader55 1y ago
      This guy is obviously the most senior person in a small startup. To me personally, calling yourself a CTO with a CV entry that amounts to what an L5 in a FAANG does in a half, is a bit ridiculous. What title would HN recommend for such a position, instead?

happytoexplain 1y ago

Consider that this conversation is even being had - that you are even in the situation to be writing what you are writing. "Failure" != "Bug"

encomiast 1y ago

> I am not sure why AWS Support was unable to communicate this OP. Maybe we should be asking why the OP was not able to hear what AWS was telling them. I think there is a fairly troublesome cognitive bias that gets flipped on when people are telling you that you're wrong — especially when all your personal branding and identity seems to be about you being right.

cldcntrl 1y ago

> If I'm reading this correctly, then AWS Support dropped the ball here but this isn't a bug in lambda. This is the documented behavior of the lambda runtime. AWS Support is generally ineffective unless you're stuck on something very simple at a higher level of the platform (e.g. misunderstanding an SDK API). Even with their higher tier support - where you can summon a subject matter expert via Chime almost instantly - they're often clueless, and will confidently pass you misleading or incorrect information just to get you off the line. I've successfully used them as a very expensive rubber ducky, but that's about it.