Skip to content
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

Trouble accessing issue journal notes #50

klmitch opened this issue Sep 22, 2014 · 1 comment

Trouble accessing issue journal notes #50

klmitch opened this issue Sep 22, 2014 · 1 comment


Copy link

klmitch commented Sep 22, 2014

I have an application using python-redmine to access our Redmine instance; we use this application to automate some state management and make comments on Redmine issues based on pull requests to our enterprise Github. Recently, I've been seeing errors related to extracting journal notes. I really only started noticing the issues today, in conjunction with the 1.0.0 release, but I suspect that the issues been present for a few days now.

The main issue I've been seeing is with journal entries which document some change to the issue, such as a status change; I seem to be getting a ValueError with the following message: "dictionary update sequence element #0 has length 1; 2 is required". The code in question loops over the the issue journals and tries to add "journal.notes" to a list. (To make the application work, I currently have the stack trace suppressed through the use of a try/except block, so I don't have a good stack trace to include at the moment…)

This is a preliminary bug report; I'll try to look more deeply into exactly what errors I get and what the corresponding journal entry looks like, as I get time, but I wanted to go ahead and log the bug report in case you already have an idea of what the cause could be. If you have any specific information you'd like me to try to collect, please let me know about that as well.

maxtepkeev added a commit that referenced this issue Sep 23, 2014
@maxtepkeev maxtepkeev added the bug label Sep 23, 2014
@maxtepkeev maxtepkeev self-assigned this Sep 23, 2014
Copy link

Hi Kevin!

Thanks for the bug report!

Yes, this bug was introduced in v1.0.0 with the addition of a Note resource from CRM plugin. I fixed it in v1.0.1 which is now available to download from PyPI.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants