Relax subgraph byte constraint to required_bytes <= bytes rather than exact match.
#64973
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
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=60&v=4){kind=small}
copybara-service
bot
force-pushed
the
exported_pr_620832564
branch
from
50ba89e
to
34ed856
Compare
…an exact match. This has been an error raised for some issues [github example](#14929). If the required bytes are covered by the current model, there is no need to raise an error due to exact size mismatch on user's side. PiperOrigin-RevId: 621699856
copybara-service
bot
force-pushed
the
exported_pr_620832564
branch
from
34ed856
to
8d698c3
Compare
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.
Relax subgraph byte constraint to
required_bytes <= bytesrather than exact match.This has been an error raised for some issues github example.
If the required bytes are covered by the current model, there is no need to raise an error due to exact size mismatch on user's side.