Rafael Mendes Pacini Bachiega

> Can you make sure that it is related to pytest-django only ... ? When I run manage.py test using Django's default test runner all tests passed.

After multiple atempts I found that the problem is with pluggy requirement. ``` .pluggy >=0.12 (requirement for pytest >=4) .pytest >=4 .pytest-django==3.8.0 ``` **this error occurs.** ``` pluggy==0.11 pytest>=3.6,=3.6,

> You mean pytest, right? No. If I keep pytest version

Yeah, I imagined... Thankfully we have Docker and pyenv to be able to install any python version we want :) That's how I managed this. > The good news is...

@evilhamsterman Thanks for the insight on how tailscale deals with SSH internally. Now it makes sense why it doesn't and won't work. `tailscacle up` won't work here because I'm trying...

All my tables have UUIDs as primary keys, and I am experiencing the same issue. Names are not shown, despite they are getting returned from the /values call. If I...

Having the same issue here, the redirect url is hardcoded. I set AFFINE_SERVER_HOST btw

I got the same problem, thanks for the tip @nbelzer, In my case, I'm using minitest and also Rails Event Store library, so I have a bunch of background jobs...

Any news here?

I gave up on the tool