Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LogIncompletedScopes was removed but still documented #15243

Open
matteus-hemstrom-nltg opened this issue Nov 17, 2023 · 4 comments
Open

LogIncompletedScopes was removed but still documented #15243

matteus-hemstrom-nltg opened this issue Nov 17, 2023 · 4 comments

Comments

@matteus-hemstrom-nltg
Copy link

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

12.3.1

Bug summary

I'm not sure if this is a documentation issue or bug. I think that LogIncompletedScopes no longer works. It is documented here: https://docs.umbraco.com/umbraco-cms/reference/configuration/debugsettings

Specifics

I believe the logging code that used this setting was removed in this PR as part of moving logic into CoreScope.

This used to be part of ChildCompleted in Scope.cs:

if (_coreDebugSettings.LogIncompletedScopes)
{
    _logger.LogWarning("Uncompleted Child Scope at\r\n {StackTrace}", Environment.StackTrace);
}

Steps to reproduce

Not sure, but setting LogIncompletedScopes does nothing.

Expected result / actual result

LogIncompletedScopes should log warnings on uncompleted scopes. (Or update documentation.)

Copy link

Hi there @matteus-hemstrom-nltg!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@Migaroez
Copy link
Contributor

Hey @matteus-hemstrom-nltg, good catch and thank you for reporting this oversight. I will have a chat with the team if want to move this functionality in the corescope or remove the docs.

@Migaroez Migaroez self-assigned this Nov 22, 2023
@Migaroez Migaroez added the state/needs-investigation This requires input from HQ or community to proceed label Nov 22, 2023
@Migaroez
Copy link
Contributor

Hey @matteus-hemstrom-nltg, my apologies for the late reply. We have discussed this and think the best course of action is to reintroduce the logging back into cores cope in the same method.

@Migaroez Migaroez added community/up-for-grabs and removed state/needs-investigation This requires input from HQ or community to proceed labels Jan 29, 2024
@Migaroez Migaroez removed their assignment Jan 29, 2024
Copy link

Hi @matteus-hemstrom-nltg,

We're writing to let you know that we would love some help with this issue. We feel that this issue is ideal to flag for a community member to work on it. Once flagged here, folk looking for issues to work on will know to look at yours. Of course, please feel free work on this yourself ;-). If there are any changes to this status, we'll be sure to let you know.

For more information about issues and states, have a look at this blog post.

Thanks muchly, from your friendly Umbraco GitHub bot :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants