absyah

A memory-saving ActiveRecord setting has been used by just one application ever, according to GitHub
There's a common performance problem in many Rails background jobs.

Background jobs often do operations across large sets of data. Basically, they do silly things like User.all.each(&:send_daily_newsletter).

So, there's a problem with that query. In development and test environments, User.all will probably return a few rows, maybe a dozen at most. Most developers have extremely limited seed data on their local machines.

In production, however, User.all will probably return quite a few rows. Depending on the app you work on, maybe a few hundred thousand.

There's a tiiiiiny issue with a result set that returns 100,000 rows, and it's not just that the SQL query will take a long time to return. It will have irreversible effects on your Ruby app too!

supairish

# spec/support/capybara.rb
require 'capybara/rails'
require 'capybara/rspec'

# port and url to webpack server
WEB_TEST_PORT = '5005'.freeze
WEB_TEST_URL = "http://localhost:#{WEB_TEST_PORT}".freeze

def capybara_wait_for_webpack_server
  10.times.each do |_|

mipearson

# Copyright 2018 Marketplacer. MIT License.

require 'json'
require 'active_support/core_ext/class/attribute'
require 'active_support/log_subscriber'

module Elk
  class RequestLogSubscriber < ActiveSupport::LogSubscriber
    PAYLOAD_KEYS_TO_COPY = %i{
      controller

anthonyeden

"""
Streaming FFmpeg to HTTP, via Python's Flask.
This is an incredibly simple example, which will yield issues due to inconsistant input and output rates.
If you're going to use this, VLC works okay as a client.
You really need to move FFmpeg into a separate thread, which should help stream audio more consistantly to the HTTP client.

Example by Anthony Eden (https://mediarealm.com.au)
"""

from flask import Flask

nerdinand

#
# A quick and dirty fixture implementation for use with Hanami, RSpec and PostgreSQL.
# Fixtures will be loaded when the suite starts and will be reset using transactions
# to the same state after each test case.
#
# Supports associations like so (author has many books):
#
# # authors.yml
# rowling:
#   name: J.K. Rowling

grawity

The official documentation is in the [sd_notify(3)][1] manual page.

Very short summary:

1. Change your systemd service to Type=notify.
2. Your daemon will receive an environment variable NOTIFY_SOCKET, which contains a path to an AF_UNIX socket.
   (If the first path byte is @, this means an "abstract" socket, and you should change the 1st byte to 0x00 before using.)
3. The protocol consists of sending datagrams containing textual (UTF-8) status messages.
   Each message contains newline-separated KEY=value parameters.
4. When the daemon is ready, it must send READY=1, and systemd will transition the service from "starting" to "running".

maxneuvians

defmodule LeakyBucket.Bucket do
  @moduledoc """
  Simulates a leaky bucket implementation
  """
  use GenServer

  @initial_amount 0
  @increment_rate 1
  @leak_rate 2
  @leak_interval 500

dittoalex

{
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "s3:GetBucketLocation",
        "s3:GetObject",
        "s3:ListBucket"
      ],
      "Resource": [

danielctull

import Cocoa

class ReplaceSegue: NSStoryboardSegue {

	override func perform() {

		guard
			let source = sourceController as? NSViewController,
			let new = destinationController as? NSViewController,

aarondfrancis

(function ($$) {
    // Open a console in your web browser and paste
    // this entire script into it. This script doesn't 
    // phone home at any point, you have to do that 
    // manually. Still, give it a read.
    
    // `Cmd + Opt + J` on Chrome

    var user;