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

(frontend)[Age 1178]Wrong latency shown in table and drawer #2157

Conversation

bekossy
Copy link
Member

@bekossy bekossy commented Oct 31, 2024

Closes AGE-1178

@bekossy bekossy requested a review from jp-agenta October 31, 2024 08:22
Copy link

vercel bot commented Oct 31, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
agenta ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 2, 2024 9:50pm
agenta-documentation ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 2, 2024 9:50pm

Copy link
Member

@mmabrouk mmabrouk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bekossy the latency is still wrong. Now it's showing that the LLM call took 3ms while the response is 3847.647ms. It should show 3.84s instead

Copy link
Member

@mmabrouk mmabrouk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @bekossy lgtm

@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Nov 3, 2024
@mmabrouk mmabrouk merged commit 3bc8152 into feature/observability-checkpoint-2 Nov 3, 2024
6 checks passed
@mmabrouk mmabrouk deleted the AGE-1178/wrong-latency-shown-in-table-and-drawer branch November 3, 2024 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Frontend lgtm This PR has been approved by a maintainer size:S This PR changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants