Feature Request: Add error details to 500 errors

[ravensorb]

It appears that almost all 500 errors do not provide any detail to track down what caused the error. There is nothing in the HTTP resource and there is nothing in any of the log files.

Request -- all 500 errors should at the very least provide a full stack trace and message in the structr log files.

[amorgner]

Hm, I see your point, but it's not a bug, rather a feature request.

[eric-schleicher]

+1

I too find this challenging

[ravensorb]

Any update to this?

[eric-schleicher]

+ 10 The visibility of error/event logging is a significant drag on our ability to use some of the more powerful capabilities of structr.

I find myself avoiding StructrScript almost in it's entirety since it's impossible to tell what goes on inside the box. worse yet... when there are issues, the service will provide 200/201 responses, when in actuality unvalidatable (underlying) errors and DML in the meta layer falls on the floor (e.g. inside function attributes, methods) .

[amorgner]

We'll add a lot more logging for the server-side scripting soon.

[vigorouscoding]

We just added lots of logging to StructrScript functions (see 6be7320) and made a lot of those functions a bit more strict.

You will see a lot more log entries for wrong parameters and for caught exceptions in structrscript functions. You can test this for example by writing ${inc_counter('test')} which will result in error output because counters need to be numeric.

[ravensorb]

Is there an update to the logging for server side issues as well?

[amorgner]

It's all about server-side logging (StructrScript and JavaScript are executed on the server).

[ravensorb]

Excellent. How about the REST interface and 500 errors - has any improvement been made there to include more details?