Pylance crashing on Jupyter Notebook Cell Deletion

Environment data

Language Server version: v2023.8.10
OS and version: Windows 10 22H2 OS Build 22621.1992
Python version (& distribution if applicable, e.g. Anaconda): 3.11.4

Repro Steps

Add 2 new empty cells in Jupyter Notebook or Deleting any other cells in between cells. Deleting one would not instantly crash, but deleting another one will
Proceed to delete the first created cell, then delete the second one (top to bottom). Deleting from bottom to top in order does not crash the server
Crashed

Expected behavior

Not crashing. Issue has been posted before in another report #4077, but this crash in reopen, not crashing the linting server

Logs
Error: Debug Failure. False expression: Chained file path undefined doesn't match cellFilePaths:
    at _0x598038 (c:\Users\leejieun\.vscode\extensions\ms-python.vscode-pylance-2023.8.11\dist\server.bundle.js:1:897913)
    at c:\Users\leejieun\.vscode\extensions\ms-python.vscode-pylance-2023.8.11\dist\server.bundle.js:1:905158
    at _0x547bdc.<computed> (c:\Users\leejieun\.vscode\extensions\ms-python.vscode-pylance-2023.8.11\dist\server.bundle.js:1:905190)
    at _0x3822ba._onDidChangeNotebookDocumentAsync (c:\Users\leejieun\.vscode\extensions\ms-python.vscode-pylance-2023.8.11\dist\server.bundle.js:1:884105)

Downgrading to v2023.7.40 seems to have solved the issue. Bug maybe introduced in new version?

Can somebody post a gif of it happening? I cannot seem to reproduce the problem:

Here's whats happening in my computer.

Did you reorder any cells or put anything in the notebook before adding the 3? extra cells at the bottom? No matter how many cells or where I put them, I can't get it to crash. But maybe reordering first is necessary.

Freshly opened vscode using reload window, then added the cells. Just happen to me on this particular version. I can try using venv to follow your gif there. Might followup in 12 hours

I think i tried waiting a few seconds before deleting another cell. Still broke the server though. But deleting from bottom to top in order seems fine.

Did you reorder any cells or put anything in the notebook before adding the 3? extra cells at the bottom? No matter how many cells or where I put them, I can't get it to crash. But maybe reordering first is necessary.

I'm getting a similar issue when deleting cells in Jupyter notebook. See my post here for a video:
https://github.com/microsoft/vscode/issues/189645#issuecomment-1665838880
I get the same error "Error: Debug Failure. False expression: Chained file path undefined doesn't match cellFilePaths"

Note: Downgrading to v2023.7.40 doesn't solve the issue for me.
Instead I had to downgrade Pylance to version 2023.6.10 and downgrade Jupyter to version 2023.6.1101941928

We really need a way to repro the problem. Nobody in house can seem to reproduce the issue. Does it happen no matter the notebook?

Yeah I still can't repro. Doesn't matter where I create a cell.

Yeah I still can't repro. Doesn't matter where I create a cell.

Can you try this?
I used D+D to delete the middle cell and Z to undo the delete
https://github.com/microsoft/pylance-release/assets/94503686/b27f3d95-2cd6-4707-af86-d9688e1f7fd6

Nope that works fine. Deleting the cell, moving it around, doesn't matter.
The code that's failing is detecting that we understand all of the cells in the notebook (they get turned into files that reference each other). When the error occurs, one of the cells is set to undefined for some reason.

Can you try an experimental setting?
 "python.analysis.enableSyncServer": true

This changes how we handle LSP messages. That setting forces us to handle one message at a time. The bug here might be we're getting a delete for a notebook cell while we get an edit for a cell and the delete might be deleting a cell we were editing.
Sync server mode should make those two messages happen synchronously.

Oh, should have said that new mode requires restarting VS code.

Not helping on my side. The crash message looks slightly different though :
2023-08-08 15:17:38.324 [info] [Error - 15:17:38] Notification handler 'notebookDocument/didChange' failed with message: Debug Failure. False expression: Chained file path undefined doesn't match cellFilePaths c:\xxx\zzz.ipynb:pylance-notebook-cell:X53sZmlsZQ==.py

That did make some progress. Autocomplete keeps working now, but objects are underlined as if they don't exist (reportUndefinedVariable). And then I'm getting the same log message as tierry-bm.
2023-08-08 15:57:35.015 [info] [Error - 3:57:35 PM] Notification handler 'notebookDocument/didChange' failed with message: Debug Failure. False expression: Chained file path undefined doesn't match cellFilePaths c:\zzz\debug.ipynb:pylance-notebook-cell:W0sZmlsZQ==.py

That probably means the 'crash' for the async server is not crashing the sync server. But the data is still messed up. Meaning it still repros.

Just to double check, everyone hitting this is using either the latest VS code insiders or VS code stable?
I tried with stable: 1.81
I tried with insiders: 1.82
Thought maybe VS code changed notebook sync messages.

I’m using stable, but tomorrow I can also try with insiders if that would be useful.

I’m using stable, but tomorrow I can also try with insiders if that would be useful.

No, I don't think that matters. I really doubt VS code changed these messages at all. There's some race condition we have in Pylance.

Using stable 1.81, ms-python.vscode-pylance-2023.8.20 on linux machine
notbooks keep crashing with mentioned error message. remote an local. Can reproduce by deleting two cells consecutively.

Related on Stack Overflow: Pylance in VS Code crashes when adding or deleting cells in a Jupyter notebook

I'm also with the same problem. I got it after deleting random cells.
Windows 11
VSCode 1.81.1 (stable)
Pylance: v2023.8.21 (pre-release version) (I also had the same problem with previous versions)

Same problem occuring with

macOS Ventura 13.0
VSCode 1.81.0 (universal)
Python ext: v2023.14.0
Pylance ext: v2023.8.20

after pylance has fully loaded and e.g. deleting two consecutive code cells. Returns with message "Error: Debug Failure. False expression: Chained file path undefined doesn't match cellFilePaths" in an instant.
Also tried the experimental setting '"python.analysis.enableSyncServer": true' mentioned above, which resulted in the message "Notification handler 'notebookDocument/didChange' failed with message: Debug Failure. False expression: Chained file path undefined doesn't match cellFilePaths". However, this time the message did not appear instantaneously, but with a few seconds delay.
Reverting pylance to v2023.7.40 worked for me!

I tried reverting pylance to v2023.7.40 and so far it's working.

Since the august update,  Intellisense breaks for me too, not sure after which particular action, but i'm sure it happens without the need to delete cells (I've experience this for 3 days). Reverting pylance to v2023.7.40 works for me.

Reverting to v2023.7.40 seems to make crashes / intellisense dropout less frequent, but it still happens. Like most of the others here, I'm having a hard time figuring out exactly what triggers the crash / dropout.

Actually even just creating and deleting a cell without doing any other action is enough to break pylance for me in some notebook files. I've had these issues for the longest time, although recently it happens more frequently, and I feel like they happen more often when I have multiple python projects open, but it might just be a coincidence.

I have confirmed that at least some of these scenarios are fixed by the fix for #4733 which will be included in this week's Pylance prerelease build.

A lot of people chimed in on this issue with different ways to hit this assert. I'm hopeful that they are all fixed by the fix for #4733 which was just released in our latest prerelease build, 2023.8.41
Could you please all upgrade to 2023.8.41 and see if your issues are resolved?

Still isn't working for me; receiving the same "Error: Debug Failure. False expression: Chained file path undefined doesn't match cellFilePaths" from Pylance output.
This occurs when deleting a cell and then undoing the delete.

Can confirm, still doesn't work for me after upgrading to 2023.8.41. Same error as before (same error as @Xavi422.

Same here, doesn't seem to fix it

Updating Pylance to 2023.8.41 actually seems to have fixed the issue for me. I've tried all the things that previously made it crash, and so far I haven't been able to get the problem to repeat.
Thanks to everyone working on this! I'm very new to coding an I need the colors :).

Using 2023.8.41 I get the same error as @Xavi422.

Still the same problem with 2023.8.41

Found another repro for this assert, which I'm now investigating.
Setup

Create empty directory
Open dir in VS Code
Add new empty file test.py
Create: New Jupyter Notebook
Add cells. The content is probably irrelevant, aside from having 3+ cells, but here's what I used:
a. thing = "thing"
b. thing
c. print(thing)
d.
e.
Save notebook in the directory as test.ipynb
Close both files
Close VS Code

Repro

Open dir in VS Code again.
Open test.py
Wait for Pylance to initialize. This may not be necessary.
Open test.ipynb
Delete second-to-last cell
Delete last cell

2023-08-25 17:05:08.658 [info] Error: Debug Failure. False expression: Chained file path undefined doesn't match cellFilePaths c:\temp\temp\4685repro\test.ipynb:pylance-notebook-cell:W1sZmlsZQ==.py
    at _0x35bbe7 (c:\Users\erikd\.vscode-insiders\extensions\ms-python.vscode-pylance-2023.8.41\dist\server.bundle.js:1:1025282)
    at c:\Users\erikd\.vscode-insiders\extensions\ms-python.vscode-pylance-2023.8.41\dist\server.bundle.js:1:1032550
    at _0x114e49.<computed> (c:\Users\erikd\.vscode-insiders\extensions\ms-python.vscode-pylance-2023.8.41\dist\server.bundle.js:1:1032582)
    at _0x4600bc._onDidChangeNotebookDocumentAsync (c:\Users\erikd\.vscode-insiders\extensions\ms-python.vscode-pylance-2023.8.41\dist\server.bundle.js:1:1010710)

The scenario above will be fixed in our next prerelease build.

I'm still facing this issue even with prerelease v2023.8.41 :

Output logs :
2023-08-28 21:39:45.397 [info] Error: Debug Failure. False expression: Chained file path undefined doesn't match cellFilePaths c:\Users\046724\PQinPrompt\test_prompt.ipynb:pylance-notebook-cell:X13sZmlsZQ==.py     at _0x35bbe7 (c:\Users\046724\.vscode\extensions\ms-python.vscode-pylance-2023.8.41\dist\server.bundle.js:1:1025282)     at c:\Users\046724\.vscode\extensions\ms-python.vscode-pylance-2023.8.41\dist\server.bundle.js:1:1032550     at _0x114e49.<computed> (c:\Users\046724\.vscode\extensions\ms-python.vscode-pylance-2023.8.41\dist\server.bundle.js:1:1032582)     at _0x4600bc._onDidChangeNotebookDocumentAsync (c:\Users\046724\.vscode\extensions\ms-python.vscode-pylance-2023.8.41\dist\server.bundle.js:1:1010710)

I'm still facing this issue even with prerelease v2023.8.41

