Importing go-logging in multiple libraries reset level to default in previous imported places

[op]

Importing go-logging in multiple libraries reset level to default in previous imported places

[op]

That's weird. How does the imports differ between these two places? Same package path?

In logger.go, there's a init() function which might be the culprit. However, the Go specification says that;

If a package has imports, the imported packages are initialized before initializing the package itself.
If multiple packages import a package P, P will be initialized only once.

[sent-hil]

They don't differ, this is roughly the structure:

go/
   src/
       github/
          op/
            go-logging
       koding/ (name of my company)
          tools
             logger (the wrapper package that imports go-logging)
          somelib
             somelib_a (imports koding/tools/logger)
          workers
             worker_a (imports koding/tools/logger and somelib_a)

Yea that's what I thought, init() calls Reset() which sets level to DEBUG. Also one thing I noticed is the debug levels are only reset for somelib_a, not the worker.

[op]

Thanks. I'll try to have a look at it as soon as I get time to. Would be neat if you could provide me with a way to reproduce this. I'm going for almost two weeks vacation soon. Can't make any promises.

PS. If I were you, I would print-debug some. Try adding some code to the Reset() function. Try adding some code to your logger method. Maybe you can try to use sync.Once in the tools/logger which only sets it up from the configuration once? Could it be a race there?

[op]

I haven't been able to reproduce this. Closing for now.