Bluesky = fediverse: can't yet handle load from influx of new Brazilian users

Instructed my friends migration to bluesky to follow https://bsky.app/profile/ap.brid.gy so I could follow them on mastodon. But they never received the DM informing their mastodon handle and trying to retrive them directly from https://fed.brid.gy/[user] returns 404
Is it overloaded? Is it broken? Are us doing something wrong?
I followed from mastodon and it created my bsky handle in less than a minute and my posts are being bridged perfectly

+1
Also having the same issue, my friends and I all followed the @ap.brid.gy account and received no messages.

Hey all, sorry for the trouble! Bridgy Fed's Bluesky => fediverse direction is indeed overloaded and backed up right now due to the huge wave of new users and usage (10x normal!) from Brazil. It's working through the backlog, but it's definitely behind.
I've been optimizing a few things, and I have at least one or two more things I can do that won't take a bigger redesign, but I won't have much time this weekend to work on it. We'll see. Fingers crossed!
https://bsky.app/profile/pfrazee.com/post/3l2xupwbsfy2f

https://bsky.app/profile/bnewbold.net/post/3l2yppyjo6p2k

ohhh that's really a lot! Would it be possible to have a mean time for process completion on the main site somewhere?
people on bluesky are usually my least tech savy friends and asking them to follow an account for me to be able to follow them is already a difficulty to explain. When the process breaks the expectation it can lose the opportunity window and they give up the idea altogether as a broken thing (reason I could not convince them to create mastodon accounts again after 2022 exodus fail)

Totally understood and agreed! And monitoring for our backlog is a good idea, at least internal if not public too. I've filed #1296 for that.

people on bluesky are usually my least tech savy friends and asking them to follow an account for me to be able to follow them is already a difficulty to explain. When the process breaks the expectation it can lose the opportunity window and they give up the idea altogether as a broken thing (reason I could not convince them to create mastodon accounts again after 2022 exodus fail)

On that note, it would be great if there was a DM to inform users who get caught in the spam filter of the requirements, too.
Right now it just looks like it fails silently if the account isn't old enough, if I'm not mistaken.

So, overall firehose event rate is up something like 10x, from 100-200/s to 1-1.5k/s. I've gotten our event handling rate up a bit, but not yet enough to keep up, much less work through the backlog. I've moved all of our logic off the main firehose client thread, tried switching CBOR parsing lib from hashberg dag-cbor to libipld, and even parallelized parsing itself. Still haven't managed to get higher than mid 100s of events/s, nor have I gotten CPU utilization above 1.5-2 cores, which implies that the websocket client itself is the bottleneck.
A bit more background in #1266, but only somewhat relevant.
https://bskycharts.edavis.dev/static/dynazoom.html?plugin_name=edavis.dev%2Fbskycharts.edavis.dev%2Fbsky&start_iso8601=2024-08-25T12%3A00%3A03-0700&stop_iso8601=2024-09-01T16%3A15%3A39-0700&start_epoch=1724612403&stop_epoch=1725232539&lower_limit=&upper_limit=&size_x=800&size_y=400&cgiurl_graph=%2Fmunin-cgi%2Fmunin-cgi-graph
(doesn't include a number of event types, eg #account, #identity, #tombstone, maybe deletes, etc)

I'm glad someone noticed and made this issue, because I wondered if it was my internet or if something had happened to this service. I don't envy the tough work needed but I am hoping for no working too hard! After all, breaks are important D: Especially with this massive scaling, jeez...Thank you for all your hard work, snarfed!

Finally managed to optimize our firehose processing from ~200 events/s up to 3-4k/s. Bluesky => fediverse bridging backlog is down from its high of 3d to just 18h now, should be caught up and back to realtime in another 5h or so.

Done! Back to realtime.


Update Triage-issues-before-devs-see-them.md

I hope the last paragraph, "Create JIRA workflow to triage raw issues", reflects your meaning and what you want me to do with bulleted points, correctly!

yes that looked good (this is still the first major pass at the content, and paragraphs like those will most likely be rewritten)
So far so good, great set of changes :)


"Ghost" installations of certain apps

Brief description of your issue
When using the upgrade command (winget upgrade), it lists all availabe updates, but there are several that can't be updated or uninstalled. To me, they seem like ghost applications.
Steps to reproduce
I don't know what I did to get here.
Expected behavior
Every app either not installed or updated should not be displayed when running winget upgrade.
Actual behavior
> winget upgrade
Name             ID                            Version  Available Quelle
------------------------------------------------------------------------
digiKam 7.9.0    KDE.digikam                   7.9.0    8.2.0     winget
blender          BlenderFoundation.Blender.LTS 3.3.3    3.3.14    winget

Above, you see several applications, supposedly awaiting an update, but in both cases, updating them doesn't do anything about these "entries".
With digiKam, it downloads and runs the 8.2.0 installer, even though 8.2.0 is already installed, and 7.9.0 isn't even on my pc.
In the case of blender, I can't update or uninstall it, every time I try, I get exitcode 1605.
In both cases, even if they aren't installed, they show up when I run winget upgrade (blender isn't installed, digiKam is).
This issue is similar to #4066.
Environment
Windows: Windows.Desktop v10.0.22631.3007
Systemarchitektur: X64
Paket: Microsoft.DesktopAppInstaller v1.21.3482.0

Sometimes, the best method is to perform the uninstall multiple times, to remove all old versions. Then to perform the install again. The ultimate root cause is having old entries in the Registry, and sometimes on disk. This might happen if one version were installed through one installer type, and then another version installed through another type. And so detangling this situation sometimes requires working at it from multiple sides.
When you say you're unable to uninstall blender, is that only through WinGet, or is the Apps Settings page uninstaller also unsuccessful?

When you say you're unable to uninstall blender, is that only through WinGet, or is the Apps Settings page uninstaller also unsuccessful?

When using WinGet, it gives me error 1605, as the uninstaller can't be found. This version of Blender doesn't even show up in the settings app.

Sometimes, the best method is to perform the uninstall multiple times, to remove all old versions.

I have tried, but no luck there. It just stays there. In the case of digiKam, the entry even persists in the settings app, but once uninstalled, it's not uninstallable a second time. The version that's displayed in the settings app is 7.9.0, even though 8.2.0 is/was installed. Even the uninstaller says 8.2.0.

We've been working on the side-by-side scenarios. You could try the latest release and enable the experimental feature on:

https://github.com/microsoft/winget-cli/releases/tag/v1.8.924-preview

Please provide feedback at:

https://github.com/microsoft/winget-cli/discussions/4281

Think I might have an idea on what's going on here!
When some applications are installed, they also can install other applications as a dependency. A good example of this is applications that install their own version of 7zip. Another example is Fortnite installing GeForce Experience.
Some of these dependencies might be full applications or embedded, but I believe Winget is picking these up as fully installed applications. I believe that's also why you can't uninstall it or see it in the settings app.
Can you check your other installed programs and see if they installed these?

Can you check your other installed programs and see if they installed these?

@davidldennison how would I check whether or not a different application has any of the above applications as a depency?
I'd like to check, even though I'm quite sure I don't have any other apps dependant on these.
Some additional information on both digiKam and blender:

digiKam seems to upgrade fine (it's on version 8.3.0 already now), but it seems to doesn't update its version in the settings and Winget (in the app itself, it says it's 8.3.0)
blender can't be found anywhere, not in the settings, not in the explorer (as far as I've looked at least). It only shows up in Winget

After diving into Winget Source Code and investigating logs, in my case it ended up being a Registry issue.
First, run winget list --upgrade-available --verbose-logs
Then winget list --upgrade-available --logs which will open the logs directory.
Find the latest log file which correlates to the command and find which ghost app its trying to update. In that line you will find a product code format {GUID}
Open regedit and navigate to HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\. If the app is 32 bit, go to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\.
In that list of guids in that registry folder, find your product code and delete the folder, NOTE: Make sure that the app is not installed in your program files, app data etc.
Give your PC a restart then try the winget upgrade command again

Find the latest log file which correlates to the command and find which ghost app its trying to update. In that line you will find a product code format {GUID}

@vatsalyagoel, I'm unable to find GUID, any chance you could offer some more information? Maybe an example on how it should look?

Using the latest version of WinGet 1.8, do you see multiple versions of these packages installed?
If they are installed, you should now be able to target the individual versions to remove them.

Using the latest version of WinGet 1.8, do you see multiple versions of these packages installed? If they are installed, you should now be able to target the individual versions to remove them.

@denelon nope, it still won't work. I used the following command:
> winget uninstall BlenderFoundation.Blender -v 3.3.3

Gefunden blender [BlenderFoundation.Blender]
Paket-Deinstallation wird gestartet...
Deinstallation fehlgeschlagen mit Exitcode: 1605

I have this issue with Blender, too. I can't find anything in my registry either. If you do figure out how to remove this, please report back. It has been driving me bonkers.


Population :: Add a new column against each state mentioning the population or Cases/1M population

Population :: Add a new column against each state mentioning the population or Cases/1M population.
This will help understand how severe hit a state is.

May I fix this issue @JunaidBabu ?

statewise google sheet is not having overall population information...This census link may be helpful here.
Statewise Overall Population Census Link

Can we get data for population in respective districts we're displaying? If so, instead of cluttering the state rows with another datapoint, the district table had empty slots that can be filled.
Thoughts on the availability of district wise population?

There is already a PR on this #228
But we'll be handling this as a separate tab. Closing this for now. Will add later.


Exclude set committee in timelock

Since governance can call set committee only before the committee checked in it is logical to exclude it from being timelocked and be more quick to onboard vaults

That's already done though


Bump version because of https://www.tenable.com/plugins/nessus/201969

Updating node version to 20.15.1 as that resolves above finding (https://www.tenable.com/plugins/nessus/201969)

Hi, @riemers, Thank you for the contribution, I'm closing the PR as your changes were included in the PR.
I've added you as a contributor and thank you again for rising the CVE!


[stable/fluentd] Session affinity

Signed-off-by: Chris Sng<EMAIL_ADDRESS>
Is this a new chart
No

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Allow configuring session affinity on the Service resource. This will ensure that connections from a particular client are forwarded to the same pod. Can be useful in avoiding filename clashes when multiple pods output logs to a common store like S3.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

@rendhalver @hectorj2f Appreciate an ok-to-test and a quick review please.

Hi @hectorj2f, if this PR is good to go, appreciate to have it approved and merged. 🙏

@hectorj2f Can we have this PR merged please?


Cleanup Hardhat Tasks

simplifies code for tasks in the hardhat.config.ts file

uses ethers functions instead of doing stuff manually

includes format fixes from #36

@passabilities  thanks!  sorry about the delay i was on vacation, then got sick.
suggested some changes

closed due to lack of response


Trouble with configuration.yaml

Hi @ColinRobbins
I am having trouble with adding this to my configuration.yaml as it keeps throwing this error:
Invalid config for [lightwave]: expected a dictionary for dictionary value @ data['lightwave']['trv']. Got None
I have copied the exact config example that you provided but still throwing the errors. Any advice you can offer would be appreciated. I had this up and running using your previous HAP-NodeJS version for quite a few years but like you, I have changed over to the Homeassistant family.

Hello, can you please provide your exact configuration?
Have you compared it to the configuration described in: https://www.home-assistant.io/integrations/lightwave/

Hi, here it is:
lightwave:
host: '192.168.0.xx'
lights:
R1D1:
name: Bedroom lights
R6D1:
name: Landing lights
R4D2:
name: Front lights
R4D1:
name: Back lights
R7D1:
name: Hallway lights
R9D2:
name: Dining lights
R8D1:
name: Baby Room lights
R3D1:
name: Garden lights
R4D4:
name: Standlight lights
trv:
  trv_proxy_ip: <IP_ADDRESS>

  trv_proxy_port: 7878
  trvs:
  R1Dh:
  name: Bedroom TRV
  serial: 0B2902

I think you have some formatting issues there, getting the indentation correct is crucial.
Looks like you need:
lightwave:
  host: '192.168.0.xx'
  lights:
    R1D1:
      name: Bedroom lights
  trv:
    trv_proxy_ip: <IP_ADDRESS>
    trv_proxy_port: 7878
    trvs:
      R1Dh:
        name: Bedroom TRV
        serial: 0B2902

Hi again Colin,
I copied the above and commented out everything else and I am getting this error:
Logger: homeassistant.components.hassio
Source: components/hassio/init.py:383
Integration: Hass.io (documentation, issues)
First occurred: 20:47:10 (3 occurrences)
Last logged: 21:08:07
Invalid config for [lightwave]: [trv] is an invalid option for [lightwave]. Check: lightwave->lightwave->lights->R4D4->trv. (See /config/configuration.yaml, line 129).
Component error: trv - Integration 'trv' not found.
Invalid config for [lightwave]: [trv_proxy_ip] is an invalid option for [lightwave]. Check: lightwave->lightwave->trv->trv_proxy_ip. (See /config/configuration.yaml, line 157).
What am I doing wrong? I have been scratching my head over this issue for 2 days now.

The line:
Invalid config for [lightwave]: [trv] is an invalid option for [lightwave]. Check: lightwave->lightwave->lights->R4D4->trv. (See /config/configuration.yaml, line 129).

suggests you have something like:
lightwave:
  host: '192.168.0.xx'
  lights:
    R1D1:
      name: Bedroom lights
      trv:

i.e., the trv line is indented to much.   It should be indented to the same level as the lights.
Also, just to check, you are using the latest homeassistant, which has the the lightwave TRV element build in.
(Older versions required a custom_component/lightwave directory in home assistant, where the configuration was different - if you have a custom_component/lightwave in your homeassistant config, remove it as it been replaced by code builtin to home assistant).
If this does not help, please paste your exact configuration, correctly formatted as code using the "insert code" option, so I can see the exact formatting.

Also, make sure the configuration.yaml is using spaces only, and no tab characters.

Still can't get this sorted.  What am I doing incorrectly? Here is my configuration.yaml:

alarm_control_panel:

platform: manual
armed_home:
delay_time: 0
code: 1321
delay_time: 0
disarmed:
trigger_time: 300
name: "Home Alarm"
trigger_time: 10
#apple_tv_mrp:
#- #name: Living Room Apple TV
#host: <IP_ADDRESS>
#port: 49152
#credentials: 3d594d252e442a544af60223caa23d72bf0e8234253c4a97e8f49778efc0ece8:26b01a3ea34141e2529601e0cb2326baa49b2eb055bb2e637c69753059bb073f:33653566376462642d653538642d343735612d613766642d613932363332646365383433:34373664643938312d376633322d343962632d623531312d613266663161623866616366

automation:
action:
  entity_id: alarm_control_panel.home_alarm
  service: alarm_control_panel.alarm_trigger
alias: "Trigger alarm while armed away"
condition:
  -
    condition: state
    entity_id: alarm_control_panel.home_alarm
    state: armed_away
trigger:
  -
    entity_id: binary_sensor.front_door
    platform: state
    to: active
  -
    entity_id: binary_sensor.kitchen_pir
    platform: state
    to: "on"
  -
    entity_id: binary_sensor.landing_pir
    platform: state
    to: "on"
  -
    entity_id: binary_sensor.hallway_pir
    platform: state
    to: "on"
  -
    entity_id: binary_sensor.lounge_pir
    platform: state
    to: "on"
  -
    entity_id: switch.siren
    platform: state
    to: active

tuya:
platform: smart_life
username<EMAIL_ADDRESS>password: thgirw47
country_code: '61'
config: ~
logger:
default: warning
logs:
homeassistant.components.homekit: debug
pyhap: debug
mobile_app:
cloud:
discovery: ~
frontend:
themes: !include_dir_merge_named themes
hacs:
#token: 93fdc48d7188e5fb50bd77eadc8feb12afae28f9
homekit:
media_player.media_player.ue55c7000_samsung_dtv_rcr:
name: "TV"
feature_list:
- feature: on_off
- feature: play_pause
- feature: play_stop
- feature: toggle_mute
- feature: volume_up
- feature: volume_down
alarm_control_panel.home_alarm:
code: '1321'
- feature: on_off
- feature: toggle_mute
  #- alarm_control_panel
  #- light
 # - media_player
 # - switch
#include_entities:
#  - binary_sensor.front_door
 # - binary_sensor.hallway_pir
 # - binary_sensor.kitchen_pir
  #- binary_sensor.landing_pir
  #- binary_sensor.lounge_pir
 # - binary_sensor.smoke_alarm
 # - switch.siren
 # - sensor.blink_bedroom_temperature
  #- sensor.blink_changing_room_temperature
  #- binary_sensor.blink_back_garden_motion_detected
  #- binary_sensor.blink_bedroom_motion_detected

konnected:
access_token: thgirw49
api_host: "http://<IP_ADDRESS>:8123"
devices:
-
binary_sensors:
-
name: "Front Door"
type: door
zone: 1
-
name: "Hallway Pir"
type: motion
zone: 2
-
name: "Lounge Pir"
type: motion
zone: 3
-
name: "Kitchen Pir"
type: motion
zone: 4
-
name: "Smoke Alarm"
type: smoke
zone: 5
-
name: "Landing Pir"
type: motion
zone: 6
host: "<IP_ADDRESS>"
id: 84f3ebfc96f1
port: "24553"
switches:
-
name: siren
zone: out
#simpleicons:
logbook:
history:
stream:
system_health: ~
#camera:
- platform: ffmpeg
name: Motorola Mia's Bedroom
#platform: ffmpeg
# name: Driveway
#input: -rtsp_transport tcp -i rtsp://<IP_ADDRESS>:554/user=admin&password=&channel=1&stream=0.sdp?/
# name: Hallway

input: -rtsp_transport tcp -i rtsp://<IP_ADDRESS>:554/user=admin&password=&channel=3&stream=0.sdp?/
#- platform: ffmpeg
input: -rtsp_transport tcp -i rtsp://<IP_ADDRESS>:554/user=admin&password=&channel=4&stream=0.sdp?/
#ffmpeg:
#ffmpeg_bin: /home/homeassistant/lib/python3.7/site-packages/homeassistant/components/ffmpeg
#blink:
#username<EMAIL_ADDRESS>#password: 'thgirw48'
#scan_interval: 300
#lightwave:
#host: '<IP_ADDRESS>'
#trv_proxy_ip: <IP_ADDRESS>
#trv_proxy_port: 7878
#lights:
#R1D1:
#name: Bedroom lights
#R6D1:
#name: Landing lights
#R4D2:
#name: Front lights
#R4D1:
#name: Back lights
#R7D1:
#name: Hallway lights
#R9D2:
#name: Dining lights
#R8D1:
#name: Baby Room lights
#R3D1:
#name: Garden lights
#R4D4:
#name: Standlight lights
#trv:
#R1Dh:
#name: Bedroom TRV
#serial: 0B2902
lightwave:
host: <IP_ADDRESS>
lights:
R1D1:
name: Master bedroom lights
R1D4:
name: Landing lights
R7D1:
name: Hallway lights
R9D4:
name: Dining lights
R8D1:
name: Mia's bedroom lights
R3D1:
name: Garden wall lights
R4D3:
name: Living room lights
R4D4:
name: Standlight lights
trv:
trv_proxy_ip: <IP_ADDRESS>
trv_proxy_port: 7878
trvs:
R1Dh:
name: Bedroom TRV
serial: 0B2902

Hi Colin, still can't figure this out so here is my configuration.yaml. Thanks for the advice by the way.

alarm_control_panel:

platform: manual
armed_home:
delay_time: 0
code:'xxxx'
delay_time: 0
disarmed:
trigger_time: 300
name: "Home Alarm"
trigger_time: 10
automation:

action:
entity_id: alarm_control_panel.home_alarm
service: alarm_control_panel.alarm_trigger
alias: "Trigger alarm while armed away"
condition:
condition: state
entity_id: alarm_control_panel.home_alarm
state: armed_away

trigger:
entity_id: binary_sensor.front_door
platform: state
to: active

entity_id: binary_sensor.kitchen_pir
platform: state
to: "on"
entity_id: binary_sensor.landing_pir
platform: state
to: "on"
entity_id: binary_sensor.hallway_pir
platform: state
to: "on"
entity_id: binary_sensor.lounge_pir
platform: state
to: "on"
entity_id: switch.siren
platform: state
to: active
tuya:
platform: smart_life
username<EMAIL_ADDRESS>password: xxxxxxxx
country_code: '61'
config: ~
logger:
default: warning
logs:
homeassistant.components.homekit: debug
pyhap: debug
mobile_app:
cloud:
discovery: ~
frontend:
themes: !include_dir_merge_named themes

hacs:
#token: 93fdc48d7188e5fb50bd77eadc8feb12afae28f9
homekit:
media_player.media_player.ue55c7000_samsung_dtv_rcr:
name: "TV"
feature_list:
- feature: on_off
- feature: play_pause
- feature: play_stop
- feature: toggle_mute
- feature: volume_up
- feature: volume_down
alarm_control_panel.home_alarm:
code: '1321'
konnected:
access_token: thgirw49
api_host: "http://192.168.0.xx:8123"
devices:
-
binary_sensors:
-
name: "Front Door"
type: door
zone: 1
-
name: "Hallway Pir"
type: motion
zone: 2
-
name: "Lounge Pir"
type: motion
zone: 3
-
name: "Kitchen Pir"
type: motion
zone: 4
-
name: "Smoke Alarm"
type: smoke
zone: 5
-
name: "Landing Pir"
type: motion
zone: 6
host: "192.168.4.xx"
id: 84f3ebfc96f1
port: "24553"
switches:
-
name: siren
zone: out
#simpleicons:
logbook:
history:
stream:
system_health: ~
lightwave:
host: 192.168.0.xx
lights:
R1D1:
name: Master bedroom lights
R1D4:
name: Landing lights
R7D1:
name: Hallway lights
R9D4:
name: Dining lights
R8D1:
name: Mia's bedroom lights
R3D1:
name: Garden wall lights
R4D3:
name: Living room lights
R4D4:
name: Standlight lights
trv:
trv_proxy_ip: <IP_ADDRESS>
trv_proxy_port: 7878
trvs:
R1Dh:
name: Bedroom TRV
serial: 0B2902

Sorry, I can't tell with this config file as shown as I can't see the indentation - which is crucial.
If you use the "insert code" <> in the formatting bar, then place the config there, it will preserve the indentations.
Can you also please check that you do NOT have a folder in your homeassistant configuration called custom_components/lightwave.  It looks a bit like it might be picking up the way this used to work, before integrated into HomeAssistant.
Also, what version of HomeAssistant are you running?

I did try to use the insert code <> icon. Unfortunately I have never used it before and was unsure. I have now searched how to use it. Also I am on the latest version of Home Assistant 0.117.6 and yes I did have a Custom component folder but have since  deleted it when you mentioned it.
---
alarm_control_panel:
  - platform: manual
    armed_home:
      delay_time: 0
    code:'xxxx'
    delay_time: 0
    disarmed:
      trigger_time: 300
    name: "Home Alarm"
    trigger_time: 10
automation:
  -
    action:
      entity_id: alarm_control_panel.home_alarm
      service: alarm_control_panel.alarm_trigger
    alias: "Trigger alarm while armed away"
    condition:
      -
        condition: state
        entity_id: alarm_control_panel.home_alarm
        state: armed_away
    trigger:
      -
        entity_id: binary_sensor.front_door
        platform: state
        to: active
      -
        entity_id: binary_sensor.kitchen_pir
        platform: state
        to: "on"
      -
        entity_id: binary_sensor.landing_pir
        platform: state
        to: "on"
      -
        entity_id: binary_sensor.hallway_pir
        platform: state
        to: "on"
      -
        entity_id: binary_sensor.lounge_pir
        platform: state
        to: "on"
      -
        entity_id: switch.siren
        platform: state
        to: active
tuya:
  platform: smart_life
  username<EMAIL_ADDRESS>  password: xxxxxxxx
  country_code: '61'
config: ~
logger:
  default: warning
  logs:
    homeassistant.components.homekit: debug
    pyhap: debug
mobile_app:
cloud:
discovery: ~
frontend:
 themes: !include_dir_merge_named themes
# hacs:
  #token: 93fdc48d7188e5fb50bd77eadc8feb12afae28f9
homekit:
  media_player.media_player.ue55c7000_samsung_dtv_rcr:
    name: "TV"
    feature_list:
      - feature: on_off
      - feature: play_pause
      - feature: play_stop
      - feature: toggle_mute
      - feature: volume_up
      - feature: volume_down
    alarm_control_panel.home_alarm:
      code: '1321'
konnected:
  access_token: xxxxxxx
  api_host: "http://192.168.0.xx:8123"
  devices:
    -
      binary_sensors:
        -
          name: "Front Door"
          type: door
          zone: 1
        -
          name: "Hallway Pir"
          type: motion
          zone: 2
        -
          name: "Lounge Pir"
          type: motion
          zone: 3
        -
          name: "Kitchen Pir"
          type: motion
          zone: 4
        -
          name: "Smoke Alarm"
          type: smoke
          zone: 5
        -
          name: "Landing Pir"
          type: motion
          zone: 6
      host: "192.168.4.xx"
      id: 84f3ebfc96f1
      port: "24553"
      switches:
        -
          name: siren
          zone: out
#simpleicons:
logbook:
history:
stream:
system_health: ~
lightwave:
  host: 192.168.0.xx
  lights:
    R1D1:
      name: Master bedroom lights
    R1D4:
      name: Landing lights
    R7D1:
      name: Hallway lights
    R9D4:
      name: Dining lights
    R8D1:
      name: Mia's bedroom lights
    R3D1:
      name: Garden wall lights
    R4D3:
      name: Living room lights
    R4D4:
      name: Standlight lights
  trv:
      trv_proxy_ip: <IP_ADDRESS>
      trv_proxy_port: 7878
      trvs:
        R1Dh:
          name: Bedroom TRV
          serial: 0B2902

Ah, there is an extra "trv_"  trv_proxy_ip should be proxy_ip.
You've also got a couple of extra spaces in there, not sure if they are signifincant or not.
Anyway, try...
lightwave:
  host: 192.168.0.xx
  lights:
    R1D1:
      name: Master bedroom lights
  trv:
    proxy_ip: <IP_ADDRESS>
    proxy_port: 7878
    trvs:
      R1Dh:
        name: Bedroom TRV
        serial: 0B2902

The above loads OK on my test system.

I also noticed you reference by old Node_JS code for doing this.   I presume this means you use Apple Homekit too.
If you add:
homekit:
  filter:
    include_domains:
      - climate

the TRVs will appear in Apple HomeKit too.
(You'll need to follow the Setup instructions for homekit in: https://www.home-assistant.io/integrations/homekit/

Hi @ColinRobbins, thanks for all the help and for integrating this into HomeAssistant! You solved my problem.
Just a note that it is shown with the trv_proxy_ip: <IP_ADDRESS> which is a little misleading and may cause others t have the same issue.
So I have it now setting the temperature, but haven't got the proxy server to start as yet, because HomeAssistant Terminal is giving me bash lwproxy: command not found.

Phew, glad we've got that bit working.
Thanks for the report on the documentation error, I've put in a request for it to be fixed:
https://github.com/home-assistant/home-assistant.io/pull/15700

As to:

HomeAssistant Terminal is giving me bash lwproxy: command not found.

You need to install lwproxy, as this is outside of the Home Assistant environment.
The simplest was is to type the following in your BASH shell...
pip3 install lw-trv-proxy

Full documentation: https://github.com/ColinRobbins/Homeassistant-Lightwave-TRV

Hi again @ColinRobbins, I am a bit confused how to use this Terminal in HomeAssistant, as I did have it running in older version as a virtual environment, where I was able to open the CLI Terminal and execute all the commands easily. However I thought it would be better to install it by itself on my Pi3.  This is what I got this time:

Sorry, I don't know about that, I'm still running in a Python Virtual environment, where I can add extra modules.
Looking at
https://community.home-assistant.io/t/components-require-additional-python-code-library/41148
it seems others tried to fool HA into installing extra modules.
Guessing,
python3 -m install lw-trv-proxy
might work.
If not, you could try to find the file:
homeassistant/components/lightwave/manifest.json
(not 100% sure of the full path to the file, but it'll be on the disk somewhere, possibly under /usr/lib/python3.9/site-packages)
and edit it to add the proxy line:
{
  "domain": "lightwave",
  "name": "Lightwave",
  "documentation": "https://www.home-assistant.io/integrations/lightwave",
  "requirements": ["lightwave==0.19"],
  "requirements": ["lw-trv-proxy==0.6.2"],
  "codeowners": []
}

and restart, which should force the download.
But I'm guessing, as I don't run Home Assistant this way.

Thanks @ColinRobbins, I'll give your suggestion a try and let you know how it goes. Thanks again for all the support. I owe you a drink!

... or if you happen to have another Linux server, you can run the proxy on that.

Thanks for noticing this! Had the same issue going on!

Hi @ColinRobbins, I have tried the things that you have suggested and no dice unfortunately. So last resort was to try and run it on another Linux server. I tried to run from a Raspberry Pi2 that I still have running Homebridge for my Camera's in HomeKit. This proved to be problematic as it is running Python2.7 and I got the error "Could not find a version that satisfies the requirement lw-trv-proxy (from versions: ) No matching distribution found for".
So now I am setting up an old Pi Zero with a clean install of Raspberry Pi OS just to run the Proxy server! I'll let you know if I succeed finally.

Getting this when I try to start the proxy server:
pi@raspberrypi:~ $ lwproxy & [1] 910
Is this correct? How can I tell if it has started correctly? Not seeing the current temperature being displayed.
Best wishes.

This proved to be problematic as it is running Python2.7 and I got the error "Could not find a version that satisfies the requirement lw-trv-proxy (from versions: ) No matching distribution found for".

Yes, you will need Python 3.
I have a Pi 2 as my Dev environment and it works fine on there.  The distribution supports it, so a dist update should fix that.

Is this correct? How can I tell if it has started correctly? Not seeing the current temperature being displayed.
Yes, that looks about right,  the proxy has started.
It will take time to gather data, as the TRVs only broadcast their state when something changes.  One way to force the TRV to broadcast state, is change the target temperature.

Hi Colin,  I think I need to change the Default IP address of the server as it is on a different Pi. Is that correct?

Correct, you’ll need -i to specify the IP address...
trvproxy -i 192.168.x.x &

Then change the configuration on home assistant TRV config as well.

Hi Colin, you're  an absolute legend! I finally have Current temperature being displayed in Homeassistant and HomeKit. I cannot tell you how happy this has made me! (Sad, I know)
Also the command for specifying the IP address is:
lwproxy -i 192.168.0.xxx &
Once again thanks for all your support and for creating this Plugin. It is greatly appreciated.

Great news.


OCP4 (CRI-O Engine) and the Splunk-connector-for-kubernetes log lines are separated

What happened:
We have currently observed a strange behavior in the logging of the OCP4 (CRI-O Engine) and the Splunk-connector-for-kubernetes
The connector actually works as expected, but individual log lines are separated into several lines
The logs in the Openshift Build-Pod (so far only occurred with these) look completely normal. About as:
... [INFO] DM :: AVShare :: Messaging :: Payload DM-ES ........ SUCCESS [0.471 s] ....
The engine of the new Openshift 4 called CRI-O only writes such logs in chunks in the file system of the respective worker node.

In this case, the Splunk Connector works properly and then grabs these torn log fragments and sends them to the Splunk. Works as designed but incredibly unattractive in practice.
We have already checked with RedHat. It is completely normal that the log lines are saved in such a torn way. You can't do anything about that. According to RedHat, the splunk-connector is not supported by RH, so no help can be expected here.
The Splunk connector knows that it is the CRI-O engine, because this is stored in the config and in the Helm chart:
Because he always parses the beginning of the line and cuts away the beginning so that only the content of the log remains:
E.g.:
Log: 2020-10-05T04: 38: 15.957601404 + 00: 00 stdout P [INFO] DM :: AVShare :: Messagi
Connector is sending this to splunk: [INFO] DM :: AVShare :: Messagi
Timestamp up to and including “stdout P / F” is always cut off here.
Helmchart value:  logFormatType: cri
The logic behind these lines is as follows: Everything that ends in “stdout P” is an incomplete line (the line is therefore abruptly torn off here). But lines ending in “stdout F” correspond to a complete line or, in this case, a line end. So you can always tell what a complete log line would correspond to (all "stdout P" summarized up to the next "stdout F")
The question is, can you reconfigure the splunk-connector so that it combines these separate log lines (stdout P to the next stdout F) into one line?
Environment:

OpenShift 4.5.14
Splunk version: Splunk Enterprise 8.0.3
Splunk Connect for Kubernetes helm chart version: 1.4.2

Hello,
I think using concat plugin and regex parsing, it seems possible but you need to find the pattern for either the start or the end of log data. https://github.com/fluent-plugins-nursery/fluent-plugin-concat
once you have regex pattern, I think you can set it here:
https://github.com/splunk/splunk-connect-for-kubernetes/blob/fefbcf4a2b9f9e71a18044498dba27aecc9461f6/helm-chart/splunk-connect-for-kubernetes/values.yaml#L163

Hi @rockb1017,
Thank you for your help!
However, I just don't know how and where to install the plugin.
Could you help us again?

this plugin is already installed with the image we are using for SCK logging pod.
just edit the values.yaml file you are using to deploy.
I would start by reading thoroughly of the comments on the values.yaml file and https://github.com/fluent-plugins-nursery/fluent-plugin-concat this github page docs.

I see, i've created a duplicate issue report: https://github.com/splunk/splunk-connect-for-kubernetes/issues/549


Rework UnixAddr to fix soundness issues

Fixes #1494
I went with making sun_path always nul-terminated since that just seems to make things easier, since (at least according to linux man pages) sockaddr_uns returned by the kernel will always be nul-terminated.

I also just changed the documentation of sockaddr_storage_to_addr.

@asomers could you take a look?


airbase conflicts with another repo

"airbase" is already another python repository. Using the same name can cause headaches resolving conflicts

@patrickwalton open to name suggestions 😄

You are welcome 😄

Also thanks for building and sharing this! It's awesome!

Hmm... airtable-async would fine also airsynctable airtablesync asynctable

@cancan101 Looking to get further user feedback on the impact of changing the module name in order to avoid conflicts with another module named airbase. Do you have any issues with the above?

Is the issue here with the name of the repos or the name of the installed Python package? I assume it is the latter.
The sync library's package name pyairtable, so perhaps pyairtable_async?


UnitTest generator?

Feature description
Generate unit test for each property
Reasoning behind
This tool is a great time saver for a starting point when writing mappers. It would be nice to have same generator for unit test asserting mapping of each property. For start it seems not important but when we have some logic after generation in the mapper or we would like to protect our code from regression it would be nice to have those tests generated.
Real word example of the usage
public void AssertName()
{
      var source = new SourceObject
      {
              Name = "Test";
      }
      var mapper = new PersonMapper();

      var mapped = mapper.Map(source);

      Assert.Equal("TestChanged", mapped.Name);

}

Hi @dominikjeske
Honesty, I can't see any value in keeping a separated tests for individual properties. Can you elaborate a little bit more what are the benefits of that approach over having a single test per use case that check all properties?
If you need something that could protect your mappings from the regression then I recommend tools like ApprovalTests.Net or Verify.  Please let me know if that solve your problem?
If you really need this kind of generator then maybe you can achieve that with my other Visual Studio extension https://github.com/cezarypiatek/CsharpMacros

Sometimes first idea is not ideal ;) I have rethinked this again and it would be over engineering;)


fix(gate) Removed BPN Property from Gate

Removed BPN property from LogisticAddress , LegalEntity and Site entities, input request and response, and updated unit tests to work without BPN.
Created a Migration file to drop BPN column from Site, LegalEntity and LogisticAddress

fixes issue #236


Multiple Data Monitoring Banners observed after DM20 timeout

Joe Kartje saw a “temporal” error from the V2 driving tests at each speed interval and restarted function C [Track Monitor Completion Status] after receiving each such error. Could this account for the multiple data monitoring banners?

This error was caused by a NPE pointer exception as a result of not receiving the DM5 from the engine after clearing the DTCs.
2017-06-06 11:21:24.897 SEVERE net.soliddesign.iumpr.controllers.Controller lambda$getRunnable$0 Error
java.lang.NullPointerException: temporal
at java.util.Objects.requireNonNull(Objects.java:228)
at java.time.format.DateTimeFormatter.formatTo(DateTimeFormatter.java:1741)
at java.time.format.DateTimeFormatter.format(DateTimeFormatter.java:1720)
at net.soliddesign.iumpr.modules.DateTimeModule.format(DateTimeModule.java:37)
at net.soliddesign.iumpr.controllers.MonitorCompletionController.run(MonitorCompletionController.java:147)
at net.soliddesign.iumpr.controllers.Controller.lambda$getRunnable$0(Controller.java:425)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Changed the logic to insist the engine respond to DM5, DM20, DM26 and DM21 requests.  If the engine doesn't respond after three attempts, "No Response" is recorded. If a DM5 is no returned, the process will cease thus preventing this error in the future.


Add links to readme and docs for several minor releases

Changes
Add links to readme and docs for several minor releases
Signed-off-by: Andrea Frittoli<EMAIL_ADDRESS>/kind documentation
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Docs included if any changes are user facing
[x] Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes
NONE

/lgtm


Pattern matching

On gitter @jgoux (thanks) has raised an interesting topic: bringing some kind of pattern matching to tcomb.
Something along the lines of the nice @paldepind's library https://github.com/paldepind/union-type.
The first sketch of the API seems nice (especially with ES6 syntax):
const A = t.struct(...);
const B = t.struct(...);

t.match(x, {
  A: (x) => 'doSomething',
  B: (x) => 'doSomethingElse',
  _: (x) => 'optionalCatchAllClause' // optional
})

My main concern is that relying on the (optional) name of a type is kind of brittle.
I'd prefer matching on type constructors (it's also more general):
t.match(x, [
  [ t.String, (s) => 'a string' ],
  [ t.Number, (n) => n > 2, (n) => 'a number gt 2' ], // case with a guard (optional)
  [ t.Number, (n) => 'a number lte 2' ],
  [ A, (a) => 'an instance of A' ],
  [ t.Any, (x) => 'other...'] // catch all
]);

:+1: for the second approach.

A third alternative you might consider is this:
t.match(x,
  A: (x) => 'doSomething',
  B: (x) => 'doSomethingElse',
  _: (x) => 'optionalCatchAllClause' // optional
)

This is probably the simplest one. You have intrinsic ordering in the arguments, so there is no need for another array.

Hi @volkanunsal, thanks for your feedback. Stretching your suggestion and using a strong convention one could even remove all the arrays:
t.match(x,
  t.String, (s) => 'a string',
  t.Number, (n) => n > 2, (n) => 'a number gt 2', // clause with a guard (optional)
  t.Number, (n) => 'a number lte 2',
  A, (a) => 'an instance of A',
  t.Any, (x) => 'other...' // catch all
);

intrinsic ordering in the arguments
clauses are always separated by a type

This is the best one so far. :+1:

I agree, the last proposition is even better. Great job !

I'm curious why you even need a function in the matchers. Don't the function parameters all refer to x anyway? Can't you write it this way to make it even simpler?
t.match(x,
  t.String, 'a string',
  t.Number, ['a number gt 2', x > 2], // case with a guard (optional)
  t.Number, 'a number lte 2',
  A, 'an instance of A',
  t.Any, 'other...' // catch all
);

why you even need a function in the matchers

In short for:

reuse (first case)
correctness: some expression could be invalid or throw an error (second case)
lazyness: expensive operations are performed only when needed (third case)

function isEven(x) {
  return x % 2 === 0;
}

function f(x) {
  return t.match(x,
    t.Number, isEven/* reuse */, () => 'a number',
    t.Number, (n) => /* a string * 2 makes no sense */ n * 2,
    t.String, () => /* say this is an expensive operation */ 'a string'
  );
}

console.log(f('a'));

Ah, yes, good point.

I was wondering, does it work with union of union types ?
If the type to match is a Union type, does it recursively check the types to check all the possibility ?
I want to use this to be able to do command routing/subrouting
Example :
// An aggregate can handle a predefined list of commands
const TodoListAggregate.Command = union([AddTodo, EditTodo])
// An aggregate route the command to its handler
const TodoListAggregate.handle = (command) => {
    return match(command,
        AddTodo, (c) => TodoListAggregate.addTodo(c),
        EditTodo, (c) => TodoListAggregate.editTodo(c)
}

// The domain accept any command defined in the aggregates
const Command = union([TodoListAggregate.Command, AnotherAggregate.Command])
// The domain route the command to its aggregate
const handle = (command) => {
    return match(command,
        TodoListAggregate.Command, (c) => TodoListAggregate.handle(c),
        AnotherAggregate.Command, (c) => AnotherAggregate.handle(c)
}

@jgoux the current implementation (merged in the master branch) uses Union.is so yes is recursive:
var A = t.subtype(t.String, function (s) { return s === 'A'; });
var B = t.subtype(t.String, function (s) { return s === 'B'; });
var C = t.subtype(t.String, function (s) { return s === 'C'; });
var D = t.subtype(t.String, function (s) { return s === 'D'; });
var E = t.subtype(t.String, function (s) { return s === 'E'; });
var F = t.subtype(t.String, function (s) { return s === 'F'; });
var G = t.subtype(t.String, function (s) { return s === 'G'; });
var H = t.subtype(t.String, function (s) { return s === 'H'; });

var U1 = t.union([A, B]);
var U2 = t.union([C, D]);
var U3 = t.union([E, F]);
var U4 = t.union([G, H]);

var UU1 = t.union([U1, U2]);
var UU2 = t.union([U3, U4]);

t.match('F',
  UU1, function () { return '1'; },
  UU2, function () { return '2'; }
); // => '2'

how to deal with union of union types when overriding the dispatch method of the upper union type ? For example how could I use the Command() as a constructor in this case ?

The default implementation of dispatch should work fine.

Shipped in v2.2.1 if you want to give it a spin. Thanks to all


Hiding Window Buttons on Mac

is it possible to be able to hide the window buttons on mac?

You can download this plugin and adjust the following values:


Fetch homoeologues for homoeologue alignments view

Related to ENSEMBL-4750.

Please also apply this change to release/86 branch if it is OK. It fixes an issue with Ensembl Plants.

In that case, could you please create it against postreleasefix/86?

Sorry! Intended to request for postreleasefix branch. Fixed now.


Fixing build issue related to new "na.print" argument in data.table

Thanks Toby @tdhock for bringing this to my attention via issue in data.table.
Recently, a new argument was added to print.data.table, which affected re-building of vignettes, as outlined in the original issue. Credit to @MichaelChirico for the find; the issue was here:
https://github.com/Causal-LDA/TrialEmulation/blob/989f064dfcb68f37ebdf280b2c37f8ee845aae0d/R/generics.R#L50
With the new na.print argument, n = 5 is no longer partially matched to nrows, so the change is trivial. I've also gone ahead and taken a quick look at other function calls that could avoid partial matching in its arguments, and changed those as well.

Thanks @joshhwuu for this PR and apologies I didn't notice it earlier. Will update on CRAN as soon as possible


TextBox completion % not showing in proper location while in 80 cols mode

TextBox completion % not showing in proper location while in 80 cols mode.

I drew a scrollbar instead of 'xx%'


Changed structure to reflect prettiness

We could include the snap packages too in the CI lifecycle

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


[AutoPR cdn/resource-manager] [Testing-please ignore] Testing edits to multiple api versions

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5121

(message created by the CI based on PR content)

Codecov Report

Merging #4295 into restapi_auto_cdn/resource-manager will decrease coverage by 3.23%.
The diff coverage is n/a.

@@                          Coverage Diff                          @@
##           restapi_auto_cdn/resource-manager    #4295      +/-   ##
=====================================================================
- Coverage                              57.26%   54.03%   -3.24%
=====================================================================
  Files                                   8002     5416    -2586
  Lines                                 162696   137390   -25306
=====================================================================
- Hits                                   93166    74234   -18932
+ Misses                                 69530    63156    -6374

Impacted Files
Coverage Δ

...e-mgmt-cdn/azure/mgmt/cdn/cdn_management_client.py
62.96% <ø> (ø)
:arrow_up:

...ure/mgmt/recoveryservicesbackup/models/__init__.py
51.91% <0%> (-48.09%)
:arrow_down:

...ights/azure/applicationinsights/models/__init__.py
53% <0%> (-47%)
:arrow_down:

...ure-mgmt-media/azure/mgmt/media/models/__init__.py
53.33% <0%> (-46.67%)
:arrow_down:

.../azure/mgmt/compute/v2018_06_01/models/__init__.py
53.35% <0%> (-46.65%)
:arrow_down:

.../azure/mgmt/compute/v2018_04_01/models/__init__.py
53.35% <0%> (-46.65%)
:arrow_down:

...iveservices/search/entitysearch/models/__init__.py
53.75% <0%> (-46.25%)
:arrow_down:

...ration/azure/mgmt/datamigration/models/__init__.py
53.89% <0%> (-46.11%)
:arrow_down:

...mgmt-monitor/azure/mgmt/monitor/models/__init__.py
54.1% <0%> (-45.9%)
:arrow_down:

azure-eventgrid/azure/eventgrid/models/__init__.py
54.54% <0%> (-45.46%)
:arrow_down:

... and 2666 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update de0a77b...b7a0e4f. Read the comment docs.

Initial issue closed


[Sprint: 45] XD-2833: Document MongoBD source, add split

I created https://jira.spring.io/browse/XD-2846 to track the initialDelay thing, as there are several modules that could benefit from this.
I suggest merging this PR if this is the only outstanding issue

Actually, I'm applying it to this PR to avoid pollRate going in the wild

LGTM; minor polishing here for your approval before I merge.

Merged as 3c31165cbdd2760373b40ecaffe4626682c82a13


⚠ Aither has degraded performance

In 0603d93, Aither ($AIH) experienced degraded performance:

HTTP code: 200
Response time: 5740 ms

Resolved: Aither performance has improved in 42278c8 after 8 minutes.


Split up thumbnail job

For each layer, a separate job is queued for thumbnailing each image as well as a job for thumbnailing the layer itself. This will enable more parallelism. To test, submit a layer and check that separate jobs are created in the log, and that all thumbnails are actually created.
Connects #262

I'm a little concerned about merging this so close to demo time, let's make sure this get thoroughly tested on staging.

I don't think we should add it on staging til after the demo. Even if it works, it won't have any visible impact on the demo.

I think that is wise.

See new commit.

Hold off on reviewing for now. I just thought of a better way of fixing things.

Ready to review.

+1 Very cool

+1. Looks good and tested successfully across multiple workers. I'd probably sqash the commit together before merge though.


Getting fatal error on Get list of labels. task

The task Get list of labels. is failing after updated with ansible_fqdn on https://github.com/atosatto/ansible-dockerswarm/commit/3bb8a49297448325b8feaa9b7a899c78b2fab97e
The node hostname(staging-manager-03) on docker node ls is different from the fqdn string given on following error:
TASK [atosatto.docker-swarm : Get list of labels.] ********************************************************************************************************************************************
fatal: [<IP_ADDRESS> -> <IP_ADDRESS>]: FAILED! => {"changed": false, "cmd": ["docker", "inspect", "--format", "{{ range $key, $value := .Spec.Labels }}{{ printf \"%s\\n\" $key }}{{ end }}", "staging-manager-03.sgp1"], "delta": "0:00:00.412684", "end": "2020-05-14 13:10:42.573599", "msg": "non-zero return code", "rc": 1, "start": "2020-05-14 13:10:42.160915", "stderr": "Error: No such object: staging-manager-03.sgp1", "stderr_lines": ["Error: No such object: staging-manager-03.sgp1"], "stdout": "", "stdout_lines": []}

For now I am using v2.2.0 which gives no error.

I have the same issue except for 'ambigious' instead of not found.
TASK [atosatto.docker-swarm : Get list of labels.] ******************************************************************************************************************************************* fatal: [asus.yi -> None]: FAILED! => {"changed": false, "cmd": ["docker", "inspect", "--format", "{{ range $key, $value := .Spec.Labels }}{{ printf \"%s\\n\" $key }}{{ end }}", "host.domain"], " delta": "0:00:00.335281", "end": "2020-05-15 22:58:12.700418", "msg": "non-zero return code", "rc": 1, "start": "2020-05-15 22:58:12.365137", "stderr": "Error response from daemon: node host.domain is ambiguous (2 matches found)", "stderr_lines": ["Error response from daemon: node host.domain is ambiguous (2 matches found)"], "stdout": "", "stdout_lines": []}

Thanks @cpxPratik for reporting this issue.
I'll try to reproduce this issue in a test cluster and figure our a better way of managing nodes.
Can you please confirm me the docker version you are using?

@atosatto The docker version is Docker version 19.03.8, build afacb8b7f0

Hello, I'm having the same issue on a cluster. It seems the node object is using hostname instead of the full FQDN.
https://github.com/atosatto/ansible-dockerswarm/commit/3bb8a49297448325b8feaa9b7a899c78b2fab97e
Though, I don't see any references in the playbook that it joins by FQDN, is this a new change on upstream docker?

btw, I'm currently running version 19.03.8

What I did to workaround this is simply use v2.2.0 instead of v2.3.0.
requirements.yml:
- src: atosatto.docker-swarm
  version: v2.2.0

Same issue here, using 19.03.6 (latest Ubuntu 18.04 provided docker.io package)

I have same issue too.

@atosatto We fixed this a while back but it was reverted or we mixed it up. It's inventory_hostname vs fqdn.

Workaround for me was: replace  {{ ansible_fqdn|lower }} on  {{ ansible_hostname }} and from the hostname remove all dots. Was node1.connect become node1connect

How about docker node inspect self --format '...'? We don't have to figure out the name of the object to inspect that way.

@atosatto We fixed this a while back but it was reverted or we mixed it up. It's inventory_hostname vs fqdn.
I thought the same tried to work around by listing the hosts as fqdns in my inventory. No luck.

Hello. I'm also having this issue. Any plans to reaply the fix? Thanks!

I can confirm that the commit 3bb8a49 mentioned in the issue #82 is the one that breaks the labels setup, if it is reverted then the playbook finishes without issues.

Seeing the same behaviour on v2.3.0, rolling back to v2.2.0 resolves this situation.

Another case where this happens is the following:
I had botched my swarm setup, so it was not about node names (e.g. inventory name or fully qualified domain name (fqdn)), but the nodes were no longer seen by the manager.
The role doesn't handle this (no judgement meant) currently. I think it's a split brain/no brain kind of thing, because I had restarted my manager (and I run only one) and then this happened.
The fix was the following:

get the join-token myself
then force leave the workers
(re-)join the manager/cluster

And then the role completes.
The other fix is to run two managers. ;-)
I am not entirely sure how this could be added to the role since the manager doesn't see the workers anymore, but the works think they are still connected. If you can afford it, trash the nodes and setup again. Maybe it's a documentation thing after all?

Same issue on Centos 7.
For now I am using v2.2.0 which works like a charm !

I can confirm that the commit 3bb8a49 mentioned in the issue #82 is the one that breaks the labels setup, if it is reverted then the playbook finishes without issues.

Now I'm not sure if this has to do with this at all, as I have been getting this error several times too with that commit reverted. It always happens when I add a new instance to the cluster. First time I run this role is ok, then I create a new aws instance and run again this role to add it to the cluster and it fails with this error. This is the error message I'm seeing being thrown by ansible on nodes that are already part of the cluster:
<<IP_ADDRESS>> (0, b'', b'')
fatal: [<IP_ADDRESS> -> <IP_ADDRESS>]: FAILED! => {
    "changed": false,
    "cmd": [
        "docker",
        "inspect",
        "--format",
        "{{ range $key, $value := .Spec.Labels }}{{ printf \"%s\\n\" $key }}{{ end }}",
        "10"
    ],
    "delta": "0:00:00.081487",
    "end": "2020-10-15 23:41:24.604902",
    "invocation": {
        "module_args": {
            "_raw_params": "docker inspect --format '{{ range $key, $value := .Spec.Labels }}{{ printf \"%s\\n\" $key }}{{ end }}' 10",
            "_uses_shell": false,
            "argv": null,
            "chdir": null,
            "creates": null,
            "executable": null,
            "removes": null,
            "stdin": null,
            "stdin_add_newline": true,
            "strip_empty_ends": true,
            "warn": true
        }
    },
    "msg": "non-zero return code",
    "rc": 1,
    "start": "2020-10-15 23:41:24.523415",
    "stderr": "Error: No such object: 10",
    "stderr_lines": [
        "Error: No such object: 10"
    ],
    "stdout": "",
    "stdout_lines": []
}

That is the error for the manager, but the workers throw it too.

Same issue on Centos 7.
For now I am using v2.2.0 which works like a charm !

For me it also happens with v2.2.0 as described on my previous comment.


broken link

The link to changes in driver signing for Windows 10 is broken.
The intended page is:
https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/
But you end up here:
https://techcommunity.microsoft.com/t5/Windows-Hardware-Certification/bg-p/WindowsHardwareCertification
You really should stop referring to blogs, especially Microsoft blogs since a lot of them are being deleted.
Also, a blog is not documentation, a blog article is most of the time one individuals personal opinion, and there's no way for a reader to know if it is officially sanctioned by Microsoft and/or whether what is described is supported by Microsoft.
Also, if there are any changes, the blog won't be updated, and the guy who wrote it might not even work for Microsoft any longer.
The same goes for references to StackOverflow, info there is not persistent, if a user removes his account his info might go too, also, any user might update the info after the link was created, so it might now contain completely different info.

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

ID: 716c22a0-7fc1-56a9-a0de-aca1f5b42d1d
Version Independent ID: 493cc896-d2a5-4d9e-74c4-274cd9227612
Content: Trusted Root Certification Authorities Certificate Store - Windows drivers
Content Source: windows-driver-docs-pr/install/trusted-root-certification-authorities-certificate-store.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

Thankss for the suggestion @Bartolomeus-649.  I completely agree with your points about non-persistent link targets.  All of the info from that blog is consolidated on https://docs.microsoft.com/en-us/windows-hardware/drivers/install/kernel-mode-code-signing-policy--windows-vista-and-later-, so I removed the link to the blog article.  Changes should be live in 15 min or so.


Implement splash screen

Should show splash screen during app launch and to show a progress (e.g. loading animation) when sending request to backend.

Is it possible to implement splash screen this weekend? or should we put it into next weeks' roadmap?


/lib folder not present on npm package

I tried one of my other packages which had the same ci/cd config as this one and noticed the npm package didn't have the /lib folder (which is really bad since it's the main folder on both packages).
Then I installed this package to check if the same was happening here and unfortunately it was...
Here is the reference to the issue I'm talking about

The issue was fixed with the above commit


Remove Navintegrity from this protoocl

navIntegrity or any field that is being “bucketed” feels like an older way of doing things. Are we signing up for a future of UTM where we can’t just put the error value? Again, for a bit packed interface it makes some sense

I think technically this covers ATM as well since it will track objects emitting via ADSB so we will have to track it, I will leave it as it is for the moment.


undefined function Random.string/0

Attempted to run the tutorial in a simple app - got this message.
Looks like everything is being pulled in, but the Alias from Misc.Random to Random isn't being called.

Hi Ryan, thanks for pointing me to this! Apparently, mix/hex doesn't pull dependencies that aren't on hex.pm. Your error sais:
(module PlugSessionMEMCACHED is not available)

So one has to include this in your deps section:
 {:mcd, github: "EchoTeam/mcd"}

I updated the README section as well. Again, thanks a lot for your contribution!

Hi @ryanmcgarvey , I fixed this naming issue (I moved a module from Random to Misc.Random) by both publishing Misc.Random to hex for automatic pulls by mix deps.get and aliased Misc.Random - thanks a million for reporting and supplying the aliasing hint.
Now, it should compile and work.


Add icon file for IntelliJ IDEA

PR Checklist

[x] A description of the changes is added to the description of this PR.
[ ] If there is a related issue, make sure it is linked to this PR.
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added or modified a feature, documentation in docs is updated

Description of changes

thank you @ebyhr !


Diagnostic unit tests: SA1015 (ClosingGenericBracketsMustBeSpacedCorrectly)

Implement unit tests for #21.

:exclamation: Make sure to test the following. SA1015 should be reported, and the code fix should remove the space after the comma.
var a = typeof(System.Func<, >);

Grabbing this.


Atom / Hydrogen friendly additions

See changes here.

Please delete it. I've just noticed travis-ci so I've change some things first.


Gradient Boosted Decision Tree (Regression)

https://github.com/Nyker510/gradient-boosted-decision-tree/blob/master/gbdtree/gbdtree.py
https://github.com/rajivsam/DecisionTrees/blob/master/DT.py

Done~


Support for KFServing V2 protocol for torchserve

/kind feature
Describe the solution you'd like
Add KFServing V2 predict api protocol support for torchserve predictor.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

/cc @deadeyegoodwin


[FIX] versionInfoGenerator: hasOwnPreload switched boolean

hasOwnPreload is only true if the library has embeds field set in manifest
and embedded manifest does not have a backlink (embeddedBy) to the library.

Coverage remained the same at 93.969% when pulling 5bd15bed1587630f075868d9c10e242d63d5447e on versionInfoGenerator-hasOwnPreload-fix into fe61d6eba6671ca31f7c49a7d1281adb6d5f2114 on master.

I find hasOwnPreload switched boolean a bit hard to understand as a bug fix message.
Basically this is now fixing how the behavior of the hasOwnPreload flag was intended to be (as follow-up of https://github.com/SAP/ui5-builder/pull/554).


Allow 255 chars for the user agent, as this is the column size in the DB

Allow 255 chars for the user agent, as this is the column size in the DB. The limit of 255 is also enforced in the calling function yourls_log_redirect.

Indeed :)


Improving and Tweaking the Progress Bar

@arjunprakash027
https://github.com/rsalmei/alive-progress#using-alive-progress
Right now, even if the our tool did not upload anything, Progress Bar reaches to 100%..
Hopefully, we can tweak and improve the Progress Bar at some stage.

@vzhd1701 Do you have any clue why would tqdm progress bar would "break" during upload?
Thank you.

tqdm breaks only when something else is printing to stdout or stderr while it's drawing progress bar. You need to figure out why you are getting airlift: error: the following arguments are required: --token, --base, --table error in the middle of the upload.

tqdm breaks only when something else is printing to stdout or stderr while it's drawing progress bar. You need to figure out why you are getting airlift: error: the following arguments are required: --token, --base, --table error in the middle of the upload.

@vzhd1701 Thanks for the insight!

@vzhd1701 Do you have any clue on why progress bar is breaking?  @arjunprakash027 Have been doing various trial and error on solving this.
We have checked our shell scripts. There is no error in our .sh file.

This one looks like a pyinstaller issue. Try adding freeze_support execution early on in the program.

This one looks like a pyinstaller issue. Try adding freeze_support execution early on in the program.

Did you add this freeze support in csv2notion?

No, I did not, but I remember something similar happening before in another project that used multiprocessing/multi-threading.

Thank you for insight!

No, I did not, but I remember something similar happening before in another project that used multiprocessing/multi-threading.

Does that mean, csv2notion does not use multiprocessing/multi-threading.


Use stricter host buffer alignment (64B) required by modern CPUs.

Hi,
Current clpeak does not show full D2H transfer potential of Arc GPU due to stricter alignment requirements on the host.
Using Core Ultra 9 285k Arc 770 is struggling to achieve any reasonable D2H bandwidth (1.6GBps) 14th gen Raptor-lake was better but still subpar (8GBps):
$ ./clpeak --transfer-bandwidth

Platform: Intel(R) OpenCL Graphics
  Device: Intel(R) Arc(TM) A770 Graphics
    Driver version  : 24.39.31294.12 (Linux x64)
    Compute units   : 512
    Clock frequency : 2400 MHz

    Transfer bandwidth (GBPS)
      enqueueWriteBuffer              : 20.25
      enqueueReadBuffer               : 1.69
      enqueueWriteBuffer non-blocking : 21.28
      enqueueReadBuffer non-blocking  : ^C

With the fix:
$ ./clpeak --transfer-bandwidth

Platform: Intel(R) OpenCL Graphics
  Device: Intel(R) Arc(TM) A770 Graphics
    Driver version  : 24.39.31294.12 (Linux x64)
    Compute units   : 512
    Clock frequency : 2400 MHz

    Transfer bandwidth (GBPS)
      enqueueWriteBuffer              : 20.58
      enqueueReadBuffer               : 21.01
      enqueueWriteBuffer non-blocking : 21.86
      enqueueReadBuffer non-blocking  : 22.39
      enqueueMapBuffer(for read)      : 20.38
        memcpy from mapped ptr        : 26.46
      enqueueUnmap(after write)       : 21.94
        memcpy to mapped ptr          : 27.08

For more information please refer to: https://github.com/intel/compute-runtime/issues/775
Please consider merging.

Thanks for the find


Fix misspelling errors and typos reported by codespell

Fixes #10998
(I'll try to cherry-pick to master if possible)

I just verified that the patch can be cherry-picked to master.
When merging, I'll go the opposite way, i.e., I push to master first and then cherry-pick back to 1.1.1, since that's our usual procedure.
@slontis please reconfirm for master.

reconfirmed.

(CHANGES and NEWS spelling errors fixed in #10545 as well, see 20d3e4e389dca22ce8e6da0818532cccb3f0b3f6.)

Sorry Shane, when logging off I just noticed that I had a lot of unsaved files in Emacs. So there is a lot more to review, see 3aa8f8cbe580d444598cc10b4f33f7a0ab2b61ac.
(I should go to bed now...)

I don't think these 'publicly' one's are right..

This brings us to an interesting discursion about grammar again. ;-)
Google seemse to have a clear preference towards publicly (262M) vs. publically (8M). Also, many online dictionaries list the latter only as an alternative spelling. There is an interesting article about this subject on grammarphobia.com, from where I took the following citation.

The Merriam-Webster’s usage guide concludes its entry on “publically” with this advice: “You can use it if you like, but we do not really recommend it, because it will look unfamiliar to many who encounter it.”

I wonder what our british EU expatriate @mattcaswell thinks about it. But if you prefer that the previous spelling remains, I'll revert the changes.

The Oxford lists it as publicly noting that publically is a misspelling:

Note that the spelling is publicly, not -ally.

The Oxford lists it as publicly noting that publically is a misspelling:

Note that the spelling is publicly, not -ally.

Yeah, I've seen that, too. I think it is listed either as uncommon or wrong, depending on how forgiving the dictionary is.

I hear a siren. I think the spelling police are coming.
There is also a conflict in rand_lcl.h

There are certainly more important issues to worry about.

There are certainly more important issues to worry about than spelling variants.

Don't worry, we're just teasing eachother.

I wonder what our british EU expatriate

Ok...no need to rub it in... :-(

@mattcaswell thinks about it. But if you prefer that the previous spelling remains, I'll revert the changes.

publically looks wrong to me.

There is also a conflict in rand_lcl.h

The conflict was caused by the fact that I based my topic branch onto the tag OpenSSL_1_1_1d to get the same line numbers as in codespell.openssl-1.1.1d.txt and forgot to rebase it to the tip of OpenSSL_1_1_1-stable afterwards. I just pushed a rebased version (without other changes).
Apropos rebase: git had no problems to detect the renaming crypto/rand_rand_lcl.h -> crypto/rand_rand_local.h. Maybe GitHub's rename limits are set too low.
$ git config -l | grep limit
merge.renamelimit=32768
diff.renamelimit=32768

Merged to master and 1.1.1, thanks!
7fa8bcfe43 Fix misspelling errors and typos reported by codespell
0f68b771b0 Fix misspelling errors and typos reported by codespell


Iox #27 create client c binding

Pre-Review Checklist for the PR Author

[x] Code follows the coding style of CONTRIBUTING.md
[x] Tests follow the best practice for testing
[x] Changelog updated in the unreleased section including API breaking changes
[x] Branch follows the naming format (iox-#123-this-is-a-branch)
[x] Commits messages are according to this guideline

[x] Commit messages have the issue ID (iox-#123 commit text)
[x] Commit messages are signed (git commit -s)
[x] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[x] Update the PR title

Follow the same conventions as for commit messages
Link to the relevant issue

[x] Relevant issues are linked
[x] Add sensible notes for the reviewer
[ ] All checks have passed (except task-list-completed)
[x] Assign PR to reviewer

Notes for Reviewer
The c binding for the client is implemented and tested.
Please verify that nothing is missing:

The client must be attachable to the waitset (states/events), therefore the waitset binding had to be adjusted
The client must be attachable to the listener (events), therefore the listener binding had to be adjusted
The return value of iox_ws_wait is a iox_notification_info_t, therefore the client had to be added there. There is a separate test for the binding but actually it makes more sense to perform the tests of the notification info directly in the waitset because it is tightly coupled and you cannot test it without the waitset.
The client API must be complete. Please compare the client.h API with the UntypedClient if some functionality is missing.
The tests are not testing the actual UntypedClient (this is done in untyped client unit test), it is testing if the arguments are correctly forwarded and the results are correctly translated - therefore I adjust often the internal state of the ClientPortData to verify the correctness.

Checklist for the PR Reviewer

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code according to our coding style and naming conventions
[ ] Unit tests have been written for new behavior

[ ] Each unit test case has a unique UUID

[ ] Public API changes are documented via doxygen
[ ] Copyright owner are updated in the changed files
[ ] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

References

Closes TBD

Please add the issue link.


Fix: asp-append-version ignored for urls containing fragment

Issue - #2862
@dougbu
unrelated nit: Removed some unnecessary whitespace in ImageTagHelperTest.

:shipit:

:shipit:


Abort requests on native targets

Is your feature request related to a problem? Please describe.
On the web fetch havev an abort mechanisms, the AbortSignal
According to the documentation there is the webFetchExtra parameter which accept a signal.
But there doesn't seem to be an equivalent for native targets. Is this by design or an oversight?
I usually abort requests in React's useEffect to avoid the "Can't perform a React state update on an unmounted component" error. For example:
useEffect(() => {
  const abortController = new AbortController()
  fetch(url, { signal: abortController.signal })
    .then(data => {
      setState(data)
    })
  return abortController.abort
}, [])

Describe the solution you'd like
For the native targets to support the signal parameter, which would accept an AbortSignal instance such as on the web.
Or for Http.request (get, post, etc) to return both the response's Promise and a cancel method.
Describe alternatives you've considered
Implementing abort on top of Http by wrapping the Http promise in an other Promise which reject whenever the signal emit the abort event

I left a PR (#193) trying to solve this. It's actually a little complicated 😅, since we need to track down the abortable requests and close their respective sockets. Currently, it's not working on iOS, though.


nest.flatten() does not work with list

System information
== cat /etc/issue ===============================================
Linux mews3153 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
VERSION_ID="8"
VERSION="8 (jessie)"
== are we in docker =============================================
No
== compiler =====================================================
c++ (Debian 4.9.2-10) 4.9.2
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
== uname -a =====================================================
Linux mews3153 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
== check pips ===================================================
numpy (1.13.1)
protobuf (3.4.0)
tensorflow (1.3.0)
tensorflow-tensorboard (0.1.5)
== check for virtualenv =========================================
True
== tensorflow import ============================================
tf.VERSION = 1.3.0
tf.GIT_VERSION = v1.3.0-rc2-20-g0787eee
tf.COMPILER_VERSION = v1.3.0-rc2-20-g0787eee
Sanity check: array([1], dtype=int32)
== env ==========================================================
LD_LIBRARY_PATH /usr/lib/libipp-intel:/opt/boost/lib/:/usr/lib64/:/mobileye/shared/boost-python2.7/lib
DYLD_LIBRARY_PATH is unset
== nvidia-smi ===================================================
/tmp/tf_env_collect.sh: line 105: nvidia-smi: command not found
== cuda libs  ===================================================
Describe the problem
The function tensorflow.contrib.data.python.util.nest.flatten fails to flatten a list. Given a flat list, it returns a nested list. This causes a problem in dataset_ops.py, when the datasource is created by zipping several datasources and then attempting to create an iterator.
Source code / logs
Example 1:
from tensorflow.contrib.data.python.util import nest
nest.flatten([1,2,3,4])

[[1, 2, 3, 4]]

nest.flatten((1,2,3,4)) # works with a tuple

[1, 2, 3, 4]

Example 2:
import tensorflow as tf
dataset1 = tf.contrib.data.Dataset.from_tensor_slices(tf.random_uniform([4, 10]))
dataset2 = tf.contrib.data.Dataset.from_tensor_slices(tf.random_uniform([4]))
dataset3 = tf.contrib.data.Dataset.zip([dataset1, dataset2])
iterator = dataset3.make_initializable_iterator()
sess = tf.InteractiveSession()
sess.run(iterator.initializer)
next1, next2 = iterator.get_next()

running the above code:
Traceback (most recent call last):
File "/tmp/tds.py", line 7, in
iterator = dataset3.make_initializable_iterator()
File "/homes/elyassaf/venv/local/lib/python2.7/site-packages/tensorflow/contrib/data/python/ops/dataset_ops.py", line 464, in make_initializable_iterator
return Iterator.from_dataset(self, shared_name)
File "/homes/elyassaf/venv/local/lib/python2.7/site-packages/tensorflow/contrib/data/python/ops/dataset_ops.py", line 97, in from_dataset
output_types=nest.flatten(dataset.output_types),
File "/homes/elyassaf/venv/local/lib/python2.7/site-packages/tensorflow/contrib/data/python/ops/dataset_ops.py", line 1199, in output_types
ds.output_types for ds in nest.flatten(self._datasets)
AttributeError: 'list' object has no attribute 'output_types'

In tensorflow.contrib.data.python.util,  list is not treated as a sequence:
https://github.com/tensorflow/tensorflow/blob/64e54423bbffa4161ba2d85dc913e1973ae52cc6/tensorflow/contrib/data/python/util/nest.py#L103-L110
I don't know enough history about this part though in your sample above I think you could change list to dict, e.g.,
>>> from tensorflow.contrib.data.python.util import nest
>>> nest.flatten((1,2,3,4))
[1, 2, 3, 4]
>>>

/cc @mrry

Closing for now since this seems to be working as intended but please reopen if you think there's an issue.


Measure contract symbolic coverage

Closes: https://github.com/runtimeverification/kontrol/issues/6
TODO

[x] Grab a KCFG a property test
[x] scan for nodes that call into any external contract ( look for CALL* opcodes)
[x] make #call, #callWithCode and #mkCall as cut rules.
[x] group them by the bytecode of the contract that they are calling
[x] for each function call, grab the path conditions for the symbolic arguments from the leaf of the subterm
[x] Union of all those contraints => results in the set of the set of executed paths for a test
[x] Negated set => paths that were not executed
[x] Simplify the set
[ ] Ask a counter example to the prover

Please do a few things:

Back out the changes to the K submodule.
Back out the changes to the pyk version.
Add a test to the Makefile called test-foundry-coverage. It should run the foundry-coverage --contract ..., and output to a file, then compare it to the expected file in the repository. You can see how test-foundry-kcfg-diff test works to understand how to make it easy to update the results for example.

It looks like the code quality checks are failing, which you can run by just going into kevm-pyk subdirectory and calling make.
Also, I don't see a test added of the coverage itself, which checks that the output on a given contract is what's expected.

The tests need to be moved to the new testing harness at kevm-pyk/src/tests/integration/test-data instead of in the tests/foundry directory.

I am closing this for now. To be reopened in kontrol.


No documentation for connection_name parameter

The connection_name parameter to client-properties allows you to set a human-readable connection name to be displayed in the RabbitMQ admin interface:

However, the only place this is mention is in the release notes for 3.6.2, making it hard to search for:
https://github.com/rabbitmq/rabbitmq-server/issues/104

This is not true.

It's not obvious where it would be most discoverable since users of different languages and libraries will look at different tutorials, doc guides and so on. I will add it to the general Connections guide but it's rarely the place of choice for beginners.
API references of several clients mention various functions. Perhaps certain sections of the logging guide can link to it as well because this value will also be used in the connection lifecycle log messages, if set.

Thanks a lot @michaelklishin!
I did not find that section even after a long time searching online and in this repo, probably because it doesn't mention the string connection_name explicitly. But now I know, and can search for this Github issue in the future (when I invariably forget)!

This feature is called "user-provided connection name" by our team. In order to search for "connection_name" you must know about it already one way or another.

Yes, I heard about it one way or the other, but what was difficult was knowing exactly what parameter name to forward into RabbitMQ from our client library (we use py-amqp, which just surfaces a "client_properties" parameter that I guess gets sent into RabbitMQ mostly unaltered).

Perhaps someone could contribute a more prominent way of setting it for a connection to py-amqp :)


multiscale graphs

please point @shangsiwang to a folder with TRT data including all ~24 different atlases,
and tell him the number of ROIs per atlas.
@willgray

did this happen?  I didn't see the email.  @gkiar

We hadn't yet generated multigraphs on all datasets with ndmg, so I am working on getting the data before I send this email. It will be done this week.

great thanks!

I emailed this data and put a public link here.

@willgray - closed right? re-open if not.


Transactional example not working on latest version

Transactional example seems not to be working on the latest  v0.6.14 release
When downgrading to v0.6.0 it works

Hi there,
I just created a topic test and ran go run . in the examples directory on v0.6.14, and it works from me.
What's the output when you add kgo.WithLogger(kgo.BasicLogger(os.Stderr, LogLevelDebug, nil)) to the options passed to both invocations of NewClient?

Hi @twmb , I think I got the problem.
In fact it's running.
What happened is that my kafka brokers was not auto creating the topics (kafka 2.7.0) and with the v0.6.14 the error was not raised, while with the v0.6.0 the exception was clear, than I manually created the topic and all worked. So at the end was the error explanation from the previous version that got it working, and not a problem with the lastest one :)
With latest version the error was not explicit

With  version 6.0.0 the error is explicit

Anyway, thanks for the fast response.

Adding the logger made  it clear on the latest version

Ah yep cool, so v0.6.0 actually had a bug that never retried if discovering the topic failed -- I recently fixed that, which means that when the topic does not exist, the client now retries (refresh metadata, does it exist? no, retry, and so on). The default retries is unlimited, so this would look like the client has hung / is not working.
Glad it's fixed! :)


feat: add vite-plugin-react-pages

getting an error locally when running pnpm test vite-plugin-react-pages
packages/react-pages prepare: [build-*node-types] src/node/static-site-generation/index.ts(81,5): error TS2322: Type 'import("/home/dominikg/develop/vitejs/vite-ecosystem-ci/workspace/vite-plugin-react-pages/vite-plugin-react-pages/node_modules/.pnpm/rollup@3.7.0/node_modules/rollup/dist/rollup").RollupOutput' is not assignable to type 'import("/home/dominikg/develop/vitejs/vite-ecosystem-ci/workspace/vite-plugin-react-pages/vite-plugin-react-pages/node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/rollup").RollupOutput'.
packages/react-pages prepare: [build-*node-types]   Type at position 0 in source is not compatible with type at position 0 in target.
packages/react-pages prepare: [build-*node-types]     The types of 'output.map' are incompatible between these types.
packages/react-pages prepare: [build-*node-types]       Type 'SourceMap | null' is not assignable to type 'SourceMap | undefined'.
packages/react-pages prepare: [build-*node-types]         Type 'null' is not assignable to type 'SourceMap | undefined'.
packages/react-pages prepare: [build-*node-types] npm run build-node-types exited with code 2
packages/react-pages prepare: Failed

something is using rollup 2.7.9, should be rollup@3

something is using rollup 2.7.9, should be rollup@3

Fixed. Could you try it again?

@cijiugechu @csr632   it passed: https://github.com/vitejs/vite-ecosystem-ci/actions/runs/3787397967
is it expected that there are 3 slow tests?

Thanks! Yes, those tests are expected to be slow. I will tweak some config to prevent the warning.

Fixed. Could you try again?


No mention of winmain

winmain is one of the most well known variations to the standard and should be called out in some form.

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

ID: d8bcbd9c-deb2-5a1a-d78b-ed4fc551bcc5
Version Independent ID: 8c3ae6e2-9bd6-bbf4-d80b-a69576a84f8e
Content: Arguments to main
Content Source: docs/c-language/arguments-to-main.md
Product: visual-cpp
Technology: cpp-c-language
GitHub Login: @corob-msft
Microsoft Alias: corob

@henke37
Interesting idea, but this isn't the right place for a discussion of winmain, as this topic is about the standard language.


Replace simplify_bed.rb with bedtools merge

Maybe faster? Does seem to not sort bed entries though so not clear

Added in development DSL2 version


Feature request. Add an option to GZIP service-worker.js file.

The issue I'm experiencing is pretty annoying.
I'm trying to optimize my first byte, by turning off compression, and gziping everything by webpack with CompressionPlugin. The issue is that it doesn't compress service-worker.js produced by sw-precache-webpack-plugin.
I understand the reason why: service-worker.js should cache all chunks produced by webpack after CompressionPlugin compression.
This is why I think it should be an option in sw-precache-webpack-plugin itself.
Thank you)

+1

Any new?

Happy to take a PR for this :)

Is there a workaround ?