Configdb scope path issue

In reply to silverace99:

Looking at the code and tests I ran, the get_sequencer() call returns the same handle as m_sequencer, so there should be no difference.

I would therefor look at something not matching in the set() hierarchy. I noticed that you used ‘null’ in the set, where typically ‘this’ is used when within the UVM environment.