@volter/supercode-teams 0.2.20

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (79) hide show
  1. package/README.md +119 -0
  2. package/attention.mjs +191 -0
  3. package/bin/fleet.mjs +151 -0
  4. package/bin/teams.mjs +291 -0
  5. package/bin/workspace/args.mjs +66 -0
  6. package/bin/workspace/files.mjs +110 -0
  7. package/bin/workspace/lifecycle.mjs +113 -0
  8. package/bin/workspace/volter-device.mjs +42 -0
  9. package/bin/workspace/volter-login.mjs +185 -0
  10. package/bin/workspace.mjs +726 -0
  11. package/browser-attach.mjs +90 -0
  12. package/client.mjs +212 -0
  13. package/connector/effects.mjs +95 -0
  14. package/connector/index.d.ts +69 -0
  15. package/connector/index.mjs +174 -0
  16. package/connector/native-continuation.d.ts +8 -0
  17. package/connector/native-continuation.mjs +50 -0
  18. package/connector/native-effects.mjs +164 -0
  19. package/context.mjs +34 -0
  20. package/contracts/adapter-map.json +16 -0
  21. package/contracts/index.d.ts +299 -0
  22. package/contracts/index.mjs +37 -0
  23. package/execution.mjs +206 -0
  24. package/fleet.mjs +78 -0
  25. package/index.mjs +12 -0
  26. package/machine-door.mjs +36 -0
  27. package/machine.mjs +1398 -0
  28. package/package.json +80 -0
  29. package/porthole-hook.cjs +137 -0
  30. package/remote/job-exec.py +146 -0
  31. package/remote/wire.py +23 -0
  32. package/server/arc2-transactions.mjs +125 -0
  33. package/server/attachment-relay.mjs +149 -0
  34. package/server/catalog.mjs +7 -0
  35. package/server/continuations.mjs +56 -0
  36. package/server/correlation.d.ts +4 -0
  37. package/server/correlation.mjs +17 -0
  38. package/server/effects-transactions.mjs +119 -0
  39. package/server/effects.mjs +97 -0
  40. package/server/event-routes.mjs +208 -0
  41. package/server/exports.mjs +46 -0
  42. package/server/harness-routes.mjs +248 -0
  43. package/server/index.d.ts +31 -0
  44. package/server/index.mjs +52 -0
  45. package/server/ingest.mjs +24 -0
  46. package/server/node-upgrade.mjs +39 -0
  47. package/server/otlp/collector-config.d.ts +2 -0
  48. package/server/otlp/collector-config.mjs +26 -0
  49. package/server/otlp/decoders/index.d.ts +63 -0
  50. package/server/otlp/decoders/index.mjs +311 -0
  51. package/server/otlp/index.d.ts +4 -0
  52. package/server/otlp/index.mjs +4 -0
  53. package/server/otlp/projection.d.ts +5 -0
  54. package/server/otlp/projection.mjs +17 -0
  55. package/server/otlp/receiver.d.ts +3 -0
  56. package/server/otlp/receiver.mjs +36 -0
  57. package/server/otlp/schema/google/protobuf/any.proto +162 -0
  58. package/server/otlp/schema/google/rpc/status.proto +48 -0
  59. package/server/otlp/schema/manifest.json +22 -0
  60. package/server/otlp/schema/opentelemetry/proto/collector/logs/v1/logs_service.proto +77 -0
  61. package/server/otlp/schema/opentelemetry/proto/collector/metrics/v1/metrics_service.proto +77 -0
  62. package/server/otlp/schema/opentelemetry/proto/collector/trace/v1/trace_service.proto +77 -0
  63. package/server/otlp/schema/opentelemetry/proto/common/v1/common.proto +154 -0
  64. package/server/otlp/schema/opentelemetry/proto/logs/v1/logs.proto +226 -0
  65. package/server/otlp/schema/opentelemetry/proto/metrics/v1/metrics.proto +735 -0
  66. package/server/otlp/schema/opentelemetry/proto/resource/v1/resource.proto +45 -0
  67. package/server/otlp/schema/opentelemetry/proto/trace/v1/trace.proto +359 -0
  68. package/server/otlp/transport.d.ts +10 -0
  69. package/server/otlp/transport.mjs +424 -0
  70. package/server/otlp/wire-codec.mjs +153 -0
  71. package/server/store-core.mjs +139 -0
  72. package/server/store-worker.mjs +23 -0
  73. package/worker/fetch-adapter.mjs +49 -0
  74. package/worker/index.mjs +127 -0
  75. package/worker/websocket-duplex.mjs +29 -0
  76. package/worker/wrangler.toml +38 -0
  77. package/workspace-client.d.ts +75 -0
  78. package/workspace-client.mjs +171 -0
  79. package/workspace-move.mjs +38 -0
