NoMethodError exception in track_request

Open
#4,080 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
rails, ruby
Domain
backend

Research direction

Start by reading app/controllers/concerns/application_concern.rb at track_request (line 65), where the backtrace reports the failure. The exception says id was called on nil; inspect the value used there and how request tracking reaches that callback. The issue names no test, and it does not specify the expected behavior, so confirm the intended handling before considering the bug fixed.

Written by the indexing model from the issue text.

Description

bug

Message

  undefined method `id' for nil:NilClass

Backtrace (last 10 lines)

app/controllers/concerns/application_concern.rb:65 track_request
lib/active_support/callbacks.rb:428 block in make_lambda
lib/active_support/callbacks.rb:249 block in halting
lib/active_support/callbacks.rb:517 block in invoke_after
lib/active_support/callbacks.rb:517 each
lib/active_support/callbacks.rb:517 invoke_after
lib/active_support/callbacks.rb:126 block in run_callbacks
lib/route_translator/extensions/action_controller.rb:18 set_locale_from_url
lib/active_support/callbacks.rb:121 block in run_callbacks
lib/ahoy/controller.rb:45 set_ahoy_request_store

View on AppSignal: https://appsignal.com/populate/sites/5ebb88520264445dc7e68b5c/exceptions/incidents/372?timestamp=2022-04-28T09:10:40Z

Dominant language
Ruby
Stars
79
Forks
31
Avg merge
2d 1h
Merged PRs (30d)
23

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PopulateTools/gobierto

All issues in PopulateTools/gobierto

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.