-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[Beam-13256] [Playground] Implement an example verification method #16048
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
[Beam-13256] [Playground] Implement an example verification method #16048
Conversation
…tions (#83) * Update workflows for playground * Attempt to fix tests * Remove continue on error to catch errors * Fix linter problem for backend dockerfile * Update folder to run backend go linter * Moved flutter test to execution via gradle tasks
Setup logger;
|
R: @pabloem |
| # TODO [BEAM-13256] Implement | ||
| pass | ||
| client = GRPCClient() | ||
| verify_failed = False |
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.
so I suppose somewhere around here we'll make calls to the service to actually verify all the examples, right? But I guess that will be a follow up change?
pabloem
left a comment
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.
What's the plan to run this script? Will it run in github actions/? Maybe it makes sense to add the main method so I get an idea of how the run looks like.
Overall this LGTM. Thanks. It would be nice to document a little more about this script in the README or in the pydoc for the main entry point.
Implement an example verification method;
Setup logger;
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username).[BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replaceBEAM-XXXwith the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
ValidatesRunnercompliance status (on master branch)Examples testing status on various runners
Post-Commit SDK/Transform Integration Tests Status (on master branch)
Pre-Commit Tests Status (on master branch)
See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.