-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't print platform detection warnings when custom binaries are provided #17900
Comments
I'm having the same issue. The warning indeed makes no sense when using custom binaries. |
Is someone working on this issue? Otherwise, I would have a look :) |
Previously on nixos, an error message regarding not available precompiled engine files was always printed. With this change, the error message is only shown if the engine files were not configured correctly via environment variables. Fixes: prisma#17900
Proposed fix to this in this PR #20138 :) |
Previously on nixos, an error message regarding not available precompiled engine files was always printed. With this change, the error message is only shown if the engine files were not configured correctly via environment variables. Fixes: prisma#17900
Previously on nixos, an error message regarding not available precompiled engine files was always printed. With this change, the error message is only shown if the engine files were not configured correctly via environment variables. Fixes: prisma#17900
Previously on nixos, an error message regarding not available precompiled engine files was always printed. With this change, the error message is only shown if the engine files were not configured correctly via environment variables. Fixes: prisma#17900
Previously on nixos, an error message regarding not available precompiled engine files was always printed. With this change, the error message is only shown if the engine files were not configured correctly via environment variables. Fixes: prisma#17900
Was going to reopen since providing the env vars doesn't skip the OpenSSL warning yet — but that's something that would be better requested in a separate issue (especially now that we technically do have another way to to skip the OpenSSL warning). |
Reopened since the openssl warning is still present, and the feature that provides a workaround is temporarily reverted. |
Currently the output on NixOS (e.g.,
nix-shell -p nodePackages.prisma --run "prisma --version"
) is too noisy:Also, an identical warning about OpenSSL is printed twice.
When custom binaries are provided, these warnings become less useful at best or misleading at worst, so it's best to skip them.
The text was updated successfully, but these errors were encountered: