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.

Sign up for GitHub

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

Jump to bottom

Bug: Inconsistent levels when creating Entry from Logger #1158

Closed

iamolegga opened this issue Jul 20, 2020 · 28 comments · May be fixed by #1163

Labels

iamolegga commented Jul 20, 2020

Example: https://play.golang.org/p/zZODKE5p6SD

Is this a bug?

Collaborator

markphelps commented Jul 20, 2020

@iamolegga that does look odd, I added some more output here: https://play.golang.org/p/Xe6QQx1igjo

You can see the entry is actually logging at the right level, ie it doesnt output 'debug' level messages since the root logger is configured to log at 'info' and above... however when you call entry.Level it still outputs level: panic which is incorrect.

logger level: info, entry level: panic
time="2009-11-10T23:00:00Z" level=info msg="I should be printed" foo=bar
logger level: info, entry level: panic

So I'm inclined to say that yes, it is a bug in that entry.Level does not seem to report the actual 'inherited level' that it is logging at.

markphelps added the bug label

hcmlinj mentioned this issue

Fix inconsistent levels when creating Entry from Logger issue #1163

Open

randomSignal pushed a commit to randomSignal/logrus that referenced this issue


          Bug: Inconsistent levels when creating Entry from Logger sirupsen#1158

84a78f5

randomSignal mentioned this issue

Bug: Inconsistent levels when creating Entry from Logger #1158 #1172

Closed

randomSignal pushed a commit to randomSignal/logrus that referenced this issue


          Bug: Inconsistent levels when creating Entry from Logger sirupsen#1158

67c9686

randomSignal mentioned this issue

Bug: Inconsistent levels when creating Entry from Logger #1158 #1173

Closed

randomSignal pushed a commit to randomSignal/logrus that referenced this issue


          Bug: Inconsistent levels when creating Entry from Logger sirupsen#1158

cf7543f

randomSignal mentioned this issue

fix Bug: Inconsistent levels when creating Entry from Logger #1158 #1174

Closed

github-actions bot commented Sep 12, 2021

This issue is stale because it has been open for 30 days with no activity.

github-actions bot added the stale label

Author

iamolegga commented Sep 12, 2021

I believe this isn't fixed yet

github-actions bot removed the stale label

github-actions bot commented Oct 13, 2021

This issue is stale because it has been open for 30 days with no activity.

github-actions bot added the stale label

Author

iamolegga commented Oct 13, 2021

ping

github-actions bot removed the stale label

github-actions bot commented Nov 14, 2021

This issue is stale because it has been open for 30 days with no activity.

github-actions bot added the stale label

Author

iamolegga commented Nov 14, 2021

not fixed

github-actions bot removed the stale label

github-actions bot commented Dec 15, 2021

This issue is stale because it has been open for 30 days with no activity.

github-actions bot added the stale label

Author

iamolegga commented Dec 15, 2021

not fixed

github-actions bot removed the stale label

github-actions bot commented Jan 15, 2022

This issue is stale because it has been open for 30 days with no activity.

github-actions bot added the stale label

Author

iamolegga commented Jan 15, 2022

not fixed

github-actions bot removed the stale label

github-actions bot commented Feb 15, 2022

This issue is stale because it has been open for 30 days with no activity.

github-actions bot removed the stale label

github-actions bot commented Mar 18, 2022

This issue is stale because it has been open for 30 days with no activity.

github-actions bot added the stale label

Author

iamolegga commented Mar 18, 2022

not fixed

github-actions bot removed the stale label

github-actions bot commented Apr 18, 2022

This issue is stale because it has been open for 30 days with no activity.

github-actions bot added the stale label

Author

iamolegga commented Apr 18, 2022

not fixed

github-actions bot removed the stale label

github-actions bot commented May 19, 2022

This issue is stale because it has been open for 30 days with no activity.

github-actions bot added the stale label

Author

iamolegga commented May 19, 2022

not fixed

github-actions bot removed the stale label

github-actions bot commented Jun 19, 2022

This issue is stale because it has been open for 30 days with no activity.

github-actions bot added the stale label

Author

iamolegga commented Jun 20, 2022

not fixed

github-actions bot removed the stale label

github-actions bot commented Jul 21, 2022

This issue is stale because it has been open for 30 days with no activity.

github-actions bot added the stale label

Author

iamolegga commented Jul 21, 2022

not fixed

github-actions bot removed the stale label

github-actions bot commented Aug 21, 2022

This issue is stale because it has been open for 30 days with no activity.

github-actions bot added the stale label

Author

iamolegga commented Aug 22, 2022

not fixed

github-actions bot removed the stale label

Contributor

edoger commented Aug 30, 2022

@iamolegga The library is already inactive, maybe you should try another solution! Just like me.

github-actions bot commented Sep 30, 2022

This issue is stale because it has been open for 30 days with no activity.

github-actions bot added the stale label

github-actions bot commented Oct 14, 2022

This issue was closed because it has been inactive for 14 days since being marked as stale.

github-actions bot closed this as completed

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