Change search queries to GraphQl to avoid permission issues

[gentlementlegen]

          It is still weird to me that the user privacy affects a search because the profile is public. Can we consider using GQL with issues search instead of the search API? Something like

query($organization: String!, $author: String!) {
  organization(login: $organization) {
    repositories(first: 100) {
      nodes {
        issues(first: 100, states: OPEN, filterBy: {createdBy: $author}) {
          nodes {
            title
            url
            createdAt
          }
        }
      }
    }
  }
}

with

{
  "organization": "ubiquity",
  "author": "sshivaditya2019"
}

would achieve the same result. I don't know if that would resolve the issue but it's worth a try.

Originally posted by @gentlementlegen in ubiquity/work.ubq.fi#119 (comment)

[0x4007]

Somebody should test and see if this works before we fund it.

[ubiquity-os-beta]

@gentlementlegen the deadline is at Mon, Oct 28, 3:49 PM UTC

[gentlementlegen]

@0x4007 I spent quite some time on this. It seems to work ok but it is awfully slow at the moment, I'll try to see if there is a better way.

[gentlementlegen]

@0x4007 I managed to make it faster but it takes still something like 5 to 10 seconds depending on the org (ubiquity for example has tons of PRs). GitHub search is obviously using caching and indexing to provide near instant results. Maybe we could have this logic as a backup when the search fails?

Sidenote, this seems to happen when the user has set his activity to private.

[0x4007]

Seamless fallback seems like a reasonable solution.

[ubiquity-os-beta]

 [ 115.938 WXDAI ] 

@gentlementlegen

Contributions Overview

View	Contribution	Count	Reward
Issue	Task	1	100
Issue	Specification	1	11.25
Issue	Comment	2	4.688
Review	Comment	2	0

Conversation Incentives

Comment	Formatting	Relevance	Reward
It is still weird to me that the user privacy affects a search b…	3.75 content: content: p: score: 0 elementCount: 4 em: score: 0 elementCount: 1 result: 0 regex: wordCount: 71 wordValue: 0.1 result: 3.75	1	11.25
@0x4007 I spent quite some time on this. It seems to work ok but…	1.9 content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 32 wordValue: 0.1 result: 1.9	0.8	1.52
@0x4007 I managed to make it faster but it takes still something…	3.52 content: content: p: score: 0 elementCount: 2 result: 0 regex: wordCount: 66 wordValue: 0.1 result: 3.52	0.9	3.168
Resolves #70QA: https://github.com/Meniole/command-start-stop/…	0 content: content: p: score: 0 elementCount: 2 result: 0 regex: wordCount: 20 wordValue: 0 result: 0	0.2	0
@0x4007 On the good news: it works, I successfully retrieve the …	0 content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 53 wordValue: 0 result: 0	0.7	0

 [ 1.028 WXDAI ] 

@0x4007

Contributions Overview

View	Contribution	Count	Reward
Issue	Comment	2	1.028

Conversation Incentives

Comment	Formatting	Relevance	Reward
Somebody should test and see if this works before we fund it.	0.83 content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 12 wordValue: 0.1 result: 0.83	0.8	0.664
Seamless fallback seems like a reasonable solution.	0.52 content: content: p: score: 0 elementCount: 1 result: 0 regex: wordCount: 7 wordValue: 0.1 result: 0.52	0.7	0.364

[ubiquity-os-beta]

! chat_not_found

[gentlementlegen]

@Keyrxng We might want to improve that message, maybe not even post it because I don't think it's relevant to users.

[Keyrxng]

I recently added logic to comment any status !== 200 for workflows during debugging it's handy but needs tweaked for sure.

For close we should do nothing. For reopen, should we create one or do nothing or detect a merged PR and only open if there isn't one?

Some little behaviours need refined and tweaked

[gentlementlegen]

I think room creation failure is important to understand that it tried to open it but failed; closing errors might be silent. We always have the logs in the Actions and Cloudflare logs if needed. But yes we should discuss these in details. We can keep the closing error but we need a prettier message at least.