ift-ts:qa:logos:2026q4-messaging-testing
Description
Continue improving messaging test reliability by maintaining existing frameworks and migrating the remaining interop tests into the Logos Delivery repository. Adapt tests to messaging component changes, address regressions, and keep coverage useful as the implementation evolves.
Task List
Interop migration
- fully qualified name:
ift-ts:qa:logos:2026q4-messaging-testing:interop-migration - owner: Florin/Radek
- status: done
- start-date: 2026/10/01
- end-date: 2026/10/13
Description
Continue the Q3 migration of messaging interop tests into the Logos Delivery repository. Port the remaining scenarios to the repository’s E2E workflow, preserve relevant protocol coverage, and resolve failures or gaps exposed by the migration.
Deliverables
- logos-messaging/logos-delivery#4335 test(e2e): cleanup harness code (migration 14)
- logos-messaging/logos-delivery#4348 test(e2e): rename the wrapper suite to c_abi (migration 15)
- logos-messaging/logos-delivery#4350 test(e2e): run the C ABI suite in parallel and make its xfailed tests pass (migration 16)
- logos-messaging/logos-delivery#4353 test(e2e): python binding as a submodule (migration 17)
- logos-messaging/logos-delivery-python-bindings#9 chore: bump logos-delivery and move the wrapper to the CBOR ABI
- status-im/status-go#7816 ci: test Logos Delivery nightly and issue reporting in Jenkins
- logos-messaging/logos-delivery#4422 test: include orphaned suites
Maintenance
- fully qualified name:
ift-ts:qa:logos:2026q4-messaging-testing:maintenance - owner: Radek
- status: in progress (25%)
- start-date: 2026/10/01
- end-date: 2026/12/31
Description
Provide ongoing maintenance of messaging testing frameworks. Update tests for messaging component changes, investigate failing or flaky tests, address regressions, and make minor framework improvements needed to keep the suites reliable.
Deliverables
- logos-messaging/logos-delivery#4368 ci: cache nim, nimble and nimcache (ci improvements 1)
- logos-messaging/logos-delivery#4379 test: configurable waiting times (ci improvements 2)
- logos-messaging/logos-delivery#4395 test: wait on conditions instead of fixed sleeps (ci improvements 3)
- logos-messaging/logos-delivery#4420 ci: test reporter
- logos-messaging/logos-delivery#4463 test(e2e): fix flaky test_s31_concurrent_sends_mixed_topics_during_churn
- logos-messaging/logos-delivery#4439 test: bug reproductions
- logos-messaging/logos-delivery#4459 test: bug reproductions 2
- logos-messaging/logos-delivery#4438 bug: the archive counts a message it already holds as written on Postgres and as an insert failure on sqlite
- logos-messaging/logos-delivery#4437 question: GET /store/v3/messages reads a startTime or endTime of 0 or less as absent, and a negative pageSize as the maximum
- logos-messaging/logos-delivery#4436 question: any —rate-limit entry replaces the default rate limits, so filter falls to 30/1m and unnamed protocols run without a limit
- logos-messaging/logos-delivery#4435 question: filter UNSUBSCRIBE of a criterion the requester does not hold answers 200 or 404 depending on other peers, and its 404 can follow a partial removal
- logos-messaging/logos-delivery#4434 bug: /filter/v2/subscriptions answers 200 “UNKNOWN” without pubsubTopic under static sharding, and its message cache ignores the result
- logos-messaging/logos-delivery#4432 bug: REST API answers an undecodable JSON body without the decoder’s reason
- logos-messaging/logos-delivery#4431 bug: /lightpush/v3/message answers 500 for INVALID_MESSAGE (420), and 413 or 500 for the same oversize message
- logos-messaging/logos-delivery#4433 question: lightpush v3 client turns the service’s BAD_REQUEST for an undecodable request into “response failure, requestId mismatch”
- logos-messaging/logos-delivery#4457 bug: POST /relay/v1/subscriptions joins a shard of another cluster or past —num-shards-in-network, and the node’s metadata then misreports its shards
- logos-messaging/logos-delivery#4456 question: DELETE /relay/v1/auto/subscriptions of one content topic unsubscribes its whole shard, silencing the other content topics on it
- logos-messaging/logos-delivery#4455 question: under autosharding —shard does not limit which shards the relay joins, yet the REST cache and —protected-shard still follow it
- logos-messaging/logos-delivery#4454 question: —cluster-id=2 applies the logos.dev preset, whose nodes are on cluster 3, and replaces an explicit —preset=logos.test
- logos-messaging/logos-delivery#4453 bug: a duplicate a node publishes goes through its own relay handlers again, and is answered as NoPeersToPublish
- logos-messaging/logos-delivery#4485 bug: with a raised —max-msg-size, store sync never transfers a message above 150 KiB, and a few such messages stop the node’s transfers to every peer
- logos-messaging/logos-delivery#4484 bug: a node that gets SIGTERM while store sync transfers messages to a peer never finishes stopping and is killed
- logos-messaging/logos-delivery#4486 bug: a message encoded within —max-msg-size is not relayed or stored when the encoded RPC message gossipsub would send exceeds the limit, and the publish routes answer 200 or “no peers”
- logos-messaging/logos-delivery#4483 bug: store sync transfer writes the pubsub topic as field 1 and the message as field 2, the reverse of the WAKU-SYNC specification
- logos-messaging/logos-delivery#4482 bug: —preset=status.prod runs the 150KiB default of —max-msg-size instead of the 1024KiB of the preset, and warns at every start that the size was provided
- logos-messaging/logos-delivery#4481 bug: a peer that connects in while the node’s own dial to it is in flight stays CannotConnect for as long as it is connected
- logos-messaging/logos-delivery#4480 question: /admin/v1/peers lists a peer that dialled in over TCP at its connection’s source port, where nothing listens
- logos-messaging/logos-delivery#4487 test: bug reproductions 3
- logos-messaging/logos-delivery#4542 test: bug reproductions 4
- logos-messaging/logos-delivery#4565 test: bug reproductions 5
- logos-messaging/logos-delivery#4592 test: bug reproductions 6
- logos-messaging/logos-delivery#4591 question: a node learns a peer’s shards once per connection, so an Edge node does not pick the peer for a shard it joins later
- logos-messaging/logos-delivery#4590 bug: an edge whose subscribed shard has no filter peer reports Filter Client READY and Connected
- logos-messaging/logos-delivery#4589 bug: logos_delivery_archive_messages_per_shard counts relay writes since the node started, not the messages the archive holds per shard
- logos-messaging/logos-delivery#4539 bug: messagingOverrides refuses anonymity-level, the CLI switch name of anonymityLevel
- logos-messaging/logos-delivery#4540 bug: on a node that is not started, send, subscribe and unsubscribe never say so, and a failed send still subscribes its content topic
- logos-messaging/logos-delivery#4522 bug: start_node after stop_node fails with “Address already in use” while REST or the metrics server is on
- logos-messaging/logos-delivery#4523 bug: library README says stop_node removes the event listeners, but they stay registered until destroy
- logos-messaging/logos-delivery#4521 bug: an edge node never subscribes through its —filternode peer, so it receives nothing until something else connects to that peer
- logos-messaging/logos-delivery#4511 question: a store node that joins after a send propagated never gets the message, and the send ends with an error instead of a resend
- logos-messaging/logos-delivery#4510 question: an edge node never dials a static node again after it was down at the edge’s start, so it never sends or receives through it
- logos-messaging/logos-delivery#4541 bug: a node reports no UnHealthy topic health at stop_node, nor after start_node when its mesh empties
- logos-messaging/logos-delivery#4563 question: a Core node reports its own message as message_received with source live when it publishes it, whether or not a peer got it
- logos-messaging/logos-delivery#4564 bug: a send that no store node confirms ends with an error event, while the node logs the failure only at DEBUG
- logos-messaging/logos-delivery#4553 bug: a library node warns that —websocket-port is ignored although its configuration sets no websocket port
- logos-messaging/logos-delivery#4544 question: onTopicHealthChange reports a shard’s topic health only when it changes, and no C ABI call reads it
- logos-messaging/logos-delivery#4543 question: channel_send on a node that is not started answers RET_OK, then reports the failure in events that name broker internals
- logos-messaging/logos-delivery#4555 bug: a node stopped while its rendezvous registration dials a peer that does not answer never finishes stopping
- logos-messaging/logos-delivery#4554 question: after stop_node and start_node, a channel created before the stop answers unknown channel
- logos-co/logos-logoscore-py#34 feat(docker): pass env vars to the daemon container
- logos-co/logos-logoscore-py#35 feat(logosctl): a docker smoke image for LogosctlDockerDaemon
- logos-messaging/logos-delivery#4610 bug: a node with an RLN plugin dials its static nodes only once the host answers the startup membership check
- logos-messaging/logos-delivery#4612 test: reproduction for #4610