After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 362436 - Retrieving group list runs forever
Retrieving group list runs forever
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
pre-1.0 betas
Other Linux
: Normal normal
: 1.0
Assigned To: Charles Kerr
Pan QA Team
: 366051 366496 368790 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-15 18:53 UTC by Søren Boll Overgaard
Modified: 2006-11-01 10:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
0.117 patch (1.17 KB, patch)
2006-10-16 21:52 UTC, Charles Kerr
none Details | Review
0.117 patch (second draft) (4.01 KB, patch)
2006-10-18 20:04 UTC, Charles Kerr
none Details | Review

Description Søren Boll Overgaard 2006-10-15 18:53:53 UTC
Hi,

After upgrading to 0.116 (I can't be sure if it occurred in versions <0.116) pan consistently runs forever when getting a list of groups from my providers news server. It just hummed along nicely fetching headers, until i quit pan. At that time it had loaded some 250000 groups. My provider carries significantly less than 100000 groups.

I have attached the output of "pan --debug" with no preexisting ~/pan2/ directory. Additionally, I have attached the output of a telnet session with my news provider, showing (what I believe to be) the full list of groups carried (ie. the output of a "list newsgroups" command).
Comment 1 Søren Boll Overgaard 2006-10-15 21:41:38 UTC
It seems bugzilla doesn't like big files, so I am linking to them instead.
They are at:
http://soren.overgaard.org/stuff/pan.out.bz2 and
http://soren.overgaard.org/stuff/news-telnet.out.bz2
Comment 2 Charles Kerr 2006-10-16 21:25:47 UTC
I believe this is a side-effect of bug #361941, which is fixed in 0.117.
Also, I can't reproduce this in 0.117.

Could you give 0.117 a try and see if it fixes it?

Comment 3 Charles Kerr 2006-10-16 21:52:10 UTC
Created attachment 74843 [details] [review]
0.117 patch

Oh, I think I found it.  Could you give this patch a try, please?
Comment 4 Guilhèm Bonnefille 2006-10-18 08:06:51 UTC
No more succes with the patch. I applied it on the 0.117
version. Actually I have read 500,000 groups on each of my 4 servers.

I tried with a really small server (5 groups) and it succeed.
So, perhaps the bug is related to the number of groups?


Is it possible to "hack" pan in order to manually add the group lists? I do not need the 120,000 groups stored on the servers I'm interested in. Only around 10 or 20 groups. So, if it is possible, I will be able to do something with pan2 ;-)
Comment 5 Charles Kerr 2006-10-18 20:04:52 UTC
Created attachment 74972 [details] [review]
0.117 patch (second draft)

Give this one a try and see how it goes.

Patch should be applied to a freshly untarred 0.117.
Comment 6 Guilhèm Bonnefille 2006-10-18 20:40:28 UTC
I decided to hack the --debug output and the code. I found that the matter seems to be related to the TIMEOUTS. I'm actually trying without the g_timeout_add calls. Next, I will apply your patch, but I'm quite sure that we found the bug.

Wait and see.
Comment 7 Søren Boll Overgaard 2006-10-18 20:53:12 UTC
It appears to be working as intended. Nice.
Comment 8 Guilhèm Bonnefille 2006-10-18 21:22:31 UTC
The same for me. Nice job Charles.
Søren, feel free to keep me informed when you made the .deb. I'm ready to give it a try.

Thanks again for all.
Comment 9 Charles Kerr 2006-10-19 16:31:11 UTC
Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report.
Comment 10 Christophe Lambin 2006-10-28 08:11:41 UTC
*** Bug 366051 has been marked as a duplicate of this bug. ***
Comment 11 Christophe Lambin 2006-10-28 23:22:07 UTC
*** Bug 366496 has been marked as a duplicate of this bug. ***
Comment 12 Christophe Lambin 2006-11-01 10:31:10 UTC
*** Bug 368790 has been marked as a duplicate of this bug. ***