The some aspects of the send/receive model are unreliable

I've been having some fun playing with this crate, but as I have added more nodes to my network, things have become unstable. There are assumptions made about the order in which messages will come out of the controller that don't really hold. For instance, functions like switch_binary_get() on Node sends a get command over the air, then reads whatever the next message it gets from the driver, assuming that it will be the report back from the switch. This isn't necessarily the case, as the next message may have been sent from another node, or be from the same node, but of a different type (most commonly in my case, a METER report).
In general, I don't think it will be safe to assume anything about the order in which messages come out of the driver, let alone their origin. Without making the Controller much more sophisticated, I'm not sure what the best way is around this. Unless there is some sort of Controller message buffer/queue/whatever that it can pick through to find the correct message to parse and return (for instance from a binary_switch_get() call), it probably isn't possible to reliably return anything. Let me know if I misunderstand what's happening under the hood.
I can think of a few alternatives:

Don't return anything meaningful from get()-like stuff. Just return whether the message parsed and sent okay. Leave it up to the client to use a handle_messages() function or read messages from the controller in a loop to capture and respond to the corresponding report.
Add some internal message storage to the Controller to read/parse and store incoming messages that aren't valid responses to the last *_get() until it gets one, then return the result. This might be limiting for some use cases...

I think the first is the easiest thing to do, but it would break existing code :(. But! going forward it would allow people to write their own fancy message grabber/dispatcher code, and not affect the overall complexity of the crate.
I should also mention that I have issues initializing a Controller when there is a switch pinging me with METER messages. I think this is causing the initialization code that expects an ACK to get confused. If I re-try the initialization a few times in quick succession, everything works okay. I think this is happening because my USB controller has a few METER messages sitting in a buffer that are the first things to come out. Somewhat related to the above; the code assumes after talking to the device that the first thing out will be an ACK.
Sorry for the long issue. Let me know if you want me to take a crack at any of this.

Hi @youngmit,
I'm with you and think for now we should go with option 1 and option 2 can be added later if needed.
When I wrote this crate the ZWave Specifcation have been not public available. With this have changed in the last year, a lot more things are clearified. The ACK is more or less written as in die Specification defined here: https://www.silabs.com/documents/login/user-guides/INS12350-Serial-API-Host-Appl.-Prg.-Guide.pdf
The API needs to change completly. So i will branch the reporisotry and start more or less from scratch in the master and only copy code over which can be reused easily.

Thanks for the link. I look forward to seeing what you come up with. In the meantime, I will start doing some experimentation of my own, get comfortable with z wave stuff, then hopefully I will be able to contribute

Hello from 2024.
I’m interested in making a ZWave / Rust tool to steer home appliances - and starting by looking at this code.

@akauppi Feel free to look into to code. I don't have to time to do a rewrite on my own right now. But please feel free to submit PRs and push this library forward.


Unable to configure Macbook Pro Trackpad

Hello,
I'm trying to configure my 2009 Macbook Pro trackpad to work with Sway under Arch Linux, using this issue as guidance.
With swaymsg -t get_inputs, I see:
 "identifier": "1452:566:Apple_Inc._Apple_Internal_Keyboard_\/_Trac"

For comparison, with sudo libinput-list-devices, I see:
Device:           Apple Inc. Apple Internal Keyboard / Trackpad

In my sway config, I have:
input "1452:566:Apple_Inc._Apple_Internal_Keyboard_/_Trac" {
    tap enabled
    natural_scroll enabled
}

but it doesn't seem to be working -- scroll direction is still not "natural," tap-to-click doesn't work.
Thinking that perhaps the truncated name were a problem, I have tried all of the following with no luck (killing sway and restarting in between each):
 "identifier": "1452:566:Apple_Inc._Apple_Internal_Keyboard_/_Trac" {
 "identifier": "1452:566:Apple_Inc._Apple_Internal_Keyboard_\/_Trac" {
 "identifier": 1452:566:Apple_Inc._Apple_Internal_Keyboard_/_Trac {
 "identifier": 1452:566:Apple_Inc._Apple_Internal_Keyboard_\/_Trac {
 "identifier": "1452:566:Apple_Inc._Apple_Internal_Keyboard_\/_Trackpad" {
 "identifier": "1452:566:Apple_Inc._Apple_Internal_Keyboard_/_Trackpad" {
 "identifier": 1452:566:Apple_Inc._Apple_Internal_Keyboard_/_Trackpad {
 "identifier": 1452:566:Apple_Inc._Apple_Internal_Keyboard_\/_Trackpad {

What am I doing wrong?

Can you produce a debug log?

Wow, that was fast.
Is there a better way than sway --verbose --debug &> sway_debug.log?
Looks like the relevant portions:
01/25/17 13:53:03 - handling config command 'input 1452:566:Apple_Inc._Apple_Internal_Keyboard_\/_Trackpad {'
01/25/17 13:53:03 - find_handler(input) 0
01/25/17 13:53:03 - new_input_config(1452:566:Apple_Inc._Apple_Internal_Keyboard_\/_Trackpad)
01/25/17 13:53:03 - entering input block: 1452:566:Apple_Inc._Apple_Internal_Keyboard_\/_Trackpad
01/25/17 13:53:03 - handling config command 'tap enabled'
01/25/17 13:53:03 - find_handler(tap) 1
01/25/17 13:53:03 - looking at input handlers
01/25/17 13:53:03 - tap for device: 1452:566:Apple_Inc._Apple_Internal_Keyboard_\/_Trackpad
01/25/17 13:53:03 - new_input_config(1452:566:Apple_Inc._Apple_Internal_Keyboard_\/_Trackpad)
01/25/17 13:53:03 - apply-tap for device: 1452:566:Apple_Inc._Apple_Internal_Keyboard_\/_Trackpad
01/25/17 13:53:03 - handling config command 'natural_scroll enabled'
01/25/17 13:53:03 - find_handler(natural_scroll) 1
01/25/17 13:53:03 - looking at input handlers
01/25/17 13:53:03 - new_input_config(1452:566:Apple_Inc._Apple_Internal_Keyboard_\/_Trackpad)
01/25/17 13:53:03 - handling config command '}'
01/25/17 13:53:03 - End of input block
01/25/17 13:53:03 - handling config command 'bar {'

01/25/17 13:53:03 - Found input device (0:1:Power_Button)
01/25/17 13:53:03 - rewritten name Power_Button
01/25/17 13:53:03 - [wlc] Set new bsurface to output (1)
01/25/17 13:53:03 - [wlc] Added output (1)
01/25/17 13:53:03 - [wlc] become active
01/25/17 13:53:03 - rewritten name Power_Button
01/25/17 13:53:03 - Found input device (0:1:Power_Button)
01/25/17 13:53:03 - rewritten name Power_Button
01/25/17 13:53:03 - Found input device (0:1:Power_Button)
01/25/17 13:53:03 - rewritten name Sleep_Button
01/25/17 13:53:03 - Found input device (0:3:Sleep_Button)
01/25/17 13:53:03 - rewritten name Apple_Computer,_Inc._IR_Receiver
01/25/17 13:53:03 - Found input device (1452:33346:Apple_Computer,_Inc._IR_Re)
01/25/17 13:53:03 - rewritten name Apple_Inc._Apple_Internal_Keyboard_/_Trackpad
01/25/17 13:53:03 - Found input device (1452:566:Apple_Inc._Apple_Internal_Keyboard_/_Trac)
01/25/17 13:53:03 - rewritten name bcm5974
01/25/17 13:53:03 - Found input device (1452:566:bcm)
01/25/17 13:53:03 - rewritten name Built-in_iSight
01/25/17 13:53:03 - new_input_config(1452:566:Apple_Inc._Apple_Internal_Keyboard_\/_Trackpad)
01/25/17 13:53:03 - handling config command '}'
01/25/17 13:53:03 - End of input block

^^ As you can see, the above was with the config including the escape character \, and the full word Trackpad, but it behaves identically without the escape (I understand I am not supposed to include the \), and identically using Trac instead of Trackpad (as per swaymsg output).

Use  "identifier": "1452:566:Apple_Inc._Apple_Internal_Keyboard_/_Trac" { and provide a full debug log, please.

Sounds good. Sorry, having a hard time figuring out how to pipe output to the clipboard (in order to paste to browser). Coming from OSX would be cat myfile.log | pbcopy. GitHub won't let me upload the file either (We don’t support that file type. with both .log and .txt extension.)
Also, as per above is sway --verbose --debug &> out.log basically the format you were expecting?
01/25/17 18:12:14 - [wlc] logind: session control granted
01/25/17 18:12:14 - [wlc] Running on vt 1 (fd 0)
01/25/17 18:12:14 - [wlc] Failed to open X11 display
01/25/17 18:12:14 - Starting sway version  (2016-10-25, branch "")

01/25/17 18:12:14 - Set XDG_CONFIG_HOME to /home/n8henrie/.config
01/25/17 18:12:14 - Loading config from /home/n8henrie/.config/sway/config
01/25/17 18:12:14 - handling config command 'set $mod Mod4'
01/25/17 18:12:14 - find_handler(set) 0
01/25/17 18:12:14 - handling config command 'set $term urxvt'
01/25/17 18:12:14 - find_handler(set) 0
01/25/17 18:12:14 - handling config command 'set $menu dmenu_run'
01/25/17 18:12:14 - find_handler(set) 0
01/25/17 18:12:14 - handling config command 'output * bg /usr/share/sway/Sway_Wallpaper_Blue_1920x1080.png fill'
01/25/17 18:12:14 - find_handler(output) 0
01/25/17 18:12:14 - Config stored for output * (enabled:-1) (-1 x -1 @ -1, -1 scale 1) (bg /usr/share/sway/Sway_Wallpaper_Blue_1920x1080.png fill)
01/25/17 18:12:14 - handling config command 'bindsym $mod+Return exec $term'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Return to command exec urxvt
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+q kill'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+q to command kill
01/25/17 18:12:14 - handling config command 'bindsym $mod+d exec $menu'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+d to command exec dmenu_run
01/25/17 18:12:14 - handling config command 'floating_modifier $mod normal'
01/25/17 18:12:14 - find_handler(floating_modifier) 0
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+c reload'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+c to command reload
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+e exit'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+e to command exit
01/25/17 18:12:14 - handling config command 'bindsym $mod+h focus left'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+h to command focus left
01/25/17 18:12:14 - handling config command 'bindsym $mod+j focus down'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+j to command focus down
01/25/17 18:12:14 - handling config command 'bindsym $mod+k focus up'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+k to command focus up
01/25/17 18:12:14 - handling config command 'bindsym $mod+l focus right'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+l to command focus right
01/25/17 18:12:14 - handling config command 'bindsym $mod+Left focus left'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Left to command focus left
01/25/17 18:12:14 - handling config command 'bindsym $mod+Down focus down'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Down to command focus down
01/25/17 18:12:14 - handling config command 'bindsym $mod+Up focus up'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Up to command focus up
01/25/17 18:12:14 - handling config command 'bindsym $mod+Right focus right'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Right to command focus right
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+h move left'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+h to command move left
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+j move down'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+j to command move down
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+k move up'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+k to command move up
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+l move right'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+l to command move right
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+Left move left'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+Left to command move left
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+Down move down'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+Down to command move down
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+Up move up'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+Up to command move up
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+Right move right'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+Right to command move right
01/25/17 18:12:14 - handling config command 'bindsym $mod+1 workspace 1'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+1 to command workspace 1
01/25/17 18:12:14 - handling config command 'bindsym $mod+2 workspace 2'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+2 to command workspace 2
01/25/17 18:12:14 - handling config command 'bindsym $mod+3 workspace 3'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+3 to command workspace 3
01/25/17 18:12:14 - handling config command 'bindsym $mod+4 workspace 4'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+4 to command workspace 4
01/25/17 18:12:14 - handling config command 'bindsym $mod+5 workspace 5'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+5 to command workspace 5
01/25/17 18:12:14 - handling config command 'bindsym $mod+6 workspace 6'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+6 to command workspace 6
01/25/17 18:12:14 - handling config command 'bindsym $mod+7 workspace 7'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+7 to command workspace 7
01/25/17 18:12:14 - handling config command 'bindsym $mod+8 workspace 8'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+8 to command workspace 8
01/25/17 18:12:14 - handling config command 'bindsym $mod+9 workspace 9'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+9 to command workspace 9
01/25/17 18:12:14 - handling config command 'bindsym $mod+0 workspace 10'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+0 to command workspace 10
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+1 move container to workspace 1'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+1 to command move container to workspace 1
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+2 move container to workspace 2'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+2 to command move container to workspace 2
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+3 move container to workspace 3'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+3 to command move container to workspace 3
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+4 move container to workspace 4'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+4 to command move container to workspace 4
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+5 move container to workspace 5'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+5 to command move container to workspace 5
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+6 move container to workspace 6'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+6 to command move container to workspace 6
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+7 move container to workspace 7'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+7 to command move container to workspace 7
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+8 move container to workspace 8'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+8 to command move container to workspace 8
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+9 move container to workspace 9'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+9 to command move container to workspace 9
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+0 move container to workspace 10'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+0 to command move container to workspace 10
01/25/17 18:12:14 - handling config command 'bindsym $mod+b splith'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+b to command splith
01/25/17 18:12:14 - handling config command 'bindsym $mod+v splitv'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+v to command splitv
01/25/17 18:12:14 - handling config command 'bindsym $mod+s layout stacking'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+s to command layout stacking
01/25/17 18:12:14 - handling config command 'bindsym $mod+w layout tabbed'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+w to command layout tabbed
01/25/17 18:12:14 - handling config command 'bindsym $mod+e layout toggle split'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+e to command layout toggle split
01/25/17 18:12:14 - handling config command 'bindsym $mod+f fullscreen'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+f to command fullscreen
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+space floating toggle'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+Shift+space to command floating toggle
01/25/17 18:12:14 - handling config command 'bindsym $mod+space focus mode_toggle'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+space to command focus mode_toggle
01/25/17 18:12:14 - handling config command 'bindsym $mod+a focus parent'
01/25/17 18:12:14 - find_handler(bindsym) 0
01/25/17 18:12:14 - bindsym - Bound Mod4+a to command focus parent
01/25/17 18:12:14 - handling config command 'bindsym $mod+Shift+minus move scratchpad'
01/25/17 18:12:14 - find_handler(bindsym) 0
...skipping...
: 800|x:   0|y:   0|g:  0|vis:t|children: 1|name:root
|focus:X     |(0xba36c0)(p:0x63a4c0)(f:0xbc56b0)(h: 1)Type:op  |layout:-    |w:1280|h: 800|x:   0|y:   0|g: -1|vis:t|children: 1|name:LVDS-1
|-focus:W    |(0xbc56b0)(p:0xba36c0)(f:0x1052ad0)(h:18446744073709551615)Type:ws  |layout:Horiz|w:1280|h: 781|x:   0|y:  19|g: -1|vis:t|children: 2|name:1
|--focus:X   |(0x103cd30)(p:0xbc56b0)(f:(nil)   )(h: 5)Type:view|layout:-    |w: 640|h: 781|x:   0|y:  19|g: -1|vis:t|children: 0|name:Unable to config
|--focus:X   |(0x102e980)(p:0xbc56b0)(f:(nil)   )(h: 4)Type:view|layout:-    |w: 640|h: 781|x: 640|y:  19|g: -1|vis:t|children: 0|name:urxvt
|==focus:K   |(0x1052ad0)(p:0xbc56b0)(f:(nil)   )(h: 6)Type:view|layout:-    |w:   1|h:   1|x: 640|y: 390|g: -1|vis:t|children: 0|name:Open Files
01/25/17 18:17:08 - geometry request for 6 236x214 @ 639,390
01/25/17 18:17:08 - Sane values for view to 236 x 214 @ 640, 390
01/25/17 18:17:09 - Setting focus to 0x1052ad0:6 (VIEW 'Open Files')
01/25/17 18:17:09 - Sending window::focus event
01/25/17 18:17:10 - Setting focus to 0x102e980:4 (VIEW 'urxvt')
01/25/17 18:17:10 - Sending window::focus event
01/25/17 18:17:11 - Setting focus to 0x1052ad0:6 (VIEW 'Open Files')
01/25/17 18:17:11 - Sending window::focus event
01/25/17 18:17:11 - Destroying window 6
01/25/17 18:17:11 - Destroying view '0x1052ad0'
01/25/17 18:17:11 - Arranging layout for 0xbc56b0 (WORKSPACE '1')
01/25/17 18:17:11 - Arranging layout for 0xbc56b0 1 1280.000000x781.000000+0.000000,19.000000
01/25/17 18:17:11 - -> Found panel for this workspace: 1280x19, position: 0
01/25/17 18:17:11 - Arranging workspace '1' at 0.000000, 19.000000
01/25/17 18:17:11 - Arranging 0xbc56b0 horizontally
01/25/17 18:17:11 - Calculating arrangement for 0x103cd30:4 (will scale 1280.000000 by 1.000000)
01/25/17 18:17:11 - Arranging layout for 0x103cd30 Unable to configure Macbook Pro Trackpad · Issue #1059 · SirCmpwn/sway - Chromium 640.000000x781.000000+0.000000,19.000000
01/25/17 18:17:11 - Set view to 640 x 781 @ 0, 19
01/25/17 18:17:11 - Calculating arrangement for 0x102e980:4 (will scale 1280.000000 by 1.000000)
01/25/17 18:17:11 - Arranging layout for 0x102e980 urxvt 640.000000x781.000000+640.000000,19.000000
01/25/17 18:17:11 - Set view to 640 x 781 @ 640, 19
focus:R      |(0x63a4c0)(p:(nil)   )(f:0xba36c0)(h:18446744073709551615)Type:root|layout:-    |w:1280|h: 800|x:   0|y:   0|g:  0|vis:t|children: 1|name:root
|focus:X     |(0xba36c0)(p:0x63a4c0)(f:0xbc56b0)(h: 1)Type:op  |layout:-    |w:1280|h: 800|x:   0|y:   0|g: -1|vis:t|children: 1|name:LVDS-1
|-focus:W    |(0xbc56b0)(p:0xba36c0)(f:0x103cd30)(h:18446744073709551615)Type:ws  |layout:Horiz|w:1280|h: 781|x:   0|y:  19|g: -1|vis:t|children: 2|name:1
|--focus:K   |(0x103cd30)(p:0xbc56b0)(f:(nil)   )(h: 5)Type:view|layout:-    |w: 640|h: 781|x:   0|y:  19|g: -1|vis:t|children: 0|name:Unable to config
|--focus:X   |(0x102e980)(p:0xbc56b0)(f:(nil)   )(h: 4)Type:view|layout:-    |w: 640|h: 781|x: 640|y:  19|g: -1|vis:t|children: 0|name:urxvt
01/25/17 18:17:11 - Sending window::close event
01/25/17 18:17:11 - Setting focus to 0x103cd30:5 (VIEW 'Unable to configure Macbo)
01/25/17 18:17:11 - Sending window::focus event
01/25/17 18:17:14 - Setting focus to 0x102e980:4 (VIEW 'urxvt')
01/25/17 18:17:14 - Sending window::focus event
01/25/17 18:17:15 - Setting focus to 0x103cd30:5 (VIEW 'Unable to configure Macbo)
01/25/17 18:17:15 - Sending window::focus event
01/25/17 18:18:14 - Setting focus to 0x102e980:4 (VIEW 'urxvt')
01/25/17 18:18:14 - Sending window::focus event
01/25/17 18:18:15 - Setting focus to 0x103cd30:5 (VIEW 'Unable to configure Macbo)
01/25/17 18:18:15 - Sending window::focus event
01/25/17 18:18:15 - Setting focus to 0x102e980:4 (VIEW 'urxvt')
01/25/17 18:18:15 - Sending window::focus event

Quit doctoring it and just upload the entire log to a pastebin somewhere like gist.github.com. And your sway config.

Sorry, I didn't do any "doctoring" intentionally -- opened the log file in one window in less, highlighted, copied, and pasted directly into the comment box.
https://gist.github.com/n8henrie/10e3232cc31373ce75cd046bb8ebab8d
Again, I'll assume sway --verbose --debug &> out.log is a reasonable way to get the information you're asking for unless you tell me otherwise (I don't see any mention of another log file, a flag or envvar for another  debug output location). Thanks for your time.

"...skipping..."
Said doctoring isn't present in the new gist, which is indeed a complete log, so I can identify the issue. The important part appears to be here:
01/25/17 21:53:33 - [handlers.c:131] Found input device (1452:566:Apple_Inc._Apple_Internal_Keyboard_/_Trac)
01/25/17 21:53:33 - [handlers.c:141] Matched input config for 1452:566:Apple_Inc._Apple_Internal_Keyboard_/_Trac
01/25/17 21:53:33 - [config.c:969] apply_input_config(1452:566:Apple_Inc._Apple_Internal_Keyboard_/_Trac)
01/25/17 21:53:33 - [config.c:996] apply_input_config(1452:566:Apple_Inc._Apple_Internal_Keyboard_/_Trac) natural_scroll_set_enabled(1)
01/25/17 21:53:33 - [config.c:1012] apply_input_config(1452:566:Apple_Inc._Apple_Internal_Keyboard_/_Trac) tap_set_enabled(1)

It seems that the device is correctly identified, your config is matched, and your options applied. This indicates that the problem is in libinput, not in sway - your options are being faithfully passed to libinput by sway. Report to them for assistance. Good luck!

Figured it out, it was a sway config issue (my fault). For future Googlers:
Looking at the capabilities listed under sudo libinput-list-devices, it showed that the device I was trying to use above doesn't have Tap-to-click or Nat.scrolling, which surprised me. Looking below that, it showed a device named bcm5974 that did have those capabilities. I googled and ends up that's the touchpad driver. I changed my config to use input "1452:566:bcm" (as reported by swaymsg -t get_inputs) and it worked instantly.
Also, I've reproduced the ...skipping... issue -- it's from scrolling while highlighting in less. Sorry about that.

Glad you got it working. You can use xclip in the future, by the way, it works fine for the Xwayland clipboard.


i2c_monitor may cause chip-level tests to get stuck

The I2C monitor watches the SDA/SCL pins of the chip.
These ping are multiplexed with other peripherals such as GPIO and PWM (and their corresponding monitors)*.
*Note:
This may be dependent on test-bench configuration and in that case, we are referring to the default configuration.
Other test-bench configurations, if exist, were not explored!
First issuel
The I2C monitor is enabled by default.
This means that the monitor is active, regardless if the PINMUX configuration.
Therefore, the monitor may interpret activity on the pins as I2C transactions, and forward them to the TLM FIFO.
Second issue:
The implementation for the monitor_ready_to_end task is:
virtual task monitor_ready_to_end();
forever begin
@(cfg.vif.scl_i or cfg.vif.sda_i or cfg.vif.scl_o or cfg.vif.sda_o);
ok_to_end = (cfg.vif.scl_i == 1'b1) && (cfg.vif.sda_i == 1'b1);
end
endtask : monitor_ready_to_end
This means that if ANY toggling on either the SCL or SDA occurs then "ok_to_end" will de-assert.
In such case, the condition "SCL is high AND SDA is high" must exist at the end of the run phase
and must be kept for the duration of the watchdog_ok_to_end timeout in order for "ok_to_end" to become asserted again.
If this is not so then the I2C monitor will raise an objection or (optionally) will keep toggling its objection up and down,
This will prevent UVM scheduler from ending the run phase and consequently the test will get stuck.
Note that:

this issue exists whether the I2C monitor is enables or not!
this issue exists in both self-contained and none self-contained S/W tests (as long as the monitor is present in the test-bench).

Workaround:
At the end of the S/W, drive the I/O pins such that the condition "SCL is high AND SDA is high" is met.
Hold the condition for sufficient time and only then exit test_main.

Does this mean we should tie the enablement of the monitor into this task and perhaps disable it by default in the chip level environment?

Issue 1:
I agree this is a problem. We can add dv_base_agent_cfg::en_monitor which must be used effectively by the agent monitors to disable the monitoring logic until the IP is ready to be used.

Issue 2:
What is the actual idle condition for the I2C? Should both pins be left undriven by either party? If so, then we can update it that way. Note that I2C agent is still under active development.

if i2c is idle, both scl and sda should be weakly pulled up.

sorry i mean that in the sense of hte protocol, not trying to say that's how the tb should behave necessarily.

we do need to do something for this one because i think a similar reason is causing failures in #16296

@tjaychen I think the consensus was leave en_monitor = 1 as default and
disable on each test.
I can fix #16296

sounds good. I personally still think it should be the other way around since so few tests make use of i2c monitor... but whatever you guys think works should do.

It is beneficial to add a config knob to enable / disable the monitor at runtime generally for all agents. In my comment above, I suggested adding it to the base class dv_base_agent_cfg. If we put it there, then it would have to default on to avoid churn for the blocks level testbenches.
Plus, the muxed interfaces issue is a chip level design artifact, so we can simply turn the I2C monitor off in chip_env_cfg when it creates the i2c_agent_cfg instances. So that way, it is off by default for all tests at the chip level. We only selectively enable it in the test sequences that exercise I2C.

that sounds good to me.

Reassigning back to @yehuda-bejar. I believe @jdonjdon's PR #16333 addresses both concerns. PTAL and let us know if there are more fixes needed.

OK


Update to Azure.Messaging.EventHubs

Seems like Microsoft.Azure.EventHubs has been replaced by Azure.Messaging.EventHubs.
Creating this to track any work to migrate.
https://www.nuget.org/packages/Azure.Messaging.EventHubs/5.3.0

I have created PR #25 that resolves this issue.

That's a question for @nblumhardt

Merged! I'm not up-to-date with event hubs (or this sink) so will need some feedback on the -dev package (should be published soon) before a "6.0" can be released.
Thanks for this, though!

Thanks @nblumhardt. The change is very straight forward. The Azure EventHub "Microsoft.Azure.EventHubs" SDK has been moved to maintenance support in favor of the newer version "Azure.Messaging.EventHubs". The code change updates the dependency and modifies some of the class names appropriately. There is no change to functionality.


Click on menus on explorer title bar collapses the explorer

re https://github.com/Microsoft/vscode/issues/27467

Clicking on the dropdown menu should not collapse the explorer.

Thanks @bpasero for the fix. It's a tricky one.


Added Group version

I was unable to get get any of the three options working. Are they available, @whyrusleeping?

They are probably just CLI level options, try to sniff the 3 through wire shark, if the request/response are the same, it means it is the CLI that is doing the parsing and filtering (which means the flags shouldn't be described on the HTTP-API)

They don't even hit wireshark. I think this is all done on the API. So; I guess I should remove those options?

Yep, that is correct :)

Thanks @diasdavid

This is for #20


vid2vid not interacting with SD?

I managed to turn Flow_utils into CPU versions due to my old GPU, it's entirely possible with a good CPU. Confused right now as to why vid2vid and SD aren't interacting.
altered code

`import numpy as np
import cv2
#RAFT dependencies
import sys
sys.path.append('RAFT/core')
from collections import namedtuple
import torch
import argparse
from raft import RAFT
from utils.utils import InputPadder
RAFT_model = None
def RAFT_estimate_flow(frame1, frame2, device = 'cpu'): # Change 'cuda' to 'cpu'
global RAFT_model
if RAFT_model is None:
args = argparse.Namespace(**{
'model': 'RAFT/models/raft-things.pth',
'mixed_precision': True,
'small': False,
'alternate_corr': False,
'path': ""
})
RAFT_model = torch.nn.DataParallel(RAFT(args))
RAFT_model.load_state_dict(torch.load(args.model, map_location=device)) # Use map_location to specify device

RAFT_model = RAFT_model.module
RAFT_model.to(device)
RAFT_model.eval()

with torch.no_grad():
frame1_torch = torch.from_numpy(frame1).permute(2, 0, 1).float()[None].to(device)
frame2_torch = torch.from_numpy(frame2).permute(2, 0, 1).float()[None].to(device)
padder = InputPadder(frame1_torch.shape)
image1, image2 = padder.pad(frame1_torch, frame2_torch)

# estimate optical flow
_, next_flow = RAFT_model(image1, image2, iters=20, test_mode=True)
_, prev_flow = RAFT_model(image2, image1, iters=20, test_mode=True)

next_flow = next_flow[0].permute(1,2,0).cpu().numpy()
prev_flow = prev_flow[0].permute(1,2,0).cpu().numpy()

fb_flow = next_flow + prev_flow
fb_norm = np.linalg.norm(fb_flow, axis=2)

occlusion_mask = fb_norm[..., None].repeat(3, axis = -1)

return next_flow, prev_flow, occlusion_mask
def compute_diff_map(next_flow, prev_flow, prev_frame, cur_frame, prev_frame_styled):
h, w = cur_frame.shape[:2]
next_flow = cv2.resize(next_flow, (w, h))
prev_flow = cv2.resize(prev_flow, (w, h))
flow_map = -next_flow.copy()
flow_map[:,:,0] += np.arange(w)
flow_map[:,:,1] += np.arange(h)[:,np.newaxis]
warped_frame = cv2.remap(prev_frame, flow_map, None, cv2.INTER_NEAREST)
warped_frame_styled = cv2.remap(prev_frame_styled, flow_map, None, cv2.INTER_NEAREST)
compute occlusion mask
fb_flow = next_flow + prev_flow
fb_norm = np.linalg.norm(fb_flow, axis=2)
occlusion_mask = fb_norm[..., None]
diff_mask_org = np.abs(warped_frame.astype(np.float32) - cur_frame.astype(np.float32)) / 255
diff_mask_org = diff_mask_org.max(axis = -1, keepdims=True)
diff_mask_stl = np.abs(warped_frame_styled.astype(np.float32) - cur_frame.astype(np.float32)) / 255
diff_mask_stl = diff_mask_stl.max(axis = -1, keepdims=True)
alpha_mask = np.maximum(occlusion_mask * 0.3, diff_mask_org * 4, diff_mask_stl * 2)
alpha_mask = alpha_mask.repeat(3, axis = -1)
#alpha_mask_blured = cv2.dilate(alpha_mask, np.ones((5, 5), np.float32))
alpha_mask = cv2.GaussianBlur(alpha_mask, (51,51), 5, cv2.BORDER_DEFAULT)
alpha_mask = np.clip(alpha_mask, 0, 1)
return alpha_mask, warped_frame_styled
`

The popout window worked like it was supposed to, allowing to view the process and leaving me with a flow.h5 file.
After that I tried to bash the ui but my PC kept saying there is no python3, instead I added the flags into the batch and just ran the batch. As SD was up and running I checked out the link to the API which leave me with: {"detail":"Method Not Allowed"} and upon running vid2vid.py nothing happens aside from an empty mp4 being created.
This is the altering I have done to the vid2vid.py:
from cpuFlow_utils import compute_diff_map
Kinda new to Python and all too but been making my way through, nonetheless I keep running into my PC not recognizing my python3 installation.

Gonna need to see more info on your code changes and more traceback details to work it out

I'm gonna close this issue as SD-CN-Animation is not working through the API anymore and this issue is no longer relevant.


Improve execution for trainer-related tests

Some of the integration tests related to the different Argilla trainers have a heavy execution in terms of resource usage. Especially those related to the spaCy framework.
It would be nice to review them and optimize the execution in terms of memory and time consumption.

And memory usage (in descending order):
test_train_no_model,<PHONE_NUMBER>
test_setfit_train,<PHONE_NUMBER>5
test_train_tokencat,<PHONE_NUMBER>5
test_evaluate_train_test, 705.703125
test_setfit_train_multi_label,<PHONE_NUMBER>5
test_train_tokencat,<PHONE_NUMBER>5
test_train_textcat,<PHONE_NUMBER>
test_train_textcat_multi_label,<PHONE_NUMBER>
test_predict_wo_training,<PHONE_NUMBER>
test_various_inputs,<PHONE_NUMBER>5
test_update_config,<PHONE_NUMBER>5
test_update_config,<PHONE_NUMBER>5
test_openai_train_token, 283.9375
test_base_token_classification,<PHONE_NUMBER>5
test_openai_train_text2text, 282.96875
test_update_config,<PHONE_NUMBER>5
test_update_config,<PHONE_NUMBER>5
test_setfit_train, 280.21875
test_openai_train_multi_label, 280.1875
test_base_token_classification,<PHONE_NUMBER>
test_base_token_classification,<PHONE_NUMBER>
test_base_text_classification_with_split,<PHONE_NUMBER>5
test_base_text_classification_with_split,<PHONE_NUMBER>
test_base_text_classification_with_split,<PHONE_NUMBER>5
test_base_text_classification_without_split, 239.015625
test_base_text_classification_without_split,<PHONE_NUMBER>5
test_base_text_classification_without_split,<PHONE_NUMBER>
test_wrong_framework, 33.4140625


training data

hi, thank you for your nice work! Do you train your M2-BERT-128 ~ 32K (shown in the paper) on LOCO V0 or LOCO V1 training set?

The public checkpoints are trained on LoCoV0. New checkpoints on LoCoV1
will be coming out soon!
On Thu, Mar 14, 2024 at 1:41 PM 41924076 @.***> wrote:

hi, nice work! Do you train your M2-BERT-128 ~ 32K (shown in the paper) on
LOCO V0 or LOCO V1 training set?
—
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/m2/issues/27, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDDIIXLR7J4RKJQRVWXDOTYYHOLXAVCNFSM6AAAAABEWR66JSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE4DMOJSGQ2DKNQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

thank you for your reply!

We use random negatives for fine-tuning. At each step for OPL, we calculate the similarity between the query and the positive passage as well as the similarity between the query and the negative passage.

thank you for your reply!

Hello, I find that it's a little bit hard to make qmsum score more than 45, do you use the whole LOCO V0 as training set with no duplication, deletion or certain data proportion? : )

We use all of LoCo V0 as our fine-tuning dataset with 32 negatives for every query-positive passage pair. The public checkpoints only go through pretraining and LoCoV0 fine-tuning. However, we plan to release an updated version of the QMSUM dataset (as well as several new datasets) in LoCoV1 soon!

Thank you for your reply! Have a nice day!

Hello, sorry to bother you. I'd like to try reproducing the training of m2bert on loco v0 or v1 with 2048 length.
According to your information and the paper, m2bert loco v0 was trained with OPL loss. However, the main branch on GitHub does not provide a statement script for training (https://github.com/HazyResearch/m2/blob/main/bert/EMBEDDINGS.md#training), and the code does not include OPL loss.
Additionally, I noticed that the jonsf branch (https://github.com/HazyResearch/m2/tree/jonsf-patch-1) includes OPL loss, but I'm unsure if the gather_loco_training_example in the jonsf branch is suitable for OPL loss. The training script provided in the jonsf branch (https://github.com/HazyResearch/m2/blob/jonsf-patch-1/bert/EMBEDDINGS.md#training) also uses GradCache's multiple_negatives_ranking_loss instead of OPL. Can this script produce good results similar to those mentioned in the paper?
If it's convenient for you, could you please provide a OPL (or  multiple_negatives_ranking) loss training script that can reproduce public checkpoint?

thank you for your reply!!!

hi, i tried to train m2bert on loco v0. i use the m2bert-2k-pretrained-checkpoint and training_yaml=yamls/finetune-glue/embedding_training.yaml.
I trained with tevatron's loss, 4neg per query, batchsize=1, 8gpu, and use negatives_x_devices, which means one query have 32 random neg in total. I trained 4 epochs and get the result as follows:
Summ ScreenFD 0.74
Gov.Report 0.92
QMSUM 0.46
QASPER Title 0.64
QASPER Abstract 0.81
avg 71.4
Do you think it's a correct result?

Hi, thank you for publishing your results and sharing your training code!
It looks like you are importing OPL as sentence_transformers.losses.OrthogonalPassageLoss.
However when i check sentence transformers they don't have this loss, so I'm assuming this is a fork of sentence_transformers, that you haven't shared?
From above and your paper it sounds like you are doing something like below pseduo_code
def opl_loss(model, query, documents, labels):
    q_embedding = model(query)
    d_embeddings = model(documents) # 1 positive + 32 randomly sampled negatives
    pairwise_cosine_sim = cosine_sim(q_embedding, d_embeddings)
    loss = mse(pairwise_cosine_sim, labels)
    return loss

Does this sound about right?

Yes, we have a custom version of the SentenceTransformers code base, in which we add orthogonal projection loss (OPL). We include the instructions for importing it in the M2 codebase but here is the link to the codebase.

Thank you for the quicky reply. This is exactly what I was looking for.


Link to x64 CEF binary leads to x32 CEF binary

The link from Step 2 in README.md for x64 sample binary distribution leads to: https://s3.amazonaws.com/wesselsga/cef/issue_1006/cef_binary_3.3425.1784.gc5ef4df_windows32_minimal.7z
Correct link should be:
https://s3.amazonaws.com/wesselsga/cef/issue_1006/cef_binary_3.3425.1784.gc5ef4df_windows64_minimal.7z
If you don't notice you downloaded 32 bit and continue to step 5, you'll be getting cryptic messages like unresolved external symbol cef_string_utf8_clear in VS2017 during build.

Good catch!  Should be fixed now.
Thanks


Extension causes high cpu load

Issue Type: Performance
Extension Name: python
Extension Version: 2022.9.11611009
OS Version: Windows_NT x64 10.0.18362
VS Code version: 1.68.0

:warning: Make sure to attach this file from your home-directory:
:warning:file:///c%3A/Users/ERICK_~1/AppData/Local/Temp/ms-python.python-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.


How do you go loop

Ok im trying to find out how these strips would go to loop. When i turn them ON they just solid white and dont go to loop (they supposed to?).  The code is original,just copy and paste. Do i need to do loop via mqtt i wonder or how?

Anyone??Why noone talks when is Mqtt in question??

Hi @KodiMkd,
what do you mean when you say loop?
are you talking about effects, such as the ones Ben shows in his video?

When i say loop i mean all the effects is bruh to go trough a loop..one then after 5 mins another the a other..all of them 15 lets say..and then start all over again same thing

OK, so you can do that with an automation in home assistant.
it would just be a case of triggering the first effect, then setting a delay on the automation, then start the next effect, and then repeat this for all you want

If you can just lead me with the first stage in HA then i can just copy the
rest
Oliver Kostov
On Dec 6, 2017 8:05 PM, "Joeboyc2"<EMAIL_ADDRESS>wrote:

OK, so you can do that with an automation in home assistant.
it would just be a case of triggering the first effect, then setting a
delay on the automation, then start the next effect, and then repeat this
for all you want
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bruhautomation/ESP-MQTT-JSON-Digital-LEDs/issues/53#issuecomment-349827760,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYiaekL8_3UrGb4hrVJIBh9qpJDMbuyFks5s9znpgaJpZM4QAUku
.


Join PipeHistory queries with pipes for additional tags

What does this PR do?
This PR adds 2 additional tags to the PipeHistory query
Motivation
Without these tags, these metrics are almost useless. Imagine the following:
2 schemas, one is dev env, one is production. Each schema has a pipe named “INPUT_PIPE” that ingests data into snowflake.
Without these tags, the metric is useless, because it aggregates across non related schemas.

[x] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.

@hestonhoffman Thanks
First contriubtion for me here - how do I fix the changelog parts? + not sure about the tests here, will they fail if the query is wrong?

@hestonhoffman Thanks First contriubtion for me here - how do I fix the changelog parts? + not sure about the tests here, will they fail if the query is wrong?

That's a good question for @DataDog/agent-integrations :)

@iliakur What's next needed here? Anyway to validate the query?

@yogevyuval sorry about the delay. I'm about to go on holiday, my colleague @alopezz will take over next week. Have a good weekend and thanks again for your patience!

Sadly, we don't have an automated way of testing the integration against an actual instance of Snowflake. If you want, you can add a test with a mocked response such as those on https://github.com/DataDog/integrations-core/blob/master/snowflake/tests/test_queries.py, but since I don't see one already in place for this query, I'm not going to block the PR based on that.
I'm going to test the PR out manually to make sure the query is valid before approval.

Fixed the PR comments (and adjusted the changelog entry accordingly).
Appreciate you helping out with manual testing - let me know if everything worked our or if additional changes are needed!

@alopezz Did you have a chance to run this? Anything else from my side needed?

Sorry for the delay. I was trying to get the necessary data into a test account to get some data from the modified query but I haven't been able to do so. The query itself is fine in that it doesn't produce an error, I'm simply not getting any results for extra confirmation.
Would you be able to share some example results of that query? Since you've found the need to improve the query I suppose you should be able to get some data from it. I can then do some final testing out of that.

Sorry for the delay. I was trying to get the necessary data into a test account to get some data from the modified query but I haven't been able to do so. The query itself is fine in that it doesn't produce an error, I'm simply not getting any results for extra confirmation.

@alopezz
Yes, I ran this query on my account and it worked well. The reason I was a bit worried is actually things like specifying the database + schema before the table name or not, because for example in the original code it uses FROM pipe_history without any db or schema, and in the join I added I specified snowflake.account_usage.pipes.
So I wanted to make the query actually compiles well, no permission errors or other things like that

@alopezz Yes, I ran this query on my account and it worked well. The reason I was a bit worried is actually things like specifying the database + schema before the table name or not, because for example in the original code it uses FROM pipe_history without any db or schema, and in the join I added I specified snowflake.account_usage.pipes.
So I wanted to make the query actually compiles well, no permission errors or other things like that

I see what you mean (I hadn't payed close enough attention to that); technically it shouldn't matter because that query is always meant to be run against the SNOWFLAKE database and is only available when the schema is set to ACCOUNT_USAGE(see config), so both qualifying and not qualifying the table name works. You might want to remove the qualification from the reference to the pipes for consistency with the rest of the existing queries, other than that I consider this ready to merge.

@alopezz I removed the qualifications


batch draw support?

If drawImage the same Image instance，combine into one draw call.

it is worth considering, the only problem is that besides catching the image I would have to catch lots of other parameters (transform matrix) so it wont be as easy as it seems.
I will give it a look.


Ghostbox

Your Description says that the Ghost Box will only speak every 10 seconds. I definetly watched it often speak in a 3-4 second pattern.

I personally have not experienced this, and the code for the Spirit Box (EVPReader) specificaly sets a 10 second timer every time it gives a response. If you capture this in a video and post it here, I will check the code again.

here ya go https://www.youtube.com/watch?v=5JLx__1M_Us

Thanks for that @pacefalm. I'll take a look at this again. Is this on the stable branch or beta branch? I know they've been making a bunch of changes on beta recently that I haven't looked into.

This was on the stable branch a few days ago.

Okay, I just saw that they pushed all changes from the beta branch to the main branch. I'll try take a look, but since they changed from Managed to IL2CPP, snooping around might be a bit more difficult.


⚠ ClamAV has degraded performance

In eeb8e15, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 239 ms

Resolved: ClamAV performance has improved in a50d76d after 5 minutes.


Not working on Ipad and Iphone

Hello, I have an issue with  tag removing by itself after page loaded.

Hi @IvMarKon,
That is the intended behaviour.

Destroys the video and prevents it downloading on iOS devices (because they can't do background video)

When the plugin was written, iOS didn't work with background videos. It may be different now, but I haven't kept up with the state of iOS and this plugin is further down my priority list than it used to be.
If you want to do some research about support for auto-playing video on new iOS versions and let me know if it's possible to support it properly now then I might be able to update the plugin accordingly.
I'm also open to pull requests.
Thanks,
Angus

Fixed by #12


Drop pathos

Replace ProcesPool by ThreadPoolExecutor in provers.

Hmmmm, why are we doing this actually? My understanding is that starting up threadpool will be less work overall. But also, it seems that onyl one thread will be allowed to execute at a time because of teh Python interpreter GIL:
https://superfastpython.com/threadpoolexecutor-vs-processpoolexecutor/

So if my undertanding is correct, then only one Python thread will be allowed to execute at a time. This would be fine if the amount of time spent in executing python code was neglible compared ot backend time, but it's not the case.

it seems that onyl one thread will be allowed to execute at a time because of teh Python interpreter GIL

You're right, I wasn't aware of this detail.

why are we doing this actually

I wanted to avoid pickling between processes because in some cases it causes problems, e.g. exceptions not propagating to the main thread, tests not being able to capture logs, etc.

This would be fine if the amount of time spent in executing python code was neglible compared ot backend time, but it's not the case.

I'll replace executors to a ProcessPoolExecutor. If it works as expected, then we can still drop the third party dependency.

I'll replace executors to a ProcessPoolExecutor. If it works as expected, then we can still drop the third party dependency.

Nope.
concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
  File "/home/ttoth/.pyenv/versions/3.10.12/lib/python3.10/multiprocessing/queues.py", line 244, in _feed
    obj = _ForkingPickler.dumps(obj)
  File "/home/ttoth/.pyenv/versions/3.10.12/lib/python3.10/multiprocessing/reduction.py", line 51, in dumps
    cls(buf, protocol).dump(obj)
AttributeError: Can't pickle local object 'foundry_prove.<locals>.init_and_run_proof'
"""


View engine is being ignored in 2.9.0

I am using an html view engine:
app.set('view engine', 'html');
app.engine('html', require('./hbs')(app, config));

And specifying my layout (layout_simple.html) like this:
res.render('signup', {
  layout: 'layout_simple'
});

Up until version 2.8.0 this was working fine. After upgrading to hbs 2.9.0 I'm getting an error on load:
Error: ENOENT, open '/.../layout_simple.hbs' (where /.../ is the correct view path.)
Specifying the layout explicitly as layout: 'layout_simple.html' works correctly. Seems like a bug to me.
This change may be the culprit:
https://github.com/donpark/hbs/compare/donpark:18c1823...donpark:5e44774#diff-0646323334941cee08c9e424acbee543R120

Yep, seems to be an issue where the PR doesn't carry the extension through. Care to make a PR to fix it with a test so we don't break again?

For sure. I will take a look at this when I have a bit of time to get into it.

fixed in 3.0.1

great news :+1:


Community: Fixing incorrect base URLs for Azure Cognitive Search Retriever

This PR adds code to make sure that the correct base URL is being created for the Azure Cognitive Search retriever. At the moment an incorrect base URL is being generated. I think this is happening because the original code was based on a depreciated API version. No dependencies need to be added. I've also added more context to the test doc strings.
I should also note that ACS is now Azure AI Search. I will open a separate PR to make these changes as that would be a breaking change and should potentially be discussed.
Twitter: @marlene_zw

No new tests added, however the current ACS retriever tests are now passing when I run them.
Code was linted.

LGTM

Hi @baskaryan, could you have a look at this PR


V2.0.2(43) android remove entry

I'm unable to find a way to remove an entry. A entry badly configured remain and i can't remove it.

Hi @devoyon,
tap on the icon of the entry. This brings up the options to move, edit the label or delete the entry.

Excellent !!! Thanks (resolved)


validation steps for each variable

In order to be able to run the validation step on observations, we first need to know which functions in validator.py need to run. The general idea is that a higher level function will queue up a job. That job will get the observation data, call the right validation functions, and store the result back in the database.
The variables are defined in datamodel.py and are:
ALLOWED_VARIABLES = {
    'surface_temperature': 'degC',
    'surface_wind_speed': 'm/s',
    'ghi': 'W/m^2',
    'dni': 'W/m^2',
    'dhi': 'W/m^2',
    'poa_global': 'W/m^2',
    'relative_humidity': '%',
    'ac_power': 'MW',
    'dc_power': 'MW',
    'availability': '%',
    'curtailment': 'MW',
}

For some variables, there may be no validation functions to run. To start, we need a mapping between the variables and a list of validation functions (in order if necessary). We'll have to decide how this will be implemented in the code (maybe a dict or a function that returns a set of functions to run) but that can come later.
@cwhanse can you make this list between variables and validation functions?

For ghi, dni or dhi: check_irradiance_day_night  I'd probably do this first before any of the other checks.  It labels day/night periods.  What is done with the labels should be discussed as a model for the other validation testing.  Do we display the results and ask the framework user to make a choice?
With ghi only: check_irradiance_limits_QCRad then check_ghi_clearsky
With ghi, dni and dhi together: check_irradiance_limits_QCRad first, then check_ghi_clearsky applied to ghi, then check_irradiance_consistency_QCRad
For surface_temperature: check_temperature_limits
For surface_wind_speed: check_wind_limits
For any measured data: check_timestamp_spacing
For measured GHI, ac_power or dc_power: detect_stale_values, then detect_interpolation
For measured ac_power: detect_clipping probably last in sequence (this function is in a PR)
Currently there is no value checking for poa_global or relative_humidity, tests should be added.
There is no value checking for availability or curtailment, either, but I think these data are checked by overlaying the data on measured ac_power, along with the output of detect_clipping

The current thinking on what would happen with the results is described in https://github.com/SolarArbiter/solarforecastarbiter-core/issues/57#issuecomment-485881215. Basically, a user will upload observations and if they pass the formatting requirements, they are inserted into the database. Then, a validation job will be queued up and will eventually run the validation functions and store the result of each test encoded as an integer described in #72.
The decision about what to do with data that is flagged by the validation functions is then decided when metrics are calculated/reports generated. The user will be able to see the validation results and can fix and re-upload data if necessary.
Does this sound reasonable? I also remember that there was some discussion of only running validation once a day on the full day of data. Is that desirable for any of the current validation functions?

If I was a framework user, I think that the sooner that validation checks are conveyed after data upload, the more I would value the content.  If, for example, I upload data, and am notified 2 days later that there's issues with the data, I may be more annoyed that I have to rewind in my work to go fix the issues, than if there was near-real time feedback at the time of upload.

I agree that a quick notification of any issue after manually uploading the data is useful. To keep the API responsive, I think we'd still want to conditionally accept the data, but make sure the validation job is run within a few minutes. We can then send a message to the dashboard on the status of the validation, and maybe users can opt in to emails about validation in beta+ versions.

I remember that, for "real-time" data feeds, we discussed the possibility of running verification as the data was submitted and then rerunning verification each night. I think we were mostly concerned about this for AC power that could be clipped or curtailed. I don't think we ever developed a good sense of if it would really be necessary or a clear plan of what it would look like in practice.
A related issue that we discussed was that verification scripts may need to operate on more than just the single upload. For example, I think some of the functions will struggle with a single data point of hourly average data that is uploaded every hour.

Good points.
Point-in-time checks: check_irradiance_limits_QCRad, check_ghi_clearsky, check_irradiance_consistency_QCRad, check_temperature_limits, check_wind_limits, check_rh_limits, check_timestamp_spacing
Checks requiring a time series: detect_stale_values, detect_interpolation, detect_clipping.  For these, I suggest requiring at least 24 hours(?) of data?  Or 10+ data points.  With shorter time series the code should run but the output is probably not useful.

with #97 and #82, most of the validation should run. However, verification that requires multiple observation series (e.g. ghi, dni, and dni or ac power and curtailment) is not implemented.

@alorenzo175 should this be closed too? "In Progress to Done" suggests yes, though it sounds like maybe a new issue should be created for verification algorithms that use multiple series.


[e2e]: go schedule main adversarial-binary-upload slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2954678233
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.schedule.main.adversarial-binary-upload.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.schedule.main.adversarial-binary-upload.slsa3.yml
Trigger: schedule
Branch: main
Date: Tue Aug 30 08:30:01 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2962347547
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.schedule.main.adversarial-binary-upload.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.schedule.main.adversarial-binary-upload.slsa3.yml
Trigger: schedule
Branch: main
Date: Wed Aug 31 08:27:47 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2970063672
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.schedule.main.adversarial-binary-upload.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.schedule.main.adversarial-binary-upload.slsa3.yml
Trigger: schedule
Branch: main
Date: Thu Sep  1 08:29:55 UTC 2022
Tests are passing now. Closing this issue.


script for latex images

We have a number of latex images and that will grow.  We use pdflatex and convert (see readme in latex folder) to make these into PNG files.
I'd like a simple script/batch file to sit in the latex folder and it runs over all the *.tex files in there and terms them into PNGs by running pdflatex and convert.

Working on this at the moment on branch JFM. I'm assuming everything that should be compiled from tex files to image files should be located in ./latex/. Let me know if this isn't correct.
Maybe a global object is created that runs through all the images and outputs them into ./uploads/images/? Might that be useful?


onRead not being called.

Added an onRead to my device, and implemented it. I do have a physical device to test with. I have tried light bulbs and ceiling fans, and I simply never see the onRead method being called. I am using Insteon+ app, and also using Siri to test.

Could you post what your device code looks like? You can post a gist or the code right inside the thread.

On Jun 26, 2015, at 8:12 PM, rayzorben<EMAIL_ADDRESS>wrote:
Added an onRead to my device, and implemented it. I do have a physical device to test with. I have tried light bulbs and ceiling fans, and I simply never see the onRead method being called. I am using Insteon+ app, and also using Siri to test.
—
Reply to this email directly or view it on GitHub.

I am using HomeBridge, but you can see the code in the pull request at https://github.com/nfarina/homebridge/pull/37/files

@rayzorben I commented on the actually pull request.

Please close, as this has been resolved by @rayzorben in https://github.com/nfarina/homebridge/issues/37 . Thanks.


Accomodate for multiple type values in styling for SDs in modern texts

In modern texts, we want the styling that we have to apply even when there is more than one @type value. Currently, styling only applies when there is more than one value and one of the values is "entrance".
I will make this change after Douai is released. @JanelleJenstad, I'm including you on this so that you can give the okay. Are you happy with this change? I don't think it will cause any unwanted fallout.
Currently what's happening:

(from H5_FM)
What happens with the proposed change:

(note that this also is on a different line than the other SD... that's coming from a different change that I'll put in a separate GH issue)
Note to self: To change this, add * after data-type in our modern text SD styling. Search
span[data-type="delivery"] to find this styling.

I'm all in favour. Please go ahead after Douai is released.

This issue may or may not be related. I'm noticing font size variations between prose and verse in Mucedorus in the LEMDO Classroom anthology.

@Janellejenstad I just checked this, and the computed font size for both speech text and stage directions in prose and verse speeches is identical: 19.44px.

@martindholmes is right. Mucedorus looks fine now.
@LEMDO-PM: Please go ahead now with your proposed fix.

Fix committed rev. 17372.

@LEMDO-PM I think you can close this now.


Issue-add opacity to bars and start mounts from same positions

Automated Review Comments
Issues in src/components/Bar.js:

(2, 'Hardcoded string found')
(3, 'Hardcoded string found')
(5, 'Line exceeds 80 characters')
(6, 'Line exceeds 80 characters')
(12, 'Hardcoded string found')
(13, 'Hardcoded string found')

I got it.


Use icon instead of action text

Is there any way I could add Icon instead of text in snackbar action?
Something like:
 <SnackBar
    visible={true}
    textMessage={"Snackbar text"}
    actionLabel={<Icon name="icon" size={30} />}
    // ...rest
  />

Hey @PiotrSzlagura ,
Sorry for delay, pushed an update implementing this.
You can pass any custom JSX to textMessage to render something custom.
Do open the PR again if that doesn't solve it.


JIProlog read_term/3 bug when reading the end of file

JIProlog <IP_ADDRESS> and previous versions have a read_term/3 bug when reading the end of file. If the option variable_names/1 is used, its value is not bound by the call. This bug results in an instantiation error when the Logtalk compiler tries to report variable naming issues.

Fixed in JIProlog <IP_ADDRESS>.


Add examples/case-studies of real-world geothermal systems

GEOPHIRES should include input/output examples for real-world geothermal systems. These examples will serve to calibrate and validate GEOPHIRES's calculations.

Candidate example: Eavor publishes 4-year update on Eavor-Lite demonstration project in Canada

Drilling operations at Fervo’s Cape Station show 70% year-over-year reduction in drilling times and pave the way for rapid geothermal deployment

Fervo has consistently reduced drilling times and costs in horizontal, high-temperature, deep granite drilling. Though Cape wells are hotter and over 2,100 feet deeper than Project Red wells, Fervo drilled its fastest Cape well in just 21 days, a 70% reduction in drilling time from Fervo’s first horizontal well drilled at Project Red in 2022. This increase in drilling efficiency has translated into significant cost reductions, with drilling costs across the first four horizontal wells at Cape falling from $9.4 million to $4.8 million per well.

Paper: https://pangea.stanford.edu/ERE/db/GeoConf/papers/SGW/2024/Elsadi.pdf?t=1706897516

Paper: Geology, State of Stress, and Heat in Place for a Horizontal Well Geothermal Development
Project at Blue Mountain, Nevada

SHR: Newberry Volcano in OR = classic example, Maxama recently awarded large grant for additional work

Fervo https://pangea.stanford.edu/ERE/db/GeoConf/papers/SGW/2023/Fercho.pdf

CATF report: A Preliminary Techno-Economic Model of Superhot Rock Energy: https://cdn.catf.us/wp-content/uploads/2022/12/16185500/shr-technoeconomic_2023report.pdf

Initial implementation for Fervo tentatively slated to be on https://github.com/malcolm-dsider/geophires-x-nrel/tree/fervo-case-study

Fervo: https://eartharxiv.org/repository/view/5704/

@malcolm-dsider Suggest we don't include the paper PDFs themselves as the large file size has negative performance impacts and other thorny technical complications.
Let's either just use standard citations in context (as I've already done for this paper here: https://github.com/softwareengineerprogrammer/GEOPHIRES-X/commit/030212a90dad26e8b263b0a4638ae35232e0438a#diff-68569bbc99a61381b74ad07a4d3f66b28463215381a74f76739bc8d4206e6402R2-R4), or if necessary, create a separate GEOPHIRES references repository.

But we already have 13 PDF files in the reference section… and one XLS. And one TXT….
From: Jonathan Pezzino @.>
Sent: Monday, May 6, 2024 11:48 AM
To: NREL/GEOPHIRES-X @.>
Cc: Malcolm Ross @.>; Mention @.>
Subject: Re: [NREL/GEOPHIRES-X] Add examples/case-studies of real-world geothermal systems (Issue #87)
@malcolm-dsider https://github.com/malcolm-dsider  Suggest we don't include the paper PDFs themselves as the large file size has negative performance impacts and other thorny technical complications.
Let's either just use standard citations in context (as I've already done for this paper here: softwareengineerprogrammer@ https://github.com/softwareengineerprogrammer/GEOPHIRES-X/commit/030212a90dad26e8b263b0a4638ae35232e0438a#diff-68569bbc99a61381b74ad07a4d3f66b28463215381a74f76739bc8d4206e6402R2-R4 030212a#diff-68569bbc99a61381b74ad07a4d3f66b28463215381a74f76739bc8d4206e6402R2-R4), or if necessary, create a separate GEOPHIRES references repository.
—
Reply to this email directly, view it on GitHub https://github.com/NREL/GEOPHIRES-X/issues/87#issuecomment-2096482211 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGVYT7PYEALJ5PCARRK3VLZA6X4PAVCNFSM6AAAAABBXILBLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJWGQ4DEMRRGE .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AWGVYT423ZSTVEWF7227453ZA6X4PA5CNFSM6AAAAABBXILBLGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT46XD2G.gif Message ID: @.*** @.***> >

@malcolm-dsider Yes, those are present and they have/do cause issues so we shouldn't add more; also if we were to create a separate repository as I suggested, we would move those files there.

https://github.com/NREL/GEOPHIRES-X/issues/288

https://github.com/NREL/GEOPHIRES-X/issues/290

Considering this resolved by addition of Fervo Project Red (https://github.com/NREL/GEOPHIRES-X/issues/202?title=Fervo+case+study) and Project Cape (https://github.com/NREL/GEOPHIRES-X/issues/288) examples


fix: small fixes and additions after demo days prep

This PR resolves [MOPLAT-]

Description
read the comments in this PR. a few changes and fixes.
PR Checklist

[ ] I tested my changes on iOS and Android.
[ ] I added screenshots or videos to illustrate my changes.
[ ] I added Tests and Stories for my changes.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Need help with something? Have a look at our docs, or get in touch with us.

🚢


Syncing Optimization

When we get blocks over pubsub, we are only able to process one at a time. This is not good, since each epoch will have multiple blocks to form a tipset. So we need to make processing concurrent in order to stay in sync.

You're working on this right now, right Eric?

Yup. But as I was doing it, realized we need to get Bitswap in, so im currently doing that right now


DatePicker modal background color

I have gone through these following points

[x] Check latest documentation: https://docs.nativebase.io/
[x] Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[x] Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[x] Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
[] For discussion purpose make use of NativeBase Slack: http://slack.nativebase.io/
[x] For queries related to theme, check Theme Variables from Docs and live NativeBase Theme Editor http://nativebase.io/customizer/

Issue Description

node, npm, react-native, react and native-base version, expo version if used, xcode version
Expo v35.0.0
Expected behaviour
The date should be seen in order to select.
Actual behaviour
For iOS dark mode the date is not seen. Actually it is rendered but the color matches with modal's background so can not be seen.
Steps to reproduce
Just a standard DatePicker code causes same experience if the code is tested with iOS dark-mode.
import * as React from 'react';
import { Text, View, StyleSheet } from 'react-native';
import { DatePicker } from 'native-base';

export default class App extends React.Component {
  constructor(props) {
    super(props);
    this.state = { chosenDate: new Date() };

    this.setDate = this.setDate.bind(this);
  }
  setDate(newDate) {
    this.setState({ chosenDate: newDate });
  }
  render() {
    return (
      <View style={styles.container}>
        <Text />
        <Text />
        <Text />
        <DatePicker
          defaultDate={new Date(1976, 12, 23)}
          minimumDate={new Date(1940, 1, 1)}
          maximumDate={new Date(2040, 12, 31)}
          locale={'en'}
          timeZoneOffsetInMinutes={undefined}
          modalTransparent={false}
          animationType={'fade'}
          androidMode={'default'}
          placeHolderText="Select date"
          textStyle={{ color: 'green' }}
          placeHolderTextStyle={{ color: '#d3d3d3' }}
          onDateChange={this.setDate}
        />
        <Text>Date: {this.state.chosenDate.toString().substr(4, 12)}</Text>
      </View>
    );
  }
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    backgroundColor: '#ecf0f1',
    padding: 8,
  },
});

Is the bug present in both iOS and Android or in any one of them?
Problem is only for iOS in dark mode
Any other additional info which would help us debug the issue quicker.
###Important
Expo snack here: (https://snack.expo.io/@mehmetkaplan/native-base-datepicker-test)

I know it isn't a solution, but for those looking for a temporary fix on their apps, you can add this to your AppDelegate.m. This will force light mode, for your application.
if (@available(iOS 13, *)) {
self.window.overrideUserInterfaceStyle = UIUserInterfaceStyleLight;
}
Source
https://github.com/facebook/react-native/issues/26299

I have posted my solution here https://github.com/facebook/react-native/issues/26299#issuecomment-552817409

@IgorUsoltsev Are you sure if your method works with native-base?
According to my analysis; the method you mentioned can be used with react-native-datepicker. Reference of the code line that I think is responsible that uses customStyles.datePickerCon: https://github.com/xgfe/react-native-datepicker/blob/2a209bd4f11a84ff4543fbde930fed60dcbc0f68/datepicker.js#L391
On the other hand it seems there is no method to customize the DatePicker in Native Base. Reference: https://github.com/GeekyAnts/NativeBase/blob/9c470822dc4912c3780cf14426cd3b6a56ef01f4/src/basic/DatePicker.js#L124

@IgorUsoltsev Are you sure if your method works with native-base?
According to my analysis; the method you mentioned can be used with react-native-datepicker. Reference of the code line that I think is responsible that uses customStyles.datePickerCon: https://github.com/xgfe/react-native-datepicker/blob/2a209bd4f11a84ff4543fbde930fed60dcbc0f68/datepicker.js#L391
On the other hand it seems there is no method to customize the DatePicker in Native Base. Reference:
https://github.com/GeekyAnts/NativeBase/blob/9c470822dc4912c3780cf14426cd3b6a56ef01f4/src/basic/DatePicker.js#L124

Sorry to hear that :(
Actually I didn't test it with this module. Just advised that might help here as I was looking through a number of similar issues looking for answer for my case.

Seems duplicate of #2966
Closing this one.

        <DatePicker
          ...
          customStyles={{
            ...
            datePicker:{backgroundColor: '#222'}
          }}
      />

how to change the styling of datepicker ?

Closed as per the duplicate label


Issue in reproducing results from the paper

Hi!
Thanks for the open-source work.
I tried training an LLVC with a custom voice using a pretrained model from weights.gg, however, there were several discrepancies that lead to failure in reproduction of the results:

The number of epochs are hardcoded to 10000, as opposed to 53 as mentioned in paper.
The training takes more than 1 hour on a H100 instance just for 250 global steps, and ~7-8 hours per 250 global steps on an A100 instance (with the default arguments in the experiments/llvc/config.json, with only the log_interval and checkpoint_interval altered). This is way off as compared to the information in the paper claiming a training time of 3 days on RTX 3090 (for 500000 steps), any suggestions to fix the same?:

Is there a way to efficiently finetune a new voice model with the pretrained G_500000.pth checkpoint in a parameter efficient manner that can be open-sourced?

The number of epochs is hardcoded to 10000, but we manually stopped training at 53. Which batch size are you using for training on the H100?
As for efficiently fine-tuning from G_500000.pt: the training procedure should be the same as starting from an untrained checkpoint, and from my informal experience should be slightly quicker to converge.


TypeInitializationException - The type initializer for ...ShadedCard threw an exception

Hi, I try to use your ShadedCard control in one of my projects.
I try to show a content page whose content is set like this:

    <controls:ShadedCard HasShadow="True" CornerRadius="0" Title="This is a card">
        <controls:ShadedCard.CardContent>
            <Label Text="This is the content..." />
        </controls:ShadedCard.CardContent>
        <controls:ShadedCard.ActionView>
            <Button Text="Action" />
        </controls:ShadedCard.ActionView>
    </controls:ShadedCard>

</FlexLayout>

When the constructor of the page is called I get the following runtime exception:
"Exception occurred while: Calling constructor DentalAssistantXF.Views.MainPage().
Exception is: TypeInitializationException - The type initializer for 'DentalAssistantXF.Controls.ShadedCard' threw an exception."
If i remove the ShadedCard control the application doesn't crash.
I would appreciate any kind of help

Looks like one of your bindable property is getting a wrong value type set, maybe as default. Can you look deeper in the exception and post the stack trace?

Ok I found it
I kept the default value you are using for the TitleStyleProperty but it was missing from my solution.
Thanks for your help


User defined error type owner is set to lang.annotations

Description:
Consider a user defined error type like below residing in say mod1:
public type Mod1Error error;

the owner of the user defined error type is set to lang.annotations. This doesn't happen to errors like type Err error<MyRec>. The owner is used by the ReferenceFinder to determine references to module mod1.
Steps to reproduce:
See description
Affected Versions:
Beta1 snapshot
Related Issues (optional):
#29276

This cause goto defs to not work for user defined error types with type reference error (ex: type Err error). Module of such user defined type symbols are set to lang.annotations too.
Blocks #29276

Relates to #29232

Relates to https://github.com/ballerina-platform/ballerina-lang/issues/26284

@pubudu91 Shall we prioritise and check this?

@pubudu91 Shall we prioritise and check this?

The correct module info gets returned now with the fix done for #26284.

Checked again in 2201.0.0, the correct module gets returned for this. Hence closing this.


Add start and stop commands

Relevant issue: Closes #20
Description:
This adds a start and a stop command to... start and stop bots.
Stopping a bot can be useful when something breaks and we need a while to figure it out.
This also contains some refactors to make the service commands more readable.
Checklist:

[x] Code Quality
[x] Pep-8
[ ] Tests (if applicable)
[x] Success Criteria Met
[x] Inline Documentation
[ ] Wiki Documentation (if applicable)

Just a note that this will require changes to the sudoers file on the server because Bubbles doesn't run as root.


How to read Automatic Proxy Detection (WPAD) in Asp.net core

in asp.net we can use the following setting in web.config to point to a wpad.dat file to read all the proxy setting, is there a way we can achieve the same thing in asp.net core?
<system.net>

</system.net>

This issue was moved to dotnet/corefx#32135


Don't override bootstrap background colours to allow bootstrap themes to work with fuelux

I've been developing an app using the superhero bootswatch theme , which is a dark theme that uses light text (unlike the default bootstrap theme). The problem is that some of the fuelux widgets (primarily repeater and wizard) have hard coded white backgrounds, which means they look terrible when combined with a dark theme, and worst of all the text is illegible.
I added superhero to your demo page as a demonstration. You can do the same to see what I mean:
var l = document.createElement("link");
l.rel = "stylesheet";
l.href = "//maxcdn.bootstrapcdn.com/bootswatch/3.3.0/superhero/bootstrap.min.css";
b = document.querySelector("body");
b.appendChild(l);

Examples:

Would it be possible to use standard bootstrap classes like .panel and .container to make fuelux work better alongside bootstrap themes? Thanks so much for the library!

Thanks @TMiguelT. This is something to consider. We've had to theme these controls manually ourselves, too. See Themed Fuel UX Controls at the bottom. These are the overrides, we've had to write ourselves.

@TMiguelT How do other Bootstrap extensions (JS plugins) handle this? Are you using any that are as complex that handle this well?

Well all bootstrap plugins I've used use bootstrap classes so I've never noticed this problem before. I did a little playing around, and I think with very little effort the wizard could be fixed to work with custom themes.
In the below examples I only changed 3 things with the wizard CSS:

Added the .panel class to the .wizard element
Removed the background-color from .fuelux .wizard
Removed the background-color from .fuelux .wizard > .actions (the top right panel with the buttons)

If you compare them to the examples I posted at the top, I think they're a lot better. They're certainly legible now.
Superhero (dark) theme:

Default fuelux theme:

@interactivellama definitively :+1:  on this. It would be nice if FuelUX would use standard bootstrap classes. This way theming would be easier.

can we do
.wizard {
  &:not(.panel) {
    background-color:
  }
}

around https://github.com/ExactTarget/fuelux/blob/master/less/wizard.less#L8
@Misiu or @TMiguelT if you would like to provide a PR and example we welcome the assistance


Can the font color please be hotpink?

Thanks!

Plz add config, i need it in neon green!!!11eleven

Contribution is welcome :-)


Need to be able to upate a texture partially

I'm writing a HeightMap module , and when the heights are edited it would be nice to be able to update only a sub-rectangle of the textures instead of the full 2048x2048 pixels (or the full 512x512 rects if the textures are chunked on superlarge terrains). My editing process is chunked already for memory efficiency, but uploading the textures would also make it faster with this feature (it's currently unbearable at size 2048)

@reduz  Is this still possible to have in 3.0?

I had a read in RasterizerStorageGLES3 to see how texture data is uploaded, and I have to admit a few things:

The function already uses glTexSubImage2D with full rectangle (while I need sub-rectangle)
However it does that only if TEXTURE_FLAG_USED_FOR_STREAMING
Many other options come into play, including mipmaps
If I implement sub-region, it may come with incomplete support of all these features (any advice?)

My use case stems from the fact that editing a 16-bit texture on CPU is awfully slow currently, because uploading it as a whole in realtime to see the result is way too slow, and won't be an option at all with big terrains. But at the same time, I wonder if it's a good idea to implement sub-rect upload with limited features. I could subdivide the heightmap in plenty of smaller textures (which I might do in the future to support streamed terrains), however I fear that this affects performance...
I could also investigate GPU painting, which would be pretty fast but would limit texture size to renderbuffer size, and I'm not sure if that would work while keeping the same formats I currently use (RH for heights, RGB8 for normals, RGBA8 for splats, R8 for discard).
WDYT @reduz ?


Feature Request: Pachyderm as a new pipeline backend

Currently KF Pipelines and Airflow are supported as runtimes for executing a pipeline. Adding Pachyderm as a 3rd runtime could be very powerful, and allow a data scientist to combine elyra's powerful pipeline editor with pachyderm's ability to combine data and code versioning.

@erikerlandson I’m moving this to the main elyra repo for better visibility/tracking


feat(docs): add gitbook

What this PR does
add skeleton for docs and website
why we need it
for PR of course :-)
Special notes for your reviewer:
pertaining to #39

Coverage remained the same at 63.528% when pulling 430b50b18b3ba4b846fc5f61c01d57f32d1092be on Jimexist:master into 1d9d0fb7d2f440dcd0126fd71fd64d94d9f5666c on caicloud:master.

Coverage remained the same at 63.528% when pulling 430b50b18b3ba4b846fc5f61c01d57f32d1092be on Jimexist:master into 1d9d0fb7d2f440dcd0126fd71fd64d94d9f5666c on caicloud:master.

Coverage remained the same at 63.528% when pulling 66c5524811a163240a692756281d17554b20aecd on Jimexist:master into 1d9d0fb7d2f440dcd0126fd71fd64d94d9f5666c on caicloud:master.

Coverage remained the same at 63.528% when pulling 66c5524811a163240a692756281d17554b20aecd on Jimexist:master into 1d9d0fb7d2f440dcd0126fd71fd64d94d9f5666c on caicloud:master.

Coverage remained the same at 63.528% when pulling 5681d89a20166ff9f1d7c5355acacd3b6b7dda29 on Jimexist:master into 1d9d0fb7d2f440dcd0126fd71fd64d94d9f5666c on caicloud:master.

Coverage remained the same at 63.528% when pulling 715bac08dc60c3b1d44e08cd38928408694bd3b0 on Jimexist:master into 1d9d0fb7d2f440dcd0126fd71fd64d94d9f5666c on caicloud:master.

Coverage remained the same at 63.528% when pulling 715bac08dc60c3b1d44e08cd38928408694bd3b0 on Jimexist:master into 1d9d0fb7d2f440dcd0126fd71fd64d94d9f5666c on caicloud:master.

Coverage remained the same at 63.528% when pulling 715bac08dc60c3b1d44e08cd38928408694bd3b0 on Jimexist:master into 1d9d0fb7d2f440dcd0126fd71fd64d94d9f5666c on caicloud:master.

@ddysher

Are we going to put all docs under website?

.mds under webiste, generated gitbook under /docs so that GitHub pages may pickup


Document GridPaper

cc @HansMuller

LGTM
btw, the name gridpaper is unfortunate because it shows up in autocomplete lists for "grid" and it's rarely what folks trying to autocomplete grid want.

Yeah.


Options and fixes for executing tests on mobile devices via BrowserStack

Test automation on Android and Apple mobile devices via BrowserStack is failing (also with Sauce Lab), and this seems to be about the drivers they use. I have made experiments to determine the why and how to bypass them.
For both Android and Apple:

executing async script is not working, while waiting for a sync script is working. This way, client side scripts calling a callback have to simply return. Apple is simply not responding, Android is telling: "This is feature will be implemented soon"

For Android:

client side scripts have to be one line (and line comments - comment blocks are ok)
client side scripts arguments cannot be null, and that is the case in at least one of them (error message when an argument is null: "Javascript arguments can be a Number, a Boolean, a String, a WebElement, or a List or a Map of those. Got: null")
only javascript locators seem to work properly without saying the locator is invalid
slowness is forcing us to add waiting times

So the issue is about implementing options for prefering sync scripts with wait calls, avoiding null arguments, using javascript locators instead of driver ones, adding default wait time for each command for slow devices, and, adding an option toggling them all to finally enable testing remotely on mobile devices with protractor !

@sjelin anything actionable for us here? I'm not sure what BrowserStack is using for mobile.

I'm going to go ahead and close this since it's been a few years. I hope things have changed enough with drivers.
In the case that this is still an issue, let's start a new one and figure out a game plan for making this actionable.


aws-okta doesn't work with ap-east-1 region

aws-okta exec x -- aws ec2 describe-instances --region ap-southeast-1
{
    "Reservations": []
}

aws-okta exec x -- aws ec2 describe-instances --region ap-east-1

An error occurred (AuthFailure) when calling the DescribeInstances operation: AWS was not able to validate the provided access credentials
exit status 255

Actually this is related to aws-okta. After upgrading all deps it started to work.

Which version were you using? Does the latest version have the same behavior? We just released v0.25.0 4 days ago. Could you try with that version and report back?

Error: error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid
        status code: 403, request id: 3009c0db-efe7-11e9-bd84-ed486c0fc78b

With 0.25.0.

As it turns out, this region, me-south-1 (Bahrain) and all future regions require them to be enabled in your AWS account before they are accessible. Once I enabled this region for an account that we own and waited a bit, things started working. Can you give this a shot?
More info here: https://aws.amazon.com/blogs/aws/now-open-aws-asia-pacific-hong-kong-region/

AWS is changing the default behavior for all new Regions going forward. For new AWS Regions, you will opt in to enable your account to operate in those Regions. This makes it easier for you to select the regions where you can create and manage AWS resources. To prepare for upcoming Region launches, we recommend that you validate the capability to enable and disable AWS Regions to ensure only approved IAM principals can enable and disable AWS Regions for your account.


MultiplexerTransform makes callbacks fire twice

Callbacks fire twice when MultiplexerTransform is added to transforms (dash-extensions 0.0.67).
from dash import html
from dash_extensions.enrich import DashProxy, TriggerTransform, MultiplexerTransform, Trigger, NoOutputTransform
from importlib import reload
import logging

reload(logging)
logging.getLogger('werkzeug')

app = DashProxy(prevent_initial_callbacks=True,
                transforms=[
                    TriggerTransform(),  # enable use of Trigger objects
                    NoOutputTransform(),  # enable callbacks without output
                    MultiplexerTransform(),  # makes it possible to target an output multiple times in callbacks
                ])

app.layout = html.Div([
    html.Button("X", id="x")
])

@app.callback(
    Trigger("x", "n_clicks"),
)
def action():
    app.logger.info("Triggering x...")

if __name__ == "__main__":
    app.run_server(debug=True)

Did you try with debug false?

Yes, the outcome is the same with or without debug mode enabled.

Did you try with debug false?

I looks like an issue with the logger. If I add a print statement to the callbacks,
def action():
    print("Hello world!")
    app.logger.info("Triggering x...")

the output is
<IP_ADDRESS> - - [08/Jan/2022 19:39:21] "GET /_favicon.ico?v=2.0.0 HTTP/1.1" 200 -
Hello world!
Triggering x...
Triggering x...
<IP_ADDRESS> - - [08/Jan/2022 19:39:26] "POST /_dash-update-component HTTP/1.1" 200 -

Hence it looks to me like the callback itself only runs once.


Unwanted messages in the console from HTML report plugin & plugin manager

[Html Report Plugin] : 2015/01/21 14:55:15 Copying '/Users/m/.gauge/plugins/html-report/1.0.1/report-template' -> '/Users/m/Documents/s/f/functional_tests/reports/html-report'
[Html Report Plugin] : Sucessfully generated html reports to => /Users/m/Documents/s/f/functional_tests/reports/html-report
Plugin [Html Report] with pid [87112] has exited

In the above messages, the only one which is required is
[Html Report Plugin] : Sucessfully generated html reports to => /Users/m/Documents/s/f/functional_tests/reports/html-report

Rest everything should be hidden behind some --verbose flag.

Fixed in commit


style/theme: Threat Color Theming and Capacity/Encumbrance Threat coloring

Rename

--t5e-warning-accent-color 👉 --t5e-threat-color
--t5e-warning-accent-contrast-color 👉 --t5e-threat-contrast-color

Utilize these colors for threatening situatons:

Encumbrance exceeded
Capacity exceeded
Attunement exceeded (sun icon and arcane overflow effect)

Pair this upgrade with #207

If you want to integrate this feature I would ask you (if it is not too much work you mean) for some hooks or api to be able to synchronize the Variant Encumbrance module with the configurations chosen by Tidy. Linked to this ticket  https://github.com/kgar/foundry-vtt-tidy-5e-sheets/issues/250

Sure thing. I will keep this front of mind while working on this feature.
It should amount to CSS variables in the end.
Once I get free from my current feature upgrades, I will return full attention to module compatibility and get currency and encumbrance adjusted to play nice with modules.

I'm going to let this one go. The visual overhaul will be a fresh start, and we can go from there.


flyway:filename default placeholder not working repeatable migrations

Which version and edition of Flyway are you using?
flyway-8.5.11 Community Edition
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Yes
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line
Which database are you using? (Type & version)
Oracle 19C
Which operating system are you using?
MacOS
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
We are trying to use the default place holders in repeatable migrations and able to access all default placeholders(defaultSchema, user, database, timestamp, workingDirectory, table ) except  {flyway:filename} . When try to use 'filename' placeholder we get the error as
ERROR: Failed to populate value for default placeholder: ${flyway:filename}
Surprisingly this works from non-repeatable migrations as well as all other callbacks like beforeMigrate, afterMigrate, beforeEachMigrate, afterEachMigration.
I have problem only with 'filename' placeholder in repeatable migrations. Wanted to understand do we have any limitation of this placeholder in repeatable migration?
What did you expect to see?
Expecting to capture current script name.
What did you see instead?
ERROR: Failed to populate value for default placeholder: ${flyway:filename}

Thanks @rgautomatedbuild. Would it be possible to access the filename from beforeEachMigrate?


Clock logo in footer of docs page is messed up

Looks like this is specific to safari, let me check


Fix stricter sibling comment for SQL Injection

The comment referred to the wrong rule ID.

Thank you for spotting (and fixing!) this. Will merge as soon as the tests pass.

Time to merge. Thanks.


Adding support to change loop device number

Some users will find their loop0 device busy, specially if snap is installed and in use. Common in Ubuntu.
This change will take the 2nd argument to change the loop number, default will be 0 if no argument specified.

I just opened an issue for this.  I'm running snap in Ubuntu 20.04.
losetup: QuadBoot.img: failed to set up loop device: Device or resource busy

great! i just ran into this and worked around it by editing the script to use /dev/loop10. same deal, ubuntu 20.04 using snaps for some things.


About scannet

Thank you for your sharing codes. I have downloaded scannet, but found that its intrinsic include intrinsic_depth and intrinsic_color. However, I find the intrinsic for depth is replaced with  the intrinsic for color in code 'make_scannet_dict' . Is it okay to do this?

Hi,
I also downloaded the scannet dataset and it is completely in a different structure format. Did you structure it according to the Dataset Readme for UnsupervisedRR? Were you able to run inference on scannet dataset?

Hey, sorry I missed the issue.
@phdymz Please check issue #2 regarding the intrinsics. To summarize; The difference between the intrinsics is pretty small after preprocessing, so I suspect it wouldn't make a difference, but I didn't properly inspect this.
@ThakurSarveshGit I am curious, what format is it coming in? It should be pretty easy to adapt the dictionary creating code to account for a different structure and define the paths there.