The first data frame comes back from the backend. The second is from the client test setup. It looks like the client is expecting row ID starting at 0, and row version starting at 0. However, the backend returns both starting at 1. This test doesn’t update the table after creation, so the data must not be out of date.
On prod, I created a table and add a new row (using SWC), then downloaded the data:
Adding , and here.
Besides the Python client integration tests, I don’t think anyone is looking at RowID and RowVersion, so it’s a low risk. I’m making notes about this in case someone runs into this problem next week.
Also, the synapser client integration tests passed because it doesn’t check for content coming back.
, you can use the develop branch to build against new stack for pre-release check. There is no new API changes to the develop branch.
, I have pushed this fixed to pypi under version 1.9.3. The source code on master branch is also updated. Your build from master branch should no longer fail at this test. The next time you run the build, can you validate this ticket? Thank you.
Verified fixed on dev branch against dev-269.