🐛 Bug Report: Dart Function Runtime Doesn't Handle Errors

[stnguyen90]

👟 Reproduction steps

1. Deploy a dart function like:

Future<void> start(final req, final res) async {
  throw new Exception('panic!');
}

2. Execute the function

👍 Expected behavior

The execution has stderr with the panic! message

👎 Actual Behavior

An internal curl error has occurred within the executor! Error Msg: Operation timed out

🎲 Appwrite version

Version 1.0.x

💻 Operating system

Linux

🧱 Your Environment

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[InfiniteVerma]

I'd like to work on this .

[DEADSEC-SECURITY]

This is a problem in python too. No print or logs are showing up when a exception crashes the program which is not the expected behavior. It should display the past stdout too as well as traceback just like AWS Lambda does for example or the normal "run in console"

[DEADSEC-SECURITY]

@InfiniteVerma anyway I can be useful? This is posing as a huge problem for debugging in our setup and I need this fixed ASAP so we can have more productivity.

I'm a python dev and also know docker pretty well so if I can be of use let me know

[DEADSEC-SECURITY]

The problem seems to be happening in the file executer.php in the part of the code in the image. The executer response doesn't seem to be returning the traceback or log when a 500 code is raised so it defaults to Internal Runtime Error.

Request header of the function where that code is located:
App::post('/v1/execution')

[stnguyen90]

The problem seems to be happening in the file executer.php in the part of the code in the image. The executer response doesn't seem to be returning the traceback or log when a 500 code is raised so it defaults to Internal Runtime Error.

Request header of the function where that code is located: App::post('/v1/execution')

@DEADSEC-SECURITY this specific problem you're mentioning is related to issue #4594 and already has a PR.