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.

Sign up for GitHub

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

Jump to bottom

Fix /report/openness #3964

Closed
1 task
nickumia-reisys opened this issue Sep 20, 2022 · 5 comments
Closed
1 task

Fix /report/openness #3964

nickumia-reisys opened this issue Sep 20, 2022 · 5 comments
Assignees
@nickumia-reisys
Labels
bug Software defect or bug CKAN component/catalog Related to catalog component playbooks/roles Testing

Comments

@nickumia-reisys
Copy link
Contributor

nickumia-reisys commented Sep 20, 2022 •
edited
Loading

User Story

In order to generate openness reports, the Data.gov Analytics team wants to fix the broken feature of generating the openness report.

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

  • GIVEN the fix has been implemented
    WHEN I visit /report/openness
    THEN the page loads.

Background

[Any helpful contextual notes or links to artifacts/evidence, if needed]

image

Security Considerations (required)

[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

Sketch

[Notes or a checklist reflecting our understanding of the selected approach]
@nickumia-reisys nickumia-reisys mentioned this issue Sep 20, 2022
Closed
7 tasks
@nickumia-reisys nickumia-reisys self-assigned this Sep 20, 2022
@nickumia-reisys nickumia-reisys moved this to In Progress [8] in data.gov team board Sep 20, 2022
@nickumia-reisys nickumia-reisys moved this from In Progress [8] to Product Backlog in data.gov team board Sep 27, 2022
@hkdctol hkdctol moved this from Product Backlog to Sprint Backlog [7] in data.gov team board Sep 29, 2022
@nickumia-reisys nickumia-reisys moved this from Sprint Backlog [7] to In Progress [8] in data.gov team board Sep 30, 2022
@nickumia-reisys
Copy link
Contributor Author

On a clean instance with no data, the page loads....

image

@nickumia-reisys
Copy link
Contributor Author

The error appears after data is added and the page is reloaded.

@nickumia-reisys nickumia-reisys mentioned this issue Sep 30, 2022
Closed
@nickumia-reisys
Copy link
Contributor Author

It seems like the following upstream PR will fix this.

🧪 Testing now...

This was referenced Sep 30, 2022
Merged
Open
@nickumia-reisys
Copy link
Contributor Author

Soo.. it works again... but it needs quite a bit of RAM to be able to load (at least the first time). On Dev with 30k datasets, it took 1:11 minutes to complete, but I needed to give it 2G of RAM. Not sure how much it actually used, but it was originally set at 750M of RAM and it was crashing at 14%.

image

Either way, the original problem was fixed with the PR mentioned above and the new problem is funneling into this one again..

Repository owner moved this from In Progress [8] to Done in data.gov team board Oct 3, 2022
@nickumia-reisys
Copy link
Contributor Author

A quick screenshot of a semi-complete analysis on Dev

image

@nickumia-reisys nickumia-reisys added component/catalog Related to catalog component playbooks/roles bug Software defect or bug Testing CKAN labels Oct 9, 2023
@nickumia-reisys nickumia-reisys moved this from ✔ Done to 🗄 Closed in data.gov team board Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nickumia-reisys nickumia-reisys

Labels
bug Software defect or bug CKAN component/catalog Related to catalog component playbooks/roles Testing
Projects
data.gov team board
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nickumia-reisys