bug with no steps to reproduce

logs show null pointer exception but doesn't have a stack trace to point a bad line of code

fuck jersey and jettycounts

Oh wow... I have one seen something similar. A tester had been reporting issues w/ solely the 'Bug Title' field filled in. Just a one-liner to tell people what the issue is about. No Description, no Steps To Reproduce. Just wow...

Anyway, I certainly don't envy you.

When I see one of these I just move it back into the test column 😅 (with a no repro comment)

@BordedDev You could add a barely known acronym 'NMI', too.

/* Need More Information. */

Not to light a fire but don't you test for NULL / Nil before using memory that was dynamically allocated... or are you using "Fluent Interface" design pattern aka "method chaining" like this:

EmailBuilder()

.setFrom("sender@example.com")

.setTo("recipient@example.com")

.setSubject("Meeting Reminder")

.setBody("Don't forget our meeting at 3 PM.")

.send();

In which case... well... you need to perform 0000 0010 acts of attrition and 0000 0100 Hail Marys.

fucking graphql syntax of consumer was wrong , so it was sending in null

certain thing in java has log optimization where it drops repeated identical stack traces so it was the sparse stack trace