PR closed without merging first

[formacube]

My PR has been closed without being merged.

My code is plenty of patches since begining of september because I'm waiting for you to validate the code.
You make me wait 6 months to change the formating of the code while it would take you less than 5 minutes to do it.

I have to wait for 6 month ...
and then you decide to kill everything because you have another idea ... that is not even yet implemented !

Please first merge my PR, so that I can have some code that works correctly and get rid of the patches.
Then when you have the time, there is no problem to implement your new idea.

But at least in the meantime, I can have a code that work, without monkey patch.
and also, it will be easy to test if your new idea is still functional for tasks that takes few days or few weeks to execute

[formacube]

it does not really change anything for you.
For you there is no drawbacks merging this PR which is now ok and formated according to your standards.

But for me it changes a lot of things

[formacube]

I couldn't react earlier as I was ill with covid.
I would appreciate if you stop closing all the issues and PRs before you get an answer. You can at least wait one or two weeks.

This is not very constructive, especially with all the efforts I put in it.

[jedie]

I'm really sorry about how it all happend. It went very unhappily for you.
The whole thing is due to the fact that I had too little time for the project in the past. I hope that this will change.

I couldn't react earlier as I was ill with covid.

I hope you have gotten over it well!

Please first merge my PR, so that I can have some code that works correctly and get rid of the patches.

OK, i will do this.
But you added cumulate2parents in #44 to pervert spamming the database full, isn't it? But my refactor will remove this, because then the cache is used and it's useless, isn't it?
So in the end there is a release with cumulate2parents and a later release will deprecate this again.

Is this okay for you?