Skip to content

fix(gold-traces): stop setting APPMAP=true for the Ruby frameworks - #13

Closed
kgilpin wants to merge 1 commit into
mainfrom
fix/ruby-no-appmap-env
Closed

kgilpin wants to merge 1 commit into
mainfrom
fix/ruby-no-appmap-env

Conversation

@kgilpin

@kgilpin kgilpin commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

The rspec, minitest and rails-test entries in frameworks.mjs set APPMAP=true on the record command. appmap-ruby does not need it, and it does harm: APPMAP=true enables every recording method, requests included, so a test run also records HTTP requests. The gem prints a warning about exactly this.

In appmap-ruby's DetectEnabled#detect_enabled, enabled_by_testing? runs before globally_enabled? and returns true for rspec, minitest and cucumber with no env var set. So the test hooks turn recording on by themselves.

Changes:

  • frameworks.mjs: the three Ruby frameworks set no environment
  • frameworks.test.mjs: the test now checks that all three set nothing, and says why
  • SKILL.md: the record_env row says it is not needed for Ruby, and why
  • manifest.template.yaml: the cucumber example drops APPMAP=true

record_env still works for a project that needs something else.

🤖 Generated with Claude Code

appmap-ruby's rspec and minitest hooks enable recording by themselves
(DetectEnabled#enabled_by_testing? runs before the APPMAP check). APPMAP=true
enables every recording method, requests included, and the gem warns about it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@kgilpin

kgilpin commented Sep 22, 2026

Copy link
Copy Markdown
Contributor Author

Folded into #12.

@kgilpin kgilpin closed this Sep 22, 2026
@kgilpin
kgilpin deleted the fix/ruby-no-appmap-env branch September 22, 2026 22:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant