-
Notifications
You must be signed in to change notification settings - Fork 31
Bug: many committees cycle selections not working #875
Comments
Looks like we caused this in #1202. We're getting the list of active two-year periods from We probably don't want to roll back #1202, since that would reintroduce problems with ECs and CCs. We could use a full outer join to join What do you think @LindsayYoung? This may be another item to add to discussions on Friday. |
I think that full outer join with showing committee pages with mostly null values might be the best we can do. Especially if we ever add back ballot candidates, they won't have any summary data or even filings. |
Due to a mismatch in active cycles between `dimcmteproperties` and `vw_filing_history`, some committee reports and totals return 404s on attempting to resolve the committee type when a cycle is specified. This patch temporarily falls back to resolving committee type from the detail table when no matching results can be found for the specified cycle. Note: this should be reverted after the underlying issue described in fecgov/openFEC-web-app#875 is resolved.
When committee history information can't be found from the history sub-endpoint, use the detail endpoint instead. This is a temporary fix and should be reverted once the underlying issue described in fecgov#875 is resolved. Depends on https://github.com/18F/openFEC/pull/1295.
@LindsayYoung and I put in a temporary fix for this to avoid problems during launch. Let's continue discussion of a better solution in https://github.com/18F/openFEC/issues/1287. |
Just noticed
Not working:
https://fec-proxy.18f.gov/data/committee/C00507384/?cycle=2010
https://beta.fec.gov/data/committee/C00507384/?cycle=2010
Working:
https://fec-proxy.18f.gov/data/committee/C00507384/
https://beta.fec.gov/data/committee/C00508002/
More examples that work the same on dev and production:
https://beta.fec.gov/data/committee/C00443176/?cycle=2006
https://beta.fec.gov/data/committee/C00508002/?cycle=2010
The text was updated successfully, but these errors were encountered: