After Latest Update Thermostat Not Reporting Correct Temperature

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
YES, BUT a Home Assistant developer has told me to come here
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
What causes the bug?
When I attempt to change the temperature through the UI it sends the command to the thermostat and the thermostat gets the new temperature but in the UI the temperature is not updated.
What do you observe?
What did you expect to happen?
It to update with the temperature after the thermostat is polled.
Steps to reproduce the behavior:

Go to '...'
Click on '...'
Scroll down to '...'
See error

Go to thermostat +/- temperature watch it update on thermostat but not in the UI or developer tools. It goes back to the temperature it was at before.
Device information
Manufacturer: Honeywell
Model name: T6
Node ID in your network:  79
How are you using node-zwave-js?

[ ] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version: 0.1.66
node-zwave-js branch:
zwavejs2mqtt branch:
Did you change anything?
yes (please describe)
If yes, what did you change?
I updated to the latest version from the version prior.
Did this work before?
Yes (please describe)
If yes, where did it work?
Prior to latest.
Attach Driver Logfile
zwave_js.log (9).txt

At first glance the communication looks good. The driver now uses Supervision for these commands, so no extra verification GET is done. But there's no value update emitted afterwards, so the UI does not update / reverts.

I can't reproduce this. In my tests, the value update is emitted.
2022-08-29T15:29:05.001Z DRIVER » [Node 002] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      4
                                  └─[SupervisionCCGet]
                                    │ session id:      1
                                    │ request updates: true
                                    └─[ThermostatSetpointCCSet]
                                        setpoint type: Cooling
                                        value:         20 °C
2022-08-29T15:29:05.001Z SERIAL « [ACK]                                                                   (0x06)
2022-08-29T15:29:05.002Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-08-29T15:29:05.002Z SERIAL » [ACK]                                                                   (0x06)
2022-08-29T15:29:05.002Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-08-29T15:29:05.012Z SERIAL « 0x010500130400ed                                                     (7 bytes)
2022-08-29T15:29:05.012Z SERIAL » [ACK]                                                                   (0x06)
2022-08-29T15:29:05.013Z DRIVER « [REQ] [SendData]
                                    callback id:     4
                                    transmit status: OK
2022-08-29T15:29:05.024Z SERIAL « 0x010b00040002056c0201ff0067                                        (13 bytes)
2022-08-29T15:29:05.024Z SERIAL » [ACK]                                                                   (0x06)
2022-08-29T15:29:05.025Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[SupervisionCCReport]
                                      session id:          1
                                      more updates follow: false
                                      status:              Success
                                      duration:            0s
2022-08-29T15:29:05.026Z CNTRLR   [Node 002] [+] [Thermostat Setpoint] setpoint[2]: 20

see last line.

A log showing both an attempt with and without S2 could help.

No change in the tests with S2 though:
2022-08-29T15:48:05.285Z DRIVER » [Node 002] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      2
                                  └─[Security2CCNonceGet]
                                      sequence number: 238
2022-08-29T15:48:05.286Z SERIAL « [ACK]                                                                   (0x06)
2022-08-29T15:48:05.286Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-08-29T15:48:05.286Z SERIAL » [ACK]                                                                   (0x06)
2022-08-29T15:48:05.286Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-08-29T15:48:05.301Z SERIAL « 0x010500130200eb                                                     (7 bytes)
2022-08-29T15:48:05.301Z SERIAL » [ACK]                                                                   (0x06)
2022-08-29T15:48:05.301Z DRIVER « [REQ] [SendData]
                                    callback id:     2
                                    transmit status: OK
2022-08-29T15:48:05.311Z SERIAL « 0x011a00040002149f026601f51059586f7253f988d91e26401dce3f9b          (28 bytes)
2022-08-29T15:48:05.312Z SERIAL » [ACK]                                                                   (0x06)
2022-08-29T15:48:05.312Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[Security2CCNonceReport]
                                      sequence number:  102
                                      SOS:              true
                                      MOS:              false
                                      receiver entropy: 0xf51059586f7253f988d91e26401dce3f
2022-08-29T15:48:05.315Z SERIAL » 0x012e001302279f03ef011241f149b15ceb2432e701e627d456424db75fc6858a8 (48 bytes)
                                  3ef96a846c859dda26e282f49250319
2022-08-29T15:48:05.316Z DRIVER » [Node 002] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      3
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 239
                                    │ extensions:
                                    │ · type: SPAN
                                    │   sender EI: 0xf149b15ceb2432e701e627d456424db7
                                    │ key:             0xe5e7972276433d39efaa8e17d39bf726
                                    │ IV:              0xc0d04414caeb68fb40ee4eff64
                                    └─[SupervisionCCGet]
                                      │ session id:      1
                                      │ request updates: true
                                      └─[ThermostatSetpointCCSet]
                                          setpoint type: Cooling
                                          value:         20 °C
2022-08-29T15:48:05.316Z SERIAL « [ACK]                                                                   (0x06)
2022-08-29T15:48:05.317Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-08-29T15:48:05.317Z SERIAL » [ACK]                                                                   (0x06)
2022-08-29T15:48:05.317Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-08-29T15:48:05.329Z SERIAL « 0x010500130300ea                                                     (7 bytes)
2022-08-29T15:48:05.329Z SERIAL » [ACK]                                                                   (0x06)
2022-08-29T15:48:05.329Z DRIVER « [REQ] [SendData]
                                    callback id:     3
                                    transmit status: OK
2022-08-29T15:48:05.339Z SERIAL « 0x011700040002119f036700af04bef5bf29f1035e7ba4c5599d                (25 bytes)
2022-08-29T15:48:05.340Z SERIAL » [ACK]                                                                   (0x06)
2022-08-29T15:48:05.341Z DRIVER « [Node 002] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 103
                                    │ key:             0xe5e7972276433d39efaa8e17d39bf726
                                    │ IV:              0x48f05fbc40907f921e220fb3a3
                                    └─[SupervisionCCReport]
                                        session id:          1
                                        more updates follow: false
                                        status:              Success
                                        duration:            0s
2022-08-29T15:48:05.342Z CNTRLR   [Node 002] [+] [Thermostat Setpoint] setpoint[2]: 20

Again, see last line.

Ohhh, that is SNEAKY! I totally missed this little detail before. This is the device's response to the supervised request:
2022-08-29T21:30:10.576Z DRIVER « [Node 101] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -68 dBm
                                  └─[SupervisionCCReport]
                                      session id:          3
                                      more updates follow: true <------ THIS
                                      status:              Success
                                      duration:            0s

While it clearly says that it is done (Success), it also says that more updates will follow, so Z-Wave JS doesn't treat this report as final.

Nevermind, that was not it either :(

Next version will contain additional "silly" logging. We can repeat the tests then and hopefully get more insight what's going on there.

Uhh, guys, is the set temperature attempt on loglevel "silly" too? This should have added lines like
[setValue] calling SET_VALUE API ThermostatModeCCAPI: ...

I tried to set the temperature, but the thermostat card would not let me because it would not acknowledge that the thermostat was even on.
@Daniel-dev22 Can you turn on heat/ac normally in your thermostat card? I can't even do that in 68 while it works fine in 65.

It seems like 0.1.68 does not output silly logs, even if the dropdown is set to silly. If you can access the container via terminal, you might be able to get the correct logs. If not, this will have to wait until that issue is fixed.

Same situation as @Daniel-dev22.

I have a Honeywell T6 TH6320ZW Thermostat as well and encountering the same problem after I upgraded from 0.1.65 to 0.1.68.  A rollback from a backup did not solve the problem, nor did a re-interview.  My thermostat is on firmware v1.3 if that has any relevance.
Also running HassOS here, but I will try to SSH in and see if I can find the logs mentioned.

2022-09-03T23:52:18.670Z CNTRLR   [Node 042] [setValue] calling SET_VALUE API ThermostatModeCCAPI:                                     property:     mode                                     property key: undefined                                     optimistic:   true 2022-09-03T23:52:18.679Z SERIAL » 0x011a00132a139f03f0004cf35c8dc19ec24cb31d23235f95fb251fb9          (28 bytes) 2022-09-03T23:52:18.680Z DRIVER » [Node 042] [REQ] [SendData]                                   │ transmit options: 0x25                                   │ callback id:      31                                   └─[Security2CCMessageEncapsulation]                                     │ sequence number: 240                                     └─[SupervisionCCGet]                                       │ session id:      12                                       │ request updates: true                                       └─[ThermostatModeCCSet]                                           mode: Off 2022-09-03T23:52:19.197Z SERIAL « [ACK]                                                                   (0x06) 2022-09-03T23:52:19.206Z SERIAL « 0x0104011301e8                                                       (6 bytes) 2022-09-03T23:52:19.208Z SERIAL » [ACK]                                                                   (0x06) 2022-09-03T23:52:19.210Z DRIVER « [RES] [SendData]                                     was sent: true 2022-09-03T23:52:19.237Z SERIAL « 0x011800131f00000300c17f7f7f7f010103000000000201000029              (26 bytes) 2022-09-03T23:52:19.237Z SERIAL » [ACK]                                                                   (0x06) 2022-09-03T23:52:19.238Z DRIVER « [REQ] [SendData]                                     callback id:            31                                     transmit status:        OK, took 30 ms                                     routing attempts:       1                                     protocol & route speed: Z-Wave, 40 kbit/s                                     ACK RSSI:               -63 dBm                                     ACK channel no.:        1                                     TX channel no.:         1 2022-09-03T23:52:19.287Z SERIAL « 0x01190004002a119f030b00fc5915db861f44b56269a157cdbf00c2            (27 bytes) 2022-09-03T23:52:19.288Z SERIAL » [ACK]                                                                   (0x06) 2022-09-03T23:52:19.290Z DRIVER « [Node 042] [REQ] [ApplicationCommand]                                   └─[Security2CCMessageEncapsulation]                                     │ sequence number: 11                                     └─[SupervisionCCReport]                                         session id:          12                                         more updates follow: true                                         status:              Success                                         duration:            0s 2022-09-03T23:52:19.292Z CNTRLR   [Node 042] [setValue] result of SET_VALUE API call for ThermostatModeCCAPI: (S                                   upervisionResult)                                     status:   Success 2022-09-03T23:52:19.293Z CNTRLR   [Node 042] [setValue] updating value with event
I have the same problem. And these are the logs I get if I turn on silly logging. There are setValue in the logs. Let me know if there is anything else that I can help with.

The exactly same problem with Heatit Z-TRM3 thermostat. Not only setting temperature, but switching thermostat On or OFF does the same. There is my silly log, when I set temperature to 16 °C:
zwave_js (1).log

@WizKid any lines below that? It looks like the command was confirmed by the device, and zwave-js would emit a value changed event. But that may be missing or just truncated.

Can you share a node dump? I'm suspecting this is getting filtered out for some reason.

Node dump for node 42: https://gist.github.com/WizKid/8c17b61509ba3b8589e3c414e5e0134b . The file was too big to make a gist out of. So I just edited the file and left just node 42 there.

And here is the silly log for me switching to off and then back to heat. That matches with the events in the node dump: https://gist.github.com/WizKid/c757e4da8f2355f372304b81357c696d

@WizKid you do know that you can just upload files here? Drag&Drop into the textbox, (almost) no size limitation.

looks like I'll need to add even more silly logging

Just need to get WSL to find the zwave USB stick

Unless you have Windows 11, that's not going to work AFAIK.

the software expects an acknowledgement with the new temp setting, but the thermostat is just saying "yeah, I did it".

The thermostat is correct in doing so.  The problem is that zwave-js should use this info and update the value, so UIs can get updated.
This isn't happening, at least not completely and I don't know why yet. I've added silly-level logs to find out in the latest version, so if you could set your logging to "silly" and redo this action you logged above, would be helpful.

Here is my log from a change (changed from 77 to 78F) after setting logging to silly:
2022-09-06T14:33:27.232Z CNTRLR   [Node 008] [setValue] calling SET_VALUE API ThermostatSetpointCCAPI:                                     property:     setpoint                                     property key: 2                                     optimistic:   true 2022-09-06T14:33:27.271Z SERIAL » 0x011c001308159f03fc0025cc2a069085379f021915aef254ebaf682509f3      (30 bytes) 2022-09-06T14:33:27.274Z DRIVER » [Node 008] [REQ] [SendData]                                   │ transmit options: 0x25                                   │ callback id:      9                                   └─[Security2CCMessageEncapsulation]                                     │ sequence number: 252                                     └─[SupervisionCCGet]                                       │ session id:      45                                       │ request updates: true                                       └─[ThermostatSetpointCCSet]                                           setpoint type: Cooling                                           value:         78 °F 2022-09-06T14:33:27.277Z SERIAL « [ACK]                                                                   (0x06) 2022-09-06T14:33:27.280Z SERIAL « 0x0104011301e8                                                       (6 bytes) 2022-09-06T14:33:27.282Z SERIAL » [ACK]                                                                   (0x06) 2022-09-06T14:33:27.283Z DRIVER « [RES] [SendData]                                     was sent: true 2022-09-06T14:33:27.296Z SERIAL « 0x010500130900e0                                                     (7 bytes) 2022-09-06T14:33:27.297Z SERIAL » [ACK]                                                                   (0x06) 2022-09-06T14:33:27.299Z DRIVER « [REQ] [SendData]                                     callback id:     9                                     transmit status: OK 2022-09-06T14:33:27.344Z SERIAL « 0x011700040008119f039c00fbdde461ffde1d1d442695294fe6                (25 bytes) 2022-09-06T14:33:27.352Z SERIAL » [ACK]                                                                   (0x06) 2022-09-06T14:33:27.356Z DRIVER « [Node 008] [REQ] [ApplicationCommand]                                   └─[Security2CCMessageEncapsulation]                                     │ sequence number: 156                                     └─[SupervisionCCReport]                                         session id:          45                                         more updates follow: true                                         status:              Success                                         duration:            0s 2022-09-06T14:33:27.365Z CNTRLR   [Node 008] [setValue] result of SET_VALUE API call for ThermostatSetpointCCAPI                                   : (SupervisionResult)                                     status:   Success 2022-09-06T14:33:27.366Z CNTRLR   [Node 008] [setValue] updating value with event 2022-09-06T14:33:27.368Z CNTRLR   [Node 008] [translateValueEvent: value updated]                                     commandClass: Thermostat Setpoint                                     endpoint:     0                                     property:     setpoint                                     propertyKey:  2                                     internal:     false                                     secret:       false                                     event source: driver 2022-09-06T14:33:27.369Z CNTRLR   [Node 008] [translateValueEvent: value updated]                                     is root endpoint:        true                                     is application CC:       true                                     should hide root values: false

Pro tip: paste the log, then select it and press the <> button.

Okay, according to your log, the value update should actually happen, it just doesn't get logged like those that actually come from the device.

Is it working for the addon?

I'm not 100% sure. A test would be good, although the latest log looks like the driver is working as intended.
Would also be good to know if the UI gets updated correctly when you're using the zwavejs2mqtt addon (in the addon UI)

no need for an interview now, just the silly logs including the [translateValueEvent: lines are enough.
Having a 1:1 comparison of the same setup in z2m and the official addon would be good to narrow the issue down though. Here's how switching works: https://www.home-assistant.io/integrations/zwave_js#can-i-switch-between-the-official-z-wave-js-add-on-and-zwavejs2mqtt

@AlCalzone Here are the silly logs when I change mode from Off to Heat https://gist.github.com/WizKid/50447f64401a5a08f9f41ba9d207f21d . And I see translateValueEvent but I have no idea what it means.
I also got the USB stick to work in WSL so I can do more debugging without you having to release new versions if that is useful

Thanks, that matches what I was seeing in my tests and confirms that the driver should be working as intended. Meaning the issue is either in zwave-js-server or the HA addon(s).

Enable debug logging for zwave-js in HA, and that will show if HA ever receives the event from the driver or not.
Either in configuration.yaml (requires a restart):
logger:
  default: info
  logs:
    homeassistant.components.zwave_js: debug
    zwave_js_server: debug

Or enable at runtime with a service call:
service: logger.set_level
data:
  homeassistant.components.zwave_js: debug
  zwave_js_server: debug

In my own experiment, I see events for a thermostat device are different from other devices. Here is the optimistic value report for setting the thermostat mode to Heat:
2022-09-06 09:19:41.834 DEBUG (MainThread) [zwave_js_server] Received message:
WSMessage(type=<WSMsgType.TEXT: 1>, data='{"type":"event","event":{"source":"node","event":"value updated","nodeId":11,"args":{"commandClassName":"Thermostat Mode","endpoint":0,"commandClass":64,"property":"mode","propertyName":"mode","ccVersion":2,"metadata":{"type":"number","readable":true,"writeable":true,"min":0,"max":255,"states":{"0":"Off","1":"Heat","2":"Cool","3":"Auto","11":"Energy heat","12":"Energy cool"},"label":"Thermostat mode"},"value":0,"newValue":1,"prevValue":0}}}', extra='')

2022-09-06 09:19:41.834 DEBUG (MainThread) [homeassistant.components.zwave_js] [climate.z_wave_thermostat] Value mode/None changed to: 0

There is both a "value" and a "newValue". HA isn't expecting this, so the newValue is overwritten with the old one, so instead of Heat it reverts to Off. My old thermostat doesn't use Supervision, so there's a 5-second post refresh that corrects the state. I confirmed this event format exists in v9.6.2 as well, so it's always been an issue. I'm guessing the update in v10 to use Supervision in more CCs has revealed this.
Here is an event for a dimmer switch, notice there's no old "value", so HA doesn't set the wrong state:
2022-09-06 10:06:58.579 DEBUG (MainThread) [zwave_js_server] Received message:
WSMessage(type=<WSMsgType.TEXT: 1>, data='{"type":"event","event":{"source":"node","event":"value updated","nodeId":14,"args":{"commandClassName":"Multilevel Switch","commandClass":38,"property":"currentValue","endpoint":0,"newValue":47,"prevValue":47,"propertyName":"currentValue"}}}', extra='')

2022-09-06 10:06:58.580 DEBUG (MainThread) [homeassistant.components.zwave_js] [light.in_wall_dimmer_switch_2] Value currentValue/None changed to: 47

In v10 (not v9), I also see duplicate value update events for the refresh:
2022-09-06 09:19:48.189 DEBUG (MainThread) [zwave_js_server] Received message:
WSMessage(type=<WSMsgType.TEXT: 1>, data='{"type":"event","event":{"source":"node","event":"value updated","nodeId":11,"args":{"commandClassName":"Thermostat Mode","commandClass":64,"property":"mode","endpoint":0,"newValue":1,"prevValue":1,"propertyName":"mode"}}}', extra='')

2022-09-06 09:19:48.190 DEBUG (MainThread) [homeassistant.components.zwave_js] [climate.z_wave_thermostat] Value mode/None changed to: 1
2022-09-06 09:19:48.192 DEBUG (MainThread) [zwave_js_server] Received message:
WSMessage(type=<WSMsgType.TEXT: 1>, data='{"type":"event","event":{"source":"node","event":"value updated","nodeId":11,"args":{"commandClassName":"Thermostat Mode","commandClass":64,"property":"mode","endpoint":0,"newValue":1,"prevValue":1,"propertyName":"mode"}}}', extra='')

2022-09-06 09:19:48.192 DEBUG (MainThread) [homeassistant.components.zwave_js] [climate.z_wave_thermostat] Value mode/None changed to: 1

Silly driver logs:
2022-09-06T16:35:23.664Z SERIAL » 0x010e00a9010b02400225000000000730                                  (16 bytes)
2022-09-06T16:35:23.664Z DRIVER » [Node 011] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      7
                                  └─[ThermostatModeCCGet]
2022-09-06T16:35:23.670Z SERIAL « [ACK]                                                                   (0x06)
2022-09-06T16:35:23.671Z SERIAL « 0x010401a90152                                                       (6 bytes)
2022-09-06T16:35:23.672Z SERIAL » [ACK]                                                                   (0x06)
2022-09-06T16:35:23.672Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2022-09-06T16:35:24.872Z SERIAL « 0x011d00a90700007500ba7f7f7f7f01010300000000420100007f7f7f7f7fbc    (31 bytes)
2022-09-06T16:35:24.873Z SERIAL » [ACK]                                                                   (0x06)
2022-09-06T16:35:24.874Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            7
                                    transmit status:        OK, took 1170 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    ACK RSSI:               -70 dBm
                                    ACK channel no.:        1
                                    TX channel no.:         1
                                    beam:                   1000 ms
2022-09-06T16:35:25.124Z SERIAL « 0x010c00a800010b0340030100baaa                                      (14 bytes)
2022-09-06T16:35:25.125Z SERIAL » [ACK]                                                                   (0x06)
2022-09-06T16:35:25.126Z CNTRLR   [Node 011] [translateValueEvent: value updated]
                                    commandClass: Thermostat Mode
                                    endpoint:     0
                                    property:     mode
                                    propertyKey:  undefined
                                    internal:     false
                                    secret:       false
                                    event source: undefined
2022-09-06T16:35:25.126Z CNTRLR   [Node 011] [~] [Thermostat Mode] mode: 1 => 1                     [Endpoint 0]
2022-09-06T16:35:25.126Z CNTRLR   [Node 011] [translateValueEvent: value updated]
                                    is root endpoint:        true
                                    is application CC:       true
                                    should hide root values: false
2022-09-06T16:35:25.129Z CNTRLR   [Node 011] [translateValueEvent: value updated]
                                    commandClass: Thermostat Mode
                                    endpoint:     0
                                    property:     mode
                                    propertyKey:  undefined
                                    internal:     false
                                    secret:       false
                                    event source: undefined
2022-09-06T16:35:25.129Z CNTRLR   [Node 011] [~] [Thermostat Mode] mode: 1 => 1                     [Endpoint 0]
2022-09-06T16:35:25.130Z CNTRLR   [Node 011] [translateValueEvent: value updated]
                                    is root endpoint:        true
                                    is application CC:       true
                                    should hide root values: false
2022-09-06T16:35:25.132Z DRIVER « [Node 011] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -70 dBm
                                  └─[ThermostatModeCCReport]
                                      mode: Heat

see here: https://github.com/home-assistant/core/issues/77579#issuecomment-1238455958
This PR fixes the issue: https://github.com/home-assistant-libs/zwave-js-server-python/pull/480

fixed downstream in Home Assistant 2022.9.0


Very Basic Android Support

So far, only example 00 is working.
We still need to finish configuring the tools to load the shader.
:)

Hi there, really sorry I missed responding to this earlier 🙈
It looks like there's a new official fork for bgfx.cmake here - https://github.com/bkaradzic/bgfx.cmake so it might be worth opening a PR against that fork instead of this one (I'm going to try and switch to that one and then archive/delete this fork as it should no longer be needed).
Thanks!
Tom


