U4-9605 - Need a debug switch to trace uncompleted scopes

Created by Stephan 07 Mar 2017, 11:41:58 Updated by Claus Jensen 08 Mar 2017, 12:07:08

Tags: Unscheduled

Subtask of: UAASSCRUM-810

If we forget to complete a nested scope, we end up having errors because the outer scope cannot complete. It can be a pain to figure out where the Complete call is missing. So there is some code in Scope to log the proper stack trace. But we cannot always do it, even in Debug log4net mode, as it can be verbose.

Need a magic appSetting to enable it.

Comments

Stephan 07 Mar 2017, 11:44:05

PR https://github.com/umbraco/Umbraco-CMS/pull/1782

test... you need to break Core somehow by removing a scope.Complete somewhere, then activate the setting, then rejoice that the log contains a nice stack trace.


Priority: Normal

Type: Task

State: Fixed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version:

Sprint: Sprint 54

Story Points:

Cycle: