bensheldon

# spec/support/capybara_check_choose.rb

# frozen_string_literal: true
module System
  module CapybaraCheckChoose
    # Speed up `allow_label_click`, which is the default, so that it
    # does the label click immediately rather than waiting for the
    # default strategy to fail
    def _check_with_label(selector, checked, locator,
      allow_label_click: session_options.automatic_label_click, **options)

bensheldon

class Household < ApplicationRecord
  has_many :members
  has_many :expenses
end

class Member < ApplicationRecord
  belongs_to :household
end

class Expense < ApplicationController

bensheldon

My theory is that folks are hallucinating complex structure for these docs. If you read the Cursor forums, people are asking the Cursor LLM how to format them 🙃 Those shared above are the results of writing in the UI and what gets puts into version control.

My approach is that when I am annoyed by something I have to manually fix up, I go update the file.

Some of it is just impossible, like using the new Strong Params expects syntax given the training cutoffs. I’m not going to completely document the interface (cursor/rules can’t link to docs and can only link to a single file) . So I hint it, and it simply hallucinates the interface mostly correctly most of the time. Principle of Least Surprise in practice!

My .cursorrules were pretty inconsistent project to project, and I don’t believe that putting very generic things like “Use exceptions for exceptional cases, not for control flow” or “Use Active Record effectively” improves things.

bensheldon

# frozen_string_literal: true

# == Schema Information
#
# Table name: ai_prompt_responses
#
#  id             :bigint           not null, primary key
#  ai_model       :text
#  completed_at   :datetime
#  error_message  :text

bensheldon

In my application every time I send a newsletter to a User, I create a NewsletterDelivery record. I frequently want to be able to query, for each user, what is the most recent newsletter delivery record. This is called a "last n per group" query and a LATERAL JOIN is the best way to do it imo. But the query I've been using (and I've told people to use, and seen blogged about) is not very good, because the conditions don't get pushed down into the subselect which means that the query ends-up lateral-joining all the records before it applies the conditions for the association.

Instead of doing subselect_table.* the better query does association.id AS assocation_id, subselect_table.id, subselect_table.title, .... and enumerates over all of the columns. This allows the association query, which Active Record tacks on at the end as WHERE association_id = $1 or WHERE association_id IN ($1, $2, $3, ...) to be pushed down c

bensheldon

#!/usr/bin/env ruby

# Place in your project (don't forget to chmod +x):
# bin/autoload-check

# Allow these files to be fixed later
allowlist = [
  "ExampleClass" # why?
]

bensheldon

Investigating memory growth with Sheap in a Rails application.

Ran this locally because of an issue with rbtrace not working with Puma when requests aren't actively arriving:

while true; do
  status_code=$(curl -o /dev/null -s -w "%{http_code}\n" -I "https://dayoftheshirt.com")
  echo "Status code: $status_code"
  sleep 1
done

bensheldon

# bin/rails-production

#!/usr/bin/env ruby

# Simulate a production environment locally
# for the purpose of profiling

ENV['RAILS_ENV'] = 'production'
ENV['NODE_ENV'] = 'production'
ENV['RACK_ENV'] = 'production'

bensheldon

diff --git a/app/controllers/account/registrations_controller.rb b/app/controllers/account/registrations_controller.rb
index 376f20a77..a554c9f8d 100644
--- a/app/controllers/account/registrations_controller.rb
+++ b/app/controllers/account/registrations_controller.rb
@@ -1,6 +1,8 @@
 # frozen_string_literal: true
 module Account
   class RegistrationsController < Devise::RegistrationsController
+    before_action :reject_spam, only: :create
+

bensheldon

/**
 * Disclaimer: This works as of the date of writing (7/11/2023) but there's no guarantees it will work in the future
 * as it depends on selectors on geekbot's web UI, which may change at any time. Use at your own risk.
 *
 * To use this:
 * 1. Navigate to your geekbot random question settings and click "Edit questions" 
 *    so that you see a list of input fields and an "+ Add question" button
 * 2. Open your devtools
 * 3. Pasting this script into the console