You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have encountered an issue with generating bulk reports for "whole folder" or "marked uploads" in the Browsing tab, specifically for CLIXML and Cyclone DX reports.
Steps to reproduce:
1. Create and run a Docker container with the latest version of the Fossology image. docker run -id -p 8885:80 fossology/fossology:latest http://localhost:8885/repo/
2. Login to Fossology and Navigate to the Browsing tab.
3. Select different uploads from the folder.
4. Click on "marked uploads."
5. Attempt to generate either a CLIXML or Cyclone DX report.
Observation:
For CLIXML reports, the generated file is incorrectly named after the first upload instead of being labeled as "Multi File <Report_Name>" Additionally, the XML file contains the first upload's name repeated times, though the contents seem to reference the other uploads (e.g., SHA1 hashes).
At times, generating the report results in the following error:
This page contains the following errors:
error on line at column 1: Extra content at the end of the document
Below is a rendering of the page up to the first error.
Any hints or suggestions that might help resolve this issue?
The text was updated successfully, but these errors were encountered:
We have encountered an issue with generating bulk reports for "whole folder" or "marked uploads" in the Browsing tab, specifically for CLIXML and Cyclone DX reports.
Steps to reproduce:
docker run -id -p 8885:80 fossology/fossology:latest
http://localhost:8885/repo/
Observation:
For CLIXML reports, the generated file is incorrectly named after the first upload instead of being labeled as "Multi File <Report_Name>" Additionally, the XML file contains the first upload's name repeated times, though the contents seem to reference the other uploads (e.g., SHA1 hashes).
At times, generating the report results in the following error:
Any hints or suggestions that might help resolve this issue?
The text was updated successfully, but these errors were encountered: