- Open Source Contributor to NestJS Core (PRs #17668, #17781, #17797)
- All of my projects are available at Ming's Projects
- Know about my experiences Ming's Resume
Three PRs merged into nestjs/nest master.
@nestjs/microservices — tracing spans left open on failure paths
- #17781 — When a message handler threw, NestJS skipped the hook that closes the tracing span: the failures you most need to trace left no telemetry, and each one stayed in memory for good. The one-shot guard added on the base
Serverclass is today the only place in the package where that hook is called — Nest's author reused it across five transports in #17794. - #17797 — Three more of the same on Kafka's request-response path. The worst leaked one span per retry, so the longer a downstream service stayed down, the faster memory grew.
@nestjs/common — a pipe that rejected every valid value
- #17668 —
ParseEnumPipereturned400for every member of a numeric enum, because HTTP params arrive as strings and the check compared'0'against0.
→ How I found and fixed each one
- 轉生為軟體工程師兩年以後的我:離開舒適圈,重新定義工程師價值
- Kubernetes(K8s)從觀念到實戰:學習筆記
- 轉生為軟體工程師一年後的我
- Docker & Docker-Compose 基本用法
- AWS — EC2 AMI 資料備份與移轉教學
More on Ming's Medium


