May be incompatible with hubot@3?
See original GitHub issueI was just trying to upgrade all my hubot things, and I went with hubot@3.0.1
. This yielded errors here:
I commented this line out to see if it the ignored users. The error just shifted to just a few lines later:
INFO Someone is typing...
DEBUG Message {
event: 'posted',
data:
{ channel_display_name: '',
channel_name: 'my8---redacted---br6c',
channel_type: 'D',
mentions: '["no4--redacted--br6c"]',
post: '{"id":"ke3----tc","create_at":1522146010510,"update_at":1522146010510,"edit_at":0,"delete_at":0,"is_pinned":false,"user_id":"my8---t1h9e","channel_id":"rn----wa","root_id":"","parent_id":"","original_id":"","message":"help","type":"","props":{},"hashtags":"","pending_post_id":"my8------h9e:1522146010862"}',
sender_name: 'mynickname',
team_id: '' },
broadcast:
{ omit_users: null,
user_id: '',
channel_id: 'rn83---redacted--cwa',
team_id: '' },
seq: 4 }
ERROR TypeError: Cannot read property 'getUserByID' of undefined
at Matteruser.message (--redacted--\node_modules\hubot-matteruser\src\matteruser.coffee:207:18, <js>:289:28)
at Client.<anonymous> (--redacted--\node_modules\hubot-matteruser\src\matteruser.coffee:1:1, <js>:5:61)
at Client.emit (events.js:160:13)
at Client.onMessage (--redacted--\node_modules\mattermost-client\src\client.coffee:279:17, <js>:381:23)
at WebSocket.<anonymous> (--redacted--\node_modules\mattermost-client\src\client.coffee:224:13, <js>:318:22)
at WebSocket.emit (events.js:160:13)
at Receiver.ontext (--redacted--\node_modules\ws\lib\WebSocket.js:841:10)
at --redacted--\node_modules\ws\lib\Receiver.js:536:18
at Receiver.applyExtensions (--redacted--\node_modules\ws\lib\Receiver.js:371:5)
at --redacted--\node_modules\ws\lib\Receiver.js:508:14
at Receiver.flush (--redacted--\node_modules\ws\lib\Receiver.js:347:3)
at Receiver.finish (--redacted--\node_modules\ws\lib\Receiver.js:541:12)
at Receiver.expectHandler (--redacted--\node_modules\ws\lib\Receiver.js:499:31)
at Receiver.add (--redacted--\node_modules\ws\lib\Receiver.js:103:24)
at TLSSocket.realHandler (--redacted--\node_modules\ws\lib\WebSocket.js:825:20)
at TLSSocket.emit (events.js:160:13)
at addChunk (_stream_readable.js:269:12)
at readableAddChunk (_stream_readable.js:256:11)
at TLSSocket.Readable.push (_stream_readable.js:213:10)
at TLSWrap.onread (net.js:599:20)
INFO ping
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Hubot 3.x compatibiltiy · Issue #460 · slackapi/hubot-slack
My gut feeling tells me that not_authed is related to the wrong or otherwise incompatible token being used, but I believe we double-checked...
Read more >Gathering Solutions and Providing APIs for their Orchestration ...
may recommend or conflict with certain referenceables. Such links are used to refer to other solutions or capabilities, which are either incompatible.
Read more >2 kişilik moyunlsar - Welkom bij Servies "Toen & Nu"
Incompatible hsdev detected version 0 0 0 0. Rks tmt-8. Bein sport 7 live streaming. ... Ömer can keman eğitimi 1 kitabı pdf...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m very sorry, My bot is currently running well enough and I am somewhat swamped. I will not be able to test this in the next 3-4 weeks. This is not for a lack of interest, though. I will update to Hubot 3.x / Matteruser 5.x at some point.
@ketchalegend @ccoenen the next version (5.x) should be compatible with Hubot3. If you are able to test the current
master
branch that would be great!