-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
I see no issues #43
Comments
set it up in local environment, also took some effort but I got the exact same result. It appears to find the issues, but not display them. |
@Tectract Have you signed in on the boards page, as issues will not be displayed until you login . Select the |
Hmmmmmmm, when I click that icon the page just reloads... in the console now I see: /?error=redirect_uri_mismatch&error_description=The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application.&error_uri=https%3A%2F%2Fdeveloper.github.com%2Fapps%2Fmanaging-oauth-apps%2Ftroubleshooting-authorization-request-errors%2F%23redirect-uri-mismatch&state=y0kcw%2Be........... |
Observations:
Which |
Hi, yes this is a private repo... Is that a problem? in my github app I have
Here's what my .env looks like
|
Please checkout the updated setup document and perform the setups mentioned in the configure app section. |
Thank you, this seems to have gotten me closer to being able to log in. When I clicked the icon after changing this github app setting, it DID take me to a page to authorize this github app. I clicked "authorize". Then it took me to an error page, at smee, that only says: Cannot GET /5xxxxxx/wuffle/login/callback Thank you again for your work here :) I hope this can be resolved, I'd love to move off Zenhub, lol. |
It should not redirect you to SMEE but to |
Ok, I had BASE_URL to be the smee url. I changed that to localhost:3000, and also the User authorization callback URL, to be localhost:3000/wuffle/login/callback. Success, I can log in. When I click on the icon in the upper right corner, now my github user icon appears. Good. I still see no issues in any columns, however. |
I'm wondering if the issue could be related to the fact that I'm trying to set up the repo for an organization I run, named EnLedger, whille my username is tectract. I see in the storedump, in the issue data: and the app is installed under the enledger organization with only access to this one repo... |
Nope. The board has multi-repository / organization support. Cf. tasks.bpmn.io where we connect 90 repositories across three different organizations (public and private ones). |
Please share your complete logs (app startup, user login) with private details redacted. |
npm run dev
|
No errors in the logs. Just seems like it doesn't recognize the issues as belonging to me. Can I just hack it to make it show me all the issues or something? |
What is the relationship between user |
EnLedger is my company. The enledger organization was created by my tectract user account, and I am the admin of that organization, along with my CEO. I have read and write / full admin access to everything in the enledger repos. As I noted, wuffle IS seeing the issues, and even apparently placing them into columns, there are 47 issues in the storedump.json file... It's just not showing them to me, lol. I only installed this app in the enledger organization, and gave it access to this one repo, because I didn't see any way to separate out the issues by repository, and I wanted a kanban board only for the EnLedger-Website repo tasks. There is actually no enledger user, as far as I know, it's just an organization created by tectract user. |
You login as |
Yes, there appears to be some problem with me being able to see the issues. I see no issues on the board. Is there anything else I can do to help you troubleshoot? I couldn't dig too deeply into the code without some assistance... |
The latest version in Run the app using
Here the board tells you exactly what it thinks are the private repositories you have access to. |
I did connect the board to all the enledger repos, some of which are public, and I did see some issues there... But not on the repo in question which is a private repo... |
I will update and test again tonight. Thanks again for your help! Maybe I can become a contributor if we get this working :) |
Let's get this working first! 🥁 |
[dev:app ] 22:57:22.067Z DEBUG wuffle:user-access: creating member filter (token=3xxx) Seem ok to you? Still no issues showing up though, even after I merged your updates in the upstream branch down to my fork... |
Yep. Everything fine on the back-end side of things. You could check your browser for errors in the log. That is the last idea I got. |
Yeah, I didn't see any errors in the web console, sadly. Can we make it spit out what issues it thinks it should be displaying in the logs somehow? I would soooooooooooo love to move off Zenhub right now, they are nickel-and-diming me! Kanban should be freeeeeeeeeeeeee! |
You could debug the app via Unfortunately I cannot help you beyond this point. |
Having an issue like "the app doesn't work at all" for a new user is a pretty serious problem, just my two cents. In my repos, I don't close critical usability issues until they are resolved, but hey that's just me. Is this app just mainly for your own use or did you intend for others to be able to use it also? I'm a very advance programmer, just not familiar with how you put this thing together. I can try to debug but without any working knowledge of the code, I feel like it's lost time. Maybe you can point me to some critical code files I should be looking at here. Can you describe how I might use ndb to debug here? Is there a description of the API, or where are those files? I actually have some additions to the setup files, after getting it working both locally and on heroku... |
@Tectract I found when I had issues initially getting my Wuffle up and running. I had issues in permissions set incorrectly, authorisation callback and incorrect webhook password etc. It could be any or all of these things. It is extremely difficult to tell what has gone wrong without being able to see everything. You should try to set it up again on a personal repo with a new probot double checking everything and that may help in your investigation. I ran it in debug mode and added lots of extra log lines to help me figure out where I had gone wrong. Although slightly out of date you could also check against my initial deployment notes PR which is slightly out of date but has a lot of details that may help you in your investigation: #36 |
I've already set it up twice, once on my local machine and once on Heroku. On both environments I spent hours tinkering with it until it ran and downloaded all the issues with no error. I got the same exact behavior in both environments: no issues show up on my board. So, I think it's the code, not me. Where should I be adding debug statements? Where in the code does it retrieve issues for display, when I load the page? |
Set it up once for a personal project, share the link to the board with us. Once you accomplished that, go forth and use the setup GitHub app for your private only org. Stuff should just work. |
Will set up a test repo, and detailed instructions of my install for heroku. Give me a day or two :) |
I give up. I don't see how me doing a bunch of hours of testing is going to change anything. Seems this tool is broken or only works for people who want to kanban their own personal repos. But you closed my issue even though it wasn't resolved so... what's the point. I'll just pay zenhub instead of losing time to this broken thing... |
Hi there, trying to set up for the first time.
I finally got the app running at heroku, and, seemingly, linked to a reposity.
I see this in the logs...
However when I go to my board, I see no issues in any columns. What happened? Where are they?
The text was updated successfully, but these errors were encountered: