YJIT makes the app slower on Digital Ocean App Platform / DOAP (the Heroku-like product, not Droplet VMs): the container runs in a sandbox (gVisor) where system calls are very expensive, and YJIT makes a lot of them while compiling.
Request latency over ~10 minutes in production:
| YJIT off | YJIT warm-up (first ~5 min) | YJIT after warm-up |
|---|
| name | form-markdown |
|---|---|
| description | A text-based format for prototyping simple web forms and pages. |
We frequently want to quickly prototype forms in order to collaborate on the copywriting of the form. For example, pasting it into a Google Doc in order to revise it.
The format is intended for quick back and forth between a rendered HTML form and a textual representation. Because the focus is on copywriting, the format is not intended to extensively capture layout or complex design elements.
## Heading is card heading, which sometimes can function as the label for a simple card
| # config/initializers/database_executor_check.rb | |
| ActiveSupport.on_load(:active_record) do | |
| ActiveRecord::ConnectionAdapters::ConnectionPool.prepend(Module.new do | |
| def checkout(*args) | |
| # Check if an ActiveSupport::Executor or ExecutionWrapper is active on this thread | |
| unless ActiveSupport::Executor.active? | |
| Rails.logger.warn <<~MSG | |
| [Warning] Database connection checked out outside of an active ActiveSupport::Executor! | |
| Call stack: |
You are acting as a reviewer for a proposed code change made by another engineer.
Below are some default guidelines for determining whether the original author would appreciate the issue being flagged.
These are not the final word in determining whether an issue is a bug. In many cases, you will encounter other, more specific guidelines. These may be present elsewhere in a developer message, a user message, a file, or even elsewhere in this system message. Those guidelines should be considered to override these general instructions.
Here are the general guidelines for determining whether something is a bug and should be flagged.
| name: Update Metabase base image | |
| on: | |
| schedule: | |
| - cron: '0 17 * * *' # Every day at ~10am Pacific (17:00 UTC) | |
| workflow_dispatch: | |
| jobs: | |
| update-metabase: | |
| runs-on: ubuntu-latest |
| # frozen_string_literal: true | |
| RSpec.shared_examples "strip normalizes text columns" do | |
| it "strip normalizes text column values" do | |
| text_columns = described_class.columns.filter_map do |col| | |
| next unless [:text, :string].include?(col.sql_type_metadata.type) | |
| next if described_class.defined_enums.key?(col.name) | |
| attr_type = described_class.attribute_types[col.name] |
| #!/usr/bin/env ruby | |
| require "fileutils" | |
| # path to your application root. | |
| APP_ROOT = File.expand_path("..", __dir__) | |
| def system!(*args) | |
| system(*args, exception: true) | |
| end | |
| FileUtils.chdir APP_ROOT do |
---
name: interactive
description: Interactively run Ruby commands against a live Rails process using bin/interact. Supports two modes: a standalone server (bin/interactive) for general exploration, and binding.interactive breakpoints inside tests or app code to pause execution and inspect local state. Use when the user wants to explore live Rails objects, debug a test, or poke at a running process.
---
Interactively run Ruby commands against a live Rails process.
$ARGUMENTS
| name | screenshot |
|---|---|
| description | Takes screenshots at specific points in a system test using the Ruby debugger. Use when the user wants to capture screenshots of a UI flow or page state during a system test without modifying test files. |
Take screenshots at specific points in a system test using the Ruby debugger to inject page.save_screenshot calls non-invasively.
The user wants screenshots of: $ARGUMENTS
| # frozen_string_literal: true | |
| class TunePostgresJob < ApplicationJob | |
| # Global autovacuum setting thresholds. If any global setting exceeds its threshold, | |
| # apply the threshold value as a per-table override. If the global setting is already | |
| # at or below the threshold, remove any per-table override so the global value applies. | |
| AUTOVACUUM_SETTINGS = { | |
| autovacuum_vacuum_scale_factor: 0.01, | |
| autovacuum_analyze_scale_factor: 0.01, | |
| autovacuum_vacuum_insert_scale_factor: 0.01, |