I have searched the issue list for something similar, but I have not found the exact same issue.

The problem is that, given these two models:

factory :employee do
  # various attributes
end

factory :job do
  association :employee, strategy: :build
end

attributes_for ignores any explicit employee assignments:

attributes_for(:job, employee: some_other_em

It would be great if a new message, appearing automatically via WebSockets, also triggers notifications via the Notifications API.

https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API

Cautionary: There should also be some kind of grouping/throttling for massive batches that arrive all at once.

Do you have a reproduction script?
Using any project:
bundle install --standalone

What were you expecting to happen?
The generated setup.rb does not contain relative path operators.
E.g.

$:.unshift "#{path}/#{ruby_engine}/#{ruby_version}/gems/rake-13.0.1/lib"

What actually happened?
The generated paths contain /../ relative path operators.

path = File.

ref: karafka/karafka#573

I recently upgraded from terraform kitchen 3.3 to kitchen 4.0. This meant that I could use inspec aws resources (which is great). However, I ran into some difficulties due to sparse documentation around how to use the aws backend and what one should put in the kitchen.yml.

I'd like to submit a PR that adds documentation with this info. However, I am not sure the appropriate place for this doc.

I'll send a suggested change for this, but it seems worth making an issue so that it's easier to find.

It turns out that you need a recent enough version of MySQL, or at least of MariaDB, if you use that. For instance, if you just yum install mysql in EL7, you actually get mariadb 5.5, which doesn't support fulltext indexing on innodb tables. Also the permissions grant on the tables doesn't

Maybe worth linking to or asking for permission to incorporate this post into a guide for running Gemstash on AWS: https://blog.showoff.ie/using-gemstash-for-private-gem-hosting-8b6170da766c

Currently, when a new user(reader) is creates, all messages (readables) created before that point in time will be marked as read. It can only be disabled by overriding the setup_new_reader function in the reader.

So the in the example have_not_read method should ideally return empty.

## Get users that have not read a given message
user1 = User.create!
user2 = User.create!

U

In reference to

https://github.com/coingecko/cryptoexchange/blob/master/lib/cryptoexchange/exchanges/binance/market.rb#L7
https://github.com/coingecko/cryptoexchange/blob/master/spec/exchanges/binance/integration/market_spec.rb#L20
Label the exchange in the README when implemented
add trade_page_url to list of the following exchanges

• Lykke
• Tidex
• Tidebit
• Koinex

https://guides.rubygems.org/specification-reference/#files

The example code is the following

require 'rake'
spec.files = FileList['lib     .rb',
                      'bin/*',
                      '[A-Z]*',
                      'test/   *'].to_a

# or without Rake...
spec.files = Dir['lib/   *.rb'] + Dir['bin/*']
spec.files += Dir['[A-Z]*'] + Dir['test/**/*']
spec.files.rejec