Issues ↑

unicorn-public@bogomips.org is the best place to report bugs, submit patches and/or obtain support after you have searched the email archives and documentation.

We will never have a centralized or formal bug tracker. Instead we can interoperate with any bug tracker which can Cc: us plain-text to unicorn-public@bogomips.org This includes the Debian BTS at bugs.debian.org/unicorn and possibly others.

If your issue is of a sensitive nature or you're just shy in public, use anonymity tools such as Tor or Mixmaster; and rely on the public mail archives for responses. Be sure to scrub sensitive log messages and such.

If you don't get a response within a few days, we may have forgotten about it so feel free to ask again.

Bugs in related projects ↑

unicorn is sometimes affected by bugs in its dependencies. Bugs triggered by unicorn in mainline Ruby, rack, GNU C library (glibc), or the Linux kernel will be reported upstream and fixed.

For bugs in Ruby itself, we may forward bugs to bugs.ruby-lang.org/ and discuss+fix them on the ruby-core list at ruby-core@ruby-lang.org Subscription to post is required to ruby-core, unfortunately: ruby-core-request@ruby-lang.org?subject=subscribe

For uncommon bugs in Rack, we may forward bugs to rack-devel@googlegroups.com and discuss there. Subscription (without any web UI or Google account) is possible via: rack-devel+subscribe@googlegroups.com Note: not everyone can use the proprietary bug tracker used by Rack, but their mailing list remains operational.

Uncommon bugs we encounter in the Linux kernel should be Cc:-ed to the Linux kernel mailing list (LKML) at linux-kernel@vger.kernel.org and subsystem maintainers such as netdev@vger.kernel.org (for networking issues). It is expected practice to Cc: anybody involved with any problematic commits (including those in the Signed-off-by: and other trailer lines). No subscription is necessary, and the our mailing list follows the same conventions as LKML for interopability. There is a kernel.org Bugzilla instance, but it is ignored by most developers.

Likewise for any rare glibc bugs we might encounter, we should Cc: libc-alpha@sourceware.org Keep in mind glibc upstream does use Bugzilla for tracking bugs: sourceware.org/bugzilla/

Submitting Patches ↑

See the HACKING document (and additionally, the SubmittingPatches document distributed with git) on guidelines for patch submission.

Contact Info ↑

Mailing list subscription is optional, so Cc: all participants.

You can follow along via NNTP (read-only):

nntp://news.public-inbox.org/inbox.comp.lang.ruby.unicorn
nntp://news.gmane.org/gmane.comp.lang.ruby.unicorn.general

Or Atom feeds:

https://bogomips.org/unicorn-public/new.atom
http://ou63pmih66umazou.onion/unicorn-public/new.atom

The HTML archives at https://bogomips.org/unicorn-public/
also has links to per-thread Atom feeds and downloadable
mboxes.

You may optionally subscribe via plain-text email:

mailto:unicorn-public+subscribe@bogomips.org
(and confirming the auto-reply)

Just keep in mind we suck at delivering email, so using NNTP, or Atom feeds might be a better bet…