Closed TechWithTy closed 4 weeks ago
Hello @TechWithTy! Sorry for the delay. We're only supporting Node.JS 18+, please let us know if the issue is solved by upgrading NodeJS version from 14 to 18.
We were actually using node 20v Somehting sorry for the typo
I have the same issue and I am on v18.
Can we reopen this @dqbd
I noticed that it doesn't generate this error inside every function wrapped inside the traceable() function. If I have more debugging information I'll let you know. Both functions had at least a chain consisting of a prompt, model, parser.
@guidorietbroek Were you able to fix the issue?
No sorry.
Issue you'd like to raise.
Issue Description Description I am encountering an issue with the getCurrentRunTree method in the langsmith library. The error message indicates that the method cannot get the current run tree and suggests that the method is not being called within a traceable function. Despite following the documentation and ensuring that my function calls are within the traceable context, the error persists.
Error Message less
Steps to Reproduce Set up a project with the langsmith library. Implement the following code snippet to trace function calls: javascript
Run the script. Expected Behavior The getCurrentRunTree method should return the current run tree without errors when called within a traceable function.
Actual Behavior The getCurrentRunTree method throws an error stating that it could not get the current run tree.
Environment OS: Windows 10 Node.js Version: 20.~ langsmith Version: x.y.z (Please specify the exact version you're using)
Suggestion:
No response