feat: add gem for auto-instrumentation in otel-operator by xuan-cao-swi · Pull Request #1384 · open-telemetry/opentelemetry-ruby-contrib

xuan-cao-swi · 2025-01-30T18:55:02Z

Description

This PR aims to contribute a script/gem that can load the necessary OpenTelemetry-related gems and initialize the SDK for the opentelemetry-operator. The script/gem also includes a resource detector as part of its features.

The main idea was inspired by new_relic, which prepends the bundler.require function and places the loading script at the end of the loading procedure. For apps or scripts that don't use Bundler or a Gemfile, more details on variations of app loading can be found in the README. Currently, the goal is to ensure that Rails apps can work, with future improvements in mind.

The reason behind creating this gem is to facilitate easy installation and dependency enforcement. Although for the OpenTelemetry-Operator Node.js, it puts the loading script directly in the src folder (and then copy over to binding volume), it still relies on the auto-instrumentation-node package to install all required packages (e.g., API/SDK and instrumentation packages).

The main purpose of the gem is to serve the OpenTelemetry-Operator, which requires more configuration changes (see the configuration section in the README). Users don't need to modify their Ruby app codebase while using the instrumentation from OpenTelemetry-Ruby, but anyone can still use it in any environment.

The gem name, file structure, and implementation need more suggestions to make them more reasonable. I have tested it with rails and sinatra (through rackup), and I currently still in the process of testing against the opentelemetry operator cluster locally. Once the operator testing done, I will mark the pr as ready.

Related to open-telemetry/opentelemetry-operator#3756

xuan-cao-swi · 2025-02-26T19:14:43Z

We don't need to push to make the gem ready/release, but the script file need to get some review first.

github-actions · 2025-03-29T02:02:41Z

👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this pull request will be closed eventually by the stale bot

github-actions · 2025-05-03T02:05:46Z

👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this pull request will be closed eventually by the stale bot

thompson-tomo · 2026-04-09T14:35:26Z

+  - Triager
+  - triagers
+  - Untrace
+  - vitess
+  - webmocks
+  - yardoc
+  - rackup
+  - traceparent


Are we sure all of these are needed, I believe I added some of these to cspell ie yard

I am not sure about what is needed; feel free to suggest which one to remove.

My suggestion would be to remove them all & then see which one's you get warnings for.

Removed these words

Just checking on this one as I can still see them.

thompson-tomo

Do we also need to add it to toys for the release process?

…trib into auto-instrumentation

Co-authored-by: Ariel Valentin <arielvalentin@users.noreply.github.com> Co-authored-by: James Thompson <thompson.tomo@outlook.com>

…lemetry-ruby-contrib into auto-instrumentation

thompson-tomo

Note we are still needing it to be added to labeller & release process. I have drafted updated docs to help guide this process aka #2219.

thompson-tomo · 2026-04-13T15:47:08Z

+Naming/FileName:
+  Enabled: false
+Gemspec/DevelopmentDependencies:
+  Enabled: false


Suggested change

Naming/FileName:

Enabled: false

Gemspec/DevelopmentDependencies:

Enabled: false

If naming is an issue add an exclusion rather than disable entire cop.

thompson-tomo · 2026-04-13T15:49:36Z

+
+  if spec.respond_to?(:metadata)
+    spec.metadata['changelog_uri'] = "https://rubydoc.info/gems/#{spec.name}/#{spec.version}/file/CHANGELOG.md"
+    spec.metadata['source_code_uri'] = 'https://github.com/open-telemetry/opentelemetry-ruby-contrib/auto-instrumentation'


Update to match existing instrumentations ie use tag and directory.

thompson-tomo · 2026-04-13T15:51:28Z

+gemspec
+
+group :test do
+  gem 'bundler'


This should have a version if we in fact need it no other gem list it.

Removed the bundler

…lemetry-ruby-contrib into auto-instrumentation

kaylareopelle

This is so close! I noticed a few things in my review today.

kaylareopelle · 2025-10-31T21:04:56Z

