# protocols-upload-checks
render pydantic_v2.BaseModel
  Error: --client-protocols['checks.later'].abort: The resumable_upload helper 'checks.later' declares remote abort, which is not supported yet; --client-protocols['checks.later'].create.session_url: The resumable_upload helper 'checks.later' declares a session URL, which is not supported yet; --client-protocols['checks.created'].create.operation: POST /drafts must declare a success response for the upload helper 'checks.created'; --client-protocols['checks.size'].create.size: The size of 'checks.size' writes the cookie 'session', which carries credentials no helper writes; --client-protocols['checks.size_body'].create.size: The size of 'checks.size_body' writes 'body', where only a path, query, or header parameter takes it; --client-protocols['checks.size_body'].probe.bindings[0].value.selector: The probe binding 0 pointer '/id' of 'checks.size_body' names no property of the POST /files/{fileId}/status response; --client-protocols['checks.size_body'].append.bindings[0].value.selector: The append binding 0 pointer '/id' of 'checks.size_body' names no property of the POST /files/{fileId}/status response; --client-protocols['checks.size_type'].create.size: The size of 'checks.size_type' gives integer values, which the header parameter 'X-Name' of POST /files does not accept; --client-protocols['checks.expiry_status'].create.expires_at: The server expiry of 'checks.expiry_status' reads the status, which gives no server expiry; --client-protocols['checks.expiry_type'].create.expires_at: The server expiry of 'checks.expiry_type' reads integer values, where only string values fit; --client-protocols['checks.expiry_header'].create.expires_at: The server expiry of 'checks.expiry_header' reads the header 'X-Expires', which POST /files does not declare; --client-protocols['checks.probe_sources'].probe.bindings[0].value.source: The probe binding 0 of 'checks.probe_sources' reads the previous response, which is not supported yet; --client-protocols['checks.probe_required'].probe.bindings: HEAD /files/{fileId} requires the path parameter 'fileId', which no binding of 'checks.probe_required' writes; --client-protocols['checks.probe_body'].probe.bindings: POST /files/{fileId}/status requires a request body, which no binding of 'checks.probe_body' writes; --client-protocols['checks.probe_form'].probe.bindings: The upload helper 'checks.probe_form' writes a request body of POST /files/{fileId}/form other than JSON, which is not supported yet; --client-protocols['checks.probe_media'].probe.bindings: The upload helper 'checks.probe_media' writes a request body of POST /files/{fileId}/search, which has no default media type; set the operation's request_media_type; --client-protocols['checks.probe_none'].probe.operation: DELETE /files/{fileId}/gone must declare a success response for the probe of 'checks.probe_none'; --client-protocols['checks.offset_type'].probe.remote_offset: The remote offset of 'checks.offset_type' reads string values, where only integer values fit; --client-protocols['checks.offset_status'].probe.remote_offset: The remote offset of 'checks.offset_status' reads the status, which gives no remote offset; --client-protocols['checks.append_media'].append.operation: PUT /files/{fileId} must take exactly one binary request media for the chunks of 'checks.append_media'; --client-protocols['checks.append_none'].append.operation: DELETE /files/{fileId}/gone must take exactly one binary request media for the chunks of 'checks.append_none'; --client-protocols['checks.append_none'].append.operation: DELETE /files/{fileId}/gone must declare a success response for the appends of 'checks.append_none'; --client-protocols['checks.append_none'].append.offset: The chunk offset of 'checks.append_none' writes the same target as its append binding 0; --client-protocols['checks.append_overlap'].append.offset: The chunk offset of 'checks.append_overlap' writes the same target as its append binding 1; --client-protocols['checks.append_length'].append.length: The chunk length of 'checks.append_length' writes the same target as its chunk offset; --client-protocols['checks.append_places'].append.offset: The chunk offset of 'checks.append_places' writes the cookie 'session', which carries credentials no helper writes; --client-protocols['checks.append_places'].append.length: The chunk length of 'checks.append_places' writes 'body', where only a path, query, or header parameter takes it; --client-protocols['checks.append_places'].append.bindings: PATCH /files/{fileId} requires the header parameter 'Upload-Offset', which no binding of 'checks.append_places' writes; --client-protocols['checks.append_types'].append.offset: The chunk offset of 'checks.append_types' gives integer values, which the header parameter 'X-Note' of PATCH /files/{fileId} does not accept; --client-protocols['checks.checksum_overlap'].append.checksum.target: The chunk checksum of 'checks.checksum_overlap' writes the same target as its chunk offset; --client-protocols['checks.checksum_place'].append.checksum.target: The chunk checksum of 'checks.checksum_place' writes the cookie 'session', which carries credentials no helper writes; --client-protocols['checks.checksum_type'].append.checksum.target: The chunk checksum of 'checks.checksum_type' gives string values, which the header parameter 'X-Count' of PATCH /files/{fileId} does not accept; --client-protocols['checks.append_body'].append.bindings[1].target: The append binding 1 of 'checks.append_body' writes the request body, which is the chunk; --client-protocols['checks.completion_media'].completion.operation: POST /files/{fileId}/finish must declare exactly one JSON success response for the completion of 'checks.completion_media'; --client-protocols['checks.completion_missing'].completion.result_schema: The result schema '/components/schemas/Missing' of 'checks.completion_missing' does not exist in its document; --client-protocols['checks.completion_other'].completion.result_schema: The result schema '/components/schemas/Note' of 'checks.completion_other' is not the schema of the POST /files/{fileId}/complete response; --client-protocols['checks.completion_body'].completion.bindings: POST /files/{fileId}/complete requires a request body, which no binding of 'checks.completion_body' writes
