bazel fails to import directory structure for "rules_go"

bazel
➜ bazel version
Build label: 0.7.0-homebrew
Build target: bazel-out/darwin_x86_64-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Thu Oct 19 09:12:48 2017<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>

IDEA
IntelliJ IDEA 2017.2.5
Build #IU-172.4343.14, built on September 26, 2017
Licensed to ***
You have a perpetual fallback license for this version
Subscription is active until February 5, 2019
JRE: 1.8.0_152-release-915-b12 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.12.6

bazel plugin
Version: 2<IP_ADDRESS>.1

make rules_go clone
git clone https://github.com/bazelbuild/rules_go
cd rules_go
git reset 697e08091d108c44f0c4e1a37f3fb7353e71aab3 --hard

and try to import project to IDEA.
It fails and no files shown in the project.
Updating VCS...
Running Bazel info...
Command: /usr/local/bin/bazel info --tool_tag=ijwb:IDEA:ultimate --curses=no --color=no --noexperimental_ui --noprogress_in_terminal_title --

Command: git diff --name-status --no-renames 697e08091d108c44f0c4e1a37f3fb7353e71aab3

____Loading package: @local_config_xcode//
Computing VCS working set...
Your working set is empty
Sync targets from project view:
  //...:all

Building IDE info files...
Command: /usr/local/bin/bazel build --tool_tag=ijwb:IDEA:ultimate --keep_going --experimental_build_event_binary_file=/var/folders/gw/y5lsln6s4lq0n9zzvn6z70jm0000gn/T/intellij-bep-005d3a04-e470-4acd-b5b5-99655273ed83 --noexperimental_build_event_binary_file_path_conversion --curses=no --color=no --noexperimental_ui --noprogress_in_terminal_title --aspects=@intellij_aspect//:intellij_info_bundled.bzl%intellij_info_aspect --override_repository=intellij_aspect=/Users/oleg/Library/Application Support/IntelliJIdea2017.2/ijwb/aspect --output_groups=intellij-info-go,intellij-info-java,intellij-info-py,intellij-info-generic -- //...:all

____Loading complete.  Analyzing...
DEBUG: /private/var/tmp/_bazel_oleg/d75c3373a0bfa3cb0c51526246454bbf/external/io_bazel_rules_go/go/private/tools/path.bzl:18:3:
EXPERIMENTAL: the go_path rule is still very experimental
Please do not rely on it for production use, but feel free to use it and file issues

DEBUG: /private/var/tmp/_bazel_oleg/d75c3373a0bfa3cb0c51526246454bbf/external/io_bazel_rules_go/go/private/tools/vet.bzl:18:3:
EXPERIMENTAL: the go_vet_test rule is still very experimental
Please do not rely on it for production use, but feel free to use it and file issues

DEBUG: /private/var/tmp/_bazel_oleg/d75c3373a0bfa3cb0c51526246454bbf/external/io_bazel_rules_go/go/private/tools/path.bzl:40:7: Duplicate package
Found github.com/bazelbuild/rules_go/go/tools/gazelle/config in
  //go/tools/gazelle/config:go_default_library
and
  @io_bazel_rules_go//go/tools/gazelle/config:go_default_library

____Found 309 targets...
____Building...
____[321 / 322] BazelWorkspaceStatusAction stable-status.txt
____Elapsed time: 2.722s, Critical Path: 0.00s
ide-info result: success
Total rules: 321, new/changed: 321, removed: 0
Reading IDE info result...
Loaded 321 aspect files, total size 178kB
ide-query result: success
Target map size: 161
Building IDE resolve files...
Command: /usr/local/bin/bazel build --tool_tag=ijwb:IDEA:ultimate --keep_going --experimental_build_event_binary_file=/var/folders/gw/y5lsln6s4lq0n9zzvn6z70jm0000gn/T/intellij-bep-5670d021-3317-4846-a7f4-19c22c2b2f59 --noexperimental_build_event_binary_file_path_conversion --curses=no --color=no --noexperimental_ui --noprogress_in_terminal_title --aspects=@intellij_aspect//:intellij_info_bundled.bzl%intellij_info_aspect --override_repository=intellij_aspect=/Users/oleg/Library/Application Support/IntelliJIdea2017.2/ijwb/aspect --output_groups=intellij-resolve-go,intellij-resolve-java,intellij-resolve-py -- //...:all

____Loading package: @local_config_xcode//
____Loading complete.  Analyzing...
DEBUG: /private/var/tmp/_bazel_oleg/d75c3373a0bfa3cb0c51526246454bbf/external/io_bazel_rules_go/go/private/tools/path.bzl:18:3:
EXPERIMENTAL: the go_path rule is still very experimental
Please do not rely on it for production use, but feel free to use it and file issues

DEBUG: /private/var/tmp/_bazel_oleg/d75c3373a0bfa3cb0c51526246454bbf/external/io_bazel_rules_go/go/private/tools/vet.bzl:18:3:
EXPERIMENTAL: the go_vet_test rule is still very experimental
Please do not rely on it for production use, but feel free to use it and file issues

DEBUG: /private/var/tmp/_bazel_oleg/d75c3373a0bfa3cb0c51526246454bbf/external/io_bazel_rules_go/go/private/tools/path.bzl:40:7: Duplicate package
Found github.com/bazelbuild/rules_go/go/tools/gazelle/config in
  //go/tools/gazelle/config:go_default_library
and
  @io_bazel_rules_go//go/tools/gazelle/config:go_default_library

____Found 309 targets...
____Building...
____[228 / 229] BazelWorkspaceStatusAction stable-status.txt
____Elapsed time: 1.560s, Critical Path: 0.01s
Prefetching genfiles...
Command: /usr/local/bin/bazel info --tool_tag=ijwb:IDEA:ultimate build-language --curses=no --color=no --noexperimental_ui --noprogress_in_terminal_title --

Reading jdeps files...
Loaded 0 jdeps files, total size 0kB
Reading package manifests...
Java content entry count: 1
Updating Jar Cache...
Prefetching files...
Computing directory structure...
Sync failed

==== TIMING REPORT ====

Sync: 133.4s
    BazelInfo: 1.6s
    GitDiff: 17ms
    WorkingSet: 0ms
    IdeQuery: 2.9s
        ExecuteBazelCommand: 2.9s
        FetchAspectOutput: 1ms
        UpdateTargetMap: 20ms
    BazelBuild: 1.8s
        ExecuteBlazeCommand: 1.8s
        PrefetchGenfiles: 0ms
    UpdateSyncState: 204ms
        BUILD language spec: 202ms
        LoadJdepsFiles: 1ms
            FetchJdeps: 1ms
        JavaWorkspaceImporter: 1ms
            ReadPackageManifests: 0ms
                FetchPackageManifests: 0ms
            CalculateSourceDirectories: 0ms
    ReverseDependencies: 0ms
    Jar Cache: 0ms
    PrefetchFiles: 0ms
    RefreshVirtualFileSystem: 19ms
    DirectoryStructure: 126.9s

Works for me. Can you attach your logs at ~/.IntelliJIdea2017.2/system/log?
Or import again with the most recent bazel plugin.

I'm gonna close this now. Please respond if you still see this issue.


Create unit-test for parse public key and assert correct behavior

Summary of Bug
Parse public key appears to incorrectly handle public keys (observed behavior: empty addresses) when used by memorialize contract
Version
v1.0.0-HEAD
Steps to Reproduce/Remediation
During testing of P8e client integration using Memorialize contract it seems that the parse public key method is not behaving as expected.  Create a unit-test for this method and ensure it correctly handles both 33 byte (compressed) and 64 byte (uncompressed) secp256k1 keys.
https://github.com/provenance-io/provenance/blob/4192fd46ea56574bb4ffcacb632d8bb54a720b28/x/metadata/types/p8e.go#L381-L391
Appropriate test case public key values:
// TODO @piercetrey-figure will supply these test case values
comp := ''"
uncomp := ""

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

here are the uncompressed/compressed base64-encoded forms of a secp256k1 public key
uncompressed: BGxX6eJRAdXlU64APi95Al44m1FJVgfHlrTpXAqUAB+8JNhM0HgIGWElKbgD6K0KOX9HTJZdlX0z3WTmQrdW+8Q
compressed: AmxX6eJRAdXlU64APi95Al44m1FJVgfHlrTpXAqUAB+8


Fix for a racy WorkSerializer shutdown

Fixes b/217470353
The way WorkSerializer is used inside gRPC Core, it is usually destroyed by a callback that's scheduled on the same work serializer. Note that there are a few layers of indirection here, where gRPC Core creates a shared WorkSerializer object so that it can pass it around to various subsystems.
This race was caused by an unhandled condition where the WorkSerializerImpl object could be orphaned between the time the last callback was executed and the queue size decremented https://github.com/grpc/grpc/blob/63398540b65c775de36f1e7e370c1800aca6637d/src/core/lib/iomgr/work_serializer.cc#L162 and the point where we make sure the queue has been drained https://github.com/grpc/grpc/blob/63398540b65c775de36f1e7e370c1800aca6637d/src/core/lib/iomgr/work_serializer.cc#L177.
In such cases, we end up hitting the assert at https://source.corp.google.com/piper///depot/google3/third_party/grpc/src/core/lib/iomgr/work_serializer.cc;rcl=424645002;l=127

Please have @soheilhy look at the atomics usage here.


Not working since update

Describe the bug
Since I updated to the latest version the target sensors don’t seem to be updating themselves. I have a few sensors. One which runs from midnight to 6am. Usually after the release of the latest rates around 4pm this triggers the calculation of the next blocks. This hasn’t happened today.
Reproduction steps
Target sensor not updating
Expected behaviour
Target sensors update after daily refresh
Tariff Code
No response
Integration Version
Latest
Home Assistant Version
Latest
Fresh Install?
After upgrading
Home Assistant Logs
NA

Hello. Can you confirm that you're not seeing the expected behaviour as outlined in the FAQ?

I don’t think so. These have been working fine before. I’ve just
reconfigured them and it’s recalculated them now but in the past this was
automatic.
D
On Sat, 25 Nov 2023 at 18:01, David Kendall @.***>
wrote:

Hello. Can you confirm that you're not seeing the expected behaviour as
outlined in the FAQ
https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/blob/develop/_docs/faq.md#why-wont-my-target-rates-update
?
—
Reply to this email directly, view it on GitHub
https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/issues/574#issuecomment-1826388299,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE5PC2CO2GKQZ4A2OVNCQUDYGIXAZAVCNFSM6AAAAAA72G2QPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWGM4DQMRZHE
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

Nothing has changed with those sensors during the last few releases, bar some name changes in attributes.
As mentioned in the FAQ, is last_evaluted updating roughly every minute?
Has target_times_last_evaluated attribute updated within the last 24 hours?
Do you have rate information for the required timeframe (midnight to 6am) available?

This is a bit of a strange one and I think maybe related to an upgrade of
Home Assistant I performed at a similar time to the Octopus integration.  A
few observations:-

A dashboard I can previously setup to show the attributes of the target
hours was showing UNKNOWN for all the attributes eg. start time, end time,
hours etc.
To remedy this I had to go and re-type/re-select the attribute to get it
to show the value which was already present as I could see it in the
attributes box of the entity.
One of my automations was referencing the hour attribute - looking at the
debug it said this variable did not exist - again re-typing/re-selecting
the variable in the automation fixed this.  It is as though the upgrade
knocked out the pointers to the variable in the target hours setup.
The target sets were not refreshing themselves until I reconfigured them
all - exact same values - through the interface.

Definitely a head scratching one but I think down to the Home Assistant
upgrade not your integration.  Think it is sorted now though ;)
On Sat, 25 Nov 2023 at 19:58, David Kendall @.***>
wrote:

Nothing has changed with those sensors during the last few releases, bar
some name changes in attributes.
As mentioned in the FAQ, is last_evaluted updating roughly every minute?
Has target_times_last_evaluated attribute updated within the last 24
hours?
Do you have rate information for the required timeframe (midnight to 6am)
available?
—
Reply to this email directly, view it on GitHub
https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/issues/574#issuecomment-1826409032,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE5PC2B3H2OR5B5V6AYNZNDYGJEYFAVCNFSM6AAAAAA72G2QPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWGQYDSMBTGI
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

Ok glad to hear, and that is very odd. It does seem like HA sometimes loses track of entities. I've been doing everything to the book (according to their docs) to my knowledge (hense why I add the new evaluated attributes.
I'll close this ticket for now, but comment here if you see the same behaviour again.


On https://prod-preview.openshift.io, cannot associate an area with a workitem

The save button for the area selection is missing (the cancel "x" button is present):

Issue fixed @ldimaggi. Please verify.

Verified !


Try to fix signing on NetStandard branch

@pharring,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@SergeyKanzhelev please merge so I can kick off another test build.


VSCode integrated terminal is opening terminals externally after the new update has been performed

The terminal process terminated with exit code:<PHONE_NUMBER>

VSCode Version: May 2019 (version 1.35)
OS Version: Windows 10 Pro 1903

Steps to Reproduce:

View > Terminal
Or Ctrl + '

Does this issue occur when all extensions are disabled?: Yes
I am having problems in my development workspace. Just when I open the VSCode's integrated terminal, it opens the powershell externally. This is happening for any terminal. When I close the terminal, it generates an unreported error.
Two observations that are worth mentioning and still pertinent in this matter is that I have already relialized VSCode clean installations in both versions. And nothing went right.

Response in this link: https://stackoverflow.com/questions/56154957/how-do-i-get-around-the-verified-bug-in-windows-1903-and-launch-the-vscode-integ


MINOR: Tag AWS instances with Jenkins build url

This will allow us to trace leaked instances back to the job,
so that we can figure out what happened and fix the leak.
Testing: Verified Jenkins build URL is set on the AWS instances when running system tests.
Backporting: Can this be backported to 0.10.2? The oldest branch we can backport the better.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Ping @ijuma : Can u merge and backport to 0.10.2? Thx


Memray leaks native backtrace state

Bug Report
I've recently tried combining flaky and pytest-memray with the leak analysers. On GitHub Actions, the pytest process was being issued SIGKILL from the kernel. Which is weird.
The behaviour is that when pytest is running, the memory usage slowly escalates (toward 10GBi or the machine runs out of memory).

So I looked and looked at which tests are leaking memory. Yes, there were some. But then it crossed my mind to take my library out of the equation and just test Stdlib modules instead.

Yes, I appreciate this is a ridiculous issue to raise. But I think that either memray or flaky is leaking significant memory. I might be totally wrong or doing something silly in these tests and we can all ignore this issue :-)

memray 1.5.0
pytest 7.4.2
flaky 3.7.0
Python 3.10.12 (main, Jun  7 2023, 19:32:10) [GCC 10.2.1 20210110]

Current Behavior A clear and concise description of the behavior.
Input Code

REPL or Repo link if applicable:

import sys
import pytest
import logging

def filter_gc(stack):
    for frame in stack.frames[:4]:
        if "bananacore" in frame.filename:
            return True

    return False

levels = [
    (logging.DEBUG, "DEBUG"),
    (logging.INFO, "INFO"),
    (logging.WARNING, "WARNING"),
    (logging.ERROR, "ERROR"),
    (logging.CRITICAL, "CRITICAL"),
    (logging.NOTSET, "NOTSET"),
]

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
@pytest.mark.parametrize("level, level_name", levels)
def test_getlevelname(level, level_name):
    assert logging.getLevelName(level) == level_name
    assert logging.getLevelName(level_name) == level

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_value_error_invalid_string_names():
    with pytest.raises(ValueError):
        assert logging.getLevelName("EXample") == "Level EXample"

junk_level_names = [None, 3.2, (), [], {}, 100]

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
@pytest.mark.parametrize("level", junk_level_names)
def test_getlevelname_invalid_level(level):
    with pytest.raises((TypeError, ValueError)):
        logging.getLevelName(level)

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_root_logger_critical(capsys):
    logging.root.handlers = []
    logging.critical("test")

    cap = capsys.readouterr()
    assert cap.out == ""
    assert cap.err == "CRITICAL:root:test\n"

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_root_logger_fatal(capsys):
    logging.root.handlers = []
    logging.fatal("test")

    cap = capsys.readouterr()
    assert cap.out == ""
    assert cap.err == "CRITICAL:root:test\n"

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_root_logger_error(capsys):
    logging.root.handlers = []
    logging.error("test")

    cap = capsys.readouterr()
    assert cap.out == ""
    assert cap.err == "ERROR:root:test\n"

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_root_logger_exception(capsys):
    logging.root.handlers = []
    logging.exception("test", exc_info=Exception("bork bork bork"))

    cap = capsys.readouterr()
    assert cap.out == ""
    assert cap.err == "ERROR:root:test\nException: bork bork bork\n"

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_root_logger_warning(capsys):
    logging.root.handlers = []
    logging.warning("test")

    cap = capsys.readouterr()
    assert cap.out == ""
    assert cap.err == "WARNING:root:test\n"

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_root_logger_warn(capsys):
    logging.root.handlers = []
    logging.warn("test")

    cap = capsys.readouterr()
    assert cap.out == ""
    assert cap.err == "WARNING:root:test\n"

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_root_logger_info(capsys):
    logging.root.handlers = []
    logging.info("test")

    cap = capsys.readouterr()
    assert cap.out == ""
    assert cap.err == ""

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_root_logger_debug(capsys):
    logging.root.handlers = []
    logging.debug("test")

    cap = capsys.readouterr()
    assert cap.out == ""
    assert cap.err == ""

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_root_logger_log():
    logging.root.handlers = []
    logging.log(logging.DEBUG, "test")

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_basic_config_with_stream_and_filename_without_handlers():
    logging.root.handlers = []

    with pytest.raises(ValueError):
        logging.basicConfig(stream=sys.stderr, filename="log.txt")

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_basic_config_with_stream_or_filename_with_handlers():
    handler = logging.StreamHandler(sys.stderr)

    with pytest.raises(ValueError):
        logging.basicConfig(handlers=[handler], stream=sys.stdout)

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_basic_config_invalid_style():
    with pytest.raises(ValueError):
        logging.basicConfig(style="!")

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_basic_config_with_level():
    logging.basicConfig(level=logging.INFO)
    assert logging.root.level == logging.INFO

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_basic_config_invalid_arguments():
    logging.root.handlers = []
    with pytest.raises(ValueError):
        logging.basicConfig(invalid_argument="value")

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
def test_make_log_record():
    log_record = logging.makeLogRecord({"levelno": logging.WARNING})

    assert log_record.levelno == logging.WARNING

@pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
@pytest.mark.parametrize("encoding", ["utf-8", None])
def test_basic_config_encoding(encoding):
    logging.basicConfig(filename="test.txt", encoding=encoding)

Running this code with memray, natives, trace python allocators and forcing flaky runs for 9-10 runs:
python -m pytest testproject/ --memray --stacks=7 --native --trace-python-allocators
--force-flaky --min-passes=9 --max-runs=10
========================================================= test session starts =========================================================
platform linux -- Python 3.10.12, pytest-7.4.2, pluggy-1.3.0
rootdir: /workspaces/picologging
plugins: repeat-0.9.1, flaky-3.7.0, Faker-19.6.2, hypothesis-6.87.0, memray-1.5.0, anyio-4.0.0, cov-4.1.0
collected 30 items

testproject/test_logging.py ......FFF...F..........FFF...                                                                       [100%] [100%] [100%] [100%] [100%] [100%] [100%] [100%]. [100%]

============================================================== FAILURES ===============================================================
________________________________________________ test_value_error_invalid_string_names ________________________________________________

    @pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
    def test_value_error_invalid_string_names():
>       with pytest.raises(ValueError):
E       Failed: DID NOT RAISE <class 'ValueError'>

testproject/test_logging.py:32: Failed
________________________________________________ test_getlevelname_invalid_level[None] ________________________________________________

level = None

    @pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
    @pytest.mark.parametrize("level", junk_level_names)
    def test_getlevelname_invalid_level(level):
>       with pytest.raises((TypeError, ValueError)):
E       Failed: DID NOT RAISE (<class 'TypeError'>, <class 'ValueError'>)

testproject/test_logging.py:42: Failed
________________________________________________ test_getlevelname_invalid_level[3.2] _________________________________________________

level = 3.2

    @pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
    @pytest.mark.parametrize("level", junk_level_names)
    def test_getlevelname_invalid_level(level):
>       with pytest.raises((TypeError, ValueError)):
E       Failed: DID NOT RAISE (<class 'TypeError'>, <class 'ValueError'>)

testproject/test_logging.py:42: Failed
________________________________________________ test_getlevelname_invalid_level[100] _________________________________________________

level = 100

    @pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
    @pytest.mark.parametrize("level", junk_level_names)
    def test_getlevelname_invalid_level(level):
>       with pytest.raises((TypeError, ValueError)):
E       Failed: DID NOT RAISE (<class 'TypeError'>, <class 'ValueError'>)

testproject/test_logging.py:42: Failed
_______________________________________ test_basic_config_with_stream_or_filename_with_handlers _______________________________________

    @pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
    def test_basic_config_with_stream_or_filename_with_handlers():
        handler = logging.StreamHandler(sys.stderr)

>       with pytest.raises(ValueError):
E       Failed: DID NOT RAISE <class 'ValueError'>

testproject/test_logging.py:144: Failed
___________________________________________________ test_basic_config_invalid_style ___________________________________________________

    @pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
    def test_basic_config_invalid_style():
>       with pytest.raises(ValueError):
E       Failed: DID NOT RAISE <class 'ValueError'>

testproject/test_logging.py:150: Failed
____________________________________________________ test_basic_config_with_level _____________________________________________________

    @pytest.mark.limit_leaks("64B", filter_fn=filter_gc)
    def test_basic_config_with_level():
        logging.basicConfig(level=logging.INFO)
>       assert logging.root.level == logging.INFO
E       assert 30 == 20
E        +  where 30 = <RootLogger root (WARNING)>.level
E        +    where <RootLogger root (WARNING)> = logging.root
E        +  and   20 = logging.INFO

testproject/test_logging.py:157: AssertionError
========================================================== warnings summary ===========================================================
testproject/test_logging.py::test_root_logger_warn
testproject/test_logging.py::test_root_logger_warn
testproject/test_logging.py::test_root_logger_warn
testproject/test_logging.py::test_root_logger_warn
testproject/test_logging.py::test_root_logger_warn
testproject/test_logging.py::test_root_logger_warn
testproject/test_logging.py::test_root_logger_warn
testproject/test_logging.py::test_root_logger_warn
testproject/test_logging.py::test_root_logger_warn
  /workspaces/picologging/testproject/test_logging.py:99: DeprecationWarning: The 'warn' function is deprecated, use 'warning' instead
    logging.warn("test")

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html

============================================================ MEMRAY REPORT ============================================================
Allocation results for testproject/test_logging.py::test_root_logger_exception at the high watermark

         📦 Total memory allocated: 3.8KiB
         📏 Total allocations: 348
         📊 Histogram of allocation sizes: |  ▂ ▇ █ ▄|
         🥇 Biggest allocating functions:
                - __init__:/home/vscode/.local/lib/python3.10/site-packages/exceptiongroup/_formatting.py:47 -> 216.0B
                - format:/home/vscode/.local/lib/python3.10/site-packages/exceptiongroup/_formatting.py:248 -> 208.0B
                - wrapper:/home/vscode/.local/lib/python3.10/site-packages/pytest_memray/plugin.py:191 -> 168.0B
                - error:/usr/local/lib/python3.10/logging/__init__.py:1506 -> 168.0B
                - error:/usr/local/lib/python3.10/logging/__init__.py:2105 -> 168.0B

Allocation results for testproject/test_logging.py::test_root_logger_warn at the high watermark

         📦 Total memory allocated: 2.5KiB
         📏 Total allocations: 222
         📊 Histogram of allocation sizes: |▁ ▇ █ ▁  |
         🥇 Biggest allocating functions:
                - validate:/usr/local/lib/python3.10/logging/__init__.py:428 -> 1.1KiB
                - validate:/usr/local/lib/python3.10/logging/__init__.py:428 -> 168.0B
                - wrapper:/home/vscode/.local/lib/python3.10/site-packages/pytest_memray/plugin.py:191 -> 168.0B
                - _showwarnmsg:/usr/local/lib/python3.10/warnings.py:112 -> 128.0B
                - validate:/usr/local/lib/python3.10/logging/__init__.py:428 -> 80.0B

Allocation results for testproject/test_logging.py::test_basic_config_invalid_arguments at the high watermark

         📦 Total memory allocated: 2.2KiB
         📏 Total allocations: 149
         📊 Histogram of allocation sizes: |  █ ▅    |
         🥇 Biggest allocating functions:
                - validate:/usr/local/lib/python3.10/logging/__init__.py:428 -> 1.1KiB
                - validate:/usr/local/lib/python3.10/logging/__init__.py:428 -> 168.0B
                - raises:/home/vscode/.local/lib/python3.10/site-packages/_pytest/python_api.py:937 -> 83.0B
                - validate:/usr/local/lib/python3.10/logging/__init__.py:428 -> 80.0B
                - __init__:/usr/local/lib/python3.10/logging/__init__.py:790 -> 80.0B

Allocation results for testproject/test_logging.py::test_root_logger_critical at the high watermark

         📦 Total memory allocated: 2.1KiB
         📏 Total allocations: 212
         📊 Histogram of allocation sizes: |▂ █ ▅ ▂  |
         🥇 Biggest allocating functions:
                - validate:/usr/local/lib/python3.10/logging/__init__.py:428 -> 1.1KiB
                - wrapper:/home/vscode/.local/lib/python3.10/site-packages/pytest_memray/plugin.py:191 -> 168.0B
                - validate:/usr/local/lib/python3.10/logging/__init__.py:428 -> 168.0B
                - __init__:/usr/local/lib/python3.10/logging/__init__.py:790 -> 80.0B
                - validate:/usr/local/lib/python3.10/logging/__init__.py:428 -> 80.0B

Allocation results for testproject/test_logging.py::test_root_logger_fatal at the high watermark

         📦 Total memory allocated: 2.1KiB
         📏 Total allocations: 212
         📊 Histogram of allocation sizes: |▂ █ ▅ ▂  |
         🥇 Biggest allocating functions:
                - validate:/usr/local/lib/python3.10/logging/__init__.py:428 -> 1.1KiB
                - validate:/usr/local/lib/python3.10/logging/__init__.py:428 -> 168.0B
                - wrapper:/home/vscode/.local/lib/python3.10/site-packages/pytest_memray/plugin.py:191 -> 168.0B
                - __init__:/usr/local/lib/python3.10/logging/__init__.py:790 -> 80.0B
                - validate:/usr/local/lib/python3.10/logging/__init__.py:428 -> 80.0B

===Flaky Test Report===

test_getlevelname[10-DEBUG] passed 1 out of the required 9 times. Running test again until it passes 9 times.
test_getlevelname[10-DEBUG] passed 2 out of the required 9 times. Running test again until it passes 9 times.
...
test_basic_config_encoding[None] passed 9 out of the required 9 times. Success!

===End Flaky Test Report===
======================================================= short test summary info =======================================================
FAILED testproject/test_logging.py::test_value_error_invalid_string_names - Failed: DID NOT RAISE <class 'ValueError'>
FAILED testproject/test_logging.py::test_getlevelname_invalid_level[None] - Failed: DID NOT RAISE (<class 'TypeError'>, <class 'ValueError'>)
FAILED testproject/test_logging.py::test_getlevelname_invalid_level[3.2] - Failed: DID NOT RAISE (<class 'TypeError'>, <class 'ValueError'>)
FAILED testproject/test_logging.py::test_getlevelname_invalid_level[100] - Failed: DID NOT RAISE (<class 'TypeError'>, <class 'ValueError'>)
FAILED testproject/test_logging.py::test_basic_config_with_stream_or_filename_with_handlers - Failed: DID NOT RAISE <class 'ValueError'>
FAILED testproject/test_logging.py::test_basic_config_invalid_style - Failed: DID NOT RAISE <class 'ValueError'>
FAILED testproject/test_logging.py::test_basic_config_with_level - assert 30 == 20
============================================== 7 failed, 23 passed, 9 warnings in 56.35s ==============================================

$ python -m pytest testproject --memray --stacks=7 --native --trace-python-allocators

Also uses significant memory but not the same total amount.
I'm not able to run my entire test suite because it gets killed by OOMKiller.

So, yep, real issue. We're leaking the state associated with libbacktrace's unwinding for each test case. We have to leak it - the API of libbacktrace is designed so that's the only option, surprisingly:
https://github.com/bloomberg/memray/blob/98032ae8eb23c16e8fbc3067efbd09a8b07b36ba/src/vendor/libbacktrace/backtrace.h#L81-L85
But, we ought to be reusing it from one test case to the next, instead of leaking it between each test and creating a new one for the next test. This has been wrong for a long time, but we never noticed because only pytest-memray reads many different capture files during the lifetime of the program - it's not possible to trigger this misbehavior through the public Memray APIs or the memray CLI entry point, because they only ever operate on one single capture file.
It's easy enough to fix - we just need to move some state to be explicitly global rather than recreating it each time a new capture file is read, and wrap a lock around it. While looking at the surrounding code I spotted some other things that I don't like, though, so I'm gonna try to clean up a few different things here...

So, yep, real issue
Is it wrong that I breathed a sigh of relief?

Thanks for figuring it out. I'll update and retest when there's a patch.

@tonybaloney the latest release, includes a bug fix for this. Hopefully it works this time. 😊


fix(SDK): Findings and Notifications service now use AccountID as global param

fixed ITs to comply with the UX change, in both findings and notifications

:tada: This PR is included in version 0.0.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Change the paths to be openshift/aro-installer

See https://issues.redhat.com/browse/ARO-3122

/cherrypick release-4.10

/cherrypick release-4.11


Add approvalStatus query param to list batch changes

In support of #659
Changes in this pull request:

add approvalStatus query parameter on the list batch changes route to filter returned batch changes by their approval status. Parameter is available for any users.
In conjunction with the ignoreAccess parameter this will allow super users to retrieve all batch changes in the system that are in a pending approval state.

we can't override the Enumeration withName method which seems to be where we'd want to compare on lowercase values if we were trying to handle this with our serializers.


Polkadot Protocol > Basics > Randomness

Create a randomness page migrated from: https://wiki.polkadot.network/docs/learn-cryptography#randomness

Niceee, looking good so far! 🚀
here there are some comments regarding content and also some about formatting to support Erin and Dawn :)

@eshaben I applied your suggestions and gave this one more pass. Just needs a final signoff.


Temporarily add ubsan supressions

https://github.com/grpc/grpc/pull/16986 was actually merged by mistake, so this PR is a hotfix:

it turns out that before #16986, ubsan on foundry wasn't actually working (it wouldn't halt on errors), so #16986 just revealed pre-existing issues.
we don't want ubsan on Foundry constantly red, so adding existing failures to ubsan_suppressions.txt
supressions should be removed as things get fixed in code.

Overview of failing ubsan tests is here:
https://source.cloud.google.com/results/invocations/5a07b143-b6f9-4b02-af63-cc2c7d98c471/targets

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

UBSAN results:

most failures from https://source.cloud.google.com/results/invocations/b6710124-7e9b-4485-8b69-085a3dcf30fe/targets are gone, but this failure of //test/core/end2end/fuzzers:client_fuzzer still remains:

D1025 17:39:16.774240523      18 fuzzer_corpus_test.cc:50]   Example file<EMAIL_ADDRESS>I1025 17:39:16.774446353      18 ev_epoll1_linux.cc:116]     grpc epoll fd: 3
D1025 17:39:16.774463992      18 ev_posix.cc:169]            Using polling engine: epoll1
D1025 17:39:16.774557868      18 dns_resolver.cc:338]        Using native dns resolver
src/core/lib/transport/status_conversion.cc:44:11: runtime error: load of value 553671168, which is not a valid value for type 'grpc_http2_error_code'
    #0 0x7ff943da35d5 in grpc_http2_error_to_grpc_status(grpc_http2_error_code, long) /proc/self/cwd/src/core/lib/transport/status_conversion.cc:44:11
    #1 0x7ff943d94337 in grpc_error_get_status(grpc_error*, long, grpc_status_code*, grpc_slice*, grpc_http2_error_code*, char const**) /proc/self/cwd/src/core/lib/transport/error_utils.cc:72:14
    #2 0x7ff943f9b611 in grpc_chttp2_fake_status(grpc_chttp2_transport*, grpc_chttp2_stream*, grpc_error*) /proc/self/cwd/src/core/ext/transport/chttp2/transport/chttp2_transport.cc:2106:3
    #3 0x7ff943f9b093 in grpc_chttp2_mark_stream_closed(grpc_chttp2_transport*, grpc_chttp2_stream*, int, int, grpc_error*) /proc/self/cwd/src/core/ext/transport/chttp2/transport/chttp2_transport.cc:2234:7
    #4 0x7ff943fdfd20 in grpc_chttp2_rst_stream_parser_parse(void*, grpc_chttp2_transport*, grpc_chttp2_stream*, grpc_slice, int) /proc/self/cwd/src/core/ext/transport/chttp2/transport/frame_rst_stream.cc:108:5

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,014,173      Total (=)      2,014,173

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,113,475      Total (=)     11,113,475

 No significant differences in binary sizes

Corrupt JSON data (indicates timeout or crash):
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.new: 10
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.old: 10

[microbenchmarks] No significant performance differences

Bazel ubsan tests passing. Merging early to fix the breakage.


Add the FileCachePrefix.is_local property and improve test coverage

Fixed Issues

None

Summary of Changes

Added the FileCachePrefix.is_local property
Added a few test cases to improve code coverage

Known Problems

None

AI Code Review is in progress (usually takes <3 minutes unless it's a very large PR).

Changelist by Bito
This pull request implements the following key changes.

Key Change
Files Impacted

Feature Improvement - Enhanced FileCachePrefix with New Properties

- __init__.py - Added 'prefix' and 'is_local' properties to FileCachePrefix class

- test_filecache.py - Added test cases for new FileCachePrefix properties

Bug Fix - Improved Path Handling and Logging

- __init__.py - Enhanced path resolution and added conditional logging for local files

AI Code Review is in progress (usually takes <3 minutes unless it's a very large PR).

AI Code Review is in progress (usually takes <3 minutes unless it's a very large PR).

AI Code Review is in progress (usually takes <3 minutes unless it's a very large PR).


TraceTCP link not working

It seems the TraceTCP link is not functioning, might be good to look into that

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

ID: 45822051-b802-c3da-01c2-88abb5482ca2
Version Independent ID: 3b6670b0-6eb8-9ab1-fd3d-02c833d2cdbc
Content: Office 365 performance tuning using baselines and performance history
Content Source: Enterprise/performance-tuning-using-baselines-and-history.md
Service: o365-administration
GitHub Login: @MSFTTracyP
Microsoft Alias: tracyp

@jopgommans This link has been corrected and updated. Thanks for letting us know.


Make the app more accessible - content description

Summary:
There are plenty of ways to increase accessibility of our app. One of them is adding content descriptions to UI elements, see docs. Currently most of our UI elements does not have their content description. This is a beginner friendly issue. Here would be steps:

Adding UI element descriptors by following the guideline that I linked.
Adding them into strings xml so that they will be translated
Placing them at very top of strings xml so that they won't be confused with other strings, as:

<!--accessibility UI description strings-->
  <string name="xxx1">yyy1</string>
  <string name="xxx2">yyy2</string>
  .....
<!--Other strings-->
  <string name="aaa1">bbb1</string>
  <string name="aaa2">bbb2</string>

Hello, I would like to contribute to this if that's OK. It's my first time on open source so, if it's possible, I would like some more guidance on how to do this. :)

Hey @neslihanturan , could you assign this issue to me? I'd to contribute to this as my first open-source contribution.

I'd like to contribute to this, it's my first time contributing to open-source projects.

Hey!
I'd like to contribute to this, it's my first time contributing to open-source projects. Appreciate any guidance.

Hi, pinging @mariammali273 and @TheProgrammerGod to see if they are still interested. If they are not, it is yours @reshmanjali . We can wait 2 days to hear from them. Please make sure you have read our contribution guide docs meanwhile.

Hey, I would like to contribute to this. This is my first time contributing to open source.

I would like to work on this issue PLease assign me

@Rishavgupta12345 Are you still willing to work on this? If yes, you might want to test Ben's pull request? :-)
By the way, I just tested Accessibility Scanner on our app, the results are interesting. Example:


ovn-kubernetes support cherry picks to release-0.8

Includes commits:
9368ae5 Import ovn-daemonset-f image
fcb9773 Deploy kind with OVN CNI (#401)
45e07b2 Add ovn-kubernetes submodule
b580847 Add makefile support for ovn

Is this still relevant?


lvalue semantic for diag

It would make sense for diag to return an assignable view.

In that case let's do the same for triu, tril, and flipud/flipr. This has be mentioned in #158.

The flip versions should be doable with views ans dynamic views eventually.

This raises the question of how much we want to stick to numpy. I guess
that in the context of jet or pythran, the answer is more.
I don't have perspective on the sort of problematics you encounter in this
context and how you can handle semantic differences like this.
On Mar 9, 2017 6:57 PM, "Wolf Vollprecht"<EMAIL_ADDRESS>wrote:

But diag is actually not a view in NumPy.
To be honest I don't even know if it is a good idea to make the flips
views. This might be just an artifact on how it's implemented in NumPy. I
wouldn't really expect the source array to change after assigning something
to the flipped thing on a NumPy array.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/QuantStack/xtensor/issues/161#issuecomment-285428742,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACSXFpSLj5RTZnA4IceYw2ZpRoPuXVgaks5rkD1sgaJpZM4MXwgB
.

But thinking about it, the case of diag is really quite unclear, isn't it?
For example:
a = xarray({1,2,3});
b = diag(a);
// = {{1, 0, 0}, {0, 2, 0}, {0, 0, 3}};
b += 123;
// = {{124, 123, 123}, ...
// and now a = {{124, 125, 126}}?

Or did you mean diagonal? I agree, for diagonal it makes a lot of sense, even though NumPy doesn't seem to allow it.

Yes I meant diagonal.

by the way, the numpy docs mention

In some future release, it will return a read/write view and writing to the returned array will alter your original array. The returned array will have the same type as the input array.

So I guess it would be a good move to overtake NumPy on this feature! :)

Good catch.

This was an experiment hijacking the xindexview (and using a functor instead of a container).
However, the xindexview currently can only have a 1D shape, so the more advanced diags don't work.
    struct diag_indices
    {
        diag_indices(std::size_t sz) : m_size(sz)
        {
        }

        template <class... Args>
        xindex operator() (std::size_t idx, Args... args) {
            return xindex(idx, idx);
        }

        xindex operator[](std::size_t idx) const
        {
            return xindex({idx, idx});
        }

        std::size_t size() const {
            return m_size;
        }
    private:
        std::size_t m_size;
    };

    template <class E>
    inline auto diagview(E&& e) noexcept
    {
        using view_type = xindexview<xclosure_t<E>, diag_indices>;
        auto sz = e.shape()[1];
        return view_type(std::forward<E>(e), diag_indices(sz));
    }

Maybe the proposed functor view could also be used for diagonal?


Fixing Snackbar zIndex issue on all app

Description
Fix snackbar z-index problem on all app.
discord username: mertolala#9076
**closes #822 **
screenshots

#Mobile

## Things to check before creating a PR

[ ] If it is a core feature, executed detailed tests.

Creating PR rules

[ ] PR must be created for an issue with approved tag. Otherwise PR will be rejected.
[ ] Relevant issue number: The issue number related to PR must be attached to head of PR header, after prefix after prefix # must be attached in parenthesis. A header like this could be used "prefix(#issue_number): PR header" .
[ ] A descriptive and understandable title: The PR title should clearly describe the nature and purpose of the changes. The PR title should be the first thing displayed when the PR is opened. And it should follow the semantic commit rules. For example, a title like "docs(#issueId): Add README.md" can be used.
[ ] Related file selection: Only relevant files should be touched and no other files should be affected.
[ ] Format and Lint Suitability : The code should be made in accordance with a certain format standard and examined according to the lint rules.
[ ] Clean commit history: The commits where the changes are made should be clear and organized.
[ ] Opening PR when job is completed: PR should be opened when job is completed and sent for review by other team members.

Changes

Feature: Add dismiss icon button to all snackbar.
Feat: Add types to enqueue function.
Fix: Fixing zIndex problem with drawer component.
Feature: Add snackbar ui message after copied map link and issue content.
Fix: Change notistack snackbar component instead of material ui snackbar.

How were these changes tested?
Test Configuration:

Firmware version:
Hardware: macos 12.6
Toolchain: Version 109.0.5414.119 (Official Build) (arm64)
SDK:

Hello, tested both on mobile and web and the snackbars are shown in front of the drawer screen as expected. It looks like issue #822 will be solved by this pr merge. Congrats. 👏  If there you need more test please let us know.

Hello, tested both on mobile and web and the snackbars are shown in front of the drawer screen as expected. It looks like issue #822 will be solved by this pr merge. Congrats. 👏  If there you need more test please let us know. @vnylbscr


issue on recognizing Javascript method - await JS.InvokeVoidAsync

[EDIT by guardrex to add code-fencing]
Description
Hi,
i am trying to invoke javascript method using await JS.InvokeVoidAsync as per described in the article. but it gives error has
Could not find method or method was undefined. PFB test sample used in .NET MAUI Blazor page(.razor)
@inject IJSRuntime JSRuntime;

<script>
  function displayTickerAlert1{
    console.log("displayTickerAlert1");
  };
</script>

in C#
@code {
    await JSRuntime.InvokeVoidAsync("displayTickerAlert1");
}

error as displayTickerAlert1 is not recognized(displayTickerAlert1  was undefined);
i have also tried defining method as below:
<script>
  window.displayTickerAlert1 = (symbol, price) => {
    alert(`${symbol}: $${price}!`);
  };
</script>

invoking in c#
await JS.InvokeVoidAsync("displayTickerAlert1", stockSymbol, price);

even this gives same error. Please help
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/javascript-interoperability/call-javascript-from-dotnet?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/javascript-interoperability/call-javascript-from-dotnet.md
Document ID
9e197a8b-2616-8363-0a15-38cac802e82e
Article author
@guardrex

I can't reproduce a problem with the example ...

Make sure you're placing the JS (<script>...</script>) in the wwwroot/index.html file or colocate a JS file SxS with the component per the guidance. Don't place scripts into Razor components (as the guidance states). The guidance is at ...
https://learn.microsoft.com/en-us/aspnet/core/blazor/javascript-interoperability/?view=aspnetcore-8.0#javascript-location
Otherwise, seek assistance from the community if you're still having trouble. We recommend the usual chats/forums ...

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


 It could look like this (example from once_cell):
static GLOBAL_DATA: Lazy<Mutex<HashMap<i32, String>>> = sync_lazy! {
    let mut m = HashMap::new();
    m.insert(13, "Spica".to_string());
    m.insert(74, "Hoyten".to_string());
    Mutex::new(m)
};

I am creating this issue to discuss what we can do with this exciting possibility :-)
Just to be clear, I am explicitly not suggesting that we should deprecate the current API and switch to the new shiny. There's a ton of code in the wild which uses lazy_static!, and that is great.
Nevertheless, I think the current API has some problems, and the possible new API has less of them! Specifically, the current lazy_static! macro is opaque: it has a somewhat unique syntax, which is Rustish, but is not exactly Rust, it creates a unique hidden type behind the scenes and the implementation is hard to follow. I think this are significant drawbacks, especially from the learnability perspective.
When a new rustecean asks "how can I have global data?", the typical answer is: "you need to lazily initialize data on the first access. This is what C++ and Java do at the language level, but Rust this is achieved via the lazy_static library". And then a rustecan goes to see how lazy_static is implemented, sees this and thinks "wow, this is almost as horrifying as STL implementations" (well, at least that was my reaction :D).
I'd want to argue that an explicit Lazy<T> would be clearer at the call site (no more magical unique types) and much easier to understand (you just Ctrl+B/F12/M-./gD and read the impl).
An interesting facet of the new API is that Lazy does not need to be static!
So, are folks excited about the possibility of getting rid of lazy_static! macro? I propose the following plan for this:

we extract sync::Lazy from once_cell and publish it as a separate rust-lang-nursery crate, sync_lazy, with the following API

pub struct Lazy<T, F = fn() -> T> { ... }

impl<T, F: FnOnce() -> T> {
  pub /*const*/ fn new(f: F) -> Lazy<T> { ... }
  pub fn force(this: &Lazy<T, F>) -> &T { ... }
}

impl <T, F: FnOnce() -> T> Deref for Lazy<T, F> {
  Target = T;
  fn deref(&self) -> &T { ... }
}

macro_rules! sync_lazy {
    ($($body:tt)*) => { ... }
}

sync_lazy crate uses parking_lot::Once. That way, we don't need to wait until non-static Once is stable, and we also give parking_lot some more testing, as was requested in https://github.com/rust-lang/rfcs/pull/1632 (hence, cc @Amanieu)

In the lazy_static readme, we point that one might try sync_lazy instead.

Here's the proposes sync_lazy implementation: https://github.com/matklad/sync_lazy

I like the direction this is headed in! Ultimately, I'd really like to see something like this in std due to its ubiquity and utility, so I'm appreciative of any effort towards that end. :-)
With that said, a dependency on parking_lot would probably stop me from using sync_lazy in practice. I think parking_lot is phenomenal, but the increase in the number of transitive dependencies doesn't "feel" proportional to me. Namely, one of my favorite things about lazy_static is that it doesn't bring in a whole bunch of extra dependencies. I would continue using it over sync_lazy for that reason alone.
With that said, this is a double edge sword, because I also like the idea of more people using and testing parking_lot. I think I just tend to be a bit more conservative with these types of things, so overall I like the idea of suggesting sync_lazy as a possible alternative!

With that said, a dependency on parking_lot would probably stop me from using sync_lazy in practice.

That is a valid concern. We need parking_lot for a Once::call_once which works for non-static Onces. This is coming to std in https://github.com/rust-lang/rust/pull/52239 (currently beta, I believe). So we can make parking_lot an optional (and probably default) dependency, and otherwise use ::std::sync::Once. That is, this exposes a tradeoff between "more dependencies" and "older rustc".
Now, https://github.com/rust-lang/rust/pull/52239 literally just removed the 'static bound, without changing implementation at all. So, I think we can also polyfill that for older rusts by just transmuting from &'a Once to &'static Once?
So, two questions:

how do you feel about making parking_lot default?
how do you feel about faking a 'static lifetime/

I'm not sure about the 'static thing. I'd have to go understand what's actually happening. :-)
In terms of making parking_lot the default... Not sure. lazy_static is often used as an internal dependency, so folks would need to re-export that feature all the way up the dependency chain, right? That kind of sounds like a drag, but honestly, it does sound like a fairly decent compromise to me.

so folks would need to re-export that feature all the way up the dependency chain, right?

Yep, that is correct. OTOH, if you care about number of deps, your deps are probably caring about that as well, and would use sync_lazy with parking-lot disabled/reexported :-) Also, because Lazy does not have to be static, you can have a large number of Lazy at runtime, so at least opt-in into potentially more efficient synchronization primitives is desired.
I've pushed updates that make parking_lot optional and default, employ the &'static "polyfill" for Once and remove usages of non-essential new features.
That gives use compatibility with Rust 1.24.0 an up, with or without parking-lot, on a somewhat questionable ground that pretending that non-static Once is static is OK :)

Cool! Do the fields here need to be public? We just finished removing the equivalent from lazy_static since it's technically a very tiny soundness problem.

Excellent observation @anp! I can't think of a way to make fields private: because we don't create a fresh type for per lazy instance anymore, we need to store the closure inside a struct, and that should work in const context.
What we can do, however, is to hide Once  behind a type with empty public interface. That should fix the soundness issue. Implemented in https://github.com/matklad/sync_lazy/commit/dedd4b51553d77d8c80349a2e8d7732968b6fa05.

No, this doesn't entirely fix the hole unfortunately :( What we can do is to split the State enum which stores either a T or an F into two options, and make the first one private. I am not quite sure its worth the effort to do so: current representation is more natural, and I don't think that subverting soundness via clearly private implementation details really counts. The proper fix here, of course, is to stabilize const_fn :)

Another potential problem with Lazys approach is that we have to use fn() -> T instead of impl FnOnce() -> T to be able to spell out a type for a static. This requires us to actually store the function pointer, thus Lazy is one pointer larger than a lazy static:

HashMap<i32, String>
()

lazy_static
48
16

sync_lazy
56
24

There's also an extra indirection during intialization, but that probably does not matter, because Once::call_once is cold and, in fact, already an indirect call.

I personally wouldn't mind if Lazy<T> became Lazy<T, F>. It'd require existential types but ultimately work better. You could also write Lazy<T, fn() ->T> to pointer stored if need be.

Status update: now lazy-static can be completely macro-free
static HASHMAP: Lazy<HashMap<u32, &'static str>> = Lazy::new(|| {
    let mut m = HashMap::new();
    m.insert(0, "foo");
    m.insert(1, "bar");
    m.insert(2, "baz");
    m
});

https://github.com/matklad/once_cell/blob/1be60cb16a5d5a6b18115d1d2d8b8b78f67f63cd/examples/lazy_static.rs#L6-L12
Still contains fn() -> T inside instead of ZST :'-(

I've just noticed that std's thread local variables also store function pointers: https://github.com/rust-lang/rust/blob/9ebf47851a357faa4cd97f4b1dc7835f6376e639/src/libstd/thread/local.rs#L80-L99

Any plans to implement something like @matklad has done? It would certainly reduce the magic.

Current status: proposing API for stdlib: https://github.com/rust-lang/rfcs/pull/2788

Current status: available in nightly with #![feature(once_cell)].
Tracking issue: https://github.com/rust-lang/rust/issues/74465

@matklad Can I use a #![feature(thread_local)] annotation on a variable initialized with #![feature(thread_local)]? I tried it and the compiler didn't complain, but I wanted to check if there are any caveats. I'm mostly going to run my code on an x86-64 architecture, so I'm okay with thread_local being unstable.
Also, I'm using this to write a thread local memory allocator as well. If you were to write something like this today, what would you use if you had to optimize for performance? Have you changed your opinion since you published the blogpost last year?


proposal: cmd/ach: -cost flag

Following from https://github.com/moov-io/ach/issues/356 (ach command line tool proposal) the NACHA rules specify a cost breakdown:

Per-Entry Fee (Jan 1 - Dec 31): $0.000145
Annual Fee: $144.00

We could estimate the cost per-file (or for a group of files) and return. At a later point we could factor this into file consolidation logic.
$ ach -cost -i customer1.ach -i customer2.ach
customer1.ach: $0.02
customer2.ach: $0.000145
Total: $0.020145

$ ach -cost -i customer*
customer1.ach: $0.02
customer2.ach: $0.000145
Total: $0.020145

Please upvote if you'd find this useful.

This issue was create a while back, @adamdecaf do you think this feature would still be useful?

Probably not as a CLI flag. We can revisit it later.


pip install ?

why don't add the package to pypi ?
if gist name is occupied, you can use other, like python-gist

Good idea!

Done. Now you can install it using pip install python-gist.


Vm package doesn't respect block overrides

vm package currently handles running tx but block overrides are not respected

gm, I'm setting up a project that uses tevm to do some calculations by calling locally compiled solidity libraries, but I'm running into the block gas limit. Is there a way to set an arbitrary block gas limit for these kinds of local scripts? I've tried using blockOverrideSet with a custom gasLimit, but it throws a different error.

Calling this not a bug. You can still do a stateless call. The correct way to change the gas limit is to update the block.
If we add tevmGetBlock and tevmSetBlock methods we can make this more ergonomic


gengraphs issue: Label in lower graph is wrong

generating a graph showing throughput per vector size, using
python gengraphs.py <file.xlsx> size
for the lower graph (in red), the y-axis is labelled "Throughput (Bytes/s)" but it should be labelled "Transactions/s".
The key has "throughput/vector size" and "throughput/vector size error region" where it should say "transactions" and "transactions error region"

fixed with commit 692efba


Resolve GitHub issue #50 "Delete Scenes"

Now this should actually work, at least everything's correct according to the docs and the parameter interface was already there.
But in my tests the API just does nothing for 10 seconds, then rejects my promise with following error:
Error: Expected to get event reply:3845092227
As I will go on vacation tomorrow, I'll just leave this here, hoping that someone can either fix it if I've done something wrong, or if it's an API bug, that one will get resolved 😄.

I'll open an item to take a look at deleteScenes to ensure it works on the service internally thanks meta


Support for asynchronous Service Bindings

OSB specification 2.14 added support for asynchronous Service Bindings (PR) and a new last operation endpoint for Service Bindings endpoint.
Feature: HCPCFS-2937

Pull Request Test Coverage Report for Build 5342

30 of 60 (50.0%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 88.886%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

broker/applications/osb-broker/src/api-controllers/middleware/index.js
6
7
85.71%

broker/applications/osb-broker/src/api-controllers/ServiceBrokerApiController.js
23
52
44.23%

Files with Coverage Reduction
New Missed Lines
%

broker/data-access-layer/db/src/DBManager.js
1
99.47%

Totals

Change from base Build 5319:
-0.3%

Covered Lines:
9591

Relevant Lines:
10407

💛  - Coveralls

Validation on k8s cluster: n-2 is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n-1 is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n-1 is succeeded.

Validation on k8s cluster: n-2 is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n-2 is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n-2 is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n-1 is succeeded.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n is succeeded.


E2E: go schedule main SLSA3 config-noldflags

Repo: https://github.com/ianlewis/example-package/tree/main
Run: https://github.com/ianlewis/example-package/actions/runs/2465596953
Workflow name: go schedule main SLSA3 config-noldflags
Workflow file: https://github.com/ianlewis/example-package/tree/main/.github/workflows/e2e.go.schedule.main.config-noldflags.slsa3.yml
Trigger: schedule
Branch: main
Date: Thu Jun  9 02:46:52 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2465711430
Workflow name: go schedule main SLSA3 config-noldflags
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.schedule.main.config-noldflags.slsa3.yml
Trigger: schedule
Branch: main
Date: Thu Jun  9 03:21:34 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2470238457
Workflow name: go schedule main SLSA3 config-noldflags
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.schedule.main.config-noldflags.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Thu Jun  9 18:08:55 UTC 2022
Tests are passing now. Closing this issue.


feature: keymaps action should be optional

Currently, which-key descriptions are automatically added for any keymap that defines options.desc, however to set a description for a "group" you must use plugins.which-key.registrations directly, which leads to (potentially related) keymap descriptions being declared in totally separate parts of a config.
If keymap's action was allowed to be null, then this could be used to register descriptions without defining an actual keymap.
You would need to manually assert that at least one of action and options.desc is non-null, panicking if both are null.

This is the behavior we had before.
We removed it when adding the aforementioned plugins.which-key.registrations option.
That being said, I get your point. I have no major reason to oppose this change.
What do you think @traxys ?

I don't feel strongly about this either. It just felt strange that you can use keymaps to register most of your key descriptions, but not all.
Looking ahead, if this is accepted and plugin-specific keymaps get refactored to be consistent with keymap, perhaps plugins.which-key.registrations would become redundant and end up being deprecated?

Actually, I remember now.
We used to allow this behavior but decided to remove it.
Basically, 1 entry in the keymaps option leads to one call of vim.keymap.set.
The latter does not support nil rhs argument. Hence, the behavior for specifying a keymap without an action does not make sense (if you forget about which-key.
We (at least I) don't want our core keymaps option to depend on a third-party plugin.


Make Potential Improvements

Great work!
I have made following improvements to the codebase.

Make use of camelCase instead of snake_case for defining variables.
Remove adonis-fold from the dependencies. All packages should be dependent upon the adonis-fold version installed by the user app (can explain more if required).
Make use of logging library instead of console.log.
Extend Mongorito.Model to have a base model and set property makePlain to make sure IoC container is not making instances of the model when using the make method and here's why.

Injecting a class another class using static get inject or by using make will create an instance of the class. Which means if I do make('App/Model/Post') the IoC will create an instance of the Post model and in case of Mongorito.Model we do not want that.

Methods like Post.all() are static.
End user should create the instances by themselves when persisting models.

Thanks @thetutlage, Now we can a base on how to do the new integration providers :)


How to make the bot stay in a certain area

Expected Behaviour
There is an area with multiple lured pokestops that I want the bot to stay at but it keeps wandering away.

There is a way to sort of do this, I used this method during testing.
Set your max steps in config to 1 and apply this patch :
http://pastebin.com/raw/Vsr2FE6h

Does the dev branch differentiate between lure catches and wild pokemon?

@Calcyfer Applied your patch and set max steps to 1. The bot seemed to target a very far away pokestop after this modification. I'm on the latest dev.

Same I'm having the same problem.

duplicate of #334

Duplicate of https://github.com/PokemonGoF/PokemonGo-Bot/issues/334
/closed


Token filters - flatten_graph [DOC]

What do you want to do?

[ ] Request a change to existing documentation
[x] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Create a separate page for Token filter: flatten_graph
Part of META issue: https://github.com/opensearch-project/documentation-website/issues/1483
*Version: all

@natebower I can take this one

@Naarcha-AWS ?

Parking this token filter as it would need to reference token filters which have not yet been expanded on


Lost Anguar code

Issue Type: Bug
I had a project of Angular and had multiple lines of code and components under it. When I opened the project after few weeks I see that all the codes and components as well as the ts files are lost. The build code is still present in the dist folder. But the actual source code is the initial code that you get when you start an Angular project from scratch. Can you please let me know why and how did this happen as now I have to write my whole code again.
VS Code version: Code 1.47.2 (17299e413d5590b14ab0340ea477cdd86ff13daf, 2020-07-15T18:22:06.216Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz (4 x 2712)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.89GB (4.30GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

simple-react-snippets
bur
1.2.3

vscode-docker
ms-
1.3.1

autoimport
ste
1.5.3

How do you know VS Code was responsible for the code gone missing? Could any other tool have deleted it? Did this happen with any other folder in your system?


create docstrings for func1 related to percentage change calculation

modification on function1: add input tyle, and modify returns.


Creating a migration dies in PHP 8 - stricter arguments don't like Util.php's usage of implode()

    public static function mapClassNameToFileName($className)
    {
        $arr = preg_split('/(?=[A-Z])/', $className);
        unset($arr[0]); // remove the first element ('')
        $fileName = static::getCurrentTimestamp() . '_' . strtolower(implode($arr, '_')) . '.php';

        return $fileName;
    }

In previous versions of PHP, you could do $array before $glue, but no longer. The implode() should now have the glue first.

Oops - using an old version of Phinx! Sorry, nvm me.


⚠ ClamAV has degraded performance

In a238993, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 198 ms

Resolved: ClamAV performance has improved in 03422a0.


Support TLS for RGW

With this patch, during cifmw ceph deployment, rgw deployment includes the TLS certificate if it is passed.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/ok-to-test

/approve


[cinder-csi-plugin] shrink image, remove unnecessary utils (#2233)

What this PR does / why we need it:
Which issue this PR fixes(if applicable):
fixes #2233
Special notes for reviewers:
I've added small shell script tools/csi-deps.sh.
It copies add utils which go-modules calls.

Release note:

NONE

/ok-to-test

I like where this is going. I wonder why the e2e tests aren't running against it. We definitely need to run those. I also think it's worth jumping directly to distroless.

Ah: https://github.com/kubernetes/test-infra/blob/1c2c42ad7b86c1390b10b5e4a17f8ec09d09ad7d/config/jobs/kubernetes/cloud-provider-openstack/provider-openstack-presubmits-release-master-config.yaml#L12
    run_if_changed: '^(pkg\/util\/|pkg\/openstack\/|cmd\/openstack-cloud-controller-manager\/|tests\/e2e\/cloudprovider\/)'

That should probably include Dockerfile changes. I'll submit a PR.

/test openstack-cloud-csi-cinder-e2e-test

Hopefully https://github.com/kubernetes/test-infra/pull/29485 would have made this run automatically.

@sergelogvinov The csi-cinder e2e test passed using debian as the base image. Do you want to update to a distroless base and run it again?

all images now from DISTROLESS_IMAGE 🎉

/test openstack-cloud-csi-cinder-e2e-test

/retest

I've got some bad news: I'm pretty sure cinder-csi-plugin-utils-check is never built, meaning we're just adding dead code here. The reason is that we build each end-target by name. buildx seems to understand the dependency tree, and because cinder-csi-plugin-utils-check isn't a dependency of any of the targets we build, it will never execute and therefore never fail.
I suspected this might be the case and ran make build-local-image-cinder-csi-plugin locally and looked at the output. I see it build cinder-csi-plugin-utils and then cinder-csi-plugin. However, if you want to double check you could deliberately add a failure to csi-deps-check.sh and see if it causes anything to fail.
csi-deps-check.sh itself is only 1.1k and executing it doesn't add anything to the image. I wonder if we just move the execution of it into the release image instead. We probably shouldn't add dead code to the build, though.

Yep, I wasn't clear here https://github.com/kubernetes/cloud-provider-openstack/issues/2233#issuecomment-1542153904, I thought we can add this stage to makefile (for ci) somewhere...
To run csi-deps-check.sh we need /bin/sh which i'd like to avoid.
As another idea:  Add COPY csi-deps-check.sh to image cinder-csi-plugin  from cinder-csi-plugin-utils-check stage (image) but it will not so clear "for us in future" )

Yep, I wasn't clear here #2233 (comment), I thought we can add this stage to makefile (for ci) somewhere...
To run csi-deps-check.sh we need /bin/sh which i'd like to avoid.

Of course.

As another idea: Add COPY csi-deps-check.sh to image cinder-csi-plugin from cinder-csi-plugin-utils-check stage (image) but it will not so clear "for us in future" )
# step 2: build tiny cinder-csi-plugin image with only necessary files
FROM --platform=${TARGETPLATFORM} ${DISTROLESS_IMAGE} as cinder-csi-plugin

COPY --from=cinder-csi-plugin-utils /dest /
COPY --from=cinder-csi-plugin-utils-check /tools/csi-deps-check.sh /bin/csi-deps-check.sh <--- here
COPY --from=builder /build/cinder-csi-plugin /bin/cinder-csi-plugin
COPY --from=certs /etc/ssl/certs /etc/ssl/certs

I actually like this idea. I'd just add a comment like:
# Copying csi-deps-check.sh simply ensures that the resulting image has a dependency on cinder-csi-plugin-utils-check and therefore that the check has passed
COPY --from=cinder-csi-plugin-utils-check /tools/csi-deps-check.sh /bin/csi-deps-check.sh

You hopefully aren't going to delete that without reading the comment right next to it.
Can you confirm that it works, though? e.g. Push a change here with a broken csi-deps-check.sh so we can see it fail.

Test case:
# echo "exit 1" >> tools/csi-deps-check.sh
# make build-local-image-cinder-csi-plugin
docker buildx build --output type=docker \
                --build-arg VERSION=v1.27.0-alpha.0-32-g71c3849f-dirty \
                --tag registry.k8s.io/provider-os/cinder-csi-plugin:v1.27.0-alpha.0-32-g71c3849f-dirty \
                --target cinder-csi-plugin \
                .
[+] Building 1.0s (17/27)
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 32B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for registry.k8s.io/build-image/debian-base:bullseye-v1.4.3                                                                                0.3s
 => [internal] load metadata for docker.io/library/alpine:3.17.3                                                                                0.0s
 => [internal] load metadata for registry.k8s.io/build-image/go-runner:v2.3.1-go1.20.3-bullseye.0                                                                                0.9s
 => [internal] load metadata for docker.io/library/golang:1.20.3                                                                                0.0s
 => [certs 1/2] FROM docker.io/library/alpine:3.17.3                                                                                0.0s
 => [builder 1/6] FROM docker.io/library/golang:1.20.3                                                                                0.0s
 => [cinder-csi-plugin-utils-check 1/5] FROM registry.k8s.io/build-image/go-runner:v2.3.1-go1.20.3-bullseye.0@sha256:ea665b97deab98ea4e373f9fe207852394b06e24caeacbd66ddf71f8632dec50             0.0s
 => [internal] load build context                                                                                0.1s
 => => transferring context: 11.41kB                                                                                0.0s
 => [cinder-csi-plugin-utils 1/4] FROM registry.k8s.io/build-image/debian-base:bullseye-v1.4.3@sha256:3fcf9bcc4949392155cde1f96591ba3eda092f4735a9cc856bf526d71f48af47                            0.0s
 => CACHED [cinder-csi-plugin-utils 2/4] RUN clean-install bash rsync mount udev btrfs-progs e2fsprogs xfsprogs                                                                                0.0s
 => CACHED [cinder-csi-plugin-utils 3/4] COPY tools/csi-deps.sh /tools/csi-deps.sh                                                                                0.0s
 => CACHED [cinder-csi-plugin-utils 4/4] RUN /tools/csi-deps.sh                                                                                0.0s
 => CACHED [cinder-csi-plugin-utils-check 2/5] COPY --from=cinder-csi-plugin-utils /dest /                                                                                0.0s
 => CACHED [cinder-csi-plugin-utils-check 3/5] COPY --from=cinder-csi-plugin-utils /bin/sh /bin/sh                                                                                0.0s
 => [cinder-csi-plugin-utils-check 4/5] COPY tools/csi-deps-check.sh /tools/csi-deps-check.sh                                                                                0.0s
 => ERROR [cinder-csi-plugin-utils-check 5/5] RUN /tools/csi-deps-check.sh                                                                                0.3s
------
 > [cinder-csi-plugin-utils-check 5/5] RUN /tools/csi-deps-check.sh:
#0 0.252 mount from util-linux 2.36.1 (libmount 2.36.1: selinux, smack, btrfs, namespaces, assert, debug)
#0 0.253 umount from util-linux 2.36.1 (libmount 2.36.1: selinux, smack, btrfs, namespaces, assert, debug)
#0 0.254 blkid from util-linux 2.36.1  (libblkid 2.36.1, 16-Nov-2020)
#0 0.254 blockdev from util-linux 2.36.1
#0 0.255 dumpe2fs 1.46.2 (28-Feb-2021)
#0 0.255        Using EXT2FS Library version 1.46.2
#0 0.256 fsck from util-linux 2.36.1
#0 0.258 mke2fs 1.46.2 (28-Feb-2021)
#0 0.258        Using EXT2FS Library version 1.46.2
#0 0.259 mke2fs 1.46.2 (28-Feb-2021)
#0 0.259        Using EXT2FS Library version 1.46.2
#0 0.260 mkfs.xfs version 5.10.0
#0 0.261 xfs_io version 5.10.0
#0 0.262 xfs_repair version 5.10.0
#0 0.263 xfs_growfs version 5.10.0
#0 0.264 btrfs-progs v5.10.1
#0 0.267 247
#0 0.268 findmnt from util-linux 2.36.1
------
ERROR: failed to solve: executor failed running [/bin/sh /tools/csi-deps-check.sh]: exit code: 1
make: *** [build-local-image-cinder-csi-plugin] Error 1

/lgtm

/retest-required

/retest

/retest

Ignore the manila-e2e-test, it's broken.
@zetaab @jichenjc is this good to go?
/lgtm

/test openstack-cloud-csi-manila-e2e-test

/override  openstack-cloud-csi-manila-e2e-test

/approve

Thank you so much for taking the time to review and provide feedback. I genuinely appreciate it.


support scan parquet file in reverse order

Describe This Problem
After #312, we only support scan parquet file in one order, ReversedFileReader cannot be used with ParquetExec
Proposal
Implement ReversedFileReader logic in datafusion's ParquetExec.
Additional Context
No response

ReversedFileReader has been removed.


Grab handles for ReorderableListView items

Demonstrate how to add "grab" handles to ReorderableListView items and custom widgets.
The "pick up and move" section of the Material Design spec indicates that a long-press-drag-release gesture can be used to move items. ReorderableListView supports moving items within a list with that gesture.
Sometimes it's useful to include a visual affordance that shows that an item can be moved, and optionally highlights while the item is being moved.  Such an affordance is often referred to as a "grab handle". It would helpful if the documentation demonstrated how to do include a grab handle in each reorderable list view item. It might also be useful to provide a utility grab handle widget.

Hey folks, we are ramping up a design to try to address this and other issues with ReorderableListView. We are tracking it with #66080 and in a design doc. Feedback welcome.

It seems to me like this can be closed as completed. I see a duplicate issue (https://github.com/flutter/flutter/issues/63709) that was completed, and the first example in the docs shows something that looks like grab handles to me.
Feel free to reopen if I'm wrong.


use customized panic handle

Use std::panic to set a customized handle to ignore force unwinding and prints customized panic message.
Possible problem:

If someone uses a library that sets another customized handler to handle panics, what would happen?

Close because it is not so urgent.


Next and previous search results not functioning correctly with filters

Fixed on test3

Now works OK
This can be closed
Geoff


Fix Doc Warnings

Fixes #482
What changes to the docs does this PR provide?
Fixes docs per some of the warnings
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Correctly picked the right branch to base the change off (master for new features, live for typos/improvements)
[ ] For new pages, used the provided template
[ ] For new features, added an entry in the Table of Contents
[x] Ran against a spell and grammar checker
[x] Contains NO breaking changes

Other information

Docs Build status updates of commit 94d741d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/controls/wpf-winforms/WindowsXamlHost.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 18c215c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/controls/wpf-winforms/InkCanvas.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WindowsXamlHost.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5e9b3fd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/controls/wpf-winforms/InkCanvas.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/InkToolbar.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WindowsXamlHost.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a1206b5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/controls/wpf-winforms/InkCanvas.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/InkToolbar.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/MapControl.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WindowsXamlHost.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 2eae4b8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/controls/wpf-winforms/InkCanvas.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/InkToolbar.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/MapControl.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/MediaPlayerElement.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WindowsXamlHost.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit c45f06d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/controls/wpf-winforms/InkCanvas.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/InkToolbar.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/MapControl.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/MediaPlayerElement.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WebView.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WindowsXamlHost.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f78c86d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/controls/wpf-winforms/InkCanvas.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/InkToolbar.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/MapControl.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/MediaPlayerElement.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WebView.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WebViewCompatible.md
:white_check_mark:Succeeded
View

docs/controls/wpf-winforms/WindowsXamlHost.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Incorrect description

The description is incorrect for this method.

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

ID: c452bd86-fa35-a48e-b5d5-9d8b91148fc6
Version Independent ID: ec5aa21c-9691-5ff9-799f-7f0fa1be8572
Content: setFilter - PowerApps
Content Source: powerapps-docs/developer/component-framework/reference/filtering/setfilter.md
Service: powerapps
GitHub Login: @Nkrb
Microsoft Alias: nabuthuk

@scottdurow Thanks for the feedback. We have updated the docs with the correct information and pushed to live. Closing the issue.


Added ability to run program by default for macOS and Linux

By default the compiled program will not run on macOS or Linux and the user must use chmod to enable the ability to execute.
By adding another step in the jobs for macOS and Linux the artifact will now run when the user downloads.

c7784b0

Thanks for the merge!
After testing this, it seems to have worked for Linux but not macOS.
Probably a perms issue. I will possibly look into it and follow up with another PR.

actions/upload-artifact@v4 will package product files into zip, and zip does not support permission management. To solve this problem, you need to package it yourself through tar.
https://github.com/actions/upload-artifact#permission-loss
- name: 'Tar files'
  run: tar -cvf my_files.tar /path/to/my/directory

- name: 'Upload Artifact'
  uses: actions/upload-artifact@v4
  with:
    name: my-artifact
    path: my_files.tar

actions/upload-artifact@v4 will package product files into zip, and zip does not support permission management. To solve this problem, you need to package it yourself through tar. https://github.com/actions/upload-artifact#permission-loss
- name: 'Tar files'
  run: tar -cvf my_files.tar /path/to/my/directory

- name: 'Upload Artifact'
  uses: actions/upload-artifact@v4
  with:
    name: my-artifact
    path: my_files.tar

Thanks for the reply. I found this out through a Post on StackOverflow and I'm working on a PR shortly.
It sure is a strange quirk!


can't find heading

I filled 'Clipped' for pre-defined header in daily note configuration (as shown in the figure), but every clipping all couldn't be generated in obsidian, a 'can't find heading' hint popped out simultaneously. After I didn't define the header, all were right. How I can eschew this problem? please help me, thanks!

Does your Daily Note template have a level 1(#) header called 'Clipped'?
This video may help
Or you can watch it here. https://docs.obsidianclipper.com

Does your Daily Note template have a level 1(#) header called 'Clipped'?
This video may help
Or you can watch it here. https://docs.obsidianclipper.com

Can level 2 header be supported?

Does your Daily Note template have a level 1(#) header called 'Clipped'?
This video may help
Or you can watch it here. https://docs.obsidianclipper.com

Can level 2 header be supported?

I am working on support for any level header. I will see if I can make it work. The challenge is around making sure that headings in the clipped data don't cause issues.

Humm, I could not find details in the video about customizing Daily Notes templates. I'm stuck with same problem. I can't use the pluggin. Too bad...

@fcavarretta sorry for such a late reply. Could you share the template that creates your daily note and the clipper settings you were using. Completely understand if you have already moved on at this point. Thanks


Add Support for Additional Java Binary Types

Java binaries can be packages in several formats that are currently not supported by log4jscanner.
Examples formats the tool currently lacks support of are:

PAR
KAR
SAR
RAR

We should already support PAR, KAR, and RAR files. Though IsJAR may need adjusting https://pkg.go.dev/github.com/google/log4jscanner/jar@main#IsJAR

An OSGi application is packaged as a JAR file, with extension .par. A PAR artifact offers several benefits:

https://docs.spring.io/s2-dmserver/2.0.0.M2/programmer-guide/html/ch04s02.html

A KAR file is essentially a jar (so a zip file) which contains a set of feature descriptor and bundle jar files.

https://karaf.apache.org/manual/latest/kar

Resource Adapter Archive (RAR) is regular jar file which is regular zip file with some predefined file structure (like manifest file). It could be read by any zip reader.

https://stackoverflow.com/a/30180261
No idea what the SAR format is though. Is that also just a ZIP file?
cc @ddworken


Does foreman support different stop signals?

In my appraisal of foreman I've LOVED everything except my uncertainty in how processes are stopped via signals. It appears that processes are only stopped by SIGKILL or SIGTERM. This seems unhelpful in certain circumstances where I know a certain signal will gracefully stop a process (e.g. QUIT for Resque). For certain processes SIGTERM or SIGKILL will likely be appropriate, but how can we handle cases where we know of a different signal that will be more beneficial?
Does foreman already support this? If I export to upstart, would foreman be able to dictate to upstart the shutdown signal to use? Apologies for not having this be a proper issue/feature request and no code attached, just not sure any other way to have these questions addressed. Thanks for your time.

I added a wiki page that describes how you can do this: https://github.com/ddollar/foreman/wiki/Custom-Signals

That wiki page doesn't address whether foreman is able to specify a kill signal when exporting to upstart.


One doubt: it's possible to the JobInfo create the job from Autofac container? If no, it's possible to set as singleton, to avoid create the class again every time the periodic run?
Thanks for the package!!

Please don’t abuse this area for support questions!!!
The jobinfo is only a descriptor, the jobinfo type is hydrated from the container.  Even if the container says it is a singleton, most of the time when the job runs (especially on Android), the container is being rebuilt anyhow.


strange character in update.sh

Hello,
everything works, but i get some strange character in the headline of the update.sh script.

If i open the update.sh script here on GitHub in raw, it shows the same character.

but in normal code view it's fine.

Any idea what this could cause?

These are unicode right and left arrows.
Right Arrow
Left Arrow
This is the screenshot of update.sh in Raw:

This is the screenshot when update.sh is executed in shell:

I mentioned under putty section in the last screenshot. Make sure whatever client you use it has UTF-8 enabled.

Ok thank you for the hint.
Are you viewing the raw on windows? I am on Mac and it does not show correct.
To make it easier for newbies, replacing these Unicode characters with some standard character like >> << would help.
Or if you want some fancy symbols, Nerdfonts is also great.
Only a suggestion.

Yes the github raw screenshot is from win machine but it looks the same in debian and ubuntu as well. Unicode is pretty much the standard across windows, unix and mac-os.
You can try copy/pasting the arrow into a document or display it in character viewer to see if the default font you are using has it. If you are able to view it using one of the these methods than it is the browser that is not able to render it. Firefox renders unicode charcters much better than Safari or Chrome.
The arrows I used above are basic UTF-8 arrows that are available across majority of the fonts in win and unix. They are also renderable in github which supports restricted unicode character set. You can check here various mac fonts have these arrows
I do not want to use any fancy characters, most of them require specific font to be installed. Anyways I will remove them in future release, they are not adding any value to the functionality.

Removed unicode arrows from update.sh
Commit


Support Casbin as the authorization module

Hi, Casbin is an authorization library that supports models like ACL, RBAC, ABAC.
Related to RBAC, Casbin has several advantages:

roles can be cascaded, aka roles can have roles.
support resource roles, so users have their roles and resource have their roles too. role = group here.
the permission assignments (or policy in Casbin's language) can be persisted in files or database (MySQL and Cassandra).

And you can even customize your own access control model, for example, mix RBAC and ABAC together by using roles and attributes at the same time. It's very flexible.
Casbin can provide more flexibility and security than the current authorization in api/auth. I can make PR if needed. Let me know if there's any question:) Thanks.

Hi @hsluoyz and thanks for your feedback.
I'm not really happy with the current implementation of our RBAC authorization model right now. Since  we're close to a release, I didn't dig into it yet but I'm definitely planning to rework this. So your comment is very timely!
If you want to give it a try and submit a PR, I'll be happy to review it!
My only question so far (after quickly scanned Casbin docs) is do we have to use dedicated files to define policies or can it be done with code only?
Thanks!

Hi @bquenin ,
Thanks for the response!
It's not necessary to reply on files for both the model and the policy rules. I have updated the docs, please see here: https://github.com/casbin/casbin#what-if-i-dont-want-to-reply-on-files-conf-csv

Hi @bquenin ,
I have an initial plan here. This plan is the first step. So I try to modify the original code as least as possible to make a smooth transition.

I noticed the subject is not used because it's always <.*>, e.g., Subjects:  []string{"<.*>"}. So I just remove it in Casbin policy.
The Fulfills() function has many checkings and is very complicated. So I decide not to touch it in this initial plan.

So here's the Casbin model:
[request_definition]
r = res, act, owner, store, res_id

[policy_definition]
p = res, act, roles, levels

[policy_effect]
e = some(where (p.eft == allow))

[matchers]
m = r.res == p.res && regexMatch(r.act, p.act) && fulfills(r.owner, r.store, r.res_id, p.roles, p.levels)

Here's the Casbin policy rules for the 11 default policies like usersAdminByThemselves, usersCanLeaveOrganizations, etc.
p, amprn:user, *, null, null

p, amprn:organization, leave, null, null
p, amprn:organization, *, owner, null

p, amprn:team, *, owner, null
p, amprn:team, create, (owner)|(member), null

p, amprn:stack, read, null, read
p, amprn:stack, (read)|(update), null, write
p, amprn:stack, *, owner, admin

p, amprn:dashboard, read, null, read
p, amprn:dashboard, (read)|(update), null, write
p, amprn:dashboard, *, owner, admin

The policy can be even compressed by integrating the stack and dashboard rules into something like:
p, amprn:(stack|dashboard), read, null, read
p, amprn:(stack|dashboard), (read)|(update), null, write
p, amprn:(stack|dashboard), *, owner, admin

Let me know if you have any questions:)


Could you mention in the README that Python3 is necessary for this to run?

Hello,
thank you for publishing this code! I've been looking for an easy-to-use variable length TensorFlow autoencoder, and this one seems to do exactly what I need.
Would you consider mentioning in the README that the code requires Python 3.x? It took me a while to figure out based on the error messages; also, the "if PY3:" part in main.py was a bit misleading, as I thought both Python versions would work.
For example, in lr_classes.py, class LRFunc(): had to be changed to class LRFunc(object):. Also, the scipy and matplotlib versions in requirements.txt were not available on my system for Python 2.x. Then there were some other errors, at which point I switched to Python 3.
Thanks!

Thanks for the feedback. I did try to make it p2 and p3 compatible but obviously I missed some.

Should be py2 compatible now.

Hello,
I am using python 3.6, it reports ImportError: cannot import name 'SIGUSR1', I would like to ask which version of python3 are you using? Thanks

Hello,
thank you for publishing this code! I've been looking for an easy-to-use variable length TensorFlow autoencoder, and this one seems to do exactly what I need.
Would you consider mentioning in the README that the code requires Python 3.x? It took me a while to figure out based on the error messages; also, the "if PY3:" part in main.py was a bit misleading, as I thought both Python versions would work.
For example, in lr_classes.py, class LRFunc(): had to be changed to class LRFunc(object):. Also, the scipy and matplotlib versions in requirements.txt were not available on my system for Python 2.x. Then there were some other errors, at which point I switched to Python 3.
Thanks!

Hello,
I am using python 3.6, it reports ImportError: cannot import name 'SIGUSR1', I would like to ask which version of python3 are you using? Thanks


Fix org package owner permissions

Addition to #19735 to fix #19583.
Old code did not respect owner visibility and the organization access calculation was wrong if the user was not a member.

@KN4CK3R this permissions should be checked via integration tests ... so we do check the whole stack ...

:rocket:


add remap keys menu

imo this would look like a keyboard map in localStorage and only storing non-ordinary ones

related #67


Add provider/sponsor name to fvz servers description

God damn, I should check the csv file before commiting ._.