[Device Support Request] Bosch Smoke Alarm II

Is your feature request related to a problem? Please describe.
Pairing works but no controls or sensors are detected
Describe the solution you'd like
Would love if we could get this device to work. I think it should be possible to read the alarm status, the battery status and also trigger the alarm.

Device signature - this can be acquired by clicking on the "Zigbee Device Signature" button in the device settings
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4617, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0402",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x0020",
        "0x0500",
        "0x0b05"
      ],
      "out_clusters": [
        "0x0019"
      ]
    }
  },
  "manufacturer": "Bosch",
  "model": "RBSH-SD-ZB-EU",
  "class": "zigpy.device.Device"
}

Diagnostic information - this can be acquired by clicking on the "Download Diagnostics" button in the device settings
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2022.5.4",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.9.9",
    "docker": true,
    "arch": "x86_64",
    "timezone": "Europe/Vienna",
    "os_name": "Linux",
    "os_version": "5.10.108",
    "supervisor": "2022.05.1",
    "host_os": "Home Assistant OS 7.6",
    "docker_version": "20.10.9",
    "chassis": "vm",
    "run_as_root": true
  },
  "custom_components": {
    "hacs": {
      "version": "1.24.5",
      "requirements": [
        "aiogithubapi>=21.11.0"
      ]
    },
    "opensprinkler": {
      "version": "1.1.8",
      "requirements": [
        "pyopensprinkler==0.7.2"
      ]
    },
    "alexa_media": {
      "version": "3.11.3",
      "requirements": [
        "alexapy==1.25.5",
        "packaging>=20.3",
        "wrapt>=1.12.1"
      ]
    }
  },
  "integration_manifest": {
    "domain": "zha",
    "name": "Zigbee Home Automation",
    "config_flow": true,
    "documentation": "https://www.home-assistant.io/integrations/zha",
    "requirements": [
      "bellows==0.29.0",
      "pyserial==3.5",
      "pyserial-asyncio==0.6",
      "zha-quirks==0.0.73",
      "zigpy-deconz==0.16.0",
      "zigpy==0.45.1",
      "zigpy-xbee==0.14.0",
      "zigpy-zigate==0.7.4",
      "zigpy-znp==0.7.0"
    ],
    "usb": [
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*2652*",
        "known_devices": [
          "slae.sh cc2652rb stick"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*zigstar*",
        "known_devices": [
          "ZigStar Coordinators"
        ]
      },
      {
        "vid": "1CF1",
        "pid": "0030",
        "description": "*conbee*",
        "known_devices": [
          "Conbee II"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8A2A",
        "description": "*zigbee*",
        "known_devices": [
          "Nortek HUSBZB-1"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8B34",
        "description": "*bv 2010/10*",
        "known_devices": [
          "Bitron Video AV2010/10"
        ]
      }
    ],
    "codeowners": [
      "@dmulcahey",
      "@adminiuga"
    ],
    "zeroconf": [
      {
        "type": "_esphomelib._tcp.local.",
        "name": "tube*"
      }
    ],
    "after_dependencies": [
      "usb",
      "zeroconf"
    ],
    "iot_class": "local_polling",
    "loggers": [
      "aiosqlite",
      "bellows",
      "crccheck",
      "pure_pcapy3",
      "zhaquirks",
      "zigpy",
      "zigpy_deconz",
      "zigpy_xbee",
      "zigpy_zigate",
      "zigpy_znp"
    ],
    "is_built_in": true
  },
  "data": {
    "ieee": "**REDACTED**",
    "nwk": 55672,
    "manufacturer": "Bosch",
    "model": "RBSH-SD-ZB-EU",
    "name": "Bosch RBSH-SD-ZB-EU",
    "quirk_applied": false,
    "quirk_class": "zigpy.device.Device",
    "manufacturer_code": 4617,
    "power_source": "Battery or Unknown",
    "lqi": 148,
    "rssi": -63,
    "last_seen": "2022-05-14T02:29:09",
    "available": true,
    "device_type": "EndDevice",
    "signature": {
      "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4617, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
      "endpoints": {
        "1": {
          "profile_id": 260,
          "device_type": "0x0402",
          "in_clusters": [
            "0x0000",
            "0x0001",
            "0x0003",
            "0x0020",
            "0x0500",
            "0x0b05"
          ],
          "out_clusters": [
            "0x0019"
          ]
        }
      }
    },
    "entities": [],
    "neighbors": [],
    "endpoint_names": [
      {
        "name": "IAS_ZONE"
      }
    ],
    "user_given_name": null,
    "device_reg_id": "f1b27eb989277500e68560e9bc2f6747",
    "area_id": null
  }
}

Additional context
This is a very newly released product. What I can tell is that it uses Zigbee 3.0. The IEEE Device ID as well as the install code is printed on the inside of the device. Pairing worked fine by invoking zha.permit and then connecting the battery. However no controls or sensors are available.
I am happy to perform any testing. I just don't have any in-depth knowledge of the zigbee protocol / zigpy so I don't know where to start

Has there been any update regarding this? I'm trying to make the Bosch Smoke Alarm II work with deCONZ but it won't even connect.
On another note: were you able to integrate the Bosch Smoke Alarm II into Home Assistant using Boschs smart home coordinator maybe?

I would be interested in this feature, too.

@Schnabulation as I don't have a Bosch Smart Home Controller I dont't know if all features would be supported that way.
But zigpy does currently support reading smoke alarm status and battery status. I don't know which zigpy update added the basic compatiblity but it was not long after opening this issue.
It would be very nice if we could be able to trigger the smoke alarm via zigbee as this is a feature available when using the official controller and app from Bosch

Hello @mnadvornik,
how should it look like?
How my device looks:

I get no Battery status and if i press the test button, the sensor stays at off..
Thx.

@011V32 :
Hi,
I've also 7 of those at home connected through ZHA.
It seems if you don't see a battery your pairing was not 100% successful.
I've "Factory Reset" those according to the manual and started the pairing again.
Afterwards they worked fine.

Hello @kfroeschl,
Thx. Now I see the battery status. 👍
What shoud "Identify" and "laszone" do?
If I press the smoke alarm, i can hear the alarm, but no status is raised in HA?
(If I press Identity nothing happend?)

Thx

@011V32 :
"Identify": Lets the red light of the sensor blink twice.
"iaszone": "Clear": No Smoke, "Dedected": Smoke. I've used it for an automation to send a Notification to the phone if it would detect anything. Though I've never triggered them with real smoke so far.

Just so you know: pressing the smoke alarm manually does not trigger the sensor. This is the same if using the Bosch SHC.

I was able to make them sound the alarm by calling the IasZone/init_test_mode command

This could also be called from a service if required.
Though I would need to read the actual Zigbee IasZone Cluster Specification to know what SHC is calling to sound the alarm.

I do not have init_test_mode, but zone_status with the same ID?

wrong tab:

My mistake. Sry
Something is still not right. The Last Seen is when I paired the device. When I run Identify, there is something in the log, but nothing flashes on the device.

When I run the test command I get the following error:

I've also tried putting the device right next to the stick... with no success

I would guess your paring was still not successful.
I had a similar behavior for some of my Devices. The device needs to "CheckIn" once an hour and update the "Last Seen".
Like it is now in your screenshot you will loose the information in some hours.
You may try again:

Reset the Device
1.1 Remove Battery
1.2 Wait for 1 minute or press the button (to remove remaining voltage
1.3 Hold the button
1.4 Insert the Battery
1.5 Wait for Device to make a sound
Wait for the device to start (at least 10 seconds)
Call the Permit Service in HomeAssistant
Press the Device Button until it sounds
Release the Device Button
Press it again for a short time
Finish the Setup in HA (like for any other Zigbee Device)

I hope i remembered all steps correctly.

All good things are 3. :P
LQI and RSSI is only displayed under Device Info and not under Diagnostic?

you can disable/enable specific entities.
enabling those would also keep their history which normally makes little sense.
(except error diagnosis maybe)

May I ask guys: were you able to integrate with or without Bosch Smart Home Controller?

without.
with "Bosch Smart Home Controller" would require a different integration (Bosch SHC i guess)

Ok thanks. Then I'll try the smoke alarm with my Conbee III and ZHA later. Will provide feedback here.

Not successful, pairing didn't work since ZHA was not able to find the smoke alarm. Tested with Conbee III stick.

I am using a Sonoff Zigbee Bridge connected to Home Assistant ZHA without any issues. The only thing missing is manually triggering the alarm

are you using the bridge pro or stick?
if bridge pro: just directly connected to your computer running HA via usb?

are you using the bridge pro or stick?
if bridge pro: just directly connected to your computer running HA via usb?

This one: https://sonoff.tech/product/gateway-and-sensors/zbbridge/
Using Tasmota as Firmware and EZSP protocol
imo the smoke detector should theoretically work with any hardware supported by zigpy / zha.
I don't know if the Bosch smoke detector supports Zigbee 2 but since your Conbee III seems to support Zigbee 3.0 this shouldn't be the issue.
Are you sure you tried the paring with the correct install code printed on the smoke detector?

can you maybe please elaborate on this:
Pairing worked fine by invoking zha.permit and then connecting the battery
How do I invoke zha.permit?

can you maybe please elaborate on this:
Pairing worked fine by invoking zha.permit and then connecting the battery
How do I invoke zha.permit?

It is explained in the documentation: https://www.home-assistant.io/integrations/zha/#service-zhapermit
I haven't found a simple tutorial but it really isn't more than calling the service via the developer tools using the data on the device (or packaging, can't remember). Seems like there is a QR code feature now so if there is a qr code on the smoke detector you can use that instead of the address and install code (don't want to unmount mine from the ceiling to check)

After filling in the details, the service won't start: Fehler beim Aufrufen des Diensts zha.permit. Unknown error
👎

can you paste the ha-logs in the chat?
btw. i don't remember filing out 2 IEEE back then but only one.
(Only "Quelle IEEE" and "Installationscode")
I also did't use the dashes ("-") in the "Installationscode"
(since i pasted the values from the QR code scanner and deleted the rest)

I tested also with qr code only (without quelle IEEE and installationscode). There were several error logs then:

Logger: homeassistant.helpers.script.websocket_api_script
Quelle: helpers/script.py:1805
Erstmals aufgetreten: 07:40:25 (15 Vorkommnisse)
Zuletzt protokolliert: 07:53:02

websocket_api script: Error executing script. Invalid data for call_service at pos 1: some but not all values in the same group of inclusion 'install_code' @ data[<install_code>]
other error log:

[547600176832] Error handling message: some but not all values in the same group of inclusion 'install_code' @ data[<install_code>]. Got None (invalid_format) SH9 from <IP_ADDRESS> (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36)

After reading through some github sites, I noted that Conbee sticks simply do not support adding devices via sha.permit yet.
For further details I link to the threads I found helpful:
https://github.com/dresden-elektronik/deconz-serial-protocol/issues/20#issuecomment-1431599456
https://github.com/Koenkk/zigbee2mqtt/issues/17492
Will order a Sonoff 3.0 USB Dongle Plus (P-version) now to check if the problem is solved then.

Conbee III doesn't support install codes. Conbee II I believe does.

I can't confirm, that Bosch smoke detector are working with ZHA&SkyConnect coordinator.
I've tried two smoke detectors in my HA-installation. ZHA detects the device and the interview starts, but won't finish, so I couldn't use them in my home. Now I'm looking for other Zigbee-Smoke-Detectors which will working with ZHA&SkyConnect.

I know this one is closed, but for all trying to pair it and land here. I had success pairing it by using the "QR-Code" only.
How I did it:

Scan the QR code at the bottom of the device (the bigger and longer one. If you only see one, it's probably the right one).
I went into the developer tools, services and choose "zha.permit".
Leave the duration as is at 60 secs and checked
checked "QR-Code" and pasted the code 1:1 the way the scan result gave it (no dashes, no blanks, just as a whole long string)
Pressed execute --> Resulting in "success"
Went to Settings - Devices & Services and got into the "ZHA"
Press "Add Device" - the same way as I would any other Zigbee device
The smoke detector was found right away and after a few seconds it went to "initializing" That took maybe another 2 min until all was fine and set up.

I hope that helps others...

@NightDragon1 , can you tell me about your experience with the smoke detector and ZHA? Are you still using the smoke detector with ZHA and what is the command to query the battery status?
I'm quite new to Zigbee and currently only use a Lidl smart blind with ZHA.

@Smarthome-Creator Yes I'm still using it. due to it's price I only have one. But plan to buy more asap.
I set it up exactly as I wrote and had no issues so far. Stable connection, but it's not very verbose in general. Guess it's a normal behavior to save battery. In regards of the command - I'm not sure if my value is correct, but it's not that old, so could be it's still 100%. It never had to go off... so...

You can issue a lot of commands, and it does response to them quite well. Just for now I was looking for the polling time. Don't mask me for the unit. Could be hours - as said it's not very verbose and I see it every here and there sending a "all good"

@Smarthome-Creator
I think this is the command you had been looking for:


Expose miniMongo and Meteor api the same way they are in the Meteor app

So you don't have to learn/do stuff differently.
They should be transparent, although what the functions return might be wrapped with more compatibility stuff.

Wontfix. With the mixin api in 1.0.0 it should be easy to make a mixin which replicates the Meteor api.


[bug 1091716] Allow about: and chrome:// URLs in client-side validation

While performing client-side validation of a URL, allow about: and
chrome:// URLs. Similar fix on the server side has already been done
as a part of fixing bug 1057617.

One minor style nit, but everything else looks good!

Awesome--this looks great!

fff1101 [bug 1091716] Allow about: and chrome:// URLs in client-side validation


Error trying to install crate bzip2-sys

I'm trying to install the zip crate that depends on bzip2 but I'm getting the following error.
Using Rust nightly 1.31.0 ("2018 edition")
Compiling bzip2-sys v0.1.6
error: failed to run custom build command for `bzip2-sys v0.1.6`
process didn't exit successfully: `C:\Dev\[project]\target\debug\build\bzip2-sys-33f8cb5c7dfcf9ea\build-script-build` (exit code: 101)
--- stdout
TARGET = Some("x86_64-pc-windows-msvc")
OPT_LEVEL = Some("0")
HOST = Some("x86_64-pc-windows-msvc")
CC_x86_64-pc-windows-msvc = None
CC_x86_64_pc_windows_msvc = None
HOST_CC = None
CC = Some("C:\\mingw-w64\\x86_64-7.3.0-posix-seh-rt_v5-rev0\\mingw64\\bin\\gcc.exe")
CFLAGS_x86_64-pc-windows-msvc = None
CFLAGS_x86_64_pc_windows_msvc = None
HOST_CFLAGS = None
CFLAGS = None
DEBUG = Some("true")
running: "C:\\mingw-w64\\x86_64-7.3.0-posix-seh-rt_v5-rev0\\mingw64\\bin\\gcc.exe" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-I" "bzip2-1.0.6" "-D_WIN32" "-DBZ_EXPORT" "-DBZ_NO_STDIO" "/FoC:\\Dev\\[project]\\target\\debug\\build\\bzip2-sys-351245291296f0d0\\out\\bzip2-1.0.6\\blocksort.o" "/c" "bzip2-1.0.6/blocksort.c"
cargo:warning=gcc.exe: error: /FoC:\Dev\[project]\target\debug\build\bzip2-sys-351245291296f0d0\out\bzip2-1.0.6\blocksort.o: Invalid argument
cargo:warning=gcc.exe: error: /c: No such file or directory
exit code: 1

--- stderr
thread 'main' panicked at '

Internal error occurred: Command "C:\\mingw-w64\\x86_64-7.3.0-posix-seh-rt_v5-rev0\\mingw64\\bin\\gcc.exe" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-I" "bzip2-1.0.6" "-D_WIN32" "-DBZ_EXPORT" "-DBZ_NO_STDIO" "/FoC:\\Dev\\[project]\\target\\debug\\build\\bzip2-sys-351245291296f0d0\\out\\bzip2-1.0.6\\blocksort.o" "/c" "bzip2-1.0.6/blocksort.c" with args "gcc.exe" did not execute successfully (status code exit code: 1).

', C:\Users\[user]\.cargo\registry\src\github.com-1ecc6299db9ec823\cc-1.0.25\src\lib.rs:2260:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Thanks for the report! It looks, though, like you're compiling for MSVC but you've set CC to a MinGW compiler. Did you mean to compile for MinGW?

I have both MSVC and MinGW installed, so it should be able to use either one. which g++ gives me the MinGW one, I'm not sure how I can check which one Cargo uses? Everything else I've tried builds fine with cargo build, only this crate gives an error.

The cc crate, which configures compilers, is reading the explicitly set CC env var and that overrides the default compiler, cl.exe, for the MSVC target. If you want this to "just work" when compiling for MSVC you'll need to unset the CC env var.

Unsetting the CC env did solve it, thanks!

In case anyone else runs into this, apparently, on OSX, if AR is set, it is likely to cause build issues. Unsetting it (and CC) solves this problem.

In case anyone else runs into this, apparently, on OSX, if AR is set, it is likely to cause build issues. Unsetting it (and CC) solves this problem.

Installing cctools from Mac Ports seems to do the trick!

Hey! Complete noob here. What does it mean to set AR and CC? Where are they (AR & CC) set? Thanks for any help.

We're talking about environment variables (often called 'env' for short). These are system-wide global variables that can be read by all applications on your machine, CC for example is used by some programs to point to an installed C compiler.
Each OS has a different way to manage them, you can look up 'how to set environment variables on [your system]' to find out how to do this.


Azure Files Work?

This article specifically calls out "Storage Accounts, Table Storage and Blob Storage", but does not mention File Storage. Not sure if this is on purpose (if not supported) or if a customer should assume that File Storage falls under Storage Accounts and thus is supported. Clarification around using Azure Files with AVS is important so customer can utilize Azure Files storage and not have to hold data locally on the cluster, similar to Blob Storage.

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

ID: 88c9f403-10e7-59e6-20c7-7f2964c010ed
Version Independent ID: d5b05dfd-1035-0525-67a0-e46eca8c0de8
Content: Concepts - Storage - Azure VMWare Solution
Content Source: articles/azure-vmware/concepts-storage.md
Service: azure-vmware
GitHub Login: @shortpatti
Microsoft Alias: v-patsho

#assign @shortpatti

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

#assign @divka78

divka78 is already assigned.

Azure Files is currently not supported.
#please-close


How to refresh configuration in .NET Framework

I followed this instruction to create a console app. ConfigurationManager.RefreshSection("configBuilders"); does no help.

@VALLIS-NERIA the .NET Framework configuration system does not support configuration change after the application is started. Please note this is a limitation of the .NET Framework ConfigurationManager.

@VALLIS-NERIA please let me know if you have other questions. I am closing this issue for now.


Node: implement LSET

https://valkey.io/commands/lset/

Remember to do npm run lint and npm run prettier:format to address CI failture.

Can you add a CHANGELOG entry as well? We'll need to do this whenever we add new Node commands

Can you add a CHANGELOG entry as well? We'll need to do this whenever we add new Node commands

When you create upstream PR from your node/integ_cyip10_lset to valkey-io:main, it will be the time to update CHANGELOG with your PR #. This PR is just an internal PR review.


BetterBuild v2

made some tiny changes to improve the build system again, this is more related to the dependencies and cmake, also updated the build.yml to accomodate the changes

The branch can be deleted after this update

I would recommend using "squash merge" instead of "merge."


Auto Flip not working Desktop WSL

bazel build -c opt --define MEDIAPIPE_DISABLE_GPU=1 mediapipe/examples/desktop/autoflip:run_autoflip
INFO: Writing tracer profile to '/root/.cache/bazel/_bazel_root/14fe9c30d99db7d79d243c0ceda4896c/command.profile.gz'
INFO: Analyzed target //mediapipe/examples/desktop/autoflip:run_autoflip (1 packages loaded, 41 targets configured).
INFO: Found 1 target...
ERROR: /home/qianyiiii/mediapipe/mediapipe/examples/desktop/autoflip/BUILD:37:1: Linking of rule '//mediapipe/examples/desktop/autoflip:run_autoflip' failed (Exit 1) gcc failed: error executing command /usr/bin/gcc @bazel-out/k8-opt/bin/mediapipe/examples/desktop/autoflip/run_autoflip-2.params
Use --sandbox_debug to see verbose messages from the sandbox
bazel-out/k8-opt/bin/mediapipe/calculators/image/_objs/scale_image_calculator/scale_image_calculator.o:scale_image_calculator.cc:function cv::Mat::~Mat(): error: undefined reference to 'cv::Mat::deallocate()'
bazel-out/k8-opt/bin/mediapipe/calculators/image/_objs/scale_image_calculator/scale_image_calculator.o:scale_image_calculator.cc:function cv::Mat::~Mat(): error: undefined reference to 'cv::fastFree(void*)'
bazel-out/k8-opt/bin/mediapipe/calculators/image/_objs/scale_image_calculator/scale_image_calculator.o:scale_image_calculator.cc:function mediapipe::ScaleImageCalculator::Process(mediapipe::CalculatorContext*): error: undefined reference to 'cv::resize(cv::_InputArray const&, cv::OutputArray const&, cv::Size, double, double, int)'
bazel-out/k8-opt/bin/mediapipe/calculators/image/_objs/scale_image_calculator/scale_image_calculator.o:scale_image_calculator.cc:function mediapipe::ScaleImageCalculator::Process(mediapipe::CalculatorContext*): error: undefined reference to 'cv::fastFree(void*)'
...
(remaining 62 argument(s) skipped)
error: undefined reference to 'cv::VideoWriter::VideoWriter(cv::String const&, int, double, cv::Size_, bool)'
bazel-out/k8-opt/bin/mediapipe/calculators/video/_objs/opencv_video_encoder_calculator/opencv_video_encoder_calculator.o:opencv_video_encoder_calculator.cc:function mediapipe::OpenCvVideoEncoderCalculator::Close(mediapipe::CalculatorContext*): warning: the use of tmpnam' is dangerous, better use mkstemp'
bazel-out/k8-opt/bin/mediapipe/calculators/video/_objs/opencv_video_encoder_calculator/opencv_video_encoder_calculator.o:opencv_video_encoder_calculator.cc:function mediapipe::OpenCvVideoEncoderCalculator::Open(mediapipe::CalculatorContext*): error: undefined reference to 'cv::VideoWriter::fourcc(char, char, char, char)'
bazel-out/k8-opt/bin/mediapipe/framework/formats/_objs/image_frame_opencv/image_frame_opencv.o:image_frame_opencv.cc:function mediapipe::formats::MatView(mediapipe::ImageFrame const*): error: undefined reference to 'cv::Mat::Mat(int, int const*, int, void*, unsigned long const*)'
collect2: error: ld returned 1 exit status
Target //mediapipe/examples/desktop/autoflip:run_autoflip failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 14.439s, Critical Path: 12.25s
INFO: 0 processes.
FAILED: Build did NOT complete successfully

The error is MediaPipe didn't find OpenCV library. Could you report how you install OpenCV on WSL?

See https://github.com/google/mediapipe/issues/562#issuecomment-606203557 if you use the setup_opencv.sh

如果使用setup_opencv.sh，请参见＃562（注释）。

Sorry, I found that my problem is the configuration problem of opencv, which was solved yesterday. Thank you very much for your reply

Sure, no problem!


O11Y-3138: Improve Adherence to Specification

Which problem is this PR solving?
This library does not closely adhere to the OpenTelemetry Specification. To improve adherence to the specification and lay the ground-work for null-safety, this PR makes the following changes:

NonRecordingSpan is no longer exported from the API package.  Consumers should use Span from that package instead.
Span is no longer exported from the SDK package.  Consumers should use Tracer to obtain Spans, or reference Span from the API package instead.
Span.setStatus now uses a positional optional parameter for description.
Tracer from the SDK package now has a protected constant constructor with non-optional arguments.
Span from the SDK package now has a protected constructor with non-optional arguments.

How Has This Been Tested?

Confirmed passing unit tests
Updated a test application from a previous version. Confirmed that changes operate properly after updates.

Security Insights
No security relevant content was detected by automated scans.
Action Items

Review PR for security impact; comment "security review required" if needed or unsure
Verify aviary.yaml coverage of security relevant code

Questions or Comments? Reach out on Slack: #support-infosec.

Public API Changes
Recommendation: :bangbang: Major version bump (fyi @Workiva/semver-audit-group )
@@ opentelemetry/api.dart <-- package:opentelemetry/src/api/trace/nonrecording_span.dart#L20 @@
-  class NonRecordingSpan implements Span
// Removing a class is a major change.

-     SpanKind get kind
//    Removing a field is a major change.

-     void recordException(dynamic exception, {StackTrace stackTrace})
//    Removing a method is a major change.

-     bool get isRecording
//    Removing a field is a major change.

-     void setStatus(StatusCode status, {String description})
//    Removing a method is a major change.

-     void setAttribute(Attribute attribute)
//    Removing a method is a major change.

-     SpanId get parentSpanId
//    Removing a field is a major change.

-     Int64 get endTime
//    Removing a field is a major change.

-     void setAttributes(List<Attribute> attributes)
//    Removing a method is a major change.

-     void end()
//    Removing a method is a major change.

-     void addEvent(String name, Int64 timestamp, {List<Attribute> attributes})
//    Removing a method is a major change.

-     SpanStatus get status
//    Removing a field is a major change.

-     String name
//    Removing a field is a major change.

-     NonRecordingSpan NonRecordingSpan(SpanContext _spanContext)
//    Removing a constructor is a major change.

-     Int64 get startTime
//    Removing a field is a major change.

-     InstrumentationLibrary get instrumentationLibrary
//    Removing a field is a major change.

-     SpanContext get spanContext
//    Removing a field is a major change.

      From dart:core/object.dart
-     bool ==(Object other)
//    Removing a method is a major change.
-     int get hashCode
//    Removing a field is a major change.
-     Type get runtimeType
//    Removing a field is a major change.
-     String toString()
//    Removing a method is a major change.
-     dynamic noSuchMethod(Invocation invocation)
//    Removing a method is a major change.

@@ opentelemetry/sdk.dart <-- package:opentelemetry/src/sdk/trace/span.dart#L16 @@
-  class Span implements Span
// Removing a class is a major change.

-     void recordException(dynamic exception, {StackTrace stackTrace})
//    Removing a method is a major change.

-     Span Span(String name, SpanContext _spanContext, SpanId _parentSpanId, List<SpanProcessor> _processors, TimeProvider _timeProvider, Resource _resource, InstrumentationLibrary _instrumentationLibrary, {SpanKind kind, List<Attribute> attributes, List<SpanLink> links, Context parentContext, SpanLimits limits, Int64 startTime})
//    Removing a constructor is a major change.

-     InstrumentationLibrary get instrumentationLibrary
//    Removing a field is a major change.

-     void addEvent(String name, Int64 timestamp, {List<Attribute> attributes})
//    Removing a method is a major change.

-     void setStatus(StatusCode status, {String description})
//    Removing a method is a major change.

-     SpanContext get spanContext
//    Removing a field is a major change.

-     SpanStatus get status
//    Removing a field is a major change.

-     void setAttributes(List<Attribute> attributes)
//    Removing a method is a major change.

-     List<SpanLink> get links
//    Removing a field is a major change.

-     void end()
//    Removing a method is a major change.

-     SpanKind get kind
//    Removing a field is a major change.

-     Resource get resource
//    Removing a field is a major change.

-     SpanId get parentSpanId
//    Removing a field is a major change.

-     void setAttribute(Attribute attribute)
//    Removing a method is a major change.

-     int get droppedAttributes
//    Removing a field is a major change.

-     bool get isRecording
//    Removing a field is a major change.

-     Int64 get startTime
//    Removing a field is a major change.

-     Int64 get endTime
//    Removing a field is a major change.

-     String name
//    Removing a field is a major change.

-     Attributes get attributes
//    Removing a field is a major change.

      From dart:core/object.dart
-     bool ==(Object other)
//    Removing a method is a major change.
-     String toString()
//    Removing a method is a major change.
-     int get hashCode
//    Removing a field is a major change.
-     Type get runtimeType
//    Removing a field is a major change.
-     dynamic noSuchMethod(Invocation invocation)
//    Removing a method is a major change.

@@ opentelemetry/api.dart <-- package:opentelemetry/src/api/trace/span.dart#L36 @@
abstract class Span
-     void setStatus(StatusCode status, {String description})
+     void setStatus(StatusCode status, [String description])
//    `description` was removed.
//    Removing a parameter is a major change.

Showing results for 8205a4594c0b8aefc98968735ccd7fa2462ae06f

Powered by semver-audit-service. Please report any problems by filing an issue.
Reported by the dart semver audit client 2.2.2
Browse public API.


Clean up plotting of resonance circles (#97)

Clean up plotting of resonance circles

Add marker size and fontsize arguments
Add downsampling arguments for data plotting
Remove filename from title
Next step is change directory naming scheme
Remove initial guess circle from plotting
Plot fit over full data range
Change color schemes in plots
Next step would be to further cleanup
Make other cosmetic changes

Update fit_S_data.py

Applying changes to fit curve line width and resonance circle markers.

I made the changes as requested on the previous pull request. I think we are ready to merge.


Broken build

Looks like 96bf2dd2d0f6e8533, once released in dist/, created the problem.
Assigning to @guillaumepotier, in hope you can figure out what's going on. I tried my best but not familiar enough with the plethora of js environments to fix.
I thought maybe cfa623c607671d031fb965ad80fad0a561b7cbff would be good, it solves the loading issue but then I think there are two different jQuery loaded, and only one has $.fn.parsley so tests fail.

I fought and tried my best, but Travis is really weird. There is something wrong with the browserify environment that works on my computer™ but not there.
After wasting too much time on that, I commented it and if someone travis/browserify skilled decide to help there it would be great. Meanwhile, we do not need it to go forward.
Best


Feedback from previous logging code review that I missed.

lgtm

Thanks!  I filed https://github.com/domokit/sky_engine/issues/224 about this issue.

Closes #224


DataArray.drop_sel() along a MultiIndex-ed dimension drops too much data

What happened?
Calling the drop_sel method on a DataArray object produces an incorrect result if the axis involved is indexed by a MultiIndex.
Assuming that dimension 'direction' is indexed by a MultiIndex with named levels 'azimuth' and 'elevation' one can attempt to drop a single item along this dimension in two ways:

call da.drop_sel(direction=(0.0, 0.0)), but this drops all items whose  'azimuth'==0, regardless of 'elevation'
call da.drop_sel(azimuth=0.0, elevation=0.0), but this results in an error ValueError: dimension 'azimuth' does not have coordinate labels

What did you expect to happen?
I expected that at least the first call would result in a correctly dropped item along dimension 'direction'. This expectation is based on the fact that calling .sel(direction=(0.0, 0.0)) works and returns the element where both 'azimuth' and 'elevation' are 0.0.
It would be convenient for the second call to also work, but the analogous call to .sel(azimuth=0.0, elevation=0.0) does not work either, so I guess this is unsupported.
Minimal Complete Verifiable Example
import numpy as np
import xarray as xr

# Create a DataArray with a MultiIndex-ed dimension:
da = xr.DataArray(
    np.reshape(np.arange(16), (4, 4)),
    dims = ['azimuth', 'elevation'],
    coords={
        'azimuth': range(4),
        'elevation': range(4),
    }).stack(direction=('azimuth', 'elevation'))

# Correctly selects a single item along 'direction'
da.sel(direction=(0, 0))

# Incorrectly removes all items along 'direction' where azimuth==0...
da.drop_sel(direction=(0, 0))

# ...but it should remove just one item, like this call:
da.drop_isel(direction=0)

# This fails with 'ValueError: dimension 'azimuth' does not have coordinate labels':
da.drop_sel(azimuth=0, elevation=0)

Relevant log output
No response
Anything else we need to know?
 It's more mundane if labels in each multi-index level are unique -- just raises an InvalidIndexError.

I am also facing the same issue.


Animate simulation

Create an animation of the particles over the simulation

This issue is not a high priority as the current focus is on enhancing performance for a larger number of particles.


Tessera is taking a long time to load...

Hey,
I'm trying to get this up-and-running on a mac with macOS Catalina. When running the ./start.sh script, it mentions that Tessera is taking a long time to start. When looking at the logs, I can see the following:
2020-10-09 10:09:28.258 [main] INFO  c.q.t.config.apps.TesseraAppFactory - Loaded app com.quorum.tessera.admin.AdminRestApp@1b2c4efb
2020-10-09 10:09:29.735 [main] WARN  c.q.t.c.util.EncryptedStringResolver - Some sensitive values are being given as unencrypted plain text in config. Please note this is NOT recommended for production environment.
2020-10-09 10:09:30.102 [main] INFO  eclipselink.logging.all - EclipseLink, version: Eclipse Persistence Services - 2.7.3.v20180807-4be1041
2020-10-09 10:09:30.106 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
2020-10-09 10:09:30.593 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
2020-10-09 10:09:30.661 [main] INFO  eclipselink.logging.connection - tessera login successful
2020-10-09 10:09:30.785 [main] INFO  o.s.o.j.LocalContainerEntityManagerFactoryBean - Initialized JPA EntityManagerFactory for persistence unit 'tessera'
2020-10-09 10:09:31.009 [main] INFO  c.q.t.t.TesseraScheduledExecutor - Starting PartyInfoPoller
2020-10-09 10:09:31.016 [main] INFO  c.q.t.t.TesseraScheduledExecutor - Started PartyInfoPoller
2020-10-09 10:09:31.018 [main] INFO  c.q.t.t.TesseraScheduledExecutor - Starting EnclaveKeySynchroniser
2020-10-09 10:09:31.019 [main] INFO  c.q.t.t.TesseraScheduledExecutor - Started EnclaveKeySynchroniser
2020-10-09 10:09:31.041 [main] INFO  c.q.t.config.apps.TesseraAppFactory - Loaded app com.quorum.tessera.p2p.P2PRestApp@36c2b646
2020-10-09 10:09:31.042 [main] INFO  c.q.t.config.apps.TesseraAppFactory - Loaded app com.quorum.tessera.q2t.Q2TRestApp@5484117b
2020-10-09 10:09:31.046 [main] INFO  c.q.t.config.apps.TesseraAppFactory - Loaded app com.quorum.tessera.thirdparty.ThirdPartyRestApp@517a2b0
2020-10-09 10:09:31.047 [main] INFO  c.q.t.config.apps.TesseraAppFactory - Creating application type THIRD_PARTY for REST
2020-10-09 10:09:31.053 [main] INFO  c.q.t.config.apps.TesseraAppFactory - Creating application type Q2T for REST
2020-10-09 10:09:31.054 [main] INFO  c.q.t.config.apps.TesseraAppFactory - Creating application type P2P for REST
2020-10-09 10:09:31.095 [main] INFO  org.eclipse.jetty.util.log - Logging initialized @4972ms to org.eclipse.jetty.util.log.Slf4jLog
2020-10-09 10:09:31.159 [main] INFO  c.quorum.tessera.server.JerseyServer - Starting http://<IP_ADDRESS>:9081
2020-10-09 10:09:31.161 [main] INFO  org.eclipse.jetty.server.Server - jetty-9.4.z-SNAPSHOT; built: 2019-04-18T19:45:35.259Z; git: aa1c656c315c011c01e7b21aabb04066635b9f67; jvm 1.8.0_151-b12
2020-10-09 10:09:31.566 [main] WARN  o.g.jersey.internal.inject.Providers - A provider com.quorum.tessera.thirdparty.RawTransactionResource registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.quorum.tessera.thirdparty.RawTransactionResource will be ignored.
2020-10-09 10:09:31.566 [main] WARN  o.g.jersey.internal.inject.Providers - A provider com.quorum.tessera.thirdparty.PartyInfoResource registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.quorum.tessera.thirdparty.PartyInfoResource will be ignored.
2020-10-09 10:09:31.566 [main] WARN  o.g.jersey.internal.inject.Providers - A provider com.quorum.tessera.thirdparty.KeyResource registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.quorum.tessera.thirdparty.KeyResource will be ignored.
2020-10-09 10:09:31.742 [main] INFO  o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@2de6f1bc{/,null,AVAILABLE}
Failed to bind to <IP_ADDRESS>/<IP_ADDRESS>:9081
2020-10-09 10:09:31.763 [Thread-2] INFO  c.quorum.tessera.server.JerseyServer - Stopping Jersey server at http://<IP_ADDRESS>:9081
2020-10-09 10:09:31.773 [Thread-2] INFO  o.e.jetty.server.AbstractConnector - Stopped ServerConnector@4cb2918c{HTTP/1.1,[http/1.1]}{<IP_ADDRESS>:9081}
2020-10-09 10:09:31.835 [Thread-2] INFO  o.e.j.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@2de6f1bc{/,null,UNAVAILABLE}
2020-10-09 10:09:31.836 [Thread-2] INFO  c.quorum.tessera.server.JerseyServer - Stopped Jersey server at http://<IP_ADDRESS>:9081
2020-10-09 10:09:31.836 [Thread-2] INFO  c.quorum.tessera.server.JerseyServer - Stopping Jersey server at unix:/Users/i306392/Documents/network/3-nodes-quickstart/qdata/c1/tm.ipc
2020-10-09 10:09:31.836 [Thread-2] INFO  c.quorum.tessera.server.JerseyServer - Stopped Jersey server at unix:/Users/i306392/Documents/network/3-nodes-quickstart/qdata/c1/tm.ipc
2020-10-09 10:09:31.836 [Thread-2] INFO  c.quorum.tessera.server.JerseyServer - Stopping Jersey server at http://<IP_ADDRESS>:9001
2020-10-09 10:09:31.837 [Thread-2] INFO  c.quorum.tessera.server.JerseyServer - Stopped Jersey server at http://<IP_ADDRESS>:9001
Any idea what this could be?
Bram

Hi - Failed to bind to <IP_ADDRESS>/<IP_ADDRESS>:9081 suggests you already have a process listening on this address.  Make sure to stop/kill any already running processes and try again.

Ohh damn I missed that indeed. Thanks, that seemed to solve it.
Bram


Fixes disconnected vnd.docker.raw-streams output

Oftentimes our executions would seem to bail out. They would continue to run, but the stream would be severed and we could not see the output from the stream. Traced it to the data variable being overwritten, and thus the buffer not properly being updated for the next bucket.

Found one more issue where a long running command would cross over the socket timeout, and the next stream would end up inheriting the previous streams buffer.
And yes, this will also fix #120 but also addresses multiple messages crossing over multiple stream get contents (from long running bash processes like CI systems output)
Im not sure how to mock out this sort of test - triggering socket timeouts while still providing data to a stream is beyond my comprehension.

Something is definitely fishy with travis.

Tests are ok on my local, some random shit going on, but this is good,
Thanks for this PR and your patience :heart:

I may open another PR - I think that when the 'default_socket_timeout' limit is hit, there should probably be some logic in the onClose callback to flush the remainder of the buffer.. will probably have to experiement some to see if it solves the problem. (http://php.net/manual/en/php-user-filter.onclose.php)


Add groupSort and medianSort.

For example, to sort varieties by descending median yield:
d3.groupSort(barley, g => -d3.median(g, d => d.yield), d => d.variety)

Or more concisely:
d3.medianSort(barley, d => -d.yield, d => d.variety)

Concerning groupSort, could that be made to work with nested grouping?
It might be nice to write
d3.groupSort(penguins, v => -v.length, d => d.species, d => d.island)

and the API of groups/rollups would feel more consistent.
We can craft that by hand by grouping on compounded keys:
d3.sort(
    d3.rollup(penguins, v => v.length, d => [d.island, d.species].toString()),
    ([, value]) => -value
  )
  .map(([key, value]) => key.split(/,/)) // [ ["Biscoe", "Gentoo"], … ]

(the toString hack would not be needed if d3.rollup accepted arrays as keys, as in https://github.com/d3/d3-array/pull/185#issuecomment-765509694)
Concerning d3.medianSort and the other shorthands, I wonder if it's not too much: they're easy to write with groupSort, and having min, max, median seems incomplete (why not the mean, length, etc). It's all just syntactic sugar so more a question of taste than anything else, but it seems a bit too sugary to me :)

Concerning groupSort, could that be made to work with nested grouping?
It might be nice to write
d3.groupSort(penguins, v => -v.length, d => d.species, d => d.island)

and the API of groups/rollups would feel more consistent.
We can craft that by hand by grouping on compounded keys:
d3.sort(
    d3.rollup(penguins, v => v.length, d => [d.island, d.species].toString()),
    ([, value]) => -value
  )
  .map(([key, value]) => key.split(/,/)) // [ ["Biscoe", "Gentoo"], … ]

(the toString hack would not be needed if d3.rollup accepted arrays as keys, as in https://github.com/d3/d3-array/pull/185#issuecomment-765509694)
Concerning d3.medianSort and the other shorthands, I wonder if it's not too much: they're easy to write with groupSort, and having min, max, median seems incomplete (why not the mean, length, etc). It's all just syntactic sugar so more a question of taste than anything else, but it seems a bit too sugary to me :)

I don’t think nested grouping will work, at least as is — what would the comparator compare? If the comparator is passed both the leaf groups and the nested groups, the comparator will have to do some introspection to figure out what it’s comparing. If the comparator is passed the leaf groups and flattened nested groups, then it’ll work, but it won’t be very efficient and it’ll add some complexity for a use case I’m not confident is very common.
You can do the compound key thing with d3.groupSort directly:
d3.groupSort(penguins, v => -v.length, d => JSON.stringify([d.species, d.island])).map(JSON.parse)

I feel like the medianSort et al. are common enough to want, and simple enough to support, that it’s worth the trouble. It does raise the question of why no sumSort, meanSort, countSort, though… I suppose we could always start with groupSort and then add the helpers later?

I don’t think nested grouping will work, at least as is — what would the comparator compare? If the comparator is passed both the leaf groups and the nested groups, the comparator will have to do some introspection to figure out what it’s comparing. If the comparator is passed the leaf groups and flattened nested groups, then it’ll work, but it won’t be very efficient and it’ll add some complexity for a use case I’m not confident is very common.
You can do the compound key thing with d3.groupSort directly:
d3.groupSort(penguins, v => -v.length, d => JSON.stringify([d.species, d.island])).map(JSON.parse)

I feel like the medianSort et al. are common enough to want, and simple enough to support, that it’s worth the trouble. It does raise the question of why no sumSort, meanSort, countSort, though… I suppose we could always start with groupSort and then add the helpers later?

Pruned this PR down to just groupSort, and put the helper methods in another branch in case we want to add them later.

Pruned this PR down to just groupSort, and put the helper methods in another branch in case we want to add them later.


currently not support writing child on the web?

Yes.
All the flutter widgets cannot shown on top of the webview in this package.
This is a limitation that mentioned in the README.

@jakky1 Is there no other solution? Or is webview just like this?

Or give me some ideas, see if I can improve it

You can try webview_windows package.

Well, that's too bad to scroll through the list

If you are experiencing display performance issues with other packages, that's why I created this package.
However, in order to avoid display performance issues, it is inevitable to cause the limitations mentioned above.
There is currently no way to work around this limitation.


iOS 15.0 Unable to archive build

CompileSwiftSources normal armv7 com.apple.xcode.tools.swift.compiler (in target 'TPPDF' from project 'Pods')
...
remark: Incremental compilation has been disabled: it is not compatible with whole module optimization
Command CompileSwiftSources failed with a nonzero exit code

Hi, thanks for opening the issue.
Can you please provide a few steps to reproduce this error?

Closed due to inactivity


error instantiating route53 challenge solver: unable to assume role: AccessDenied: User: arn:aws:sts::xxxxx:assumed-role/cert-manager/xxxx is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::9xxxxx:role/cert-manager

Error details:
I am going though below error, please provide me any suggest on how to fix this issue
error instantiating route53 challenge solver: unable to assume role: AccessDenied: User: arn:aws:sts::975050273702:assumed-role/cert-manager/171xxxxxx is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::9xxxxx:role/cert-manager
Environment details::

Kubernetes version:  EKS 1.29
Cloud-provider/provisioner: AWS Route53
cert-manager version:  v1.14.4
Install method:  Helm

The logs from the certificate manager display the following error stack traces
E0325 02:12:23.998103       1 sync.go:126] "Failed to determine the list of Challenge resources needed for the Order" err="no configured challenge solvers can be used for this challenge" logger="cert-manager.orders" resource_name="stage-keycloak.xxxx.xxxx-2242030729" resource_namespace="keycloak" resource_kind="Order" resource_version="v1"
E0325 02:12:24.035530       1 sync.go:126] "Failed to determine the list of Challenge resources needed for the Order" err="no configured challenge solvers can be used for this challenge" logger="cert-manager.orders" resource_name="stage-stage-keycloak.xxxx.xxxx-2242030729" resource_namespace="keycloak" resource_kind="Order" resource_version="v1"
E0325 02:12:24.036247       1 controller.go:167] "re-queuing item due to error processing" err=<
error instantiating route53 challenge solver: unable to assume role: AccessDenied: User: arn:aws:sts::9xxxx2:assumed-role/cert-manager/1711332743998839274 is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::9xxxxx2:role/cert-manager
status code: 403, request id: f60496bf-f21d-415e-9d8f-bee17dd2fd01

The name of the service account for the 'cert-manager' installed by Helm is 'cert-manager-controller'. You need to change the binding service account to 'cert-manager-controller'

@leganck - I've noticed that the service account name defaults to 'cert-manager,' but would you recommend changing it to 'cert-manager-controller' in this context?
JFYR,
❯ k get sa -n cert-manager
NAME                      SECRETS   AGE
aws-privateca-issuer-sa   0         20d
cert-manager              0         12h
cert-manager-cainjector   0         12h
cert-manager-webhook      0         12h
default                   0         20d
❯ k get sa -n cert-manager cert-manager -o yaml
apiVersion: v1
automountServiceAccountToken: true
kind: ServiceAccount
metadata:
  annotations:
    eks.amazonaws.com/role-arn: arn:aws:iam::9xxxxx2:**role/cert-manager**
    meta.helm.sh/release-name: cert-manager
    meta.helm.sh/release-namespace: cert-manager
  creationTimestamp: "2024-03-25T00:41:24Z"
  labels:
    app: cert-manager
    **app.kubernetes.io/component: controller**
    **app.kubernetes.io/instance: cert-manager**
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: cert-manager
    app.kubernetes.io/version: v1.14.4
    helm.sh/chart: cert-manager-v1.14.4
    helm.toolkit.fluxcd.io/name: cert-manager
    helm.toolkit.fluxcd.io/namespace: cert-manager
  **name: cert-manager**
  namespace: cert-manager
  resourceVersion: "15982674"
  uid: d0e4c9fb-1e64-43c2-8002-f0d488e63157

❯ k get deploy -n cert-manager cert-manager -o yaml | grep -i service
      enableServiceLinks: false
      serviceAccount: **cert-manager**
      serviceAccountName: **cert-manager**

Good to see you are making progress.
I'll close this issue and we can continue in https://github.com/cert-manager/cert-manager/issues/6874.


Esp8266 baud rate ignored with Flasher::connect

I am trying to flash an esp8266 board with a speed of 921600
but the flasher baud is ignored in the connect function
// Now that we have established a connection and detected the chip and flash
        // size, we can set the baud rate of the connection to the configured value.
        if let Some(baud) = speed {
            match flasher.chip {
                Chip::Esp8266 => (), // Not available
                _ => {
                    if baud > 115_200 {
                        warn!("Setting baud rate higher than 115,200 can cause issues");
                        flasher.change_baud(baud)?;
                    }
                }
            }
        }

this does not seem right as I am in fact able to call the function after using connect and the flashing does complete without issue.
   let mut flasher = Flasher::connect(interface, info.clone(), Some(921600), true).expect("unable to connect");
   flasher.change_baud(921600).unwrap();

is there a particular reason on why the esp8266 is ignored and not simply prompting the warning like the others?

I don't know that there's any specific reason for this. Seems to have been this way since 2020 when it was added.
Looking at esptool it doesn't look like they support setting the baud rate for the ESP8266 either, unless I've missed something. It's been so long since I've used that chip I frankly don't remember much about it, sorry.

from esptool code
https://github.com/espressif/esptool/blob/master/esptool/loader.py#L1084-L1085
could it be that the STUB loader allows for the baud rate to be changed ?

Ok so after investigating a bit more on this, it looks like you can set the baudrate higher than 115200 after loading the stub.
So initially you shoud:

Open the connection at 115200
Upload the stub if supported
after the stub is loaded you can set the baudrate higher like 921600

We've decided to drop support for the ESP8266 (see #576), so closing this issue.


Rename null safety strong mode flag

Currently the null safety strong mode flag is controlled by the flag --no-null-safety / --null-safety.
From offline discussion, we find that this is suboptimal: When a developer opts out of sound/strong checking with --no-null-safety they will still get some null safety (e.g. static analysis), but the flag name makes it sound like they are loosing all of null safety.
We'd thus like to rename this flag to --no-sound-null-safety / --sound-null-safety.
Source

Is this for all tools?  Do we have a source of truth doc on the correct flags for null safety across all tools?
@leafpetersen

Yes, this is for all tools.

@franklinyow can you turn this into a meta-bug and file an actual bug per tool?

@mit-mit I search the code (link in description), so I need one bug for vm and one for dart2js?

Sounds good

@mit-mit I search the code (link in description), so I need one bug for vm and one for dart2js?

I don't think dart2js is special here.  I think there is one for the CFE (which consumes the flag), and possibly one for the VM, dart2js, and ddc which may (or may not) pass the flag to the CFE.
There is also coordination to be done with whatever is passing those flags in the build files and on the bots.
I'd probably start by checking with @athomas and @johnniwinther .

@mit-mit I search the code (link in description),

p.s. you probably also need to search for --null-safety since the flag is negatable.

This should be in the test matrix, e.g.:
https://github.com/dart-lang/sdk/blob/c5a5884b7ff58794e9ac921e0537353323282189/tools/bots/test_matrix.json#L628

Should I move this and all the sub-issues to the beta?

Renaming is done, closing


chore: remove routify

As we decided to ditch #32 for an upcoming more flexible PR, we should remove routify separately.
Reasoning: Routify is nearly unused on npm, and we do recommend creating full kit applications

we can remove the svelte environment now as this was the only one that wouldn't run in a kit project

Do you mean completely removing the svelte property, or completely removing the environment property?

We can just have the kit field where it indicates that SvelteKit is required. if kit === true and we're not in a SvelteKit project, then the precondition error is thrown

Should this still be an object while we are going to be refactoring that? Can we think of any other environments that might appear in the future?
Should we rename kit to requiresKit to make things more clear?

Maybe we should just get rid of the field entirely and add a setup hook as part of #181? I don't think we should be blocking this PR from merging as we can address this separately.

Yeah, I was talking about the svelte environment, which has always felt weird to me because everything is a svelte project. Maybe we should just rename that one to vite instead?

Can we think of any other environments that might appear in the future?

vite would probably be the main one. Like I bet the Tailwind adder isn't actually a svelte adder, but is a vite adder. Probably if you tried to set it up in a webpack project it doesn't work because you need postcss setup correctly

yeah, it doesn't have to block this PR
I'd thought about the setup hook too. The trade-off there is that a hook is more flexible, but can't be displayed easily via a website directory

But kit project are also using vite.
setup hooks sounds fine, and aligns with our goal of a more flexible api. But let's implement this in #181


[HUDI-863] get decimal properties from derived spark DataType

What is the purpose of the pull request
This PR fixes a null pointer exception when calling converter for decimal datatype.
Brief change log

get decimal properties from derived spark DataType

Verify this pull request
(currently) This pull request is a trivial rework / code cleanup without any test coverage.
I wanted the tests can be implemented by extending the existing cases to process nested records with decimal values
Committer checklist

[x] Has a corresponding JIRA in PR title & commit

[x] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@umehrot2 able to review this?

@umehrot2 able to review this?

@vinothchandar will do today

@rolandjohann : can you assign this ticket to yourself. https://issues.apache.org/jira/browse/HUDI-863
thanks.

@umehrot2 gentle ping :)

@nsivabalan it seems that I can't do that. "assign to me" link is missing and klicking on Assignee "Unassigned" doesn't transform the field to the desired people select. This is the same for HUDI-888. Can you assign those two issues to me?

Added you as a contributor on jira.. So you should be able to claim those now! let us know if you still face issues..

LGTM overall.. If you can throw in a test, like you mentioned, that'd be great.
Also trying to understand the scope of the issue.. without this, does every decimal type conversion fail?

@vinothchandar every decimal conversion does not fail. As I understand from this PR, the NPE would occur when decimal field is not a top level field in the avro schema, but nested within another type. @rolandjohann is this understanding correct ?

@vinothchandar @umehrot2 is right: only when the field is not at level.
This happened because the avro schema has been passed to each recursion of the method, but without selecting the actual field whose schema must be passed to the recursion.
It seems that there is no one with decimals at nested structs using hudi currently - or at least doesn't report that ;)

@rolandjohann The fix makes sense to me. Lets add a test for decimal type handling, and make it nested within another type as well. Recently we have tried to exhaustively test as many data types handling as possible, by adding fields with those data types in the schema for test data that Hudi uses across various tests: https://github.com/apache/incubator-hudi/blob/master/hudi-client/src/test/java/org/apache/hudi/common/HoodieTestDataGenerator.java#L95 .  We recently added Map and Array types test. What you can do is add a decimal field to the trip record schema as a nested type. Infact, easy solution with be in FARE_NESTED_SCHEMA change the type of amount from double to decimal. double is either ways tested through other fields, this would accurately test decimal field in nested schema.

@bhasudha this is a good 0.5.3 candidate.. if we are crunched on time, I can also write the test and push/merge tonight :)

Spent some time on this. It's note straight forward for a few reasons. the datasource tests convert avro to json back to DF.. I managed to add a decimal type at the data frame level using withColumn() , but getting it nested is a separate story.. I filed HUDI-908 to revisit this in 0.6.0 timeline


AttributeError: module 'qwiic_button' has no attribute 'Qwiic_Button'

Hello,
Thanks for making this library; it's exactly what I was looking for! I have a BOB-15932 (red Qwiic button) hooked up to a Raspberry Pi 2B via Qwiic hat. I've installed the library via sudo pip install sparkfun-qwiic-button. When I try to run the sample code at the bottom of this page, I get the following error: AttributeError: module 'qwiic_button' has no attribute 'Qwiic_Button'. Thoughts?

Hi there @TaylorHokanson. Thanks for finding this issue with the code on the readme. I've just updated that code, it should work for you now. I've tested the other examples and they work too. I'll be closing this issue. Let me know if anything else comes up.


improve CI actions

IMPORTANT: The default github actions permissions for the entire tlspuffin organization have been set to "restricted" mode. If you came here because a previously working workflow now fails because of insufficient permissions, set the required permissions explicitly in this particular workflow. See the github documentation for the list of default permissions granted in "restricted" mode.
This PR aims to provide several improvements over the current github actions:

add justfile recipe to run github actions locally
fix calls to Swatinem/rust-cache
update external actions relying on deprecated Node 16
add ability to control the CI workflow based on PR labels
add smoke test before running the complete build matrix
fix CI/CD permissions

See also:

Github's notice of deprecation for Node 16
Github's introduction to workflow permissions

PENDING

[ ] Waiting for #304 to land because the new CI rely on some changes/fixes included in that PR.
[ ] The following external action still need to update to Node 20: peaceiris/actions-mdbook#500

Seems like CI is now disabled on PRs forked from a branch different from main, despite using the ci:full flag. Would be nice to keep the control on when CI is enabled with the flags.

@LCBH I'm not sure what you mean. This PR makes CI run a reduced set of checks on every PR, regardless of the source branch and source repository. The label ci:full activates the full set of CI checks on the annotated PR. The full set of checks always run when pushing to the branches main and trailofbits. I didn't change the behavior in that respect. Did I miss something?


Client UX "Settings" Update

Change "Account ID" to "Workspace" in local clients & documentation.

I think we're going to remove this altogether, closing


chore: add dashboard route deletion to plugin

https://issues.redhat.com/browse/OSSM-4377
This PR adds functionality to the OSSM plugin which removes the now obselete odh-dashboard route (which bypasses the mesh) from the KfDef root namespace.  It does so by calling a goroutine at the end of the Init() step, which checks every 10 seconds for the route, and if it finds it, deletes the route and then ends.
This must be done directly through the plugin rather than through a patch as we are unable to delete a route using patches at this time.
Tested on CRC with image: quay.io/maistra-dev/opendatahub-operator:v0.0.5-route

deploy operator
create KfDef in opendatahub ns
Check opendatahub routes to ensure that route odh-dashboard has been deleted

Closing this - since the route is recreated by the operator since it is present in the dashboard manifests. We will have to revisit this.


improve block building performance

[ ] bulk storage fetch
[ ] For Kusama / Polkadot improve session change block handling somehow to avoid session related work, which reads a lot of storages

after #93 is merged we can start task with pre-key-value to avoid going back and forth for well known keys that are required to initialize block or execute transaction

in case those keys are not locally then it will be wise to fetch multi keys before starting the task


[SPARK-50536][CORE] Log downloaded archive file sizes in SparkContext and Executor

What changes were proposed in this pull request?
This PR aims to log downloaded archive file sizes in SparkContext and Executor.
Why are the changes needed?
To improve the UX by showing the file size intuitively in order to help check file health.
Does this PR introduce any user-facing change?
No, this is a log message.
How was this patch tested?
Manual check with the Apache Spark test jar file.

https://github.com/apache/spark/raw/refs/heads/master/data/artifact-tests/smallJar.jar

$ ls -al data/artifact-tests/smallJar.jar
-rwxr-xr-x  1 dongjoon  staff  787 Dec  3 09:06 data/artifact-tests/smallJar.jar

Run the spark-shell and grep (787 bytes) from the log message like the following.
$ bin/spark-shell --archives https://github.com/apache/spark/raw/refs/heads/master/data/artifact-tests/smallJar.jar -c spark.log.level=DEBUG 2>&1 | grep '787 bytes'
24/12/10 10:05:09 INFO SparkContext: Unpacking an archive https://github.com/apache/spark/raw/refs/heads/master/data/artifact-tests/smallJar.jar (787 bytes) from /private/var/folders/c8/9r5k3d7n19g2m72c86qm08580000gn/T/spark-28ceb587-8376-403e-b364-e675529aeef0/smallJar.jar to /private/var/folders/c8/9r5k3d7n19g2m72c86qm08580000gn/T/spark-d97fc8fc-358e-4044-a904-dfc6823d742d/userFiles-89ff1008-a0d7-4c83-bd9f-9c4e2e830645/smallJar.jar
24/12/10 10:05:09 INFO Executor: Unpacking an archive https://github.com/apache/spark/raw/refs/heads/master/data/artifact-tests/smallJar.jar (787 bytes) from /private/var/folders/c8/9r5k3d7n19g2m72c86qm08580000gn/T/spark-b9020649-cb2b-476b-89f5-5d502f1e0ba8/smallJar.jar to /private/var/folders/c8/9r5k3d7n19g2m72c86qm08580000gn/T/spark-d97fc8fc-358e-4044-a904-dfc6823d742d/userFiles-89ff1008-a0d7-4c83-bd9f-9c4e2e830645/smallJar.jar

Was this patch authored or co-authored using generative AI tooling?
No.

Could you review this log PR for Spark 4, @LuciferYang ?

If the integrity of those file in question what about calculating the CRC by using (java.util.zip.CRC32) but only calculating and  logging out the value when TRACE level logging is requested.

If the PR only targets archives I am confused as for a zip file (like a jar) crc check is done by default when its content is unpacked. May I ask what was the use case where this might help?

Thank you for review and approval, @MaxGekk and @viirya .
To @attilapiros , yes, the goal is specifically to log the file size in addition to the file name. Nothing more. From the logs, a user can check the file size is expected value. Or, they can add the size to calculate the total traffic.

Do you have a further question, @attilapiros ?

Let me merge this~
To @attilapiros , your idea (auto verification?) sounds independent from this log-only PR. We can talk orthogonally later.

As we talk about zips where CRC check is already included we do not need to check the integrity once more it will be checked at unpack.

late LGTM ~ thanks @dongjoon-hyun


Have a look at https://guide.elm-lang.org/interop/ to see what can be improved

[x] Do the thing

Personally I like the new interop guide, it covers most of the questions I've seen beginners ask about flags and ports especially around how to use Elm.Main.init(...) providing the flags
A hint in https://guide.elm-lang.org/interop/ports.html that ports are only generated in JS when actually used in Elm would be handy as this is a common beginner hurdle
People who know other languages almost always have the same kind of questions about why Elm chooses to do stuff in specific - usually uncommon - ways. It might be helpful to include an FAQ on the usual topics
Pulling the "Design Considerations" out of interop/ports into its own interop/limits makes sense to give this information more exposure
The localization custom element example is way better than just having a link to MDN

Action items to create issues for

[x] (#2) Add a hint to https://guide.elm-lang.org/interop/ports.html that only used ports are generated in JS
[x] (#3) Create a guide on how to set up custom elements specifically for usage with Elm, decide whether this guide should be part of this repo and put the guide where it belongs
[x] (#4) Create an FAQ on common interop topics with links to discourse and elm-discuss/elm-dev , decide whether this should be part of this repo and put it where it belongs (taks ports, FFI, kernel code, etc).

Some notes:

the links to the "simple" examples should stay unchanged, so https://guide.elm-lang.org doesn't break
there will be a more directory with a separate more/README.md that will harbor more information and "fancier" examples


feat: add Router address to BNB Chain

[x] add router address to BNB chain
[x] test
[x] yarn changeset

LGTM


parser: TSTypeAssertion panics in tsx  context

Test with following string:
arr.push(<string>a);
https://oxc-project.github.io/oxc/playground/

I believe this is expected behavior. Both oxc and tsc treat <string> as a JSXOpeningElement that has no corresponding closing tag.
https://www.typescriptlang.org/play/?#code/DYUwLgBAhgTjBc0B2BPA2gXQgXgpg3AFCwwB0ADgK4DOAFgBQA81YMAlkgOYB8UAlESA


Adding Action Workflow to perform param file regression tests

PR Summary
Adding the capability to dynamically validate a list of parameter files against the bicep code.
closes #117
PR Checklist

[ ] PR has a meaningful title
[ ] Summarized changes
[ ] This PR is ready to merge and is not Work in Progress
[ ] Link to a filed issue

Looking like the regression tests work! 😉


[CMT-865-1222] Translated NL 52 in Chinese

Description

Please include a summary of the change and which issue is fixed.
Please also include relevant motivation and context.

This pull request ...
Fixed issue

Please indicate the fixed issues with this exact format Fixes #232 where 232 is the number of the issue. This will trigger an auto-close if the issue when this PR is merged.
Supported keywords:
Fixes #1,#2,#3
close #1, #2, #3
fix #1 #2 #3
resolve #1,#2 #3
Resolves: #1,#2,#3
closed : #1, #2, #3

Fixes #(issue)
Type of change

Please delete options that are not relevant and check the box.

[ ] Add a new article/page
[ ] Fix a Typo
[ ] Add a new translation
[ ] Other

Resources

Any screenshots, links or relevant resources to explain better the changes.

this PR is pushing 19 commits, but only 3 files are being edited. you need to make sure your english branch is up to date(fetch and merge), then create a new branch and do the edits there. Once you are done, you can do the PR from the new branch, it should come here clean

one more thing, please make sure the front matter is up to date (according to the new blog system)


Bare output includes extra line in non-screen output with no vulnerabilities

safety version: 2.3.1
Python version: 3.6 and later
Operating System: Linux

Description
When running safety with --output bare in an environment with no vulnerabilities in a non-screen environment (eg. within a cron task or piping to a file), a single line is output:
+==============================================================================+
When used as a cron task, this causes an unnecessary email to be sent.
What I Did
Within a cron environment:
>>> safety check --output bare
+==============================================================================+

Due to the un-needed output, an email is sent.

@chris-bradley, as a workaround, you should be able to redirect stderr. Let me know if that helps.


Update PlanetShine version, + a little edit

This will be fixed in #841

Thank you @Olympic1
This pull request does not have a reason to exist anymore, I'm closing it.


linux boot error

in opencore 0.5.6-0.5.8 Dev version
When booting KaliLinux with open core,
A ramdisk error occurs and a freeze occurs.
And when I mount the Kalin Linux efi partition on my Mac, I get an error that the Kalin Linux EFI boot partition is saved in the BIOS.
Opencore 0.5.5 was able to boot normally, but after updating
This happens.
Is there any other way to boot KaliLinux normally from open core?

There was many changes from 0.5.5-0.5.8. You may need to read the doc to understand what changed.


Language cannot be changed programmatically

Allow User to change the language programmatically without requesting language dialog.

solved in #11


FeatureGroups don't work with SQL feature backend

SQLAlchemyFeatureGroup doesn't correctly upload data - it incorrectly tries to load data from the featuregroup name

closed by #54


Greenbeard

Greenbeard was actually a character (although I've forgotten him)
I was initially perplexed thinking the network came up with a word outside the vocab.
http://awoiaf.westeros.org/index.php/Greenbeard
Just clearing it up for anybody who might be thinking along similar lines.

That's a good point! Sorry for the confusion. I've updated the docs.


[Artwork Grid] fixes loading state UI

While data is still loading, this fix makes sure the artwork grid has a minimum height set so it occupies the remainder of the screen height and hides other grid below it.

An explanation of how this fixes the issue would be 👍

Fails

:no_entry_sign:
No CHANGELOG added.

Warnings

:warning:
Could not find stories using these components:

ArtworkRail

  Generated by :no_entry_sign: dangerJS

@orta

Could not find stories using these components:
ArtworkRail

what's danger asking for?

It's saying that there are no story files that reference the ArtworkRail - it's a warning because it's hard to say whether every leaf in a component tree should be referenced inside a story

It's there to encourage us to use storybooks for making re-usable components like reaction-force does.

My requests are 👍


Scroll issue in sidebar

In my laptop view, I can't scroll to view all sidebar options. I can only view up to the heading of customization. When I zoom out my browser, I am able to see some contents of  components  .

yea noticed it
here is a temporary fix click on customization then use your down arrow key on your keyboard to scroll down

@RijoKsd could you please tell me which resolution is your screen because, I've tested that on different screen sizes but didn't got this issue.

@sajadevo Now there is no scroll issue, I think they fixed it now


Support for nullable fields

Currently when I have a row that does not specify NOT NULL i'd expect the parameter in the resulting function to take an Option but I currently see no way of doing that. To get around this I've created two sql files but this feels like something that should be provided.

Yes! I really want a way to support this, sadly Postgres doesn't give us enough information to get this kind of info and it will probably have to be implemented as some sort of annotation.
Did you have any design in mind for how that could look?

I was mostly hoping for each nullable field would be a Option(a) instead of just a. This would be breaking however

I was mostly hoping for each nullable field would be a Option(a) instead of just a. This would be breaking however.
For example given the pseudo sql below:
username NOT NULL
email NOT NULL
profile_picture NULLABLE

then the generated squirrel code would go from (like it is right now)
sql.create_user(username: String, email: String, profile_picture: String)

to
sql.create_user(username: String, email: String, profile_picture: Option(String))

Yeah I get that but Postgres won't give us the kind of information we need to figure out if some query parameter is nullable or not. So it would most likely need to be implemented as some sort of extension with a magic comment or something like that

Gotchu, that is problematic. I think keeping away from magic comments are some best things with gleam so i think that should be avoided. If you were to go that way however then you could do something like frontmatter where the first comment in a document is yaml or some config language* that is read and then parsed as a file config so you'd do.
/*
nullable:
  - profile_picture
*/

INSERT INTO user(username, profile_picture) VALUES($1, $2)

Where this would make profile_picture or $2 an Option(String) but that would open up to runtime errors since you could accidentally break a not null constraint.


py2 or py3

请问这个代码支持pyhon3嘛，我记得coco-caption是用python2的

The training code supports python3 now.
The evaluation code involving coco-caption does not support python3.


When publishing a dataset the files associated with the samples in the dataset are not saved

Published datasets copy all the information associated with the items in the dataset. The entries in the sample2datafile table are not saved, so published datasets do not save the association of files to their samples.
This means that the provenance outline in the published data site cannot show the files for a sample.

Actually, I made a mistake - this issues is NOT RELATED to #733 - but I don't know how to undo that comment - above.


Updates search to use Address and Zip

Overview
Since all results are within the city of Philadelphia. Search results are for the zip of the searched address.
Demo

Notes
Fixes a swap in the default config bounding box extent that prevented bbox geocoding from working properly
Testing
Update the bounding box extent in your config.js
Search a few addresses/zips, make sure results are sensible.

Wrong base. Closing.


CH340G is 5V powered, not 3.3V

CH340G is 5V powered and thus pushing 5V level (through R12 ~4.3V)  into ESP12 on RXD0 instead of 3.3V level.

This would explain why my 0.9 boards are unstable and difficult to flash.

Argh, lovely...

Where is the software for these drivers?  The one on here drives me nuts as it keeps disconnecting and connecting.


Make request path more easily visible to LB policies.

This passes the path into the LB policy API as a first-class parameter, which eliminates the need for LB policies to inefficiently dig it out of the metadata.
As part of this, I have also improved the tests for accessing trailing metadata in an LB policy.

Green!


Extra Disassembly view Window opens up when the breakpoint is hit on the disassembled Instructions

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.79.1
OS Version: Windows_NT x64 10.0.19042

Steps to Reproduce:

Create a simple Hello World program with C Source code.
Set Breakpoint in the C code to Debug
Start Debugging, Once the breakpoint is hit on the Source Code, open the disassembly view.
Put the opened disassembly view window in the split window section, and set the breakpoint in the disassembled Instructions.
Do continue or step over, Once the breakpoint is hit in the disassemble Instruction, another disassembly view window opens up in the vs code.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.79.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

The issue can be reproduced with the latest version of vscode which is 1.79.2


[Compatibility Bug] "You can't use this item yet" popup compatibility issues

Please take a look at this for reference, make sure to read iMukul's comment:
https://github.com/Momo-Studios/Cold-Sweat-Rework-Forge/issues/21

This seems to be quite a simple fix, I'll implement it as soon as I have time.

Nvm, just did it immediately. Should be on curseforge quite soon.


Request for takeUntil with predicate function

I've run into an issue several times where I'm usingtakeWhile but I also want to include the last element from the source observable that triggered the predicate function. For example:
Observable.of('red', 'blue', 'green', 'orange').takeWhile(color => color !== 'green')

gives me:
'red', 'blue'

but I want:
'red', 'blue', 'green'

I haven't found a graceful way to compose this behavior using existing operators. Ideally, I would like to have a derivative of takeWhile that adds an additional call to next() here: takeWhile.ts#L85
RxJava 1.x implemented this by overloading takeUntil to also take a predicate function. You can find the thread discussing this here.
Let me know if there's any interest in this. I'd be happy to put together a PR.

It's funny that last week I've encountered exactly the same thing and I was wondering if I'm just dumb or there's really no easy way to do this.
I ended up using the following:
Observable.of('red', 'blue', 'green', 'orange')
  .concatMap(color => {
    if (color === 'green') {
      return Observable.of(color, null);
    }
    return Observable.of(color);
  })
  .takeWhile(color => color)
  .subscribe(color => console.log(color));

This produces the result you want but is very confusing and inefficient.

Thanks @martinsik, that's pretty clever. I still think an operator would be nice, especially since there's precedent in RxJava. I'll keep this as a workaround though.

Thanks to http://stackoverflow.com/a/35800173/1709679 I figured out how to make it with work with let:
const takeWhileInclusive = predicate => source =>
  new Observable(observer => {
    const subscription = source.subscribe({
      next: value => {
        observer.next(value);

        if (!predicate(value)) {
          observer.complete();
        }
      },
      error: error => observer.error(error),
      complete: () => observer.complete()
    });

    return () => subscription.unsubscribe();
  });

Observable.of("red", "blue", "green", "orange")
  .let(takeWhileInclusive(color => color !== "green"))
  .subscribe({ next: value => console.log(`takeWhileInclusive: ${value}`) });

Working example:  http://jsbin.com/mekupugeza/edit?js,console

also possible w/ multicast:
Observable
  .of("red", "blue", "green", "orange")
  .multicast(
    () => new ReplaySubject(1),
    (colors) => colors.takeWhile((c) => c !== 'green').concat(colors.take(1))
  )

I understand that you don't want to add too many operators to avoid bloat and confusion, but I would love to see an operator similar to takeWhileInclusive. I need this behavior relatively often and while the multicast solution is a nice, I would prefer an operator to help readability.

I use it also very often. Would love to see it as operator out of the box

For now I've created a library for this operator that can be found here: https://www.npmjs.com/package/rxjs-take-while-inclusive.

Closing this because an inclusive parameter is being added to takeWhile. See #4000 and #4115.


Error while writing full data content log to a file

Firstly, thanks for a great tool.
I'm experiencing a problem when I choose to write content log to a file.
I run sslsplit with following command:
./sslsplit -D -l ./connections.log -L ./connections_data.log -k my.key -c my.crt ssl <IP_ADDRESS> 8443
It results in the following error message and nothing works:
Error from ioctl(DIOCNATLOOK): Operation not permitted
Connection not found in NAT state table, aborting connection
However, when I run sslsplit with:
./sslsplit -D -l ./connections.log -S ./logdir -k my.key -c my.crt ssl <IP_ADDRESS> 8443
It works fine!
What I'm doing wrong?
Thanks.

i also get
"Connection not found in NAT state table, aborting connection"
This is what I use on terminal:
sslsplit -k ca.key -c ca.crt -D -l connect.log -S logdir -L sslsplit.log https <IP_ADDRESS> 10443 http <IP_ADDRESS> 10080
On FreeBSD 13.1
# sslsplit -V
SSLsplit 0.5.5 (built 2023-02-20)
Copyright (c) 2009-2019, Daniel Roethlisberger<EMAIL_ADDRESS>https://www.roe.ch/SSLsplit
Build info: V:FILE HDIFF:0 N:83c4edf
Features: -DHAVE_IPFILTER -DHAVE_IPFW -DHAVE_PF
NAT engines: pf* ipfw ipfilter
ipfilter: version 5010200
Local process info support: yes (FreeBSD sysctl)
compiled against OpenSSL 1.1.1o-freebsd  3 May 2022 (101010ff)
rtlinked against OpenSSL 1.1.1o-freebsd  3 May 2022 (101010ff)
OpenSSL has support for TLS extensions
TLS Server Name Indication (SNI) supported
OpenSSL is thread-safe with THREADID
OpenSSL has engine support
Using SSL_MODE_RELEASE_BUFFERS
SSL/TLS protocol availability: tls10 tls11 tls12
SSL/TLS algorithm availability: !SHA0 RSA DSA ECDSA DH ECDH EC
OpenSSL option availability: SSL_OP_NO_COMPRESSION SSL_OP_NO_TICKET SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS SSL_OP_NO_SESSION_RESUMPTION_ON_RENEGOTIATION SSL_OP_TLS_ROLLBACK_BUG
compiled against libevent 2.1.12-stable
rtlinked against libevent 2.1.12-stable
compiled against libnet 1.2
rtlinked against libnet 1.2
compiled against libpcap n/a
rtlinked against libpcap 1.9.1
8 CPU cores detected

uname -a
FreeBSD user.user.user 13.1-RELEASE-p3 FreeBSD 13.1-RELEASE-p3 GENERIC amd64
Thanks.

That usually happens if you cannot redirect traffic to sslsplit properly. Please read the man page paragraph starting with "SSLsplit does not automagically redirect any network traffic.", if you haven't yet.


Explain the problem cause by 'intersecting' expansion sets

Hi all.  On the  May 6 VR call (and in Hinxton the week before), concerns were raised about scenarios in which a single discrete variant instance (e.g. NP_478102.2:p.Ser73Arg) might appear in more than one variation expansion sets in a given corpus of VA data (e.g. ClinVar).
Can someone explain why this creates a "conundrum" -  perhaps with examples of specific tasks/use cases where this is problematic, and what the problems are?  @larrybabb calling on you first here as you raised this concern most recently - I think from the perspective of mapping ClinVar variation ids to ClinGen allele registry ids.
Thanks, and apologies if this is clear to others and I am just being dense. But I suspect that myself (and others) may be thinking about this from different angles/perspectives, or imagining a different workflow for creating, indexing, and querying over variation sets. From where I sit it is not clear how 'intersecting' expansion sets cause problems.

My reference to this concern was coming from the notion of how to "correctly" handle aggregation of statements that are related to sets that have intersecting members.
In ClinVar the variationID expansion sets include lift over between genomic builds as well as both projection from genomic to transcript and transcript to protein sequences.  All of these lift-over and projected forms are provided for the purpose of aggregation.
One of the primary use cases for variant knowledgebases like ClinVar is to aggregate knowledge about a variant. In the case of ClinVar this knowledge is being submitted by heterogeneous sources into an archive.  Agreement and conflict identification between the same or similar statements about the same variant is a major feature and value proposition of the ClinVar archive. ClinGen works with ClinVar submitters and ClinVar to identify, verify and help with expert resolution of aggregate variant pathogenicity statements in ClinVar. ClinVar has automated "review status" policies informed by ClinGen and other submitters input.  This review status is often referred to as the "star levels" for a given variant or variant-disease combination.
So when submissions are made to ClinVar it is very important to be able to gather knowledge about the same variant, reliably.
If you do a search on ClinVar BRCA2 variant p.Ser326Arg[Variant name] you will see that there are 3 separate records, each with separate submissions of pathogenicity for similar diseases. While this may seem harmless, it isn't clear (to me) whether these three sets of statements can be aggregated and compared without altering the intended meaning of the statements themselves.
I think it is important that we clarify that if a set of variation is used as a subject of a statement then we presume that the entire set collectively represents what the statement is about.  If we take the approach that any member of the set is a suitable substitute for the statement subject itself then we must be sure that we are not changing the intended meaning of the original statement.
I suppose therefore that maybe the concern isn't so much about whether members of the set intersect as it is about whether any member of the set can be substituted for the statement's subject without altering the meaning of the statement.

I just had a conversation with a clinical geneticist about this issue in some detail. They agree that the subject of a pathogenicity statement is often the set of variants (genomic->transcript->protein). All statements of pathogenicity should start with the DNA change was tested and observed but also what prediction evidence, literature and other evidence related to a particular transcript and its predicted protein change that lead to a specific disease pathogenicity assertion.  This combo of genomic, genomic+transcript or genomic+transcript+protein are all important to clearly defining the statement being made by the submitter and should be grouped (or associated) as such.
However, it would not be reasonable to presume that ClinVar's generalized variation set for each variant in ClinVar is precisely reflective of what each submitter intended for the statements/submissions associated with a given variant.

A variant in two sets is a hallmark of a potential problem, but not the problem itself. Furthermore, it depends on intended use.
If a variant is in two distinct sets, the set is not "complete" (i.e., not fully connected). The implication, then, is that variants in that intersection are in some way like the disjoint members of the sets, but that the disjoint members are dissimilar. This should be the first hint that annotating sets is going to be fraught with problems in which an annotation might apply to only some members of these sets, but that which ones in unspecified.
See this spreadsheet:

Study of 3 ClinVar "alleles" hgvs sets in gene CDKN2A that contain "NP_478102.2:p.Ser73Arg".
Allele 133657 (①) occurs at one location. Alleles 484124 (②) and 9423 (③) occur at another location.
All result in Ser73Arg in one transcript, but have different consequences in other transcripts.

Okay, now imagine using a ClinVar set as an annotation subject. The most immediate problem is that it's unclear which set should be the annotation subject if you want to make a statement about an intersection member.
The other problems are correlated with the existence of overlapping sets, but not caused by them. For example, overlapping sets tend to be the kinds that are hetergeneous bags of stuff. Such sets have very little value (IMO) because the subject is ill-defined (or, rather precisely defined as a bunch of things), which dilutes the utility of any statement. And, my personal peeve is that this actually encourages people to make sloppy annotations on the wrong subjects. For example, a genomic variant is NEVER a stop codon: it might have that consequence in a particular transcript, but it is not itself a stop codon. And it's certainly never a catalytic residue in a protein.

@mbrush Would you please close this issue if you think it's resolved? Thanks

Thanks Reece - I now understand a bit more about the perspective from which you see intersecting sets as problematic (or indicative of potential problems). I want to dig into one statement in particular, as it highlights a potentially different view of the workflow/context in which expansion sets will be created and applied:

Imagine using a ClinVar set as an annotation subject. The most immediate problem is that it's unclear which set should be the annotation subject if you want to make a statement about an intersection member.

This suggests a workflow in which annotation creators would 'shop' for and aim to re-use existing expansion sets initially created for some other annotation, or perhaps created independently of a particular annotation altogether.  In my view 'expansion sets' are always created de novo for a particular annotation, to include all discrete variations which an agent believes are representative of the 'biological variant' to which the knowledge applies.  So the scenario described above where it is "unclear which set should be the annotation subject if you want to make a statement about an intersection member", would never exist . . . because expansion sets are not 're-used' in this way.
If this is the case, then the specific issue above of 'selecting the right set for re-use' isn't necessarily a problem. But there are plenty of other reasons why we might prefer not to allow variation expansion sets as annotation subjects (which I will summarize elsewhere). I think that we agree about this in principle . . .  based on what I heard in Hinxton, on calls, and in tickets,  we all believe that it is best to always annotate to a specific, discrete variation.  And that expansion sets, where desired, can be captured to the side.
As highlighted above however, it seems that the reasons why we feel this way may not be entirely overlapping, as a result of different views on the workflow/context in which expansion sets will be created and applied. I also think there are differing opinions about allowing expansion sets as annotation subjects in practice -  that despite our philosophical objection to this, it may be impractical to completely ban it.  But these are topics for another ticket/document, and a future call.
I will leave this ticket open a couple days in case there are responses to this comment - then close.  Thanks all.


Fix typo

No idea why I am just seeing this now. Thanks for pointing it out.
Since your fork got a bit out of synch, I went ahead and fixed this in a separate commit.
Might want to sync your fork to get the latest. Thx!


Pool creation logs missing

when creating a pool, no pool specific information (e.g data from initial pool info, maxbalance etc) is logged. so the initial config cannot be derived from the events alone.
only the component creation of logged, but that log is generic and does not contain specific information about the pool.

the same is valid for the other component types, default info information (e.g. fees) is not logged.


Generating Presigned URLs

hi
Can I use boto3 to  generating presigned URL?  I can not find the document

@wwj718 Any specific reason you are not using minio-py  client library, we have examples documented here and it works for both AWS S3 and Minio, like (presigned_get_object.py)[https://github.com/minio/minio-py/blob/master/examples/presigned_get_object.py]
For generating presigned URL for boto3, following this document it can be achieved.
Replace the credentials with your local setup.

import boto3
from botocore.client import Config
import requests

# Get the service client.

s3 = boto3.client('s3',
                    endpoint_url='http://localhost:9000',
                    aws_access_key_id='BKIKJAA5BMMU2RHO6IBB ',
                    aws_secret_access_key='V8f1CwQqAcwo80UEIJEjc5gVQUSSx5ohQ9GSrr12',
                    config=Config(signature_version='s3v4'),
                    region_name='us-east-1')

# Generate the URL to get 'key-name' from 'bucket-name'
url = s3.generate_presigned_url(
    ClientMethod='get_object',
    Params={
        'Bucket': 'atul',
        'Key': 'eReceipt.pdf'
    }
)

# Use the URL to perform the GET operation. You can use any method you like
# to send the GET, but we will use requests here to keep things simple.
response = requests.get(url)
print url

You can curl the url it prints, hope it helps.

@koolhead17 Got it！ Thanks a lot

Hi @koolhead17
When I  upload  a file to generate_presigned_url with brower ,the uploaded file contains a WebKitFormBoundary header and footer, like this:
------WebKitFormBoundarySL7tAOmBXV8JjBpj^M
Content-Disposition: form-data; name="test.txt"; filename="test.txt"^M
Content-Type: text/plain^M
^M

How to get rid of WebKitFormBoundary in uploaded file
Thanks

Fixed the referenced document, closing.

@koolhead17  Got it , thanks !

Fixed the referenced document, closing.

Can you tell me what you did for this upload to work? I spending a lot of time to fix tho solve this... ):

Hello @wwj718 I see a solution for the same suggested on stackoverflow See if you can apply it with your code and it helps.
thanks.

remember for change your upload types
like
const file = $input[0].files[0];