Pixi errror when loading pytest in VS code

Type: Bug

Behaviour
I get a pytest discovery error when starting pytest from the vs code testing window. The systems utilizes micromamba as the python package manager, with an alias set up between conda -> micromamba. The error originates from pixi not being found,
Steps to reproduce:

Use micromamba environment that is activated in powershell
Open VSCode and the testing toolbar (with the Python Extension set to 2024.10.0)
Tests will not be discovered

Diagnostic data

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

XXX

Extension version: 2024.10.0
VS Code version: Code 1.91.0 (ea1445cc7016315d0f5728f8e8b12a45dc0a7286, 2024-07-01T18:52:22.949Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

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

User Settings

condaPath: "<placeholder>"

languageServer: "Pylance"

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

Installed Extensions

Extension Name
Extension Id
Version

autoDocstring - Python Docstring Generator
njpwerner.autodocstring
0.6.1

CodeSnap
adpyke.codesnap
1.3.4

CSV to Table
phplasma.csv-to-table
1.4.0

Data Wrangler
ms-toolsai.datawrangler
1.4.1

FindItFaster
TomRijndorp.find-it-faster
0.0.38

Git Graph
mhutchie.git-graph
1.30.0

GitLens — Git supercharged
eamodio.gitlens
15.1.0

Hex Editor
ms-vscode.hexeditor
1.10.0

JavaScript Debugger
ms-vscode.js-debug
1.91.0

json
ZainChen.json
2.0.2

Jupyter
ms-toolsai.jupyter
2024.6.0

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

Jupyter Notebook Renderers
ms-toolsai.jupyter-renderers
1.0.18

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

Live Preview
ms-vscode.live-server
0.4.13

Path Intellisense
christian-kohler.path-intellisense
2.9.0

Pretty Formatter
mblode.pretty-formatter
0.2.4

Pylance
ms-python.vscode-pylance
2024.6.1

Python
ms-python.python
2024.11.2024070801

Python Debugger
ms-python.debugpy
2024.6.0

Rainbow CSV
mechatroner.rainbow-csv
3.12.0

SQLite
alexcvzz.vscode-sqlite
0.14.1

SVG
jock.svg
1.5.4

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

Todo Tree
Gruntfuggly.todo-tree
0.0.226

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (8 x 2995)

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: enabled

Load (avg)
undefined

Memory (System)
23.71GB (5.42GB free)

Process Argv
--folder-uri=vscode-remote://wsl+Ubuntu-22.04/home/adam/Documents/Git/QUIET --remote=wsl+Ubuntu-22.04

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu-22.04

OS
Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

CPUs
11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (8 x 0)

Memory (System)
11.54GB (9.78GB free)

VM
0%

I have the same issue. It started happening after the latest VS Code Python extension update. I use Poetry for creating my virtual environments and I don't even know what Pixi is.

I have tested that downgrading to v2024.8.1 works @rafrafek. However this is a temporary solution, and I would highly appreciate fixing the bug by the core team

My logs:
2024-07-09 14:41:13.122 [info] Experiment 'pythonCreateEnvOnPipInstall' is active
2024-07-09 14:41:13.122 [info] Experiment 'pythonRecommendTensorboardExt' is active
2024-07-09 14:41:13.122 [info] Experiment 'pythonTerminalEnvVarActivation' is active
2024-07-09 14:41:13.122 [info] Experiment 'pythonTestAdapter' is active
2024-07-09 14:41:13.122 [error] Reading directory to watch failed [Error: ENOENT: no such file or directory, scandir '/Users/username/Projects/project-name/.pixi/envs'
	at Object.readdirSync (node:fs:1515:3)
	at t.readdirSync (node:electron/js2c/node_init:2:11289)
	at /Users/username/.vscode/extensions/ms-python.python-2024.10.0-darwin-arm64/out/client/extension.js:2:574598
	at /Users/username/.vscode/extensions/ms-python.python-2024.10.0-darwin-arm64/out/client/extension.js:2:574789
	at Array.map (<anonymous>)
	at d.initWatchers (/Users/username/.vscode/extensions/ms-python.python-2024.10.0-darwin-arm64/out/client/extension.js:2:574507)
	at async d.ensureWatchersReady (/Users/username/.vscode/extensions/ms-python.python-2024.10.0-darwin-arm64/out/client/extension.js:2:536827)] {
  errno: -2,
  syscall: 'scandir',
  code: 'ENOENT',
  path: '/Users/username/Projects/project-name/.pixi/envs'
}
2024-07-09 14:41:13.122 [error] Dir "/Users/username/Projects/project-name/.pixi/envs" is not watchable (directory does not exist)
2024-07-09 14:41:13.154 [info] Default formatter is set to null for workspace /Users/username/Projects/project-name
2024-07-09 14:41:13.157 [info] Python interpreter path: ./.venv/bin/python
2024-07-09 14:41:13.282 [info] > pyenv which python
2024-07-09 14:41:13.282 [info] cwd: .
2024-07-09 14:41:13.915 [info] > pixi --version
2024-07-09 14:41:13.916 [error] [Error: spawn pixi ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn pixi',
  path: 'pixi',
  spawnargs: [ '--version' ]
}
2024-07-09 14:41:13.916 [warning] could not find a pixi interpreter for the interpreter at /Users/username/Projects/project-name/.venv/bin/python
2024-07-09 14:41:14.487 [warning] could not find a pixi interpreter for the interpreter at /Users/username/Projects/project-name/.venv/bin/python
2024-07-09 14:41:14.497 [info] > . ./.venv/bin/activate && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode/extensions/ms-python.python-2024.10.0-darwin-arm64/python_files/printEnvVariables.py
2024-07-09 14:41:14.497 [info] shell: bash
2024-07-09 14:41:14.527 [warning] could not find a pixi interpreter for the interpreter at /Users/username/Projects/project-name/.venv/bin/python
2024-07-09 14:41:14.528 [info] > ./.venv/bin/python -m pytest -p vscode_pytest --collect-only tests
2024-07-09 14:41:14.528 [info] cwd: .
2024-07-09 14:41:14.657 [error] Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/pytest/__main__.py", line 5, in <module>
    raise SystemExit(pytest.console_main())
                     ^^^^^^^^^^^^^^^^^^^^^
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 192, in console_main
    code = main()
           ^^^^^^
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 150, in main

2024-07-09 14:41:14.658 [error] config = _prepareconfig(args, plugins)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 331, in _prepareconfig
    config = pluginmanager.hook.pytest_cmdline_parse(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/pluggy/_hooks.py", line 265, in __call__
    return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/pluggy/_manager.py", line 80, in _hookexec
    return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/pluggy/_callers.py", line 55, in _multicall
    gen.send(outcome)
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/_pytest/helpconfig.py", line 104, in pytest_cmdline_parse
    config: Config = outcome.get_result()
                     ^^^^^^^^^^^^^^^^^^^^
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/pluggy/_result.py", line 60, in get_result
    raise ex[1].with_traceback(ex[2])

2024-07-09 14:41:14.658 [error]   File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/pluggy/_callers.py", line 39, in _multicall
    res = hook_impl.function(*args)
          ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 1075, in pytest_cmdline_parse

2024-07-09 14:41:14.658 [error]     self.parse(args)
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 1425, in parse
    self._preparse(args, addopts=addopts)
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 1301, in _preparse

2024-07-09 14:41:14.659 [error]     self.pluginmanager.consider_preparse(args, exclude_only=False)
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 709, in consider_preparse

2024-07-09 14:41:14.659 [error]     self.consider_pluginarg(parg)
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 735, in consider_pluginarg

2024-07-09 14:41:14.659 [error]     self.import_plugin(arg, consider_entry_points=True)
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 781, in import_plugin

2024-07-09 14:41:14.659 [error]     __import__(importspec)

2024-07-09 14:41:14.659 [error]   File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "/Users/username/Projects/project-name/.venv/lib/python3.12/site-packages/_pytest/assertion/rewrite.py", line 186, in exec_module
    exec(co, module.__dict__)
  File "/Users/username/.vscode/extensions/ms-python.python-2024.10.0-darwin-arm64/python_files/vscode_pytest/__init__.py", line 895, in <module>
    class DeferPlugin:
  File "/Users/username/.vscode/extensions/ms-python.python-2024.10.0-darwin-arm64/python_files/vscode_pytest/__init__.py", line 896, in DeferPlugin
    @pytest.hookimpl(wrapper=True)
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: HookimplMarker.__call__() got an unexpected keyword argument 'wrapper'

2024-07-09 14:41:14.676 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /Users/username/Projects/project-name.
2024-07-09 14:41:14.677 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /Users/username/Projects/project-name. Creating and sending error discovery payload
2024-07-09 14:41:14.677 [error] pytest test discovery error for workspace:  /Users/username/Projects/project-name

 The python test process was terminated before it could exit on its own, the process errored with: Code: 1, Signal: null for workspace /Users/username/Projects/project-name

Hi! What version of pytest are you using? It might be due to you being on a older version and updating might fix your problem.

Hi! I'm using version 7.4.4, and updating to the latest version 8.2.2 fixed the issue in my case. I'm not the author of this issue, though, so I would wait to confirm if it helps in that case.

I have also had this issue

I had the same problem. It seems that having the pytest verion 7.4.4, and updating to the latest version 8.2.2, fixed the issue on my end

I have now checked my environment package versions, and I had pytest running also running on 7.4.4, however, as @jk1man1 and @rafrafek pointed out, 8.2.2 works out of the box. I have also tested, and 7.4.0 works as well.
I am therefore closing this issue, as not relevant for vscode-python

Hi, seems like this is actually this error: https://github.com/microsoft/vscode-python/issues/23707 and therefore a duplicate. I am putting in a fix hopefully today for it. Lmk if you aren't seeing this error and are seeing something else and I can reopen thank you!

If someone wants to stay on Pytest version 7.x, can just bump pluggy https://pypi.org/project/pluggy/ to version 1.5.0.

@garganpaull are you trying to use pixi?

@garganpaull are you trying to use pixi?

No.  I dont even know what Pixi is.

my steps to a solution:

poetry update pytest
removed .venv
updated python version from 3.10 to 3.11 in pyrpoject.toml
removed poetry.lock
poetry env use 3.11
poetry install

ended up with
pytest            8.2.2
pluggy            1.5.0

I am actually also encountering this pixi error on my VS Code after the update. Right now, pytest Discovery is displaying errors that I have never seen before.
My current Versions are:
pytest 7.2.2
pytest bdd 7.1.2
pluggy 1.0.0
VSCode 1.91.1
python 3.8.10
Here is the complete error:
`2024-07-12 15:09:10.914 [info] Experiment 'pythonaacf' is active
2024-07-12 15:09:10.915 [info] Experiment 'pythonCreateEnvOnPipInstall' is active
2024-07-12 15:09:10.915 [info] Experiment 'pythonRecommendTensorboardExt' is active
2024-07-12 15:09:10.915 [info] Experiment 'pythonTerminalEnvVarActivation' is active
2024-07-12 15:09:10.915 [info] Experiment 'pythonTestAdapter' is active
2024-07-12 15:09:10.915 [error] Reading directory to watch failed [Error: ENOENT: no such file or directory, scandir 'c:\qa-sphere-frontend-pom-bdd.pixi\envs'
at Object.readdirSync (node:fs:1515:3)
at t.readdirSync (node:electron/js2c/node_init:2:11289)
at c:\Users<username>.vscode\extensions\ms-python.python-2024.10.0-win32-x64\out\client\extension.js:2:574598
at c:\Users<username>.vscode\extensions\ms-python.python-2024.10.0-win32-x64\out\client\extension.js:2:574789
at Array.map ()
at d.initWatchers (c:\Users<username>.vscode\extensions\ms-python.python-2024.10.0-win32-x64\out\client\extension.js:2:574507)
at async d.ensureWatchersReady (c:\Users<username>.vscode\extensions\ms-python.python-2024.10.0-win32-x64\out\client\extension.js:2:536827)] {
errno: -4058,
syscall: 'scandir',
code: 'ENOENT',
path: 'c:\<project_name>\.pixi\envs'
}
2024-07-12 15:09:10.915 [error] Dir "c:<project_name>.pixi\envs" is not watchable (directory does not exist)
2024-07-12 15:09:10.915 [info] Default formatter is set to null for workspace c:<project_name>
2024-07-12 15:09:10.958 [info] Python interpreter path: ..venv\Scripts\python.exe
2024-07-12 15:09:11.763 [info] > pyenv which python
2024-07-12 15:09:11.763 [info] cwd: .
2024-07-12 15:09:11.848 [info] > conda info --json
2024-07-12 15:09:12.491 [info] > pixi --version
2024-07-12 15:09:12.511 [error] [Error: spawn pixi ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)] {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn pixi',
path: 'pixi',
spawnargs: [ '--version' ]
}
2024-07-12 15:09:12.512 [warning] could not find a pixi interpreter for the interpreter at c:<project_name>.venv\Scripts\python.exe
2024-07-12 15:09:12.803 [info] > & ./.venv/Scripts/Activate.ps1 ; echo 'e8b39361-0157-4923-80e1-22d70d46dee6' ; python ~/.vscode/extensions/ms-python.python-2024.10.0-win32-x64/python_files/printEnvVariables.py
2024-07-12 15:09:12.803 [info] shell: powershell
2024-07-12 15:09:14.207 [info] Discover tests for workspace name: <project_name> - uri: c:<project_name>
2024-07-12 15:09:14.207 [info] Running discovery for pytest using the new test adapter.
2024-07-12 15:09:14.231 [warning] The cwd resolves to a different path, checking if it has a symbolic link somewhere in its path.
2024-07-12 15:09:14.233 [warning] could not find a pixi interpreter for the interpreter at c:<project_name>.venv\Scripts\python.exe
2024-07-12 15:09:14.562 [info] > ./.venv/Scripts/activate.bat && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode/extensions/ms-python.python-2024.10.0-win32-x64/python_files/printEnvVariables.py
2024-07-12 15:09:14.562 [info] shell: commandPrompt
2024-07-12 15:09:14.841 [info] > C:\ProgramData\anaconda3\Scripts\conda.exe info --json
2024-07-12 15:09:15.309 [info] > ~\AppData\Local\Programs\Python\Python38\python.exe ~/.vscode/extensions/ms-python.python-2024.10.0-win32-x64/python_files/printEnvVariables.py
2024-07-12 15:09:15.309 [info] shell: powershell
2024-07-12 15:09:15.312 [warning] could not find a pixi interpreter for the interpreter at c:<project_name>.venv\Scripts\python.exe
2024-07-12 15:09:15.335 [info] > ..venv\Scripts\python.exe -m pytest -p vscode_pytest --collect-only .
2024-07-12 15:09:15.335 [info] cwd: .
2024-07-12 15:09:15.417 [info] Starting Pylance language server.
2024-07-12 15:09:16.116 [info] Prepending environment variable PATH in collection with c:\Users<username>.vscode\extensions\ms-python.python-2024.10.0-win32-x64\python_files\deactivate\powershell;C:<project_name>.venv\Scripts; {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-07-12 15:09:16.116 [info] Setting environment variable VIRTUAL_ENV in collection to C:<project_name>.venv {"applyAtShellIntegration":true,"applyAtProcessCreation":true}
2024-07-12 15:09:16.909 [error] Traceback (most recent call last):
File "C:\Users<username>\AppData\Local\Programs\Python\Python38\lib\runpy.py", line 194, in run_module_as_main
return run_code(code, main_globals, None,
File "C:\Users<username>\AppData\Local\Programs\Python\Python38\lib\runpy.py", line 87, in run_code
exec(code, run_globals)
File "c:<project_name>.venv\lib\site-packages\pytest_main.py", line 5, in
raise SystemExit(pytest.console_main())
File "c:<project_name>.venv\lib\site-packages_pytest\config_init.py", line 189, in console_main
code = main()
File "c:<project_name>.venv\lib\site-packages_pytest\config_init.py", line 147, in main
config = prepareconfig(args, plugins)
File "c:<project_name>.venv\lib\site-packages_pytest\config_init.py", line 328, in _prepareconfig
config = pluginmanager.hook.pytest_cmdline_parse(
File "c:<project_name>.venv\lib\site-packages\pluggy_hooks.py", line 265, in call
return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult)
File "c:<project_name>.venv\lib\site-packages\pluggy_manager.py", line 80, in hookexec
return self.inner_hookexec(hook_name, methods, kwargs, firstresult)
File "c:<project_name>.venv\lib\site-packages\pluggy_callers.py", line 55, in multicall
gen.send(outcome)
File "c:<project_name>.venv\lib\site-packages_pytest\helpconfig.py", line 103, in pytest_cmdline_parse
config: Config = outcome.get_result()
File "c:<project_name>.venv\lib\site-packages\pluggy_result.py", line 60, in get_result
raise ex[1].with_traceback(ex[2])
File "c:<project_name>.venv\lib\site-packages\pluggy_callers.py", line 39, in multicall
res = hook_impl.function(*args)
File "c:<project_name>.venv\lib\site-packages_pytest\config_init.py", line 1075, in pytest_cmdline_parse
self.parse(args)
File "c:<project_name>.venv\lib\site-packages_pytest\config_init.py", line 1425, in parse
self.preparse(args, addopts=addopts)
File "c:<project_name>.venv\lib\site-packages_pytest\config_init.py", line 1301, in preparse
self.pluginmanager.consider_preparse(args, exclude_only=False)
File "c:<project_name>.venv\lib\site-packages_pytest\config_init.py", line 710, in consider_preparse
self.consider_pluginarg(parg)
File "c:<project_name>.venv\lib\site-packages_pytest\config_init.py", line 736, in consider_pluginarg
self.import_plugin(arg, consider_entry_points=True)
File "c:<project_name>.venv\lib\site-packages_pytest\config_init.py", line 782, in import_plugin
import(importspec)
File "", line 991, in _find_and_load
File "", line 975, in find_and_load_unlocked
File "", line 671, in load_unlocked
File "c:<project_name>.venv\lib\site-packages_pytest\assertion\rewrite.py", line 178, in exec_module
exec(co, module.dict)
File "c:\Users<username>.vscode\extensions\ms-python.python-2024.10.0-win32-x64\python_files\vscode_pytest_init.py", line 895, in
class DeferPlugin:
File "c:\Users<username>.vscode\extensions\ms-python.python-2024.10.0-win32-x64\python_files\vscode_pytest_init.py", line 896, in DeferPlugin
@pytest.hookimpl(wrapper=True)
TypeError: call() got an unexpected keyword argument 'wrapper'
2024-07-12 15:09:16.987 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace c:<project_name>.
2024-07-12 15:09:16.987 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace c:<project_name>. Creating and sending error discovery payload
2024-07-12 15:09:16.987 [error] pytest test discovery error for workspace:  c:<project_name>
The python test process was terminated before it could exit on its own, the process errored with: Code: 1, Signal: null for workspace c:<project_name>
`

I can report the same problem. In my output log I can find:
2024-07-16 12:15:12.324 [error] Reading directory to watch failed [Error: ENOENT: no such file or directory, scandir '/home/path_to_the_project/.pixi/envs'
Apart from it, I can also find this in my output log:
2024-07-16 12:18:22.351 [info] INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/local/miniconda3/envs/<project_name>/lib/python3.11/site-packages/_pytest/main.py", line 271, in wrap_session
INTERNALERROR>     session.exitstatus = doit(config, session) or 0

2024-07-16 12:18:22.351 [info] INTERNALERROR>                          ^^^^^^^^^^^^^^^^^^^^^
INTERNALERROR>   File "/local/miniconda3/envs/<project_name>/lib/python3.11/site-packages/_pytest/main.py", line 324, in _main
INTERNALERROR>     config.hook.pytest_collection(session=session)
INTERNALERROR>   File "/local/miniconda3/envs/<project_name>/lib/python3.11/site-packages/pluggy/_hooks.py", line 501, in __call__
INTERNALERROR>     return self._hookexec(self.name, self._hookimpls.copy(), kwargs, firstresult)
INTERNALERROR>            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
INTERNALERROR>   File "/local/miniconda3/envs/<project_name>/lib/python3.11/site-packages/pluggy/_manager.py", line 119, in _hookexec
INTERNALERROR>     return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
INTERNALERROR>            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
INTERNALERROR>   File "/local/miniconda3/envs/<project_name>/lib/python3.11/site-packages/pluggy/_callers.py", line 181, in _multicall
INTERNALERROR>     return outcome.get_result()
INTERNALERROR>            ^^^^^^^^^^^^^^^^^^^^
INTERNALERROR>   File "/local/miniconda3/envs/<project_name>/lib/python3.11/site-packages/pluggy/_result.py", line 99, in get_result
INTERNALERROR>     raise exc.with_traceback(exc.__traceback__)
INTERNALERROR>   File "/local/miniconda3/envs/<project_name>/lib/python3.11/site-packages/pluggy/_callers.py", line 102, in _multicall
INTERNALERROR>     res = hook_impl.function(*args)
INTERNALERROR>           ^^^^^^^^^^^^^^^^^^^^^^^^^
INTERNALERROR>   File "/local/miniconda3/envs/<project_name>/lib/python3.11/site-packages/_pytest/main.py", line 335, in pytest_collection
INTERNALERROR>     session.perform_collect()
INTERNALERROR>   File "/local/miniconda3/envs/<project_name>/lib/python3.11/site-packages/_pytest/main.py", line 677, in perform_collect
INTERNALERROR>     self.config.pluginmanager.check_pending()
INTERNALERROR>   File "/local/miniconda3/envs/<project_name>/lib/python3.11/site-packages/pluggy/_manager.py", line 384, in check_pending
INTERNALERROR>     raise PluginValidationError(
INTERNALERROR> pluggy._manager.PluginValidationError: unknown hook 'pytest_xdist_auto_num_workers' in plugin <vscode_pytest.DeferPlugin object at 0x7f1936d327d0>

I don't know if it is related to pixi.

@garganpaull are you trying to use pixi?

No. I dont even know what Pixi is.
My colleague does not have this issue and is running Pytest version is 7.2.0, Python version is 3.10.2 using VS Code v1.86.2.
Im using VS Code 1.91.1, Python 3.10.6, pytest-8.2.2, pluggy-1.5.0.
This issue only started for me yesterday when I upgraded my VS Code

Is this fixed yet as problem still persists.

I'm using VS Code 1.91.1, Python 3.10.6, pytest-8.2.2, pluggy-1.5.0.

Can you try with Python 3.10.14? Python 3.10.6 is 2 years old and there were many fixes between 3.10.6 and 3.10.14.

Also having this issue. I have no idea about or intention to use Pixi.

Dir "/workspaces/EARL-CAPEX-API/.pixi/envs" is not watchable (directory does not exist)
This is untrue; I explicitly created that path... and yet the error persists.
pluggy             1.5.0
pytest             8.2.2
pytest-cov         5.0.0
Python 3.9.2 (required by my project)
Linux e0655aa2f2f5 5.15.0-117-generic #127-Ubuntu SMP Fri Jul 5 20:13:28 UTC 2024 x86_64 GNU/Linux

Hello,
I am also having the same error but I am willing to use pixi:
2024-08-07 15:35:42.061 [error]
EnvironmentLocationNotFound: Not a conda environment: /HOME/mambaforge/envs/default

2024-08-07 15:35:42.198 [info] Send text to terminal: /HOME/mambaforge/bin/conda install --name default pytest -y
2024-08-07 15:35:42.522 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /HOME/path.
2024-08-07 15:35:42.522 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /HOME/path. Creating and sending error discovery payload
2024-08-07 15:35:42.535 [error] pytest test discovery error for workspace:  /HOME/path

 The python test process was terminated before it could exit on its own, the process errored with: Code: 1, Signal: null for workspace /HOME/path
2024-08-07 15:35:42.896 [warning] could not find a pixi interpreter for the interpreter at /HOME/path
2024-08-07 15:35:42.919 [info] > ~/mambaforge/bin/conda run -n default --no-capture-output python ~/.vscode-server/extensions/ms-python.python-2024.12.2-linux-x64/python_files/get_output_via_markers.py -c "import pytest"

It says it cannot find pixi interpreter, but I actually have pixi installed and setup as my python interpreter.

I am actually also encountering this pixi error on my VS Code after the update. Right now, pytest Discovery is displaying errors that I have never seen before.
My current Versions are: pytest 7.2.2 pytest bdd 7.1.2 pluggy 1.0.0 VSCode 1.91.1 python 3.8.10
Here is the complete error:
`2024-07-12 15:09:10.914 [info] Experiment 'pythonaacf' is active 2024-07-12 15:09:10.915 [info] Experiment 'pythonCreateEnvOnPipInstall' is active 2024-07-12 15:09:10.915 [info] Experiment 'pythonRecommendTensorboardExt' is active 2024-07-12 15:09:10.915 [info] Experiment 'pythonTerminalEnvVarActivation' is active 2024-07-12 15:09:10.915 [info] Experiment 'pythonTestAdapter' is active 2024-07-12 15:09:10.915 [error] Reading directory to watch failed [Error: ENOENT: no such file or directory, scandir 'c:<project_name>.pixi\envs' at Object.readdirSync (node:fs:1515:3) at t.readdirSync (node:electron/js2c/node_init:2:11289) at c:\Users.vscode\extensions\ms-python.python-2024.10.0-win32-x64\out\client\extension.js:2:574598 at c:\Users.vscode\extensions\ms-python.python-2024.10.0-win32-x64\out\client\extension.js:2:574789 at Array.map () at d.initWatchers (c:\Users.vscode\extensions\ms-python.python-2024.10.0-win32-x64\out\client\extension.js:2:574507) at async d.ensureWatchersReady (c:\Users.vscode\extensions\ms-python.python-2024.10.0-win32-x64\out\client\extension.js:2:536827)] { errno: -4058, syscall: 'scandir', code: 'ENOENT', path: 'c:<project_name>.pixi\envs' } 2024-07-12 15:09:10.915 [error] Dir "c:<project_name>.pixi\envs" is not watchable (directory does not exist) 2024-07-12 15:09:10.915 [info] Default formatter is set to null for workspace c:<project_name> 2024-07-12 15:09:10.958 [info] Python interpreter path: ..venv\Scripts\python.exe 2024-07-12 15:09:11.763 [info] > pyenv which python 2024-07-12 15:09:11.763 [info] cwd: . 2024-07-12 15:09:11.848 [info] > conda info --json 2024-07-12 15:09:12.491 [info] > pixi --version 2024-07-12 15:09:12.511 [error] [Error: spawn pixi ENOENT at ChildProcess.handle.onexit (node:internal/child_process:286:19) at onErrorNT (node:internal/child_process:484:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)] { errno: -4058, code: 'ENOENT', syscall: 'spawn pixi', path: 'pixi', spawnargs: [ '--version' ] } 2024-07-12 15:09:12.512 [warning] could not find a pixi interpreter for the interpreter at c:<project_name>.venv\Scripts\python.exe 2024-07-12 15:09:12.803 [info] > & ./.venv/Scripts/Activate.ps1 ; echo 'e8b39361-0157-4923-80e1-22d70d46dee6' ; python ~/.vscode/extensions/ms-python.python-2024.10.0-win32-x64/python_files/printEnvVariables.py 2024-07-12 15:09:12.803 [info] shell: powershell 2024-07-12 15:09:14.207 [info] Discover tests for workspace name: <project_name> - uri: c:<project_name> 2024-07-12 15:09:14.207 [info] Running discovery for pytest using the new test adapter. 2024-07-12 15:09:14.231 [warning] The cwd resolves to a different path, checking if it has a symbolic link somewhere in its path. 2024-07-12 15:09:14.233 [warning] could not find a pixi interpreter for the interpreter at c:<project_name>.venv\Scripts\python.exe 2024-07-12 15:09:14.562 [info] > ./.venv/Scripts/activate.bat && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode/extensions/ms-python.python-2024.10.0-win32-x64/python_files/printEnvVariables.py 2024-07-12 15:09:14.562 [info] shell: commandPrompt 2024-07-12 15:09:14.841 [info] > C:\ProgramData\anaconda3\Scripts\conda.exe info --json 2024-07-12 15:09:15.309 [info] > ~\AppData\Local\Programs\Python\Python38\python.exe ~/.vscode/extensions/ms-python.python-2024.10.0-win32-x64/python_files/printEnvVariables.py 2024-07-12 15:09:15.309 [info] shell: powershell 2024-07-12 15:09:15.312 [warning] could not find a pixi interpreter for the interpreter at c:<project_name>.venv\Scripts\python.exe 2024-07-12 15:09:15.335 [info] > ..venv\Scripts\python.exe -m pytest -p vscode_pytest --collect-only . 2024-07-12 15:09:15.335 [info] cwd: . 2024-07-12 15:09:15.417 [info] Starting Pylance language server. 2024-07-12 15:09:16.116 [info] Prepending environment variable PATH in collection with c:\Users.vscode\extensions\ms-python.python-2024.10.0-win32-x64\python_files\deactivate\powershell;C:<project_name>.venv\Scripts; {"applyAtShellIntegration":true,"applyAtProcessCreation":true} 2024-07-12 15:09:16.116 [info] Setting environment variable VIRTUAL_ENV in collection to C:<project_name>.venv {"applyAtShellIntegration":true,"applyAtProcessCreation":true} 2024-07-12 15:09:16.909 [error] Traceback (most recent call last): File "C:\Users\AppData\Local\Programs\Python\Python38\lib\runpy.py", line 194, in run_module_as_main return run_code(code, main_globals, None, File "C:\Users\AppData\Local\Programs\Python\Python38\lib\runpy.py", line 87, in run_code exec(code, run_globals) File "c:<project_name>.venv\lib\site-packages\pytest__main.py", line 5, in raise SystemExit(pytest.console_main()) File "c:<project_name>.venv\lib\site-packages_pytest\config__init.py", line 189, in console_main code = main() File "c:<project_name>.venv\lib\site-packages_pytest\config__init__.py", line 147, in main config = prepareconfig(args, plugins) File "c:<project_name>.venv\lib\site-packages_pytest\config__init_.py", line 328, in prepareconfig config = pluginmanager.hook.pytest_cmdline_parse( File "c:<project_name>.venv\lib\site-packages\pluggy_hooks.py", line 265, in call return self.hookexec(self.name, self.get_hookimpls(), kwargs, firstresult) File "c:<project_name>.venv\lib\site-packages\pluggy_manager.py", line 80, in hookexec return self.inner_hookexec(hook_name, methods, kwargs, firstresult) File "c:<project_name>.venv\lib\site-packages\pluggy_callers.py", line 55, in multicall gen.send(outcome) File "c:<project_name>.venv\lib\site-packages_pytest\helpconfig.py", line 103, in pytest_cmdline_parse config: Config = outcome.get_result() File "c:<project_name>.venv\lib\site-packages\pluggy_result.py", line 60, in get_result raise ex[1].with_traceback(ex[2]) File "c:<project_name>.venv\lib\site-packages\pluggy_callers.py", line 39, in multicall res = hook_impl.function(*args) File "c:<project_name>.venv\lib\site-packages_pytest\config__init.py", line 1075, in pytest_cmdline_parse self.parse(args) File "c:<project_name>.venv\lib\site-packages_pytest\config__init.py", line 1425, in parse self.preparse(args, addopts=addopts) File "c:<project_name>.venv\lib\site-packages_pytest\config__init.py", line 1301, in preparse self.pluginmanager.consider_preparse(args, exclude_only=False) File "c:<project_name>.venv\lib\site-packages_pytest\config__init.py", line 710, in consider_preparse self.consider_pluginarg(parg) File "c:<project_name>.venv\lib\site-packages_pytest\config__init__.py", line 736, in consider_pluginarg self.import_plugin(arg, consider_entry_points=True) File "c:<project_name>.venv\lib\site-packages_pytest\config__init__.py", line 782, in import_plugin import(importspec) File "", line 991, in find_and_load File "", line 975, in find_and_load_unlocked File "", line 671, in load_unlocked File "c:<project_name>.venv\lib\site-packages_pytest\assertion\rewrite.py", line 178, in exec_module exec(co, module.dict) File "c:\Users.vscode\extensions\ms-python.python-2024.10.0-win32-x64\python_files\vscode_pytest__init.py", line 895, in class DeferPlugin: File "c:\Users.vscode\extensions\ms-python.python-2024.10.0-win32-x64\python_files\vscode_pytest__init_.py", line 896, in DeferPlugin @pytest.hookimpl(wrapper=True) TypeError: call() got an unexpected keyword argument 'wrapper'
2024-07-12 15:09:16.987 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace c:<project_name>. 2024-07-12 15:09:16.987 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace c:<project_name>. Creating and sending error discovery payload 2024-07-12 15:09:16.987 [error] pytest test discovery error for workspace: c:<project_name>
The python test process was terminated before it could exit on its own, the process errored with: Code: 1, Signal: null for workspace c:<project_name> `

I was able to fix this by upgrading pytest to the latest version. I suggest everyone who is encountering this do it too.

@anthonykim1, could you circle around on this as you have made fixes in this area? Thanks!

I have upgraded from pytest 8.3.2 to 8.3.3 but still have the same warning, which I believe is preventing Python/pytest to find packages in my data environment---see log below. This issue started yesterday, probably after an update (I don't recall if the update was yesterday or the day before).
2024-09-11 09:25:55.537 [warning] could not find a pixi interpreter for the interpreter at C:\Users\btrindad\AppData\Local\anaconda3\envs\data\python.exe
2024-09-11 09:25:55.570 [info] > python -m pytest -p vscode_pytest --collect-only tests
2024-09-11 09:25:55.570 [info] cwd: .
2024-09-11 09:25:57.457 [info] ============================= test session starts =============================
platform win32 -- Python 3.11.5, pytest-7.4.0, pluggy-1.0.0

2024-09-11 09:25:57.465 [info] rootdir: c:\Users\btrindad\Desktop\BUs\VWPA\harrisburg-hyd-model-calibration
plugins: anyio-3.5.0

2024-09-11 09:26:04.318 [info] collected 18 items / 2 errors

<Package tests>

2024-09-11 09:26:04.318 [info]   <Module test_calibration_plotter.py>
    <Function test_initialization>
    <Function test_process_model_tank_results>
    <Function test_process_model_flow_results>
    <Function test_process_model_results>
    <Function test_plot_calibration>
    <Function test_group_sum_flows>
    <Function test_calc_calib_error>
    <Function test_plot_calibration_deviations>
  <Module test_outlier_replacement.py>
    <Function test_with_valid_inputs>
    <Function test_with_no_outliers>
    <Function test_with_non_existent_columns>
    <Function test_with_specific_time_ranges>
    <Function test_with_invalid_time_ranges>
    <Function test_with_valid_dataframe>
    <Function test_with_empty_dataframe>
    <Function test_with_non_datetime_index>
    <Function test_with_different_quantile_and_multiplier>
    <Function test_with_missing_data>

2024-09-11 09:26:04.383 [error] pytest test discovery error for workspace:  c:\Users\btrindad\Desktop\BUs\VWPA\harrisburg-hyd-model-calibration
 _pytest.nodes.Collector.CollectError: ImportError while importing test module 'c:\Users\btrindad\Desktop\BUs\VWPA\harrisburg-hyd-model-calibration\tests\test_ccb_downscaler.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
..\..\..\..\AppData\Local\anaconda3\Lib\importlib\__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests\test_ccb_downscaler.py:4: in <module>
    from typeguard import TypeCheckError
E   ModuleNotFoundError: No module named 'typeguard'
 Check Python Test Logs for more details.

_pytest.nodes.Collector.CollectError: ImportError while importing test module 'c:\Users\btrindad\Desktop\BUs\VWPA\harrisburg-hyd-model-calibration\tests\test_water_distribution_tool.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
..\..\..\..\AppData\Local\anaconda3\Lib\importlib\__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
tests\test_water_distribution_tool.py:4: in <module>
    from shapely import Polygon
E   ModuleNotFoundError: No module named 'shapely'
 Check Python Test Logs for more details.

Interrupted: 2 errors during collection
 Check Python Test Logs for more details.

@bernardo-suez  Your errors do not appear to be related to this issue. I'm not attempting to defend Github or Microsoft (I'm pretty annoyed with them, TBH). However...
You appear to have problem with your PYTHONPATH and/or how you are attempting to import packages. This appears to be unrelated to the Pixi errors we're describing, here.

@eleanorjboyd can you please help us solving this issue?
After blocking automatic update and downgrading vscode and python extension - pytest works.
Are mine versions of vscode/python last working versions or we will be able to upgrade them again in the future?

You won't see the --version as error nor "2024-07-16 12:15:12.324 [error] Reading directory to watch failed [Error: ENOENT: no such file or directory, scandir '/home/path_to_the_project/.pixi/envs'". Try clearing the output and downloading the latest version of Python extension. Related: https://github.com//pull/23942

@anthonykim1 I can confirm that the issue is still present in vscode:
Version: 1.93.0 (user setup)
Commit: 4849ca9bdf9666755eb463db297b69e5385090e3
Date: 2024-09-04T13:02:38.431Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22631

And python extension v2024.14.1
$ pytest --version
pytest 8.3.3

From python output:
...
2024-09-14 15:28:56.260 [info] > ~/miniconda3/bin/conda run -n state_machine --no-capture-output python ~/.vscode-server/extensions/ms-python.python-2024.14.1-linux-x64/python_files/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2024.14.1-linux-x64/python_files/printEnvVariables.py
2024-09-14 15:28:56.260 [info] shell: bash
2024-09-14 15:28:57.879 [info] > pixi --version
2024-09-14 15:28:57.880 [warning] could not find a pixi interpreter for the interpreter at /home/zoran/miniconda3/envs/state_machine/bin/python
2024-09-14 15:28:57.886 [info] > python -m pytest -p vscode_pytest --collect-only tests
2024-09-14 15:28:57.886 [info] cwd: .
2024-09-14 15:28:57.914 [error] /home/zoran/miniconda3/bin/python: No module named pytest

2024-09-14 15:28:57.933 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /home/zoran/state_machine.
2024-09-14 15:28:57.933 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /home/zoran/state_machine. Creating and sending error discovery payload
2024-09-14 15:28:57.933 [error] pytest test discovery error for workspace:  /home/zoran/state_machine

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

If I run pytest directly from integrated terminal, everything works:
$ pytest --collect-only
================================================================================================================== test session starts ===================================================================================================================
platform linux -- Python 3.11.9, pytest-8.3.3, pluggy-1.5.0
rootdir: /home/zoran/state_machine
configfile: pyproject.toml
collected 1 item

<Dir state_machine>
  <Dir tests>
    <Module test_example.py>
      <Function test_bla>

=============================================================================================================== 1 test collected in 8.04s ================================================================================================================

After reloading window I can see that pytest is now not accessible from vscode:
2024-09-14 15:39:35.866 [info] shell: bash
2024-09-14 15:39:36.827 [info] > pixi --version
2024-09-14 15:39:36.828 [warning] could not find a pixi interpreter for the interpreter at /home/zoran/miniconda3/envs/state_machine/bin/python
2024-09-14 15:39:36.839 [info] > python -m pytest -p vscode_pytest --collect-only tests
2024-09-14 15:39:36.839 [info] cwd: .
2024-09-14 15:39:36.863 [error] /home/zoran/miniconda3/bin/python: No module named pytest

2024-09-14 15:39:36.876 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /home/zoran/state_machine.
2024-09-14 15:39:36.876 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /home/zoran/state_machine. Creating and sending error discovery payload
2024-09-14 15:39:36.876 [error] pytest test discovery error for workspace:  /home/zoran/state_machine

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

But I can access it from integrated terminal. I can confirm that proper interpreter is selected (from state_machine).
$ pytest --collect-only
================================================================================================================== test session starts ===================================================================================================================
platform linux -- Python 3.11.9, pytest-8.3.3, pluggy-1.5.0
rootdir: /home/zoran/state_machine
configfile: pyproject.toml
collected 2 items

<Dir state_machine>
  <Dir tests>
    <Module test_example.py>
      <Function test_bla>
      <Function test_bla2>

=============================================================================================================== 2 tests collected in 0.04s ===============================================================================================================
(state_machine) (base) zoran@WSL:~/state_machine main
$ pytest
================================================================================================================== test session starts ===================================================================================================================
platform linux -- Python 3.11.9, pytest-8.3.3, pluggy-1.5.0
rootdir: /home/zoran/state_machine
configfile: pyproject.toml
collected 2 items

tests/test_example.py ..                                                                                [100%]

=================================================================================================================== 2 passed in 8.38s ====================================================================================================================
(state_machine) (base) zoran@WSL:~/state_machine main

Probably we have multiple problems here, but problem exists.

Error still exists 17/Sep/2024

Error still exists 17/Sep/2024

They closed the issue?

Closed -- this is what I expect from Microsoft. I would have expected testing before releasing from Github... but, hey, Microsoft gonna Microsoft.

The irony in expecting testing in a testing functionality

And what now? To open a new issue and ask to reopen this one?
@eleanorjboyd can we avoid it?

You won't see the --version as error nor "2024-07-16 12:15:12.324 [error] Reading directory to watch failed [Error: ENOENT: no such file or directory, scandir '/home/path_to_the_project/.pixi/envs'". Try clearing the output and downloading the latest version of Python extension. Related: https://github.com//pull/23942

@anthonykim1 I can confirm that the issue is still present in vscode:
Version: 1.93.0 (user setup)
Commit: 4849ca9bdf9666755eb463db297b69e5385090e3
Date: 2024-09-04T13:02:38.431Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22631

And python extension v2024.14.1
$ pytest --version
pytest 8.3.3

From python output:
...
2024-09-14 15:28:56.260 [info] > ~/miniconda3/bin/conda run -n state_machine --no-capture-output python ~/.vscode-server/extensions/ms-python.python-2024.14.1-linux-x64/python_files/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2024.14.1-linux-x64/python_files/printEnvVariables.py
2024-09-14 15:28:56.260 [info] shell: bash
2024-09-14 15:28:57.879 [info] > pixi --version
2024-09-14 15:28:57.880 [warning] could not find a pixi interpreter for the interpreter at /home/zoran/miniconda3/envs/state_machine/bin/python
2024-09-14 15:28:57.886 [info] > python -m pytest -p vscode_pytest --collect-only tests
2024-09-14 15:28:57.886 [info] cwd: .
2024-09-14 15:28:57.914 [error] /home/zoran/miniconda3/bin/python: No module named pytest

2024-09-14 15:28:57.933 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /home/zoran/state_machine.
2024-09-14 15:28:57.933 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /home/zoran/state_machine. Creating and sending error discovery payload
2024-09-14 15:28:57.933 [error] pytest test discovery error for workspace:  /home/zoran/state_machine

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

If I run pytest directly from integrated terminal, everything works:
$ pytest --collect-only
================================================================================================================== test session starts ===================================================================================================================
platform linux -- Python 3.11.9, pytest-8.3.3, pluggy-1.5.0
rootdir: /home/zoran/state_machine
configfile: pyproject.toml
collected 1 item

<Dir state_machine>
  <Dir tests>
    <Module test_example.py>
      <Function test_bla>

=============================================================================================================== 1 test collected in 8.04s ================================================================================================================

After reloading window I can see that pytest is now not accessible from vscode:
2024-09-14 15:39:35.866 [info] shell: bash
2024-09-14 15:39:36.827 [info] > pixi --version
2024-09-14 15:39:36.828 [warning] could not find a pixi interpreter for the interpreter at /home/zoran/miniconda3/envs/state_machine/bin/python
2024-09-14 15:39:36.839 [info] > python -m pytest -p vscode_pytest --collect-only tests
2024-09-14 15:39:36.839 [info] cwd: .
2024-09-14 15:39:36.863 [error] /home/zoran/miniconda3/bin/python: No module named pytest

2024-09-14 15:39:36.876 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /home/zoran/state_machine.
2024-09-14 15:39:36.876 [error] Subprocess exited unsuccessfully with exit code 1 and signal null on workspace /home/zoran/state_machine. Creating and sending error discovery payload
2024-09-14 15:39:36.876 [error] pytest test discovery error for workspace:  /home/zoran/state_machine

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

But I can access it from integrated terminal. I can confirm that proper interpreter is selected (from state_machine).
$ pytest --collect-only
================================================================================================================== test session starts ===================================================================================================================
platform linux -- Python 3.11.9, pytest-8.3.3, pluggy-1.5.0
rootdir: /home/zoran/state_machine
configfile: pyproject.toml
collected 2 items

<Dir state_machine>
  <Dir tests>
    <Module test_example.py>
      <Function test_bla>
      <Function test_bla2>

=============================================================================================================== 2 tests collected in 0.04s ===============================================================================================================
(state_machine) (base) zoran@WSL:~/state_machine main
$ pytest
================================================================================================================== test session starts ===================================================================================================================
platform linux -- Python 3.11.9, pytest-8.3.3, pluggy-1.5.0
rootdir: /home/zoran/state_machine
configfile: pyproject.toml
collected 2 items

tests/test_example.py ..                                                                                [100%]

=================================================================================================================== 2 passed in 8.38s ====================================================================================================================
(state_machine) (base) zoran@WSL:~/state_machine main

Probably we have multiple problems here, but problem exists.
Hint: It is enough to downgrade python extension to v2024.9.1 and everything works.

v2024.9.1 did not work for me either.  Other version info from VSCode
Version: 1.93.1 (user setup)
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22631

Probably we have multiple problems here, but problem exists.

@zljubisic You are probably right. It seems like mix of couple problems and confusions. Let's try to solve this puzzle one by one - that being said  I'm putting up a PR to change log level on this pixi warning to see and hoping it will clear up things. https://github.com/microsoft/vscode-python/pull/24164/files this way pixi warnings won't be screaming at you even when you are irrelevant (you don't have pixi nor do not intend to use one)
Can't connect the dots between how pixi warning is related to pytest at the moment.
@clement-chaneching If you are still suffering from your pixi environment not being discovered, you can file a separate issue. Give https://github.com/microsoft/vscode-python/issues/23975#issuecomment-2306443372 a read for your pixi specific related problems though.
@toddsayersshell FYI It is not Microsoft who closed this issue.
Thanks

@anthonykim1 thanks for your reply. PR you have mentioned will help us not to see pixi warning, but problem with pytest discovery within vscode remains. Which issue will track that?
If the issue is this one, we could ask @adam-lagoda to reopen it (if possible).

Downgrading the Python Extension initially has worked for me. Right now I am running v2024.14.1 and VSCode 1.93.1 without issues

this issue seems related with the incorrect environment being selected for python when testing: https://github.com/microsoft/vscode-python/issues/24122

Thoughts on pycharm?

I have a colleague that uses Pycharm. It's quite a bit more robust. It's... arguably better than VScode. HOWEVER... when you consider that VScode is a glorified web page (Electron app)... it's more impressive than anything I'll ever build. Moreover, Pycharm is not free. VScode IS "free." I suspect that I simply don't understand the cost (surely they're getting something from us... or will).
Now, I detest Microsoft. I ditched Windows in the 90s... and my life has been so much better. That said... VScode is one of the best things they've built (granted, using OSS componentry). It's truly cross-platform. And if you use it atop a real OS (e.g., Linux)... well, it's a solid experience across Linux/Windoze/Mac. I had bad luck using WSL2 (possibly due to corporate updates/etc)... but I've been happy running it against a Docker installation running in a VirtualBox/Ubuntu VM.
I don't believe that you're making a fair comparison. If you don't mind paying for Pycharm... from what I've seen, it IS better than VScode. Alas... VScode is generally "good enough" for me.  I believe that their corporate culture/etc is lacking. They KEEP reintroducing problems. But, well, it's free. I'm admittedly unjustifiably grumpy about their failings/bugs -- mostly because they seem to hit at the worst time.
If you need a solid product that cannot fail (and that has commercial support for when it does)... well, you might want to pay for that. Complaining is free, you know...

For what it's worth,  on my Linux container on a Chromebook, Pycharm
started slowing down very significantly as my Python project grew in size.
I ended up switching to VSCode and all my IDE-specific memory/performance
problems went away overnight.
I was using the Community version of Pycharm.
Thanks & regards
Ashok Natesan
Cell:<PHONE_NUMBER>
Streamlinity LLC
https://www.streamlinity.com
On Thu, Sep 26, 2024 at 11:42 AM Old Man @.***> wrote:

Pycharm is not free.
The community version is
I don't believe that you're making a fair comparison.
I didn't compare anything. I just asked for thoughts. Thanks for sharing
yours. Are there any other good alternatives?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-python/issues/23773#issuecomment-2377675708,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ5KD2E7P3D3Y45HAJI6ZCDZYRIRPAVCNFSM6AAAAABKSVHEEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXGY3TKNZQHA
.
You are receiving this because you commented.Message ID:
@.***>

We are actively investigating this. The short answer is, we are not able to isolate the issue. If we can't isolate it, we may have to revert pixi support. We want to avoid reverting pixi support which is a community contributed feature.
If you are running into this, and it is blocking, pin the extension to a previous version.
I will be marking anything that does not directly help us address this issue as off topic. I understand the frustration, we are investigating this. Off-topic comments are not helpful to get us to resolving this issue.

@karthiknadig If you want to isolate issue, create a new python project, install pytest, write a test and try to debug it. You will see that test is not found. Maybe it will brake after some number of tests, so you have to write more than one test.
While vscode is braking, executing pytest from the shell works as expected.

@zljubisic I have tried to repro this on few repos with 70k tests. Unfortunately, I can't repro it. the hypothesis is that it seems to be related some state of the environment that makes pixi categorize it as non conda.
I have a build here where we prioritize the conda category over pixi. If this works then it means that the issue is with forming the activation commands that pixi takes over when. If this does not bypass it then we need to look further.
Try pre-release version ms-python.python.2024.15.2024092702, it requires latest VS Code insiders.

@zljubisic I have tried to repro this on few repos with 70k tests. Unfortunately, I can't repro it. the hypothesis is that it seems to be related some state of the environment that makes pixi categorize it as non conda.
I have a build here where we prioritize the conda category over pixi. If this works then it means that the issue is with forming the activation commands that pixi takes over when. If this does not bypass it then we need to look further.
Try pre-release version ms-python.python.2024.15.2024092702, it requires latest VS Code insiders.

My code has no conda, has no pixi. Just main.py and tests/test_code.py

@thethiny Did you try with the ms-python.python.2024.15.2024092702 build to see what happens?

@karthiknadig I just happened to experience this issue today. I switched to the latest prerelease version (it says v2024.17.2024100102) and now the tests are working again.

@thethiny Did you try with the ms-python.python.2024.15.2024092702 build to see what happens?

I updated to the latest release and it didn't work. Then I switched python to pre-release and they're working fine.

@zljubisic I have tried to repro this on few repos with 70k tests. Unfortunately, I can't repro it. the hypothesis is that it seems to be related some state of the environment that makes pixi categorize it as non conda.
I have a build here where we prioritize the conda category over pixi. If this works then it means that the issue is with forming the activation commands that pixi takes over when. If this does not bypass it then we need to look further.
Try pre-release version ms-python.python.2024.15.2024092702, it requires latest VS Code insiders.

@karthiknadig thank you for paying attention to this issue.
Unfortunately, I can't update to VS Code insiders and also I wouldn't be happy with pre-lease version of the python extension.
I am creating virtual environments using (mini)conda. I don't know if this helps.

@thethiny ms-python.python.2024.15.2024092702 mentioned would be the pre-release version, so I think you are getting the expected result.
Looks like https://github.com/microsoft/vscode-python/pull/24198 helped re-prioritize conda over pixi. So people should really give a try on the latest PRE-release of the Python extension.

I am using Poetry to manage my dependencies.   I don't use either pixi or
conda (at least I am not consciously using either at my end).
Should the latest pre-release solve the problem in this configuration
Thanks & regards
Ashok Natesan
Cell:<PHONE_NUMBER>
Streamlinity LLC
https://www.streamlinity.com
On Wed, Oct 2, 2024 at 8:46 AM Anthony Kim @.***> wrote:

@thethiny https://github.com/thethiny
ms-python.python.2024.15.2024092702 mentioned would be the pre-release
version, so I think you are getting the expected result.
Looks like #24198 https://github.com/microsoft/vscode-python/pull/24198
helped re-prioritize conda over pixi. So people should really give a try on
the latest PRE-release of the Python extension.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-python/issues/23773#issuecomment-2389014411,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ5KD2CB4NYQIXGZIOOJ3N3ZZQINFAVCNFSM6AAAAABKSVHEEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBZGAYTINBRGE
.
You are receiving this because you commented.Message ID:
@.***>


Refactor Graphite dependency management

Use workspace dependencies throughout the projects to minimize the number of different versions of crates used in the project

cargo check:
error: failed to load manifest for workspace member `C:\Users\Keavon\Projects\Graphite\editor`

Caused by:
  failed to load manifest for dependency `graphite-document-legacy`

Caused by:
  failed to load manifest for dependency `graphene-std`

Caused by:
  failed to load manifest for dependency `compilation-client`

Caused by:
  failed to load manifest for dependency `future-executor`

Caused by:
  failed to read `C:\Users\Keavon\Projects\Graphite\node-graph\future-executor\Cargo.toml`

Caused by:
  The system cannot find the path specified. (os error 3)


DCGM on GKE partially up and and running

I've installed DCGM via helm on my GKE cluster, and there are always several pods not running as expected.

the values are referenced from #59 , and I bumped the memory to 256Mi so the OOM issue is gone. But other than that, there's no useful info I could ever get from the failed pods. All the pods are showing the log as:
`
time="2023-10-30T17:03:32Z" level=info msg="Starting dcgm-exporter"
time="2023-10-30T17:03:34Z" level=info msg="DCGM successfully initialized!"
time="2023-10-30T17:03:42Z" level=info msg="Collecting DCP Metrics"
time="2023-10-30T17:03:42Z" level=info msg="No configmap data specified, falling back to metric file /etc/dcgm-exporter/dcp-metrics-included.csv"
time="2023-10-30T17:03:42Z" level=info msg="Initializing system entities of type: GPU"
time="2023-10-30T17:03:58Z" level=info msg="Initializing system entities of type: NvSwitch"
time="2023-10-30T17:03:58Z" level=info msg="Not collecting switch metrics: no switches to monitor"
time="2023-10-30T17:03:58Z" level=info msg="Initializing system entities of type: NvLink"
time="2023-10-30T17:03:58Z" level=info msg="Not collecting link metrics: no switches to monitor"
time="2023-10-30T17:03:58Z" level=info msg="Kubernetes metrics collection enabled!"
time="2023-10-30T17:03:58Z" level=info msg="Starting webserver"
time="2023-10-30T17:03:58Z" level=info msg="Pipeline starting"
`
I've checked all the nodes have allocatable GPU resources, and both the successful and failed nodes are configured identical.
to dig deep into the container, the pod description shows:
`
Containers:
exporter:
Container ID:  containerd://0c7df098ffaf4f54f3addba8465acb76903fd2034c3b48b304fe1e44d77252e5
Image:         nvcr.io/nvidia/k8s/dcgm-exporter:3.2.5-3.1.7-ubuntu20.04
Image ID:      nvcr.io/nvidia/k8s/dcgm-exporter@sha256:53fc1319303b36184c168107987693aeaca364a1a9ef5e3845191d8d745e51f0
Port:          9400/TCP
Host Port:     0/TCP
Args:
-f
/etc/dcgm-exporter/dcp-metrics-included.csv
State:          Waiting
Reason:       CrashLoopBackOff
Last State:     Terminated
Reason:       Completed
Exit Code:    0
Started:      Mon, 30 Oct 2023 10:24:06 -0700
Finished:     Mon, 30 Oct 2023 10:25:03 -0700
Ready:          False
Restart Count:  7
Limits:
cpu:     100m
memory:  256Mi
Requests:
cpu:      100m
memory:   256Mi
Liveness:   http-get http://:9400/health delay=45s timeout=1s period=5s #success=1 #failure=3
Readiness:  http-get http://:9400/health delay=45s timeout=1s period=10s #success=1 #failure=3
`
it seems the container just executed normally, and gets terminated, but it is supposed to be running continuously in a server manner.
any guidance would be greatly appreciated!

the tricky issue i can find from the pod description is the container last status to be:
Last State:     Terminated
Reason:       Completed
Exit Code:    0
it seems the exporter container simply gets executed and quit successfully, not running continuously.


Issue 1

@bmoussaud, could you please close this Issue? Thanks a lot for your hard work. :-)

closzed


ShouldDispatchAfterCommit does not work after child transactions are committed

Laravel Version
10.32.1
PHP Version
8.2
Description
When a child transaction is committed inside of a parent transaction, any events with the ShouldDispatchAfterCommit interface that are dispatched after the child transaction has committed, but before the parent transaction is committed, will be dispatched immediately.
The problem is related to that the dispatcher adds the event listeners using DatabaseTransactionManager@addCallback, and that this method only adds the callback if it has any pendingTransactions - which are flushed whenever a transaction is committed.
Steps To Reproduce
I wrote a failing test case in ShouldDispatchAfterCommitEventTest.php that illustrates the problem:
public function testItOnlyDispatchesEventsAfterTheRootTransactionIsCommitted()
{
    Event::listen(ShouldDispatchAfterCommitTestEvent::class, ShouldDispatchAfterCommitListener::class);

    DB::transaction(function () {
        // Begin and commit a child transaction. This line causes the test to fail.
        DB::transaction(function () {});

        Event::dispatch(new ShouldDispatchAfterCommitTestEvent);

        $this->assertFalse(ShouldDispatchAfterCommitTestEvent::$ran);
    });

    $this->assertTrue(ShouldDispatchAfterCommitTestEvent::$ran);
}

@hansnn do you have the failing test case in a repo? Or the body of those two classes at the very least?

@cosmastech The test can be copy-pasted as-is into the tests/Integration/Events/ShouldDispatchAfterCommitEventTest.php file of this repository.
I should've made that more clear in the description. I guess I assumed familiarity with the PR where this feature, and the test, were added.


Please rename this lib: Routex already in use

Dear maintainer(s),
We share our love for routes in Elixir, and our love for Routex! Unfortunately, we both have another Routex in mind. I am talking about https://hex.pm/packages/routex
Could you be so kind to rename this lib/repo?
Regards,
Bart Otten, author of 'different Routex'

I understand your concern, but this project was created before the other Routex. It's also an internal project open to others if needed.


Kubernetes -- tiller-deploy is failing to run

Describe your issue here
I see the following messgaes in the kubernetes dashboard --
Failed to pull image "gcr.io/kubernetes-helm/tiller:v2.1.3": Error response from daemon: {"message":"target is unknown"}
Error syncing pod, skipping: failed to "StartContainer" for "tiller" with ErrImagePull: "Error response from daemon: {"message":"target is unknown"}"

Useful
Info

Versions
Rancher v1.3.3 Cattle: v0.175.9 UI: v1.3.5

Access
localauth admin

Orchestration
Kubernetes

Route
k8s-tab.dashboard

I am seeing this as well on our setup.

May be duplicate of https://github.com/rancher/rancher/issues/7303

@karnatip What version of Docker are you running?  Looks like it may be a bug in docker that has been resolved in 1.13.1 rc1.  See https://github.com/kubernetes/helm/issues/1838#issuecomment-277021528

This shoudl work out of the box now. Feel free to try it on a modern version of rancher (using docker 1.12.6 ideally).


build error: Command in array or slice literal

I try to build gogs from the src on Voidlinux and since 0.11.29 we get:

=> gogs-0.11.29_1: running do_build ...
# _/builddir/gogs-0.11.29
./gogs.go:31: cannot use cmd.Web (type "github.com/gogits/gogs/vendor/github.com/urfave/cli".Command) as type "github.com/urfave/cli".Command in array or slice literal
./gogs.go:32: cannot use cmd.Serv (type "github.com/gogits/gogs/vendor/github.com/urfave/cli".Command) as type "github.com/urfave/cli".Command in array or slice literal
./gogs.go:33: cannot use cmd.Hook (type "github.com/gogits/gogs/vendor/github.com/urfave/cli".Command) as type "github.com/urfave/cli".Command in array or slice literal
./gogs.go:34: cannot use cmd.Cert (type "github.com/gogits/gogs/vendor/github.com/urfave/cli".Command) as type "github.com/urfave/cli".Command in array or slice literal
./gogs.go:35: cannot use cmd.Admin (type "github.com/gogits/gogs/vendor/github.com/urfave/cli".Command) as type "github.com/urfave/cli".Command in array or slice literal
./gogs.go:36: cannot use cmd.Import (type "github.com/gogits/gogs/vendor/github.com/urfave/cli".Command) as type "github.com/urfave/cli".Command in array or slice literal
./gogs.go:37: cannot use cmd.Backup (type "github.com/gogits/gogs/vendor/github.com/urfave/cli".Command) as type "github.com/urfave/cli".Command in array or slice literal
./gogs.go:38: cannot use cmd.Restore (type "github.com/gogits/gogs/vendor/github.com/urfave/cli".Command) as type "github.com/urfave/cli".Command in array or slice literal

I get the same error on gogs-0.11.34.
The package is build via xbps used this template: https://github.com/voidlinux/void-packages/blob/master/srcpkgs/gogs/template
What is the best way to fix this?

Thanks to https://gitter.im/gogits/gogs?at=59d58ff7bac826f054379ecb
Erik Williamson @ertw Oct 04 18:50
"Nevermind, this was a GOPATH issue on my side."
The fix is to make sure GOPATH is set to a path where the go pre-reqs and gogs source will live.
export GOPATH="$HOME/go"

# Download and install dependencies
$ go get -u github.com/gogits/gogs

# Build main program
$ cd $GOPATH/src/github.com/gogits/gogs
$ go build -tags "sqlite cert"

References: https://gogs.io/docs/installation/install_from_source


Implement hare 3.0

i think we should use hare 2 instead of hare 3 for the sake of the implementation versioning. hare 2 didn't really came out of the private research discussions

Ok, so we'll call it hare 2.0 in the code, but we'll use what we are currently referring to as the hare 3.0 spec.

So it was decided that it would be easier if we just refer to this as hare 3.0 and have a gap in the versioning, so from now on both the conceptual design and the implementation will be referred to as hare3 or hare 3.0


TorchBench Integration Part 1

Add support for Dynamo compile
Prototype of RFC #2059

Implemented + Raised TorchBench PR: https://github.com/pytorch/benchmark/pull/1753

Prototype Part 1 Complete


Cleanup, reorganize structure, refactoring ThrowableRendererInterface

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
✔

Fixed issues
-

👍


Setup build environment with Make.

Ignore the last commit typo, it's late..

Looks like that was included by mistake. Will remove.

Another thing, the binary is quite large for it's relatively small codebase. Can anything be done to optimize that or is that not a priority right now?

Another thing, the binary is quite large for it's relatively small codebase. Can anything be done to optimize it or is that not a priority right now?

It's something that has to do with the web development library gin, it's not something we can tackle at this stage but I don't see the file size growing any exponentially larger in the future


Next/Previous Sibling performs very slowly

The functions to go to the next or previous Sibling (shift+j and shift+k) are very useful to move around quickly, but they are very slow. So I tend to just press multiple times j to go down, which is not ideal.
I know it may be a technical limitation because it's not a native function of logseq, but it would be great if it could run faster.
Maybe it is better to ask the logseq team to implement such a function?

Yes, you are right, I can just give the suggestion to Logseq Team for now.


refactor(authorization): further split fields

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update
[x] Refactor
[ ] Build-related changes
[ ] Other (please describe)

Does this PR introduce a breaking change?

[ ] Yes
[x] No

The PR fulfills these requirements:

[x] It's submitted to the main branch
[x] When resolving a specific issue, it's referenced in the PR's description  (e.g. fix #xxx, where "xxx" is the issue number)

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature

Other information:

@ChrisPdgn @kon14 the "ignore" solution should be further refined. SQL DBs support ASC/DESC indexes and we should create a new type of index, that will encompass these indexes that are available in both DB technologies. In general though, we should also either introduce 2 fields for index, one for each db type, or keep the ignore functionality


Remove CC physical (Mountain View, CA) address from CC FaceBook account

https://www.facebook.com/creativecommons/info?tab=page_info

@cablegreen @mattl I don't think we should remove it. We have the PO Box listed, which is correct in case we need to get any mail, etc.

OK. Good point.
Cable

On Mar 18, 2015, at 11:58 AM, Timothy Vollmer<EMAIL_ADDRESS>wrote:
@cablegreen @mattl I don't think we should remove it. We have the PO Box listed, which is correct in case we need to get any mail, etc.
—
Reply to this email directly or view it on GitHub.


config file doesnt load in

Commands tried and error. Path is correct and config and server settinsg file are in that folder. Same issue faced even if command prompt is used.

Dammit. The documentation points to the wrong image, that's why you're having problems running it. The image should be alexandreteles/jmusicbot instead of jagrosh/jmusicbot as jagrosh himself doesn't provide a docker image even if we insist on having an official one. Anyway, your problem should be solved if you run:
docker run --name jmusicbot -d -v /home/rawr/.docker/desktop/config.txt:/app/config.txt:ro -v /home/rawr/.docker/desktop/serversettings.json:/app/serversettings.json:ro --restart=always alexandreteles/jmusicbot

I'm closing this issue just so I can keep track of what I'm doing but feel free to reopen it if needed.


Finalize all open file descriptors

Hi,
I've been carrying some patches I haven't had time to clean up and offer upstream, and I need to do something about that. This one is easy and non-invasive, just a trivial patch to allow a program to close the /dev/urandom file descriptor. The reason for this is that valgrind detects the open resource and thinks it's a leak even though it obviously isn't, and I like to keep the output of my test tools very clean so that any new problems jump out at me--otherwise I might miss them among the "expected failures."

I'll merge this although I think that leaving file descriptors open is perfectly fine. (Kernel will close them once process is cleaned up IIRC).

On 01/23/2015 10:11 AM, Pavol Rusnak wrote:

I'll merge this although I think that leaving file descriptors open is
perfectly fine. (Kernel will close them once process is cleaned up IIRC).

Thanks.
You're right in that it's absolutely fine. The problem is that test
tools can't tell whether it was left unclosed by accident or on purpose,
and I like to reassure their little minds so I don't inadvertently
ignore a real bug.
Same thing with freeing memory on exit--there's no requirement to do so
as it's more efficient to let the kernel reclaim everything at once, but
if you don't free everything explicitly, at least in debug builds, you
don't actually know whether you're tracking every allocated chunk or not.
Dustin


Columns that are added/changed/removed by a TableTransformer

Is your feature request related to a problem?
It would be useful to know which columns get added, changed, or removed by a TableTransformer.
Desired solution
The TableTransformer abstract base class should get three new abstract methods:

get_names_of_added_columns
get_names_of_changed_columns
get_names_of_removed_columns

Each of them should return a list of strings in correct order. All subclasses of TableTransformer must implement these methods. The docstrings of the subclasses should also describe how columns are affected by the transformer.
Possible alternatives (optional)
No response
Screenshots (optional)
No response
Additional Context (optional)
No response

It is unclear which table the methods should refer to.
E.g., should get_names_of_changed_columns, applied on an Imputer instance, return a list of those column names that have been changed in the last table the Imputer has been used to transform? (That would mean we store data that logically belongs to a Table globally in the Transformer class.)
Or should it return all the column names that can in principle be affected, i.e. all names that had been passed to fit?

Or should it return all the column names that can in principle be affected, i.e. all names that had been passed to fit?

This.

:tada: This issue has been resolved in version 0.13.0 :tada:
The release is available on:

v0.13.0
GitHub release

Your semantic-release bot :package::rocket:


Tracer configuration using options

Modeled after hertz-contrib/monitor-prometheus.
Allow users to configure the prometheus registry used by tracer themselves

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

license header需要加下


Only works in incognito mode

Once I've loaded up one of the three calculators, I will forever be stuck being re-directed to that calculator. Wiping cookies, switching browsers, switching computers, opening a browser in incognito mode fixes the problem for a hot second. Changing my settings to disallow FactorioLab to store anything in cookies breaks the site entirely. So I'm stuck using workarounds.

@Trequetrum If you are able to discuss in the FactorioLab Discord server that might be helpful.

Have you tried using the "Game" dropdown in the Settings menu?

I am assuming you mainly mean that the links at the top of the page do not work to redirect you to the other game calculators?

Are you using Chrome? Mobile or desktop?

If on desktop, could you open the browser developer console and check if there are any errors there? (Right click, "Inspect", and check for anything in the Console)

I ask because I am not able to duplicate this issue in Firefox or Chrome. I admit I have occasionally seen it get stuck in one game and the links at the top do not work, but it always works after refreshing the page, so I'm not sure what is unique about your issue.

Hey,

I hadn't tried that, that seems to work and solves my problem. Though I'm a bit surprised that the settings menu and the links at the top of the page aren't handled the same way! Does one reload the page and the other routes SPA-style?
Exactly, yes.
I'm using Firefox with GalliumOS (desktop).
The console does say: Loading failed for the

The links at the top are actual links, anchor or  tags, that route to the different game calculators. I'm also interested if you ctrl+click one of those links to open it in a new tab, does that work or no?
The dropdown in the Settings menu actually changes the game internally without reloading everything (hence a bit more reliable).
It seems that the application is not detecting the URL change when you click on the link. I'm curious, what does the address bar show when you click on the links, does it change or not?
That message in the console is not relevant to this issue.
Previously those links worked a bit differently, they would set the URL, wait 100 - 250 ms, and then force the page to reload. I think that method might be more reliable and I might have to switch back to it to make it work in your case. I'll set that up in the staging environment at some point and you can tell me whether the links work there. (Not sure when that will be with the Thanksgiving holiday coming up though)

I can restart my computer, but if I haven't cleared my cookies, the issue persists. Opening in a new tab doesn't make a difference. Copy and pasting the URL for a different calculator doesn't make a difference either. It just returns me to the last recipe I had open on the last calculator that I used, it even changes the URL.
Right now, for example, if I write in any valid address, I get redirected to https://factoriolab.github.io/list?p=supercomputer*60&s=dsp&v=1
If, however, I navigate to https://factoriolab.github.io/list?p=error, then I get an error message "The application has encountered an error: TypeError: t is undefined" and then the links at the top will work again. Until I've loaded a recipe in any of the 3 calculators.
No errors in the dev console throughout.

@Trequetrum I know it's been a minute, but if you have a chance, could you please try this out at https://factoriolab.github.io/staging. If you can open the developer tools and check the console, it should log some information about the location that would be helpful in debugging this. Specifically what I would like you to try is to navigate to:
https://factoriolab.github.io/staging/list?p=wooden-chest*1&v=1 (Factorio Calculator)
Then, navigate to:
https://factoriolab.github.io/staging/list?p=iron-ore*1&s=dsp&v=1 (DSP Calculator)
On the second navigation, open the console and let me know what is logged. I am not able to reproduce this problem so this may be a bit tough to fix. The application is supposed to check whether you have a state in the URL before loading any saved state from local storage. My only guess is on your system that check fails for some reason, and the application thinks you don't have any state in the URL when you actually do. I've added a lot of debug statements in that area to see if I can determine why that check fails.

Hey @dcbroad3, I'm not seeing this bug anymore. I've tried to re-create the exact conditions that caused it before, though I can't be sure. I'd originality navigated via a bookmark, though I've since deleted that bookmark.

Thanks for the update. Do you mean you're not seeing the bug even at https://factoriolab.github.io, or not seeing the bug just at the staging website I pointed to?

@Trequetrum can you confirm, you don't see this issue at all any more? Should this issue be closed?

I'm not seeing it at either address. This issue should be closed (I'll re-open if it happens again and can be consistently reproduced).
Thanks for your time/effort!

Thanks for following up!


problem to get data from firestore. generate an error

QuestionModel  getQuestionModelFromDatasnapshot(
DocumentSnapshot questionSnapshot) {
QuestionModel questionModel = new QuestionModel();
questionModel.question = questionSnapshot.data**['question'];**

/// shuffling the options
List<String> options = [
  questionSnapshot.data**['option1'],**
  questionSnapshot.data**['option2'],**
  questionSnapshot.data**['option3'],**
  questionSnapshot.data**['option4'],**
];
options.shuffle();

questionModel.option1 = options[0];
questionModel.option2 = options[1];
questionModel.option3 = options[2];
questionModel.option4 = options[3];
questionModel.correctOption = questionSnapshot.data**['correctoption'];**
questionModel.answered = false;

print(questionModel.correctOption.toLowerCase());

return questionModel;

}
Error Generate:
Closure call with mismatched arguments: function '[]'
Receiver: Closure: () => Map<String, dynamic> from Function 'data':.
Tried calling:
Found:  => Map<String, dynamic>

Hi @muneeb900
Can you provide more details and Logs:

flutter doctor -v

flutter run -v

minimal complete reproducible code sample

Added wait label for what @hamdikahloun asked
Cc myself

problem solved

hi @muneeb900
how?

Error Generate:
Closure call with mismatched arguments: function '[]'
Receiver: Closure: () => Map<String, dynamic> from Function 'data':.
Tried calling:
Found: => Map<String, dynamic>

Can you please tell me how you solved this?

problem solved

I'm getting the same error.
Can you please share your solution?

Use get() isntrad of just get
On Wed, Dec 30, 2020, 2:26 PM reema-pandya<EMAIL_ADDRESS>wrote:

problem solved
I'm getting the same error.
Can you please share your solution?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/64624#issuecomment-752376181,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR3NS2PJINGDNRF65DGVX2TSXLRTJANCNFSM4QLRXXTA
.

Please share the solution in details. @Testapp

If you are using get to get some value use get() instead of get to retrieve
that value
On Wed, May 19, 2021, 10:37 AM Santosh Chapagain @.***>
wrote:

Please share the solution in details. @TestApp
https://github.com/TestApp
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/64624#issuecomment-843744278,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR3NS2OOVCYJCOMXL3NXV53TOM7XFANCNFSM4QLRXXTA
.


Granularize error/pre/post-condition checking machenisim

For now, there's three ways to check if an error (or function pre/post condition violation) occurs.

if(some condition) { throw EtError("bla, bla, bla..."); }
et_assert(some condition)
checkProperties(tensor, )

Which is kinda not enough. if(...) throw; is okay for simple conditions but doesn't generate a stack trace even if we want to. et_assert just abort the entire program (including cling if using PyEtaler or ROOT) leading to a bad interactive experience. And checkProperties only works for tensors.
So I purpose the following:

We reserve if..... throw; for simple cases
checkProperties is still used for tensor checking
et_assert is for absolutely worst, non-recoverable errors like OOM or internal state mess-ups
a new et_check is used for ordinary condition checking. If the check fails, it throws an EtError and optionally generates a stack trace.
We need a way to generate stack traces pragmatically. It also would be nice to be able to detect the present of cling and use cling for traces when available.

Even tho the C++ standard committee is against using exceptions for programming errors (dtype/shape/backend mismatch is our cases). We consider these user errors - the developers are our users and exceptions gives us a better experiences under an interactive environment. However depending on how contracts are implemented in C++23, it might be a good idea to replace some of the checks with it in the future.
Related to #93

Fixed by #140


64-bit OpenSSL doesn't work with the cmake script

The CMakeLists.txt needs to know how to select the correct lib for both 32 and 64 bit arch.

Windows, Linux or OS X?

Like all cmake packages, hint variables can be set to help cmake find the correct library if not installed in a standard place for the build host.
###Hints:
Set OPENSSL_ROOT_DIR to the root directory of an OpenSSL installation.
Set OPENSSL_USE_STATIC_LIBS to TRUE to look for static libraries.
Set OPENSSL_MSVC_STATIC_RT set TRUE to choose the MT version of the lib.
Ref: https://cmake.org/cmake/help/latest/module/FindOpenSSL.html
Are you able to supply some "steps to reproduce"? i.e. which libraries installed/built where in the file system?

Windows. I build a Visual Studio solution and then build that. Stock OpenSSL Windows installer (both 32 and 64 bit installed).

Using vcpkg to install 32 and 64 bit OpenSSL, and then using the vcpkg toolchain file, fixes this.


added index.py

Issue: #3
created folders and added index.py file
here is the screenshot link
https://drive.google.com/file/d/1UWSht-KRojvMcMtmgcwc1Rgu34Mjwm4F/view?usp=sharing

Hey @sankalpj47
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

Hey @sankalpj47
Your PR has been merged 🥳🥳 and you have earned 10 points.
Thanks for contributing in OpenCode'24 ✨✨


Merge python_version and python_full_version markers

Relates-to: python-poetry/poetry#5717

[x] Added tests for changed code.
[ ] Updated documentation for changed code.

Reintroduces merging of python_version and python_full_version, which was removed in #382 because of python-poetry/poetry#5717
The constraint of the python_marker is converted via get_python_constraint_from_marker() and thus should be consistent with the latest findings described in #385.

I think this looks correct, I'll leave a couple of style quibbles.
I continue to have a slight feeling of unease that this code has become so elaborate: I like a marker simplification as much as the next person, but there's so much of it!

I don't necessarily disagree, but I think ultimately we get higher quality results if we try to make sure the markers are as consistent and clean as possible. I think our best tool for maintainability is robust and through testing, and incremental refactoring as better patterns make themselves apparent. That being said, yes there's getting to be a lot of it and if I don't pay attention for a few weeks I forget how it works again 😆

I continue to have a slight feeling of unease that this code has become so elaborate: I like a marker simplification as much as the next person, but there's so much of it!

It's just necessary for the solver to not try solving some bogus overrides. Solving not just for one environment is complex, but that's one of poetry's USPs.


Revert clear response operation of timeoutfilter

Signed-off-by: crazyhzm<EMAIL_ADDRESS>What is the purpose of the change
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #11562 (b318e7a) into 3.1 (1ab11d3) will increase coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                3.1   #11562      +/-   ##
============================================
+ Coverage     64.64%   64.66%   +0.01%
  Complexity       14       14
============================================
  Files          1431     1431
  Lines         59975    59974       -1
  Branches       8808     8808
============================================
+ Hits          38770    38780      +10
+ Misses        17133    17117      -16
- Partials       4072     4077       +5

Impacted Files
Coverage Δ

...ava/org/apache/dubbo/rpc/filter/TimeoutFilter.java
41.66% <ø> (+3.20%)
:arrow_up:

...gistrycenter/processor/ZookeeperUnixProcessor.java
60.71% <0.00%> (-17.86%)
:arrow_down:

...g/apache/dubbo/remoting/api/ConnectionHandler.java
51.51% <0.00%> (-9.10%)
:arrow_down:

...bbo/rpc/cluster/support/ForkingClusterInvoker.java
83.33% <0.00%> (-4.77%)
:arrow_down:

.../apache/dubbo/remoting/transport/AbstractPeer.java
67.39% <0.00%> (-4.35%)
:arrow_down:

...ache/dubbo/common/extension/ExtensionDirector.java
93.33% <0.00%> (-3.34%)
:arrow_down:

.../src/main/java/org/apache/dubbo/rpc/RpcStatus.java
80.95% <0.00%> (-1.20%)
:arrow_down:

.../dubbo/remoting/transport/netty4/NettyChannel.java
72.64% <0.00%> (-0.95%)
:arrow_down:

...apache/dubbo/common/extension/ExtensionLoader.java
79.32% <0.00%> (-0.16%)
:arrow_down:

...e/dubbo/remoting/transport/netty/NettyChannel.java
52.27% <0.00%> (+1.13%)
:arrow_up:

... and 9 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more