Today I spent 1.5 - 2 hours trying to debug an issue I was having with PHPMailer -- or was it my foreach loop, or perhaps a misspelled variable, or...
For further actions, you may consider blocking this person and/or reporting abuse
A procedure I had running was going backwards, and I simply had two swap two parameters around and the whole the worked as intended.
Backwards? Wow, that's definitely a new one on me.
It was a stupid mistake by myself. Instead of it working out like 4 - 3 = 1, it was doing 3 - 4 = -1.
But it took me roughly 3 months to figure out it was a problem, i.e. when it went into production aha. My testing was showing correct values, but that's because I was faking the math correctly.
It was a learning experience :)
That reminds me of that post about things we always google. One of mine always seems to be the param order for the callback passed to
Array.prototype.map().Param order can definitely get you. But I'm now glad to have hints in both Atom and VS Code about what the next param is expected to be -- at least if the function is defined in the code, or is a native member of the language.
I don’t have a nice pneumonic to help but I realized one day that
map,forEach, and a few others all have the same callback Parma order ofvalue,index,arrayI kept flipping
indexandvalue(and forgetting aboutarray, honestly). But that order does make a lot more sense since theindexandarrayaren't needed for everything.Thanks for mentioning that by the way. I guess they would've done that for consistency and ease of use.
We had sidekiq jobs setup to send out emails. We made a few changes to the template one day and then it started.
Some outgoing email had the new email template and some were still using the old template. This baffled everyone on the team, QAs were frustrated too since they could not reproduce it consistently in the QA env. This was supposed to be rolled out the next day, hence a sense of urgency too.
BUG
We had recently setup a new sidekiq jobs server and did not decommission the old one (we planned to use it for another env). The new code was deployed to the new servers. Whenever the old server would pick the job it would send out an email with the old template causing the confusion.
I was writing a unit test for
POSTrequests on an api endpoint and was wondering why no data was being returned. I tried logging the request object and the data expected was being sent back; it was a wild situation that I almost threw the towel in. Apparently, the endpoint was responding with a204status code that literally meantNO CONTENT. That's a funny TIL moment for me.Ok, I ended up deleting a sentence because I couldn't get
strikethroughto work. Turns out I was using the wrong character. 😅Oh yeah, those are my favorites (wrong letter case).