NullPointerException when execution has no Job

[mveroone]

while running : rd executions deletebulk -p wproject> --older 28d -y i came upon this error :

Exception in thread "main" java.lang.NullPointerException
	at org.rundeck.client.api.model.Execution.getInfoMap(Execution.java:97)
	at org.rundeck.client.tool.commands.Executions.lambda$outputExecutionList$12(Executions.java:569)

This line in the code does a getJob().
But API reference (v23 or v27) speicifes that the fiels <job> is optional when querying for a list of executions.

that seems like a big bug and I can't understand how noone ever faced it before, although I couldn't find during my search

[mveroone]

Same when the execution is an ad-hoc command.

It seems weird for such a bug to exists for so long, am I doing something wrong ?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mveroone]

Funny as I have tested something, and it seems the client fails only if a format output is given (with -% "blabla %id xyz" . Without it, it won't try to get this non-existant id and will run correctly.

Also what the hell ? Issues automatically get labeled "wontfix" when noone from rundeck answers the issue ? It doesn't change the fact that the code is broken and needs fixing ?

(I understand that the actual open-source community lacks maintainers for a lot of projects, but this one has a company providing support, so it should have a minimal work done on OSS solutions...)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mveroone]

This is nuts. It's not because noone had time to acknowledge this bug that it is stale or deserves to be closed ><

[gschueler]

sorry, the stale bot is a bit aggressive!! I will remove or disable it, i don't like that behavior!! @mveroone