Open kueda opened 9 months ago
I think this was fixed in 41fcf0bb8189a3daccab12c17757da44222db346. I was able to replicate the problem using the image and user and taxon - it was related to the place associated with the user and the common ancestor taxon. If it occurs again, it would be great to get another test image note which user is experiencing the problem
Seems to still be happening:
Auth as kueda-test, using this request:
curl -XPOST \
-H "Authorization: kueda-test-jwt" \
-F "image=@/Users/kueda/Downloads/lupine.jpg" \
-F "lat=37" \
-F "lng=-122" \
--form-string 'fields=(combined_score:!t,taxon:(ancestor_ids:!t,default_photo:(id:!t,url:!t),name:!t,preferred_common_name:!t,rank:!t,rank_level:!t))' \
"https://stagingapi.inaturalist.org/v2/computervision/score_image"
I can stell replicate using an auth token for the kueda-test user and this image:
curl -XPOST \
-H "Authorization: kueda-test-jwt" \
-F "image=@/Users/kueda/Downloads/zamioculcas.JPG" \
-F "lat=37" \
-F "lng=-122" \
--form-string 'fields=(combined_score:!t,taxon:(ancestor_ids:!t,default_photo:(id:!t,url:!t),name:!t,preferred_common_name:!t,rank:!t,rank_level:!t))' \
"https://stagingapi.inaturalist.org/v2/computervision/score_image"
When I do this using a JWT for https://staging.inaturalist.org/people/kueda:
with this image:
I get this response:
Weirdly, I do the same with a JWT for https://staging.inaturalist.org/people/kueda-test, I do not get an error. I've tried fiddling with the place settings for the kueda user on staging but it doesn't seem to make a difference.