Error: Error in migration engine. Reason: [migration-engine\cli\src/main.rs:68:41] called `Result::unwrap()` on an `Err` value: Custom { kind: InvalidData, error: "stream did not contain valid UTF-8" }

[divyenduz]

Command: prisma migrate dev --preview-feature
Version: 2.16.0
Binary Version: 854c8ba7f0dce66f115af36af24e66989a8c02a1
Report: https://prisma-errors.netlify.app/report/12944
OS: x64 win32 10.0.19041

JS Stacktrace:

Error: Error in migration engine.
Reason: [migration-engine\cli\src/main.rs:68:41] called `Result::unwrap()` on an `Err` value: Custom { kind: InvalidData, error: "stream did not contain valid UTF-8" }

Please create an issue with your `schema.prisma` at 
https://github.com/prisma/prisma/issues/new

    at ChildProcess.<anonymous> (C:\Users\kaTeilX\AppData\Roaming\npm\node_modules\prisma\build\index.js:54621:23)
    at ChildProcess.emit (events.js:210:5)
    at ChildProcess.EventEmitter.emit (domain.js:475:20)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)

Rust Stacktrace:

[migration-engine\cli\src/main.rs:68:41] called `Result::unwrap()` on an `Err` value: Custom { kind: InvalidData, error: "stream did not contain valid UTF-8" }

[safinsingh]

Rust Strings must contain valid UTF-8, and judging by this code, it seems like your schema contained invalid UTF-8. Verify the character encoding of the file.

[pantharshit00]

@safinsingh Yes, we are aware of that. Issue is automatically collected from the cli so @divyenduz is not the user here.

We are more concerned about the panic. Engine panic should never happen as we try to handle all errors gracefully.

[safinsingh]

Perhaps instead of unwrapping, you could use something like anyhow to gracefully handle errors with additional context?

[pantharshit00]

Yeah, that is what we will do but we also need to propagate this upto the javascript client. We have some macros in the codebase for that.