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
Sort by latency in ascending order and scroll to the second page. One item should appear twice as the last item of the first page and the first item of the second page.
Alternatively, make the following GraphQL request:
query TracesTableQuery(
$after: String = null
$filterCondition: String = null
$first: Int = 100
$sort: SpanSort = {col: startTime, dir: desc}
$timeRange: TimeRange
$id: GlobalID!
) {
node(id: $id) {
__typename
...TracesTable_spans_1XEuU
__isNode: __typename
id
}
}
fragment SpanColumnSelector_evaluations on Project {
spanEvaluationNames
}
fragment TracesTable_spans_1XEuU on Project {
...SpanColumnSelector_evaluations
rootSpans: spans(first: $first, after: $after, sort: $sort, rootSpansOnly: true, filterCondition: $filterCondition, timeRange: $timeRange) {
edges {
rootSpan: node {
spanKind
name
metadata
statusCode: propagatedStatusCode
startTime
latencyMs
cumulativeTokenCountTotal
cumulativeTokenCountPrompt
cumulativeTokenCountCompletion
parentId
input {
value
}
output {
value
}
context {
spanId
traceId
}
spanEvaluations {
name
label
score
}
documentRetrievalMetrics {
evaluationName
ndcg
precision
hit
}
descendants {
spanKind
name
statusCode: propagatedStatusCode
startTime
latencyMs
parentId
cumulativeTokenCountTotal: tokenCountTotal
cumulativeTokenCountPrompt: tokenCountPrompt
cumulativeTokenCountCompletion: tokenCountCompletion
input {
value
}
output {
value
}
context {
spanId
traceId
}
spanEvaluations {
name
label
score
}
documentRetrievalMetrics {
evaluationName
ndcg
precision
hit
}
}
}
cursor
node {
__typename
}
}
pageInfo {
endCursor
hasNextPage
}
}
id
}
Spans can appear more than once when paginating, probably due to a floating point rounding issue.
To reproduce:
pagination
branch.with variables
The rowid of the cursor and the rowid of the first record in the response is 671.
The text was updated successfully, but these errors were encountered: