| Age | Commit message (Collapse) | Author |
|---|
|
Instead of having a separate channel+goroutine for the backend, just call
.Write() right where we get results from the backend, but don't let an
error cause us to stop reading from the backend, an error should just cause
us to stop writing. This ensures that the backend now always has its
output chan drained; before if there were a write error, the backend chan
wouldn't get drained, and the resources never released.
|
|
nslcd_proto.Read() and .Write() panic() with any errors that they may
need to emit. This made composition really simple, I was OK with it
being against the normal Go style.
But, I'm not happy with it anymore; have them return errors now.
This leads us in to nslcd_server.HandleRequest() using those panics
for control flow. Add a maybePanic(error) function to wrap all of the
proto.Read() and proto.Write() calls to restore the panicing behavior.
|
|
|
|
|
|
While it mostly played nice with autothing before, by having autothing
treat `go generate` as an opaque step, it didn't populate `files.src.gen`.
|
|
|
|
|
|
|
|
This is just a search/replace s/syscall/unix/g in the broken code.
|
|
|
