Incorrect start/end times for 'emsg' event.

The entries in the emsg v1 box are in media time units.
However the 'emsg' event is supposed to have the start/end times in presentation time units.
The current code works when timestamps start at 0 but fails when timestamps start at non-zero timestamps.

oops. accidentally closed.

Please take a look at these test failures, and leave a comment when you've addressed them.  If you need help, let us know that, too, and we'll be happy to help.  Thanks!

Sorry my bad looks like I missed integration tests.  Fixed that.

Thank you!


Build error: Unknown type name 'uintptr_t'

I'm attempting to build the project using GCC with these parameters:
make VERSION=us TARGET_N64=0 COMPILER=gcc

I have installed all the dependencies on my machine running Debian Buster, but I received the following error:
In file included from include/ultra64.h:4,
                 from src/engine/surface_collision.c:1:
/usr/include/math.h:27:10: fatal error: bits/libc-header-start.h: No such file or directory
   27 | #include <bits/libc-header-start.h>
      |

I was able to resolve this error by installing the gcc-multilib and g++-multilib packages. However, this causes another build error:
In file included from include/ultra64.h:12,
                 from src/engine/surface_collision.c:1:
include/PR/os_misc.h:9:1: error: unknown type name 'uintptr_t'
    9 | uintptr_t osVirtualToPhysical(void *);
      | ^~~~~~~~~
In file included from include/ultra64.h:23,
                 from src/engine/surface_collision.c:1:
include/PR/os_pi.h:24:5: error: unknown type name 'uintptr_t'
   24 |     uintptr_t devAddr; // c
      |     ^~~~~~~~~
include/PR/os_pi.h:48:5: error: unknown type name 'uintptr_t'
   48 |     uintptr_t address;
      |     ^~~~~~~~~
include/PR/os_pi.h:61:14: error: unknown type name 'uintptr_t'
   61 |     /*0x0C*/ uintptr_t devAddr;
      |              ^~~~~~~~~
include/PR/os_pi.h:78:61: error: unknown type name 'uintptr_t'
   78 | s32 osPiStartDma(OSIoMesg *mb, s32 priority, s32 direction, uintptr_t devAddr, void *vAddr,
      |                                                             ^~~~~~~~~
include/PR/os_pi.h:82:17: error: unknown type name 'uintptr_t'
   82 | s32 osPiWriteIo(uintptr_t devAddr, u32 data);
      |                 ^~~~~~~~~
include/PR/os_pi.h:83:16: error: unknown type name 'uintptr_t'
   83 | s32 osPiReadIo(uintptr_t devAddr, u32 *data);
      |                ^~~~~~~~~
make: *** [Makefile:582: build/us/src/engine/surface_collision.o] Error 1

I am suspecting that maybe I did not install the right C libraries and this is why I am facing this issue. Is there a specific C library package that is required that I do not have installed?

Same error for me. I found an older source code from January the fifth. With this code I had to install glfw-x11 then it was possible to compile and run the game.
I'm on Arch.

Change target_n64 to 1 and compiler to ido. Other compiler options are not supported.


change the version of hashie

change the version of hashie '3.0' to '2.0.5' for using in gbp

change version of hashie


Release process guide / manual

part of #864
What problem are you facing?
There is no release guide that educates and informs an engineer of Crossplane on how to release a new version of the software.  @jbw976 has run the releases so far but no one else knows how to perform one.
How could Crossplane help solve your problem?
We should create a new release process guide that provides all the instructions and tips for running a release of the Crossplane software.  This guide should cover how to tag/branch, build and publish, and promote.  It should also cover patch releases as well.

This release guide will be finalized with real world examples/output of the process from running through the real v0.4.0 release.  Therefore, this issue will be fixed first thing in v0.5.0.


[ci:component:github.com/gardener/logging:v0.36.2->v0.37.0]

Release Notes:
Logs can be spread across Shoot control-plane Loki and central Loki base on the Shoot state.

/close


Matomo not mapping to mariadb

Problem
The Matomo container can't connect to the MariaDB.

The directions in setup-matomo.sh and setup Matomo on Crossfeed contradict one another.  Need to sort out the order and fix one or the others directions.

Shouldn't the command in the .sh file be:
docker-compose exec crossfeed_matomo_1 sed -i 's/"localhost"/"localhost:3000"/g' /var/www/html/config/config.ini.php

Nope.  Can remain as is.
Solution is making sure the mariadb container is running.  At a mininum the version of mariadb needs to be bumped to mariadb:10.11.2 in the docker-compose file.


[Question] why you answer a PING with another PING?

First of all sorry for the noise, I didn't find another place to ask this.
Reading through your code I noticed that when you receive a PING from twitch you answer with another PING instead of answering with a PONG, as the documentation suggests.
Is this intentional? and if so, why?
PS. thanks for working on this library, its the most complete twitch library in Go.
https://github.com/Adeithe/go-twitch/blob/eee71bbf962d35422efb687cd4310da06a344485/irc/conn.go#L351-L352
https://github.com/Adeithe/go-twitch/blob/eee71bbf962d35422efb687cd4310da06a344485/irc/conn.go#L168-L178

A PING/PONG is only required to prevent the connection from being deemed dead by Twitch and closed from their end. You do not need to send any PONG messages as long as a PING/PONG is sent from either end.
Sending a PING instead allows the client to easily track the latency to the server, which is then made available by the library if needed.


Update fit

updated capacity split-output regex to handle a bytes-like object and updated xrange to range on line 94

updated capacity split-output regex to handle a bytes-like object and updated xrange to range on line 94


Disposing session as kernel process died ExitCode:<PHONE_NUMBER>

Applies To

[x] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
The Jupyter kernel crashes whenever I type a dot (.) following pd.DataFrame() or pd.Series()!
VS Code Version
1.95.3
Jupyter Extension Version
2024.10.0
Jupyter logs
Visual Studio Code (1.95.3, undefined, desktop)
Jupyter Extension Version: 2024.10.0.
Python Extension Version: 2024.20.0.
Pylance Extension Version: 2024.12.1.
Platform: win32 (x64).
Temp Storage folder ~\AppData\Roaming\Code\User\globalStorage\ms-toolsai.jupyter\version-2024.10.0
Workspace folder ~\Desktop\codetest, Home = c:\Users\weaver
23:07:26.098 [debug] Start refreshing Kernel Picker<PHONE_NUMBER>098)
23:07:26.125 [trace] Preferred Remote kernel for ~\Desktop\codetest\test.ipynb is undefined
23:07:26.158 [trace] No controller, hence notebook communications cannot be initialized for editor ~\Desktop\codetest\test.ipynb
23:07:26.158 [debug] Start refreshing Interpreter Kernel Picker
23:07:26.699 [trace] Search for KernelSpecs in Interpreter d:\ProgramData\Anaconda3\python.exe
23:07:26.699 [trace] Search for KernelSpecs in Interpreter d:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro_py3\python.exe
23:07:26.699 [trace] Search for KernelSpecs in Interpreter d:\ProgramData\Anaconda3\envs\fenicsx-env\python.exe
23:07:26.700 [trace] Search for KernelSpecs in Interpreter d:\ProgramData\Anaconda3\envs\py310\python.exe
23:07:26.700 [trace] Search for KernelSpecs in Interpreter d:\ProgramData\Anaconda3\envs\py311\python.exe
23:07:26.700 [trace] Search for KernelSpecs in Interpreter d:\ProgramData\Anaconda3\envs\py312\python.exe
23:07:26.700 [trace] Search for KernelSpecs in Interpreter d:\ProgramData\Anaconda3\envs\py312_DL\python.exe
23:07:26.700 [trace] Search for KernelSpecs in Interpreter d:\ProgramData\Anaconda3\envs\py313\python.exe
23:07:26.720 [debug] Get Custom Env Variables, Class name = Em, completed in 622ms, has a truthy return value, Arg 1: undefined, Arg 2: "RunPythonCode"
23:07:26.720 [debug] Jupyter Paths kernels:
23:07:26.721 [trace] Kernel fenicsx-env matches d:\PROGRAMDATA\ANACONDA3\ENVS\FENICSX-ENV\PYTHON.EXE based on argv.
23:07:26.721 [trace] Kernel undefined.-xfrozen_modules=off matches d:\PROGRAMDATA\ANACONDA3\ENVS\PY312_DL\PYTHON.EXE based on argv.
23:07:26.721 [trace] Kernel py310 matches d:\PROGRAMDATA\ANACONDA3\ENVS\PY310\PYTHON.EXE based on argv.
23:07:26.722 [trace] Kernel py311 matches d:\PROGRAMDATA\ANACONDA3\ENVS\PY311\PYTHON.EXE based on argv.
23:07:26.722 [trace] Kernel undefined.-xfrozen_modules=off matches d:\PROGRAMDATA\ANACONDA3\ENVS\PY312\PYTHON.EXE based on argv.
23:07:26.722 [trace] Kernel undefined.-xfrozen_modules=off matches d:\PROGRAMDATA\ANACONDA3\ENVS\PY313\PYTHON.EXE based on argv.
23:07:26.725 [debug] Kernel Spec Root Paths, ~\AppData\Roaming\jupyter\kernels, c:\ProgramData\jupyter\kernels
23:07:26.733 [error] Failed to validate Password info [D [FetchError]: request to http://localhost:8778/notebooks/E:/%E7%94%A8%E6%88%B7/GIS/%E5%B0%8F%E8%AE%BA%E6%96%87/2023.05%E5%AE%81%E5%A4%8F%E5%9C%B0%E4%B8%8B%E6%B0%B4/GIS%E5%A4%84%E7%90%86.ipynb/ failed, reason:
	at ClientRequest.<anonymous> (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\dist\node_modules\node-fetch.js:1:306417)
	at ClientRequest.emit (node:events:519:28)
	at emitErrorEvent (node:_http_client:101:11)
	at Socket.socketErrorListener (node:_http_client:504:5)
	at Socket.emit (node:events:519:28)
	at emitErrorNT (node:internal/streams/destroy:169:8)
	at emitErrorCloseNT (node:internal/streams/destroy:128:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)] {
  type: 'system',
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED'
}
23:07:27.106 [error] Error fetching kernels from http://localhost:8778/notebooks/E:/用户/GIS/小论文/2023.05宁夏地下水/GIS处理.ipynb (localhost): [FetchError: request to http://localhost:8778/notebooks/E:/%E7%94%A8%E6%88%B7/GIS/%E5%B0%8F%E8%AE%BA%E6%96%87/2023.05%E5%AE%81%E5%A4%8F%E5%9C%B0%E4%B8%8B%E6%B0%B4/GIS%E5%A4%84%E7%90%86.ipynb/api/kernels?1733843246753 failed, reason:
	at ClientRequest.<anonymous> (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\dist\node_modules\node-fetch.js:1:306417)
	at ClientRequest.emit (node:events:519:28)
	at emitErrorEvent (node:_http_client:101:11)
	at Socket.socketErrorListener (node:_http_client:504:5)
	at Socket.emit (node:events:519:28)
	at emitErrorNT (node:internal/streams/destroy:169:8)
	at emitErrorCloseNT (node:internal/streams/destroy:128:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)]
23:07:27.106 [trace] Disposing Jupyter Lab Helper
23:07:27.106 [trace] SessionManager - dispose contents manager
23:07:27.107 [trace] ShutdownSessionAndConnection - dispose session manager
23:07:27.108 [trace] Finished disposing Jupyter Lab Helper
23:07:27.108 [error] Jupyter Lab Helper:getKernelSpecs failure:  [Error: Poll (@jupyterlab/services:KernelSpecManager#specs) is disposed.
	at i.dispose (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\dist\node_modules\@jupyterlab\services.js:11:35855)
	at Kr.dispose (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\dist\node_modules\@jupyterlab\services.js:11:75419)
	at c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\dist\extension.node.js:181:17985
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)]
23:07:27.153 [debug] KernelProvider switched kernel to id = .jvsc74a57bd0e2fd1a852522f4beac4f7293d90080bfa2ac6b4d4ed570765f628c70b4631bed.d:\ProgramData\Anaconda3\envs\py311\python.exe.d:\ProgramData\Anaconda3\envs\py311\python.exe.-m#ipykernel_launcher
23:07:27.154 [debug] start the kernel, options.disableUI=true for ~\Desktop\codetest\test.ipynb
23:07:27.158 [trace] Registering commtarget jupyter.widget
23:07:27.159 [debug] Controller selection change completed
23:07:27.238 [debug] Get Custom Env Variables, Class name = Em, completed in 0ms, has a truthy return value, Arg 1: "/C:/Users/~/Desktop/codetest", Arg 2: "RunPythonCode"
23:07:27.239 [info] Starting Kernel (Python Path: d:\ProgramData\Anaconda3\envs\py311\python.exe, Conda, 3.11.10) for '~\Desktop\codetest\test.ipynb' (disableUI=true)
23:07:27.239 [trace] Creating raw notebook for resource '~\Desktop\codetest\test.ipynb'
23:07:27.246 [error] Failed to validate Password info [D [FetchError]: request to http://localhost:8778/notebooks/E:/%E7%94%A8%E6%88%B7/GIS/%E5%B0%8F%E8%AE%BA%E6%96%87/2023.05%E5%AE%81%E5%A4%8F%E5%9C%B0%E4%B8%8B%E6%B0%B4/GIS%E5%A4%84%E7%90%86.ipynb/ failed, reason:
	at ClientRequest.<anonymous> (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\dist\node_modules\node-fetch.js:1:306417)
	at ClientRequest.emit (node:events:519:28)
	at emitErrorEvent (node:_http_client:101:11)
	at Socket.socketErrorListener (node:_http_client:504:5)
	at Socket.emit (node:events:519:28)
	at emitErrorNT (node:internal/streams/destroy:169:8)
	at emitErrorCloseNT (node:internal/streams/destroy:128:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)] {
  type: 'system',
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED'
}
23:07:27.279 [debug] Get Custom Env Variables, Class name = Em, completed in 0ms, has a truthy return value, Arg 1: "/c:/Users/~/Desktop/codetest/test.ipynb", Arg 2: "RunPythonCode"
23:07:27.320 [error] Error fetching kernels from http://localhost:8778/notebooks/E:/用户/GIS/小论文/2023.05宁夏地下水/GIS处理.ipynb (localhost): [FetchError: request to http://localhost:8778/notebooks/E:/%E7%94%A8%E6%88%B7/GIS/%E5%B0%8F%E8%AE%BA%E6%96%87/2023.05%E5%AE%81%E5%A4%8F%E5%9C%B0%E4%B8%8B%E6%B0%B4/GIS%E5%A4%84%E7%90%86.ipynb/api/kernels?1733843247247 failed, reason:
	at ClientRequest.<anonymous> (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\dist\node_modules\node-fetch.js:1:306417)
	at ClientRequest.emit (node:events:519:28)
	at emitErrorEvent (node:_http_client:101:11)
	at Socket.socketErrorListener (node:_http_client:504:5)
	at Socket.emit (node:events:519:28)
	at emitErrorNT (node:internal/streams/destroy:169:8)
	at emitErrorCloseNT (node:internal/streams/destroy:128:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)]
23:07:27.320 [trace] Disposing Jupyter Lab Helper
23:07:27.320 [trace] SessionManager - dispose contents manager
23:07:27.320 [trace] ShutdownSessionAndConnection - dispose session manager
23:07:27.320 [trace] Finished disposing Jupyter Lab Helper
23:07:27.320 [error] Jupyter Lab Helper:getKernelSpecs failure:  [Error: Poll (@jupyterlab/services:KernelSpecManager#specs) is disposed.
	at i.dispose (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\dist\node_modules\@jupyterlab\services.js:11:35855)
	at Kr.dispose (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\dist\node_modules\@jupyterlab\services.js:11:75419)
	at c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\dist\extension.node.js:181:17985
	at process.processTicksAndRejections (node:internal/process/task_queues:95:5)]
23:07:27.320 [error] UniversalRemoteKernelFinder: Failed to get kernels without cache [FetchError: request to http://localhost:8778/notebooks/E:/%E7%94%A8%E6%88%B7/GIS/%E5%B0%8F%E8%AE%BA%E6%96%87/2023.05%E5%AE%81%E5%A4%8F%E5%9C%B0%E4%B8%8B%E6%B0%B4/GIS%E5%A4%84%E7%90%86.ipynb/api/kernels?1733843247247 failed, reason:
	at ClientRequest.<anonymous> (c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\dist\node_modules\node-fetch.js:1:306417)
	at ClientRequest.emit (node:events:519:28)
	at emitErrorEvent (node:_http_client:101:11)
	at Socket.socketErrorListener (node:_http_client:504:5)
	at Socket.emit (node:events:519:28)
	at emitErrorNT (node:internal/streams/destroy:169:8)
	at emitErrorCloseNT (node:internal/streams/destroy:128:3)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)]
23:07:27.321 [trace] UniversalRemoteKernelFinder: Writing 0 remote kernel connection metadata to cache
23:07:27.321 [trace] Hiding default KernelSpec d:\ProgramData\Anaconda3\envs\py310\python.exe for interpreter d:\ProgramData\Anaconda3\envs\py310\python.exe (KernelSpec file d:\ProgramData\Anaconda3\envs\py310\share\jupyter\kernels\python3\kernel.json)
23:07:27.321 [trace] Hiding default KernelSpec d:\ProgramData\Anaconda3\python.exe for interpreter d:\ProgramData\Anaconda3\python.exe (KernelSpec file d:\ProgramData\Anaconda3\share\jupyter\kernels\python3\kernel.json)
23:07:27.322 [trace] Hiding default KernelSpec d:\ProgramData\Anaconda3\envs\fenicsx-env\python.exe for interpreter d:\ProgramData\Anaconda3\envs\fenicsx-env\python.exe (KernelSpec file d:\ProgramData\Anaconda3\envs\fenicsx-env\share\jupyter\kernels\python3\kernel.json)
23:07:27.322 [trace] Hiding default KernelSpec d:\ProgramData\Anaconda3\envs\py311\python.exe for interpreter d:\ProgramData\Anaconda3\envs\py311\python.exe (KernelSpec file d:\ProgramData\Anaconda3\envs\py311\share\jupyter\kernels\python3\kernel.json)
23:07:27.324 [trace] Kernels for interpreter D:\PROGRAMDATA\ANACONDA3\ENVS\PY311\PYTHON.EXE are .jvsc74a57bd0e2fd1a852522f4beac4f7293d90080bfa2ac6b4d4ed570765f628c70b4631bed#ir.d:\ProgramData\Anaconda3\envs\py311\python.exe.\.r#--slave#-e#irkernel::main()#--args#{connection_file}, .jvsc74a57bd0e2fd1a852522f4beac4f7293d90080bfa2ac6b4d4ed570765f628c70b4631bed.d:\ProgramData\Anaconda3\envs\py311\python.exe.d:\ProgramData\Anaconda3\envs\py311\python.exe.-m#ipykernel_launcher
23:07:27.326 [trace] Hiding default KernelSpec d:\ProgramData\Anaconda3\envs\py313\python.exe for interpreter d:\ProgramData\Anaconda3\envs\py313\python.exe (KernelSpec file d:\ProgramData\Anaconda3\envs\py313\share\jupyter\kernels\python3\kernel.json)
23:07:27.326 [trace] Hiding default KernelSpec d:\ProgramData\Anaconda3\envs\py312\python.exe for interpreter d:\ProgramData\Anaconda3\envs\py312_DL\python.exe (KernelSpec file d:\ProgramData\Anaconda3\envs\py312_DL\share\jupyter\kernels\python3\kernel.json)
23:07:27.326 [trace] Hiding default KernelSpec d:\ProgramData\Anaconda3\envs\py312\python.exe for interpreter d:\ProgramData\Anaconda3\envs\py312\python.exe (KernelSpec file d:\ProgramData\Anaconda3\envs\py312\share\jupyter\kernels\python3\kernel.json)
23:07:27.326 [trace] Kernels for interpreter D:\PROGRAMDATA\ANACONDA3\ENVS\PY312\PYTHON.EXE are .jvsc74a57bd0faf140ff0f5f9d86cdbc5c76469dd70318756508101fa2855a35ca2a7575f709#ir.d:\ProgramData\Anaconda3\envs\py312\python.exe.\.r#--slave#-e#irkernel::main()#--args#{connection_file}, .jvsc74a57bd0faf140ff0f5f9d86cdbc5c76469dd70318756508101fa2855a35ca2a7575f709.d:\ProgramData\Anaconda3\envs\py312\python.exe.d:\ProgramData\Anaconda3\envs\py312\python.exe.-m#ipykernel_launcher
23:07:27.359 [trace] Hiding default KernelSpec d:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro_py3\python.exe for interpreter d:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro_py3\python.exe (KernelSpec file d:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro_py3\share\jupyter\kernels\python3\kernel.json)
23:07:27.359 [trace] Kernels for interpreter D:\PROGRAM FILES\ARCGIS\PRO\BIN\PYTHON\ENVS\ARCGISPRO_PY3\PYTHON.EXE are .jvsc74a57bd03684f063b6a359112b8354210d934241ec9b32ba13dfc82c4f024b6130247516#xpython.d:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro_py3\python.exe.d:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro_py3\python.exe., .jvsc74a57bd03684f063b6a359112b8354210d934241ec9b32ba13dfc82c4f024b6130247516.d:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro_py3\python.exe.d:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro_py3\python.exe.-m#ipykernel_launcher
23:07:27.365 [debug] Launching kernel .jvsc74a57bd0e2fd1a852522f4beac4f7293d90080bfa2ac6b4d4ed570765f628c70b4631bed.d:\ProgramData\Anaconda3\envs\py311\python.exe.d:\ProgramData\Anaconda3\envs\py311\python.exe.-m#ipykernel_launcher for ~\Desktop\codetest\test.ipynb in ~\Desktop\codetest with ports 9001, 9000, 9004, 9002, 9003
23:07:28.129 [trace] Conda file is conda
23:07:28.682 [debug] Interpreter for Pylance for Notebook URI "~\Desktop\codetest\test.ipynb" is d:\ProgramData\Anaconda3\envs\py311\python.exe
23:07:28.755 [trace] Python API env change detected, update => 'D:\PROGRAMDATA\ANACONDA3\PYTHON.EXE'
23:07:28.755 [trace] Python API env change detected, update => 'D:\PROGRAM FILES\ARCGIS\PRO\BIN\PYTHON\ENVS\ARCGISPRO_PY3\PYTHON.EXE'
23:07:28.755 [trace] Python API env change detected, update => 'D:\PROGRAMDATA\ANACONDA3\ENVS\FENICSX-ENV\PYTHON.EXE'
23:07:28.756 [trace] Python API env change detected, update => 'D:\PROGRAMDATA\ANACONDA3\ENVS\PY310\PYTHON.EXE'
23:07:28.756 [trace] Python API env change detected, update => 'D:\PROGRAMDATA\ANACONDA3\ENVS\PY311\PYTHON.EXE'
23:07:28.756 [trace] Python API env change detected, update => 'D:\PROGRAMDATA\ANACONDA3\ENVS\PY312\PYTHON.EXE'
23:07:28.756 [trace] Python API env change detected, update => 'D:\PROGRAMDATA\ANACONDA3\ENVS\PY312_DL\PYTHON.EXE'
23:07:28.757 [trace] Python API env change detected, update => 'D:\PROGRAMDATA\ANACONDA3\ENVS\PY313\PYTHON.EXE'
23:07:28.758 [debug] Refreshed Environments
23:07:29.759 [debug] End refreshing Kernel Picker<PHONE_NUMBER>098)
23:07:30.238 [debug] Got env vars from Python Ext in 3000ms for d:\ProgramData\Anaconda3\envs\py311\python.exe, with env var count 78.
23:07:30.238 [trace] Prepend PATH with python bin for d:\ProgramData\Anaconda3\envs\py311\python.exe
23:07:30.239 [debug] Getting activated env variables, Class name = Id, completed in 3000ms, has a truthy return value, Arg 1: "/C:/Users/~/Desktop/codetest", Arg 2: "D:\\PROGRAMDATA\\ANACONDA3\\ENVS\\PY311\\PYTHON.EXE", Arg 3: undefined
23:07:30.244 [info] Process Execution: d:\ProgramData\Anaconda3\envs\py311\python.exe -m pip list
23:07:30.251 [debug] Got env vars from Python Ext in 2972ms for d:\ProgramData\Anaconda3\envs\py311\python.exe, with env var count 78.
23:07:30.251 [trace] Prepend PATH with python bin for d:\ProgramData\Anaconda3\envs\py311\python.exe
23:07:30.251 [debug] Getting activated env variables, Class name = Id, completed in 2972ms, has a truthy return value, Arg 1: "/c:/Users/~/Desktop/codetest/test.ipynb", Arg 2: "D:\\PROGRAMDATA\\ANACONDA3\\ENVS\\PY311\\PYTHON.EXE", Arg 3: undefined
23:07:30.256 [info] Process Execution: d:\ProgramData\Anaconda3\envs\py311\python.exe -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
23:07:30.262 [info] Process Execution: d:\ProgramData\Anaconda3\envs\py311\python.exe c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\pythonFiles\vscode_datascience_helpers\kernel_interrupt_daemon.py --ppid 12292
    > cwd: ~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\pythonFiles\vscode_datascience_helpers
23:07:30.337 [trace] Got a response of 1780 for INITIALIZE_INTERRUPT:0
23:07:30.342 [info] Process Execution: d:\ProgramData\Anaconda3\envs\py311\python.exe -m ipykernel_launcher --f=c:\Users\~\AppData\Roaming\jupyter\runtime\kernel-v37cde88f6d1e642d965dff46138a8cfdf78433c98.json
    > cwd: ~\Desktop\codetest
23:07:30.343 [debug] Kernel process 9896.
23:07:30.477 [trace] ipykernel version & path 6.29.5, d:\ProgramData\Anaconda3\envs\py311\Lib\site-packages\ipykernel\__init__.py for d:\ProgramData\Anaconda3\envs\py311\python.exe
23:07:31.007 [debug] Kernel output 9896: To connect another client to this kernel, use:
--existing c:\Users\~\AppData\Roaming\jupyter\runtime\kernel-v37cde88f6d1e642d965dff46138a8cfdf78433c98.json
23:07:31.065 [debug] Waiting for Raw Session to be ready in postStartRawSession
23:07:31.065 [debug] Waiting for Raw session to be ready, status: connected
23:07:31.065 [trace] Raw session connected
23:07:31.065 [debug] Waited for Raw session to be ready & got status: connected
23:07:31.065 [debug] Successfully waited for Raw Session to be ready in postStartRawSession
23:07:31.065 [debug] Kernel status is 'unknown' before requesting kernel info and after ready
23:07:31.065 [debug] Sending request for kernelInfo
23:07:31.178 [trace] Got response for requestKernelInfo
23:07:31.178 [debug] Successfully completed postStartRawSession after 1 attempt(s) in 113ms
23:07:31.179 [trace] Executing silently Code (idle) = import sys as _VSCODE_sys\nprint(_VSCODE_sys.executable); del _VSCODE_sys
23:07:31.187 [trace] Executing silently Code (completed) = import sys as _VSCODE_sys\nprint(_VSCODE_sys.executable); del _VSCODE_sys with 1 output(s)
23:07:31.188 [trace] Started running kernel initialization for ~\Desktop\codetest\test.ipynb
23:07:31.188 [trace] Executing silently Code (idle) = try:\nimport ipywidgets as _VSCODE_ipywidgets\nprint("e976ee50-99ed-4aba-9b6b-9dcd5634d07d:IPy
23:07:31.229 [trace] Executing silently Code (completed) = try:\nimport ipywidgets as _VSCODE_ipywidgets\nprint("e976ee50-99ed-4aba-9b6b-9dcd5634d07d:IPy with 1 output(s)
23:07:31.230 [trace] Determined IPyWidgets Version as 8
23:07:31.230 [trace] Version of IPyWidgets 8 determined after 4.072s
23:07:31.230 [trace] Executing silently Code (idle) = def __VSCODE_inject_module():\ndef __VSCODE_call_function(function, callback, data=None):
23:07:31.239 [trace] Executing silently Code (completed) = def __VSCODE_inject_module():\ndef __VSCODE_call_function(function, callback, data=None): with 0 output(s)
23:07:31.239 [debug] Requesting Kernel info
23:07:31.240 [trace] Got Kernel info
23:07:31.240 [trace] End running kernel initialization, now waiting for idle
23:07:31.240 [trace] Waiting for idle on (kernel): db455c40-1981-48f2-b825-7d58c043e746 -> idle
23:07:31.240 [trace] Finished waiting for idle on (kernel): db455c40-1981-48f2-b825-7d58c043e746 -> idle
23:07:31.240 [trace] End running kernel initialization, session is idle
23:07:31.241 [trace] Registering Kernel Completion Provider from kernel py311 (Python 3.11.10) for language python
23:07:31.241 [trace] IPyWidgetScriptSource.initialize
23:07:31.242 [info] Kernel successfully started
23:07:31.243 [debug] getDataDirsImpl, Class name = Kr (started execution), Arg 1: "/c:/Users/~/Desktop/codetest/test.ipynb", Arg 2: "D:\\PROGRAMDATA\\ANACONDA3\\ENVS\\PY311\\PYTHON.EXE"
23:07:31.244 [debug] Get Custom Env Variables, Class name = Em, completed in 1ms, has a truthy return value, Arg 1: undefined, Arg 2: "RunPythonCode"
23:07:31.244 [debug] Jupyter Paths :
23:07:31.244 [debug] Get Custom Env Variables, Class name = Em, completed in 0ms, has a truthy return value, Arg 1: "/c:/Users/~/Desktop/codetest/test.ipynb", Arg 2: "RunPythonCode"
23:07:31.245 [debug] Got env vars from Python Ext in 1ms for d:\ProgramData\Anaconda3\envs\py311\python.exe, with env var count 78.
23:07:31.245 [trace] Prepend PATH with python bin for d:\ProgramData\Anaconda3\envs\py311\python.exe
23:07:31.245 [debug] Getting activated env variables, Class name = Id, completed in 1ms, has a truthy return value, Arg 1: "/c:/Users/~/Desktop/codetest/test.ipynb", Arg 2: "D:\\PROGRAMDATA\\ANACONDA3\\ENVS\\PY311\\PYTHON.EXE", Arg 3: undefined
23:07:31.255 [info] Process Execution: d:\ProgramData\Anaconda3\envs\py311\python.exe c:\Users\~\.vscode\extensions\ms-toolsai.jupyter-2024.10.0-win32-x64\pythonFiles\printJupyterDataDir.py
23:07:31.307 [debug] getDataDirsImpl, Class name = Kr, completed in 64ms, has a truthy return value, Arg 1: "/c:/Users/~/Desktop/codetest/test.ipynb", Arg 2: "D:\\PROGRAMDATA\\ANACONDA3\\ENVS\\PY311\\PYTHON.EXE", Return Value: <Uri:/C:/Users/~/AppData/Roaming/jupyter>, <Uri:/D:/ProgramData/Anaconda3/envs/py311/share/jupyter>, <Uri:/C:/ProgramData/jupyter>
23:07:31.763 [trace] Web view is ready to receive widget messages
23:07:31.765 [trace] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
23:07:31.766 [trace] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
23:07:31.775 [trace] Widget Message: data-base-url set to https://file%2B.vscode-resource.vscode-cdn.net/c%3A/Users/~/.vscode/extensions/ms-toolsai.jupyter-2024.10.0-win32-x64/temp/scripts/95035c8b1e253d7d4b05d6fe57344b073a2dc57a1c6a38a0b0aeb9ada4a3a581/jupyter
23:07:31.775 [trace] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
23:07:31.775 [trace] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
23:07:31.775 [trace] Widget Message: data-base-url set to https://file%2B.vscode-resource.vscode-cdn.net/c%3A/Users/~/.vscode/extensions/ms-toolsai.jupyter-2024.10.0-win32-x64/temp/scripts/95035c8b1e253d7d4b05d6fe57344b073a2dc57a1c6a38a0b0aeb9ada4a3a581/jupyter
23:07:31.775 [trace] Widget Message: Received IPyWidget scripts [{"moduleName":"jupyter-matplotlib","scriptUri":"https://file%2B.vscode-resource.vscode-cdn.net/c%3A/Users/~/.vscode/extensions/ms-toolsai.jupyter-2024.10.0-win32-x64/temp/scripts/95035c8b1e253d7d4b05d6fe57344b073a2dc57a1c6a38a0b0aeb9ada4a3a581/jupyter/nbextensions/jupyter-matplotlib/index","source":"local"}]
23:07:31.775 [trace] Widget Message: Source for IPyWidget jupyter-matplotlib found in local @ https://file%2B.vscode-resource.vscode-cdn.net/c%3A/Users/~/.vscode/extensions/ms-toolsai.jupyter-2024.10.0-win32-x64/temp/scripts/95035c8b1e253d7d4b05d6fe57344b073a2dc57a1c6a38a0b0aeb9ada4a3a581/jupyter/nbextensions/jupyter-matplotlib/index.
23:07:31.775 [trace] Widget Message: Registering IPyWidget jupyter-matplotlib found in https://file%2B.vscode-resource.vscode-cdn.net/c%3A/Users/~/.vscode/extensions/ms-toolsai.jupyter-2024.10.0-win32-x64/temp/scripts/95035c8b1e253d7d4b05d6fe57344b073a2dc57a1c6a38a0b0aeb9ada4a3a581/jupyter/nbextensions/jupyter-matplotlib/index.
23:07:31.775 [trace] Widget Message: Received IPyWidget scripts [{"moduleName":"jupyterlab-plotly","scriptUri":"https://file%2B.vscode-resource.vscode-cdn.net/c%3A/Users/~/.vscode/extensions/ms-toolsai.jupyter-2024.10.0-win32-x64/temp/scripts/95035c8b1e253d7d4b05d6fe57344b073a2dc57a1c6a38a0b0aeb9ada4a3a581/jupyter/nbextensions/jupyterlab-plotly/index","source":"local"}]
23:07:31.775 [trace] Widget Message: Source for IPyWidget jupyterlab-plotly found in local @ https://file%2B.vscode-resource.vscode-cdn.net/c%3A/Users/~/.vscode/extensions/ms-toolsai.jupyter-2024.10.0-win32-x64/temp/scripts/95035c8b1e253d7d4b05d6fe57344b073a2dc57a1c6a38a0b0aeb9ada4a3a581/jupyter/nbextensions/jupyterlab-plotly/index.
23:07:31.775 [trace] Widget Message: Registering IPyWidget jupyterlab-plotly found in https://file%2B.vscode-resource.vscode-cdn.net/c%3A/Users/~/.vscode/extensions/ms-toolsai.jupyter-2024.10.0-win32-x64/temp/scripts/95035c8b1e253d7d4b05d6fe57344b073a2dc57a1c6a38a0b0aeb9ada4a3a581/jupyter/nbextensions/jupyterlab-plotly/index.
23:07:35.999 [debug] Jupyter completion time: 10
23:07:36.002 [debug] Execution of code ms-toolsai.jupyter-1 completed in 12ms
23:07:38.535 [debug] Execution of code ms-toolsai.jupyter-2 completed in 7ms
23:07:38.584 [debug] Jupyter completion time: 56
23:07:39.670 [debug] Jupyter completion time: 8
23:07:39.672 [debug] Execution of code ms-toolsai.jupyter-3 completed in 10ms
23:07:39.758 [trace] Inspecting code import pandas as
23:07:39.765 [debug] Inspected code import pandas as in 7ms
23:07:39.766 [debug] Execution of code ms-toolsai.jupyter-4 completed in 8ms
23:07:40.220 [debug] Execution of code ms-toolsai.jupyter-5 completed in 14ms
23:07:40.220 [debug] Jupyter completion time: 15
23:07:40.223 [trace] Inspecting code import pandas as pass
23:07:40.231 [debug] Inspected code import pandas as pass in 8ms
23:07:40.232 [debug] Execution of code ms-toolsai.jupyter-6 completed in 9ms
23:07:40.389 [debug] Jupyter completion time: 12
23:07:40.390 [debug] Execution of code ms-toolsai.jupyter-7 completed in 12ms
23:07:40.987 [debug] Handle Execution of Cells 1 for ~\Desktop\codetest\test.ipynb
23:07:40.988 [trace] Execute Notebook ~\Desktop\codetest\test.ipynb. Step 1
23:07:40.988 [trace] Connect to Kernel ~\Desktop\codetest\test.ipynb. Step 2
23:07:40.988 [trace] Connected to Kernel ~\Desktop\codetest\test.ipynb. Step 3
23:07:40.988 [trace] executeCell 1. Step 4
23:07:40.989 [trace] Cell Index:1 sent to kernel
23:07:40.992 [trace] Start cell 1 execution @<PHONE_NUMBER>992 (clear output)
23:07:40.993 [debug] Kernel acknowledged execution of cell 1 @<PHONE_NUMBER>992
23:07:41.285 [trace] Cell 1 completed in 0.293s (start:<PHONE_NUMBER>992, end:<PHONE_NUMBER>285)
23:07:41.286 [trace] Cell 1 executed successfully
23:07:44.494 [trace] Queue code ms-toolsai.datawrangler-1 from ms-toolsai.datawrangler after 0ms:

23:07:44.494 [trace] Execution Id:ms-toolsai.datawrangler-1. Start Code execution.
23:07:44.494 [trace] Execution Id:ms-toolsai.datawrangler-1. Send code for execution.
23:07:44.495 [trace] Execution Id:ms-toolsai.datawrangler-1. Execution Request Sent to Kernel.
23:07:44.501 [trace] Execution Id:ms-toolsai.datawrangler-1. Executed successfully.
23:07:44.501 [debug] Execution of code ms-toolsai.datawrangler-1 completed in 7ms
23:07:44.503 [trace] Queue code ms-toolsai.datawrangler-2 from ms-toolsai.datawrangler after 0ms:

def __DW_GET_DF_VARS__():
    # see definition of these in the debug session
    global __DW_LOCALS__
    global __DW_GLOBALS__

    import json
    import builtins
    import sys

    try:
        import IPython
        curr_scope = { **builtins.globals(), **builtins.locals() }
        curr_globals = IPython.get_ipython().user_ns
        hidden_scope = IPython.get_ipython().user_ns_hidden
    except builtins.Exception:
        curr_scope = { **__DW_LOCALS__, **__DW_GLOBALS__ }
        curr_globals = __DW_GLOBALS__
        hidden_scope = {}

    supported_dataframe_types = {
        builtins.list: "list",
        builtins.dict: "dictionary",
    }

    if 'numpy' in sys.modules:
        try:
            import numpy as np
            supported_dataframe_types[np.ndarray] = "ndarray"
        except builtins.Exception:
            pass

    if 'pandas' in sys.modules:
        try:
            import pandas as pd
            supported_dataframe_types[pd.DataFrame] = "pandas"
            supported_dataframe_types[pd.Series] = "series"
        except builtins.Exception:
            pass

    if 'polars' in sys.modules:
        try:
            import polars as pl
            supported_dataframe_types[pl.DataFrame] = "polars"
            supported_dataframe_types[pl.Series] = "polarsSeries"
        except builtins.Exception:
            pass

    if 'xarray' in sys.modules:
        try:
            import xarray as xr
            supported_dataframe_types[xr.DataArray] = "dataArray"
        except builtins.Exception:
            pass

    if 'tensorflow' in sys.modules:
        try:
            import tensorflow as tf
            supported_dataframe_types[tf.Tensor] = "eagerTensor"
        except builtins.Exception:
            pass

    if 'torch' in sys.modules:
        try:
            import torch
            supported_dataframe_types[torch.Tensor] = "tensor"
        except builtins.Exception:
            pass

    if 'pyspark' in sys.modules and False:
        try:
            import pyspark
            supported_dataframe_types[pyspark.sql.dataframe.DataFrame] = "pyspark"
        except builtins.Exception:
            pass
        try:
            import pyspark
            supported_dataframe_types[pyspark.sql.connect.dataframe.DataFrame] = "pyspark"
        except builtins.Exception:
            pass

    def is_fallback_supported(variable):
        return builtins.hasattr(variable, "to_pandas") or builtins.hasattr(variable, "toPandas") or builtins.hasattr(variable, "__dataframe__") or builtins.type(variable).__name__ in {"DataFrame","list","dict","ndarray","Series","Tensor","EagerTensor","DataArray"}

    try:
        # we still need this due to https://github.com/ipython/ipykernel/issues/795
        import IPython
        capture_output = IPython.utils.capture.capture_output
    except Exception:
        class capture_output():
            def __init__(self):
                import io
                self.stdoutio = io.StringIO()
                self.stderrio = io.StringIO()
            @property
            def stdout(self):
                return self.stdoutio.getvalue()
            @property
            def stderr(self):
                return self.stderrio.getvalue()
            def __enter__(self):
                from contextlib import redirect_stdout, redirect_stderr
                self.redirect_stdout = redirect_stdout(self.stdoutio)
                self.redirect_stderr = redirect_stderr(self.stderrio)
                self.redirect_stdout.__enter__(),
                self.redirect_stderr.__enter__()
                return self
            def __exit__(self, *args, **kwargs):
                result_stdout = self.redirect_stdout.__exit__(*args, **kwargs)
                result_stderr = self.redirect_stderr.__exit__(*args, **kwargs)
                return result_stdout and result_stderr

    with capture_output():
        def is_local(k):
            return k not in curr_globals or curr_scope[k] is not curr_globals[k]
        def valid_keys(k):
            # see https://github.com/ipython/ipython/blob/main/IPython/core/magics/namespace.py#L275
            return not k.startswith('_') and not (k in hidden_scope and not is_local(k))

        variables = builtins.sorted(builtins.filter(valid_keys, curr_scope.keys()))
        dataframe_vars = {d: curr_scope[d] for d in variables}
        dataframes_with_metadata = []
        for v in variables:
            df_type = builtins.type(dataframe_vars[v])
            if df_type not in supported_dataframe_types and not is_fallback_supported(dataframe_vars[v]):
                continue
            dtype = supported_dataframe_types[df_type] if df_type in supported_dataframe_types else "unknown"
            dataframes_with_metadata.append({
                "variableName": v,
                "type": dtype,
                "supportedEngines": ["pandas"],
                "isLocalVariable": is_local(v),
                "rawType": ".".join([df_type.__module__, df_type.__name__])
            })

    builtins.print(json.dumps(dataframes_with_metadata))

try:
    __DW_GET_DF_VARS__()
finally:
    del __DW_GET_DF_VARS__
23:07:44.503 [trace] Execution Id:ms-toolsai.datawrangler-2. Start Code execution.
23:07:44.503 [trace] Execution Id:ms-toolsai.datawrangler-2. Send code for execution.
23:07:44.503 [trace] Execution Id:ms-toolsai.datawrangler-2. Execution Request Sent to Kernel.
23:07:44.517 [trace] Execution Id:ms-toolsai.datawrangler-2. Executed successfully.
23:07:44.517 [debug] Execution of code ms-toolsai.datawrangler-2 completed in 14ms
23:07:44.525 [trace] Queue code ms-toolsai.datawrangler-3 from ms-toolsai.datawrangler after 0ms:

23:07:44.525 [trace] Execution Id:ms-toolsai.datawrangler-3. Start Code execution.
23:07:44.525 [trace] Execution Id:ms-toolsai.datawrangler-3. Send code for execution.
23:07:44.525 [trace] Execution Id:ms-toolsai.datawrangler-3. Execution Request Sent to Kernel.
23:07:44.529 [trace] Execution Id:ms-toolsai.datawrangler-3. Executed successfully.
23:07:44.530 [debug] Execution of code ms-toolsai.datawrangler-3 completed in 5ms
23:07:44.568 [debug] Jupyter completion time: 8
23:07:44.569 [debug] Execution of code ms-toolsai.jupyter-8 completed in 9ms
23:07:44.633 [trace] Queue code ms-toolsai.datawrangler-4 from ms-toolsai.datawrangler after 0ms:

23:07:44.633 [trace] Execution Id:ms-toolsai.datawrangler-4. Start Code execution.
23:07:44.633 [trace] Execution Id:ms-toolsai.datawrangler-4. Send code for execution.
23:07:44.633 [trace] Execution Id:ms-toolsai.datawrangler-4. Execution Request Sent to Kernel.
23:07:44.638 [trace] Execution Id:ms-toolsai.datawrangler-4. Executed successfully.
23:07:44.638 [debug] Execution of code ms-toolsai.datawrangler-4 completed in 5ms
23:07:44.644 [trace] Queue code ms-toolsai.datawrangler-5 from ms-toolsai.datawrangler after 0ms:

23:07:44.644 [trace] Execution Id:ms-toolsai.datawrangler-5. Start Code execution.
23:07:44.644 [trace] Execution Id:ms-toolsai.datawrangler-5. Send code for execution.
23:07:44.644 [trace] Execution Id:ms-toolsai.datawrangler-5. Execution Request Sent to Kernel.
23:07:44.648 [trace] Execution Id:ms-toolsai.datawrangler-5. Executed successfully.
23:07:44.648 [debug] Execution of code ms-toolsai.datawrangler-5 completed in 4ms
23:07:44.882 [debug] Execution of code ms-toolsai.jupyter-9 completed in 10ms
23:07:44.882 [debug] Jupyter completion time: 10
23:07:45.110 [trace] Inspecting code pd.ArrowDtype
23:07:45.140 [debug] Inspected code pd.ArrowDtype in 30ms
23:07:45.146 [debug] Execution of code ms-toolsai.jupyter-10 completed in 36ms
23:07:45.279 [trace] Inspecting code pd.DataFrame
23:07:45.287 [debug] Inspected code pd.DataFrame in 8ms
23:07:45.289 [debug] Execution of code ms-toolsai.jupyter-11 completed in 10ms
23:07:49.689 [debug] KernelProcess Exited 9896, Exit Code -<PHONE_NUMBER>
23:07:49.689 [error] Disposing session as kernel process died ExitCode:<PHONE_NUMBER>, Reason:
23:07:49.689 [debug] Dispose Kernel process 9896.
23:07:49.692 [debug] Disposed Kernel process 9896.
23:07:49.693 [trace] Start cell 1 execution @<PHONE_NUMBER>992
23:07:49.723 [trace] Cell 1 completed in -1733843260.992s (start:<PHONE_NUMBER>992, end: undefined)
23:07:49.768 [debug] Code execution cancelled by extension ms-toolsai.jupyter
23:07:49.768 [debug] Code execution cancelled by extension ms-toolsai.jupyter
23:07:49.768 [debug] Jupyter completion time: 108

Coding Language and Runtime Version
Python v3.10.15 or Python v3.11.10
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
None

https://github.com/user-attachments/assets/bd5a1033-df48-4523-bf3c-ed1b292bff51

Please can you disable the datawrangler  extension and see if this issue repros?

Please can you disable the datawrangler extension and see if this issue repros?

This issue still occurs when I disable the DataWrangler.

If I import pandas but haven't run the code yet, Pylance takes about 3-5 seconds to show suggestions after typing a dot (.) following pd.DataFrame() or pd.Series(). But, the jupyter kernel still crashes when I disable the Pylance.

Please can you try to disable the following setting (i.e. un-tick it)
let me know if that works.

Please can you try to disable the following setting (i.e. un-tick it)
let me know if that works.

Great! This issue has been resolved. It works well. Thank you!


Opening task analytics or quality control pages adds an extra visit in page history

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce

Open task analytics page using the task actions menu button
The .../analytics page will be opened
The .../analytics#overview will be opened

The same for quality control. This adds a confusing extra action when you're trying to return back in the browsing history, using the standard browser elements/keybinds.
Expected Behavior
The previous page opens in 1 "back" click in the browser.
Possible Solution
No response
Context
No response
Environment
No response

Hey @zhiltsov-max
I reproduced the bug. Could you assign this issue to me?


Add path2root

Adds a function to get the VfsRoot for a given path (if any). Needed for my OUT_DIR work over in the main rust-analyzer repo

Updated to use find. The correct course of action seems to be to figure out how to add a new vfs root on the fly for each out_dir over in rust-analyzer/rust-analyzer#3582

bors r+

Yeah, I am not sure what we need to do here on the high-level. I have plans for replacing ra_vfs completely with https://docs.rs/watchman_client/0.5.0/watchman_client/.
For the time being, I think its ok to implement work-arounds even if they don't fit the current architecture nicely.

publised as 0.5.3

The correct course of action seems to be to figure out how to add a new vfs root on the fly for each out_dir over in rust-analyzer/rust-analyzer#3582

I think, with the current architecture, it is probably best to run cargo check once at the start of the main loop to learn about out dir. Ie, we have a flag, disabled by default, which will block main loop until cargo check is run once.
At this moment, I don't know what long-term solution do we want. I really need to look closely into watchman_client....

@matklad Okay! That sounds reasonable, and a lot simpler to implement for now. Will get working on it :)


Serializationrework

Hi!
My main comment on https://github.com/duckdb/duckdb/pull/8156 was better expressed as code plus I wanted to give it a try, so here a PR on a PR.
Basically I feel a bit uneasy about exposing the default constructors publicly, since I fear it will lead to stuff like vector<SomeClass> v(100); being used, leading to potentially hard to spot bugs around logically not fully initialised instances + adds complexity when reasoning around the class.
I think one problem that led to going with public was that make_uniq that would need to be a member (defeating the purpose), so I guessed that skipping make_uniq and substituting with its implementation should do the trick.

Thanks! Good idea for sure


Markdown converts embed HTML into non-usable HTML

This:
<embed type="text/html" src="https://example.com/" width="100%" height="100%">

gets converted into this (when rendered on the page):

 <embed type="text/html" src="https://example.com/" width="100%" height="100%">

making the embed tag unusable. Is there are any way to stop this from happening?

I can't seem to replicate this:
>>> markdown.markdown('<embed type="text/html" src="https://example.com/" width="100%" height="100%">')
'
<embed type="text/html" src="https://example.com/" width="100%" height="100%">
'

Which version are you using?

@waylan I'm using version 3.2.
I'm django for the project and have the following displaying the markdown:
{{ page.text | escape | markdown | safe }}
with page.text being the variable holding the text.

Never

@Smudger1 I assume you closed this because you worked out that either the escape or safe Django filters were the cause of the problem.


refactor (client): Move out of react build

ID-518
WIP. Do not merge.
Problem statement:
The React is imported even though only the API client is needed. This unnecessarily increases the bundle load on the importing package.
Solution:
Moving the API client to its own subpath similar to React.
Testing
Testing yet to be done.
Breaking change
Yes
TODO

Rename client to something more meaningful.
Import and test /react and /client separately.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 9.329%

Totals

Change from base Build<PHONE_NUMBER>2:
0.0%

Covered Lines:
10115

Relevant Lines:
108420

💛  - Coveralls

@rsbh Did a basic round of testing. Can you please go through on your end also as this might be a breaking change?


Implement the module linking proposal in Wasmtime

I plan to use this as a tracking issue for the module linking proposal in Wasmtime. I'll be updating this description over time as I find time and as work is done:

[x] Implement in wasm-tools (validation, text, binary, etc) https://github.com/bytecodealliance/wasm-tools/pull/26, https://github.com/bytecodealliance/wasm-tools/pull/30, https://github.com/bytecodealliance/wasm-tools/pull/38, https://github.com/bytecodealliance/wasm-tools/pull/40, ...
[ ] Update wasmparser used by Wasmtime to understand module linking https://github.com/bytecodealliance/wasmtime/pull/2059
[ ] Initial groundwork for compiling many modules at once https://github.com/bytecodealliance/wasmtime/pull/2093
[ ] Implement the alias section
[ ] Implement the instance section
[ ] Implement module export/import
[ ] Implement instance export/import
[ ] Ensure the Rust API exposes module linking well
[ ] Implement module linking in the C API
[ ] Implement module linking for one of wasmtime-{go,dotnet,py}

Implementation Notes
Some miscenalleous notes on the implementation and how this is being implemented:

Per-module data structures are intended to continue to be per-module, only wasmtime::Module will internally have a list of modules to select from.
Aliases are expected to be implemented under the hood as imports.

It's expected that instantiation will pass in a Resolver for the actual imports, as well as the "surrounding environment" which is probably "the list of all other modules that came from the original wasm file".
JIT code will call an aliased function from an imported instance as if it were an imported function. (similar for tables/globals/etc)

Open questions:

What should wasm2obj do for multi-module wasm files?
What should the runtime representation in wasmtime-jit be for imported instances and imported modules?

Update wasmparser used by Wasmtime to understand module linking

It seems like this is done?

Indeed!

Ok this is all done now so I'm going to close this. I'm still wading through fuzz bugs at this point but the bulk of it is all there!


Update formatters to V2 and add item duration to test report

Solves https://github.com/codewars/hspec-formatters-codewars/issues/2

I tried to compose assertion messages in a way closes to default HSpec reposter as possible:


A call to SSPI failed, see inner exception

Hello -
I am trying to make a Explicit SSL request to my UNIX based ftpd.
                conn.EncryptionMode = FtpEncryptionMode.Explicit;
                conn.SslProtocols = SslProtocols.Tls12;

I receive the exception "A call to SSPI failed, see inner exception"
The ftp server logs give me this :
 Failed TLS negotiation on control channel, disconnected. (SSL_accept(): (1) error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher)
Any insight you can provide would be greatly appreciated!

Didnt read Documentation, Going to try that first :)

I followed this post:
[](http://stackoverflow.com/questions/13697230/ssl-stream-failed-to-authenticate-as-client-in-apns-sharp as mentioned in the documentation.)
I generated my own PFX cert, and registered it like so:

Despite all this, I am getting exactly what you outlined in the docs
Exception: "A call to SSPI failed, see inner exception."

 Inner Message = "The message received was unexpected or badly formatted"

Any help would be greatly appreciated.
PS: I have a working POC of your application with SOCKS5 support. Look out for it once I tidy it up!
Here is my config settings:
                conn.Credentials = new NetworkCredential(SizzrUser, SizzrPass);
                conn.DataConnectionType = FtpDataConnectionType.PASV;
                conn.EncryptionMode = FtpEncryptionMode.Explicit;
                conn.SocketPollInterval = 5000;

                conn.Host = SiIp;
                conn.Port = SiPort;
                conn.ValidateCertificate += (control, e) => {
                    e.Accept = true;
                };

I don't have an SSL FTP test server setup. Perhaps you can share credentials to yours (if its a test server) via email, or send me a guide to setting it up on whichever OS it works best? Currently I'm using Windows 7 x64 and have no Unix box nearby.

What is your Email? I have a test server, But id rather not post it publicly :)

Here you go
IP: <IP_ADDRESS>
Port: 6446
User hgupta
Pass: 6K8CtuKU
From: Harsh Gupta<EMAIL_ADDRESS>Sent: Friday, November 18, 2016 3:14 AM
To: hgupta9/FluentFTP<EMAIL_ADDRESS>Cc: zharris6<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [hgupta9/FluentFTP] A call to SSPI failed, see inner exception (#9)
I don't have an SSL FTP test server setup. Perhaps you can share credentials to yours (if its a test server) via email, or send me a guide to setting it up on whichever OS it works best? Currently I'm using Windows 7 x64 and have no Unix box nearby.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/hgupta9/FluentFTP/issues/9#issuecomment-261473233 , or mute the thread https://github.com/notifications/unsubscribe-auth/AGS2cWHLzk2BbcAVUiYSOO5nVj6uVHEkks5q_V5UgaJpZM4K1-tl .  https://github.com/notifications/beacon/AGS2cXCNLRL8kGtOvigRYoxQMef1Fxpwks5q_V5UgaJpZM4K1-tl.gif

Sent

This worked fine with the same server, last week. The server hasen't changed.
I don't understand why. Maybe I am missing a setting i had before? Or something with my certs?

I was able to solve this by totally by passing MS SSPI.
After days and days of trying every cert known to man, I am starting to think it is a bug with SSPI and newer /stronger CERTS.
I implemented OpenSSL and was able to log in fine.
If you would like more information, please let me know.
I would be happy to keep testing SSPI, however, if it will benefit others.
Also i can try to impliment OpenSSL handshakes into FluentFTP if there is a need.

I lost you. You "implemented OpenSSL"? I don't understand what's going on.

I Implemented this package:
https://github.com/openssl-net/openssl-net
For whatever reason, SSPI cannot successfully authenticate with my server.
My guess is because the UNIX based server, that is using OpenSSL for its negotiation.
I am really not 100% sure.
Have you had a chance to try the test server I setup?

No, not yet. Maybe later this week or next week. If its a specialized use case then I'd prefer not testing it.

Hi @zharris6,
Could you show an example of how you implemented the package openssl-net.
https://github.com/openssl-net/openssl-net

I am several versions behind at this point. But here is the ActivateEncrpytion method using https://github.com/openssl-net/openssl-net.  For the record, I do not believe a Linux/Unix based server using OpenSSL is a specialized use case at all.
   public void ActivateEncryption(string targethost, X509CertificateCollection clientCerts, SslProtocols sslProtocols)
       {
           if (!IsConnected)
               throw new InvalidOperationException("The FtpSocketStream object is not connected.");

           if (m_netStream == null)
               throw new InvalidOperationException("The base network stream is null.");

           if (m_sslStream != null)
               throw new InvalidOperationException("SSL Encryption has already been enabled on this stream.");

           try
           {
               DateTime auth_start;
               TimeSpan auth_time_total;

               m_sslStream = new OpenSSL.SSL.SslStream(NetworkStream, true, null, null);

               auth_start = DateTime.Now;

               OpenSSL.X509.X509List asd = new OpenSSL.X509.X509List();

               OpenSSL.X509.X509Certificate cert1 = new OpenSSL.X509.X509Certificate();

               OpenSSL.X509.X509Chain chan = new OpenSSL.X509.X509Chain();

               OpenSSL.X509.X509Certificate cert = new OpenSSL.X509.X509Certificate();

               chan.Add(cert);

               asd.Add(cert1);
               m_sslStream.AuthenticateAsClient(targethost, asd, chan, OpenSSL.SSL.SslProtocols.Default, OpenSSL.SSL.SslStrength.All, false);

               auth_time_total = DateTime.Now.Subtract(auth_start);
               FtpTrace.WriteLine("Time to activate encryption: {0}h {1}m {2}s, Total Seconds: {3}.",
                   auth_time_total.Hours,
                   auth_time_total.Minutes,
                   auth_time_total.Seconds,
                   auth_time_total.TotalSeconds);
           }
           catch (AuthenticationException ex)
           {
               // authentication failed and in addition it left our
               // ssl stream in an unsuable state so cleanup needs
               // to be done and the exception can be re-thrown for
               // handling down the chain.
               Close();
               throw ex;
           }
       }

Thank you @zharris6 , when I arrive at the company I will test.

I'm looking for more information with this issue;
There's still a plethora of companies running windows 7 on their devices where SSPI is having issues with tls 1.2. I'm at the point where I have to circumvent SSPI all together because the companies can't/won't upgrade the systems.
I'm looking to either use https://www.nuget.org/packages/System.Security.Cryptography.OpenSsl/ because of maintainability, but at this point i'll take anything that works.


After 1.66 update scroll speed is faster

After i have done 1.66 update using MacBook Pro M1 Max trackback noticed that in code window scrolling is faster.
Version: 1.66.0
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.4.0

Yes, I just updated and immediately noticed this as well

/gifPlease

@deepak1556 explain to me how you expect me to provide screenshot or something when this is about scrolling? Maybe please try to understand the issue first before just randomly slapping bot

Here is a very unscientific comparison:
Version 1.65
https://user-images.githubusercontent.com/67158575/161089527-a9bf58a1-6297-4052-8edb-2e7d539315f2.MOV
Version 1.66
https://user-images.githubusercontent.com/67158575/161089944-b2a7d8f7-b930-4a93-ac2f-d42420dd7656.MOV

Can you follow the steps below for both 1.66 and 1.65 and attach the generated profile,

Run Developer: Toggle Developer Tools from the command palette
Go the Performance tab
Click the record button or Cmd+E
Perform the scrolling
Stop the recording

For now, you could set the "editor.mouseWheelScrollSensitivity" to (or below) 0.5 to slow down the scrolling speed.

+1, noticing this, too.

For now, you could set the "editor.mouseWheelScrollSensitivity" to (or below) 0.5 to slow down the scrolling speed.
Also:
workbench.list.mouseWheelScrollSensitivity
terminal.integrated.mouseWheelScrollSensitivity

This option works, but it doesn't feel smooth.
Especially on 120Hz MacBook, after reduce the mouseWheelScrollSensitivity, the frame rate of the scrolling screen is significantly reduced. 🤨
Hope that VS Code can fix this issue instead of letting users manually change this sensitivity option.

I also noticed that after updating the 1.66 version, the scrolling code is faster than before, not so smooth

The same issue here for MacBook

It would be helpful if anyone facing this issue can provide the logs mentioned in https://github.com/microsoft/vscode/issues/146403#issuecomment-1084795587, otherwise the issue cannot move forward with identifying the root cause.

Sorry but just going to say, this is typical Indian Customer Service response... only following the script. A lot of people are facing this, so why cant you just ask the creators if they have same issue is being me.

Even after lowering the mouseWheelSensitivity setting the rocket speed scrolling remains with jupyter notebooks in VS Code.
Also, the same applies to all the tabs (Explorer, Extensions, etc.)

@KristianBalaj for me when i lowered the setting it did help, i'm using 0.7 and feels ok, but choppy because not 120hz smooth as it was before but i can live with that

I have this setting lowered to 0.4, but it really does not feel like it felt before the update.
I've modified only the Editor: mouseWheelScrollSensitivity and it works only in a classical editor - not even with the jupyter notebooks.

@deepak1556
Here is the profile.
At first I've scrolled in the editor (classic text file) and then I've scrolled in the Explorer.
https://easyupload.io/7dt5ws

Here is a very unscientific comparison:
Version 1.65
1.65.mp4
Version 1.66
1.66.mp4

Hi all, here's a simpler reproduction.
On 1.65.2, scrolling down once on the scroll wheel moves the screen by 9 lines:
https://user-images.githubusercontent.com/3344958/161851371-7628cee8-4aa0-4b1f-8c38-a24d96348c21.mp4
1.65.2.json.zip
On 1.66.0, scrolling down once on the scroll wheel moves the screen by 18 lines:
https://user-images.githubusercontent.com/3344958/161851395-428c4dda-1774-45f7-b0e4-38175ed4fe3d.mp4
1.66.0.json.zip
I'm guessing whatever issue is affecting the scroll wheel is also affecting the trackpad.
@deepak1556 I've attached recordings of both 1.65.2 and 1.66.0.

Thanks for the traces @bmalehorn , I don't see any difference in the smooth scrolling stack traces /cc @alexdima has there been any changes in core with scrolling code path ? Although I do notice the number of idle frames are different between 1.65 and 1.66 for the same test, I think this should be addressed with https://github.com/electron/electron/pull/33618. Will check back on this once we update to Electron 17.4.0
@bmalehorn can you perform one more test and see if the issue repros with https://vscode.dev/ with same workspace settings.

Can anyone check if the issue persists with latest insiders https://code.visualstudio.com/insiders that comes with a newer version of the runtime which contains the fix linked in https://github.com/microsoft/vscode/issues/146403#issuecomment-1089703207

Can anyone check if the issue persists with latest insiders https://code.visualstudio.com/insiders that comes with a newer version of the runtime which contains the fix linked in #146403 (comment)

@deepak1556 on the latest insiders 1.67, scrolling down once still scrolls the screen by 18 lines:
https://user-images.githubusercontent.com/3344958/162499111-23042d17-c682-4798-b444-1e01557aad16.mp4
It probably wouldn't be too hard to reproduce this issue if you have a mouse lying around, or some way of simulating a mouse scroll input.

@bmalehorn thanks for testing, the fix in 17.4.0 was a backport from newer chromium versions and will not have affect your scenario since you were also able to repro with stable chrome on vscode.dev. I will follow up on the scroll wheel issue.
It would be great to confirm, if others seeing the issue on M1 macs are still able to repro with latest insiders ?

I'm also still seeing the issue on the latest Insiders build on an M1 Mac @deepak1556 👍
Version: 1.67.0-insider
Commit: b84feecf9231d404a766e251f8a37c730089511b
Date: 2022-04-11T05:29:24.197Z
Electron: 17.4.0
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.4.0

Don't believe it's specific to M1, I have a regular pro and have this problem.

@deepak1556  have you carried out any testing from your end, are you able to replicate?

The issue also still occurs for me in the Insider build on an Intel Mac.
Version: 1.67.0-insider
Commit: b84feecf9231d404a766e251f8a37c730089511b
Date: 2022-04-11T05:16:55.090Z
Electron: 17.4.0
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 21.4.0

If I move the window to external display (just a regular 1080p), then the behavior is as expected (the same is true for 1.66).

Interesting, I'm using a 4K external display scaled to 1440p and see the fast scrolling issue.
If I set the resolution to unscaled 4K, scrolling seems fine in 1.66 and 1.67.

Thanks @klanchman @stodan that might hint the underlying issue, can you also confirm the value for following vscode settings
"editor.smoothScrolling"
"window.zoomLevel"

Also, from the terminal, run the following
> system_profiler SPDisplaysDataType | grep Resolution
> /usr/libexec/PlistBuddy -c "Print DisplayAnyUserSets:0:0:UnmirroredWidth" -c "Print DisplayAnyUserSets:0:0:UnmirroredHeight" /Library/Preferences/com.apple.windowserver.plist

@alexdima with chromium 98, https://bugs.chromium.org/p/chromium/issues/detail?id=716231 ensures devicePixelRatio is affected by zoom level on macOS as well. It is very likely we need https://github.com/microsoft/vscode/commit/1d8fdcab15cda8c46c640c037777b56b1d7c08f7 to address this issue.

Thanks for looking into this @deepak1556.
I have defaults for the config (smoothScrolling disabled, zoom 0), no noticeable changes after enabling smoothScrolling (using trackpad no mouse).
> system_profiler SPDisplaysDataType | grep Resolution
          Resolution: 3024 x 1964 Retina
          Resolution: 1920 x 1080 (1080p FHD - Full High Definition)

I don't have the specified plist, but I guess you are looking for this:
> /usr/libexec/PlistBuddy -c "Print" /Library/Preferences/com.apple.windowserver.displays.plist
... snip ...
            Array {
                Dict {
                    UnmirrorInfo = Dict {
                        IsLink = false
                        High = 1.000000
                        OriginY = 0.000000
                        Scale = 1.000000
                        OriginX = 0.000000
                        Depth = 4
                        Wide = 1.000000
                        Rotation = 0
                        Hz = 60.000000
                    }
                    UUID = 37D8832A-2D66-02CA-B9F7-8F30A301B230
                    Rotation = 0.000000
                    CurrentInfo = Dict {
                        IsLink = false
                        High = 982.000000
                        OriginY = 0.000000
                        Scale = 2.000000                <---------- this is interesting
                        OriginX = 0.000000
                        Depth = 8
                        Wide = 1512.000000
                        Rotation = 0
                        Hz = 120.000000
                    }
                }
                Dict {
                    UnmirrorInfo = Dict {
                        IsLink = false
                        High = 1.000000
                        OriginY = 0.000000
                        Scale = 1.000000
                        OriginX = 0.000000
                        Depth = 4
                        Wide = 1.000000
                        Rotation = 0
                        Hz = 60.000000
                    }
                    UUID = 0DE77A5A-6133-42DC-B595-6F86F09B5D30
                    Rotation = 0.000000
                    CurrentInfo = Dict {
                        IsLink = false
                        High = 1080.000000
                        OriginY = -1080.000000
                        Scale = 1.000000
                        OriginX = -203.000000
                        Depth = 4
                        Wide = 1920.000000
                        Rotation = 0
                        Hz = 63.000000
                    }
                }
            }

@deepak1556 I've also got zoom level 0 and smooth scrolling disabled.
System profiler:
$ system_profiler SPDisplaysDataType | grep Resolution
          Resolution: 5120 x 2880 (5K/UHD+ - Ultra High Definition Plus)
          Resolution: 3456 x 2234 Retina

Plist entry for built-in MacBook monitor:
$ /usr/libexec/PlistBuddy -c "Print DisplayAnyUserSets:Configs:0:0:UnmirrorInfo:Wide" -c "Print DisplayAnyUserSets:Configs:0:0:UnmirrorInfo:High" /Library/Preferences/com.apple.windowserver.displays.plist
1728.000000
1117.000000

Plist entry for external monitor (scaled resolution like I normally use it):
$ /usr/libexec/PlistBuddy -c "Print DisplayAnyUserSets:Configs:0:1:UnmirrorInfo:Wide" -c "Print DisplayAnyUserSets:Configs:0:1:UnmirrorInfo:High" /Library/Preferences/com.apple.windowserver.displays.plist
2560.000000
1440.000000

Plist entry for external monitor (unscaled resolution):
/usr/libexec/PlistBuddy -c "Print DisplayAnyUserSets:Configs:0:1:UnmirrorInfo:Wide" -c "Print DisplayAnyUserSets:Configs:0:1:UnmirrorInfo:High" /Library/Preferences/com.apple.windowserver.displays.plist
3840.000000
2160.000000

@klanchman @stodan @bmalehorn  can you check if the issue is better with the following build. Once you launch the application, add the setting "update.mode": "none" and continue testing. Ensure that build has following Commit info
Version: 1.67.0-insider (Universal)
Commit: 3e00fca504dce0d2d5d651da7d9e2198b7ba9118
Date: 2022-04-19T18:13:31.957Z
Electron: 17.4.0
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0

@deepak1556 Unfortunately that build still seems to have the same issue for me 😓
Let me know if there's any other info I can grab to help debug!

@deepak1556 The change https://github.com/microsoft/vscode/commit/1d8fdcab15cda8c46c640c037777b56b1d7c08f7 only helps when scrolling using a physical mouse wheel and configuring editor.smoothScrolling.
The background is: we have a setting called editor.smoothScrolling. When set to true, the editor will perform an animation when changing the scroll position using the keyboard (e.g. page up/page down) or when changing the scroll position using a physical mouse wheel. The classifier used there is used to detect if the scroll is done via a physical mouse wheel or via the trackpad. If the scroll is done via the physical mouse wheel, then the editor's animation should kick in, otherwise not, because it looks weird, as the trackpad usually has its own animation and us adding ours on top feels dizzy. That said, the animation itself does not affect in any way the scroll distance.
Given this issue is about the scroll distance and it reproduces without editor.smoothScrolling, I don't think those particular calls to that classifier play any role. I think that the values sent via wheelDeltaX and wheelDeltaY might be different now.

What's the status of this issue? Is there anything I can do to help troubleshoot and move it along?

I can still reproduce this issue in 1.69.0. However, one interesting thing I noticed is the scrolling speed is still normal in the release notes window. Can anyone else reproduce this?

I can still reproduce this issue in 1.69.0. However, one interesting thing I noticed is the scrolling speed is still normal in the release notes window. Can anyone else reproduce this?

You're right, the release notes windows scrolls as smooth as before 1.66.0.
The other windows scroll too fast and if I adjust the speed in settings manually to the old scrolling speed, scrolling becomes choppy and feels unnatural.

I picked up an old project today that I use VS code for and instantly noticed this problem myself. I'm also using M1 MacBook.
Hope this can be resolved soon, but in the meantime I thought I'd leave a tip for others encountering the problem. Setting "editor.mouseWheelScrollSensitivity": 0.3 and "editor.smoothScrolling": true helped a lot. Others hadn't mentioned  smoothScrolling, but I found it was the key as the sensitivity alone didn't feel quite right. I set the sensitivity value kinda arbitrarily, so may be worth fiddling with it get it to preference.
Things feel more natural now, though I don't know how it'd be  for 120hz screens users, and unfortunately, many other areas such as Settings and the file explorer still scroll too fast.

I have the same issue
Version: 1.69.1
Commit: b06ae3b2d2dbfe28bca3134cc6be65935cdfea6a
Date: 2022-07-12T08:21:51.333Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 19.6.0
When the PY or CPP file is opened and currently being rendered in the editor tab, switching between dark+ and light+ themes (daily I'm doing it two times in the morning and evening) makes scrolling in this file tab unresponsive and laggy for few seconds.
https://user-images.githubusercontent.com/7201157/180653725-f8bf788b-7030-4731-b8ad-798eb038c6a3.mov

The default speed of 1.7.3 insider is also too fast

btw, the issue still persists on macos

same behavior: after switching the theme scrolling is unresponsive

Yeah, same for me, interesting that this https://github.com/microsoft/vscode/issues/146403#issuecomment-1179845370 is indeed true:

the scrolling speed is still normal in the release notes window

I am in the totally same situation as https://github.com/microsoft/vscode/issues/146403#issuecomment-1291208559.
For now, I can solve this problem following https://github.com/microsoft/vscode/issues/146403#issuecomment-1189076955. I changed the scroll speed to 0.2 not only for editor(editor.mouseWheelScrollSensitivity) but also workbench(workbench.list.mouseWheelScrollSensitivity) and terminal(terminal.integrated.mouseWheelScrollSensitivity).

@friendship1 is 0.2 an estimate or is that the exact same speed as when scrolling in release notes?

@milosivanovic
To me, empirically, in the editor window, around 0.4 seems to be the closest to a 'release note'.
I just wanted to inform that scroll speed can be adjusted separately not only in editor, but also in terminal and workbench.

M1 MacBook Pro running macOS 13
I tried use Chrome 91/95/97/98/107 to open https://vscode.dev, before chrome 98, scroll speed was normal, but when I use v98 and later, scroll speed become too fast. Same issue was append to other web editors which was using mousewheel Event to scroll.

We've stumbled upon this behavior in RStudio, which recently has moved from Qt to Electron, effectively updating underlying Chromium to v98+ and as @h3110w0r1d-y  pointed out, causing the issue (https://github.com/rstudio/rstudio/issues/11578). RStudio uses Ace (Ajax.org Cloud9 Editor) and was affected in the same way as Monaco editor used by VSC. It was solved by allowing the user to change the scroll speed multiplier, similar to VSC. However, the rest of RStudio was not affected at all. Perhaps it does not utilize mousewheel Event. AFAIK, the GUI is build on Google's GWT. In addition, there is another editor mode resembling jupyter notebook which is built, I believe, on prosemirror and it doesn't suffer from the issue. May be worth exploring.

I have submitted this issue to Chromium.
https://bugs.chromium.org/p/chromium/issues/detail?id=1404833

@h3110w0r1d-y thanks a lot for doing that, it does seem like the issue is with Chromium. As per their reply it seems they're saying the issue still exists in Chrome version 98 whereas you're saying that the issue shouldn't exist there. Not sure why there would be a discrepancy like that. Would you be able to ask them to try version 91 since that's what the last VSCode version was prior to this issue starting?
Version: 1.65.2
Commit: c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1
Date: 2022-03-10T14:42:05.236Z (10 mos ago)
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin arm64 20.6.0

Could this issue be monaco editor issue than VS Code issue? The scrolling seems fine in the web preview windows like the release notes. But in the editors scrolling seems to be a bit clunky on mac.
Checking the front page of monaco https://microsoft.github.io/monaco-editor/ scrolling feels a bit speedy and somewhat augmented. It's not matching other macos programs. It's not precise either (sometimes jumping multiple pixels)
Changing the scroll sensitivity to 0.2 gets it close to the same speed but scroll overall seems to have lost precision

Scroll speed of VS Code on my system (Windows 11) has always been super fast when using two finger scroll.
Here's a video where I scroll twice with the same speed. Mouse Wheel Scroll Sensitivity (editor.mouseWheelScrollSensitivity) needs to be reduced all the way to 0.01 for it to scroll at a normal speed.
https://user-images.githubusercontent.com/85291498/218583492-8d54fe74-62aa-4566-af62-19c9bf290f42.mp4
Here are the specs of the current version of VS Code I have:
Version: 1.75.1 (user setup)
Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf
Date: 2023-02-08T21:32:34.589Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: Yes

How do I change the scroll speed multiplier for Jupyter notebooks? "editor.mouseWheelScrollSensitivity": 0.5 doesn't seem to work for Jupyter.

@NightMachinery There are separate settings, this one is for the editor only (powered by Monaco). Search for "scroll" and it'll come up.

👋
IMO everyone should be directing attention here - all scroll settings (e.g. mouse, trackpad) should be defaulting to the OS
Frankly - to put it politely - a bit perplexed people are posting their own specific scroll speed settings as fixes 🤦
Regards

Quick solution, according to this post https://bugs.chromium.org/p/chromium/issues/detail?id=1404833, the direct solution is to change all scroll sensitivity settings to 0.5, which should bring back the normal scrolling speed. So what I did is: "editor.smoothScrolling": true,   "workbench.list.smoothScrolling": true,   "terminal.integrated.smoothScrolling": true,   "editor.mouseWheelScrollSensitivity": 0.5,   "workbench.list.mouseWheelScrollSensitivity": 0.5,   "terminal.integrated.mouseWheelScrollSensitivity": 0.5, and now the scrolling behaviour seems normal.

Bumping this!
The issue persist
Version: 1.79.2 (Universal)
Commit: 695af097c7bd098fbf017ce3ac85e09bbc5dda06
Date: 2023-06-14T08:58:52.392Z
Electron: 22.5.7
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.5.0

This issues persists in the latest release.
Only by changing scrollsensitivity to 0.5 can the scrolling feel the same as in Chrome or native apps.
Version: 1.81.1
Commit: 6c3e3dba23e8fadc360aed75ce363ba185c49794
Date: 2023-08-09T22:20:33.924Z
Electron: 22.3.18
ElectronBuildId: 22689846
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 22.5.0

I can also confirm that the issue is still present in the latest release (1.81.1), and as first reported by https://github.com/microsoft/vscode/issues/146403#issuecomment-1179845370, the issue does not present itself in the Release Notes tab (viewable at Help > Show Release Notes), where the scrolling feels native and normal.
One thing I don't understand is that if this is an upstream issue with Chromium, why is the Release Notes view not affected? Are we sure that this is truly an upstream Chromium issue?
Version: 1.81.1 (Universal)
Commit: 6c3e3dba23e8fadc360aed75ce363ba185c49794
Date: 2023-08-09T22:20:33.924Z (1 wk ago)
Electron: 22.3.18
ElectronBuildId: 22689846
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.6.0

👋
IMO everyone should be directing attention here - all scroll settings (e.g. mouse, trackpad) should be defaulting to the OS
Frankly - to put it politely - a bit perplexed people are posting their own specific scroll speed settings as fixes 🤦
This issue should be merged/closed
Regards

Although I agree that VS Code should ideally respect and use scroll sensitivity settings across all operating systems, it appears like that is a separate issue. That issue was reported in 1.51.1 and may have been present earlier, while this issue is about a clear change that is documented to have occurred between 1.65 and 1.66.
macOS does not have an option to adjust the scrolling speed/sensitivity of the trackpad, but even if it did and VS Code took it into account, this issue would still exist because for versions 1.66 and above, the scrolling speed in VS Code is approximately double the native scrolling speed in all other applications. So no matter how the OS scroll sensitivity may be configured, VS Code will scroll faster than desired until this is fixed.

@ErikSwan The Release Notes view is not affected because it is a iframe, and the scrolling events are not handled by javascript like scrollableElement.ts. If you pause script execution in devtools, you would find the release notes page is still scrollable but not monaco-scrollable-elements.

@ErikSwan The Release Notes view is not affected because it is a iframe, and the scrolling events are not handled by javascript like scrollableElement.ts. If you pause script execution in devtools, you would find the release notes page is still scrollable but not monaco-scrollable-elements.

Ah, that makes sense. It does indeed seem like this is definitely a bug in Chromium, then. I would encourage everyone to star this issue so that it can be prioritized by the Chromium team:
https://bugs.chromium.org/p/chromium/issues/detail?id=1404833
This won't be fixed in VSCode until it gets fixed upstream by Chromium.

https://bugs.chromium.org/p/chromium/issues/detail?id=1404833 was marked duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=1207308

Should be fixed now in Chromium!

Does vscode have a plan of when to update their electron framework? That fix would need some time to get into electron then eventually vscode...

I also wanna know the upgrade plan timeline

Also would like to know the timeline.  For now, I'm going back to another editor - vscode scrolling feels unnatural.

According to https://github.com/chromium/chromium/commit/99678716b6e3d1985bbcf69e0d6726ce1919a142 the fix was tagged with 118.0.5983.0 so we need to wait for a VS Code version that has an Electron version that has a Chromium version of at least 118.0.5983.0.

Which is Electron 27.0.0-beta.5 and never at the moment.

I have another question, if it is now fixed in chromium, how does the vscode.dev still have its scroll deltas multiplied by ~1.4 compared to normal chrome tabs in the latest chrome canary(120.0.6049.0 at the time of writing)?

Upstream fix for incorrect delta values on hiDPI is now available with https://github.com/microsoft/vscode/commit/12fece34ed49c972d85b1a9ff0f5b8532eea569c
Please check if the issue is resolved with latest insiders https://code.visualstudio.com/insiders

@deepak1556 I can verify that on MacOS builtin HiDPI monitor the scroll is still too fast compared to native apps, or native webview such as release notes that do not use javascript to scroll. As I said in another comment, this is not just a Chrome bug, because vscode.dev scroll speed is still too fast on latest Chrome, and this problem is also present in the ajaxorg/ace web code editor, it is simply too hard to accurately scroll in it.

I tried the latest Insider build, and it feels that the scroll speed is still way too fast.

I can also see that this issue hasn't been fixed. Here's a simple repro:

Go to https://insiders.vscode.dev/ in Chrome
Click the settings cog in the bottom right
Choose Settings in the dropdown which opens a tab with a lot of content
Scroll down and up

The scrolling speed in that settings tab is much faster than this very GitHub issue page that I am commenting on, which is also in Chrome. It is so obviously faster - everyone should be able to tell this difference immediately. I am surprised that after 1.5 years we still haven't been able to figure out exactly what introduced this bug after version 1.66.

@deepak1556 thank you for re-opening but please don't close an issue until people had a chance to test, also really don't think people should test the insiders builds and confirm if its working or not vs public build that most people are using.

I can also see that this issue hasn't been fixed. Here's a simple repro:
1. Go to https://insiders.vscode.dev/ in Chrome

2. Click the settings cog in the bottom left

3. Choose Settings in the dropdown which opens a tab with a lot of content

4. Scroll down and up

The scrolling speed in that settings tab is much faster than this very GitHub issue page that I am commenting on, which is also in Chrome. It is so obviously faster - everyone should be able to tell this difference immediately. I am surprised that after 1.5 years we still haven't been able to figure out exactly what introduced this bug after version 1.66.

My understanding this is upstream issue coming from Electron not vs code specific, but what's strange, dev's or anyone who is working and building vscode not noticed or maybe they did but not mentioned to anyone who is working for vscode.
I will always find these things strange when support staff ask for random reproducible when sometimes that just don't make sense and instead of asking for it why not try yourself and let us know

@alexdima I revisited this bug today and was able to make some progress, here are the highlights from macOS but I believe the issue affects all OS

scroll event from the OS are handled here and processed at WebMouseWheelEventBuilder::Build, side note there is a nice code comment to learn of how values are chosen for continuous scroll vs rest.
Final wheel event data that gets sent to users are processed in blink::WheelEvent::Create
We rely on wheelDeltaY in scroll operations for chromium environments.
Checking the value between step 1 and 2, the value is simply not just multiplied by the TickMultiplier of 120 but also double for my built-in 13 inch retina display
So there is another code path that is actually scaling the event and it was indeed happening at blink::TranslateAndScaleWebInputEvent. It was scaling by the device scale factor
But interesting fact was the bug started with Chromium 98 and this scaling code path did not have any changes in that period which could only mean the device scale factor computation might have changed.
That turned out to be the case, refactor in feature https://bugs.chromium.org/p/chromium/issues/detail?id=716231 which got launched in Chromium 98 adjusted the scale factor of input events which was previously always 1 to the scale factor of the current screen via RenderWidgetHostImpl::SynchronizeVisualProperties
Upstream bugs linked in https://github.com/microsoft/vscode/issues/146403#issuecomment-1697999001 addressed the scaled deltaX, deltaY values by accommodating the window.devicePixelRatio in https://chromium-review.googlesource.com/c/chromium/src/+/4813942 which makes sense based on the above feature (DPR = DSF * user applied zoom for a page) but only downside was the CL didn't adjust the values of wheelDeltaX and wheelDeltaY which are still scaled.

I will follow-up with upstream and make the relevant changes. In the meantime, we can perform the same changes in VSCode by accounting DPR when using wheel deltas.
Slightly related: I see that we are always using the deprecated webkit event branch in chromium browsers, the code path to respect delta mode was introduced in but got later reverted in this commit. Should we reconsider the newer event code path, I am not much familiar with this area but seems WheelDelta values are deprecated so their behavior can break without notice moving forward.

@milosivanovic @hym3242 @netique please check if the issue is resolved with the following version https://insiders.vscode.dev/?vscode-version=d3be6957fd216401450d23817ab52b0f78a7ed7f

@deepak1556 that looks great to me! Thanks so much for finding the time to dive deep into this issue and implement a fix! 🎉

@deepak1556 At the moment, I can tell it is slower that the current vscode.dev.

Just as an FYI: I haven't updated my installed vscode since version 1.65.2 due to this bug, and to me the scrolling in my installed vscode 1.65.2 and the vscode insiders commit posted by @deepak1556 above feel exactly comparable.

@deepak1556 Thank you so much for that informational comment and the valuable time spent on this problem! I can verify on latest chrome on macOS builtin HiDPI display that build of vscode.dev vertically scrolls noticably slower, albeit still feeling a little coarse, i had to change delta multiplier to 0.7 to feel as natural and precise as native. I guess internal event processing may have lost some precision along the way.
By the way, the horizontal scroll events still feel too coarse.

@deepak1556 https://insiders.vscode.dev/?vscode-version=d3be6957fd216401450d23817ab52b0f78a7ed7f this does feel slower but i can't tell if better, tested on Firefox.
on my vscode i have "editor.mouseWheelScrollSensitivity": 0.5 but i think it feels like 0.3

Thanks everyone for testing the build,

By the way, the horizontal scroll events still feel too coarse.

Good catch, I haven't adjust deltaX values in the build.

this does feel slower but i can't tell if better, tested on Firefox.

Oh yeah the change should only be isolated to Chrome, fixed it. Good Catch!

Hope I am not demanding too much, but I want to point out that although the speed is indeed slower, the trackpad scroll accelaration curve still feels somehow a little off.
I draw a graph in graphtoy to showcase:

x is scroll velocity, y is deltaY in pixel, every 'stair' represents a pixel.
Yellow is how macOS and Chrome native feel like, blue is what vscode feels like (both current and the new fixed insider)
Because this difference in acceleration, trying to set the vscode delta multiplier feels like being forced to choose between speed and precision. Increase it, you can scroll across large chunks of text easily but lose the pixel-level precision. Decrease it, you get a similar feel to native when you scroll rather slowly, but lose the ability to "throw" the text far away. As I said, this is analogous to turning off mouse accel after getting used to it -- you simply cannot accurately click on a 5-pixel button, while still being able to throw the cursor all the way to another 27inch monitor.

And again, a million thank you to deepak1556 !

@hym3242 I closed this issue with the fix discussed so far, I have created a follow-up issue for your findings. Can you comment on there on how you ended up deriving the values for the graph, some exact steps to repro would help and editor owners should be able to continue the discussion further.

@deepak1556 just wanted to say thank you! I hadn't noticed an issue with VS Code, but scrolling inside the Monaco editor that's embedded in Google's BigQuery console was driving me crazy. I monkeypatched their editor.js and applied the same changes from your commit and it's made a world of difference.

This bug has been fixed in the latest release of VS Code Insiders!
@MariuzM, you can help us out by commenting /verified if things are now working as expected.
If things still don't seem right, please ensure you're on version 1091f68d834974d78cd4f9769034b4ae4581ff2a of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.
Happy Coding!

Marking verified based on Chris' last comment above ^


v0.19.1 planning (ETA: 2023-12-18, depending on the plan for QEMU v8.2.0)

QEMU v8.2.0 will be released in 2023-12-19: https://wiki.qemu.org/Planning/8.2
If the patches (https://lists.gnu.org/archive/html/qemu-devel/2023-12/msg01694.html ) are not merged as of 2023-12-18, we will have to merge this PR and release Lima v0.19.1.
If the patches can be merged, we can just close this PR.

Originally posted by @AkihiroSuda in https://github.com/lima-vm/lima/pull/2061#discussion_r1426164939

https://github.com/lima-vm/lima/releases/tag/v0.19.1


Problem with integrated terminal font rendering between characters in v1.55.2 as compared to v1.54.x

VS Code Version: 1.55.2
OS Version: Windows 10 Professional 19042.928

Steps to Reproduce:

Set the VS Code integrated terminal to use 'Fira Code' or another powerline enabled font.  I do not see this issue in Windows Terminal using the same font and same SSH host.
Open a terminal that renders lines like that with powerline-go, in my case I was using the "Microsoft Remote - SSH" extension to access a Linux distro-based host that was running powerline-go.

Does this issue occur when all extensions are disabled?: Yes

/duplicate of #120129
Shuld be fixed Insiders build https://code.visualstudio.com/insiders/


chore(depencies): update storybook, babel and caniuse-lite

General summary
Updating the storybook, babel and caniuse-lite  dependencies
Tests:

Test local dev

yarn start
yarn storybook
yarn build

Test CI
Test chromatic deploy
Test alpha release (build & publish process) and test the alpha version has no regression

StoryBook: Deploying...

Testing:

Test local dev

yarn start ✅
yarn storybook ✅
yarn build (build all apps) ✅

Test CI 🚧
Test chromatic deploy 🚧
Test alpha release 🚧

Testing a new alpha version (after #1063 is merge) https://github.com/lumapps/design-system/actions/runs/7420877101

Test OK, no apparent regression on all devtools or on release (tested with all lumapps automated tests)


Install python3 version of supervisor, ditch pip2

This change is

Note: somewhat disappointingly, the debian step still installs python2.


Some duplication of signing functionality

util/signature package seems like a partial duplication of eponymous package in NeoFS API Go module. We need to anchor design: what stays there (signing of stable-marshalers only?) and what we support here in SDK.
@fyrchik pls report ur thoughts about this.

I think SDK can alter api-go functionality in 2 ways:

More convenient/extendable interface (use SDK types, use interfaces for signers) + SDK is simpler to refactor and update.
Adding new private signing schemes for custom installations, which are missing from neofs-api by design. This is where we could implement something like sigutil.RegisterScheme(id, signer).

So, while there is a little duplication I don't like reusing api-go functionality directly. We may export specific helpers for checking signature for each scheme, though.

See also #219.

btw we don't have util/signature anymore, only crypto

Closing according to #219


Where to find the documentation of this chart ?

I am new to Kubernetes and I was able to deploy Airflow via this helm chart. Everything is working smoothly as expected thanks to the creators of this chart. But now I want to pull dags and I don't want them to be pulled each time and want to store them separately in a different volume. These are the basic question to which I hope I will get an answer from the documentation.
Where is the documentation of this chart? is it in there as comments or is it separately managed somewhere else? also where I can get the configuration of my airflow?
Best Regards
Ali

@harvetech all the documentation is stored in the README,  the questions you ask are in the FAQ:

How to set airflow configs?
How to store DAGs?

Thankyou @thesuperzapper


CI: Will uv be faster than eight minutes when omitting --upgrade?

What the title says.

Prepared 234 packages in 8m 45s

It looks like a lot of time is spent downloading or building packages? Maybe some verbose logs would be helpful. That's way longer than I'd expect.

It looks like a lot of time is spent downloading or building packages?

Yes. Building pandas on Python 3.12 ;].
-- https://github.com/crate/academy-fundamentals-course/actions/runs/12188650467/job/34002116111?pr=36


Friendly fire/team damage counter

When enabled in Misc, logs damage done to teammates in the developer console (~).
Example: [ Friendly Fire ] Kills: <2> Damage: <148>
Keeps counting but doesn't log when the option is disabled (prevents desync)
Resets when the match starts, after warmup.
also my vs plugins removed some trailing whitespace
Built status with VC++ / VS2019
Debug x86: Success
Release x86: Success
Download with git clone https://github.com/xAkiraMiura/Osiris.git -b team-damage-indicator

looks cool, could be useful to track team damage / team kills other players on your team commit for griefing purposes as well in the future

I couldn't find a way to reset the variable whenever I join a new match so it only gets cleared at the start of one. This should be fine because you can't join mid-game in competitive but if you join before that you could possibly miss the start event.

would there be a way to make it colored so that you can see it easily in the console? also, do you have to bind a button to it to work or ?

whenever you shoot a teammate with it enabled it will log it to the console. i don't think player_hurt is networked when you shoot your teammates without friendly fire enabled. try going into a bot competitive match and shoot someone. i got it working there.
I know there is a colored varient of memory.debugMsg but i haven't found it.

NICE :D

Does it only show the damage you have done to your allies? Wouldn't it be possible to show others?
Ex: Player But  [ Friendly Fire ] Kills: <0> Damage: <8>
Player Evil  [ Friendly Fire ] Kills: <-2> Damage: <240>

it only shows the damage that has been done in total to teammates, adding it for other players is possible but would require a lot of state management. you could probably make a vector where the index is the player index; you would have to shift it around whenever someone leaves or joins though.
player_hurt is always networked even if someone is dormant i think

hmmmm, I understand.

I know there is a colored varient of memory.debugMsg but i haven't found it.

Now you can use Memory::conColorMsg e.g.
memory.conColorMsg({ 255, 255, 0, 255 }, "ColorTest");

I know there is a colored varient of memory.debugMsg but i haven't found it.

Now you can use Memory::conColorMsg e.g.
memory.conColorMsg({ 255, 255, 0, 255 }, "ColorTest");

Can you help with the code to show the damage caused by the team?
With any example or formula to do?

I couldn't find a way to reset the variable whenever I join a new match so it only gets cleared at the start of one. This should be fine because you can't join mid-game in competitive but if you join before that you could possibly miss the start event.

wouldn't it be nice to create a "reset" button? So whenever you leave a match, you would reset the count.

added a reset counter button in the GUI.
i can't figure out how to rebase commits correctly so i don't have the concolormsg on my version.

YOU ARE THE BEST

@xAkiraMiura  The function is counting the damage done to itself ...
https://imgur.com/8dwxiHf

added a check to prevent counting self damage @Evilhelder

added a check to prevent counting self damage

I saw. Very good.

Now and find a way to count the damage from the rest of the team separately.
Showing nick and total damage ...
Ex:

Here's a tip look for server id/ip/name or whatever for unique identification of server so you can reset when u go to another game and not when you disconnect or have to click on a button.

Here's a tip look for server id/ip/name or whatever for unique identification of server so you can reset when u go to another game and not when you disconnect or have to click on a button.

probably won't change whenever the round ends, i could watch for when isInGame() changes states but then I would be checking every tick rather than just being event driven, leading to slightly worse performance.

I think you can get the info on the players and stuff right after you connected.
If so then check for isConnected && !inGame like in namechanger.

Also moving this to a ui would be easier.

maybe a full imgui playerlist that uses team damage as a column would be the ideal implementation of this

maybe a full imgui playerlist that uses team damage as a column would be the ideal implementation of this

If creating a window with the list of players, you could add "StealName", or "Fake Friendfire" ....

Or even a variation of the "reportbot" to flood only one player ...

FakeFriendly Fire Example:

https://github.com/AimTuxOfficial/AimTux/blob/master/src/ATGUI/Windows/playerlist.cpp
aimtux did an implementation of a playerlist like this

Made in ImGui (alot cleaner and easier to use)
https://youtu.be/ltA4hGhS4bw

Oh i just read the codes. I thought it was something like this.

Oh i just read the codes. I thought it was something like this.

xD. Osiris still working...
CS GO just updated and changed some things in the interface ...

https://youtu.be/z5mhgFVTS2o
An update on my grieving box
https://github.com/danielkrupinski/Osiris/pull/1149

https://youtu.be/z5mhgFVTS2o
An update on my grieving box
#1149

NICE MAN, :D THIS IS BEAUTIFUL..


Better reload alias

alias reload='source ~/.bash_profile' # Reloads session.

I've noticed that if I change .bash_functions or .bash_aliases, and then do a reload, my changes are not noticed.
As a quick fix, this seems to work:
alias reload='source ~/.bash_{profile,aliases,functions}' # Reloads session.

Closed via  89b297a