Pylance hints not working in Jupyter Notebook in Remote Tunnel

Environment data

Pylance version: 2024.8.2
OS and version: Ubuntu 22.04
Python version (& distribution if applicable, e.g. Anaconda): 3.12

The behaviour in #5071  which was also mentioned here https://github.com/microsoft/vscode/issues/196740 seems to be occurring again.
At the end of the #5071 issue there seems to be at least four people still experiencing this and it was advised to open a new ticket. Given that this is the same issue resurfacing I'm keeping the issue report minimal
When I try to execute a cell I get NO notebook document for 'file://// and the cell fails to run.

looks like dup of https://github.com/microsoft/pylance-release/issues/5034

Hey @this-josh, thanks for posting this issue. I am trying to reproduce this issue, Can you please provide a small code sample and log as described under "Filing an issue" in the troubleshooting guide?
Or could you confirm that the below steps repro this issue for you? (quoted from #5071)

Open VS code from WSL
Create a new notebook
Create a cell
Deselect the code
Hit 'dd'
Hit 'z'
Repeat until crash

I'm having difficulty creating a reproducible example as the error occurs randomly around 5 minutes after opening a notebook.
At the time of failure the Python Language produces this error each time I write a character in the notebook
2024-10-22 08:10:03.374 [info] [Error - 08:10:03] (2648257) Received change text document command for closed file file:///path/to/my/notebook.ipynb.py#X16sdnNjb2RlLXJlbW90ZQ%3D%3D

Could you share the VS Code version you're using? Might be related to this one: https://github.com/microsoft/pylance-release/issues/5543

I'm seeing probably the same issue.
Here's what I do; It's not super clear to me how to reproduce this.

In WSL2, create a new folder, create a new venv (python3 -m venv .venv; source .venv/bin/activate)
Start VSCode in the folder code .
Create a new notebook. Select the python from venv.
Add a cell; run. VSCode will ask to install Jupyter etc.
Make some modifications...

Errors in Output: Python Language Server:
2024-10-29 09:52:23.992 [info] [Error - 9:52:23 AM] (20498) Received change text document command for closed file file:///home/redacted/foo.ipynb.py#W1sdnNjb2RlLXJlbW90ZQ%3D%3D
Version:
Version: 1.94.2 (user setup)
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22631

Some stack traces from developer tools:
INFO Started local extension host with pid 4928.
log.ts:419  INFO Invoking resolveAuthority(wsl)...
log.ts:419  INFO [LocalProcess0][resolveAuthority(wsl,1)][0ms] obtaining proxy...
log.ts:419  INFO [LocalProcess0][resolveAuthority(wsl,1)][0ms] invoking...
log.ts:419  INFO [LocalProcess0][resolveAuthority(wsl,1)][662ms] returned WebSocket(<IP_ADDRESS>:64358)
log.ts:419  INFO resolveAuthority(wsl) returned 'WebSocket(<IP_ADDRESS>:64358)' after 664 ms
log.ts:419  INFO Creating a socket (renderer-Management-577fb71d-b77c-41db-8861-9c8d79a238e3)...
log.ts:419  INFO Creating a socket (renderer-ExtensionHost-0f35599f-cd97-46bc-b3c5-80a9d1e64c92)...
log.ts:419  INFO Creating a socket (renderer-Management-577fb71d-b77c-41db-8861-9c8d79a238e3) was successful after 122 ms.
log.ts:419  INFO Creating a socket (renderer-ExtensionHost-0f35599f-cd97-46bc-b3c5-80a9d1e64c92) was successful after 285 ms.
console.ts:137 [Extension Host] Checking whether to register object drop extension
console.ts:137 [Extension Host] Registering object drop provider
console.ts:137 [Extension Host] Registered object drop provider
webviewElement.ts:486 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ webviewElement.ts:486
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.sql.
log.ts:419  INFO [perf] Render performance baseline is 59ms
log.ts:439   ERR adding EXISTING notebook file:///home/REDACTED/projects/REDACTED/py/demographics.ipynb : Error: adding EXISTING notebook file:///home/REDACTED/projects/REDACTED/py/demographics.ipynb
	at nh.$acceptDocumentAndEditorsDelta (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:13379)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
  ...
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
console.ts:137 [Extension Host] info 09:49:19.251: Jupyter Extension: Starting Kernel (Python Path: ~/projects/REDACTED/py/.venv/bin/python, Venv, 3.10.12) for '~/projects/REDACTED/py/demographics.ipynb' (disableUI=true)
console.ts:137 [Extension Host] info 09:49:19.694: Jupyter Extension: Process Execution: ~/projects/REDACTED/py/.venv/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
console.ts:137 [Extension Host] info 09:49:19.698: Jupyter Extension: Process Execution: ~/projects/REDACTED/py/.venv/bin/python -m ipykernel_launcher --f=/home/REDACTED/.local/share/jupyter/runtime/kernel-v31489eb49c8330c747d7d9f6212d52f0262bc1e2b.json
    > cwd: //home/REDACTED/projects/REDACTED/py
console.ts:137 [Extension Host] info 09:49:19.707: Jupyter Extension: Process Execution: ~/projects/REDACTED/py/.venv/bin/python -m pip list
console.ts:137 [Extension Host] info 09:49:20.661: Jupyter Extension: Kernel successfully started
console.ts:137 [Extension Host] info 09:49:20.669: Jupyter Extension: Process Execution: ~/projects/REDACTED/py/.venv/bin/python /home/REDACTED/.vscode-server/extensions/ms-toolsai.jupyter-2024.9.1-linux-x64/pythonFiles/printJupyterDataDir.py
console.ts:137 [Extension Host] info 09:49:40.082: Jupyter Extension: Dispose Kernel '~/projects/REDACTED/py/demographics.ipynb' associated with '~/projects/REDACTED/py/demographics.ipynb'
webviewElement.ts:486 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ webviewElement.ts:486
log.ts:439   ERR adding EXISTING notebook file:///home/REDACTED/projects/REDACTED/py/test.ipynb : Error: adding EXISTING notebook file:///home/REDACTED/projects/REDACTED/py/test.ipynb
	at nh.$acceptDocumentAndEditorsDelta (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:13379)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
	...
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
console.ts:137 [Extension Host] info 09:50:03.614: Jupyter Extension: Starting Kernel (Python Path: ~/projects/REDACTED/py/.venv/bin/python, Venv, 3.10.12) for '~/projects/REDACTED/py/test.ipynb' (disableUI=true)
console.ts:137 [Extension Host] info 09:50:03.623: Jupyter Extension: Process Execution: ~/projects/REDACTED/py/.venv/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
console.ts:137 [Extension Host] info 09:50:03.709: Jupyter Extension: Process Execution: ~/projects/REDACTED/py/.venv/bin/python -m ipykernel_launcher --f=/home/REDACTED/.local/share/jupyter/runtime/kernel-v3eddd17e7f77b49836dfc39952a482bcca7778918.json
    > cwd: //home/REDACTED/projects/REDACTED/py
console.ts:137 [Extension Host] info 09:50:04.260: Jupyter Extension: Kernel successfully started
console.ts:137 [Extension Host] info 09:51:34.199: Jupyter Extension: Starting Kernel (Python Path: ~/projects/REDACTED/py/.venv/bin/python, Venv, 3.10.12) for '~/projects/REDACTED/py/demographics.ipynb' (disableUI=true)
console.ts:137 [Extension Host] info 09:51:34.218: Jupyter Extension: Process Execution: ~/projects/REDACTED/py/.venv/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
console.ts:137 [Extension Host] info 09:51:34.275: Jupyter Extension: Process Execution: ~/projects/REDACTED/py/.venv/bin/python -m ipykernel_launcher --f=/home/REDACTED/.local/share/jupyter/runtime/kernel-v3139381d6986310f2e11215649ba510ef7bbaa95a.json
    > cwd: //home/REDACTED/projects/REDACTED/py
console.ts:137 [Extension Host] info 09:51:35.167: Jupyter Extension: Kernel successfully started
console.ts:137 [Extension Host] info 09:52:18.616: Jupyter Extension: Dispose Kernel '~/projects/REDACTED/py/demographics.ipynb' associated with '~/projects/REDACTED/py/demographics.ipynb'
log.ts:439   ERR unknown text editor: 42d6d461-d6cc-4d6b-947b-424d679e7cde. known editors: 6ba23677-263a-4c0e-b55c-6341416559fa : Error: unknown text editor: 42d6d461-d6cc-4d6b-947b-424d679e7cde. known editors: 6ba23677-263a-4c0e-b55c-6341416559fa
	at nh.getEditorById (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:5598)
	at wb.$acceptEditorPropertiesChanged (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:16972)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
  ...
	at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
2log.ts:439   ERR NO notebook document for 'file:///home/REDACTED/projects/REDACTED/py/demographics.ipynb': Error: NO notebook document for 'file:///home/REDACTED/projects/REDACTED/py/demographics.ipynb'
	at nh.getNotebookDocument (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:5868)
	at DU.$acceptModelChanged (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:16411)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
  ...
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
console.ts:137 [Extension Host] info 09:52:48.366: Jupyter Extension: Dispose Kernel '~/projects/REDACTED/py/test.ipynb' associated with '~/projects/REDACTED/py/test.ipynb'
log.ts:439   ERR unknown text editor: 42d6d461-d6cc-4d6b-947b-424d679e7cde. known editors:  : Error: unknown text editor: 42d6d461-d6cc-4d6b-947b-424d679e7cde. known editors:
	at nh.getEditorById (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:5598)
	at wb.$acceptEditorPropertiesChanged (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:16972)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
  ...
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)

Extensions:
Name: Jupyter
Id: ms-toolsai.jupyter
Description: Jupyter notebook support, interactive programming and computing that supports Intellisense, debugging and more.
Version: 2024.9.1
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter

Name: Pylance
Id: ms-python.vscode-pylance
Description: A performant, feature-rich language server for Python in VS Code
Version: 2024.10.1
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-python.vscode-pylance

Name: Python
Id: ms-python.python
Description: Python language support with extension access points for IntelliSense (Pylance), Debugging (Python Debugger), linting, formatting, refactoring, unit tests, and more.
Version: 2024.16.1
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-python.python

I'm still struggling to find a simple reproducer; sorry. For some notebooks, the problem happens consistently after a few minutes. It seems that having some import helps.
Here's something I tried now:

Create a new folder, a venv, start code, create a notebook as described above
The notebook currently contains the two cells below
I'm doing a bit of editing, including adding things that would cause errors that pylance can find

This is the current state of the notebook:
import pandas as pd
import numpy as np

df = pd.DataFrame(
    np.array([[1, 2, 3], [4, 5, 6], [7, 8, 9]]),
    columns=['a', 'b', 'c']
)
df.loc["a"] = foo
with pd.option_context("display.max_rows", 100):
    display(df)

The problem first happened when I added the df.loc["a"] = foo line.
Python language server output shows 2024-10-29 10:24:14.352 [info] [Error - 10:24:14 AM] (29738) Received change text document command for closed file file:///home/jbw/repro/repro.ipynb.py#W1sdnNjb2RlLXJlbW90ZQ%3D%3D
Dev tools show:
INFO Started local extension host with pid 16768.
log.ts:419  INFO Invoking resolveAuthority(wsl)...
log.ts:419  INFO [LocalProcess0][resolveAuthority(wsl,1)][0ms] obtaining proxy...
log.ts:419  INFO [LocalProcess0][resolveAuthority(wsl,1)][0ms] invoking...
log.ts:419  INFO [LocalProcess0][resolveAuthority(wsl,1)][673ms] returned WebSocket(<IP_ADDRESS>:64537)
log.ts:419  INFO resolveAuthority(wsl) returned 'WebSocket(<IP_ADDRESS>:64537)' after 673 ms
log.ts:419  INFO Creating a socket (renderer-Management-1a6e70f9-e3f5-4011-b5d7-cae4c94381d8)...
log.ts:419  INFO Creating a socket (renderer-ExtensionHost-1c2c5d40-e559-48a4-92e2-5efa718cae8d)...
log.ts:419  INFO Creating a socket (renderer-Management-1a6e70f9-e3f5-4011-b5d7-cae4c94381d8) was successful after 92 ms.
log.ts:419  INFO Creating a socket (renderer-ExtensionHost-1c2c5d40-e559-48a4-92e2-5efa718cae8d) was successful after 234 ms.
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.sql.
Old grammar file: file:///c%3A/Users/ltlyg/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/sql/syntaxes/sql.tmLanguage.json.
New grammar file: vscode-remote://wsl%2Bubuntu/home/REDACTED/.vscode-server/extensions/mtxr.sqltools-0.28.3/language/sql.tmLanguage.json
register @ TMScopeRegistry.ts:46
TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.sql.
Old grammar file: file:///c%3A/Users/ltlyg/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/sql/syntaxes/sql.tmLanguage.json.
New grammar file: vscode-remote://wsl%2Bubuntu/home/REDACTED/.vscode-server/extensions/mtxr.sqltools-0.28.3/language/sql.tmLanguage.json
register @ TMScopeRegistry.ts:46
log.ts:419  INFO [perf] Render performance baseline is 71ms
console.ts:137 [Extension Host] Checking whether to register object drop extension
console.ts:137 [Extension Host] Registering object drop provider
console.ts:137 [Extension Host] Registered object drop provider
webviewElement.ts:486 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ webviewElement.ts:486
webviewElement.ts:486 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ webviewElement.ts:486
log.ts:439   ERR adding EXISTING notebook file:///home/REDACTED/repro/repro.ipynb : Error: adding EXISTING notebook file:///home/REDACTED/repro/repro.ipynb
	at nh.$acceptDocumentAndEditorsDelta (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:13379)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
	at Zb.Q (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155532)
...
	at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
console.ts:137 [Extension Host] info 10:21:51.536: Jupyter Extension: Starting Kernel (Python Path: ~/repro/.venv/bin/python, Venv, 3.10.12) for '~/repro/repro.ipynb' (disableUI=true)
console.ts:137 [Extension Host] info 10:21:52.122: Jupyter Extension: Process Execution: ~/repro/.venv/bin/python -m pip list
console.ts:137 [Extension Host] info 10:21:52.131: Jupyter Extension: Process Execution: ~/repro/.venv/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
console.ts:137 [Extension Host] info 10:21:52.138: Jupyter Extension: Process Execution: ~/repro/.venv/bin/python -m ipykernel_launcher --f=/home/REDACTED/.local/share/jupyter/runtime/kernel-v3c760129574c1c4f791a671aa5abb4f29fba272a9.json
    > cwd: //home/REDACTED/repro
console.ts:137 [Extension Host] info 10:21:53.045: Jupyter Extension: Kernel successfully started
console.ts:137 [Extension Host] info 10:21:53.053: Jupyter Extension: Process Execution: ~/repro/.venv/bin/python /home/REDACTED/.vscode-server/extensions/ms-toolsai.jupyter-2024.9.1-linux-x64/pythonFiles/printJupyterDataDir.py
2console.ts:137 [Extension Host] info 10:22:52.327: Jupyter Extension: Disposing request as the cell (1) was deleted ~/repro/repro.ipynb
console.ts:137 [Extension Host] info 10:22:52.328: Jupyter Extension: Dispose Kernel '~/repro/repro.ipynb' associated with '~/repro/repro.ipynb'
webviewElement.ts:486 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ webviewElement.ts:486
console.ts:137 [Extension Host] info 10:23:03.746: Jupyter Extension: Starting Kernel (Python Path: ~/repro/.venv/bin/python, Venv, 3.10.12) for '~/repro/repro.ipynb' (disableUI=true)
console.ts:137 [Extension Host] info 10:23:03.760: Jupyter Extension: Process Execution: ~/repro/.venv/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
console.ts:137 [Extension Host] info 10:23:03.804: Jupyter Extension: Process Execution: ~/repro/.venv/bin/python -m ipykernel_launcher --f=/home/REDACTED/.local/share/jupyter/runtime/kernel-v3dda9f9854777fe6546710fa3c5bd581b9b534a63.json
    > cwd: //home/REDACTED/repro
console.ts:137 [Extension Host] info 10:23:04.663: Jupyter Extension: Kernel successfully started
webviewElement.ts:486 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ webviewElement.ts:486
console.ts:137 [Extension Host] info 10:24:09.854: Jupyter Extension: Dispose Kernel '~/repro/repro.ipynb' associated with '~/repro/repro.ipynb'
log.ts:439   ERR unknown text editor: 1ddaceb1-9613-4685-bdb2-ee6adfc8d152. known editors:  : Error: unknown text editor: 1ddaceb1-9613-4685-bdb2-ee6adfc8d152. known editors:
	at nh.getEditorById (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:5598)
	at wb.$acceptEditorPropertiesChanged (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:16972)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
...
	at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
log.ts:439   ERR NO notebook document for 'file:///home/REDACTED/repro/repro.ipynb': Error: NO notebook document for 'file:///home/REDACTED/repro/repro.ipynb'
	at nh.getNotebookDocument (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:5868)
	at DU.$acceptModelChanged (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:16411)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
...
	at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
log.ts:429  WARN Error: NO notebook document for 'file:///home/REDACTED/repro/repro.ipynb'
	at nh.getNotebookDocument (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:5868)
	at IU.$participateInSave (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:15492)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
	at Zb.Q (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155532)
	at Zb.M (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:154583)
...
	at addChunk (node:internal/streams/readable:559:12)
	at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
log.ts:439   ERR NO notebook document for 'file:///home/REDACTED/repro/repro.ipynb': Error: NO notebook document for 'file:///home/REDACTED/repro/repro.ipynb'
	at nh.getNotebookDocument (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:5868)
	at DU.$acceptDirtyStateChanged (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:16528)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
	at Zb.Q (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155532)
...
	at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
log.ts:439   ERR NO notebook document for 'file:///home/REDACTED/repro/repro.ipynb': Error: NO notebook document for 'file:///home/REDACTED/repro/repro.ipynb'
	at nh.getNotebookDocument (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:5868)
	at DU.$acceptModelSaved (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:16612)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
