From der_julian at web.de  Tue Jan  3 17:08:52 2006
From: der_julian at web.de (Julian Stecklina)
Date: Tue, 3 Jan 2006 18:08:52 +0100
Subject: [cl-xmpp-devel] upgrade to cxml cvs
In-Reply-To: <58f839b70512311154g72a14344h6f5ba2e32cb8f2fd@mail.gmail.com>
References: <20051230144741.GA25603@gargravarr.knowledgetools.de>
	<58f839b70512311154g72a14344h6f5ba2e32cb8f2fd@mail.gmail.com>
Message-ID: <20060103180852.12d57277@localhost>

On Sat, 31 Dec 2005 14:54:03 -0500
Erik Enge <erik.enge at gmail.com> wrote:

> On 12/30/05, David Lichteblau <david at lichteblau.com> wrote:
> > attached changes for cxml cvs.
> 
> Thanks for the patch!
> 
> I've applied it and it's looking ok.

I get 

Package "CXML-DOM" not found. [file position = 354]
   [Condition of type READER-ERROR]

in cxml.lisp.

Regards,
-- 
Julian Stecklina

When someone says "I want a programming language in which I
need only say what I wish done," give him a lollipop. - Alan Perlis


From erik.enge at gmail.com  Tue Jan  3 17:10:12 2006
From: erik.enge at gmail.com (Erik Enge)
Date: Tue, 3 Jan 2006 12:10:12 -0500
Subject: [cl-xmpp-devel] upgrade to cxml cvs
In-Reply-To: <20060103180852.12d57277@localhost>
References: <20051230144741.GA25603@gargravarr.knowledgetools.de>
	<58f839b70512311154g72a14344h6f5ba2e32cb8f2fd@mail.gmail.com>
	<20060103180852.12d57277@localhost>
Message-ID: <58f839b70601030910r2ca7c05eq998da72b3e57a7c1@mail.gmail.com>

On 1/3/06, Julian Stecklina <der_julian at web.de> wrote:
> I get
>
> Package "CXML-DOM" not found. [file position = 354]
>    [Condition of type READER-ERROR]
>
> in cxml.lisp.

Try cxml CVS; David has announced there will be a new release of cxml
soon and CVS cl-xmpp expects it.

Thanks,
Erik.


From adam.thorsen at gmail.com  Sun Jan  8 02:01:42 2006
From: adam.thorsen at gmail.com (Adam Thorsen)
Date: Sat, 7 Jan 2006 18:01:42 -0800
Subject: [cl-xmpp-devel] request-subscription problem
Message-ID: <290f54b70601071801kbcb0843r993bc5375a3f7aed@mail.gmail.com>

I am trying to call request-subscription, then restart the
receive-stanza loop, like so:

(defun subscribe(user-uid expert-jid)
  (let ((connection (get-connection user-uid)))
  (xmpp:request-subscription connection expert-jid)
  (sb-thread:make-thread (lambda () (xmpp:receive-stanza-loop connection))))
  )

However, I get the error below.  I looked at cl-xmpp:make-error -
there is indeed no way to call it with a (nil) argument.  I tried to
define a method that would but I was told that the generic function
declaration wouldn't allow it.  Any ideas what's going wrong?

There is no applicable method for the generic function
  #<STANDARD-GENERIC-FUNCTION CL-XMPP::MAKE-ERROR (1)>
when called with arguments
  (NIL).
   [Condition of type SIMPLE-ERROR]

Restarts:
  0: [TERMINATE-THREAD] Terminate this thread (#<THREAD {94F4359}>)

Backtrace:
  0: ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) #<unavailable
argument> #<unavailable argument> #<STANDARD-GENERIC-FUNCTION
CL-XMPP::MAKE-ERROR (1)> (NIL))
  1: ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) #<unavailable
argument> #<unavailable argument> #<STANDARD-GENERIC-FUNCTION
CL-XMPP::MAKE-ERROR (1)> (NIL))
  2: (SB-KERNEL:%MAP-TO-LIST-ARITY-1 #<CLOSURE (LAMBDA (CL-XMPP::X))
{950891D}> (#<CL-XMPP:XML-ELEMENT IQ (4attr:1child:0data) {95084F9}>))
  3: (CL-XMPP::DEFAULT-STANZA-CALLBACK #<DOM-IMPL::DOCUMENT {9504E21}>
#<CL-XMPP:CONNECTION to guruza.com:5222 (open) {946D881}> :DOM-REPR
NIL)
  4: ((SB-PCL::FAST-METHOD CL-XMPP:RECEIVE-STANZA
(CL-XMPP:CONNECTION)) #<unavailable argument> #<unavailable argument>
#<CL-XMPP:CONNECTION to guruza.com:5222 (open) {946D881}>
(:STANZA-CALLBACK CL-XMPP::DEFAULT-STANZA-CALLBACK :DOM-REPR NIL))
  5: ((SB-PCL::FAST-METHOD CL-XMPP:RECEIVE-STANZA-LOOP
(CL-XMPP:CONNECTION)) #<unavailable argument> #<unavailable argument>
#<CL-XMPP:CONNECTION to guruza.com:5222 (open) {946D881}> NIL)
  6: ((SB-PCL::FAST-METHOD CL-XMPP:RECEIVE-STANZA-LOOP
(CL-XMPP:CONNECTION)) #<unavailable argument> #<unavailable argument>
#<CL-XMPP:CONNECTION to guruza.com:5222 (open) {946D881}> NIL)
  7: ((LAMBDA NIL))
  8: ("foreign function: call_into_lisp")
  9: ("foreign function: funcall0")
 10: ("foreign function: new_thread_trampoline")
 11: ("foreign function: #xB7FD5ABA")


From erik.enge at gmail.com  Sun Jan  8 02:16:40 2006
From: erik.enge at gmail.com (Erik Enge)
Date: Sat, 7 Jan 2006 21:16:40 -0500
Subject: [cl-xmpp-devel] request-subscription problem
In-Reply-To: <290f54b70601071801kbcb0843r993bc5375a3f7aed@mail.gmail.com>
References: <290f54b70601071801kbcb0843r993bc5375a3f7aed@mail.gmail.com>
Message-ID: <58f839b70601071816t7f465506la999739b6a3da81f@mail.gmail.com>

On 1/7/06, Adam Thorsen <adam.thorsen at gmail.com> wrote:
> However, I get the error below.  I looked at cl-xmpp:make-error -
> there is indeed no way to call it with a (nil) argument.  I tried to
> define a method that would but I was told that the generic function
> declaration wouldn't allow it.  Any ideas what's going wrong?

I think this stems for me not testing the previous patches well
enough.  I suspect that we introduced a bug in xml-element-to-event
somewhere which results in this.  I'll try and find out over the
weekend and let you know (busy right now setting up the new server for
clnet, sorry).

Thanks,
Erik.


From adam.thorsen at gmail.com  Sun Jan 15 21:45:06 2006
From: adam.thorsen at gmail.com (Adam Thorsen)
Date: Sun, 15 Jan 2006 13:45:06 -0800
Subject: [cl-xmpp-devel] error handling issue
Message-ID: <290f54b70601151345t28f8c830x620dbb3f347963d9@mail.gmail.com>

I'm trying to write some code to join a MUC using cl-xmpp.  Of course,
I screwed up and sent a message to the server that generated an error
from the server:

#<PRESENCE from:testroom1 at conference.shiva.guruza.com/web-chat
show:NIL {9418071}>
>><message from='testroom1 at shiva.guruza.com'
to='stranger at shiva.guruza.com/web-chat' type='error'><x
xmlns='&apos';http://jabber.org/protocol/muc#user&apos;'><invite
to='awt at shiva.guruza.com'><reason>You have been invited to help a
user.</reason></invite></x><error code='503'
type='cancel'><service-unavailable
xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></message

Well, somehow this message causes the exception below.  Now, I know
that I am not calling GET-ELEMENT, but for some reason CL-XMPP is, and
it is calling it on some empty value that it shouldn't be.  I looked
at the defmethod for get-element, and there is indeed no method to
handle this case.  How can I fix this?

Thanks,
-Adam

There is no applicable method for the generic function
  #<STANDARD-GENERIC-FUNCTION CL-XMPP:GET-ELEMENT (1)>
when called with arguments
  (NIL :|#TEXT|).
   [Condition of type SIMPLE-ERROR]

Restarts:
  0: [TERMINATE-THREAD] Terminate this thread (#<THREAD {9402E91}>)

Backtrace:
  0: ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) #<unavailable
argument> #<unavailable argument> #<STANDARD-GENERIC-FUNCTION
CL-XMPP:GET-ELEMENT (1)> (NIL :|#TEXT|))
  1: ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) #<unavailable
argument> #<unavailable argument> #<STANDARD-GENERIC-FUNCTION
CL-XMPP:GET-ELEMENT (1)> (NIL :|#TEXT|))
  2: ((SB-PCL::FAST-METHOD CL-XMPP::XML-ELEMENT-TO-EVENT
(CL-XMPP:CONNECTION CL-XMPP:XML-ELEMENT (EQL :MESSAGE))) #<unavailable
argument> #<unavailable argument> #<unavailable argument>
#<CL-XMPP:XML-ELEMENT MESSAGE (3attr:2child:0data) {9CCE9A1}>
#<unavailable argument>)
  3: (SB-KERNEL:%MAP-TO-LIST-ARITY-1 #<CLOSURE (LAMBDA (CL-XMPP::X))
{9CCF1E5}> (#<CL-XMPP:XML-ELEMENT MESSAGE (3attr:2child:0data)
{9CCE9A1}>))
  4: (CL-XMPP::DEFAULT-STANZA-CALLBACK #<RUNE-DOM::DOCUMENT {9C04511}>
#<CL-XMPP:CONNECTION to shiva.guruza.com:5222 (open) {AA308F9}>
:DOM-REPR NIL)
  5: ((SB-PCL::FAST-METHOD CL-XMPP:RECEIVE-STANZA
(CL-XMPP:CONNECTION)) #<unavailable argument> #<unavailable argument>
#<CL-XMPP:CONNECTION to shiva.guruza.com:5222 (open) {AA308F9}>
(:STANZA-CALLBACK CL-XMPP::DEFAULT-STANZA-CALLBACK :DOM-REPR NIL))
  6: ((SB-PCL::FAST-METHOD CL-XMPP:RECEIVE-STANZA-LOOP
(CL-XMPP:CONNECTION)) #<unavailable argument> #<unavailable argument>
#<CL-XMPP:CONNECTION to shiva.guruza.com:5222 (open) {AA308F9}> NIL)
  7: ((SB-PCL::FAST-METHOD CL-XMPP:RECEIVE-STANZA-LOOP
(CL-XMPP:CONNECTION)) #<unavailable argument> #<unavailable argument>
#<CL-XMPP:CONNECTION to shiva.guruza.com:5222 (open) {AA308F9}> NIL)
  8: ((LAMBDA NIL))


From root at common-lisp.net  Wed Jan 18 16:23:28 2006
From: root at common-lisp.net (root)
Date: Wed, 18 Jan 2006 10:23:28 -0600 (CST)
Subject: [cl-xmpp-devel] Auto-nag: cl-xmpp link verifier failed
Message-ID: <20060118162328.5B1401580D@common-lisp.net>

You are being nagged on because your project's
name showed up in the nightly Checkbot run.  Checkbot checks
for broken links etc.  This probably means that you are 
either pointing to a broken link or that someone is pointing
to a broken link on your site.  Or something else, it check's
a bunch of stuff.  Update your webpages or you shall be nagged
again next week.

To find out what's wrong with your webpages, please consult:

  http://common-lisp.net/checkbot/checkbot-common-lisp.net.html

Any questions?  You can reach the author of this cronjob at
admin at common-lisp.net

Thanks!


From adam.thorsen at gmail.com  Mon Jan 23 01:08:25 2006
From: adam.thorsen at gmail.com (Adam Thorsen)
Date: Sun, 22 Jan 2006 17:08:25 -0800
Subject: [cl-xmpp-devel] Trouble with escapes
Message-ID: <290f54b70601221708q2389e860idd23d7d6d6f70c29@mail.gmail.com>

This is probably a question for cxml, but I thought I'd check with you
(Erik) first.  CXML appears to have trouble parsing escaped
characters.  For example, when calling read-stanza on a stream that
contains &apos, I get the stacktrace below.  It also happens when I
send messages containing single quotes, double quotes, and ampersands.

I can see from the stacktrace that cxml is trying to process the
&apos;, but something is throwing it off.

Here is the debug output from cl-xmpp (just to show how far the parser gets):
<message from='awt at shiva.guruza.com/Psi' to='gernika at shiva.guruza.com'
type='chat' id='ac28a'>
<body>hey man what is up &apos

Any ideas?

The value NIL is not of type CXML::STREAM-NAME.
   [Condition of type TYPE-ERROR]

Restarts:
  0: [ABORT] Abort handling SLIME request.
  1: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread"
{A9B56E9}>)

Backtrace:
  0: ((LAMBDA (CXML::X)) #<RUNES:XSTREAM NIL>)
  1: (SB-KERNEL:%FIND-POSITION-IF #<CLOSURE (LAMBDA (CXML::X))
{934768D}> (:STOP #<RUNES:XSTREAM NIL>) NIL 0 NIL #<FUNCTION
IDENTITY>)
  2: (CXML::ZSTREAM-PUSH #<RUNES:XSTREAM [apos :GENERAL NIL]>
#S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK
(:STOP #<RUNES:XSTREAM NIL>)))
  3: ((LAMBDA (CXML::NEW-XSTREAM)) #<RUNES:XSTREAM [apos :GENERAL NIL]>)
  4: (CXML::CALL-WITH-ENTITY-EXPANSION-AS-STREAM #S(CXML::ZSTREAM
:TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK (:STOP
#<RUNES:XSTREAM NIL>)) #<CLOSURE (LAMBDA (CXML::NEW-XSTREAM))
{9347605}> "apos" :GENERAL NIL)
  5: (CXML::P/CONTENT #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL
:TOKEN-SEMANTIC NIL :INPUT-STACK (:STOP #<RUNES:XSTREAM NIL>)))
  6: (CXML::P/ELEMENT #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL
:TOKEN-SEMANTIC NIL :INPUT-STACK (:STOP #<RUNES:XSTREAM NIL>)))
  7: (CXML::P/CONTENT #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL
:TOKEN-SEMANTIC NIL :INPUT-STACK (:STOP #<RUNES:XSTREAM NIL>)))
  8: (CXML::P/ELEMENT #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL
:TOKEN-SEMANTIC NIL :INPUT-STACK (:STOP #<RUNES:XSTREAM NIL>)))
  9: (CXML::P/DOCUMENT #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL
:TOKEN-SEMANTIC NIL :INPUT-STACK (:STOP #<RUNES:XSTREAM NIL>))
#<CL-XMPP::STANZA-HANDLER {92D7C99}> :VALIDATE NIL :DTD NIL :ROOT NIL
:ENTITY-RESOLVER NIL :DISALLOW-INTERNAL-SUBSET NIL :RECODE T)
 10: (CXML::PARSE-XSTREAM #<RUNES:XSTREAM NIL>
#<CL-XMPP::STANZA-HANDLER {92D7C99}>)
 11: (CL-XMPP::READ-STANZA #<CL-XMPP:CONNECTION to
shiva.guruza.com:5222 (open) {91462D9}>)
 12: ((SB-PCL::FAST-METHOD CL-XMPP:RECEIVE-STANZA
(CL-XMPP:CONNECTION)) #<unavailable argument> #<unavailable argument>
#<CL-XMPP:CONNECTION to shiva.guruza.com:5222 (open) {91462D9}> NIL)
 13: (SB-INT:EVAL-IN-LEXENV (CL-XMPP:RECEIVE-STANZA (GET-CONNECTION
20)) #<NULL-LEXENV>)


From erik.enge at gmail.com  Mon Jan 23 03:31:09 2006
From: erik.enge at gmail.com (Erik Enge)
Date: Sun, 22 Jan 2006 22:31:09 -0500
Subject: [cl-xmpp-devel] Trouble with escapes
In-Reply-To: <290f54b70601221708q2389e860idd23d7d6d6f70c29@mail.gmail.com>
References: <290f54b70601221708q2389e860idd23d7d6d6f70c29@mail.gmail.com>
Message-ID: <58f839b70601221931h4e36b3e8t57ca98ece151e2b5@mail.gmail.com>

On 1/22/06, Adam Thorsen <adam.thorsen at gmail.com> wrote:
> Any ideas?

I haven't tried to reproduce this, but off the top of my head it does
look like cxml is having a hiccup, not cl-xmpp.  To make sure that's
the case, try to reproduce this without even loading cl-xmpp into your
Lisp and boil it down to the smallest example which still produces
that error.  Then send that to cxml-devel and see what they say.

Thanks,
Erik.


From david at lichteblau.com  Mon Jan 23 10:37:02 2006
From: david at lichteblau.com (David Lichteblau)
Date: Mon, 23 Jan 2006 11:37:02 +0100
Subject: [cl-xmpp-devel] Trouble with escapes
In-Reply-To: <58f839b70601221931h4e36b3e8t57ca98ece151e2b5@mail.gmail.com>
References: <290f54b70601221708q2389e860idd23d7d6d6f70c29@mail.gmail.com>
	<58f839b70601221931h4e36b3e8t57ca98ece151e2b5@mail.gmail.com>
Message-ID: <20060123103702.GB7175@gargravarr.knowledgetools.de>

Quoting Erik Enge (erik.enge at gmail.com):
> On 1/22/06, Adam Thorsen <adam.thorsen at gmail.com> wrote:
> > Any ideas?
> 
> I haven't tried to reproduce this, but off the top of my head it does
> look like cxml is having a hiccup, not cl-xmpp.  To make sure that's
> the case, try to reproduce this without even loading cl-xmpp into your
> Lisp and boil it down to the smallest example which still produces
> that error.  Then send that to cxml-devel and see what they say.

Since I don't have a working lisp+cxml+cl-xmpp installation around to
test this right now, here's a blind guess at a patch that might address
the problem.

Does this help?


d.
-------------- next part --------------
Index: cl-xmpp.lisp
===================================================================
RCS file: /project/cl-xmpp/cvsroot/cl-xmpp/cl-xmpp.lisp,v
retrieving revision 1.24
diff -u -u -u -r1.24 cl-xmpp.lisp
--- cl-xmpp.lisp	31 Dec 2005 20:15:06 -0000	1.24
+++ cl-xmpp.lisp	23 Jan 2006 10:27:01 -0000
@@ -316,7 +316,12 @@
 (defun read-stanza (connection)
   (unless (server-xstream connection)
     (setf (server-xstream connection)
-          (cxml:make-xstream (make-slow-stream (server-stream connection)))))
+          (cxml:make-xstream (make-slow-stream (server-stream connection))
+			     :name
+			     (cxml::make-stream-name
+			      :entity-name "stanza"
+			      :entity-kind :main
+			      :uri nil))))
   (force-output (server-stream connection))
   (catch 'stanza
     (let ((cxml::*namespace-bindings*

From adam.thorsen at gmail.com  Mon Jan 23 15:24:24 2006
From: adam.thorsen at gmail.com (Adam Thorsen)
Date: Mon, 23 Jan 2006 07:24:24 -0800
Subject: [cl-xmpp-devel] Trouble with escapes
In-Reply-To: <20060123103702.GB7175@gargravarr.knowledgetools.de>
References: <290f54b70601221708q2389e860idd23d7d6d6f70c29@mail.gmail.com>
	<58f839b70601221931h4e36b3e8t57ca98ece151e2b5@mail.gmail.com>
	<20060123103702.GB7175@gargravarr.knowledgetools.de>
Message-ID: <290f54b70601230724y256346fbi4e5156562b55a970@mail.gmail.com>

David, preliminary testing indicates that your patch indeed fixed the
problem.  My next task is to understand how :)

Thanks a lot.

-Adam

On 1/23/06, David Lichteblau <david at lichteblau.com> wrote:
> Quoting Erik Enge (erik.enge at gmail.com):
> > On 1/22/06, Adam Thorsen <adam.thorsen at gmail.com> wrote:
> > > Any ideas?
> >
> > I haven't tried to reproduce this, but off the top of my head it does
> > look like cxml is having a hiccup, not cl-xmpp.  To make sure that's
> > the case, try to reproduce this without even loading cl-xmpp into your
> > Lisp and boil it down to the smallest example which still produces
> > that error.  Then send that to cxml-devel and see what they say.
>
> Since I don't have a working lisp+cxml+cl-xmpp installation around to
> test this right now, here's a blind guess at a patch that might address
> the problem.
>
> Does this help?
>
>
> d.
>
>
> _______________________________________________
> cl-xmpp-devel mailing list
> cl-xmpp-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/cl-xmpp-devel
>
>
>
>


From erik.enge at gmail.com  Mon Jan 23 16:45:54 2006
From: erik.enge at gmail.com (Erik Enge)
Date: Mon, 23 Jan 2006 11:45:54 -0500
Subject: [cl-xmpp-devel] Trouble with escapes
In-Reply-To: <290f54b70601230724y256346fbi4e5156562b55a970@mail.gmail.com>
References: <290f54b70601221708q2389e860idd23d7d6d6f70c29@mail.gmail.com>
	<58f839b70601221931h4e36b3e8t57ca98ece151e2b5@mail.gmail.com>
	<20060123103702.GB7175@gargravarr.knowledgetools.de>
	<290f54b70601230724y256346fbi4e5156562b55a970@mail.gmail.com>
Message-ID: <58f839b70601230845m58017fe2t3afbe15557291c2@mail.gmail.com>

On 1/23/06, Adam Thorsen <adam.thorsen at gmail.com> wrote:
> David, preliminary testing indicates that your patch indeed fixed the
> problem.  My next task is to understand how :)

I committed this patch to CVS, thanks!

Erik.


From erik.enge at gmail.com  Thu Jan 26 15:46:09 2006
From: erik.enge at gmail.com (Erik Enge)
Date: Thu, 26 Jan 2006 10:46:09 -0500
Subject: [cl-xmpp-devel] error handling issue
In-Reply-To: <290f54b70601151345t28f8c830x620dbb3f347963d9@mail.gmail.com>
References: <290f54b70601151345t28f8c830x620dbb3f347963d9@mail.gmail.com>
Message-ID: <58f839b70601260746r184fe195w977d82d4398c7a4f@mail.gmail.com>

On 1/15/06, Adam Thorsen <adam.thorsen at gmail.com> wrote:
> Well, somehow this message causes the exception below.  Now, I know
> that I am not calling GET-ELEMENT, but for some reason CL-XMPP is, and
> it is calling it on some empty value that it shouldn't be.  I looked
> at the defmethod for get-element, and there is indeed no method to
> handle this case.  How can I fix this?

It looks to me like this message has no body.  See line 284 in
cl-xmpp.lisp; I think that's where this problem happens (although I
haven't had the time to check and verify this).  You could
conditionalize that call on whether or not the message actually have a
body.

Erik.