Python Test uses incorrect python environment

Type: Bug

Behaviour
My tests no longer show up due to a "pytest Discovery Error".  I check the output (thanks for the link) and I see that it tries to use my environment, but then it outputs a warning and tries running pytest with the default python installed on the machine!
I can tell it is the default because in an earlier test I saw it was using the C:/Python311
which doesn't have pytest-cov installed.  I have pytest-cov installed in my conda environment.
When I run the command it says it is using
python -m pytest --collect-only tests

That command fails when according to the Python Output, but it works just fine if I manually run it in my conda environment. When I manually run the command in the default python env (C:\Python311 or whatever), it has the same error output as the python-tests about not accepting coverage-related input arguments.
I don't know why this suddenly started to break?
The problematic part of the output (as far as I can tell):
2024-09-10 10:23:09.863 [info] > ~\AppData\Local\anaconda3\Scripts\conda.exe run -n Autobot --no-capture-output python ~\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\python_files\get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2024.14.0-win32-x64/python_files/printEnvVariables.py
2024-09-10 10:23:09.863 [info] shell: commandPrompt
2024-09-10 10:23:11.575 [info] > pixi --version
2024-09-10 10:23:11.576 [warning] could not find a pixi interpreter for the interpreter at C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\python.exe
2024-09-10 10:23:11.584 [info] > python -m pytest -p vscode_pytest --collect-only tests

Is it failing to find pixi and that breaks something that forces it to default to python instead of conda run -n Autobot python?
I tried updating the python extension and pytest, but I get the feeling the issue is in the extension since it is using the wrong python environment.
Steps to reproduce:

Open the Testing tab
Refresh tests
Check the output

Diagnostic data

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

