Pavel Kirilin

Can you please show me how you use it? Because it seems like something is purging out `__name__` attribute of methods.

I tried this snippet and seems like all methods have `__name__` by default. ```python for name, met in inspect.getmembers(TaskClass): if not callable(met): continue print(name) print(met.__name__) ``` Which led me to...

I don't think it should have worked in the first place. The tasks were intended to be functions, and currently, classes and objects are not officially supported. We can add...

@lindycoder, can you please share with me MRE of the codebase that works on previous version and doesn't work since the 0.11.16. Because the code you sent doesn't work on...

@scott-boost, yeah, thanks for noticing. My bad. I was running it on `0.11.14`. It doesn't work on `0.11.15` because of `__name__` and doesn't work on `0.11.14` because tasks are not...

@lindycoder, okay, clear point. Can you describe the framework you have a little bit so I can re-create something similar to test out my solutions?

Seems like this issue is more related to taskiq-faststream integration.

Does it work on vanila taskiq?

You can obtain the current `task_id` from `context.message.task_id`. Also, I'm not sure if [Context](https://github.com/taskiq-python/taskiq/blob/2620fc36074f37bdbe6af4603fabad659260bdf7/taskiq/context.py#L11) has a method named `set_progress`. In order to set a progress, you need to depend on...

Not really. Previous versions could be embeded in actix programs, but I'm not sure about this one. Also, we don't have publishing to crates, which might add some complexity.