Selecting a kernel from remote server searches for kernels "forever", Failed to parse remote URI

Environment data

VS Code version: Version: 1.79.2 (Universal)
Commit: 695af097c7bd098fbf017ce3ac85e09bbc5d
Jupyter Extension version (available under the Extensions sidebar): v2023.5.1101742258
Python Extension version (available under the Extensions sidebar): v2023.10.1
OS (Windows | Mac | Linux distro) and version: mac Ventura 13.3
Python and/or Anaconda version: 3.9.16
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Jupyter server running: remote

Expected behaviour
When selecting a kernel from an existing jupyter server a list of running kernels is presented so that the user can pick one.
Actual behaviour
No list of kernels is presented but the blue progress bar (perhaps indicating ongoing search for kernels) runs forever without producing any result.
Steps to reproduce
Command-Shift-P -> Select Kernel -> Existing Jupyter Server -> http://toyen.sklik-vyzkum.ko1.os.scif.cz:10891/lab?token=mytoken -> some name of the kernel -> blue progress bar running indefinitely
See please the log below. Please note that there are two "failed to parse" messages: one regarding the currently entered server, another regarding a server that I entered some time before. The addresses of servers are given exactly as printed out by jupyter lab. VS Code is apparently able to communicate with the server as it returns an error message if no token or a wrong token is given.
Log (Command-Shift-P -> Jupyter: Show output)
18:16:33.350 [error] Failed to parse remote URI http://toyen.sklik-vyzkum.ko1.os.scif.cz:10891/lab?token=mytoken Error: Invalid remote URI
at qr (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.5.1101742258-linux-x64/out/extension.node.js:2:1694598)
at hk.parseUri (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.5.1101742258-linux-x64/out/extension.node.js:24:530090)
at ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.5.1101742258-linux-x64/out/extension.node.js:24:528878
at b.invoke (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
at deliver (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:2121)
at n.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:1729)
at f._fireDidAccept (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:102:114142)
at E.$onDidAccept (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:102:112352)
at s.N (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:112:11717)
at s.M (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:112:11435)
at s.H (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:112:10516)
at s.G (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:112:9494)
at ~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:112:8282
at b.invoke (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
at deliver (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:2121)
at n.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:1729)
at p.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:73:14783)
at ~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:128:32461
at b.invoke (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
at deliver (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:2121)
at n.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:1729)
at p.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:73:14783)
at D.E (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:73:18830)
at ~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:73:16818
at b.invoke (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
at deliver (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:2121)
at n.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:1729)
at h.acceptChunk (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:73:12514)
at ~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:73:11801
at b.invoke (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
at deliver (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:2121)
at n.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:1729)
at E.u (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:128:20017)
18:16:46.410 [error] Failed to setup finder for Select Kernel Error: 'Failed to parse remote URI http://jp2.sklik-vyzkum.ko1.os.scif.cz:10791?token=xyz
at qr (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.5.1101742258-linux-x64/out/extension.node.js:2:1694682)
at ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.5.1101742258-linux-x64/out/extension.node.js:17:126648
at async Promise.all (index 0)
at ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.5.1101742258-linux-x64/out/extension.node.js:17:126492

Thank you for filling this issue and I’m sorry you are running into this problem
Looks like a duplicate of #13602
Please open the command palette then select the command
‘ Jupyter: Clear Jupyter Remote Server List’
once since please re-enter the url and try again
this should work

