Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: tracing provider edits don't reflect #654

Open
bderenzi opened this issue Sep 2, 2024 · 0 comments
Open

bug: tracing provider edits don't reflect #654

bderenzi opened this issue Sep 2, 2024 · 0 comments

Comments

@bderenzi
Copy link
Collaborator

bderenzi commented Sep 2, 2024

Here's what I did:

  1. Created a new project on langfuse with a new API key
  2. Created a new tracing provider and used an old langfuse API key
  3. Connected my experiment to the new tracing provider, tested, realized it was sending new traces to the old project.
  4. Edited the new tracing provider on OCS to use the new API key
  5. Still sent traces to the old project space. Double checked. Triple checked. Still sent to the old project space
  6. Made a new new tracing provider with the new API key, updated the experiment to use the new new tracing provider. Everything worked.

The error is that at step 4 it should have started sending stuff to the new provider. Is there some langfuse object that is instantiated in memory that doesn't get updated when we edit the provider?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant