Refactor and cleanup

[andrejridzik]

Change

Slight refactoring and cleanup of the code.

This change includes addition of Ruff formatter and creation of Github workflows.

How to Test

Does not require any additional testing as functionality is not being changed

Checklist

• Tests have been added or updated to reflect the changes, or their absence is explicitly explained.
• Documentation has been added or updated to reflect the changes, or their absence is explicitly explained.
• A self-review has been conducted checking:
  • No unintended changes have been committed.
  • The changes in isolation seem reasonable.
  • Anything that may be odd or unintuitive is provided with a GitHub comment explaining it (but consider if this should not be a code comment or in the documentation instead).
• All CI checks pass before pinging a reviewer, or provide an explanation if they do not.

Related Issues

None

[marcel-vesely-kinit]

The only thing I'm unsure of is the use of asyncio.run that I've commented for you.

Both versions, with or without the asyncio.run wrapper did work correctly. Actually it seems like that the current contents of the start_async_thread function might be doing a very similar job to the asyncio.run function.

[marcel-vesely-kinit]

I've actually encountered a warning regarding the proper cleanup of resources, but it's not related to the way how we start off the async function in a new thread (or at the very least, I get the same warning regardless of whether I use the old or the new implementation of functions found in the threads.py file)

Warning: UserWarning: resource_tracker: There appear to be 1 leaked semaphore objects to clean up at shutdown

How to reproduce (if you're interested): Start the app from terminal using uvicorn command and then, once everything is set up, terminate the app by using CTRL C shortcut.

TODO: For now I shall put it to backlog, it's not that pressing at the moment. The number of leaked semaphores doesn't increase with the number of spawned new threads utilizing a scheduler which is nice...

[andrejridzik]

I've actually encountered a warning regarding the proper cleanup of resources, but it's not related to the way how we start off the async function in a new thread (or at the very least, I get the same warning regardless of whether I use the old or the new implementation of functions found in the threads.py file)

Warning: UserWarning: resource_tracker: There appear to be 1 leaked semaphore objects to clean up at shutdown

How to reproduce (if you're interested): Start the app from terminal using uvicorn command and then, once everything is set up, terminate the app by using CTRL C shortcut.

TODO: For now I shall put it to backlog, it's not that pressing at the moment. The number of leaked semaphores doesn't increase with the number of spawned new threads utilizing a scheduler which is nice...

Adding a link to the newly created issue #24 that captures this.