1199626 - [s3] Error message displayed in comm dashboard after approving an app with a file attached

Status: RESOLVED DUPLICATE of bug 1233540

(Marketplace Graveyard :: Reviewer Tools, defect, P2)

Description

[Madalin Cotetiu]

Steps to reproduce:
1. Open a review detail page for any app.
2. Attach a file and approve the app.
3. Open the comm dashboard page for that app.

Expected results:
The page successfully loads.

Actual results:
"Error loading threads" message is displayed.

Notes/Issues:
Verified in FF43(Win7) in marketplace-dev.allizom.org
Screencast for this issue: http://screencast.com/t/Zki7KcY9N4JX

Comment 1

[Andrew Williamson [:eviljeff]]

regression from bug 1198817 ?

Comment 2

[Madalin Cotetiu]

Issue is now also reproducing in stage.

Comment 3

[Rob Hudson [:robhudson]]

I had a hard time finding this exact app on -dev. From the screencast I saw id=302 which no longer exists on -dev, which could be why this is having an issue?

Madalin could you re-verify using an existing app? Or share the URL of the one you're testing so I can take a look?

Thanks.

Comment 4

[Rob Hudson [:robhudson]]

I added a recent attachment to this app in the reviewer tools and it shows up fine in the reviewer tools and comm dashboard:
https://marketplace-dev.allizom.org/reviewers/apps/review/elegant-curry
https://marketplace-dev.allizom.org/comm/app/elegant-curry

Please re-open if I'm looking at the wrong thing.

Comment 5

[Madalin Cotetiu]

I can't no longer reproduce this issue on stage or -dev. I'll keep investigating and reopen if I will see it again.

Comment 6

[Valentina Virlics [:vvalentina], Ecosystem QA]

The issue from comment 0 is now reproducing on https://marketplace-dev.allizom.org/reviewers page using FF43(Win 7).

Also, may be a related issue, the following:
1. Load https://marketplace-s3dev.allizom.org/reviewers page
2. Go to Queue-Apps and click on an app (i.e. Exquisite Bacon)
3. Submit a review (Approve/Reject/Comment with or without attachment)

Excpected results:
The message/attachment is saved and displayed in App History.

Actaul results:
An “Internal Server Error” is thrown in the web console and nothing appears in App History.

Please see the screencast: http://screencast.com/t/XEcuIVzX
Let me now if another issue should be logged.

Comment 7

[David Durst [:ddurst]]

While we aren't going to do the rest of the S3 migration, 500 error is bad.