2024-09-10 10:21:37.396 [info] Experiment 'pythonRecommendTensorboardExt' is active
2024-09-10 10:21:37.396 [info] Experiment 'pythonTerminalEnvVarActivation' is active
2024-09-10 10:21:37.396 [info] Experiment 'pythonTestAdapter' is active
2024-09-10 10:21:37.396 [info] Native locator: Refresh started
2024-09-10 10:21:37.396 [info] Default formatter is set to ms-python.black-formatter for workspace e:\source\MissionTesting
2024-09-10 10:21:37.396 [error] Following setting is deprecated: "python.linting.pylamaEnabled"
2024-09-10 10:21:37.396 [error] All settings starting with "python.linting." are deprecated and can be removed from settings.
2024-09-10 10:21:37.396 [error] Linting features have been moved to separate linter extensions.
2024-09-10 10:21:37.396 [error] See here for more information: https://code.visualstudio.com/docs/python/linting
2024-09-10 10:21:37.396 [error] Selected linter "pylama" may be supported by extensions like "Ruff", which include several linter rules: https://marketplace.visualstudio.com/items?itemName=charliermarsh.ruff
2024-09-10 10:21:37.419 [info] Conda environment manager found at: C:\Users\loganjones\AppData\Local\anaconda3\Scripts\conda.exe
2024-09-10 10:21:37.438 [info] Python interpreter path: ~\AppData\Local\anaconda3\envs\Autobot\python.exe
2024-09-10 10:21:39.121 [info] > pyenv which python
2024-09-10 10:21:39.121 [info] cwd: .
2024-09-10 10:21:39.188 [info] > conda info --json
2024-09-10 10:21:39.188 [info] shell: powershellCore
2024-09-10 10:21:39.219 [info] > ~\AppData\Local\anaconda3\Scripts\conda.exe info --json
2024-09-10 10:21:41.620 [info] Starting Pylance language server.
2024-09-10 10:21:41.892 [info] Native locator: Refresh finished in 4961 ms
2024-09-10 10:21:50.503 [info] > ~\.conda\Scripts\conda.exe info --json
2024-09-10 10:21:50.503 [info] shell: powershellCore
2024-09-10 10:21:52.852 [info] > ~\.conda\envs\SD-UI\Scripts\conda.exe info --json
2024-09-10 10:21:52.852 [info] shell: powershellCore
2024-09-10 10:21:54.937 [info] > ~\.conda\envs\aigt-processors\Scripts\conda.exe info --json
2024-09-10 10:21:54.937 [info] shell: powershellCore
2024-09-10 10:21:57.024 [info] > ~\AppData\Local\anaconda3\Scripts\conda.exe info --json
2024-09-10 10:21:57.024 [info] shell: powershellCore
2024-09-10 10:22:01.227 [info] > ~\AppData\Local\anaconda3\envs\CV\Scripts\conda.exe info --json
2024-09-10 10:22:01.227 [info] shell: powershellCore
2024-09-10 10:22:03.223 [info] > ~\AppData\Local\anaconda3\envs\Autobot\Scripts\conda.exe info --json
2024-09-10 10:22:03.224 [info] shell: powershellCore
2024-09-10 10:22:05.347 [info] > ~\AppData\Local\anaconda3\envs\GameBuilder\Scripts\conda.exe info --json
2024-09-10 10:22:05.347 [info] shell: powershellCore
2024-09-10 10:22:07.412 [info] > ~/AppData/Local/anaconda3/Scripts/activate ; conda activate Autobot ; echo 'e8b39361-0157-4923-80e1-22d70d46dee6' ; python ~/.vscode/extensions/ms-python.python-2024.14.0-win32-x64/python_files/printEnvVariables.py
2024-09-10 10:22:07.412 [info] shell: powershellCore
2024-09-10 10:22:09.877 [info] > C:\Python311\python.exe ~/.vscode/extensions/ms-python.python-2024.14.0-win32-x64/python_files/printEnvVariables.py
2024-09-10 10:22:09.877 [info] shell: powershellCore
2024-09-10 10:22:12.075 [error] [
  'parseEnvironmentOutput, Class name = j, completed in 0ms, has a falsy return value',
  SyntaxError: Unexpected token 'L', "Loading cu"... is not valid JSON
      at JSON.parse (<anonymous>)
      at c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:232183
      at j.parseEnvironmentOutput (c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:449554)
      at c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:547377
      at j.r.value (c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:547612)
      at c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:547377
      at j.r.value (c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:547612)
      at j.getProcessEnvironmentVariables (c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:446496)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at R._applyCollectionImpl (c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:897618)
      at R._applyCollection (c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:896575)
]
2024-09-10 10:22:12.075 [error] [
  'Failed to parse Environment variables, Class name = j, completed in 1ms, has a falsy return value, Arg 1: "Loading custom scripts from: D:\\\\loganjones\\\\OneDrive - Microsoft\\\\Documents\\\\PowerShell\\\\CustomScripts\\r\\n\\r\\n{\\"ALLUSERSPROFILE\\": \\"C:\\\\\\\\ProgramData\\", \\"APPDATA\\": \\"C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Roaming\\", \\"C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3;C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\Library\\\\\\\\mingw-w64\\\\\\\\bin;C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\Library\\\\\\\\usr\\\\\\\\bin;C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\Library\\\\\\\\bin;C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\Scripts;C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\bin;C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\condabin;C:\\\\\\\\Program Files\\\\\\\\PowerShell\\\\\\\\7;C:\\\\\\\\Program, \\"_CONDA_EXE\\": \\"C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\Scripts\\\\\\\\conda.exe\\", \\"_CONDA_ROOT\\": \\"C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\", \\"__COMPAT_LAYER\\": \\"DetectorsAppHealth HighDpiAware\\", \\"__CONDA_OPENSLL_CERT_FILE_SET\\": \\"1\\", \\"__PSLOCKDOWNPOLICY\\": \\"0\\"}\\r\\n", Arg 2: undefined, Return Value: undefined',
  SyntaxError: Unexpected token 'L', "Loading cu"... is not valid JSON
      at JSON.parse (<anonymous>)
      at c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:232183
      at j.parseEnvironmentOutput (c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:449554)
      at c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:547377
      at j.r.value (c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:547612)
      at c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:547377
      at j.r.value (c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:547612)
      at j.getProcessEnvironmentVariables (c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:446496)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at R._applyCollectionImpl (c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:897618)
      at R._applyCollection (c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\out\client\extension.js:2:896575)
]
2024-09-10 10:22:12.078 [info] Setting environment variable CONDA_DEFAULT_ENV in collection to Autobot {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.078 [info] Setting environment variable CONDA_EXE in collection to C:\Users\loganjones\AppData\Local\anaconda3\Scripts\conda.exe {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.078 [info] Setting environment variable CONDA_PREFIX in collection to C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.078 [info] Setting environment variable CONDA_PREFIX_1 in collection to C:\Users\loganjones\AppData\Local\anaconda3 {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.078 [info] Setting environment variable CONDA_PROMPT_MODIFIER in collection to (Autobot)  {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.078 [info] Setting environment variable CONDA_PYTHON_EXE in collection to C:\Users\loganjones\AppData\Local\anaconda3\python.exe {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.078 [info] Setting environment variable CONDA_SHLVL in collection to 2 {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.078 [info] Prepending environment variable PATH in collection to C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot;C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\Library\mingw-w64\bin;C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\Library\usr\bin;C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\Library\bin;C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\Scripts;C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\bin;C:\Users\loganjones\AppData\Local\anaconda3\condabin; {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.079 [info] Setting environment variable PATHEXT in collection to .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.PYW;.CPL {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.079 [info] Setting environment variable PSMODULEPATH in collection to D:\loganjones\OneDrive - Microsoft\Documents\PowerShell\Modules;C:\Program Files\PowerShell\Modules;c:\program files\powershell\7\Modules;C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules;C:\Program Files (x86)\Microsoft Azure Information Protection\Powershell {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.079 [info] Setting environment variable PYTHONIOENCODING in collection to utf-8 {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.079 [info] Setting environment variable PYTHONPATH in collection to e:\source\MissionTesting {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.079 [info] Setting environment variable PYTHONUNBUFFERED in collection to 1 {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.079 [info] Setting environment variable SSL_CERT_FILE in collection to C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\Library\ssl\cacert.pem {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.079 [info] Setting environment variable _CONDA_EXE in collection to C:\Users\loganjones\AppData\Local\anaconda3\Scripts\conda.exe {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.079 [info] Setting environment variable _CONDA_ROOT in collection to C:\Users\loganjones\AppData\Local\anaconda3 {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.079 [info] Setting environment variable __COMPAT_LAYER in collection to DetectorsAppHealth HighDpiAware {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.079 [info] Setting environment variable __CONDA_OPENSLL_CERT_FILE_SET in collection to 1 {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-10 10:22:12.080 [info] Send text to terminal: & C:/Python311/python.exe c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\python_files\printEnvVariablesToFile.py c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\python_files\deactivate\powershell\envVars.txt
2024-09-10 10:23:09.849 [info] Discover tests for workspace name: MissionTesting - uri: e:\source\MissionTesting
2024-09-10 10:23:09.849 [info] Running discovery for pytest using the new test adapter.
2024-09-10 10:23:09.850 [warning] The cwd resolves to a different path, checking if it has a symbolic link somewhere in its path.
2024-09-10 10:23:09.850 [info] All environment variables set for pytest discovery: {"PYTHONPATH":"c:\\Users\\loganjones\\.vscode\\extensions\\ms-python.python-2024.14.0-win32-x64\\python_files;e:\\source\\MissionTesting","ALLUSERSPROFILE":"C:\\ProgramData","APPDATA":"C:\\Users\\loganjones\\AppData\\Roaming","HOMEDRIVE":"C:","HOMEPATH":"\\Users\\loganjones","LOCALAPPDATA":"C:\\Users\\loganjones\\AppData\\Local","TEST_RUN_PIPE":"\\\\.\\pipe\\python-test-discovery-64879d75d2645a05e212-sock"}
2024-09-10 10:23:09.863 [info] > ~\AppData\Local\anaconda3\Scripts\conda.exe run -n Autobot --no-capture-output python ~\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\python_files\get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2024.14.0-win32-x64/python_files/printEnvVariables.py
2024-09-10 10:23:09.863 [info] shell: commandPrompt
2024-09-10 10:23:11.575 [info] > pixi --version
2024-09-10 10:23:11.576 [warning] could not find a pixi interpreter for the interpreter at C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\python.exe
2024-09-10 10:23:11.584 [info] > python -m pytest -p vscode_pytest --collect-only tests
2024-09-10 10:23:11.584 [info] cwd: .
2024-09-10 10:23:11.979 [error] ERROR: usage: __main__.py [options] [file_or_dir] [file_or_dir] [...]
__main__.py: error: unrecognized arguments: --cov=autobot --cov=common --cov-report=lcov
  inifile: e:\source\MissionTesting\pyproject.toml
  rootdir: e:\source\MissionTesting

2024-09-10 10:23:12.003 [error] Subprocess exited unsuccessfully with exit code 4 and signal null on workspace e:\source\MissionTesting.
2024-09-10 10:23:12.003 [error] Subprocess exited unsuccessfully with exit code 4 and signal null on workspace e:\source\MissionTesting. Creating and sending error discovery payload
2024-09-10 10:23:12.003 [error] pytest test discovery error for workspace:  e:\source\MissionTesting

 The python test process was terminated before it could exit on its own, the process errored with: Code: 4, Signal: null for workspace e:\source\MissionTesting

Extension version: 2024.14.0
VS Code version: Code 1.93.0 (4849ca9bdf9666755eb463db297b69e5385090e3, 2024-09-04T13:02:38.431Z)
OS version: Windows_NT x64 10.0.22631
Modes:

Python version (& distribution if applicable, e.g. Anaconda): 3.10.13
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
Value of the python.languageServer setting: Default

User Settings

languageServer: "Pylance"

testing
• pytestArgs: "<placeholder>"
• pytestEnabled: true

Installed Extensions

Extension Name
Extension Id
Version

.NET Install Tool
ms-dotnettools.vscode-dotnet-runtime
2.1.5

ARM Template Viewer
bencoleman.armview
0.4.6

autoDocstring - Python Docstring Generator
njpwerner.autodocstring
0.6.1

Azure Account
ms-vscode.azure-account
0.12.0

Azure CLI Tools
ms-vscode.azurecli
0.6.0

Azure Functions
ms-azuretools.vscode-azurefunctions
1.15.3

Azure Pipelines
ms-azure-devops.azure-pipelines
1.228.0

Azure Resource Manager (ARM) Tools
msazurermtools.azurerm-vscode-tools
0.15.12

Azure Resources
ms-azuretools.vscode-azureresourcegroups
0.9.4

Azure Storage
ms-azuretools.vscode-azurestorage
0.16.1

Azurite
Azurite.azurite
3.32.0

Better C++ Syntax
jeff-hykin.better-cpp-syntax
1.27.1

Black Formatter
ms-python.black-formatter
2024.2.0

C/C++
ms-vscode.cpptools
1.22.2

C/C++ Extension Pack
ms-vscode.cpptools-extension-pack
1.3.0

C/C++ Themes
ms-vscode.cpptools-themes
2.0.0

C#
ms-dotnettools.csharp
2.45.20

Code Spell Checker
streetsidesoftware.code-spell-checker
3.0.1

Coverage Gutters
ryanluker.vscode-coverage-gutters
2.11.1

Data Wrangler
ms-toolsai.datawrangler
1.8.0

Dev Containers
ms-vscode-remote.remote-containers
0.384.0

Docker
ms-azuretools.vscode-docker
1.29.2

Doxygen Documentation Generator
cschlosser.doxdocgen
1.4.0

ES7+ React/Redux/React-Native snippets
dsznajder.es7-react-js-snippets
4.4.3

ESLint
dbaeumer.vscode-eslint
3.0.10

Even Better TOML
tamasfe.even-better-toml
0.19.2

Excel Viewer
GrapeCity.gc-excelviewer
4.2.62

GitHub Copilot
GitHub.copilot
1.229.0

GitHub Copilot Chat
GitHub.copilot-chat
0.21.2024090602

GitHub Pull Requests
GitHub.vscode-pull-request-github
0.96.0

GitLens — Git supercharged
eamodio.gitlens
15.4.0

GraphQL: Syntax Highlighting
GraphQL.vscode-graphql-syntax
1.3.6

Graphviz (dot) language support for Visual Studio Code
joaompinto.vscode-graphviz
0.0.6

Graphviz Interactive Preview
tintinweb.graphviz-interactive-preview
0.3.5

Hex Editor
ms-vscode.hexeditor
1.10.0

HTML Preview
tht13.html-preview-vscode
0.2.5

IntelliCode
VisualStudioExptTeam.vscodeintellicode
1.3.1

IntelliCode API Usage Examples
VisualStudioExptTeam.intellicode-api-usage-examples
0.2.8

isort
ms-python.isort
2023.10.1

JavaScript Debugger
ms-vscode.js-debug
1.93.0

JavaScript Debugger Companion Extension
ms-vscode.js-debug-companion
1.1.3

JSON Utility
GanesanChandran.json-utility
1.0.1

Jupyter
ms-toolsai.jupyter
2024.8.1

Jupyter Cell Tags
ms-toolsai.vscode-jupyter-cell-tags
0.1.9

Jupyter Keymap
ms-toolsai.jupyter-keymap
1.1.2

Jupyter Notebook Renderers
ms-toolsai.jupyter-renderers
1.0.19

Jupyter Slide Show
ms-toolsai.vscode-jupyter-slideshow
0.1.6

Live Preview
ms-vscode.live-server
0.4.14

Markdown All in One
yzhang.markdown-all-in-one
3.6.2

markdownlint
DavidAnson.vscode-markdownlint
0.55.0

Material Theme
Equinusocio.vsc-material-theme
34.5.2

Material Theme Icons — Free
equinusocio.vsc-material-theme-icons
3.8.8

Microsoft Edge Tools for VS Code
ms-edgedevtools.vscode-edge-devtools
2.1.5

npm Intellisense
christian-kohler.npm-intellisense
1.4.5

Phind.com - Chat with your Codebase
phind.phind
0.25.4

Polyglot Notebooks
ms-dotnettools.dotnet-interactive-vscode
1.0.5229040

PowerShell
ms-vscode.powershell
2024.2.2

Prettier - Code formatter
esbenp.prettier-vscode
11.0.0

Protobuf support
peterj.proto
0.0.4

Pylance
ms-python.vscode-pylance
2024.9.1

Python
ms-python.python
2024.14.0

Python Debugger
ms-python.debugpy
2024.10.0

React Native Tools
msjsdiag.vscode-react-native
1.13.0

Serial Monitor
ms-vscode.vscode-serial-monitor
0.12.0

Simple React Snippets
burkeholland.simple-react-snippets
1.2.8

Table Visualizer for JavaScript Profiles
ms-vscode.vscode-js-profile-table
1.0.9

Todo Tree
Gruntfuggly.todo-tree
0.0.226

Unreal Engine Python
NilsSoderman.ue-python
1.4.1

VS Code Speech
ms-vscode.vscode-speech
0.10.0

Word Count
ms-vscode.wordcount
0.1.0

WSL
ms-vscode-remote.remote-wsl
0.88.2

XML Format
mikeburgh.xml-format
1.1.3

YAML
redhat.vscode-yaml
1.15.0

YAML ❤ JSON
hilleer.yaml-plus-json
1.12.2

yarn
gamunu.vscode-yarn
2.1.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz (20 x 2808)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
63.71GB (23.96GB free)

Process Argv
--crash-reporter-id 82edcc25-c4c8-4994-be5c-0197222c8a32

Screen Reader
no

VM
0%

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
724cj586:31013169
a69g1124:31058053
dvdeprecation:31068756
dwnewjupyter:31046869
newcmakeconfigv2:31071590
impr_priority:31102340
nativerepl2:31134655
refactort:31108082
pythonrstrctxt:31112756
flightc:31134773
wkspc-onlycs-t:31132770
nativeloc1:31134641
wkspc-ranged-t:31125599
3ad50483:31134767
autoexpandse:31133494
fje88620:31121564

Hi! I am seeing an error arise before you get the the actual testing. This error:
  'Failed to parse Environment variables, Class name = j, completed in 1ms, has a falsy return value, Arg 1: "Loading custom scripts from: D:\\\\loganjones\\\\OneDrive - Microsoft\\\\Documents\\\\PowerShell\\\\CustomScripts\\r\\n\\r\\n{\\"ALLUSERSPROFILE\\": \\"C:\\\\\\\\ProgramData\\", \\"APPDATA\\": \\"C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Roaming\\", \\"C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3;C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\Library\\\\\\\\mingw-w64\\\\\\\\bin;C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\Library\\\\\\\\usr\\\\\\\\bin;C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\Library\\\\\\\\bin;C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\Scripts;C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\bin;C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\condabin;C:\\\\\\\\Program Files\\\\\\\\PowerShell\\\\\\\\7;C:\\\\\\\\Program, \\"_CONDA_EXE\\": \\"C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\\\\\\\Scripts\\\\\\\\conda.exe\\", \\"_CONDA_ROOT\\": \\"C:\\\\\\\\Users\\\\\\\\loganjones\\\\\\\\AppData\\\\\\\\Local\\\\\\\\anaconda3\\", \\"__COMPAT_LAYER\\": \\"DetectorsAppHealth HighDpiAware\\", \\"__CONDA_OPENSLL_CERT_FILE_SET\\": \\"1\\", \\"__PSLOCKDOWNPOLICY\\": \\"0\\"}\\r\\n", Arg 2: undefined, Return Value: undefined',
  SyntaxError: Unexpected token 'L', "Loading cu"... is not valid JSON

Can you check any environment variables you are putting in? Through a .env file, vscode settings or otherwise. It seems like it can't parse something and that is why it cannot start up the environment to then run tests

Good catch, but unfortunately, that issue (I was printing out something in my Powershell profile on Powershell startup that it was trying to parse in addition to env variables) does not seem related.  I fixed it and restarted VS code and even my machine and I still get the same issue where it appears to be using the default python for the system instead of the environment for the workspace.  I include the whole thing again just to show that it doesn't error anymore, but I assume the issue is still more related to the last several lines?

024-09-11 12:12:04.732 [info] Experiment 'pythonRecommendTensorboardExt' is active
2024-09-11 12:12:04.733 [info] Experiment 'pythonTerminalEnvVarActivation' is active
2024-09-11 12:12:04.733 [info] Experiment 'pythonTestAdapter' is active
2024-09-11 12:12:04.733 [info] Native locator: Refresh started
2024-09-11 12:12:04.733 [info] Default formatter is set to ms-python.black-formatter for workspace e:\source\MissionTesting
2024-09-11 12:12:04.747 [info] Conda environment manager found at: C:\Users\loganjones\AppData\Local\anaconda3\Scripts\conda.exe
2024-09-11 12:12:04.841 [info] Python interpreter path: ~\AppData\Local\anaconda3\envs\Autobot\python.exe
2024-09-11 12:12:05.204 [info] > pyenv which python
2024-09-11 12:12:05.204 [info] cwd: .
2024-09-11 12:12:08.224 [info] > conda info --json
2024-09-11 12:12:08.225 [info] shell: powershellCore
2024-09-11 12:12:08.607 [info] Native locator: Refresh finished in 4051 ms
2024-09-11 12:12:15.778 [info] > conda run -n Autobot --no-capture-output python ~\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\python_files\get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2024.14.0-win32-x64/python_files/printEnvVariables.py
2024-09-11 12:12:15.778 [info] shell: powershellCore
2024-09-11 12:12:15.873 [info] Starting Pylance language server.
2024-09-11 12:12:19.920 [info] > C:\Python311\python.exe ~/.vscode/extensions/ms-python.python-2024.14.0-win32-x64/python_files/printEnvVariables.py
2024-09-11 12:12:19.921 [info] shell: powershellCore
2024-09-11 12:12:22.366 [info] Setting environment variable APPLICATION_INSIGHTS_NO_DIAGNOSTIC_CHANNEL in collection to 1 {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-11 12:12:22.366 [info] Setting environment variable CONDA_DEFAULT_ENV in collection to Autobot {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-11 12:12:22.366 [info] Setting environment variable CONDA_PREFIX in collection to C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-11 12:12:22.366 [info] Setting environment variable CONDA_PREFIX_1 in collection to C:\Users\loganjones\AppData\Local\anaconda3 {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-11 12:12:22.366 [info] Setting environment variable CONDA_PROMPT_MODIFIER in collection to (Autobot)  {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-11 12:12:22.367 [info] Setting environment variable CONDA_SHLVL in collection to 2 {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-11 12:12:22.367 [info] Prepending environment variable PATH in collection to C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot;C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\Library\mingw-w64\bin;C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\Library\usr\bin;C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\Library\bin;C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\Scripts;C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\bin;C:\Users\loganjones\AppData\Local\anaconda3\condabin;C:\Program Files\PowerShell\7;C:\Program Files (x86)\Common Files\Oracle\Java\java8path;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Python311\Scripts;C:\Python311;C:\Python310\Scripts;C:\Python310;C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files\dotnet;C:\ProgramData\chocolatey\bin;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn;C:\Program Files\Microsoft SQL Server\150\Tools\Binn;D:\Program Files\Graphviz\bin;C:\Program Files\Microsoft\Web Platform Installer;C:\Program Files\Git LFS;D:\ffmpeg\bin;D:\Program Files\GitHub CLI;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;D:\Program Files\nodejs;C:\Program Files\Microsoft\Azure Functions Core Tools;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit;C:\Program Files\Git\cmd;C:\Program Files\PowerShell\7;C:\Program Files\Docker\Docker\resources\bin;C:\Users\loganjones\AppData\Local\anaconda3;C:\Users\loganjones\AppData\Local\anaconda3\Library\mingw-w64\bin;C:\Users\loganjones\AppData\Local\anaconda3\Library\usr\bin;C:\Users\loganjones\AppData\Local\anaconda3\Library\bin;C:\Users\loganjones\AppData\Local\anaconda3\Scripts;C:\Users\loganjones\scoop\apps\latex\current\texmfs\install\miktex\bin\x64;C:\Users\loganjones\scoop\shims;C:\Users\loganjones\AppData\Local\Microsoft\WindowsApps;C:\Users\loganjones\.dotnet\tools;C:\Users\loganjones\AppData\Local\Programs\Microsoft VS Code\bin;D:\Program Files\Graphviz\bin;C:\Users\loganjones\.dotnet\tools;C:\Users\loganjones\AppData\Local\GitHubDesktop\bin;C:\Program Files (x86)\Nmap;C:\Users\loganjones\AppData\Local\Microsoft\WindowsApps;C:\Users\loganjones\AppData\Roaming\npm;C:\Users\loganjones\.dotnet\tools;C:\Users\loganjones\AppData\Local\Programs\Ollama;.; {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-11 12:12:22.367 [info] Setting environment variable PROMPT in collection to (Autobot) $P$G {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-11 12:12:22.367 [info] Setting environment variable SSL_CERT_FILE in collection to C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\Library\ssl\cacert.pem {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-11 12:12:22.367 [info] Setting environment variable _CONDA_OLD_CHCP in collection to 437 {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-11 12:12:22.367 [info] Setting environment variable __CONDA_OPENSLL_CERT_FILE_SET in collection to "1" {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-11 12:12:22.367 [info] Setting environment variable CONDA_ROOT in collection to C:\Users\loganjones\AppData\Local\anaconda3 {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-09-11 12:12:22.368 [info] Send text to terminal: & C:/Python311/python.exe c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\python_files\printEnvVariablesToFile.py c:\Users\loganjones\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\python_files\deactivate\powershell\envVars.txt
2024-09-11 12:13:23.256 [info] Discover tests for workspace name: MissionTesting - uri: e:\source\MissionTesting
2024-09-11 12:13:23.256 [info] Running discovery for pytest using the new test adapter.
2024-09-11 12:13:23.258 [warning] The cwd resolves to a different path, checking if it has a symbolic link somewhere in its path.
2024-09-11 12:13:23.258 [info] All environment variables set for pytest discovery: {"ALLUSERSPROFILE":"C:\\ProgramData","APPDATA":"C:\\Users\\loganjones\\AppData\\Roaming","APPLICATION_INSIGHTS_NO_DIAGNOSTIC_CHANNEL":"1","CHROME_CRASHPAD_PIPE_NAME":"\\\\.\\pipe\\crashpad_18936_CRWVZVSVPOVKTYZX","COMPUTERNAME":"THINKSTATION-LO","EFC_13476":"1","ELECTRON_RUN_AS_NODE":"1","FPS_BROWSER_APP_PROFILE_STRING":"Internet Explorer","FPS_BROWSER_USER_PROFILE_STRING":"Default","GIT_LFS_PATH":"C:\\Program Files\\Git LFS","HOMEDRIVE":"C:","HOMEPATH":"\\Users\\loganjones","LOCALAPPDATA":"C:\\Users\\loganjones\\AppData\\Local","LOGONSERVER":"\\\\THINKSTATION-LO","NUMBER_OF_PROCESSORS":"20","OLLAMA_MODELS":"E:\\Logan\\source\\LLMs\\ollama\\models","ORIGINAL_XDG_CURRENT_DESKTOP":"undefined","OS":"Windows_NT","PATHEXT":".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.PY;.PYW","POWERSHELL_DISTRIBUTION_CHANNEL":"MSI:Windows 10 Enterprise","PROCESSOR_ARCHITECTURE":"AMD64","PROCESSOR_IDENTIFIER":"Intel64 Family 6 Model 165 Stepping 5, GenuineIntel","PROCESSOR_LEVEL":"6","PROCESSOR_REVISION":"a505","PUBLIC":"C:\\Users\\Public","SESSIONNAME":"Console","TEMP":"C:\\Users\\LOGANJ~1\\AppData\\Local\\Temp","TMP":"C:\\Users\\LOGANJ~1\\AppData\\Local\\Temp","UATDATA":"C:\\WINDOWS\\CCM\\UATData\\D9F8C395-CAB8-491d-B8AC-179A1FE1BE77","USERDNSDOMAIN":"northamerica.corp.microsoft.com","USERDOMAIN":"NORTHAMERICA","USERDOMAIN_ROAMINGPROFILE":"NORTHAMERICA","USERNAME":"loganjones","USERPROFILE":"C:\\Users\\loganjones","VSCODE_AMD_ENTRYPOINT":"vs/workbench/api/node/extensionHostProcess","VSCODE_CODE_CACHE_PATH":"C:\\Users\\loganjones\\AppData\\Roaming\\Code\\CachedData\\4849ca9bdf9666755eb463db297b69e5385090e3","VSCODE_CRASH_REPORTER_PROCESS_TYPE":"extensionHost","VSCODE_CWD":"C:\\WINDOWS\\system32","VSCODE_DOTNET_INSTALL_TOOL_ORIGINAL_HOME":"undefined","VSCODE_HANDLES_UNCAUGHT_ERRORS":"true","VSCODE_IPC_HOOK":"\\\\.\\pipe\\22a38d4b-1.93.0-main-sock","VSCODE_NLS_CONFIG":"{\"userLocale\":\"en-us\",\"osLocale\":\"en-us\",\"resolvedLanguage\":\"en\",\"defaultMessagesFile\":\"C:\\\\Users\\\\loganjones\\\\AppData\\\\Local\\\\Programs\\\\Microsoft VS Code\\\\resources\\\\app\\\\out\\\\nls.messages.json\",\"locale\":\"en-us\",\"availableLanguages\":{}}","VSCODE_PID":"18936","ZES_ENABLE_SYSMAN":"1","ChocolateyInstall":"C:\\ProgramData\\chocolatey","ChocolateyLastPathUpdate":"132876180735061241","ComSpec":"C:\\WINDOWS\\system32\\cmd.exe","CommonProgramFiles":"C:\\Program Files\\Common Files","CommonProgramFiles(x86)":"C:\\Program Files (x86)\\Common Files","CommonProgramW6432":"C:\\Program Files\\Common Files","DriverData":"C:\\Windows\\System32\\Drivers\\DriverData","Env_GeneratedVersion":"0.1.22139.24290","OneDrive":"D:\\loganjones\\OneDrive - Microsoft","OneDriveCommercial":"D:\\loganjones\\OneDrive - Microsoft","OneDriveConsumer":"E:\\Logan\\OneDrive","PSModulePath":"C:\\Program Files\\WindowsPowerShell\\Modules;C:\\WINDOWS\\system32\\WindowsPowerShell\\v1.0\\Modules;C:\\Program Files (x86)\\Microsoft Azure Information Protection\\Powershell","ProgramData":"C:\\ProgramData","ProgramFiles":"C:\\Program Files","ProgramFiles(x86)":"C:\\Program Files (x86)","ProgramW6432":"C:\\Program Files","SystemDrive":"C:","SystemRoot":"C:\\WINDOWS","__PSLockDownPolicy":"0","windir":"C:\\WINDOWS","Path":"C:\\Program Files (x86)\\Common Files\\Oracle\\Java\\java8path;C:\\Program Files (x86)\\Common Files\\Oracle\\Java\\javapath;C:\\Python311\\Scripts\\;C:\\Python311\\;C:\\Python310\\Scripts\\;C:\\Python310\\;C:\\Program Files (x86)\\Microsoft SDKs\\Azure\\CLI2\\wbin;C:\\WINDOWS\\system32;C:\\WINDOWS;C:\\WINDOWS\\System32\\Wbem;C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\;C:\\WINDOWS\\System32\\OpenSSH\\;C:\\Program Files\\dotnet\\;C:\\ProgramData\\chocolatey\\bin;C:\\Program Files\\Microsoft SQL Server\\Client SDK\\ODBC\\170\\Tools\\Binn\\;C:\\Program Files\\Microsoft SQL Server\\150\\Tools\\Binn\\;D:\\Program Files\\Graphviz\\bin;C:\\Program Files\\Microsoft\\Web Platform Installer\\;C:\\Program Files\\Git LFS;D:\\ffmpeg\\bin\\;D:\\Program Files\\GitHub CLI\\;C:\\WINDOWS\\system32;C:\\WINDOWS;C:\\WINDOWS\\System32\\Wbem;C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\;C:\\WINDOWS\\System32\\OpenSSH\\;C:\\Program Files (x86)\\NVIDIA Corporation\\PhysX\\Common;C:\\Program Files\\NVIDIA Corporation\\NVIDIA NvDLISR;D:\\Program Files\\nodejs\\;C:\\Program Files\\Microsoft\\Azure Functions Core Tools\\;C:\\Program Files (x86)\\Windows Kits\\10\\Windows Performance Toolkit\\;C:\\Program Files\\Git\\cmd;C:\\Program Files\\PowerShell\\7\\;C:\\Program Files\\Docker\\Docker\\resources\\bin;C:\\Users\\loganjones\\AppData\\Local\\anaconda3;C:\\Users\\loganjones\\AppData\\Local\\anaconda3\\Library\\mingw-w64\\bin;C:\\Users\\loganjones\\AppData\\Local\\anaconda3\\Library\\usr\\bin;C:\\Users\\loganjones\\AppData\\Local\\anaconda3\\Library\\bin;C:\\Users\\loganjones\\AppData\\Local\\anaconda3\\Scripts;C:\\Users\\loganjones\\scoop\\apps\\latex\\current\\texmfs\\install\\miktex\\bin\\x64;C:\\Users\\loganjones\\scoop\\shims;C:\\Users\\loganjones\\AppData\\Local\\Microsoft\\WindowsApps;C:\\Users\\loganjones\\.dotnet\\tools;C:\\Users\\loganjones\\AppData\\Local\\Programs\\Microsoft VS Code\\bin;D:\\Program Files\\Graphviz\\bin;C:\\Users\\loganjones\\.dotnet\\tools;C:\\Users\\loganjones\\AppData\\Local\\GitHubDesktop\\bin;C:\\Program Files (x86)\\Nmap;C:\\Users\\loganjones\\AppData\\Local\\Microsoft\\WindowsApps;C:\\Users\\loganjones\\AppData\\Roaming\\npm;C:\\Users\\loganjones\\.dotnet\\tools;C:\\Users\\loganjones\\AppData\\Local\\Programs\\Ollama;","PYTHONPATH":"c:\\Users\\loganjones\\.vscode\\extensions\\ms-python.python-2024.14.0-win32-x64\\python_files","TEST_RUN_PIPE":"\\\\.\\pipe\\python-test-discovery-3c3f73bfeb452b366820-sock"}
2024-09-11 12:13:23.270 [info] > ~\AppData\Local\anaconda3\Scripts\conda.exe run -n Autobot --no-capture-output python ~\.vscode\extensions\ms-python.python-2024.14.0-win32-x64\python_files\get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2024.14.0-win32-x64/python_files/printEnvVariables.py
2024-09-11 12:13:23.270 [info] shell: commandPrompt
2024-09-11 12:13:24.871 [info] > pixi --version
2024-09-11 12:13:24.872 [warning] could not find a pixi interpreter for the interpreter at C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\python.exe
2024-09-11 12:13:24.880 [info] > python -m pytest -p vscode_pytest --collect-only tests
2024-09-11 12:13:24.880 [info] cwd: .
2024-09-11 12:13:25.437 [error] ERROR: usage: __main__.py [options] [file_or_dir] [file_or_dir] [...]
__main__.py: error: unrecognized arguments: --cov=autobot --cov=common --cov-report=lcov
  inifile: e:\source\MissionTesting\pyproject.toml
  rootdir: e:\source\MissionTesting

2024-09-11 12:13:25.463 [error] Subprocess exited unsuccessfully with exit code 4 and signal null on workspace e:\source\MissionTesting.
2024-09-11 12:13:25.463 [error] Subprocess exited unsuccessfully with exit code 4 and signal null on workspace e:\source\MissionTesting. Creating and sending error discovery payload
2024-09-11 12:13:25.463 [error] pytest test discovery error for workspace:  e:\source\MissionTesting

 The python test process was terminated before it could exit on its own, the process errored with: Code: 4, Signal: null for workspace e:\source\MissionTesting

I turned on the Debug level logging and got a little more detail:
2024-09-11 13:32:21.424 [debug] Testing: Manually triggered test refresh
2024-09-11 13:32:21.425 [debug] Testing: Clearing all discovered tests
2024-09-11 13:32:21.425 [debug] Testing: Forcing test data refresh
2024-09-11 13:32:21.425 [debug] Testing: Refreshing all test data
2024-09-11 13:32:21.426 [debug] Python API env change detected C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\python.exe update
2024-09-11 13:32:21.427 [info] Discover tests for workspace name: MissionTesting - uri: e:\source\MissionTesting
2024-09-11 13:32:21.427 [info] Running discovery for pytest using the new test adapter.
2024-09-11 13:32:21.427 [debug] Starting Test Discovery named pipe
2024-09-11 13:32:21.427 [debug] Creating named pipe server on \\.\pipe\python-test-discovery-4cb861741fb10d23b583-sock
2024-09-11 13:32:21.428 [warning] The cwd resolves to a different path, checking if it has a symbolic link somewhere in its path.
2024-09-11 13:32:21.428 [info] All environment variables set for pytest discovery: { *SEE PREVIOUS COMMENTS FOR ENV VARS* }
2024-09-11 13:32:21.428 [warning] could not find a pixi interpreter for the interpreter at C:\Users\loganjones\AppData\Local\anaconda3\envs\Autobot\python.exe
2024-09-11 13:32:21.429 [debug] Executable does not exist within conda env, assume the executable to be `python` {"name":"Autobot","prefix":"C:\\Users\\loganjones\\AppData\\Local\\anaconda3\\envs\\Autobot\\python.exe"}
2024-09-11 13:32:21.435 [debug] Running pytest discovery with command: -m pytest -p vscode_pytest --collect-only tests for workspace e:\source\MissionTesting.
2024-09-11 13:32:21.435 [info] > python -m pytest -p vscode_pytest --collect-only tests
2024-09-11 13:32:21.435 [info] cwd: .
2024-09-11 13:32:21.799 [error] ERROR: usage: __main__.py [options] [file_or_dir] [file_or_dir] [...]
__main__.py: error: unrecognized arguments: --cov=autobot --cov=common --cov-report=lcov
  inifile: e:\source\MissionTesting\pyproject.toml
  rootdir: e:\source\MissionTesting

2024-09-11 13:32:21.819 [error] Subprocess exited unsuccessfully with exit code 4 and signal null on workspace e:\source\MissionTesting.
2024-09-11 13:32:21.819 [error] Subprocess exited unsuccessfully with exit code 4 and signal null on workspace e:\source\MissionTesting. Creating and sending error discovery payload
2024-09-11 13:32:21.819 [error] pytest test discovery error for workspace:  e:\source\MissionTesting

 The python test process was terminated before it could exit on its own, the process errored with: Code: 4, Signal: null for workspace e:\source\MissionTesting
2024-09-11 13:32:21.819 [debug] deferredTill EOT resolved

And for confirmation it is using the system default python, I removed the --cov and similar coverage commands from the pyproject.toml so pytest was able to start but then (understandably) ran into issues immediately after that and the stacktrace shows it is using the C:\Python311:
2024-09-11 13:49:30.368 [error] pytest test discovery error for workspace:  e:\source\MissionTesting
 _pytest.nodes.Collector.CollectError: ImportError while importing test module 'e:\source\MissionTesting\tests\autobot\behaviors\test_actor_behaviors.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
C:\Python311\Lib\importlib\__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests\autobot\behaviors\test_actor_behaviors.py:5: in <module>
    from autobot.behaviors import (
autobot\behaviors.py:9: in <module>

I believe I am facing the same problem. However, it does not occur anymore when I switch the python.locator option from 'native' to 'js'. Maybe you can give this a try as well to narrow down the issue?

I believe I am facing the same problem. However, it does not occur anymore when I switch the python.locator option from 'native' to 'js'. Maybe you can give this a try as well to narrow down the issue?

That did it! Test collection and execution are back to working like normal.
Thank you! I never would have thought to try that.
@eleanorjboyd the above solved my issue, but it would be interesting to know if there is a plan to make it so python.locator = native works more reliably since that is the default option.

I have the same problem as the above, and adding "python.locator": "js" to my settings (and restarting VSCode) also resolved the issue for me.
My selected python interpreter in VSCode in my workspace is (and has been for multiple years) a conda environment, but I noticed as of today that VSCode's test runner seemed to be using a .pyenv python interpreter/path instead, which in my case ran into problems upon initial load with test discovery since pytest itself wasn't installed for that python env:
2024-09-12 16:57:10.589 [error] /Users/sdemartini/.pyenv/versions/3.10.5/bin/python: No module named pytest

2024-09-12 16:57:10.594 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /Users/sdemartini/my_project.
2024-09-12 16:57:10.594 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /Users/sdemartini/my_project. Creating and sending error discovery payload
2024-09-12 16:57:10.594 [error] pytest test discovery error for workspace:  /Users/sdemartini/my_project

 The python test process was terminated before it could exit on its own, the process errored with: Code: 1, Signal: null for workspace /Users/sdemartini/my_project

I had the same issue — I believe it (python.locator) was changed after an update to vsstudio.

@karthiknadig any ideas about the correlation between the native locator stuff?

@eleanorjboyd Not really sure why this is happening. We can look at the API and see if there is a difference is why it misses selecting the expected repo. We might need a repro for this to diagnose further.

It seems that it's taking a prefix that has bin/python in it (example: /opt/homebrew/Caskroom/miniconda/base/envs/testtest/bin/python), and then appending bin/python to it again.

I just tested v2024.16.0 and the problem still persists for me. Unfortunately my work machine is pretty locked down so I can't share logs easily. @logar16 maybe you can also check it on your side?


Preliminary Code for Motor Control

mikael 2.5 hrs
Philippe 6.5 hrs

Requirements :

2 XL430
Ctrl : id3 with Left Joystick and id9 with Right One
CtrlMode : Velocity mapped on joystick from 0 t max rad/s


Test failures on 32 bit ARM (Raspberry Pi)

Note: migrated from original JIRA: https://issues.apache.org/jira/browse/ARROW-10187
Perhaps these failures are to be expected and perhaps we can't really support 32 bit?
{code:java}
---- array::array::tests::test_primitive_array_from_vec stdout ----
thread 'array::array::tests::test_primitive_array_from_vec' panicked at 'assertion failed: (left == right)
left: 144,
right: 104', arrow/src/array/array.rs:2383:9---- array::array::tests::test_primitive_array_from_vec_option stdout ----
thread 'array::array::tests::test_primitive_array_from_vec_option' panicked at 'assertion failed: (left == right)
left: 224,
right: 176', arrow/src/array/array.rs:2409:9---- array::null::tests::test_null_array stdout ----
thread 'array::null::tests::test_null_array' panicked at 'assertion failed: (left == right)
left: 64,
right: 32', arrow/src/array/null.rs:134:9---- array::union::tests::test_dense_union_i32 stdout ----
thread 'array::union::tests::test_dense_union_i32' panicked at 'assertion failed: (left == right)
left: 1024,
right: 768', arrow/src/array/union.rs:704:9---- memory::tests::test_allocate stdout ----
thread 'memory::tests::test_allocate' panicked at 'assertion failed: (left == right)
left: 0,
right: 32', arrow/src/memory.rs:243:13
{code}

Comment from Andy Grove(andygrove) @ 2020-10-06T04:18:16.429+0000:
I was able to run the DataFusion examples though, despite these test failures.
Comment from Andy Grove(andygrove) @ 2020-10-06T14:36:18.391+0000:
If these tests really are specific to 64 bit platforms then we could use conditional compilation and only compile them when target_pointer_width == 64.

See [https://doc.rust-lang.org/reference/conditional-compilation.html#target_pointer_width] for more information.
Comment from Andy Grove(andygrove) @ 2020-10-06T14:37:10.663+0000:
[~nevi_me] [~vertexclique] I'd be interested in your opinions on this one.
Comment from Mahmut Bulut(vertexclique) @ 2020-10-06T14:42:40.349+0000:
[~andygrove] Hi Andy, I don't have raspberry pi at hand. I want to check the compilation problems on ARM asap, target_pointer_width gate might be a good option for it. What version of rpi did you use?
Comment from Neville Dipale(nevi_me) @ 2020-10-16T04:08:01.196+0000:
[~andygrove] 64-bit types and offsets would also be a blocker for supporting wasm32.

If someone completes ARROW-9453, perhaps we can gauge from that on what effort it takes to support 32-bit.

An update on this. We still have some failures on 32 bit Rasp Pi.
---- array::array_primitive::tests::test_primitive_array_from_vec_option stdout ----
thread 'array::array_primitive::tests::test_primitive_array_from_vec_option' panicked at 'assertion failed: `(left == right)`
  left: `216`,
 right: `172`', arrow/src/array/array_primitive.rs:533:9

---- array::array_primitive::tests::test_primitive_array_from_vec stdout ----
thread 'array::array_primitive::tests::test_primitive_array_from_vec' panicked at 'assertion failed: `(left == right)`
  left: `136`,
 right: `100`', arrow/src/array/array_primitive.rs:511:9

---- array::array_primitive::tests::test_timestamp_fmt_debug stdout ----
thread 'array::array_primitive::tests::test_timestamp_fmt_debug' panicked at 'called `Option::unwrap()` on a `None` value', arrow/src/array/array_primitive.rs:286:54

Environment (Rasperry Pi 4 Model B):
Raspbian GNU/Linux 10
Linux raspberrypi 4.19.97-v7l+ #1294 SMP Thu Jan 30 13:21:14 GMT 2020 armv7l GNU/Linux
rustc 1.51.0 (2fd73fabe 2021-03-23)

Amazingly, this issue is reproducible on any computer using Docker and cross. Make sure you have the Docker daemon running, then run:
cargo install cross
cross build --target armv7-unknown-linux-gnueabihf
cross test --target armv7-unknown-linux-gnueabihf


data preprocessing

Can you tell me how to transfer AOL raw data to model training data?
AOL raw data has [AnonID, Query, QueryTime, ItemRank, ClickURL] fields while training data is json format with query and clicks.
Thanks!

We have gone through a long pipeline to convert the AOL raw data into a session-based dataset as we used in our experiments. I am providing a brief detail of the processing steps.

Crawled around 1M unique web-URLs found as ClickURL in the AOL dataset. There are ~1.6M unique URLs and ~1M were found alive when we crawled (in 02/2017).
The crawled dataset is processed using word segmentation and tokenization.
The queries are processed using word segmentation, a spell checker and a tokenizer.
Sessions are created based on time-interval between consecutive queries and their cosine similarity using a vector representation. The vector representation is computed using averaging query term embeddings.
AOL dataset contains only ClickURLs but we need a list of candidate documents for the ranking task. To get a list of candidate documents for a query, we run BM25 on an index created using the 1M crawled documents.

Please read our papers to learn more detail about the dataset.

The crawled dataset is processed using word segmentation and tokenization.
Sessions are created based on time-interval between consecutive queries and their cosine similarity using a vector representation. The vector representation is computed using averaging query term embeddings.

could please tell me the difference between segment and tokenization?
your paper did not mention the time-interval ,How long is the interval and How to combine the time and query embedding?

Thanks a lot!


fix: update current tree after evaluation for jsobjects

Description
Previously, the current tree after evaluating a js collection's body doesn't get updated, so bindings still show up instead of their evaluated values.
Fixes #9645
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Manual
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:red_circle: Total coverage has decreased
// Code coverage diff between base branch:release and head branch: fix/update-evaluated-body-in-js-objects

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
total
55.72 (0)
37.03 (-0.02)
35.79 (0)
56.07 (-0.01)

:red_circle:
app/client/src/utils/WorkerUtil.ts
89.76 (0)
70.59 (-1.96)
100 (0)
93.33 (0)

:red_circle:
app/client/src/utils/autocomplete/TernServer.ts
52.71 (-0.23)
40.83 (-0.84)
36.21 (0)
56.74 (-0.25)

:red_circle:
app/client/src/workers/evaluationUtils.ts
57.75 (-0.62)
55.96 (-1.18)
63.49 (-1.03)
56.87 (-0.83)

@ohansFavour this is not the right solution here. variables don't have a dependency on the select widget at all because those are not responsive. and we are not making it responsive as of now

@ohansFavour this is not the right solution here. variables don't have a dependency on the select widget at all because those are not responsive. and we are not making it responsive as of now

All right. But mind you, this issue isn't particular to the select widget. It happens to all widgets as long as the property value is a binding.

We have decided not to make js Object variables reactive.
More => https://github.com/appsmithorg/appsmith/issues/9645#issuecomment-1054198460

We have decided not to make js Object variables reactive.
More => https://github.com/appsmithorg/appsmith/issues/9645#issuecomment-1054198460


development status

This is a neat project and could solve some issues for me.
Looks like last commit was in august.  Is it still in progress?  Would there be someone available to approve PRs?

The current status satisfied our requirement and we are not actively adding new features now. But we are totally happy to accept pull request and fix bugs


BatchingChannelReader Timer ObjectDisposedException

Today I encountered the following exception:
System.ObjectDisposedException: Cannot access a disposed object.
   at System.Threading.TimerQueueTimer.Change(UInt32 dueTime, UInt32 period)
   at System.Threading.Timer.Change(Int64 dueTime, Int64 period)
   at Open.ChannelExtensions.BatchingChannelReader`1.TryPipeItems(Boolean flush)
   at Open.ChannelExtensions.BufferingChannelReader`2.TryRead(TOut& item)

I think this can occur because it's possible TryPipeItems retrieves the _timer value on thread A, the last item is pushed to the channel on thread B which disposes and nulls _timer, but then TryPipeItems on thread A still tries to use the value it previously loaded which has now been disposed.

Investigating.

v6.0.3 released to nuget
https://www.nuget.org/packages/Open.ChannelExtensions/6.0.3
THANK YOU!!!


python38Packages.scrapy-deltafetch: 1.2.1 -> 2.0.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.scrapy-deltafetch is: "Scrapy spider middleware to ignore requests to pages containing items seen in previous crawls"
meta.homepage for python38Packages.scrapy-deltafetch is: "https://github.com/scrapy-plugins/scrapy-deltafetch"
meta.changelog for python38Packages.scrapy-deltafetch is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.0.1 with grep in /nix/store/fwzpx5rp36dbq55q9ry1i59l8gdqsv44-python3.8-scrapy-deltafetch-2.0.1

found 2.0.1 in filename of file in /nix/store/fwzpx5rp36dbq55q9ry1i59l8gdqsv44-python3.8-scrapy-deltafetch-2.0.1

directory tree listing: https://gist.github.com/f35d3009419233da161f647c0ee71ec7

du listing: https://gist.github.com/5aec82dc8edaed906d5476e2bbcb5d52

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python38Packages.scrapy-deltafetch
python39Packages.scrapy-deltafetch

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fwzpx5rp36dbq55q9ry1i59l8gdqsv44-python3.8-scrapy-deltafetch-2.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.scrapy-deltafetch https://github.com/r-ryantm/nixpkgs/archive/a3937bf3b8cb8ba09333646c947529084f9b58c1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fwzpx5rp36dbq55q9ry1i59l8gdqsv44-python3.8-scrapy-deltafetch-2.0.1
ls -la /nix/store/fwzpx5rp36dbq55q9ry1i59l8gdqsv44-python3.8-scrapy-deltafetch-2.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

Maintainer pings
cc @evanjs for testing.

@jonringer I’m confused or missing something dumb.
How was this merged after #139053?


Add Login Page

Add a new login page...

Can you assign me!

Can you assign me!

be patient. Thanks.

@frypan01 Sorry for late reply. You can work on it.

Should  I add  a new page or a section in the index.html

Should I add a new page or a section in the index.html

Probably better to make it a separate thing, we don't want newbies to have too many things in a single place. After all the project is to help people new to coding.

Please Review

I would like to work on this issue.Can you please assign me this


Fix and update fixtures

As the api for embeding tweets, vimeo and youtube videos has change,
we need to update the fixtures used for mocking requests and also
updating the reference documents for testing.
Also fixes a bug caused by using .present? without active support.

If GitHub doesn't show a diff, then the fixtures are probably unreadable.
I guess they are fine for integration tests, but now I don't know if they were updated in any meaningful way for the tests to pass.

@christofdamian The fixtures are readable, and gh shows the diff. The ones which are not the are the reference documents, which are generated by the update_reference_script.sh
Maybe we could update the testing process so that they are generated each time? but that could make the test suite slower.
Anyway, this has been like this since the beginning of the project, this time we needed to change because as the responses from some embedded apis have changes, the whole thing changes. I'm really open to change this, but might be a bigger effort, and already took me sometime to realize what was happening (I made a small change, and some test which seemed not related failed).

@towanda I realize it was like this before. It wasn't meant as critic on the current PR. Running the update reference script in CI might be an idea.


Report Layouts Not Rendering To PDF Properly

So I've run into an issue where report layouts are not creating identical PDF's from the web client between environment setups. Running the exact same container image (tried versions from 14.1 up to the most recent mcr.microsoft.com/businesscentral/onprem (and sandbox), with the ltsc2019 branches. The problem environment is running server core 2019 (ltsc) 17763.737.1909062324 as the docker host. With mcr.microsoft.com/businesscentral/onprem:ltsc2019 the Cronus Customer/Item report is being sent from the web client like THIS.
I am not using navcontainerhelper for any of this, and with minimal script changes to test this. I have read through all I can find and know that fonts must be installed on server core as they can't be part of the image. The only change to the scripts is in navstart.ps1 my file starts with:
Invoke-Expression -Command 'c:\run\my\Fonts.ps1'
And then Fonts.ps1 has:
$SourceDir   = "C:\run\my\fonts\"
$Source      = "C:\run\my\fonts\*"
$Destination = (New-Object -ComObject Shell.Application).Namespace(0x14)
$TempFolder  = "C:\Windows\Temp\Fonts"
New-Item -ItemType Directory -Force -Path $SourceDir
New-Item $TempFolder -Type Directory -Force | Out-Null
Get-ChildItem -Path $Source -Include '*.ttf','*.ttc','*.otf' -Recurse | ForEach {
    If (-not(Test-Path "C:\Windows\Fonts\$($_.Name)")) {
        $Font = "$TempFolder\$($_.Name)"
        Copy-Item $($_.FullName) -Destination $TempFolder
        $Destination.CopyHere($Font,0x10)
        Remove-Item $Font -Force
    }
}
I have only included Arial at this point in the fonts folder, and fonts are rendering in reports like in the link above. I add the fonts at the beginning of navstart.ps1 as I think that is the first script the container initiates and hopefully makes sure they are installed prior to the BC service starting. In our dev I like to think that a container is temporal and if it runs into an issue it should be replaced (normally we connect them to existing db's vs SQL in the container). I have read that after installing fonts the whole container must be restarted. If a container is temporal a full restart of the container while retaining settings is an issue as that implies recreating it. If it was a full Windows install with a UI restarting explorer and maybe shell32 would refresh fonts for everything. Typically this is why a restart is suggested after installing things. I am hoping the order things occur is all that is needed within server core. Maybe fonts are being added in the reports, but the report renderer is loaded before that? Fonts maybe get added but spacing and resizing things become broken? Are there services I should restart in server core?
Containers shouldn't inherit any dependencies from their hosts, should they? Having server core as the container host is the big difference here vs where it works. I am also using kubernetes via AKS to orchestrate the cluster, however I'm quite sure the docker engine (19.03.3) is still utilized to run the actual container in that setup and hopefully things run the same.
Using a container orchestrator is obviously something different from the normal nav-docker setup, but a RDL(C) report is rendered to a PDF via a standard .net dll shipped with the product. A container takes the concept of standardization of a product, and standardizes how it is hosted.
Maybe my issue is how that is hosted, maybe it is something with how reports are rendered, or maybe it is with something navcontainerhelper does that I am not doing, but any help would be appreciated in troubleshooting it. I would have assumed the functions to create a pdf would be the same experience between containers, and unless I'm missing some setup for the containers, there is some maybe environment difference effecting the container.
From what I see, the right half of the page probably has all the report elements right aligned to the page. In those the alignments from left to right become messed up in places. Vertically (and horizonally), it looks like the element size was determined prior to rendering the fonts (maybe) and wrapping leads to things being cut off. I am hoping I'm just missing something with my font install as the best case.

I didn't think it was enough to just copy the files to the fonts folder.
In my function, I also install the font:
https://github.com/microsoft/navcontainerhelper/blob/master/Misc/Add-FontsToNavContainer.ps1
You could try that

Thanks Freddy,
I for some reason had assumed that the $Destination = (New-Object -ComObject Shell.Application).Namespace(0x14) and $Destination.CopyHere($Font,0x10) were doing the same thing as the gdi32.dll import in your script, however looking it up this morning showed that wasn't the case.
Using gdi32.dll to register them and the registry changes you had in your script seems to have resolved this. I'm actually very glad it was such a simple mistake by me.

$SourceDir   = "C:\run\my\fonts"
$Source      = "C:\run\my\fonts*"
$Destination = (New-Object -ComObject Shell.Application).Namespace(0x14)
$TempFolder  = "C:\Windows\Temp\Fonts"
#*******************************************************************
#*  Load C# code
#*******************************************************************
$fontCSharpCode = @'
using System;
using System.Collections.Generic;
using System.Text;
using System.IO;
using System.Runtime.InteropServices;
namespace FontResource
{
public class AddRemoveFonts
{
[DllImport("gdi32.dll")]
static extern int AddFontResource(string lpFilename);
public static int AddFont(string fontFilePath) {
try
{
return AddFontResource(fontFilePath);
}
catch
{
return 0;
}
}
}
}
'@
Add-Type $fontCSharpCode
#* Create hashtable containing valid font file extensions and text to append to Registry entry name.
$hashFontFileTypes = @{}
$hashFontFileTypes.Add(".fon", "")
$hashFontFileTypes.Add(".fnt", "")
$hashFontFileTypes.Add(".ttf", " (TrueType)")
$hashFontFileTypes.Add(".ttc", " (TrueType)")
$hashFontFileTypes.Add(".otf", " (OpenType)")
$fontRegistryPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts"
#* Create the source directory if it doesn't already exist
New-Item -ItemType Directory -Force -Path $SourceDir
New-Item $TempFolder -Type Directory -Force | Out-Null
Get-ChildItem -Path $Source -Include '.ttf','.ttc','.otf' -Recurse | ForEach {
If (-not(Test-Path "C:\Windows\Fonts$($.Name)")) {
$Font = "$TempFolder$($.Name)"
# Copy font to local temporary folder
Copy-Item $($.FullName) -Destination $TempFolder
#* Install font
$Destination.CopyHere($Font,0x10)
$path = "C:\Windows\Fonts$($.Name)"
$fileDir  = split-path $path
$fileName = split-path $path -leaf
$fileExt = (Get-Item $path).extension
$fileBaseName = $fileName -replace($fileExt ,"")
$shell = new-object -com shell.application
$myFolder = $shell.Namespace($fileDir)
$fileobj = $myFolder.Items().Item($fileName)
$fontName = $myFolder.GetDetailsOf($fileobj,21)
if ($fontName -eq "") { $fontName = $fileBaseName }
$retVal = [FontResource.AddRemoveFonts]::AddFont($path)
if ($retVal -eq 0) {
Write-Host -ForegroundColor Red "Font '$($path)'' installation failed"         } else {             Write-Host -ForegroundColor Green "Font '$($path)`' installed successfully"
Set-ItemProperty -path "$($fontRegistryPath)" -name "$($fontName)$($hashFontFileTypes.item($fileExt))" -value "$($fileName)" -type STRING
}
#* Delete temporary copy of font
Remove-Item $Font -Force
}
}

@freddydk With MICR support in MS cloud BC coming with 15.3, is it a reasonable request for nav-docker images to automatically install fonts located in maybe c:\run\my\fonts automatically when starting? I know navcontainerhelper has this functionality, and you can't include fonts in the image, but are there restrictions or issues on including font installing within the docker image?

I will add this idea to the idea list. If I do this, the functionality would be in the generic layer and will only be available in new images created after the update.
If you put the above script in AdditionalSetup.ps1 in a folder you share to the my folder together with your fonts, then that will automatically get called and installed and since you need to share a my folder anyway, it seems like an easy approach.


[FEATURE] Improving Modal

Description
Currently we are using ReportModal in the Footer.jsx, which makes the footer component hard to read and manageable.
It's better to have one separate component for for modal as Modal.jsx, which will have that cross button and round corners with white background and that black background (overlay) in the background, the content can be passed through children prop. That way we can separate the modal's logic and design. Thus we can have reusable modal with custom content in it.
It'll also increase readability of Footer.jsx and would make code more manageable
Screenshots
No response
🥦 Browser
Google Chrome
👀 Have you checked for similar open issues?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

Are you willing to work on this issue ?
Yes I am willing to submit a PR!

Amazing concept, assigining to you !

@IAmTamal I am facing some problems in using css styles from Modal.css, as its styles are getting applied on the whole project not on just Modal.jsx. So would it be okay if I use css modules instead like Modal.module.css so it's style only get applied to Modal.jsx?
More on CSS Modules

Umm i don't understand the concept - if you have different classnames this shouldn't happen.

@IAmTamal I have also found some grammatical errors in the project and some .gitignore errors like it's not ignoring the /dist dir that produced by running npm run build, should I fix them in this issue itself? I should create new issues? (they're small issue)

Intresting, i've never tried pushing /dist in the first place lol. My bad.
I think you can make a separate issue for all the other changes. That way we can track the changes that happens over time !


Better output for CppUMock

CppUMock should be able to give more clear & precise output information about the (missing)actual & expectation.
And it will be really great if it can give the line number of the missing expectation.

A missing expectation is missing. It means it was not called, so the framework cannot point to the place where it was not called from... Or I misunderstand something.
But my question is:
Is there any way to allow to continue a test after the first failure? I mean I'd like to get the following failure message:
BlaBla.cpp:394: Actual Value of testVariable = [0 0x0]( != [1 0x1 ] ) does not match expected value
BlaBla.cpp:394: Actual Value of testVariable2 = [5 0x5]( != [2 0x2 ] ) does not match expected value
Expected call "testFunction" called with data = [4 0x4](!= [3 0x3] ) does not match ...

The multiple failure message required by a state machine test, where unfortunatelly I can see only "value not equals with expected one" intead of "target state not reached". I mean because a check fails it hides information about te target state reached or not.


Downgrade to debian stretch

Debian Buster has glibc version 2.28. A number of people have complained that the SDK is broken for them, since their OS does not support that glibc version. Going back to Debian Stretch will mostly resolve that (glibc 2.27 is well supported). I don't think we lose much by downgrading debian.
On the other hand, there will always be someone whose glibc is not supported, and so maybe drawing the line at 2.28 and saying this is the version we officially support is the right way to go.

After some testing it looks like downgrading the debian version is not sufficient to keep glibc to <2.28. I suspect it's clang++-7 that is forcing glibc to upgrade.

fwiw, clang-7 doesn't appear to cause a glibc version upgrade on debian stretch. This is from a local debian:stretch container where I installed clang-7 (GLIBC 2.24 is the same version that ships with a default stretch install):
root@743f80e7d9dc:/# clang++-7 --version | grep version
clang version 7.0.1-8~deb9u2 (tags/RELEASE_701/final)
root@743f80e7d9dc:/# ldd --version | grep GLIBC
ldd (Debian GLIBC 2.24-11+deb9u4) 2.24
root@743f80e7d9dc:/# grep VERSION= /etc/os-release
VERSION="9 (stretch)"

also here is a little table I put together while testing some sdk-packaging changes of a handful of common distros and their default libc / libstdc++ versions, plus the result of attempting to install the .deb / .rpm on that distro when the binaries where built using debian:buster

distro
glibc
libstdc++
install ok?

debian 9 (stetch)
2.24
6.3.0
☠  libc deps

debian 10 (buster)
2.28
8.3.0
ok

ubuntu 16.04.6 LTS (bionic)
2.23
5.4.0
☠  libc deps

ubuntu 18.04.3 LTS (xenial)
2.27
8.3.0
☠  libc deps

centos 7
2.17
4.8.5
☠  libc deps

centos 8
2.28
8.2.1
ok, but  must enable PowerTools repo first

fedora 30
2.29
9.2.1
ok

fedora 29
2.28
8.3.1
ok

I strongly support downgrading ASAP. This is causing lots of user issues.

After some testing it looks like downgrading the debian version is not sufficient to keep glibc to <2.28. I suspect it's clang++-7 that is forcing glibc to upgrade.

Did some more poking at this. The problem dependency is actually libstdc++ (or libc++), not clang-7, which only requires libc >= 2.19 on debian stretch, but also uses an old libstdc++ 6.3.0. Tweedledum requires C++17 support, which means at least libstdc++ >= 7 or libc++ >= 4, though the min required version will depend on exactly which C++17 features tweedledum uses. Probably safest to target the min supported versions claimed in the tweedledum README, i.e. the ones that ship with GCC 7.3.0 / Clang 6.01.
Unfortunately, AFAICT, upgrading libstdc++ on debian stretch means enabling the testing repo, which will also pull in a very recent libc, as @notmgsk mentions.
Here are some (untested) things we might try:

Try building tweedledum against the libc++1-7 that comes with debian stretch. This requires adding a libc++ runtime dependency.

Build our own compiler toolchain, ship our own libstdc++ or libc++ alongside libtweedledum. For example, the libstdc++6 (8.3.0) package for debian buster claims it only depends on libc6 >= 2.22.

Here are the results of testing out the first suggestion from my previous comment, namely building on debian stretch against libc++-7-dev rather than libstdc++. The distros/versions tested are the same as the above table for building on debian buster against libstdc++.
Compared to the current situation as outlined in the above table, we'd gain support for debian 9 and ubuntu 18.04, but lose support for centos 8, since I couldn't find libc++ in any of the centos 8 repos, not even EPEL! I suspect ubuntu and debian are more popular desktop environments than CentOS though, so this is probably a net win.
Building on Debian Stretch against libc++-7-dev

distro
glibc
libc++
./quilc -S

debian 9 (stretch)
2.24
3.5, 7.0
✅

debian 10 (buster)
2.28
7.0
✅

ubuntu 16.04.6 LTS (xenial)
2.23
3.7
☠

ubuntu 18.04.3 LTS (bionic)
2.27
6.0, 7.0
✅

centos 7
2.17
3.8
☠

centos 8
2.28
n/a!
☠

fedora 29
2.28
7.0
✅

fedora 30
2.29
8.0
✅

For distros that have more than one version of libc++ available in their repos, I list the min version and the first version recent enough to satisfy tweedledum's C++ 17 requirements (i.e. libc++1-7 / libc++-7-dev on debian-derived distros).

I think CentOS is the OS used on the QMI and so being unsupported there would be less than ideal.

@notmgsk @appleby What's the resolution here?

The docker image was downgraded to debian stretch in #4 and tweedledum was disbaled in quilc in  https://github.com/rigetti/quilc/pull/475.
With those two changes, all the sdk is working again on all distros / versions in the above table, plus a couple more we tested. notmgsk created a google doc with the details. I'll send you the link.


"9fans.net/go/acme" Inaccessible

"9fans.net/go/acme" Inaccessible

I would like to ask if it can be considered to remove dependency on "9fans.net/go/acme". It seems to be required only by acme.go file (which I assume is some support for acme editor - correct me if I am wrong). It cause download of about 1MB package (9fans.net/go) which I assume most of the users don't need. Its also go against singe responsibility principle.

Unsure if it's the same issue, but certificates for https://9fans.net appear to be expired, so it is no longer possible to go get github.com/rogpeppe/godef.
Reported here: https://github.com/9fans/go/issues/12.
But also another reminder that it would be nice to have acme dependency be separated out.

Fixed by #35


Add support for response body compression

Add support for response body compression …This change lets Undertow compress response body using gzip or deflate
if client sends requests with Accept-Encoding: gzip or
Accept-Encoding: deflate header.
This change assumes #589.
When client sends Accept-Encoding: gzip, deflate, the server uses gzip (gzip has higher priority). This is because the client has a bug with deflate. See #590.

@komamitsu @muga Is there any reason this PR is not merged even though approved same as #589 ?

Just in case, I will postpone to 0.9.41.

As of discussion in person, we will merge to v0_10 after v0_11 has been created.

This change assumes #589 as the description. I will merge this PR and close it.


List View should use asp-action instead of Html.ActionLink

List View currently uses a mix of asp-action and Html.ActionLink:
Create New

@Html.ActionLink("Edit", "Edit", new { /* id=item.PrimaryKey */ }) |
@Html.ActionLink("Details", "Details", new { /* id=item.PrimaryKey */ }) |
@Html.ActionLink("Delete", "Delete", new { /* id=item.PrimaryKey */ })

I think the preferred syntax is now asp-action, so I would suggest replacing Html.ActionLink with asp-action.

This is still an issue a year later.

Any update on this? I think users should be encouraged to use Tag Helpers - and scaffolding is a way to do that.

@mkArtakMSFT - This is a content issue.


Update Pandas 1.0.5

Target branch: pd1.

@xaleryb
I guess it is expected?
[08:22:06]conda.exceptions.ResolvePackageNotFound:
[08:22:06]  - numba==0.50.1
[08:22:06]  - pandas==1.0.5


colorfilter + advanced blend is broken

spawned from: https://github.com/flutter/flutter/issues/155456
reproduction
TEST_P(AiksTest, ImageFilterAdvancedBlend) {
  bool has_color_filter = true;
  auto callback = [&]() -> sk_sp<DisplayList> {
    if (AiksTest::ImGuiBegin("Controls", nullptr,
                             ImGuiWindowFlags_AlwaysAutoResize)) {
      ImGui::Checkbox("has color filter", &has_color_filter);
      ImGui::End();
    }

    DisplayListBuilder builder;
    builder.Scale(GetContentScale().x, GetContentScale().y);

    auto src_image =
        DlImageImpeller::Make(CreateTextureForFixture("blend_mode_src.png"));
    auto dst_image =
        DlImageImpeller::Make(CreateTextureForFixture("blend_mode_dst.png"));

    std::vector<DlBlendMode> blend_modes = {
        DlBlendMode::kScreen,     DlBlendMode::kOverlay,
        DlBlendMode::kDarken,     DlBlendMode::kLighten,
        DlBlendMode::kColorDodge, DlBlendMode::kColorBurn,
        DlBlendMode::kHardLight,  DlBlendMode::kSoftLight,
        DlBlendMode::kDifference, DlBlendMode::kExclusion,
        DlBlendMode::kMultiply,   DlBlendMode::kHue,
        DlBlendMode::kSaturation, DlBlendMode::kColor,
        DlBlendMode::kLuminosity,
    };

    for (uint32_t i = 0; i < blend_modes.size(); ++i) {
      builder.Save();
      builder.Translate((i % 5) * 200, (i / 5) * 200);
      builder.Scale(0.4, 0.4);
      {
        DlPaint dstPaint;
        builder.DrawImage(dst_image, {0, 0}, DlImageSampling::kMipmapLinear,
                          &dstPaint);
      }
      {
        DlPaint srcPaint;
        srcPaint.setBlendMode(blend_modes[i]);
        if (has_color_filter) {
          std::shared_ptr<const DlColorFilter> color_filter =
              DlBlendColorFilter::Make(DlColor::RGBA(0.9, 0.5, 0.0, 1.0),
                                       DlBlendMode::kSrcIn);
          srcPaint.setColorFilter(color_filter);
        }
        builder.DrawImage(src_image, {0, 0}, DlImageSampling::kMipmapLinear,
                          &srcPaint);
      }
      builder.Restore();
    }
    return builder.Build();
  };
  ASSERT_TRUE(OpenPlaygroundHere(callback));
}

observed

expected
(but with an orange src)

Notice that the first blend works correctly, then the subsequent blends don't.  Here's the frame capture of just rendering 2 (multiply and hue).  We can see it is attempting to do the advanced blend for the second render (hue) but we don't get the expected result.
color-filter-adv-blend.gputrace.zip

This is the graph for just drawing 2 (multiply and hue)

It looks like the vertex shader is giving wrong results for the second snapshot
first pass

second pass

The reason it works the first time is only because it's close to the origin.  This problem didn't manifest with the porter dfuf blends because we perform them in place, but when we do an advanced blend we are performing them on a snapshot from a different render pass so the MVP is different for the color filter.  Hopefully we just have to find a way to change the vertex shader's MVP depending on if it's performing on a subpass or not.

I verified that the following patch fixes advanced blends (but breaks porter duff blends).
--- a/impeller/entity/contents/filters/blend_filter_contents.cc
+++ b/impeller/entity/contents/filters/blend_filter_contents.cc
@@ -461,8 +461,12 @@ std::optional<Entity> BlendFilterContents::CreateForegroundPorterDuffBlend(
     FS::FragInfo frag_info;
     VS::FrameInfo frame_info;

+
+    Matrix foo = dst_snapshot->transform;
+    foo.m[12] = 0;
+    foo.m[13] = 0;
     frame_info.mvp = Entity::GetShaderTransform(entity.GetShaderClipDepth(),
-                                                pass, dst_snapshot->transform);
+                                                pass, foo);


cli: netdataregister command should return Done

Running the netdataregister doesn't return the expected 'Done' response:
./soc --nodeid=1 -S
netdataregister
netdataregister

After running the command, other commands still work.  But if the command is run twice, the shell becomes unresponsive to all commands:
./soc --nodeid=1 -S
netdataregister
netdataregister
panid
panid
65535
Done
netdataregister
netdataregister
panid
panid

I submitted #16 to address the hang issue.
"Done" is only printed if the command completes successfully.  In your example, OpenThread was not started yet, so netdataregister is not successful.  Should we enhance the CLI to print "Error" with the error code instead?

Yes, "Error: \r\n" would be a good format and deterministically parseable by the testing suite.

Fixed in #66.


[Feature Request] Show how stale data is

If I search for an item, it shows a list of prices and servers. The issue is, when I go to Universalis.app, I find out half of the servers haven't been checked for that item in 3 weeks. I have no issue going to those servers to check/update the prices for everyone, but /pmb doesn't indicate if data is stale, or at least not that I was able to find, and seems to represent all data as current. I'd be happy with just a colored dot or something, green for updated in last day, yellow for last 3 days, red for way out of date, maybe customizable time breakdowns in the settings.  Ideally, there would be a column with an accurate listing of exactly when a server had a data refresh, but the dot would make me happy.

Ok, I found that if I specify exact servers, that there is an update timer under the server name. Since I normally search by DC, it didn't occur to me to check this way.  Still, that being said, it would be nice to see a quick idea of how stale a price is listed with the price instead of having to survey each server individually for each item.


[IR-6046] to develop

Change ProductsApi#productsRefDiagramImageGet()'s and ProductsApi#productsRefDiagramImageGetWithHttpInfo()'s return type from String to byte[].

@nestorrente since this whole project is auto-generated from swagger, it does not contain Java src code.  Will this patch still work when the user runs: mvn package to re-generate the jar from swagger?

@stephendv1 we have updated the swagger.yaml file for preventing the patch from being lost when re-generate the jar :) thank you for noticing!


Fix violated rule R2026 for 2022-02-01 managedCluster swagger

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Fix the violated rule R2026 (AvoidAnonymousTypes/SDKViolation) in stable/2022-02-01 managedCluster.

Change the nesting relationship between allOf and properties in the model definition.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Hi @leni-msft , this PR aims to fix the R2026 rule violated in our swagger managedClusters of 2022-02-01. There's a similar PR for the preview version 2022-02-02-preview.
Could you please help review and merge this PR? Thanks!


Debugging

Is there any sort of debugging? I'm getting pages without any content but all it logs is "Listen 3000" and a couple of proxy warnings. It doesn't seem to log anything for requests, or authentication, etc.

hey, there are no logs currently, as for the missing responses, i belive i have had this report once, but logging is probably what will help get this fixed. thanks for reporting.


Add parsing and message support for embeds

The current system only works off of message.content, which is fine. Except, if we aren't ignoring bots then embeds are a thing we should handle. However, I won't work on this until a later date.

Loosely tie into something similar to this where it recursively gets all text contained in the embed


Failing to connect to Qb2 device

Hi!
I am trying to get pointcloud from the lidar but the ros2 driver fails to connect to the device giving the following error:
[blickfeld_qb2_driver]: Failed to connect to Qb2: qb2-xxxxxxxxx , due to: Connection to Qb2 device 'qb2-xxxxxxxxx:50051' failed (insecure pre-handshake serial number fetch): DNS resolution failed.
In the blickfeld_qb2_ros2_driver.launch.py file I tried providing both the IP address and qb2-xxxxxxxxx host name as parameters but get the same error for both.
Using the IP address I can ping the device and in the WebUI I can access the device and also get a pointcloud.
Any advice would be helpful.
Thank you

Updated: was using the host IP instead of using device IP. Using device IP works however the hostname does not work

I'm having the exact same problem, where I can ping the device and access via WebUI, but the ros2 driver is failing to connect (colcon build was successful). Could you explain me what exactly you changed to solve the problem? I don't understand where you get the device IP and where I should put it in. Thank you in advance!