Skip to content
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

cached event agenda is out of sync with legistar #443

Closed
hancush opened this issue May 17, 2019 · 1 comment
Closed

cached event agenda is out of sync with legistar #443

hancush opened this issue May 17, 2019 · 1 comment

Comments

@hancush
Copy link
Collaborator

hancush commented May 17, 2019

on 5/15, an event agenda document was updated to reflect a withdrawn item, however the cached document was not updated and an out of date version was displayed in the web ui.

i did the following to resolve the issue manually:

  • visit the event in question in the councilmatic ui and retrieve the ocd id from the console.
  • using the ocd id from the console, visit the event in the ocd api and retrieve the agenda document url.
  • in a python interpreter, generate the s3 key: import urllib; document_url = 'DOCUMENT_URL'; print(urllib.parse.quote_plus(document_url)) (here's the code that generates it in the pic app.)
  • in the aws console, go to the s3 dashboard, then the councilmatic-document-cache bucket.
  • search for the key you generated in your console, and click its filename.
  • to the right of the "overview", "properties"... tabs, there's a latest version dropdown. click it, then click the trashcan to delete the cached image.
  • visit the event in question in the councilmatic ui again, and confirm that document has been updated. you may see a red "invalid response" banner in the pdf viewer in some browsers. this is documented in PDF viewer: Browser compability #378. refresh again and confirm that the document has been updated.

it looks like the refresh_pic command tries to update cached documents for changed events, however the withdrawal of a matter on the event agenda did not register as a change to the event. so, we'll need to debug that and update the management command to reflect what we learn.

related to #347 and #407.

@hancush
Copy link
Collaborator Author

hancush commented Sep 1, 2020

This management command has been totally refactored. This issue is superseded by #621.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant