jeromeludmann / deno-irc Goto Github PK

Hello, I bring a strange issue I've been trying to debug in the production instance of my discord-irc fork. We love your library and it's been fantastic.

We're getting an exception in the createNicklist function that only crops up occasionally.

It seems to be immediately after a user quits the application bubbles up this exception. I've tried to reproduce it in my test environment but I don't get the exception on user quit. We plan to run the prod instance with a debugger at some point to see if we can get you more useful information for debugging.

Has anyone seen this problem before? We reboot the instance automatically for now with minimal downtime.

Hi, when I ran the following code, it exits with the error.
The code is almost same to https://github.com/jeromeludmann/deno-irc#usage and I added client.quit();.
How can I properly quit from the IRC channel and disconnect from the IRC server?

import { Client } from "https://deno.land/x/irc/mod.ts";

const client = new Client({
  nick: "bot",
  channels: ["#general"],
});

client.on("join", (msg) => {
  if (msg.channel === "#general") {
    client.privmsg("#general", "Hello world!");
  }
  client.quit();
});

// no TLS
await client.connect("127.0.0.1", 6667);

❯ deno run -A irc-bot.ts
Check file:///Users/kyanny/workspaces/deno/irc-bot/irc-bot.ts
error: Uncaught (in promise) Interrupted: operation canceled
      read = await conn.read(this.buffer);
             ^
    at deno:core/01_core.js:106:46
    at unwrapOpResult (deno:core/01_core.js:126:13)
    at async read (deno:ext/net/01_net.js:21:19)
    at async Client.read (https://deno.land/x/[email protected]/core/client.ts:149:14)
    at async Client.loop (https://deno.land/x/[email protected]/core/client.ts:132:22)

It would be nice if there was some built-in way to automatically try reconnecting when the connection is lost (perhaps using some static or exponential backoff)

I'm looking to join a network and list all channels.

I'm just wondering if it'd be worth our while to support connecting over WebSockets. AIUI the protocol is the same, the only difference being the transport. This would mean we could even eventually branch out to our code also running in the browser (which should be helped along by Deno emulating a browser environment as far as APIs etc go.