mooncell07 / azaka Goto Github PK

At the moment, at user level the code is callback styled and due to that users can't do synchronization and consumption of results.

For this issue I am thinking of writing a different runner API which will behave like asyncio.run().

Hey Nova,

First off, thank you so much for building azaka, it's an incredible tool and I can't thank you more for open-sourcing it. I scheduled a call with you through the website (there was a link and then I scheduled for basically now, however it doesn't seem like you are available at the moment). Do let me know where and how we can chat!

Appreciate it, and apologies for creating an issue - for I could not find any other active platform to contact you through!

Problem

When a SET command is issued with a bad ID, the API sends an undocumented error of type invalid. Due to it not being present in the
dict of errors a KeyError is raised.

Fix

Just need to implement an error type InvalidQueryError (query because the error body says so).

Here for some reason the self.subscriber is getting ok even though there's an if condition specifically for that.

Problem

Azaka needs a dump parser for VNDB's database dumps.

Fix

I have made another repo for handling dumps and it will be an optional dependency.

Additionally typing.Final is not present in py 3.7 and since 3.7 has reached its EOL, so I think the best thing to do is to make requirement ^3.8 and as for shutdown_default_executors a
version check can be implemented.

The documentation at the moment doesn't really explain the stuff well but I will continue to write it in same way and ones it's complete i will enhance it.

Currently even if a handler is added using on_error for eg:

@client.on_error
def handler(error):
    ...

The errors are still raised.