@@ -0,0 +1,45 @@
1
+ // Copyright 2019, OpenTelemetry Authors
2
+ //
3
+ // Licensed under the Apache License, Version 2.0 (the "License");
4
+ // you may not use this file except in compliance with the License.
5
+ // You may obtain a copy of the License at
6
+ //
7
+ // http://www.apache.org/licenses/LICENSE-2.0
8
+ //
9
+ // Unless required by applicable law or agreed to in writing, software
10
+ // distributed under the License is distributed on an "AS IS" BASIS,
11
+ // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12
+ // See the License for the specific language governing permissions and
13
+ // limitations under the License.
14
+
15
+ syntax = "proto3";
16
+
17
+ package opentelemetry.proto.resource.v1;
18
+
19
+ import "opentelemetry/proto/common/v1/common.proto";
20
+
21
+ option csharp_namespace = "OpenTelemetry.Proto.Resource.V1";
22
+ option java_multiple_files = true;
23
+ option java_package = "io.opentelemetry.proto.resource.v1";
24
+ option java_outer_classname = "ResourceProto";
25
+ option go_package = "go.opentelemetry.io/proto/otlp/resource/v1";
26
+
27
+ // Resource information.
28
+ message Resource {
29
+ // Set of attributes that describe the resource.
30
+ // Attribute keys MUST be unique (it is not allowed to have more than one
31
+ // attribute with the same key).
32
+ // The behavior of software that receives duplicated keys can be unpredictable.
33
+ repeated opentelemetry.proto.common.v1.KeyValue attributes = 1;
34
+
35
+ // The number of dropped attributes. If the value is 0, then
36
+ // no attributes were dropped.
37
+ uint32 dropped_attributes_count = 2;
38
+
39
+ // Set of entities that participate in this Resource.
40
+ //
41
+ // Note: keys in the references MUST exist in attributes of this message.
42
+ //
43
+ // Status: [Development]
44
+ repeated opentelemetry.proto.common.v1.EntityRef entity_refs = 3;
45
+ }
@@ -0,0 +1,359 @@
1
+ // Copyright 2019, OpenTelemetry Authors
2
+ //
3
+ // Licensed under the Apache License, Version 2.0 (the "License");
4
+ // you may not use this file except in compliance with the License.
5
+ // You may obtain a copy of the License at
6
+ //
7
+ // http://www.apache.org/licenses/LICENSE-2.0
8
+ //
9
+ // Unless required by applicable law or agreed to in writing, software
10
+ // distributed under the License is distributed on an "AS IS" BASIS,
11
+ // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12
+ // See the License for the specific language governing permissions and
13
+ // limitations under the License.
14
+
15
+ syntax = "proto3";
16
+
17
+ package opentelemetry.proto.trace.v1;
18
+
19
+ import "opentelemetry/proto/common/v1/common.proto";
20
+ import "opentelemetry/proto/resource/v1/resource.proto";
21
+
22
+ option csharp_namespace = "OpenTelemetry.Proto.Trace.V1";
23
+ option java_multiple_files = true;
24
+ option java_package = "io.opentelemetry.proto.trace.v1";
25
+ option java_outer_classname = "TraceProto";
26
+ option go_package = "go.opentelemetry.io/proto/otlp/trace/v1";
27
+
28
+ // TracesData represents the traces data that can be stored in a persistent storage,
29
+ // OR can be embedded by other protocols that transfer OTLP traces data but do
30
+ // not implement the OTLP protocol.
31
+ //
32
+ // The main difference between this message and collector protocol is that
33
+ // in this message there will not be any "control" or "metadata" specific to
34
+ // OTLP protocol.
35
+ //
36
+ // When new fields are added into this message, the OTLP request MUST be updated
37
+ // as well.
38
+ message TracesData {
39
+ // An array of ResourceSpans.
40
+ // For data coming from a single resource this array will typically contain
41
+ // one element. Intermediary nodes that receive data from multiple origins
42
+ // typically batch the data before forwarding further and in that case this
43
+ // array will contain multiple elements.
44
+ repeated ResourceSpans resource_spans = 1;
45
+ }
46
+
47
+ // A collection of ScopeSpans from a Resource.
48
+ message ResourceSpans {
49
+ reserved 1000;
50
+
51
+ // The resource for the spans in this message.
52
+ // If this field is not set then no resource info is known.
53
+ opentelemetry.proto.resource.v1.Resource resource = 1;
54
+
55
+ // A list of ScopeSpans that originate from a resource.
56
+ repeated ScopeSpans scope_spans = 2;
57
+
58
+ // The Schema URL, if known. This is the identifier of the Schema that the resource data
59
+ // is recorded in. Notably, the last part of the URL path is the version number of the
60
+ // schema: http[s]://server[:port]/path/<version>. To learn more about Schema URL see
61
+ // https://opentelemetry.io/docs/specs/otel/schemas/#schema-url
62
+ // This schema_url applies to the data in the "resource" field. It does not apply
63
+ // to the data in the "scope_spans" field which have their own schema_url field.
64
+ string schema_url = 3;
65
+ }
66
+
67
+ // A collection of Spans produced by an InstrumentationScope.
68
+ message ScopeSpans {
69
+ // The instrumentation scope information for the spans in this message.
70
+ // Semantically when InstrumentationScope isn't set, it is equivalent with
71
+ // an empty instrumentation scope name (unknown).
72
+ opentelemetry.proto.common.v1.InstrumentationScope scope = 1;
73
+
74
+ // A list of Spans that originate from an instrumentation scope.
75
+ repeated Span spans = 2;
76
+
77
+ // The Schema URL, if known. This is the identifier of the Schema that the span data
78
+ // is recorded in. Notably, the last part of the URL path is the version number of the
79
+ // schema: http[s]://server[:port]/path/<version>. To learn more about Schema URL see
80
+ // https://opentelemetry.io/docs/specs/otel/schemas/#schema-url
81
+ // This schema_url applies to the data in the "scope" field and all spans and span
82
+ // events in the "spans" field.
83
+ string schema_url = 3;
84
+ }
85
+
86
+ // A Span represents a single operation performed by a single component of the system.
87
+ //
88
+ // The next available field id is 17.
89
+ message Span {
90
+ // A unique identifier for a trace. All spans from the same trace share
91
+ // the same `trace_id`. The ID is a 16-byte array. An ID with all zeroes OR
92
+ // of length other than 16 bytes is considered invalid (empty string in OTLP/JSON
93
+ // is zero-length and thus is also invalid).
94
+ //
95
+ // This field is required.
96
+ bytes trace_id = 1;
97
+
98
+ // A unique identifier for a span within a trace, assigned when the span
99
+ // is created. The ID is an 8-byte array. An ID with all zeroes OR of length
100
+ // other than 8 bytes is considered invalid (empty string in OTLP/JSON
101
+ // is zero-length and thus is also invalid).
102
+ //
103
+ // This field is required.
104
+ bytes span_id = 2;
105
+
106
+ // trace_state conveys information about request position in multiple distributed tracing graphs.
107
+ // It is a trace_state in w3c-trace-context format: https://www.w3.org/TR/trace-context/#tracestate-header
108
+ // See also https://github.com/w3c/distributed-tracing for more details about this field.
109
+ string trace_state = 3;
110
+
111
+ // The `span_id` of this span's parent span. If this is a root span, then this
112
+ // field must be empty. The ID is an 8-byte array.
113
+ bytes parent_span_id = 4;
114
+
115
+ // Flags, a bit field.
116
+ //
117
+ // Bits 0-7 (8 least significant bits) are the trace flags as defined in W3C Trace
118
+ // Context specification. To read the 8-bit W3C trace flag, use
119
+ // `flags & SPAN_FLAGS_TRACE_FLAGS_MASK`.
120
+ //
121
+ // See https://www.w3.org/TR/trace-context-2/#trace-flags for the flag definitions.
122
+ //
123
+ // Bits 8 and 9 represent the 3 states of whether a span's parent
124
+ // is remote. The states are (unknown, is not remote, is remote).
125
+ // To read whether the value is known, use `(flags & SPAN_FLAGS_CONTEXT_HAS_IS_REMOTE_MASK) != 0`.
126
+ // To read whether the span is remote, use `(flags & SPAN_FLAGS_CONTEXT_IS_REMOTE_MASK) != 0`.
127
+ //
128
+ // When creating span messages, if the message is logically forwarded from another source
129
+ // with an equivalent flags fields (i.e., usually another OTLP span message), the field SHOULD
130
+ // be copied as-is. If creating from a source that does not have an equivalent flags field
131
+ // (such as a runtime representation of an OpenTelemetry span), the high 22 bits MUST
132
+ // be set to zero.
133
+ // Readers MUST NOT assume that bits 10-31 (22 most significant bits) will be zero.
134
+ //
135
+ // [Optional].
136
+ fixed32 flags = 16;
137
+
138
+ // A description of the span's operation.
139
+ //
140
+ // For example, the name can be a qualified method name or a file name
141
+ // and a line number where the operation is called. A best practice is to use
142
+ // the same display name at the same call point in an application.
143
+ // This makes it easier to correlate spans in different traces.
144
+ //
145
+ // This field is semantically required to be set to non-empty string.
146
+ // Empty value is equivalent to an unknown span name.
147
+ //
148
+ // This field is required.
149
+ string name = 5;
150
+
151
+ // SpanKind is the type of span. Can be used to specify additional relationships between spans
152
+ // in addition to a parent/child relationship.
153
+ enum SpanKind {
154
+ // Unspecified. Do NOT use as default.
155
+ // Implementations MAY assume SpanKind to be INTERNAL when receiving UNSPECIFIED.
156
+ SPAN_KIND_UNSPECIFIED = 0;
157
+
158
+ // Indicates that the span represents an internal operation within an application,
159
+ // as opposed to an operation happening at the boundaries. Default value.
160
+ SPAN_KIND_INTERNAL = 1;
161
+
162
+ // Indicates that the span covers server-side handling of an RPC or other
163
+ // remote network request.
164
+ SPAN_KIND_SERVER = 2;
165
+
166
+ // Indicates that the span describes a request to some remote service.
167
+ SPAN_KIND_CLIENT = 3;
168
+
169
+ // Indicates that the span describes a producer sending a message to a broker.
170
+ // Unlike CLIENT and SERVER, there is often no direct critical path latency relationship
171
+ // between producer and consumer spans. A PRODUCER span ends when the message was accepted
172
+ // by the broker while the logical processing of the message might span a much longer time.
173
+ SPAN_KIND_PRODUCER = 4;
174
+
175
+ // Indicates that the span describes consumer receiving a message from a broker.
176
+ // Like the PRODUCER kind, there is often no direct critical path latency relationship
177
+ // between producer and consumer spans.
178
+ SPAN_KIND_CONSUMER = 5;
179
+ }
180
+
181
+ // Distinguishes between spans generated in a particular context. For example,
182
+ // two spans with the same name may be distinguished using `CLIENT` (caller)
183
+ // and `SERVER` (callee) to identify queueing latency associated with the span.
184
+ SpanKind kind = 6;
185
+
186
+ // The start time of the span. On the client side, this is the time
187
+ // kept by the local machine where the span execution starts. On the server side, this
188
+ // is the time when the server's application handler starts running.
189
+ // Value is UNIX Epoch time in nanoseconds since 00:00:00 UTC on 1 January 1970.
190
+ //
191
+ // This field is semantically required and it is expected that end_time >= start_time.
192
+ fixed64 start_time_unix_nano = 7;
193
+
194
+ // The end time of the span. On the client side, this is the time
195
+ // kept by the local machine where the span execution ends. On the server side, this
196
+ // is the time when the server application handler stops running.
197
+ // Value is UNIX Epoch time in nanoseconds since 00:00:00 UTC on 1 January 1970.
198
+ //
199
+ // This field is semantically required and it is expected that end_time >= start_time.
200
+ fixed64 end_time_unix_nano = 8;
201
+
202
+ // A collection of key/value pairs. Note, global attributes
203
+ // like server name can be set using the resource API. Examples of attributes:
204
+ //
205
+ // "/http/user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36"
206
+ // "/http/server_latency": 300
207
+ // "example.com/myattribute": true
208
+ // "example.com/score": 10.239
209
+ //
210
+ // Attribute keys MUST be unique (it is not allowed to have more than one
211
+ // attribute with the same key).
212
+ // The behavior of software that receives duplicated keys can be unpredictable.
213
+ repeated opentelemetry.proto.common.v1.KeyValue attributes = 9;
214
+
215
+ // The number of attributes that were discarded. Attributes
216
+ // can be discarded because their keys are too long or because there are too many
217
+ // attributes. If this value is 0, then no attributes were dropped.
218
+ uint32 dropped_attributes_count = 10;
219
+
220
+ // Event is a time-stamped annotation of the span, consisting of user-supplied
221
+ // text description and key-value pairs.
222
+ message Event {
223
+ // The time the event occurred.
224
+ fixed64 time_unix_nano = 1;
225
+
226
+ // The name of the event.
227
+ // This field is semantically required to be set to non-empty string.
228
+ string name = 2;
229
+
230
+ // A collection of attribute key/value pairs on the event.
231
+ // Attribute keys MUST be unique (it is not allowed to have more than one
232
+ // attribute with the same key).
233
+ // The behavior of software that receives duplicated keys can be unpredictable.
234
+ repeated opentelemetry.proto.common.v1.KeyValue attributes = 3;
235
+
236
+ // The number of dropped attributes. If the value is 0,
237
+ // then no attributes were dropped.
238
+ uint32 dropped_attributes_count = 4;
239
+ }
240
+
241
+ // A collection of Event items.
242
+ repeated Event events = 11;
243
+
244
+ // The number of dropped events. If the value is 0, then no
245
+ // events were dropped.
246
+ uint32 dropped_events_count = 12;
247
+
248
+ // A pointer from the current span to another span in the same trace or in a
249
+ // different trace. For example, this can be used in batching operations,
250
+ // where a single batch handler processes multiple requests from different
251
+ // traces or when the handler receives a request from a different project.
252
+ message Link {
253
+ // A unique identifier of a trace that this linked span is part of. The ID is a
254
+ // 16-byte array.
255
+ bytes trace_id = 1;
256
+
257
+ // A unique identifier for the linked span. The ID is an 8-byte array.
258
+ bytes span_id = 2;
259
+
260
+ // The trace_state associated with the link.
261
+ string trace_state = 3;
262
+
263
+ // A collection of attribute key/value pairs on the link.
264
+ // Attribute keys MUST be unique (it is not allowed to have more than one
265
+ // attribute with the same key).
266
+ // The behavior of software that receives duplicated keys can be unpredictable.
267
+ repeated opentelemetry.proto.common.v1.KeyValue attributes = 4;
268
+
269
+ // The number of dropped attributes. If the value is 0,
270
+ // then no attributes were dropped.
271
+ uint32 dropped_attributes_count = 5;
272
+
273
+ // Flags, a bit field.
274
+ //
275
+ // Bits 0-7 (8 least significant bits) are the trace flags as defined in W3C Trace
276
+ // Context specification. To read the 8-bit W3C trace flag, use
277
+ // `flags & SPAN_FLAGS_TRACE_FLAGS_MASK`.
278
+ //
279
+ // See https://www.w3.org/TR/trace-context-2/#trace-flags for the flag definitions.
280
+ //
281
+ // Bits 8 and 9 represent the 3 states of whether the link is remote.
282
+ // The states are (unknown, is not remote, is remote).
283
+ // To read whether the value is known, use `(flags & SPAN_FLAGS_CONTEXT_HAS_IS_REMOTE_MASK) != 0`.
284
+ // To read whether the link is remote, use `(flags & SPAN_FLAGS_CONTEXT_IS_REMOTE_MASK) != 0`.
285
+ //
286
+ // Readers MUST NOT assume that bits 10-31 (22 most significant bits) will be zero.
287
+ // When creating new spans, bits 10-31 (most-significant 22-bits) MUST be zero.
288
+ //
289
+ // [Optional].
290
+ fixed32 flags = 6;
291
+ }
292
+
293
+ // A collection of Links, which are references from this span to a span
294
+ // in the same or different trace.
295
+ repeated Link links = 13;
296
+
297
+ // The number of dropped links after the maximum size was
298
+ // enforced. If this value is 0, then no links were dropped.
299
+ uint32 dropped_links_count = 14;
300
+
301
+ // An optional final status for this span. Semantically when Status isn't set, it means
302
+ // span's status code is unset, i.e. assume STATUS_CODE_UNSET (code = 0).
303
+ Status status = 15;
304
+ }
305
+
306
+ // The Status type defines a logical error model that is suitable for different
307
+ // programming environments, including REST APIs and RPC APIs.
308
+ message Status {
309
+ reserved 1;
310
+
311
+ // A developer-facing human readable error message.
312
+ string message = 2;
313
+
314
+ // For the semantics of status codes see
315
+ // https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#set-status
316
+ enum StatusCode {
317
+ // The default status.
318
+ STATUS_CODE_UNSET = 0;
319
+ // The Span has been validated by an Application developer or Operator to
320
+ // have completed successfully.
321
+ STATUS_CODE_OK = 1;
322
+ // The Span contains an error.
323
+ STATUS_CODE_ERROR = 2;
324
+ };
325
+
326
+ // The status code.
327
+ StatusCode code = 3;
328
+ }
329
+
330
+ // SpanFlags represents constants used to interpret the
331
+ // Span.flags field, which is protobuf 'fixed32' type and is to
332
+ // be used as bit-fields. Each non-zero value defined in this enum is
333
+ // a bit-mask. To extract the bit-field, for example, use an
334
+ // expression like:
335
+ //
336
+ // (span.flags & SPAN_FLAGS_TRACE_FLAGS_MASK)
337
+ //
338
+ // See https://www.w3.org/TR/trace-context-2/#trace-flags for the flag definitions.
339
+ //
340
+ // Note that Span flags were introduced in version 1.1 of the
341
+ // OpenTelemetry protocol. Older Span producers do not set this
342
+ // field, consequently consumers should not rely on the absence of a
343
+ // particular flag bit to indicate the presence of a particular feature.
344
+ enum SpanFlags {
345
+ // The zero value for the enum. Should not be used for comparisons.
346
+ // Instead use bitwise "and" with the appropriate mask as shown above.
347
+ SPAN_FLAGS_DO_NOT_USE = 0;
348
+
349
+ // Bits 0-7 are used for trace flags.
350
+ SPAN_FLAGS_TRACE_FLAGS_MASK = 0x000000FF;
351
+
352
+ // Bits 8 and 9 are used to indicate that the parent span or link span is remote.
353
+ // Bit 8 (`HAS_IS_REMOTE`) indicates whether the value is known.
354
+ // Bit 9 (`IS_REMOTE`) indicates whether the span or link is remote.
355
+ SPAN_FLAGS_CONTEXT_HAS_IS_REMOTE_MASK = 0x00000100;
356
+ SPAN_FLAGS_CONTEXT_IS_REMOTE_MASK = 0x00000200;
357
+
358
+ // Bits 10-31 are reserved for future use.
359
+ }
@@ -0,0 +1,10 @@
1
+ export type OtlpSignal = "logs" | "traces" | "metrics";
2
+ export type OtlpRepresentation = "json" | "protobuf" | "application/json" | "application/x-protobuf";
3
+ export interface RawOtlpEvidence { signal: OtlpSignal; evidenceKind: "log_record" | "span" | "metric_data_point" | "metric_metadata"; resource: unknown | null; resourceSchemaUrl: string | null; scope: unknown | null; scopeSchemaUrl: string | null; record: unknown; metric?: { dataType: string | null; data: unknown; [key: string]: unknown }; receivedAt: number | null; position: { resourceIndex: number; scopeIndex: number; recordIndex: number; pointIndex?: number } }
4
+ export declare const MAX_UNCOMPRESSED_BODY_BYTES: number;
5
+ export declare function decodeOtlpRequest(input: { signal: OtlpSignal; representation: OtlpRepresentation; bytes: Uint8Array | string; receivedAt?: number | null }): Promise<{ envelope: unknown; records: RawOtlpEvidence[]; rejected: Array<{ evidence: RawOtlpEvidence; error: string }> }>;
6
+ export declare function encodeOtlpRequest(input: { signal: OtlpSignal; representation: OtlpRepresentation; envelope: unknown }): Promise<Buffer>;
7
+ export declare function encodeOtlpResponse(input: { signal: OtlpSignal; representation: OtlpRepresentation; rejectedCount?: number; errorMessage?: string }): Promise<Buffer>;
8
+ export declare function encodeOtlpError(input: { representation: OtlpRepresentation; code: number; message: string }): Promise<Buffer>;
9
+ export declare function decodeContentEncoding(bytes: Uint8Array | string, contentEncoding?: string, maxBytes?: number): Uint8Array;
10
+ export declare function readBoundedBody(body: Uint8Array | string | AsyncIterable<Uint8Array | string>, maxBytes?: number): Promise<Uint8Array>;