From 7d9a019a360c979d05db38bf68b1a35b416f5f7b Mon Sep 17 00:00:00 2001 From: Bryan Leong Date: Mon, 15 Dec 2025 17:07:57 +0800 Subject: [PATCH 1/2] docs: edits to deduplication-tuning docs - added missing backticks - fixed image path to point to correct asset --- .../finding_deduplication/deduplication_tuning_os.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/content/en/working_with_findings/finding_deduplication/deduplication_tuning_os.md b/docs/content/en/working_with_findings/finding_deduplication/deduplication_tuning_os.md index 2acf22e0e08..bc448ed826f 100644 --- a/docs/content/en/working_with_findings/finding_deduplication/deduplication_tuning_os.md +++ b/docs/content/en/working_with_findings/finding_deduplication/deduplication_tuning_os.md @@ -112,7 +112,7 @@ docker compose exec uwsgi /bin/bash -c "python manage.py dedupe --hash_code_only ``` Help/usage: - +```bash options: --parser PARSER List of parsers for which hash_code needs recomputing (defaults to all parsers) @@ -135,9 +135,9 @@ To help troubleshooting deduplication use the following tools: - Observe log out in the `dojo.specific-loggers.deduplication` category. This is a class independant logger that outputs details about the deduplication process and settings when processing findings. - Observe the `unique_id_from_tool` and `hash_code` values by hovering over the `ID` field or `Status` column: -![Unique ID from Tool and Hash Code on the View Finding page](images/hash_code_id_field.png) + ![Unique ID from Tool and Hash Code on the View Finding page](/docs/assets/images//hash_code_id_field.png) -![Unique ID from Tool and Hash Code on the Finding List Status Column](images/hash_code_status_column.png) + ![Unique ID from Tool and Hash Code on the Finding List Status Column](/docs/assets/images/hash_code_status_column.png) ## Related documentation From 4e6000391d74cea412fe7870a8f82e01c80de9e4 Mon Sep 17 00:00:00 2001 From: "bryan.leong.e" Date: Thu, 18 Dec 2025 10:59:08 +0800 Subject: [PATCH 2/2] chore: reset image path reference to follow convention --- .../finding_deduplication/deduplication_tuning_os.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/content/en/working_with_findings/finding_deduplication/deduplication_tuning_os.md b/docs/content/en/working_with_findings/finding_deduplication/deduplication_tuning_os.md index bc448ed826f..3e3e4eae684 100644 --- a/docs/content/en/working_with_findings/finding_deduplication/deduplication_tuning_os.md +++ b/docs/content/en/working_with_findings/finding_deduplication/deduplication_tuning_os.md @@ -135,13 +135,12 @@ To help troubleshooting deduplication use the following tools: - Observe log out in the `dojo.specific-loggers.deduplication` category. This is a class independant logger that outputs details about the deduplication process and settings when processing findings. - Observe the `unique_id_from_tool` and `hash_code` values by hovering over the `ID` field or `Status` column: - ![Unique ID from Tool and Hash Code on the View Finding page](/docs/assets/images//hash_code_id_field.png) + ![Unique ID from Tool and Hash Code on the View Finding page](images/hash_code_id_field.png) - ![Unique ID from Tool and Hash Code on the Finding List Status Column](/docs/assets/images/hash_code_status_column.png) + ![Unique ID from Tool and Hash Code on the Finding List Status Column](images/hash_code_status_column.png) ## Related documentation - [Deduplication Algorithms](deduplication_algorithms): conceptual overview and endpoint behavior. - [Avoiding duplicates via reimport](avoiding_duplicates_via_reimport). -