Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
lbfalvy11009112dYou're the only person who remembers fragments of what happened when you got the error, no one is in a better position to reproduce the issue than you. Once you can reliably reproduce it, other people can contribute.
lbfalvy11009112dBut yeah, sounds like a terrible mentor.
fruitfcker970112dTo me, it seems the "manager" fsck'd up and, to save face, blamed it on the new guy.
You just had your first taste. Be ready for more.
gitpush33117112dCheck APIs repo see if anything related to configurations has changed if you suspect something pull that repo with that change and disable what you suspect to see if it works again.
If this is a recent incident, go to commit history and check, if you figure it out keep it as a note and next time when this happens you know the fix to push
Although from your rant it doesn't look like code change but a server config, if this happens again take a screenshot or even better a screen recording and keep it aside, show it when no one believes you