[
https://issues.apache.org/jira/browse/FLINK-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15660428#comment-15660428
]
ASF GitHub Bot commented on FLINK-4521:
---
Github user mushketyk commented on the issu
Github user mushketyk commented on the issue:
https://github.com/apache/flink/pull/2431
Hi @iampeter
Thank you for your review.
Do I need to rebase this PR to merge it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
Github user mushketyk commented on a diff in the pull request:
https://github.com/apache/flink/pull/2457#discussion_r87701980
--- Diff:
flink-runtime-web/web-dashboard/app/scripts/modules/jobs/jobs.dir.coffee ---
@@ -281,7 +281,8 @@ angular.module('flinkApp')
# Otherwi
[
https://issues.apache.org/jira/browse/FLINK-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15660425#comment-15660425
]
ASF GitHub Bot commented on FLINK-3680:
---
Github user mushketyk commented on a diff i
[
https://issues.apache.org/jira/browse/FLINK-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15660423#comment-15660423
]
ASF GitHub Bot commented on FLINK-3719:
---
Github user mushketyk commented on a diff i
Github user mushketyk commented on a diff in the pull request:
https://github.com/apache/flink/pull/2467#discussion_r87701960
--- Diff:
flink-runtime-web/web-dashboard/app/scripts/modules/jobs/jobs.dir.coffee ---
@@ -168,14 +168,15 @@ angular.module('flinkApp')
return
[
https://issues.apache.org/jira/browse/FLINK-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15660184#comment-15660184
]
ASF GitHub Bot commented on FLINK-4913:
---
GitHub user uce opened a pull request:
GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/2795
Revert "[FLINK-4913][yarn] include user jars in system class loader"
In general, a very good fix imo, but it is part of RC1 for 1.1.4. It might
be better to exclude it for the bug fix release since it c
GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/2794
[backport] [FLINK-5057] [task] Pick cancellation timeout from task manager
config
Backport of #2793 with no major changes. This should be merged for 1.1.4
(requiring a new RC).
You can merge this pull
[
https://issues.apache.org/jira/browse/FLINK-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15660151#comment-15660151
]
ASF GitHub Bot commented on FLINK-5057:
---
GitHub user uce opened a pull request:
[
https://issues.apache.org/jira/browse/FLINK-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15660148#comment-15660148
]
ASF GitHub Bot commented on FLINK-5057:
---
GitHub user uce opened a pull request:
GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/2793
[FLINK-5057] [task] Pick cancellation timeout from task manager config
This was previously picked from the wrong config (the Task config). There
was a test for it, but it was also testing the task confi
Ufuk Celebi created FLINK-5057:
--
Summary: Cancellation timeouts are picked from wrong config
Key: FLINK-5057
URL: https://issues.apache.org/jira/browse/FLINK-5057
Project: Flink
Issue Type: Bug
[
https://issues.apache.org/jira/browse/FLINK-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Mushketyk reassigned FLINK-4649:
-
Assignee: Ivan Mushketyk
> Implement bipartite graph metrics
> --
[
https://issues.apache.org/jira/browse/FLINK-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659963#comment-15659963
]
Ivan Mushketyk commented on FLINK-4647:
---
Implemented here:
https://github.com/mushke
[
https://issues.apache.org/jira/browse/FLINK-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659734#comment-15659734
]
ASF GitHub Bot commented on FLINK-4900:
---
Github user Makman2 commented on the issue:
Github user Makman2 commented on the issue:
https://github.com/apache/flink/pull/2703
Btw shall I use "fixup commits" or fix the commit directly? I prefer the
second method, I'm not a real fan of non-atomic commits and commits like "Oops,
fixing mistake from before". Though I've read
GitHub user sunjincheng121 opened a pull request:
https://github.com/apache/flink/pull/2792
Flink 4937 pr
Thanks for contributing to Apache Flink. Before you open your pull request,
please take the following check list into consideration.
If your changes take all of the items in
[
https://issues.apache.org/jira/browse/FLINK-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659666#comment-15659666
]
ASF GitHub Bot commented on FLINK-4937:
---
GitHub user sunjincheng121 opened a pull re
[
https://issues.apache.org/jira/browse/FLINK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659436#comment-15659436
]
Philipp von dem Bussche commented on FLINK-2821:
[~mxm] sorry for my late
20 matches
Mail list logo
