Nlattr payloads should pad to a multiple of NLMSG_ALIGNTO bytes

Hey John, I want to avoid piling a bunch of issues on you, so please feel free to ignore this if you're busy. I had some protocol errors and discovered this as the cause and just wanted to file it somewhere. I think the fix is easy, so I'll do a pull request myself within a few weeks.
I think NlAttrHdr payload construction methods should be padding aware. To quote libnl:

Most netlink protocols enforce a strict alignment policy for all boundries. The alignment value is defined by NLMSG_ALIGNTO and is fixed to 4 bytes. Therefore all netlink message headers, begin of payload sections, protocol specific headers, and attribute sections must start at an offset which is a multiple of NLMSG_ALIGNTO.

This is a low priority issue for my use case since being aware of it means you can use a simple workaround. (Just use new_binary_payload and append whatever 0's are necessary.)
In my specific usage (with neli 0.3.1), I was calling new_nl_payload and passing a u16. Including this attribute caused all further attributes to be improperly parsed by the kernel since this attribute was 6 bytes. Appending 2 bytes (to get to 8) fixed the problem.

Hi Brandon, not a problem. I'd rather know when things aren't working as expected. Currently bumping into some issues around how I solved stateful size calculations with regards to #15. I'm going to finish that up soon and after that will prioritize this. Thanks!

Hi Brandon, I've bumped into a situation where I actually need to solve this before the multiple message issue #15! The problem boils down to this. To handle multiple messages, I've needed to rework the traits a bit to be more flexible around how size is hinted when deserializing so that Vecs can be properly hinted and do not consume the rest of the buffer. These two problems are actually tightly coupled and I'm going to start with this one so that my trait architecture is flexible enough for all the uses cases it needs to cover. I need to support two use cases currently:

deserializing structs that contain string identifiers represented by C types like char[] which translates into a Rust struct with &'a str or at least String - these should not be padded, only the whole struct should be padded to fit alignment
deserializing String/u16 payloads and other types that need to be padded as, on their own, they do  not meet the 4 byte alignment
I originally didn't think of the first use case until I dug into some ACPI event netlink stuff and realized that if that case is not handled, neli will assume all strings are padded, even in the context of a struct which causes netlink errors when constructing messages. My initial thought on how to solve this in the general case in a better way than the case by case approach I took previously is to create an NlPadding type that is placed at the end of structs that need proper alignment. Not every type processed by neli is guaranteed to need it in every single circumstance so this would allow the user to essentially mark a struct as needing proper alignment when deserializing. It would also provide serialization with a way to understand that the padding should be discarded when converting it into a Rust representation. How does that sound to you?

I originally didn't think of the first use case until I dug into some ACPI event netlink stuff and realized that if that case is not handled, neli will assume all strings are padded, even in the context of a struct which causes netlink errors when constructing messages.

That's weird. To make sure I'm understanding you correctly, you're saying some ACPI event netlink messages require padding strings within structs? Where the entire struct is a Netlink attribute and the string is not (an attribute)? I think I might be misreading the above since it contradicts the first bullet point.

It would also provide serialization with a way to understand that the padding should be discarded when converting it into a Rust representation. How does that sound to you?

I may not have fully understood this either. I may be missing something, but is the following strategy enough to cover all cases?

During serialization of an attribute, determine length as we currently do, but add len % 4 null bytes to the payload vector.
During deserialization, read the attribute len, consume len + len % 4 bytes from the buffer, and run len bytes through the Nl type deserialize method.

From what I've seen, the len property of an attribute header is the unpadded length. If this isn't universally true, I can see this being significantly harder.

I originally didn't think of the first use case until I dug into some ACPI event netlink stuff and realized that if that case is not handled, neli will assume all strings are padded, even in the context of a struct which causes netlink errors when constructing messages.

That's weird. To make sure I'm understanding you correctly, you're saying some ACPI event netlink messages require padding strings within structs? Where the entire struct is a Netlink attribute and the string is not (an attribute)? I think I might be misreading the above since it contradicts the first bullet point.

Nevermind, I see what you meant. You were saying that the library currently assumes that strings within structs are padded, but this typically isn't the case.

My initial thought on how to solve this in the general case in a better way than the case by case approach I took previously is to create an NlPadding type that is placed at the end of structs that need proper alignment.

Hm.. to elaborate on my comment above, I don't know if an explicit NlPadding type (following the payload) is necessary since len is the unpadded size. I suppose it doesn't hurt to do though.

I was just about to get back to you and try to reword but I think we're on the same page now! I guess my idea with explicitly mentioning whether a struct should be padded or not came from my learning curve dealing with netlink. I had a lot of unfortunate encounters with padding bugs when first writing this library so I wanted to make it a little more readable to the user. However, I just finished discussing Linux struct alignment/memory mechanics with some people who are more familiar with those details than I am and it seems it might make sense to simply add the padding to the payloads instead of tying myself in knots trying to address the "padding or no padding" problem at the struct field level instead of the struct level. I'll see how that works and will report back with the results. For now, I think you're right that the padding handling can be implicit in the serialization/deserialization methods for the struct that contains the payload instead of in the Vec/String/etc. serialization/deserialization methods themselves. In retrospect, that doesn't make a lot of sense.

Just made a very big commit that should help fix some problems with the way that I designed the traits themselves. It is a breaking change but I think it will make my life and the life of developers using the library a lot easier. 8904c9edcec2899c93320d51f4b455895b63fffe fixes some things that have made me kinda tie myself in knots while writing this through changes to buffering and reworking the Nl trait by breaking it into Nl and NlBuf traits, removing the need for Nl::{serialize_with,deserialize_with}. Thank you for working with me on this. I know this is taking longer than I expected and hope that the resulting code will make maintenance moving forward a lot easier.

Just made a very big commit that should help fix some problems with the way that I designed the traits themselves. It is a breaking change but I think it will make my life and the life of developers using the library a lot easier.

Cool stuff! Thanks for the update.

Thank you for working with me on this. I know this is taking longer than I expected and hope that the resulting code will make maintenance moving forward a lot easier.

No worries! Take your time. I appreciate that you're doing this at all.

I think I've fixed this! I'm pushing this to the same branch as #15.

No rush, of course but lemme know on this issue and the multiple messages issue if either or both have been resolved. I've rebased my rtnetlink work onto this branch because of some fundamental design changes these two issues required. I will keep working off of the rtnl-dev branch but I'll leave multi-msg-feature unmerged for now so I can add anything else you may need before closing these. Thanks!

No rush, of course but lemme know on this issue and the multiple messages issue if either or both have been resolved.

The changes you've made work really well for multiple messages! Thanks.
I have yet to do some padding tests. I'll respond again once I do that.

Okay sounds good! Glad to hear it's working on your end.

So on the multi-msg-feature branch, following snippet:
use neli::nlattr::Nlattr;

fn main() {
    let payload = Nlattr::new_nl_payload::<u16>(None, 1, 3).unwrap();
    println!("{:#?}", payload);
}

currently prints out
Nlattr {
    nla_len: 8,
    nla_type: 1,
    payload: [
        3,
        0,
        0,
        0,
    ],
}

I believe nla_len should be 6. 4 bytes for the header plus 2 bytes for the u16. From looking at genl ctrl, padding doesn't seem to be counted as a part of the length.
I haven't found any Linux documentation explicitly stating that nla_len doesn't count padding, but libnl's nla_len doesn't count padding either.

nla_len() will return the length of the payload not including eventual padding bytes.
http://www.infradead.org/~tgr/libnl/doc/core.html#_parsing_a_message

http://www.infradead.org/~tgr/libnl/doc/api/group__attr.html#gac5a7705797946fa9c0775997bb8d130b

You're absolutely right on this. I missed this and I see where the problem is: I added padding to the payload in the function ::new_nl_payload which breaks .size(). This should only be done in the .serialize() function for Nlattr because only that function should handle alignment. I'm making those changes now. Thanks for catching this.

I'm just pushed tests as well to make sure I don't break this moving forward. I had removed tests for this during module refactoring and realized I should rewrite them.

I'm going to merge multi-msg-feature and close this. Feel free to comment here if it's not resolved and I'll reopen. Thanks!


Sidebar don't scroll with the page.

Sidebar support to don't scroll with the page?

I've got the same problem.

the sidebar does not scroll with the page when it is scrolled, help please

https://github.com/trendmicro-frontend/react-sidenav/issues/5
This worked for me


Handle case when Content-Encoding is gzip, without requests

Currently, there is a "magic" behaviour when whether or not requests is installed, a dependency which currently is quite hidden.
This PR tries to reduce the magic behaviour, by handling the gzip case (ignoring the cases of compress, deflate and br) and raising an error being transparent that the package cannot decode the current encoding and recommending installing request.

Thanks. I agree that the current behavior isn't as discoverable as it should be, but I'm more inclined to make requests or now httpx a required dependency and drop the urllib code. Happy to see a PR which does that instead! And appreciated either way.


Auto refresh store on open

Currently the store doesn't seem to auto refresh. Users are not seeing new apps in the list until after a manual refresh. Perhaps the app list should either refresh each time the store is opened or each time it polls for updates?

Strange. It should refresh on each update check (https://github.com/accrescent/accrescent/blob/c091e16ca28c34e51285492737df7d98d3e85f85/app/src/main/java/app/accrescent/client/workers/AutoUpdateWorker.kt#L22).

I can't reproduce this, and the code appears to be correct. Can you confirm that it doesn't auto refresh for sure?

Hard to test since new apps / updates are so infrequent and update in the background, so there are very small windows to test a new app being released but not yet picked up by accrescent 🤔

Closing as resolved by https://github.com/accrescent/accrescent/commit/12e252c4d1c806d557ebddd02eb8a4913ac01c07


Zigbee2mqtt refuses to see / connect to conbee II

Zigbee2mqtt refuses to recognize the the Conbee II usb
Deconz can see and connect to the conbee II no issues.
Zigbeemqtt wont see /connect to the conbee II
But....if i have deconz running....and then start zigbeemqtt....zigbeemqttt reports "device busy"
Operating environment : HassOS vm on qnap.
Description of problem:
I can see the conbee II in  /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE*****-if00 and /devttyACM0
I have tried both paths above for the configuration, no luck
Your logs from Home Assistant
Zigbee2MQTT:info  2021-01-09 12:51:36: Starting Zigbee2MQTT version 1.17.0 (commit #1.17.0)
Zigbee2MQTT:info  2021-01-09 12:51:36: Starting zigbee-herdsman (0.13.46)
Zigbee2MQTT:error 2021-01-09 12:51:55: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-01-09 12:51:55: Failed to start zigbee
Zigbee2MQTT:error 2021-01-09 12:51:55: Exiting...
Zigbee2MQTT:error 2021-01-09 12:51:55: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.<anonymous> (/zigbee2mqtt-1.17.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:94:31)
    at Generator.throw (<anonymous>)
    at rejected (/zigbee2mqtt-1.17.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)
npm
ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR!
<EMAIL_ADDRESS>start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-01-08T23_51_55_944Z-debug.log
2021-01-09T12:51:57: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2021-01-09T12:51:57: PM2 log: App [npm:0] starting in -fork mode-
2021-01-09T12:51:57: PM2 log: App [npm:0] online
><EMAIL_ADDRESS>start /zigbee2mqtt-1.17.0
> node index.js

** Config
serial:
  port: >-
    /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE*****-if00
advanced:
  log_level: info

same issue here!
I'm new to this - but if you need any information - i'd like to help

same issue here!
I'm new to this - but if you need any information - i'd like to help

@&#&#%<EMAIL_ADDRESS>figured out i needed adapter: deconz is the config file @benwedel-snabble

@&#&#%<EMAIL_ADDRESS>figured out i needed adapter: deconz is the config file @benwedel-snabble

@&#&#%<EMAIL_ADDRESS>figured out i needed adapter: deconz is the config file @benwedel-snabble

Sorry, what do you mean?

@&#&#%<EMAIL_ADDRESS>figured out i needed adapter: deconz is the config file @benwedel-snabble

Sorry, what do you mean?

See https://www.zigbee2mqtt.io/information/supported_adapters.html and scroll down to Conbee II for more information regarding this issue.

See https://www.zigbee2mqtt.io/information/supported_adapters.html and scroll down to Conbee II for more information regarding this issue.

Wow!!!! Thanks a lot - it‘s actually working with that! ✌🏽🙌🏽

Wow!!!! Thanks a lot - it‘s actually working with that! ✌🏽🙌🏽

Can this issue be closed?

I have the right serial: port & adapter, but still getting these errors... very annoying...

I have the same isssue :(

@JaCoLJcL @kvmgz can you post logs for your errors? You might have different problems than the missing settings for adapter as the poster above.

Same issue here too unfortunately. Posted my logs here @ciotlosm: https://github.com/danielwelch/hassio-zigbee2mqtt/issues/494#issuecomment-791962197

Same issue here too unfortunately. Posted my logs here @ciotlosm: #494 (comment)

Your error is different :  Error: Error while opening serialport 'Error: Error: Resource busy, cannot open /dev/ttyACM1

I have the same problem, I found out that I have to turn off DeConz and then run zigbee2mqtt.

@WesNz Here's my config file:
data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto'
  user: [REDACTED]
  password: [REDACTED]
serial:
  port: /dev/ttyACM1
  adapter: deconz
advanced:
  log_level: warn
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  options: '-d -d'
  log: false

@kraton77 That's interesting—I have ZHA running on a completely different stick entirely (that's incompatible with Z2MQTT). Still, I've never configured ZHA with the Conbee I'm trying to run z2m on.

@mg0716
here's my config file below ...i see your Port is different?
the main thing that strikes me with your error message is its saying that your device is busy...which means a) some app or soemthing is using the device.. or b) you are pointing to the wrong device?
data_path: /share/zigbee2mqtt external_converters: [] devices: devices.yaml groups: groups.yaml homeassistant: true permit_join: true mqtt:   base_topic: zigbee2mqtt   server: 'mqtt://<IP_ADDRESS>:1883'   user: meh   password: meh serial:   adapter: deconz   port: >-     /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2253437-if00 advanced:   log_level: info   pan_id: 6754   channel: 11   network_key:     - 1     - 3     - 5     - 7     - 9     - 11     - 13     - 15     - 0     - 2     - 4     - 6     - 8     - 10     - 12     - 13   availability_blocklist: []   availability_passlist: [] device_options: {} blocklist: [] passlist: [] queue: {} frontend:   port: 8099 experimental:   new_api: true socat:   enabled: false   master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'   slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'   restartdelay: 1   initialdelay: 1   options: '-d -d'   log: false

Thanks @WesNz.  It turns out that I never turned off Deconz 😑🙄🤦🏼♂. Safe to say, it's running now lol.

I have the same issue, and I have devices that will only work with Zigbee2Mqtt (Philips Hue PAR38 outdoor flood bulbs) so DeConz is not an option for me.
Config file:
data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
base_topic: zigbee2mqtt
serial:
port: >-
/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2469763-if00
advanced:
log_level: warn
pan_id: 6754
channel: 11
network_key:
- 1
- 3
- 5
- 7
- 9
- 11
- 13
- 15
- 0
- 2
- 4
- 6
- 8
- 10
- 12
- 13
availability_blocklist: []
availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
port: 8099
experimental: {}
availability: false
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: '-d -d'
log: false
server: mqtt://192.168.x.xxx [it has the correct ip address]
Logfile:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing...
[13:41:03] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing...
[13:41:04] INFO: MQTT available, fetching server detail ...
[13:41:04] INFO: MQTT server settings not configured, trying to auto-discovering ...
[13:41:04] INFO: Configuring 'mqtt://core-mosquitto:1883' mqtt server
[13:41:05] INFO: MQTT credentials not configured, trying to auto-discovering ...
[13:41:05] INFO: Configuring'addons' mqtt user
[13:41:05] INFO: Previous config file found, checking backup
[13:41:05] INFO: Creating backup config in '/config/zigbee2mqtt/.configuration.yaml.bk'
[13:41:05] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[13:41:06] INFO: Handing over control to Zigbee2mqtt Core ...

<EMAIL_ADDRESS>start
node index.js
Zigbee2MQTT:error 2022-01-03 13:41:33: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-01-03 13:41:33: Failed to start zigbee
Zigbee2MQTT:error 2022-01-03 13:41:33: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-01-03 13:41:33: Exiting...
Zigbee2MQTT:error 2022-01-03 13:41:33: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:102:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:123:29)
at Zigbee.start (/app/lib/zigbee.ts:58:27)
at Controller.start (/app/lib/controller.ts:100:27)
at start (/app/index.js:97:5)
[13:41:34] INFO: Handing over control to Zigbee2mqtt Core ...
<EMAIL_ADDRESS>start
node index.js

