Plasma6 system monitor fails to load sensors

Describe the bug
When starting the system monitor app, no sensors are loaded
Steps To Reproduce
Steps to reproduce the behavior:

Enable plasma through services.desktopManager.plasma6.enable = true; and services.xserver.displayManager.defaultSession = "plasma";
Start plasma-systemmonitor

Expected behavior
The system monitor app loads with all its sensors
Screenshots

Additional context
Tested on a new user on the same system, same result
[user@system:~]$ plasma-systemmonitor
qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
kf.package: Path traversal attempt detected: "/nix/store/0xqr3234s5c5fn81krwa7xbw4larmdpa-libksysguard-6.0.2/share/ksysguard/sensorfaces/org.kde.ksysguard.linechart/contents/faceproperties" is not inside "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.linechart/"
kf.package: Could not find required file "FaceProperties" for package "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.linechart/" should be QList("faceproperties")
qrc:/qt/qml/org/kde/ksysguard/page/PageContents.qml:273: TypeError: Value is null and could not be converted to an object
kf.package: Path traversal attempt detected: "/nix/store/0xqr3234s5c5fn81krwa7xbw4larmdpa-libksysguard-6.0.2/share/ksysguard/sensorfaces/org.kde.ksysguard.linechart/contents/faceproperties" is not inside "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.linechart/"
kf.package: Could not find required file "FaceProperties" for package "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.linechart/" should be QList("faceproperties")
qrc:/qt/qml/org/kde/ksysguard/page/PageContents.qml:273: TypeError: Value is null and could not be converted to an object
kf.package: Path traversal attempt detected: "/nix/store/0xqr3234s5c5fn81krwa7xbw4larmdpa-libksysguard-6.0.2/share/ksysguard/sensorfaces/org.kde.ksysguard.linechart/contents/faceproperties" is not inside "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.linechart/"
kf.package: Could not find required file "FaceProperties" for package "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.linechart/" should be QList("faceproperties")
qrc:/qt/qml/org/kde/ksysguard/page/PageContents.qml:273: TypeError: Value is null and could not be converted to an object
qrc:/qt/qml/org/kde/ksysguard/page/EditablePage.qml?page=history.page:223:9: QML Loader: Binding loop detected for property "height"
file:///nix/store/dxb6rwq951n1ajlsvmgb5ivaqcpy203z-kirigami-6.0.0/lib/qt-6/qml/org/kde/kirigami/Dialog.qml:334:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth"
file:///nix/store/dxb6rwq951n1ajlsvmgb5ivaqcpy203z-kirigami-6.0.0/lib/qt-6/qml/org/kde/kirigami/Dialog.qml:386:33: QML Binding: Binding loop detected for property "target"
kf.package: Path traversal attempt detected: "/nix/store/0xqr3234s5c5fn81krwa7xbw4larmdpa-libksysguard-6.0.2/share/ksysguard/sensorfaces/org.kde.ksysguard.textonly/contents/faceproperties" is not inside "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.textonly/"
kf.package: Could not find required file "FaceProperties" for package "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.textonly/" should be QList("faceproperties")
org.kde.ksysguard.plugin.network: Helper process terminated abnormally: "The process doesn't have permission to open the capture source"
qrc:/qt/qml/org/kde/ksysguard/page/PageContents.qml:273: TypeError: Value is null and could not be converted to an object
kf.package: Path traversal attempt detected: "/nix/store/0xqr3234s5c5fn81krwa7xbw4larmdpa-libksysguard-6.0.2/share/ksysguard/sensorfaces/org.kde.ksysguard.textonly/contents/faceproperties" is not inside "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.textonly/"
kf.package: Could not find required file "FaceProperties" for package "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.textonly/" should be QList("faceproperties")
qrc:/qt/qml/org/kde/ksysguard/page/PageContents.qml:273: TypeError: Value is null and could not be converted to an object
kf.package: Path traversal attempt detected: "/nix/store/0xqr3234s5c5fn81krwa7xbw4larmdpa-libksysguard-6.0.2/share/ksysguard/sensorfaces/org.kde.ksysguard.textonly/contents/faceproperties" is not inside "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.textonly/"
kf.package: Could not find required file "FaceProperties" for package "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.textonly/" should be QList("faceproperties")
qrc:/qt/qml/org/kde/ksysguard/page/PageContents.qml:273: TypeError: Value is null and could not be converted to an object
kf.package: Path traversal attempt detected: "/nix/store/0xqr3234s5c5fn81krwa7xbw4larmdpa-libksysguard-6.0.2/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/contents/faceproperties" is not inside "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/"
kf.package: Could not find required file "FaceProperties" for package "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/" should be QList("faceproperties")
qrc:/qt/qml/org/kde/ksysguard/page/PageContents.qml:273: TypeError: Value is null and could not be converted to an object
kf.package: Path traversal attempt detected: "/nix/store/0xqr3234s5c5fn81krwa7xbw4larmdpa-libksysguard-6.0.2/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/contents/faceproperties" is not inside "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/"
kf.package: Could not find required file "FaceProperties" for package "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/" should be QList("faceproperties")
qrc:/qt/qml/org/kde/ksysguard/page/PageContents.qml:273: TypeError: Value is null and could not be converted to an object
kf.package: Path traversal attempt detected: "/nix/store/0xqr3234s5c5fn81krwa7xbw4larmdpa-libksysguard-6.0.2/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/contents/faceproperties" is not inside "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/"
kf.package: Could not find required file "FaceProperties" for package "/nix/store/6rd9pz13dl1jq4nggjcjn1qq66wc6cs9-system-path/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/" should be QList("faceproperties")
qrc:/qt/qml/org/kde/ksysguard/page/PageContents.qml:273: TypeError: Value is null and could not be converted to an object

Notify maintainers
@ilya-fedin
@K900
@LunNova
@mjm
@NickCao
@SuperSandro2000
@ttuegel

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
these 6 paths will be fetched (0.75 MiB download, 10.20 MiB unpacked):
  /nix/store/pqraddz55s3qlsjxs71zwjchj0c4csfw-file-5.45
  /nix/store/27g0inj79hpzaw31kqshbv5v9caz3qac-gnu-config-2023-09-19
  /nix/store/3wwka0sn2h96cmqxyclj2vba26a5sk1s-gnumake-4.4.1
  /nix/store/3125ahv429pk8sxnfhj5l3f2ph7jllrk-patchelf-0.15.0
  /nix/store/v099hqvw5z87423p4hz1vfhzaqa07dii-stdenv-linux
  /nix/store/zfgzsn57hhv547x3qmxgpf9y8a320mjr-update-autotools-gnu-config-scripts-hook
copying path '/nix/store/27g0inj79hpzaw31kqshbv5v9caz3qac-gnu-config-2023-09-19' from 'https://cache.nixos.org'...
copying path '/nix/store/pqraddz55s3qlsjxs71zwjchj0c4csfw-file-5.45' from 'https://cache.nixos.org'...
copying path '/nix/store/3wwka0sn2h96cmqxyclj2vba26a5sk1s-gnumake-4.4.1' from 'https://cache.nixos.org'...
copying path '/nix/store/3125ahv429pk8sxnfhj5l3f2ph7jllrk-patchelf-0.15.0' from 'https://cache.nixos.org'...
copying path '/nix/store/zfgzsn57hhv547x3qmxgpf9y8a320mjr-update-autotools-gnu-config-scripts-hook' from 'https://cache.nixos.org'...
copying path '/nix/store/v099hqvw5z87423p4hz1vfhzaqa07dii-stdenv-linux' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 6.8.1, NixOS, 24.05 (Uakari), 24.05.20240319.b06025f`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/store/zaza7mgggz4m5h6z18kajabf4wciaj47-source`

Add a :+1: reaction to issues you find important.

Yeah, that's something I noticed myself. The system monitor widget doesn't seem to work on my panel, too...

Hmm. Everything working fine for me.

Same here. Would appreciate if someone that can reproduce the issue can look into it. It might be something about some specific sensor on specific hardware...

I have no idea what changed but an update seems to have fixed this issue


Release v1.1.6

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.
Here's what I've got...
For recipe/meta.yaml:

❌ requirements: run: scipy >= 1.11.3 should not contain a space between relational operator and the version, i.e. scipy >=1.11.3

For recipe/meta.yaml:

ℹ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

ℹ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub actions workflow below for more details. You can also ping conda-forge/core for further assistance or you can try rerendering locally.
The following suggestions might help debug any issues:

Is the recipe/{meta.yaml,recipe.yaml} file valid?
If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnnings.
Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11865802022.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

ℹ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I got 'python_min' is undefined in symfc-feedstock build although following advice by conda-forge-linting service. So it was manually set as follows:
{% set python_min = "3.9" %}

https://github.com/conda-forge/cfep/blob/main/cfep-25.md
https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/679ebe3fe70e4ced11da3f5626ab715f608481fd/recipe/conda_build_config.yaml#L791


Oidc behavior when only authorization is needed

Description
Fixes the OIDC behavior when requests arrive with valid tokens that were created through another
party and not as part of the local negotiation. Likely to happen in scenarios with a load balancer.
Modifies the format of the JWT tokens to rely on the subject for source identification rather than customer headers.
Allows JWT tokens to provide a Data section.

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "jwt-updates",
    "component": "enforcerd",
    "pr-id": "1072",
    "commit-sha": "68f2b4fa32a2419238f332de8e2ebff2e85c5345"
  },
  {
    "project": "jwt-updates",
    "component": "trireme-lib",
    "pr-id": "754",
    "commit-sha": "acb9fd77a62d5d83bd74e268b941330cb9c2378b"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "jwt-updates",
    "component": "enforcerd",
    "pr-id": "1072",
    "commit-sha": "68f2b4fa32a2419238f332de8e2ebff2e85c5345"
  },
  {
    "project": "jwt-updates",
    "component": "trireme-lib",
    "pr-id": "754",
    "commit-sha": "2af76b7623b6ea4a4ae3e2b4ffa4ee5a65211538"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "jwt-updates",
    "component": "enforcerd",
    "pr-id": "1072",
    "commit-sha": "68f2b4fa32a2419238f332de8e2ebff2e85c5345"
  },
  {
    "project": "jwt-updates",
    "component": "trireme-lib",
    "pr-id": "754",
    "commit-sha": "1257efd854a3d9b39294ef69f199e2538e0b152c"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "jwt-updates",
    "component": "enforcerd",
    "pr-id": "1072",
    "commit-sha": "68f2b4fa32a2419238f332de8e2ebff2e85c5345"
  },
  {
    "project": "jwt-updates",
    "component": "trireme-lib",
    "pr-id": "754",
    "commit-sha": "1257efd854a3d9b39294ef69f199e2538e0b152c"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "jwt-updates",
    "component": "enforcerd",
    "pr-id": "1072",
    "commit-sha": "d7d5d323ac66d1ca0fa14b369c13ec05b3bba1af"
  },
  {
    "project": "jwt-updates",
    "component": "trireme-lib",
    "pr-id": "754",
    "commit-sha": "1257efd854a3d9b39294ef69f199e2538e0b152c"
  }
]


Getting gas required exceeds allowance while using forge create

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (200b3f4 2023-05-05T00:04:08.284562894Z)
What command(s) is the bug in?
forge create
Operating System
Linux
Describe the bug
I am using below command:
forge create ./src/SimpleERC.sol:SimpleERC --rpc-url 'https://eth-goerli.g.alchemy.com/v2/'${ALCHEMY_ETH_GOERLI} --private-key ${PRIVATE_KEY} --force --constructor-args "SimpleERC" "SERC"

with the simplest possible contract for ERC20 token like below:
// SPDX-License-Identifier: UNLICENSED
pragma solidity 0.8.18;

import<EMAIL_ADDRESS>
contract SimpleERC is ERC20 {
    constructor() ERC20("SimpleERC", "SERC") {
        _mint(msg.sender, 100 * 10 ** decimals());
    }
}

So I believe this is not related to small amount of ETH on wallet. What it could be?

Hi! Thanks for reporting this.
I think our gas estimation might still be off @mattsse — investigating.


Impro 1720 remove weighting code top nbhood

Removed  CollapseMaskedNeighbourhoodCoordinate plugin, by moving functionality to collapse weights into the ApplyNeighbourhoodProcessingWithAMask plugin.
Wrote new unit tests for the collapse and process function of the ApplyNeighbourhoodProcessingWithAMask plugin.
Updated docstrings.

Further refactoring of the land-sea CLI and plugins in calls is discussed on the ticket with the aim of avoiding future confusion.
Testing:

[ ] Ran tests and they passed OK
[ ] Added new tests for the new feature(s)

 Here is an overview of what got changed by this pull request:

Complexity decreasing per file
==============================
+ improver_tests/nbhood/use_nbhood/test_ApplyNeighbourhoodProcessingWithAMask.py  -2
+ improver/nbhood/use_nbhood.py  -1

Clones added
============
- improver_tests/nbhood/use_nbhood/test_ApplyNeighbourhoodProcessingWithAMask.py  2

See the complete overview on Codacy

On the command line I was getting a couple of pylint errors, but they don't seem to be occurring in the automated tests on this PR. Maybe something for a reviewer to look out for.
Don't know why sphinx is failing here. It isn't on the command line

 Here is an overview of what got changed by this pull request:

Complexity decreasing per file
==============================
+ improver_tests/nbhood/use_nbhood/test_ApplyNeighbourhoodProcessingWithAMask.py  -2
+ improver/nbhood/use_nbhood.py  -1

Clones added
============
- improver_tests/nbhood/use_nbhood/test_ApplyNeighbourhoodProcessingWithAMask.py  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 1

Complexity decreasing per file
==============================
+ improver_tests/nbhood/use_nbhood/test_ApplyNeighbourhoodProcessingWithAMask.py  -2
+ improver/nbhood/use_nbhood.py  -1

Clones added
============
- improver_tests/nbhood/use_nbhood/test_ApplyNeighbourhoodProcessingWithAMask.py  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity decreasing per file
==============================
+ improver_tests/nbhood/use_nbhood/test_ApplyNeighbourhoodProcessingWithAMask.py  -2
+ improver/nbhood/use_nbhood.py  -1

Clones added
============
- improver_tests/nbhood/use_nbhood/test_ApplyNeighbourhoodProcessingWithAMask.py  2

See the complete overview on Codacy

@TomekTrzeciak  and @gavinevans I think I've responded to all your requested changes.


Asks for login every time I do something on backstage2

I am using the mbassan fork. Every time I click on something on backstage2, it asks me to login again before completing the action. Usually this is ok, but the problem is that I can't submit anything on app configuration, etc, because form data is not preserved.

The frontend and backstage have conflicting sessions. Open them in
different browsers.
This will not be a problem in a production environment where those
components are on different servers.
On Jan 18, 2017 7:07 PM, "Mark Polyakov"<EMAIL_ADDRESS>wrote:

I am using the mbassan fork. Every time I click on something on
backstage2, it asks me to login again before completing the action. Usually
this is ok, but the problem is that I can't submit anything on app
configuration, etc, because form data is not preserved.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/wlox/wlox/issues/81, or mute the thread
https://github.com/notifications/unsubscribe-auth/AF1VdTTPMU-7bpgqGvV0OO4vnkAcj7TBks5rTqlYgaJpZM4LnjHU
.

Ok, thank you. Clearing the cookies helps.

You're welcome. Remember to open them in different browsers.
On Jan 18, 2017 9:16 PM, "Mark Polyakov"<EMAIL_ADDRESS>wrote:

Ok, thank you. Clearing the cookies helps.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/wlox/wlox/issues/81#issuecomment-273662919, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF1VddXs0HIcsZ7L0D9sGVqrf0RE2Ltmks5rTsdlgaJpZM4LnjHU
.


TypeError: unsupported operand type(s) for &: 'int' and 'str'

╭─ ~ ‹system›
╰─$ cat ~/.notification.yaml                                                                          1 ↵
layout:
  anchor: top_right
  margin: 25
╭─ ~ ‹system›
╰─$ notification-thing --debug --conf ~/.notification.yaml --test-message
DEBUG:notification_thing.display:Creating window with parameters: {'body': 'Desktop notification daemon started successfully on host: delogo\nVersion: 16.10.7\nCode path: /usr/lib/python2.7/site-packages/notification_thing\nSound enabled: true\nPubSub enabled: false', 'markup': 'True', 'summary': 'Notification daemon started <tt>\xc2\xaf\\(\xc2\xb0_o)/\xc2\xaf</tt>', 'urgency': 'critical', 'icon': 'None'}
DEBUG:daemon:Created notification (id: 1, timeout: 5000.0 (ms))
DEBUG:daemon:Starting gobject loop
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/notification_thing/display.py", line 404, in <lambda>
    win.gobj.connect('configure-event', lambda w,void: self._update_layout())
  File "/usr/lib/python2.7/site-packages/notification_thing/display.py", line 181, in _update_layout
    if 2**ax & self.layout_anchor else self.margins[-2**ax], xrange(2) ))
  File "/usr/lib/python2.7/site-packages/notification_thing/display.py", line 181, in <lambda>
    if 2**ax & self.layout_anchor else self.margins[-2**ax], xrange(2) ))
TypeError: unsupported operand type(s) for &: 'int' and 'str'
╭─ ~ ‹system›
╰─$ notification-thing --debug --conf ~/.notification.yaml --test-message --layout-anchor top_right   1 ↵
DEBUG:notification_thing.display:Creating window with parameters: {'body': 'Desktop notification daemon started successfully on host: delogo\nVersion: 16.10.7\nCode path: /usr/lib/python2.7/site-packages/notification_thing\nSound enabled: true\nPubSub enabled: false', 'markup': 'True', 'summary': 'Notification daemon started <tt>\xc2\xaf\\(\xc2\xb0_o)/\xc2\xaf</tt>', 'urgency': 'critical', 'icon': 'None'}

specifying layout.anchor in the configuration file fails with the error above. Passing it via the CLI works as expected.

Hm, looks like duplicate with last comment in #4, and should be fixed in current git, right?
A bit puzzled as to why it seem to be opened after #4 was closed then, maybe some automation magic at work...

Nope, not fixed. Try yourself :)

Sorry, for being sloppy in our conversation. I'm not giving this the required time.
Yeah I was wrong in the other ticket.
Try with latest git, and the configuration as shown in the description of this ticket.

Hm, weird, seem to be second issue I fail to reproduce:
 # fraggod@maled~:-..ication-thing% git ls -1
commit af309d2b5876ee73b938304b357baff92ed55dc9 (HEAD -> master, fg_core/master)
Author: Mike Kazantsev<EMAIL_ADDRESS>Date:   Tue Nov 1 20:26:53 2016 +0500

    cli: fix parsing --layout-* enum values

 notification_thing/__init__.py |  2 +-
 notification_thing/daemon.py   | 26 ++++++++++----------------
 2 files changed, 11 insertions(+), 17 deletions(-)

 # fraggod@maled~:-..ication-thing% cat test.yaml
layout:
  anchor: top_right
  margin: 25

 # fraggod@maled~:-..ication-thing% ./notification-thing --debug --conf test.yaml --test-message
DEBUG:notification_thing.display:Creating window with parameters: {'body': 'Desktop notification daemon started successfully on host: malediction\nVersion: 16.11.0\nCode path: /home/fraggod/hatch/notification-thing/notification_thing\nSound enabled: true\nPubSub enabled: false', 'markup': 'True', 'summary': 'Notification daemon started <tt>\xc2\xaf\\(\xc2\xb0_o)/\xc2\xaf</tt>', 'urgency': 'critical', 'icon': 'None'}
DEBUG:daemon:Created notification (id: 1, timeout: 5000.0 (ms))
DEBUG:daemon:Starting gobject loop
DEBUG:daemon:Closing notification(s) (id: 1, reason: expired)
DEBUG:daemon:Closing notification(s) (id: 1, reason: dismissed)
DEBUG:daemon:NotificationClosed signal (id: 1, reason: expired)
^CTraceback (most recent call last):
  File "./notification-thing", line 782, in <module>
    if __name__ == '__main__': sys.exit(main())
  File "./notification-thing", line 779, in main
    loop.run()
  File "/usr/lib/python2.7/site-packages/gi/overrides/GLib.py", line 576, in run
    raise KeyboardInterrupt
KeyboardInterrupt

 # fraggod@maled~:-..ication-thing% ./notification-thing --debug --conf test.yaml --test-message --layout-anchor top_right
DEBUG:notification_thing.display:Creating window with parameters: {'body': 'Desktop notification daemon started successfully on host: malediction\nVersion: 16.11.0\nCode path: /home/fraggod/hatch/notification-thing/notification_thing\nSound enabled: true\nPubSub enabled: false', 'markup': 'True', 'summary': 'Notification daemon started <tt>\xc2\xaf\\(\xc2\xb0_o)/\xc2\xaf</tt>', 'urgency': 'critical', 'icon': 'None'}
DEBUG:daemon:Created notification (id: 1, timeout: 5000.0 (ms))
DEBUG:daemon:Starting gobject loop
DEBUG:daemon:Closing notification(s) (id: 1, reason: expired)
DEBUG:daemon:Closing notification(s) (id: 1, reason: dismissed)
DEBUG:daemon:NotificationClosed signal (id: 1, reason: expired)
^CTraceback (most recent call last):
  File "./notification-thing", line 782, in <module>
    if __name__ == '__main__': sys.exit(main())
  File "./notification-thing", line 779, in main
    loop.run()
  File "/usr/lib/python2.7/site-packages/gi/overrides/GLib.py", line 576, in run
    raise KeyboardInterrupt
KeyboardInterrupt

http://fraggod.net/tmp/shot-2016-11-01_22-30-02.jpg
http://fraggod.net/tmp/shot-2016-11-01_22-30-36.jpg
Maybe double-check that you're running latest code, i.e. git pulls stuff in and such (though honestly have no clue why it wouldn't with pkgbuild)...
Just seem to be exact issue that should be fixed (and I was able to reproduce easily) in the latest commit.

Also, realized that that --test-message does the right thing and prints version (which I put in there for exactly this reason), and yours has Version: 16.10.7\n in it, while it should be Version: 16.11.0\n (same as mine).

16.10.7 seem to be from before both fixes in #4, so should have all the problems you've mentioned there.

One thing that came to mind wrt why you might be running older code in the first comment/snippet is because unlike earlier, you seem to not be in git repo dir, like you were previously, i.e. CWD is ~ here:
╭─ ~ ‹system›
╰─$ notification-thing --debug --conf ~/.notification.yaml --test-message

And ~/Documents/dev/aur/notification-thing-git in this snippet from #4:
╭─ ~/Documents/dev/aur/notification-thing-git ‹system› ‹master*›
╰─$ notify-send test

Latter makes import notification_thing in python import stuff from current dir, while former will use /usr/lib/pythonX.Y/site-packages.
If you run ./notification-thing or ./notification_thing/daemon.py directly (i.e. as __main__ py module), it also has a bit of code to make sure it always runs from checkout, not any site-packages dir, though "cd" into checkout should be enough for that as well.

You're probably right. I'll check again and let you know! Thanks for everything again!
On November 1, 2016 8:16:39 PM GMT+02:00, Mike Kazantsev<EMAIL_ADDRESS>wrote:

One thing that came to mind wrt why you might be running older code in
the first comment/snippet is because unlike earlier, you seem to not be
in git repo dir, like you were previously, i.e. CWD is ~ here:
╭─ ~ ‹system›
╰─$ notification-thing --debug --conf ~/.notification.yaml
--test-message

And ~/Documents/dev/aur/notification-thing-git in this snippet from
#4:
╭─ ~/Documents/dev/aur/notification-thing-git ‹system› ‹master*›
╰─$ notify-send test

Latter makes import notification_thing in python import stuff from
current dir, while former will use /usr/lib/pythonX.Y/site-packages.
If you run ./notification-thing or ./notification_thing/daemon.py
directly (i.e. as __main__ py module), it also has a bit of code to
make sure it always runs from checkout, not any site-packages dir,
though "cd" into checkout should be enough for that as well.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/mk-fg/notification-thing/issues/5#issuecomment-257647835

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Indeed, you're right. I now did run the latest version and it works fine. Thanks again :)


[zh] fix and update feature-gates

FIX #26672

@CaoDonghui123 This is a dup of #26319 which has been created several months ago ...

sorry, I didn't notice that.
I closed

@CaoDonghui123 Maybe you can help review the #26319 PR and see if something is error or missing?


SPIKE for Performance issue with Delivery Status Processing Bug

BACKGROUND
We receive at least two delivery statuses back for every message that goes out.  If a service is configured for a callback, we make a post request to the callback endpoint for each of those delivery statuses that come in.
ISSUE
The service is not processing the delivery statutes fast enough.  As a result, the queue that feeds the task is filled with requests and callbacks arent being made for a significant time after the delivery status was received.
@k-macmillan provided some helpful background on his investigation so far:
We sent an SMS request at 11am and didn't process the delivery status callback until 1pm:
The Delivery status Lambda is receiving delivery statuses and is processing them quickly:

SQS backs up with messages:

From the logs, there doesn't seem to be any exceptions or errors being thrown by the service, celery task, or sqs that would explain the issue.
Acceptance Criteria

[ ] Discover possible root causes of the delay
[ ] Attempt to narrow it down to the most likely candidates
[ ] Create a follow-on ticket to attempt to fix the issue based on the most likely causes

Out of Scope
Implementing a fix

Updated to high priority as it was determined to be urgent to investigate the cause. Timeboxed to a 3.

Right now, investigating celery-sqs relationship as the culprit.

The Lambda is handling the load and offloading to the queue fine.
There are no cloudwatch logs with the queue itself so doesn't look like any failures on the queue
there are no permissions issues with the celery role and sqs that would cause a back off
there are no issues from code in the task

The average time between sending of an SMS and receiving the first delivery status is about 10 seconds to get a sent and about 10-20 more seconds to get a delivered status (loosely measured by using timestamps of when I click on a postman send button and the timestamp of receipt of the first delivery status in pipedream).
My current theory is that the combination of polling with how many items are dequeued during polling is leading to a natural backup of messages in the queue.  I was looking in the celery documentation for modifying batch size and didn't find it yet.  I read about CELERY_WORKER_PREFETCH_MULTIPLIER value but I'm not sure we can use that considering the container does multiple things and it may exhaust resources for delivery statuses.
What I'm going to look at tomorrow is:

confirm the batch size of the dequeue of celery from sqs
figure out how many twilio sms messages were sent over the course of a day
use that number to determine a baseline number for how many delivery statuses we would've received
calculate how long it would take celery with a polling interval of 1 to drain the queue.

I have not confirmed my theory but I am more confident in it.
As expected peaks and valleys of SMS send delivery receipt follow one another.  I believe that workers are being tied up with SMS sends and while those sends are happening, 2x delivery receipts are coming into the queue.
The delivery receipts queue doesn't get drained quickly because most of the available workers are working on sending SMS.  This leads to the peak.  When the SMS sends are complete, celery starts draining the delivery -receipts SQS.
Celery dequeues 4 messages (this is the default since we don't set it explicitly) per worker process at a time.  This is the valley for the queue.
So everything is actually working the way it should.  I'm not entirely sure we need to change anything right now because we could get these statuses up to 3 days later anyway, so I don't think that anybody waiting for a callback is expecting them urgently.
However, if we decide to change this, then the options are:

Create a new service that has the responsibility of handling callbacks/webhooks.  If the service is dedicated to these tasks then they'll happen quicker.
Create a lambda that handles processing delivery status callbacks.  We could disconnect celery from the queue and use the queue to trigger the lambda to handle the callback.  The small downside of this is that we'd have to build in stuff for statsd that I don't think exists currently in our other lambdas.

FYI: The metrics I really wanted to get were what worker is working on what task at any particular time.  We don't have that insight right now and I think that should be something we build in to DataDog so that we can troubleshoot these kinds of issues in the future.  As the system grows in functionality and the services handle more tasks, it will be really important.  I can get with @ldraney and @k-macmillan to discuss this further.

@jakehova Can you please update the acceptance criteria checklist and provide the link to the new ticket please?


Super Complex and not Working

[Enter feedback here]

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

ID: 520b9821-ecef-20af-a601-ea36c4297d88
Version Independent ID: da9c8ac9-4d7a-4b40-56a2-a4bfe7083567
Content: Secure an ASP.NET Core Blazor WebAssembly hosted app with Azure Active Directory B2C
Content Source: aspnetcore/blazor/security/webassembly/hosted-with-azure-active-directory-b2c.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

I have tried this 3 times and still not able to get it to work. Doing so much to enable signing up/in is really a killer and scare many developers away. I use Google Firebase most of the time and setting it up is much much easier than this. This seems to be over-engineers in not useful

Hello @toorajhelmi ... On the docs side, there isn't anything we can do to make app scenarios (or Azure) less complex outside of improving the guidance generally and covering more gotcha scenarios. Specific feedback is actionable, so feel free to add detail when you discover what the problem is with the app or Azure config.
You can open an issue for the product unit to provide general feedback on the scenario, but they will need something more specific to react to than just 'it's too complex' ... you'll have to explain specifically what you find complex about the scenario ...
https://github.com/dotnet/aspnetcore/issues
WRT 'not working' ... Currently, we don't have any other open issues on problems with the guidance in this node. Given that the cause of the problem is unknown, there isn't much that we can do ... especially right now ... I'm on ⛄ holiday vacation 🎁 for another couple of weeks.
We recommend the usual support channels for product support that we aren't able to offer ...

Stack Overflow (tag: blazor)
ASP.NET Core Slack Team
Blazor Gitter

If you find out the problem, please add a comment back here. If I can improve the doc to cover it in some way, I'll re-open this issue and work on the topic to cover what was causing your app (or Azure config) to fail.

Hi,
Thanks for the response. There are couple of points:

Microsoft is a big enterprise so if one person is on vacation there should other people who provide support in his absence. Telling me you were on vacation for a couple of weeks was fine if I was working with a startup not with Microsoft.
You have closed the issue but rather you should have done two things: first had somebody from your org work with me to find the problem and potentially update this document accordingly and two escalate to responsible azure PMs to find ways to simplify the overall flow. Offering a product which cannot be easily used by customers is worse than provide nothing. I have spent around 30 hours at this point trying to make it work which I would have spent on other important features of my project.
Happy holidays and don’t take this personally but rather an opportunity to improve things at your organization.
Regards,Tooraj

Sent from Yahoo Mail for iPhone
On Sunday, December 27, 2020, 3:10 PM, Luke Latham<EMAIL_ADDRESS>wrote:
Hello @toorajhelmi ... On the docs side, there isn't anything we can do to make app scenarios (or Azure) less complex outside of improving the guidance generally and covering more gotcha scenarios. Specific feedback is actionable, so feel free to add detail when you discover what the problem is with the app or Azure config.
You can open an issue for the product unit to provide general feedback on the scenario, but they will need something more specific to react to than just 'it's too complex' ... you'll have to explain specifically what you find complex about the scenario ...
https://github.com/dotnet/aspnetcore/issues
WRT 'not working' ... Currently, we don't have any other open issues on problems with the guidance in this node. Given that the cause of the problem is unknown, there isn't much that we can do ... especially right now ... I'm on ⛄ holiday vacation 🎁 for another couple of weeks.
We recommend the usual support channels for product support that we aren't able to offer ...

Stack Overflow (tag: blazor)
ASP.NET Core Slack Team
Blazor Gitter

If you find out the problem, please add a comment back here. If I can improve the doc to cover it in some way, I'll re-open this issue and work on the topic to cover what was causing your app (or Azure config) to fail.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Microsoft is a big enterprise so if one person is on vacation there should other people who provide support in his absence. Telling me you were on vacation for a couple of weeks was fine if I was working with a startup not with Microsoft.

There are only about two others here (three really, but two have many responsibilities elsewhere), and they are also out on vacation. There are no active ... non-vacationing 🏖 ... doc authors here right now. Everyone will be back working in a couple of weeks. Notwithstanding our staffing right now, my role is ~95% Blazor docs ... I'm literally THE Blazor docs 🐈 here. I jump in for critical updates and to answer messages, but that's about it right now.

You have closed the issue but rather you should have done two things: first had somebody from your org work with me to find the problem and potentially update this document accordingly and two escalate to responsible azure PMs to find ways to simplify the overall flow. Offering a product which cannot be easily used by customers is worse than provide nothing. I have spent around 30 hours at this point trying to make it work which I would have spent on other important features of my project.

Some of your comments are product feedback, which we don't take here. That's why I gave you the product unit issues link ...
https://github.com/dotnet/aspnetcore/issues
... so you could tell them what you find complex and provide any ideas you have for making the framework less so. That's their responsibility, and they don't monitor issues here. You have to open an issue with them to discuss that aspect.
WRT the guidance failing ...
Often, I do work with devs to narrow the scope of a problem, sometimes just to determine if opening an issue with the product unit is warranted (at the link that I provided).
In this case thus far, you've provided no actionable information ... no errors or specific behaviors ... no notes on tooling in use ... SDK and framework versions ... or anything really. All you've said is 'this is complex' and 'the app doesn't work.' nothing that I can hoep I closed the issue and said that if you add detail and if I can hel


[FLINK-5528][query][tests] reduce the retry delay in QueryableStateITCase

Using 100ms instead of the 1s previously used does not impose too much
additional query load and reduces the test suite's duration from 16-20s to
13-15s on my machine with the current set of unit tests. Further reductions
in the retry delay do not yield more improvements so far.

Good idea! Will merge this with one minor change (see inline comment).


command option

Now every command in little scheme has no options, however, it would be a thing in the near future. We can cut the argument list by break.

Not break, but partition, but this would also close since not must contain.


how to handle RpcException ?

Respected Maintainer
Previously, I thought its support only v5, but thankful to author who corrected me.
I have started using this lib newly.
and I'm stuck while catching WTelegramClient errors.
Currently I'm using following code from documentation to log events.
//little modified
WTelegram.Helpers.Log = ((lvl, str) =>
{
    Console.WriteLine("TDIWE!"[lvl]);
    Console.WriteLine($"str:{str}");
});

It works to output error, like:
D
str:4>Sending   MsgContainer                             2022-07-30 10:42:20Z (svc)
D
str:            → Channels_InviteToChannel               #1EC5
D
str:            → MsgsAck
D
str:4>Receiving RpcResult                                2022-07-30 10:42:20Z
E
str:             → RpcError 400 CHAT_ADMIN_REQUIRED      #1EC5

But that errors closes application. Whats proper to catch and handle it ?
I mean NOT like if (str.contains("400 CHAT_ADMIN_REQUIRED")) 😆
Instead something like we do normally in c#
try
{
    //do_something_faulty_stuff_here();
}
catch(RpcError ex)
{
    if(ex.type == Errors.CHAT_ADMIN_REQUIRED) continue;
}

Like errors code mentioned: https://revgram.github.io/errors.html
Thanks

RpcException not RpcError
try
{
  // some API call
}
catch (RpcException ex) when (ex.Code == 400 && ex.Message == "CHAT_ADMIN_REQUIRED")
{
  // handle error 400 CHAT_ADMIN_REQUIRED here
}


New release with LightGBM 2.2.1

Release 2.2.1 of LightGBM (see Microsoft/LightGBM#1727) allowed running it on older systems (most notably CentOS 7). Could you kindly consider releasing a new version of mmlspark incorporating this change?
Update: corrected the PR link.

@superbobry I think you meant a different link than #727 ?

@superbobry  sure I can work on releasing a newer version but I first need to make sure it would indeed work and I need to figure out how to test it.  If I release it would you be able to test it?

@imatiach-msft thanks, I've updated the link. I will be able to test the release once it's out, yes.
By the way, thank you very much for the superb support! It is very rare to see replies on OSS' issues on the same day, not just within the same hour :)

@superbobry sorry, would you be able to try out this build:
--packages com.microsoft.ml.spark:mmlspark_2.11:0.14.dev9+1.g5783ce91
--repositories https://mmlspark.azureedge.net/maven

you need to specify our build repository since I haven't published it to maven central yet, I want to make sure to verify it first.  Hope it fixes the issue!  If you have trouble, let me know if we could get on a skype call together and debug the issue, I might be able to help.

@imatiach-msft are you sure the artifact is available in the repository?
$ curl https://mmlspark.azureedge.net/maven/Azure/mmlspark_2.11/0.14.dev9+1.g5783ce91/mmlspark_2.11-0.14.dev9+1.g5783ce91.pom
<?xml version="1.0" encoding="utf-8"?><Error>BlobNotFound<Message>The specified blob does not exist.
RequestId:010da925-c01e-0047-2c0d-623285000000
Time:2018-10-12T09:28:28.2599081Z</Message></Error>%

@superbobry
I can see it here: https://mmlspark.azureedge.net/maven/com/microsoft/ml/spark/mmlspark_2.11/0.14.dev9+1.g5783ce91/mmlspark_2.11-0.14.dev9+1.g5783ce91.pom
It's not under Azure, that's for the official maven central release.  This is just for our builds.

Thanks! @alois-bissuel, could you give it a try on Monday?

@alois-bissuel @superbobry please let me know if this resolves the issue or if you run into any other problems

Yes, I am trying it now. The only trouble is that the repo where I pull this custom version (https://mmlspark.azureedge.net/maven/) doesn't have the full dependency (lightGBM.jar at least), so it could streamline our work if it were.

@alois-bissuel could you please explain that a bit more, it should have the dependency based on this in the PR I built:
https://github.com/Azure/mmlspark/pull/391/files#diff-7b450c33e07c4838c2f8f1901b791b77R41
"com.microsoft.ml.lightgbm" %  "lightgbmlib" % "2.2.100"

The dependency is also from a maven repo I created from an Azure blob:
"LightGBM Maven Repo" at "https://azuremlbuild.blob.core.windows.net/maven"

@imatiach-msft : no it is OK, I managed eventually to pull all the dependencies, do not bother to publish to maven central. I will test this tomorrow. Thanks for the quick answer, I will keep you posted !

I just managed to run with the version you provided. There is still a linking error:
java.lang.UnsatisfiedLinkError: /hdfs/uuid/c19321f1-80c9-4338-8a11-30c98f5fcbd4/yarn/data/usercache/XXXX/appcache/application_1539164595645_1548310/container_e293_1539164595645_1548310_01_000588/tmp/mml-natives6180385213394115619/lib_lightgbm.so: /lib64/libstdc++.so.6: version GLIBCXX_3.4.20' not found (required by /hdfs/uuid/c19321f1-80c9-4338-8a11-30c98f5fcbd4/yarn/data/usercache/XXXX/appcache/application_1539164595645_1548310/container_e293_1539164595645_1548310_01_000588/tmp/mml-natives6180385213394115619/lib_lightgbm.so)`
It seems that on CentOS 7 the latest version of GLIBCXX is 3.4.19!  I don't know which version of GLIBCXX was targeted by Microsoft/LightGBM#1727.

@alois-bissuel <2.25, see https://github.com/Microsoft/LightGBM/pull/1718#issuecomment-426244665.

A small update: the error above corresponds to problem linking to libstdc++, as indicated here Microsoft/LightGBM#1708. There are no more linking problems with the libstdc.

Thanks for all this really interesting work and potential users with a spark cluster with centos 7 !
I've tested the new jar and I have the same problem @alois-bissuel
Caused by: java.lang.UnsatisfiedLinkError: /hdfs/hadoop/yarn/local/usercache/livy/appcache/application_1539859181572_0009/container_e51_1539859181572_0009_01_000009/tmp/mml-natives3222353148039997186/lib_lightgbm.so: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found

Did you find a solution to solve this ?

And of course : I can help for some test if required !

It looks like I overcame the linking error by adding to the LD_LIBRARY_PATH a more recent version of libstdc++.so.6 (which I incidentally found in my installation of miniconda, in case somebody asks). At least, ldd lib_lightgbm.so shows no linking problem.
For running with spark, it is simply a matter of using the spark.yarn.dist.files (for the lib) and spark.executor.extraLibraryPath (to add the current working directory to the LD_LIBRARY_PATH of the executors).
I still have errors after (which seem unrelated), so I can't rule out that this fix does not work.

Coming back from the network error in #405 , I now have a bad allocation error.
One again, I added an external libstdc++.so.6 to every executor's LD_LIBRARY_PATH.
See the stacktrace:
java.lang.Exception: Dataset create call failed in LightGBM with error: std::bad_alloc
at com.microsoft.ml.spark.LightGBMUtils$.validate(LightGBMUtils.scala:26)
at com.microsoft.ml.spark.LightGBMUtils$.generateSparseDataset(LightGBMUtils.scala:349)
at com.microsoft.ml.spark.TrainUtils$.translate(TrainUtils.scala:42)
at com.microsoft.ml.spark.TrainUtils$.trainLightGBM(TrainUtils.scala:211)
at com.microsoft.ml.spark.LightGBMClassifier$$anonfun$1.apply(LightGBMClassifier.scala:58)
at com.microsoft.ml.spark.LightGBMClassifier$$anonfun$1.apply(LightGBMClassifier.scala:58)

@alois-bissuel  I wouldn't rule out there being a memory leak in the native code, but I do delete the arrays to create the native lightgbm dataset here for training:
https://github.com/Azure/mmlspark/blob/master/src/lightgbm/src/main/scala/LightGBMUtils.scala#L318
https://github.com/Azure/mmlspark/blob/master/src/lightgbm/src/main/scala/LightGBMUtils.scala#L359
and here for prediction:
https://github.com/Azure/mmlspark/blob/master/src/lightgbm/src/main/scala/LightGBMBooster.scala#L67
https://github.com/Azure/mmlspark/blob/master/src/lightgbm/src/main/scala/LightGBMBooster.scala#L106
here for label col:
https://github.com/Azure/mmlspark/blob/master/src/lightgbm/src/main/scala/TrainUtils.scala#L62
and here to free learner:
https://github.com/Azure/mmlspark/blob/master/src/lightgbm/src/main/scala/TrainUtils.scala#L111
and here to free dataset after training is done:
https://github.com/Azure/mmlspark/blob/master/src/lightgbm/src/main/scala/TrainUtils.scala#L118
If I missed something somewhere then that could be an issue.  But I'm not sure what else I could have missed, these are the only native constructs created during training

Thank you for the very quick answer!
I don't think this is a matter of memory available for the workers. I have a pretty small dataset (around 1 Gb), and I tried running on 10 executors with a lot of memory available (32 Gb on off-heap through yarn memory overhead), and I still have the same error.

@alois-bissuel is it the same bad-alloc error:
java.lang.Exception: Dataset create call failed in LightGBM with error: std::bad_alloc

if so, I'm not really sure what else it could be.  Searching online definitely suggests it is caused by OOM.  One thing to double check for sanity would be to print out the number of partitions of the dataset prior to training on lightgbm and make sure it is not 1 but some reasonable number.  Also, if you sample down the dataset, say be 50%, do you still see the error?  The error is definitely coming from one of the workers and not the driver so I don't think increasing driver memory would help.  Are you sure the spark.executor.memory or --executor-memory configuration is set to a reasonable size?

I have checked it all: the number of partition is reasonable (or maybe too high, but I also tried setting one partition per executor), the memory setting looks sensible. I did not try subsampling the dataset, as it is already quite small (a Gb for ten executors having each three dozen Gb of RAM).
When looking at the profiling tools that we have at our company, it seems that the executors are consuming a lot of heap, but very little off-heap. Is it expected, given that LightGBM should allocate off-heap ?

@alois-bissuel hmm, just to make sure I understand correctly, by off-heap do you mean unmanaged memory (eg the native C/C++ allocations, NOT the memory on the stack in the process) and by on-heap do you mean the Java managed heap?  If I understand correctly, then they should be about the same, since we take the memory from the Java side and allocate it in the native side.  If the Java on-heap memory is much higher than the native off-heap memory, then indeed this seems like a bug, that we should be able to trace to the scala code written.

Yes, this is exactly what I meant (regarding on-heap and off-heap). The off-heap usage stays very low (150 Mb) whereas the on-heap usage increases to 7-8 Gb. Are there any tests or some sort of profiling which I could do ?

The off-heap usage stays very low (150 Mb) whereas the on-heap usage increases to 7-8 Gb

@alois-bissuel that is odd, I would assume the off-heap usage would be at least 1 GB since that is the size of the dataset, if not more.  I'm not sure why it would be so low, 150 MB doesn't make sense to me.
I'm not sure about how to profile on spark, do there exist good tools for profiling distributed clusters?  For C# I've used jetbrains memory profiler & redgate memory profiler a lot, for python I've used cProfile a lot, I've also used GNU gdb and windbg a lot in the past.  Haven't used a lot of Java memory profilers, and certainly haven't used one on a distributed cluster.  It looks like this is a good one based on some simple searching: https://github.com/uber-common/jvm-profiler
Ideally it would be nice to see which objects are holding so much memory and what is preventing them from being garbage collected.


Implement the controller for API BGPPolicy

This commit implements the controller of API BGPPolicy, designed to advertise
Service IPs, Egress IPs, and Pod IPs to BGP peers from selected Kubernetes Nodes.
According to the spec of BGPPolicy, the Node selector is used to select Nodes
to which a BGPPolicy is applied. Multiple BGPPolicies can be applied to the
same Node. However, only the oldest BGPPolicy will be effective on a Node,
with others serving as alternatives. The effective one may be changed in the
following cases:

The current effective BGPPolicy is updated and not applied to the Node.
The current effective BGPPolicy is deleted.

The BGP server instance is only created and started for the effective BGPPolicy on
a Node. If the effective BGPPolicy is changed, the corresponding BGP server instance
will be terminated by calling the Stop method, and a new BGP server instance will
be created and started by calling the Start method for the new effective BGPPolicy.
To create a BGP server instance, ASN, router ID, and listen port must be specified.
The ASN and listen port are specified in the spec of the effective BGPPolicy. For router ID,
if the Kubernetes cluster is IPv4-only or dual-stack, we use the Node's IPv4 address
as the router ID, ensuring uniqueness. If the Kubernetes cluster is IPv6-only, where no
Node IPv4 address is available, the router ID could be specified via the Node annotation
node.antrea.io/bgp-router-id. If not present, a router ID will be generated by hashing
the Node name and update it to the Node annotation node.antrea.io/bgp-router-id.
Additionally, the stale BGP server instance will be terminated and a new BGP server
instance should be created and started when any of ASN, routerID, or listen port changes.
The information of the BGP peers is specified in the effective BGPPolicy. The unique
identification of a BGP peer is the peer IP address and peer ASN.
To reconcile the latest BGP peers:

Get the BGP peers to be added and add them by calling the AddPeer method of the
BGP server instance.
Get the BGP peers to be deleted and delete them by calling the RemovePeer method
of the BGP server instance.
Get the remaining BGP peers and calculate the updated BGP peers, then update them by
calling the UpdatePeer method of the BGP server instance.

The information of the IPs to be advertised can be calculated from the spec of the
effective BGPPolicy. Currently, we advertise the IPs and CIDRs to all the BGP peers.
To reconcile the latest IPs to all BGP peers:

If the BGP server instance is newly created and started, advertise all the IPs by
calling the AdvertiseRoutes method.
If the BGP server instance is not newly created and started:

Get the IPs/CIDRs to be added and advertise them by calling the AdvertiseRoutes method.
Get the IPs/CIDRs to be removed and withdraw them by calling the WithdrawRoutes method.

The feature is gated by the alpha BGPPolicy feature gate and only supported in Linux.

[x] BGPPolicy API #6009
[x] goBGP integration tests #6447
[x] goBGP logger #6447
[ ] e2e tests #6523 #6488
[ ] documents #6524 (https://github.com/antrea-io/antrea/pull/6203#discussion_r1677520852)
[x] unit tests
[x] refine code comments

Hi @hongliangl could you explain more about advertise Service IPs, Egress IPs, and Pod IPs to BGP peers from selected Nodes.?  According to the API, there is enum of ipTypes, Does it mean users can choose what's kind of Service can be advertised? Will there be a default one? It would be better to provide a sample BGPPolicy and explain the behavior to help reviewers. Thanks.

Hi @hongliangl could you explain more about advertise Service IPs, Egress IPs, and Pod IPs to BGP peers from selected Nodes.? According to the API, there is enum of ipTypes, Does it mean users can choose what's kind of Service can be advertised? Will there be a default one? It would be better to provide a sample BGPPolicy and explain the behavior to help reviewers. Thanks.

will add

Addressed all comments, will reply every comment later. @tnqn

I observed a panic when testing the patch:
E0722 06:25:16.742241       1 runtime.go:79] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
goroutine 561 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic({0x2a8ad00?, 0x4e7ef90})
        k8s.io/apimachinery@v0.29.2/pkg/util/runtime/runtime.go:75 +0x85
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0x0?})
        k8s.io/apimachinery@v0.29.2/pkg/util/runtime/runtime.go:49 +0x6b
panic({0x2a8ad00?, 0x4e7ef90?})
        runtime/panic.go:914 +0x21f
antrea.io/antrea/pkg/agent/controller/bgp.matchedNode(0x0, 0xc000078022?)
        antrea.io/antrea/pkg/agent/controller/bgp/controller.go:744 +0x2e
antrea.io/antrea/pkg/agent/controller/bgp.(*Controller).matchedCurrentNode(0x19e7c00019c7c?, 0x1a27c0001a07c?)
        antrea.io/antrea/pkg/agent/controller/bgp/controller.go:739 +0x3f
antrea.io/antrea/pkg/agent/controller/bgp.(*Controller).addBGPPolicy(0xc000739200, {0x2f1cb40?, 0xc000bec780})
        antrea.io/antrea/pkg/agent/controller/bgp/controller.go:699 +0x52
k8s.io/client-go/tools/cache.ResourceEventHandlerFuncs.OnAdd(...)
        k8s.io/client-go@v0.29.2/tools/cache/controller.go:239
k8s.io/client-go/tools/cache.(*processorListener).run.func1()
        k8s.io/client-go@v0.29.2/tools/cache/shared_informer.go:972 +0x13e
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0x30?)
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/backoff.go:226 +0x33
k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0xc00120e738?, {0x34cc420, 0xc0011cc000}, 0x1, 0xc0011ca000)
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/backoff.go:227 +0xaf
k8s.io/apimachinery/pkg/util/wait.JitterUntil(0x1420480000004?, 0x3b9aca00, 0x0, 0x4?, 0x10a0400010804?)
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/backoff.go:204 +0x7f
k8s.io/apimachinery/pkg/util/wait.Until(...)
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/backoff.go:161
k8s.io/client-go/tools/cache.(*processorListener).run(0xc0008af830)
        k8s.io/client-go@v0.29.2/tools/cache/shared_informer.go:966 +0x69
k8s.io/apimachinery/pkg/util/wait.(*Group).Start.func1()
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/wait.go:72 +0x4f
created by k8s.io/apimachinery/pkg/util/wait.(*Group).Start in goroutine 443
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/wait.go:70 +0x73
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0xb0 pc=0x259142e]

I observed a panic when testing the patch:
E0722 06:25:16.742241       1 runtime.go:79] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
goroutine 561 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic({0x2a8ad00?, 0x4e7ef90})
        k8s.io/apimachinery@v0.29.2/pkg/util/runtime/runtime.go:75 +0x85
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0x0?})
        k8s.io/apimachinery@v0.29.2/pkg/util/runtime/runtime.go:49 +0x6b
panic({0x2a8ad00?, 0x4e7ef90?})
        runtime/panic.go:914 +0x21f
antrea.io/antrea/pkg/agent/controller/bgp.matchedNode(0x0, 0xc000078022?)
        antrea.io/antrea/pkg/agent/controller/bgp/controller.go:744 +0x2e
antrea.io/antrea/pkg/agent/controller/bgp.(*Controller).matchedCurrentNode(0x19e7c00019c7c?, 0x1a27c0001a07c?)
        antrea.io/antrea/pkg/agent/controller/bgp/controller.go:739 +0x3f
antrea.io/antrea/pkg/agent/controller/bgp.(*Controller).addBGPPolicy(0xc000739200, {0x2f1cb40?, 0xc000bec780})
        antrea.io/antrea/pkg/agent/controller/bgp/controller.go:699 +0x52
k8s.io/client-go/tools/cache.ResourceEventHandlerFuncs.OnAdd(...)
        k8s.io/client-go@v0.29.2/tools/cache/controller.go:239
k8s.io/client-go/tools/cache.(*processorListener).run.func1()
        k8s.io/client-go@v0.29.2/tools/cache/shared_informer.go:972 +0x13e
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0x30?)
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/backoff.go:226 +0x33
k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0xc00120e738?, {0x34cc420, 0xc0011cc000}, 0x1, 0xc0011ca000)
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/backoff.go:227 +0xaf
k8s.io/apimachinery/pkg/util/wait.JitterUntil(0x1420480000004?, 0x3b9aca00, 0x0, 0x4?, 0x10a0400010804?)
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/backoff.go:204 +0x7f
k8s.io/apimachinery/pkg/util/wait.Until(...)
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/backoff.go:161
k8s.io/client-go/tools/cache.(*processorListener).run(0xc0008af830)
        k8s.io/client-go@v0.29.2/tools/cache/shared_informer.go:966 +0x69
