Closed CristopherH95 closed 2 years ago
From running local tests, it appears as though the build error occurs only with Django 1.11
. It looks like the error is occurring while setting up the test database, which the code changed here should have nothing to do with. I wonder if perhaps the latest version of mysqlclient
is not compatible with Django 1.11
? The last successful build used mysqlclient
version 2.0.3
, whereas 2.1.0
is now used when the build is run.
Edit: it appears as though mysqlclient
version 2.1.0
causes the build error, as when I manually downgrade back to 2.0.3
the tests run no problem. Whereas if I upgrade to 2.1.0
I see the same error as in the CI build, since that is the version installed automatically. This makes me wonder, does Django 1.11
still need to be supported by Watson?
I'm happy to drop Django 1.x from the test matrix. Go ahead and do that in this MR! Otherwise, this is a nice elegant fix, and good to merge once we fix the tests.
Apologies for the slow update, the most recent commit should remove 1.x from the test matrix!
Merged! I'll cut a release.
As was highlighted by #292, lack of proper handling for primary key field types which derive from
RelatedField
inget_pk_output_field
causes errors when runningbuildwatson
. This change adds a simple check to theget_pk_output_field
function which will retrieve the field type from the related model instead, to avoid errors.fixes #292