Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

serverSideEmit(..., callback) does not deliver events until heartbeat is triggered

Ouverte
  • Quelque chose ne va pas ?
#16 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

@Harjot2022 y travaille déjà.

Depuis le 22/3/2026.

  • #18 par @wangxpych — fermée sans fusion

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
52/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
postgresql, typescript
Domaine
backend, databases, distributed-systems

Piste de recherche

Start with the Postgres adapter's serverSideEmit(..., callback) and heartbeat or server discovery flow, using the minimal reproduction in the issue. Compare callback-based emits with emits without callbacks and verify that all connected servers receive the event and return acknowledgements before any dummy emit is sent.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Environment

  • @socket.io/postgres-adapter: 0.4.0
  • socket.io: 4.8.x
  • pg: 8.16.x
  • Node.js: 22
  • PostgreSQL: 14.x

Problem description

When using serverSideEmit(..., callback), the callback is invoked with:

(err, responses) => {
  console.log(err);       // null
  console.log(responses); // [] ← empty
}

The event is never delivered to any other server, and the handler (io.on(...)) is never triggered on them.

However, if each individual server sends at least one serverSideEmit() (even a dummy one), things start working — the events are delivered and acknowledged as expected.

Note: If serverSideEmit() is used without a callback, the event is delivered to other servers even before they have sent any emits themselves. The issue only affects the ACK-based communication (serverSideEmit(..., callback)).

Root cause

The Postgres adapter does not deliver serverSideEmit(..., callback) events to other servers unless those servers have already started sending their own heartbeats.

Until a server sends a serverSideEmit():

  • It is connected and listening on the correct LISTEN channel
  • It can receive broadcast events without callback
  • But it will not be discoverable by other servers for ACK-based communication (serverSideEmit(..., callback))

As a result:

  • The initiating server sends a request and waits for ACKs
  • But other servers ignore the request because they don't recognize the source as active
  • The callback returns with responses = []

Minimal reproduction

// on all servers:
io.on("test-ack", (data, callback) => {
  console.log("received:", data);
  callback("ack from " + process.pid);
});

// on emitter server:
setTimeout(() => {
  io.serverSideEmit("test-ack", "hello", (err, responses) => {
    console.log("err:", err);           // null
    console.log("responses:", responses); // [] if heartbeat not yet started on other servers
  });
}, 1000);

Workaround

Ensure that every server sends a dummy serverSideEmit() after startup to trigger the heartbeat:

io.serverSideEmit("__init__", "poke");

This ensures each server becomes discoverable by others and can participate in ACK-based messaging.

Langage dominant
TypeScript
Étoiles
28
Forks
9
Aucune PR mergée en 30 j

Préparer son environnement

  • Fournit un Dockerfile ou un fichier Docker Compose
  • Aucun modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de socketio/socket.io-postgres-adapter

Toutes les issues de socketio/socket.io-postgres-adapter

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.