XMPP Council - 2012-05-25

well, that was an interesting bug

how should I file swift bugs?

Send them to me.

will do

Thanks.

sent

Ta.

m and m: Well, that's truly odd.

It shouldn't be going anywhere near any code that'd be doing that.

yeah, interesting bug -- I saw that in other chatrooms he was in, too

It's receiving the 110 code, seeing that the nick isn't what it expects and updates itself.

ah

The question is why it decided that the nick wasn't the same.

right

escaping madness?

Yes, but why?

hmm

what version was he running?

Goodness knows.

I'm going to guess not latest.

1.0.10, thought I put that in the email...

Oh, so you did. I skipped it because that's not a Swift version.

So 1.0 then, I guess.

sorry, yes ... not sure where I got the .10 from

oh, the dmg name is Swift-1.0-10.6 ... I must have transposed - to .

Ah.

http://swift.im/downloads/releases/swift-2.0beta1/Swift-2.0beta1.dmg

already downloaded (-:

well, it's fixed in beta!

now, to figure out why my prosody server dislikes saving vCard-based avatars...

Size limit? Don't have the vcard plugin installed/configured? (If you need such a thing)

I do have the vcard plugin installed, and my avatar is 6K @ 64x64 pixels ... well within the stated limits in XEP-0084

The error message is the cryptic "Client Disconnected: Invalid Argument"

Swift bug?

no, it happens with Adium, InstantBird, and PSI

m&m, er, same message in each?

yes

Not the kind of error message we'd come up with

But I have an idea... do you have compression enabled?

mmm ... let me check

no

Very strange

Try enabling debug logging in Prosody, it should shed some light on where the error originates at least

bbs

hrmph

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)

What kind of system is it running on?

Also, check your error log

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

/sigh

Thought so

Wait, what?

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 }

What version of Prosody is it?

0.8.2

That looks like config soup from various versions

hrm

log = { debug = "/usr/local/var/lib/prosody/log.txt"; error = "/usr/local/var/lib/prosody/err.txt"; }

/-: -rw-r----- 1 prosody prosody 0 May 25 15:30 err.txt

maybe I'll build and install 0.9 this weekend

0.9's out?

no ... but I'm willing to be brave (-:

someone needs to disable "avanlindt@sophialegal.com" on the jdev@jabber.org list pronto!

NN

No, you're not my Dad.

No, Kev - *I* am your father.

Oh, now it all makes sense