[bug]: Tapd fails to start if minter doesn't have funds

Description
Currently if a batch is created and a funding is attempted but no sufficient funds are available, tapd will terminate with an error related to not enough funds being available.
Upon restarting this error will immediately surface again and stop the daemon from starting up normally. See logs below
            "error":  "unable to initialize RPC server: unable to start asset minter: unable to fund minting PSBT for batch:
036d76af505d9443a303e8991b53a00f29199dd2aafba27e2f03112beebe0c1521 unable to fund psbt: unable to fund psbt: rpc
error: code = Unknown desc = error selecting coins: fee 0.00007700 BTC on total output value 0.00014115 BTC",

Solution
We could reduce this to just be an ERR level log, or revert the funding of the batch / cancel it

Cancel sounds reasonable since the node operator could fund the backing wallet and then resubmit; daemon def shouldn't shut down if funding fails, will look into downgrading overall severity of the error.


updated exploit scripts for challenges from ctf's of 2015,2016

Updated exploits to use log,fit,flat,map
Could not find shellcode of required length in shellcraft module.

I think you issued this PR against the wrong repo.


Moving 'rendered += suggestions.length;' down by 1 line

Bumping version number to 0.11.2

Looks good!
+1


Reworked module loading:

Added support for transitive dependencies in the ModuleLoader.

This should merge ;3

MY BAD


Expose stdout/stderr in Session

This PR:

Makes explicit the notion that 0=stdin, 1=stdout, 2=stdout in the QueryCallback's "FS"
Exposes the outputs in Session
Removes printing to stdout and stderr in the callback itself. This is now the responsibility of the host if needed.
Adds the Fibonacci test with stdout to CI using the write mechanism

The idea is that after this we should also expose the proof's publics and make a stream mechanism for inputs and outputs

Also, what do we do about our runtime::print? it won't print anymore right?

Also, what do we do about our runtime::print? it won't print anymore right?

we can print it in the test

Also, what do we do about our runtime::print? it won't print anymore right?

we can print it in the test

i mean, won't it be confusing to users that runtime::print does nothing?

ahhh runtime print, sorry I confused with the test. Yea true... let me think about it

I removed it from the queue again because somehow the newly added Fibonacci RISCV test (as an example) is running in every job, instead of in one.


SVGs are pre-viewable, but not viewable

It seems SVGs can be correctly pre-viewed, but not correctly viewed.
Example:
Photos/albums pre-view:

View of first image:

View of second image:

There's a tint applied for svgs on view, that was intended for
monochromatic svgs like icons to be tinted from Black to White in order to
be visible, but I guess it's not worth it as the colored svgs are broken.
I will revert the tint change asap
On Wed, Apr 19, 2023, 11:49 PM Julian @.***> wrote:

It seems SVGs can be correctly pre-viewed, but not correctly viewed.
Example:
Photos/albums pre-view:
[image: IMG_20230419_224540]
https://user-images.githubusercontent.com/43753131/233196096-74d2edea-f9f1-4157-9241-cc7366ce5f68.jpg
View of first image:
[image: Screenshot_20230419-224430]
https://user-images.githubusercontent.com/43753131/233196508-458a63cf-9674-4299-be01-2248874ace6d.png
View of second image:
[image: Screenshot_20230419-224434]
https://user-images.githubusercontent.com/43753131/233196696-483aaab6-8d00-42df-a601-7875b19ed27a.png
—
Reply to this email directly, view it on GitHub
https://github.com/IacobIonut01/Gallery/issues/35, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AETKYGZZR5NXVOPAFXVBTELXCBFVZANCNFSM6AAAAAAXES54TA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

The fix is pushed to the repo, you can download the apk manually from Github Actions or wait for the weekly release


Exalted 3e Sheet

Updated the sheet to 2.1. See commits for more details.
Kindly merge this the same time as you merge the pull request I made with the API repository, as the script I updated had to be modified to remove hard-coded restrictions enforced by this sheet.

It looks like your branch was out of date when you submitted this pull request, which has resulted in a lot of conflicts which are preventing me from merging.
These conflicts will need to be resolved, the simplest way to do this may be to delete your branch and then create a new fork. This will make sure everything is completely up to date. Then, re-apply your changes and submit a new pull request. If this doesn't make sense, let me know and I'd be happy to help.
Also, how will these changes affect current users of the sheet? Mostly we're concerned about changing or removing attribute names. Normally I would glance through the commit to check for this but your changes are difficult to look through quickly.

The changes will not affect  current players. Previously, the attribute 'peripheral-essence_max' and 'personal-essece_max' were hard coded to '@{essence} * 7 + 26' and '@{essence} * 3 + 10' respectively. This update changes these attributes to @{personal-equation} and @{peripheral-equation}, which are editable and by default set to the previously hard coded values.
There is also a worker script that changes the equation attributes, however it is only set to run when the attribute 'caste' is changed.
I think I get what you mean. I'll get around to submitting a new pull request with no conflicts. Thanks for the help!


Filter modifications: Activate filter by clicking anywhere in the territory of the space; Filter 2 converted to a “New Tab” type button; “Filter 1” removed – everything replaced by pluses

Left: "Filter 1"
Right: "+" ?

Done


No products being returned after implementing http request

Just completed the Retrieving Data using HTTP module and no products are being returned in the product list. Getting a 404 "Cannot get /null" error in the browser console. No errors being indicated in VS code.

Silly error on my part. fixed.

Glad you resolved it!

Me too!
The error was in this line of my service class:
private _productUrl: 'api/products/products.json';
since the above is valid TS, it wasn't cluing me in to the fact that i need an = operator to properly assign the path to the variable.
Thanks again for your responsiveness and your work on the course.


OpenSSL 1.1.1e version BN_CTX_free -> "segmentation fault"

BN_CTX_new
BN_CTX_start
BN_CTX_get(ctx)
... ...
many times
BN_CTX_end
BN_CTX_free
and then, when I call BN_CTX_free(ctx), It will occure "segmentation fault".
but this same code will work on 1.0.2 version very well.
what's wrong with me?

Just like:

and then, I call the BN_new instead of BN_CTX_get function
It work properly, do not "segmentation fault" again.
thank you

This pattern should be working, and is used extensively both in the library code and in tests.
Can you provide a minimal working example to reproduce the segmentation fault?

I am not sure, because it is a part of big soafeware
it is hard to spun off

sorry, I made a mistake.
I call "BN_free" after "BN_CTX_get"
such as:
b = BN_CTX_get();
BN_free(b); // this should not be called

so I got the "segmentation fault".

Do not call BN_free; BN's are released when the context is free'd.


InvalidOperationException on SelectList

The example code, as written with the exception of a namespace difference yields the following error:
InvalidOperationException: Could not create an instance of type 'Microsoft.AspNetCore.Mvc.Rendering.SelectList'. Model bound complex types must not be abstract or value types and must have a parameterless constructor. Alternatively, set the 'Genres' property to a non-null value in the 'vsWebApp.Pages.Movies.IndexModel' constructor.

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

ID: cc54dbf8-e6fe-a212-b2cd-c015a6ba5439
Version Independent ID: b96b0b44-3e3a-a6c2-6b2b-c7bab4b78f0d
Content: Add search to ASP.NET Core Razor Pages
Content Source: aspnetcore/tutorials/razor-pages/search.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

The code works. You might want to test the download.

I mistakenly left a [BindProperty] annotation on the Genres property of SelectList type. Problem solved.


React 16 support & Babel plugin hotfix

Use prop-types external package instead of deprecated React.PropTypes.
Renamed babel plugin to check-es2015-constants

+1

+1

@jeremyeaton89 can you take a look as part of our upgrade process?

+1

@brunocascio Can we have the dependency as
 "prop-types": "*"

instead of hard coding the version?

