This is a very common pattern:

class MyChannel < ApplicationCable::Channel
  def subscribed
    if box = identity.boxes.find_by(id: params[:id])
      stream_for box
    else
      reject
    end
end

You're looking for a record based on a parameter, and if you find it, you'll start streaming. If the record isn't there, you reject the connection. We should extract `Add Ac

Motivation

Hi, I've struggled (like a lot of persons it seems) with setting up github pages with shpinx. In particular, the way include works on folders/subfolders.

To solve the problem, I went to the documentation and looked how it was done in the default configuration [here](https://jekyllrb.com/do

Question Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Question Subject

This is a question about documentatio

Homebrew/livecheck provides various automated ways of detecting formulae updates. A livecheck DSL should be added in Homebrew/brew and used by Homebrew/homebrew-core formulae and migrated from Homebrew/livecheck's Livecheckables directory and brew livecheck use this new data.

• OS: Fedora
• vagrant version: 2.2.6
• vagrant-libvirt (0.0.45, system)

Actual results

The content of the output indicates that the tool is not aware of the input command, as illustrated:

• it suggests to run that last, vagrant global-status --prune.
• statement "_The above shows information about all known Vagrant environments on this machine.. This data is cached and may not be com

This is in response to #7264, since we decided that PR is not the right way to do it.

I think we decided on: move the non-browser-specific tests out of the browser-specific test files.

So if the "chrome only" tests pass when using Firefox for instance, they should be moved to unit tests or into a common spec file of some kind.

This issue has 2 parts

1. Style/RescueStandardError isn't represented at all in the style guide
2. In particular, https://github.com/bbatsov/ruby-style-guide/tree/2c0b4713794ea07a70ca4e1dee81405350fa7544#no-blind-rescues shows that rescue => e is "good", but this line would fail against Style/RescueStandardError 's default of "explicit".

Since this cop has 2 choices (implicit and explicit

When you have only one registered aspect, then people belonging to that aspect don't get shown with the name of the aspect, but with the generic "All Aspects".
I don't know if it was meant to be like this, I just find it confusing.

Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/86276565-profile-visualization-when-there-is-onl

I have setup rbenv according to the documentation on a fresh CentOS 7.7 machine. The result is that the installation does not work (ruby is not found regardless of me adding it as local or global). I finally found out that the shims directory never makes it to the path and therefore executed

echo 'export PATH="$HOME/.rbenv/shims:$PATH"' >> ~/.bash_profile

which made the stuff work. I a

Commands that are described within the on-line documentation aren't where they are described to be.

So it seems there is a variable current_path which points to wherever :deploy:to/current symlink points. So after deploy:symlink:release it points to the current release.
Also there is a variable release_path that seems to point to the current release directory which is created by create_release task.

What

Whenever I try to install the sinatra gem, the first install hangs during:

"Installing ri documentation for sinatra-2.0.7"

I manually interrupt it, then do it again, and then it works.

I have no idea what causes it, but all the other gems and their ri
documentation do not have this issue.

I believe that there must be something special for sinatra documentation
done that causes this b

Is your feature request related to a problem? Please describe.

There are a few situations where you have only the Cop name but you are not able to figure out what it is enforcing. Here are a few examples:

• CI fails
• Someone disabled a cop inline on the source code
• A new issue is discussing enabling/disabling a specific Cop

Describe the solution you'd like

It would be useful

Would be nice to be able to add more unique information on a per store basis.

Useful field Examples:

• Full address (replace the static address that is hard coded into the footer).
• Dedicated field for customer facing contact email address (in case you want to use a separate send from such as a no-reply@you.com).
• upload store logo.
• upload store favicon image.

Would love to hear if anyone has extended out postal to a HA setup. With the postal install looking for IPs bound locally, that causes some issue.

Extending out the database/queues shouldn't be too hard but comes down to how mail is sent.

Having single reliance on a VM/server running postal is always a worry. Whilst the underlying hardware (for us) has resilience, there is still the single p

I think it would be a good idea to mention the tee command, probably somewhere in the "Cat, Less, Tail and Head" chapter

Custom error formatter must have now 5 arguments instead of the old 4. These changes were introduced here on #1652

When migrating from 0.19 to 1.1.0 I had issues on a custom error formatter because the original_exception argument was introduced but that change was not documented on the upgrading guide.

Describe the solution you'd like

Providing placeholder expander for 3rd party plugins.

Describe alternatives you've considered

none

Additional context

fluent/fluent-plugin-prometheus#129

btw I'm wondering long time that fluentd officially provides the way to expand placeholder by messages to 3rd party plugins or not. Otherwise every plugins

I wanted to ask if a migration guide was created for going from a 1.4.3 version to a 2.x version? If there is no migration guide, what non-passive changes were introduced that caused the 2.x version bump?

Here are all the Faker classes that have been updated with YARD docs/need to be updated:

• Blockchain
  • Aeternity (#1742)
  • Bitcoin (#1553)
  • Ethereum (#1553)
  • Tezos (#1553)
• Books
  • Book (#1553)
  • Culture (#1553) - Still needs descriptions for the YARD docs.
  • Dune (#1553)
  • Lovecraft (#1553)
• Creature
  • Animal (#1

We've received a good amount of feedback for formatting values instantiated within the page_entries_info method. Currently we don't have a concrete interface for the method and Kaminari users need to implement a decorator that's not intuitive. It would be helpful if the method sends a certain sed of messages to the collection object. I'm not sure what the interface should look like, but here i