Dustin N.

in which case you can definitely get a conflict

if it's truly a new database I am confused as to why that would trigger a new mutation, but are you running two applications with separate tables all in the same database?

hmmm this is using postgres?

hi Ashwin G. did you recently try to update the phoenix version? I'm curious about the circumstances around a migration being run

you can check with:

import phoenix.client

print(phoenix.client.__version__)

hi Andrew S. we'll try and do a better job of informing users if their server/client version are out of sync. To use the splits feature try to make sure your client version is >=1.22.0

cc Roger Y.

It's currently a priority of ours to improve the collector performance

hi Andrei L. we do not currently have official benchmarking scripts but this depends on a number of factors, such as database performance and the topology of your input traces

hi Valentin G. can you try and instruct the model to ensure that it makes a cool call in the prompt?