Skip to content
This repository has been archived by the owner on Jun 30, 2022. It is now read-only.

Presence update blows up bot #37

Open
moos3 opened this issue Feb 15, 2016 · 0 comments
Open

Presence update blows up bot #37

moos3 opened this issue Feb 15, 2016 · 0 comments

Comments

@moos3
Copy link

moos3 commented Feb 15, 2016

Lita crashes and burns every time there's a presence update. Anyone else seeing this in version 4.0 ?

Lita.configure do |config|
  config.robot.name = "Lita Bot Development"
  config.robot.mention_name = "litadev"
  config.http.host = "0.0.0.0"
  config.http.port = "8080"
  config.robot.alias = "!"
  config.robot.adapter = :hipchat
  config.adapters.hipchat.jid = "92512_********@chat.hipchat.com"
  config.adapters.hipchat.password = "**********"
  config.adapters.hipchat.debug = true
  config.adapters.hipchat.rooms = :all
  config.redis[:host] = "127.0.0.1"
  config.handlers.karma.cooldown = 300
  config.handlers.pagerduty.api_key   = ''
  config.handlers.pagerduty.subdomain = ''
end
D, [2016-02-15T14:39:44.445733 #7083] DEBUG -- : TRYING message/iq/presence/cbs...
D, [2016-02-15T14:40:16.097885 #7083] DEBUG -- : RECEIVED:
    <presence from='[email protected]/mobile_proxy|pubproxy-d100.hipchat.com|5272_proxy|pubproxy-c100.hipchat.com|5232_proxy|pubproxy-b100.hipchat.com|5242_proxy|pubproxy-c100.hipchat.com|5252_proxy|pubproxy-c100.hipchat.com|5292_proxy|pubproxy-b100.hipchat.com|5232_proxy|pubproxy-d100.hipchat.com|5262_proxy|pubproxy-b100.hipchat.com|5232_proxy|pubproxy-b100.hipchat.com|5232_proxy|pubproxy-b100.hipchat.com|5242_proxy|pubproxy-b100.hipchat.com|5232_proxy|pubproxy-d100.hipchat.com|5292_proxy|pubproxy-c100.hipchat.com|5252_proxy|pubproxy-d100.hipchat.com|5272_proxy|pubproxy-b100.hipchat.com|5272_proxy|pubproxy-c100.hipchat.com|5292_proxy|pubproxy-c100.hipchat.com|5232_proxy|pubproxy-c100.hipchat.com|5292_proxy|pubproxy-b100.hipchat.com|5272_proxy|pubproxy-b100.hipchat.com|5272_proxy|pubproxy-c100.hipchat.com|5292_proxy|pubproxy-b100.hipchat.com|5272_proxy|pubproxy-b100.hipchat.com|5232_proxy|pubproxy-b100.hipchat.com|5292_proxy|pubproxy-d100.hipchat.com|5272_proxy|pubproxy-c100.hipchat.com|5292_proxy|pubproxy-d100.hipchat.com|5282||proxy|pubproxy-b100.hipchat.com|5252' to='[email protected]/bot||proxy|pubproxy-d100.hipchat.com|5262' type='unavailable'><mobile type='sms' xmlns='http://hipchat.com/protocol/presence'/></presence>
D, [2016-02-15T14:40:16.098878 #7083] DEBUG -- : PROCESSING:
    <presence from='[email protected]/mobile_proxy|pubproxy-d100.hipchat.com|5272_proxy|pubproxy-c100.hipchat.com|5232_proxy|pubproxy-b100.hipchat.com|5242_proxy|pubproxy-c100.hipchat.com|5252_proxy|pubproxy-c100.hipchat.com|5292_proxy|pubproxy-b100.hipchat.com|5232_proxy|pubproxy-d100.hipchat.com|5262_proxy|pubproxy-b100.hipchat.com|5232_proxy|pubproxy-b100.hipchat.com|5232_proxy|pubproxy-b100.hipchat.com|5242_proxy|pubproxy-b100.hipchat.com|5232_proxy|pubproxy-d100.hipchat.com|5292_proxy|pubproxy-c100.hipchat.com|5252_proxy|pubproxy-d100.hipchat.com|5272_proxy|pubproxy-b100.hipchat.com|5272_proxy|pubproxy-c100.hipchat.com|5292_proxy|pubproxy-c100.hipchat.com|5232_proxy|pubproxy-c100.hipchat.com|5292_proxy|pubproxy-b100.hipchat.com|5272_proxy|pubproxy-b100.hipchat.com|5272_proxy|pubproxy-c100.hipchat.com|5292_proxy|pubproxy-b100.hipchat.com|5272_proxy|pubproxy-b100.hipchat.com|5232_proxy|pubproxy-b100.hipchat.com|5292_proxy|pubproxy-d100.hipchat.com|5272_proxy|pubproxy-c100.hipchat.com|5292_proxy|pubproxy-d100.hipchat.com|5282||proxy|pubproxy-b100.hipchat.com|5252' to='[email protected]/bot||proxy|pubproxy-d100.hipchat.com|5262' type='unavailable' xmlns='jabber:client'><mobile type='sms' xmlns='http://hipchat.com/protocol/presence'/></presence> (Jabber::Presence)
D, [2016-02-15T14:40:16.099119 #7083] DEBUG -- : TRYING stanzacbs...
D, [2016-02-15T14:40:16.099153 #7083] DEBUG -- : TRYING message/iq/presence/cbs...
W, [2016-02-15T14:40:16.099436 #7083]  WARN -- : EXCEPTION:
    Jabber::ArgumentError
    Resource too long
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/gems/2.1.0/gems/xmpp4r-0.5.6/lib/xmpp4r/jid.rb:45:in `initialize'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/gems/2.1.0/gems/xmpp4r-0.5.6/lib/xmpp4r/xmppstanza.rb:92:in `new'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/gems/2.1.0/gems/xmpp4r-0.5.6/lib/xmpp4r/xmppstanza.rb:92:in `from'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/gems/2.1.0/gems/xmpp4r-0.5.6/lib/xmpp4r/muc/helper/mucclient.rb:369:in `block in activate'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/gems/2.1.0/gems/xmpp4r-0.5.6/lib/xmpp4r/callbacks.rb:99:in `call'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/gems/2.1.0/gems/xmpp4r-0.5.6/lib/xmpp4r/callbacks.rb:99:in `block in process'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/gems/2.1.0/gems/xmpp4r-0.5.6/lib/xmpp4r/callbacks.rb:98:in `each'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/gems/2.1.0/gems/xmpp4r-0.5.6/lib/xmpp4r/callbacks.rb:98:in `process'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/gems/2.1.0/gems/xmpp4r-0.5.6/lib/xmpp4r/stream.rb:281:in `receive'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/gems/2.1.0/gems/xmpp4r-0.5.6/lib/xmpp4r/streamparser.rb:74:in `block in parse'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/2.1.0/rexml/parsers/sax2parser.rb:142:in `call'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/2.1.0/rexml/parsers/sax2parser.rb:142:in `block in parse'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/2.1.0/rexml/parsers/sax2parser.rb:142:in `each'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/2.1.0/rexml/parsers/sax2parser.rb:142:in `parse'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/gems/2.1.0/gems/xmpp4r-0.5.6/lib/xmpp4r/streamparser.rb:91:in `parse'
    /Users/moose/.rbenv/versions/2.1.8/lib/ruby/gems/2.1.0/gems/xmpp4r-0.5.6/lib/xmpp4r/stream.rb:75:in `block in start'
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant