Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/thediveo/fdooze
File descriptor leak detection for Gomega (on Linux).
https://github.com/thediveo/fdooze
Last synced: about 1 month ago
JSON representation
File descriptor leak detection for Gomega (on Linux).
- Host: GitHub
- URL: https://github.com/thediveo/fdooze
- Owner: thediveo
- License: apache-2.0
- Created: 2022-04-09T11:43:56.000Z (over 2 years ago)
- Default Branch: master
- Last Pushed: 2023-10-27T19:27:51.000Z (about 1 year ago)
- Last Synced: 2024-06-21T18:50:16.698Z (5 months ago)
- Language: Go
- Homepage:
- Size: 685 KB
- Stars: 2
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# `fdooze`
[![PkgGoDev](https://img.shields.io/badge/-reference-blue?logo=go&logoColor=white&labelColor=505050)](https://pkg.go.dev/github.com/thediveo/fdooze)
[![GitHub](https://img.shields.io/github/license/thediveo/fdooze)](https://img.shields.io/github/license/thediveo/fdooze)
[![Go Report Card](https://goreportcard.com/badge/github.com/thediveo/fdooze)](https://goreportcard.com/report/github.com/thediveo/fdooze)
![Coverage](https://img.shields.io/badge/Coverage-100.0%25-brightgreen)`fdooze` complements [Gomega](https://github.com/onsi/gomega) with tests to
detect leaked ("oozed") [file
descriptors](https://man7.org/linux/man-pages/man2/open.2.html#DESCRIPTION).> **Note:** `fdooze` is available on **Linux only**, as discovering file
> descriptor information requires using highly system-specific APIs and the
> descriptor information varies across different systems (if available at all).## Installation
In your project (with a `go.mod`) run
```go
go get github.com/thediveo/fdooze@latest
```to get and install the latest stable release.
## Usage
In your tests, using [Ginkgo](https://github.com/onsi/ginkgo):
```go
import . "github.com/thediveo/fdooze"var _ = Describe("...", func() {
BeforeEach(func() {
goodfds := Filedescriptors()
DeferCleanup(func() {
Expect(Filedescriptors()).NotTo(HaveLeakedFds(goodfds))
})
})})
```This takes a snapshot of "good" file descriptors before each test and then after
each test it checks to see if there are any leftover file descriptors that
weren't already in use before a test. `fdooze` does not blindly just compare fd
numbers, but takes as much additional detail information as possible into
account: like file paths, socket domains, types, protocols and addresses, et
cetera.On finding leaked file descriptors, `fdooze` dumps these leaked fds in the
failure message of the `HaveLeakedFds` matcher. For instance:```
Expected not to leak 1 file descriptors:
fd 7, flags 0xa0000 (O_RDONLY,O_CLOEXEC)
path: "/home/leaky/module/oozing_test.go"
```For other types of file descriptors, such as pipes and sockets, several details
will differ: instead of a path, other parameters will be shown, like pipe inode
numbers or socket addresses. Due to the limitations of the existing fd discovery
API, it is not possible to see _where_ the file descriptor was opened (which
might be deep inside some 3rd party package anyway).## `Expect` or `Eventually`?
In case you are already familiar with Gomega's
[gleak](https://onsi.github.io/gomega/#codegleakcode-finding-leaked-goroutines)
goroutine leak detection package, then please note that typical `fdooze` usage
doesn't require `Eventually`, so `Expect` is fine most of the time. However, in
situations where goroutines open file descriptors it might be a good idea to
first wait for goroutines to terminate and not leak and only then test for any
file descriptor leaks.When using Eventually() make sure to pass the Filedescriptors function itself to
it, not the result of calling Filedescriptors.// Correct
Eventually(Filedescriptors).ShouldNot(HaveLeakedFds(...))> **WRONG:**
> `Eventually(Filedescriptors()).ShouldNot(HaveLeakedFds(...))`## Leak Tests on Launched Processes
The `session` package implements retrieving the open file descriptors from a
Gomega `gexec.Session` (Linux only). This allows checking processes launched by
a test suite for file descriptor leaks, subject to normal process access
control.It is recommended to dot-import the session package, as this keeps the "session"
identifier free to be used by test writers as they see fit.```go
session, err := gexec.Start(cmd, GinkgoWriter, GinkgoWriter)
Expect(err).NotTo(HaveOccurred())// Optional, please see note below.
client.DoWarmupAPIThing()// When using Eventually, make sure to pass the function, not its result!
sessionFds := func ([]FileDescriptor, error) {
return FiledescriptorsFor(session)
}goodfds := sessionFds()
client.DoSomeAPIThing()
Expect(session).Should(gbytes.Say("I did the thing"))Eventually(sessionFds).ShouldNot(HaveLeakedFds(goodfds))
Eventually(session.Interrupt()).Should(gexec.Exit(0))
```In case the launched process is implemented in Go, fd leak tests need to be
carefully designed as to not fail with false positive fd leaks caused by Go's
netpoll runtime (for instance, see [The Go
netpoller](https://morsmachine.dk/netpoller) for more background information).For instance, when opening a file or network socket for the first time, Go's
runtime creates an internal epoll fd as well as a non-blocking pipe fd for use
in its internal asynchronous I/O handling.Unfortunately, it is not possible to easily filter out the file descriptors
belonging to the Go runtime netpoller: fds in general don't record who created
them and for what purpose. An epoll fd might be used in an application itself
and thus quite often be ambigous. Also, the exact fd number will depend on a Go
application highly specific initialization process.It is thus mandatory to take a "reference" snapshot of baseline fds only after
the launched process has opened its first file or network socket. In case of
network-facing services this will be when the listening transport port has
become available.## Go Version Support
`fdooze` supports versions of Go that are noted by the Go release policy, that
is, major versions _N_ and _N_-1 (where _N_ is the current major version).## Goigi the Gopher
Goigi the gopher mascot clearly has been inspired by the Go gopher art work of
[Renee French](http://reneefrench.blogspot.com/). It seems as if Goigi has some
issues with plumbing file descriptors properly.## Copyright and License
`fdooze` is Copyright 2022-23 Harald Albrecht, and licensed under the Apache
License, Version 2.0.