I am sorry, but this is not a duplicate. I cleared the remote server list (even before posting the issue), and it does not alleviate the error. (Please note that I also know about another issue where clearing server list failed, but this is not my case.) Moreover 13602 is related to connecting to Codespace server and some remapping of ports (not this case). There seems to be some mistake regarding parsing URIs
Failed to parse remote URI http://toyen.sklik-vyzkum.ko1.os.scif.cz:10891/lab?token=mytoken Error: Invalid remote URI
This is precisely the URI I wish to connect to, so it is difficult to see how clearing remote server list could help.
Jupyter output after clearing server list (please note that Jupyter: Clear Remote Server List does not output anything in Jupyter output)
01:28:18.370 [error] Failed to parse remote URI http://toyen.sklik-vyzkum.ko1.os.scif.cz:10891/lab?token=mytoken Error: Invalid remote URI
at qr (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.5.1101742258-linux-x64/out/extension.node.js:2:1694598)
at hk.parseUri (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.5.1101742258-linux-x64/out/extension.node.js:24:530090)
at ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.5.1101742258-linux-x64/out/extension.node.js:24:528878
at b.invoke (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
at deliver (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:2121)
at n.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:1729)
at f._fireDidAccept (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:102:114142)
at E.$onDidAccept (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:102:112352)
at s.N (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:112:11717)
at s.M (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:112:11435)
at s.H (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:112:10516)
at s.G (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:112:9494)
at ~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:112:8282
at b.invoke (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
at deliver (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:2121)
at n.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:1729)
at p.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:73:14783)
at ~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:128:32461
at b.invoke (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
at deliver (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:2121)
at n.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:1729)
at p.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:73:14783)
at D.E (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:73:18830)
at ~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:73:18009
at b.invoke (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
at deliver (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:2121)
at n.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:1729)
at h.acceptChunk (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:73:12514)
at ~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:73:11801
at b.invoke (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
at deliver (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:2121)
at n.fire (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:63:1729)
at E.u (~/.vscode-server/bin/695af097c7bd098fbf017ce3ac85e09bbc5dda06/out/vs/workbench/api/node/extensionHostProcess.js:128:20017)
01:28:39.181 [error] Failed to setup finder for Select Kernel Error: 'Failed to parse remote URI http://jp2.sklik-vyzkum.ko1.os.scif.cz:10791?token=xyz
at qr (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.5.1101742258-linux-x64/out/extension.node.js:2:1694682)
at ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.5.1101742258-linux-x64/out/extension.node.js:17:126648
at async Promise.all (index 0)
at ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.5.1101742258-linux-x64/out/extension.node.js:17:126492

Please note that the remote URI which VS Code failed to parse could be open in a web browser (and the jupyter session there was flawless).

I’m sorry you’re still running into this issue.
Please  Could you install vscode insiders and the latest pre-release version of the Jupyter extension 2023.6.100* and let me know if the problem still exists in that version,
if not then we know it’s fixed in the main branch, else it’sa completely new issue and  would require more logging and investigation

Thank you for your help and quick reopening of the issue. The bug is fixed in the main branch. When connecting to a kernel from vscode insiders as suggested, all is fine. I have tested this multiple times, with both jupyter lab and jupyter notebook URI. Connecting also works (please excuse I have omitted this potentially important source of information) when VS Code is SSH connected to a host or attached to a running container.

Thank you very much for texting this again and getting back

Adding to this, I had the same issue on VScode main one after latest update; installing insider version solved the problem.

I also have this issue. It works when i use the insider version, but when will this be fixed in the main one? The insider version's Side by Side editing is quite a pain to use at the moment...

The latest release (with fixes from insiders version) will be released some time this week

Thanks. For info the version 1.8.0 is not working for me

new update today and issue fixed for me; thank you.


use memcpy inside ctypes_read/ctypes_write to avoid undefined behaviour

When stub generation is used, Ctypes can also deal with packed structs. Once packed structs are use, the pointer arithmetic inside ctypes_read and ctypes_write is not longer valid (similar issue like #584 ).
The test doesn't produce any error - C compilers are quite tolerant. But libubsan would complain:
/usr/home/andreas/ocaml-ctypes/src/ctypes/type_info_stubs.c:105:25: runtime error: store to misaligned address 0x604000000411 for type 'int64_t' (aka 'long'), which requires 8 byte alignment
0x604000000411: note: pointer points here
 00 80 40  7f 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /usr/home/andreas/ocaml-ctypes/src/ctypes/type_info_stubs.c:105:25 in
/usr/home/andreas/ocaml-ctypes/src/ctypes/type_info_stubs.c:104:25: runtime error: store to misaligned address 0x604000000439 for type 'int32_t' (aka 'int'), which requires 4 byte alignment
0x604000000439: note: pointer points here
 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /usr/home/andreas/ocaml-ctypes/src/ctypes/type_info_stubs.c:104:25 in
/usr/home/andreas/ocaml-ctypes/src/ctypes/type_info_stubs.c:61:45: runtime error: load of misaligned address 0x604000000411 for type 'int64_t' (aka 'long'), which requires 8 byte alignment
0x604000000411: note: pointer points here
 00 80 40  7f ef cd ab 90 78 56 34  12 00 f0 e6 d5 c4 b3 a2  91 33 40 00 00 00 00 00  00 00 30 54 76
              ^
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /usr/home/andreas/ocaml-ctypes/src/ctypes/type_info_stubs.c:61:45 in
/usr/home/andreas/ocaml-ctypes/src/ctypes/type_info_stubs.c:60:45: runtime error: load of misaligned address 0x604000000439 for type 'int32_t' (aka 'int'), which requires 4 byte alignment
0x604000000439: note: pointer points here
 00 00 00  00 78 56 34 12 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00

There's something odd about this, since whichever struct layout the compiler uses, it's always valid to read from write to struct fields through a pointer.  It seems that the packed structs rather than the read/write code are the source of undefined behaviour.

I think it might be the casting to an unaligned pointer that is the undefined behaviour (the cast will always be aligned in the case of a normal, unpacked struct).
Found a good explanation here:
https://stackoverflow.com/questions/46790550/c-undefined-behavior-strict-aliasing-rule-or-incorrect-alignment/46790815#46790815

it's always valid to read from and write to struct fields through a pointer.

No, just simple assignments are valid, when the type definition of the packed struct is present. Taking the address of a packed struct member is dodgy, because the address might not be a multiple of its type's alignment. Compilers warn about it, if the context is present:
typedef struct __attribute__((packed)) packed {
    char c;
    int x;
} packed;

void foo(void){
  packed a = {'a',1};
  int b = a.x; /* valid, because type definition of packed is known */
  int * c = &a.x; /* invalid, warning enabled by default with recent
     gcc and clang versions: -Waddress-of-packed-member: "taking address of
     packed member of ‘struct packed’ may result in an unaligned pointer value"
   */
}

And the address of a packed struct members might be passed to ctypes_read and ctypes_write where the casts wrongly tell the compiler that the pointers are suitably aligned.

@fdopen: I mean that packed structs aren't part of standard C, and in standard C, a program that (1) takes the address of a struct field, then (2) reads/writes through that address during the object's lifetime is always valid.
I agree that reading/writing through an misaligned pointer is an error.  But what's odd here is that the problem arises in step (1), and the proposed fix is to change step (2).  One possible consequence of this approach is that every read and write to memory will suffer a performance cost for potentially misaligned access.


bb requires libc++

It actually happened to be while live coding at the NoirCon workshop.
Proposed solution is to bbup to install libc++

Personal preference is that we list dependencies in the docs, rather than being installed directly in a script.

Yep this needs a different approach, namely through docs. I'll open a different PR for that


Add Code Of Conduct

Fixed issue #74

@Itachii27 u used gpt didnt u

You got many things wrong check pls

You got many things wrong check pls

I didn't use chatgpt. I took reference from different repositories. Apologies that the introduction is not right. I have done changes please check again.

@Itachii27 press on commit suggestion

Hi @aditya-bhaumik I have done.


add unit tests

closes #6
This codifies examples from the toplevel README into executable tests.

Thanks @kostmo !


Some of the properties for resources need to be Nilable

I've started playing with this library to develop a K8s operator but bumped into a few issues. I had to adjust by hand a few properties in the Pod resources for this to work; I suspect it might be the case for other resources as well.
field generate_name : String?

also
field block_owner_deletion : Bool?

I haven’t noticed this before when fetching Pods from the k8s API, but I went ahead and made them nilable. One of the hard parts about porting these data structures to Crystal is having to go through all the places these resources are defined in the K8s code and figuring out which ones are marked with omitempty and either setting defaults or making them nilable. In a few places I’ve set defaults (like strings to empty, booleans to false, numbers to 0, etc) but I’m still figuring out how some of these properties are used outside of K8s itself.
Also since I rarely use more than a few properties from any resource I’ve mostly only added things that either seem useful or that I’ve actually used. If there’s a way to export a CRD-style spec for some of these resources we could just use Kubernetes.import_crd to load them.
A lot of this shard is still trial and error, but it does work for operators I’ve been building:

NATS (StatefulSet, Service, PersistentVolumeClaim)
Postgres (StatefulSet, Service, PersistentVolumeClaim)
Redis (StatefulSet, Service, PersistentVolumeClaim)
Heroku-style App operator (Certificate, Ingress, Service, Deployment, Job)


Fix Studio :: OpenPype :: Disable 'persp' camera on Build workfile from template

In GitLab by @support-bot on Mar 7, 2023, 08:14
When we build an asset workfile with build workfile from template, we load our turntable camera.
But then we have 2 renderables camera : persp and turntable mayaSceneMain_01_:cam
To render the turntable we know that we will always have to disable the persp camera so we would like it disable and at the build of the workfile.
Maybe a way to be more generic would be to have a maya python script available to us (in Openpype Settings)so that we could do several custom command specific to each task.

Softwares concerned
Maya, Fix

Merge request
https://github.com/ynput/OpenPype/pull/4815

This is working, tested in several context, asset / shot, it's good

A new ticket was opened for this specific issue : https://github.com/quadproduction/OpenPype/issues/421


Colors of demo

After updating to Coreui 4.3.2 Pro, it seems like the colors defined are not the same as the ones on the demo :
Demo :
Mine :
I can't find the same colors of 4.3. All my colors are the one of 4.2

The all layout looks different. As exemple, i don't have the same shadows. I feel like I have the old SASS file.


Remove cutSuffix as its go >=1.20 only

Tested and works as expected, merging directly to unblock building under fips


ObjectDB instances leaked at exit

Godot Engine v4.3.stable.official.77dcf97d8 on Linux x86_64
As per the sample code in the readme:
var qr_code: QrCode = QrCode.new()

# choose the level of error correction (LOW, MEDIUM, QUARTILE, HIGH)
qr_code.error_correct_level = QrCode.ErrorCorrectionLevel.LOW

var texture: ImageTexture = qr_code.get_texture("Godot") # Add your text here

var qr_code_image := $Path/To/QrCodeImage
qr_code_image.texture = texture

When exiting my application:
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
     at: cleanup (core/object/object.cpp:2284)
Leaked instance: GDScriptNativeClass:9223372047558640203
Leaked instance: GDScript:9223372063413109958 - Resource path: res://qr_code.gd
Leaked instance: GDScript:9223372064017089738 - Resource path: res://reed_solomon_generator.gd
Leaked instance: Node:32380028260 - Node name:
Leaked instance: Node:32396805477 - Node name:
Leaked instance: Node:32413582694 - Node name:
Leaked instance: Node:32430359911 - Node name:
Leaked instance: Node:32447137128 - Node name:
Leaked instance: Node:32463914345 - Node name:
Leaked instance: Node:32480691562 - Node name:
Leaked instance: Node:32497468779 - Node name:
Leaked instance: Node:32514245996 - Node name:
Leaked instance: Node:32531023213 - Node name:
Hint: Leaked instances typically happen when nodes are removed from the scene tree (with `remove_child()`) but not freed (with `free()` or `queue_free()`).
ERROR: 2 resources still in use at exit.
   at: clear (core/io/resource.cpp:599)

If I add qr_code.queue_free() after the last line above:
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
     at: cleanup (core/object/object.cpp:2284)
Leaked instance: GDScriptNativeClass:9223372047558640203
Leaked instance: GDScript:9223372064017089738 - Resource path: res://reed_solomon_generator.gd
Leaked instance: Node:32396805477 - Node name:
Leaked instance: Node:32413582694 - Node name:
Leaked instance: Node:32430359911 - Node name:
Leaked instance: Node:32447137128 - Node name:
Leaked instance: Node:32463914345 - Node name:
Leaked instance: Node:32480691562 - Node name:
Leaked instance: Node:32497468779 - Node name:
Leaked instance: Node:32514245996 - Node name:
Leaked instance: Node:32531023213 - Node name:
Hint: Leaked instances typically happen when nodes are removed from the scene tree (with `remove_child()`) but not freed (with `free()` or `queue_free()`).
ERROR: 1 resources still in use at exit.
   at: clear (core/io/resource.cpp:599)

Am I doing something wrong or is there a fix?

Thanks for the fix @JonnyTech :)


[bug] AsyncAutoResetEvent deadlocks

Run this test.   On my computer, it deadlocks after about 6 seconds
	[TestMethod]
	public async Task DotNextAsyncAutoResetEvent()
	{
		DotNext.Threading.AsyncAutoResetEvent autoResetEvent = new(false);

		var loopCount = 0;
		var setCount = 0;
		var consumedCount = 0;
		var timer =Stopwatch.StartNew();
		var lastSecondReported = 0;
		var producerTask = Task.Run(() => {

			while (true)
			{
				loopCount++;
				var didSet = autoResetEvent.Set();
				if (didSet)
				{
					setCount++;
				}

				if (timer.Elapsed > TimeSpan.FromSeconds(lastSecondReported))
				{
					var tup1 = new { loopCount };
					var tup = new { loopCount, setCount, consumedCount };
					Console.WriteLine($"t={lastSecondReported}sec:  {new { loopCount, setCount, consumedCount }}");
					lastSecondReported++;
				}

				if (timer.Elapsed > TimeSpan.FromSeconds(30))
				{
					break;
				}
			}
		});

		var consumerTask = Task.Run(async () => {

			while (true)
			{
				var success = await autoResetEvent.WaitAsync(TimeSpan.FromMilliseconds(1));
				if (success)
				{
					consumedCount++;
				}
				if (producerTask.IsCompleted)
				{
					break;
				}
			}
		});

		await producerTask;
		autoResetEvent.Set();
		await consumerTask;
	}

using DotNext 4.0.0-beta.8 from Nuget

@jasonswearingen , .NEXT RC1 has been released. It uses GA version of .NET 6 so you can try tests again.

The bug is still there.  deadlocks in same location.   tested with dotnet6.0 release

I found the root cause:

Thread # 1: ManualResetCompletionSource.CancellationRequested is trying to enter monitor infinitely
Thread # 2: ManualResetCompletionSource.OnCompleted is trying to enter monitor infinitely
Thread # 3: ManualResetCompletionSource.StopTrackingCancellation stuck on timeoutTracker.Dispose() method

timeoutTracker is of type CancellationTokenRegistration. I think that Dispose waits for completion of cancellation callback. In the same time, cancellation callback stuck on Thread # 1. So Dispose is called within monitor and cancellation callback too. As a result, we observe a dead lock.

According to sources in .NET repo, Dispose call is blocking while Unregister not.

@jasonswearingen , many thanks for reporting this bug! The potential fix is in develop branch. The related commit is specified above.


how is the Version Compatibility??

refer to composer.json of LaravelFly.
It runs on laravel 5.5 which requires php7.
This project is for speed , so there is no need to consider php5 which is much slower than php7.
swoole 2 will be requied when concurrent service for Laravel are added.


[fix] FMA LIR Type fixed for ternary nodes

Ternary nodes should infer the LIR type using the three operands. LIR types for FMA instructions were getting the LIR with the first two values, instead of the 3 operands. This patch fixes that.
Backend/s tested

[X] OpenCL
[X] PTX

OS tested

[X] Linux
[ ] OSx
[ ] Windows

Did you check on FPGAs?
If possible, check your changes on FPGAs.

[ ] Yes
[X] No

How to test the new patch?
make tests
tornado-test.py -pk --debug -V -J"-Ds0.t0.device=0:0" --fast uk.ac.manchester.tornado.unittests.matrices.TestMatrices#testMatrixMultiplication

I added a few tests:
tornado-test.py --debug -pk -V --fast  uk.ac.manchester.tornado.unittests.math.TestMath#testFMA
tornado-test.py --debug -pk -V --fast  uk.ac.manchester.tornado.unittests.math.TestMath#testFMA2

Graal will perform a typecast before the FMA operation, in the case the data types differ. However, still the LIR should be the combination of all operands.


Observability task: registration center related index data improvement investigation and improvement（可观测性任务注册中心相关指标数据完善调研与完善)

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Describe the proposal

