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

ML based Labeling Bot #37

Open
goern opened this issue Jun 2, 2020 · 5 comments
Open

ML based Labeling Bot #37

goern opened this issue Jun 2, 2020 · 5 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@goern
Copy link
Member

goern commented Jun 2, 2020

Is your feature request related to a problem? Please describe.
This bot will use a back end service to predict a set of labels for a given issue or pull request.

Describe the solution you'd like
one back end service should expose a ml model for inference

Describe alternatives you've considered
n/a

Additional context
n/a

@harshad16
Copy link
Member

Text base analysis of the issue's body content could be used for the relevant label addition.

@goern
Copy link
Member Author

goern commented Jun 3, 2020

@GiorgosKarantonis
Copy link

GiorgosKarantonis commented Jun 3, 2020

I've been working on the laptop and the bootcamp so far... I'll make sure to have some suggestions by tomorrow!

EDIT: Some pretty straightforward issues I see so far have to do with the language modeling and the overall network structure. Tomorrow I'll take a look on the dataset as well and see how we can augment it.

  • Regarding the language modeling, in the notebook they use the Keras Embedding layer which to me doesn't look like a very good option, especially for the dataset we deal with, since posted issues are usually small in size with high variance.

  • Regarding the network structure, we could try increasing the number of recurrent layers (depending on the size of the dataset we'll end up using) and test it with LSTMs too just for completeness.

Again, these are just straightforward suggestions and if they don't give good results I could look for a good paper to implement or come up with something more complex.

@sesheta sesheta added kind/feature Categorizes issue or PR as related to a new feature. and removed enhancement labels Feb 9, 2021
@sesheta
Copy link
Contributor

sesheta commented Jul 3, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 3, 2021
@harshad16
Copy link
Member

/lifecycle frozen
this project would be also reviewed for this use case https://github.com/aicoe-aiops/github-labeler

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

4 participants