Closed Nebrethar closed 5 years ago
Confirmed on a fresh checkout of dev
@gabe-heim : This is related it appears to our removal of the cms_id
column as you were doing insights work? Can we fix the API quick?
LINE 3: ri_date AS date, cms_id AS rating, ri_fresh ...
[SQL:
SELECT rg_name, repo.repo_group_id, repo_insights.repo_id, repo_git, ri_metric, ri_value AS value,
ri_date AS date, cms_id AS rating, ri_fresh AS discovered
FROM repo_insights JOIN repo ON repo.repo_id = repo_insights.repo_id JOIN repo_groups ON repo.repo_group_id = repo_groups.repo_group_id
WHERE repo_insights.repo_id IN (
SELECT repo_id
FROM repo
WHERE repo_group_id = %(repo_group_id)s
AND repo_id IN (SELECT repo_id FROM repo_insights WHERE data_collection_date > CURRENT_DATE - INTERVAL '10' DAY GROUP BY repo_id, ri_id HAVING 304 > count(repo_insights.repo_id) ORDER BY ri_id desc)
LIMIT %(num_repos)s
)
]
@sgoggins there is an api change that is needed as well as some frontend logic that references that column, I am fixing it now
Fixed in 2e8e05f.
Describe the bug:
Calling these front page endpoint URLs results in 500 errors. I have included my trace at the bottom of this post. It seems to be related to the variable
cms_id
which does not seem to exist in this context.To Reproduce: Steps to reproduce the behavior:
Expected behavior: I did not know what to expect, but it wasn't that.
Screenshots
Desktop (please complete the following information):
Additional context