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

Big NodeJS-Reports #175

Open
Reamer opened this issue Sep 25, 2019 · 0 comments
Open

Big NodeJS-Reports #175

Reamer opened this issue Sep 25, 2019 · 0 comments
Labels
bug reproduced bug Bugs that could be reproduced by the maintainer

Comments

@Reamer
Copy link
Member

Reamer commented Sep 25, 2019

Describe the bug
HTML-Reports get really huge (> 60MB). I faced this issue with a nodejs report and mysql. MySQL isn't supported by sonarqube. Maybe a change to postgres solved this issue.

To Reproduce

  1. Create a nodejs report

Current behavior
Database is bloated with reports.

Expected behavior
We doesn't want to change the original report, maybe it's possible to compress the report and serve as a download.
@Reamer Reamer added the bug label Sep 25, 2019
@Reamer Reamer mentioned this issue Feb 18, 2020
Closed
@Reamer Reamer mentioned this issue Oct 21, 2020
Closed
@Reamer Reamer added the reproduced bug Bugs that could be reproduced by the maintainer label Jan 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug reproduced bug Bugs that could be reproduced by the maintainer
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Reamer