Error in Python test (submission annotations)


Heads up: Was running python tests against a dev stack (more precisely against cwtest stack, to generate activity), based on 316 and got the error below.

Note: I run these tests weekly against dev stack to verify there's no change on the backend that would break the client. This is like a pre-test (haven't updated dev stack yet).


python 3.6, synapseclient from main branch, backend 316.


Xavier Schildwachter
July 10, 2020, 8:23 PM

Verified fixed from develop branch.

Jordan Kiang
July 9, 2020, 6:50 PM

can you validate that the issue is resolved for you (this issue manifested in the python client integration tests which now succeed as in

Jordan Kiang
June 24, 2020, 11:04 PM

Fixed with

% nosetests tests.integration.synapseclient.test_evaluations:test_evaluations
Ran 1 test in 18.666s


Bruce Hoff
June 22, 2020, 10:55 PM

: You describe the issue perfectly. I am pretty certain I introduced the change last week while removing some deprecated code:

I'm also fairly sure that clients rarely (if ever) use the annotations placed on an entity when evaluating a challenge submission. I asked Tom Yu, who does most of our work on challenges in this area and he says, "No. We do not instruct people to annotate the original file entity". So I think it's fine to proceed with your pull request and patch the released version of the Python client. I'm not worried about "breaking" any current challenges.

Thanks for diligently checking, !

Xavier Schildwachter
June 22, 2020, 10:43 PM

@bruce, I typically run the test against the dev stack we build every week. This one just happens to run against a separate stack I created (cwtest, build off release-316) to test the CloudwatchLogs. I mentioned it so you guys don't try to repro against the dev stack (still off release-315) before I ugrade it. Sorry I was not was very clear!



Jordan Kiang


Xavier Schildwachter




Xavier Schildwachter

Development Area


Release Version History


Slack Channel


Fix versions

Affects versions