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.
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(sdk): unblock valid topology. #8416
fix(sdk): unblock valid topology. #8416
Changes from 1 commit
693b583
02ba99a
a23f9ae
f73e94d
8b3b633
472bc02
07e74fd
4d8b6b4
586ef5a
2eb19cf
867bc86
60c167a
9593203
f01e25e
0a0d15b
ecbd172
6ea91c0
3593036
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 action required / not your code: I want to note here that I'm not sure if this should use a
RuntimeError
. This is a runtime error in the sense that it results an ambiguous runtime topology, but it's not a true "runtime" error at the time it's raised.This file used
RuntimeError
before this PR and, since this PR actually reduces the set of topologies for which this error would be raised, we don't necessarily need to reconsider this in this PR.Furthermore, an
Exception
is usually used when the error is attributed to user code, whereas anError
is usually used when the error is attributed to something else, such as an environment. In this case, this is user code.For this reason, I think it would make sense for this to be a custom
InvalidTopologyException
or something similar.Relatedly, some of the
ValueErrors
frompipeline_task.py
now becomeRuntimeErrors
in this PR, so perhaps that is a reason to consider this in the short term.