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

Invalid conflict links in quality reports for tasks with honeypots #8628

Open
2 tasks done
zhiltsov-max opened this issue Oct 31, 2024 · 0 comments
Open
2 tasks done
Labels
bug Something isn't working server

Comments

@zhiltsov-max
Copy link
Contributor

zhiltsov-max commented Oct 31, 2024

Actions before raising this issue

  • I searched the existing issues and did not find anything similar.
  • I read/searched the docs

Steps to Reproduce

  1. Create a task with honeypots
  2. Add some GT annotations
  3. Compute quality for the task
  4. Try to open conflict links from job reports

It seems like links use frame indices from jobs instead of task frame numbers. For instance, there can be a link with frame id 5 in a job starting from the frame 20.

Expected Behavior

No response

Possible Solution

No response

Context

No response

Environment

@zhiltsov-max zhiltsov-max added bug Something isn't working server labels Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working server
Projects
None yet
Development

No branches or pull requests

1 participant