agent data is now correctly requested#742
Draft
LuffyNoNika wants to merge 1 commit into
Draft
Conversation
Contributor
Author
|
@backend team, I tested with my local agent. Speed, cracks and Last Activity are rendered correctly, but I'm not sure about the backend logic behind "Time spent". I see in the JSON response "timeSpent": 12575, which means 3h+, but what I see rendered is different. Could anyone check that? |
Contributor
|
Iam not sure if I completely get it. but the timespent in the agent is the total timespent (on all tasks). for assigned agent we probably want only the timespent on this tasks, which needs a new backend helper for which this issue was created: hashtopolis/server#2297 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In task-agents-table.component, speed is prioritised by agent.chunk.speed. LAST_ACTIVITY uses task time (chunk.solveTime) and sues agent.LastTime as a fallback.
agents.datasource loads chunks separating taskId + agentId, builds chunkData for agent/task and assigns currentChunk.
Spec reflects new flow