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

Issue Matching Fails, with invalid payload object. #60

Closed
shiv810 opened this issue Dec 12, 2024 · 12 comments · Fixed by #61
Closed

Issue Matching Fails, with invalid payload object. #60

shiv810 opened this issue Dec 12, 2024 · 12 comments · Fixed by #61

Comments

@shiv810
Copy link
Collaborator

shiv810 commented Dec 12, 2024

The issue matchmaking (issue contributor recommendation) functionality should work across multiple orgs/repos and not be restricted within single repo.

Copy link
Contributor

ubiquity-os-beta bot commented Dec 12, 2024

Note

The following contributors may be suitable for this task:

sshivaditya2019

73% Match ubiquity-os-marketplace/text-vector-embeddings#7

0x4007

71% Match ubiquity/ubiquibot#917

zugdev

71% Match ubiquity/work.ubq.fi#169

@0x4007
Copy link
Member

0x4007 commented Dec 13, 2024

The issue matching functionality

This isn't specific enough please be careful to use precise terminology.

Is this for issue deduplication or is this for talent recommendation?

I have some mixed feelings.

For issue deduplication:

  • the same issue description in two different repos can be two very different types of projects.
  • I'm leaning towards that it makes sense to scope within a specific repo instead of global because this is intended to automatically close issues that are too similar. If another project did the same feature then obviously this automation doesn't make any sense.

For talent recommendation:

  • given that these are suggestions and that the intended flow is that human managers should manually review and then decide to tag makes this more forgiving.
  • the precise use case is if it was implemented in another project you can poach that same talent to solve the same problem for you
  • this should be global (across all repos and orgs)

Also, a new policy will be that issue authors should always set time labels and then admins will set priority level levels

Copy link
Contributor

! You are not allowed to generate permits.

Copy link
Contributor

! Error: TypeError: Cannot read properties of null (reading 'node')

Copy link
Contributor

! Error: TypeError: Cannot read properties of null (reading 'node')

@rndquu rndquu removed this from Development Dec 19, 2024
@0x4007 0x4007 mentioned this issue Dec 19, 2024
@0x4007
Copy link
Member

0x4007 commented Dec 19, 2024

! You are not allowed to generate permits.

@gentlementlegen sshivaditya2019 is a collaborator

@0x4007 0x4007 reopened this Dec 19, 2024
@0x4007 0x4007 closed this as completed Dec 19, 2024
@0x4007 0x4007 reopened this Dec 19, 2024
Copy link
Contributor

@sshivaditya2019 the deadline is at Thu, Dec 19, 3:31 PM UTC

@0x4007 0x4007 closed this as completed Dec 19, 2024
Copy link
Contributor

+ Evaluating results. Please wait...

1 similar comment
Copy link
Contributor

+ Evaluating results. Please wait...

Copy link
Contributor

 [ 153.84 WXDAI ] 

@sshivaditya2019
Contributions Overview
ViewContributionCountReward
IssueTask1150
IssueSpecification13.84
ReviewComment40
Conversation Incentives
CommentFormattingRelevancePriorityReward
The issue matchmaking (issue contributor recommendation) functio…
1.28
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 20
  wordValue: 0.1
  result: 1.28
133.84
Resolves #60 - Allows Issue Matching outside repos and orgs. …
1
content:
  content:
    p:
      score: 0
      elementCount: 3
    ul:
      score: 0
      elementCount: 1
    li:
      score: 0.5
      elementCount: 2
  result: 1
regex:
  wordCount: 17
  wordValue: 0
  result: 0
0.930
It could be any value. Should I add this to config instead ?
0
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 12
  wordValue: 0
  result: 0
0.730
It doesn't matter, it could be any value since we are mocking th…
0
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 24
  wordValue: 0
  result: 0
0.530
QA:https://github.com/sshivaditya2019/test-public/issues/235
5
content:
  content:
    p:
      score: 0
      elementCount: 2
    a:
      score: 5
      elementCount: 1
  result: 5
regex:
  wordCount: 1
  wordValue: 0
  result: 0