I tried to add the below lines to my configuration.yaml file:
serial:
adapter: deconz
However, that just gives me an Invalid Config notification:
Invalid config
The following integrations and platforms could not be set up:
serial

@ciotlosm @WesNz @mg0716 how does one turn off deconz? I removed all the devices from there but it still autodiscovers stuff.
I have a feeling this is why I am getting the same error in zigbee2mqtt.

I have the exact same issue and error message, I used to run my Conbee through Deconz but I don't know how to turn it off

I had to add serial: deconz to my zigbeemqtt yank configuration file. It’s sort of hidden away in the docs, but it’s on the zigbeemqtt website.

Already have that, here is my config :
data_path: /config/zigbee2mqtt external_converters: [] devices: devices.yaml groups: groups.yaml homeassistant: true permit_join: true mqtt:   base_topic: zigbee2mqtt serial:   port: >-     /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2467521-if00   adapter: deconz advanced:   log_level: warn   pan_id: 6754   channel: 11   network_key:     - 1     - 3     - 5     - 7     - 9     - 11     - 13     - 15     - 0     - 2     - 4     - 6     - 8     - 10     - 12     - 13   availability_blocklist: []   availability_passlist: [] device_options: {} blocklist: [] passlist: [] queue: {} frontend:   port: 8099 experimental: {} availability: false socat:   enabled: false   master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777   slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5   options: '-d -d'   log: false

I use this:
serial:
port: /dev/ttyACM0
adapter: deconz
Maybe try that. You can try resetting the usb by doing a reboot but really what did it for me was that serial statement.


ACL

[ ] 1.	Users should have access to the Menus according to their access.

[ ] 2.	Data Isolation

[ ] 3.	In Users > Create; Change the position of Role and Module.

[ ] 4.	 Roles will be suggested according to the selection of Module.

[x] 5. In Menu > List, Hide Delete Icon.

[x] 6.	Hide the Create Submenu from Menu Module.

[x] 7.	In Menu > List; Link columns texts should be disabled.

[x] 8.	In Menu > List; Hidden Column is not required.

[x] 9.	In Menu > List; Menu Title, Sort Order, Active icon should be only editable others should be fixed, non-editable.

[ ] 10.	In Menu > Manage, Module, menu permission field name, or check box is not needed. Change it into Arrow Icon.

[ ] 11.	A Captcha should be available in the login page. It should be similar like the PMIS.

[ ] 12.	If User selects the Remember ME option then the session will be remembered for 1 day.

[ ] 13.	In case of Forget Password, the flow will be like; User Name > Email > Click on the Link > Reset Password.

[ ] 14.	User Mapping, One user can be assigned to multiple modules and roles can be selected according to them.

[ ] 15.	In case of Session Out, a session out message should be provided for the users.

[ ]

In Menu > Manage, Module, menu permission field name, or check box is not needed. Change it into Arrow Icon. Solved in different way. Did not  add arrow but  menu permission and Check box is removed from the list

In Users >List ; Role for O&M is not showing the correct role.

O&M_USER is actually O&M_USER .... Since it contains special character, so it is encoded by the library used for drop down. It can't fixed.
I have a recommendation of not using the special characters.

Point no 13 -> In case of Forget Password, the flow will be like; User Name > Email > Click on the Link > Reset Password.
We don't need to show email here. By asking a user to prove the email is not safe for security purpose and also it includes one more check. It will be good to ask username from user to identification.

Path: Menu bar
** Issue: ** Arrows should be in outward corner.

Issue no-7 : In Menu > List ; Link columns texts should be disabled.
**Reference : **

Users should have access to the Menus according to their access.- Fixed
Data isolation fixed.
In Users > Create; Change the position of Role and Module.  Fixed
4.Roles will be suggested according to the selection of Module.   Fixed
In Menu > List, Hide Delete Icon.  Fixed
Hide the Create Submenu from Menu Module.  Fixed
In Menu > List; Hidden Column is not required.  Fixed
In Menu > List; Menu Title, Sort Order, Active icon should be only editable others should be fixed, non-editable. < Only ID and Link option is fixed others are editable.> - Not Fixed
In Menu > Manage, Module, menu permission field name, or check box is not needed. Change it into Arrow Icon. Fixed
A Captcha should be available in the login page. It should be similar like the PMIS.

User Mapping, One user can be assigned to multiple modules and roles can be selected according to them.- Fixed

In case of Session Out, a session out message should be provided for the users.

In case of Forget Password, the flow will be like; User Name > Email > Click on the Link > Reset Password.  Does not recognize User ID


Update Workflow to utilize arcaflow-docsgen

Changes introduced with this PR
Integrate reusable_workflow to generate documentation using arcaflow-docsgen. Also renamed the workflow file to simply workflow.yaml and changed the name to Arcaflow CI, as this has become more than just using Arcaflow Container Toolkit.

By contributing to this repository, I agree to the contribution guidelines.

Once approved I will use this template to update all official python plugin repositories to match.


Exclusive property for Accordion

This PR adds a new property called "exclusive" , which when enabled allows only one accordion to be open at any given time.

Wrong PR


Add Support for Xiaomi Smart Safe Cayo Anno 30Z Device

This pull request adds support for the Xiaomi Smart Safe Cayo Anno 30Z. It includes new BLEAction and MiBeacon converters, mapping for lock method and abnormal conditions, and sensor readings for action ID, abnormal condition, time, and battery.

Thanks!

https://github.com/AlexxIT/XiaomiGateway3/releases/tag/v3.3.0


Added a Project Report template in General Templates

Repo URL: Project Report Typst
It is a very simple template I have created for my students for their project report in college and university level.

Thanks for the awesome contribution @aurghya-0 !


Fix cocoeval version_max to 1.5.7

Sure @gfursin . We can do that either by using venv for a chain for sub dependency or docker. We eventually will need to do both.


ValueError: negative dimensions are not allowed

When I run test.py, this error will appear at the end

When I run test.py, this error will appear at the end

i get this error too.and i solve it by modify the test.py code refer to openpcdet

When I run test.py, this error will appear at the end

i get this error too.and i solve it by modify the test.py code refer to openpcdet

能分享以下怎么修改的么，你发的图片看不到。

