We deployed a couple prodigy recipes and have had them running for a while. I admit to not checking Chrome (as I use Safari on my mac). And today Chrome fails to load the majority of the recipe (the standard prodigy guts exist, but the custom recipe does not) and we get this error message: http://prodigy.XXX.XXX:YYYY/userinfo 404 (Not Found)
I upgraded to the latest prodigy hoping to solve the problem, but it did not. Chrome is the also the latest version.
Note: I do see the same error message in Safari, but the recipe still loads and works.
404 from the userinfo enpoint usually means that the basic HTTP authentication failed. Could it be that you have PRODIGY_ALLOWED_SESSIONS, or PRODIGY_BASIC_AUTH_USER set in the environment and the session you're you are accessing with is not one of the expected named sessions?
This of course doesn't explain why the behavior would be different for Chrome and Safari (I get the same behavior in both for this condition). It's not obvious to me why Safari would load the recipe despite 404 - can you observe any differences in the browsers' console?
@lauvil are you reproducing this situation (works on Safari but not on Chrome) locally on your mac or is it only in the another deployment context?
Could you start Prodigy server with PRODIGY_LOGGING=basic access it with the named session using Chrome and share the console output, please.
Also, it would be great if you could share any errors that show up in the Chrome's console (right click on the Prodigy window > Inspect > Console tab)
(I need to ask because I'm not reproducing this problem with the latest Chrome)
Thanks!
The userinfo endpoint 404 should not be problem here actually, we need to figure out what happens when the app tries to access /project/{name} endpoint.
I decided to just try a recipe from prodigy and I see the same message in the browser console and logging. So maybe this has always been there for how we are running. Note: We found out that one of the images was labeled a png but was really a tiff, but safari will load tiff but chrome and other microsoft browsers will not. So a different issue. However, as I mentioned I am still seeing failure to load the userinfo, so am I missing a step? Below are the commands I ran and the relevant output from the logging.
I added env vars for session "export PRODIGY_ALLOWED_SESSIONS=victor,joe,loretta,nora"
I started prodigy with "prodigy ner.manual ner_test en_core_web_lg ./demo_out.jsonl --label PERSON,ORG,PRODUCT"
Here is the relevant log messages...
INFO: Started server process [345962]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://192.17.98.136:8080 (Press CTRL+C to quit)
INFO: xxx:54056 - "GET /?session=loretta HTTP/1.1" 200 OK
INFO: xxx:54055 - "GET /bundle.js HTTP/1.1" 200 OK
INFO: xxx:54056 - "GET /userinfo HTTP/1.1" 404 Not Found
INFO: xxx:54055 - "GET /project/loretta HTTP/1.1" 200 OK
INFO: xxx:54059 - "GET /favicon.ico HTTP/1.1" 200 OK
INFO: xxx:54056 - "GET /fonts/lato-bold.woff2 HTTP/1.1" 200 OK
INFO: xxx:54060 - "GET /fonts/lato-regular.woff2 HTTP/1.1" 200 OK
INFO: xxx:54055 - "GET /fonts/robotocondensed-bold.woff2 HTTP/1.1" 200 OK
The 404 on /userinfo endpoint should not be offending in any way here. It's only relevant for the Prodigy Company Plugin. This request should not be done in the context outside the Company Plugin so that's something for us to look at, but you might as well ignore it for now.
Does you're workflow work as expected otherwise (and after eliminating the tiff image issue)?