Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

logging to a winston-nssocket transport fails if this endpoint isn't listening #2

Open
camerondgray opened this Issue Jun 27, 2012 · 1 comment

Comments

Projects
None yet
2 participants

if you attempt to log to a winstond server by using the winston-nssocket transport you will get an exception stating that you are logging on a bad socket if the winstond server is unavailable even momentarily. Ideally the transport would buffer so that the app that is logging does not crash if the winstond server become unavailable. I am trying to write a test to replicate the issue but currently I am having trouble getting the existing tests to pass.

Collaborator

chjj commented Jun 27, 2012

Ideally the transport would buffer so that the app that is logging does not crash if the winstond server become unavailable.

That's a good idea. It should also probably have some kind of limit though, so it's not just buffering forever if a server is completely broken. I'll mess around with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment