You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Tracing doesn't work when port is manually entered through px.launch_app
The code below works fine when port is not manually entered (default=6006)
To Reproduce
Steps to reproduce the behavior:
importphoenixaspxfromdotenvimportload_dotenv, find_dotenvfromlangchain.chat_modelsimportChatOpenAIfromlangchain.promptsimportChatPromptTemplatefromlangchain.chainsimportLLMChainfromphoenix.trace.langchainimportOpenInferenceTracer, LangChainInstrumentorload_dotenv(find_dotenv())
session=px.launch_app(port=6007) # HIGHLIGHTtracer=OpenInferenceTracer()
LangChainInstrumentor(tracer).instrument()
llm=ChatOpenAI(temperature=0.9, model="gpt-3.5-turbo")
prompt=ChatPromptTemplate.from_template(
"What is the best name to describe \ a company that makes {product}?"
)
chain=LLMChain(llm=llm, prompt=prompt)
product="Queen Size Sheet Set"chain.run(product)
session.url
after running the above code, go to the url provided by session.url
Expected behavior
I would expect trace to exist for the query, prompt, and output
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
OS: Apple M1 (macOS Ventura 13.5.1)
Browser: Chrome
pheonix version: 2.4.1
langchain version: 0.1.0
The text was updated successfully, but these errors were encountered:
Describe the bug
Tracing doesn't work when port is manually entered through
px.launch_app
The code below works fine when port is not manually entered (default=6006)
To Reproduce
Steps to reproduce the behavior:
after running the above code, go to the url provided by
session.url
Expected behavior
I would expect trace to exist for the query, prompt, and output
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: