Achieve3318 16354f4e14 fix(dify): guard retrieval argument error behavior (#14169) ...

## What problem does this PR solve?

The Dify-compatible `/dify/retrieval` endpoint recently gained stricter
parsing and validation for its request payload, including:
- Normalized `retrieval_setting.top_k` and
`retrieval_setting.score_threshold` types.
- Clear separation between malformed arguments vs missing required
fields.
Previously, there was no unit test explicitly guarding the exact error
code and message contract for these cases.

## What does this PR change?

- **Add guard-style unit test** in `test_dify_retrieval_routes_unit.py`:
  - `test_retrieval_argument_error_messages`:
    - Sends a request with malformed numeric options:
- `retrieval_setting = {"top_k": "not-int", "score_threshold":
"not-float"}`
      - Asserts `code == RetCode.ARGUMENT_ERROR` and message contains  
        `"invalid or malformed arguments:"`.
    - Sends a request with required fields missing:
      - Empty payload (`{}`)
      - Asserts `code == RetCode.ARGUMENT_ERROR` and message contains  
        `"required arguments are missing:"`.

This test encodes the intended behavior of the Dify retrieval API so
future refactors cannot silently regress error handling.

## Type of change

- [x] Tests (add coverage and guardrails for existing behavior)

Co-authored-by: Kevin Hu <kevinhu.sh@gmail.com>

2026-05-11 13:17:42 +08:00

..

dify_retrieval.py

fix(dify): guard retrieval argument error behavior (#14169)

2026-05-11 13:17:42 +08:00

doc.py

fix: authorize beta document downloads by tenant (#14496)

2026-05-06 14:55:41 +08:00

session.py

fix: enforce tenant-scoped authorization for chatbot SDK endpoints (#14592)

2026-05-08 18:00:18 +08:00