Langsmith hub - unable to retrieve my prompts

[KeenanFernandes2000]

Checked other resources

• I added a very descriptive title to this question.
• I searched the LangChain documentation with the integrated search.
• I used the GitHub search to find a similar question and didn't find it.

Commit to Help

• I commit to help with one of those options 👆

Example Code

Code

import { pull } from "langchain/hub";

const prompt = await pull<ChatPromptTemplate>("thecodingbarista/superagent");


Error
node:internal/deps/undici/undici:11576
    Error.captureStackTrace(err, this);
          ^

TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11576:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Client.listCommits (file:///C:/Users/Keenan/Desktop/Work/PotentialLive/node_modules/langchainhub/dist/client.js:160:21)
    at async Client._getLatestCommitHash (file:///C:/Users/Keenan/Desktop/Work/PotentialLive/node_modules/langchainhub/dist/client.js:210:29)
    at async Client.pull (file:///C:/Users/Keenan/Desktop/Work/PotentialLive/node_modules/langchainhub/dist/client.js:288:26)
    at async pull (file:///C:/Users/Keenan/Desktop/Work/PotentialLive/node_modules/langchain/dist/hub.js:23:20)
    at async executeCommand (file:///C:/Users/Keenan/Desktop/Work/PotentialLive/app/docgenerator.js:232:20)
    at async file:///C:/Users/Keenan/Desktop/Work/PotentialLive/app/agent.js:331:23 {
  cause: Error: unable to verify the first certificate
      at TLSSocket.onConnectSecure (node:_tls_wrap:1600:34)
      at TLSSocket.emit (node:events:517:28)
      at TLSSocket.emit (node:domain:489:12)
      at TLSSocket._finishInit (node:_tls_wrap:1017:8)
      at ssl.onhandshakedone (node:_tls_wrap:803:12) {
    code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'
  }
}

Description

I'm trying to retrieve my prompt from langsmith like I've done in the past, however now none of my prompts work and throws (UNABLE_TO_VERIFY_LEAF_SIGNATURE) error. I do not know what has changed since we have paused development with langchain, now that we are doing some more development I ran into this issue.

System Info

Node.js v18.18.0
[email protected]
[email protected]

[dosubot[bot]]

The UNABLE_TO_VERIFY_LEAF_SIGNATURE error indicates an issue with SSL certificate verification in your Node.js environment. This can occur if Node.js can't verify the server's SSL certificate, often seen with self-signed certificates or incorrect certificate chains.

To bypass this error for development purposes, you can disable SSL certificate validation by setting process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0" in your Node.js script. This should be done with caution and only in a trusted environment, as it disables SSL/TLS certificate verification for all outgoing HTTPS connections, potentially exposing your application to security risks.

process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";

Ensure to remove or comment out this line before moving to production to maintain the security of your application.

Regarding the pull function from langchain/hub, it's designed to retrieve prompts from Langsmith. It requires specifying the repository name and an optional commit hash. The function returns a promise with the loaded prompt. For detailed usage, refer to the langchain/src/hub.ts in the Langchain documentation.

If the issue persists or you need further assistance, providing more details about your setup and the steps you've taken can help in offering more specific advice.

Details

Sources

• langchain/src/prompts/load.ts
• langchain/src/hub.ts
• langchain/src/prompts/index.ts
• langchain/src/chains/question_answering/refine_prompts.ts
• langchain/src/chains/question_answering/map_reduce_prompts.ts
• langchain/src/output_parsers/prompts.ts
• langchain/src/prompts/few_shot.ts
• langchain/package.json

About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

[jkaos92]

@KeenanFernandes2000
Be carefull with process.env.NODE_TLS_REJECT_UNAUTHORIZED to 0, don't use it in production. Use it only in a development/debug or test environment.

By any chance you have ESET Antivirus on that machine? If so, an update of ESET broke SSL/TLS for node

[KeenanFernandes2000]

@jkaos92 No way 😮😮😮, I do have ESET on the machine. I will try it out after disabling ESET. How did you figure out that this would cause the issue.

[jkaos92]

@KeenanFernandes2000 If you have ESET, for sure this is the problem. Untill they fix, i suggest to disable SSL check on ESET only on Node. Don't disable the whole ESET features (just follow the bullet points in the stackoverflow link above).
It was definitely a strange discovery!

[KeenanFernandes2000]

@jkaos92 I disabled it and it worked, thanks a lot. It didn't even cross my mind that the antivirus would be causing the issue.

[jkaos92]

@KeenanFernandes2000 glad it worked :)