Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Slack] Direct messages require existing channel #58

Closed
jaraco opened this issue Mar 1, 2017 · 5 comments
Closed

[Slack] Direct messages require existing channel #58

jaraco opened this issue Mar 1, 2017 · 5 comments

Comments

@jaraco
Copy link
Member

jaraco commented Mar 1, 2017

Following on #57, direct messages are now arriving but only if the channel between pmxbot and the user was already opened.

@jaraco
Copy link
Member Author

jaraco commented Mar 1, 2017

I found the slacker project implements a method to open a new IM.

@jaraco jaraco closed this as completed in 51fbc07 Mar 1, 2017
jaraco added a commit that referenced this issue Mar 1, 2017
jaraco added a commit that referenced this issue Mar 1, 2017
jaraco added a commit that referenced this issue Mar 1, 2017
@jaraco
Copy link
Member Author

jaraco commented Mar 1, 2017

After several rounds, I believe I have a technique that solves this in 1118.0.3.

@jaraco jaraco changed the title [Slack API] Direct messages require existing channel [Slack] Direct messages require existing channel Mar 7, 2017
@jaraco
Copy link
Member Author

jaraco commented Mar 7, 2017

Apparently even with the dual-API technique, this issue was not resolved, though I'm not entirely sure the issue was accurately tested either, because after we switched back to the IRC gateway, the issue persists.

@jaraco jaraco reopened this Mar 7, 2017
@jaraco jaraco added the Slack label May 22, 2017
@jaraco
Copy link
Member Author

jaraco commented May 22, 2017

after we switched back to the IRC gateway, the issue persists.

Although I registered this apparent issue here, I can't find the reason why I said that, and there have not been ongoing issues with notifications except when we know the bot has become disconnected from the server.

@jaraco jaraco added the invalid label Nov 2, 2018
@jaraco
Copy link
Member Author

jaraco commented Nov 2, 2018

We've since been forced to switch to a Slack-based bot, and no one has complained about this issue. Unless someone complains, I'm not going to worry about it.

@jaraco jaraco closed this as completed Nov 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant