The console-output-datadog's discuss from socketry

Initializing using `console-output-datadog` results in `uninitialized constant Console::Output::Datadog (NameError)`

When attempting to use Console with CONSOLE_OUTPUT set to Console::Output::Datadog,Console::Output::Default, I get the following error:

.../ruby/gems/console-1.23.2/lib/console/output.rb:19:in `block in new': uninitialized constant Console::Output::Datadog (NameError)

					Output.const_get(name).new(output, **options)
					      ^^^^^^^^^^
	from .../ruby/gems/console-1.23.2/lib/console/output.rb:18:in `each'
	from .../ruby/gems/console-1.23.2/lib/console/output.rb:18:in `inject'
	from .../ruby/gems/console-1.23.2/lib/console/output.rb:18:in `new'
	from .../ruby/gems/console-1.23.2/lib/console/logger.rb:51:in `default_logger'
	from .../ruby/gems/console-1.23.2/lib/console/logger.rb:60:in `local'
	from .../ruby/gems/fiber-local-1.0.0/lib/fiber/local.rb:45:in `instance'
	from .../ruby/gems/console-1.23.2/lib/console.rb:15:in `logger'
	from .../ruby/gems/falcon-0.42.3/bin/falcon:30:in `rescue in <top (required)>'
	from .../ruby/gems/falcon-0.42.3/bin/falcon:25:in `<top (required)>'
	from .../ruby/bin/falcon:25:in `load'
	from .../ruby/bin/falcon:25:in `<top (required)>'
	from .../ruby/gems/bundler-2.4.10/lib/bundler/cli/exec.rb:58:in `load'
	from .../ruby/gems/bundler-2.4.10/lib/bundler/cli/exec.rb:58:in `kernel_load'
	from .../ruby/gems/bundler-2.4.10/lib/bundler/cli/exec.rb:23:in `run'
	from .../ruby/gems/bundler-2.4.10/lib/bundler/cli.rb:492:in `exec'
	from .../ruby/gems/bundler-2.4.10/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	from .../ruby/gems/bundler-2.4.10/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	from .../ruby/gems/bundler-2.4.10/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	from .../ruby/gems/bundler-2.4.10/lib/bundler/cli.rb:34:in `dispatch'
	from .../ruby/gems/bundler-2.4.10/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	from .../ruby/gems/bundler-2.4.10/lib/bundler/cli.rb:28:in `start'
	from .../ruby/gems/bundler-2.4.10/exe/bundle:45:in `block in <top (required)>'
	from .../ruby/gems/bundler-2.4.10/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
	from .../ruby/gems/bundler-2.4.10/exe/bundle:33:in `<top (required)>'
	from .../ruby/bin/bundle:25:in `load'
	from .../ruby/bin/bundle:25:in `<main>'

It is being required correctly, as manual initialization of Console::Output::Datadog works just fine.

I was thinking of initializing it manually, but the problem with that approach is that the fiber-local logger is initialized lazily for each fiber, and when it does, it tries to do so using the environment variables again, since the one I initialize manually during the rails app startup is seemingly assigned to Console.logger on a different thread.

Do you have any recommendation on how to proceed?

socketry / console-output-datadog Goto Github PK

console-output-datadog's Issues

Initializing using `console-output-datadog` results in `uninitialized constant Console::Output::Datadog (NameError)`

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

Jobs