"Yield Task" not yielding some tasks

[ines (Ines Montani)]

@ameliatqy

But I am not sure about the case in which the Prodigy instance is already running and the ignored annotations are generated during the session - I’ll let you know when I test that scenario out.

Yes, that'd definitely be interesting! Also, if the existing answer is the cause here, one quick fix should be to overwriteit /remove it from the task dict before sending it out? And if not, that'd also be interesting, since it means something else would be going on, if I understand this correctly?

@ameliatqy

I am still using the old version of Prodigy for this (Prodigy 1.6 - Prodigy 1.7 returns JWT: caller token did not validate when I try to start it up.

Btw, I think we have a fix for that – see here:

Super basic authentication

@koAlech Hurray for authenticating users, and welcome! We’ve begun integrating more full-featured authentication for Prodigy Scale, and the snippet you used conflicts with that code. A workaround is to remove the occurrences of the string , requires=conditional_api_token from app.py. This will remove your ability to use the PRODIGY_JWT_* environment variables, but if you want to use basic auth, that should be no problem. edit: there’s a better fix below