-
Notifications
You must be signed in to change notification settings - Fork 30
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
Handled exceptions in python files #97
base: main
Are you sure you want to change the base?
Conversation
Once check and tell me if I have to do something |
Can you update me |
Hi @Sai-ganesh-0004 , |
any updates |
@devansh-shah-11 any updates? |
any updates @devansh-shah-11 |
def Main_page(): | ||
def main_page(): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did you renamed the function?
@Sai-ganesh-0004 could you please solve this errors in tests.
|
@Devasy23 upgrade this to level3, this deserves to be level3 due to extensive work that has to be done...! |
@SparshKhanna0001 i understand your concern but it is already decided by mentors that it is level 2 but it all errors are solved then maybe we can give level 3. @Sai-ganesh-0004 please complete the necessary |
Description
This update introduces exception handling for the concurrent execution of the FastAPI and Flask applications. The changes ensure that if either application fails to start, an error message is logged, helping to diagnose issues during startup. The motivation for this enhancement is to improve the reliability and maintainability of the application by providing clear logging of errors.
**Fixes #96
Type of change
How Has This Been Tested?
The following tests were conducted to verify the changes:
Both the FastAPI and Flask applications were started simultaneously using the updated script.
The applications were intentionally made to throw exceptions (e.g., by pointing to incorrect configurations) to verify that the error logging works correctly.
No other tests were run since this change pertains primarily to startup error handling.
Test A: Verified that both applications start without issues under normal conditions.
Test B: Confirmed that errors are logged when one of the applications fails to start.
Checklist: