Run autofixers with pinned up packages

Signed-off-by: Tim Paine <[email protected]>

Author: timkpaine

docs/wiki/concepts/Execution-Modes.md

@@ -41,14 +41,14 @@ As always, `csp.now()` should still be used in `csp.node` code, even when runnin
 
 When consuming data from input adapters there are three choices on how one can consume the data:
 
-| PushMode       | EngineMode | Description |
-| :-------       | :--------- | :---------- |
-| **LAST_VALUE** | Simulation | all ticks from input source with duplicate timestamps (on the same timeseries) will tick once with the last value on a given timestamp |
-|           | Realtime   | all ticks that occurred since previous engine cycle will collapse / conflate to the latest value |
+| PushMode           | EngineMode | Description                                                                                                                                                       |
+| :----------------- | :--------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **LAST_VALUE**     | Simulation | all ticks from input source with duplicate timestamps (on the same timeseries) will tick once with the last value on a given timestamp                            |
+|                    | Realtime   | all ticks that occurred since previous engine cycle will collapse / conflate to the latest value                                                                  |
 | **NON_COLLAPSING** | Simulation | all ticks from input source with duplicate timestamps (on the same timeseries) will tick once per engine cycle. subsequent cycles will execute with the same time |
-|           | Realtime | all ticks that occurred since previous engine cycle will be ticked across subsequent engine cycles as fast as possible |
-| **BURST**      | Simulation | all ticks from input source with duplicate timestamps (on the same timeseries) will tick once with a list of all values |
-|           | Realtime | all ticks that occurred since previous engine cycle will tick once with a list of all the values |
+|                    | Realtime   | all ticks that occurred since previous engine cycle will be ticked across subsequent engine cycles as fast as possible                                            |
+| **BURST**          | Simulation | all ticks from input source with duplicate timestamps (on the same timeseries) will tick once with a list of all values                                           |
+|                    | Realtime   | all ticks that occurred since previous engine cycle will tick once with a list of all the values                                                                  |
 
 ## Realtime Group Event Synchronization
 

docs/wiki/dev-guides/Build-CSP-from-Source.md

@@ -198,11 +198,11 @@ By default, we pull and build dependencies with [vcpkg](https://vcpkg.io/en/). W
 
 CSP has listing and auto formatting.
 
-| Language | Linter | Autoformatter | Description |
-| :------- | :----- | :------------ | :---------- |
-| C++      | `clang-format` | `clang-format` | Style |
-| Python   | `ruff`         | `ruff` | Style |
-| Python   | `isort`         | `isort` | Imports |
+| Language | Linter         | Autoformatter  | Description |
+| :------- | :------------- | :------------- | :---------- |
+| C++      | `clang-format` | `clang-format` | Style       |
+| Python   | `ruff`         | `ruff`         | Style       |
+| Python   | `isort`        | `isort`        | Imports     |
 
 **C++ Linting**
 

setup.py

@@ -64,7 +64,7 @@
     )
 
     if VCPKG_TRIPLET is not None:
-        cmake_args.append( f"-DVCPKG_TARGET_TRIPLET={VCPKG_TRIPLET}" )
+        cmake_args.append(f"-DVCPKG_TARGET_TRIPLET={VCPKG_TRIPLET}")
 else:
     cmake_args.append("-DCSP_USE_VCPKG=OFF")