Fundamental_Analysis/services/data-persistence-service/.sqlx/query-a01fb0ba486147652fb7ad4e555c5205a2adc87ba01c405a73c71e5bd15ca8b6.json
Lv, Qi 0cb31e363e Refactor E2E tests and improve error handling in Orchestrator
- Fix `simple_test_analysis` template in E2E test setup to align with Orchestrator's data fetch logic.
- Implement and verify additional E2E scenarios:
    - Scenario C: Partial Provider Failure (verified error propagation fix in Orchestrator).
    - Scenario D: Invalid Symbol input.
    - Scenario E: Analysis Module failure.
- Update `WorkflowStateMachine::handle_report_failed` to correctly scope error broadcasting to the specific task instead of failing effectively silently or broadly.
- Update testing strategy documentation to reflect completed Phase 4 testing.
- Skip Scenario B (Orchestrator Restart) as persistence is not yet implemented (decision made to defer persistence).
2025-11-21 20:44:32 +08:00

42 lines
956 B
JSON

{
"db_name": "PostgreSQL",
"query": "\n SELECT \n cache_key, \n data_payload, \n updated_at, \n expires_at\n FROM provider_response_cache\n WHERE cache_key = $1 AND expires_at > $2\n ",
"describe": {
"columns": [
{
"ordinal": 0,
"name": "cache_key",
"type_info": "Varchar"
},
{
"ordinal": 1,
"name": "data_payload",
"type_info": "Jsonb"
},
{
"ordinal": 2,
"name": "updated_at",
"type_info": "Timestamptz"
},
{
"ordinal": 3,
"name": "expires_at",
"type_info": "Timestamptz"
}
],
"parameters": {
"Left": [
"Text",
"Timestamptz"
]
},
"nullable": [
false,
false,
false,
false
]
},
"hash": "a01fb0ba486147652fb7ad4e555c5205a2adc87ba01c405a73c71e5bd15ca8b6"
}