-
Hi I'm not really sure why an error occurs within the work flow. this is the error log ──────────────────────────────────────────────────────────────── |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
Hello ! Actually I'm wondering what's happening too... I forked your repo at lowlighter/uoojin1 and I seem able to generate your metrics when I provide a personal token (by the way, this line should have Using the GraphQL explorer with generated query seems ok too. Generated query
Anyway the same query is executed on shared instance so I really don't know what could cause this error. By searching on google, it seems that What you could try though (although I'm not sure it'll have any effect) :
Seems you already find a workaround for now 🙂 If nothing above works or does not give additional data, I'll try to contact GitHub support with your requests ids to get more informations. Have a nice day ! |
Beta Was this translation helpful? Give feedback.
-
Hey lowlighter! Thanks for the detailed response. It was really helpful and I was able to get it to work. I think it was a scope issue. I added few more permissions to the token and it started working :). One weird thing I noticed is that when I generate the svg from this website (https://metrics.lecoq.io/), it picks up my contributions to repositories that are from a private organization (need SSO login). However when I run the query with the github action, it doesn't seem to pick up those contributions (so less commits are shown on the calendar plugin). Please let me know if there is a way to fix this issue Thank you! |
Beta Was this translation helpful? Give feedback.
-
Glad you were able to make it work ! Do you know which scopes were actually missing ? As for the contributions from private organizations, I'm not sure myself... Playing the following query on GraphQL explorer and executing the JS one-liner : Query and JSquery Calendar {
user(login: "uoojin1") {
calendar:contributionsCollection(from: "2020-01-07T00:00:00.000Z", to: "2021-01-08T00:00:00.000Z") {
contributionCalendar {
weeks {
contributionDays {
contributionCount
color
date
}
}
}
}
}
} Object(/* Pasted result */).data.user.calendar.contributionCalendar.weeks.reduce((a, b) => a + b.contributionDays.reduce((c, d) => c + d.contributionCount, 0), 0) Yields me more or less the same result which is displayed on your profile page : Basically that's what metrics.lecoq.io is able to display since it only uses a scope-less bot token. I confess that it's weird that your personal token seems to be able to do less than a stranger token x) You can try the following workaround, but I think it's a bit troublesome so maybe it's simpler to use metrics.lecoq.io. Basically, what you could do is to generate isocalendar in its own step (a bit like here) with a scope-less token (so basically you would use a second token). If you get the same results or if you encounter again the initial issue ( It's like reproducing the same behaviour from metrics.lecoq.io so I'm pretty confident it would work, but seems a bit hacky. Sorry that you got so much trouble so far. As I don't really work with GitHub organizations myself, it's something that I don't really thoughrouly tested 😅 Hope you still appreciate it 🙂 |
Beta Was this translation helpful? Give feedback.
-
yeah it was a little weird haha 😅. I was actually able to get it fully working with a new token (scopeless) and authorizing it for use with SSO. Took a long time but finally got there lol. Thanks for all the help, really appreciate it! |
Beta Was this translation helpful? Give feedback.
-
Nice ! Thanks for linking the documentation too ! |
Beta Was this translation helpful? Give feedback.
yeah it was a little weird haha 😅.
I was actually able to get it fully working with a new token (scopeless) and authorizing it for use with SSO.
Authorizing a personal access token for use with SAML single sign-on
Took a long time but finally got there lol.
Thanks for all the help, really appreciate it!