-
Couldn't load subscription status.
- Fork 2.3k
Created a new lib metadata-common to separate out metadata related dependencies from the server #18778
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
Conversation
|
❌ Gradle check result for 6301ae0: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
6301ae0 to
74eea10
Compare
|
❌ Gradle check result for 74eea10: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
74eea10 to
b160aef
Compare
|
❌ Gradle check result for b160aef: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
b160aef to
510451f
Compare
|
❌ Gradle check result for 510451f: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
510451f to
feb22a5
Compare
|
❌ Gradle check result for feb22a5: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
feb22a5 to
94dd65b
Compare
|
❌ Gradle check result for 94dd65b: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
94dd65b to
193faae
Compare
|
❌ Gradle check result for 193faae: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
193faae to
d305b45
Compare
|
❌ Gradle check result for d305b45: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
d305b45 to
0b6be9b
Compare
|
❌ Gradle check result for 0b6be9b: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
0b6be9b to
4846055
Compare
|
❌ Gradle check result for 4846055: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
4846055 to
fd56161
Compare
|
❌ Gradle check result for fd56161: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
fd56161 to
9f0bf16
Compare
|
❌ Gradle check result for 9f0bf16: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
339b4ad to
6ae833c
Compare
|
❌ Gradle check result for 6ae833c: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
6ae833c to
6da7edd
Compare
|
❌ Gradle check result for 6da7edd: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
6da7edd to
c7d6e35
Compare
|
❌ Gradle check result for c7d6e35: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
c7d6e35 to
ee6fc88
Compare
|
❌ Gradle check result for ee6fc88: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
ee6fc88 to
5c0c5d9
Compare
|
❌ Gradle check result for 5c0c5d9: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
5c0c5d9 to
fc96a6b
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #18778 +/- ##
============================================
- Coverage 72.80% 72.77% -0.04%
- Complexity 68535 68572 +37
============================================
Files 5572 5575 +3
Lines 314779 314876 +97
Branches 45691 45699 +8
============================================
- Hits 229166 229138 -28
- Misses 67014 67129 +115
- Partials 18599 18609 +10 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
fc96a6b to
33deac9
Compare
|
❌ Gradle check result for 33deac9: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
…pendencies from the server Signed-off-by: Manik Garg <gargmanik1317@gmail.com>
33deac9 to
a7dbb5b
Compare
|
❌ Gradle check result for a7dbb5b: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Created a new lib metadata-common to separate out metadata related dependencies from the server
Description
[Describe what this change achieves]
Related Issues
Resolves #[Issue number to be closed when this PR is merged]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.