@joonhocho The version is not hardcoded. It is using ^X.Y.Z

any plans on merging this soon?

0.0.19 live: https://www.npmjs.com/package/react-native-parsed-text

awesome! thanks @bleonard


AzureSpatialAnchors.dll | FileNotFoundException Build Error

ASA: 2.11.0
MRTK: 2.7.2
Unity: 2020.3.26f1
AR Foundation: 4.2.2
MR OpenXR Plugin: 1.2.1
OpenXR Plugin: 1.3.1
Trying to build for UWP results in the following error:
FileNotFoundException: Packages/com.microsoft.azure.spatial-anchors-sdk.windows/Plugins/ARM/AzureSpatialAnchors.dll does not exist
System.IO.File.Copy (System.String sourceFileName, System.String destFileName, System.Boolean overwrite) (at <695d1cc93cca45069c528c15c9fdd749>:0)
PostProcessWinRT.CopyFileWithDebugSymbols (System.String source, System.String target, System.Boolean isFileManagedAssembly) (at C:/buildslave/unity/build/PlatformDependent/MetroPlayer/Extensions/Managed/PostProcessWinRT.cs:599)
PostProcessWinRT.CopyPlugins () (at C:/buildslave/unity/build/PlatformDependent/MetroPlayer/Extensions/Managed/PostProcessWinRT.cs:909)
PostProcessWinRT.Process () (at C:/buildslave/unity/build/PlatformDependent/MetroPlayer/Extensions/Managed/PostProcessWinRT.cs:164)
UnityEditor.UWP.BuildPostprocessor.PostProcess (UnityEditor.Modules.BuildPostProcessArgs args) (at C:/buildslave/unity/build/PlatformDependent/MetroPlayer/Extensions/Managed/ExtensionModule.cs:86)
Rethrow as BuildFailedException: Exception of type 'UnityEditor.Build.BuildFailedException' was thrown.
UnityEditor.UWP.BuildPostprocessor.PostProcess (UnityEditor.Modules.BuildPostProcessArgs args) (at C:/buildslave/unity/build/PlatformDependent/MetroPlayer/Extensions/Managed/ExtensionModule.cs:90)
UnityEditor.Modules.DefaultBuildPostprocessor.PostProcess (UnityEditor.Modules.BuildPostProcessArgs args, UnityEditor.BuildProperties& outProperties) (at <55729f52d042492e9efc384182ae2feb>:0)
UnityEditor.PostprocessBuildPlayer.Postprocess (UnityEditor.BuildTargetGroup targetGroup, UnityEditor.BuildTarget target, System.String installPath, System.String companyName, System.String productName, System.Int32 width, System.Int32 height, UnityEditor.BuildOptions options, UnityEditor.RuntimeClassRegistry usedClassRegistry, UnityEditor.Build.Reporting.BuildReport report) (at <55729f52d042492e9efc384182ae2feb>:0)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)

Have you enabled LFS for Git before clone the repo?
https://github.com/microsoft/OpenXR-Unity-MixedReality-Samples#welcome
⚠ NOTE : This repository uses Git Large File Storage to store large files, such as Unity packages and images. Please install the latest git-lfs before cloning this repo.

@yl-msft I had downloaded it through github.com, cloning with git did resolve that error but now I am getting the following error when running in VS. After successfully exporting out of Unity, when the app runs, it crashes with
Unhandled exception at 0x00007FF8122EED58 (GameAssembly.dll) in OpenXR-Unity-ASASample.exe: 0xC0000005: Access violation reading location 0x000000000015000A.

After recreating a new project this issue seems to be resolved so it likely had something to do with the specific project and the original issue was that I downloaded the zip rather than git clone


Collect events from monitoring namespace if MonitoringTest fails

Also made all_events log capture a UTC timestamp too.

@enmasse-ci run tests testcase=**.MonitoringTest


feat(icon): add gleam icon

Adds icons for Gleam including .gleam files and gleam.toml (config file)
Changes proposed:

[x] Add
[ ] Delete
[ ] Fix
[ ] Prepare

Was about to add it, nice <3


Bug fixes+changes

If you would like to use owner commands like detailedeval,eval,deployslash, instead of going to the commands and changing Tomato's ID, it will use the first owner ID in the array in config.json, to decide whether the user is allowed to run the command or not
it was a simple change but bcoz i saw someone made an issue on it i thought it would have been useful to add this
Also fixed setup-boostlog (hopefully, coz i cant test it)
and i did more stuff but i am not bothered to explain, just read the commit messages lol

@Tomato6966

