-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ServiceX fails to report science image missing under certain circumstances #540
Comments
I suspect this is a good first issue. |
Hi, I started exploring ServiceX only few days back and so far, I am able to deploy it locally and am trying to run a transformation on a ROOT file. This issue indeed looks like a good one for beginners but can you please give more info on how to reproduce it? Also, is there a document describing all the REST APIs? If so, I can test the fix by directly invoking the API (using "curl" for example). I looked at
As can be seen, there is already a check for 404 error. In this particular case, I suspect that the return status is something else (may even be 500) and the response contains non-JSON (most probably some HTML error message). So Finally, I see the file |
@gordonwatts is this issue still relevant? |
I have no idea - I've not tried to do a request with a different docker image recently to repro this error. @BenGalewsky - is this even possible with the new way of specifying code generators (since this is a transformer image)? |
Describe the bug
This crash when running:
Can with some deeper debugging be tracked to:
If you look at that bug you'll see it is in the middle of the check of the docker science image existence up on the hub.
To Reproduce
Steps to reproduce the behavior:
sslhep/sslhep/servicex_func_adl_xaod_transformer:v1.1.4
Expected behavior
A clear message declaring the image could not be found. The error should include the image that it was trying to look up so the user can try to track this back to something they did (or how SX was misconfigured).
The text was updated successfully, but these errors were encountered: