Post #4191884

Found and fixed a bug that could cause the MockOscilloscope driver in ngscopeclient to report bogus sample rates and memory depths when working with offline sessions. Unfortunately the bad state is persistent if you save a session when it happens, and it had been lurking for quite a long time. There's no permanent data loss, since if you have waveform data in the session you can figure out the actual sample rate and memory depth from that, but you need to manually patch the "rate" and "depth" entries under the instrument node in the .scopesession to repair the file if you've been affected.