Renamed GitHub repo did not generate new Hub entry
dbeatty10 opened this issue · 2 comments
Overview
As mentioned here, https://github.com/tuva-health/core was renamed to https://github.com/tuva-health/core.
When the script ran on Heroku, it successfully cloned the repo:
2022-11-17 15:03:57 INFO Drawing down tuva-health's the_tuva_project
2022-11-17 15:03:57 INFO cloning https://github.com/tuva-health/the_tuva_project.git to /app/target/tuva-health_the_tuva_project
2022-11-17 15:03:59 INFO pulling main at /app/target/tuva-health_the_tuva_project
But it did not collect tags and write index.json when appropriate (like it successfully did for terminology and data_profiling:
...
2022-11-17 15:04:48 INFO no new tags for terminology. Skipping...
2022-11-17 15:04:48 INFO collecting tags for data_profiling
2022-11-17 15:04:48 INFO pkg hub tags: []
2022-11-17 15:04:48 INFO pkg remote tags: ['0.1.0']
2022-11-17 15:04:48 INFO creating task to add new tags ['0.1.0'] to data_profiling
...
2022-11-17 15:04:50 INFO writing index.json to /app/target/hub.getdbt.com/data/packages/tuva-health/data_profiling/index.json
2022-11-17 15:04:50 INFO
2022-11-17 15:04:50 INFO downloading: https://codeload.github.com/tuva-health/data_profiling/tar.gz/0.1.0
2022-11-17 15:04:50 INFO SHA1: e3c25af1078d845d3ba1065249eb76676120888b
2022-11-17 15:04:50 INFO writing spec to /app/target/hub.getdbt.com/data/packages/tuva-health/data_profiling/versions/0.1.0.json
2022-11-17 15:04:50 INFO hubcap: Adding tag 0.1.0 for tuva-health/data_profiling
Next steps
Try to reproduce and troubleshoot this locally (rather than via Heroku).
Fall-back if all else fails
Manually create a pull request within https://github.com/dbt-labs/hub.getdbt.com that adds the appropriate files.
cc @tuvaforrest for visibility
During my first attempt, I was not able to reproduce the issue locally. (Side note: this means I could just do production run locally in order to generate the relevant PR for hub.getdbt.com. But I'd prefer to discover and fix the root cause on the Heroku side of things.)
Looking more closely at the Heroku logs, it looks like the name is still core within Heroku -- see where it says collecting tags for core instead of the expected collecting tags for the_tuva_project:
2022-11-17 17:04:33 INFO collecting tags for data_profiling
2022-11-17 17:04:33 INFO pkg hub tags: ['0.1.0']
2022-11-17 17:04:33 INFO pkg remote tags: ['0.1.0']
2022-11-17 17:04:33 INFO no new tags for data_profiling. Skipping...
2022-11-17 17:04:33 INFO collecting tags for core
2022-11-17 17:04:33 INFO pkg hub tags: ['0.1.0', '0.1.1', '0.1.2', '0.1.3', '0.1.4', '0.1.5', '0.1.6', '0.1.7', '0.1.8', '0.1.9']
2022-11-17 17:04:33 INFO pkg remote tags: ['0.1.0', '0.1.1', '0.1.2', '0.1.3', '0.1.4', '0.1.5', '0.1.6', '0.1.7', '0.1.8', '0.1.9']
2022-11-17 17:04:33 INFO no new tags for core. Skipping...
2022-11-17 17:04:33 INFO collecting tags for readmissions
2022-11-17 17:04:33 INFO pkg hub tags: ['0.1.0', '0.1.1', '0.1.2']
2022-11-17 17:04:34 INFO pkg remote tags: ['0.1.0', '0.1.1', '0.1.2']
2022-11-17 17:04:34 INFO no new tags for readmissions. Skipping...
