Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Compile errors don't make it to the log on Linux apps

See original GitHub issue

In a .csx function, change return to retur to break it, and click Save and Run. All you get is:

2018-04-19T21:40:44.047 [Error] System.Private.CoreLib: Exception while executing function: Functions.HttpTriggerCSharp1. Microsoft.Azure.WebJobs.Script: Script compilation failed. 2018-04-19T21:40:44.048 [Error] Executed ‘Functions.HttpTriggerCSharp1’ (Failed, Id=a7042c3f-6406-4be9-a780-b7555cfbf943)

It’s missing all the detailed compile error info.

Issue Analytics

State:
Created 5 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

1reaction

davidebbocommented, Jun 5, 2018

We now understand what’s going on.

On Windows, we only log the compile error at the time the .csx file is saved, and never when it’s run.

But on Linux, where we don’t have reliable file change notification, @ahmelsayed implemented a workaround where each time a file is saved in the Portal, he restarts the host. As a result, the code path that logs errors on file saves (based on notifications) never takes place, and the errors never make it to the log.

1reaction

paulbatumcommented, Apr 20, 2018

@fabiocav Is this a runtime issue, or is it something about the portal not consuming the structured error log when running against linux?