The SourceForge admins couldn't replicate the patch upload problem, and managed to attach a file to the Python bug report in question, yet when I try it, it still fails for me. So, a question for this list: has uploading patches or other files been working for you recently, particularly today? Maybe with more data, we can see a pattern (browser version, SSL/non-SSL, cluefulness of user, ...). If you want to try it, feel free to try attaching a file to bug #404680: https://sourceforge.net/tracker/index.php?func=detail&aid=404680&group_id=5470&atid=305470 ) The SF admin request for this problem is at http://sourceforge.net/tracker/?func=detail&atid=100001&aid=404688&group_id=1, but it's better if I collect the results and summarize them in a single comment. --amk
If you want to try it, feel free to try attaching a file to bug #404680: https://sourceforge.net/tracker/index.php?func=detail&aid=404680&group_id=5470&atid=305470 )
The SF admin request for this problem is at http://sourceforge.net/tracker/?func=detail&atid=100001&aid=404688&group_id=1, but it's better if I collect the results and summarize them in a single comment.
My conclusion: the file upload is refused iff the comment is empty -- in other words the complaint about an empty comment is coded wrongly and should only occur when the comment is empty *and* no file is uploaded. Or maybe they want you to add a comment with your file -- that's fine too, but the error isn't very clear. http or https made no difference. I used NS 4.72 on Linux; Tim used IE and had the same results. --Guido van Rossum (home page: http://www.python.org/~guido/)
Andrew, FYI, we have seen the same problem on the SF zope-book patch tracker. I have a user who can reproduce it, like you. Would you like me to get you more info? -Michel On Tue, 27 Feb 2001, Andrew Kuchling wrote:
The SourceForge admins couldn't replicate the patch upload problem, and managed to attach a file to the Python bug report in question, yet when I try it, it still fails for me. So, a question for this list: has uploading patches or other files been working for you recently, particularly today? Maybe with more data, we can see a pattern (browser version, SSL/non-SSL, cluefulness of user, ...).
If you want to try it, feel free to try attaching a file to bug #404680: https://sourceforge.net/tracker/index.php?func=detail&aid=404680&group_id=5470&atid=305470 )
The SF admin request for this problem is at http://sourceforge.net/tracker/?func=detail&atid=100001&aid=404688&group_id=1, but it's better if I collect the results and summarize them in a single comment.
--amk
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev
[Guido]
My conclusion: the file upload is refused iff the comment is empty -- in other words the complaint about an empty comment is coded wrongly and should only occur when the comment is empty *and* no file is uploaded. Or maybe they want you to add a comment with your file -- that's fine too, but the error isn't very clear.
http or https made no difference. I used NS 4.72 on Linux; Tim used IE and had the same results.
BTW, this may be more pervasive: I recall that in the wee hours, I kept getting "ERROR: nothing changed" rejections when I was just trying to clean up old reports via doing nothing but changing the assigned-to (for example) dropdown list value. Perhaps they want a comment with every change of any kind now?
BTW, this may be more pervasive: I recall that in the wee hours, I kept getting "ERROR: nothing changed" rejections when I was just trying to clean up old reports via doing nothing but changing the assigned-to (for example) dropdown list value. Perhaps they want a comment with every change of any kind now?
Which in itself is not a bad policy. But the error sucks. --Guido van Rossum (home page: http://www.python.org/~guido/)
On Tue, Feb 27, 2001 at 05:34:06PM -0500, Andrew Kuchling wrote:
The SourceForge admins couldn't replicate the patch upload problem, and managed to attach a file to the Python bug report in question, yet when I try it, it still fails for me. So, a question for this list: has uploading patches or other files been working for you recently, particularly today? Maybe with more data, we can see a pattern (browser version, SSL/non-SSL, cluefulness of user, ...).
I still can't upload patch files (even though I always supply a comment). Specifically, I getting the following error message in red at the top of the page after pressing the "Submit Changes" button: ArtifactFile: File name, type, size, and data are RequiredSuccessfully Updated FWIW, I'm using Netscape 4.72 on Windows. Jason -- Jason Tishler Director, Software Engineering Phone: +1 (732) 264-8770 x235 Dot Hill Systems Corp. Fax: +1 (732) 264-8798 82 Bethany Road, Suite 7 Email: Jason.Tishler@dothill.com Hazlet, NJ 07730 USA WWW: http://www.dothill.com
On Tue, Feb 27, 2001 at 11:01:51PM -0500, Jason Tishler wrote:
I still can't upload patch files (even though I always supply a comment). Specifically, I getting the following error message in red at the top of the page after pressing the "Submit Changes" button:
Same here. It's not from leaving the comment field empty (I got the error message too and figured out what it meant); instead I can fill in a comment, select a file, and upload it. The comment shows up; the attachment doesn't (using NS4.75 on Linux). Anyone got other failures to report? --amk
participants (6)
-
Andrew Kuchling
-
Andrew Kuchling
-
Guido van Rossum
-
Jason Tishler
-
Michel Pelletier
-
Tim Peters