1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
/*
*
* Copyright (c) 2026 Project CHIP Authors
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
//! The Diagnostic Logs cluster *client* side (the controller fetching logs).
//!
//! The client sends `RetrieveLogsRequest` via the generated `DiagnosticLogsClient`
//! proxy on an [`Exchange`](crate::transport::exchange::Exchange); when the server
//! answers a `BDX` request by pushing the log over BDX, the client receives it
//! with [`DiagLogsBdxHandler`] - a [`BdxHandler`] it chains into its responder,
//! the mirror of the server-side
//! [`OtaBdxHandler`](crate::dm::clusters::ota_prov::OtaBdxHandler).
use crate;
use crateError;
use MAX_FILE_DESIGNATOR;
/// A destination for diagnostic logs received over BDX - the *client* side.
///
/// Implemented by an application that collects logs from devices (e.g. a small
/// management controller that fetches logs and forwards them to a cloud). The
/// [`DiagLogsBdxHandler`] calls [`receive`](Self::receive) once per incoming BDX
/// log transfer; pull the bytes from `reader` yourself and store them however you
/// like - there is no per-chunk callback.
/// The client side of Diagnostic Logs over BDX: a [`BdxHandler`] that accepts a
/// log a device *pushes* over BDX and hands it to a [`DiagLogsReceiver`].
///
/// This mirrors [`OtaBdxHandler`](crate::dm::clusters::ota_prov::OtaBdxHandler) on
/// the server side. Wrap it in a [`Bdx`](crate::bdx::Bdx) handler and chain that
/// into your responder: after you send a `RetrieveLogsRequest` with
/// `RequestedProtocol = BDX` (via the generated `DiagnosticLogsClient` proxy on an
/// [`Exchange`](crate::transport::exchange::Exchange)), the device opens a BDX
/// transfer back to you, and the responder routes it here - concurrently with the
/// still-in-flight request, so no explicit `accept`/`select` is needed.