Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

5.2 breaking changes

See original GitHub issue

5.2 broke my tests all over the place, with changes not documented anywhere.

My test errors show that now when we call pg.connect, the library modifies the original connection object.

I think I’m just the first one running into this, and there will be more.

Issue Analytics

State:
Created 7 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

brianccommented, Jun 22, 2016

@sibedge - I will restore your access, but I’d like to go over a few things real quick hopefully we can agree to going forward.

Please be kind, patient, and grateful when people open up issues here. Open source can be scary and daunting to new folks, its definitely scary for me on some projects, and anything that would serve to alienate them or put people off of contributing, to me, is a major no no.

If I get too many issues opened up as duplicates or lacking code formatting that’s probably a bug in my documentation on how to submit issues & I should better document the process. I’ve had to moderate a few things you said as I felt they were a touch unfriendly to people who are looking for help or advice on what might be a very complex module for them to use, which is ultimately why I blocked the vitaly-t account.

I realize it can be frustrating if there are duplicate issues opened or questions about seemingly (to you) trivial issues, but if you’re feeling frustrated don’t worry about pitching in on those issues, I will eventually get to them as I have over the years. 😄

I definitely have appreciated your help here on reporting issues you’ve found through your pg-promise library, and overall node-postgres quality has improved because of you. I just cannot have people feeling rejected when they come to this repo for help. If you know the answer to their bug by all means pitch in, and I’m always happy to field bug requests and questions from you as well.

I do this in my spare time for free & sometimes my time is limited and its easier to just block than engage in trying to course correct - hopefully we’re on the same page now & we can continue to make FOSS better side by side! If you’d like I can provide feedback on issues or privately if you send me your email address next time instead of just removing access! ❤️

0reactions

vitaly-tcommented, Jun 22, 2016

@brianc Fresh contribution: #1060 😉