-
Notifications
You must be signed in to change notification settings - Fork 11
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
/annotate
#67
Comments
Note The following contributors may be suitable for this task: shiv810
Keyrxng
|
/ask I wonder if there is a more suitable command name instead of |
! An error occurred |
! No answer from OpenAI |
/help |
It's interesting I think because the original plan for shiv's addition to my V1
It seems to me foo or yourself should have been about to just use the So the only truly new functionality here is the ability to annotate a particular comment with the |
/start |
Tip
|
|
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Task | 1 | 200 |
Conversation Incentives
Comment | Formatting | Relevance | Priority | Reward |
---|
[ 2.368 WXDAI ]
@Keyrxng
Contributions Overview
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 1 | 2.368 |
Conversation Incentives
Comment | Formatting | Relevance | Priority | Reward |
---|---|---|---|---|
It's interesting I think because the original plan for shiv's ad… | 5.93content: content: p: score: 0 elementCount: 5 result: 0 regex: wordCount: 122 wordValue: 0.1 result: 5.93 | 0.8 | 2 | 2.368 |
[ 146.79 WXDAI ]
@0x4007
Contributions Overview
View | Contribution | Count | Reward |
---|---|---|---|
Review | Base Review for #70 | 1 | 25 |
Review | Code Review | 3 | 55.82 |
Issue | Specification | 1 | 23.98 |
Review | Comment | 26 | 41.99 |
Review Details for #70
Changes | Priority | Reward |
---|---|---|
+261 -6 | 2 | 5.34 |
+2489 -19 | 2 | 50.16 |
+4 -12 | 2 | 0.32 |
Conversation Incentives
Comment | Formatting | Relevance | Priority | Reward |
---|---|---|---|---|
There are situations where we write about certain issues that we… | 11.99content: content: p: score: 0 elementCount: 3 a: score: 5 elementCount: 1 result: 5 regex: wordCount: 148 wordValue: 0.1 result: 6.99 | 1 | 2 | 23.98 |
My review status doesn't appear to be approved so approving one … | 1.54content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 25 wordValue: 0.1 result: 1.54 | 0.2 | 2 | 0.616 |
Wouldn't it make more sense to have a null comment ID | 0.83content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 12 wordValue: 0.1 result: 0.83 | 0.7 | 2 | 1.162 |
This seems problematic if a comment contains normal footnotes. … | 3.34content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 62 wordValue: 0.1 result: 3.34 | 0.9 | 2 | 6.012 |
Maybe null again. Empty strings seem to be LLM code smell | 0.77content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 11 wordValue: 0.1 result: 0.77 | 0.6 | 2 | 0.924 |
Null or undefined makes more sense. | 0.46content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 6 wordValue: 0.1 result: 0.46 | 0.5 | 2 | 0.46 |
Maybe we should prefix the footnotes for issue de duplication wi… | 1.33content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 21 wordValue: 0.1 result: 1.33 | 0.8 | 2 | 2.128 |
```suggestionlet footnotes: string[];``&… | 0content: content: {} result: 0 regex: wordCount: 0 wordValue: 0.1 result: 0 | 0.4 | 2 | 0 |
I don't know off hand if 10 turns into 010 or just 10 | 0.94content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 14 wordValue: 0.1 result: 0.94 | 0.3 | 2 | 0.564 |
This seems brittle to target strings like this. Any ideas to get… | 1.38content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 22 wordValue: 0.1 result: 1.38 | 0.6 | 2 | 1.656 |
Sure. Just seems more concise to write it that way | 0.71content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 10 wordValue: 0.1 result: 0.71 | 0.5 | 2 | 0.71 |
Can you make it? Seems pretty relevant and here is our first use… | 0.94content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 14 wordValue: 0.1 result: 0.94 | 0.7 | 2 | 1.316 |
I suppose this should be removed. | 0.46content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 6 wordValue: 0.1 result: 0.46 | 0.1 | 2 | 0.092 |
QA screenshot looks promising but better if you can link that th… | 1.11content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 17 wordValue: 0.1 result: 1.11 | 0.2 | 2 | 0.444 |
@gentlementlegen @whilefoo RFC | 0.25content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 3 wordValue: 0.1 result: 0.25 | 0.1 | 2 | 0.05 |
This will look up from our already generated embeddings. It need… | 1.11content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 17 wordValue: 0.1 result: 1.11 | 0.3 | 2 | 0.666 |
So what's the solution | 0.39content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 5 wordValue: 0.1 result: 0.39 | 0.2 | 2 | 0.156 |
Given this task I think we should support commands in the copilo… | 6content: content: p: score: 0 elementCount: 1 a: score: 5 elementCount: 1 result: 5 regex: wordCount: 15 wordValue: 0.1 result: 1 | 0.4 | 2 | 4.8 |
All commands move to chat box. No more in comments. | 0.71content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 10 wordValue: 0.1 result: 0.71 | 0.3 | 2 | 0.426 |
I had a similar problem with bun I needed to upgrade it before i… | 1.22content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 19 wordValue: 0.1 result: 1.22 | 0.4 | 2 | 0.976 |
https://docs.github.com/en/copilot/using-github-copilot/asking-g… | 8.2content: content: p: score: 0 elementCount: 1 a: score: 5 elementCount: 1 result: 5 regex: wordCount: 59 wordValue: 0.1 result: 3.2 | 0.6 | 2 | 9.84 |
I realized also that we could do a workaround by using the web b… | 6.44content: content: p: score: 0 elementCount: 1 img: score: 5 elementCount: 1 result: 5 regex: wordCount: 23 wordValue: 0.1 result: 1.44 | 0.3 | 2 | 3.864 |
Then comment slash command for now | 0.46content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 6 wordValue: 0.1 result: 0.46 | 0.1 | 2 | 0.092 |
Our plugins invoked by commands should populate on our help menu… | 1.85content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 31 wordValue: 0.1 result: 1.85 | 0.4 | 2 | 1.48 |
Actually I see that the manifests aren't building on push @gentl… | 1.11content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 17 wordValue: 0.1 result: 1.11 | 0.4 | 2 | 0.888 |
Agreed on the recommendation. @gentlementlegen maybe you can han… | 2.2content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 38 wordValue: 0.1 result: 2.2 | 0.5 | 2 | 2.2 |
@shiv810 @whilefoo @gentlementlegen you guys can do a retroactiv… | 1.17content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 18 wordValue: 0.1 result: 1.17 | 0.2 | 2 | 0.468 |
[ 38.29 WXDAI ]
@gentlementlegen
Contributions Overview
View | Contribution | Count | Reward |
---|---|---|---|
Review | Code Review | 1 | 5.36 |
Review | Comment | 9 | 32.93 |
Review Details for #70
Changes | Priority | Reward |
---|---|---|
+262 -6 | 2 | 5.36 |
Conversation Incentives
Comment | Formatting | Relevance | Priority | Reward |
---|---|---|---|---|
The code looks generally okay, for the lock file I think you sho… | 2.49content: content: p: score: 0 elementCount: 2 result: 0 regex: wordCount: 44 wordValue: 0.1 result: 2.49 | 0.9 | 2 | 4.482 |
It will skip the plugin only for `issue.comment_created`… | 1.38content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 22 wordValue: 0.1 result: 1.38 | 0.7 | 2 | 1.932 |
@0x4007 It uses this event to store the comment in the database:… | 6.28content: content: p: score: 0 elementCount: 1 a: score: 5 elementCount: 1 result: 5 regex: wordCount: 20 wordValue: 0.1 result: 1.28 | 0.8 | 2 | 10.048 |
@0x4007 do you have access to it on mobile devices? I don't seem… | 1.22content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 19 wordValue: 0.1 result: 1.22 | 0.1 | 2 | 0.244 |
@koya0 You have to update `bun.lockb` because it is not … | 1.06content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 16 wordValue: 0.1 result: 1.06 | 0.8 | 2 | 1.696 |
@koya0 You can try upgrading bun to `1.2` where lock fil… | 1.28content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 20 wordValue: 0.1 result: 1.28 | 0.75 | 2 | 1.92 |
@koya0 Can't you just delete it now that you are using the plain… | 1.06content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 16 wordValue: 0.1 result: 1.06 | 0.4 | 2 | 0.848 |
I confirm it is available in the browser on mobile versions. But… | 7.92content: content: p: score: 0 elementCount: 3 a: score: 5 elementCount: 1 result: 5 regex: wordCount: 53 wordValue: 0.1 result: 2.92 | 0.5 | 2 | 7.92 |
It is normal that the manifest is not built, there are no push e… | 3.2content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 59 wordValue: 0.1 result: 3.2 | 0.6 | 2 | 3.84 |
[ 60.21 WXDAI ]
@shiv810
Contributions Overview
View | Contribution | Count | Reward |
---|---|---|---|
Review | Code Review | 1 | 55.18 |
Review | Comment | 2 | 5.03 |
Review Details for #70
Changes | Priority | Reward |
---|---|---|
+2742 -17 | 2 | 55.18 |
Conversation Incentives
Comment | Formatting | Relevance | Priority | Reward |
---|---|---|---|---|
This regex will match all footnotes, i.e., any `[^<NUM>… | 1.7content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 28 wordValue: 0.1 result: 1.7 | 0.8 | 2 | 2.72 |
We could something like this, this should be better than handlin… | 1.65content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 27 wordValue: 0.1 result: 1.65 | 0.7 | 2 | 2.31 |
[ 63.024 WXDAI ]
@whilefoo
Contributions Overview
View | Contribution | Count | Reward |
---|---|---|---|
Review | Code Review | 1 | 55.18 |
Review | Comment | 5 | 7.844 |
Review Details for #70
Changes | Priority | Reward |
---|---|---|
+2742 -17 | 2 | 55.18 |
Conversation Incentives
Comment | Formatting | Relevance | Priority | Reward |
---|---|---|---|---|
Using metadata would be more reliable, you'd need to use `po… | 1.54content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 25 wordValue: 0.1 result: 1.54 | 0.8 | 2 | 2.464 |
The kernel should be modified so that if the plugin manifest def… | 2.15content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 37 wordValue: 0.1 result: 2.15 | 0.6 | 2 | 2.58 |
This is an additional way to trigger commands, right? You'd stil… | 2.2content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 38 wordValue: 0.1 result: 2.2 | 0.4 | 2 | 1.76 |
I think on mobile it's only for Github Pro users | 0.77content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 11 wordValue: 0.1 result: 0.77 | 0.2 | 2 | 0.308 |
Normally if there's a conflict with `bun.lockb`, you jus… | 1.22content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 19 wordValue: 0.1 result: 1.22 | 0.3 | 2 | 0.732 |
Hey @koya0 I was trying to use it here any idea why it's not working |
It could be that no similar issues were found. Is there a specific issue you wanted the command to make a reference to? I could test it in my repo and see if this's what its really happening |
or maybe you could make a comment exactly like the body of the issue and try the command |
i tried this here and worked: koya0/.ubiquity-os#32 |
Is there a bottom threshold? Can strings match even with a 1% match? I think that might be why it's not showing anything. @shiv810 maybe you have some perspective on how the matching works exactly with issue deduplication but the string I wanted annotated was
|
the command only identifies similar issues above or equal the |
|
i made some tests with koya0/.ubiquity-os#33 (comment) and apparently the comment you wanted to annotate is 84% similar to the issue of the own comment, so at least the bot should annotate that issue As the supabase function im using to get similar issues its probably not the same of the prod supabase, I don't know if in prod the comment is not that similar to the issue or the command really has a problem |
is it possible to check the bot log? If yes, we can confirm what is the problem |
Possibly here https://github.com/ubiquity-os-marketplace/text-vector-embeddings/actions/workflows/compute.yml |
I couldn't find the comments you made with the annotate command |
/annotate |
for this one no similar issues were found https://github.com/ubiquity-os-marketplace/text-vector-embeddings/actions/runs/13166645094/job/36748291657 |
Maybe the action is only used to store the embedding I'm not sure since I never worked on this repo. You should know better where the logs would appear I would guess! |
Yes, by default all the embeddings would have a cosine similarity value more than
This approach won't work because text-vector-embeddings/src/plugin.ts Lines 36 to 38 in 0f91884
|
when a comment is created I call userAnnotate, that checks the /annotate prefix and runs the command text-vector-embeddings/src/plugin.ts Lines 40 to 44 in 0f91884
|
The @whilefoo rfc ? |
but this command: #67 (comment) worked. If you check
|
I am not sure how |
|
If listeners include So it seems the plugin is ran but it doesn't find any similar issues |
We'll definitely need an output of sorts. I wish there was an appropriate emoji reaction to the annotate comment but not sure there is. It can post an error message in the form of a new comment explaining that it ran successfully but there's no good matches. |
There are situations where we write about certain issues that were likely to have been posted in the past, but are difficult to find.
Imagine if using vector embeddings, we can instantly link to whatever issues are being referenced:
From kingsley-einstein/contributions-scan#4 (comment)
Using this command, we should replicate the behavior of issue deduplication on the existing comment and edit/add the footnotes with links to the source issues.
A limitation that I see is how wide of a search we should conduct. Within the same repository is somewhat useless, and globally might incur too much noise.
Organization wide might be the best default, but sometimes it would be very useful, especially for us using three organizations, to do a global annotation/search.
Perhaps we can have optional arguments to scope the search.
But default can be just
And it will automatically annotate the previous comment with an organization wide search.
The text was updated successfully, but these errors were encountered: