Errors should be clearer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ratings and Reviews server |
New
|
Undecided
|
Unassigned | ||
software-center (Ubuntu) |
Confirmed
|
Undecided
|
Aaron Peachey |
Bug Description
Bug Description:
Currently any review that fails to be sent is flagged with "Failed to send review" this give no reason as too why. 2 solutions are to point the user at the oops file in /tmp this is ugly and not guaranteed to be clear the other is to display from the oops the important part, for example:
Failed to send review: You have already posted a review for this application.
Failed to send review: There is an issue with the server please try again latter
Version:
Django 1.1.1
Python 2.6.5 (r265:79063, Apr 16 2010, 14:15:55) [GCC 4.4.3]
preflight 0.1
rnr-server 11.01
openid 2.2.1
launchpadlib 1.6.0
piston 0.2.2
South 0.6
OS:
64bit Maverick
Browser:
in built python webkit
Problem URL:
n/a
Steps To Reproduce:
1. Send a review for gedit
2. Try to send another review for gedit
3. Change the run_testing..... script to a host that doesn't exist for rnr and send a review on any app.
Expected Result:
As an end user I expect to be notified as to why I can't send my review, or for server outages to be asked to send it later.
This maybe an issue in conjunction with Software Center, but I think should be based on key words in oops reports locally probably.
Related branches
tags: | added: client-server |
affects: | software-center → software-center (Ubuntu) |
I'm working on this on the client side first to see if we already get useful info that we can use consistently for a user friendly error message. If not, I'll take a look at the handlers on the server to see if we can return some more useful text (or something that will be useful in distinguishing what the issue is so the client can determine the string to show)