Issue connecting in Deno via SSL
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8.7k
- Forks
- 374
- Avg merge
- 11d 16h
- Merged PRs (30d)
- 1
Description
Someone already opened up a bug in the Deno repo here:
https://github.com/denoland/deno/issues/28526
I'm having the same problem. However, am able to connect to the same database with PostgreJS, which doesn't even advertise Deno support.
So, I bet the problem isn't in Deno, but may be in some Deno-specific TLS-handling inside postgres.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the SSL connection failure in Deno and read the linked Deno issue #28526 for the related report. Compare the behavior with PostgreJS, then trace postgres's Deno-specific TLS handling; done means identifying and resolving the connection failure with a regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno, javascript, postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100