vulnerability question, log handler problem, database connection exception about octane HOT 6 CLOSED

i found that the second problem can be solved by turning the singleton binding 'log' into scoped:
/vendor/laravel/framework/src/Illuminate/Log/LogServiceProvider.php

PR didn't work for me

i can do it myself, but how many places in laravel should i still think about? is this production-ready? could it be the right solution to redefine all singleton bindings as scoped?

from octane.

Hi there,

Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

• Laracasts Forums
• Laravel.io Forums
• StackOverflow
• Discord
• Larachat
• IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!

Thanks.

from octane.

@driesvints

Hey, why did you close the problem? I have 3 important questions about the work of octane, could you show more respect to the consumer and give advice?

from octane.

These questions can be asked on a support channel. We generally only handle bug reports on this issue tracker.

from octane.

@driesvints

you just threw me over to try my luck somewhere else, even though I clearly attached two problems, two obvious errors and a potential security issue. thanks)

from octane.

could you give a couple of comments about this?

Could you help me understand what the problem is?

what could be the reason for such unexpected behavior?

These are support questions. This is open source, not free support.

from octane.