Re: Last sprint to finish line: Replace EasyMock/Powermock with Mockito

[Christo Lolov]

Hello,

I have not been able to make a lot of progress on the Mockito migration myself, 
but Yash and Divij opened and merged a PR each.

The following PRs have made it into trunk:

https://github.com/apache/kafka/pull/12615
https://github.com/apache/kafka/pull/12677
https://github.com/apache/kafka/pull/12492

Thank you to Yash and Divij for authoring them and to Chris and Bruno for the 
reviews!

The following PRs are in progress:

In need of reviewer attention - RA
In need of author attention - AA

https://github.com/apache/kafka/pull/12409 (RA)
https://github.com/apache/kafka/pull/12418 (AA)
https://github.com/apache/kafka/pull/12465 (RA)
https://github.com/apache/kafka/pull/12505 (AA)
https://github.com/apache/kafka/pull/12524 (RA)
https://github.com/apache/kafka/pull/12527 (RA)
https://github.com/apache/kafka/pull/12607 (AA)

A summary of the Mockito migration:

https://issues.apache.org/jira/browse/KAFKA-14133 
 - a little under 1/3 of all 
classes using EasyMock have been moved and merged; a bit over 1/3 are in PRs 
and around 1/3 are remaining.

https://issues.apache.org/jira/browse/KAFKA-14132 
 - a little under 1/3 of all 
classes using PowerMock have been moved and merged; a bit over 2/3 are 
remaining.

Best,
Christo

Request for contributor permissions

[Christopher Razavian]

Hello,

I'd like to request for contributor permissions. JIRA ID: pooya72. Thank
you.

Regards,

Chris

[jira] [Resolved] (KAFKA-14043) The latest status of the task is overwritten by the old status

[doupengwei (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-14043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

doupengwei resolved KAFKA-14043.

Resolution: Not A Bug

> The latest status of the task is overwritten by the old status
> --
>
> Key: KAFKA-14043
> URL: https://issues.apache.org/jira/browse/KAFKA-14043
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Affects Versions: 2.4.0
> Environment: Centos 7.6
> kafka  2.4.0
>Reporter: doupengwei
>Priority: Major
>
> Kafka version : 2.4.0
> connect.protocol : compatible
> In kafka connect cluster, if  one node  faced net work issue,  then will 
> caused worker try to stop connector and task which running on this node. and 
> due to net work issue. it will stop failed and throw exception, then worker 
> process will try to update task or connector status, producer will retry 
> indefinitely until successfully sent. but due to net work issue, the new 
> assignment have  performed on the other connect node. after net work recover, 
> old task status will cover latest status.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)