Gnutella Forums

Gnutella Forums (http://www.gnutellaforums.com/)
-   General Discussion (http://www.gnutellaforums.com/general-discussion/)
-   -   Bug Squashing Challenge! (open for users and devs) (http://www.gnutellaforums.com/general-discussion/34914-bug-squashing-challenge-open-users-devs.html)

arne_bab March 11th, 2005 03:36 AM

Bug Squashing Challenge! (open for users and devs)
 
Phex is nearing its first full release for almost 8 months, and I decided to take the chance to start some small game:

The

Bug Squashing Challenge


Rules of the game:

Everyone who finds a not-yet-known bug, gets one Spot-point.
Everyone who fixes a bug and submits the changes (either as patch or directly in cvs), gets one Squasher-point.

As soon as the release ships all points get added together and the one with the most points makes it into the Bug Squashing Hall of Fame and his or her name will stay there as long as the data lives on.


Hall of Fame
Release 2.2:
- Top Spotter: lokad
- Top Squatter. GregorK


All Bugs count!
(except those already in this thread and those in earlier versions)

We will keep track of the Bug-Spots and Squashes in this thread.
Naturally I am excluded from posting Bugs, but anyone can post Squashes.

A Spot must at the very least include the following information:

- What happened?
- Where did it happen (download-pane, preferences-network, etc)?
- Your Operating System (Windows XP/2000/98/95/...., MacOSX 10.1/10.2.6/10.3.8/..., Linux-version, other)
- Why did it Bug you? (did it cost time or did it destroy a precious download, or did it just look a bit strange? ... )
- How should we call you?

A Squash must include your Alias and an attached patch (or your cvs-Alias, so we can doublecheck).

The following Bugs are already too well known for reporting (so that noone just checks the database and wins even before the challenge starts - Squashing them still gives a point :) ):

- German localisation not yet complete
- Doesn't work behind my router/NAT (that's a configuration-thing for your router, but UPnP could help here someday)

Here comes the

Bug Squashing List

- Connections over SOCKS didn't work. Squashed by GregorK (in cvs by tonight).
- sizes / visibility of dialogs. Spotted by lokad - Squashed by GregorK


How far do you manage to get up in the Spot-Shqasher Ranking?
I'll update this Liste eveery few days, so you can always check your Score.
Can you get to the Top?

Bug-Squasher Ranking

1. Place: Gregork (0 / 2)
2. Place: lokad (1 / 0)
...


Now it's your time! Fire up Phex and sharpen your glasses, or get that good old Squasher of yours from the code-cabinet and go squashing!

(The most recent Beta of Phex can be downloaded here: http://phex.kouk.de/download.php )

GregorK March 11th, 2005 07:21 AM

Hey... I found and fixed one ;)

- What happened?
Connections over SOCKS5 server didnt work.

- Where did it happen?
Network, Download, Upload

- Your Operating System?
All

- Why did it Bug you?
I would not allow me to connect using SOCKS5

- How should we call you?
You can call me the BUG SQUASHER!
:D

Fix will be in CVS by tonight.

arne_bab March 11th, 2005 10:13 AM

So here comes the main Dev ;)
Does it suffice, if I count this as a Squash? :)

lokad March 21st, 2005 02:14 AM

sizes / visibility of dialogs
 
- What happened?
Dialogs where not visible and just partly visible after resizing. Then there was a huge space in the lower right corner and the component stuck in the upper left one (happened only once in each tested java version). The rows in the different tables are either too small or too wide (height) and also the pane headers, menu entries and menuitems are too high (height). This happened with blackdown-jdk-1.4.2.01, but not with sun-jdk-1.5.0.01 (ther was only _one time_ the prob that the really-shut-down-? dialog was only displayed after resizing it, never happened again)
- Where did it happen?
*Anywhere*
- Your Operating System
Linux 2.6.11 mm4
- Windowmanager
wmi-10
- Why did it Bug you?
It did just look a bit strange :)
- How should we call you?
lokad

Best regards lokad

lokad March 21st, 2005 02:19 AM

phex version and log
 
forgot: tested phex-2.4.8.82 precompiled (no ants running :)

[snip]
050321 09:49:22,0943:Error: java.net.SocketException: Socket closed
050321 09:49:23,0056:Error: java.lang.NullPointerException
050321 09:57:07,0913:Error: (Global)! Exception occured: java.lang.IllegalArgumentException: Non-positive period.
at java.util.Timer.schedule(Timer.java:221)
at phex.common.Environment.scheduleTimerTask(Unknown Source)
at phex.net.Server$FirewallCheckTimer.run(Unknown Source)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

050321 10:05:31,0576:Error: java.net.SocketException: Socket closed
050321 10:05:31,0577:Error: java.lang.NullPointerException
050321 10:08:29,0105:Error: java.io.IOException: Host access denied: xx.xx.xx.xx
050321 10:10:16,0448:Error: Missing language key: UseLogarithmicSliders


----
GregorK: Fixed in CVS

GregorK March 22nd, 2005 05:46 AM

This is a difficult bug to reproduce and to fix. Actually the plattform together with the Java VM and the selected Look and Feel (Skin) is responsible to layout the dialogs and elements.
You can try to use a different Look and Feel and check after a restart if there are still the same problems. It might be that certain Look and Feels behave wrong on some plattforms.
The Look and Feel controlls anything from component sizes, layout and fonts. Phex only uses thirdparty LaFs, like Plastic or the standard Java LaF Metal.


Quote:

Originally posted by lokad
- What happened?
Dialogs where not visible and just partly visible after resizing. Then there was a huge space in the lower right corner and the component stuck in the upper left one (happened only once in each tested java version). The rows in the different tables are either too small or too wide (height) and also the pane headers, menu entries and menuitems are too high (height). This happened with blackdown-jdk-1.4.2.01, but not with sun-jdk-1.5.0.01 (ther was only _one time_ the prob that the really-shut-down-? dialog was only displayed after resizing it, never happened again)
- Where did it happen?
*Anywhere*
- Your Operating System
Linux 2.6.11 mm4
- Windowmanager
wmi-10
- Why did it Bug you?
It did just look a bit strange :)
- How should we call you?
lokad

Best regards lokad



All times are GMT -7. The time now is 04:20 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.

Copyright 2015 Gnutella Forums.
All Rights Reserved.