Bug 193170 – nopaste barfs on Xorg log

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Marijn Schouten (RETIRED) 2007-09-20 12:41:40 UTC]

$ nopaste ~/Xorg.0.log_nouveau_garbled_screen
/usr/lib64/ruby/1.8/net/protocol.rb:133:in `sysread': end of file reached (EOFError)
        from /usr/lib64/ruby/1.8/net/protocol.rb:133:in `rbuf_fill'
        from /usr/lib64/ruby/1.8/timeout.rb:56:in `timeout'
        from /usr/lib64/ruby/1.8/timeout.rb:76:in `timeout'
        from /usr/lib64/ruby/1.8/net/protocol.rb:132:in `rbuf_fill'
        from /usr/lib64/ruby/1.8/net/protocol.rb:116:in `readuntil'
        from /usr/lib64/ruby/1.8/net/protocol.rb:126:in `readline'
        from /usr/lib64/ruby/1.8/net/http.rb:2017:in `read_status_line'
        from /usr/lib64/ruby/1.8/net/http.rb:2006:in `read_new'
        from /usr/lib64/ruby/1.8/net/http.rb:1047:in `request'
        from /usr/lib64/ruby/1.8/net/http.rb:989:in `request_post'
        from /usr/bin/nopaste:71:in `nopaste'
        from /usr/lib64/ruby/1.8/net/http.rb:543:in `start'
        from /usr/lib64/ruby/1.8/net/http.rb:440:in `start'
        from /usr/bin/nopaste:69:in `nopaste'
        from /usr/bin/nopaste:106

[Comment 1 Marijn Schouten (RETIRED) 2007-09-20 12:44:57 UTC]

log too big to attach: http://dev.gentoo.org/~hkbst/Xorg.0.log_nouveau_garbled_screen

[Comment 2 Jakub Moc (RETIRED) 2007-09-20 12:46:14 UTC]

We should just punt this, no maintainer and wgetpaste replaces this without crazy ruby dependency.

[Comment 3 Markus Ullmann (RETIRED) 2007-09-20 12:48:27 UTC]

does rafb even accept such big (and mostly duplicated content) attachments?

[Comment 4 Santiago M. Mola (RETIRED) 2007-09-29 13:08:23 UTC]

(In reply to comment #2)
> We should just punt this, no maintainer and wgetpaste replaces this without
> crazy ruby dependency.
> 

Not so fast, wgetpaste has some weird behavior that needs to be fixed, and nopaste just works for most cases.

[Comment 5 Hans de Graaff 2007-11-04 12:47:49 UTC]

The error is caused by a time-out with the HTTP POST to rafb.net. Are you sure that this is not a transient error that depends on rafb.net being busy or other networking issues? 

Also, can you upload the same file to rafb.net using other means? I was going to try but then I noticed that the file is 2.4Mb in size... My guess is that your upload is too slow and you run into the default timeout because of that.

Frankly, this doesn't look like a bug to me, although nopaste should probably catch the timeout and display a nice message saying that posting doesn't currently work due to a timeout.

[Comment 6 Ryan Hill (RETIRED) 2007-11-04 16:47:40 UTC]

i would say don't post 2MiB of pointless log to rafb.  it works fine if you cut it in half.

Vote: --

[Comment 7 Samuli Suominen (RETIRED) 2007-11-04 17:16:57 UTC]

-1 from me too, not going anywhere

[Comment 8 Samuli Suominen (RETIRED) 2007-11-04 17:30:46 UTC]

See, http://rafb.net/paste/toobig.html

"Sorry, the file you have pasted is too large.
To prevent the disk filling up, pasted files may not exceed 10,000 lines or 800 KB."

But still, I've mailed agriffis, error message could be better.

[Comment 9 Bo Ørsted Andresen (RETIRED) 2007-11-04 18:32:45 UTC]

(In reply to comment #4)
> Not so fast, wgetpaste has some weird behavior that needs to be fixed, and
> nopaste just works for most cases.

Care to elaborate on that. Possibly in a new bug report.

[Comment 10 Samuli Suominen (RETIRED) 2007-11-08 16:13:25 UTC]

+*nopaste-2802 (08 Nov 2007)
+
+  08 Nov 2007; Samuli Suominen <[e-mail]> +nopaste-2802.ebuild:
+  Version bump with slightly better error handling wrt #193170, thanks to Aron
+  Griffis.

Quoting upstream:

"As far as I'm concerned, there's nothing wrong with an occasional
backtrace for exceptional conditions.  If people want everything
pretty and opaque, they should use a GUI."

I believe this bug is closed.