Skip to content

#109 pool release fix #197

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Feb 21, 2017
Merged

Conversation

zbarbuto
Copy link
Contributor

Description

A combination of PR #146 which fixes #109 and a switch from explicitly calling connection.release to using the built-in done callback provided by pg to release connection (see here)

Related issues

Checklist

  • New tests added or existing tests modified to cover all changes
  • Code conforms with the style
    guide

@slnode
Copy link

slnode commented Jan 10, 2017

Can one of the admins verify this patch? To accept patch and trigger a build add comment ".ok\W+to\W+test."

@slnode
Copy link

slnode commented Jan 10, 2017

Can one of the admins verify this patch?

2 similar comments
@slnode
Copy link

slnode commented Jan 10, 2017

Can one of the admins verify this patch?

@slnode
Copy link

slnode commented Jan 10, 2017

Can one of the admins verify this patch?

@zbarbuto
Copy link
Contributor Author

@jannyHou @superkhau This has been sitting here for a while and I haven't received any feedback. I noticed the test status is still waiting. #109 is still an issue for us if we don't use this forked branch.

@jannyHou
Copy link
Contributor

@slnode test please

@jannyHou
Copy link
Contributor

jannyHou commented Feb 16, 2017

@zbarbuto Thank you for the pr, while I am currently working on some other high priority tasks, sorry for the delay of review. I triggered a test, will take a look ASAP.

@superkhau
Copy link
Contributor

@zbarbuto Can you add a test to verify your results?

@raymondfeng
Copy link
Contributor

LGTM

@superkhau
Copy link
Contributor

@zbarbuto Can you rebase this PR also? I think the two failures are unrelated -- something to do with forceId -- @jannyHou please confirm before landing.

@jannyHou
Copy link
Contributor

@superkhau good catch.
@zbarbuto Please rebase your code :) I believe the new checked in pr will get those two failures pass.

@zbarbuto zbarbuto force-pushed the #109-pool-release-fix branch from df817ac to 364dfaa Compare February 16, 2017 22:20
@zbarbuto
Copy link
Contributor Author

Have rebased but can't seem to get the transaction tests to run on my local machine (Uncaught Error: getaddrinfo ENOTFOUND undefined undefined:5432). The README file says "Ask a core developer for instructions on how to set up test server credentials on your machine" - any clues?

@superkhau
Copy link
Contributor

@zbarbuto Those instructions need updating, you should be able to override configs now for local testing via env vars. See https://github.com/strongloop/loopback-connector-postgresql/blob/master/test/init.js#L21.

cc @jannyHou @crandmck We should update that README text

@zbarbuto
Copy link
Contributor Author

@superkhau Ah yes, is working now, also need to use CI=true for some reason to allow those settings to be read. Adding a test case now.

@zbarbuto
Copy link
Contributor Author

zbarbuto commented Feb 16, 2017

@superkhau @jannyHou Test added which fails on current master branch but passes with this PR 😀

@zbarbuto
Copy link
Contributor Author

@superkhau Have made #214 to fix that README information about testing too.

@superkhau
Copy link
Contributor

@rmg Hanging here too.

@jannyHou
Copy link
Contributor

@slnode test please

@jannyHou
Copy link
Contributor

@zbarbuto Now all test pass, please rebase the code and I think it will be ready to land 🚢

cc @superkhau

@zbarbuto zbarbuto force-pushed the #109-pool-release-fix branch from 4eb828c to 1fe639b Compare February 17, 2017 21:11
@zbarbuto
Copy link
Contributor Author

Rebased. Thanks.

@zbarbuto
Copy link
Contributor Author

Also would be good to get a release out of this sooner rather than later as it's a rather critical issue with transactions not being able to do more than a few at a time.

@zbarbuto
Copy link
Contributor Author

@jannyHou @superkhau

@jannyHou
Copy link
Contributor

@slnode test please

@jannyHou
Copy link
Contributor

jannyHou commented Feb 21, 2017

@zbarbuto After rebase the pr is all good now and we will make a new release after checking in it.

Sorry for the delay of trigging testing :( could you do a rebase again? I will keep an eye on this issue and run test immediately after your rebase. Thank you.

@zbarbuto zbarbuto force-pushed the #109-pool-release-fix branch from 1fe639b to b618133 Compare February 21, 2017 22:22
@zbarbuto
Copy link
Contributor Author

@jannyHou Done

@jannyHou
Copy link
Contributor

@slnode test please

@jannyHou jannyHou merged commit 679fb05 into loopbackio:master Feb 21, 2017
@cadesalaberry
Copy link

Cannot wait for the release!

@jannyHou
Copy link
Contributor

@cadesalaberry @zbarbuto released as 2.8.0. Please check. Thanks

@STRML STRML mentioned this pull request Sep 12, 2017
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TypeError: Object [object Object] has no method 'release'
7 participants