m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas joined
m&mhas left
m and mhas joined
m and m
well, that was an interesting bug
m and m
how should I file swift bugs?
m and mhas left
m and mhas joined
Kev
Send them to me.
m and m
will do
Kev
Thanks.
m and mattempts to isolate from logs
m and m
sent
Kev
Ta.
Kev
m and m: Well, that's truly odd.
Kev
It shouldn't be going anywhere near any code that'd be doing that.
stpeter
yeah, interesting bug -- I saw that in other chatrooms he was in, too
Kev
It's receiving the 110 code, seeing that the nick isn't what it expects and updates itself.
stpeter
ah
Kev
The question is why it decided that the nick wasn't the same.
stpeter
right
stpeter
escaping madness?
Kev
Yes, but why?
foo&barhas joined
foo&bar
hmm
foo&bar
what version was he running?
Kev
Goodness knows.
Kev
I'm going to guess not latest.
Tobiashas joined
m and m
1.0.10, thought I put that in the email...
Kev
Oh, so you did. I skipped it because that's not a Swift version.
Kev
So 1.0 then, I guess.
m and m
sorry, yes ... not sure where I got the .10 from
m and m
oh, the dmg name is Swift-1.0-10.6 ... I must have transposed - to .
now, to figure out why my prosody server dislikes saving vCard-based avatars...
Kev
Size limit? Don't have the vcard plugin installed/configured? (If you need such a thing)
m&m
I do have the vcard plugin installed, and my avatar is 6K @ 64x64 pixels ... well within the stated limits in XEP-0084
m&m
The error message is the cryptic "Client Disconnected: Invalid Argument"
Kev
Swift bug?
m&m
no, it happens with Adium, InstantBird, and PSI
MattJ
m&m, er, same message in each?
m&m
yes
MattJ
Not the kind of error message we'd come up with
MattJ
But I have an idea... do you have compression enabled?
m&m
mmm ... let me check
m&m
no
MattJ
Very strange
MattJ
Try enabling debug logging in Prosody, it should shed some light on where the error originates at least
m&m
bbs
m&mhas left
m&mhas joined
m&mhas left
m&mhas joined
m&mhas left
m&mhas joined
m&m
hrmph
m&m
did not even parse it...
May 25 15:23:02 socket debug server.lua: client 64.101.72.30:51270 read error: Invalid argument
May 25 15:23:02 c2s97d2ed0 info Client disconnected: Invalid argument
May 25 15:23:02 c2s97d2ed0 info Destroying session for linuxwolf@outer-planes.net/59b79eb1-ccfa-479f-b7ff-189b0a5790d7 (linuxwolf@outer-planes.net)
MattJ
What kind of system is it running on?
MattJ
Also, check your error log
m&m
Linux (Fedora 15)
[linuxwolf@li115-220 ~]$ uname -a
Linux li115-220 3.0.18-linode43 #1 SMP Mon Jan 30 11:44:09 EST 2012 i686 i686 i386 GNU/Linux
m&m
/sigh
MattJ
Thought so
m&mturns on error logging
MattJ
Wait, what?
m&m
log = {
{ levels = { min = "debug" }, to = "file", filename = "/usr/local/var/lib/prosody/log.txt"};
-- Change 'info' to 'debug' for verbose logging
-- error = "/usr/local/var/lib/prosody/err.txt";
-- "*syslog"; -- Uncomment this for logging to syslog
-- "*console"; -- Log to the console, useful for debugging with daemonize=false
}