+  module OTelInitializer
+    @initialized = false
+
+    OTEL_INSTRUMENTATION_MAP = {


Are there any new instrumentations we should add here?

Updated. I will create a workflow that keep track of this OTEL_INSTRUMENTATION_MAP later.

I think it's worth to explore what James comment to have separate repo for this gem.

When I look at the github org I see the following repos for auto instrumentation:
https://github.com/open-telemetry/opentelemetry-go-instrumentation
https://github.com/open-telemetry/opentelemetry-java-instrumentation
https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation
https://github.com/open-telemetry/opentelemetry-php-instrumentation

Since it will have dependabot that need to track the latest sdk and instrumentation gem, I don't want to pollute the PR pages.

kaylareopelle · 2026-04-14T14:03:05Z

+require 'version'
+
+Gem::Specification.new do |spec|
+  spec.name        = 'auto-instrumentation'


What do you think about calling the gem opentelemetry-auto-instrumentation? Without the opentelemetry prefix it feels very broad.

I remember talking about naming a long time ago, but haven't found that conversation.

@thompson-tomo made a similar comment in the changelog about updating the name.

Updated to opentelemetry-auto-instrumentation. Let me know if you want the folder name also changed to opentelemetry-auto-instrumentation

kaylareopelle · 2026-04-14T14:08:25Z

+opentelemetry-instrumentation-all
+opentelemetry-exporter-otlp
+opentelemetry-helpers-mysql
+opentelemetry-helpers-sql-obfuscation


I think we want to replace the sql-obfuscation gem with opentelemetry-helpers-sql-processor

kaylareopelle · 2026-04-14T14:08:59Z

+opentelemetry-helpers-sql-obfuscation
+opentelemetry-resource-detector-azure
+opentelemetry-resource-detector-container
+opentelemetry-resource-detector-aws


We also have a GCP resource detector. Does that make sense to include?

The GCP resource detector depends on the extra google-cloud-env gem, which can introduce version conflicts. I’m leaning toward only copying the OTEL‑related gems into the operator.
That gem mainly pulls GCP metadata, whereas the other resource detectors use more self‑contained methods like fetching metadata from a local URL.

kaylareopelle · 2026-04-14T14:11:40Z

+
+## Configuration
+
+The following environment variables are specific to this gem (not standard OpenTelemetry variables):


What do you think about mentioning that all other OTEL environment variables can still be used for configuration with this gem?

kaylareopelle · 2026-04-14T14:27:17Z

+
+require 'test_helper'
+
+describe 'AutoInstrumentation' do


Suggested change

describe 'AutoInstrumentation' do

describe 'OpenTelemetry::AutoInstrumentation' do

kaylareopelle · 2026-04-14T14:29:54Z

+require 'opentelemetry-sdk'
+require 'opentelemetry-instrumentation-all'


If we require these and opentelemetry/resource/detector here, could we be getting false positives? (just thinking about open-telemetry/opentelemetry-ruby#1956)

The tests seem to pass even if we remove those requires.

yeah, these gem are not need to require here (removed).

kaylareopelle · 2026-04-14T14:41:35Z

+      warn '[OpenTelemetry] WARNING: Detected OpenTelemetry gems in your Gemfile: ' \
+           "#{gem_names}. When using auto-instrumentation, OpenTelemetry gems are loaded " \
+           'from the auto-instrumentation gem path, NOT from your bundle. The gem versions ' \
+           'in your Gemfile/Gemfile.lock are not used and may cause version conflicts or ' \
+           'unexpected behavior. Please remove these gems from your Gemfile when using ' \
+           'auto-instrumentation.'


Does this mean that people who want to use metrics or logs can't use auto instrumentation? If that's the case, what do you think about adding a note to the README?

I added the metrics and logs sdk support in the autoinstrumentation (also include the example in rails-example)

kaylareopelle · 2026-04-14T14:55:34Z

+gem 'rake', '13.0.6'
+gem 'bigdecimal', '3.1.3'
+gem 'logger', '1.5.3'


Why are these versions locked?

This was the main problem I encountered with the rails example. I was using Ruby 3.4 and these versions are older than the latest versions. If I commented these versions out and regenerated the Gemfile.lock, everything worked fine.

When I tried to follow the instructions in the example README and installed the versions it asked for specifically, I kept getting the same error.

This is the issue of version conflict between user gem env and the auto-instrumentation env.
I added the note that this won't be an issue in operator because we only copy otel-related gem to operator.
To make this example run, you may need to manually update the system gem (e.g. gem update rake/gem install rake -v 13.4.1) when you see something like

You have already activated rake 13.4.2, but your Gemfile requires rake 13.4.1. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)

…lemetry-ruby-contrib into auto-instrumentation

arielvalentin · 2026-04-18T14:57:06Z

@xuan-cao-swi can I ask you to resolve conflicts?

Copilot

Pull request overview

Adds a new opentelemetry-auto-instrumentation Ruby gem/package intended to support OpenTelemetry Operator-style zero-code auto-instrumentation (via RUBYOPT), along with examples, tests, and CI wiring.

Changes:

Introduces the opentelemetry-auto-instrumentation gem (gemspec, loader/initializer, versioning, docs, rake tasks, rubocop config).
Adds Minitest coverage that runs initialization in a forked subprocess and validates traces/metrics/logs and Bundler warning behavior.
Updates repo CI to run this new package’s checks and adjusts Docker build dependencies/base image.

Show a summary per file

File	Description
packages/auto-instrumentation/test/test_helper.rb	Adds subprocess test harness for isolated auto-instrumentation initialization.
packages/auto-instrumentation/test/opentelemetry-auto-instrumentation_test.rb	Adds Minitest specs for initialization, signal emission, and Bundler Gemfile warning behavior.
packages/auto-instrumentation/opentelemetry-auto-instrumentation.gemspec	Defines new gem metadata and runtime dependencies.
packages/auto-instrumentation/lib/version.rb	Introduces gem version constant.
packages/auto-instrumentation/lib/opentelemetry-auto-instrumentation.rb	Implements Bundler hook + SDK/config initialization + resource detection wiring.
packages/auto-instrumentation/example/simple-example/app.rb	Adds minimal script demonstrating HTTP client instrumentation.
packages/auto-instrumentation/example/simple-example/Gemfile	Adds Gemfile scaffold for the simple example.
packages/auto-instrumentation/example/rails-example/config.ru	Adds rackup entrypoint for Rails example.
packages/auto-instrumentation/example/rails-example/app.rb	Adds Rails example application emitting metrics/logs.
packages/auto-instrumentation/example/rails-example/Gemfile	Adds dependencies for Rails example.
packages/auto-instrumentation/example/README.md	Documents how to run the included examples.
packages/auto-instrumentation/Rakefile	Adds test/rubocop/yard tasks for the new package.
packages/auto-instrumentation/README.md	Adds package-level documentation and configuration reference.
packages/auto-instrumentation/LICENSE	Adds license file for the new package.
packages/auto-instrumentation/Gemfile	Adds development/test dependencies for the new package.
packages/auto-instrumentation/CHANGELOG.md	Adds changelog scaffold.
packages/auto-instrumentation/.rubocop.yml	Adds package-specific RuboCop config/exclusions.
Dockerfile	Updates base image and adds `yaml-dev` dependency.
.github/workflows/ci-contrib.yml	Adds CI job and path filters for packages, including this new gem.
.cspell.yml	Removes an extraneous entry/line.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comments suppressed due to low confidence (1)

packages/auto-instrumentation/example/rails-example/app.rb:55

The RuboCop directive comment is malformed (# rubocop enable:). RuboCop expects # rubocop:enable ..., so this line won't actually re-enable the cop (and the disable above won’t work either).

# rubocop enable:Style/OneClassPerFile

Files reviewed: 20/20 changed files
Comments generated: 9

Copilot · 2026-04-18T15:03:30Z

+# rubocop disable:Style/OneClassPerFile
+class ApplicationController < ActionController::API


The RuboCop directive comment is malformed (# rubocop disable:). RuboCop expects # rubocop:disable ..., so this line won't actually suppress the cop.

This issue also appears on line 55 of the same file.

Copilot · 2026-04-18T15:03:30Z

+
+  if spec.respond_to?(:metadata)
+    spec.metadata['changelog_uri'] = "https://rubydoc.info/gems/#{spec.name}/#{spec.version}/file/CHANGELOG.md"
+    spec.metadata['source_code_uri'] = "https://github.com/open-telemetry/opentelemetry-ruby-contrib/tree/#{spec.name}/v#{spec.version}/packages/opentelemetry-auto-instrumentation"


spec.metadata['source_code_uri'] points to packages/opentelemetry-auto-instrumentation, but this gem lives under packages/auto-instrumentation in the repository. This makes the published metadata link incorrect.

Suggested change

spec.metadata['source_code_uri'] = "https://github.com/open-telemetry/opentelemetry-ruby-contrib/tree/#{spec.name}/v#{spec.version}/packages/opentelemetry-auto-instrumentation"

spec.metadata['source_code_uri'] = "https://github.com/open-telemetry/opentelemetry-ruby-contrib/tree/#{spec.name}/v#{spec.version}/packages/auto-instrumentation"

Copilot · 2026-04-18T15:03:30Z

+url = URI.parse('http://catfact.ninja/fact')
+req = Net::HTTP::Get.new(url.to_s)
+Net::HTTP.start(url.host, url.port) do |http|
+  http.request(req)


This example uses URI.parse and Net::HTTP without requiring the stdlib modules (require 'uri' and require 'net/http'), so it will raise NameError in a clean Ruby process.

Copilot · 2026-04-18T15:03:31Z

+    name: "auto-instrumentation / ${{ matrix.os }}"
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1


This job pins actions/checkout to a different commit (# v6.0.1) than the rest of the workflow (# v6.0.2 at lines 49/90/130/168/206). To keep dependency management consistent, pin this step to the same SHA/version used elsewhere in the repo.

Suggested change

- uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1

- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2

Copilot · 2026-04-18T15:03:31Z

+
+      env.split(',').map { |instrumentation| OTEL_INSTRUMENTATION_MAP[instrumentation] }


_otel_determine_enabled_instrumentation can return nil entries (unknown keys or whitespace like "redis, mysql2"), which later leads to c.use nil raising. Consider normalizing tokens (strip/downcase) and dropping/handling unknown instrumentations (e.g., compact + warning in debug mode).

Suggested change

env.split(',').map { |instrumentation| OTEL_INSTRUMENTATION_MAP[instrumentation] }

unknown_instrumentations = []

enabled_instrumentation = env.split(',').map do |instrumentation|

normalized_instrumentation = instrumentation.strip.downcase

next if normalized_instrumentation.empty?

mapped_instrumentation = OTEL_INSTRUMENTATION_MAP[normalized_instrumentation]

unknown_instrumentations << instrumentation if mapped_instrumentation.nil?

mapped_instrumentation

end.compact

if ENV['OTEL_RUBY_AUTO_INSTRUMENTATION_DEBUG'] == 'true' && unknown_instrumentations.any?

warn '[OpenTelemetry] WARNING: Ignoring unknown instrumentations from ' \

"OTEL_RUBY_ENABLED_INSTRUMENTATIONS: #{unknown_instrumentations.join(', ')}"

end

enabled_instrumentation

Copilot · 2026-04-18T15:03:31Z

+| `OTEL_RUBY_ENABLED_INSTRUMENTATIONS` | Only load specific instrumentations (comma-separated). Omit to load all available. | `redis,mysql2,faraday` |
+| `OTEL_RUBY_ADDITIONAL_GEM_PATH` | Custom gem installation path for OpenTelemetry Operator environments. | `/custom/gem/path` |
+| `OTEL_RUBY_AUTO_INSTRUMENTATION_DEBUG` | Set to `true` for debug output during initialization. | `true` |
+| `OTEL_RUBY_UNLOAD_LIBRARY` | Prevent specific gems from being preloaded (e.g., `google-protobuf`). | `google-protobuf` |


OTEL_RUBY_UNLOAD_LIBRARY is documented here, but there is no corresponding implementation in the gem (no code references this env var). Either implement the behavior or remove it from the configuration table to avoid misleading users.

Suggested change

| `OTEL_RUBY_UNLOAD_LIBRARY` | Prevent specific gems from being preloaded (e.g., `google-protobuf`). | `google-protobuf` |

Copilot · 2026-04-18T15:03:31Z

+
+# /otel-auto-instrumentation-ruby is default path for otel operator (ruby.go)
+# If requires different gem path to load gem, set env OTEL_RUBY_ADDITIONAL_GEM_PATH
+gem_path = ENV['OTEL_RUBY_ADDITIONAL_GEM_PATH'] || '/otel-auto-instrumentation-ruby' || Gem.dir


gem_path fallback is incorrect: ENV[...] || '/otel-auto-instrumentation-ruby' || Gem.dir will never reach Gem.dir because the string literal is always truthy. This prevents falling back to the default RubyGems directory when OTEL_RUBY_ADDITIONAL_GEM_PATH is unset (or when the operator path doesn't exist).

Suggested change

gem_path = ENV['OTEL_RUBY_ADDITIONAL_GEM_PATH'] || '/otel-auto-instrumentation-ruby' || Gem.dir

gem_path_candidates = [

ENV['OTEL_RUBY_ADDITIONAL_GEM_PATH'],

'/otel-auto-instrumentation-ruby',

Gem.dir

].compact

gem_path = gem_path_candidates.find { |path| File.directory?(path) } || Gem.dir

Copilot · 2026-04-18T15:03:31Z

+
+lib = File.expand_path('lib', __dir__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'version'


Gemspec version loading deviates from established repo convention: gemspecs require a fully namespaced version file (e.g. helpers/sql/opentelemetry-helpers-sql.gemspec:9). Requiring plain 'version' risks load path collisions with other gems/files named version.rb.

Suggested change

require 'version'

require 'opentelemetry/auto/instrumentation/version'

xuan-cao-swi added 8 commits January 29, 2025 14:59

feat: init commit for zero-code instrumentation

9d13c5a

lint

444959a

rubocop

4c0c97b

enforce the dependencies version

8a2fadd

assume use bundle exec all the time

f96a637

merge

ef5f348

update readme

60a3ab2

cspell

3512225

xuan-cao-swi marked this pull request as ready for review February 26, 2025 19:13

xuan-cao-swi requested review from a team, ahayworth, arielvalentin, dazuma, ericmustin, fbogsany, kaylareopelle, mwear, plantfansam, robbkidd, robertlaurin and simi as code owners February 26, 2025 19:13

xuan-cao-swi mentioned this pull request Mar 3, 2025

Autoinstrumentation for opentelemetry ruby open-telemetry/opentelemetry-operator#3762

Open

github-actions Bot added the stale Marks an issue/PR stale label Mar 29, 2025

kaylareopelle removed the stale Marks an issue/PR stale label Apr 2, 2025

update the script

2c880da

github-actions Bot added the stale Marks an issue/PR stale label May 3, 2025

thompson-tomo reviewed Apr 9, 2026

View reviewed changes

Comment thread packages/auto-instrumentation/CHANGELOG.md Outdated

xuan-cao-swi and others added 6 commits April 13, 2026 11:10

Merge branch 'main' of github.com:xuan-cao-swi/opentelemetry-ruby-con…

b644d81

…trib into auto-instrumentation

Apply suggestions from code review

608417a

Co-authored-by: Ariel Valentin <arielvalentin@users.noreply.github.com> Co-authored-by: James Thompson <thompson.tomo@outlook.com>

Merge branch 'auto-instrumentation' of github.com:xuan-cao-swi/opente…

bf98eea

…lemetry-ruby-contrib into auto-instrumentation

revision

95958ec

update bundler version

c9b79f3

update bundler version

31ea352

thompson-tomo reviewed Apr 13, 2026

View reviewed changes

xuan-cao-swi and others added 5 commits April 13, 2026 12:44

update

4a15e56

rubocop format

ef6d1d3

Merge branch 'main' into auto-instrumentation

a4c0b64

remove cspell words

74a9bc1

Merge branch 'auto-instrumentation' of github.com:xuan-cao-swi/opente…

01e4f2e

…lemetry-ruby-contrib into auto-instrumentation

kaylareopelle reviewed Apr 14, 2026

View reviewed changes

xuan-cao-swi and others added 6 commits April 16, 2026 12:48

revision

362d6e1

Merge branch 'main' into auto-instrumentation

15b4dd9

lint

387f1a7

Merge branch 'auto-instrumentation' of github.com:xuan-cao-swi/opente…

8cc8981

…lemetry-ruby-contrib into auto-instrumentation

remove unnecessary require in test

d62d69c

ci fix

82ed423

thompson-tomo reviewed Apr 17, 2026

View reviewed changes

Comment thread Dockerfile Outdated

arielvalentin requested review from Copilot and removed request for marcotc April 18, 2026 14:57

Copilot started reviewing on behalf of arielvalentin April 18, 2026 14:57 View session

Merge branch 'main' into auto-instrumentation

ef1987e

Copilot AI reviewed Apr 18, 2026

View reviewed changes

Merge branch 'main' into auto-instrumentation

c08bdb2


		## Configuration

		The following environment variables are specific to this gem (not standard OpenTelemetry variables):

	describe 'AutoInstrumentation' do
	describe 'OpenTelemetry::AutoInstrumentation' do

		require 'opentelemetry-sdk'
		require 'opentelemetry-instrumentation-all'

		# rubocop disable:Style/OneClassPerFile
		class ApplicationController < ActionController::API

	spec.metadata['source_code_uri'] = "https://github.com/open-telemetry/opentelemetry-ruby-contrib/tree/#{spec.name}/v#{spec.version}/packages/opentelemetry-auto-instrumentation"
	spec.metadata['source_code_uri'] = "https://github.com/open-telemetry/opentelemetry-ruby-contrib/tree/#{spec.name}/v#{spec.version}/packages/auto-instrumentation"

	- uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
	- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2


		env.split(',').map { \|instrumentation\| OTEL_INSTRUMENTATION_MAP[instrumentation] }

-      env.split(',').map { |instrumentation| OTEL_INSTRUMENTATION_MAP[instrumentation] }
+      unknown_instrumentations = []
+      enabled_instrumentation = env.split(',').map do |instrumentation|
+        normalized_instrumentation = instrumentation.strip.downcase
+        next if normalized_instrumentation.empty?
+        mapped_instrumentation = OTEL_INSTRUMENTATION_MAP[normalized_instrumentation]
+        unknown_instrumentations << instrumentation if mapped_instrumentation.nil?
+        mapped_instrumentation
+      end.compact
+      if ENV['OTEL_RUBY_AUTO_INSTRUMENTATION_DEBUG'] == 'true' && unknown_instrumentations.any?
+        warn '[OpenTelemetry] WARNING: Ignoring unknown instrumentations from ' \
+             "OTEL_RUBY_ENABLED_INSTRUMENTATIONS: #{unknown_instrumentations.join(', ')}"
+      end
+      enabled_instrumentation

-gem_path = ENV['OTEL_RUBY_ADDITIONAL_GEM_PATH'] || '/otel-auto-instrumentation-ruby' || Gem.dir
+gem_path_candidates = [
+  ENV['OTEL_RUBY_ADDITIONAL_GEM_PATH'],
+  '/otel-auto-instrumentation-ruby',
+  Gem.dir
+].compact
+gem_path = gem_path_candidates.find { |path| File.directory?(path) } || Gem.dir

	require 'version'
	require 'opentelemetry/auto/instrumentation/version'

Conversation

xuan-cao-swi commented Jan 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Uh oh!

xuan-cao-swi commented Feb 26, 2025

Uh oh!

github-actions Bot commented Mar 29, 2025

Uh oh!

github-actions Bot commented May 3, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

thompson-tomo left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

thompson-tomo left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

thompson-tomo Apr 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kaylareopelle left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

xuan-cao-swi Apr 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

xuan-cao-swi commented Jan 30, 2025 •

edited

Loading

thompson-tomo left a comment •

edited

Loading

thompson-tomo Apr 13, 2026 •

edited

Loading

xuan-cao-swi Apr 16, 2026 •

edited

Loading

xuan-cao-swi Apr 16, 2026 •

edited

Loading