En:This is mainly to deal with the interaction between Dubbo and the registration center. For users, they can understand the interaction time between the current system and the registration center, registration mode, connection status and other indicators, so that developers can keep track of the health status of the application and the registration center to assist in troubleshooting. and optimize performance.
中文：这里主要是处理Dubbo内部与注册中心的交互，对于用户来说了解当前系统内部与注册中心的交互时间，注册模式，连接状况等指标，方便开发者随时掌握应用与注册中心的健康状况协助排查问题与优化性能。

pls assign to me

Referring to Google's 4 golden indicators, for the registration center, I think the following indicators are needed.

dubbo_registry_duration_seconds
Interaction delay, interaction behavior includes service register, subscription, heartbeat, indicating the network connection status of the application and registry center

dubbo_registry_notify_total
The change notification push received by the consumer side indicating the frequency of the service provider online or offline

dubbo_registry_connect_total
The number of times to reconnect with the registry center, indicating the available time of the registry center

In addition, a large change in the number of application instances will lead to an increase in received push traffic, which may cause a huge change in 【memory usage】 and have a greater impact on the 【gc】 of the current application.
These two indicators belong to the system indicators and are not included for the time being.
中文：参考google四大黄金指标，我认为注册中心应该需要的指标如下：

dubbo_registry_duration_seconds
交互延迟，交互行为包含注册、订阅、心跳，反映应用和注册中心的网络连接状况
dubbo_registry_notify_total
consumer端接收到的变更通知推送，反映服务提供者上下线的频率
dubbo_registry_connect_total
与注册中心重连的次数，反映注册中心的可用时间

另外，应用实例数的大量变化会导致接收的推送流量增大，可能会造成内存使用的巨大变化，并且对当前应用的gc造成较大影响。
这两个指标属于系统指标，暂时不列入。
Anyone have suggestions?

可以的，正常的服务订阅，服务注册，接收通知，查询服务几个场景
指标类型可以处理下次数，耗时，错误次数
另外可以还有服务迁移过程显示的服务注册类型看看是否可以显示出来当前接口的服务注册类型比如当前是应用级别注册还是接口级别，订阅者当前是接口级别还是应用级别比较有利于观察dubbo升级迁移过程


KTO: fix logits metric, add logits metric to BCOTrainer

This is a continuation from #2077.
For the logits metric: when logging, aggregate the sum and divide by final count. Do not divide earlier.
Plus, this adds the same metric for BCO as well
@kashif @qgallouedec @PhilipMay

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Recommend periodic build frequency and update repos.

@theganyo: https://github.com/apigee-apihub-demo/petstore/pull/25#pullrequestreview-1472986625
Daily seems like a lot but I don't think it's costing us anything. I would like for builds to repeat with some periodicity so that we're aware of any broken dependencies.

What dependencies do we allow to float?

Even tagged dependencies can disappear.

True and even changed... perhaps we should be vendoring.


Timezone setup

How to set timezone for the scheduler to use timezone other than the local system / browser?

Unfortunately, no option for that in the current setup.

@aldabil21 will there be timezone support in the future?

@borstelmannl Honestly, I don't have a plan for this yet. But it's in the list of todos

Why day view is not working properly ?
Error: Uncaught TypeError: Cannot assign to read only property '0' of object '[object Array]'  appears if I choose day view in navigation.


Fixed form errors for comment

Can you please post a screenshot of the change? For comparison, this is how errors look right now:

Before:

After:

OK. The change only affects the comment form. I missed that. Sorry. Your change looks good to me :+1: Thanks.

Thanks for fixing this bug @hason.


also document oid for app only tokens

that it contains the id of the sP

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2471c08b-befe-8e1a-df08-f13e116c231e
Version Independent ID: 0d827d33-2906-6352-9398-13863def9354
Content: Microsoft identity platform access tokens - Microsoft identity platform
Content Source: articles/active-directory/develop/access-tokens.md
Service: active-directory
Sub-service: develop
GitHub Login: @hpsin
Microsoft Alias: hirsin

@kalyankrishna1
Thanks for your feedback! I have assigned this issue to the author who will investigate and update as appropriate.

@kalyankrishna1
Thanks for your feedback! I have assigned this issue to the author who will investigate and update as appropriate.

Thanks Kalyan, good callout.  #please-close


Bump up google-cloud-storage version to fix data corruption issue

The data corruption issue has been fixed since google-resumable-media-2.7.2 (https://github.com/googleapis/google-resumable-media-python/pull/451), and it is now covered in google-cloud-storage-2.8.2 (https://github.com/googleapis/python-storage/pull/1339).

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Do we know the range of beam versions affected? Was the upstream bug always there since gcs migration?
Beam version between 2.53.0 and 2.58.0 are affected by this problem, and yes, the upstream bug had been there since gcsio migration.

The bug was introduced two years ago at https://github.com/googleapis/google-resumable-media-python/pull/294, which was then released as version google-resumable-media-2.3.0.
We had our GcsIO migration at Beam release 2.53.0 ((https://github.com/apache/beam/commit/8ac8b20bcd180cb8cca41993e2cbd2ce81f7b862) and introduced the new dependency of google-cloud-storage-2.10.0, which depends on google-resumable-media-2.3.2. (https://github.com/googleapis/python-storage/blob/v2.10.0/setup.py#L34C6-L34C37).

Beam version between 2.53.0 and 2.58.0 are affected by this problem, and yes, the upstream bug had been there since gcsio migration.

Let's document this in an issue, see examples:
https://github[.]com/apache/beam/issues/30867#issue-2227999908
https://github[.]com/apache/beam/issues/28246#issue-1874558863

Beam version between 2.53.0 and 2.58.0 are affected by this problem, and yes, the upstream bug had been there since gcsio migration.

Let's document this in an issue, see examples:
#30867 (comment) #28246 (comment)

Thanks! Added #32169.


Secret from store refuses to pull latest version

Have you

[x] Read Troubleshooting Guide
[x] Searched on GitHub issues and Discussions

What steps did you take and what happened:

Updated the value of an existing secret in the keyvault
kubectl delete secret <secret>, when it recreated it used the old value.

I tried several things that I've had to do before to 'kick it' to get it working

I tried deleting the secrets-store-provider-azure and secrets-store-csi-driver pods, then deleting the secret. It still pulled the old value.
I tried disabling the old version of the secret in the azure portal, then doing 1. It still pulled the old value.
I tried explicitly updating the SecretProviderClass to point objectVersion to the new secret version, then doing 1. It still pulled the old value.
I upgraded to make sure I wasn't out of date.
I tried going to bed and doing all this again 9 hours later, no luck.

What did you expect to happen:
I expected eventually for the secret value to update.
Anything else you would like to add:
No suspicious error logs, only "reconcile started" and "reconcile completed" in the driver. If it matters at all, the old and the new secret values are precisely the same length.
Config subset:
apiVersion: secrets-store.csi.x-k8s.io/v1alpha1
kind: SecretProviderClass
metadata:
  name: <name>
spec:
  provider: azure
  secretObjects:
    - data:
      - key: mySecret
        objectName: mySecret
      secretName: apisecrets
      type: Opaque
  parameters:
    resourceGroup: "<name>"
    subscriptionId: "<guid>"
    tenantId: "<guid>"
    keyvaultName: "<name>"
    userAssignedIdentityID: "<guid>"

    usePodIdentity: "false"
    useVMManagedIdentity: "true"
    cloudName: ""
    cloudEnvFileName: ""
    objects:  |
      array:
        - |
          objectName: mySecret
          objectType: secret
          objectVersion: "91a53ae..."

Which access mode did you use to access the Azure Key Vault instance:
User Assigned Managed Identity
Environment:

Secrets Store CSI Driver version: (use the image tag): v0.0.20
Azure Key Vault provider version: (use the image tag): 0.0.13
Kubernetes version: (use kubectl version and kubectl get nodes -o wide): v1.18.14
Cluster type: (e.g. AKS, aks-engine, etc): AKS

@connor4312 I see you have the objectVersion defined
          objectVersion: "91a53ae..."

Is that the old object version? If object version is defined, then the provider will only pull that version. If you want to always get the latest, then the version should be empty.
https://azure.github.io/secrets-store-csi-driver-provider-azure/getting-started/usage/#create-your-own-secretproviderclass-object

objectVersion
no
version of a Key Vault object, if not provided, will use latest
""

No, that's the new object version. It was previously empty and I tried specifying the new version to get it to pull explicitly.

@connor4312 The Kubernetes secret is a mirror of the pod mount (https://secrets-store-csi-driver.sigs.k8s.io/topics/sync-as-kubernetes-secret.html). So until the pod mount has the old value, that's what will be used for the Kubernetes secret. You'll need to restart the pod after deleting the Kubernetes secret.
Or you can use the secret autorotation feature and the CSI driver will automatically update the mount and Kubernetes secret with the new version periodically: https://secrets-store-csi-driver.sigs.k8s.io/topics/secret-auto-rotation.html

If you're not using the autorotation feature, the steps are documented here: https://secrets-store-csi-driver.sigs.k8s.io/known-limitations.html#how-to-fetch-the-latest-content-with-release-v0014-and-earlier-or-without-auto-rotation-feature-enabled

Thanks, autorotation did the trick!
It'll be great once that becomes the default, it'll save a lot of pain for others 😄

@aramase

Or you can use the secret autorotation feature and the CSI driver will automatically update the mount and Kubernetes secret with the new version periodically: https://secrets-store-csi-driver.sigs.k8s.io/topics/secret-auto-rotation.html

Do I need to do anything special regarding this?
I have installed the chart as explained:
╰─$  helm -n devops ls | grep csi-secret
csi-secrets-store-provider-azure     	devops   	11      	2021-05-11 09:11:24.859690406 +0000 UTC	deployed	csi-secrets-store-provider-azure-0.0.18                                                                     	0.0.14

─$ helm -n devops get values csi-secrets-store-provider-azure
USER-SUPPLIED VALUES:
enableSecretRotation: true
rotationPollInterval: 2m

But it seems like secrets are not being updated:
kubectl get secretProviderClass clearml-agent-spc -o yaml
...
    objects: |
      array:
        - |
          objectAlias: clearml.conf
          objectName: hosted-clearml-conf
          objectType: secret
...
 provider: azure
  secretObjects:
  - data:
    - key: clearml.conf
      objectName: clearml.conf
    secretName: hosted-clearml-conf
...

status:
  mounted: true
  objects:
  - id: secret/hosted-clearml-conf
    version: a954692d5d864af0a3007f20310cc50e

While:
$ az keyvault secret list-versions --vault-name ourvault --name hosted-clearml-conf | jq -r ".[].id"
https://ourvault.vault.azure.net/secrets/hosted-clearml-conf/87fe67f39f1b46abb00d5e36112f8b6f
https://ourvault.vault.azure.net/secrets/hosted-clearml-conf/a954692d5d864af0a3007f20310cc50e

The newest version is different.
Checking the logs from the controller shows only

reconcile started
reconcile complete

of different pods.
Any idea what am I doing wrong?
Thank you
Shaked

@Shaked How are you providing the values for enableSecretRotation and rotationPollInterval. Is it under secrets-store-csi-driver in the values?
For example:
➜ helm install csi csi-secrets-store-provider-azure/csi-secrets-store-provider-azure --set secrets-store-csi-driver.enableSecretRotation=true --set secrets-store-csi-driver.rotationPollInterval=2m --set windows.enabled=false --set secrets-store-csi-driver.windows.enabled=true --set secrets-store-csi-driver.filteredWatchSecret=true

@aramase thank you! I missed the part of adding secrets-store-csi-driver.*. It's working :)


Add ngen integration workflow to gh actions

Reminder to include a ngen integration workflow similar to other formulation repos (e.g. cfe).  Currently, the existing workflow yaml just speaks to (1) standalone & (2) bmi unit testing scripts.

I am pretty preoccupied at the moment. Does anyone want to take a shot at
it? It is fairly straightforward. Just copy over the ngen_integration.yml
from one of the other submodules and make a few minor changes. I am ready
to help if you needed.
On Fri, Jan 26, 2024 at 12:30 PM JessicaGarrett-NOAA <
@.***> wrote:

Reminder to include a ngen integration workflow similar to other
formulation repos (e.g. cfe
https://github.com/NOAA-OWP/cfe/blob/master/.github/workflows/ngen_integration.yaml).
Currently, the existing workflow yaml
https://github.com/NOAA-OWP/lstm/blob/master/.github/workflows/test_unit_standalone.yml
just speaks to (1) standalone & (2) bmi unit testing scripts.
—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-OWP/lstm/issues/41, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACA4SRJNLGSFLDB7S5JD76TYQPY2ZAVCNFSM6AAAAABCMRVLJSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYDENZQGA4DMMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I am pretty preoccupied at the moment. Does anyone want to take a shot at it? It is fairly straightforward. Just copy over the ngen_integration.yml from one of the other submodules and make a few minor changes. I am ready to help if you needed.

@stcui007 - I went ahead and assigned this to myself :) I'll take a stab at it next week and will reach out if any issues come about.  -thanks!

@Jessica Garrett - NOAA Affiliate @.***> Thanks for
taking this on.
On Fri, Jan 26, 2024 at 3:37 PM JessicaGarrett-NOAA <
@.***> wrote:

I am pretty preoccupied at the moment. Does anyone want to take a shot at
it? It is fairly straightforward. Just copy over the ngen_integration.yml
from one of the other submodules and make a few minor changes. I am ready
to help if you needed.
@stcui007 https://github.com/stcui007 - I went ahead and assigned this
to myself :) I'll take a stab at it next week and will reach out if any
issues come about. -thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-OWP/lstm/issues/41#issuecomment-1912729032, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACA4SRKFNRV2LBOTKQES7V3YQQOZ7AVCNFSM6AAAAABCMRVLJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJSG4ZDSMBTGI
.
You are receiving this because you were mentioned.Message ID:
@.***>


Other Tag Support

Currently, the only tag that works is the valid tag. Support for enabled, visible, and return must be supported as well.

Added support for all the remaining tags: enabled, visible, selector, and result.
In no particular order:

selector: A string value which doesn't inherently do anything. It is needed for enabled and visible to be used to their fullest extent.
enabled: A boolean value which represents whether or not its owner is enabled. Sets the "disabled" property as appropriate on the jQuery element represented by the selector tag. If the selector tag is omitted, then it will infer an input of the owning identifier's name.
visible: A boolean value which represents whether or not its owner is visible. Calls jQuery#show() and jQuery#hide() as appropriate on the jQuery element represented by the selector tag. If the selector tag is omitted, then it will infer an input of the owning identifier's name (though doing so looks awful and would probably never be done).
result: Any type of value which represents the resulting data format of the form. This value is primarily used on the server to be returned to user-code after a form has been successfully validated. This gives them their data in a useful organization immediately while allowing them to take advantage of the same format within the Uniform code.

Car form is essentially complete at this point, it is able to enable/disable or show/hide the form based on the state of the hasCar checkbox and works fairly well.
I did come across a minor issue in that the selector tag must come before a sibling enabled or visible tag. I filed #53 to address this when we get to it.

Regarding your commit comment about overriding an enabled or visible tag, I had totally forgotten about that. I've updated it so that any <input /> tag will follow the nearest parent enabled tag value. This means that it is possible to do:
<div id="carForm">
    <input name="make" />
    <input name="model" />
</div>

@carForm {
    selector: "#carForm";
    enabled: hasCar;

    make {
        enabled: not hasCar;
    }
}

The model input will follow enabled: hasCar, while the make input will follow enabled: not hasCar as it is overridden at a nearer DOM node.
Unfortunately, it was not technically feasible to create the same behavior for visible. When a node is given the style display: none, it collapses with all its children, and I could not find any method of showing a child when its parent is hidden. There are a couple CSS hacks involving the position style which we can't really use as we don't want to restyle the form.
Considering it doesn't make a lot of sense anyways, I'm inclined to say that visible: false on a parent trumps visible: true on a child. I think it is a little more intuitive that way. If people have an issue with that decision, then we can come up with another way of handling it.

You mentioned that there was a bug for selector having to be declared before enabled. Is there a ticket for that? Other than that looks good.

Yes, #53 is the issue to address that problem.


Enable Falcon 180B

What does this PR do?
This PR enables Falcon 180B Finetuning.

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

I pushed a commit because there were a few issues with the code block examples in the README.
One question, when you say "For inference we need to merge the pretrained model and LoRA weights", do you mean that users have to call .merge_and_unload() (see here) so that inference works? Or just that you need both checkpoints to run the LoRA model?

@regisss from the code below in run_lora_clm.py it looks like full model is being saved (not only LoRA parameters), what do you think?  @hlahkar please check this on your side.
https://github.com/huggingface/optimum-habana/blob/0dfda27dd0351d0753c35de2abb752309e2383b4/examples/language-modeling/run_lora_clm.py#L648C66-L648C66

I remembered when we tested falcon40b lora training checkpoint, we have to have both checkpoints to run inference. I remembered we tried load_and_merged call, it doesn't work well at that time
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: regisss @.>
Sent: Friday, November 24, 2023 8:45:24 AM
To: huggingface/optimum-habana @.>
Cc: Libin Tang @.>; Review requested @.>
Subject: Re: [huggingface/optimum-habana] Enable Falcon 180B (PR #537)
I pushed a commit because there were a few issues with the code block examples in the README.
One question, when you say "For inference we need to merge the pretrained model and LoRA weights", do you mean that users have to call .merge_and_unload() (see herehttps://github.com/huggingface/optimum-habana/blob/0dfda27dd0351d0753c35de2abb752309e2383b4/examples/text-generation/utils.py#L208C17-L208C36) so that inference works? Or just that you need both checkpoints to run the LoRA model?
—
Reply to this email directly, view it on GitHubhttps://github.com/huggingface/optimum-habana/pull/537#issuecomment-1825772100, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGLGHZP26XSAAKDXV7HCAADYGCXIBAVCNFSM6AAAAAA7RTUGKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRVG43TEMJQGA.
You are receiving this because your review was requested.Message ID: @.***>

I pushed a commit because there were a few issues with the code block examples in the README.
One question, when you say "For inference we need to merge the pretrained model and LoRA weights", do you mean that users have to call .merge_and_unload() (see here) so that inference works? Or just that you need both checkpoints to run the LoRA model?

@regisss Yes we are only storing the LoRA weights in this case; and the user will have to use '.merge_and_unload' to make inference work.


OCPBUGS-1973: Pass CPU limits to the container

It looks like S2I was already doing this, it just never got implemented in Docker and Daemonless
https://github.com/openshift/builder/blob/master/pkg/build/builder/sti.go#L359-L366

/jira refresh

/retest

/assign @nalind
Would you mind taking a look at this for me and make sure that I am not doing anything dumb? :)

/assign @bparees
ptal if you get a chance.

/retest
infra issues

/retest

i'm also interested in nalin's take.  my expectation is that this is safe because we were already cpu throttling due to running the container in the parent cgroup, so nothing should really change for the build process other than that the cpu cgroup values are explicilty exposed instead of just implicity enforced.
also iirc we have tests that ensure the memory limits are seen within the build, you should update those tests to do the same for cpu limits as part of this.

/hold
It looks like the CPU Limits may not be getting populated correctly.

There might still be a missing piece or two.  If I'm reading builderConfig.execute() in pkg/build/builder/cmd/builder.go right, some of the cgroup settings that we'll be applying are retrieved from the builder process's cgroups by calling GetCGroupLimits() in pkg/build/builder/util_linux.go, which currently doesn't appear to be reading CPU-related limits.  Those settings are then passed down to DockerBuilder.dockerBuild() in pkg/build/builder/docker.go.  So GetCGroupLimits() might need an update as well.


invitations: Default to empty channel list when inviting guest users.

This PR resets the channels list to be empty (with the default channels checkbox unchecked) when the user selects "Guests" from the role dropdown while inviting users. It includes the following changes:

When inviting users for guest roles, an empty channel list is displayed instead of the default channel list, and the default channels checkbox is unchecked.
When inviting users for non-guest roles, the default channels checkbox remains selected (maintaining the old behavior).
When switching between guest and non-guest roles, the previous state of included channels (if any specified explicitly by the user) for the guest role is restored while inviting a user as a guest.

Fixes: #31988.
Screenshots and screen captures:
Before Changes

1. Inviting Users as Guest

2. Inviting Users for Non-Guest Roles

3. Switching between Guest and Non-Guest Roles

After Changes

1. Inviting Users as Guest

2. Inviting Users for Non-Guest Roles (no changes)

3. Switching between Guest and Non-Guest Roles
Please note that if the channels named announce and Denmark are selected for the "Guests" role and then the role is changed to "Members" when switching back to the guest role, the previously selected channels are restored in the channel list.

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[ ] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@alya as mentioned in this comment, I have collaborated with @userAdityaa and mentioned him as a co-author in my commits. This PR is ready for review. Thank you.

Hey @alya, Ready for review!

Thanks @saubhagya-patel @userAdityaa !
@sahil839, would you be up for reviewing this one?

I am not sure about the expected behavior. The issue mentions that when switching between roles we should go back to previous state of what channels are included. So, does it mean that the list should become empty everytime I switch the role dropdown to guest from any other role and then when I change the role from guest to some other role, the list of streams should be what it was before the role was changed to guest?

The current behavior when inviting users is that the default channels are selected (the "default channels" checkbox is selected) for both Guest and Non-Guest roles.
Based on the changes discussed in the issue and the CZO thread, the following changes have been addressed:

When inviting users for non-guest roles, the default channels are selected (the "default channels" checkbox is selected) - no changes to the current behavior.
When inviting users for guest roles, the channel list should be empty, with the "default channels" checkbox unselected, if the user has not explicitly specified any channels.
If a user specifies one or more channels explicitly (e.g., #announce and #Denmark) when inviting for a guest role, then:

When the user switches to a non-guest role, the "default channels" checkbox should be selected, and the channel list should include the default channels.
When switching back to the guest role, the channel list should restore the channels that the user had previously specified (e.g., #announce and #Denmark).

Kindly check the visual changes mentioned in this comment.
Hence,

So, does it mean that the list should become empty everytime I switch the role dropdown to guest from any other role

The list should restore the channels specified for Guest roles, if any. So, if no channels are explicitly specified while inviting for a guest role the channel list would be empty while switching back to a guest role from a non-guest role.

and then when I change the role from guest to some other role, the list of streams should be what it was before the role was changed to guest?

When we switch from a guest role to a non-guest role the list follows current behavior, i.e. the default channels are selected (the "default channels" checkbox is selected).
@sahil839 I hope I was able to highlight the expected behavior and the changes made. Thank you.

I have updated the PR as mentioned in this comment.

Change made: Renamed the function update_guest_visible_users_count() to update_guest_visible_users_count_and_stream_ids().

As @sahil839 mentioned in this comment:

Regarding the behavior, do we also want to retain the streams selected for non-guest role while changing the role? Like I selected a couple of streams when role was selected as "Members". Then I change the role to "Guest" and then again change the role to "Members", default streams are selected again. Do we want to have the same couple of streams that I selected initially.

I don't think we want to retain the streams selected for non-guest roles when changing roles for invited users. This is based on the issue and the CZO thread, both of which suggest modifying the channel list for guest roles.
Please let me know if any adjustments are needed. Thank you.

Ok, code changes look good as per the current behavior.

Merged, thanks @saubhagya-patel!


Not working for mobile users

this package is really awesome in case of desktop users,but not working for mobile users. how can i fix that?

@karthikwebdev  Thank you for your compliment. I'll take your advice into account with next release, maybe on 26th this week.

@dilidili Great library. Do you have an update on this issue?

@karthikwebdev @Vijay-mRoads  version 0.3.0 supports mobile devices now! can try it on https://react-drawing-board-demo.dilidili.now.sh/ from mobile user agent.

Thanks, @dilidili. It's working for me. Can you please add the documentation on how to build it? I am getting compilation errors when I try to build it for development purposes. Do you want me to open a different issue for this?

Thanks, @dilidili. It's working for me. Can you please add the documentation on how to build it? I am getting compilation errors when I try to build it for development purposes. Do you want me to open a different issue for this?

npm install && npm run dev should work. If not, please open another issue and post an error log.


⚠ Samsung has degraded performance

In 0404ce9, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2750 ms

Resolved: Samsung performance has improved in 17a187f.


verrpc: add GetVersion endpoint

This PR adds a minimal verrpc subserver that is purely responsible for serving
version information about the running daemon. Though some of this information is
displayed via GetInfo, it is useful to have a single endpoint and service for this
purpose so that the chances of breaking changes are mitigated.
Third-party applications may not have the ability to be tightly synced with the
daemon, e.g. a mobile app connecting remotely via RPC. In order to support
proto version desynchronization, these apps typically come installed with several
historical versions of the proto files (especially when breaking changes have
been introduced). Apps can then determine the version of the daemon by trying
to decode various requests and looking for signals that indicate the version.
With verrpc, these headaches are largely eliminated. There may still be a need
to package multiple proto versions, but this makes it dead simple to map the
correct version. The intent (crosses fingers) is that this endpoint would never
undergo breaking changes so that app developers have a stable API they rely
on to determine versioning info.
In the future, we could consider separating the initialization of the verrpc
subserver to be active for wallet unlocking as well, but those protos don't
experience nearly as much churn as the others.

updated to compile build tags and go version into lnd and lncli, new output looks like this:
$ lncli version
{
    "lncli": {
        "commit": "v0.9.0-beta-551-ge89f4907f3a3d3ae034b400a44fd10c1567546c7-dirty",
        "commit_hash": "e89f4907f3a3d3ae034b400a44fd10c1567546c7",
        "version": "0.9.0-beta",
        "app_major": 0,
        "app_minor": 9,
        "app_patch": 0,
        "app_pre_release": "beta",
        "build_tags": [
            "routerrpc",
            "invoicesrpc"
        ],
        "go_version": "go1.14"
    },
    "lnd": {
        "commit": "v0.9.0-beta-551-ge89f4907f3a3d3ae034b400a44fd10c1567546c7-dirty",
        "commit_hash": "e89f4907f3a3d3ae034b400a44fd10c1567546c7",
        "version": "0.9.0-beta",
        "app_major": 0,
        "app_minor": 9,
        "app_patch": 0,
        "app_pre_release": "beta",
        "build_tags": [
            "routerrpc",
            "invoicesrpc"
        ],
        "go_version": "go1.14"
    }
}

Building on Windows is no longer working.
go build -v -tags="dev" -o lnd-debug -ldflags \-X github.com/ligh
tningnetwork/lnd/build.Commit=v0.9.0-beta-595-ga53a6f160e25dac4696685d5b5edfb799
194e2d7 -X github.com/lightningnetwork/lnd/build.CommitHash=a53a6f160e25dac46966
85d5b5edfb799194e2d7 -X github.com/lightningnetwork/lnd/build.GoVersion=go1.14.2
 -X github.com/lightningnetwork/lnd/build.RawTags=dev" github.com/lightningnetwo
rk/lnd/cmd/lnd
/usr/bin/sh: -c: line 0: unexpected EOF while looking for matching `"'
/usr/bin/sh: -c: line 1: syntax error: unexpected end of file
Makefile:107: recipe for target 'build' failed
make: *** [build] Error 258

Thanks for the report, @githorray! Can you please try if https://github.com/lightningnetwork/lnd/pull/4190 fixes the problem?

@guggero and I ran into the problem that go get -tags doesn't set the build tags compiler variable. So even though the subservers are enabled, they aren't reported. Maybe conditional compilation of boolean vars would have been better for that.
Worth mentioning in release notes @cfromknecht?

I don't think it's necessary. Our install docs are pretty clear that you should build with the makefile.


k8s version is not available sometimes in the dropdown while creating a cluster in a HA setup

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Bring up a HA cluster on master-head

Deploy a DO cluster.

k8s version dropdown is empty

On a refresh of kubernetes metadata, the k8s version were available in the dropdown during cluster creation

Expected Result:
k8s version should be available in the dropdown
Other details that may be helpful:
Note: Not always reproducible (hit this issue 1 out of 3 ha setups on master-head)
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head - commit id: a195fe7c6
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): rke do
Kubernetes version (use kubectl version):

1.17

@sowmyav27 How quickly are you going to start creating clusters? I wonder if it's a timing thing?

@sowmyav27  if you reproduced it next time, can you share the setup? I'd like to know if version never shows up until you refresh or it is just a timing thing.

@deniseschannon @StrongMonkey
Logs:
2020/03/27 00:25:44 [INFO] Refreshing driverMetadata in 1440 minutes
2020/03/27 00:25:44 [INFO] driverMetadata: refreshing data from upstream https://releases.rancher.com/kontainer-driver-metadata/dev-v2.4/data.json
2020/03/27 00:25:45 [INFO] kontainerdriver googlekubernetesengine listening on address <IP_ADDRESS>:42833
2020/03/27 00:25:45 [INFO] kontainerdriver googlekubernetesengine stopped
2020/03/27 00:25:45 [INFO] kontainerdriver amazonelasticcontainerservice listening on address <IP_ADDRESS>:44585
2020/03/27 00:25:45 [INFO] kontainerdriver amazonelasticcontainerservice stopped
2020/03/27 00:25:45 [INFO] kontainerdriver azurekubernetesservice listening on address <IP_ADDRESS>:42295
2020/03/27 00:25:45 [INFO] kontainerdriver azurekubernetesservice stopped
2020/03/27 00:25:45 [INFO] update kontainerdriver googlekubernetesengine
..

^^^ was initially when the rancher server was up
And when I manually refreshed
2020/03/27 00:36:13 [INFO] failed to run channelserver: signal: killed
2020/03/27 00:36:14 [INFO] driverMetadata: refreshing data from upstream https://releases.rancher.com/kontainer-driver-metadata/dev-v2.4/data.json
2020/03/27 00:37:21 [INFO] [mgmt-cluster-rbac-delete] Creating namespace c-8qb5n
2020/03/27 00:37:22 [INFO] [mgmt-cluster-rbac-delete] Creating Default project for cluster c-8qb5n
2020/03/27 00:37:22 [INFO] [mgmt-project-rbac-create] Creating namespace p-f58gh
2020/03/27 00:37:22 [INFO] [mgmt-cluster-rbac-delete] Creating System project for cluster c-8qb5n

@sowmyav27 I think this should be fixed but I couldn't reproduce it locally. If you see this again, keep the setup and let me know.

Verified on an upgrade from v2.2.11-rc2  to 2.4.0-rc14
On an upgrade, the k8s version in the dropdown were available after about a minute after upgrade.

On an upgrade to 2.4.x, the k8s version in the dropdown were available after about a minute after upgrade. This was observed in several upgrades.
As per @StrongMonkey 's confirmation, that this slight delay is acceptable, closing the issue


Bar chart not displaying correctly

ALL software version info

Software Version Info
hvplot=0.11.1
holoviews=1.20.0rc0 (same problem with 0.11.1, I upgraded to the rc to see if it fixes the problem, which it doesn't)
python= 3.10.10
polars=1.12.0
bokeh=3.6.0

Description of expected behavior and the observed behavior
Bars are to wide and overlap each other. In previous versions bars were small and each ratio had its one distinguisable bar.
Complete, minimal, self-contained example code that reproduces the issue
import holoviews as hv
hv.extension("bokeh")
import hvplot.polars
import polars as pl

dic = {"ratio": [0.82, 1.11, 1.18, 1.2, 1.21, 1.23, 1.24, 1.25, 1.28, 1.33, 1.34, 1.35, 1.36, 1.37, 1.38, 1.39, 1.4, 1.41, 1.42, 1.43, 1.44, 1.45],
       "count": [1, 2, 1, 3, 1, 1, 2, 7, 2, 4, 1, 2, 2, 3, 2, 1, 17, 35, 73, 173, 6606, 63550]}

pl_df = pl.DataFrame(dic)

print(pl_df)
pl_df.hvplot.bar(x="ratio", y="count", grid=True, height=600, rot=90, shared_axes=False, width=1345)

Screenshots or screencasts of the bug in action
Screenshot is from the chart generated with actual data. The code example is a simplified version with less data.

@nconsulting this is fixed in HoloViews and is going to be released in version 1.20.0.

In previous versions bars were small and each ratio had its one distinguisable bar.

Something else that changed compared to previous versions is that HoloViews since version 1.19.0 allows Bar plots to be plotted on continuous axes and not just categorical. Before that and adapted to your example, the ratio data was considered categorical, even if it's numeric data. If for some reason that's the behavior you need, you can always cast ratio to string before plotting.

@maximlt Thank you very much for the quick fix. I'll keep your message in mind, once I get my hands on the fixex HoloViews. Any idea when 1.20.0 will be available or an rc version with the fix?

@maximlt Thank you very much for the quick fix. I'll keep your message in mind, once I get my hands on the fixex HoloViews. Any idea when 1.20.0 will be available or an rc version with the fix?

1.20.0rc1 has been released with this fix.


Modify NER class

Our NER class currently is not that great https://github.com/wellcometrust/WellcomeML/blob/main/wellcomeml/ml/spacy_ner.py
In an internal project, @ivyleavedtoadflax created a class that can extract entities using either space or transformers. This is great. https://github.com/wellcometrust/grant_ner/blob/main/src/extract_entities.py
We would benefit from having a generic class with that functionality.

Additionally, @ivyleavedtoadflax has also worked on another NER model for deep reference parser which could also be nice to come here. The architecture there is a great baseline for NER stacked bilstm+crf.
I am also happy to contribute into this if it is of interest


ARVideoKit License

I recently added ARVideoKit to my application ScribScrab. I want to start this off by saying the kit is incredible and the documentation is very easy to use. I'm going to try and release an update of ScribScrab using the ARVideoKit on the App Store soon but I wanted to reach out about the licence and how I go about it? I wanted to make sure that I give ARVideoKit the proper credit. Also would it be possible to get ScribScrab on the "Apps using ARVideoKit" list?

Hi @Jlack6, please add the license in the settings section of your application under a section called Licenses where you'd list the open source code you've used throughout the app. If you don't have a settings section in the app, you may add the license in the Settings bundle (where it can be viewed from the System Settings); see instructions to do so here: https://gist.github.com/zetachang/4111314
Of course, please fork the repository, add ScribScrab to the README file and create a pull request!

@AFathi Hey, thanks for getting back to me so quickly. I don't have a settings section in the application but I have a link on the home screen that goes to a website I built for the app (The website is still a work in progress). I built this link on the site for acknowledgements https://scribscrabweb.firebaseapp.com/Acknowledgements.html, does that work? Let me know if I need to change anything. I'll also try to make sure I get that Settings bundle in soon. I'm kind of new to this so sorry for all the questions and thanks for the help.

Yes, that works!
Regards,
Ahmed Bekhit
On Fri, Sep 11, 2020 at 5:06 AM James Lack < James Lack ( James Lack<EMAIL_ADDRESS>) > wrote:

Reopened #116 ( https://github.com/AFathi/ARVideoKit/issues/116 ).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (
https://github.com/AFathi/ARVideoKit/issues/116#event-3753806356 ) , or unsubscribe
(
https://github.com/notifications/unsubscribe-auth/AA7KTR4MCVOWJDP4NHX5VGTSFFZYJANCNFSM4RD2OWAQ
).


IOS-2065: Converted SHEmailValidationTextField into Swift

Issue Link
https://spothero.atlassian.net/browse/IOS-2065
Description

Implemented a Bridging Header to allow usage of SHAutocorrectSuggestionView within the new Swift files.
Converted EmailTextFieldDelegate into Swift.
Converted EmailTextFieldDelegate into Swift.
Added missing error codes to SpotHeroEmailValidator.Error, matching the old values and reordering them.

I tried to keep this as close to a 1:1 migration as possible to make it easy to compare the Obj-C and Swift files.

Something around the delegate and delegateProxy nonsense is breaking. Will dig in further later.


Output the IP of a created server resource

Currently when creating a server resource with this provider it only outputs the ID of the server when it's created, but no information that would allow connecting to the created resource. I think it would be good to output the needed information after the creation so that one does not have to still have to open the UpCloud UI to get information like the IP of the created server. Outputting this info allows for automation where terraform apply could be run in a script that captures the IP and continues the configuration automatically. The example documentation here https://github.com/vtorhonen/terraform-provider-upcloud/blob/master/examples/README.md suggests this would happen. When testing the tool this part never showed up:
Outputs:

ip = <SOME IP ADDRESS>

Thanks. Fixed in #19.
You can also use terraform state show upcloud_server.test to print out all stored fields from the state file for that resource.

@vtorhonen Thanks for instructing the noob here.


[Question] How can I use SwiftDDP in a command line tool?

Hi.
I tried to use SwiftDDP in a command line tool and I had to modify two points.

SwiftWebSocket uses main_queue for eventQueue in default and it causes dead lock when it run as command line tool. I could avoid dead lock to create another DispatchQueue.
SwiftDDP uses current OperationQueue for callback and it causes dead lock when it run as command line tool because current one is "Main Queue". I could avoid dead lock to create another OperationQueue.

but I feel that I might modify redundantly since the necessity of the above two modifications are just one reason.
I think that you can make a command line tool without any modifications of SwiftDDP if you make main thread free. Am I right? And how can I do it?
Thanks.

I found that what I needed was dispatchMain.


Ecto.Adapters.MyXQL, isn't currently supported

Hi, I found Honeydew while looking for a solution for background processing  in a Phoenix app with use of Ecto. I followed the example and ran into the following issue:
 your repo's ecto adapter, Ecto.Adapters.MyXQL, isn't currently supported, but it's probably not hard to implement, open an issue and we'll chat!

I had a look at the PG.Adapter, seems possible to implement it for MySQL. Any pointers on what I should look out for, did anybody already try and fail?

Hey there @basbz!
Nobody (that I know of) has written a MyXQL module for Honeydew yet, but it should be fairly straight forward.
My only pointer would be to make sure that the "reserve" query is as efficient as possible while retaining atomic semantics. In the postgres adaptor, it uses SKIP LOCKED to prevent contention between multiple reserving processes.
Definitely drop me a line if you run into any snags, I'm happy to install mysql and lend a hand. :)

Hi, thanks for getting back to me 👍
I'll take a look and hopefully get back with a PR.
closing the issue for now...
Best!


Add tril, triu and find to cupyx.scipy.sparse

This PR adds tril, triu and find to cupyx.scipy.sparse.

pfnCI, test this please.

Jenkins CI test (for commit f9e8e73ccfcb462770a1fd1642de544a0a3a3c2c, target branch master) succeeded!

pfnCI, test this please.

LGTM! Waiting for CI pass.

Jenkins CI test (for commit b8e34fd71bc1015ab223bfcecd878f36fe29f05b, target branch master) succeeded!


Error from doFetch in Chrome console

Using the  selectivity-rails (0.2.0) gem.
I notice the following error  from the doFetch function, selecting any entry.
selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:2528 Uncaught TypeError: fetch(...).then(...).then(...).catch is not a function
at doFetch (selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:2528)
at invokeFunc (selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:232)
at trailingEdge (selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:279)
at timerExpired (selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:267)
doFetch @ selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:2528
invokeFunc @ selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:232
trailingEdge @ selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:279
timerExpired @ selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:267
setTimeout (async)
leadingEdge @ selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:240
debounced @ selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:307
options.query @ selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:2550
options.query @ selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:2586
search @ selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:1066
(anonymous) @ selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:4871
search @ selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:3913
search @ selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:4442
(anonymous) @ selectivity.self-3115294f8e09eb7ec50b269e15cd6223f48262a40140de9e2b9a42ccb52047a2.js?body=1:4382

Sorry for the late reply. Are you using Selectivity in combination with jQuery? And if so, which version of jQuery? The reason I'm asking is because the AJAX functionality in Selectivity depends on the fetch() function which comes standard in modern browsers. For compatibility with older browsers (and consistency with other code using $.ajax()), the jQuery build of Selectivity comes with an implementation of fetch() that uses $.ajax() under the hood. However, this requires jQuery 3 or higher to work correctly because older versions of jQuery return a Promise-like object from $.ajax() that's incompatible with the Promise specification.
This is documented in the README in a small note for the "jquery/ajax" plugin, but if this is indeed the problem, I might need to document this more prominently.

Switched to select2 months ago. Thank you anyway.


[FEATURE] Add Support Pagefind search engines

Describe the feature you want 描述你的功能需求
Doit current uses algolia and fuse as search engines. With fuse if the same keyword appears multiple times in the same post, that post will be listed multiple times in the search results, and the index file for fuse is relatively large. I tried Pagefind, and this issue does not occur. However, I am not familiar with front-end development, so I don't know how to add Pagefind to the search engines .
Currently, I can just create new HTML files in the static directory to use Pagefind, but there are still some problems. For example, the Doit theme places the rendered HTML directly in the public root directory, unlike Hugo's native approach of placing it in the public/post directory. As a result, Pagefind can only index all HTML files in the public directory, including directories like categories, posts, tags, and series. This leads to indexing of search keywords if they are included in categories, posts, tags, or series.
fuse search result

Pagefind  search result

Useful reference 有价值的参考
https://pagefind.app/
https://zenn.dev/k1350/articles/42c13020038d4c

I've looked into Pagefind before, pretty interesting. If possible, I'll give it a try after I finish my bachelor thesis.

I've looked into Pagefind before, pretty interesting. If possible, I'll give it a try after I finish my bachelor thesis.

Great, looking forward to your masterpiece.

Looks pretty good.

Copy themes/DoIt/layouts/posts/single.html save as layouts/posts/single.html .
And modify it like  <article class="......." data-pagefind-body>
This will help pagefind to limite only posts page can be indexed.
https://pagefind.app/docs/indexing/

You can control what content on your site is indexed via tags on your HTML elements. data-pagefind-*

@Sped0n 太巧了，我一直关注，这次上来查看，竟然发现9分钟前实现了，美滋滋啊

@Sped0n 太巧了，我一直关注，这次上来查看，竟然发现9分钟前实现了，美滋滋啊

@coloraven 让老哥久等了，这段时间私事比较多，安顿下来才有空补完


:sparkles: Compile time flows and CLI simulation update

Description
🚧 Work in progress 🚧
This PR introduces new CMake flags to build individual flows of the fiction CLI. Furthermore, it exposes SiDB simulation capabilities via the CLI.
Checklist:

[x] The pull request only contains commits that are related to it.
[ ] I have added appropriate tests and documentation.
[ ] I have made sure that all CI jobs on GitHub pass.
[ ] The pull request introduces no new warnings and follows the project's style guidelines.

@marcelwa That's super cool! I will address your points as soon as possible.

@Drewniok In this PR, I've started to expose SiDB simulation via the CLI. You can now use read --sqd (or read -s for short) SiQAD files and print them via print -c. Via commands quicksim and quickexact, you can generate a CDS, which you can print via print -c as well.
This is pretty basic as far as SiDB simulation on the command line can go, and there are several aspects and details I would like to discuss with you. Here are some things to ponder for you:
* What other SiDB algorithms should we expose?

* Right now, only the ground state (I think) is saved, how do we deal with the others?

* The QuickExact implementation doesn't actually store its global potential variable to the further simulation parameters. I think it should.

* QuickExact seems to store the base number additionally, even though it is included in the sim result object via the physical parameters.

* Does QuickSim actually respect a given base number? No, right? In that case, the respective option needs to be removed again from the CLI.

Furthermore TODO:
* Add documentation to the CLI chapter in the RTD pages.

Would be cool if you could play around with it such that we can have a discussion soon.

@marcelwa, I have two questions, comments:

Can you explain again or rephrase you question? Are you referring to QuickExact?
The base number stored in the additional parameters is the base number actually used for the simulation. This can be different from the base number set by the physical parameters if automatic base number detection is enabled. But I see the confusion! I will change the naming.

@Drewniok In this PR, I've started to expose SiDB simulation via the CLI. You can now use read --sqd (or read -s for short) SiQAD files and print them via print -c. Via commands quicksim and quickexact, you can generate a CDS, which you can print via print -c as well.
This is pretty basic as far as SiDB simulation on the command line can go, and there are several aspects and details I would like to discuss with you. Here are some things to ponder for you:
* What other SiDB algorithms should we expose?

* Right now, only the ground state (I think) is saved, how do we deal with the others?

* The QuickExact implementation doesn't actually store its global potential variable to the further simulation parameters. I think it should.

* QuickExact seems to store the base number additionally, even though it is included in the sim result object via the physical parameters.

* Does QuickSim actually respect a given base number? No, right? In that case, the respective option needs to be removed again from the CLI.

Furthermore TODO:
* Add documentation to the CLI chapter in the RTD pages.

Would be cool if you could play around with it such that we can have a discussion soon.

@marcelwa, I have two questions, comments:

Are you referring to the CLI?
The base number stored in the additional parameters is the base number actually used for the simulation. This can be different from the base number set by the physical parameters if automatic base number detection is enabled. But I see the confusion! I will change the naming.

My points 1 and 2 referred to the CLI, yes. The others didn't (5 kinda touched upon it).
Thanks for your clarification regarding the base number storage.

@marcelwa I think all the above TODOs are done. As discussed, it would be convenient to have the critical temperature and part of the operational domain in the CLI. I can support you there!

@marcelwa I think all the above TODOs are done. As discussed, it would be convenient to have the critical temperature and part of the operational domain in the CLI. I can support you there!

Perfect, many thanks! 🙏 I'll come up with something and might ask for your feedback once it's done.

@Drewniok this PR is now feature-complete. If you find some time, I would appreciate your input. It's not urgent.

The new CLI commands quickexact, quicksim, temp, and opdom are available.
The CLI commands read and print have been updated to support read --sqd and print -c for CDS.
Furthermore, I made some small changes to critical_temperature and its tests in order to streamline the code.


Non Azure Servers Security

Security Center can monitor the security posture of your non-Azure computers but you need to first onboard these resources.
Does this cover n/w receommendations??
Does non azure servers can have JIT enabled??
Could you please provide what all features can be enabled for non azure servers?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fed761ca-5bee-7f31-2e57-9a29bba2f35e
Version Independent ID: f265cac7-227e-134e-4b4d-93bb82754178
Content: Standard tier's enhanced security - Azure Security Center
Content Source: articles/security-center/security-center-onboarding.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@priyankareddy20 Thank you for your query. We will investigate and update the thread.

@priyankareddy20  Azure Security center does not show any network related recommendations for Non-Azure Servers. The functionality with respect to Non azure servers are limited as of now.
JIT is currently only for VMs deployed through Azure Resource Manager. So these will not available for non azure servers as well.
You can have a look at full list for non azure supported feature here.   Let me know if you have any questions.

@priyankareddy20 Let us know if you have any further questions, closing this thread for now, will be glad to assist if you need any help.


Cohorts total streamed calculation

Comparing total withdrawn data from buidlguidl website with streamogator I found some Cohorts with different data.
Here are the details of the difference:

Cohort
Bg hackers
BG streamed
streamo hackers
streamo streamed
ETH difference
Builders difference

Main Hacker House
14
60.82
15
38.44
22.38
1

Play Full
13
13.58
13
8.21
5.37
0

Infrastructure
4
7.74
4
5.74
2
0

BG Outreach
3
14
3
10.63
3.37
0

Not Just Notfellows
7
6.98
7
5.95
1.03
0

Security & Optimizooors
2
2.5
2
1.5
1
0

Autonomous Worlds
7
9.49
7
5.99
3.5
0

ZK & Cryptography
15
23.65
14
18.75
4.9
1

Digging a bit into the withdrawal data, found the correct value was streamogator's.
I think the reason of the difference is there are duplicated builders (builders added a couple of times onchain) in these cohorts, and we are counting the withdrawn ETH twice for those builders.
Example:

ZK Cohort duplicated 4 builders, adding them twice in 2 different tx:

https://etherscan.io/tx/0xe19edc444beb51ed53e12807bb42228ac7c710240290ec21d9b3209fada4b944#eventlog
https://etherscan.io/tx/0x505e5808d2b01da8af2df67414346207b6b4b1a0fbf1a7ef0b8cda094f3e2441#eventlog

Security & Optimizooors Cohort duplicated 1 builder in these tx:

https://etherscan.io/tx/0x6109a36689227fa7d2aa35d490eeaf8d8c63535a368ec2c8c7f6f05fb3103123#eventlog
https://etherscan.io/tx/0xc4637a849132eff7900008f26c8e3e17c8339cbe4bd8299edd7e3543fc6fe724#eventlog

There is a couple of Cohorts with 1 builder difference, but haven't figured out yet the reason, but in that case the correct data is in BG website.

Just ran a script to remove the duplicates from the BG indexer. It's looking good now!
Could you take a look? Let's see if this doesn't happen again with new withdraws... if not, something might be wrong with the indexer script.

It's looking great! TYSM!!
Closing 👌


VC build: handle assertions as the dmc build

The current VC builds of dmd removes all assert in a release build and just crash instead of reporting assertions.
This PR enables asserts and disables interactive crash reports.

Auto-merge toggled on


docs: install provider steps

Add missing provider install documentation
Fixes #160

I still need to work on configuring it with the DeploymentRuntimeConfig. I'll reopen it when it'll be ready

Hi Smana,
Do you mind if I push a new commit to help you out on this?
I get a set-up up and running with a DeploymentRuntimeConfig, I can contribute.


Add http method and request data parameters to HTTPRequest::request

Implements feature proposed in #4028.

scene/main/http_request.{h,cpp}: add method and request_data parameters to HTTPRequest::request

This is my first PR in Godot. Hope it helps.

Looks good to me besides the indentation issue.

Fixed identation.

Could you squash the two commits together for clarity?
git rebase -i HEAD~2
// change `pick` for `fixup` in front of the indentation-fix commit
// save and leave the editor, it will rebase
git status
git show
git log // check it's all right
git push --force origin http-request-methods

Sorry, forgot about that! There, done.

Thanks.


adding input widget for each color format

adding input widget for each color format

Known issue: Inaccuracy due to color conversion to the HSV format and then back to the desired format.


What about providing some detailed examples to display how to run real jobs on the remote clusters?

How can we improve the documentation?
Hi Andrew,
Recently, I installed quacc and covalent on my own wsl2(Ubuntu), and I have used quacc to run some jobs locally. And when I tried to use quacc to run the VASP job on the "XSEDE-expanse", it failed, although I have installed covalent-hpc-plugin on my wsl and created a new conda enviroment on expanse where I installed covalent and psij-python. If there is a detailed example to introduce how to submit a vasp job on the remote cluster from the local terminal might be helpful.

Hi @RedStar-Iron! Thanks for your comment! I appreciate your report.
I agree that deploying remotely is the hardest part by far. I'm sure you have seen this page already, which defined a sample HPC executor instance.
I imagine if you were following that, you actually were setting things up correctly. May I ask which version of quacc and Covalent are you using? There are some gnarly bugs with Covalent < 0.227.0rc0. The main branch of quacc has just been made compatible with Covalent >= 0.227.0rc0 (I'll mint a new release tonight).
But regardless, I agree that a complete example be fruitful. I'll add that shortly and make sure it works with the most recent versions of everything.

Hi @Andrew-S-Rosen! Thanks for your reply!
By far, I used the quacc=0.3.1 and Covalent=0.226. When I tried to do a relax_job with VASP or even emt, I got an error  "Invalid OpenSSH certificate", but I already generate the id_rsa&id_rsa.pub and can ssh to the expanse cluster directly without typing password. And if I just did some easy calculation in the workflow, such as "2+2", it went smoothly.

@RedStar-Iron: Thanks for the reply. That sounds like it could be related to some of the prior Covalent bugs. I would try updating quacc (which will also update Covalent) and see if that fixes it. If not, it would be particularly helpful if you could share a full example (e.g. the EMT one) so I can troubleshoot. But my gut instinct is that you are following the instructions correctly and it's a bug related to setting inheritance in Covalent.

Hi @Andrew-S-Rosen,
The code below is what I used to run emt job on expanse. And I have a question about how quacc and covalent started the vasp job on the remote cluster. I didn't supply the absolute path of vasp on the expanse to the quacc and covalent directly, did it use the ase env variable on the expanse ASE_VASP_COMMAND & VASP_PP_PATH ?
And I set the ASE_VASP_COMMAND="mpirun -np 32 path/to/vasp" on expanse, while in this config file, vasp_parallel_cmd = (f"srun -N {n_nodes} --ntasks-per-node={n_cores_per_node} --cpu_bind=cores"), did it just extract the path of vasp from ASE_VASP_COMMAND?
Also, I looked the code of vasp.py, it also called the Vasp class in ASE, so, did quacc call the ASE on expanse to run the vasp? I feel a bit confused about these questions.
Maybe, if there is a flowchart to depict the principle of this workflow might be helpful to understand.
import covalent as ct
from ase.build import bulk, molecule
from quacc import flow
from quacc import SETTINGS
from quacc.recipes.emt.core import relax_job

SETTINGS.VASP_USE_CUSTODIAN = False
n_nodes = 1  # Number of nodes to reserve for each calculation
n_cores_per_node = 32  # Number of CPU cores per node
vasp_parallel_cmd = (
    f"srun -N {n_nodes} --ntasks-per-node={n_cores_per_node} --cpu_bind=cores"
)

executor = ct.executor.HPCExecutor(
    # SSH credentials
    username="gsliu2021",
    address="login01.expanse.sdsc.edu",
    ssh_key_file="~/.ssh/id_rsa",
    cert_file="~/.ssh/id_rsa.pub",
    # PSI/J parameters
    instance="slurm",
    resource_spec_kwargs={
        "node_count": n_nodes,
        "processes_per_node": n_cores_per_node,
    },

    job_attributes_kwargs={
        "duration": 10,  # minutes
        "project_name": "uop149",
        "queue_name": "debug",
        # "custom_attributes": {"slurm.constraint": "cpu", "slurm.qos": "debug"},
    },
    environment={"QUACC_VASP_PARALLEL_CMD": vasp_parallel_cmd},
    # Pre-/post-launch commands
    pre_launch_cmds=["module load purge","module load slurm"],
    # Remote Python env parameters
    remote_conda_env="finetuna",

    # Covalent parameters
    remote_workdir="/expanse/projects/qstore/uop149/gsliu2021/quacc",
    create_unique_workdir=True,
    log_stdout="/expanse/projects/qstore/uop149/gsliu2021/quacc",
    log_stderr="/expanse/projects/qstore/uop149/gsliu2021/quacc",
)

@flow(executor=executor)
def workflow(atoms1, atoms2):
    # Define two independent relaxation jobs
    result1 = relax_job(atoms1)
    result2 = relax_job(atoms2)

    return {"result1": result1, "result2": result2}

# Define two Atoms objects
atoms1 = bulk("Cu")
atoms2 = molecule("N2")

# Dispatch the workflow to the Covalent server
dispatch_id = ct.dispatch(workflow)(atoms1, atoms2)

# Fetch the results from the server
result = ct.get_result(dispatch_id, wait=True)
print(result)

The code below is what I used to run emt job on expanse.

Thanks for the detailed report. I'll take a look on Friday (currently wrapping up vacation but had a few minutes to check GitHub!).

and I have a question about how quacc and covalent started the vasp job on the remote cluster. I didn't supply the absolute path of vasp on the expanse to the quacc and covalent directly, did it use the ase env variable on the expanse ASE_VASP_COMMAND & VASP_PP_PATH

This is a good question. By default, quacc executes VASP by calling ASE but instead of having ASE run VASP directly, ASE runs Custodian for on-the-fly error handling. That is the section below:
https://github.com/Quantum-Accelerators/quacc/blob/d30c8f7e754831cad2632a32ee896aeb423c05f5/src/quacc/calculators/vasp.py#L251-L254
However, in your scenario, it looks like you are trying to disable the use of Custodian, in which case quacc will execute VASP via ASE as you are used to.
In the former case, that's where the VASP_PARALLEL_CMD and related settings come into play:
https://github.com/Quantum-Accelerators/quacc/blob/d30c8f7e754831cad2632a32ee896aeb423c05f5/src/quacc/calculators/custodian/vasp.py#L80-L87
In the latter case, quacc is calling ASE as usual and therefore ASE_VASP_COMMAND mut be set:
https://github.com/Quantum-Accelerators/quacc/blob/d30c8f7e754831cad2632a32ee896aeb423c05f5/src/quacc/calculators/vasp.py#L256-L260
This could likely be made clear in the VASP setup part of the instructions. Right now, it is written under the assumption that the user is going to run with Custodian, which is the default.
Anyway, to answer your question directly now: in your scenario, yes, it likely used your ASE environment variables (but ignored QUACC_VASP_PARALLEL_CMD altogether).

Thanks for your detailed reply! I am much clearer about the process of quacc now, I will submit a slurm job and look into the code as well which can help me to further understand how the workflow works. Thanks again for your help!

@RedStar-Iron: Great! Keep me posted.
And as a note to myself, I am proposing the following additions to the docs:

A section in the docs doing a top-to-bottom worked example for deploying calculations for several types of recipes, namely: EMT, ORCA, and VASP as prototypical examples. This should, ideally, be mostly copy-and-pasteable. It should also highlight how to approach this process gradually, e.g. first submitting a Python script as a slurm job, then using the workflow engine.

@RedStar-Iron: I updated the documentation per your request (see #1025 and the updated "Using a Workflow Engine" section of the live documentation).
I was able to confirm that the EMT workflow shared in the docs works as expected. However, I have confirmed that there is a bug in PSI/J, which is a dependency that covalent-hpc-plugin (i.e. HPCExecutor) relies on, and this causes an issue for VASP. See https://github.com/ExaWorks/psij-python/issues/423.


webui: group rule hits by function

Add an option to group rule hits by the function they are found in.

see #377 for reference