0.130

 [ 35.541 WXDAI ] 

@0x4007
Contributions Overview
ViewContributionCountReward
IssueComment231.92
ReviewComment53.621
Conversation Incentives
CommentFormattingRelevancePriorityReward
This isn't specific enough please be careful to use precise term…
10.64
content:
  content:
    p:
      score: 0
      elementCount: 1
    ul:
      score: 0
      elementCount: 1
    li:
      score: 0.5
      elementCount: 5
  result: 2.5
regex:
  wordCount: 177
  wordValue: 0.1
  result: 8.14
1331.92
@gentlementlegen sshivaditya2019 is a collaborator
0.39
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 5
  wordValue: 0.1
  result: 0.39
030
Isn't this error prone if a single request fails then everything…
0.88
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 13
  wordValue: 0.1
  result: 0.88
0.832.112
Why no analytics
0.25
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 3
  wordValue: 0.1
  result: 0.25
0.330.225
Why 5?
0.18
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 2
  wordValue: 0.1
  result: 0.18
0.430.216
Why similar3
0.18
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 2
  wordValue: 0.1
  result: 0.18
0.530.27
Probably not but was just curious why you chose 5 but based on b…
1.33
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 21
  wordValue: 0.1
  result: 1.33
0.230.798

Copy link
Contributor

 [ 153.84 WXDAI ] 

@sshivaditya2019
Contributions Overview
ViewContributionCountReward
IssueTask1150
IssueSpecification13.84
ReviewComment40
Conversation Incentives
CommentFormattingRelevancePriorityReward
The issue matchmaking (issue contributor recommendation) functio…
1.28
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 20
  wordValue: 0.1
  result: 1.28
133.84
Resolves #60 - Allows Issue Matching outside repos and orgs. …
1
content:
  content:
    p:
      score: 0
      elementCount: 3
    ul:
      score: 0
      elementCount: 1
    li:
      score: 0.5
      elementCount: 2
  result: 1
regex:
  wordCount: 17
  wordValue: 0
  result: 0
0.930
It could be any value. Should I add this to config instead ?
0
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 12
  wordValue: 0
  result: 0
0.730
It doesn't matter, it could be any value since we are mocking th…
0
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 24
  wordValue: 0
  result: 0
0.530
QA:https://github.com/sshivaditya2019/test-public/issues/235
5
content:
  content:
    p:
      score: 0
      elementCount: 2
    a:
      score: 5
      elementCount: 1
  result: 5
regex:
  wordCount: 1
  wordValue: 0
  result: 0
0.130

 [ 35.805 WXDAI ] 

@0x4007
Contributions Overview
ViewContributionCountReward
IssueComment231.92
ReviewComment53.885
Conversation Incentives
CommentFormattingRelevancePriorityReward
This isn't specific enough please be careful to use precise term…
10.64
content:
  content:
    p:
      score: 0
      elementCount: 1
    ul:
      score: 0
      elementCount: 1
    li:
      score: 0.5
      elementCount: 5
  result: 2.5
regex:
  wordCount: 177
  wordValue: 0.1
  result: 8.14
1331.92
@gentlementlegen sshivaditya2019 is a collaborator
0.39
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 5
  wordValue: 0.1
  result: 0.39
030
Isn't this error prone if a single request fails then everything…
0.88
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 13
  wordValue: 0.1
  result: 0.88
0.932.376
Why no analytics
0.25
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 3
  wordValue: 0.1
  result: 0.25
0.330.225
Why 5?
0.18
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 2
  wordValue: 0.1
  result: 0.18
0.430.216
Why similar3
0.18
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 2
  wordValue: 0.1
  result: 0.18
0.530.27
Probably not but was just curious why you chose 5 but based on b…
1.33
content:
  content:
    p:
      score: 0
      elementCount: 1
  result: 0
regex:
  wordCount: 21
  wordValue: 0.1
  result: 1.33
0.230.798

@gentlementlegen
Copy link
Member

I know that the profile is private so probably the bot cannot see the collaborator status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants