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

Be more resilient to module initialization failure #135

Open
tfmorris opened this issue Mar 7, 2024 · 0 comments
Open

Be more resilient to module initialization failure #135

tfmorris opened this issue Mar 7, 2024 · 0 comments
Assignees

Comments

@tfmorris
Copy link
Member

tfmorris commented Mar 7, 2024

Currently if any module loading/wiring/initialization fails, the entire server is disabled and just returns 500s with the initialization error. In some deployment scenarios, some of the modules might be ancillary not critical to the operation of the server (e.g. OpenRefine extensions). In this case it would be good if the server attempted to initialize the rest of the modules and continue operation.

This behavior should probably be controlled by a Butterfly property so that users can choose whether they want the historical behavior or the new behavior.

This was the second half of #13 which didn't get implemented.

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

1 participant