-
Notifications
You must be signed in to change notification settings - Fork 17
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 list not loading #118
Comments
After weeks of smooth sailing with Redtimer I am suddenly experiencing this in Ubuntu 18.04. I'm using Redmine 4.0.4.stable with redtimer-v1.2.9. I have tried rolling back my database, using various versions of Redtimer, fresh installing Redmine (via Docker), clearing the "Thomssen IT/RedTimer.ini" file but have had no luck with any of it. Redtimer CAN create new issues in this state, but it is unable to view them or any others once they are created, rendering it unusable. Any help would be greatly appreciated. |
I'll also note that Redtimer does issue get requests when opening the issues list and choosing a project (i.e. hxxp://192.x.x.x:8080/issues.json?project_id=2&offset=0&limit=100 ). Opening those requests in a browser finds that non-malformed JSON data is returned upon making those requests, but Redtimer seems uninterested in parsing it. It doesn't have trouble filling the project list or activities list, only the issues. I am logged in as the admin user, so these issues are available to me (and were all listed previously before experiencing this issue.) |
Update: I compiled and ran from source with QtCreator and to my surprise the fresh build worked. And then my previously installed build worked as well, inexplicably... If the problem occurs again I'll debug and report back (time permitting) any findings for anyone else encountering the issue and hopefully help with the resolution. |
I am on macOS High Sierra 10.13.4 (17E202) and Redmine 3.4.4.stable.
RedTime receives everything properly (projects, users, etc) except the issue list. It throws a notification saying that it could not receive the issues ("Error transfering the issues [...]").
The text was updated successfully, but these errors were encountered: