-
Notifications
You must be signed in to change notification settings - Fork 98
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
CSW harvesting fails for all records #3376
Comments
First step is to roll back to working version of code, we believe this broke on this PR. |
On FCS, the spatial code does not seem to work. I believe it is due to needed later versions of OWSLib, but those are not working well on Python2. I can't find much documentation on the support of OWSLib.
I believe this is deep in OWSLib, and debugging is painful. My suggestion is to pin spatial in FCS to not get the latest, and only use the latest for Py3 and CKAN2.9. |
I agree with James. I think the main concern was that we weren't sure if harvesting was working for PY3 and it was verified that it does. Tracking two different versions for FCS and cloud.gov is the right approach from my perspective too. I think it's just important to make sure that all of the relevant components were upgraded and they are.. ckanext-spatial,
ckanext-harvest,
ckanext-geodatagov,
ckanext-harvest does have upstream edits and we have two PY3 upgrades that we needed to do, this will get messy if it continues,
|
On Catalog, CSW harvest stopped working. The harvesting generated an error for each record:
How to reproduce
https://catalog.data.gov/harvest/opentopography-csw/job/55b8e5dd-7700-4aa1-9956-2338168c2c2c
Expected behavior
Successful harvest report
Actual behavior
Error for all records
Context
Harvest source side there is no changes. It should be related to recent requirements update we did a few weeks ago.
Sketch
The text was updated successfully, but these errors were encountered: