Issues ↑

unicorn-public@yhbt.net 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@yhbt.net This includes the Debian BTS at bugs.debian.org/unicorn and possibly others.

unicorn is a server; it does not depend on graphics/audio. Nobody communicating with us will ever be expected to go through the trouble of setting up graphics nor audio support.

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 Unofficial archives are available at: public-inbox.org/ruby-core/

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. Unofficial archives are available at: public-inbox.org/rack-devel/

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. Archives are available at lore.kernel.org/lkml/ There is a kernel.org Bugzilla instance, but it is ignored by most.

Likewise for any rare glibc bugs we might encounter, we should Cc: libc-alpha@sourceware.org Unofficial archives are available at: public-inbox.org/libc-alpha/ 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 ↑

Mail is publicly-archived, SMTP subscription is discouraged to avoid servers being a single-point-of-failure, so Cc: all participants.

The HTTP(S) archives have links to per-thread Atom feeds and downloadable mboxes. Read-only IMAP(S) folders and NNTP(S) newsgroups are also available.

Full Atom feeds:

We only accept plain-text mail: unicorn-public@yhbt.net