flinkbot edited a comment on issue #9537: [hotfix][kinesis] Update emit record javadoc and don't count max watermark as timeout URL: https://github.com/apache/flink/pull/9537#issuecomment-525052373 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit fc93ac2188416b5b9a2c92fa0c4893d842e167ce (Tue Aug 27 21:12:42 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! <sub>Mention the bot in a comment to re-run the automated checks.</sub> ## Review Progress * ✅ 1. The [description] looks good. - Approved by @jgrier * ✅ 2. There is [consensus] that the contribution should go into to Flink. - Approved by @jgrier * ❓ 3. Needs [attention] from. * ✅ 4. The change fits into the overall [architecture]. - Approved by @jgrier * ✅ 5. Overall code [quality] is good. - Approved by @jgrier Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process.<details> The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required <summary>Bot commands</summary> The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier </details>
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