k8s.io/apimachinery/pkg/util/wait.(*Group).Start.func1()
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/wait.go:72 +0x4f
created by k8s.io/apimachinery/pkg/util/wait.(*Group).Start in goroutine 443
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/wait.go:70 +0x73
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0xb0 pc=0x259142e]

Thanks, will resolve this.

F

I observed a panic when testing the patch:
E0722 06:25:16.742241       1 runtime.go:79] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
goroutine 561 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic({0x2a8ad00?, 0x4e7ef90})
        k8s.io/apimachinery@v0.29.2/pkg/util/runtime/runtime.go:75 +0x85
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0x0?})
        k8s.io/apimachinery@v0.29.2/pkg/util/runtime/runtime.go:49 +0x6b
panic({0x2a8ad00?, 0x4e7ef90?})
        runtime/panic.go:914 +0x21f
antrea.io/antrea/pkg/agent/controller/bgp.matchedNode(0x0, 0xc000078022?)
        antrea.io/antrea/pkg/agent/controller/bgp/controller.go:744 +0x2e
antrea.io/antrea/pkg/agent/controller/bgp.(*Controller).matchedCurrentNode(0x19e7c00019c7c?, 0x1a27c0001a07c?)
        antrea.io/antrea/pkg/agent/controller/bgp/controller.go:739 +0x3f
antrea.io/antrea/pkg/agent/controller/bgp.(*Controller).addBGPPolicy(0xc000739200, {0x2f1cb40?, 0xc000bec780})
        antrea.io/antrea/pkg/agent/controller/bgp/controller.go:699 +0x52
k8s.io/client-go/tools/cache.ResourceEventHandlerFuncs.OnAdd(...)
        k8s.io/client-go@v0.29.2/tools/cache/controller.go:239
k8s.io/client-go/tools/cache.(*processorListener).run.func1()
        k8s.io/client-go@v0.29.2/tools/cache/shared_informer.go:972 +0x13e
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0x30?)
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/backoff.go:226 +0x33
k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0xc00120e738?, {0x34cc420, 0xc0011cc000}, 0x1, 0xc0011ca000)
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/backoff.go:227 +0xaf
k8s.io/apimachinery/pkg/util/wait.JitterUntil(0x1420480000004?, 0x3b9aca00, 0x0, 0x4?, 0x10a0400010804?)
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/backoff.go:204 +0x7f
k8s.io/apimachinery/pkg/util/wait.Until(...)
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/backoff.go:161
k8s.io/client-go/tools/cache.(*processorListener).run(0xc0008af830)
        k8s.io/client-go@v0.29.2/tools/cache/shared_informer.go:966 +0x69
k8s.io/apimachinery/pkg/util/wait.(*Group).Start.func1()
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/wait.go:72 +0x4f
created by k8s.io/apimachinery/pkg/util/wait.(*Group).Start in goroutine 443
        k8s.io/apimachinery@v0.29.2/pkg/util/wait/wait.go:70 +0x73
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0xb0 pc=0x259142e]

@tnqn  Fixed. You could review the code change here: https://github.com/antrea-io/antrea/compare/a20c311dc340df5d2e31e3c7fbe43cb535e2181d..682706171f6fdb422f5600b8aece407bbf7a1397

/test-all

/test-all

@hongliangl  Thanks a lot for the quick response, @antoninbas  @tnqn could you take another look? We plan to release 2.1 tomorrow, need to merge this as early as we can to move forward. Thanks!
btw, can we defer the e2e PR #6523 if there is no enough time to close it?

/test-all


Gzip fixes

Coverage increased (+0.9%) to 99.353% when pulling 54b2e3c1e012d2cca2e27ac149bd6e24ffff4f38 on gzip into e419e893b72e327e39da269d0b5a6bee09d06b69 on master.

Coverage increased (+0.9%) to 99.353% when pulling 54b2e3c1e012d2cca2e27ac149bd6e24ffff4f38 on gzip into e419e893b72e327e39da269d0b5a6bee09d06b69 on master.

Coverage increased (+0.9%) to 99.353% when pulling 54b2e3c1e012d2cca2e27ac149bd6e24ffff4f38 on gzip into e419e893b72e327e39da269d0b5a6bee09d06b69 on master.

Coverage increased (+0.9%) to 99.353% when pulling ba3c404a578dcf8b2f39c2635c7dcaafe380d592 on gzip into e419e893b72e327e39da269d0b5a6bee09d06b69 on master.

Coverage increased (+0.9%) to 99.378% when pulling 0c9f325ec7233a63f44e5de8039e593046204dd8 on gzip into e419e893b72e327e39da269d0b5a6bee09d06b69 on master.

Coverage increased (+0.9%) to 99.353% when pulling 20a586a1c3972dd4116dea0c7f4993ced37f871e on gzip into e419e893b72e327e39da269d0b5a6bee09d06b69 on master.

Coverage increased (+0.9%) to 99.353% when pulling 20a586a1c3972dd4116dea0c7f4993ced37f871e on gzip into e419e893b72e327e39da269d0b5a6bee09d06b69 on master.


Sending can yield the thread

When we call try_send on a sender, here's what I think is happening:

ConcurrentQueue::push is called here
If the queue is unbounded, Unbounded::push is called here
If the queue reached its current capacity, busy_wait is called here
Which either spins or yields the thread, as defined here

I find it weird that we end up yielding the thread in async code.
If this is expected, I think it should be documented.

@notgull have you seen this and would you like me to work on a solution?


[devicelab] CodeSign failures with "Your session has expired. Please log in."

The following build commands failed:
CodeSign /Users/flutter/.cocoon/flutter/dev/integration_tests/ui/build/ios/Debug-
iphoneos/Runner.app/Frameworks/App.framework
CodeSign /Users/flutter/.cocoon/flutter/dev/integration_tests/ui/build/ios/Debug-
iphoneos/Runner.app/Frameworks/Flutter.framework

fastlane match or this article may help: https://support.apple.com/en-us/HT204836.

Tong is trying out fastlane and creating a design doc for using fastlane.

Here's the observed error:
2019-11-12T13:54:46.846030: stdout: Failed to build iOS app
2019-11-12T13:54:46.847864: stdout: Error output from Xcode build:
stdout: ↳
2019-11-12T13:54:46.848005: stdout:     2019-11-12 13:54:43.984 xcodebuild[77507:38779338]  DVTPortal: Service '' encountered an unexpected result code from the portal ('1100')
stdout:     2019-11-12 13:54:43.984 xcodebuild[77507:38779338]  DVTPortal: Error:
stdout:     Error Domain=DVTPortalServiceErrorDomain Code=1100 "Your session has expired.  Please log in." UserInfo={payload={type = mutable dict, count = 9,
stdout:     entries =>
stdout:     	0 : responseId = {contents = "fb07752e-cafb-4506-a1b6-8ae422c8b467"}
stdout:     	2 : {contents = "protocolVersion"} = QH65B2
stdout:     	3 : {contents = "requestUrl"} = {contents = "https://developerservices2.apple.com/services/QH65B2/viewDeveloper.action"}
2019-11-12T13:54:46.848081: stdout:     	6 : {contents = "userLocale"} = en_US
stdout:     	8 : resultCode = {value = +1100, type = kCFNumberSInt64Type}
stdout:     	9 : userString = {contents = "Your session has expired.  Please log in."}
stdout:     	10 : {contents = "resultString"} = {contents = "Your session has expired.  Please log in."}
stdout:     	11 : httpCode = {value = +200, type = kCFNumberSInt64Type}
stdout:     	12 : {contents = "creationTimestamp"} = {contents = "2019-11-12T21:54:44Z"}
stdout:     }
stdout:     , NSLocalizedDescription=Your session has expired.  Please log in.}
stdout:     2019-11-12 13:54:44.276 xcodebuild[77507:38779339]  DTDeviceKit: deviceType from b4873f14ffb248dfcb00c8cb7fdd4cdcff87f1f0 was NULL
stdout:     2019-11-12 13:54:44.333 xcodebuild[77507:38779365]  DVTPortal: Service '' encountered an unexpected result code from the portal ('1100')
2019-11-12T13:54:46.848143: stdout:     2019-11-12 13:54:44.333 xcodebuild[77507:38779365]  DVTPortal: Error:
stdout:     Error Domain=DVTPortalServiceErrorDomain Code=1100 "Your session has expired.  Please log in." UserInfo={payload={type = mutable dict, count = 9,
stdout:     entries =>
stdout:     	0 : responseId = {contents = "0e4d3d78-ba92-4cf9-82c4-48e43a4ab69f"}
stdout:     	2 : {contents = "protocolVersion"} = QH65B2
stdout:     	3 : {contents = "requestUrl"} = {contents = "https://developerservices2.apple.com/services/QH65B2/viewDeveloper.action"}
stdout:     	6 : {contents = "userLocale"} = en_US
stdout:     	8 : resultCode = {value = +1100, type = kCFNumberSInt64Type}
2019-11-12T13:54:46.848192: stdout:     	9 : userString = {contents = "Your session has expired.  Please log in."}
stdout:     	10 : {contents = "resultString"} = {contents = "Your session has expired.  Please log in."}
stdout:     	11 : httpCode = {value = +200, type = kCFNumberSInt64Type}
stdout:     	12 : {contents = "creationTimestamp"} = {contents = "2019-11-12T21:54:44Z"}
stdout:     }
stdout:     , NSLocalizedDescription=Your session has expired.  Please log in.}
stdout:     ** BUILD FAILED **
stdout:
stdout:
2019-11-12T13:54:46.848239: stdout: Xcode's output:
stdout: ↳
stdout:     fatal error: module map file '/Users/flutter/.cocoon/flutter/examples/flutter_gallery/ios/Pods/Headers/Public/video_player/video_player.modulemap' not found
stdout:     1 error generated.
stdout:     note: Using new build systemnote: Planning buildnote: Constructing build descriptionwarning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 6.0, but the range of supported deployment target versions is 8.0 to 13.0.99. (in target 'Reachability' from project 'Pods')
stdout:
2019-11-12T13:54:46.855299: stderr: Encountered error while building for device.
2019-11-12T13:54:46.867583: "/Users/flutter/.cocoon/flutter/bin/flutter" exit code: 1
2019-11-12T13:54:46.874735: Task failed: Executable "/Users/flutter/.cocoon/flutter/bin/flutter" failed with exit code 1.2019-11-12T13:54:46.874966:

We have been checking different options here:

We added a health check that is not preventing the issue because is just flakiness. It can fail and then next in the next iteration just pass.
We added security unlock command before each task execution and still failing from time to time.

The next step will be to add a wrapper to the code sign command so we can retry that specific command within the same task.

Prepare to experiment the fastlane approach on mac1.

Summary of my findings so far: there's nothing obviously wrong with the login.keychain, it is unlocked on Keychain Access UI and it doesn't automatically lock.
Somehow the command security unlock-keychain login.keychain fixes the issue. I can't verify how it works because there's no way to show a keychain lock status via command line.

Couple of mitigations will be implemented:

Will run security unlock-keychain before running the task.
Adding retries to the codesign command to remove flakiness at the task level.

As manual signing on mac1 didn't fail for a week, I'm going to apply manual signing to all mac machines. /cc @keyonghan

Related issue: https://github.com/flutter/flutter/issues/45016

Manual code signing has been deployed to all mac bots, watching how it goes. Next step is checking in related infra code.

Manual singing solved this problem. The scripts of setting up code signing identities have been checked in.


Use deprecated field of yaml schema specification instead of only modifying description

There is a deprecated field in specification  http://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.9.3
it would be nice to use it instead of mentioning the deprecation only in description field like here https://github.com/apache/camel-k/blob/48422c08bc20295d09cb31694adc177726806d6b/helm/camel-k/crds/crd-kamelet.yaml#L217
it will allow various tooling to make it more visible.

Yeah, it would be good to have. We are generating the CRDs with some tooling and I haven't found an immediate way to declare the value is deprecated, ie Resources []ResourceSpec json:"resources,omitempty,deprecated"``. Not sure if it exists some struct label that is taken in consideration when we generate the CRDs.

Maybe we're lucky if we bump the gen-tool version: https://github.com/kubernetes-sigs/controller-tools/pull/541
Going to have a look later.

While CRD structural schemas rely on OpenAPI v3 schemas, there are some limitations. The deprecated field cannot be set, as documented in:
https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation
The +kubebuilder:deprecatedversion marker applies at the CRD level, not the field level.

still an important feature even if upstream doesn't provide an out of the box solution currently


Update poetry.lock

poetry.lock file is not up to date with pyproject.toml. This commit is
the result of running poetry update.

Thanks, last updates had been quick fixes and I was lazy and forgot my build procedures. ;)


Seeing "...  is not implemented" status messages

Behaviour
I've recently started seeing some ".... is not implemented" status messages, where - if I remember correctly - those statuses were previously reported via this action.
In particular I noticed the GitHub Pages status no longer reporting, while I use that to prevent potentially borking a GH Pages website if a deploy is run while there is an outage.
Steps to reproduce this issue
      - name: Check GitHub Pages status
        uses: crazy-max/ghaction-github-status@v3
        with:
          pages_threshold: major_outage

Expected behaviour
Statuses being reported for all systems.
Actual behaviour

Should be fixed with latest release

@crazy-max Much appreciated!


Block contact

Is that possible block contact with this lib?

[ ] The language must be English, if you are not fluent in English consider using: https://www.deepl.com/translator if it supports your native language

[ ] Please check if any other issue already adresses your concerns or if a recent PR is already fixing the mentioned issue

[ ] Please make sure to format your code, and to mark your code as such, with the provided tools from github (upper right of this box)

[ ] Please state your Operating System (inlcuding version), your Python Version, and your installation way (pip, from repo) and if you are running it inside a docker container

[ ] Note that the pip installation might be behind, so try to fix your issue with a pull from the repo and update to the most recent version

[ ] Follow the Stackoverflow Guidelines (https://stackoverflow.com/help/how-to-ask) when in need of help

[ ] Consider posting your question on Stackoverflow if it is a general programming question

[ ] There will be no support for spamming, or other mischief

[ ] There will be no support for finding professionals

add this function in api.js
window.WAPI.contactBlock = function(id, done){
    const contact = window.Store.Contact.get(id);
    if (contact !== undefined){
        contact.setBlock(!0);
        done(true);
        return true;
    }
    done(false);
    return false;
}

window.WAPI.contactUnblock = function(id, done){
    const contact = window.Store.Contact.get(id);
    if (contact !== undefined){
        contact.setBlock(!1);
        done(true);
        return true;
    }
    done(false);
    return false;
}

check this pr #421


installation diffculty

i tired installing cython inside the directory as directed in https://www.cython.org, but it's giving me this error message, python: can't open file 'setup.py': [Errno 2] No such file or directory
also, installing pracmln as directed in https://www.praclm.org, it's also giving me this message, python: can't open file 'setup.py': [Errno 2] No such file or directory
how can i solve this?

Hi @chris4real, can you try to run pip install pracmln from inside a virtualenv?
If there is an error please post the output here.

I wrote a dockerfile on this, https://gist.github.com/cjen07/0cd56081453c5d7d602393ca71a37789 any suggestions are welcome


Uploading PDF media in collections

Hello,
When trying to upload .pdf files from my computer via the media picker they appear to be uploading (as the percentage increases), however they do not appear in the media picker once uploaded.
I am able to upload any other image files, just not PDFs.
Are PDFs supported in the mediapicker? Is there any reason this could be happening?
Thanks

The PDFs the client were trying to upload seemed to be too large - once compressed, they uploaded fine.


Put together the functions we have and divide them into classes

This is a quite large issue, maybe we should do it all together in a larger session. Goal is to bring our code into a shape we discussed in the code diagram.

In the file: https://github.com/lucasthierry17/Ant_Project/blob/lucas/Version1.py we have separated the function into three main classes (Ants, Food, Board)


Using toString as a data title causes c3 to crash (C3 0.4.11)

C3 Version: 0.4.11
Using toString as a data title causes c3 to crash. I tested this in Chrome, Firefox, and internet explorer 11.
With a Pie Chart, it gives the error: "Uncaught TypeError: t.indexOf is not a function"
Example:
var chart = c3.generate({
    data: {
        columns: [
            ['toString', 30]
        ],
        type : 'pie',
    }
});

With a  line chart, it silently fails.
Example:
var chart = c3.generate({
    data: {
        columns: [
            ['toString', 30, 50]
        ]
    }
});

Closing as duplicate of #662


esp-wifi: Align default settings

Thank you for your contribution!
We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:
Submission Checklist 📝

[ ] I have updated existing examples or added new ones (if applicable).
[x] I have used cargo xtask fmt-packages command to ensure that all changed code is formatted correctly.
[ ] My changes were added to the CHANGELOG.md in the proper section.
[ ] I have added necessary changes to user code to the Migration Guide.
[x] My changes are in accordance to the esp-rs API guidelines

Extra:

[x] I have read the CONTRIBUTING.md guide and followed its instructions.

Pull Request Details 📖
Description
Fixes #2246
It turned out that (in my wifi setup) we sometimes/often miss packets - especially the DHCP offer packet which made getting an IP address take often 60 seconds for me.
In the end our defaults are just not correctly aligned (and thus "not ideal") - so let's align the defaults to what esp-idf is currently using.
With this change I pretty much always get the IP address instantly - sometimes it might take one retry (10 seconds)
I don't think this deserves a CHANGELOG entry
Testing
Running the wifi examples

I ran the DHCP (blocking and async) examples and on Xtensas, it takes ~50% of the runs 10 seconds to get IP address for me. RISCV chips seems to be fine for me.

How long does it take on main for the Xtensas? Mind checking the https://github.com/espressif/esp-idf/tree/master/examples/wifi/getting_started/station example for reference?
(There might be an additional problem around the DHCP socket - but 10s is much better than the 60s it was for me)

I just want to make sure that the value changes coming from esp-wifi-sys are known and expected.

+1 better to double check

Is it worth having some tests that just assert our defaults match the sys defaults? So we at least know when they change? Maybe it's not worth the effort, not sure.

Is it worth having some tests that just assert our defaults match the sys defaults? So we at least know when they change? Maybe it's not worth the effort, not sure.

Would probably be a viable workaround but I would be in favor of teaching esp-config a way to evaluate defaults at the call-site somehow

I ran the DHCP (blocking and async) examples and on Xtensas, it takes ~50% of the runs 10 seconds to get IP address for me. RISCV chips seems to be fine for me.

How long does it take on main for the Xtensas? Mind checking the https://github.com/espressif/esp-idf/tree/master/examples/wifi/getting_started/station example for reference?
(There might be an additional problem around the DHCP socket - but 10s is much better than the 60s it was for me)

With that IDF example, Xtensas get the IP almost instantly for me.

I ran the DHCP (blocking and async) examples and on Xtensas, it takes ~50% of the runs 10 seconds to get IP address for me. RISCV chips seems to be fine for me.

How long does it take on main for the Xtensas? Mind checking the https://github.com/espressif/esp-idf/tree/master/examples/wifi/getting_started/station example for reference?
(There might be an additional problem around the DHCP socket - but 10s is much better than the 60s it was for me)

With that IDF example, Xtensas get the IP almost instantly for me.

And main?

Main seems to be working more-or-less fine for me - most of the time I get IP almost instantly (tested Xtensas).

Main seems to be working more-or-less fine for me - most of the time I get IP almost instantly (tested Xtensas).

Doesn't make a lot of sense .... would need Wireshark analysis to see what esp-wifi sees and what is really happening on the network (i.e. comparing Wireshark capturing the network and using esp-wifi-wireshark plugin and compare that)


💡 [REQUEST] - Add Cloud Run example(s) to Cloud Monitoring backends

Summary
We have examples for App Engine, Pub/Sub and Load Balancer. Cloud Run probably deserves its own example(s) too, as it is becoming more and more popular.
Basic Example
Define your SLO in slo_cloudrun_service_availability.yaml (with MQL):
apiVersion: sre.google.com/v2
kind: ServiceLevelObjective
metadata:
  name: cloudrun-service-availability
  labels:
    service_name: cloudrun
    feature_name: service
    slo_name: availability
spec:
  description: Availability of Cloud Run service
  backend: cloud_monitoring_mql
  method: good_bad_ratio
  exporters:
  - cloud_monitoring
  service_level_indicator:
    filter_good: >
      fetch cloud_run_revision
      | metric 'run.googleapis.com/request_count'
      | filter resource.project_id == '${CLOUDRUN_PROJECT_ID}'
      | filter resource.service_name == '${CLOUDRUN_SERVICE_NAME}'
      | filter metric.response_code_class == '2xx'
    filter_valid: >
      fetch cloud_run_revision
      | metric 'run.googleapis.com/request_count'
      | filter resource.project_id == '${CLOUDRUN_PROJECT_ID}'
      | filter resource.service_name == '${CLOUDRUN_SERVICE_NAME}'
  goal: 0.85

Populate ${CLOUDRUN_PROJECT_ID} and ${CLOUDRUN_SERVICE_NAME} in .env:
export CLOUDRUN_PROJECT_ID=slo-generator-demo
export CLOUDRUN_SERVICE_NAME=cloud-run-randomly-fails

Run with:
$ source .env
$ slo-generator compute --slo-config=samples/cloud_monitoring_mql/slo_cloudrun_service_availability.yaml --config=samples/config.yaml
INFO - cloudrun-service-availability    | 1 hour   | SLI: 70.0    % | SLO: 85.0 % | Gap: -15.0 % | BR: 2.0 / 9.0 | Alert: 0 | Good: 42       | Bad: 18
INFO - cloudrun-service-availability    | 12 hours | SLI: 76.1111 % | SLO: 85.0 % | Gap: -8.89 % | BR: 1.6 / 3.0 | Alert: 0 | Good: 548      | Bad: 172
INFO - cloudrun-service-availability    | 7 days   | SLI: 75.4186 % | SLO: 85.0 % | Gap: -9.58 % | BR: 1.6 / 1.5 | Alert: 1 | Good: 7612     | Bad: 2481
INFO - cloudrun-service-availability    | 28 days  | SLI: 75.0158 % | SLO: 85.0 % | Gap: -9.98 % | BR: 1.7 / 1.0 | Alert: 1 | Good: 23783    | Bad: 7921
INFO - Run finished successfully in 7.7s.
INFO - Run summary | SLO Configs: 1 | Duration: 7.7s

Screenshots
![DESCRIPTION](LINK.png)

Drawbacks
None.
Unresolved questions
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thanks Laurent. Very much appreciated this one :)


Python API SIGSEGV during call to model.symbols (clingo 5.5.0)

I sometimes ran into the following error code:
Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
Debugging with python faulthandler yielded the following:
Fatal Python error: Segmentation fault
_Current thread 0x00007efd70e14740 (most recent call first):
File "/some_path/lib/python3.9/site-packages/clingo/solving.py", line 345 in symbols
File "/some_path/benchmarking/benchmark-GUC/solvers/python_solvers/two_solvers_brave.py", line 147 in check'
...
The call in line 147 was the following:
model.symbols(shown=True, complement=True)
The model was received the following way:
In the init method the control object was set(the missing space between -e and brave is not a typo, it might be a little bug?):
self._ctl = Control(['-ebrave'])
In the check method the brave model was computed the following way:
  with self._ctl.solve(assumptions, yield_=True) as hnd:
  for i, _ in enumerate(hnd):
  model = hnd.model()
(sorry for missing indents)
I can provide more information if requested.

Could you please send a full example that produces the segfault?
PS: Short options with an argument do not need a space after them. You could also write ['-e', 'brave'].
PPS: You can use triple backticks for code
```python
while True:
    pass
```

Compare your code with the code in #305
Models cannot be reused outside of their handling context. You can save the symbols though. I just had a similar problem.

Thanks! That solved my problem.


The ability to add multiple devices (Kodis) in the extension's settings.

I really like this extension. I use it a lot.
One feature I'm missing, though, is being able to add multiple devices in the settings: I have Kodi both in my living room and in my bedroom, and every time change room, I have to change the ip-adr. in the extension's settings. It would be really nice to be able to have multiple devices – and maybe even name them in the settings.
I'd really appreciate the feature.

Hi,
Thanks for the feedback. We already have enhancement request https://github.com/goldenratio/xbmc-web-remote/issues/24
I will find time to finish this. Closing this now.

made some progress here, https://github.com/goldenratio/xbmc-web-remote/issues/24


Remove dotnet-release from Grafana Servicing jobs in R&D queues dashboard

dotnet-release repo is not part of .NET product, official builds always run from main and there is no concept for servicing jobs so it should be excluded from Servicing jobs in R&D queues dashboard

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[ ] Internal Infrastructure Improvements

Release Note Description
Removed dotnet-release from Servicing jobs in R&D queues dashboard

PR: https://dev.azure.com/dnceng/internal/_git/dotnet-helix-service/pullrequest/35958

This is done


links option is not implemented

The command line -links option is defined, but link generation is not implemented.

@moorereason I've created PR #8 which adds links to the template. The links flag is still not wired, but the template output should contain functional anchor links. Source code links are a bit trickier due to the way godoc works. I'll submit another PR when I figure it out

@lordnynex  is #20 what you meant by the source code links?


Trying to put too many players into a single game breaks it

ex:
playerList: "player1,bot1,bot12,bot13,bot14,bot15,bot16,bot17,bot18,bot19,bot122,bot123"
This brings the user to the game but only the constructor fires, leaving the single gold node

ex:
playerList: "player1,bot1,bot12,bot13,bot14,bot15,bot16,bot17,bot18,bot19,bot122,bot123"
This brings the user to the game but only the constructor fires, leaving the single gold node

Front-end needs to do error checking with API calls.


Major and minor grid lines

I'm looking to make minor lines in my grid, like so:
(i've searched all the issues with no luck)

This is a feature that I'd like as well (especially with log scaling). I'm new to this codebase but will submit a PR for this if time permits.

Major / minor grid lines can be achieved easily using a plugin. I've written a very simple plugin to achieve this.
http://jsbin.com/yemomu/edit?js,output
Just include the plugin function within your project and add the plugin to Chartist as shown in the bin.

Closing becauase of inactivity


Navigation Offline

Hello, first of all, thank you very much for the plugin!!
Would it be possible to implement offline navigation? It would be a very interesting feature.
Att,

Yes, this would be a great feature, it is in the future pipeline but haven't had time to work on it yet


Put all data in error messages

Right now the curl only uses a few names and a timestamp, no IDs.
Also decode timestamp to human readable.
Also make the bot ignore itself in sending error messages (but still put its messages in the database).

This was mostly fixed in bf5843abf527c2d52d99fdb7c6266c8d07d4604a
It does not currently ignore itself? Test this by replying with a message into general AFTER making it ignore itself.

This was finished!


Account: as a user I would like to copy the memo field content

Figma design: https://www.figma.com/file/vYQD6uZtkPgtmgJ3zfauq0/Zashi-UI?type=design&node-id=1890-14530&mode=design&t=a1dCwbgVg0LQ0PEs-4

Closing this as already done.


Constrain version of Keras used to <=2.3.1

Hi,
As discussed in https://github.com/notAI-tech/deepsegment/issues/33, certain versions of Keras are having compatibility issues with Tensorflow. My problem is that my project uses Poetry to manage dependencies. I'm also using DeepSegment, which uses this, which doesn't specify which versions of Keras work, so Poetry keeps trying to update Keras every time I update anything else. I'm having to manually edit my lockfile to keep Keras from updating.
I believe the solution is simple: just add a version number to the setup.py file. Something like Keras<=2.3.1 should do it. This can always be changed if/when the compatibility issue is solved. I'm happy to write a pull request for this, if you'd like.
Thanks!

added and pushed the new version to PyPI.

Awesome, thank you for your quick response.


Stepper shows Firefox native up/down buttons in control

Expected Behavior
Native up/down step control buttons should not show
Actual Behavior
When running in FF up/down buttons show in the control along with the spectrum up/down buttons
Reproduce Scenario (including but not limited to)
Run http://opensource.adobe.com/spectrum-css/2.9.1/docs/#stepper in Firefox
Steps to Reproduce
Run page in Firefox - look at stepper control
Browser name/version/os (ie Chrome Version 62.0.3202.94 (Official Build) (64-bit) MacOS)
Firefox 66.0.3 (64-bit) MacOS
Spectrum-CSS version
2.9.1
Sample Code that illustrates the problem
Screenshots (if applicable)

This is caused by
.spectrum-Textfield {
...
 -moz-appearance:textfield;
 -webkit-appearance:none!important;
}

-webkit-appearance is also supported by FF so is overriding -moz-appearance

Thanks, @jnurthen! It turns out we don't need !important there at all. After checking with the latest version of normalize.css, there are no problems even if that statement is removed entirely. I dropped the !important and tested in FF and Chrome + Normalize, and it's looking right now.

Still reproduces. I think you need to reverse the order of -moz-appearance and -webkit-appearance

@lazd Do I need to log a new issue or can you reopen this one.

@jnurthen Reopening should be good.

Looks like this should be fixed by https://github.com/adobe/spectrum-css/commit/0fc6c3b12b26e87c4730878003509e3a44c0da86, which will be merged to master shortly.

This is fixed, just tested in Firefox.


Correct support for DATE, DATE_AND_TIME and DT

Turns out that a DT ADS type is read from pyads as DATE_AND_TIME, which is not supported yet.
Moreover, the existing DT type is c_int32, while I'm quite sure that should be c_uint32 (unsigned).
Beckoff says the DT is equal to DWORD, which has a lower bound of 0.

Additionally, I would suggest to clean up our list of types a little bit by using aliases. For instance, if DT is a DWORD, let's define it like:
PLCTYPE_DWORD = c_uint32
PLCTYPE_DT = PLCTYPE_DWORD
```


If last_write_wins is true, dvv_enabled must be false [JIRA: CLIENTS-849]

There is currently no way to change the property "dvv_enabled" for a Bucket.
When I set the "last_write_wins" property to true, the following error is thrown:

Invalid bucket properties: [{dvv_enabled, "If last_write_wins is true, dvv_enabled must be false"}]

It would be nice to have a withDVV method in StoreBucketProperties.Builder so that we can disable the DVV:
new StoreBucketProperties.Builder(namespace) .withLastWriteWins(true) .withDVV(false) .build();
I am using the version 2.0.4.
Thanks!

Hi Guillaume,
Our PB interface doesn't currently have the capability for the dvv bucket property (https://github.com/basho/riak_pb/blob/develop/src/riak.proto#L108-L160), so I'll create an issue for that.
After we get that in we can look into adding it to the Java client.
A workaround would be to set that property through the HTTP api, or to set it at the bucket-type level through the command line.
Thanks,
Alex
Related: https://github.com/basho/riak-go-client/issues/64

Thanks, Alex!


Clarify the usage of X-App-Domain and X-Sales-Channel Headers

and incorporate into the existing guidelines.
Related to / triggered by #228.

Only discovered one usage in our API repository. Same API is also responsible for other headers from #253.

From the meeting: We don't need to change anything here.


add ATMs around Los Santos

https://github.com/PatrickGTR/gta-open/commit/9ffa32c662509e5779518efb7d79b5eb6c30141b done in this commit


Source Asana: Add dbt converter

closes #9

Nice @pangeran-bottor I'm gonna review tomorrow! Sorry the delay

@pangeran-bottor it looks good, missing a couple of models.

Thanks for the help @marcosmarxm
Finalized this PR to be reviewed. The models already cover all Fivetran models from https://github.com/fivetran/dbt_asana_source/blob/main/models/src_asana.yml