Clicking restore-defaults on an Experiment or Instrument tab in a batch should only affect that tab and batch. This commit fixes a bug where a notification was sent to all batches, and every Experiment and Instrument tab was being reset. The fix is to separate updating the instrument (which is required to ensure we have up-to-date settings loaded from the instrument) from the subsequent notification which updates all batches. Instead, the particular Experiment/Instrument tab where the request was made restores its own defaults itself.

Re #28429

The problem here was that when the instrument is set on the new batch, a notification is sent that the instrument has changed and all batches were being reset. However, although the instrument has been set, we can just check whether it is different to the current instrument to check whether it really has changed, and if not, do not do the updates.

Re #28429

Re #28429

The original test json string contained largely default/empty values so it is hard to tell whether they are really being loaded. Add a new string containing fully populated values as well as an "empty" batch representation containing defaults. Use these for the main window containing two batches.

Add a new unit test to test the case where the instrument has changed.

Re #28429

Tidy up existing tests to improve readability

Re #28429

Re #28429

Emit Kafka exception msg when err callback used

Add quotes to Span patching step, in case there are spaces

Update sanitizers to use compiler instrumentation

Determine the total number of detectors used in the spectrum info

Adds clangd to the gitignore, this is generated by using the language
server on a source dir in VS code

Fixes sanitizers not switching off if USE_SANITIZER was set to off.
Additionally gets rid of a space between LSAN_OPTIONS and the actual
options, which was causing the suppressions file to be ignored.

Previously Kafka dropped the exception and just incremented using the
same callback our wait. This will now print the exception message
associated, so we can distinguish between a successful and failed
callback in unit test logs.

I could have made it so that the exception is thrown in the main thread
by taking a s_ptr. However it quickly becomes unweildly for a simple
probe, and we only gain the stack trace - which was already lost when
extractData re throws the exception.

Move FileDescriptor and NexusDescriptor includes to derived classes

Avoid extra multiply in Plus and Minus

Added Mantid::NeXus::NexusHDF5Descriptor class caching metadata

Populates Metadata entries in constructor
Internal reference accessible in public function
Added unit test
Address CI issue with POSIX strdup function

Improve Outputs When Focusing in Eng Diff 2 GUI

Change Algorithm State tracking

Co-Authored-By: StephenSmith25 <56431339+StephenSmith25@users.noreply.github.com>

Adds quotes to the patching step for span in case there are spaces in
the path causing it to fail

Signed-off-by: Steven Hahn <hahnse@ornl.gov>

Stop for loop in Rebin2D asking for next element after the last bin

Remove extra indents that were causing Flake8 Jenkins failure

Makes clang-format parallel where possible

Update google test / span

Make python targets runnable on MSVC IDE

Refactored Track to use boost::container::small_vector with optimised vector size

Signed-off-by: Steven Hahn <hahnse@ornl.gov>

Signed-off-by: Steven Hahn <hahnse@ornl.gov>

Update copyright to include CSNS

Exits the sanitizer build on first exit, since Ctest is the handler it
will continue to schedule other tests, but mark the current test as
failed this way.

Updates the CMake configuration to set our debugging targets. This means
a user can debug Workbench or System tests, which have a python entry
point, directly from the MSVC IDE.