You should figure out where your negative dimensions come from. I had a similar error; it turned out that the box type was not specified in the config, which is why the size was set to -1. Change the config type passed here (https://github.com/PJLab-ADG/DetZero/blob/12c1358de8bcd0a0f5d51312a0a976e388a4d2ba/detection/detzero_det/datasets/waymo/waymo_eval_detection.py#L87) to the one you need

You should figure out where your negative dimensions come from. I had a similar error; it turned out that the box type was not specified in the config, which is why the size was set to -1. Change the config type passed here (
https://github.com/PJLab-ADG/DetZero/blob/12c1358de8bcd0a0f5d51312a0a976e388a4d2ba/detection/detzero_det/datasets/waymo/waymo_eval_detection.py#L87
) to the one you need

Hello, may I ask where the specific configuration needs to be changed. thank.

anyone solved?

Traceback (most recent call last):
File "test.py", line 203, in
main()
File "test.py", line 199, in main
eval_single_ckpt(model, test_loader, args, eval_output_dir, logger, epoch_id, dist_test=dist_test)
File "test.py", line 64, in eval_single_ckpt
eval_utils.eval_one_epoch(
File "/home/ubt-346/devdata1/llz/DetZero/detection/tools/eval_utils.py", line 141, in eval_one_epoch
result_str, result_dict = dataset.evaluation(
File "/home/ubt-346/devdata1/llz/DetZero/detection/detzero_det/datasets/waymo/waymo_dataset.py", line 126, in evaluation
ap_result_str, ap_dict = waymo_eval(eval_det_annos, eval_gt_annos)
File "/home/ubt-346/devdata1/llz/DetZero/detection/detzero_det/datasets/waymo/waymo_dataset.py", line 112, in waymo_eval
ap_dict = eval.waymo_evaluation(
File "/home/ubt-346/devdata1/llz/DetZero/detection/detzero_det/datasets/waymo/waymo_eval_detection.py", line 256, in waymo_evaluation
metrics = self.build_graph(graph, config_type)
File "/home/ubt-346/devdata1/llz/DetZero/detection/detzero_det/datasets/waymo/waymo_eval_detection.py", line 159, in build_graph
metrics = detection_metrics.get_detection_metric_ops(
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/waymo_open_dataset/metrics/python/detection_metrics.py", line 154, in get_detection_metric_ops
variable_and_update_ops[name] = _update(name, update, init_shape, dtype)
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/waymo_open_dataset/metrics/python/detection_metrics.py", line 40, in _update
v = tf.compat.v1.get_local_variable(
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/ops/variable_scope.py", line 1727, in get_local_variable
return get_variable(
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/ops/variable_scope.py", line 1579, in get_variable
return get_variable_scope().get_variable(
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/ops/variable_scope.py", line 1322, in get_variable
return var_store.get_variable(
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/ops/variable_scope.py", line 578, in get_variable
return _true_getter(
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/ops/variable_scope.py", line 531, in _true_getter
return self._get_single_variable(
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/ops/variable_scope.py", line 952, in _get_single_variable
v = variables.VariableV1(
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/ops/variables.py", line 260, in call
return cls._variable_v1_call(*args, **kwargs)
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/ops/variables.py", line 206, in _variable_v1_call
return previous_getter(
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/ops/variables.py", line 199, in
previous_getter = lambda **kwargs: default_variable_creator(None, **kwargs)
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/ops/variable_scope.py", line 2612, in default_variable_creator
return resource_variable_ops.ResourceVariable(
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/ops/variables.py", line 264, in call
return super(VariableMetaclass, cls).call(*args, **kwargs)
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/ops/resource_variable_ops.py", line 1584, in init
self._init_from_args(
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/ops/resource_variable_ops.py", line 1722, in _init_from_args
initial_value = initial_value()
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/waymo_open_dataset/metrics/python/detection_metrics.py", line 39, in
initializer = lambda: tf.constant([], shape=init_shape, dtype=dtype)
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/framework/constant_op.py", line 264, in constant
return _constant_impl(value, dtype, shape, name, verify_shape=False,
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/framework/constant_op.py", line 281, in _constant_impl
tensor_util.make_tensor_proto(
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/tensorflow/python/framework/tensor_util.py", line 455, in make_tensor_proto
nparray = np.empty(shape, dtype=np_dt)
ValueError: negative dimensions are not allowed
Is this related to data sets? Instead of using the complete waymo dataset, I downloaded only part of v1.4.0, and then modified the contents of train.txt, val.txt, and text.txt. During the training, there was an error report of "AttributeError:'str 'object has no attribute' exists'". I solved it by modifying waymo_utils. At the test step, the error occurred again in the evaluation part.

When I use the pre training model：
Traceback (most recent call last):
File "test.py", line 203, in
main()
File "test.py", line 199, in main
eval_single_ckpt(model, test_loader, args, eval_output_dir, logger, epoch_id, dist_test=dist_test)
File "test.py", line 64, in eval_single_ckpt
eval_utils.eval_one_epoch(
File "/home/ubt-346/devdata1/llz/DetZero/detection/tools/eval_utils.py", line 141, in eval_one_epoch
result_str, result_dict = dataset.evaluation(
File "/home/ubt-346/devdata1/llz/DetZero/detection/detzero_det/datasets/waymo/waymo_dataset.py", line 126, in evaluation
ap_result_str, ap_dict = waymo_eval(eval_det_annos, eval_gt_annos)
File "/home/ubt-346/devdata1/llz/DetZero/detection/detzero_det/datasets/waymo/waymo_dataset.py", line 112, in waymo_eval
ap_dict = eval.waymo_evaluation(
File "/home/ubt-346/devdata1/llz/DetZero/detection/detzero_det/datasets/waymo/waymo_eval_detection.py", line 223, in waymo_evaluation
print(f"Prediction boxes3d min values: {pd_boxes3d.min(axis=0)}")
File "/home/ubt-346/anaconda3/envs/detzero/lib/python3.8/site-packages/numpy/core/_methods.py", line 43, in _amin
return umr_minimum(a, axis, None, out, keepdims, initial, where)
ValueError: zero-size array to reduction operation minimum which has no identity


Unexpected type reference between divided modules

TypeScript Version:  2.0.2
Code
sampleA.ts
{
    // local types
    type Data = string | boolean;
    let obj: Data = true;
    console.log(obj);
}
export { }

sampleB.ts
let v = "str" || true;

export { v }

tsconfig.json
{
    "compilerOptions": {
        "declaration": true,
        "skipDefaultLibCheck": true
    },
    "include": [
        "sample*.ts"
    ]
}

This is minimal settings.
When "declaration": true and "skipDefaultLibCheck": true, this issue is occured.
Expected behavior:
We can compile this code.
Actual behavior:
$ tsc -v
Version 2.0.2
$ tsc -p ./
sampleB.ts(1,5): error TS4023: Exported variable 'v' has or is using name 'Data' from external module "/private/tmp/hogehogehoge/sampleA" but cannot be named.

at glance root cause of the issue is caching of union types: type of Data in sampleA.ts is string | boolean and it is the same with type of v in sampleB.ts. However type in the first case has associated alias which is not visible if the same type is reused in different context.
Why error does not repro without skipDefaultLibCheck - I guess some declaration in lib.d.ts has the same type. This type will be put in the cache and used for both sampleA.ts and sampleB.ts will
// CC @ahejlsberg


ClassLoader Leak when adding spring-cloud-context dependency

I am currently trying to create my own version of the spring-boot-admin. Since we are still using a standalone Tomcat on our servers I am creating a war package. To discover memory leaks with regard to ClassLoader leaks we have created an integration test: https://github.com/evosec/tomcat-classloader-leak-test
Sadly the test fails for the spring-boot-admin. I could boil it down to the spring-cloud-context 1.2.0 dependency. I have created a demo project that demonstrates the issue: https://github.com/ArloL/spring-cloud-context-classloader-leak-demo
Note that master runs successfully and the spring-cloud-context branch fails.
The only difference is the added spring-cloud-context dependency: https://github.com/ArloL/spring-cloud-context-classloader-leak-demo/compare/master...spring-cloud-context
I have tried analyzing the heap dump with VisualVM as described in https://cdivilly.wordpress.com/2012/04/23/permgen-memory-leak. Be aware that the query is a bit different nowadays select x from org.apache.catalina.loader.ParallelWebappClassLoader x. This sadly did not give any helpful results.
Then I tried adding the classloader-leak-prevention-servlet3. Sadly this does not change the test result: https://travis-ci.org/ArloL/spring-cloud-context-classloader-leak-demo/builds/233563888. There is also no difference in the heap dump.
I do realize that deployment inside a standalone Tomcat is not in the focus of a spring-cloud dependency but maybe there is a bug (e.g. instantiated Servlet that is not properly destroyed) that is presenting itself due to this test. Maybe someone else has an idea about what's going on here. Thanks a lot :)

This is a major issue for anyone who wants to use spring-cloud features for traditional deployment on servlet containers. The bootstrap context adds itself as a parent to the root ApplicationContext but it's never closed, it's not a web context.
You can to add a listener that will close the root web application context and its parent. This can be done by overriding the SpringBootServletInitializer.onStartup() method somewhat like this:
servletContext.addListener(new ContextLoaderListener(rootAppContext) {
    @Override
    public void contextInitialized(ServletContextEvent event) {
        // no-op because the application context is already initialized
    }
    @Override
    public void contextDestroyed(ServletContextEvent event) {
        ApplicationContext parentAppContext = rootAppContext.getParent();
        super.contextDestroyed(event);
        if (parentAppContext != null) {
            SpringApplication.exit(parentAppContext, () -> 0);
        }
        parentAppContext = null;
    }
});

I can try to make a pull request on spring-boot but I don't know if it's relevant...

I can confirm that @mouellet is correct. See the build log of his PR that successfully runs https://travis-ci.org/ArloL/spring-cloud-context-classloader-leak-demo/builds/253899065
His branch where he added the logic: https://github.com/mouellet/spring-cloud-context-classloader-leak-demo/tree/spring-cloud-context
Is this something that has to be done by each application or can spring-cloud-commons fix this?

This is specifically when deployed to a standalone tomcat correct?

Hi @spencergibb, yes, that is correct.

Not limited to tomcat however. I can confirm the same behavior on WebLogic 12.1.3 & 12.2 and I suspect the same for all sevlet container...


msbot defaults to paid tier for Azure Search

When cloning a bot that has an Azure Search service in the recipie we default to the Standard tier which costs around $80/£60 a month. We cover this by highlighting what we're going to do up front and warn in the docs. However Azure Search is one of the few services that doesn't let you reduce the tier after cloning. Meaning you'd have to msbot disconnect, delete, create and msbot connect.
Thinking about this, it might be good to have a property in the recipe for in this qna to indicate you want the free tier. If you already have a free tier then creation will fail as azure search limits the free instances you can have. Perhaps in the validation step we can check if a free tier is available and throw an error or just simply through a warning at the validation step to say creation may fail later if a free tier already exists would simplify the logic.

As an additional note on this, the Standard service, which is currently being deployed for search, actually costs nearly £190 per month. At the very least I think the default should be Basic (approx. £60 per month) with a switch to allow to user to specify the search tier required when cloning service.

Is there likely to be any movement on this soon?  We now have a live customer project where this is going to be an issue for us when automating our environment deployments.
Thanks.

Pinging @sgellock and @yochay for a priority on this one.


fix: Add MongoDB 'name cannot be null' troubleshooting steps

Added steps on the query troubleshoorting page to troubleshoot MongoDB error that gives the error message Name cannot be null.
I wasn't able to reproduce this specific error message within Appsmith (I got other error messages that told me to add the database name), however here are some user support queries that reference this:

Includes error message and screenshot
User query solved by this advice
No conclusive solution, but mentions the error

Please let me know if I'm understanding the cause of the error correctly, since I wasn't able to reproduce it!
Resolves [appsmithorg/appsmith#16038]

Hey @danciaclara just checking in about the Error message component you mentioned above. I'm not 100% about what that is, let me know if any action is needed on my part! :)

@spark-c - I've added a new component that would highlight the error message. See PR#561. Once that PR is merged, you'll have to modify the error message to be added as a Message tag.


[BUG] Not all drives are recognised / not named recognisable

Go Hass Agent Version
7.3.1
Describe the bug
go-hass-agent seems to only create a sensor for one of my two drives. And interestingly this is the temperature of the second drive or sdb not sda. This sensor is named HOSTNAME_drivetemp_temp1_temp.
To Reproduce
Steps to reproduce the behaviour:

have two drives
start go-hass-agent

Expected behaviour
I would expect go-hass-agent to create two sensors. And it would be great, if the sensor represents the path or name of the drive.
Logs
go-hass-agent.log
Desktop (please complete the following information):

OS: Linux
Distribution Proxmox
Version  6.2.16-4-pve

Hey @dflvunoooooo, hmm, are both the drives the exact same make/model? The agent is using the Linux kernel hwmon API for userspace. So the hardware sensors are based off of whatever chips get exposed there. A device, like a hard drive or your CPU or graphics card, might expose zero or more chips. Each chip might have any number of sensors. The latter are what are exposed by the agent to Home Assistant.
To verify if the agent is missing a temp sensor for your sda drive, we could try some troubleshooting. Though the hwmon API is not the most featured API out there 😆
Firstly it might be worth checking the names of all the chips that are exposed:
cat /sys/class/hwmon/hwmon?/name

Note the names might be recognisable as a device, or could be something else. If you see one called sda, you've found the chips exposed by your drive.
If you found a chip called sda:
Note the directory under /sys that is listed, and you could then see if there are any files under those for temperature sensors:
ls /sys/class/hwmon/hwmonN/temp?_{input,label}

Replace N with the appropriate number. This will list out all the temp sensors that the agent will be able to read. Each temp sensor will have a tempN_label file containing its "name", used to derive the sensor name/id by the agent and a tempN_input file which is the actual reading/value. If you don't have both of those, then the device/chip doesn't have any temp sensors we can use.
If you didn't find a chip called sda:
It might be that the particular drive does not have a temp sensor, or it can't be exposed through hwmon for some reason. You can check the names of all temp sensors all chips are reporting with:
cat /sys/class/hwmon/hwmon?/temp?_label

This might help with correlating which chip is associated with your drives. You can then poke around in that directory to see if there is actually a temp sensor, it would need at least two files called tempN_label and tempN_input (where N is a number).
I do know that you might see a temp reported for this drive in other monitoring tools; they are likely using some other method to get it (like SMART attributes). I am planning on creating sensors for SMART attributes in the future.
Hope this helps!

Thank you for your very elaborate answer!
I have a Western Digital red SSD and a HDD. The model is definitely different. But the chip as you call it under /sys/class/hwmon/ is twice called drivetemp. Maybe that is the problem. Should the chips realy be called sda and sdb?
Under /sys/class/hwmon/hwmon2/temp1_input and /sys/class/hwmon/hwmon3/temp1_input there are different temperatures reported and the model under /sys/class/hwmon/hwmon2/device/model and /sys/class/hwmon/hwmon3/device/model is also different.
I can get the temperature with S.M.A.R.T. via smartctl -a /dev/sda | grep "Temperature" and in the same way for sdb.
Interestingly cat /sys/class/hwmon/hwmon?/temp?_label does only report the temperatures of the CPU cores and some package.
Package id 0
Core 0
Core 1
Core 2
Core 3
Core 4
Core 5

Okay, this should be fixed in the next release by https://github.com/joshuar/go-hass-agent/commit/16f56dda42ca9d3d525c2d0d59446549a7a7c5b0. There is some background in the commit message.
This unfortunately required changing the naming format of all chips, so will result in new sensors being recorded in Home Assistant.
The new naming convention will have a number appended to the chip name. So for example, where most Intel CPUs had a hwmon chip called "Coretemp", producing sensor names like "Coretemp Core 0 Temp", these will now be called "Coretemp 0 Core 0 Temp" (i.e., a number after "Coretemp"). Similar naming patterns are used for other chips. For example, for your two drives, there should now be several sensors with "Drivetemp 0 ..." and "Drivetemp 1 ..." prefixes.
Once you've installed the new release, you may want to remove the old sensors manually, under Developer Tools->Statistics in Home Assistant, for example. Or they can wait until they age out of the Home Assistant long-term statistics database automatically. Or, you can remove the agent from Home Assistant, wipe its config and then re-register it to remove any unused sensors.

Great! Thank you for you fast work! And thank you for changing so much code.
To represent sda or sdb is not possible with hwmon, I think. But couldn't the model under /sys/class/hwmon/hwmon2/device/model be used? For the drives this would represent the maker and had the benefit of knowing which of the numbered sensors is which.

Good idea! I've implemented that. Here is a temp sensor for a disk in one of my machines:

This will be in the next version.

Great, thank you for your work! I now have a sensor called WDC WD100EFAX-68 Temp1, but only the one. The second WDC WDS500G1R0A does not appear. Here is my log:
go-hass-agent.log

Hmm, on the system with the missing drive sensor, can you git clone the go-hass-agent source, then in the source directory, run:
go run pkg/linux/hwmon/examples/getAllSensors.go

This will print out all hwmon sensors and values, something like:
Acpitz 0 Temp1: 27.800 °C [Temp] (id: acpitz_0_temp_1, path: /sys/class/hwmon/hwmon0)
Iwlwifi 1 0 Temp1: 25.000 °C [Temp] (id: iwlwifi_1_0_temp_1, path: /sys/class/hwmon/hwmon5)
PM9A1 NVMe Samsung 1024GB Composite: 42.850 °C [Temp] (id: nvme_0_temp_1, path: /sys/class/hwmon/hwmon1) (crit: 84.850, max: 82.850, min: -273.150)
PM9A1 NVMe Samsung 1024GB Sensor 1: 42.850 °C [Temp] (id: nvme_0_temp_2, path: /sys/class/hwmon/hwmon1) (max: 65261.850, min: -273.150)
PM9A1 NVMe Samsung 1024GB Sensor 2: 46.850 °C [Temp] (id: nvme_0_temp_3, path: /sys/class/hwmon/hwmon1) (max: 65261.850, min: -273.150)
PM9A1 NVMe Samsung 1024GB Temp1 Alarm: 0.000  [Alarm] (id: nvme_0_temp_1_alarm, path: /sys/class/hwmon/hwmon1)
Dell Smm 0 Other: 69.000 °C [Temp] (id: dell_smm_0_temp_3, path: /sys/class/hwmon/hwmon3)
Dell Smm 0 Other: 32.000 °C [Temp] (id: dell_smm_0_temp_4, path: /sys/class/hwmon/hwmon3)
Dell Smm 0 Gpu: 40.000 °C [Temp] (id: dell_smm_0_temp_5, path: /sys/class/hwmon/hwmon3)
Dell Smm 0 Other: 50.000 °C [Temp] (id: dell_smm_0_temp_8, path: /sys/class/hwmon/hwmon3)
Dell Smm 0 Processor Fan: 5310.000 rpm [Fan] (id: dell_smm_0_fan_1, path: /sys/class/hwmon/hwmon3) (max: 5200.000, min: 5200.000, target: 5200.000)
Dell Smm 0 Motherboard Fan: 689.000 rpm [Fan] (id: dell_smm_0_fan_3, path: /sys/class/hwmon/hwmon3) (max: 3000.000, min: 0.000, target: 3000.000)
Dell Smm 0 Cpu: 54.000 °C [Temp] (id: dell_smm_0_temp_2, path: /sys/class/hwmon/hwmon3)
Dell Smm 0 Motherboard Fan: 718.000 rpm [Fan] (id: dell_smm_0_fan_2, path: /sys/class/hwmon/hwmon3) (max: 3000.000, min: 0.000, target: 3000.000)
Dell Smm 0 Ambient: 30.000 °C [Temp] (id: dell_smm_0_temp_6, path: /sys/class/hwmon/hwmon3)
Dell Smm 0 Other: 41.000 °C [Temp] (id: dell_smm_0_temp_7, path: /sys/class/hwmon/hwmon3)
Coretemp 0 Core 24: 42.000 °C [Temp] (id: coretemp_0_temp_26, path: /sys/class/hwmon/hwmon4) (max: 80.000, crit: 100.000)
Coretemp 0 Core 0: 44.000 °C [Temp] (id: coretemp_0_temp_2, path: /sys/class/hwmon/hwmon4) (max: 80.000, crit: 100.000)
Coretemp 0 Temp14 Alarm: 0.000  [Alarm] (id: coretemp_0_temp_14_alarm, path: /sys/class/hwmon/hwmon4)
Coretemp 0 Core 28: 44.000 °C [Temp] (id: coretemp_0_temp_30, path: /sys/class/hwmon/hwmon4) (crit: 100.000, max: 80.000)
Coretemp 0 Temp6 Alarm: 0.000  [Alarm] (id: coretemp_0_temp_6_alarm, path: /sys/class/hwmon/hwmon4)
Coretemp 0 Core 16: 42.000 °C [Temp] (id: coretemp_0_temp_18, path: /sys/class/hwmon/hwmon4) (max: 80.000, crit: 100.000)
Coretemp 0 Core 20: 45.000 °C [Temp] (id: coretemp_0_temp_22, path: /sys/class/hwmon/hwmon4) (max: 80.000, crit: 100.000)
Coretemp 0 Temp2 Alarm: 0.000  [Alarm] (id: coretemp_0_temp_2_alarm, path: /sys/class/hwmon/hwmon4)
Coretemp 0 Core 36: 41.000 °C [Temp] (id: coretemp_0_temp_38, path: /sys/class/hwmon/hwmon4) (crit: 100.000, max: 80.000)
Coretemp 0 Temp41 Alarm: 0.000  [Alarm] (id: coretemp_0_temp_41_alarm, path: /sys/class/hwmon/hwmon4)
Coretemp 0 Core 37: 41.000 °C [Temp] (id: coretemp_0_temp_39, path: /sys/class/hwmon/hwmon4) (crit: 100.000, max: 80.000)
Coretemp 0 Core 8: 44.000 °C [Temp] (id: coretemp_0_temp_10, path: /sys/class/hwmon/hwmon4) (crit: 100.000, max: 80.000)
Coretemp 0 Core 12: 43.000 °C [Temp] (id: coretemp_0_temp_14, path: /sys/class/hwmon/hwmon4) (max: 80.000, crit: 100.000)
Coretemp 0 Package Id 0: 45.000 °C [Temp] (id: coretemp_0_temp_1, path: /sys/class/hwmon/hwmon4) (max: 80.000, crit: 100.000)
Coretemp 0 Temp30 Alarm: 0.000  [Alarm] (id: coretemp_0_temp_30_alarm, path: /sys/class/hwmon/hwmon4)
Coretemp 0 Temp38 Alarm: 0.000  [Alarm] (id: coretemp_0_temp_38_alarm, path: /sys/class/hwmon/hwmon4)
Coretemp 0 Temp26 Alarm: 0.000  [Alarm] (id: coretemp_0_temp_26_alarm, path: /sys/class/hwmon/hwmon4)
Coretemp 0 Temp39 Alarm: 0.000  [Alarm] (id: coretemp_0_temp_39_alarm, path: /sys/class/hwmon/hwmon4)
Coretemp 0 Temp40 Alarm: 0.000  [Alarm] (id: coretemp_0_temp_40_alarm, path: /sys/class/hwmon/hwmon4)
Coretemp 0 Temp10 Alarm: 0.000  [Alarm] (id: coretemp_0_temp_10_alarm, path: /sys/class/hwmon/hwmon4)
Coretemp 0 Core 39: 41.000 °C [Temp] (id: coretemp_0_temp_41, path: /sys/class/hwmon/hwmon4) (crit: 100.000, max: 80.000)
Coretemp 0 Temp18 Alarm: 0.000  [Alarm] (id: coretemp_0_temp_18_alarm, path: /sys/class/hwmon/hwmon4)
Coretemp 0 Temp1 Alarm: 0.000  [Alarm] (id: coretemp_0_temp_1_alarm, path: /sys/class/hwmon/hwmon4)
Coretemp 0 Temp22 Alarm: 0.000  [Alarm] (id: coretemp_0_temp_22_alarm, path: /sys/class/hwmon/hwmon4)
Coretemp 0 Core 38: 41.000 °C [Temp] (id: coretemp_0_temp_40, path: /sys/class/hwmon/hwmon4) (crit: 100.000, max: 80.000)
Coretemp 0 Core 4: 41.000 °C [Temp] (id: coretemp_0_temp_6, path: /sys/class/hwmon/hwmon4) (crit: 100.000, max: 80.000)
Amdgpu 0 Fan1: 948.000 rpm [Fan] (id: amdgpu_0_fan_1, path: /sys/class/hwmon/hwmon2) (enable: 0.000, max: 3200.000, min: 0.000, target: 948.000)
Amdgpu 0 Sclk: 5000.000 Hz [Frequency] (id: amdgpu_0_freq_1, path: /sys/class/hwmon/hwmon2)
Amdgpu 0 Mclk: 96000.000 Hz [Frequency] (id: amdgpu_0_freq_2, path: /sys/class/hwmon/hwmon2)
Amdgpu 0 Ppt: 0.000 W [Power] (id: amdgpu_0_power_1, path: /sys/class/hwmon/hwmon2) (average: 16000.000, cap: 186000.000, cap_default: 186000.000, cap_max: 186000.000, cap_min: 174000.000)
Amdgpu 0 Pwm1: 0.000 Hz [PWM] (id: amdgpu_0_pwm_1, path: /sys/class/hwmon/hwmon2) (enable: 2.000, max: 255.000, min: 0.000)
Amdgpu 0 Junction: 56.000 °C [Temp] (id: amdgpu_0_temp_2, path: /sys/class/hwmon/hwmon2) (crit: 110.000, crit_hyst: -273.150, emergency: 115.000)
Amdgpu 0 Vddgfx: 0.862 V [Voltage] (id: amdgpu_0_in_0, path: /sys/class/hwmon/hwmon2)
Amdgpu 0 Edge: 50.000 °C [Temp] (id: amdgpu_0_temp_1, path: /sys/class/hwmon/hwmon2) (crit: 110.000, crit_hyst: -273.150, emergency: 115.000)
Amdgpu 0 Mem: 54.000 °C [Temp] (id: amdgpu_0_temp_3, path: /sys/class/hwmon/hwmon2) (crit: 105.000, crit_hyst: -273.150, emergency: 110.000)
{"level":"info","time":"2024-04-29T10:02:48+10:00","message":"Mem stats: alloc=6mb total_alloc=6mb sys=17mb heap_alloc=6mb heap_sys=11mb heap_idle=3mb heap_released=3mb heap_in_use=7mb stack_in_use=512kb stack_sys=512kb mspan_sys=95kb mcache_sys=30kb buck_hash_sys=1mb gc_sys=1mb other_sys=1mb mallocs_n=5342 frees_n=389 heap_objects_n=4953 gc_cpu_fraction=0.12"}

Can you paste that output here? From it, we should be able to see what is going on with the sensors.

I ran into a version error. It is a proxmox sevrer, so it runs debian. It seems to want version 1.23
/home/kevin/go-hass-agent/go.mod:3: invalid go version '1.22.0': must match format 1.23

My go version seems to be 1.19
user@proxfuji:~$ go version
go version go1.19.8 linux/amd64

Hey that's super interesting, that you get a different number of sensors when you run that, its the exact same code used by the agent! :confused: Do you get a different number of sensors each time you run it? Note the order they are displayed might change, as the chips are processed in parallel.
I think I can see the problem from the logs and this output. The sensor ID I generate, which is used as an entity ID in Home Assistant, is still not unique. I've got a code change that should fix this, though it'll break sensor output in Home Assistant again unfortunately. I'll circle back when it is committed.
Side note: yeah I build with whatever is the latest and greatest Go version. You don't need Go installed to use the binaries, just for building. I use the official Go installation instructions rather than any package provided by my distro, which is often not the latest version. The build system also follows this installation method.

That is strange. Does the path from which it is run matter? No, every time the same amount. But there are only the temperature sensors. go-hass-agent finds alto more sensors than just temperature sensors.
I see, sorry to be the cause of so much headache. Thank you for your work!
Great, I followed that installation instructions too.

That's super odd. I can't explain how the output of the command and the agent would differ. They are literally calling the exact same code :confused: It shouldn't matter where you run that command.
Anyway I have been refactoring the code so that it generates unique sensors for duplicate hardware drivers, like two hard drives both having a drivetemp driver listed, as you do.
Can you try out the latest build artifacts from here? Please note, this build will create new entities in Home Assistant for all hardware sensors. However, these builds should support the situation in this issue.
Please grab whichever artifact you need for your architecture (amd64, arm or arm64). Inside the archive will all the packages for that architecture that would normally be included on the release page. So  you can pick whichever one you would normally use to upgrade an existing install.
 sensors for various temp, fan, power etc. sensors. For those hard drives, you should see sensors named "WDC ... Temp ..." (i.e., named after the hard drive).
I'm having trouble reproducing this problem locally, as none of my systems have multiple drivetemp sensors and I haven't worked out how I could artificially reproduce this scenario. But I do hope these artifacts either fix or move in the right direction.

I don't know. Maybe I downloaded a different version or something.
Awesome! This verion fixes the problem and both hdds are displayed with the modenumber, great work!

The only "Hardware Sensor …" entities I see are for coretemp. I don't know if this is intended. I am sorry to be such a bother. But I am happy to help if I can and certainly test everything!

Brilliant! I'm glad we got to the bottom of this. Thank you for your patience and assistance resolving this and also for the suggestion to use the drive labels. I think the sensors look much nicer in Home Assistant now!

Everything seems to be working, thank you!


First draft changes for adding PITR workflow APIs

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

I've just added a summary of my changes.

/azp run automation - sdk

/azp run automation - sdk

        "code": {

if you are updating this can you inherit from the common definition here:  specification\common-types\resource-management\v1\types.json

Refers to: specification/cosmos-db/resource-manager/Microsoft.DocumentDB/preview/2020-06-01-preview/cosmos-db.json:4494 in 2505433. [](commit_id =<PHONE_NUMBER>e7361997a120da277e6214cafea97e, deletion_comment = False)

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

LGTM. Ready to merge?

@ruowan , This PR is ready to merge. Please help me merge at the earliest


After authentication, the ui redirects to logout

 Issue by skinkie
Tuesday Jul 10, 2018 at 18:25 GMT
Originally opened as https://github.com/catalogueglobal/datatools-ui/issues/207

I tried to setup catalogue. After I got Auth0 to work (this part needs to be better documented) I stumbled upon the UI logging me out every time after sign in.
The error that pops up is: err = TypeError: Cannot read property 'datatools' of undefined at receiveTokenAndProfile (http://catalogue.openov.nl/dist/index.js:38117:69) at http://catalogue.openov.nl/dist/index.js:262636:35 at http://catalogue.openov.nl/dist/index.js:10675:24 at
I did set up the datatools section in my Auth0 user in the app_metadata section. But the /userprofile does not contain this section, it does include things like nickname, picture (gravatar). There are quite some pages on Google about this issue, hence more people must have hit it.
How to move forward?

 Comment by joelhaasnoot
Tuesday Jul 10, 2018 at 19:12 GMT

Auth0 has done some things over the last year or so to make itself OIDC compliant. That's nice, but they haven't been good about their documentation. The app_metadata feature no longer works well for new accounts, see https://community.auth0.com/t/how-can-i-make-app-metadata-available-in-userinfo-endpoint/6664 - it needs to be namespaced if added with a hack/rule.

 Comment by skinkie
Tuesday Jul 10, 2018 at 19:23 GMT

https://github.com/catalogueglobal/datatools-ui/pull/72

 Comment by abyrd
Wednesday Jul 11, 2018 at 15:49 GMT

I just talked to @landonreed about this - apparently Auth0 has changed significantly but Conveyal's Auth0 account still functions as it did before those changes, because it was created before the changes.
We of course need to update this project to work with current-day Auth0 but hadn't confronted the problem yet. @landonreed is working on it.

 Comment by landonreed
Tuesday Jul 24, 2018 at 20:26 GMT

As I mentioned in #72, the proposed solution of using an Auth0 rule to make the app_metadata available in the user profile doesn't seem to play nicely with our existing production applications (i.e., it wipes out the app_metadata field that currently exists in the profile).  After attempting to implement a few different fixes without much success (partly due to the removal of the tokeninfo endpoint see catalogueglobal/datatools-server#102, it seems like a good bet is to entirely rethink how Auth0 is used in this application.
One approach we are considering is something that we have discussed previously internally: storing user permissions in a Users collection in the datatools-server MongoDB database. The authentication would still be handled by Auth0, but the user_id associated with the user would be used to lookup the permissions, which would be sent back to the client's browser to determine their access to the application.  I'll continue to update this issue as we make decisions and progress on this topic, but if other users have input on this approach, please do share it.

 Comment by ilarimikkonen
Tuesday Oct 09, 2018 at 15:27 GMT

Hi,
are there any plans on how to proceed with enabling the Auth0 for new Auth0 accounts? I have experimented with this and corresponding serverside fix, and login works OK. Unfortunately now we are facing problems getting all other things (editor) working.
We'd be interested in further developing this, if it fits our needs. Unfortunately we are now stuck as we cannot verify if the editor has needed functionality

 Comment by landonreed
Tuesday Oct 09, 2018 at 18:30 GMT

Do the editor problems you're experiencing already have tickets documenting the issues? Or are the problems you're facing related to the Auth0 issue?
We are looking to resolve a number of outstanding PRs this week in both the UI and Server repositories.

 Comment by ilarimikkonen
Wednesday Oct 10, 2018 at 05:39 GMT

I did not create issues. I was not sure that it would make sense to create issues when I've used a branches that are not merged to dev or master. I have a guess that they are somehow Auth0 related, but I'm not sure. Those problems I'm experiencing may have something to do with the changes I did to the code.
I think the work that you have done is great. Would you guys be willing to have a quick call where I explain what we are trying to accomplish? I think that would help us resolve this quicker. I can make an issue, but there is the chance that my setup is somehow wrong and we spend a lot of time figuring that out

 Comment by xaverio
Thursday Oct 18, 2018 at 17:51 GMT

Same problem as issue's title
After authentication, the ui redirects to logout


[Question] How to disable edition of specific nodes while using Flow?

Hello
When using Flow, if you select a node, a field in the right panel will let you change its label.
I want to disable this behavior for some (not all) nodes, so only certain ones are editable.
Is that possible? If so, how? Thanks in advance.

one potential solution (may not be the best way)

set a specific model property for your uneditable nodes (e.g. 'tag')

// section in demo/FlowItemPanel.js
<Item
    type="node"
    size="72*72"
    shape="flow-circle"
    model={{
        color: '#FA8C16',
        label: 'Start',
        tag: 'readOnly',
    }}
/>

make Input antd component disabled if tag matches above

// section in demo/DetailForm.js
renderNodeDetail = () => {
    const { form } = this.props;
    const { label, tag } = this.item.getModel();

    return (
      <Item label="Label" {...inlineFormItemLayout}>
        {form.getFieldDecorator('label', {
          initialValue: label,
        })(<Input onBlur={this.handleSubmit} disabled={tag==='readOnly'}/>)}
      </Item>
    );
  };


Update BASE_VERSION to master-2023-11-28T19-01-20

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
f9e0c84bb2d2278329c9416c4aa91b57c5fe0b74
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
f9e0c84bb2d2278329c9416c4aa91b57c5fe0b74
link
unknown
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-istiodremote


(pdb-2034) schema error on replace-facts with escape-quoted strings

Without this commit we're broken on escape-quoted fact names and fact names
containing #~. Some escape-quoting we do before storage was causing different
names to come out of realize-paths! than went in, which caused an empty key
lookup that led to the error.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/155/
Test PASSed.

I'll reopen this on stable


doc: specify which files to delete during strip simulator archs step before submission to App Store

Thanks!


Update UAA to use our "fix"

What
See https://github.com/alphagov/paas-uaa/commit/f9705f0e3ed621cd7bc289261e69fc4cc9b9e611
Who can review
@richardTowers

Merging, done as pair with @richardTowers


c++ feature request: support return of Result<Vec, Error>

already implemented and tested in c++_tests TestResult::f4


DefaultCanvas repeat = 1 may be too simplistic

Discussion from #64 Summarized Below

@parijatm @arvuce22 I think having the unit cell height (and for that matter, the unit cell width) is a nice thing to be encoded in the grid. I think at least the m2 centerline grid should have a repeat of the number of m2 lines per unit cell. Arvind and I discussed this a while back. Unfortuanately, this doesn't help with the stop point grid. Maybe we need to support triples as well so we can get the (row, grid line in the row, minor grid line of the stop point grid). This should be straightforward to do but might be confusing to use. Maybe we can skip it for now (add an issue so we can remember to look at it later) since we shouldn't need to manipulate stop point grids very often (for example if we use ASCII diagrams.)

The triplet does sound easy to implement. And I think usage should be pretty straightforward as well in case the cell height is an integral multiple of relevant metal pitches. My main concern is what happens in case of a non-integral repeat. We can error out of course and force the user to specify a valid cell height. But this might be hard to do for all layers without making the UnitCell too big.
Alternatively, we could just pick one layer (such as M2) like we had done in our previously. If its just one layer though, we could think of some mechanism to override the default repeats as well... As in construct the DefaultCanvas with repeat = 1 & provide some mechanism to override the repeat.

We don't use DefaultCanvas for more complicated PDKs. Closing.


Catches exception thrown by Ember 2.0 when no item is selected #91

Ember 2.0 changed the behavior of Ember.get(obj, keyName). If obj is undefined or null, older versions of Ember return undefined. With the changes of Ember 2.0 this behavior changed and an exception is been thrown. This exception can be reproduced when no item is selected (selection = null).
The changes restore the old behavior of Ember.get by wrapping it in the method _getWithExceptionHandling.
See issue #91

@ninoraubaum I think that testing obj instead would be more idiomatic. Something like:
_get(obj, keyName) {
  if (obj) { return get(obj, keyName); }
  else { return undefined; }
}

Do you agree, and if so, would you mind updating the PR?
Thanks a lot.


Export icon should also be clickable and on clicking on it items should be exported.Implement this wherever export is used.

Framework Version: 0.1.3

Framework Version: 0.1.4
Fixed


how to specify the part number (namely via helm chart)

Is the new way to specify the part number for podtato to use set the environment variable PODTATO_PART_NUMBER on the deployments?  If so, it would be helpful to expose an easy way to specify this via the helm chart (and possibly other delivery methods?).
Happy to turn this into a pull request if it is the right approach, or someone else could include it in their own PR.
Branch with helm changes: https://github.com/MxNxPx/podtato-head/commit/5229dab58496884b7e242452e10feb2fbb02318b

An env var for changing the served part is an intended approach, a PR for an integration like that would be great, thanks!


Upgrading Java8 cask is broken

General troubleshooting steps

[X] I have retried my command with --force and the issue is still present.
[X] I have checked the instructions for reporting bugs (or making requests) before opening the issue.

[X] None of the templates was appropriate for my issue, or I’m not sure.

[X] I ran brew update-reset && brew update and retried my command.
[X] I ran brew doctor, fixed as many issues as possible and retried my command.
[X] I understand that if I ignore these instructions, my issue may be closed without review.

Description of issue
Running brew cask upgrade on java8 fails with the following error:

curl: (23) Failed writing body (0 != 12462)
==> Purging files for version 1.8.0_162-b12,0da788060d494f5095bf8624735fa2f1 of Cask java8
Error: Download failed on Cask 'java8' with message: Download failed: http://download.oracle.com/otn-pub/java/jdk/8u162-b12/0da788060d494f5095bf8624735fa2f1/jdk-8u162-macosx-x64.dmg

I suspect it is related to: https://github.com/caskroom/homebrew-cask/issues/42890
Output of your command with --verbose --debug
$ brew cask upgrade --verbose --debug
==> Upgrading 4 outdated packages, with result:
caskroom/versions/java8 1.8.0_162-b12,0da788060d494f5095bf8624735fa2f1, vagrant 2.0.2, vagrant-manager 2.6.0, virtualbox 5.2.6-120293
==> Started upgrade process for Cask java8
==> Hbc::Installer#fetch
==> Satisfying dependencies
==> Downloading
==> Downloading http://download.oracle.com/otn-pub/java/jdk/8u162-b12/0da788060d494f5095bf8624735fa2f1/jdk-8u162-macosx-x64.dmg
/usr/bin/curl --show-error --user-agent Homebrew/1.5.2-50-gaf8f8f1 (Macintosh; Intel Mac OS X 10.12.6) curl/7.54.0 --fail --location --remote-time --continue-at - --output /Users/me/Library/Caches/Homebrew/Cask/java8--1.8.0_162-b12,0da788060d494f5095bf8624735fa2f1.dmg.incomplete http://download.oracle.com/otn-pub/java/jdk/8u162-b12/0da788060d494f5095bf8624735fa2f1/jdk-8u162-macosx-x64.dmg -b oraclelicense=accept-securebackup-cookie
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   527  100   527    0     0   1049      0 --:--:-- --:--:-- --:--:--  1049
Warning: Failed to create the file
Warning: /Users/me/Library/Caches/Homebrew/Cask/java8--1.8.0_162-b12,0da7
Warning: 88060d494f5095bf8624735fa2f1.dmg.incomplete: No such file or
Warning: directory
  0  247M    0 13830    0     0  24197      0  2:58:28 --:--:--  2:58:28 24197
curl: (23) Failed writing body (0 != 13830)
==> Purging files for version 1.8.0_162-b12,0da788060d494f5095bf8624735fa2f1 of Cask java8
Error: Download failed on Cask 'java8' with message: Download failed: http://download.oracle.com/otn-pub/java/jdk/8u162-b12/0da788060d494f5095bf8624735fa2f1/jdk-8u162-macosx-x64.dmg
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/download.rb:42:in `rescue in fetch'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/download.rb:40:in `fetch'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/download.rb:15:in `perform'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:126:in `download'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:51:in `fetch'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/upgrade.rb:56:in `block in run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/upgrade.rb:29:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/upgrade.rb:29:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/abstract_command.rb:35:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:98:in `run_command'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:168:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:132:in `run'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:8:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:100:in `<main>'
Error: Kernel.exit
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:173:in `exit'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:173:in `rescue in run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:156:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:132:in `run'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:8:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:100:in `<main>'

Output of brew cask doctor
$ brew cask doctor
==> Homebrew-Cask Version
Homebrew-Cask 1.5.2-50-gaf8f8f1
caskroom/homebrew-cask (git revision 6f0fc; last commit 2018-02-05)
==> macOS
10.12.6
==> SIP
Enabled
==> Java
1.8.0_152
==> Homebrew-Cask Install Location
<NONE>
==> Homebrew-Cask Staging Location
/usr/local/Caskroom
==> Homebrew-Cask Cached Downloads
~/Library/Caches/Homebrew/Cask
==> Homebrew-Cask Taps:
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask (3902 casks)
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-versions (177 casks)
==> Contents of $LOAD_PATH
/usr/local/Homebrew/Library/Homebrew/cask/lib
/usr/local/Homebrew/Library/Homebrew
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/gems/2.3.0/gems/did_you_mean-1.0.0/lib
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/site_ruby/2.3.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/site_ruby/2.3.0/x86_64-darwin9.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/site_ruby/2.3.0/universal-darwin9.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/site_ruby
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/vendor_ruby/2.3.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/vendor_ruby/2.3.0/x86_64-darwin9.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/vendor_ruby/2.3.0/universal-darwin9.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/vendor_ruby
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/2.3.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/2.3.0/x86_64-darwin9.0
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/2.3.0/universal-darwin9.0
==> Environment Variables
LC_ALL="en_US.UTF-8"
PATH="/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/Homebrew/Library/Homebrew/shims/scm"
SHELL="/bin/bash"

If you ignore this guide, your issue may be closed without review.

https://github.com/caskroom/homebrew-cask/blob/master/doc/reporting_bugs/a_cask_fails_to_install.md#curl-error

I followed the format exactly as followed by the linked issue. This issue is almost certainly the same or very similar issue except that it applies to the versioned java8 instead of the mainline java. The issue is not a simple CURL issue meaning it does not fit into one of your existing templates as best as I can tell. The issue is that the site wants some cookies for an accepted license.
When I have manually navigated to the java website and manually accepted the license the download link that is being tried by cask works:
http://download.oracle.com/otn-pub/java/jdk/8u162-b12/0da788060d494f5095bf8624735fa2f1/jdk-8u162-macosx-x64.dmg

The issue has nothing to do with the other one. They’re both curl errors, but that’s where the similarities end.
I can’t reproduce your problem. brew cask fetch java8 works without an issue.

Well, I have no idea what has happened. I have changed nothing on the machine that I tried this on this morning. I tried a brew cask fetch java8 as you did which began downloading as expected. So I tried a brew cask upgrade which then began working properly. Maybe the fetch command initiated something that upgrade doesn't?

Let’s chalk it up to “computers are weird and sometimes things stop working and get fixed without our intervention”.
What matters is that it’s working now for you!


toggle-header  is not working

as of 0.3.1
the code calls the command "application:toggle-header"
and that triggers all-right in a standalone jlab
however when inside fun-mooc it does not

this one is hard to reach
primarily one would expect to just have to do this
app.commands.execute('application:toggle-header')
BUT
first off there's the usual race condition side of things, and there's a need to wait for the command to get registered, something like this https://github.com/parmentelat/jupyterlab-nbhosting/blob/0ef235d634a12254ba1462195ea773172ae0d603/src/index.ts#L264-L279
AND
even with this in place, we never get the change event corresponding to that command, even though the function is accessible through either menu or palette...

this is now fixed within 0.4.2


chore(workspace): Prep release

Overview
Prepares for the first release of the crates.

#301  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @clabby and the rest of your teammates on  Graphite

Codecov Report
Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 79.6%. Comparing base (258f020) to head (5607b99).

Files
Patch %
Lines

crates/executor/src/lib.rs
0.0%
4 Missing :warning:

Additional details and impacted files

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


Johannes/javasrc diffgraph

This still needs to be done, but it'll probably be easier to just to it in a new branch by now.


[Not an issue] Autoclicker broken ? Nope.

Accidentally, i erased my local .js with my options. The actual script seems to not work properly regarding the autoclicker, am i the only one ? Did Valve change something about that ?
// version 3.8.1
Edit : Okay well, check the last comment. One click to rule them all o/.

It does, you just don't see the clicks anymore to reduce lag and the memory leak.

If i display text, i see it for my own clicks but not the ones of the autoclicker. I don't think it's normal.
And when i check the datas over here, the number of clicks / person is extremely low compared to yesterday.

It condenses the clicks down so it clicks 1 and is read by the server 20 times.
I believe that is what wchill said yesterday.
Not sure what to make of the click data, I didn't really believe any of them yesterday because they were all over the board. Some in the quadrillions+ and some in the billions.

Yeah, something isn't working correctly. I'm not getting any click gold, and lane switching does not seem to be functioning properly (yes, I have auto-fire cannon).

From: MY AUTOCLICKER IS BROKEN!
"No it isn't. This is because the script is using the newer click method and it only has to "click" once per second (but it counts 20 times).
Your crits, money, damage, etc. will all appear once per second, and they represent the whole second. (So all Raining Gold money in one second will appear at one time.)"
-wchill

You might be right about the lane switching because mine isn't working, although it's possible that the lag is just too much and it's not able to switch.

I don't think it is working, because I am getting a very small amount of gold from bosses when they are staying alive for 5+ seconds. If I manually click, I got a billion (server side)

I was able to see it more clearly on a boss. Seems like it's working properly indeed. And it's switching lanes.
Anyway, kudos to the devs ;).

Just tried using the script on Chrome with TamperMonkey and it worked fine. Firefox with GreaseMonkey does not like the script for whatever reason.

I'm not seeing the click damage text but the autofire damage text is showing. I'm also using Firefox, so I'm guessing something in the overnight changes isnt supported by greasemonkey?

And lane changing is definitely broken too.

Chrome (v43.0.2357.124 m) with Tampermonkey (v3.11) doesn't seem to autoclick as of version 3.8.3. It's almost hard to tell on spawners because they die so quickly in my current room, but I can spam-click manually on bosses and farm several hundred million gold. If I do nothing, my gold increases in-line with my auto cannon but nothing else.
All other features appear to work as intended.

I can definitely say that autoclick is still working. If you see a blue number at all, it is working.

Lane changing is working for me, so I will need more information (browser, environment, are you on latest version?)

Waterfox 38.0 with Greasemonkey 3.2 on Windows 8. Script version is 2.8.3

(My lane-switching is working, since this thread seems to be about two different features not working, but possibly for a related reason.)
I see blue text, but if auto-clicking is working, gold harvested from it while a Raining Gold power-up is active is not adding to my bank (though it doesn't make sense for those to be disconnected).
I can provide any kind of logs/debugging info.

Are you sure the gold collected isn't added to your "bank" afterwards ? It can take a few seconds before you see it in your total. For me at least, lvl 1541 and counting, it's working as intended. It was just quite confusing at the beginning because mobs were dying so fast i was seeing 1 level / 20 almost.

@Harest You might be correct; Level 1073 and counting, though now that I'm watching it people are nuking bosses -- I am seeing several million added to the bank a few seconds after the boss dies.
It didn't occur to me that the client-side gold update of the old-style autoclicker might be a usability optimisation that syncs with the server on a different interval.

No blue text in Firefox 39, and I've only seen lane switching work a couple of times.
I also see this error in the javascript console: TypeError: this.m_rgLaneData[this.m_rgPlayerData.current_lane] is undefined

@Yves-Be: are you using Tamper/Greasemonkey?

Okay, now that I've encountered a boss that lived for more than two seconds, I can confirm my autoclicking report can be disregarded. My gold is increasing at rates I would expect. It was simply a visual disconnect of my human brain.

I use Greasemonkey

Lane switching not working in Greasemonkey confirmed:
TypeError: this.m_rgLaneData[this.m_rgPlayerData.current_lane] is undefined running.js:1113:0
TypeError: this.m_data is undefined enemies.js:126:1

Try copy paste and see if that works. I have a good idea of why it's broken in Greasemonkey.

Copy paste seems to work.

Copy paste what exactly?

@Thiana Use the manual instructions. Copy/paste the whole script into your browsers console and hit Enter.

With the cut+paste method both click damage and lane changing are working.

I was copy/paste in Chrome, and it wrote me:
"undefined
VM194:1019 Locking to element 1 as chosen by SteamID
VM194:159 Uncaught TypeError: Cannot set property 'innerHTML' of null"
That's ok?

@jamesssun: refresh before you copy paste.

I/m sorry, but how?

Turn off the Tampermonkey-Script, then Refresh, then copy&paste raw script, otherwise script is running twice

Sorry for this question. Is that mean, if i'm install script in Tampermonkey, i don't need to copy/paste, it's wroks already?

Same issue on Firefox 38.0.5 Mac OS X 10.10.3 Using GreaseMonkey.
No visible error in console exept :
TypeError: this.m_rgLaneData[this.m_rgPlayerData.current_lane] is undefined1 running.js:1113:0
But this error is visible even when not using the script, so it doesn't seems related.
Copy paste script works fine !

This issue is due to be closed, no?

Yep


Proguard "Unable to instantiate VerticalBlockViewFactory" error

Hi,
I'm getting an "Unable to instantiate VerticalBlockViewFactory" error when using Proguard. Everything works fine without Proguard.
The same issue was observed here as well. I tried creating an exclusion for the VerticalBlockViewFactory class but that didn't work.
Please help.
Thanks

Make sure the VerticalBlockViewFactory class is not renamed. It is loaded by name as a convenience since most developers will use this library for block rendering, while preventing a circular dependency between the two libraries.
As I noted in the thread you pointed to, you need to add an exception to prevent Proguard from renaming VerticalBlockViewFactory.  I haven't tested it, but it looks like...
-keepnames class com.google.blockly.android.ui.vertical.VerticalBlockViewFactory

...is the right option. As noted previously, there may me other classes (particularly field view classes with loaded by layout files) that may also need to be excluded.

Thanks, the exception worked for me, so I closed the issue.
Cheers!


Determine what changes we need to support r750 in the Alias lab

It seems the r750 nodes in the Alias lab ended up installing a cluster however the playbook timed out on max recursion.  We should root cause why those machines took so long to boot into their post discovery install.  Perhaps the machines have a really long boot cycle until they boot the disk we installed on?

For Alias lab, we might just need to switch to curl commands as documented here with a non-root user able to set the virtual media.
It is still unclear why the r750s took so long to boot, maybe @mcurrier2 can help discern to the long boot times?

On @mkarg75 environment bm_control_plane_install_disk: /dev/sdk allowed the install to succeed. (Install onto disk sdk)

Closing this, reopen if further issues occur.


Metrics are reported before actual action. (e.g PUT request to S3)

As a result metrics can be misleading when action did not complete (e.g failed request to S3)
Spotted in ingester e.g here: https://github.com/weaveworks/cortex/blob/master/ingester/ingester.go#L607
Not yet sure if somewhere else as well.
Mentioned that already here: https://github.com/weaveworks/cortex/issues/319

@Bplotka good catch.  Would welcome a PR to fix this...

I know I know ^^
Worst user ever.. only complaining and not fixing... Will do my best to catch up on this!
Fix for this issue: https://github.com/weaveworks/cortex/pull/336

Fix, merged.


Dependabot/cargo/aws config 0.101

Issue #, if available: N/A
Description of changes:
https://github.com/awslabs/aws-nitro-enclaves-cose/pull/78 and https://github.com/awslabs/aws-nitro-enclaves-cose/pull/79 had to be done in lockstep for it to work.
Additionally, aws-config introduced a breaking change where behavior-version-latest feature needs to be used when constructing the SdkConfig struct.
Finally, MSRV needs to be updated to 1.70.0 as aws-smithy-runtime (a dependency of aws-sdk-kms) needs 1.70 to compile.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Done similarly in https://github.com/awslabs/aws-nitro-enclaves-cose/commit/b12ed3a556982e89af6137824ea0530ce84e2734


_SESSION is not working for CORS

$_SESSION does not work with CORS fetch

If you have a problem with CORS it means you are mixing your application with another different source.
In that case, you will need to allow CORS in your server side. You will find a lot of CORS examples and explanations on the web.


Add Conference Module

Coverage decreased (-0.6%) to 44.122% when pulling eaff6e06de17fbd5693c76e91c3486a6c3681b77 on caffffe:add-conference-module into 96f96eaa2a26fcb14e9d125eb7320a2f424fbb09 on ringcentral:master.

Coverage decreased (-0.6%) to 43.844% when pulling 459877a3ff1177640119eeae98744bd24da6373e on caffffe:add-conference-module into 6ab0bb3df48de707e9e2e0bf6baf74384f1b2694 on ringcentral:master.


Clarify scope

I think we should clarify whether this action should include things like preprocessing links, dealing with uncommitted changes, renaming README.md ➡ Home.md etc. This issue is to

Track as a "todo" for @jcbhmr to write down all the things discussed in this issue (if any) and put them into a readme or similar document
Actually discuss what to do about the open questions about scope

Open questions

If I want to rename README.md to Home.md in my wiki, does that belong here or do i need to manually mv wiki/README.md wiki/Home.md in my workflow?
If I want to change all markdown links to strip off the .md suffix so they work on the wiki, is that in scope here, or should that be done in a preprocess step like Andrew-Chen-Wang/strip-md-suffix-markdown-links or similar?

/assign jcbhmr
Originally posted by @jcbhmr in https://github.com/Andrew-Chen-Wang/github-wiki-action/issues/9#issuecomment-1464362090
@Andrew-Chen-Wang are there any other scope questions that you want addressed/documented/discussed?

in my opinion which I am perfectly OK with being overruled is that these are both out of scope and should be encouraged to:
- uses: actions/checkout
- uses: user/strip-md-links
  with:
    path: wiki
- run: git add -A && git commit --amend --no-edit
- uses: Andrew-Chen-Wang/github-wiki-action

or similar

You know I'm just now realizing how much I have just interjected myself forcefully into this project... 🤔 is this OK with you @Andrew-Chen-Wang or would you like my to pump the brakes a bit?

happy to make you a co maintainer. I'll just add in a review requirement before merging for both of us. appreciate it as work has taken a toll on me which meant less OSS work!

If I want to rename README.md to Home.md in my wiki, does that belong here or do i need to manually mv wiki/README.md wiki/Home.md in my workflow?

Should be a flag default True.

If I want to change all markdown links to strip off the .md suffix so they work on the wiki, is that in scope here, or should that be done in a preprocess step like Andrew-Chen-Wang/strip-md-suffix-markdown-links or similar?

Not sure what you mean here.

run: git add -A && git commit --amend --no-edit

Not fully opposed to pre-processing actions, but we want to do as much as possible inside the script and give users an option/flag unless it's not possible. Also strive to keep backwards compatibility.

If I want to change all markdown links to strip off the .md suffix so they work on the wiki, is that in scope here, or should that be done in a preprocess step like Andrew-Chen-Wang/strip-md-suffix-markdown-links or similar?

Not sure what you mean here.

What I'm talking about is the problem discussed in #8 where a link like [View our help page](./Help.md) works only when viewing it in the GitHub source tree but them if you just push that file to the wiki, the .md suffix won't work because links are no longer https://github.com/Andrew-Chen-Wang/github-wiki-action/blob/master/README.md, they are https://github.com/Andrew-Chen-Wang/github-wiki-action/wiki/Test-Page-1
Note that the README.md is README.md, not just README as it would be when deployed to the wiki itself.

If I want to change all markdown links to strip off the .md suffix so they work on the wiki, is that in scope here, or should that be done in a preprocess step like Andrew-Chen-Wang/strip-md-suffix-markdown-links or similar?

What I'm getting at here is: which of these do you want? Do we want to offer that feature or do we want it to be a preprocess step done by some other action?
- uses: user/strip-md-links@v1
- uses: EndBug/add-and-commit@v9
- uses: Andrew-Chen-Wang/github-wiki-action@v4

- uses: Andrew-Chen-Wang/github-wiki-action@v4

Not fully opposed to pre-processing actions, but we want to do as much as possible inside the script and give users an option/flag unless it's not possible. Also strive to keep backwards compatibility.

Awesome ❤ thanks for the vision clarification.
Here's some ideas of a list of features to tout on the README:

We auto-rename README.md to Home.md
We auto-strip .md from link suffixes
We support auto commit of changes

happy to make you a co maintainer. I'll just add in a review requirement before merging for both of us. appreciate it as work has taken a toll on me which meant less OSS work!

Cool! 👍 I'll try to be somewhat cautious and incremental with my changes and PRs.


[Release Radar Request] Keep your secrets secret!

Open Source Project name
Trousseau
What is your project?
The Trousseau project provides a Kubernetes native way to encrypt the secret resources within the standard etcd using the Kubernetes KMS provider framework.
This allows to no have to deploy application with an extra set of sidecars, have the Dev team learns about how to manage/interact different KMS solutions, and adapt deployments for CD/GitOps workflows by leverage the standard Kubernetes API for secret management and a fully transparent in-transit encryption using a remote key from e.g. Vault.
Version
1.0.0
Date
December 1st, 2021
Description of changes
This is our first major and stable release hitting the ground this December 1st with full support of Hashicorp Vault Community and Enterprise edition. More KMS to come!
GitHub Repo
https://github.com/Trousseau-io/trousseau
Website
https://trousseau.io/
Link to changelog
https://github.com/Trousseau-io/trousseau/releases/tag/v1.0.0
Social media
https://www.linkedin.com/posts/trousseau-io_github-trousseau-iotrousseau-store-and-activity-6878980107009171456-22IY
Anything else to add?
Indeed You rock! Thank you for providing such a great platform and exposure.

Congrats on being featured in the December Release Radar 🥳

Read the blog here
Check out our GitHub Tweet
Feel free to retweet Mish's tweet featuring you

Keep an eye on our YouTube Channel for a December Release Radar promo video 😄