-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Better dotenv error messages #4464
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
7 Ignored Deployments
|
✅ This changes can build |
🟢 CI successful 🟢Thanks |
jridgewell
force-pushed
the
jrl-env-root-cause
branch
from
April 5, 2023 06:48
8080837
to
1e3603a
Compare
jridgewell
added
the
pr: automerge
Kodiak will merge these automatically after checks pass
label
Apr 5, 2023
sokra
requested changes
Apr 5, 2023
jridgewell
commented
Apr 5, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh wow, I don't know why I didn't see the potential to split the methods. Done.
jridgewell
force-pushed
the
jrl-env-root-cause
branch
from
April 6, 2023 04:18
5486be2
to
dac29fc
Compare
sokra
approved these changes
Apr 6, 2023
sokra
added a commit
to vercel/next.js
that referenced
this pull request
Apr 6, 2023
### What? Add a error message when using "use server". * vercel/turborepo#4477 <!-- Tobias Koppers - add ServerDirective transform which reports unsupported --> ### Why? Turbopack doesn't support "use server" yet. ### Other turbopack updates * vercel/turborepo#4464 <!-- Justin Ridgewell - Better dotenv error messages --> * vercel/turborepo#4485 <!-- Justin Ridgewell - Add ServerAddr::hostname method -->
sokra
added a commit
to vercel/next.js
that referenced
this pull request
Apr 6, 2023
### What? Add a error message when using "use server". * vercel/turborepo#4477 <!-- Tobias Koppers - add ServerDirective transform which reports unsupported --> ### Why? Turbopack doesn't support "use server" yet. ### Other turbopack updates * vercel/turborepo#4464 <!-- Justin Ridgewell - Better dotenv error messages --> * vercel/turborepo#4485 <!-- Justin Ridgewell - Add ServerAddr::hostname method -->
sokra
added a commit
to vercel/next.js
that referenced
this pull request
Apr 6, 2023
### What? Add a error message when using "use server". * vercel/turborepo#4477 <!-- Tobias Koppers - add ServerDirective transform which reports unsupported --> ### Why? Turbopack doesn't support "use server" yet. ### Other turbopack updates * vercel/turborepo#4464 <!-- Justin Ridgewell - Better dotenv error messages --> * vercel/turborepo#4485 <!-- Justin Ridgewell - Add ServerAddr::hostname method -->
sokra
added a commit
to vercel/next.js
that referenced
this pull request
Apr 6, 2023
### What? Add a error message when using "use server". * vercel/turborepo#4477 <!-- Tobias Koppers - add ServerDirective transform which reports unsupported --> ### Why? Turbopack doesn't support "use server" yet. ### Other turbopack updates * vercel/turborepo#4464 <!-- Justin Ridgewell - Better dotenv error messages --> * vercel/turborepo#4485 <!-- Justin Ridgewell - Add ServerAddr::hostname method -->
sokra
added a commit
to vercel/next.js
that referenced
this pull request
Apr 6, 2023
### What? Add a error message when using "use server". * vercel/turborepo#4477 <!-- Tobias Koppers - add ServerDirective transform which reports unsupported --> ### Why? Turbopack doesn't support "use server" yet. ### Other turbopack updates * vercel/turborepo#4464 <!-- Justin Ridgewell - Better dotenv error messages --> * vercel/turborepo#4485 <!-- Justin Ridgewell - Add ServerAddr::hostname method -->
sokra
added a commit
to vercel/next.js
that referenced
this pull request
Apr 6, 2023
### What? Add a error message when using "use server". * vercel/turborepo#4477 <!-- Tobias Koppers - add ServerDirective transform which reports unsupported --> ### Why? Turbopack doesn't support "use server" yet. ### Other turbopack updates * vercel/turborepo#4464 <!-- Justin Ridgewell - Better dotenv error messages --> * vercel/turborepo#4485 <!-- Justin Ridgewell - Add ServerAddr::hostname method -->
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 25, 2024
The issue message emitted by `TryDotenvProcessEnv` was pretty bad: `Execution of TryDotenvProcessEnv::read_all failed`. This error message comes from #3550, which attaches the calling function as the context for every failed turbo function. This PR accomplishes 2 main things: 1. Expose an explicit method determining whether a the `DotenvEnvProcess`'s prior or current env failed 2. Detects a current env failure and uses the error's root cause for the issue message. <img width="961" alt="Screen Shot 2023-04-04 at 7 29 52 PM" src="https://user-images.githubusercontent.com/112982/229944525-d39dbe87-778a-4421-9bc8-632924cd3782.png"> Fixes WEB-851 Tests: #47937
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Jul 29, 2024
The issue message emitted by `TryDotenvProcessEnv` was pretty bad: `Execution of TryDotenvProcessEnv::read_all failed`. This error message comes from #3550, which attaches the calling function as the context for every failed turbo function. This PR accomplishes 2 main things: 1. Expose an explicit method determining whether a the `DotenvEnvProcess`'s prior or current env failed 2. Detects a current env failure and uses the error's root cause for the issue message. <img width="961" alt="Screen Shot 2023-04-04 at 7 29 52 PM" src="https://user-images.githubusercontent.com/112982/229944525-d39dbe87-778a-4421-9bc8-632924cd3782.png"> Fixes WEB-851 Tests: #47937
ForsakenHarmony
pushed a commit
to vercel/next.js
that referenced
this pull request
Aug 1, 2024
The issue message emitted by `TryDotenvProcessEnv` was pretty bad: `Execution of TryDotenvProcessEnv::read_all failed`. This error message comes from #3550, which attaches the calling function as the context for every failed turbo function. This PR accomplishes 2 main things: 1. Expose an explicit method determining whether a the `DotenvEnvProcess`'s prior or current env failed 2. Detects a current env failure and uses the error's root cause for the issue message. <img width="961" alt="Screen Shot 2023-04-04 at 7 29 52 PM" src="https://user-images.githubusercontent.com/112982/229944525-d39dbe87-778a-4421-9bc8-632924cd3782.png"> Fixes WEB-851 Tests: #47937
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue message emitted by
TryDotenvProcessEnv
was pretty bad:Execution of TryDotenvProcessEnv::read_all failed
. This error message comes from #3550, which attaches the calling function as the context for every failed turbo function.This PR accomplishes 2 main things:
DotenvEnvProcess
's prior or current env failedFixes WEB-851
Tests: vercel/next.js#47937