removed illegal partition assign from input.py

[rgnf]

Die für einen subscription based consumer illegale Operation "assign(topic_partition)" aus _lost_callback entfernt.
Ggf. muss noch irgendwas aufgeräumt werden.
Da diese Partitionen potentiell bereits von einem anderen Consumer bearbeitet werden, passt "batch_finished" nicht. Das könnte zu Chaos bei den Offsets führen.
Ob ein "output_connector._write_backlog" Chaos auf der Output Seite auslösen kann, kann ich nicht beurteilen.

[ekneg54]

Thank you for your PR. The language in this project is English. So please write only in English.
Please read our Contributing Guidelines https://github.com/fkie-cad/Logprep/blob/main/CONTRIBUTING.md and do what is suggested there to contribute to this project.

Until that happen I revert this PR into a draft.

[rgnf]

For subscription based consumers it is not allowed/iilegal to use "assign(topic_partition)". Therefore I removed the offending code from _lost_callback.
Maybe there is need for additional cleanup.
As the lost partitions could be already used by other consumers, a call to batch_finished could cause chaos.
I do not know if calling output_connector._write_backlog could cause chaos on the output part.

[rgnf]

Updated changelog provided in PR #674 .
No need to update documenation
No test provided, as it is unknown how to reproduce "lost partition" event for testing.

[ekneg54]

could you add all means depending this change in this pull request please? It is not necessary to open further PRs.
Please fix the failing unittests and adhere to black formatting in your change. Note that the failing containerbuild is not fixable by you.

[rgnf]

Was some fiddeling, but now this PR includes also the CHANGELOG.md.
As the changes were made directly in the Github Web UI, I do not know how to "black format" the changes.
Where can I see which Unit Tests fail as result of the change?
I do not believe that this part of the code is covered in any test. Otherwise existing tests would have pointed to this issue long ago.

[ekneg54]

i triggered the pipeline again. have a look in the failing unittests and in the code quality job. there you are able to see, what is failing

[rgnf]

Done, but I do not understand what issue it is complaining about.
If I understand the report correctly, it wants to replace a blank line with a blank line. Can the reporting configured in a way, to show "non printable characters" like newline, carriage return, tab, blanks?
I guess, the Github editor fooled me somehow by unintentionally identation.

[rgnf]

Removed identation on blank line.

[rgnf]

Now the linter complains about code I did not touch.

[ekneg54]

close because will be addressed by #678