-
Notifications
You must be signed in to change notification settings - Fork 17
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
Big upstream sync #217
Merged
Merged
Big upstream sync #217
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
To prevent infinite recursion, only the "top-level" method established the "seen" set.
I originally wrote this as a proof-of-concept and testing, but it's not a legal case because the `Dataset` ctor isn't publicly visible. In other words, `Dataset` isn't a ctor that returns in `Dataset` in "real life." Doing this initially just made the implementation a bit easier to visualize.
It shouldn't just pass-through it's argument. Otherwise, the PA doesn't look right.
* Intraprocedural case for dataset iterators. * More tests. * Handle the intraprocedural case.
This reverts commit 53aa471. It's failing test cases in our client but seems not to do any harm here.
…_from_directory()`.
* New dataset APIs. * Add `from_tensors()`. * Add summary for `tf.data.Dataset.enumerate()`. * More APIs. * Apply spotless. * Add `list_files` summary. * Add random. * Sample from datasets. * Apply spotless.
Let's keep it. We may use it at some point.
* Add tests. * More tests for wala#65. * Hack it. * More tests. * More tests. * Revert "Hack it." This reverts commit 13f6c78. Do it through the PA instead. * Progress. * Remove warning suppression. We're using the logger now. * More tests. * Add logging. * Progress. * Another transitive test. * Only traverse the queue. We still need it. * Check if the value is a constant first. * Rearrange. * Short circuit when we find the import. Use only the first found library. * Generalize. * Move CG assertions after dump. * Cleanup variables. * Remove unnecessarily method call. * Move variables out. * Progress. * Cleanup. * Update test.
Bumps `maven.surefire.version` from 3.3.0 to 3.3.1. Updates `org.apache.maven.plugins:maven-surefire-plugin` from 3.3.0 to 3.3.1 - [Release notes](https://github.com/apache/maven-surefire/releases) - [Commits](apache/maven-surefire@surefire-3.3.0...surefire-3.3.1) Updates `org.apache.maven.plugins:maven-surefire-report-plugin` from 3.3.0 to 3.3.1 - [Release notes](https://github.com/apache/maven-surefire/releases) - [Commits](apache/maven-surefire@surefire-3.3.0...surefire-3.3.1) --- updated-dependencies: - dependency-name: org.apache.maven.plugins:maven-surefire-plugin dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: org.apache.maven.plugins:maven-surefire-report-plugin dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
For example: `from X.Y.Z import *`.
This reverts commit 5d72128.
This reverts commit abc9b16.
…re.version-3.3.1 Bump maven.surefire.version from 3.3.0 to 3.3.1
Bumps [org.apache.maven.plugins:maven-shade-plugin](https://github.com/apache/maven-shade-plugin) from 3.4.1 to 3.6.0. - [Release notes](https://github.com/apache/maven-shade-plugin/releases) - [Commits](apache/maven-shade-plugin@maven-shade-plugin-3.4.1...maven-shade-plugin-3.6.0) --- updated-dependencies: - dependency-name: org.apache.maven.plugins:maven-shade-plugin dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
This can happen now since we continue processing after a parse error.
Bumps [black](https://github.com/psf/black) from 24.4.2 to 24.8.0. - [Release notes](https://github.com/psf/black/releases) - [Changelog](https://github.com/psf/black/blob/main/CHANGES.md) - [Commits](psf/black@24.4.2...24.8.0) --- updated-dependencies: - dependency-name: black dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Bump black from 24.4.2 to 24.8.0
…maven-shade-plugin-3.6.0
…aven.plugins-maven-shade-plugin-3.6.0 Bump org.apache.maven.plugins:maven-shade-plugin from 3.4.1 to 3.6.0
msridhar
approved these changes
Nov 8, 2024
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.
Gonna blind stamp this one, no way I'm going to have time to review anytime soon 🙂
Thanks! |
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.
Sorry for the large sync up. I'll try to summarize the changes as best as I can:
CODEOWNERS
file (please modify if desired).PYTHONPATH
module fixes (e.g., Incorrect import when there are two files with the same name but in different directories #209).tf.reshape()
for data sources other than MNIST #195.reshape()
parsing (this causes a need for a workaround after exposing a bug).abseil
,click
.__init__.py
).