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

Explore support for detecting duplicate issues #41292

Closed
chrmarti opened this issue Jan 8, 2018 · 1 comment
Closed

Explore support for detecting duplicate issues #41292

chrmarti opened this issue Jan 8, 2018 · 1 comment
Assignees
Labels
engineering VS Code - Build / issue tracking / etc. feature-request Request for new features or functionality plan-item VS Code - planned item for upcoming
Milestone

Comments

@chrmarti
Copy link
Contributor

chrmarti commented Jan 8, 2018

Exploration of existing ML approaches is needed.

Since we would eventually want to know the existing duplicate graph, that could also serve as a middle-ground from where we can continue with ML approaches or simply listing recent duplicate target issues.

@chrmarti chrmarti added engineering VS Code - Build / issue tracking / etc. feature-request Request for new features or functionality plan-item VS Code - planned item for upcoming labels Jan 8, 2018
@chrmarti chrmarti self-assigned this Jan 8, 2018
@chrmarti chrmarti added this to the December 2017/January 2018 milestone Jan 8, 2018
@chrmarti
Copy link
Contributor Author

Early testing with the Python package Gensim suggested that in 25% of cases of existing duplicates there would be the original (or another duplicate) among the first 5 candidates. Further testing showed that the hit rate drops quickly with the number of issues considered as candidates, more investigation in this will be needed for a more solid estimate. E.g., ignoring all issues closed for the current stable release might reduce the number of issues to consider.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
engineering VS Code - Build / issue tracking / etc. feature-request Request for new features or functionality plan-item VS Code - planned item for upcoming
Projects
None yet
Development

No branches or pull requests

1 participant