ciozi137

@drjdpowell I’ve tried to reproduce the error with the DVR but so far unsuccessful. 
 

when you have a chance can you review or comment latest pull request? Targets mostly libpq install, threading, etc. thanks

Hi James, I can't seem to reproduce the error now either. Basically when I added the classes to "PQ.lvlib" LabVIEW had trouble finding the correct cluster element in this unbundle by name. I suspect the same problem was happening behind the scenes during the PPL build (?).

I put "everything PQ" into "PQ.lvlib"* and I was able to build the test PPL. When I added the existing PQ classes to PQ.lvlib I had to fix an error inside "Connection Record.vi" unbundle to get the DVR. Perhaps that was the root of the problem before, but creating "PQ.lvlib" let me fix the problem before building.

*thanks to @Francois Normandin for the lvlib hint

Hi @DEPeter I was able to reproduce your error. It looks like Connection Record.vi is broken inside the lvlibp, but I can't see why yet.

thanks @drjdpowell 

21 hours ago, drjdpowell said:

Can you try forking the repo?  Then making a pull request?   I only have a free Bitbucket account and there is a limit on how many people I can add to my repos.

Sounds good. I will make pull requests as I work through the open issues. I'll stay with LV 2017 for now per updates from @Antoine Chalons

@drjdpowell bumping this topic to see how best I can contribute to the postgres repo

Hi @Jordan Kuehn I recently had the same issue with not being able to use SHA-256 passwords. I had to change them in my database to md5. I think James is right that the library needs to be updated to support SHA-256. See also here: https://www.vipm.io/posts/6b996996-5212-4191-aef4-ccaf68c93ae7/ (Perhaps someone can recruit Tom to help us out?)

@drjdpowell Can you give me pull or commit access to the repository and I can help coordinate fixing this and other issues?

Patrick