Currently, when there is a schema mismatch, it is difficult to identify the input and schema that caused the mismatch. In particular, Sequence schema uses valibot's special schema internally, so it is difficult to identify the cause of the mismatch.
[01:45:27.184] ERROR (ldap/16312): AsnParseError
err: {
"type": "o",
"message": "",
"stack":
Error:
at C.decode ([...]/node_modules/@kazuemon/asn1/dist/index.js:120:13)
at LDAPServer.onData ([...])
at Socket.<anonymous> ([...])
at Socket.emit (node:events:519:28)
at addChunk (node:internal/streams/readable:559:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
at Socket.Readable.push (node:internal/streams/readable:390:5)
at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
}
Solution
Add input data and schema data to SchemaMismatchError
Problem
Solution