search

denoland / deploy_feedback

For reporting issues with Deno Deploy
https://deno.com/deploy
74 stars 5 forks source link

[Bug]: execution abruptly killed? #672

Open morgothulhu opened 2 months ago

morgothulhu commented 2 months ago

Problem description

My execution seems to have been killed (outside of my code paths). No console/log around the time of the abrupt end of request.

Steps to reproduce

No real pointers other than post-mortem log.

https://dash.deno.com/projects/trooper-sms/logs?filters=%7B%22query%22%3A%2201HZN16VH7RKJTNTT14RK3KAWV%22%2C%22timeRangeOption%22%3A%22recent%22%2C%22recentValue%22%3A%2224hours%22%2C%22customValues%22%3A%7B%22start%22%3A%222024-06-05T20%3A17%3A52.000Z%22%2C%22end%22%3A%222024-06-06T01%3A48%3A52.920Z%22%7D%2C%22logLevels%22%3A%7B%22debug%22%3Afalse%2C%22info%22%3Afalse%2C%22warning%22%3Afalse%2C%22error%22%3Afalse%7D%2C%22regions%22%3A%7B%22gcp-asia-northeast1%22%3Afalse%2C%22gcp-asia-south1%22%3Afalse%2C%22gcp-asia-southeast1%22%3Afalse%2C%22gcp-australia-southeast1%22%3Afalse%2C%22gcp-europe-west2%22%3Afalse%2C%22gcp-europe-west3%22%3Afalse%2C%22gcp-me-west1%22%3Afalse%2C%22gcp-southamerica-east1%22%3Afalse%2C%22gcp-us-east4%22%3Afalse%2C%22gcp-us-south1%22%3Afalse%2C%22gcp-us-west2%22%3Afalse%7D%7D

No log/possible explanation after 6/5/2024, 1:28:18 PM timestamp

Expected behavior

Execution to continue through code paths

Environment

No response

Possible solution

No response

Additional context

No response

rbetts commented 2 months ago

I reviewed the logs for this project but only see application errors, as you state in this report. I don't see any platform limit events (like CPU limit or memory limits). Can you give some more context about this application? For example, are these short lived request/responses? Longer lived executions? How did you detect the termination?

morgothulhu commented 2 months ago

thanks @rbetts . The app is long-running (websocket based) for handling Twilio Voice data stream.

I hooked up the unhandledrejection global event - to see if I can capture any unhandled exception - but no luck on that front.

This is a fresh repro - same - no logs/indications of what happened: logs

Re: expected data paths. I have a proper close path, with many logs as a result. This is a "valid" log of a proper completion: logs