-
Notifications
You must be signed in to change notification settings - Fork 10
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
feat: container-type level version compatibility check #140
Conversation
Signed-off-by: Keran Yang <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #140 +/- ##
=======================================
Coverage ? 60.41%
Complexity ? 364
=======================================
Files ? 122
Lines ? 2448
Branches ? 169
=======================================
Hits ? 1479
Misses ? 840
Partials ? 129 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Keran Yang <[email protected]>
FBSINKER("fb-sinker"), | ||
UNKNOWN("unknown"); | ||
|
||
private final String name; | ||
|
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.
Do we need to support UNKNOWN
?
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.
No, I put it mainly for error scenarios.
As discussed, lets not go extract the container type from the server info file path. We can pass it as an argument from each component.
Signed-off-by: Keran Yang <[email protected]>
Java version of numaproj/numaflow-go@36deadf