Right. We fixed a related bug (#4733) in 2023.8.41. The scenario in my comment above seems closer to what users are reporting in this issue and will be fixed in our next prerelease build. Likely on Wednesday.

Just posting to confirm that I'm having the exact same issue.

I can confirm that I have the same issue. I downgraded to 2023.7.30 and 2023.7.40, and also switched to pre-release version (2023.8.41) and still the same issue.

The whole python linting/autocomplete experience is broken so regularly that it has become embarrassing for me to recommend VS Code to new users. It is always "it should be working today, lets see"

So since we are Wednesday does the pre release build that will be released today fix this issue?

Problem seems was fixed after installing Pyright v1.1.325, which claims that have fixed it.
https://github.com/microsoft/pyright/pull/5854

There was an additional fix that isn't in Pyright. it's only in pylance at the moment.

When we ship the next Pylance prerelease, the bug should be fixed. That would be 2023.8.51

This issue has been fixed in prerelease version 2023.8.51, which we've just released. You can find the changelog here: CHANGELOG.md

I am on v2023.8.51 of pylance and this does not seem to be fixed. I still get white text pretty often on imports. Need to refresh window.

I am on v2023.8.51 of pylance and this does not seem to be fixed. I still get white text pretty often on imports. Need to refresh window.

@jzazo, after that happens, if you add/delete/reorder a cell, does Pylance crash with an error like the one below? If not, it's a different issue.
2023-08-25 20:20:22.473 [info] Error: Debug Failure. False expression: Chained file path undefined doesn't match cellFilePaths c:\temp\temp\4685repro_2\test.ipynb:pylance-notebook-cell:W0sZmlsZQ==.py
    at _0x35bbe7 (c:\Users\erikd\.vscode-insiders\extensions\ms-python.vscode-pylance-2023.8.41\dist\server.bundle.js:1:1025282)
    at c:\Users\erikd\.vscode-insiders\extensions\ms-python.vscode-pylance-2023.8.41\dist\server.bundle.js:1:1032550
    at _0x114e49.<computed> (c:\Users\erikd\.vscode-insiders\extensions\ms-python.vscode-pylance-2023.8.41\dist\server.bundle.js:1:1032582)
    at _0x4600bc._onDidChangeNotebookDocumentAsync (c:\Users\erikd\.vscode-insiders\extensions\ms-python.vscode-pylance-2023.8.41\dist\server.bundle.js:1:1010710)

Can confirm that upgrading to Pylance 2023.8.51 worked for me. For now. Thank you all for working on this.

I am not using jupyter or interpreted python, I am on a normal python module, and pylance stops working. Yeah, it may happen when I reorder code, is that possible?

I am not using jupyter or interpreted python, I am on a normal python module, and pylance stops working. Yeah, it may happen when I reorder code, is that possible?

@jzazo, the identifying behavior of this issue is the crash. The fact that semantic highlighting stops working just before the crash is a symptom of the underlying problem, but there are many reasons that semantic highlighting could stop working. It's impossible for this crash to occur without opening a notebook. The code where the "Chained file path x doesn't match cellFilePaths" check is performed is only executed when VS Code tells Pylance that a notebook has been opened or modified.
So what you're seeing is a different issue. Can you please open a new issue?
The only existing issue I found that looked similar is https://github.com/microsoft/pylance-release/issues/4513, but I don't think there's enough detail there yet for us to know if it's the same as your issue. So open a new one and we can always resolve it as a duplicate after investigation if appropriate.

Thanks, I will keep monitoring and report back if I observe it crashes.

Thanks, I will keep monitoring and report back if I observe it crashes.

@jzazo, sorry if I wasn't clear. When the semantic highlighting (colored text) changes to white, which of the following options is true for you? Note that having a notebook "open" does not necessarily mean that it is the active tab that you are typing in. Simply having it open as another tab may be sufficient to cause this issue.
No notebooks are open
If you don't have any notebooks open when you see the semantic highlighting (colored text) change to white, then what you are seeing is unrelated to this issue. File a new issue please.
1+ notebook is open and adding/deleting/reordering cell does not cause this crash
If you do have a notebook open (as an open tab, but not necessarily the active tab) when you see the semantic highlighting (colored text) change to white (in any file), then when that color change occurs, please switch to the open notebook and try adding, deleting, or reordering a cell there. If that doesn't cause the crash I mentioned above, then what you are seeing is unrelated to this issue. File a new issue please.
1+ notebook is open and adding/deleting/reordering cell causes this crash
If you see the coloration disappear with a notebook open, and adding/deleting/reordering a cell causes the crash I mentioned above, and you are using 2023.8.51, then what you're seeing is related to this issue and we'll need more details on your project and what actions you are taking before the problem occurs.

Thanks @debonte. Yeah, I don't have any notebooks open, so it is an unrelated issue. I will keep monitoring, it doesn't happen as frequently as before.

I have upgraded today to the 2023.8.51 pre-release version. I have worked all day on a large notebook (dozens of MB file size, due to lots of graphics). Remote session into a Linux machine via the SSH extension.
Syntax highlighting and autocompletion worked flawlessly all day (if a bit slow due to the huge notebook size). No crashes (that I know of).
With recent previous versions, I used to experience a loss of syntax highlighting and autocompletion after a while, that required closing/reopening the notebook. I have never seen any crashes with previous versions (may have occurred, I just never saw them).
I believe the 2023.8.51 pre-release fixes the problems I had.
Thanks @debonte

I am on v2023.11.11 and this issue is still persisting
2023-11-06 10:53:41.635 [info] Error: Debug Failure. Cell path not found for cell vscode-notebook-cell:/c%3A/Users/ilirk/projects/adhoc/movement.ipynb#W6sZmlsZQ%3D%3D
    at _0x5e8922.getNotebookCellPath (c:\Users\ilirk\.vscode\extensions\ms-python.vscode-pylance-2023.11.11\dist\server.bundle.js:1:261668)
    at _0x8f195a.decodeTextDocumentUri (c:\Users\ilirk\.vscode\extensions\ms-python.vscode-pylance-2023.11.11\dist\server.bundle.js:1:230980)
    at _0x45a7e7.onDidCloseTextDocument (c:\Users\ilirk\.vscode\extensions\ms-python.vscode-pylance-2023.11.11\dist\server.bundle.js:1:901599)
    at c:\Users\ilirk\.vscode\extensions\ms-python.vscode-pylance-2023.11.11\dist\pyright.bundle.js:1:1144202
    at c:\Users\ilirk\.vscode\extensions\ms-python.vscode-pylance-2023.11.11\dist\vendor.bundle.js:2:1234062
    at oe (c:\Users\ilirk\.vscode\extensions\ms-python.vscode-pylance-2023.11.11\dist\vendor.bundle.js:2:1234284)
    at c:\Users\ilirk\.vscode\extensions\ms-python.vscode-pylance-2023.11.11\dist\vendor.bundle.js:2:1230224
    at Immediate.<anonymous> (c:\Users\ilirk\.vscode\extensions\ms-python.vscode-pylance-2023.11.11\dist\vendor.bundle.js:2:1230244)
    at processImmediate (node:internal/timers:476:21)

2023-11-06 10:53:41.819 [info] [Error - 10:53:41 AM] Server process exited with code 1.
2023-11-06 10:53:41.826 [info] [Info  - 10:53:41 AM] Connection to server got closed. Server will restart.
2023-11-06 10:53:41.827 [info] true
2023-11-06 10:53:42.959 [info] [Info  - 10:53:42 AM] (11624) Pylance language server 2023.11.11 (pyright 64c9c3ff) starting
2023-11-06 10:53:42.959 [info] [Info  - 10:53:42 AM] (11624) Server root directory: C:\Users\ilirk\.vscode\extensions\ms-python.vscode-pylance-2023.11.11\dist
2023-11-06 10:53:42.960 [info] [Error - 10:53:42 AM] Server initialization failed.
2023-11-06 10:53:42.960 [info]   Message: Request initialize failed with message: You may install and use any number of copies of the software only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services (collectively, the “Visual Studio Products and Services”) to develop and test your applications. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. You may not: work around any technical limitations in the software that only allow you to use it in certain ways; reverse engineer, decompile or disassemble the software, or otherwise attempt to derive the source code for the software, except and to the extent required by third party licensing terms governing use of certain open source components that may be included in the software; remove, minimize, block, or modify any notices of Microsoft or its suppliers in the software; use the software in any way that is against the law or to create or propagate malware; or share, publish, distribute, or lease the software (except for any distributable code, subject to the terms above), provide the software as a stand-alone offering for others to use, or transfer the software or this agreement to any third party.

----- [29023443aa0953887e4bf9867965fbbfac2b37d3fe3788884a690a80741a1b19]

The same problem in my jupyter notebook. I used plotly lib to visualization, and after i deleted cell with plot pylance server was crashed
my version: 1.85.0-insider (user setup)
Commit: 9aacac648821b5c9c1a7192ac9d44c50af6fe241
Date: 2023-11-06T05:34:22.485Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045

The deleting of the cell is actually tracked in a separate issue. This one: https://github.com/microsoft/pylance-release/issues/5071. The fix for that should be in the next prerelease version when we ship it. Otherwise I'd recommend switching to stable.

The same problem in my jupyter notebook. I used plotly lib to visualization, and after i deleted cell with plot pylance server was crashed
my version: 1.85.0-insider (user setup) Commit: 9aacac648821b5c9c1a7192ac9d44c50af6fe241 Date: 2023-11-06T05:34:22.485Z Electron: 25.9.2 ElectronBuildId: 24603566 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: <IP_ADDRESS>-electron.0 OS: Windows_NT x64 10.0.19045

Same problem here, tried several past versions with the server crashing on open, none seems to work.

This issue happens again for my Pylance in version 2023.8.50

This issue happens again for my Pylance in version 2023.8.50

@LicoriceLin, If that's your version, you should upgrade. This bug has been fixed since 2023.11.12

This issue happens again for my Pylance in version 2023.8.50

@LicoriceLin, If that's your version, you should upgrade. This bug has been fixed since 2023.11.12

Oh thanks!
I just forgot to turn on auto-update in my new dev-environment.

This issue happens again for my Pylance in version 2023.8.50

@LicoriceLin, If that's your version, you should upgrade. This bug has been fixed since 2023.11.12

Oh I think it's a new issue as update doesn't fix it. And my error log goes like " Received change text document command for closed file":

This issue happens again for my Pylance in version 2023.8.50

@LicoriceLin, If that's your version, you should upgrade. This bug has been fixed since 2023.11.12

Oh I think it's a new issue as update doesn't fix it. And my error log goes like " Received change text document command for closed file":

In my situation any change to jupyter codes, even if it's in the existent blocks, will make pylance crash

That sounds like this problem then:
https://github.com/microsoft/pylance-release/issues/5543
Which looks to be an issue with VS code:
https://github.com/microsoft/vscode/issues/206487
If you downgrade VS code to 1.86.2, the problem should go away.

having this problem right now on

@2blo please open a new issue with the contents of the output log. It should give us a callstack of where the problem occurred.


PackagesNotFoundError: The following packages are not available from current channels:    - rad_haplotyper

Hi, I am trying to phase some ddrad data. Thank you for any help.  I am getting the below error when trying to create the rad_haplotyper conda environment:
(base) Jessicas-MacBook-Pro-2:filtering jessicaoswald$ conda create -n rad_haplotyper_env rad_haplotyper
Collecting package metadata (current_repodata.json): done
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed
PackagesNotFoundError: The following packages are not available from current channels:

rad_haplotyper

Current channels:

https://conda.anaconda.org/bioconda/osx-64
https://conda.anaconda.org/bioconda/noarch
https://conda.anaconda.org/conda-forge/osx-64
https://conda.anaconda.org/conda-forge/noarch
https://repo.anaconda.com/pkgs/main/osx-64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/r/osx-64
https://repo.anaconda.com/pkgs/r/noarch
https://conda.anaconda.org/r/osx-64
https://conda.anaconda.org/r/noarch

To search for alternate channels that may provide the conda package you're
looking for, navigate to
https://anaconda.org

and use the search bar at the top of the page.

There wasn't an OS X version of this package, but there is now.  Please try
again.
--
Jon Puritz, PhD
Assistant Professor
Department of Biological Sciences
University of Rhode Island
120 Flagg Road,  Kingston, RI 02881
Webpage: MarineEvoEco.com
Cell:<PHONE_NUMBER>
Work:<PHONE_NUMBER>
"The most valuable of all talents is that of never using two words when one
will do. ”  -Thomas Jefferson
Q: Why is this email five sentences or less?
A: http://five.sentenc.es
I only check and respond to email at 10am and 4:00pm each day.
On February 7, 2020 at 2:09:25 PM, Jessica Oswald<EMAIL_ADDRESS>wrote:
Hi, I am trying to phase some ddrad data. Thank you for any help. I am
getting the below error when trying to create the rad_haplotyper conda
environment:
(base) Jessicas-MacBook-Pro-2:filtering jessicaoswald$ conda create -n
rad_haplotyper_env rad_haplotyper
Collecting package metadata (current_repodata.json): done
Solving environment: failed with repodata from current_repodata.json, will
retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed
PackagesNotFoundError: The following packages are not available from
current channels:

rad_haplotyper

Current channels:

https://conda.anaconda.org/bioconda/osx-64
https://conda.anaconda.org/bioconda/noarch
https://conda.anaconda.org/conda-forge/osx-64
https://conda.anaconda.org/conda-forge/noarch
https://repo.anaconda.com/pkgs/main/osx-64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/r/osx-64
https://repo.anaconda.com/pkgs/r/noarch
https://conda.anaconda.org/r/osx-64
https://conda.anaconda.org/r/noarch

To search for alternate channels that may provide the conda package you're
looking for, navigate to
https://anaconda.org
and use the search bar at the top of the page.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/chollenbeck/rad_haplotyper/issues/32?email_source=notifications&email_token=ABE5CR2K5XMSA5P2SCFL3GTRBWWWJA5CNFSM4KRTN6D2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IL4VMMA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABE5CR3GRHSHUX3BCLYAHFDRBWWWJANCNFSM4KRTN6DQ
.

Gave it a go -
(base) Jessicas-MacBook-Pro-2:filtering jessicaoswald$ conda create -n rad_haplotyper_env rad_haplotyper
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
[y/N]: y

That seems like a different kind of conda error.
--
Jon Puritz, PhD
Assistant Professor
Department of Biological Sciences
University of Rhode Island
120 Flagg Road,  Kingston, RI 02881
Webpage: MarineEvoEco.com
Cell:<PHONE_NUMBER>
Work:<PHONE_NUMBER>
"The most valuable of all talents is that of never using two words when one
will do. ”  -Thomas Jefferson
Q: Why is this email five sentences or less?
A: http://five.sentenc.es
I only check and respond to email at 10am and 4:00pm each day.
On February 7, 2020 at 5:05:20 PM, Jessica Oswald<EMAIL_ADDRESS>wrote:
Gave it a go -
(base) Jessicas-MacBook-Pro-2:filtering jessicaoswald$ conda create -n
rad_haplotyper_env rad_haplotyper
shell-init: error retrieving current directory: getcwd: cannot access
parent directories: No such file or directory
[y/N]: y
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/chollenbeck/rad_haplotyper/issues/32?email_source=notifications&email_token=ABE5CRY5HASIEGFKBACKNPLRBXLKBA5CNFSM4KRTN6D2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELEZJRQ#issuecomment-583636166,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABE5CRZSTN52FSFNZZLA6PTRBXLKBANCNFSM4KRTN6DQ
.

Hi Jon, I tried again this morning and it works. Thank you!


<IP_ADDRESS>.2	Allow volunteer to accept/reject task assignment

Requires completed implementation of #40
As a volunteer I can:

[ ] Accept a task assignment
[ ] Reject a task assignment

By way of documentation, the task sign-up status can be set to the following values:

Assigned (assigned by an admin to a volunteer)
Accepted (accepted by a volunteer - assumed to now be in-progress)
Rejected (rejected by a volunteer)
Completed (completed by a volunteer)
CanNotComplete (marked by a volunteer as a task that can't be completed)

Taking this over from @rockfordlhotka. Please switch assignments @BillWagner / @tonysurma


Create methods with only mandatory fields for international standing order consents

Description
Create methods in securebanking-openbanking-uk-obie-datamodel to initialize objects only with the mandatory fields according to the International standing order Consents - v3.1.8 Documentation

Hey team! Please add your planning poker estimate with Zenhub @frlaura-jianu @mariantiris


Bluetooth: controller: Convert benign BT_WARN() messages to BT_DBG()

BT_WARN() should only be used for log messages that may indicate a
problem. However, the controller HCI code was using it for messages
that were of a pure debugging/informational nature. Convert these to
BT_DBG() instead - this should hopefully also help avoid unnecessary
user questions of seemingly alarming log messages.
Signed-off-by: Johan Hedberg<EMAIL_ADDRESS>

Codecov Report

Merging #14679 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master   #14679   +/-   ##
=======================================
  Coverage   51.97%   51.97%
=======================================
  Files         309      309
  Lines       45584    45584
  Branches    10555    10555
=======================================
  Hits        23694    23694
  Misses      17082    17082
  Partials     4808     4808

Impacted Files
Coverage Δ

subsys/bluetooth/controller/hci/hci.c
52.66% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7ba52ea...12390e4. Read the comment docs.


Infinite Loop in InstanceDefaults when using Models.service.get(id)

Steps to reproduce
Hi,
I am using the sample code from the docs  -
instanceDefaults (data, { store, Model, Models }) {
        return {
          description: '',
          isComplete: false,
          userId: null,
          get user () {
            if (this.userId) {
              const user = Models.User.getFromStore(this.userId)

              // Fetch the User record if we don't already have it
              if (!user) {
                Models.User.get(this.userId)
              }

              return user
            } else {
              return null
            }
          }
        }

When the userId doesn't exist on the server (and sometimes even when it does - still trying to figure out where the infinite loop happens in that case), it goes into an infinite loop.
I also checked if this was related to https://github.com/feathers-plus/feathers-vuex/issues/207 but something else seems to be happening in this case.
I am quite new to feathers-vuex and trying to figure out if it's a bug or if I did something wrong.
System configuration
Feathers-vuex version: v1.7.0
NodeJS version: v11.6.0
Thanks!

@kshitizshankar thanks for filing this.  I actually just ran into this exact same issue, yesterday.  I believe that the issue is caused by the way that Vue tracks and re-runs dependencies.  I wasn't able to come up with a solution other than to move the API request (Models.User.get()) outside of the getter.

This issue definitely deserves more research to see if there's a decent workaround.

Thanks for the reply! I wasn't sure if there were any workarounds for this or not, so ended up removing the get requests from instance defaults as well.
It might be a good idea to mention it in docs till we find a solution, given it will crash the app/browser when it happens.

I'm closing this issue since I've added it to the bottom of the new documentation, to eventually be merged into real docs.


check if model file exists before parsing

Instead of showing "parsing error" it now show "model file does not exist" if the model file is missing or path is incorrect.
@rnbguy

Thanks for the PR @udit-gulati ! I added some comments :slightly_smiling_face:

Thanks @udit-gulati :rocket:


Move the Kafka Source to the knative-eventing namespace

Signed-off-by: Matthias Wessendorf<EMAIL_ADDRESS>Fixes #

Proposed Changes

move source to knative-eventing
add old/deprecated controller replica
-remove config-xyz duplicates
change the leader election cfg name for the source

Release Note

The KafkaSource will be installed in the knative-eventing namespace, and the old controller in knative-sources is scalled to 0

Docs

@antoineco @pierDipi @lionelvillard I updated this PR
For now we will have config-leader-election-kafka CMs, however, I feel this is wrong, as expressed here:
https://github.com/knative-sandbox/eventing-kafka/pull/231
Also related:
https://github.com/knative/eventing/issues/4593

So what's the plan, merge this, hold #231, then un-hold #231 after this is merged?

@antoineco

I  think we should avoid renaming things in this PR if they are unrelated to the original intention which is "Move the Kafka Source to the knative-eventing namespace"

Sure, I updated earlier today, see: https://github.com/knative-sandbox/eventing-kafka/pull/224/files

So what's the plan, merge this, hold #231, then un-hold #231 after this is merged?

I'd think so - the #231 is already on hold ;-)


InfoNCE loss

Summary
This PR adds InfoNCE and NTXent losses for contrastive learning.

Codecov Report
Attention: 56 lines in your changes are missing coverage. Please review.

Comparison is base (8ed720e) 83.88% compared to head (49557d0) 84.26%.
Report is 26 commits behind head on main.

Files
Patch %
Lines

audyn/criterion/contrastive.py
83.19%
40 Missing :warning:

audyn/modules/activation.py
93.62%
16 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #55      +/-   ##
==========================================
+ Coverage   83.88%   84.26%   +0.38%
==========================================
  Files          81       82       +1
  Lines        8183     8741     +558
==========================================
+ Hits         6864     7366     +502
- Misses       1319     1375      +56

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix encoding of empty lua table.

A fix for the following issue.
https://github.com/heroiclabs/nakama-defold/issues/17

Thanks to @RonKip ,
It works , i was able to create a match using
local message = {
    match_create = {}
}
local result = nakama.socket.send(socket,message)

the only note is that there is a little issue in the code indentation , i guess @britzl who take care of checks .

Thanks to @RonKip ,
It works , i was able to create a match using
local message = {
    match_create = {}
}
local result = nakama.socket.send(socket,message)

the only note is that there is a little issue in the code indentation , i guess @britzl who take care of checks .

@RonKip
What if actually we meant to send an empty array for example , this will force all [ ] to be { } without exceptions .
e.g :
local match_data = {
    match_data_send = {
        match_id = match.match.match_id,
        op_code = 1337,
        data = {
            players = {} -- i want to receive it as an empty array
        }
    }
}

if i am not mistaken, in this case the players will be converted to Json object instead of an empty array of players

@RonKip
What if actually we meant to send an empty array for example , this will force all [ ] to be { } without exceptions .
e.g :
local match_data = {
    match_data_send = {
        match_id = match.match.match_id,
        op_code = 1337,
        data = {
            players = {} -- i want to receive it as an empty array
        }
    }
}

if i am not mistaken, in this case the players will be converted to Json object instead of an empty array of players

@RonKip Thanks for the pull request. I think the best approach is to special case the encoded input to the empty Lua table for the specific function call rather than convert all usages.

@RonKip Thanks for the pull request. I think the best approach is to special case the encoded input to the empty Lua table for the specific function call rather than convert all usages.

OK. That will be a better approach.

OK. That will be a better approach.


Make the aside position sticky

Friendly suggestion to make the docs easier to follow along with (Moves the aside while scrolling down the page).

Thanks @Hammadus! It's much nicer now :raised_hands:


Remove extra layer of abstraction

"DeviceBuffer" can go!
"InterpretedBuffer" is the same as "RawBuffer"

Also rename lazydata -> data and LazyBuffer -> Buffer
The days of non lazy are never coming back


fix: delete pods that are unscheduled to force recreation

Closes #1946

/test limit=local

/test limit=local

@Ornias1993 Sadly the proposed fix in this PR isn't good enough given that creates a programmatic fail in the E2E test suite.
I will try to investigate further when I have time

@Ornias1993 Sadly the proposed fix in this PR isn't good enough given that creates a programmatic fail in the E2E test suite. I will try to investigate further when I have time

Edited to make clear it's just a global design review.

Full E2E run running in EDB fork https://github.com/EnterpriseDB/cloudnative-pg/actions/runs/9842619062

Full E2E tests running on EDB fork https://github.com/EnterpriseDB/cloudnative-pg/actions/runs/9857999815

/test

/test tl=4 d=main


We have found an issue with the sample code on the official website. The specific problem lies in "Example 4: Forms and callbacks" at “ https://docs.streamlit.io/develop/concepts/architecture/session-state ”.

Checklist

[X] I have searched the existing issues for similar issues.
[X] I added a very descriptive title to this issue.
[X] I have provided sufficient information below to help reproduce this issue.

Summary

We have found an issue with the sample code on the official website. The specific problem lies in "Example 4: Forms and callbacks" at “ https://docs.streamlit.io/develop/concepts/architecture/session-state ”.
The below line should be added, otherwise the error message "AttributeError: stsession-state has no attribute" last_updated "will be reported.
if 'last_updated' not in st.session_state:  st.session_state.last_updated = datetime.time(0, 0)
`

Reproducible Code Example
import streamlit as st
import datetime

st.title('Counter Example')
if 'count' not in st.session_state:
    st.session_state.count = 0
    st.session_state.last_updated = datetime.time(0,0)

def update_counter():
    st.session_state.count += st.session_state.increment_value
    st.session_state.last_updated = st.session_state.update_time

with st.form(key='my_form'):
    st.time_input(label='Enter the time', value=datetime.datetime.now().time(), key='update_time')
    st.number_input('Enter a value', value=0, step=1, key='increment_value')
    submit = st.form_submit_button(label='Update', on_click=update_counter)

st.write('Current Count = ', st.session_state.count)
st.write('Last Updated = ', st.session_state.last_updated)

Steps To Reproduce

run the code.
then you will see the AttributeError

Expected Behavior
Update sample code:
if 'last_updated' not in st.session_state:  st.session_state.last_updated = datetime.time(0, 0)
`
Current Behavior
AttributeError: st.session_state has no attribute "last_updated".
Is this a regression?

[ ] Yes, this used to work in a previous version.

Debug info

Streamlit version:1.30.0
Python version:3.11.5
Operating System:win11
Browser:edge

Additional Information

I do not get an AttributeError when running this code. In order to trigger the error, you'd need to initialize "count" in Session State with some other code, then paste this code into an already running Streamlit server. Modifying code while running a Streamlit app can certainly have unintended consequences, but this works as-is if run cleanly. 😄


Problem with the Travis CI build script?

Submitted pull request #285 Add Tucson Neighborhoods and the Travis CI build failed. Error messages showed outdated Node version and that jshint failed to run. I can't see anything wrong with the GeoJSON and JSON files in the pull request, so I'm guessing there's an issue with the Travis CI setup.
If there are issues with the JSON, I would be happy to fix them, but they worked great on the fork I tested with - and I did make sure the fork was up to date with the master before testing and submitting the pull request.

The build script doesn’t work and I don’t think it ever did. If it works locally, it’s probably good. I’ll try to take a look soon…

Well, that's good to know. I was worried there was something wrong with the pull request I submitted!


HTML report pass/fail filters do not work correctly while testsuite runs

The HTML report can filter by failures. Clicking on the Mocha stats in the top-right to inspect the failures, while the test suite is still running, all suites that have all passing tests are still added to the page. E.g. if you have a test that fails, clicking on failures shows that test. However, every consecutive suite that passes just fine is appended (just the name) to the report. Clicking on passes and then back on failures clears these names and again only shows the failures.
Therefore, I would like to have the failures page filter out fully passing test suites while the full test suite is running. I think that after this line the code from here must be run to then hide the suite name?

Thanks for spotting this; I don't know I'd have ever thought to click the filters while the report is still running! I assume a similar problem occurs for failing suites when the passing filter is turned on and should only show passing tests/suites?
My understanding is that the tests are hidden by CSS based on a class applied to the root of the report, while the suites are hidden by JS actions upon them only when the filter button is clicked. I presume that's because whether a suite should be hidden depends on whether there are passing/failing tests in its descendants and CSS can't do anything based on descendants. But the fact that this is done by mutating individual suites each time the filter is set means that new suites aren't affected.
If my understanding is correct, then I'd like to fix this by:

When a passed/failed test is added, walk the DOM structure of suites to add a "contains passed/failed test" class to each ancestor suite of that test.
Update the CSS to hide suites that descend from the pass/fail class on the root and do :not() have the "contains passed/failed test" class.
Remove the suite stuff from the JS that fires on clicking the filter button.

This should achieve the same end result as directly hiding/showing suites on the addition of passed/failed tests, but since it separates the state of the filter from whether a suite should be shown or hidden in any given filter state, the filter state is simplified to one CSS class and the JS on the whole doesn't get more complicated (we'd replace the suite hiding/showing code with suite pass/fail-containing-marking code, rather than keeping the filter-state-finding and suite hiding/showing code but also adapting it to add a variation in another place), and the whole thing involves less direct manipulation by individual mutation of the end result and more semantic underlying behavior from which the right result should emerge in any given situation. That's what I think I'm going to advocate for at the moment anyway. ;^)
Either way, I'll see if I can devise tests for tests and suites being hidden correctly when the filter is activated before the relevant tests are added, and add them to #2900 (actually, ought to be tests in there that I can adapt for this just by moving the click-filter line). Any that aren't passing I can mark as pending and we can try either or both possible solutions and validate them by un-skipping those tests!

Sounds good, I have no personal experience with the code :stuck_out_tongue: Looking forward to the fix!

@ScottFreeCode could you give an update for this issue? It seems that #2900 is blocked on #2886. In turn #2886 was blocked on #2890, but that has been resolved as of yet. Does that mean #2886 can be moved forward to unblock #2900 as well? Looking forward to your reply 😄

A lot of the stuff that #2886 and #2900 touched was overhauled in release 4, so I need to figure out how to rewrite each of those PRs to keep their intended changes while applying them to the current version of Mocha -- and then we'll find out for sure whether #2890 really did get fixed or only some other types of hanging. It shouldn't take too long once I can really devote some time to it but it's the kind of comprehensive analysis that I can't easily do in bits and pieces, so it's going to have to wait till I have a free evening or two to devote to it.

While making a new html-electron reporter I tend to try to streamline the original html reporter.
I added a link to the duration display to enable showing only slow tests (slow/medium) and also an 'all' link
To get the filtering working while tests are still running I created a  function updateHiding()
This is then called from each of the filter events and from inside the updateStats() function.
/**
 * Stats template.
 */

var statsTemplate = '
' +
  '
<canvas width="40" height="40"></canvas>
' +
  '
all:
' +         // <- added link
  '
passes: 0
' +
  '
failures: 0
' +
  '
duration: 0s
' + // <- added link
  '
';

var playIcon = '‣';

/**
 * Initialize a new `HTML` reporter.
 *
 * @api public
 * @param {Runner} runner
 */
function HTML_Electron (runner) {
  Base.call(this, runner);

  var self = this;
  var stats = this.stats;
  var stat = fragment(statsTemplate);
  var items = stat.getElementsByTagName('li');
  var allLink = items[1].getElementsByTagName('a')[0];  // <- added link and indexes adjusted
  var passes = items[2].getElementsByTagName('em')[0];
  var passesLink = items[2].getElementsByTagName('a')[0];
  var failures = items[3].getElementsByTagName('em')[0];
  var failuresLink = items[3].getElementsByTagName('a')[0];
  var duration = items[4].getElementsByTagName('em')[0];
  var durationLink = items[4].getElementsByTagName('a')[0];  // <- added link
  var canvas = stat.getElementsByTagName('canvas')[0];
  var report = fragment('

');
  var stack = [report];
  var progress;
  var ctx;
  var root = document.getElementById('mocha');

  if (canvas.getContext) {
    var ratio = window.devicePixelRatio || 1;
    canvas.style.width = canvas.width;
    canvas.style.height = canvas.height;
    canvas.width *= ratio;
    canvas.height *= ratio;
    ctx = canvas.getContext('2d');
    ctx.scale(ratio, ratio);
    progress = new Progress();
  }

  if (!root) {
    return error('#mocha div missing, add it to your document');
  }

  // *******************
  const reState = / fail| pass| time/g

  function updateHiding() {
    unhide()
    var found = report.className.match(/pass|fail|time/)
    if (found) switch (found[0]) {
      case 'pass':
        hideSuitesWithout('test pass')
      break;

      case 'fail':
        hideSuitesWithout('test fail')
      break;

      case 'time':
        hideSuitesWithNoneOf(['test medium','test slow'])
      break;
    }
  }
  // show all
  on(allLink, 'click', function (evt) {
    evt.preventDefault();
    report.className = report.className.replace(reState, '');
    updateHiding()
  });

  // pass toggle
  on(passesLink, 'click', function (evt) {
    evt.preventDefault();
    var name = (/pass/).test(report.className) ? '' : ' pass';
    report.className = report.className.replace(reState, '') + name;
    updateHiding()
  });

  // failure toggle
  on(failuresLink, 'click', function (evt) {
    evt.preventDefault();
    var name = (/fail/).test(report.className) ? '' : ' fail';
    report.className = report.className.replace(reState, '') + name;
    updateHiding()
  });

  // duration toggle
  on(durationLink, 'click', function (evt) {
    evt.preventDefault();
    var name = (/time/).test(report.className) ? '' : ' time';
    report.className = report.className.replace(reState, '') + name;
    updateHiding()
  });

.
.
.

  function updateStats () {
    // TODO: add to stats
    var percent = stats.tests / runner.total * 100 | 0;
    if (progress) {
      progress.update(percent).draw(ctx);
    }

    // update stats
    var ms = new Date() - stats.start;
    text(passes, stats.passes);
    text(failures, stats.failures);
    text(duration, (ms / 1000).toFixed(2));

    updateHiding()  // <-  !!!
  }

/**
 * Check for suites that do not have elements
 * with any of `classnames`, and hide them.
 *
 * @param {text[]} classnames
 */
function hideSuitesWithNoneOf (classnames) {
  var suites = document.getElementsByClassName('suite');
  for (var i = 0; i < suites.length; i++) {
    var count = 0;
    for (var j = 0; j < classnames.length; j++) {
      var els = suites[i].getElementsByClassName(classnames[j]);
      count += els.length
    }
    if (count === 0) {
      suites[i].className = suites[i].className.replace(
        'suite',
        'suite hidden'
      );
    }
  }
}

I hope this will be of help for furthering the project. @ScottFreeCode

@ScottFreeCode Would you be so kind giving another update on this issue? Thanks!


non recurrent mode for variational dropout

variational dropout as described in Gal et al., 2016 does not have the expected result for NMT. Adding a new mode variational_non_recurrent for further exploration.

Codecov Report

Merging #390 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #390      +/-   ##
==========================================
- Coverage   69.62%   69.61%   -0.01%
==========================================
  Files          74       74
  Lines        6282     6290       +8
==========================================
+ Hits         4374     4379       +5
- Misses       1908     1911       +3

Impacted Files
Coverage Δ

onmt/modules/Encoder.lua
92.2% <100%> (ø)
:arrow_up:

onmt/modules/GRU.lua
94.44% <100%> (ø)
:arrow_up:

onmt/modules/LSTM.lua
98.3% <100%> (ø)
:arrow_up:

onmt/train/Trainer.lua
17.69% <0%> (-0.21%)
:arrow_down:

onmt/data/Preprocessor.lua
92.97% <0%> (+0.05%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b3b26fc...7cf6909. Read the comment docs.


How to add access policies to key vault, when add app service. I need principal id of added api service.

Discussed in https://github.com/Azure/bicep/discussions/3747

Originally posted by motycak July 26, 2021
How to add Access Policies to Key Vault, when adding App Service? I need "Principal ID" of added App Service.
I'm trying to get a Principal ID. But I get error on deployment:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"InvalidTemplate","message":"Unable to process template language expressions for resource '/subscriptions/xxxxxxx-yyyyyy-xxxxxxxx/resourceGroups/my-resource-group-name/providers/Microsoft.KeyVault/vaults/my-key-vault-name/accessPolicies/add' at line '1' and column '2267'. 'The language expression property 'identity' doesn't exist, available properties are 'apiVersion, location, tags, kind, properties, deploymentResourceLineInfo, subscriptionId, resourceGroupName, scope, resourceId, referenceApiVersion, condition, isConditionTrue, isTemplateResource, isAction, provisioningOperation'.'"}]}
My code:
param baseName string
param deploymentEnvironment string
param appServicePlanId string
param appInsightsInstrumentationKey string
param aspnetEnvironment string
param appConfigurationEndpoint string
param service string = ''
param location string = resourceGroup().location
param tags object = {}

resource apiService 'Microsoft.Web/sites@2018-11-01' = {
  name: '${baseName}-${deploymentEnvironment}-${service}-api'
  location: location
  tags: tags
  properties: {
    serverFarmId: appServicePlanId
    httpsOnly: true
    clientAffinityEnabled: false
    siteConfig: {
      netFrameworkVersion: 'v4.0'
      http20Enabled: true
      alwaysOn: true
      webSocketsEnabled: false
      ftpsState: 'Disabled'

      appSettings: [
        {
          name: 'ASPNETCORE_ENVIRONMENT'
          value: aspnetEnvironment
        }
        {
          name: 'APPINSIGHTS_INSTRUMENTATIONKEY'
          value: appInsightsInstrumentationKey
        }
        {
          name: 'AppConfig:Endpoint'
          value: appConfigurationEndpoint
        }
        {
          name: 'WEBSITE_ENABLE_SYNC_UPDATE_SITE'
          value: 'true'
        }
        {
          name: 'WEBSITE_RUN_FROM_PACKAGE'
          value: '1'
        }
      ]
    }
  }
}

resource keyVault 'Microsoft.KeyVault/vaults@2021-04-01-preview' existing = {
  name: 'prefix-${deploymentEnvironment}-kv'
}

var appKeyVaultPermissions = {
  keys: [
    'get'
    'list'
  ]
  secrets: [
    'get'
    'delete'
  ]
  certificates: []
  storage: []
}

resource keyVault_accessPolicies 'Microsoft.KeyVault/vaults/accessPolicies@2019-09-01' = {
  name: '${keyVault.name}/add'
  properties: {
    accessPolicies: [
      {
        tenantId: subscription().tenantId
        objectId: apiService.identity.principalId
        permissions: appKeyVaultPermissions
      }
    ]
  }
}
```</div>

See #2419.  The identity property isn't available as the app service hasn't been created with an identity.  If you set the identity when creating the app service, it should work.
identity: {
  type: 'SystemAssigned'
}

It works. Thanks. @afscrome


CSS keyframe animations do not work in Firefox w/ cleanslate

Hi Ya'll,
I am building a chat widget typing indicator animation and using cleanslate. The issue is that cleanslate's transform: none !important is overriding my animation keyframe transform declarations.
Heres part of the CSS animation that makes the typing indicator bounce:
@keyframes wave {
      0%, 60%, 100% {
        transform: initial !important;
      }
      30% {
        transform: translateY(-3px) !important;
      }
      85% {
        transform: translateY(1px) !important;
      }
    }

From MDN: "Declarations in a keyframe qualified with !important are ignored."
The animation is somehow playing on all browsers (Chrome, IE11, Safari) except for Firefox. Likely because most browsers allow animations of properties that have been previously qualified with !important whereas Firefox does not allow animations of declarations previously qualified with  !important.
Any thoughts? What do you recommend for folks working on stuff reset with Cleanslate that require animations? Thank you!

That's an interesting problem. I'm not sure if there's anything reasonable
you could do. Presumably using the Web Animations API (a JavaScript
interface for CSS animations) would have the same result, but could be
worth checking. Please let us know if you find any workaround.
Depending on what you are making and how it is deployed, you might be able
to avoid Cleanslate by using another sandboxing mechanism. These days,
there are Custom Elements which can be sandboxed from the host page CSS.
--
Prem Rose
dharmafly.com
premasagar.com

Thanks for the quick reply @premasagar ! After doing some research I think it might make sense to remove animation declarations from Cleanslate. Am considering forking and making this modification. Heres why:

https://bugzilla.mozilla.org/show_bug.cgi?id=854242 - This explains that Firefox explicitly ignores any animations that are qualified with !important

https://tosbourn.com/firefox-honours-important-in-css-animations-no-one-else-seems-to/ - Toby explains that other browsers ignore !important when it comes to animation declarations. So they work regardless of !importance and follow regular cascading.

Is it possible that animation declarations should be omitted from Cleanslate because majority of browsers don't respect !important on them and it actually breaks Firefox animations?

I have found a work around which works but it may not be the best solution.
.cleanslate div{     -webkit-box-shadow: none; /* remove !important*/     box-shadow: none; /* remove !important*/ }
Removing !important from these lines fixes the keyframe animation issue.
@gingersnapp If you were able to find a better solution, please let me know. Thanks!

@faizan47 no I never found a better solution :(


[REEF-944] Fix typos in TestRuntimeStartHandler

JIRA:
REEF-944
Pull Request:
Closes #

Looks good, I will merge.

Thank you, @afchung .


[helm] Add support for relabelings and metricRelabelings an serviceMonitor

Pull Request Motivation
I need additional metrics on cert-manager, since we have more than one.
Kind
feature
Release Note

[helm] Add support for relabelings and metricRelabelings an serviceMonitor

Thanks for the PR @jkroepke .
We aim to keep the cert-manager helm chart without options to configure advanced features that cannot be tested and can't be easily verified if they work or not, see https://cert-manager.io/docs/contributing/policy/#additional-configuration-options-for-the-helm-chart
I'm afraid the relabelings seem to fall into that category. I would recommend that you use another mechanism such as Helm post-install hooks (from the doc linked above) to configure it for your servicemonitors. I hope that makes sense and again thanks for the contribution!

Hi @irbekrm
thanks for sharing the current policies. I added e2e tests for the service monitor. By installing the CRDs on the kind cluster. Helm will do API validations before apply the manifests to the local cluster. This guaranteed that the service monitor manifests are correctly generated. The service monitor object in combination are highly accepted in the kubernetes world. I would much appreciate it, if cert-manager could support this.
The advertised option using helm post hooks is a nice try, but this option will never work in GitOps approaches. On Top, ArgoCD does not support helm post renderer.
Since the relabel configs are part of the e2e test suite, I'm looking forward here since the mentioned category does not longer apply here.

/assign @inteon

Thanks for adding the tests @jkroepke . I don't think that it really tests that the new fields contain valid values as we do not have a Prometheus instance installed that would actually use them in any way. There are additional issues with this PR such as the fact that it enables ServiceMonitor creation by default which we should not do as not all users will have those APIs and it seems like other unrelated values like intervals are added/changed.

but this option will never work in GitOps approaches. On Top, ArgoCD does not support helm post renderer.

I think that's a matter of a discussion as to whether we change our policy in regards to helm chart features like this. Happy to have that discussion and you're welcome to add it our meeting notes and discuss, but for now it seems to me that this feature clearly matches what we've stated we won't add to charts.

I don't think that it really tests that the new fields contain valid values

Please take a look that the CRDs first.
https://github.com/prometheus-operator/prometheus-operator/blob/1758cd6256cd4c328ee8f74ea8866443ead6b0d8/example/prometheus-operator-crd-full/monitoring.coreos.com_servicemonitors.yaml#L356
The CRDs from the Prometheus Operators having validation options. From point of view, of a helm chart, is should be enough from my point of view.
I don't think that 3rd party functionality doesn't need to test here, since they are already covered by prometheus itself. cert-manager (chart) setups the configuration. The added e2e tests covers if the generated ServerMonitor configuration. Which should fine-enough for a helm chart.

Well I may not able speak english fluent enough to be part of one of your meetings, but the current strict policies for the helm-chart feels unnatural and I have not seen this pattern on any another project yet.


install in Windows-Sandbox

Description of the new feature / enhancement
Add a new CLI option for installing packages into Windows Sandbox, e.g. via winget test <manifest>/winget sandbox <manifest> or winget install --sandbox <manifest>.
Note that this was already proposed in #253, but I cannot retrace why it was "only" implemented as a Powershell script and not natively into winget. Pinging @felipecrs, who might be interested in implementing this?
This would allow users to install/try applications in the Windows Sandbox directly from winget, without having to download/git clone the winget-pkgs repo.
UPDATE: Note that my request goes beyond verification/validation of manifests, but to have full winget functionality in the Windows Sandbox, plus being able to spin it up from the host machine and install the desired application with winget.
I use the SandboxTest.ps1 quite frequently for example when I want to install a different version than I have installed locally or when I want to have a clean environment. I would be even better, if I could tell someone "run winget install --sandbox <manifest of your application> to reproduce".
I am not sure if this has any overlap with #386.
Proposed technical implementation details
This would incorporate the functionality of SandboxTest.ps1, but natively in winget. That would make it possible to easily install applications from remote sources (msstore, winget-pkgs, etc.) as well.
IMHO winget install --sandbox <manifest> would be preferable, since we probably want "Install this manifest, just do it in the Windows-Sandbox". I don't know, however, if all winget install arguments would be applicable to a sandbox install as well.

I find it neat, indeed. But I'm not so sure if it is worth it.
The bar is lower for contributing a PowerShell script in a repository that will only get accessed by developers who clone it if compared to this repository.
If it were to be included in the winget-cli source code, I suspect we would need to spend many more cycles to make the code production-ready (we are talking about delivering it to any Windows 10/11 device out there). One example is internationalization.
But anyway, I'm saying this as my opinion only. I would be happy to see it in winget-cli as well.

Pinging @felipecrs, who might be interested in implementing this?

I am not interested... but that does not change much, as I know very little about C# anyway.

I would also add that not every device supports the windows sandbox. Given that winget is supported on Win10 Home edition, it could be very confusing for someone to think that the option was available but then find they don’t meet the requirements to enable the sandbox. Given that developers are more likely to read into the documentation, having the script is good enough in my opinion.
There are also other challeneges to running winget in the sandbox such as ensuring that VCLibs and the XamlLibs are installed; This is relatively easy to do with a powershell script, but for the client to do this would involve more downloading and copying of files, unless it were to only download the application and provide it as a file available to the sandbox and not install winget inside the sandbox. This would mean that users should be informed that additional dependencies would be downloaded, which may cause some users security concerns.
For a majority of users, I dont believe there is a business case that makes sense to integrate directly with the sandbox for installation.

not every device supports the windows sandbox

I'd be surprised if that couldn't be queried easily on winget startup.
As for the business case:

Windows Sandbox provides a lightweight desktop environment to safely run applications in isolation.
https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-sandbox/windows-sandbox-overview

The winget command line tool enables users to discover, install, upgrade, remove and configure applications on Windows 10 and Windows 11 computers.
https://docs.microsoft.com/en-us/windows/package-manager/winget/

Those are literally the first sentences on those two pages. "run applications" and "install (etc.) applications" sounds like those two should definitely work together. Actually I'd find it pretty weird if the Windows Package Manager wouldn't be integrated in the Windows Sandbox.

I think this is probably better in wingetcreate:

microsoft/winget-create/issues/98

I see the use case of verification/validation in Sandbox more applies there.
Running in a sandbox as opposed to the OS is an interesting scenario to consider. I'll leave this one open to see if it gets any traction (as in more 👍).

@denelon Thanks! I see this as going beyond "just" verification/validation of manifests, namely to "discover, install, upgrade, remove and configure applications" in the sandbox for whatever reason. In my case this has mostly been debugging, but I am sure there are other use-cases as well.
Having winget available within the sandbox when it is installed on the host machine would already go a long way (is it on Win11? it definitely isn't on my Win10). Being able to spin up the sandbox from winget on the host machine (like SandboxTest.ps1 does) would be even better.

I wanted to test an automated installation script in Windows Sandbox and introduce winget for some dependencies. I found that winget is not available in the sandbox. I don't know of other implications, e. g. Microsoft Store is also not available there as well.
As it was mentioned before: The purpose of the sandbox to run apps in isolation and the ability to automate installation of apps using winget is a perfect fit.

@calle2010 you can definitely leverage the SandboxTest.ps1, as it allows you to run any script.

This should be a no-brainer. I expected it to be there already and got heavily dissapointed.

I used the new DSC Resource for configuring the WIndows Sandbox in:

https://github.com/microsoft/winget-cli/issues/3887

I uploaded the files to that issue in a .zip.
We are working on samples and better documentation to be added to https://aka.ms/dsc.yaml.

@vedantmgoyal9 "can install winget using DSC" doesn't mean that it winget is available in the sandbox after a "normal" winget install, is it? AFAIU DSC is a feature for developers (i.e. not all users) and requires additional install or configuration steps from the user.
What I meant with this issue is that winget is available in the sandbox on a default windows install (assuming that winget and sandbox are installed, of course).

This would allow users to install/try applications in the Windows Sandbox directly from winget, without having to download/git clone the winget-pkgs repo

... fuss with additional setup steps.
So being able to install winget using DSC does not solve this issue completely, as far as I am concerned (unless I am missing something?). If that's the best we can/want to do ATM, then that's fine, of course, but it does not solve it the way I meant.

I've reached out to the Windows Sandbox team with several requests. I don't have timelines for these, but I thought I'd share a few:

Include App Installer from Host OS
Ability to increase disk size for Sandbox
Ability to pass a configuration file to the sandbox

I hope we dont have to manually install WinGet. It should be available by default, without us needing to modify anything.

I'm here because I use sandbox daily for testing things. Today I wanted to use winget to deploy something and was pleased to find it should be on all recent versions of Windows 10 and 11. I was not pleased to find that it doesn't work in sandbox without additional setup.


Inline props as object

Fixes #43.
This PR changes the interface for React.Dom.domProps. Before these changes, domProps was a function with ~400 optional labelled arguments, after these changes we treat it as an object.
There are a few reasons for this change, but the most important is bundle size. jsoo compiles the optional arguments into zeros generating per each domProps call near 400 zeros, jsoo treated labeled arguments as positions into arrays. There are a few issues opened about this, I only found this one though: https://github.com/ocsigen/js_of_ocaml/issues/801
Another of the reasons is about correctness, props in React are an object and after those changes, we treat it as an Object as well. Giving the same flexibility as the underneath layer could enable features that aren't possible on reason-react or rescript/react, for example adding missing attributes, allowing destructuring props in bindings, allowing "data"-attributes or type-safety on certain attributes.
Todos

[x]  Basic functionality with attributes
[x]  What should we do with ref and key
[x]  Type-safe attributes
[x]  Type-safe events
[x] Add suppressContentEditableWarning
[x] Add dangerouslySetInnerHTML
[x] Update snapshot tests
[ ] Add a few test cases
[ ] Fix test baseSuite:refs:forwardRef (maybe it's related with my doubt? probably no)
[ ] Analyze better the bundle-size
[ ] Re-visit dangerouslySetInnerHTML type/format.

Doubts
I have a doubt about the ref prop. Right now the ref is typed with React.Dom.Ref.t option but React.Dom.domRef doesn't seem to return an optional. But I believe the bindings are not the same as reason-react since they use an anonymous type from the useRef.
File "example/src/Code.re", line 14, characters 14-45:
14 |     <code ref={React.Dom.Ref.domRef(codeRef)}> {text |> React.string} </code>
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error: This expression has type React.Dom.domRef
       but an expression was expected of type React.Dom.domRef option

Future
As mentioned before, this change allows us a few niceties on the dom attributes API, from the top of my head:

[ ] We could add more type-safety on many properties:

[ ]  polyvariants (for example ?preload is now string (* "none", "metadata" or "auto" (and "" as a synonym for "auto") *) None | Metadata | `Auto)
[ ]  dates (for example: max (* should be int or Js.Date.t *)`
[ ]  regex
[ ]  etc

[ ]  We could add warnings/errors about deprecated attributes
[ ] Try to implement "data" attributes (if the propName starts with "data", we render the value without any typecheck.

PS: I have the editor configured to format using ocamlformat, I believe we should run it across all files (I separate the formatting into one commit, in order to not affect the review)

This is a quick analysis of bundle size impact of this PR using webpack-bundle-analyzer.
For each case, I ran:

make build-prod from project root folder
Then yarn webpack:production from examples folder (previously adding new BundleAnalyzerPlugin() to webpack plugis list.

This branch (https://github.com/reason-in-barcelona/jsoo-react/pull/66/commits/84e7869ba23ec3c7e9be85233cc4da4318a85920):

Master branch (https://github.com/reason-in-barcelona/jsoo-react/commit/1ff26837c94142005a61fea5316df0028529132d):

Bringing this in. Thanks again @davesnx !


Further Warnings Needed for Marketo Salesforce Native Sync using OAuth

Issue in ./help/marketo/product-docs/crm-sync/salesforce-sync/setup/enterprise-unlimited-edition/step-1-of-3-add-marketo-fields-to-salesforce-enterprise-unlimited.md
I've had two customers this month who have inadvertently linked their Marketo instance to the wrong Salesforce Instance because of the nature of the Oauth Process.

Clear your browser cache

Sorry, hit submit too early. Can you please add these tips to the documentation as an EXTRA warning?


Speed up entry creation

PR Description
This PR  ensures that entries are created quickly by persisting the last entry on the form.
Issue
#400

So I thought about the feedback you gave and it is really good. But I came up with another idea. Instead of injecting the created record into the redirect, we could instead, get the last hour for the current user. We could pass in current_user.hours.last to prefilled the hours' form and current_user.mileages.last to prefilled the mileages form. With this approach, even when the user logged out and comes back after some time, the form would still be prefilled with the last saved entry.  I hope that sounds good.


Relative refs inside of a ref'd section have the wrong context.

Observed when running swagger-codegen generate -l typescript-node -o SDK -i index.yaml against this source.
I've created two branches with minimal examples. The only relevant files for these branches are index.yaml, path/infomous.yaml and definitions/error.yaml.
The testforron branch demonstrates the breakage on what I believe to be the correct syntax/path for the ref in path/infomous.yaml.
The testforron2 branch demonstrates that the ref is working in path/infomous.yaml. In this case, the path is being resolved as if it were from the root, not from the path subdirectory.
This may be related to an issue reported on swagger-codegen.

@nicksloan Did this resolve things for you?  I'm working with a spec and referenced schemas that live on a file system, and the master branch still appears to suffer from the same problem you describe here.  I can try to craft a failing test; however, if this works for you and you're using a file system as opposed to hosting these files, I'm pretty sure I must be misunderstanding something.

@fehguy Can you verify this fix is supposed to work for specs on the filesystem?  If so, isn't this test data problematic?  IMO, it should be:
"$ref": "../paramaters/params.json#/param1"

As an aside, I hope to help some.  Just have to convince the powers that be!

@crankydillo I think you are right. That reference points to a folder that doesn't exist at that level, but one above (inside json directory).


Aspire: Support rabbitmq.connection.v0, rabbitmq.server.v0

We need to come up with a design for how we want to run this on Azure - It's not 100% clear what we want to do here - we need some production ready managed service at some point, but we might be able to get a way with "run an open source version as a container" as we do for our dev redis service with ACA.

Moving this to the Germanium semester bucket. We can pull it into appropriate milestones as we move along. Currently for Aspire Preview 3 we are targeting to add support for sql/sqlserver and cosmos
@davidfowl @mitchdenny @ellismg @spboyer @gkulin

We will not add hand-crafted, template-based Bicep deployment support in azd. Instead, we will be moving towards using bicep resource type and CDK effort.

https://github.com/dotnet/aspire/issues/1941
https://github.com/Azure/azure-dev/issues/3279


redirect all json api logs into separate test file

@rgolovat @vdelendik I think it makes sense to add parameter for that feature to make it optional. Since in many api test projects it's more suitable to have all log files in one place and there is no need to remove http logs for passed tests.
Also isn't it needed to add http.log to zafira artifacts to publish it afterwards?


[stable/openldap] Fix for "spec.clusterIP: Invalid value" error on upgrade

What this PR does / why we need it:
Ensures users can upgrade existing installs
see

https://github.com/helm/charts/pull/13646

Checklist

[x] DCO signed
[X] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @jlegrone

/ok-to-test


fix generate repo so it's does a git init - fixes #551

fixes git init never actually executing when generating a repo - #551

Merged as 9fc27347505d1be804e94b31b5843146ea604f65 with a slight cleanup in 4d4cc8d685ace0dba98553de70036efaa945c979
Thanks for contributing!


Bug: Can't import PubNub package

Is this a bug report?
Yes
Did you try recovering your dependencies?
Yes
Environment

Environment Info:
System:
OS: Windows 10
CPU: (8) x64 Intel(R) Xeon(R) CPU E3-1245 v5 @ 3.50GHz
Binaries:
Node: 12.9.1 - E:\nodejs\node.EXE
Yarn: 1.17.3 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.10.2 - E:\nodejs\npm.CMD
Browsers:
Edge: 41.16299.248.0
Internet Explorer: 11.0.16299.15
npmPackages:
react: ^16.9.0 => 16.9.0
react-dom: ^16.9.0 => 16.9.0
react-scripts: Not Found
npmGlobalPackages:
create-react-app: Not Found

Steps to Reproduce

yarn create react-app --scripts-version @react-workspaces/react-scripts test
cd test && yarn add pubnub
vi src/App.js
Add import pubnub from "pubnub"; at the top
yarn start

Expected Behavior
Start with only a unused warning
Compiled with warnings.

./src/App.js
  Line 4:  'pubnub' is defined but never used  no-unused-vars

Actual Behavior
Compiles but give a runtime error in the browser.

Uncaught TypeError: Cannot read property 'fd' of undefined
at Function.useColors (node.js:60)
at createDebug (debug.js:112)
at Object. (index.js:14)
at Object../node_modules/http-proxy-agent/index.js (index.js:110)
at webpack_require (bootstrap:781)
at fn (bootstrap:149)
at Object../node_modules/pac-proxy-agent/index.js (index.js:36)
at webpack_require (bootstrap:781)
at fn (bootstrap:149)
at Object../node_modules/proxy-agent/index.js (index.js:22)
at webpack_require (bootstrap:781)
at fn (bootstrap:149)
at Object../node_modules/superagent-proxy/index.js (index.js:4)
at webpack_require (bootstrap:781)
at fn (bootstrap:149)
at Object../node_modules/pubnub/lib/networking/modules/node.js (node.js:11)
at webpack_require (bootstrap:781)
at fn (bootstrap:149)
at Object../node_modules/pubnub/lib/node/index.js (index.js:16)
at webpack_require (bootstrap:781)
at fn (bootstrap:149)
at Module../src/App.js (App.css?4433:45)
at webpack_require (bootstrap:781)
at fn (bootstrap:149)
at Module../src/index.js (index.css?f3f6:45)
at webpack_require (bootstrap:781)
at fn (bootstrap:149)
at Object.0 (serviceWorker.js:135)
at webpack_require (bootstrap:781)
at checkDeferredModules (bootstrap:45)
at Array.webpackJsonpCallback [as push] (bootstrap:32)
at main.chunk.js:1

Reproducible Demo
Can't recreate the issue in codesandbox.  Creating the issue in a new project as described above is fast and straightforward.
Some tests I did

Tried with nodejs 10.16.3/12.9.1 with same issue.
Tried with official react-scripts 3.0.1 and 3.1.1 and I do not face the issue.

Thanks

Are you still trying to get this working?


Search behavior has changed? Not getting expected results

There seems to be some changes in the search behavior recently. I'm not longer getting expected results, based on previous behavior
This link, for example is used to open MapRoulette to any given coordinates and display all tasks available from the osmapaaralan challenge.
Here are some observations:
Search results are now significantly slower to appear

Clicking on clustered results , the map will zoom in and then display no markers for taks that are supposed to be available

Browsing the same area manually shows a different number of markers for the challenge

Manually browsing tasks , and clicking on markers works as expected.

Addressed by maproulette/maproulette2#811

Still getting unexpected results. The link in the original post will show that tasks are available in the area, but when markers are clicked, they disappear.
Also, it seems like keywords (to limit search to certain challenges) are being ignored, and maybe that's why the search results are taking longer to appear?
For example, this search link: https://maproulette.org/browse/challenges?challengeSearch=124.23950850963594%2C7.190261702587633%2C124.24515187740327%2C7.193343264569108&keywords=osmapaaralan&location=intersectingMapBounds displays tasks that doesn't use the "osmapaaralan" keyword.

Hi @govvin this will be fixed in the next release. I think the issue got closed when the fix was merged in, but it hasn't yet been released.
I will reopen the issue until it's deployed to maproulette.org to avoid any further confusion. Thanks for staying on top of things!

The fix is now deployed to maproulette.org -- please let me know if you continue to experience problems.

I confirm that this is now working as expected, and getting the search results seem to be back to its previous speed.


Status Code 401  on Login

Hi,
I try to used your code to connect to my client Metasys WebServer. I cannot pass this failure code 401 on the Login call.
Is there any specifics that need to be done on the server to pass this error and be able to login and than use all the other feature calls.

I used to work with the OLD MSSDA but need to upgrade.
The Metasys server is on Computer 1 where my Application would be on Computer 2 however under the same private network.
Computer 1 (Metasys) has a certificat installed.
Function: Login Message: Call failed with status code 401 (Unauthorized): POST https://**********/api/v3/login Source: MetasysServices Trace:    at JohnsonControls.Metasys.BasicServices.BasicServiceProvider.ThrowHttpException(FlurlHttpException e)    at JohnsonControls.Metasys.BasicServices.MetasysClient.<TryLoginAsync>d__38.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at JohnsonControls.Metasys.BasicServices.MetasysClient.TryLogin(String username, String password, Boolean refresh)
Function: sendCMD2Control Message: Call failed with status code 401 (Unauthorized): GET https://*********/api/v3/objectIdentifiers?fqr=********%3ATDC1-NAE2BMA%2FProgramming.HVAC%20CALLS.Tower-6.T6-06HVAC%205525 Source: MetasysServices Trace:    at JohnsonControls.Metasys.BasicServices.BasicServiceProvider.ThrowHttpException(FlurlHttpException e)    at JohnsonControls.Metasys.BasicServices.MetasysClient.<GetObjectIdentifierAsync>d__46.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at JohnsonControls.Metasys.BasicServices.MetasysClient.GetObjectIdentifier(String itemReference)

The biggest issues with login are

Not using a user with type API User
Not logging in to MUI or SMP with that account at least one time to accept terms and conditions.


Chat scroller rework

This PR fixes major issues with the scroller on mobile. It's not absolutely perfect, but should be an improvement.
Further work/known issues:

Fix scrolling to newest items
Fix main pane scroll when scrolling to an item in a thread
Polish loader appearance
Implement better estimateSize
Improve key and spacebar navigation on desktop

Fixes LAND-898
Fixes LAND-406
Fixes LAND-691

code is looking great! This is feeling buttery on both desktop and mobile, was immediately sad when i had to go back to the production version 🙃
the only non-fine tuning issue I ran into a few times was a channel getting stuck and not loading anything beyond the current messages it had. I think this is just an issue with the top/bottom detection in the fetch new messages effect because resizing the screen did seem to resolve it. I'll try to snag a video, but it was pretty sporadic.
"view new messages" banner was also working intermittently for me, but i belive that's a known issue.


delete slide feature would be useful

The slides property (prs.slides) only supports add_slide and rename_slides method. It would be useful, if we have a delete_slide method as well.
Thanks.

Duplicate of #67.


Implementation of Gradient-guided nested sampling

Is your feature request related to a problem? Please describe.
While nested sampling is implemented in jax in this package, it does not (to my knowledge) make use of jax autograd. There is a recent paper describing a gradient-guided nested sampling method that actually cites this package! https://arxiv.org/pdf/2312.03911.pdf
Describe the solution you'd like
I would like an implementation in this package, ideally so that I can use it in numpyro. I do not have time to work full-time on an implementation myself, but I would be interested in a joint-effort as well if that is preferred/needed.
Additional context
There is an example pytorch implementation here: https://github.com/Pablo-Lemos/GGNS/tree/main

Hi thanks for the idea. I've considered this before. I could introduce this as an experimental feature. It would need to be assessed will before becoming part of the core engine.
The focus of jaxns is fast easy general purpose probabilistic programming. I'm trying to keep the amount implementation experimentation needed by a user to solve their problem to a minimum so they can focus on building better models. To that end I'm not looking to have a library of nested sampling implementations. But I can explore this from an experimental perspective. If the engine can be improved and still remain general purpose and robust with good defaults that solve most problems then it could be an option. This year at the MaxEnt conference I'll discuss the latest nested sampling research with others in the field and plan to update jaxns accordingly.

I see, thank you for the update! My initial impression from the paper is that this method allows for nested sampling to be extended to higher dimensional models. My current research interest is in applying bayesian methods to simulation-based inference problems which often have quite large latent spaces, and so I was hoping this would be the best of both worlds between NUTS/HMC (better scaling with large models) and nested sampling (marginal likelihoods and evidence).
I will keep posted for now, then; feel free to reach out if you ever need an early tester!

You should try out an experimental feature of jaxns: parametrised models. In jaxns you can let some variables be Bayesian and some be pointwise estimates of a prior. When you solve the model it finds the parameter values that maximizes the evidence and gives you the posterior of the rest. This can be really powerful, since a full Bayesian treatment with huge latent spaces is impractical for large dimension. You can use this to have Bayesian hierarchical models that perform well.On Jan 20, 2024 06:53, Juehang Qin @.***> wrote:
I see, thank you for the update! My initial impression from the paper is that this method allows for nested sampling to be extended to higher dimensional models. My current research interest is in applying bayesian methods to simulation-based inference problems which often have quite large latent spaces, and so I was hoping this would be the best of both worlds between NUTS/HMC (better scaling with large models) and nested sampling (marginal likelihoods and evidence).
I will keep posted for now, then; feel free to reach out if you ever need an early tester!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Thank you for the suggestion; do you have any papers on this topic? I couldn't find much about this kind of method with a cursory search; I suppose it is similar to profile likelihoods but I was wondering if there are any papers exploring the statistical properties of this procedure, what the limitations are, etc.

It's novel, and I will write a paper after I answer some of these questions myself. Are you interested in being a part of the paper? If your example use case is a good fit then it could be the example for the paper.On Jan 20, 2024 23:53, Juehang Qin @.***> wrote:
Thank you for the suggestion; do you have any papers on this topic? I couldn't find much about this kind of method with a cursory search; I suppose it is similar to profile likelihoods but I was wondering if there are any papers exploring the statistical properties of this procedure, what the limitations are, etc.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

I would love to, and I do think I have a model that would be a reasonable use-case (there are 1e2~1e5 latent parameters, depending on dataset, but because those latent parameters correspond to individual events we don't necessarily care about knowing these parameters better than a best-fit estimate).
On top of that, model comparison is something I would be interested in with this model, so nested sampling would be perfect. Would you like to talk about this over zoom or something? Otherwise perhaps we can move this conversation off of the github issue for now 🙂

From: Joshua George Albert @.>
Sent: Sunday, January 21, 2024 9:58:35 AM
To: Joshuaalbert/jaxns @.>
Cc: Juehang Qin @.>; Author @.>
Subject: Re: [Joshuaalbert/jaxns] Implementation of Gradient-guided nested sampling (Issue #136)
It's novel, and I will write a paper after I answer some of these questions myself. Are you interested in being a part of the paper? If your example use case is a good fit then it could be the example for the paper.On Jan 20, 2024 23:53, Juehang Qin @.***> wrote:
Thank you for the suggestion; do you have any papers on this topic? I couldn't find much about this kind of method with a cursory search; I suppose it is similar to profile likelihoods but I was wondering if there are any papers exploring the statistical properties of this procedure, what the limitations are, etc.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHubhttps://github.com/Joshuaalbert/jaxns/issues/136#issuecomment-1902678833, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJLCK34SGYY7IQCXXO2CF3TYPU3KXAVCNFSM6AAAAABB7SJNZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBSGY3TQOBTGM.
You are receiving this because you authored the thread.Message ID: @.***>

Yes, sounds like a good idea. Do you have LinkinedIn? This is my profile and easy to connect there and move to email/zoom.On Jan 21, 2024 22:09, Juehang Qin @.***> wrote:
I would love to, and I do think I have a model that would be a reasonable use-case (there are 1e2~1e5 latent parameters, depending on dataset, but because those latent parameters correspond to individual events we don't necessarily care about knowing these parameters better than a best-fit estimate).
On top of that, model comparison is something I would be interested in with this model, so nested sampling would be perfect. Would you like to talk about this over zoom or something? Otherwise perhaps we can move this conversation off of the github issue for now 🙂

From: Joshua George Albert @.***>
Sent: Sunday, January 21, 2024 9:58:35 AM
To: Joshuaalbert/jaxns @.***>
Cc: Juehang Qin @.>; Author @.>
Subject: Re: [Joshuaalbert/jaxns] Implementation of Gradient-guided nested sampling (Issue #136)
It's novel, and I will write a paper after I answer some of these questions myself. Are you interested in being a part of the paper? If your example use case is a good fit then it could be the example for the paper.On Jan 20, 2024 23:53, Juehang Qin @.***> wrote:
Thank you for the suggestion; do you have any papers on this topic? I couldn't find much about this kind of method with a cursory search; I suppose it is similar to profile likelihoods but I was wondering if there are any papers exploring the statistical properties of this procedure, what the limitations are, etc.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHubhttps://github.com/Joshuaalbert/jaxns/issues/136#issuecomment-1902678833, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJLCK34SGYY7IQCXXO2CF3TYPU3KXAVCNFSM6AAAAABB7SJNZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBSGY3TQOBTGM.
You are receiving this because you authored the thread.Message ID: @.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Implementing a basic version of this now. Benchmarks show slightly improved estimates of logZ and KL(posterior || prior) due to faster decorrelation from initial seed points. Note, I use a different approach than in the paper.


Support multiple "spawned-by"s

When trying to add multiple Spawned-bys, an error occurs when compiling.
YAML Exception reading /github/workspace/docs/Windows/System32/systemreset.exe/index.md: (<unknown>): found a tab character that violate indentation while scanning a plain scalar at line 10 column 7

I'm not able to reproduce this issue, is this a case where you used a tab instead of four spaces?


requireSpaceAfterLineComment: drop allowSlash value

Drop deprecated value for this rule in 2.0.
According to #696

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/5378555-requirespaceafterlinecomment-drop-allowslash-value-in-2-0?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github).

Moving to #1834


Fix behaivor of MaxCpuSockets

What this PR does
See issue for background. Now MaxCpuSockets will no be used if a VM defines more sockets but rather the #of sockets will be used for MaxSockets.

Fixes #12394
Links to places where the discussion took place:
Special notes for your reviewer

Release note

MaxCpuSockets won't block creation of VMs with more Sockets than MaxCpuSockets declare

Based on https://github.com/kubevirt/kubevirt/pull/12583

/approve

/kind bug

@lyarwood  Can't reply directly https://github.com/kubevirt/kubevirt/pull/12599#discussion_r1763757824 so here I go. I agree with you, the fact Antonio asked about the same proves this is wrong but I want to backport this so I am keeping it small intentionally.
PTAL

/lgtm

/cherrypick release-1.3

/cherrypick release-1.2


Rewrite MochaResponse so it won't be so reliant on StringBuilder

https://stackoverflow.com/questions/76789555/java-http-server-is-not-rendering-images-properly/76791070#76791070

MochaResponse should also be able to render JSON and other application files.


Stepper Slide Animation Doesn't Work

When upgraded to 0.1.2+10, pressing next or previous button the animation don't follow the steps, like showed:
https://user-images.githubusercontent.com/9019172/109513641-16b27d00-7a84-11eb-8647-b19ba8743bfc.mp4
PS: maybe property Alignment is related to the problem?

Is the function available again?


v5.0.0 formal release checklist

Today we had a user on Discord wondering if it was safe to use neon-js as it looked unmaintained. After a short discussion with the user I understand where that point of view comes from.

Documentation; The current documentation is outdated and is still talking about neo3 preview 2, NEP5 and one guide even uses Fixed8 and other outdated code.
Repo first look; The last commit on the master branch is from July 2021, the dev and neo3 branches are even further back and the Releases side bar shows the latest release being May 2020. Without knowing that next is the NEO3 branch I would also think the project is abandoned.

Neo 3 has been live for some months now, and I think that the next branch has N3 covered pretty good that I believe it is time to see if we can make a formal release of v5.0.0, no?
Todo

[x] #820
[ ] #822
[x] #823
[x] #824
[x] #825
[x] #827
[ ] #831
[ ] #832

I have commented or fixed all relevant issues. I don't think cleanup should be a blocker for the release. Is there anything else? I know docs are lacking but we can release the code first.

I need to stop reading github by mail as I loose notifications on the web when I can actually do something with it.
All good enough for me. Let's release it!


Fix exit code of run-tests.sh

Right now run-tests.sh exits with success even if a test failed. Fix it.
Signed-off-by: Vivek Goyal<EMAIL_ADDRESS>

cc @cgwalters @jlebon @rhatdan

Makes sense to me.


Documentation for the C Wrapper

Heya,
Is there a guide or documentation around the methods used in the C wrapper please, sorry If I've missed them?
Thanks
Marc

There's not really much in the way of C API documentation unfortunately. The C API is pretty close to the rust API, which is documented at https://docs.quic.tech/quiche/#structs
quiche_config_* -> https://docs.quic.tech/quiche/struct.Config.html
quiche_conn_* -> https://docs.quic.tech/quiche/struct.Connection.html
etc.

Closing since the immediate question was answered. While it might be nice to improve the C docs, the Rust docs are a lot more ergonomic to maintain and read, and port over ok.


docs(performance): remove section on literal vs enum performance

Change Summary
I've removed the docs on the performance differences between using a literal or an enum. It seems the performance improvements made in 2.7 have made them perform nearly identically in the previous example, so unless theres a case missing, it doesn't seem worth promoting this tip anymore.
Related issue number

Checklist

[x] The pull request title is a good summary of the changes - it will be used in the changelog
[x] Unit tests for the changes exist
[x] Tests pass on CI
[x] Documentation reflects the changes where applicable
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

So for some benchmarks, using the following script:
import enum
from timeit import timeit

from typing_extensions import Literal

from pydantic import TypeAdapter

ta = TypeAdapter(Literal['a', 'b'])
result1 = timeit(lambda: ta.validate_python('a'), number=1000000)

class AB(str, enum.Enum):
    a = 'a'
    b = 'b'

ta = TypeAdapter(AB)
result2 = timeit(lambda: ta.validate_python('a'), number=1000000)
print(result2 / result1)

on 2.6.4 -> 2.80
on 2.7.0 -> 0.99
Im using a 2022 M2 macbook, maybe results differ on other platforms.

please review

@ollz272,
Nice work! Thanks!!


Is there any way to keep the sidebar closed when the page loads on the docs template?

As the question says.
Currently, the sidebar is always open (on desktop screen size) when  the page loads and the user has the option to close the sidebar once the page loads by clicking the toggle button. But isi there a way to keep the sidebar closed when the page loads, and  later the user can  click on the toggle button to open the sidebar.
How can I achieve it? Is there any options for this?

There is no way to do it

It might be possible by storing the value in localStorage or cookie, then attaching a script that loads the value and display the sidebar if it is enabled
Example:
<body class="group-sidebar-open">   <!-- Attached by the script -->
    <script></script> <!-- Add "group-sidebar-open" class to body if enabled -->
    <aside class="hidden group-[-sidebar-open]:block">...</aside>
</body>