Reason: ReferenceError: guild is not defined at first_layer (/home//_/commands/👑 Owner/setup-serverlog.js:41:46) at Object.run (/home///commands/👑 Owner/setup-serverlog.js:37:9) at module.exports (/home///events/guild/messageCreate.js:295:17) at Client.emit (node:events:402:35) at MessageCreateAction.handle (/home//__/node_modules/discord.js/src/client/actions/MessageCreate.js:26:14) at Object.module.exports [as MESSAGE_CREATE] (/home/_/***/node_modules/discord.js/src/client/websocket/handlers/MESSAGE_CREATE.js:4:32) at WebSocketManager.handlePacket (/home///node_modules/discord.js/src/client/websocket/WebSocketManager.js:351:31) at WebSocketShard.onPacket (/home///node_modules/discord.js/src/client/websocket/WebSocketShard.js:444:22) at WebSocketShard.onMessage (/home///node_modules/discord.js/src/client/websocket/WebSocketShard.js:301:10) at WebSocket.onMessage (/home///node_modules/ws/lib/event-target.js:199:18) at WebSocket.emit (node:events:390:28) at Receiver.receiverOnMessage (/home///node_modules/ws/lib/websocket.js:1098:20) at Receiver.emit (node:events:390:28) at Receiver.dataMessage (/home///node_modules/ws/lib/receiver.js:528:14) at Receiver.getData (/home///node_modules/ws/lib/receiver.js:446:17) at Receiver.startLoop (/home///node_modules/ws/lib/receiver.js:148:22) at Receiver._write (/home///node_modules/ws/lib/receiver.js:83:10) at writeOrBuffer (node:internal/streams/writable:389:12) at _write (node:internal/streams/writable:330:10) at Receiver.Writable.write (node:internal/streams/writable:334:10) at TLSSocket.socketOnData (/home///node_modules/ws/lib/websocket.js:1192:35) at TLSSocket.emit (node:events:390:28)

How did you get access to that setup-serverlog command?
That was accidentally added by me i was testing something, and its deleted now

Reason: ReferenceError: guild is not defined at first_layer (/home//**_/commands/👑 Owner/setup-serverlog.js:41:46) at Object.run (/home///commands/👑 Owner/setup-serverlog.js:37:9) at module.exports (/home///events/guild/messageCreate.js:295:17) at Client.emit (node:events:402:35) at MessageCreateAction.handle (/home//__/node_modules/discord.js/src/client/actions/MessageCreate.js:26:14) at Object.module.exports [as MESSAGE_CREATE] (/home/_/*****/node_modules/discord.js/src/client/websocket/handlers/MESSAGE_CREATE.js:4:32) at WebSocketManager.handlePacket (/home///node_modules/discord.js/src/client/websocket/WebSocketManager.js:351:31) at WebSocketShard.onPacket (/home///node_modules/discord.js/src/client/websocket/WebSocketShard.js:444:22) at WebSocketShard.onMessage (/home///node_modules/discord.js/src/client/websocket/WebSocketShard.js:301:10) at WebSocket.onMessage (/home///node_modules/ws/lib/event-target.js:199:18) at WebSocket.emit (node:events:390:28) at Receiver.receiverOnMessage (/home///node_modules/ws/lib/websocket.js:1098:20) at Receiver.emit (node:events:390:28) at Receiver.dataMessage (/home///node_modules/ws/lib/receiver.js:528:14) at Receiver.getData (/home///node_modules/ws/lib/receiver.js:446:17) at Receiver.startLoop (/home///node_modules/ws/lib/receiver.js:148:22) at Receiver._write (/home///node_modules/ws/lib/receiver.js:83:10) at writeOrBuffer (node:internal/streams/writable:389:12) at _write (node:internal/streams/writable:330:10) at Receiver.Writable.write (node:internal/streams/writable:334:10) at TLSSocket.socketOnData (/home///node_modules/ws/lib/websocket.js:1192:35) at TLSSocket.emit (node:events:390:28)

How did you get access to that setup-serverlog command? That was accidentally added by me i was testing something, and its deleted now

its not deleted

Reason: ReferenceError: guild is not defined at first_layer (/home//**_/commands/👑 Owner/setup-serverlog.js:41:46) at Object.run (/home///commands/👑 Owner/setup-serverlog.js:37:9) at module.exports (/home///events/guild/messageCreate.js:295:17) at Client.emit (node:events:402:35) at MessageCreateAction.handle (/home//__/node_modules/discord.js/src/client/actions/MessageCreate.js:26:14) at Object.module.exports [as MESSAGE_CREATE] (/home/_/*****/node_modules/discord.js/src/client/websocket/handlers/MESSAGE_CREATE.js:4:32) at WebSocketManager.handlePacket (/home///node_modules/discord.js/src/client/websocket/WebSocketManager.js:351:31) at WebSocketShard.onPacket (/home///node_modules/discord.js/src/client/websocket/WebSocketShard.js:444:22) at WebSocketShard.onMessage (/home///node_modules/discord.js/src/client/websocket/WebSocketShard.js:301:10) at WebSocket.onMessage (/home///node_modules/ws/lib/event-target.js:199:18) at WebSocket.emit (node:events:390:28) at Receiver.receiverOnMessage (/home///node_modules/ws/lib/websocket.js:1098:20) at Receiver.emit (node:events:390:28) at Receiver.dataMessage (/home///node_modules/ws/lib/receiver.js:528:14) at Receiver.getData (/home///node_modules/ws/lib/receiver.js:446:17) at Receiver.startLoop (/home///node_modules/ws/lib/receiver.js:148:22) at Receiver._write (/home///node_modules/ws/lib/receiver.js:83:10) at writeOrBuffer (node:internal/streams/writable:389:12) at _write (node:internal/streams/writable:330:10) at Receiver.Writable.write (node:internal/streams/writable:334:10) at TLSSocket.socketOnData (/home///node_modules/ws/lib/websocket.js:1192:35) at TLSSocket.emit (node:events:390:28)

How did you get access to that setup-serverlog command? That was accidentally added by me i was testing something, and its deleted now

its not deleted

Check my branch, it is

I already fixxed all of those bugs before in the script.
except the typos
aka i will upload them in the next major update v11.0
When i finished the Sharded Version with MONGODB SUPPORT

But thanks for your effort jedd!

If u want fixxes, tell them to me on discord

imma keep it open, so i dont forget!

okay

I already fixxed all of those bugs before in the script. except the typos
aka i will upload them in the next major update v11.0
When i finished the Sharded Version with MONGODB SUPPORT

when will this version be ready?

okay

@jedddg  The fixes has been put on tomato's main branch?

these changes have not been made yet.

the fatal boostlog bug still occurs
owner commands require going into the commands and configuring it custom


Feature request: LaTeX equation rendering

Currently, if I include a LaTeX equation in my markdown, it is just rendered as plain text. I believe that most flavours of Markdown actually support LaTeX equations by default and it would be great to have this feature in this Markdown reader as well.

+1!

https://chrome.google.com/webstore/detail/markdown-reader/gpoigdifkoadgajcincpilkjmejcaanc
Done!


离线ASR进度卡住

2024-04-25 00:56:30,709 - modelscope - INFO - PyTorch version 2.0.0+cu118 Found.
2024-04-25 00:56:30,711 - modelscope - INFO - Loading ast index from C:\Users\Admin.cache\modelscope\ast_indexer
2024-04-25 00:56:30,838 - modelscope - INFO - Loading done! Current index file version is 1.10.0, with md5 dc0c9ee702463555275a41f8a2fb65fe and a total number of 946 components indexed
2024-04-25 00:56:31,200 - modelscope - INFO - Use user-specified model revision: v2.0.4
Downloading:   0%|                                                                          | 0.00/840M [00:00<?, ?B/s]2024-04-25 00:59:36,429 - modelscope - WARNING - Download file from: 167772160 to: 335544319 failed, will retry

看样子是网不好

我也是这个问题，很早就有了

我也有这个问题，卡在这里没有进度


Fix encrypt check

Coverage remained the same at 94.32% when pulling 0b058d65c6bb62ccd1ab29ed10c118945cf9efaa on JDonadio:fix/encrypted into 2f7cecfaf09fb9e56d9ee68e20db0c43b71ab33e on bitpay:master.

Coverage increased (+0.01%) to 94.333% when pulling 95e8fb4e66bed80c9054a64bb3cc02848d13bfdf on JDonadio:fix/encrypted into 2f7cecfaf09fb9e56d9ee68e20db0c43b71ab33e on bitpay:master.


JSON Stringify Operation

Accepts a JSON string, parses it and then stringifies it.
Closes #977

Hey @n1073645, I'm pretty sure this functionality is identical to "JSON Minify" operator and thus I'm going to close this PR.  The original PR seems to primarily be talking about JS -> JSON conversion.


Closure of One Call API 2.5

What happened?
OpenWeather announced last week that they would be closing their One Call API 2.5 in June 2024, and replacing it with One Call API 3.0.
What does this mean?
Because WxCenter relies on One Call API 2.5 for international forecasts, it will no longer be able to retrieve forecast data for international locations starting sometime in June of 2024.
More info here: https://openweathermap.org/one-call-transfer
Resolving this issue is more complicated than simply pointing WxCenter to the new 3.0 API URL. The 3.0 API has a new subscription model which, while still including 1,000 free API calls per day, now also charges an overage per call made, which requires a method of payment in order to use.
What are our options?
The way I see it, there are at least 3 ways a sysop can choose to address this issue:

Minimal effort: If you run a U.S. based BBS and your users are primarily also U.S. based, then perhaps you don't care about international forecasts. If this describes you, your board, and your users, then simply edit your wxcenter.ini file and make sure preferredSource is set to WDG, useOtherSourceOnFail is set to false, and remove the owmApiKey value. This will make WxCenter get its data from Weather.gov only.

Moderate effort: Perhaps you don't mind OpenWeather's updated subscription model, in which case you can follow the guide in the link above to migrate to One Call API 3.0. Once you've completed the migration, you will need to update the API URL in wxcenter.js on line 32: https://github.com/codefenix-ConChaos/WxCenter/blob/4f839899fc56d91acd1d2ad4469dc0d0dd688314/wxcenter.js#L32
Change it to:
const OWM_API_URL = "https://api.openweathermap.org/data/3.0/onecall?lat=%s&lon=%s&units=%s&appid=%s&exclude=minutely,hourly"; In other words, change "2.5" to "3.0". WxCenter should continue to work as it currently does.

High effort: If you're an experienced JavaScript programmer, fork the project and rework WxCenter to your liking, perhaps making use of another API like Weatherapi.com instead. You could use the getForecastFromOneCallApi function as a template for designing a new function. I won't go into further detail on how to accomplish this.

Maybe you're even thinking of your own solution as you read this. There are no wrong answers.
Final words
I am no longer working on this project or any other BBS-adjacent things at the moment, so I will not be committing a permanent fix for this issue myself. In my opinion, the updated subscription model kills the "free" spirit of the project, as well as any interest I had in continuing it.
I am posting this issue so that when One Call API 2.5 closes in June 2024, sysops will be aware of the cause of the problem and how to address it. If anyone creates a new issue for this problem, I will close it and link to this one.
It's unfortunate that OpenWeather decided to update their subscription model, but such is the nature of all projects which rely on APIs. This is similar to what ended up killing the syncWXremix  project, and this is the second time that an API change was disruptive to the WxCenter project.
I enjoyed working on this project while I did, and I was happy to share it here on Git.
Thanks and good luck!

I absolutely love what you were able to accomplish with WxCenter. I haven't been able to keep up with the BBS scene for a while now, but when I saw this come across my email, I thought about something I ran into a little while back.
Visual Crossing apparently has a plan that allows for 1000 API calls a day, for free, without any need for a credit card.
https://www.visualcrossing.com/resources/blog/replacing-the-weather-underground-api/
(the replacing weather underground bit was especially interesting to me because that's what ran syncWXremix)
I am not sure how good of a fit this API would be, as I have not looked into the code too much, but I wanted to drop a quick line about it, just in case it was helpful.
Thanks so much for the hard work on this app/door, codefenix!


Update manager/config/samples

manager/config/samples does not contain the latest yaml versions of M4D CRDs.

I don't think that we need it

OK. Let's delete them then.


Update sk.coffee

Translation of tips II

@nwinter, can you merge this pull request?

Thanks @cundamic!


[fix] remove rfkill switch support

Fix #174
The previous fix(0af3d0d) of disabling rfkill-input does not work anymore, this results in the wifi device turning off when starting swhkd.

CC: @zubairmh Thoughts?

CC: @zubairmh Thoughts?

Maybe it's better to make it optional to keep support on distros that need it?

We

CC: @zubairmh Thoughts?

Maybe it's better to make it optional to keep support for distros that need it?

Most distro's seem to be unaffected, if someone is able to confirm that their distro is affected then it might be considerable.
It also seems inconsistent to have rfkill switch support for one distro and not for others

Artix, Arch and Fedora are from my experience, affected. Since most of the major distros are facing issues due to the previous changes, I would like to see this merged.
Does that sound acceptable? CC: @id3v1669

Just tested on 3 distros:

Distro
wifi dies with rfkill
wifi dies without rfkill

Opensuse(Tumbleweed)
+
+

NixOS(unstable)
-
+

Debian 12
-
+

If your tests show that other distros are not affected by removing rfkill, it's ok to merge.
For nix I'll add rfkill support in packaging as a patch.
Debian users are not realy the audience for swhkd, so doesn't matter.
Opensuses' wifi gets killed with and without rfkill , so doesn't matter too.

Hey, @id3v1669
I'm having trouble understanding the table. Does the second column mean that wifi dies even after removing SW_RFKILL_ALL from the list of switches?

Hey, @id3v1669 I'm having trouble understanding the table. Does the second column mean that wifi dies even after removing SW_RFKILL_ALL from the list of switches?

Yes, second column mean that wifi dies even after removing 'SW_RFKILL_ALL'.
No idea why that is happening, but on different devices I've got different behavior with same configuration.


Feat/Numerical Field

Numerical field
This PR display localised numbers for numerical fields, according to the defined numerical inputs rules from the design system.
When the user is typing, the field must be formatted with narrow no-break space as thousands separators and full stop as decimal separator.
Usage
 <NumericalField
    decimalLimit={APP_ENV.chains[0].feeCurrencies[0].coinDecimals}
    decimalSeparator="."
    id="fees"
    // locale="de-DE"
    onChange={handleChange}
    placeholder="0"
    rightElement={<span>{APP_ENV.chains[0].currencies[0].coinDenom}</span>}
    value={value}
  />

Given the intricate nature of this feature, particularly the myriad scenarios to take into account when handling the display and editing of formatted input content, we have discussed about the most appropriate alternative to create the Numerical Input component from scratch. Factors under consideration include:

Adjusting text size in relation to the quantity of thousand separators
Maintaining cursor position
Handling selection of multiple characters for deletion or addition of content
Distinguishing between the usage of Backspace or Delete keys on Windows
Managing negative numbers, leading zeroes, etc

Given these complexities, we concluded that using a library dedicated to numerical input is the most effective and efficient approach, and probably rebuild your own numerical field in the future according to our needs. Therefore, we have closed this PR in favour of a new implementation. You can find the updated feature implementation in PR #428.


Interested for the idea 3 and add my information

I am very interested in the ideal 3 and have completed all the microtasks.
I added my information to this list. The project proposal will be uploaded soon.

In addition, this is not mergeable now. Please ensure (likely, by rebasing the commit) that it can be merged clean.


Trouble setting up Balena Sound services

When I access my Balena dashboard I can't see the services part where you activate or deactivate Airdrop, Bluetooth...
It just does not appear  (I've been following the official tutorial).
Can anyone help me?

hey @Javilatte, do you mean you can't see the section or that the section has an empty container list? If the section is empty it might be that you didn't deploy the application yet, maybe you skipped a step?
In any case, our forums (https://forums.balena.io/) are a much better place for this type of support questions. We are very active with support in our forums which is handled by the same engineers that build the balena products. So I suggest you post there if you don't manage to solve your problem.


Fix course so it can use proper Node runtime

This PR requires this commit on the template repo. The commit on the template repo gets us through the final deployment in the course, but for some reason the version of the action that lives on Dockerhub doesn't support Node 12. This PR changes the last step to use the repo as the source of the action instead and I've verified it works.
This PR fixes #25

@hectorsector 👍


[MM-31497] - Prevent end users from inviting people and exceeding the free tier limits

…

Summary
This PR adds redux code needed to pull data from the new endpoint added in this PR
Ticket Link
MM-31497

Hello @AGMETEOR,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Hello @AGMETEOR,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


Issue in a Production Enviroment

Hello,
First of all, thank you all very much for maintaining this project. It is a great package.
Now for the issue. While the app demo in its current state works as intended in an angular development environment when creating an angular production build, minifying and uglifying the code destroys the ComponentRegistration logic used, as the component constructor function names will be all uglified to the same name. This obviously breaks the map used with string keys.
To solve this, there are probably many avenues, for example, the easiest would be using static string names instead of constructor.name, as these aren't compressed, which however has its own issues, as we would need to maintain it across all references and thus multiple files. Alternatively registering the function names to not be minified could be another option.
While answering the latter question perfectly might not be in the scope of this demo, fixing the issue and shining a light on this trap fall could help users, which study this example to learn the usage of the package with Angular.
Greetings,
Michael Martini

Thanks @Aloterraner - Have fixed with static string names. :smiley:


Code changes to make / check

[ ] Make sure layers are in proper projection (6589). Currently .to_crs("EPSG=6589", inplace = True) does not seem to be changing projection.

[ ] Try to debug few pharmacies for which concentric polygons are not working


EIP1559 implementation #4138

Closes #4138

@hboon need your help to check if function EIP1559FeeOracle.eip1559FeeEstimates() works as needed.

@oa-s you need to push your web3swift fork.

Do we check or hardcode if a chain supports EIP1559?
nope, in case chain when doesnt support EIP1559 the fee history request will return an error

continue after https://github.com/AlphaWallet/alpha-wallet-ios/pull/5246

@oa-s don't forget this

should finish up this

here we got an issue with calculating estimate values, have no idea how to fix it

Would you help rebase and point out where it is? Can help to see too, if you like

Would you help rebase and point out where it is? Can help to see too, if you like

yes, sure

@hboon bump

@oa-s ah. Should I look at any particular place?

@oa-s okie, I'll take a look. Thanks!

@oa-s sorry, stuck with some other work, will come back to this :)

@hboon i will push after rebase, fifixed signing tx, and some other issues, still have issue with estimation coputation

@oa-s thanks. Sorry, haven't come to look at this yet. I will, but I will let you know before I do in case you work on this.

@oa-s thanks. Sorry, haven't come to look at this yet. I will, but I will let you know before I do in case you work on this.

yes, sure

@oa-s what else is left for this PR?

tweak changing fees when sending a tx

handling fees updates

@hboon could u please take a look at editing gas fee, not quite sure how to done it

@oa-s OK, I'll check the next 2 days. Working on something at the moment. Can you help paste a permalink to show where to look (if you know already)?

Getting a warning after I rebase master (not pushed here):

[R.swift] project.pbxproj is internally inconsistent.

Probably a bad merge with the project file

Pushed 2 commits that fixes the project file. They can be squashed into your commit(s)

Just notes:
Sent an EIP-1559 transaction on Goerli https://goerli.etherscan.io/tx/0x6fbe4f273f7c0ef419e8e86ca7f3c6e5d38f85bbe06cb5a4dd7a1fb03bbdcaab
Was successful and gas price = 284.x gwei, much higher than a transaction from 2 days ago https://goerli.etherscan.io/tx/0x598d15adc5cd894ab82b2c42cfca2516d1f39a365cea1110c83bf2e2dc4ba9b1
But seems inline with a transaction around the same period (281 gwei) https://goerli.etherscan.io/tx/0xe17bb1df31f254db3d1336dd5312ebfc5b49b8b1160852330498610b99507099

I am finishing with applying updates to ui, will test it more, and we will be able to finish it

What about estimates, do they seem correct? Sometimes i was able to catch zero estimates, on mainnet. Looks like that happened because of zero base fee. Not sure on what step it setted to zero

[ ] Looks like TransactionConfigurator isn't destroyed after TransactionConfirmationCoordinator is destroyed by cancelling the transaction confirmation actionsheet

[ ] With EIP-1559 transactions, we still need the old "Gas Limit". So 2 sliders for pre-EIP-1559 and 3 sliders for EIP-1559

What about estimates, do they seem correct? Sometimes i was able to catch zero estimates, on mainnet. Looks like that happened because of zero base fee. Not sure on what step it setted to zero

I'll play with it a bit more and look at the estimation function. No idea how it's supposed to work, but I'll check

Ok, I will check

If you have implemented a wallet sweep action; this is only possible using Legacy transaction style since the exact amount of gas used is not known with 1559 until the transaction is written.

[ ] How do we handle this? This is referring to the "All Funds" button

[ ] Good to mention and link to https://github.com/komputing/KEthereum/blob/master/eip1559_feeOracle/src/main/kotlin/org/kethereum/eip1559_fee_oracle/EIP1559FeeOracle.kt in the header for SuggestEip1559.

merge https://github.com/AlphaWallet/alpha-wallet-ios/pull/6647 first, need to resolve future conflicts

Also the "Priority Fee" slider goes from 0-4 as discrete Int. So if the user goes here and save, I suppose the Priority Fee would be overridden as 0. Should we change it to a floating point instead?

i am trying to use floating point instead of int, but get issue with convertation entered value back to BigInt,
in case if use type a number 1.23 for example, BigInt still will be 1, any clues how to handle such case?

Sometimes we end up with the priority fee for Rapid being lower than Fast. That shouldn't be possible:
can we facing such issue on Android?

Also the "Priority Fee" slider goes from 0-4 as discrete Int. So if the user goes here and save, I suppose the Priority Fee would be overridden as 0. Should we change it to a floating point instead?

i am trying to use floating point instead of int, but get issue with convertation entered value back to BigInt, in case if use type a number 1.23 for example, BigInt still will be 1, any clues how to handle such case?

This:

BigInt still will be 1

Is the unit for priority fee when stored here as BigInt in gwei? 1.23 is only truncated to 1 if we store it as gwei. So we should store it as wei instead (the smallest unit for Ethereum). I think, in general, whenever we store Ethereum amounts in BigInt/BigUInt, they should match the lowest "unit" in Ethereum then we're always safe in this aspect. We only convert them to gwei etc when we convert to string or floating point for calculating/storage.

Sometimes we end up with the priority fee for Rapid being lower than Fast. That shouldn't be possible:
can we facing such issue on Android?

No idea about this one on Android. I can look into the computation if you want. But I was thinking you ported it from the Kotlin version, so I only stared at the UI :)

Hope that helps? will check, thanks

updated code with latest changes, numbers looks good (not sure)

@hboon do we have any validation rules for priorityFee? except safe range 0...4

@oa-s we can look at this in a separate PR. I thought I saw this already done, but it applies for pre-EIP-1559 too

How do we handle this? This is referring to the "All Funds" button
nope, not for eip1559

should be good at this point, e.g. tests seems broken in #6693

tests seems broken in https://github.com/AlphaWallet/alpha-wallet-ios/pull/6693

Fixed :P
@oa-s ok. Let's merge

Added #6698


Updated Using on Windows topic

linked to RTM resources

This is still pulling in the wrong topics

It happens to me sometimes. But you can actually verify which files will be included before submitting the PR.


Not lighting "controllers icon" Green in Steam VR

Hello,
I have got the latest version of Orion running, I have double checked I have the Visual C++ redistributables installed. I have leap working in games such as Altspace VR with full tracking of my hands in game.
I have run the #8 version .exe file and installation goes through without apparant issue. Then load up steamVR and it fails to identify any controllers (Neither flashing or green), restarted computer just in case. I have uninstalled that version and tried #3, no different.
I am wondering could it be that steam is not installed on my C: steam is installed on my larger game drive? Could this be an issue? I am not computer illiterate however when it comes to this kind of thing i'm certainly no expert. I have followed the "installation of this driver on the download page" and even the Youtube tutorial by Reality Check VR, The steam VR controllers never "light up" flashing or solid.
Any tips? This is like holding a carrot in-front of my face, CANT WAIT to try it! But I'm out of ideas!
Thanks!!!!

Also, I keep seeing OpenVR SDK 1.0.0 - Should I have installed this file? Or is it part of the installer. If so, how do I install the SDK? I cant find any information on what to do with it!
SO sorry for the amateur questions, you help is greatly appreciated!!

I had the same issue, it wouldn't detect anything because the driver did not install
https://github.com/cbuchner1/driver_leap/issues/3
I talk about how I fixed it

You can try the Alpha #3 Release first before giving up (uninstall the #8 before)
Von meinem iPhone gesendet

Am 16.06.2016 um 06:33 schrieb Ibsn87<EMAIL_ADDRESS>Hello,
I have got the latest version of Orion running, I have double checked I have the Visual C++ redistributables installed. I have leap working in games such as Altspace VR with full tracking of my hands in game.
I have run the #8 version .exe file and installation goes through without apparant issue. Then load up steamVR and it fails to identify any controllers (Neither flashing or green), restarted computer just in case. I have uninstalled that version and tried #3, no different.
I am wondering could it be that steam is not installed on my C: steam is installed on my larger game drive? Could this be an issue? I am not computer illiterate however when it comes to this kind of thing i'm certainly no expert. I have followed the "installation of this driver on the download page" and even the Youtube tutorial by Reality Check VR, The steam VR controllers never "light up" flashing or solid.
Any tips? This is like holding a carrot in-front of my face, CANT WAIT to try it! But I'm out of ideas!
Thanks!!!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I had the same issue.
Check your "SteamVR" in Steam client.
Open property, click beta tab, and select "beta - SteamVR Beta Update".
If "Leap motion control panel"s icon in taskbar does not change green, reinstall "Leap motion SDK".


CredUnPackAuthenticationBuffer() never parses domain name

CredUnPackAuthenticationBuffer() never parses domain name
In file CredentialManager.cs, function private static bool PromptForCredentials(string target, NativeCode.CredentialUIInfo credUI, ref bool save, out string user, out string password, out string domain) makes following call:
if (NativeCode.CredUnPackAuthenticationBuffer(0, outCredBuffer, outCredSize, usernameBuf, ref maxUserName, domainBuf, ref maxDomain, passwordBuf, ref maxPassword))
{
....
}

No matter what I enter<EMAIL_ADDRESS>or domain1\user444) that call always fails to return anything in domainbuf
How can this be explained?

Are you testing it on Windows server 2008? We have tests (IntegrationTest, TestGetCredentials). One of them is run as part of the CI build. So its working in recent Windows versions.

No I am testing on Windows 10. And all tests complete, sure, but TestPromptForCredentials() outputs following to Output window:
Domain null
InvalidParameter

If you trace where this happens in the debugger you will see what I mean.

Oh, I think I know what you are referring to. The idea of this library was to capture credentials from user and pass it in Basic header. Basic header by definition does not have a "domain", though you can send the domain in the user@org or org\user format.
I use CredUIPromptForWindowsCredentialsW  to ask for the credentials. This supports only generic credentials or secure credentials (i.e. in a secure desktop).  CredUnPackAuthenticationBuffer is then used to convert the buffer to a managed strings. The documentation is still TBD for domain part, so I am not sure if it is even designed to split the domain from user name.
Hence in my code if the domain is null I call CredUIParseUserName to  split the user name and domain. Note that CredUIParseUserName has its own criteria and it will not split user@domain but handled domain\user  !!
 if (String.IsNullOrWhiteSpace(domain))
                    {
                        Debug.WriteLine("Domain null");
                        if (!ParseUserName(usernameBuf.ToString(), usernameBuf.Capacity, domainBuf.Capacity, out user, out domain))
                            user = usernameBuf.ToString();
                        password = passwordBuf.ToString();
                    }


Add memoize macro

macro memoize(type_decl)
  @{{type_decl.var}} : {{type_decl.type}}?
  def {{type_decl.var}}
    @{{type_decl.var}} ||= {{yield}}
  end
end

class Users::Index < BaseAction
  memoize users : UserQuery do
    UserQuery.all.active
  end
end

https://play.crystal-lang.org/#/r/25hp
Also an interesting version here https://play.crystal-lang.org/#/r/25ha

This code should work as-is, but it needs a spec and docs. The reason for this is that it makes it simpler to memoize things. Having to declare an instance variable somewhere else and then use it in the method is kind of ugly and a PITA. This macro should make it simpler to do

Actually I think it's easier to just explain how to do this in the guides. The macro doesn't do enough


Test matrix and definitions for all standard gates

some gates have a hardcoded matrix associated with them.
some have definitions in terms of more elementary gates.
the equivalency of these two should be tested for all gates.
I did this for ch in #2837. Others need to be added in test.python.circuit.test_gate_definitions

Hi there! I'm interested in this issue, and wanted to know if I can work on it.

Hi @drholmie, great. Please wait for #2837 to merge, and then you can build on the test there.

Alright, thanks! I do have a few questions about it, will ask after the merge if that's alright.

Congrats on the merge! Wanted to ask a couple things about it. Firstly, I'm assuming this is an implementation of issue #1741 and wanted to know if I should continue with changing other gate definitions, following the issue's suggestion of other shorter gate definitions, or if I should just focus on writing tests for gates.
Secondly, are tests to be added for every gate in qiskit.extensions.standard ? If so I'd like to tackle the issue by splitting it into multiple PRs, where each PR is a test for a certain gate, thus allowing for easier reviews. Do tell if this is okay with you, and please do correct me if I'm wrong in my understanding of the situation.

Hey there! I don't really know if this issue should be closed. Was actually working on the other tests as well since I was advised to split this issue into multiple PRs. I apologize for the delay, I was busy with my college examinations. Is it still okay for me to submit the other tests and continue to reference this issue?


graph init command failed

While initializing graph using command garph init, installing dependencies with yarn fails because request is no longer being maintained as stated by request team here https://github.com/request/request/issues/3142/#issue-427331880 with the following error.

@VaibhavArora19 so I tried graph init on new project. I do not get the error you see. (But found a new error on lists while debugging this https://github.com/graphprotocol/graph-tooling/issues/1058)

Not sure if this is a windows specific problem but I tried changing my node version to 16.17.0 as well, graph-cli v0.38.0 and I am still having the same error as I was having before. I've seen some other devs as well facing the same issue. Some screenshots attached below of the same problem that other people faced.

I had an error when I tried to launch graph init in my project folder, where package.json and yarn.lock files existed. However, when I ran the same command outside of the project folder, it worked fine. I think this might be a workaround for people who are experiencing this problem.


Fix for #547 #543

This PR is a fix for #547 #543

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@nateshmbhat what's the test plan on this ? Just curious how you know this fixes your issue - did you run it locally?

Yes i changed this and re compiled the project. It built successfully and android 13 features worked fine.
I have been using this change as part of patch package file.

it was working fine in my project but may have been the different gradle versions. Will release this today. thank you for the patch 🔥


How to handle API key without parameter name when building [Independent publisher connector ]

Hello wonderful team,
i hope everything going well with you,
i will come straight to the point, i was trying to build a independent publisher connector and i have small issues while developing, The service api i am using have the apiKey without any parameter name how do I handle this type of url ? They have mentioned it should be in the query but not in headers,
Thanks in advance,

Can you share which API it is? So the query is something like …/action?{apiKey} ?

Hello @troystaylor,
thanks for your quick response :)
here is how actual URL looks
https://imdb-api.com/en/API/Search/k_y7v36i61/lost
But when testing I noticed in swagger definition request url as below
https://imdb-api.com/en/API/Search/lost/apiKey=k_y7v36i61

I’m AFK, but I believe you can use route request policy to accomplish this: https://docs.microsoft.com/en-us/connectors/custom-connectors/policy-templates/routerequesttoendpoint/routerequesttoendpoint
I would suggest that you use no authentication, then download the connector and add a connection parameter for the apiKey, then upload it, after which the connection parameter would be available to the policy.

Alright, I did try but it showed no effect, anyway, I will try your suggestion and see if it works and will update you on the status.
and can you tell me how I can use apiKey parameter in the route policy template in new path
Thanks

Use the second example:
https://test.abc.xyz/get/{id} | /@queryParameters('version')/get/{id} | https://test.abc.xyz/v2/get/{id}
You don’t want the user to have to enter the apiKey for every action, so instead of the query parameter it will be a connection parameter in the same format:
/Search/@connectionParameters(‘apiKey’)/lost

When you uploaded it with paconn, it uploaded successfully to the right connector?

I am trying to upload via 'Import an OpenApi file' in the Custom connector section and it throwing me this below error i believe i need to use paconn,

Ok, you need to download the connector you have built and update the apiProperties file.
https://docs.microsoft.com/en-us/connectors/custom-connectors/paconn-cli#download-custom-connector-files

understood! I will do that and will update the status.
thanks :)

I have updated the Connection parameters as per your suggestion and updated the connector via paconn.

however, It seems policy still did not detect it. i got below error
{   "error": {     "code": 500,     "message": "Invalid parameters template. No property names specified in @headers or @queryParameters or @connectionParameters expression",     "source": "europe-002.azure-apim.net",     "path": "choose[3]\\when[1]",     "policyId": ""   } }

Can you share the paconn update successful command screenshot?

sure  here

Hello team,
is there any help I can get?
I want to understand how to get through with this.
thanks


Modal navigation discards session

I just tried out v0.5.2 of this package in my Inertia v1.3 / Vue 3.4 app and bumped into a problem related to the modal's redirect functionality.
The first issue I found is that, when opening a modal with navigation, the current session is discarded. This means the user is signed out of the application when he closes the modal or hits refresh.
A second issue I found is that the session is only passed to the redirector when Laravel's session.store parameter is configured. However, the session.store parameter is only relevant when using a cache-driven session backend like Redis. When using the file, cookie, or database driver, you don't configure the session.store.
// If the session is set on the application instance, we'll inject it into
// the redirector instance. This allows the redirect responses to allow
// for the quite convenient "with" methods that flash to the session.
if (isset($app['session.store'])) {
    $redirector->setSession($app['session.store']);
}

It's not session.store from the config, but the Illuminate\Session\Session instance that's bound to the Laravel container. I tried persisting a value into the session (which was fine), but not with an authenticated user. I'll investigate it!

I did a quick check on the demo application (default Laravel project), but I couldn't break it with an authenticated user. Could you share some code (controller, modal, etc.)

I've added a test in c549981

I got this issue as well. Inertia UI modal v0.9.1, Inertia v1.3.0, and vue v3.3.13. Authentication using Laravel Jetstream.
routes:
Route::resource('users', UserController::class);
controller:
public function show(User $user)
{
    $user->load(['roles']);

    return Inertia::modal('Users/Show', [
        'user' => $user,
    ])->baseRoute('users.index');
}

Show.vue

<template>
  <Modal>

Show User

{{ props.users.name }}

  </Modal>
</template>

I encounter the same issue with 0.11.1 and Inertia 1.
I have a Laravel Breeze Starter with react and InertiaJS and basically a simple controller with 2 views (list and detail). Opening the detail and closing terminates the session.

@philippreiner Thanks for reporting! Which session driver are you using? Is there any way you could share a (simplified) version of the repo?

Hi @pascalbaljet
Hi @pascalbaljet,
I'm encountering the same issue. I'm using the VILT stack. Here’s a simplified repo: https://github.com/juprir/inertiauimodal.
When the modal is accessed using ModalLink, the user stays logged in, but the base URL is not shown. However, if the modal is accessed using an anchor tag or by typing the URL directly into the address bar, the user is automatically logged out.

Thanks, @juprir! I'll look into it!

Hi @pascalbaljet
Its happening to me too, using the base URL functionality, when accessing to the modal typing the URL manually i see the modal open, but the moment i close it, im automatically logged out

I'm encountering the same issue. I'm using the VILT stack. Here’s a simplified repo: https://github.com/juprir/inertiauimodal.

Thanks for this! I can now reproduce it!

I've found it! It's the EncryptCookies middleware that is double encrypting and decrypting the cookies on the subsequent request. I've got a fix but still need to write a test.

Still not working. Closing a modal is discarding the session.

I sill have the same problem, after all lib updated... and the issue was:
Access Denied for some folder inside Laravel, and this command fixed the random disconect after opening the modal:
chmod -R 775 storage
chmod -R 775 bootstrap/cache


Automatic emails with interview location and time

As a part of the changes to the admission system, emails with an interview time should be automatically sent to applicants.
We need to closely consider the best way to do this. We probably need to add a "did get interview email" field to the application model, and add a tool that sends emails to selected people. The most important considerations I can think of right now are:

Everyone MUST get emails. It should not be possible to accidentally miss some applicants
It must be possible to send emails in batches since large groups plan interviews continuously
We should prevent accidental changes of interview times when an email was sent out. It should still be possible to change however, in case an applicant cannot meet at the selected time.

One idea on how to do this is to have a "Schedule interviews" button which takes you to a new page.
This page would look like this:
Interview start: [ DATETIME FIELD ]
Interview end: [ DATETIME FIELD ]
Interview duration: [ INT FIELD ]
Interview location: [ TEXT FIELD ]
Breaks: [ SELECT FIELD] (none, between each interview, between each 2nd interview, 3rd, 4th etc)
Break time: [ INT FIELD ]
[ GENERATE SCHEDULE BUTTON ]
Once the button is pressed, you get a suggested schedule (table of applicants/times) that can be edited/some can be removed. When you are happy with the schedule you press a [ CONFIRM AND SEND EMAIL TO APPLICANTS ] button which sends the emails and sets their interview times. Next time you schedule an interview these applicants will be excluded.

Take a look at this  @Frenje123


[Feature Request] Add the ability to define payment adapter logo outside of CSS

Describe the bug

Stripe  / My plugin / Custom
How ever current all logo's are hard coded in:
https://github.com/FOSSBilling/FOSSBilling/blob/main/src/themes/huraga/assets/css/logos.css
How to reproduce
Download https://github.com/jaapmarcus/mollie-fossbilling and install it
Create a new invoice and try to pay as user
In the order page it has been solved by listing the payment providers as  text:
Pay with xxx
Expected behavior
Ability to have the logo visible
Screenshots
No response
FOSSBilling version
N/A
Module version
No response
Device
No response
Information
No response
Additional context
No response

This also happens with Paystack payment too

And it is hardcoded in:
https://github.com/FOSSBilling/FOSSBilling/blob/8863cb4b65c9b80800cb67dfdd3a35bd0adee4c2/src/modules/Invoice/html_client/mod_invoice_invoice.html.twig#L34

Existing Custom gateways need to update their code to support them:
See: https://github.com/jaapmarcus/FOSSBilling/blob/be3ef9db36f8f9f72b25e7dffd037e6e94b85ea3/src/library/Payment/Adapter/Custom.php for the changes required


SeatAndEat : Change Styles Of About Us Page

Make about us section responsive

I want to work on this issue.

Are you referring to the 'About Page' or the 'About Us Section'?

It is referred to the about page

I want to work on this. Can you assign me this issue?

Assigned @iamatifmoin


torcs: anonscm.debian.org has moved

the patch links returned a HTTP error 401 as
anonscm.debian.org moved to a gitlab at salsa.debian.org
I used the non access required download link generated by the new instance
As @worldofpeace suggested in #58978 I used the last commit involving the files.

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build torcs

Tried to build it on my system, but it failed because of a invalid conversion in OpenALMusicPlayer.cpp

make[4]: Entering directory '/build/torcs-1.3.7/src/libs/musicplayer'
gcc -E  -M -D__DEPEND__ -I/build/torcs-1.3.7/export/include -I/build/torcs-1.3.7 -D_DEFAULT_SOURCE -DSHM -DHAVE_CONFIG_H   SoundStream.cpp OggSoundStream.cpp OpenALMusicPlayer.cpp musicplayer.cpp > .depend
g++ -I/build/torcs-1.3.7/export/include -I/build/torcs-1.3.7 -g -O2 -Wall -fPIC -fno-strict-aliasing -O2 -DUSE_RANDR_EXT -DGL_GLEXT_PROTOTYPES -Wall -fPIC -fno-strict-aliasing -O2 -DUSE_RANDR_EXT -DGL_GLEXT_PROTOTYPES  -D_DEFAULT_SOURCE -DSHM -DHAVE_CONFIG_H  -c SoundStream.cpp
g++ -I/build/torcs-1.3.7/export/include -I/build/torcs-1.3.7 -g -O2 -Wall -fPIC -fno-strict-aliasing -O2 -DUSE_RANDR_EXT -DGL_GLEXT_PROTOTYPES -Wall -fPIC -fno-strict-aliasing -O2 -DUSE_RANDR_EXT -DGL_GLEXT_PROTOTYPES  -D_DEFAULT_SOURCE -DSHM -DHAVE_CONFIG_H  -c OggSoundStream.cpp
g++ -I/build/torcs-1.3.7/export/include -I/build/torcs-1.3.7 -g -O2 -Wall -fPIC -fno-strict-aliasing -O2 -DUSE_RANDR_EXT -DGL_GLEXT_PROTOTYPES -Wall -fPIC -fno-strict-aliasing -O2 -DUSE_RANDR_EXT -DGL_GLEXT_PROTOTYPES  -D_DEFAULT_SOURCE -DSHM -DHAVE_CONFIG_H  -c OpenALMusicPlayer.cpp
OpenALMusicPlayer.cpp: In member function 'virtual bool OpenALMusicPlayer::streamBuffer(ALuint)':
OpenALMusicPlayer.cpp:164:22: error: invalid conversion from 'char' to 'const char*' [-fpermissive]
const char* error = '\0';
make[4]: *** [/build/torcs-1.3.7/Make-default.mk:240: OpenALMusicPlayer.o] Error 1
make[4]: Leaving directory '/build/torcs-1.3.7/src/libs/musicplayer'
make[3]: *** [/build/torcs-1.3.7/Make-default.mk:679: subdirs] Error 1
make[3]: Leaving directory '/build/torcs-1.3.7/src/libs'
make[2]: *** [/build/torcs-1.3.7/Make-default.mk:679: subdirs] Error 1
make[2]: Leaving directory '/build/torcs-1.3.7/src'
make[1]: *** [/build/torcs-1.3.7/Make-default.mk:679: subdirs] Error 1
make[1]: Leaving directory '/build/torcs-1.3.7'
make: *** [Makefile:32: restart] Error 2
builder for '/nix/store/39nqla9fscgp525w8nqq177jc3rsrybp-torcs-1.3.7.drv' failed with exit code 2
error: build of '/nix/store/39nqla9fscgp525w8nqq177jc3rsrybp-torcs-1.3.7.drv' failed

See https://github.com/NixOS/nixpkgs/pull/59527
Anyone volunteering to raise this issue upstream if it hasn't already been?

@GrahamcOfBorg build torcs

I added the patch for GCC7 and built it locally on NixOS. Let's check with ofBorg though.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-30-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4672

Questions ?
Please refer to the Backport tool documentation


Fix Date Format

Fix Date Format
Summary of Issue
Currently, the web app display date in a strange format in the data table. The strange format is a standard YYYY-MM-DD with a "T00:00:00Z" at the end. I am hoping to get rid of that "T00..." portion. I theorize that the strange date format is likely from importing the column from excel, where the column is formatted as "Date".
Below is what is currently displayed:

Possible Solution
Bug may be fixed by importing date as a character value
read_xlsx(input$client_log, col_types("text", "numeric", "character")
and then forcing it to be a date value after importing it, before displaying it
%>% as.date(.$DOS)
Status
Still needs to be attempted


Consider bravado-core to manage OpenAPI/Swagger 2.0 validation/parser

I have found that we are dealing a lot with OpenAPI/Swagger 2.0 Specification validation and parsing in Connexion code. I was willing to implement an library independent of Connexion code that would manage all those reference checks and validations in a way that could be used by Connexion and other packages that want to deal with OpenAPI Specification. I have found that there is already a package that does exactly what I was looking for. It is called bravado-core by Yelp.
The question is, have you already considered that before? If so, why not reuse that code? If not, what do you think about that idea?
There are many advantages and disadvantages of going that way. Like the core functionality of Connexion being dependent of an external library being the biggest concern. But there are also great benefits like a lot of work is done ahead on supporting the OpenAPI specification.

@rafaelcaricio thanks for the hint, I'm planning on writing a library to automatically have a convenient command line client for Swagger APIs: https://github.com/zalando/openapi-cli-client

I will try to fit bravado-core into Connexion code and see what happens.

I started working on it and seems like we are already supporting some invalid definitions. I am thinking about creating a compatibility layer over the invalid declarations we are supporting and throwing a warning for those while fixing them automatically whenever possible. Also I am fixing our code to work only with valid specification. I just wanted to update you all with the status of this task.

I have backed up on using bravado-core since it's propose is other than being used in backend applications to handle specs. We would need to call their internal functions/methods that could change anytime and make bad impact in how we would use it in Connexion codebase.
Instead I decided to just use the swagger_spec_validation package which will guarantee that we stick to the proper valid Swagger/OpenAPI 2.0 specification. That addition is ready to be merged in the pull request #160. Please review and/or give feedback on that.


Disable IDF - workaround?

Is there a way to disable IDF from scoring. Just like how we disable field norms?
Apparently a lot of people want to disable IDF in search engines. There is a way to do it in Elasticsearch, but not here?

If not possible. Can anyone please point me to a direction? Like where exactly is the IDF score being applied in the codebase?

CC: @fmassot @fulmicoton

Is it something you actually need or is it a general suggestion?


Wrong pypi url in XDU mirror

The pypi address of XDU(LAN only) provided by https://help.mirrors.cernet.edu.cn/pypi/ is https://linux.xidian.edu.cn/mirrors/pypi/web/simple
However, the correct url should be https://linux.xidian.edu.cn/mirrors/pypi/simple

It can be solved in two ways

provide an option, similar to #27. This is ugly.
Contact XDU mirror admin and ask for a symlink in pypi/web, i.e.cd pypi/web; ln -s . web

PKU and JLU have done so.

done.