...
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
log.ts:439   ERR unknown text editor: 1ddaceb1-9613-4685-bdb2-ee6adfc8d152. known editors:  : Error: unknown text editor: 1ddaceb1-9613-4685-bdb2-ee6adfc8d152. known editors:
	at nh.getEditorById (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:5598)
	at wb.$acceptEditorPropertiesChanged (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:16972)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
...
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
log.ts:439   ERR NO notebook document for 'file:///home/REDACTED/repro/repro.ipynb': Error: NO notebook document for 'file:///home/REDACTED/repro/repro.ipynb'
	at nh.getNotebookDocument (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:5868)
	at DU.$acceptModelChanged (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:16411)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
...
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
log.ts:439   ERR NO notebook document for 'file:///home/REDACTED/repro/repro.ipynb': Error: NO notebook document for 'file:///home/REDACTED/repro/repro.ipynb'
	at nh.getNotebookDocument (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:5868)
	at bb.$cellExecutionChanged (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:25626)
...
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)
4log.ts:439   ERR unknown text editor: 1ddaceb1-9613-4685-bdb2-ee6adfc8d152. known editors:  : Error: unknown text editor: 1ddaceb1-9613-4685-bdb2-ee6adfc8d152. known editors:
	at nh.getEditorById (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:5598)
	at wb.$acceptEditorPropertiesChanged (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:155:16972)
	at Zb.S (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155752)
	at Zb.Q (file:///home/REDACTED/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/out/vs/workbench/api/node/extensionHostProcess.js:31:155532)
...
	at Readable.push (node:internal/streams/readable:390:5)
	at TCP.onStreamRead (node:internal/stream_base_commons:191:23)

If the issue reproduces without pylance, the problem would not be related. You could log an issue on the Jupyter extension here:
https://github.com/microsoft/vscode-jupyter/issues

Done: https://github.com/microsoft/vscode-jupyter/issues/16193


Low legibility for code in help

Nordic use same color as comment for code in help make them very hard to read. Majority of other theme use string color. See screenshot
Nordic

Tokyonight

Thanks, will fix!

What highlight is used there?

It is @text.literal.


Fixing #9. Modified eclipse-birt-runtime to birt.

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io


add default snapshot to project config

Duped from #118 such that CI can run

This fixes the following bug when running cargo spatial local launch
Encountered an error during command execution.                                 Snapshot file is not set. Please provide a snapshot file using either t
he --snapshot flag or the 'defaultSnapshotUploadFilepath' field under 'snapshot' in the project configuration file

Could be that there's an alternative approach, but this felt easy enough.

Huh. Turns out the default shell changed for Windows machines since the last PR went through 😰
Check on #114:
Run pushd project-example && cargo spatial --verbose codegen && popd
  pushd project-example && cargo spatial --verbose codegen && popd
  shell: C:\windows\system32\cmd.exe /D /E:ON /V:OFF /S /C "CALL "{0}""
  env:
    SPATIAL_LIB_DIR: ../dependencies

Check on this one:
Run pushd project-example && cargo spatial --verbose codegen && popd
  pushd project-example && cargo spatial --verbose codegen && popd
  shell: C:\Program Files\PowerShell\6\pwsh.EXE -command ". '{0}'"
  env:
    SPATIAL_LIB_DIR: ../dependencies

Should be a simple fix though - I'll get that done and merged later today @johnpmayer 😄


Support IO Binding for merged decoder

As per title. The tests from pytest tests/onnxruntime/test_modeling.py -k "test_compare_to_io_binding and ORTModelForCausalLMIntegrationTest" -s all pass.
Before submitting

[x] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Detect the language of a code snippet in memory

This pull request adds a new class to Linguist to allow for the analysis of code snippets in memory (i.e. without a corresponding file on disk). It expands the API so that it is possible to do this:
require 'linguist'

blob = Linguist::MemoryBlob.new('README.asc', '==== Test\n\nTest app')
Linguist::Language.detect(blob)

It will make it possible to use Linguist in github/markup (as discussed in github/markup#468) without restricting the API (See usage of markup).

@bkeepers @arfon What do you think of this?

I'm at OSCON this week and slammed with some other stuff, so I won't get a chance to look at this until at least next week. Sorry!

I'm at OSCON this week and slammed with some other stuff, so I won't get a chance to look at this until at least next week. Sorry!

No problem! It can wait.

This looks pretty good.
I would love to see an implementation of https://github.com/github/markup using this API before this gets merged, just to make sure this makes sense.

I would love to see an implementation of https://github.com/github/markup using this API before this gets merged, just to make sure this makes sense.

I just opened a pull request on github/markup. It's not complete but it'll give you an idea of how Linguist::Blob can be used in github-markup.

@bkeepers Did you get a chance to look at the implementation?

@pchaigno I just checked it out and left some comments. Thanks for taking a crack at that.

@bkeepers @pchaigno - I found myself wanting exactly this functionality in Linguist this morning. What's the status of this as far as you are both concerned?

This branch is ready on my side. The PoC in github/markup works for me locally (I have to generate the samples.json file manually) but I wasn't able to make it work with Travis CI.

Closing in favour of #2694


Fail to compile on Ubuntu 16.4

os: ubuntu 16.4
GPU: Tesla V100-SXM2 *4 ,one node
cuda:9.1
nccl: 2.1.15
cudnn:7.0
cmd:
make CUDA_PATH=/usr/local/cuda CUDNN_PATH=/usr/lib/x86_64-linux-gnu  MPI_PATH=/usr/local/openmpi-1.10.2_cuda9.1 NCCL_PATH=/usr/lib/x86_64-linux-gnu  USE_TENSOR_CORES=1  ARCH=sm_70
while compile the benchmark, it met the error, just like:
./kernels/gemm_problems.h:2:0:   required from here
/usr/include/c++/6/tuple:489:65: error: mismatched argument pack lengths while expanding ‘std::is_convertible<_UElements&&, _Elements>’
return _and<is_convertible<_UElements&&, _Elements>...>::value;
^~~~~
/usr/include/c++/6/tuple:490:1: error: body of constexpr function ‘static constexpr bool std::_TC<, _Elements>::_ImplicitlyMoveConvertibleTuple() [with _UElements = {const std::tuple<int, int, int, bool, bool>&}; bool  = true; _Elements = {int, int, int, bool, bool}]’ not a return-statement
}
^
Makefile:30: recipe for target 'gemm' failed
make[1]: *** [gemm] Error 1
make[1]: Leaving directory '/root/DeepBench/code/nvidia'
can you give me some suggestion.

Is this still an issue? I don't see this error on our end.


Markdown syntax problems in manpages

There are errors in the manpages because parameters in angle brackets aren't included in md2man output. For example,
**ADD ["<src>"... "<dest>"]** This form is required for paths containing whitespace.

renders as
ADD [""... ""] This form is required for paths containing whitespace.

Note the missing <src> and <dest>.
This can also be seen in GitHub's rendering of the text:
ADD [""... ""] This form is required for paths containing whitespace.

ping @cpuguy83
On Mon, Feb 9, 2015 at 12:41 PM, Dan Lipsitt<EMAIL_ADDRESS>wrote:

There are errors in the manpages because parameters in angle brackets
aren't included in md2man output. For example
https://github.com/docker/docker/blame/master/docs/man/Dockerfile.5.md#L137,
ADD [""... ""] This form is required for paths containing whitespace.
renders as
ADD [""... ""] This form is required for paths containing whitespace.
Note the missing  and .
This can also be seen in GitHub's rendering of the text:
ADD [""... ""] This form is required for paths containing whitespace.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/10667.

Thanks, let me take a look.

Since this isn't fixed in docker/docker yet, I think it's appropriate that we leave this open. :wink:

Sorry, didn't realize GH would auto-close :)

btw, I don't like the fix I put in since it's perfectly valid to use raw html in MD, but I think it's better than not rendering anything at all.

What happens if you use backticks to protect the params (<foo>)? Sorry I don't have time to experiment right now.

Is using <something> the standard way to notate things in man-pages, or a convention that Docker uses?
Asking, because the same problem occurred on a couple of pages of the documentation as well; the values did not show up on GitHub when viewing the docs.
If it is not a standard notation in man-pages, perhaps Docker should use a different convention in stead of modifying md2man, because other MarkDown renderers have the same problem.

@thaJeztah It's pretty common when writing CLI docs to use <something> as a way to indicate a required argument (vs [something] as not required)

can md2man be made to support < and > ?

@duglin Can you open an issue on the repo with what you expect it to output?

@cpuguy83 thanks for explaining.

btw, I don't like the fix I put in since it's perfectly valid to use raw html in MD, but I think it's better than not rendering anything at all.

Looking at the man-page on GitHub, the pages look mangled as well. I think the problem overall is that they use a bit of a "MarkDown-ish" syntax; everything is assumed to be "<pre>" and only a sub-set of MarkDown (Head (#), bold and italic) is used.
I think from that perspective, it's reasonable to not support HTML?

Yeah, I tend to agree that this looks like a bug in our use of Markdown
here, not a bug in go-md2man.

Perhaps call it MarkDown-flavoured plain-text, and change the file extension to .txt, to make it better readable on GitHub as well.

Opened issue in md2man: https://github.com/cpuguy83/go-md2man/issues/11

so what was the outcome here @cpuguy83 can you triage and add the right labels so someone can contribute it to fix it if they see this issue

Triaged

Closing since these man pages were updated.
If anyone sees a specific problem, please open a new issue with that specific problem.
Thanks!


Add quincynjoroge's fileCreate new file

I have created a branch, file, made a commit and opened a pull request

Thank you.


Fix parser.

skipSpace consumes whitespace, leading to strange endOfLine behavior. Removing this and adding 'endOfInput' leads to the expected parser output (at least for test.hasm).

Merged manually.


Added spo-get-files-and-creators-modifiers example

For your consideration

Hey @ToddKlindt, all processed, thank you - great sample!! 👏😊 This should be live shortly 😊


Add support for Elastic Stack 7.0

This PR adds support for Elastic Stack 7.0 to the Azure ARM template.

Adds apm_system and remote_monitoring_user built-in user accounts to setup accounts for Elasticsearch 6.5.0+.
Removes the es_read user account setup from the template. This user account is a long carried over artifact from very early versions of the template which can easily be setup post-deployment.

Closes #274

run
npm run links -- --branch master

before merging


Retrieve VOs from token

Take into account that:

I removed support for DEEP IAM because it does not support VOs.
We could potentially handle that corner case and make DEEP-IAM users to deploy in the ai4eosc namespace. But the code will eventually get dirty as we would need to check that DEEP-IAM IDs do not clash with EGI IDs and so on. I would rather start from a nice foundation and only support EGI Checkin, which will be anyways the default authentication method for the project.

You have to enable the eduperson_entitlement scope to access the VOs, so you might need to reconfigure your oidc-agent for EGI Checkin.
https://github.com/AI4EOSC/ai4-lib/tree/auth#generate-a-token-via-the-terminal
Or you could use EGI Checkin UI to get the token:
https://github.com/AI4EOSC/ai4-lib/tree/auth#generate-a-token-with-a-ui

I was not able to use oidc-agent (because it can't work as a registered client, of course) to generate EGI tokens, but they can be obtained easily at https://aai.egi.eu/token - including a refresh token all with a curl command for generation of 1-hour access tokens and id tokens. The curl command needs to be modified a bit, the offline_access scope needs to be added in the list of scopes at the end of the URL.


Add robl sshkey

This PR makes no actual changes (the commits add a public key file, then remove it). Closing.


beta.8 break update webapi

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

custom data service extending EntityCollectionServiceBase
call update base method with Partial<T>
remote is called with complex object of type Update: {id: string|number, changes: T}

Any log messages given by the failure

Expected/desired behavior

as the behavior before Beta 8, the remote call's body should be entity T flat object only, which is what the dotnet core webapi expect: a full updated entity. Complex object like Update is difficult to work with for webapi.

OS and Version?

Windows 10

Versions

beta.8

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Correction: complex object like Update is NOT difficult to work with for webapi, but to me, it is very strange and unnecessary to me.
I have not checked the Restful spec, but if the spec specify as such, it is a bug fix rather than a bug.

It should NOT send Update to a server. Should just be the entity. I will confirm your finding and fix. I wonder how it got by my tests? Maybe I wrote a bad test.

Found the bug ... and how my tests missed it. Fixing. Will be fixed in Beta 9.

Thanks for the fix. Is this the new ngrx-breeze in the near future?
On Mon, 2 Jul 2018 at 21:32, Ward Bell<EMAIL_ADDRESS>wrote:

Found the bug ... and how my tests missed it. Fixing. Will be fixed in
Beta 9.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/johnpapa/angular-ngrx-data/issues/165#issuecomment-401925532,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKY6h9aTWyVrPaAVlxipl5LI47iviptkks5uCoNggaJpZM4U8qcf
.

Closed by Beta 9.

Is this the new ngrx-breeze in the near future?

LOL. It certainly is acquiring Breeze features.  It's not nearly as capable as Breeze. Not as heavy either. We'll see where the real world use cases drive us!


proto: convert integer to rune before converting to string

Go 1.15 introduced a new go vet warning (https://golang.org/doc/go1.15#vet) for conversions of the form string(x) where x is an integer type other than rune or byte. This warning is enabled by default when running go test. As a consequence, running go test github.com/golang/protobuf/proto results in a build failure prior to this commit.
Fixes #1209.

We consider development of the github.com/golang/protobuf module frozen at this point. However, it is an important goal that the module continues to work with higher versions of Go. Therefore, this change is justified.
The PR looks good to me, but will require the CLA to be signed in order to be merged.

Thank you for merging and for the very quick response time! :)


Skip checking a file if it failed to read

Summary
Up to know, there was the risk of a race condition between when we discovered the files of a package and when we called check_file
because a file could have been deleted in the meantime before the file watch notification came in. This PR changes check_file to raise an error (diagnostic) if that happens.
I explored a few different designs and ultimately ended with using an accumulator. It's not the nicest API.
try_source_text function with specify
My first approach was to introduce a try_source_text that returns a Result<SourceText, SourceTextError> and uses specify (Salsa) to cache the read source text
when the file could be read successfully. Unfortunately, this doesn't work because specify requires that the query arguments are tracked Salsa structs, but File is an input.
try_source_text query
My second approach was to change source_text to try_source_text that returns a Result<SourceText, SourceTextError (now a salsa query) and
to introduce a new source_text function (not a salsa query) that invokes the fallback logic.
This could technically work but there are a few caveats:

Every (uncached) source_text call would create an empty fallback notebook. This should not be too bad because we only do this when we have a very specific race.
std::io::Error doesn't implement Eq. That means source_text can no longer use Salsa's backdating optimization (because the Result no longer implements Eq)

Accumulator
I do this in this PR: I use a salsa accumulator to emit a diagnostic in source text and explicitly consume the diagnostic in check_file.
I would have preferred if the test for reading the file was more explicit (e.g., by using a Result), but I also think the way it is now is fine.
However, we'll have to add these checks everywhere where we perform file-centric operations (check, fix, format).
We don't need the check for other operations like providing auto-completion because the fallback of an empty document is sufficient in that case.
The fallback primarily exists to avoid creating additional diagnostics because the text is empty.
Should we just change source_text to always return a Result.
Besides the points mentioned above: Changing source_text to return a Result would require making all queries that transitively read a file's source text (which is almost all queries)
to return a Result. That would be very painful without having a clear upside. In most cases, assuming the file is empty is actually a pretty good default (e.g., it results in an import not found* error when trying to import a symbol from that file. This is not 100% accurate but good enough considering that this is a race condition.

Test Plan
See the added integration test

I think what @carljm would prefer is:

Add a has_read_errors() method to SourceText and set it to true if reading the file failed.
Define Diagnostics in ruff_db and pull the diagnostics in RootDatabase::check and RootDatabase::check_file.

I thought about this more. I don't mind adding a flag to source text and testing that flag instead of branching based on whether there are Diagnostics.
But I do prefer to defer the decision on whether we want a single Diagnostic type or not because that's less clear to me, but I plan to look into it next week.
That's why I would prefer keeping the accumulator as is (querying an accumulator in a query is supported by salsa).

Tbh it seems to me that having source_text query return a Result is a pretty good option here: it's the most idiomatic/intuitive way to represent this. The Result doesn't have to carry the original std::io::Error, it can carry our own error type that does implement Eq, so back-dating can still work. Caller queries shouldn't care about the details of the I/O error anyway, those details just belong in the user diagnostic.
And the concern about all dependent queries then also having to return a Result doesn't make sense to me. The whole point of this PR is that caller queries should be aware if there was a file read error and handle it in some way. It's better if they have to be aware of it. Returning a Result achieves that. It doesn't force them to propagate the Result; they can instead match on it and handle the Err branch however they want (e.g. abort checking, or whatever makes sense.) There is no law requiring use of the ? operator to handle a Result ;)

Tbh it seems to me that just having source_text query return a Result is a pretty good option here: it's the most idiomatic/intuitive way to represent this. The Result doesn't have to carry the original std::io::Error, it can carry our own error type that does implement Eq, so back-dating can still work. Caller queries shouldn't care about the details of the I/O error anyway, those details just belong in the user diagnostic.

We could do that, although I would then just return an Option. But I don't think we should do it...

And the concern about all dependent queries then also having to return a Result doesn't make sense to me. The whole point of this PR is that caller queries should be aware if there was a file read error and handle it in some way.

To me, the only two options are:

source_text emits the diagnostic and performs the recovery itself as it does today
All queries that use source_text or transitively depend on it return Result

The middle ground doesn't make sense to me. It only introduces unclear responsibilities:B
If source_text returns an Result, is it then the responsibility of parsed_module to do the error recovery? I don't think it should because we could then as well have done the error recovery in source_text. That leaves the question about which query should then do the error recovery? It would have to be the top queries: format, lint_syntax, lint_semantic because they can then decide not to emit diagnostics. That's option 2 and it introduces the ambiguity of who's now responsible for emitting a diagnostic. Only one method should push a diagnostic of we end up with duplicates but we can't know which queries are called in a single execution. It can be format only or format, lint and type_check.
Returning a Result would work better in a non-Salsa world where check_file would read the result, deal with any IO errors and call into lint_syntax when there are none, passing the source code as an argument. But this doesn't work in a salsa design where queries pull the information they need. There's not even a need for check_file to call source_text at all because it doesn't need to pass the result as an argument to any functions it calls. That means, requiring explicit error handling doesn't really work (unless we propagate the error everywhere through) because:

The methods that should handle the error have no need to call source_text, and therefore, don't profit from any explicit error handling
The methods that don't care about error handling (because they should be resilient to errors, similar to the parser) don't really know what to do, other than implementing their own error recovery mechanism

That's why I still think that doing the error recovery in source_text is the right approach. I think adding a boolean flag to SourceText indicating whether the read has failed and can be used to make such decisions does make sense.

I agree that there should be clear responsibilities. To me, clear responsibilities means that whatever layer wants to be able to make a different decision depending on whether there was an error, is the (only) layer that should handle the error, and report an appropriate diagnostic to the user depending on its specific needs.
To me, that means that source_text should return a Result (or Option, if callers never need to distinguish different failure modes, which seems plausible) and not report any diagnostic or provide any fallback, parsed_module should propagate the error/option and likewise not report any diagnostic or provide any fallback, and any queries that call parsed_module should "catch" the error/option and take action as appropriate for their particular case, including possibly reporting a diagnostic.

To me, that means that source_text should return a Result (or Option, if callers never need to distinguish different failure modes, which seems plausible) and not report any diagnostic or provide any fallback, parsed_module should propagate the error/option and likewise not report any diagnostic or provide any fallback, and any queries that call parsed_module should "catch" the error/option and take action as appropriate for their particular case, including possibly reporting a diagnostic. (And not propagate the error/option, of course.)

Yeah, but I don't see how this can work (as explained above)

Multiple queries call parsed_module at different stages. There's no guarantee in which order or which queries are executed. We would report the same diagnostic multiple times or never
Let's say parsed_module propagates the error. But which query catches it? semantic_index? It can't, because lint_syntax would then still not have to deal with handling the error. So it has to propagate and so do all type inference methods all the way up to lint_syntax

I would need to look at the details of who actually calls parsed_module, but I need to go to sleep now instead :) I think the more principled approach is to propagate as much as needed to avoid that problem, but I'm also fine with falling back to empty plus setting a flag if you prefer to go that route!

Everything calls parsed_module transitively. Every SemanticIndex method ;) My worry is that it would make our code extremely cumbersome. All code in type inference would have to deal with the possibility that the semantic index is None because we can't statically assert that it is guaranteed to be non-none when doing type inference.
I'm happy to discuss this more in person but I do think a flag is the best way to go. It's also closest to what we already to with our AST where incorrect identifiers are "marked" as invalid and require explicit checking, because for most code, it doesn't matter.

Overall, this seems a fundamental design question and I think our two options really are:

Handle the error in source_text and recover
Propagate the query through the entire semantic analysis and bubble it up all the way to check_file. But that would mean that all our query methods (and all methods that use anything derived from a query) become Result. I don't think it's worth the complexity that it introduces.


INT-B-18637 create bb order type

Agility ticket
Summary
Added BLUEBARK order type as well as labels on all Office Queues and on the Move Details header for office users and customers.
Verification Steps for the Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[ ] Have the BL acceptance criteria been met for this change?
[ ] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test

Access the customer app
Login as a new user
Create a move with the BLUEBARK order type
Test BLUEBARK label on customer home page header
Login as a TOO/TIO/SC/QAE and search for new move
Make sure BLUEBARK label is visible within the move queue and on the Move Details Header

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 32b9a1eec0f56451a9cb7330065ddabd64b6eb07


suspended in standby state

Same, IDK how to fix. I am on Windows tho.

Windows: Install Visual C++. Then re-open Mechvibes.
MacOS: System Preferences > Privacy > Mechvibes and enable. Then re-open Mechvibes.


Window Switcher / Alt-Tab functionality

So far I'm really loving this compositor!
Having a functionality similar to gnome/windows's alt-tab feature to switch between all active windows from all workspaces would be great to see, or some sort of plugin to waybar to show a task switcher  / minimized applications

gnome/windows's

You just described perfectly what this compositor is aiming not to be.
You can use cyclenext to cycle between windows on the same workspace and workspace to switch workspaces. An overview like this will not be added.


unexpected console output while using JSModuleContext

js host code:
        var engine = new JsModuleContext();
        engine.ConsoleEvent += Engine_ConsoleEvent;
        engine.Log += Engine_Log;

        await engine.RunAsync(rootdir,"test.js");

test.js
//test.js
console.log ("hello");

after compile and test this program I got unexpected console output:
2024/4/9 7:11:24 - Compiling module V:\test\yantratest\yantratest\js\./test.js
hello

which is problematic , cause it may break my console output format.
I checked YantraJs source found the problem is in JSModuleContext.js line 380
Console.WriteLine($"{DateTime.Now} - Compiling module {module.filePath}");

is this part of design ?

@fsz1987 no it is not part of design, I will remove it. It was added for debugging.


can: overlay and config for reel board CAN expansion

Overlay and config for reel board can expansion. Draft for driver and hardware testing only.
@karstenkoenig FYI

This is awesome!

@jfischer-phytec-iot can you make a shield for the board?

@alexanderwachter Not sure about the particularities for the reel board as it has a properly defined connector, but I also tried making a general mcp2515 shield before (for the cheap aliexpress breakout boards) and sort of gave up because SPI CS and various other GPIOs doesn't really work well for the shields yet. That's why there is the mcp2515-dts.overlay in the samples so people can at least find a place to start and (fairly) straight forward adjust the cs and irq gpios.
There is a few discussions ongoing such as
https://github.com/zephyrproject-rtos/zephyr/issues/15637
https://github.com/zephyrproject-rtos/zephyr/pull/14057
but no short term solution. So I think the straightest way ahead is creating a boards folder and tossing the overlays and configs in there until there is a proper solution in place.
I added a board folder here https://github.com/zephyrproject-rtos/zephyr/pull/15658

This PR could be closed. #18081 includes the dts and config.


refactor: [M3-5181] - React Query for Events

Description 📝

React Query-ifys our events / events polling system
This PR's polling system should match the behavior of the existing polling system. The main changes revolve around  the fact that we are now storing and retrieving data from the React Query cache.
This is take two of https://github.com/linode/manager/pull/9416 because we had to revert it https://github.com/linode/manager/pull/9444

The big "bug" with that PR was that useEventsInfiniteQuery was mounted many times, which also mounted the cache updating code many times, which caused many renders to happen when event were polled. This PR fixed that by only mounting a polling hook that update the cache once.
This PR takes some inspiration from https://github.com/linode/manager/pull/9416, but is different in some ways

Main Additions
useEventsPoller ⏲

A hook mounted at the root of the app, which is responsible for polling the events endpoint for new events
This hook is responsible for

Updating the cache based on the events it polls
Showing toast notifications for global toasts (like volume_delete for example)
Invoking our React Query event handlers (volumeEventsHandler for example)

useInProgressEvents 📇

A hook that returns only active / in-progress events
Used in LinodeRow for example

useEventsInfiniteQuery 📃

Used to render lists of events
This is used for EventsLanding, LinodeActivity, and the Event Menu

Other mentions

Removes rxjs dependency 🎉
Removes events completely from Redux 🗑

How to test 🧪

Verify that all "real-time" feature of Cloud Manager work

For example, rebooting a Linode, shutting down a Linode, resizing a Linode, ...

Test polling behavior compared to production

Verify that this PR does not cause a significant change in the frequency in which we poll the events endpoint

Test the http://localhost:3000/events page

Verify the infinite scrolling works as expected
Verify the events are in the correct order
Verify new events show up in realtime

Test the Linode Details events tab

Verify the infinite scrolling works as expected
Verify the events are in the correct order
Verify new events show up in realtime

Test on a large account
Check for bad performance
Check the functionality of the Events / Notification Menu in the top navigation

As an Author I have considered 🤔

[ ] 👀 Doing a self review
[ ] ❔ Our contribution guidelines
[ ] 🤏 Splitting feature into small PRs
[ ] ➕ Adding a changeset
[ ] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[ ] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

@bnussman sorry for taking time to review this. would you mind going through a more exhaustive self review? To be frank I have little knowledge or experience with this part of the code base and any help reviewing it would be greatly appreciated considering the size of the PR. thx!

The comments in the code contain most of my self-review, but I'll continue to document and review where I can! @abailly-akamai


Retry failed block requests

This required quite a lot of additional machinery in order to inform the BlockStore of request failures, so it can retry.
Now, whenever we send a direct external message in node.rs, we remember a request_id which is returned to the caller. One level up, we keep a correspondence of our generated request_id to libp2p's request ID. When a request succeds or fails, we can look up the request_id in this map and pass it back down the stack to inform the initial caller of the result.
We've also changed the type which gets sent from the network layer to the node.rs layer from an ExternalMessage to a Result<ExternalMessage, OutgoingMessageFailure>. The Err half is how failed messages are passed down.

PS - I think we've discussed this before, but it's safe for stuff to expire from the LRU cache, right?


feat: jl projection

Summary
This pr implemented the JL projection method that projects the given polynomial ring matrix to a polynomial ring matrix with smaller dimension.
Example
Given a data matrix D_{2, 256} by setting the target dimension of 128, the expected result would be a data matrix of D_{2, 128}

In the Greyhound paper (https://eprint.iacr.org/2024/1293.pdf#page=28.41), they made some changes to the details of the JL project. I think we should follow these changes. But I'm not sure what the probability distribution of {1, -1}, maybe 1/2?


[FIX] fix typo in PR title which got into src/CHANGES.md

That leads to failing CI as in
https://github.com/bids-standard/bids-specification/pull/1120/files#file-src-changes-md-L13
Ideally we should add spell checking for PR title, but those would keep changing,
would need separate workflow and react to changes to titles and then have no way
to easily say "ignore". May be src/CHANGES.md should be excluded... separate issue would
that be

Won't the changelog updater automatically fix it since @effigies corrected the PR title, the next time there's a merged PR to trigger it?

Won't the changelog updater automatically fix it since @effigies corrected the PR title, the next time there's a merged PR to trigger it?

I hope that changelog updated considers only relevant PRs since the last release and not all PRs historically since that would be growing burden to avoid. ... indeed looking at https://github.com/bids-standard/bids-specification/blob/HEAD/.circleci/config.yml#L176  it considers only the last merge commit, so no retroactive fixes

It will happily modify any entry since the first GitHub version if we go and change the titles.

how would it do that if it works only on the latest one (git log -1)??? point blind me to the code

https://github.com/bids-standard/bids-specification/blob/e347f304b18ef5c230c8d223a85e15eac18c0909/.circleci/config.yml#L108-L120


Unable to download ruby source for the version 2.1, 2.2 and 2.3 while building

What problems are you experiencing?
Unable to download the ruby source when the rake task rake ruby23 DKVER=mingw64-64-4.7.2 is ran.
Steps to reproduce

Go to ruby installer path
Run rake ruby23 DKVER=mingw64-64-4.7.2

We see this error
rake aborted!
URI::NotFoundError: Looking for http://cache.ruby-lang.org/pub/ruby/2.3//ruby-2.3.3.tar.bz2 and all I got was a 404!

What's the output from ruby -v?
ruby 2.3.5p376 (2017-09-14 revision 59905) [x64-mingw32]

URI::NotFoundError: Looking for http://cache.ruby-lang.org/pub/ruby/2.3//ruby-2.3.3.tar.bz2 and all I got was a 404!

http://cache.ruby-lang.org/pub/ruby/2.3//ruby-2.3.3.tar.bz2 should be http://cache.ruby-lang.org/pub/ruby/2.3/ruby-2.3.3.tar.bz2
note- https://www.ruby-lang.org/en/news/2019/03/31/support-of-ruby-2-3-has-ended/ on 31 Mar 201

fix for Ruby 2.1,2.2 & 2.3 ; looks good to me.

In 2008MigDate :10/14/2008 locked intel Project Ruby in Hardware construction


import process crashes with invalid file (no errors reported)

I am running the example application on Docker.  I find that the process crashes when using an incomplete 'artists' file.  I don't see any error message or warnings, the celery container eventually crashes with 'out of memory' error.
To reproduce (I have a branch here which runs the application in Docker - docker compose up --build):

Go to Artist import
Leave Resource on default of 'ArtistResourceWithM2M'
Choose the attached file (change name to 'artists.csv')
Click import

You will see the following requests:

In my Docker instance (running on MacOS) I see this error after about 5 mins:
[ERROR] Worker (pid:19) was sent SIGKILL! Perhaps out of memory?

No other errors are reported.
If you import the file 'artists-sm.csv' it runs fine (ensure an 'Instrument' FK exists with id=1).
artists.csv.txt
artists-sm.csv.txt

btw - it's taken me a little while to get the test_project up and running - I'm happy to add this to the documentation if that's of interest?

Hi @matthewhegarty ,
I found out the reason for out of memory, it happens when trying to render template. I removed extra loop, please try, will this fix your error?

Thanks - AFAICT it has the same issue.  I merged your branch and pushed here.
btw - am in the django-import-export discord if it helps.

I still get the same issue when using containers (it's the server container which crashes due to memory issues).
The process works fine when I run celery and server in my IDE (PyCharm), though it takes ~45 seconds to prepare the preview for importing 2k files (see artists.csv in thread above).  It would be ideal if the UI indicated that parsing has started - at the moment there is no feedback to the user.

@matthewhegarty So, i think problem inside your Dockerfile

RUN pip install poetry django-import-export-extensions

This command will install latest released version from pypi, which still has the issue.


Move SOS to SDK build

Add RestoreArcade target and some other properties to SOS NETCore project
Remove the hack to Skip SoS for arcade builds

The build phase goes through, overall build fails in packaging.


Two menus are displaying

Two Menus are displaying, how do I only show one?
I am using the media query example provided below.

I'm having the same issue except only got the script running once?!


Fixed disconnect async method resuming its continuation

By locking the async method we make sure it doesn't try to resume more than once which crashes the app

This will be merged with #8 because the commit in this branch was unverified


chore: refactor git protect branch check

Description
Refactor the branch protection check to a utility class as part of 1 click upgrade
PR fixes following issue(s)
Fixes # (issue number)
Type of change

Chore (housekeeping or task changes that don't impact user perception)

Testing
How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] JUnit

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

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

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test


Remove mytiki.com from app entitlements

As a mantainer I need to inform Apple about the domains that are handled by my app.
The mytiki.com domain SHOULD NOT be linked to the app.
The mytiki.app domain SHOULD be linked to the app.
Acceptance criteria

Remove any reference to mytiki.com from app entitlements
Confirm the references in the pipeline

#462


HADOOP-17388. AbstractS3ATokenIdentifier to issue date in UTC

In HADOOP-17379, I missed to set issue date as local timezone sensitive, whereas we actually set issue date in UTC.
https://github.com/apache/hadoop/blob/07050339e0a41a7d4b89b852ffdd7aa315a9184b/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/token/delegation/AbstractDelegationTokenSecretManager.java#L418-L439
This PR fixes the issue.

cc. @steveloughran Appreciate your review. Thanks!

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 14s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
41m  3s

trunk passed

+1 :green_heart:
compile
0m 58s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
compile
0m 44s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
checkstyle
0m 35s

trunk passed

+1 :green_heart:
mvnsite
0m 56s

trunk passed

+1 :green_heart:
shadedclient
21m 29s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 27s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
0m 38s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+0 :ok:
spotbugs
1m 28s

Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
1m 25s

trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 44s

the patch passed

+1 :green_heart:
compile
0m 48s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javac
0m 48s

the patch passed

+1 :green_heart:
compile
0m 38s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
javac
0m 38s

the patch passed

+1 :green_heart:
checkstyle
0m 23s

the patch passed

+1 :green_heart:
mvnsite
0m 45s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
shadedclient
19m 35s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 21s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
0m 31s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
findbugs
1m 25s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 31s

hadoop-aws in the patch passed.

-1 :x:
asflicense
0m 40s
/patch-asflicense-problems.txt
The patch generated 2 ASF License warnings.

98m 45s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2477/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2477

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 8e3234213756 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 07050339e0a

Default Java
Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2477/1/testReport/

Max. process+thread count
564 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2477/1/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Rationalization of no new test: tests were addressed in HADOOP-17379. Please let me know if we need to improve the test to strictly check for issue date that current time of UTC is returned.
asflicense looks to be false alarm, or real issue brought from other PR.

ASF license is an independent and I need to work out what's up there. We deleted those files earlier in the week, see

LGTM, +1

+1, merged to 3.3+

Thanks for reviewing and merging!


[bugs] Unable to login, make sure to login and keep your browser open. Error Failed to authenticate session

Can't log in with the browser.

Open AI API is OK, but I guess it's not ChatGPT but just GPT-3.

What's your OS, browser and versions? I just checked, it seems to be working for me with default settings (Chrome on Win11)

Chrome 110.0.5481.100 on Win 11.

Interesting, the extension is either not able to get your access token or see the textarea where you normally ask questions to chatgpt. Could you try closing all of your Chrome instances and let the extension log you in on a fresh browser? I can't reproduce your issue, tried a few times.

I try it again with your advice, but it also won't work. I guess it's because I need a proxy setting in the Vscode? I'm using a global socks proxy with v2ray to keep access the ChatGPT website.

Proxy sounds like the issue. Check this comment, it may help https://github.com/gencay/vscode-chatgpt/issues/77#issuecomment-1409346121

I tried it, not work either.

Why does your setting page have many models, but I just have two options?

Are you clicking/typing anywhere on the page until it logs you in and gets minimized? The second error in your screenshots suggests that your autologin flow may be interrupted.

Yes, maybe it is! I'm logged in success now. But Why did it happen?

Glad it worked @A11en0 ! As noted in Readme you should avoid interrupting the autologin flow and let it log you in and it will get automatically minimized. You shouldn't close the browser, since the extension uses browser to send and receive requests/responses from OpenAI via browser.

Cool! Sorry for my sloppiness, I think this is a significant consideration and it might be better to use bold and large-size fonts in the README.

Appreciate the feedback, I will update the Readme in the next iteration!

@A11en0 updated the readme with highlighted info regarding not interrupting the flow.


Add Dockerfile for riscv64-unknown-linux-gnu

See #1415

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @gnzlbg (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Note that this is not tested on CI, that would require adding a build job to .travis.yml. Is that intended ?

Not intended so much as I just wasn't sure how to add the job to CI. I'll make that change in a bit

I've restarted this particular build: https://travis-ci.com/rust-lang/libc/jobs/212378258

That runs into a sort of circular issue: there isn't a riscv64gc-unknown-linux-gnu target yet because the standard library can't be compiled for 64-bit RISC-V. And the standard library can't be build for it because libc doesn't yet support it.
Perhaps there'd be a way to temporarily use the risc64gc-unknown-none-elf target?

@fintelia to add new CPU and target at same time you have to fix and test everything locally using by building Rust with modified dependencies (like patched libc), get dependencies fixes merged, get new target merged and finally add tests everywhere once the target works.

@mati865 That makes more sense

@fintelia my recommendation is to add it as a libcore target only first to rust-lang/rust . That requires adding a target specification to rust-lang/rust/src/librustc_target, and not much more. Once that is done, libc is no_std, so it can be built against that. Once you have libcore and libc working, getting support for liballoc shouldn't be hard, you can just shim out to libc::malloc. The largest chunk of work is getting libstd support, depending on how similar this is to other unix targets, might be a breeze or not.

Good point, I didn't know you can make something as big as *-unknown-linux-gnu std-less.

Good point, I didn't know you can make something as big as *-unknown-linux-gnu std-less.

If the target isn't tier2, nothing is built, and then you have to build it with xargo, which you can use to build libcore only. So... it kind of works by omission 😆

Where is the tier listing actually specified in the rustc source? It seems that just adding a target spec file and including it in the supported_targets! macro is enough to cause ./x.py build to try building the standard library for that target

@fintelia you need to set no_std = true for your target here: https://github.com/rust-lang/rust/blob/03bd2f653f0d0adb69d862fbeec64663157e71e1/src/bootstrap/sanity.rs#L171

:umbrella: The latest upstream changes (presumably #1376) made this pull request unmergeable. Please resolve the merge conflicts.

This needs rebasing. What was previously in the .travis.yml needs to be moved to ci/azure.yml (check out how the other targets are added there - should be pretty similar).

ping

Sorry for the delay on this. I don't think I'm going to have a chance to go through all of the steps to get this together in the near term so if anyone else is interested feel free to take over

@msizanoen1 please feel free to fork this branch and update it as you see fit and submit a PR.

Actually getting std to compile for riscv64 is pretty simple: https://github.com/rust-lang/rust/compare/master...msizanoen1:riscv-std

The dockerfile is added by #1684 and I'm closing this in favor of it, thanks for contributing!


[bug] Grouping by security level has duplicate groups

Version
zwavejs2mqtt: 6.2.0
zwave-js: 8.9.1
home id:<PHONE_NUMBER>
home hex: 0xe3722143
Checklist:

[x] I am not using Home Assistant. Or: a developer has told me to come here.
[x] I have checked the troubleshooting section and my problem is not described there.
[x] I have read the changelog and my problem is not mentioned there.

Build/Run method

[x] Docker
[ ] PKG
[ ] Snap package
[ ] Manually built (git clone - yarn install - yarn run build )

Describe the bug
When grouping by Security level, I get the below image - the "None" security has been duplicated into two seperate groups. The groups with blank texts ("") are probably a migration thing.

To Reproduce
On my end I simply group the security column, and there are duplicate groups.

Expected behavior
Only one of each grouped value appears. All devices are moved to the corresponding group.
Additional context

If I minimize one of the "None" groups, all of the None groups are minimized. So they are likely the "same", just not visually grouped.

@ahochsteger ?

I guess it has to do with #1977 - I'll look into it.

@ahochsteger Thanks! :)

Fixed by #2414


Include working example

Would it be possible to provide a working exampleand also include the needed CSS Files to make it work?
would be great..

Hello, it would be very useful, as it seems that the HTML markup is different from the one generated by the jQuery version, so the CSS used in that example on Codepen is not quickly reusable.
I'm also unable to get it working properly, as in my case it always displays the dropdown menu and not the default menu, no matter the viewport width. Without a live example to compare to it's hard to debug.

Even a link to a demo on Codepen in the README would be helpful ...


Parameter name "in" appears to be reserved

ColdFusion 2016 throws a compiler error if "in" is used as a function parameter name. It appears to be reserved.

Looks great! Thanks for the contribution!
@all-contributors please add @JamoCA for bug and code

@JamoCA any interest in becoming a committer?

Sure. I was evaluating feature flags back when Ben was initially blogging about them and wasn't interested in paying for something could be done with CFML.  I plan on adding this library to a couple projects.  I prefer to write code compatible with current Lucee and CF2016+. (This is my migration path at the moment.)


HADOOP-17650. Bump solr to unblock build failure with Maven 3.8.1 (#2939)

Reviewed-by: Siyao Meng<EMAIL_ADDRESS>Description of PR
patch 538ce9c / #2939 on branch-3.3; if good will add to 3.3.3
without this you can only build hadoop with a proxy nexus server
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

just having nexus review this; will merge if it is happy


NIFI-10991 Add AWS MSK IAM support to Kafka processors

Summary
NIFI-10991
This PR adds AWS IAM for authentication and authorization functionality against Amazon MSK clusters that have AWS IAM enabled as an authentication mechanism. You need to enable include-kafka-aws profile to include the required module. A previous PR (https://github.com/apache/nifi/pull/5291) tried to tackle this problem. In this PR, though, we decided not to include awsRoleArn, awsRoleSessionName, awsStsRegion as properties because they just add extra complexity with minimal value. When NiFi runs in EC2, and no profile is specified, the processor will use the role assigned to the EC2 instance. When NiFi runs locally, we can define a profile name that will reference a profile in ~/.aws/credentials (depends on os) file. In this file, you can specify the above properties along with the access key id and secret.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 8
[ ] JDK 11
[ ] JDK 17

Licensing

[x] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[x] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Thank you for the review @turcsanyip and @exceptionfactory! I've changed the code based on your advice.

@nandorsoma There seems to be regression in the kerberos login.
I get the error below when trying to connect to a kerberized kafka using SASL_SSL + GSSAPI. I built the processors without the new include-kafka-aws profile. The same flow works with the version on the current main branch.
2023-01-18 14:28:17,992 WARN [Timer-Driven Process Thread-9] o.a.n.controller.tasks.ConnectableTask Processing halted: uncaught exception in Component [PublishKafka_2_6[id=c49ff5ca-0185-1000-d5c3-1f042d05afeb]]
org.apache.kafka.common.KafkaException: Failed to construct kafka producer
	at org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:441)
	at org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:273)
	at org.apache.nifi.processors.kafka.pubsub.PublisherPool.createLease(PublisherPool.java:88)
	at org.apache.nifi.processors.kafka.pubsub.PublisherPool.obtainPublisher(PublisherPool.java:78)
	at org.apache.nifi.processors.kafka.pubsub.PublishKafka_2_6.onTrigger(PublishKafka_2_6.java:444)
	at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
	at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1356)
	at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:246)
	at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:102)
	at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: Value not specified for key 'required' in JAAS config
	at org.apache.kafka.common.security.JaasConfig.parseAppConfigurationEntry(JaasConfig.java:116)
	at org.apache.kafka.common.security.JaasConfig.<init>(JaasConfig.java:63)
	at org.apache.kafka.common.security.JaasContext.load(JaasContext.java:90)
	at org.apache.kafka.common.security.JaasContext.loadClientContext(JaasContext.java:84)
	at org.apache.kafka.common.network.ChannelBuilders.create(ChannelBuilders.java:134)
	at org.apache.kafka.common.network.ChannelBuilders.clientChannelBuilder(ChannelBuilders.java:73)
	at org.apache.kafka.clients.ClientUtils.createChannelBuilder(ClientUtils.java:105)
	at org.apache.kafka.clients.producer.KafkaProducer.newSender(KafkaProducer.java:449)
	at org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:430)
	... 16 common frames omitted

I felt quite confusing that the kerberos properties are always shown on the processor, even when they are not relevant, and it is not clear which properties belong to the given authentication type that should be filled in (in case of PLAINTEXT or SCRAM, and also the new AWS IAM). Not sure why dependsOn() has not been applied here so far. I would suggest implementing it either in this PR or in a follow-up one.

@turcsanyip Due to changes over time, there are multiple ways to configure Kerberos credentials, so that is part of the reason that some Kerberos properties are always shown. It might be possible to improve this in some scenarios, and that could be a useful improvement in a separate effort.

Thank you @turcsanyip for your review! I've changed what you have asked except the dependsOn part. I'll do that in a separate PR as @exceptionfactory suggested.


Jesse: Watch makeo.app

Jesse requests the watch of the watch_keyword makeo\.app. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

makeo\.app has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Persist environment variables from commands

Feature description 💡
Currently when environment variables are set in a BASH command, those variables do not persist in the flow. For example, let's say I want to assume a role in AWS and then run terraform plan. I want to accomplish this with the following template:
flow:
  - type: "terraformPlan"
    name: "Init and Plan"
    step: 100
    commands:
      - runtime: "BASH"
        priority: 100
        before: true
        script: |
          creds=$(aws sts assume-role --role-arn 'arn:aws:iam::123456789012:role/terrakube-role' --role-session-name session --output json)
          export AWS_ACCESS_KEY_ID=$(echo $creds | jq '.Credentials.AccessKeyId')
          export AWS_SECRET_ACCESS_KEY=$(echo $creds | jq '.Credentials.SecretAccessKey')
          export AWS_SESSION_TOKEN=$(echo $creds | jq '.Credentials.SessionToken')

That way, terraform can plan and apply using the designated role
Anything else?
No response

I think you could write a "auto.tfvars" file so terraform can pick the values from there

That works if we need them as terraform variables, but this is a session that expires and our terraform code expects the user to be already authenticated to AWS, that's why there is a need for injecting these environment variables to the job.

That works if we need them as terraform variables, but this is a session that expires and our terraform code expects the user to be already authenticated to AWS, that's why there is a need for injecting these environment variables to the job.

Adding that to save the environment variables will require some work.
Another alternative will be that you use "aws dynamic credentials" so the workspace can authenticate automatically with AWS automatically without any kind of secrets, instead of defining "AWS_ACCESS_KEY_ID", "AWS_SECRET_ACCESS_KEY" and "AWS_SESSION_TOKEN"
You could check here for the AWS dynamic credentials support:
https://docs.terrakube.io/user-guide/workspaces/dynamic-provider-credentials/aws-dynamic-provider-credentials


Created the admin page and servlet, also added the path to the admin …

…page in the path if and only if the user is an admin. Also fix a bug of creating a conversation with an empty title

https://drive.google.com/open?id=10_VDotqMZsrebk-GzTZsi4YRtpbaLUlp


fix: Disable opening animation for side Split panel

Description
A month ago we discovered that split panel opening animation is not working due to a typo, the fix was done in this PR https://github.com/cloudscape-design/components/pull/1471 .
After the fix was out we got reports that resizing the split panel is laggy and leaves a right gap while resizing, the issue is reproducible only in React 18 when createRoot is used and the page has many components like table.
the issue is due to some excessive rerendering issues, fixing that is not trivial as it needs refactoring different parts of AppLayout and SplitPanel
After discussing with the team we decided to disable animations back as mitigation for now.
Related links: AWSUI-22396
How has this been tested?

Upgrade to react 18
Use createRoot in dev pages
visit a dev page with split pane and a table
before this commit you should see the same bug in the reported ticket

Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness

Changes include appropriate documentation updates.
Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
Changes do not include unsupported browser features, see CONTRIBUTING.md.
Changes were manually tested for accessibility, see accessibility guidelines.

Security

If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

Changes are covered with new/existing unit tests?
Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Does the issue happen only when resizing, or also when showing and hiding? If only when resizing, can we remove the animation only when resizing? Because I don't think the animation should be applied while resizing anyway.

Does the issue happen only when resizing, or also when showing and hiding? If only when resizing, can we remove the animation only when resizing? Because I don't think the animation should be applied while resizing anyway.

@jperals animation should only happen when showing, however for it to work properly we need to pass the split panel size which gets updated on resizing causing the excessive re-rendering issue, passing the size only when the split panel opens  is not possible as it will cause wrapping issues while opening the split panel, we also need to pass the last reported size after resizing finishes, I tried doing that by adding another property to both the split panel and app layout context that gets updated onkeyup after resizing or when split panel is closed but the problem was getting the first width when the page renders, multiple rerenders happen and it's tricky to get which is the last render before opening, solving that is theoretically possible but it needs lots of refactoring and optimising both in App layout and Split panel and it has a risk of breaking other more important behaviour.


Comparing IP addresses and MAC addresses results in stack overflow

If a program attempts to compare an IP address with an Ethernet (MAC) address (such as using "is"), rather than resulting in an appropriate error stating invalid types were used for comparison, some mutual recursion results which only terminates on a stack overflow and a program crash.

import ipaddress
import netifaces

# Example IP and MAC addresses
ip_address = ipaddress.ip_address('<IP_ADDRESS>')
mac_address = netifaces.ifaddresses('eth0')[netifaces.AF_LINK][0]['addr']

# Comparing IP and MAC addresses
if ip_address == mac_address:
    print("IP and MAC addresses are equal.")
else:
    print("IP and MAC addresses are not equal.")


Inconsistent health.status in Kargo from what is shown in Argo

Checklist

[x] I've searched the issue queue to verify this is not a duplicate bug report.
[x] I've included steps to reproduce the bug.
[x] I've pasted the output of kargo version.
[x] I've pasted logs, if applicable.

Description
Kargo stages seem to be inconsistent with what constitutes "Healthy" and "Unhealthy" health.status
In the attached screenshots, the first is reporting "Unhealthy" because the Argo CD Application is out of sync. Then Healthy even when the syncStatus.status is still OutOfSync.
In both of these cases Argo CD shows the Application as "Healthy", which is what I expect to be reflected in Kargo.
Screenshots

Steps to Reproduce
Unfortunately this just pops up sometimes... I'm not sure how to reproduce it.
Version
Running in a kubernetes cluster along side argocd
The screenshots were taken in v0.8.5
We just upgraded to v0.8.7, I'll confirm here if I see this pop up in v0.8.7

This isn't a bug. This is because Stage health and App health are not the same thing.
App health factors into Stage health, but they are not the same.
Consider the following:

Some Stages may not have any Apps at all.

Some Stages may have multiple Apps.

An App that is out sync in Argo CD can be "normal," as believe it or not, many Apps exist in a perpetual state of drift.

An App that is in sync in Argo CD may still be problematic from Kargo's perspective if it is synced to the wrong revision.

Kargo may integrate well with Argo CD, but it would be short sighted of us if it were going to work only with Argo CD forever. Our plans are bigger than that. Consider especially that we are working hard to make Kargo extensible, which means any number of third-party integrations are on the horizon and they may all contribute to the health equation in different ways.

Taken all together, Kargo Stage health is a not the same as App health. What it is is as comprehensive a snapshot of how the Stage is doing at the moment. We are always trying to improve it, but at the moment, if you are using it with Argo CD, a Stage is going to appear healthy if all related Apps are Healthy, synced to the correct revision(s), and done syncing, even if they report being out of sync. i.e. Apps being done syncing to the right things + being healthy makes a Stage healthy.
Now, with all of that being said...
It's sometimes a bit complicated to make this assessment and there have been plenty of bugs related to it that we have had to fix and it wouldn't shock me if there are more. So if, with the above explanation in mind, things that still don't seem right to you, more detail might lead us to something actionable, however, Stage and App health merely not matching isn't necessarily a sign of something amiss.


Docs: sort catalog

@sagarbehere FYI, it was implemented by 134da82. Now the catalog is sorted by weight(in descending order), and then sort the rest of pages without specifying weight by title in alphabetical order.

@razonyang Yes, this is working great! Thank you :-)

@razonyang Now that I have got some experience with the catalog sidebar, I think a minor adjustment is necessary: Let's sort the catalog sidebar by weight in ascending order (instead of the existing descending order), and then sort the rest of pages without specifying weight by title in alphabetical order. This requires changing only one word in layouts/partials/docs/catalog.html. In the line
{{- range ($section.Pages.GroupBy "Weight" "desc") -}}

change desc to asc. Everything else stays the same.
The reason for this is that once you have a large number of pages and you want to order them in a certain way, it is easy to think of the first page you want in the order.. and assign it a low weight like 10. Then think of the next page you want in the sequence.. and give it a weight like 20.. the next page gets a weight 30.. and so on. And then the pages will appear in that order (if sorted by weight in ascending order). However, in the existing descending order, one needs to think in the opposite way: Think of the first page you want.. then give it some really high weight, like 100. Then for the next page, give a weight of 90.. and so on. But if you then realize that you have more than 10 pages.. oops.. you then need to go back and change the weights of all the previous pages.. that is annoying and not very user-friendly :)

@sagarbehere I've thought about it before, but the weight pages will always behide the non-weight pages. That is because there is a default value in golang struct, that is, actually non-weight pages have a default value 0.

@razonyang Oh! Okay, in that case the existing settings make more sense. No changes needed. Thank you for clarifying.


chore: bdd-gh-1584269646 to 0.0.1

chore: Promote bdd-gh-1584269646 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment