-
Notifications
You must be signed in to change notification settings - Fork 5.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
fix(hydrator): don't use manifest-generate-paths (#22039) #22015
fix(hydrator): don't use manifest-generate-paths (#22039) #22015
Conversation
Signed-off-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com>
❌ Preview Environment deleted from BunnyshellAvailable commands (reply to this comment):
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #22015 +/- ##
==========================================
+ Coverage 55.73% 55.75% +0.02%
==========================================
Files 342 342
Lines 57075 57085 +10
==========================================
+ Hits 31809 31827 +18
+ Misses 22622 22621 -1
+ Partials 2644 2637 -7 ☔ View full report in Codecov by Sentry. |
…t-generate-paths Signed-off-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com>
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.
LGTM. Good call on documenting this!
/cherry-pick release-2.14 |
…goproj#22015) Signed-off-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com> Signed-off-by: Harshit-Bajpai <Harshit.Bajpai@skyscanner.net>
…goproj#22015) Signed-off-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com>
…goproj#22015) Signed-off-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com> Signed-off-by: kingbj0429 <kingbj0429@lunit.io>
Fixes #22039
The behavior is flaky, and the unit/e2e tests are prohibitively difficult to write. So I'm relying on using the change internally and noting that "Invalid revision range" disappears from logs after releasing the change.