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
Failure to load provider/plugin not reported, anywhere [CORE4478] #4798
Comments
Commented by: Sean Leyne (seanleyne) Restated the Summary for better reading |
Modified by: Sean Leyne (seanleyne)summary: No feedback from a provider failed to load => Failure to load provider/plugin not reported, anywhere |
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: @AlexPeshkoff I like an idea of adding configuration info to distinguish required and not-required plugins. But may be better mark plugins that may be not loaded? Currently I know only one in default configuration - engine12 in client case. When adding non-default entries mentioning in them not-required plugins will be possible but hardly needed. |
Commented by: @AlexPeshkoff Added parameter Required to plugins configuration. Sample - section in plugins.conf Plugin = Engine12 { will make plguin manager raise an error when module for this plugin is missing. When module is bad (empty, invalid format, etc.) error is reported always no matter of Required value. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 Beta 1 [ 10332 ] |
Commented by: @aafemt What is default value for this parameter? |
Commented by: @AlexPeshkoff false |
Commented by: @aafemt "true" would be better. With "false" users will have a hard time looking for a mistype in pligin's name. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Cannot be tested |
Submitted by: @aafemt
If a plugin cannot be loaded, there is no information about it anywhere. Even if the plugin is a mission-critical security-related one. IMHO, there must be a way to configure a plugin as a "must work one" and the engine must raise error if such plugin failed to load.
Commits: 2b066db FirebirdSQL/fbt-repository@acef6a6
The text was updated successfully, but these errors were encountered: