Markdown cell spontaneously combusts

Applies To

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

What happened?
I was writing in a markdown cell. I expected it to write markdown.
Suddenly, it was filled with json.  It took several of the previous cells, converted them to markdown and dropped them into the active cell.
VS Code Version
Version: 1.86.0 (user setup) Commit: 05047486b6df5eb8d44b2ecd70ea3bdf775fd937 Date: 2024-01-31T10:28:19.990Z Electron: 27.2.3 ElectronBuildId: 26495564 Chromium: 118.0.5993.159 Node.js: 18.17.1 V8: <IP_ADDRESS>-electron.0 OS: Windows_NT x64 10.0.22621
Jupyter Extension Version
v2024.1.2024012502 (pre-release)

Jupyter logs
I'm not sure I captured the output in time. I think it happened between two and three yesterday.

Visual Studio Code (1.86.0, wsl, desktop)
Jupyter Extension Version: 2024.1.2024012502.
Python Extension Version: 2024.0.0.
Pylance Extension Version: 2023.12.1.
Platform: linux (x64).
Workspace folder ~/CDA_6740/CDA_6740_HW2, Home = /home/red
16:14:44.741 [info] Start refreshing Kernel Picker<PHONE_NUMBER>741)
16:14:44.764 [info] Using Pylance
16:14:48.493 [info] End refreshing Kernel Picker<PHONE_NUMBER>741)
16:14:50.361 [info] Start refreshing Kernel Picker<PHONE_NUMBER>361)
16:14:51.127 [info] Starting Kernel startUsingPythonInterpreter, .jvsc74a57bd0f19e134c926254c139edde4123793a0595dad2883afa50a4372a451fc0c5cdc3.~/anaconda3/envs/cda_6740_hw2/python.~/anaconda3/envs/cda_6740_hw2/python.-m#ipykernel_launcher  (Python Path: ~/anaconda3/envs/cda_6740_hw2/bin/python, Conda, cda_6740_hw2, 3.1.0) for '~/CDA_6740/CDA_6740_HW2/Q3.ipynb' (disableUI=true)
16:14:52.932 [info] Process Execution: ~/anaconda3/envs/cda_6740_hw2/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
16:14:52.964 [info] Process Execution: ~/anaconda3/envs/cda_6740_hw2/bin/python -m ipykernel_launcher --f=~/.local/share/jupyter/runtime/kernel-v2-11362777MFcDyT7HWPS.json
    > cwd: ~/CDA_6740/CDA_6740_HW2
16:14:52.965 [info] Kernel process 1136581.
16:14:53.103 [info] Process Execution: ~/anaconda3/envs/cda_6740_hw2/bin/python -m pip list
16:14:53.569 [warn] StdErr from Kernel Process 0.00s - Debugger warning: It seems that frozen modules are being used, which may
0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off
0.00s - to python to disable frozen modules.
0.00s - Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to disable this validation.
16:14:53.937 [warn] Failed to get activated env vars for /bin/python3 in 436ms
16:14:54.115 [info] Process Execution: /bin/python3 -c "import site;print("USER_BASE_VALUE");print(site.USER_BASE);print("USER_BASE_VALUE");"
16:14:54.366 [info] Process Execution: /bin/python3 -m pip list
16:14:54.508 [info] Process Execution: /bin/python3 -c "import pip;print('6af208d0-cb9c-427f-b937-ff563e17efdf')"
16:14:54.679 [info] Process Execution: ~/anaconda3/envs/cda_6740_hw2/bin/python ~/.vscode-server/extensions/ms-toolsai.jupyter-2024.1.2024012502-linux-x64/pythonFiles/printJupyterDataDir.py
16:14:54.811 [warn] sysPrefix was not set for ~/anaconda3/envs/cda_6740_hw2/bin/python
16:14:55.571 [info] End refreshing Kernel Picker<PHONE_NUMBER>361)
16:15:42.205 [info] Start refreshing Interpreter Kernel Picker
16:15:42.205 [info] Start refreshing Kernel Picker<PHONE_NUMBER>205)
16:15:43.227 [info] End refreshing Kernel Picker<PHONE_NUMBER>205)
16:16:51.259 [info] Restart requested ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:16:51.261 [info] Dispose Kernel process 1136581.
16:16:51.327 [info] Process Execution: ~/anaconda3/envs/cda_6740_hw2/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
16:16:51.408 [info] Process Execution: ~/anaconda3/envs/cda_6740_hw2/bin/python -m ipykernel_launcher --f=~/.local/share/jupyter/runtime/kernel-v2-1136277B3qIQ4Z630vM.json
    > cwd: ~/CDA_6740/CDA_6740_HW2
16:16:51.408 [info] Kernel process 1137269.
16:16:51.770 [warn] StdErr from Kernel Process 0.00s - Debugger warning: It seems that frozen modules are being used, which may
0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off
0.00s - to python to disable frozen modules.
0.00s - Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to disable this validation.
16:16:51.850 [info] Restarted c2fbb43b-a01d-4e0e-b591-d1013410f1e7
16:16:55.355 [info] Handle Execution of Cells 0,2,3,6,8,11,13,15,16,17,18,19 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:16:55.383 [info] Kernel acknowledged execution of cell 0 @<PHONE_NUMBER>381
16:16:57.342 [info] End cell 0 execution after 1.96s, completed @<PHONE_NUMBER>341, started @<PHONE_NUMBER>381
16:16:57.356 [info] Kernel acknowledged execution of cell 2 @<PHONE_NUMBER>356
16:16:57.477 [info] End cell 2 execution after 0.121s, completed @<PHONE_NUMBER>477, started @<PHONE_NUMBER>356
16:16:57.489 [info] Kernel acknowledged execution of cell 3 @<PHONE_NUMBER>489
16:16:57.589 [info] End cell 3 execution after 0.099s, completed @<PHONE_NUMBER>588, started @<PHONE_NUMBER>489
16:16:57.601 [info] Kernel acknowledged execution of cell 6 @<PHONE_NUMBER>601
16:16:58.121 [info] End cell 6 execution after 0.52s, completed @<PHONE_NUMBER>121, started @<PHONE_NUMBER>601
16:16:58.180 [info] Kernel acknowledged execution of cell 8 @<PHONE_NUMBER>180
16:17:01.097 [info] End cell 8 execution after 2.916s, completed @<PHONE_NUMBER>096, started @<PHONE_NUMBER>180
16:17:01.109 [info] Kernel acknowledged execution of cell 11 @<PHONE_NUMBER>108
16:17:01.135 [info] End cell 11 execution after 0.027s, completed @<PHONE_NUMBER>135, started @<PHONE_NUMBER>108
16:17:01.147 [info] Kernel acknowledged execution of cell 13 @<PHONE_NUMBER>146
16:17:01.259 [info] End cell 13 execution after 0.113s, completed @<PHONE_NUMBER>259, started @<PHONE_NUMBER>146
16:17:01.271 [info] Kernel acknowledged execution of cell 15 @<PHONE_NUMBER>271
16:17:01.317 [info] End cell 15 execution after 0.046s, completed @<PHONE_NUMBER>317, started @<PHONE_NUMBER>271
16:17:01.329 [info] Kernel acknowledged execution of cell 16 @<PHONE_NUMBER>328
16:17:01.333 [info] End cell 16 execution after 0.005s, completed @<PHONE_NUMBER>333, started @<PHONE_NUMBER>328
16:17:01.349 [info] Kernel acknowledged execution of cell 17 @<PHONE_NUMBER>349
16:17:01.693 [info] End cell 17 execution after 0.344s, completed @<PHONE_NUMBER>693, started @<PHONE_NUMBER>349
16:17:01.696 [info] End cell 18 execution after 0s, completed @ undefined, started @ undefined
16:17:01.698 [info] End cell 19 execution after 0s, completed @ undefined, started @ undefined
16:17:12.452 [info] Handle Execution of Cells 13 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:17:12.463 [info] Kernel acknowledged execution of cell 13 @<PHONE_NUMBER>463
16:17:12.526 [info] End cell 13 execution after 0.063s, completed @<PHONE_NUMBER>526, started @<PHONE_NUMBER>463
16:18:48.306 [info] Handle Execution of Cells 15 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:18:48.342 [info] Kernel acknowledged execution of cell 15 @<PHONE_NUMBER>341
16:18:48.362 [info] End cell 15 execution after 0.02s, completed @<PHONE_NUMBER>361, started @<PHONE_NUMBER>341
16:19:03.739 [info] Handle Execution of Cells 16 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:19:03.750 [info] Kernel acknowledged execution of cell 16 @<PHONE_NUMBER>749
16:19:03.754 [info] End cell 16 execution after 0.004s, completed @<PHONE_NUMBER>753, started @<PHONE_NUMBER>749
16:19:12.074 [info] Handle Execution of Cells 15 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:19:12.085 [info] Kernel acknowledged execution of cell 15 @<PHONE_NUMBER>085
16:19:12.101 [info] End cell 15 execution after 0.016s, completed @<PHONE_NUMBER>101, started @<PHONE_NUMBER>085
16:19:35.806 [info] Handle Execution of Cells 14 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:19:35.819 [info] Kernel acknowledged execution of cell 14 @<PHONE_NUMBER>819
16:19:35.831 [info] End cell 14 execution after 0.012s, completed @<PHONE_NUMBER>831, started @<PHONE_NUMBER>819
16:21:10.274 [info] Handle Execution of Cells 16 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:21:10.297 [info] Kernel acknowledged execution of cell 16 @<PHONE_NUMBER>297
16:21:10.895 [warn] Cell completed with errors rd [Error]: name 'nearest_centers' is not defined
    at r.execute (~/.vscode-server/extensions/ms-toolsai.jupyter-2024.1.2024012502-linux-x64/dist/extension.node.js:263:4968) {
  ename: 'NameError',
  evalue: "name 'nearest_centers' is not defined",
  traceback: [
    '\x1B[0;31m---------------------------------------------------------------------------\x1B[0m',
    '\x1B[0;31mNameError\x1B[0m                                 Traceback (most recent call last)',
    'Cell \x1B[0;32mIn[16], line 16\x1B[0m\n' +
      '\x1B[1;32m     12\x1B[0m     \x1B[38;5;28;01mreturn\x1B[39;00m arr[ix, :], ix\n' +
      '\x1B[1;32m     15\x1B[0m points, indices \x1B[38;5;241m=\x1B[39m closest_centers(embedding, centers)\n' +
      '\x1B[0;32m---> 16\x1B[0m \x1B[38;5;28mprint\x1B[39m(nearest_centers)\n',
    "\x1B[0;31mNameError\x1B[0m: name 'nearest_centers' is not defined"
  ]
}
16:21:10.898 [info] End cell 16 execution after 0.597s, completed @<PHONE_NUMBER>894, started @<PHONE_NUMBER>297
16:21:18.240 [info] Handle Execution of Cells 16 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:21:18.259 [info] Kernel acknowledged execution of cell 16 @<PHONE_NUMBER>258
16:21:18.278 [info] End cell 16 execution after 0.02s, completed @<PHONE_NUMBER>278, started @<PHONE_NUMBER>258
16:21:44.333 [info] Handle Execution of Cells 16 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:21:44.341 [info] Kernel acknowledged execution of cell 16 @<PHONE_NUMBER>341
16:21:44.346 [warn] Cell completed with errors rd [Error]: invalid syntax. Perhaps you forgot a comma?<PHONE_NUMBER>.py, line 7)
    at r.execute (~/.vscode-server/extensions/ms-toolsai.jupyter-2024.1.2024012502-linux-x64/dist/extension.node.js:263:4968) {
  ename: 'SyntaxError',
  evalue: 'invalid syntax. Perhaps you forgot a comma?<PHONE_NUMBER>.py, line 7)',
  traceback: [
    '\x1B[0;36m  Cell \x1B[0;32mIn[18], line 7\x1B[0;36m\x1B[0m\n' +
      '\x1B[0;31m    print("Centroids:\\n"centers)\x1B[0m\n' +
      '\x1B[0m          ^\x1B[0m\n' +
      '\x1B[0;31mSyntaxError\x1B[0m\x1B[0;31m:\x1B[0m invalid syntax. Perhaps you forgot a comma?\n'
  ]
}
16:21:44.347 [info] End cell 16 execution after 0.005s, completed @<PHONE_NUMBER>346, started @<PHONE_NUMBER>341
16:22:38.244 [info] Handle Execution of Cells 16 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:22:38.256 [info] Kernel acknowledged execution of cell 16 @<PHONE_NUMBER>256
16:22:38.280 [info] End cell 16 execution after 0.023s, completed @<PHONE_NUMBER>279, started @<PHONE_NUMBER>256
16:23:40.040 [info] Disposing request as the cell (-1) was deleted ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:24:13.907 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:24:13.934 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>934
16:24:14.487 [info] End cell 18 execution after 0.553s, completed @<PHONE_NUMBER>487, started @<PHONE_NUMBER>934
16:26:13.449 [info] Handle Execution of Cells 16 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:26:13.470 [info] Kernel acknowledged execution of cell 16 @<PHONE_NUMBER>469
16:26:13.490 [info] End cell 16 execution after 0.021s, completed @<PHONE_NUMBER>490, started @<PHONE_NUMBER>469
16:27:57.879 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:27:57.908 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>908
16:27:58.351 [info] End cell 18 execution after 0.443s, completed @<PHONE_NUMBER>351, started @<PHONE_NUMBER>908
16:28:10.568 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:28:10.609 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>609
16:28:11.088 [info] End cell 18 execution after 0.479s, completed @<PHONE_NUMBER>088, started @<PHONE_NUMBER>609
16:28:39.299 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:28:39.309 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>308
16:28:39.501 [info] End cell 18 execution after 0.192s, completed @<PHONE_NUMBER>500, started @<PHONE_NUMBER>308
16:28:49.447 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:28:49.462 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>462
16:28:49.572 [info] End cell 18 execution after 0.11s, completed @<PHONE_NUMBER>572, started @<PHONE_NUMBER>462
16:29:08.085 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:29:08.105 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>105
16:29:08.376 [info] End cell 18 execution after 0.271s, completed @<PHONE_NUMBER>376, started @<PHONE_NUMBER>105
16:29:17.235 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:29:17.261 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>261
16:29:17.360 [info] End cell 18 execution after 0.098s, completed @<PHONE_NUMBER>359, started @<PHONE_NUMBER>261
16:29:23.272 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:29:23.289 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>289
16:29:23.397 [info] End cell 18 execution after 0.108s, completed @<PHONE_NUMBER>397, started @<PHONE_NUMBER>289
16:29:28.306 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:29:28.324 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>323
16:29:28.494 [info] End cell 18 execution after 0.17s, completed @<PHONE_NUMBER>493, started @<PHONE_NUMBER>323
16:29:37.907 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:29:37.923 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>923
16:29:38.059 [info] End cell 18 execution after 0.136s, completed @<PHONE_NUMBER>059, started @<PHONE_NUMBER>923
16:29:46.184 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:29:46.193 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>193
16:29:46.327 [info] End cell 18 execution after 0.133s, completed @<PHONE_NUMBER>326, started @<PHONE_NUMBER>193
16:29:52.121 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:29:52.143 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>142
16:29:52.319 [info] End cell 18 execution after 0.177s, completed @<PHONE_NUMBER>319, started @<PHONE_NUMBER>142
16:30:04.124 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:30:04.140 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>140
16:30:04.297 [info] End cell 18 execution after 0.157s, completed @<PHONE_NUMBER>297, started @<PHONE_NUMBER>140
16:30:09.821 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:30:09.835 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>835
16:30:10.035 [info] End cell 18 execution after 0.2s, completed @<PHONE_NUMBER>035, started @<PHONE_NUMBER>835
16:30:20.916 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:30:20.936 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>935
16:30:21.142 [info] End cell 18 execution after 0.207s, completed @<PHONE_NUMBER>142, started @<PHONE_NUMBER>935
16:30:27.509 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:30:27.530 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>529
16:30:27.736 [info] End cell 18 execution after 0.207s, completed @<PHONE_NUMBER>736, started @<PHONE_NUMBER>529
16:30:42.984 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:30:43.008 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>008
16:30:43.259 [info] End cell 18 execution after 0.25s, completed @<PHONE_NUMBER>258, started @<PHONE_NUMBER>008
16:31:20.866 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:31:20.881 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>881
16:31:21.156 [info] End cell 18 execution after 0.275s, completed @<PHONE_NUMBER>156, started @<PHONE_NUMBER>881
16:31:35.270 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:31:35.312 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>312
16:31:35.556 [info] End cell 18 execution after 0.244s, completed @<PHONE_NUMBER>556, started @<PHONE_NUMBER>312
16:31:57.814 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:31:57.829 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>828
16:31:58.073 [info] End cell 18 execution after 0.244s, completed @<PHONE_NUMBER>072, started @<PHONE_NUMBER>828
16:32:10.704 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:32:10.745 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>745
16:32:10.971 [info] End cell 18 execution after 0.226s, completed @<PHONE_NUMBER>971, started @<PHONE_NUMBER>745
16:32:17.574 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:32:17.591 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>591
16:32:17.833 [info] End cell 18 execution after 0.241s, completed @<PHONE_NUMBER>832, started @<PHONE_NUMBER>591
16:32:28.035 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:32:28.055 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>054
16:32:28.328 [info] End cell 18 execution after 0.274s, completed @<PHONE_NUMBER>328, started @<PHONE_NUMBER>054
16:32:40.779 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:32:40.832 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>832
16:32:41.087 [info] End cell 18 execution after 0.255s, completed @<PHONE_NUMBER>087, started @<PHONE_NUMBER>832
16:32:53.360 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:32:53.370 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>370
16:32:53.667 [info] End cell 18 execution after 0.297s, completed @<PHONE_NUMBER>667, started @<PHONE_NUMBER>370
16:33:13.738 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:33:13.751 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>750
16:33:14.140 [info] End cell 18 execution after 0.39s, completed @<PHONE_NUMBER>140, started @<PHONE_NUMBER>750
16:33:22.054 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:33:22.070 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>070
16:33:22.638 [info] End cell 18 execution after 0.568s, completed @<PHONE_NUMBER>638, started @<PHONE_NUMBER>070
16:33:33.728 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:33:33.750 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>750
16:33:34.066 [info] End cell 18 execution after 0.315s, completed @<PHONE_NUMBER>065, started @<PHONE_NUMBER>750
16:33:48.891 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:33:48.909 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>908
16:33:49.243 [info] End cell 18 execution after 0.334s, completed @<PHONE_NUMBER>242, started @<PHONE_NUMBER>908
16:34:04.096 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:34:04.114 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>114
16:34:04.470 [info] End cell 18 execution after 0.355s, completed @<PHONE_NUMBER>469, started @<PHONE_NUMBER>114
16:34:23.716 [info] Handle Execution of Cells 18 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:34:23.729 [info] Kernel acknowledged execution of cell 18 @<PHONE_NUMBER>729
16:34:23.963 [info] End cell 18 execution after 0.233s, completed @<PHONE_NUMBER>962, started @<PHONE_NUMBER>729
16:34:45.816 [info] Handle Execution of Cells 19 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:34:45.831 [info] Kernel acknowledged execution of cell 19 @<PHONE_NUMBER>831
16:34:46.062 [info] End cell 19 execution after 0.231s, completed @<PHONE_NUMBER>062, started @<PHONE_NUMBER>831
16:34:54.350 [info] Handle Execution of Cells 19 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:34:54.366 [info] Kernel acknowledged execution of cell 19 @<PHONE_NUMBER>366
16:34:54.689 [info] End cell 19 execution after 0.322s, completed @<PHONE_NUMBER>688, started @<PHONE_NUMBER>366
16:35:04.464 [info] Handle Execution of Cells 19 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:35:04.481 [info] Kernel acknowledged execution of cell 19 @<PHONE_NUMBER>480
16:35:04.818 [info] End cell 19 execution after 0.338s, completed @<PHONE_NUMBER>818, started @<PHONE_NUMBER>480
16:35:13.419 [info] Handle Execution of Cells 19 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:35:13.443 [info] Kernel acknowledged execution of cell 19 @<PHONE_NUMBER>443
16:35:13.795 [info] End cell 19 execution after 0.352s, completed @<PHONE_NUMBER>795, started @<PHONE_NUMBER>443
16:39:45.308 [info] No interpreter for Pylance for Notebook URI "~/CDA_6740/CDA_6740_HW2/Q2.ipynb"
16:39:45.335 [info] Starting Kernel startUsingPythonInterpreter, .jvsc74a57bd0f19e134c926254c139edde4123793a0595dad2883afa50a4372a451fc0c5cdc3.~/anaconda3/envs/cda_6740_hw2/python.~/anaconda3/envs/cda_6740_hw2/python.-m#ipykernel_launcher  (Python Path: ~/anaconda3/envs/cda_6740_hw2/bin/python, Conda, cda_6740_hw2, 3.1.0) for '~/CDA_6740/CDA_6740_HW2/Q2.ipynb' (disableUI=true)
16:39:46.823 [info] Process Execution: ~/anaconda3/envs/cda_6740_hw2/bin/python -m pip list
16:39:46.885 [info] Process Execution: ~/anaconda3/envs/cda_6740_hw2/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
16:39:46.957 [info] Process Execution: ~/anaconda3/envs/cda_6740_hw2/bin/python -m ipykernel_launcher --f=~/.local/share/jupyter/runtime/kernel-v2-1136277DX2dSPJ59wh5.json
    > cwd: ~/CDA_6740/CDA_6740_HW2
16:39:46.958 [info] Kernel process 1143112.
16:39:47.499 [warn] StdErr from Kernel Process 0.00s - Debugger warning: It seems that frozen modules are being used, which may
0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off
0.00s - to python to disable frozen modules.
0.00s - Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to disable this validation.
16:40:23.577 [info] Handle Execution of Cells 22 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:40:23.593 [info] Kernel acknowledged execution of cell 22 @<PHONE_NUMBER>593
16:40:23.598 [info] End cell 22 execution after 0.005s, completed @<PHONE_NUMBER>598, started @<PHONE_NUMBER>593
16:40:31.154 [info] Handle Execution of Cells 22 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:40:31.168 [info] Kernel acknowledged execution of cell 22 @<PHONE_NUMBER>168
16:40:31.174 [info] End cell 22 execution after 0.006s, completed @<PHONE_NUMBER>174, started @<PHONE_NUMBER>168
16:41:03.904 [info] Handle Execution of Cells 22 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:41:03.925 [info] Kernel acknowledged execution of cell 22 @<PHONE_NUMBER>925
16:41:03.929 [info] End cell 22 execution after 0.004s, completed @<PHONE_NUMBER>929, started @<PHONE_NUMBER>925
16:41:10.494 [info] Handle Execution of Cells 22 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:41:10.508 [info] Kernel acknowledged execution of cell 22 @<PHONE_NUMBER>508
16:41:10.513 [info] End cell 22 execution after 0.005s, completed @<PHONE_NUMBER>513, started @<PHONE_NUMBER>508
16:41:38.321 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:41:38.334 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>334
16:41:38.965 [warn] Cell completed with errors rd [Error]: name 'll' is not defined
    at r.execute (~/.vscode-server/extensions/ms-toolsai.jupyter-2024.1.2024012502-linux-x64/dist/extension.node.js:263:4968) {
  ename: 'NameError',
  evalue: "name 'll' is not defined",
  traceback: [
    '\x1B[0;31m---------------------------------------------------------------------------\x1B[0m',
    '\x1B[0;31mNameError\x1B[0m                                 Traceback (most recent call last)',
    'Cell \x1B[0;32mIn[60], line 8\x1B[0m\n' +
      '\x1B[1;32m      5\x1B[0m Xc \x1B[38;5;241m=\x1B[39m Xc\x1B[38;5;241m.\x1B[39mT\n' +
      '\x1B[1;32m      6\x1B[0m C \x1B[38;5;241m=\x1B[39m (Xc \x1B[38;5;241m@\x1B[39m Xc\x1B[38;5;241m.\x1B[39mT)\x1B[38;5;241m/\x1B[39mm\n' +
      '\x1B[0;32m----> 8\x1B[0m eigvals, eigvecs \x1B[38;5;241m=\x1B[39m ll\x1B[38;5;241m.\x1B[39meig(C)\n' +
      '\x1B[1;32m      9\x1B[0m eigvals \x1B[38;5;241m=\x1B[39m eigvals\x1B[38;5;241m.\x1B[39mreal\n' +
      '\x1B[1;32m     10\x1B[0m eigvecs \x1B[38;5;241m=\x1B[39m eigvecs\x1B[38;5;241m.\x1B[39mreal\n',
    "\x1B[0;31mNameError\x1B[0m: name 'll' is not defined"
  ]
}
16:41:38.967 [info] End cell 23 execution after 0.631s, completed @<PHONE_NUMBER>965, started @<PHONE_NUMBER>334
16:42:28.346 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:42:28.359 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>358
16:42:28.459 [info] End cell 23 execution after 0.101s, completed @<PHONE_NUMBER>459, started @<PHONE_NUMBER>358
16:42:35.246 [info] Disposing request as the cell (-1) was deleted ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:42:35.246 [info] Disposing request as the cell (-1) was deleted ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:42:35.246 [info] Disposing request as the cell (-1) was deleted ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:42:35.246 [info] Disposing request as the cell (-1) was deleted ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:44:30.442 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:44:30.448 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>448
16:44:30.454 [warn] Cell completed with errors rd [Error]: closing parenthesis ')' does not match opening parenthesis '{'<PHONE_NUMBER>.py, line 1)
    at r.execute (~/.vscode-server/extensions/ms-toolsai.jupyter-2024.1.2024012502-linux-x64/dist/extension.node.js:263:4968) {
  ename: 'SyntaxError',
  evalue: "closing parenthesis ')' does not match opening parenthesis '{'<PHONE_NUMBER>.py, line 1)",
  traceback: [
    '\x1B[0;36m  Cell \x1B[0;32mIn[62], line 1\x1B[0;36m\x1B[0m\n' +
      '\x1B[0;31m    ax = pd.DataFrame({"First Component":dim1, "Second Component":dim2).plot.scatter(x="First Component", y="Second Component", c="black", s=10)\x1B[0m\n' +
      '\x1B[0m                                                                      ^\x1B[0m\n' +
      "\x1B[0;31mSyntaxError\x1B[0m\x1B[0;31m:\x1B[0m closing parenthesis ')' does not match opening parenthesis '{'\n"
  ]
}
16:44:30.454 [info] End cell 23 execution after 0.006s, completed @<PHONE_NUMBER>454, started @<PHONE_NUMBER>448
16:44:42.973 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:44:42.990 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>990
16:44:43.202 [info] End cell 23 execution after 0.211s, completed @<PHONE_NUMBER>201, started @<PHONE_NUMBER>990
16:44:59.179 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:44:59.192 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>191
16:44:59.374 [info] End cell 23 execution after 0.183s, completed @<PHONE_NUMBER>374, started @<PHONE_NUMBER>191
16:45:24.301 [info] Handle Execution of Cells 24 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:45:24.311 [info] Kernel acknowledged execution of cell 24 @<PHONE_NUMBER>310
16:45:24.316 [info] End cell 24 execution after 0.006s, completed @<PHONE_NUMBER>316, started @<PHONE_NUMBER>310
16:45:30.193 [info] Handle Execution of Cells 22 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:45:30.211 [info] Kernel acknowledged execution of cell 22 @<PHONE_NUMBER>210
16:45:31.569 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:45:39.647 [info] End cell 22 execution after 9.437s, completed @<PHONE_NUMBER>647, started @<PHONE_NUMBER>210
16:45:39.652 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>652
16:45:39.806 [info] End cell 23 execution after 0.153s, completed @<PHONE_NUMBER>805, started @<PHONE_NUMBER>652
16:46:43.163 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:46:43.184 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>184
16:46:43.203 [info] End cell 23 execution after 0.019s, completed @<PHONE_NUMBER>203, started @<PHONE_NUMBER>184
16:47:06.539 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:47:06.560 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>560
16:47:06.572 [info] End cell 23 execution after 0.011s, completed @<PHONE_NUMBER>571, started @<PHONE_NUMBER>560
16:47:43.276 [info] Handle Execution of Cells 24 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:47:43.284 [info] Kernel acknowledged execution of cell 24 @<PHONE_NUMBER>283
16:47:43.553 [info] End cell 24 execution after 0.27s, completed @<PHONE_NUMBER>553, started @<PHONE_NUMBER>283
16:48:46.028 [info] Handle Execution of Cells 22 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:48:46.040 [info] Kernel acknowledged execution of cell 22 @<PHONE_NUMBER>040
16:48:46.141 [info] End cell 22 execution after 0.101s, completed @<PHONE_NUMBER>141, started @<PHONE_NUMBER>040
16:49:01.775 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:49:01.792 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>791
16:49:01.828 [info] End cell 23 execution after 0.037s, completed @<PHONE_NUMBER>828, started @<PHONE_NUMBER>791
16:49:10.857 [info] Handle Execution of Cells 24 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:49:10.877 [info] Kernel acknowledged execution of cell 24 @<PHONE_NUMBER>877
16:49:11.099 [info] End cell 24 execution after 0.222s, completed @<PHONE_NUMBER>099, started @<PHONE_NUMBER>877
16:49:43.920 [info] Handle Execution of Cells 22 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:49:43.936 [info] Kernel acknowledged execution of cell 22 @<PHONE_NUMBER>935
16:49:46.034 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:49:48.819 [info] Handle Execution of Cells 24 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:49:54.326 [info] End cell 22 execution after 10.391s, completed @<PHONE_NUMBER>326, started @<PHONE_NUMBER>935
16:49:54.336 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>336
16:49:54.348 [info] End cell 23 execution after 0.012s, completed @<PHONE_NUMBER>348, started @<PHONE_NUMBER>336
16:49:54.357 [info] Kernel acknowledged execution of cell 24 @<PHONE_NUMBER>356
16:49:54.567 [info] End cell 24 execution after 0.211s, completed @<PHONE_NUMBER>567, started @<PHONE_NUMBER>356
16:50:57.047 [info] Handle Execution of Cells 24 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:50:57.061 [info] Kernel acknowledged execution of cell 24 @<PHONE_NUMBER>060
16:50:57.297 [info] End cell 24 execution after 0.237s, completed @<PHONE_NUMBER>297, started @<PHONE_NUMBER>060
16:51:17.772 [info] Handle Execution of Cells 24 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:51:17.807 [info] Kernel acknowledged execution of cell 24 @<PHONE_NUMBER>807
16:51:18.043 [info] End cell 24 execution after 0.236s, completed @<PHONE_NUMBER>043, started @<PHONE_NUMBER>807
16:51:27.254 [info] Handle Execution of Cells 24 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:51:27.272 [info] Kernel acknowledged execution of cell 24 @<PHONE_NUMBER>272
16:51:27.562 [info] End cell 24 execution after 0.289s, completed @<PHONE_NUMBER>561, started @<PHONE_NUMBER>272
16:51:37.250 [info] Handle Execution of Cells 24 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:51:37.265 [info] Kernel acknowledged execution of cell 24 @<PHONE_NUMBER>265
16:51:37.538 [info] End cell 24 execution after 0.273s, completed @<PHONE_NUMBER>538, started @<PHONE_NUMBER>265
16:51:44.561 [info] Handle Execution of Cells 24 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:51:44.575 [info] Kernel acknowledged execution of cell 24 @<PHONE_NUMBER>574
16:51:44.893 [info] End cell 24 execution after 0.319s, completed @<PHONE_NUMBER>893, started @<PHONE_NUMBER>574
16:51:55.394 [info] Handle Execution of Cells 24 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:51:55.405 [info] Kernel acknowledged execution of cell 24 @<PHONE_NUMBER>405
16:51:55.698 [info] End cell 24 execution after 0.293s, completed @<PHONE_NUMBER>698, started @<PHONE_NUMBER>405
16:52:22.454 [info] Handle Execution of Cells 24 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:52:22.468 [info] Kernel acknowledged execution of cell 24 @<PHONE_NUMBER>468
16:52:22.760 [info] End cell 24 execution after 0.292s, completed @<PHONE_NUMBER>760, started @<PHONE_NUMBER>468
16:52:40.483 [info] Handle Execution of Cells 24 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:52:40.504 [info] Kernel acknowledged execution of cell 24 @<PHONE_NUMBER>504
16:52:40.776 [info] End cell 24 execution after 0.271s, completed @<PHONE_NUMBER>775, started @<PHONE_NUMBER>504
16:52:50.131 [info] Handle Execution of Cells 24 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:52:50.172 [info] Kernel acknowledged execution of cell 24 @<PHONE_NUMBER>171
16:52:50.440 [info] End cell 24 execution after 0.269s, completed @<PHONE_NUMBER>440, started @<PHONE_NUMBER>171
16:52:54.420 [info] Disposing request as the cell (-1) was deleted ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:52:54.421 [info] Disposing request as the cell (-1) was deleted ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:52:54.421 [info] Disposing request as the cell (-1) was deleted ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:53:26.325 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:53:26.342 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>341
16:53:26.647 [info] End cell 23 execution after 0.306s, completed @<PHONE_NUMBER>647, started @<PHONE_NUMBER>341
16:53:30.902 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:53:31.132 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>132
16:53:31.420 [info] End cell 23 execution after 0.287s, completed @<PHONE_NUMBER>419, started @<PHONE_NUMBER>132
16:53:39.583 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:53:39.599 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>599
16:53:39.924 [info] End cell 23 execution after 0.324s, completed @<PHONE_NUMBER>923, started @<PHONE_NUMBER>599
16:53:47.186 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:53:47.218 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>218
16:53:47.542 [info] End cell 23 execution after 0.323s, completed @<PHONE_NUMBER>541, started @<PHONE_NUMBER>218
16:54:01.276 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:54:01.299 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>298
16:54:01.657 [info] End cell 23 execution after 0.358s, completed @<PHONE_NUMBER>656, started @<PHONE_NUMBER>298
16:54:07.163 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:54:07.195 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>195
16:54:07.532 [info] End cell 23 execution after 0.337s, completed @<PHONE_NUMBER>532, started @<PHONE_NUMBER>195
16:54:15.352 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:54:15.374 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>373
16:54:15.867 [info] End cell 23 execution after 0.494s, completed @<PHONE_NUMBER>867, started @<PHONE_NUMBER>373
16:54:25.815 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:54:25.830 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>829
16:54:26.228 [info] End cell 23 execution after 0.398s, completed @<PHONE_NUMBER>227, started @<PHONE_NUMBER>829
16:54:30.565 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:54:30.582 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>582
16:54:30.984 [info] End cell 23 execution after 0.401s, completed @<PHONE_NUMBER>983, started @<PHONE_NUMBER>582
16:54:43.284 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:54:43.298 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>297
16:54:43.713 [info] End cell 23 execution after 0.416s, completed @<PHONE_NUMBER>713, started @<PHONE_NUMBER>297
16:54:51.113 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:54:51.138 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>138
16:54:51.563 [info] End cell 23 execution after 0.424s, completed @<PHONE_NUMBER>562, started @<PHONE_NUMBER>138
16:55:02.092 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:55:02.139 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>139
16:55:02.564 [info] End cell 23 execution after 0.425s, completed @<PHONE_NUMBER>564, started @<PHONE_NUMBER>139
16:55:27.589 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
16:55:27.609 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>609
16:55:28.064 [info] End cell 23 execution after 0.454s, completed @<PHONE_NUMBER>063, started @<PHONE_NUMBER>609
16:58:02.129 [info] Disposing request as the cell (-1) was deleted ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
17:02:03.601 [info] Handle Execution of Cells 25 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
17:02:03.626 [info] Kernel acknowledged execution of cell 25 @<PHONE_NUMBER>626
17:02:03.645 [warn] Cell completed with errors rd [Error]: cannot reshape array of size 698 into shape (64,64)
    at r.execute (~/.vscode-server/extensions/ms-toolsai.jupyter-2024.1.2024012502-linux-x64/dist/extension.node.js:263:4968) {
  ename: 'ValueError',
  evalue: 'cannot reshape array of size 698 into shape (64,64)',
  traceback: [
    '\x1B[0;31m---------------------------------------------------------------------------\x1B[0m',
    '\x1B[0;31mValueError\x1B[0m                                Traceback (most recent call last)',
    'Cell \x1B[0;32mIn[99], line 1\x1B[0m\n' +
      '\x1B[0;32m----> 1\x1B[0m plt\x1B[38;5;241m.\x1B[39mimshow(dim1\x1B[38;5;241m.\x1B[39mreshape(\x1B[38;5;241m64\x1B[39m, \x1B[38;5;241m64\x1B[39m)\x1B[38;5;241m.\x1B[39mT, cmap\x1B[38;5;241m=\x1B[39m\x1B[38;5;124m"\x1B[39m\x1B[38;5;124mgray\x1B[39m\x1B[38;5;124m"\x1B[39m, interpolation\x1B[38;5;241m=\x1B[39m\x1B[38;5;124m"\x1B[39m\x1B[38;5;124mantialiased\x1B[39m\x1B[38;5;124m"\x1B[39m)\n',
    '\x1B[0;31mValueError\x1B[0m: cannot reshape array of size 698 into shape (64,64)'
  ]
}
17:02:03.648 [info] End cell 25 execution after 0.018s, completed @<PHONE_NUMBER>644, started @<PHONE_NUMBER>626
17:02:45.587 [info] Handle Execution of Cells 23 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
17:02:45.594 [info] Kernel acknowledged execution of cell 23 @<PHONE_NUMBER>594
17:02:45.605 [info] End cell 23 execution after 0.01s, completed @<PHONE_NUMBER>604, started @<PHONE_NUMBER>594
17:05:03.726 [info] Handle Execution of Cells 0,1,2,4,6,8 for ~/CDA_6740/CDA_6740_HW2/Q2.ipynb
17:05:03.749 [info] Kernel acknowledged execution of cell 0 @<PHONE_NUMBER>748
17:05:05.981 [info] End cell 0 execution after 2.232s, completed @<PHONE_NUMBER>980, started @<PHONE_NUMBER>748
17:05:05.993 [info] Kernel acknowledged execution of cell 1 @<PHONE_NUMBER>992
17:05:06.009 [info] End cell 1 execution after 0.017s, completed @<PHONE_NUMBER>009, started @<PHONE_NUMBER>992
17:05:06.035 [info] Kernel acknowledged execution of cell 2 @<PHONE_NUMBER>035
17:05:06.044 [info] End cell 2 execution after 0.009s, completed @<PHONE_NUMBER>044, started @<PHONE_NUMBER>035
17:05:06.057 [info] Kernel acknowledged execution of cell 4 @<PHONE_NUMBER>056
17:05:06.473 [info] End cell 4 execution after 0.416s, completed @<PHONE_NUMBER>472, started @<PHONE_NUMBER>056
17:05:06.522 [info] Kernel acknowledged execution of cell 6 @<PHONE_NUMBER>522
17:05:06.819 [info] End cell 6 execution after 0.297s, completed @<PHONE_NUMBER>819, started @<PHONE_NUMBER>522
17:05:06.838 [info] Kernel acknowledged execution of cell 8 @<PHONE_NUMBER>838
17:05:06.848 [info] End cell 8 execution after 0.01s, completed @<PHONE_NUMBER>848, started @<PHONE_NUMBER>838
17:06:39.877 [info] Handle Execution of Cells 1 for ~/CDA_6740/CDA_6740_HW2/Q2.ipynb
17:06:39.904 [info] Kernel acknowledged execution of cell 1 @<PHONE_NUMBER>904
17:06:39.910 [info] End cell 1 execution after 0.006s, completed @<PHONE_NUMBER>910, started @<PHONE_NUMBER>904
17:10:15.119 [info] Handle Execution of Cells 11 for ~/CDA_6740/CDA_6740_HW2/Q2.ipynb
17:10:15.159 [info] Kernel acknowledged execution of cell 11 @<PHONE_NUMBER>159
17:10:15.165 [info] End cell 11 execution after 0.005s, completed @<PHONE_NUMBER>164, started @<PHONE_NUMBER>159
17:11:32.425 [info] Handle Execution of Cells 11 for ~/CDA_6740/CDA_6740_HW2/Q2.ipynb
17:11:32.437 [info] Kernel acknowledged execution of cell 11 @<PHONE_NUMBER>437
17:11:32.981 [warn] Cell completed with errors rd [Error]: 'Styler' object has no attribute 'hide_columns'
    at r.execute (~/.vscode-server/extensions/ms-toolsai.jupyter-2024.1.2024012502-linux-x64/dist/extension.node.js:263:4968) {
  ename: 'AttributeError',
  evalue: "'Styler' object has no attribute 'hide_columns'",
  traceback: [
    '\x1B[0;31m---------------------------------------------------------------------------\x1B[0m',
    '\x1B[0;31mAttributeError\x1B[0m                            Traceback (most recent call last)',
    'Cell \x1B[0;32mIn[9], line 2\x1B[0m\n' +
      '\x1B[1;32m      1\x1B[0m df[[\x1B[38;5;124m"\x1B[39m\x1B[38;5;124mCountry\x1B[39m\x1B[38;5;124m"\x1B[39m, \x1B[38;5;124m"\x1B[39m\x1B[38;5;124mGarlic\x1B[39m\x1B[38;5;124m"\x1B[39m]]\x1B[38;5;241m.\x1B[39msort_values(\n' +
      '\x1B[0;32m----> 2\x1B[0m     by\x1B[38;5;241m=\x1B[39m\x1B[38;5;124m"\x1B[39m\x1B[38;5;124mGarlic\x1B[39m\x1B[38;5;124m"\x1B[39m, ascending\x1B[38;5;241m=\x1B[39m\x1B[38;5;28;01mFalse\x1B[39;00m)\x1B[38;5;241m.\x1B[39mT\x1B[38;5;241m.\x1B[39mstyle\x1B[38;5;241m.\x1B[39mhide_columns()\n',
    "\x1B[0;31mAttributeError\x1B[0m: 'Styler' object has no attribute 'hide_columns'"
  ]
}
17:11:32.981 [info] End cell 11 execution after 0.544s, completed @<PHONE_NUMBER>981, started @<PHONE_NUMBER>437
17:11:49.897 [info] Handle Execution of Cells 11 for ~/CDA_6740/CDA_6740_HW2/Q2.ipynb
17:11:49.926 [info] Kernel acknowledged execution of cell 11 @<PHONE_NUMBER>926
17:11:49.932 [warn] Cell completed with errors rd [Error]: 'Styler' object has no attribute 'hide_columns'
    at r.execute (~/.vscode-server/extensions/ms-toolsai.jupyter-2024.1.2024012502-linux-x64/dist/extension.node.js:263:4968) {
  ename: 'AttributeError',
  evalue: "'Styler' object has no attribute 'hide_columns'",
  traceback: [
    '\x1B[0;31m---------------------------------------------------------------------------\x1B[0m',
    '\x1B[0;31mAttributeError\x1B[0m                            Traceback (most recent call last)',
    'Cell \x1B[0;32mIn[10], line 2\x1B[0m\n' +
      '\x1B[1;32m      1\x1B[0m df[[\x1B[38;5;124m"\x1B[39m\x1B[38;5;124mCountry\x1B[39m\x1B[38;5;124m"\x1B[39m, \x1B[38;5;124m"\x1B[39m\x1B[38;5;124mGarlic\x1B[39m\x1B[38;5;124m"\x1B[39m]]\x1B[38;5;241m.\x1B[39msort_values(\n' +
      '\x1B[0;32m----> 2\x1B[0m     by\x1B[38;5;241m=\x1B[39m\x1B[38;5;124m"\x1B[39m\x1B[38;5;124mGarlic\x1B[39m\x1B[38;5;124m"\x1B[39m, ascending\x1B[38;5;241m=\x1B[39m\x1B[38;5;28;01mFalse\x1B[39;00m)\x1B[38;5;241m.\x1B[39mT\x1B[38;5;241m.\x1B[39mstyle\x1B[38;5;241m.\x1B[39mhide_columns()\n',
    "\x1B[0;31mAttributeError\x1B[0m: 'Styler' object has no attribute 'hide_columns'"
  ]
}
17:11:49.933 [info] End cell 11 execution after 0.006s, completed @<PHONE_NUMBER>932, started @<PHONE_NUMBER>926
17:13:19.068 [info] Handle Execution of Cells 11 for ~/CDA_6740/CDA_6740_HW2/Q2.ipynb
17:13:19.081 [info] Kernel acknowledged execution of cell 11 @<PHONE_NUMBER>081
17:13:19.098 [info] End cell 11 execution after 0.016s, completed @<PHONE_NUMBER>097, started @<PHONE_NUMBER>081
17:13:54.675 [info] Handle Execution of Cells 11 for ~/CDA_6740/CDA_6740_HW2/Q2.ipynb
17:13:54.695 [info] Kernel acknowledged execution of cell 11 @<PHONE_NUMBER>695
17:13:54.702 [info] End cell 11 execution after 0.007s, completed @<PHONE_NUMBER>702, started @<PHONE_NUMBER>695
17:15:13.762 [info] Disposing request as the cell (-1) was deleted ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
17:15:37.089 [info] Handle Execution of Cells 25 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
17:15:37.129 [info] Kernel acknowledged execution of cell 25 @<PHONE_NUMBER>129
17:15:37.135 [warn] Cell completed with errors rd [Error]: cannot reshape array of size 698 into shape (64,64)
    at r.execute (~/.vscode-server/extensions/ms-toolsai.jupyter-2024.1.2024012502-linux-x64/dist/extension.node.js:263:4968) {
  ename: 'ValueError',
  evalue: 'cannot reshape array of size 698 into shape (64,64)',
  traceback: [
    '\x1B[0;31m---------------------------------------------------------------------------\x1B[0m',
    '\x1B[0;31mValueError\x1B[0m                                Traceback (most recent call last)',
    'Cell \x1B[0;32mIn[101], line 1\x1B[0m\n' +
      '\x1B[0;32m----> 1\x1B[0m plt\x1B[38;5;241m.\x1B[39mimshow(dim1\x1B[38;5;241m.\x1B[39mT\x1B[38;5;241m.\x1B[39mreshape(\x1B[38;5;241m64\x1B[39m, \x1B[38;5;241m64\x1B[39m)\x1B[38;5;241m.\x1B[39mT, cmap\x1B[38;5;241m=\x1B[39m\x1B[38;5;124m"\x1B[39m\x1B[38;5;124mgray\x1B[39m\x1B[38;5;124m"\x1B[39m, interpolation\x1B[38;5;241m=\x1B[39m\x1B[38;5;124m"\x1B[39m\x1B[38;5;124mantialiased\x1B[39m\x1B[38;5;124m"\x1B[39m)\n',
    '\x1B[0;31mValueError\x1B[0m: cannot reshape array of size 698 into shape (64,64)'
  ]
}
17:15:37.137 [info] End cell 25 execution after 0.006s, completed @<PHONE_NUMBER>135, started @<PHONE_NUMBER>129
17:15:44.457 [info] Handle Execution of Cells 25 for ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
17:15:44.475 [info] Kernel acknowledged execution of cell 25 @<PHONE_NUMBER>475
17:15:44.490 [warn] Cell completed with errors rd [Error]: cannot reshape array of size 698 into shape (64,64)
    at r.execute (~/.vscode-server/extensions/ms-toolsai.jupyter-2024.1.2024012502-linux-x64/dist/extension.node.js:263:4968) {
  ename: 'ValueError',
  evalue: 'cannot reshape array of size 698 into shape (64,64)',
  traceback: [
    '\x1B[0;31m---------------------------------------------------------------------------\x1B[0m',
    '\x1B[0;31mValueError\x1B[0m                                Traceback (most recent call last)',
    'Cell \x1B[0;32mIn[102], line 1\x1B[0m\n' +
      '\x1B[0;32m----> 1\x1B[0m plt\x1B[38;5;241m.\x1B[39mimshow(dim1\x1B[38;5;241m.\x1B[39mreshape(\x1B[38;5;241m64\x1B[39m, \x1B[38;5;241m64\x1B[39m)\x1B[38;5;241m.\x1B[39mT, cmap\x1B[38;5;241m=\x1B[39m\x1B[38;5;124m"\x1B[39m\x1B[38;5;124mgray\x1B[39m\x1B[38;5;124m"\x1B[39m, interpolation\x1B[38;5;241m=\x1B[39m\x1B[38;5;124m"\x1B[39m\x1B[38;5;124mantialiased\x1B[39m\x1B[38;5;124m"\x1B[39m)\n',
    '\x1B[0;31mValueError\x1B[0m: cannot reshape array of size 698 into shape (64,64)'
  ]
}
17:15:44.491 [info] End cell 25 execution after 0.015s, completed @<PHONE_NUMBER>490, started @<PHONE_NUMBER>475
17:15:58.612 [info] Disposing request as the cell (-1) was deleted ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
17:15:58.612 [info] Disposing request as the cell (-1) was deleted ~/CDA_6740/CDA_6740_HW2/Q3.ipynb
17:15:58.612 [info] Disposing request as the cell (-1) was deleted ~/CDA_6740/CDA_6740_HW2/Q3.ipynb

Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
Python 3.11.5
Anaconda Version (if applicable)
user-agent : conda/24.1.0 requests/2.31.0 CPython/3.11.7 Linux/<IP_ADDRESS>-microsoft-standard-WSL2 ubuntu/22.04.3 glibc/2.35 solver/libmamba conda-libmamba-solver/24.1.0 libmambapy/1.5.6 aau/0.4.3 c/dHDm
Running Jupyter locally or remotely?
N/A or Not sure

Did this only happen once or can you get it to repro regularly.
If you can repro on demand, can you try to run Help: start extension bisect to see if the issue is caused by an extension?

It happened two or three times, but I haven't figured out the pattern.
It's possible I'm hitting some shortcut key on accident while typing, but I don't know why that shortcut would exist.
I will update the issue next time it happens.

It just happened. I'm not sure how Help: start extension bisect will help since I don't know how to cause the issue deliberately.

I grabbed this log, I don't know if it's the right info though.
log.ts:417  INFO Started local extension host with pid 39388.
log.ts:437   ERR Extension 'ms-toolsai.datawrangler CANNOT USE these API proposals 'notebookDeprecated'. You MUST start in extension development mode or use the --enable-proposed-api command line flag
log.ts:417  INFO Invoking resolveAuthority(wsl)...
log.ts:417  INFO [LocalProcess0][resolveAuthority(wsl,1)][0ms] obtaining proxy...
log.ts:417  INFO [LocalProcess0][resolveAuthority(wsl,1)][0ms] invoking...
log.ts:417  INFO [LocalProcess0][resolveAuthority(wsl,1)][455ms] returned WebSocket(<IP_ADDRESS>:51642)
log.ts:417  INFO resolveAuthority(wsl) returned 'WebSocket(<IP_ADDRESS>:51642)' after 455 ms
log.ts:417  INFO Creating a socket (renderer-Management-b72e4d3f-4b24-4f8e-bffa-0d846335b6f8)...
log.ts:417  INFO Creating a socket (renderer-ExtensionHost-fbb7dba4-1461-4d93-8120-3418fd9c1240)...
log.ts:417  INFO Creating a socket (renderer-Management-b72e4d3f-4b24-4f8e-bffa-0d846335b6f8) was successful after 176 ms.
log.ts:437   ERR Extension 'ms-toolsai.datawrangler CANNOT USE these API proposals 'notebookDeprecated'. You MUST start in extension development mode or use the --enable-proposed-api command line flag
log.ts:417  INFO Creating a socket (renderer-ExtensionHost-fbb7dba4-1461-4d93-8120-3418fd9c1240) was successful after 446 ms.
webviewElement.ts:512 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ webviewElement.ts:512
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope text.tex.
Old grammar file: file:///c%3A/Users/joshu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/latex/syntaxes/TeX.tmLanguage.json.
New grammar file: vscode-remote://wsl%2Bubuntu/home/red/.vscode-server/extensions/james-yu.latex-workshop-9.18.0/syntax/TeX.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope text.tex.latex.
Old grammar file: file:///c%3A/Users/joshu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/latex/syntaxes/LaTeX.tmLanguage.json.
New grammar file: vscode-remote://wsl%2Bubuntu/home/red/.vscode-server/extensions/james-yu.latex-workshop-9.18.0/syntax/LaTeX.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope text.bibtex.
Old grammar file: file:///c%3A/Users/joshu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/latex/syntaxes/Bibtex.tmLanguage.json.
New grammar file: vscode-remote://wsl%2Bubuntu/home/red/.vscode-server/extensions/james-yu.latex-workshop-9.18.0/syntax/Bibtex.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope text.tex.markdown_latex_combined.
Old grammar file: file:///c%3A/Users/joshu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/latex/syntaxes/markdown-latex-combined.tmLanguage.json.
New grammar file: vscode-remote://wsl%2Bubuntu/home/red/.vscode-server/extensions/james-yu.latex-workshop-9.18.0/syntax/markdown-latex-combined.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.cpp.embedded.latex.
Old grammar file: file:///c%3A/Users/joshu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/latex/syntaxes/cpp-grammar-bailout.tmLanguage.json.
New grammar file: vscode-remote://wsl%2Bubuntu/home/red/.vscode-server/extensions/james-yu.latex-workshop-9.18.0/syntax/cpp-grammar-bailout.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope text.tex.
Old grammar file: file:///c%3A/Users/joshu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/latex/syntaxes/TeX.tmLanguage.json.
New grammar file: vscode-remote://wsl%2Bubuntu/home/red/.vscode-server/extensions/james-yu.latex-workshop-9.18.0/syntax/TeX.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope text.tex.latex.
Old grammar file: file:///c%3A/Users/joshu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/latex/syntaxes/LaTeX.tmLanguage.json.
New grammar file: vscode-remote://wsl%2Bubuntu/home/red/.vscode-server/extensions/james-yu.latex-workshop-9.18.0/syntax/LaTeX.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope text.bibtex.
Old grammar file: file:///c%3A/Users/joshu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/latex/syntaxes/Bibtex.tmLanguage.json.
New grammar file: vscode-remote://wsl%2Bubuntu/home/red/.vscode-server/extensions/james-yu.latex-workshop-9.18.0/syntax/Bibtex.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope text.tex.markdown_latex_combined.
Old grammar file: file:///c%3A/Users/joshu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/latex/syntaxes/markdown-latex-combined.tmLanguage.json.
New grammar file: vscode-remote://wsl%2Bubuntu/home/red/.vscode-server/extensions/james-yu.latex-workshop-9.18.0/syntax/markdown-latex-combined.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.cpp.embedded.latex.
Old grammar file: file:///c%3A/Users/joshu/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/latex/syntaxes/cpp-grammar-bailout.tmLanguage.json.
New grammar file: vscode-remote://wsl%2Bubuntu/home/red/.vscode-server/extensions/james-yu.latex-workshop-9.18.0/syntax/cpp-grammar-bailout.tmLanguage.json
register @ TMScopeRegistry.ts:46
log.ts:417  INFO [perf] Render performance baseline is 33ms
log.ts:417  INFO Extension host (Remote) is unresponsive.
log.ts:417  INFO Extension host (Remote) is responsive.
log.ts:437   ERR Illegal value for line: Error: Illegal value for line
at p.t (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:149:961)
at Object.lineAt (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:149:90)
at EditCodeAction.provideCodeActions (/home/red/.vscode-server/extensions/sourcegraph.cody-ai-1.4.1/src/code-actions/edit.ts:17:23)
at M.provideCodeActions (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:150:90629)
at /home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:150:117435
at ve.s (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:150:112365)
at ve.$provideCodeActions (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:150:117422)
at d.S (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:147:5520)
at d.Q (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:147:5286)
at d.M (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:147:4338)
at d.L (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:147:3455)
at g.value (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:147:2242)
at r.y (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at r.fire (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at n.fire (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:105:14073)
at g.value (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:173:8051)
at r.y (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at r.fire (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at n.fire (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:105:14073)
at s.z (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:105:17138)
at g.value (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:105:15590)
at r.y (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at r.fire (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at g.acceptChunk (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:105:11847)
at g.value (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:105:11134)
at r.y (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at r.fire (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at r.z (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:170:19768)
at r.acceptFrame (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:170:19574)
at i.n (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:170:18073)
at /home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:170:15293
at Socket.y (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:170:13198)
at Socket.emit (node:events:514:28)
at Socket.emit (node:domain:489:12)
at addChunk (node:internal/streams/readable:324:12)
at readableAddChunk (node:internal/streams/readable:297:9)
at Socket.Readable.push (node:internal/streams/readable:234:10)
at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
console.ts:137 [Extension Host] Starting WebSocket: RAW/api/kernels/972a6b65-8e61-4870-90ce-9be801a42dcd
log.ts:437   ERR Illegal value for line: Error: Illegal value for line
at p.t (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:149:961)
at Object.lineAt (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:149:90)
at EditCodeAction.provideCodeActions (/home/red/.vscode-server/extensions/sourcegraph.cody-ai-1.4.1/src/code-actions/edit.ts:17:23)
at M.provideCodeActions (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:150:90629)
at /home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:150:117435
at ve.s (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:150:112365)
at ve.$provideCodeActions (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:150:117422)
at d.S (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:147:5520)
at d.Q (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:147:5286)
at d.M (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:147:4338)
at d.L (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:147:3455)
at g.value (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:147:2242)
at r.y (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at r.fire (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at n.fire (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:105:14073)
at g.value (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:173:8051)
at r.y (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at r.fire (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at n.fire (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:105:14073)
at s.z (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:105:17138)
at g.value (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:105:15590)
at r.y (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at r.fire (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at g.acceptChunk (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:105:11847)
at g.value (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:105:11134)
at r.y (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at r.fire (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at r.z (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:170:19768)
at r.acceptFrame (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:170:19574)
at i.n (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:170:18073)
at /home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:170:15293
at Socket.y (/home/red/.vscode-server/bin/31c37ee8f63491495ac49e43b8544550fbae4533/out/vs/workbench/api/node/extensionHostProcess.js:170:13198)
at Socket.emit (node:events:514:28)
at Socket.emit (node:domain:489:12)
at addChunk (node:internal/streams/readable:324:12)
at readableAddChunk (node:internal/streams/readable:297:9)
at Socket.Readable.push (node:internal/streams/readable:234:10)
at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
webviewElement.ts:512 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ webviewElement.ts:512

open the developer tools with Developer: Toggle developer tools and check the console for any error logs.


[Add]

Details

Add a menu and hide icons. to minimize the nav bar element and hide unnecessary details in a small device

ADD the create button inside the menu buttons bars for the small device

Screenshots

Type of Contribution

[ ] Update to an existing Animated Button
[X] Adding a new Button
[ ] Resolving a bug
[ ] Proposal to the Repository
[ ] Changes related to documentation or README.md
[ ] Other Changes

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue
[X] I am a GSSoC'23 contributor

Assigned. You may work on it.


runtime/autoload/zig/fmt.vim is missing from unix-like system distribution

Steps to reproduce

Open any file with extension ".zig" (it's ok if the file does not exist yet): vim /tmp/t.zig;
:w<CR> to save it.

Expected behaviour
No error occurs.
Version of Vim
9.0.1632
Environment
Operating system: Alpine Linux Edge
Logs and stack traces
running :msg<CR> gets error info:
Error detected while processing BufWrite Autocommands for "<buffer=1>":
E117: Unknown function: zig#fmt#Format

I guess src/Makefile needs update, so runtime/autoload/zig/fmt.vim would not be skipped?

:mes<CR> instead of :msg<CR>; sorry for the typo.


Throw a more informative error on invalid flag

Passing an invalid flag to an operation throws a very uninformative bad argument #1 to 'band' (number expected, got nil) error. This PR checks for invalid flags and throws a much cleaner error, detailing the name of the invalid flag. As an example, calling flatten with "nonsense" as a flag would result in unable to call operation flatten: invalid flag 'nonsense'.

Hi @RiskoZoSlovenska, that's a nice improvement, thanks!


Added my data

please add hacktoberfest-accepted while merging the PR
Thank you!

Please resolve the merge conflicts and update the PR @WraitH17


support jedis pipeline

[ ] If this is non-trivial feature, paste the links/URLs to the design doc.

[X] Update the documentation to include this new feature.

[X] Tests(including UT, IT, E2E) are added to verify the new feature.

[ ] If it's UI related, attach the screenshots below.

[X] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #6434 .

[X] Update the CHANGES log.

Read plugin development doc, one step is missing. We need the plugin e2e test.

Read plugin development doc, one step is missing. We need the plugin e2e test.

OK

I think you should run the test locally, there is no actual span generated. You could read the logs by yourself.

I think you should run the test locally, there is no actual span generated. You could read the logs by yourself.

It look just OK for me

I think you should run the test locally, there is no actual span generated. You could read the logs by yourself.

I ran the test ,found out it's compatible with version 2.9.0 2.8.2 2.7.3, but not compatible with version 2.6.3 and before.
Before 2.6.3, the parent class of pipeline has package private access, so it will bring java.lang.NoSuchMethodError

I ran the test ,found out it's compatible with version 2.9.0 2.8.2 2.7.3, but not compatible with version 2.6.3 and before.
Before 2.6.3, the parent class of pipeline has package private access, so it will bring java.lang.NoSuchMethodError

Have you tried to find other intercepting points? Such as intercept the parent methods directly? SkyWalking enhancement doesn't care it is a public or private method.

@wu-sheng It's done now


Setting language url on datatables breaks functionality

Whenever I try to translate the datatables strings using a json file the filters of yadcf are disabled.
When I load the page the filters show up, but when the page finishes loading they dissapear.
DataTables version: 1.10.10
yadcf version: 0.8.8
Current code (doesn't work):
$('#stock_table').dataTable( {
            "paginate": false,
            "dom": '<"#category">lfrt',
            "language": {
            	"url": "/includes/datatables/Spanish.json"
        	},
			"columnDefs": [
				{
					"targets": [ 1, 2, 3, 4 ],
					"searchable": false,
					"orderable": false,
					"className": "centrado"
				}
			]
        }).yadcf([
			{
				column_number: 0,
				filter_type: "auto_complete"
			},
			{
				column_number: 1,
				column_data_type: "html",
				html_data_type: "text",
				filter_default_label: "Seleccionar categoría"
			}
		]);

But deleting the language option on datatables makes it work:
$('#stock_table').dataTable( {
            "paginate": false,
            "dom": '<"#category">lfrt',
			"columnDefs": [
				{
					"targets": [ 1, 2, 3, 4 ],
					"searchable": false,
					"orderable": false,
					"className": "centrado"
				}
			]
        }).yadcf([
			{
				column_number: 0,
				filter_type: "auto_complete"
			},
			{
				column_number: 1,
				column_data_type: "html",
				html_data_type: "text",
				filter_default_label: "Seleccionar categoría"
			}
		]);

Sorry for my english.
Greetings from Spain!

Please provide a link to a jsbin/jsfiddle with the language issue, otherwise I wont be able to reproduce/debug it

https://jsfiddle.net/3fut3xhp/embedded/result/

grab the 0.8.9.beta.29
see working sample
as to the autocomplete filter you must include jquery ui autocomplete js/css in order for it to work


Resync events are not passed to registered filters

Hello, I have a reconciler that registers a ResourceEventFilter as well as a short-ish resync interval. Based only on the logs from my classes, I can see that the events received during resync are never processed by the filter, but they are seen by the reconciler. Is this by design?

Hi @asardaes , what exactly you mean by resync interval in this case, what configuration?
ResourceEventFilter now applies now just on events for the custom resources. The periodic reconciliation is not implemented using resync intervals. So that is right, it will not receive the events for reconciliationMaxInterval from @ControllerConfiguration if you mean that.

Hi, yes, I was talking about reconciliationMaxInterval, I also use some informers directly with fabric8's client, that's why I thought it was related to that kind of resync. Is there more information about the reconciliation mechanism then? I think it's causing some weird race conditions because it doesn't go through the filters.

@asardaes can you be more specific what are you seeing? Maybe some logs.
This is a relatively new feature, but basically it works that after reconciliation registers a timed event. The concurrency related logic is handled on a lower layer and it's independent from informers, that should not be an issue because of this.
Also note, that how it is mentioned in docs, this is meant to be rather a fail-safe, ideally you have informers and event sources to reconcile just on changes.

Sorry, I guess I mixed some topics in an uninteded way. I didn't mean that my reconciler also has an informer or anything like that, I just meant that I've used informers in other projects, so when I saw the reconciliationMaxInterval options in this SDK, I thought it would simply pass that value to fabric8's classes to configure resync.
I think my intention is similar to #870. I have this in my filter class:
private static final ConcurrentMap<String, String> VERSIONS = new ConcurrentHashMap<>();

public static void skipOneChangeAfter(ObjectMeta resourceMeta) {
    VERSIONS.put(resourceMeta.getName(), resourceMeta.getResourceVersion());
}

@Override
public boolean acceptChange(ControllerConfiguration<T> configuration, T oldResource, T newResource) {
    String oldVersion = oldResource == null ? "" : oldResource.getMetadata().getResourceVersion();
    ObjectMeta newMeta = newResource.getMetadata();

    boolean shouldSkip = oldVersion.equals(newMeta.getResourceVersion()) ||
            oldVersion.equals(VERSIONS.get(newMeta.getName()));

    return !shouldSkip;
}

The goal was to skip changes when resourceVersion didn't change, or it matches a version that I know will change because I update the resource. However, I noticed that during periodic reconciliation the reconciler still received events where resourceVersion didn't change.
I find it odd that filtering doesn't apply to periodic reconciliation, but if that's by design, I guess it could at least be documented?

The goal was to skip changes when resourceVersion didn't change, or when it matches a version that I know will change because I updated the resource in the reconciler. However, I noticed that during periodic reconciliation the reconciler still received events where resourceVersion didn't change.

Basically, as said before this is a fail-safe, if you want just to react on changes of the custom resource, you don't have to do anything that is by default. The resourceVersion changes are filtered out by the generation awareness (generationAwareEventProcessing), what is by default turned on also.
I understand this might be different from controller runtime, which contains such failsafe too (but not sure how it is implemented there).
Create a PR to improve javadoc: https://github.com/java-operator-sdk/java-operator-sdk/pull/984
The docs mentions this periodic reconcile, not sure this should be explicitly mentioned in the Max Interval Between Reconciliations section, since it is really don't have anything to do with resources. So would rather stick with that part as it is in the docs.
https://javaoperatorsdk.io/docs/features

Right now I'm handling Config Maps, which don't have generation, so generationAwareEventProcessing is disabled in my case.


Enable codecov

The codecov test panics were due to this change, mentioned on this and this issue. The error backtrace is:
test api::vcx::tests::test_import_after_init_fails ... thread '<unnamed>' panicked at 'attempted to leave type `linked_hash_map::Node<std::string::String, raw_statement::RawStatement>` uninitialized, which is invalid', /rustc/25c8c53dd994acb3f4f7c02fe6bb46076393f8b0/library/core/src/mem/mod.rs:658:9
stack backtrace:
   0: rust_begin_unwind
             at /rustc/25c8c53dd994acb3f4f7c02fe6bb46076393f8b0/library/std/src/panicking.rs:483
   1: core::panicking::panic_fmt
             at /rustc/25c8c53dd994acb3f4f7c02fe6bb46076393f8b0/library/core/src/panicking.rs:85
   2: core::panicking::panic
             at /rustc/25c8c53dd994acb3f4f7c02fe6bb46076393f8b0/library/core/src/panicking.rs:50
   3: linked_hash_map::LinkedHashMap<K,V,S>::insert
   4: <rusqlite::cache::CachedStatement as core::ops::drop::Drop>::drop
   5: <indy_wallet::storage::default::SQLiteStorage as indy_wallet::storage::WalletStorage>::add
   6: indy_wallet::wallet::Wallet::add
   7: indy_wallet::WalletService::add_record
   8: indy_wallet::WalletService::add_indy_object
   9: indy::commands::did::DidCommandExecutor::execute
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

To read: https://doc.rust-lang.org/nomicon/unchecked-uninit.html

Perhaps could be fixed by updating rusqlite from which the error seems to be originating, libindy is now using 0.20.0, but 0.24.0 is available.
https://github.com/rusqlite/rusqlite/releases
Anyway, for codecov restoreation this fix this is ofcourse good enough.


"FSM Reset On State INIT" trying MODBUS RTU from Raspberry Pi

I'm submitting a ...  (check one with "x")
Support/Advice

support/advice request => Please do not submit support requests here, instead use the link to our support page, please!

Feature

( ) feature request

What is the motivation / use case for changing the behavior?

Simple question to get some hint

( ) simple question => please visit the Wiki, the YouTube tutorials and the Info tab by clicking on the node inside Node-RED before
(x) help wanted => you read all information and watched relevant YouTube tutorials, but you need more help

Problem

( ) bug report => please search github for a similar issue or PR and test Modbus problems with the modbus-serial package before submitting
(x) unexpected behavior => please visit the Wiki before

Current behavior
I'm getting "FSM Reset On State INIT" trying what I think is a simple read over MODBUS RTU.
Expected behavior
I think I should be able to connect to a device and read a holding register.
Minimal reproduction of the problem with instructions
Example flow:
[{"id":"4574faa5.6644fc","type":"modbus-read","z":"8a48f2a4.6ef5b","name":"","topic":"","showStatusActivities":true,"logIOActivities":false,"showErrors":true,"unitid":"","dataType":"HoldingRegister","adr":"1","quantity":"1","rate":"3","rateUnit":"s","delayOnStart":true,"startDelayTime":"5","server":"7184f32.2fa8a8c","useIOFile":false,"ioFile":"","useIOForPayload":false,"x":230,"y":60,"wires":[["85de5d96.026548"],[]]},{"id":"7184f32.2fa8a8c","type":"modbus-client","z":"","name":"","clienttype":"simpleser","bufferCommands":false,"stateLogEnabled":true,"tcpHost":"<IP_ADDRESS>","tcpPort":"502","tcpType":"DEFAULT","serialPort":"/dev/serial0","serialType":"RTU-BUFFERD","serialBaudrate":"19200","serialDatabits":"8","serialStopbits":"1","serialParity":"none","serialConnectionDelay":"100","unit_id":"","commandDelay":"100","clientTimeout":"1000","reconnectTimeout":"2000"}]
The serial connection to the MODBUS slave seems to be basically working as verified by running sudo minicom -D /dev/serial0 -b19200. When connected this way, I see that when I type anything in the window, the Pi's TX light lights up and the device RX light lights up.
Your Environment
Please tell us about your environment:

Node-RED version: v0.19.4

Node.js version: v8.11.1

Raspian Linux 4.14.98-v7+ arm LE

node-red-contrib-modbus v4.1.3

( ) I am using just the Node-RED package and got modbus-serial package installed with it
( ) I have installed modbus-serial package global from source (using git clone)
(x) I have installed modbus-serial as a global package (using npm i -g)

Yes, modbus-serial is the name but it does all, TCP and Serial.
The node-modbus package is just for the Modbus Server node.

Device :

( ) macOS: v
( ) Linux: v
( ) Windows: v
(x) Raspbian: v 4.14.98-v7+ arm LE
( ) Other:

Name:
Version:

Description of the connecting Modbus system:

In-house prototyped hardware that does work outside of node-red.

node-red-contrib-modbus version: v4.1.3

Node: (min. 6.x)
node --version = v8.11.1

Logs
I've seen you request logs in other issues, so I thought I'd try to get you what you're looking for here. Running DEBUG=contribModbus:write*,contribModbus:core:client,modbus-serial node-red -v gives me:

Welcome to Node-RED
===================

7 May 21:04:52 - [info] Node-RED version: v0.19.4
7 May 21:04:52 - [info] Node.js  version: v8.11.1
7 May 21:04:52 - [info] Linux 4.14.98-v7+ arm LE
7 May 21:04:55 - [info] Loading palette nodes
7 May 21:04:59 - [warn] ------------------------------------------------------
7 May 21:04:59 - [warn] [node-red-node-pi-sense-hat/sensehat] Error: Can't find Sense HAT python libraries. Run sudo apt-get install sense-hat
7 May 21:04:59 - [warn] ------------------------------------------------------
7 May 21:04:59 - [info] Settings file  : /home/pi/.node-red/settings.js
7 May 21:04:59 - [info] Context store  : 'default' [module=memory]
7 May 21:04:59 - [info] User directory : /home/pi/.node-red
7 May 21:04:59 - [info] Server now running at http://<IP_ADDRESS>:1880/
7 May 21:04:59 - [info] Active project : info-lab-hub-nodered
7 May 21:04:59 - [info] Flows file     : /home/pi/.node-red/projects/info-lab-hub-nodered/flow.json
7 May 21:04:59 - [info] Starting flows
  contribModbus:core:client Client -> start: NEW +0ms
  contribModbus:core:client Client -> FSM events:init,stop +3ms
  contribModbus:core:client Client -> initialized +2ms
  contribModbus:core:client Client -> after event: init old: NEW new: INIT +7ms
7 May 21:04:59 - [warn] [modbus-client:7184f32.2fa8a8c] Client -> reconnect in 2000 ms Serial@/dev/serial0:19200bit/s default Unit-Id: 1
  contribModbus:core:client Client -> event: init old: NEW new: INIT Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +4ms
7 May 21:04:59 - [info] Started flows
  contribModbus:core:client Client -> RTU buffered port serial Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +500ms
  modbus-serial { action: 'port open error',
  modbus-serial   error: Error: Error: Permission denied, cannot open /dev/serial0 } +0ms
  modbus-serial modbusSerialErrorHandling:Error: Permission denied, cannot open /dev/serial0 +0ms
  contribModbus:core:client Client -> event: failure old: INIT new: FAILED Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +28ms
7 May 21:05:00 - [warn] [modbus-read:4574faa5.6644fc] FSM Reset On State INIT
  contribModbus:core:client Client -> event: break old: FAILED new: BROKEN Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +2ms
7 May 21:05:00 - [warn] [modbus-client:7184f32.2fa8a8c] Client -> try to reconnect by init in 2000 ms Serial@/dev/serial0:19200bit/s default Unit-Id: 1
  contribModbus:core:client Client -> after event: init old: BROKEN new: INIT Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +2s
7 May 21:05:02 - [warn] [modbus-client:7184f32.2fa8a8c] Client -> reconnect in 2000 ms Serial@/dev/serial0:19200bit/s default Unit-Id: 1
  contribModbus:core:client Client -> event: init old: BROKEN new: INIT Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +5ms
  contribModbus:core:client Client -> RTU buffered port serial Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +2s
  contribModbus:core:client Client -> connection closed Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +4ms
  modbus-serial { action: 'port open error',
  modbus-serial   error: Error: Error: Permission denied, cannot open /dev/serial0 } +4s
  modbus-serial modbusSerialErrorHandling:Error: Permission denied, cannot open /dev/serial0 +4s
  contribModbus:core:client Client -> event: failure old: INIT new: FAILED Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +5ms
7 May 21:05:04 - [warn] [modbus-read:4574faa5.6644fc] FSM Reset On State INIT
  contribModbus:core:client Client -> event: break old: FAILED new: BROKEN Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +2ms
7 May 21:05:04 - [warn] [modbus-client:7184f32.2fa8a8c] Client -> try to reconnect by init in 2000 ms Serial@/dev/serial0:19200bit/s default Unit-Id: 1
  contribModbus:core:client Client -> after event: init old: BROKEN new: INIT Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +2s
7 May 21:05:06 - [warn] [modbus-client:7184f32.2fa8a8c] Client -> reconnect in 2000 ms Serial@/dev/serial0:19200bit/s default Unit-Id: 1
  contribModbus:core:client Client -> event: init old: BROKEN new: INIT Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +3ms
^C7 May 21:05:07 - [info] Stopping flows
  contribModbus:core:client Client -> event: failure old: INIT new: FAILED Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +1s
7 May 21:05:07 - [warn] [modbus-read:4574faa5.6644fc] FSM Reset On State INIT
  contribModbus:core:client Client -> event: break old: FAILED new: BROKEN Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +3ms
7 May 21:05:07 - [warn] [modbus-client:7184f32.2fa8a8c] Client -> try to reconnect by init in 2000 ms Serial@/dev/serial0:19200bit/s default Unit-Id: 1
  contribModbus:core:client Client -> close node Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +2ms
  contribModbus:core:client Client -> connection closed Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +8ms
7 May 21:05:07 - [info] Stopped flows

And in that, I think the money lines are...
  contribModbus:core:client Client -> connection closed Serial@/dev/serial0:19200bit/s default Unit-Id: 1 +4ms
  modbus-serial { action: 'port open error',
  modbus-serial   error: Error: Error: Permission denied, cannot open /dev/serial0 } +4s
  modbus-serial modbusSerialErrorHandling:Error: Permission denied, cannot open /dev/serial0 +4s

But I'm not sure how to resolve that apparent permission issue.

I think this is a non-issue. Default Raspian has the following in /boot/cmdline.txt:
console=serial0,115200 console=tty1

So that was already using serial0 and therefore I couldn't use it for this.
Removing that line and adding enable_uart=1 to /boot/config.txt allowed everything to work as I'd hoped.


[CARBONDATA-1303] Update CarbonContext.scala

to skip serilize this two not-serializable class while apply mapPartitions function to dataframe create from CarbonContext
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[CARBONDATA-<Jira issue #>] Description of pull request

[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).

[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.

[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

[ ] Testing done
 Please provide details on
 - Whether new unit test cases have been added or why no new tests are required?
 - What manual testing you have done?
 - Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Build Failed with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/451/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/3039/

Can one of the admins verify this patch?

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/36/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1214/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/583/

can you please add test case to reproduce this scenario

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/77/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9197/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3416/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/102/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/101/

Build Failed  with Spark 2.4.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/98/

Build Failed  with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/7/


Germline labels

Add a description of the file structure to the Germline Sets section, and fix minor typos. Add GermlineSet and GenotypeSet to the list of high-level schema objects.

The file structure will need to match the DataFile which also has a direct correspondence to how data is returned from the ADC API.

Thanks Scott. I have added a reference to the AIRR DataFile,

Done, but can we please discuss their inclusion in the next major release.

@williamdlees There is no problem in including the Germline object in the next release of the Schema. But if we consider this to be required metadata for all studies, this would be an incompatible change of the MiAIRR standard an thus would have to wait until v2.0. Does this clarify my previous point?

MiAIRR does require a germline set reference, germline_database in set 5 (DataProcessing). It might be reasonable to now require that field to contain the globally unique germline reference ID, that is, germline_set_ref instead of being free-form text?

@schristley I agree, we should move in this direction. But IMO that's another pull request :smiley:

added some more detail about file structure, I think this might be ready to merge.


Added shapes and lines Module. Issue No #40

Description:
Added a new module for "Shapes & Lines" to enhance the learning experience of the app users. This module provides interactive content to educate users about different shapes and lines.
Changes Made:
Created a new Dart file named lines.dart within the pages directory to host the Shapes & Lines page. Implemented the UI layout for the Shapes & Lines page, including text descriptions and placeholders for various shapes and lines.
Updated the routes.dart file to include a new route constant (linesRoute) for the Shapes & Lines page. Integrated the Shapes & Lines page into the main app (main.dart) by importing the page file and adding the new route to the routes map in the MaterialApp widget.
This pull request enhances the educational content of the app and improves user engagement by adding a new module focused on shapes and lines. Future iterations may include further enhancements to the UI and interactive features within this module.

The page is there from the beginning.
Add the details (Shapes and lines) to that page...


Bump patch version for new docs/CI changes

The Julia compat was changed to 1.3 as well but I think since we're <1.0 on the package version this should be fine.

Resolved by re-adding the SSH deploy key, which was missing


Colaps curl and tar to reduce linecount.

I just like the piping... :)

Why did you close this?

I created a new one... :/

I am able to change an existing PR?

Sure, mate!
Just do git push -f, that's all.

Hehe... you never stop learning in IT.


Applozic Framework 2.3 Release

Universal Simulator Debug Release refer to :- https://github.com/AppLozic/Applozic-iOS-SDK/commit/c5ebc7d1681a53889c090c30578075eebf6fa912


Add perPage option to a list along with select component

right now on each page there is default 10 items. It should be set by user in the UI
Design: https://invis.io/YEVQB42BWNG#/402515662_AdminBro-Tables-1
Acceptance criteria

there shouldbe 10/20/50/100 elements
picked option should be stored so next time user shows the page it will be selected (stored per resource)
in ResourceOpton there should be a default value (like with sortBy)

For select we can use: https://github.com/misantronic/react-slct

Please don't limit to any value but leave it also open for entering own value b.v. 250. Very useful addition to the list interface. Thanks.

It should be expanded with a export button to be able to fill a spreadsheet with the selected values to do further work on extracted data - like making a list of lables for participants of an event.

Hi @wojtek-krysiak
any updates on this implementation?

@sharath-mallikarjuna we will be working on a v3.0 soon (like next week). I added this and some other tasks to the v3 backlog.

I have installed the latest version v3.1, but still I can't know where to place the perPage parameter per resource to change the default value of 10 records per page.

we haven't managed to do that last time. It is still in the backlog.

I have installed the latest version v3.1, but still I can't know where to place the perPage parameter per resource to change the default value of 10 records per page.

@mohamed-nazmi This ticket is almost ancient, but I'll paste my workaround solution anyway for any future visitors. Use actions.list.before in your resources in adminJsOptions like this:
{
  resource: User,
  options: {
    ...,
    parent: userSidebarSection,
    actions: {
      list: {
        before: async (request) => {
          request.query.perPage ??= 100;
          return request;
        },
      },
    },
  },
}


Explorer not updating contents of folders when files are added, e.g. CSS generated by gulp

VSCode Version: Code 1.10.2 (8076a19fdcab7e1fc1707952d652f0bb6c6db331, 2017-03-08T13:56:35.908Z)
OS Version: Darwin x64 16.4.0
Extensions: none

Steps to Reproduce:
1.create a new SCSS file in your gulp setup
2.observe that the CSS file is not shown, but is actually there

@therobyouknow does it show up after an explorer refresh? can you share your settings?

I hadn't tried the refresh as I couldn't initially see where it was - I looked for it in the menus but couldn't see it. I realise now that it is the circular arrow on the root folder.
It would be nice to have this circular arrow on the folder that one is currently hovering on.
I'm running gulp inside a puphpet.com/vagrant provisioned Ubuntu 14.04 VM with NFS mounting to share the files from the host (i.e. Mac) with Ubuntu in the VM. The files are being updated in the VM by gulp running there. I would guess that my original issue whereby the changes are not being seen by Code might be due to file added information not being seen by Code on the host somehow.
I tried to reproduce the issue by adding a further SCSS file to see if the CSS got added when I checked in the Terminal to then compare with what Code sees, but I was unable to reproduce - the CSS file wasn't being created at all for sure. That's down to my limitations by not being totally familiar with this particular gulp setup. However, originally I had seen this issue whereby the CSS file not shown in a folder in Code but shown in the Terminal cd'd into that folder. That's all the information I can give for now.

Refresh does work I think. I saw this to be the case for a different scenario whereby I had deleted some non-version controlled files and then re-run composer install to re-fetch them. They did not initially show but the refresh showed them. Suggested improvement might be that Code "listens" to the file system (MacOS) for changes. Closing ticket.


Redis fixes

Fixed #109, #137
Fixed resource check on RedisResourceManager.
Fixed normalization of libOptions, normalizing them on resource initialization.

Thanks, @thomasvargiu!


fix: Remove package working dir prior to build

This resolves a very weird issue where the_luggage doesn't cleanup
before building a new version. It can sometimes result in an output
package with twice the file size since the Crypt.bundle is included
twice once at /Lib/Sec/SecAgentPlugins/Crypt.bundle and a second copy
inside the bundle itself.
Since this has happened all of twice, once to Graham in August of
2018 and to me today it isn't a huge issue but an annoying one when it
does happen.
Reference: https://macadmins.slack.com/archives/C07LPS75M/p1544112534025200

Oh man, thank you. I ran into this so many time but wasn’t sure the best way to fix it.


2906 process extensions input and output parameters for tasks should …

…be validated only if the implementation exists
https://github.com/Activiti/Activiti/issues/2906

Closing this as it was fixed in another PR.


fix: items, additionItems, propertyNames API type mismatch

#80 has updated the extend API result type, however it lead to the type mismatch in ArraySchema.items, Array.Schema.addtionalItems API argument.
This PR is used to fix those type mismatch issue.
Checklist

[x] run npm run test and npm run benchmark
[x] tests and/or benchmarks are included
[ ] documentation is changed or added
[x] commit message and code follows the Developer's Certification of Origin
and the Code of conduct

@aboutlo sorry to border you. I think you are the one who responsible for this package. It have been a long day waiting for this change to be merge. Do you have time to review this PR?


Adds ability to skip sending emails when empty config is provided

@neerajdotname _a please review.
The build on CircleCI is failing because it is not able to connect to the repo. We may have to re-create the CircleCi project for this repo, could you please try doing that?


Private monica

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@Monicalyy,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@azuresdkci add to whitelist

@Monicalyy You will need to follow the durections here: https://aka.ms/azuregithub for joining the Azure organization, or, if you are not part of the azure organization, sign the CLS.
@darshanhs90  Please approve

This is obsolete, so close it.


Update test methods

Closes #315.
I've left this as three separate commits for visibility, we of course should squash on merge!
This change looks bigger than it is, pretty much just find-and-replace!

@tejasbubane thanks!  @exercism/ecmascripts any other concerns, or are we good to merge?


Update + OSX Compatibility

Update Readme
Fix Osx compatibility
Added check of python dependencies
Installer
Convert addon directly downloading repo in  file

Hi Anton, thanks for the contribution, I just tested it on Windows, and I'm happy to say that it works there, as well (with a couple of notes).
I may rewrite parts of the README so that it's clear how to install on Windows as well as Mac, the only difference seems to be that you still need Admin privileges to install Python packages, even when it's handled by pip.
Very nice work, the Dependencies panel, especially, is a very slick way to handle it, and a good way to notify users which package they're missing.

Hey, of course, Thanks for your feedback.
Regards :)


Update to BCs v12 by default

Move to BCs v12 by default. Also moves to L181 by default.

Your development orb(s) have been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link(s):
https://circleci.com/developer/orbs/orb/geos-esm/circleci-tools?version=dev:f0c2c8ef70b5b840bbd8e08f6fabaa9f7bb4d5d4
https://circleci.com/developer/orbs/orb/geos-esm/circleci-tools?version=dev:alpha

Your development orb(s) have been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link(s):
https://circleci.com/developer/orbs/orb/geos-esm/circleci-tools?version=dev:aa7ebf7e482efad5c54fdd51ae95218a12e81fc4
https://circleci.com/developer/orbs/orb/geos-esm/circleci-tools?version=dev:alpha

Your development orb(s) have been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link(s):
https://circleci.com/developer/orbs/orb/geos-esm/circleci-tools?version=dev:aa7ebf7e482efad5c54fdd51ae95218a12e81fc4
https://circleci.com/developer/orbs/orb/geos-esm/circleci-tools?version=dev:alpha

Your orb has been published to the CircleCI Orb Registry.
You can view your published orb on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/geos-esm/circleci-tools?version=5.1.0