---
title: "Discussion on \"The Third Listener Was Never Called\" | Hashnode"
description: "Discussion on \"The Third Listener Was Never Called\". Two of three callbacks raised, the caller got one exception, and the healthy one was never scheduled — in a tree with 1227 passing tests and 100% coverage."
url: "https://hashnode.com/posts/the-third-listener-was-never-called/6af7fb86a2d0a7605dbb8174"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The Third Listener Was Never Called](https://mediaforge-studio.hashnode.dev/the-third-listener-was-never-called?utm_source=hashnode&utm_medium=feed)

Two of three callbacks raised, the caller got one exception, and the healthy one was never scheduled — in a tree with 1227 passing tests and 100% coverage.

16h ago · 7 min read · mediaforge-studio.hashnode.dev  
Read the article

-   [#python](https://hashnode.com/tag/python)
-   [#testing](https://hashnode.com/tag/testing)
-   [#devops](https://hashnode.com/tag/devops)
-   [#programming](https://hashnode.com/tag/programming)

## Written by

[dafili](https://hashnode.com/@vaultcheck)

@vaultcheck · Chengdu, China

  
[View profile](https://hashnode.com/@vaultcheck)

Indie developer building command-line tools for Linux auditing and B2B data extraction.

Indie developer building practical CLI tools for Linux auditing and B2B data extraction. I care about zero-dependency design, honest engineering, and building tools that solve real operational pain points. Currently maintaining Vaultcheck and NPILift.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
