Skip to content

Internal numbering of the sessions in the CLI tool report is sometimes incorrect #4

@kobitzruya-omniguardai

Description

@kobitzruya-omniguardai

Please see the following. the report skipped session # 8. We see session #7 and right after it session # 9

Session 7: environment_prod_2eed303c.json

Overall Decision: 🟡 WARNING

Scanner Results:

  • FactsChecker: 🟡 WARNING
    • Total: 6 | Safe: 3 | Warnings: 3 | Blocks: 0
    • Reason: NeMo GuardRails WARNING: RAG Ungroundedness

Session 9: environment_prod_411bb1aa.json

Overall Decision: 🟡 WARNING

Scanner Results:

  • FactsChecker: 🟡 WARNING
    • Total: 5 | Safe: 2 | Warnings: 3 | Blocks: 0
    • Reason: NeMo GuardRails WARNING: RAG Ungroundedness

Also skip from session 13 to 16:

Session 13: environment_prod_53e9d2a7.json

Overall Decision: 🟡 WARNING

Scanner Results:

  • FactsChecker: 🟡 WARNING
    • Total: 5 | Safe: 4 | Warnings: 1 | Blocks: 0
    • Reason: NeMo GuardRails WARNING: RAG Ungroundedness

Session 16: environment_prod_61184717.json

Overall Decision: 🔴 BLOCK

Scanner Results:

  • FactsChecker: 🔴 BLOCK
    • Total: 1 | Safe: 0 | Warnings: 1 | Blocks: 1
    • Reason: NeMo GuardRails BLOCKED: Self-Contradiction detected (also found warnings: RAG Ungroundedness)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions