Can't get the repo's issues


#1

I tried this query:

query { 
    repository(owner: "avajs", name: "ava") {
         createdAt,
        description,
        issues(first: 5) {
            nodes {
              id
            }
        }
    }
}

but I failed to recieve any issue:

{
  "data": {
    "repository": {
      "createdAt": "2014-11-18T17:20:26Z",
      "description": ":rocket: Futuristic JavaScript test runner",
      "issues": {
        "nodes": []
      }
    }
  }
}

Please, help :older_woman:


#2

Hi there @yanisurbis , thanks for sharing this report with us! I’ve asked our team to investigate this in an internal issue. I’m not sure why that’s happening and I’ll be sure to reach out again when I hear more from them!

Are you seeing this in any other repository?

Also, I noticed that you included commas in your original query and omitted edges between issues and nodes and specified nodes rather than node. I just ran this query and I’m able to see the first five issues from the github/linguist project – could you give this a try and let me know if you’re able to see those issues?

{
  repository(owner: "github", name: "linguist") {
    createdAt
    description
    issues(first: 5) {
      edges {
        node {
          id
        }
      }
    }
  }
}

#3

Thank you, yes, your query is working for me. Actually, my query that didn’t work is working too now.
Now I have some problems with retrieving of only one issue.

I can’t get any of them =(


#4

This should also be fixed. Could you please confirm?


#5

Hi again @yanisurbis! I tried reproducing your latest report by running the following query:

{
  repository(owner: "tflearn", name: "tflearn") {
    issue(number: 761) {
      body
    }
  }
}

and the equivalent curl command:

curl -v -H “Authorization: token TOKEN” https://api.github.com/graphql -d ‘{“query”: “{ repository(owner: “tflearn”, name: “tflearn”) { issue(number: 761) { body } } }”}’

If you’re still seeing this issue, could you share the full textual output of the curl -v command so we can take a look?


#6

@gjtorikian yes, it’s working, thank you a lot )