Merci

@roggervalf @manast Hi! I think it's a victory. Now all tests will pass successfully. Mostly bugs with decoding binary strings and architecture. Data from job can be received and processed...

Well, the last test was not executed due to the fact that I confused ats with atm and attemptsMade was assigned to ats, not atm, but now everything is normal...

Damn, forgot the type casting. I fixed it, well, this time it’s all right

More precisely, I’m talking about the same decoding of a byte string. In the case of job_id, it could be done both through int() and decode(), however, if the second...

I've added a new test. It's very simple. The point is to receive the job data in the worker function and do something with it; in my case, simply return...

```python async def test_getting_job_data_in_process(self) -> None: queue = Queue(queueName) data = {"foo": "bar"} job = await queue.add( "test-job", data, {"removeOnComplete": False} ) async def process(job: Job, token: str) -> str:...

It is quite possible that on different redis configurations or under your specific conditions, the strings will not be byte strings, but in other cases they will be. The point...

> hi @YeaMerci I search for this kind of error and https://redis-py.readthedocs.io/en/latest/examples/connection_examples.html#By-default-Redis-return-binary-responses,-to-decode -them-use-decode_responses=True could you try to add this option into your connection config. It could be that in your...

@roggervalf @manast It’s just that the modification itself does not break anything; a repository with it can now simply avoid such an error without the need for investigation. In addition,...

At least such a case should be described in the documentation, because it’s a complete ass to dig into the source code and try to fix a bug that is...