feat: emit error on connections when receiving "EXPIRE"

Closes peers#924
WofWca · Sep 3, 2023 · b2016a5 · b2016a5
1 parent 59cea73
commit b2016a5
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 0 deletions.
diff --git a/lib/enums.ts b/lib/enums.ts
@@ -61,6 +61,7 @@ export enum PeerErrorType {
 }
 
 export enum BaseConnectionErrorType {
+ PeerUnavailable = "peer-unavailable",
  NegotiationFailed = "negotiation-failed",
  ConnectionClosed = "connection-closed",
 }

diff --git a/lib/peer.ts b/lib/peer.ts
@@ -4,6 +4,7 @@ import { Socket } from "./socket";
 import { MediaConnection } from "./mediaconnection";
 import type { DataConnection } from "./dataconnection/DataConnection";
 import {
+ BaseConnectionErrorType,
  ConnectionType,
  PeerErrorType,
  ServerMessageType,
@@ -379,6 +380,16 @@ export class Peer extends EventEmitterWithError<PeerErrorType, PeerEvents> {
  PeerErrorType.PeerUnavailable,
  `Could not connect to peer ${peerId}`,
  );
+ // Emit an error on all connections with this peer.
+ const connections = (this._connections.get(peerId) ?? []).filter(
+ (c) => c.peer === peerId,
+ );
+ for (const conn of connections) {
+ conn.emitError(
+ BaseConnectionErrorType.PeerUnavailable,
+ `${peerId} is unavailable`,
+ );
+ }
  break;
  case ServerMessageType.Offer: {
  // we should consider switching this to CALL/CONNECT, but this is the least breaking option.