bkeepers

Queries to show GoodJob queue latency, runtime, and counts in Blazer

bkeepers

// Plain ol' JavaScript module for fetching feature flags from the server
//
//   import { isEnabled } from './flipper.js'
//
//   if (await isEnabled("new_feature")) {
//     // render new feature
//   } else {
//     // render old feature
//   }
//

bkeepers

# config/initializers/flipper.rb

require 'flipper/adapters/sync'

Rails.application.configure do
  # Disable per-request memoization
  config.flipper.memoize = false
end

Flipper.configure do |config|

bkeepers

require "flipper/adapters/dual_write"
require "flipper/adapters/poll"

Flipper.configure do |config|
  config.adapter do
    # Primary storage adapter
    storage_adapter = Flipper::Adapters::ActiveRecord.new

    # Poll the primary storage adapter every 10 seconds to get all features
    poller = Flipper::Adapters::Poll::Poller.get('memoizer', {

bkeepers

# Allow legacy jobs in the queue to be initialized and processed now that they use ActiveJob
#
# Each job must also define `#init_with(coder)` to define how serialized instance variables are
# used to initialize the new ActiveJob instance.
module Delayed::LegacyJob
  class Proxy < SimpleDelegator
    # ActiveJob calls `#perform_now` internally when executing a job to pass arguments to `#perform`
    def perform
      perform_now
    end

bkeepers

# config/initializers/flipper.rb
ActiveSupport::Notifications.subscribe('feature_operation.flipper') do |event|
  operation, feature_name, result = event.payload.values_at(:operation, :feature_name, :result)
  return unless operation == :enabled?
  
  result ? Bugsnag.add_feature_flag(feature_name) : Bugsnag.clear_feature_flag(feature_name)
end

bkeepers

# Register test groups
# https://www.flippercloud.io/docs/features#enablement-group

Flipper.register(:group_a) do |actor, context|
  # Algorithm or database lookup to determine if a user is in this group
  # e.g. 10% percentage of actors
  crc32('group_a' + context.feature_name + actor.flipper_id) % 100 < 10
end

Flipper.register(:group_b) do |actor, context|

bkeepers

We're on the cusp of 2022 and most software is now written in JavaScript, but it is still virtually impossible to fail integration tests on a JavaScript error and get a useful stack trace from the browser.

This gist includes my description of the problem and sample code from my attempts to solve it.

What I want:

• Integration test should fail (preferabbly immediately) on any uncaught JavaScript error (window.onerror, unhandledrejection, etc)
• The stack trace should use source maps and be close to what browsers show in DevTools

The tools I'm currently using:

bkeepers

import { Controller } from 'stimulus'

// Stimulus controller to save location of same-origin iframe in hash of parent
// window and restore on reload.
//
//   <iframe src="…"
//           data-controller="iframe-location"
//           data-action="load->iframe-location#save">
//   </frame>
//

bkeepers