search

YorCreative / Laravel-Scrubber

A Laravel package to scrub sensitive information that breaks operational security policies from being leaked on accident or not by developers.
MIT License
140 stars 12 forks source link

IMPORTANT: Scrubber is consuming stacktrace off the logs #28

Closed Whizboy-Arnold closed 1 year ago

Whizboy-Arnold commented 1 year ago

Hey, @yordadev, there is this thing i noticed that my stacktraces on exception are not logged instead i have this statement {"exception":[]}. The exception itself is however not consumed as i can view it from the request result on the client. Could you clarify if this is the intended behavior? and if so provide an opt-out option in the config. Otherwise if not provide for a way for stack traces to still be written in the logs.

yordadev commented 1 year ago

This is not intended behavior will need to look into this. I'm not entirely sure when I'll get a chance to dig into this. I need more information how to closest mimic the demo instance to recreate this?

🍺 I welcome you or anyone else to give it the old college try to at-least identify the issue here in the meantime 🍻 🙏🏼

yordadev commented 1 year ago

I think this was resolved in 2.6 release. Reopen if issue continues.

Whizboy-Arnold commented 1 year ago

Hey thank you will check it out

On Wed, 21 Jun 2023, 4:58 am Yorda, @.***> wrote:

Closed #28 https://github.com/YorCreative/Laravel-Scrubber/issues/28 as completed.

— Reply to this email directly, view it on GitHub https://github.com/YorCreative/Laravel-Scrubber/issues/28#event-9586871540, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKHNIPXKOL37UAGMFNDFZSDXMJIMHANCNFSM6AAAAAAWRIUSGA . You are receiving this because you authored the thread.Message ID: @.***>