-
Notifications
You must be signed in to change notification settings - Fork 41
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
Can't get project by slug as Projects instance parse fails #188
Comments
Had the same issue, thanks for the quick fix @XaverStiensmeier! |
Thank you, @XaverStiensmeier, for identifying this issue and providing a fix! I encountered the same problem, and your solution worked perfectly for me. |
@psybers @Daschi1 @annaerdi @XaverStiensmeier I've just released 1.3.1 version that should address this issue. Could you please check if everything is working as expected now? |
Thank you, @protoroto, for addressing this issue! However, I used this project to export data and migrate away from Taiga. I also deleted my Taiga instance after completing the migration, so I’m unable to test the fix under the same circumstances I had before. |
@protoroto I can confirm the old behavior/bug and that it works with the latest release. |
@psybers Cool! I'm going to close this issue then, @XaverStiensmeier feel free to open a new one if you're experiencing problems with this again! |
Description
Executing:
I get:
It's not like
entries = [None]
or something, but more that the parsers gets (last lines before error) see below. Logging format print("Entry {line of code in base.py where the print is placed}", entry):Steps to reproduce
Versions
python -c "import django; print(django.get_version())"
Expected behaviour
Get the project - while I get a correct JSON response, the error occurs while interpreting it.
Actual behaviour
I get an error saying that entries can't be iterated.
Additional information
The JSON response looks correct. It is just the interpreting that throws the error. I will try to debug this further on my machine.
Fix?
I have just changed the
ListResource
method to:not sure if that's a good way to handle it, but it seems to work for my needs for now.
The text was updated successfully, but these errors were encountered: