Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Failure with Rails 5

Aperta
#25 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
rails, ruby

Direzione di ricerca

Riproduci il malfunzionamento con Rails 5.2.6 ed ecs-logging 1.0.0, quindi esamina ecs_logging/logger.rb insieme a active_support/tagged_logging.rb nei punti di chiamata dello stack trace. Determina perché gli argomenti con nome sono incompatibili; il lavoro è completato quando l’applicazione Rails si avvia e il logging non solleva più questo ArgumentError.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

agent-ruby

Trying to use ecs-logging with Rails 5:

Traceback (most recent call last):
	33: from bin/rails:4:in `<main>'
	32: from /home/user/.ruby/gems/activesupport-5.2.6/lib/active_support/dependencies.rb:291:in `require'
	31: from /home/user/.ruby/gems/activesupport-5.2.6/lib/active_support/dependencies.rb:257:in `load_dependency'
	30: from /home/user/.ruby/gems/activesupport-5.2.6/lib/active_support/dependencies.rb:291:in `block in require'
	29: from /home/user/.ruby/gems/bootsnap-1.6.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
	28: from /home/user/.ruby/gems/bootsnap-1.6.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
	27: from /home/user/.ruby/gems/bootsnap-1.6.0/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
	26: from /home/user/.ruby/gems/bootsnap-1.6.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
	25: from /home/user/.ruby/gems/bootsnap-1.6.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
	24: from /home/user/.ruby/gems/railties-5.2.6/lib/rails/commands.rb:18:in `<main>'
	23: from /home/user/.ruby/gems/railties-5.2.6/lib/rails/command.rb:46:in `invoke'
	22: from /home/user/.ruby/gems/railties-5.2.6/lib/rails/command/base.rb:69:in `perform'
	21: from /home/user/.ruby/gems/thor-0.19.4/lib/thor.rb:369:in `dispatch'
	20: from /home/user/.ruby/gems/thor-0.19.4/lib/thor/invocation.rb:126:in `invoke_command'
	19: from /home/user/.ruby/gems/thor-0.19.4/lib/thor/command.rb:27:in `run'
	18: from /home/user/.ruby/gems/railties-5.2.6/lib/rails/commands/server/server_command.rb:142:in `perform'
	17: from /home/user/.ruby/gems/railties-5.2.6/lib/rails/commands/server/server_command.rb:142:in `tap'
	16: from /home/user/.ruby/gems/railties-5.2.6/lib/rails/commands/server/server_command.rb:147:in `block in perform'
	15: from /home/user/.ruby/gems/railties-5.2.6/lib/rails/commands/server/server_command.rb:51:in `start'
	14: from /home/user/.ruby/gems/railties-5.2.6/lib/rails/commands/server/server_command.rb:89:in `log_to_stdout'
	13: from /home/user/.ruby/gems/rack-2.2.3/lib/rack/server.rb:422:in `wrapped_app'
	12: from /home/user/.ruby/gems/railties-5.2.6/lib/rails/commands/server/server_command.rb:29:in `app'
	11: from /home/user/.ruby/gems/activesupport-5.2.6/lib/active_support/deprecation/instance_delegator.rb:29:in `warn'
	10: from /home/user/.ruby/gems/activesupport-5.2.6/lib/active_support/deprecation/instance_delegator.rb:22:in `warn'
	 9: from /home/user/.ruby/gems/activesupport-5.2.6/lib/active_support/deprecation/reporting.rb:22:in `warn'
	 8: from /home/user/.ruby/gems/activesupport-5.2.6/lib/active_support/deprecation/reporting.rb:22:in `tap'
	 7: from /home/user/.ruby/gems/activesupport-5.2.6/lib/active_support/deprecation/reporting.rb:23:in `block in warn'
	 6: from /home/user/.ruby/gems/activesupport-5.2.6/lib/active_support/deprecation/reporting.rb:23:in `each'
	 5: from /home/user/.ruby/gems/activesupport-5.2.6/lib/active_support/deprecation/reporting.rb:23:in `block (2 levels) in warn'
	 4: from /home/user/.ruby/gems/activesupport-5.2.6/lib/active_support/deprecation/behaviors.rb:33:in `block in <class:Deprecation>'
	 3: from /home/user/.ruby/gems/ecs-logging-1.0.0/lib/ecs_logging/logger.rb:73:in `block (2 levels) in <class:Logger>'
	 2: from /home/user/.ruby/gems/ecs-logging-1.0.0/lib/ecs_logging/logger.rb:53:in `add'
	 1: from /home/user/.ruby/gems/ecs-logging-1.0.0/lib/ecs_logging/logger.rb:94:in `format_message'
/home/user/.ruby/gems/activesupport-5.2.6/lib/active_support/tagged_logging.rb:22:in `call': unknown keywords: :"transaction.id", :"trace.id", :"span.id" (ArgumentError)

Not sure what to do at that stage.

Lingua principale
Ruby
Stelle
8
Fork
10
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di elastic/ecs-logging-ruby

Tutte le issue di elastic/ecs-logging-ruby

Issue simili

Altre issue su Ruby

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.