[ADD ME TO THE ORGANIZATION]

Name: Parth Mandale
Location: Pune, Maharashtra
Interest: Web Development, Open Source, web3
Discord username(optional):- Parth Mandale#8947
Why do you want to join?

I want to join because I want to connect with like-minded people in tech and want to build a network where I can learn and grow together in open source community.

You can also join our Discord community here
Feel free to check out other cool repositories of the DevsInTech Community here.

@Susmita-Dey Please review my PR and Invitation.

@Parthmandale Thanks for your interest. Invitations have been sent to you. Kindly accept it and make your membership public.


[WIP] Implement std::fmt::Debug for Map and TileLayer manually

Self-explanatory

Didn't see this was a draft -- Are you planning to add anything else?

Didn't see this was a draft -- Are you planning to add anything else?

I was checking TileLayer, FiniteTileLayer, InfiniteTileLayer and map_wrapper! macro to see how I could implement Debug for these but it seems they are already done.

@aleokdev This seems like it would not require rewriting the whole implementation for Map. This, however, would add extra to compile time as we will introduce an extra dependency.
If you find this viable, I could go down this path. :)

It's ok, we'll do it manually - Same thing we have done for Error (we could've used thiserror but chose not to)

Well, I'm going to check TileLayer stuff after I wake up. Thank you for your time. :)

@aleokdev
I've checked the TileLayer. Apparently, it is an enum with FiniteTileLayer and InfiniteTileLayer, both of which implement Debug manually (well, at least their inner data FiniteTileLayerData and InfiniteTileLayerData do), and they do not seem to include Vecs to their debug-print.
https://github.com/mapeditor/rs-tiled/blob/f86e079fc2ca9de362ed576d2ae8c21636bf479d/src/layers/tile/finite.rs#L19-L26
https://github.com/mapeditor/rs-tiled/blob/f86e079fc2ca9de362ed576d2ae8c21636bf479d/src/layers/tile/infinite.rs#L18-L22
So, I think it's good to go. Feel free to merge. :beer:

Great, thank you!


Some metadata not shown in Snow Leopard

Probably being drawn as black text. The background is also black...

After the change in SHA: b3c132f it looks OK.


Potential bug on Tails v4.12 when installing .deb files [/usr/local/sbin/tails-additional-software apt-pre apt_hook_pre()]

See:

MVP of VSCode On TailsOS #1

How to reproduce the error
wget https://go.microsoft.com/fwlink/?LinkID=760868 -O /tmp/vscode.deb
sudo apt update
sudo apt install /tmp/vscode.deb

complete log
amnesia@amnesia:~$ wget https://go.microsoft.com/fwlink/?LinkID=760868 -O /tmp/vscode.deb
--2020-10-23 15:59:58--  https://go.microsoft.com/fwlink/?LinkID=760868
Resolving go.microsoft.com (go.microsoft.com)... <IP_ADDRESS>
Connecting to go.microsoft.com (go.microsoft.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://update.code.visualstudio.com/latest/linux-deb-x64/stable [following]
--2020-10-23 16:00:01--  https://update.code.visualstudio.com/latest/linux-deb-x64/stable
Resolving update.code.visualstudio.com (update.code.visualstudio.com)... <IP_ADDRESS>
Connecting to update.code.visualstudio.com (update.code.visualstudio.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://az764295.vo.msecnd.net/stable/d2e414d9e4239a252d1ab117bd7067f125afd80a/code_1.50.1-1602600906_amd64.deb [following]
--2020-10-23 16:00:04--  https://az764295.vo.msecnd.net/stable/d2e414d9e4239a252d1ab117bd7067f125afd80a/code_1.50.1-1602600906_amd64.deb
Resolving az764295.vo.msecnd.net (az764295.vo.msecnd.net)... <IP_ADDRESS>
Connecting to az764295.vo.msecnd.net (az764295.vo.msecnd.net)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 64463220 (61M) [application/x-debian-package]
Saving to: ‘/tmp/vscode.deb’

/tmp/vscode.deb                                      100%[=====================================================================================================================>]  61.48M   614KB/s    in 1m 52s

2020-10-23 16:01:58 (562 KB/s) - ‘/tmp/vscode.deb’ saved [64463220/64463220]

amnesia@amnesia:~$ sudo apt update

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for amnesia:
Hit:1 tor+http://sdscoq7snqtznauu.onion/torproject.org buster InRelease
Hit:2 tor+http://vwakviie2ienjx6t.onion/debian buster InRelease
Hit:3 tor+http://umjqavufhoix3smyq6az2sx4istmuvsgmz4bq5u5x56rnayejoo6l2qd.onion 4.12 InRelease
Hit:4 tor+http://vwakviie2ienjx6t.onion/debian bullseye InRelease
Hit:5 tor+http://vwakviie2ienjx6t.onion/debian buster-backports InRelease
Hit:6 tor+http://vwakviie2ienjx6t.onion/debian sid InRelease
Hit:7 tor+http://sgvtcaew4bxjd7ln.onion buster/updates InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.
amnesia@amnesia:~$ sudo apt install /tmp/vscode.deb
[sudo] password for amnesia:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'code' instead of '/tmp/vscode.deb'
The following package was automatically installed and is no longer required:
  libpcre2-posix0
Use 'sudo apt autoremove' to remove it.
The following NEW packages will be installed:
  code
0 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.
Need to get 0 B/64.5 MB of archives.
After this operation, 276 MB of additional disk space will be used.
Get:1 /tmp/vscode.deb code amd64 1.50.1-1602600906 [64.5 MB]
[INFO] Saving package changes
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 297, in __getitem__
    rawpkg = self._cache[key]
KeyError: 'code'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/sbin/tails-additional-software", line 672, in <module>
    apt_hook_pre()
  File "/usr/local/sbin/tails-additional-software", line 459, in apt_hook_pre
    if not apt_cache[package_name].is_installed:
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 299, in __getitem__
    raise KeyError('The cache has no package named %r' % key)
KeyError: "The cache has no package named 'code'"
E: Sub-process /usr/local/sbin/tails-additional-software apt-pre returned an error code (1)
E: Failure running script /usr/local/sbin/tails-additional-software apt-pre
amnesia@amnesia:~$

/usr/lib/python3/dist-packages/apt/cache.py, around 299
    def __getitem__(self, key):
        # type: (object) -> Package
        """ look like a dictionary (get key) """
        try:
            key = str(key)
            rawpkg = self._cache[key]
        except KeyError:
            raise KeyError('The cache has no package named %r' % key)

        # It might be excluded due to not having a version or something
        if not self.__is_real_pkg(rawpkg):
            raise KeyError('The cache has no package named %r' % key)

        pkg = self._rawpkg_to_pkg(rawpkg)

        return pkg

/usr/local/sbin/tails-additional-software, line 415-466
def apt_hook_pre():
    """Subcommand to handle Dpkg::Pre-Install-Pkgs."""
    _exit_if_in_live_build()
    logging.info("Saving package changes")

    apt_cache = apt.cache.Cache()

    installed_packages = []
    removed_packages = []

    line = sys.stdin.readline()
    if not line.startswith("VERSION 3"):
        raise ASPDataError("APT data is not version 3")
    line = sys.stdin.readline()
    # Ignore configuration space, which ends with an empty line
    while line != "\n":
        line = sys.stdin.readline()
    # Package action lines
    for line in sys.stdin:
        # Package action lines consist of five fields in Version 2: package
        # name (without architecture qualification even if foreign), old
        # version, direction of version change (< for upgrades, > for
        # downgrades, = for no change), new version, action. The version
        # fields are "-" for no version at all (for example when installing
        # a package for the first time; no version is treated as earlier
        # than any real version, so that is an upgrade, indicated as - <
        # 1.23.4). The action field is "**CONFIGURE**" if the package is
        # being configured, "**REMOVE**" if it is being removed, or the
        # filename of a .deb file if it is being unpacked.
        #
        # In Version 3 after each version field follows the architecture of
        # this version, which is "-" if there is no version, and a field
        # showing the MultiArch type "same", "foreign", "allowed" or "none".
        # Note that "none" is an incorrect typename which is just kept to
        # remain compatible, it should be read as "no" and users are
        # encouraged to support both.
        #
        # Example:
        #
        # colordif - - none < 1.0.16-1 all none **CONFIGURE**
        package_name, old_version, old_arch, old_multiarch, direction, \
                new_version, new_arch, new_multiarch, action = line.split()
        if action.endswith(".deb"):
            # Filter packages that will only be upgraded
            if not apt_cache[package_name].is_installed:
                installed_packages.append(package_name)
        elif action.endswith("**REMOVE**"):
            removed_packages.append(package_name)

    result = {"installed": installed_packages, "removed": removed_packages}
    with open(ASP_STATE_PACKAGES, 'w') as f:
        json.dump(result, f)

/usr/local/sbin/tails-additional-software, hotfix
sudo gedit /usr/local/sbin/tails-additional-software
original
        if action.endswith(".deb"):
            # Filter packages that will only be upgraded
            if not apt_cache[package_name].is_installed:
                installed_packages.append(package_name)

hofixed
We check if apt_cache[package_name] is valid before trying to check if is_installed
        if action.endswith(".deb"):
            # Filter packages that will only be upgraded
            if (package_name not in apt_cache) or apt_cache[package_name].is_installed:
                installed_packages.append(package_name)


/host_run/dbus is being deprecated in favour of /host/run/dbus/system_bus_socket on resin 2.0 devices

/host_run is deprecated, so it's a good moment to switch to /host/run/dbus/system_bus_socket

In general, shouldn't we supply/set that variable in the container by default?

@imrehg there are cases where people don't want to use the session DBus. they only want ipc within the container, so auto setting this ENV Var would make this very strange for those guys.


chore(ci): parallelise noir-projects CI

This PR splits all of the tests for various noir projects so that they can be run in parallel.

This halves the CI times relative to #9057 as we don't need to wait for the TXE in order to start running tests on the protocol circuits.


feat(CX-3066): Add MyC Insights web tracking events

The type of this PR is: Feature

This PR resolves CX-3066
Description
This PR adds ClickedMyCollectionInsightsMedianAuctionRailItem event to My Collection Insights events for the web

PR Checklist (tick all before merging)

[ ] If I've added a new file to the tree I've exported it from the common index.ts
[x] I've added comments with examples for any new interfaces and ensured that they're in the docs
[x] No platform-specific terminology has been used outside of click and tap (platform is inferred by the DB storing events)

Niice

:rocket: PR was released in v4.67.0 :rocket:


Fully functional tinyg driver

Still need to figure out the best way to include the tinyg lib, but this is the code I am running with pretty solid today

Anthony, looks good!
One thing leaps out at me. The hardwiring of devname in the mocha tests results in tests that only work on your machine. The only thing I can think of would be to make it possible for folks to override via system environment variable. Perhaps:
var devName = process.env.TINYG_SERIAL || "/dev/ttyUSB0";
Does that actually work on your machine? If so please amend code so I can pull them all in.

I like that Karl, and I tested it to work great


Loading a my regular config(not visuals) causes engis buildings to be placed behind my model

Fedoraware Version Date:
Config used:
https://files.catbox.moe/tj4wog.fw
Description:
whenever i load my regular config it causes the buildings i place to be placed behind myself. ive tried turning off all things that were turned on for the config and it still did not fix the issue
Steps to reproduce:

[x] I am able to consistently reproduce this error

Steps to reproduce the behavior:

Enable Hacks config
Play engineer and place a building
Notice it is placed behind yourself

[x] I have included the steps to reproduce to the best I am able to share.

Not my biggest issue just annoying af

Sorry, i forgot to give it the bug tab (i am very new to github :(.    )

nevermind i fixed it (idk how i just turned on everything manually and it fixed it)

what a WACKY bug!


how to Add《web_socket_channel: 1.0.12 &   quickclient: 0.1.0》

In my app ,I want to use package of《web_socket_channel: 1.0.12 ，quickclient: 0.1.0》as a library.

In  <pubspec.yaml> add
dependencies:
web_socket_channel: 1.0.12
quickclient: 0.1.0

2.Install it
$ flutter packages get
it's running，but  it's  fail！

it's running，but it's fail!

You did not post how it failed, so it is unlikely that someone can help you. It seems like the formatting might be off?
Something like:
dependencies:
  web_socket_channel: 1.0.12
  quickclient: 0.1.0


Can I pass additional flags when building benchmark?

I often use LTO with swift bulid --experimental-lto-mode=full -Xswiftc -experimental-hermetic-seal-at-link.
Can I pass these flags to swift-build when running swift package benchmark? If so, how do I do?

I think just adding them to your binary target in Package.swift should do what you want - did you try it?

I think just adding them to your binary target in Package.swift should do what you want - did you try it?

Only the swiftc flags can be passed in Package.swift, not the swift-build flags.

To illustrate with the example given in my first comment, -experimental-hermetic-seal-at-link is a flag of swiftc and --experimental-lto-mode=full is a flag of swift-build.

Ah. Good question, will need to investigate if there's support in the swiftpm api for specifying this for builds, as that's what we're using to build the targets...

@hassila Thank you, but I don't think #262 resolves this issue because --experimental-lto-mode is not a flag of swiftc. It's a flag of SwiftPM.

It seems to work? I tried specifically with the command at
https://github.com/ordo-one/package-benchmark/releases/tag/1.25.0

The ones available to specify through the SwiftPM API is:
    /// Parameters and options to apply during a build.
    public struct BuildParameters {

        /// Whether to build for debug or release.
        public var configuration: PackagePlugin.PackageManager.BuildConfiguration

        /// Controls the amount of detail in the log returned in the build result.
        public var logging: PackagePlugin.PackageManager.BuildLogVerbosity

        /// Whether to print build logs to the console
        public var echoLogs: Bool

        /// Additional flags to pass to all C compiler invocations.
        public var otherCFlags: [String]

        /// Additional flags to pass to all C++ compiler invocations.
        public var otherCxxFlags: [String]

        /// Additional flags to pass to all Swift compiler invocations.
        public var otherSwiftcFlags: [String]

        /// Additional flags to pass to all linker invocations.
        public var otherLinkerFlags: [String]

        public init(configuration: PackagePlugin.PackageManager.BuildConfiguration = .debug, logging: PackagePlugin.PackageManager.BuildLogVerbosity = .concise, echoLogs: Bool = false)
    }

Sorry, I'll try it out.

Please give it a try and see if it does what you expect, let me know how it works out!

(those options were with a Swift 6 toolchain, "experimental-lto-mode" was renamed AFAICT)

Hmmm, reading through https://forums.swift.org/t/pitch-support-lto-for-swift/67379 it seems it may not work as you suggest, it may be that a new SwiftPM API is needed to make it possible...

If you haven't read this yet, it's worth a read.
https://github.com/swiftlang/swift-package-manager/pull/6611
The following sentence is particularly important. If you use swiftc's lto option, it does not generate intermediate products in the correct location. To solve it, --experimental-lto-mode was added to SwiftPM.

as well as place them in the proper output location.

And it has not been renamed.
https://github.com/swiftlang/swift-package-manager/blob/74f06f8a7fd6b4c729e474dee34db66319d90759/Sources/CoreCommands/Options.swift#L508

Ah, that was why I was spammed with bc files ;-)
It seems we need some way to specify the LTO mode when using the SwiftPM API in BuildParameters then unless I'm missing something, would you mind file a case on SPM requesting it? Guess they might wait to support it until it is an official feature though...

Please open a new issue later for supporting such feature in SwiftPM - this issue is sorted in the sense that arbitrary swiftc flags now can be passed - something else is needed for the full scope that you need...

OK, I'll create new issues in swiftlang/swift-package-manager and ordo-one/package-benchmark.
By the way, the command you have written in the release note will cause the following errors.
$ swift package --package-path Benchmarks clean
$ swift package --package-path Benchmarks benchmark
...
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/BenchmarkTool.build/Command+Helpers.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/BenchmarkTool.build/FilePath+Additions.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/BenchmarkTool.build/FilePath+DirectoryView.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/BenchmarkTool.build/String+Additions.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/ComplexModule.build/Arithmetic.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/ComplexModule.build/Complex.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/ComplexModule.build/Differentiable.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/ComplexModule.build/ElementaryFunctions.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/Histogram.build/Histogram.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/Numerics.build/Numerics.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/RealModule.build/AlgebraicField.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/RealModule.build/ApproximateEquality.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/RealModule.build/AugmentedArithmetic.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/RealModule.build/Double+Real.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/RealModule.build/ElementaryFunctions.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/RealModule.build/Float+Real.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/RealModule.build/Float16+Real.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/RealModule.build/Float80+Real.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/RealModule.build/Real.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/RealModule.build/RealFunctions.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/CInterop.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/Constants.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/Errno.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/Exports.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/FileDescriptor.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/FileHelpers.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/FileOperations.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/FilePath.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/FilePathComponentView.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/FilePathComponents.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/FilePathParsing.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/FilePathString.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/FilePathSyntax.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/FilePathWindows.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/FilePermissions.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/Mocking.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/PlatformString.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/Syscalls.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/SystemString.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/Util.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/UtilConsumers.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/SystemPackage.build/WindowsSyscallAdapters.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/TextTable.build/FancyGridFormat.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/TextTable.build/GridFormat.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/TextTable.build/HtmlFormat.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/TextTable.build/LatexFormat.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/TextTable.build/OrgFormat.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/TextTable.build/PipeFormat.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/TextTable.build/PlainFormat.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/TextTable.build/PsqlFormat.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/TextTable.build/RstFormat.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/TextTable.build/SimpleFormat.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/TextTable.build/String+Util.swift.o'
clang: error: no such file or directory: '/home/kebo/zyphy/Benchmarks/.build/aarch64-unknown-linux-gnu/release/TextTable.build/TextTable.swift.o'
[29/30] Linking BenchmarkTool

Benchmark failed to build the BenchmarkTool in release mode.
error: buildFailed

It seems that this is because the *.bc files are generated outside the .build directory.

Funny, I only tried it in macOS - wonder if there is some flag to direct the .bc output?!

(I used the Xcode 16.1 beta toolchain)


Modal positioning with dynamic content

If your modal has dynamic content that increases the vertical size of a modal, the modal scroll for out of content viewport doesn't work.
http://jsfiddle.net/hg2n5zn8/1/
^ Problem Modal shows the bug, 'Good' Modal shows what I would expect to happen after expanding the content.
This may be an expected limitation of the modal component, feel free to consider this a feature request.

Normally you need setting the observeChanges to true, but that doesn't work actually with your sample because, the MutationObserver is configuree with 'childList' and 'subtree' notify but not with 'attributes'.
To solve you problem you can after show your data, refresh the modal like this : http://jsfiddle.net/hg2n5zn8/3/

thx!


Ensure working with OVS works

WIP
DO NOT MERGE YET
Initial commit 6c4e930 should fix vrouter, at least doesn't break the non-OVS environment: https://beta-jenkins.mcc.schubergphilis.com/job/cosmic/job/0002-tracking-repo-branch-build/136/

Using OVS  https://github.com/MissionCriticalCloud/bubble-toolkit/pull/129
and running full set of tests: https://beta-jenkins.mcc.schubergphilis.com/job/cosmic-dev/job/0020-tracking-repo-build/48/

When using "just" the current environment/switches: https://beta-jenkins.mcc.schubergphilis.com/job/cosmic/job/0020-tracking-repo-build/480/


Nele

I added the Grants and Projects section with the grants/projects that Kevin asked me to add:

ELFF-project (e-learning)
NEH grant
NSF grant
Nvidia grant

很好


Fix adding a column with a foreign key constraint in SQLite

If more than one query is passed to queryArray(), the statement producer of every query has to be executed.

Released in 0.95.11


Microsoft Python Language Server - Excessive Memory Usage

Issue Type: Bug
Python Language Server uses ~16-18 GB RAM on a 24 GB RAM laptop. Causing my memory usage to hang around 95%. It's also chewing through disk with 20-40 MB/s. It's a hungry, hungry hippo.

Restarted and after 10 minutes it is at about 1.2 GB RAM with very low disk usage.
VS Code version: Code 1.26.1 (493869ee8e8a846b0855873886fc79d480d342de, 2018-08-16T18:38:57.434Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz (8 x 1896)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
23.84GB (0.67GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

gc-excelviewer
Gra
2.1.26

r
Iku
0.6.1

rainbow-csv
mec
0.5.0

mssql
ms-
1.4.0

anaconda-extension-pack
ms-
1.0.0

python
ms-
2018.8.0

PowerShell
ms-
1.8.4

vscode-yaml
red
0.0.15

gitblame
wad
2.4.4

Hi @falonso-caa, thanks for the report!
First, could you please verify for us that you are indeed running the Python Language Server and not Jedi? That is, your settings should have 'Python: Jedi Enabled' unchecked, or the settings.json file should have "python.jediEnabled": false in it.
Second, if you've verified that you are not using Jedi, could you please try capturing the information in the terminal windows and adding that information here? You can see the terminal information we request in our default issue template.
Third, if you are using the Python Language Server, what happens when you use Jedi?
How large is the codebase you are working in? Is there a way we can have a look (ie. is it on Github?).

Hello @d3r3kk,
It does appear that I have Jedi enabled. Is the princess in another castle?
Unfortunately, the code base is proprietary so I don't think I can share details.

Does the problem go away if you disable Jedi?

Yes, it does appear that the problem goes away with Jedi disabled. Thanks for the help!

Awesome!


Merge breaking change

I noticed a (undocumented) breaking change in the R.merge function between v0.18.0 and v0.19.0.
Reproduction:
R.merge({a: 5}, undefined)

Behaviour in v0.18.0
Behaviour in v0.19.0

As soon as I have a bit of time I'll try to figure out the cause of the regression and prepare a PR for it. For now, I'll just open the issue. :smiley:

Though this is a behaviour change, I don't consider it a regression. R.merge was not and is not documented to accept null or undefined: it operates on two objects. The previous implementation happened to treat undefined as equivalent to {} due to its use of keys, which for some reason does not throw when applied to undefined.
This is a situation where sanctuary-def-style type checking—discussed in #1125—would have prevented a "regression" by not allowing the invalid use in the first place.

Hi @davidchambers,
good point. Without type-checking it is indeed difficult to know/predict whether or not the function will be called correctly (unfortunately undefined is often slip through).
Right now though R.merge has an inconsistent behaviour when it comes to non objects, which makes using it fairly confusing.
I would suggest either adding a runtime type check - like in the case of R.test - or defaulting the input parameters to the empty object in case they are not objects to begin with, sort of how R.keys defaults to the empty array if its input is not an object.

I'll let @CrossEye respond to this. My position on run-time type checking is well documented. ;)

Sorry, just catching up on some old issues.
While I agree that this is not technically a regression, as we didn't document any behavior for non-objects, I believe the 0.18 behavior is what we would prefer.  I especially like this:

defaulting the input parameters to the empty object in case they are not objects to begin with, sort of how R.keys defaults to the empty array if its input is not an object.

I especially like this:

defaulting the input parameters to the empty object in case they are not objects to begin with, sort of how R.keys defaults to the empty array if its input is not an object.

I'm not fond of ad hoc polymorphism. R.keys(null) is a type error, as far as I'm concerned. ;)

typeof null; //=> "object"

:smile:
This is definitely something on which we disagree.  I think that we should most often be able to give reasonable behavior when null or undefined is supplied in place of an object.  To me we should do so in these cases.  Since null has no keys, R.keys(null) should simply return [].

c'mon @CrossEye, in any reasonable language keys(null) would be a type error. Or null would not exist. But here we are

Since null has no keys, R.keys(null) should simply return [].

Similarly, R.inc('XXX') should evaluate to NaN presumably?
The problem with failure values such as NaN is they allow failures to propagate implicitly. I'd prefer either to be forced to handle failures explicitly, or to have my program crash so I know what needs fixing. :)

c'mon @CrossEye, in any reasonable language keys(null) would be a type error. Or null would not exist. But here we are

Yes, here we are, writing a Javascript library for Javascript developers.  This is one of those places where I don't think the behaviours from other languages are particularly relevant.

Since null has no keys, R.keys(null) should simply return [].

Similarly, R.inc('XXX') should evaluate to NaN presumably?

I don't see it myself.  I see a function as answering a question more than performing an operation.  keys(val) answers the question "What are the keys of val?"  inc(n) answers the question "What is the successor to n?"  The first question has a reasonable answer for many values other than the expected input, and I have no problem supplying that.  The second one generally doesn't, although clearly we might find non-integer data types for which it is, in fact, appropriate.
What are the keys of null?  Well, it doesn't have any.  Neither does {}.  They deserve the same answer as far as I can tell.  The alternative is an exception.  I'm very loathe to throw exceptions.  Exceptions do not compose.  They return the answer "Hey, dummy, you don't know what you're doing here!"  To me, that's only acceptable when there is no reasonable alternative.
Such is the case with inc('XXX').  There is no reasonable answer.  There is no successor to 'XXX', and NaN certainly is not a useful answer to that question.  That might fall out of an implementation, and we might live with it, but it should never be considered desirable or correct behavior.  Nor should the current behaviour, inc('XXX'); //=> '1XXX'.  Here I would absolutely consider throwing as a possible last resort.

The problem with failure values such as NaN is they allow failures to propagate implicitly. I'd prefer either to be forced to handle failures explicitly, or to have my program crash so I know what needs fixing. :)

That's really useful for a certain style of application, and a certain kind of data.  It works well if you have reasonably fixed inputs that you can readily recreate, something like batch jobs, or well-logged server-side work.  If you have to work with user-facing applications and inconsistent -- perhaps even incoherent -- input streams, then code that will crash an application unnecessarily is simply a hazard.  You won't appreciate that keys(null) throws an exception if there is a possible null supplied to keys when, "Well, I had put fourteen items in my shopping cart, then deleted numbers three, seven, and nine, but added back number seven twice before dragging the coupon from the other window (did I mention the coupon already?) to the coupon box, and typing in my credit card number but not tabbing out of the field, merely clicking on the submit button.  This doesn't happen every time, mind you, but at least every fifth time I try it.  It seems more likely to happen if I have both GMail and Facebook open in other tabs, but that might be just coincidence."  In that situation, if the code can recover well enough to proceed without obvious error, without an application-crashing exception, then you're probably much happier.

I'm very pleased not to be responsible for debugging that shopping cart bug. :stuck_out_tongue_winking_eye:


chore: implement a better cart in headless-ssr-commerce sample

https://coveord.atlassian.net/browse/KIT-3681
This PR implements a proper cart in our samples.
To achieve this, I created server actions that simulate a server state by using cookies (in memory state was not possible with both server action and route handlers) in @actions/cart.ts. During the pages first load we call the getCart server action to get the initialState.
I also created a util file in @utils/cart.ts where there are functions for every cart use case. In each of those functions we update the controller state and then call a server action in @actions/cart.ts to update the server state of the cart.

Nice! While the cart action is outside the sample scope (i.e. users should definitely not use that), I'm wondering about the usage of cookies. Instead, maybe we should have a Route Handler to mimick an API, and have a singleton pouchDB in the route to handle the cart persistence. This would allow to have no other cookie in the user of the sample other than the visitorId,
Tho, this is a nitpik tbh.

Sure, I can add pouchDB, I just didn't want to add any dependencies and in-memory storage was not possible using route handlers. . Ill change it to use route handlers with pouchDB instead.


License?

I'm about to add a listing of this remake to https://osgameclones.com/ but I don't see any license information? Is it open source or is it meant to be non-permissive license?
This website might help https://choosealicense.com in choosing an appropriate license. Thanks!

Thank you for pointing this out @nikuda I had indeed neglected to add a license but have chosen the MIT License. This is an educational project and I want people to benefit from it in any way they like.  Feel free to add links to your web site.


Redeem Function

Write a function to redeem the card by Id

The function should be payable
Should accept cardId and Password
If password after encryption with keccak256 matches with the initial transfer the amount to msg.sender

Resolved


hotReloadInitialDevFSSyncAfterRelaunchMilliseconds, hotReloadInitialDevFSSyncMilliseconds regressions

See https://flutter-flutter-perf.skia.org/e/?begin=1620396542&end=1620837185&keys=X3ede329e250323f68d006ede1b60b568&requestType=0&xbaroffset=24008. Looks like it started with https://github.com/flutter/flutter/pull/82291, although I don't see how any of those engine commits could have raised the hot reload times.
/cc @jason-simmons, this week's engine sheriff.
Given the small increase involved, I'm marking this a P1 so it doesn't block further releases.

I tried reproducing this locally.  The change to the metric in the benchmark graph is around 5%, and the variance between local runs of the benchmark on my setup is larger than that.  So I was not able to reproduce a consistent change due to a recent commit.
The only engine change that landed in that range was https://github.com/flutter/engine/commit/0fe6b7b410d43c18ce8932360295887dc993a25e.  There were no rolls or Dart or other dependencies.
Besides the engine roll there were two framework changes, neither of which seem related to hot reload.
Given that, I'd vote for rebaselining this benchmark.

SGTM. Will do and closing.


[doc] Document the requirement for OpenOCD 0.11

After a rather extensive release cycle the OpenOCD finally produced an
upstream stable release with RISC-V support. This allows us to switch
back to the normal upstream version of OpenOCD, which will soon also
appear in distribution.
CI is already using OpenOCD 0.11.0 (rc2 before, since today the final
0.11.0 release), giving us the confidence that what we document actually
works.

Btw, you can get the OpenOCD packages we use in CI at https://software.opensuse.org/download/package?package=openocd-0.11.0&project=home%3Aphiwag%3Aedatools if you don't want to compile it yourself.

Woo!


[Feature]: Automated Greeting Workflow

Description
I propose to create a GitHub workflow named "Greetings". This workflow will automatically greet users who create new issues or pull requests in this repository.  The Greeting will look like "Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible."
Please assign this issue to me
Why implement this feature?
By implementing this feature the Contributors will feel appreciated of their efforts and also the time to write the message manually is reduced as it is automated.
Any additional information?

Checklist

[X] I have checked the existing issues and made sure that this is not a duplicate feature request form.

Assigned @sanmarg
It's really a good feature


Config port inconsistent connection

The config port sometimes does not connect correctly causing it to not send in odometer messages.

Fixed in v1.1.3


Integrate CDC data from MySQL/Postgres/MongoDb data source

Description
Integrate with Kafka Connect and Debezium MySQL/Postgres/MongoDb plugin for CDC
Issues Resolved
Resolves #3233 #3234 #3235
Check List

[x] New functionality includes testing.
[x] New functionality has a documentation issue. Please link to it in this PR.

[x] New functionality has javadoc added

[x] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Overall, the changes look good to me. Let's close out the items pointed by @dlvenable and have a plan for that.


net: conn_mgr: connectivity API

Adds a connectivity API to conn_mgr that allows applications to generically configure and trigger post-admin-up associate/connect operations on ifaces / L2s that implement support for it.

Features removed that must be re-implemented in this PR:

binding init call on start
timeout and fatal-error NET_MGMT events

Features removed that will need to be re-implemented in a follow-up PR:

NET_IF_NO_AUTO_CONNECT

Most recent changes still not tested, and thus hypothetical. Not totally sure whether what I've done for the mutex will actually work. Hoping to massage it into a buildable state tomorrow and find out.

I don't see the advantage of conn_mgr_conn_binding section over a statically allocated array of network interface context owned solely by conn_mgr, naturally net_if index sorted then.

When it comes to the interface binding context, we'd need to preallocate then, I see one major advantage for the CONN_MGR_BIND_CONN() macro. The binding context consists of a generic part struct conn_mgr_conn_binding which also contains a pointer to connectivity-implementatation specific context (in theory this will be different for OT/Wi-Fi/LTE etc.). Currently, this specific structure is allocated when CONN_MGR_BIND_CONN() is used (unique for each interface). I don't really see how this could be achieved if we wanted to preallocate structures at the conn_mgr level.

(the only drawback is that we cannot, at build time, make the static net_if count from the section net_if_dev, if I remember well. So this would need some thoughts on that area).

That's also solved by the current approach. If we use binding macro when defining a network interface, we only allocate as much space as we really need. If we'd count for example interfaces (assuming it'd be possible at build level) we may overallocate (consider an abstract sceneario where we have several Ethernet interfaces and one OpenThread - we'd only need a one binding context then, not for each interface).

Having bindings done like that means tweaking all existing device drivers, and each and every device driver has to know the bindings to provide.

Not all actually, only those that need to support some kind of connectivity. Others simply don't define a binding, so no changes are needed then.

RAM usage since you would have private context per net_if, and bindings would exist per dev-type

I think that struct conn_mgr_conn_binding should be unique for each interface, as it contains parameters (flags, timeout) that should not be shared across interfaces. What is shared by the dev-type is struct conn_mgr_conn_impl, and that's how it currently works (you only define it once, then provide a respective identifier when binding the interface with CONN_MGR_BIND_CONN_INST().

At least it seems more logical that way, the net device driver should not know anything about conn_mgr, but conn_mgr should know what the net device is and what it provides, so it could behave the right way for each and every device. It also concentrates the infrastructure even more into conn_mgr.

I'm not going to argue with that, but I still think the current proposal is a good trade-off when it comes to memory management which IMO should be a consideration when it comes to memory-constrained systems. With the dedicated section, we only allocate as many binding contexts as we really need, and the conn_mgr can easily iterate over them.
The current approach also leaves an opening to easily extend the conn_mgr with custom connectivity implementations, w/o a need to modify the conn_mgr itself, which is of a great value for us at Nordic.

@tbursztyka

Why would you not need any context for ethernet? Since afterwards, you may add up more info in that context that will be necessary for conn_mgr to function?

To clarify, the conn_mgr_conn_binding struct is intended solely for use with the connectivity API. The conn_mgr_handler thread you wrote will continue to use the statically allocated iface_states array for its per-iface state tracking.
That means:

conn_mgr_conn_binding structs should only be allocated for ifaces that support the connectivity API (that is the whole purpose of the struct)
conn_mgr_conn_binding structs will only contain state and information relevant to connectivity, which is IMO an L2 concern, not an L4 concern

I think you will, soon, end up in conn_mgr requiring to store some info per-net_if anyway. The connection status perhaps, some runtime conn_mgr specific settings that target specific net_if (which one has the priority for auto-connection to keep the system connected/online etc...)

IMO, it does not make sense to mix the connectivity API with such hypothetical information. Instead, it would make more sense to alter the iface_states array (which is already statically pre-allocated for each and every iface in the manner you suggest) to store this hypothetical extra information. That way, we don't mix L4 concerns into the L2/connectivity-focused conn_mgr_conn_binding struct.
In other words, yes, information that truly needs to be stored for every iface should go in a statically allocated array. But conn_mgr_conn_binding doesn't belong as part of that array, since it is only concerned with connectivity. Mixing them would be less logical IMO, since we would now be storing the connectivity API and conn_mgr's internal state tracking in the same location.

[The current approach brings] quite a mess in the device drivers [because it forces them to implement their connect/disconnect logic themselves]

I understand that you view this as messy, because you are concerned about L2 and L4 mixing, but as I have pointed out above, no L4 logic actually lives inside conn_mgr_conn_binding or its API implementations, nor should it ever. So that seems like a non-issue to me.
Furthermore, allowing device drivers full autonomy over their connect/disconnect routines is one of our primary goals, so having this logic along side other L2 concerns is actually desirable to us, rather than some kind of unfortunate side effect. We think this makes sense because connect/disconnect routines will generally be forced to make the same kind of low-level driver calls that the net_if_up and net_if_down handlers do.

The biggest problem with that is the requirement of adding stuff to the device driver that has nothing to do there: L4 specific data into L2. Design wise, it's really messy.

I reiterate that conn_mgr_conn_binding is intended to be purely concerned with L2 matters. We are no where near IP/UDP/TCP at the connectivity/association stage. This is an API exposing a necessary sub-step for achieving oper-up. I think it is pretty squarely L2, and thus we are not mixing L2 with L4.
We would only be mixing L2 and L4 if we go with your suggestion to re-interpret conn_mgr_conn_binding as conn_mgr_context and start using it as a general purpose state/context container for the conn_mgr_handler thread. IE, merge conn_mgr_conn_binding with iface_states.
And yes, it is possible to perform that merge without mixing L2 and L4 if we also follow your other suggestions to:

Internalize connectivity logic completely into conn_mgr
Add some kind of network-type flags or metadata to ifaces so that conn_mgr knows which logic to use
Allow the definition of custom connectivity logic and custom network types so that downstream net-devs can be handled by conn_mgr too

But this seems like a pointless, and very significant complication (it requires inventing a new system by which to define custom network-type handlers), when we can avoid L2 and L4 mixing simply by keeping conn_mgr_conn_binding and iface_states separate. Plus, by keeping them separate, we avoid the need to modify net_if with these flags you suggest, which I would have assumed you would find desirable.
So I ask: Other than avoiding mixing L2 and L4 (which we avoid anyways), why bother with this more complex approach when the simpler one already works and is implemented?

Guys the naming really need so be revised: conn_mgr_conn_ as a prefix, why the second "conn"?

The second conn is short for connectivity, and is meant to signify that the item is related to the connectivity API, as opposed to being a general conn_mgr feature
I'm open to other naming conventions that maintain this distinction, of course, if you have any suggestions (other than conn_mgr_context, which as I mention above would not match the intended purpose of conn_mgr_conn_binding)

I'd just want to add that regarding to:

No device driver has to be modified (the type can already come from the L2 its net_if is related to)

If really we need to shrink to the most, then again from the existing net_if allocator macro, and because it knows the L2, we could conditionally allocate a more or less complex context per-interface.

This wouldn't really work nicely with offloaded interfaces, as from the Zephry perspective there is no information on what underlying technology the interface is using (i. e. they don't implement Zephyr L2, so it can't be used to derive L2 connectivity information). A similar problem applies to native Wi-Fi devices, which re-use Ethernet L2 (and we're likely not having a native Wi-Fi L2 in Zephyr any time soon). Using binding macros explicitly per interface solves this problem.

LGTM

NET_IF_GET and CONN_MGR_BIND_CONN_INST can only be called from a place that has called NET_DEVICE_INIT

Just to clarify, CONN_MGR_BIND_CONN_INST is expected to be called at the same place as NET_DEVICE_INIT - that's the way we propose to statically bind connectivity implementation with an interface. NET_IF_GET is just a convenient way to obtain the interface pointer test purposes. I'd expect the applications would call some public APIs instead, like net_if_lookup().
I'm just wondering on how to proceed here, would refactoring the test code a bit, to split interface definitions into a separate file, not to mix up with actual test cases, and use public APIs in tests only work? It should clearly show then how the new conn_mgr APIs should be used then. @glarsennordic Any thoughts?

@rlubos I could definitely separate the iface definitions out from the test suite. The main reason I didn't is that net_if structs are declared as static by NET_DEVICE_INIT, so if I declare them in a separate compilation unit, I will no longer be able to directly access them by name.
Most of the networking test suites work around this by looping through the ifaces iterable section and re-identifying each iface they construct. I could probably get an approach like this to work, but I preferred direct pointer access.
I'll look into alternative approaches to see if there is a middle-ground that would allow a clean extraction of the iface declarations

@glarsennordic Compliance error :(

MISSING_EOF_NEWLINE: adding a line without newline at end of file
File:tests/net/conn_mgr_conn/src/test_ifaces.c

Ahhh I was so close. Easy fix, though.


[FLINK-24781] Add to string casting rules

What is the purpose of the change
Port to string casting logic to the new CastRule stack
Brief change log

Added a method in CastRule to define explicitly if the rule can fail or not. Then adapted the ScalarOperatorGens runtime to make sure CAST doesn't fail when the rule can fail (as temporary fix before https://issues.apache.org/jira/browse/FLINK-24385 is worked out)
Added to string cast rules

Modified some methods in parsing logic for numerics and dates to make sure they fail when the conversion can't be performed.

Verifying this change
Added test cases to CastRulesTest
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@snuyanzin Updated with feedback. The issue with date/time methods in particular is that the parsing methods from DateTimeUtils should fail, instead or returning boxed null values, and they should fail with proper exceptions explaining why. I want to avoid to tackle this particular aspect of the issue in this PR, since these methods are used in other parts of the codegen. I hope to fix once for all the behavior of these methods in the context of https://issues.apache.org/jira/browse/FLINK-24507

thank you very much.
No more comments from my side.
LGTM

I rebased the PR so it can be merged like it is


TS L1 Enhancement - Test Profile Changes - DeepSleep manager

This task is to modify the Deepsleep manager L1 concerning the latest Test profile changes if any. If there are no changes concerning the test profile, this Jira can be closed with proper information.
Interface file:
https://github.com/rdkcentral/rdk-halif-deepsleep_manager/tree/develop/include
L1 Code:
https://github.com/rdkcentral/rdk-halif-test-deepsleep_manager/blob/develop/src/test_l1_deepSleepMgr.c

There are no changes in deepsleep manager concerning the latest test profile.


[Cosmos] enable pk delete tests

Re-enabling these tests now that we have emulator support in the pipelines.

/azp run python - cosmos - tests

API change check
API changes are not detected in this pull request.

/azp run cosmos - python - tests


window type error

Describe the bug
before:

after:

I don't know why
Reproduction
https://github.com/howiepu/vitesse-window-type-error
System Info
System:
    OS: macOS 14.5
    CPU: (10) arm64 Apple M1 Pro
    Memory: 77.16 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.18.2 - ~/Library/Caches/fnm_multishells/73994_1718641724213/bin/node
    npm: 9.8.1 - ~/Library/Caches/fnm_multishells/73994_1718641724213/bin/npm
  Browsers:
    Chrome: 126.0.6478.61
    Safari: 17.5

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Contributions

[ ] I am willing to submit a PR to fix this issue
[ ] I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)

like this the type is ok


HBASE-28155 RecoveredReplicationSource quit when there are still unfi…

…nished groups

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 25s
Docker mode activated.


Update Set-SPOSite.md

new cmdlet option added
Set-SPOSite -Identity  -ConditionalAccessPolicy AuthenticationContext -AuthenticationContextName "Name of Authentication Context"

Docs Build status updates of commit 6e167fb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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 9bc25f5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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 bf3a005:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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

@tseward

Docs Build status updates of commit 77c96fc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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

@Kateyanne Please merge this PR. Thanks

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

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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


DOP-4983: controlled sections and refs for collapsibles

Ticket
DOP-4983
Notes

This PR updates sectioning logic for collapsibles: the heading option will be at the same level as the sibling content above, and content within collapsibles should be considered another level down.
Also addressed the third point in the issue, where refs that were pointing to collapsibles were not pulling the content from the heading option.

README updates

[ ] This PR introduces changes that should be reflected in the README.md and/or HACKING.md, and I have made those updates.

[X] This PR does not introduce changes that should be reflected in the README.md and/or HACKING.md

hey @i80and ! i think i may have overlooked somethings in this PR:

this iterator will always be true, have to check that its not empty
A new section should be added within collapsible content (if there are none) as described above. but also, a collapsible itself should be in a section, as its heading should always be h2 and subsequent headers should follow suit (h3, subtitle) afterwards

More fixes coming up


Wrong parameter SourceImageId documented

In the PowerShell example:
$rgName = "MyResourceGroup"
$galleryName = "MyGallery"
$galleryImageDefinitionName = "MyImageDef"
$location = "eastus"
$galleryImageVersionName = "1.0.0"
$sourceImageId = "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/myVMRG/providers/Microsoft.Compute/galleries/MyGallery/images/Gen2VMImageDef/versions/0.0.1"
New-AzGalleryImageVersion -ResourceGroupName $rgName -GalleryName $galleryName -GalleryImageDefinitionName $galleryImageDefinitionName -Name $galleryImageVersionName -Location $location -SourceImageId $sourceImageId

The parameter SourceImageId is wrong. It has to be SourceImageVmId.

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

ID: 8ee728ba-a880-324c-83e7-84936b4d9533
Version Independent ID: 64638d26-e84c-22b9-6c22-2b1e0dd3608b
Content: Deploy a trusted launch VM - Azure Virtual Machines
Content Source: articles/virtual-machines/trusted-launch-portal.md
Service: virtual-machines
Sub-service: trusted-launch
GitHub Login: @lakmeedee
Microsoft Alias: howieasmerom

@AlyaKoni
Thanks for your feedback! We will investigate and update as appropriate.

@AlyaKoni
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.

@AlyaKoni
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@AlyaKoni Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.

It's been months and this still is incorrect.
As a matter of fact, every single reference where you create a VM Gallery Image from a VM using PowerShell is incorrect.
PG needs to get the Docs updated to account for the new spec ASAP.


active tab top border is missing

I'm unable to add it back in manually

It's working for me

Can you try the newest insiders and in case you still see it, send me your entire colorCustomizations setting?
Also, if you have any other tab related setting that would also be helpful to know (even though probably not the cause).

it's back on the latest insiders


[gym] Add show build timing summary option

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I see several green ci/circleci builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
Currently, there is no way to run xcodebuild with the showBuildTimingSummary  option using the gym command.
This option is provides a breakdown of how long each task in the build process takes and can come in very handy to collect metrics on CI.
Description
This PR adds an optional flag to the gym command and, if set, it adds the showBuildTimingSummary option to xcodebuild.
I tested it by changing my project's Gemfile to point to the local version of fastlane with these changes.
When running fastlane build_with_summary and inspecting the logs, the Build Timing Summary section is present:
  lane : build_with_summary do
    default_platform(:ios)

    # Build with timing summary
    gym(
      project: "TestFastlane.xcodeproj",
      derived_data_path: "./derived-data",
      output_directory: "./build",
      export_method: "development",
      skip_profile_detection: true,
      export_options: {
        provisioningProfiles: {
          "dev.polpiella.TestFastlane" => "Pol's App Development"
        }
      },
      clean: true,
      skip_archive: true,
      build_timing_summary: true,
      buildlog_path: "."
    )
  end

output
Build Timing Summary

SwiftCompile (2 tasks) | 5.695 seconds
SwiftEmitModule (1 task) | 1.788 seconds
Ld (1 task) | 0.119 seconds
CopySwiftLibs (1 task) | 0.069 seconds
CodeSign (1 task) | 0.047 seconds
SwiftDriver (1 task) | 0.034 seconds
RegisterExecutionPolicyException (1 task) | 0.008 seconds
WriteAuxiliaryFile (12 tasks) | 0.005 seconds
CompileAssetCatalog (1 task) | 0.004 seconds
ProcessInfoPlistFile (1 task) | 0.002 seconds
Copy (4 tasks) | 0.002 seconds
ProcessProductPackagingDER (1 task) | 0.002 seconds
SwiftMergeGeneratedHeaders (1 task) | 0.001 seconds
Touch (1 task) | 0.001 seconds
ExtractAppIntentsMetadata (1 task) | 0.001 seconds
SwiftDriver Compilation Requirements (1 task) | 0.000 seconds
ProcessProductPackaging (2 tasks) | 0.000 seconds
Validate (1 task) | 0.000 seconds
SwiftDriver Compilation (1 task) | 0.000 seconds
ValidateDevelopmentAssets (1 task) | 0.000 seconds

Testing Steps
Run gym with both skip_archive and build_timing_summary set to true. The reason why we need skip_archive set to true is that xcodebuild does not show the timing summary with the archive command.

Super useful. Out of curiosity: would it be much additional work to also add the flag to scan? It'd be great to also be able to see a timing summary for test builds.


Failed to build on VS 2022 17.0.2 - 'expression did not evaluate to a constant' . in  write.hpp

Code failed to build using VS 2022. Error is 'expression did not evaluate to a constant' . in  write.hpp. Line 232.
               static constexpr auto member_ptr =
                  std::get<member_it->second.index()>(member_it->second);

[{
"resource": "/C:/Users/akmal/projects/cpp/glaze/include/glaze/binary/write.hpp",
"owner": "cmake-build-diags",
"code": "C2131",
"severity": 8,
"message": "expression did not evaluate to a constant [C:\Users\akmal\projects\cpp\glaze\build\_glaze.vcxproj]",
"source": "MSVC",
"startLineNumber": 232,
"startColumn": 49,
"endLineNumber": 232,
"endColumn": 49
}]

Wait, still broken... fixed a bug near this one.

Okay, this commit fixes the problem (06c0e16). Thanks again!


Implement the matching service with message queue

Develop the backend logic that uses a message queue to match users based on their selected topic and difficulty level. Integrate with the provided user service (code given for user service).
For submission:
Debug/log message indicating the status of the queue before and after the match

To clarify, they have not provided us a second batch of new stuff after we've integrated the user service?


add ThirdParty payer type

this is also a valid type of payer.

@dbojdo can you look? :)

Thanks! I've created the next stable release 1.0.2

brill, thanks for quick merge&release :)


Update github actions, add auto PR labeling action.

Going to need to fork https://github.com/einaregilsson/build-number to fix a number of deprecations with it (See possible PR on it)

No reason to wait on the build number fixes. Might as well merge this now and fix the build number stuff later.


Cannot launch the android emulator when run "react-native run-android" on the lastest version

check the issues above

check the document

search the issue in the stackoverflow

To Reproduce
Init a new project using the latest version, react-native run-android. Build successful but cannot launch the android emulator
Expected Behavior
Launch the android emulator normally
logs
info Starting JS server...
info Building and installing the app on the device (cd android && ./gradlew app:installDebug)...

> Task :app:installDebug
11:46:30 V/ddms: execute: running am get-config
11:46:30 V/ddms: execute 'am get-config' on 'emulator-5554' : EOF hit. Read: -1
11:46:30 V/ddms: execute: returning
Installing APK 'app-debug.apk' on 'Nexus_6_Edited_API_27(AVD) - 8.1.0' for app:debug
11:46:30 D/app-debug.apk: Uploading app-debug.apk onto device 'emulator-5554'
11:46:30 D/Device: Uploading file onto device 'emulator-5554'
11:46:30 D/ddms: Reading file permision of /Users/langke/TestReactNative/DrawerLayoutAndroid/android/app/build/outputs/apk/debug/app-debug.apk as: rw-r--r--
11:46:31 V/ddms: execute: running pm install -r -t "/data/local/tmp/app-debug.apk"
11:46:33 V/ddms: execute 'pm install -r -t "/data/local/tmp/app-debug.apk"' on 'emulator-5554' : EOF hit. Read: -1
11:46:33 V/ddms: execute: returning
11:46:33 V/ddms: execute: running rm "/data/local/tmp/app-debug.apk"
11:46:33 V/ddms: execute 'rm "/data/local/tmp/app-debug.apk"' on 'emulator-5554' : EOF hit. Read: -1
11:46:33 V/ddms: execute: returning
Installed on 1 device.

BUILD SUCCESSFUL in 4s
26 actionable tasks: 1 executed, 25 up-to-date
/bin/sh: /Users/langke/Library/Android/sdkexport/platform-tools/adb: No such file or directory
info Starting the app (/Users/langke/Library/Android/sdkexport/platform-tools/adb shell am start -n com.drawerlayoutandroid/com.drawerlayoutandroid.MainActivity...

Environment
  React Native Environment Info:
    System:
      OS: macOS 10.14.4
      CPU: (4) x64 Intel(R) Core(TM) i3-8100B CPU @ 3.60GHz
      Memory: 17.34 MB / 8.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 11.5.0 - /usr/local/bin/node
      Yarn: 1.12.3 - /usr/local/bin/yarn
      npm: 6.4.1 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
      Android SDK:
        API Levels: 23, 26, 27, 28
        Build Tools: 27.0.3, 28.0.2, 28.0.3
        System Images: android-27 | Intel x86 Atom_64, android-27 | Google APIs Intel x86 Atom
    IDEs:
      Android Studio: 3.2 AI-181.55<IP_ADDRESS>56338
      Xcode: 10.2/10E125 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.3 => 0.59.3
    npmGlobalPackages:
      react-native-cli: 2.0.1
      react-native-update-cli: 0.1.0

anybody knows that?  Thanks a lot

It couldn't find adb command used to install APK, you can see from below snippet from your description. Please make sure that SDK is installed completely.
/bin/sh: /Users/langke/Library/Android/sdkexport/platform-tools/adb: No such file or directory


OAuth2ServiceException: Error retrieving JWT token, when trying to get Destinations.

Issue Description
I have upgraded to use the 5.11.0 version of cloud sdk in my code base. However, when I am trying to get the destinations with the DestinationAccessor, I am getting the excpetion
2024-09-13T05:32:07.996+0000 [APP/PROC/WEB/0] STDOUT Caused by: com.sap.cloud.security.xsuaa.client.OAuth2ServiceException: Error retrieving JWT token. Server URI https://1(sensitive url)/oauth/token. Http status code 401. Response body '{"error":"invalid_client","error_description":"Bad credentials"}'.
Important information:

Your code -- DestinationAccessor.getDestination(destinationName);
Expected outcome -- Destination object
Actual outcome - Error above

The same request with the same destionations was working with cloud sdk version 4.28
But after upgrading to 5.11.0, getting the above error.
Impact / Priority
Our Go live is in a few days. This is of high priority.
Affected development phase: e.g.Release
Impact:  Blocked
Timeline: e.g. Go-Live code freeze is due in 1week.
Please paste your stracktrace here within the backticks (replacing this comment)

Application Logs
Cannot paste the complete stack trace due to sensitive information.

SDK Version:
5.11.0

Project type, for example:

[ ] CAP Project

Platform:

[ ] Cloud Foundry
[ ] Deploy with Confidence (Cloud Foundry)

Could you send your destination configuration in BTP (don't forget to censure credentials) and the mvn dependency:tree

After two weeks without feedback, we're closing the ticket.
Please create a new one, if the issue persists.


Why New-PartnerAzureSubscription requires CustomerName parameter

Feature Request
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I am always frustrated when [...]
Why New-PartnerAzureSubscription requires CustomerName parameter. Customer name is not unique property. It should require tenantid/customerId otherwise if there are two customers with the same name problems will occur.
Describe the solution you would like
A clear and concise description of what you want to happen.
Describe alternatives you have considered
A clear and concise description of any alternative solutions or features you have considered.
Additional context
Add any other context or screenshots about the feature request here.

@slavizh this particular command is calling the Azure Resource Manager API to create the subscription. That parameter is one of the required values for how the API was designed. It might be possible to interchange the identifier and name, but I have only tired using the customer name.
You can find more details about the API here.

@isaiahwilliams is it possible that you change the command in a way that we provide customer ID and the commandlet finds the customer and provides the needed information to the API. That would be better and more consistent experience within the whole module

@slavizh with the release of version 3.0 we will be adding the CustomerId parameter to this command. Also, the currently plan is to remove the CustomerName parameter when version 3.0.1 is released.

@slavizh version 3.0 has been released. You can find the details regarding the release here. Thank you for sharing this feedback it is greatly appreciated.


feature: Codecommit integration

Hey, I just made a Pull Request!
Adds an AWS CodeCommit integration and urlreader.
This allows using AWS CodeCommit as the source for catalog-info.yaml and techdoc files.
:heavy_check_mark: Checklist

[X] A changeset describing the change and affected packages. (more info)
[X] Added or updated documentation
[X] Tests for new functionality and regression tests for bug fixes
[X] Screenshots attached (for UI changes)
[X] All your commits have a Signed-off-by line in the message. (more info)

note: solves #15210

Closing due to all kinds of build issues introduced by a bad merge. A new/clean PR is opened (#23828)


401 error after upgrading to new version of test cafe

What is your Scenario?
Automating a website using testcafe
The issue is while authenticating with windows auth
We are getting a 401 unauthorized exception
We used the below version
Node version 14 or later
Test cafe version 1.13 or later
The same scripts working in below version
Node version 14
Test cafe version 1.13 or below
Writing our scripts in vscode
Testing in edge chromium
We are using .httpAuth with username, password, and domain. We tried without domain.
We tried to find out SendRequest method in hammerhead but could not find
What is the Current behavior?
while authenticating with windows auth
We are getting a 401 unauthorized exception
What is the Expected behavior?
The browser popup for credential would come and post authentication should go to the home page
What is your public website URL? (or attach your complete example)
Na
What is your TestCafe test code?
Na
Your complete configuration file
No response
Your complete test report
No response
Screenshots
No response
Steps to Reproduce

TestCafe version
1.13+
Node.js version
14
Command-line arguments
Na
Browser name(s) and version(s)
No response
Platform(s) and version(s)
No response
Other
No response

Hello Thank you team,
We are trying in client regulated environment and application which we are testing is an INTRANET web site.
It is only doing logging in using windows authentication and going to a particular url
It is working in an older version of testcafe with the same scripts.
Only issue with apps having windows authentication
Can you help with the below

Is there any specific library that we should look for that is required for Windows authentication but may not have been installed during the upgrade?
Could you provide us with a file/class in a node module that we can debug to better understand window authentication so that we can see if any specific arguments, such as the header, are passed or not?
Any alternative to .httpAuth, which resembles Windows authentication and works in both earlier and later versions
Is there a difference in the creation of webproxies in recent versions that is preventing Windows authentication?

We are experiencing exactly the same issue. We are stuck on version 1.14 of testcafe because of this.

Hello @deepak30051982

Is there any specific library that we should look for that is required for Windows authentication but may not have been installed during the upgrade?

NTLM authentication in TestCafe is implemented in the https://github.com/DevExpress/testcafe-hammerhead module. The testcafe-hammerhead module uses the webauth module to add credentials to the request options.

Could you send us a file/class in a node module that we can debug to understand window authentication better and see if any specific arguments, such as the header, are passed?

Sure, you can start with the _onResponse method in testcafe-hammerhead here:
https://github.com/DevExpress/testcafe-hammerhead/blob/3e60530b9ebcfdd176878905102c98609ef533e6/src/request-pipeline/destination-request/index.ts#L176
Then, you can go with the _resendWithCredentials method:
https://github.com/DevExpress/testcafe-hammerhead/blob/3e60530b9ebcfdd176878905102c98609ef533e6/src/request-pipeline/destination-request/index.ts#L204
The idea of the httpAuth is resending the initial request if the response status code is 401.

Any alternative to .httpAuth, which resembles Windows authentication and works in both earlier and later versions

TestCafe only assumes using the httpAuth method.

Is there a difference in the creation of webproxies in recent versions that is preventing Windows authentication?

There should not be any difference. This code has not been changed in recent years.


next: scheduler HTTP API wants StreamID header

xref https://issues.apache.org/jira/browse/MESOS-3583

see https://reviews.apache.org/r/44278/diff/4#index_header

should consider how/if to replay (otherwise valid) CALL's that receive a 400 response (invalid stream ID) because the persistent SUBSCRIBE connection was dropped for some reason.

implemented and working well


Add ability to travel through portals from level to level

from Discord:

The way it works is: if there's no next_level_portal_name set it uses the first checkpoint under Checkpoints node, to position the player in the new level, this has the benefit that it immediately visits the checkpoint so it gets saved for the dying state and if next_level_portal_name is set then it uses that specific portal to place the player in the new scene/level

had to add a Player.has_traveled bool "check" which is used when traveling from portal to portal between levels so that _on_body_entered doesn't trigger the level load on first pass
also removed unused Exit.* files from under src/Level and renamed src/Objects/Exit.* to Portal.*
removed Checkpoints node under Game & moved visited_checkpoints-related mechanics inside Game.gd
changed visited_checkpoints from simple Array to Dictionary to track which checkpoints are from what level and to "re-apply" is_visited checks when triggering level loading (in LevelLoader.gd)

closes #145

Seems good to me, is it good to merge? I'd test it in practice and make more changes later

Yeah, good to merge, it isn't WIP, it's just that I think we can possibly improve the system, it seems a bit more complex than it should, but I think it gives a good test bed for later updates

Got it, I'll merge and we can review it later!


Add error logs when metrics cannot be send to the platform

Is your feature request related to a problem? Please describe.
When testing the entity registration func for v4 integration, we were sending an entity type that was being rejected by the platform and so the metrics were being discarded and it was difficult/impossible to find errors in the logs that pointing the issue.
Feature Description
As an integration builder I would like to see logs at error level when metrics will be discarded because an entity registration issue.
Describe Alternatives
Additional context
additional context in this thread
Priority
Please help us better understand this feature request by choosing a priority from the following options:
Really Want

Possible improvement: we could add error log when entity cannot be registered due to invalid payload values (e.g. invalid entity type) and only printed those lines when in debug mode. We don't want to pollute the log with errors if these come from an invalid / incomplete integration.


endpoint / ApplyPolicyMapChanges: fix incorrect comment

This comment incorrectly referenced some now-reverted behavior. Remove this now so we don't confuse ourselves.
Fixes: #31775

This just changes a code comment, marking as ready-to-merge.


Fix tests

QRcode.test.tsx
ShadesAndTints.test.tsx
Avatar.test.tsx
ColorPicker.test.tsx

Error: @mantine/core: MantineProvider was not found in component tree, make sure you have it in your app

Had to downgrade to
		"@mantine/core": "^6.0.10",
		"@mantine/hooks": "^6.0.10",

From
"@mantine/core": "^7.3.2",
"@mantine/hooks": "^7.3.2",


desktoppr won't read the current desktop picture when a feature to automatically change a wallpaper is enabled.

When a feature to automatically change the wallpaper every n minutes is enabled, desktoppr won't display the path of the current wallpaper, only the folder where that wallpaper is located.
Can it be fixed?

No, the API desktoppr uses does not provide that information.


[Enhancement] Add root cause of #25 to doc : MAX_FETCH_RECORDS cause timeout

https://issues.apache.org/jira/browse/FLINK-26159


Improvements to icons + Hiding 'Include suggested change'

After some tests with pads with 100+ comments, I've noticed sidebar comments were taking almost 10s to be shown, and comment icons were taking FOREVER. So here are some performance improvements (was able to reduce load time to 2s) + hiding 'Include suggested change' when hovering over a comment + a fix for frontend tests when icons are disabled on settings.json.
I still need to make icons work when ep_page_view is not installed, will work on that on Monday.

nice thanks!


Making Multiple requests with http fails?

I'm trying to create a request library and an sdk But it seems I'm doing something wrong only the first request seems to work the other one responds with failed request
use "assert"
use "collections"
use "net/http"
use "net/ssl"
use "json"

primitive OAuthEndPoint fun apply(): String => "https://playlyfe.com"
primitive APIEndPoint fun apply(): String => "https://api.playlyfe.com/v2"

actor Playlyfe
  let _env: Env
  let _client: Client
  let client_id: String
  let client_secret: String

  new create(env: Env, client_id': String, client_secret': String) =>
    _env = env
    client_id = client_id'
    client_secret = client_secret'
    _client = Client(None)

  be api(method: String, route: String) =>
    try
      let url = URL.build(APIEndPoint() + route)
      let req = Payload.request(method, url, recover this~apply() end)
      _client(consume req)
    else
      _env.out.print("Malformed URL: " + route)
    end
    // Fact(url.host.size() > 0)

  be get(route: String) =>
    api("GET", route)

  be post(route: String) =>
    api("POST", route)

  be patch(route: String) =>
    api("PATCH", route)

  be put(route: String) =>
    api("PUT", route)

  be delete(route: String) =>
    api("DELETE", route)

  fun createJWT() =>
    """
    Creates a JWT Token which can be used to authenticate your users from your
    own backed
    """

  be apply(request: Payload val, response: Payload val) =>
    if response.status != 0 then
      // TODO: aggregate as a single print
      _env.out.print(
        response.proto + " " +
        response.status.string() + " " +
        response.method)

      for (k, v) in response.headers().pairs() do
        _env.out.print(k + ": " + v)
      end

      _env.out.print("")

      for chunk in response.body().values() do
        _env.out.write(chunk)
      end

      _env.out.print("")
    else
      _env.out.print("Failed: " + request.method + " " + request.url.string())
    end

actor Main

  new create(env: Env) =>
    var pl = Playlyfe(env, "Fsf", "fsd")
    pl.get("/")
    pl.get("/")

This seems to be something to do with your API endpoint, as exchanging it with a variety of other HTTP and HTTPS URLs doesn't exhibit the same issue. The only thing I noticed is that the server is responding with connection: close headers.
It could be that the HTTP client is attempting to pipeline requests where it shouldn't. E.g. maybe both requests are pipelined on the same socket but the server closes the socket after servicing the first request.

This discussion seems to have been abandoned. Closing. Please reopen if active investigation is required.


Directory restructure

New build system: this restructure has been successfully tested with the new build system. The new build system requires the following update to the Makefile:
SOURCEDIR     = rst_files --> SOURCEDIR     = source/rst
It may not be compatible with Windows as the repository contains and requires a _static directory symlink.
Updates

Renamed rst_files to source
Created rst directory in source directory
Moved all rst source files and sphinx conf.py into new rst directory
Added symlink so sphinx can access _static directory
Removed template (non content) images banner.png and sloan_logo.png and referenced them from assets.quantecon.org

New repo structure:

@mmcky The current structure is such that pdfs, code, etc., live inside the rst_files directory, which has led to some confusion.  This PR makes different kinds of files easier to find.
I'd like to merge this tomorrow morning and then get the corresponding instructions up.  Your comments are very welcome but if you don't have a chance to look I'll go ahead and merge.


Failed to load items causing unusable saves

Gibbed.BorderlandsOz.GameInfo.ResourceNotFoundException: item type 'GD_Cork_ClassMods_TW.A_Item_Prototype.ClassMod_Prototype_ShortCircuit' is not valid for 'GD_Cork_ItemGrades.ClassMods.BalDef_ClassMod_Prototype_05_Legendary'
at Gibbed.BorderlandsOz.GameInfo.ItemBalanceDefinition.Create(ItemDefinition item)
at Gibbed.BorderlandsOz.SaveEdit.BaseItemViewModel.BuildPartAssets()
at Gibbed.BorderlandsOz.SaveEdit.BaseItemViewModel..ctor(BaseItem item)
at Gibbed.BorderlandsOz.SaveEdit.BackpackItemViewModel..ctor(BackpackItem item)
at Gibbed.BorderlandsOz.SaveEdit.BackpackViewModel.ImportData(WillowTwoPlayerSaveGame saveGame, Platform platform)
at Gibbed.BorderlandsOz.SaveEdit.ShellViewModel.<>c__DisplayClass62_0.b__0()
at Caliburn.Micro.Contrib.Results.DelegateResult.Execute(ActionExecutionContext context)
Again with borderlands 2 gibbed no idea when this issue started it was just told to me one of my saves was showing as corrupt and went to fix it when i run in to this error

Please attach a sample save file that has this issue, decrypted if it's a console save.

SaveDROP.zip


sys::mman: adding few madvise flags.

MADV_PAGEOUT which reclaim the address range, swapping it out if the page is anonymous or written back to disk if it's backed up by a file.
MADV_COLD which deactivate the address range but as a hint.
MADV_WIPEONFORK after fork(), the address range is wiped out to avoid sharing sensible data between processes.
MADV_KEEPONFORK disables MADV_WIPEONFORK workflow.

@SteveLauC is it ok if, eventually, I do not add new tests there is no previous madvise test.

is it ok if, eventually, I do not add new tests there is no previous madvise test.

Yeah, I think so. Having tests is great, but Nix, as a wrapper crate, only needs to ensure the wrappers work. These flags are just constants, not syscalls, they are guarded by the libc crate, so it is ok not to have tests for every constant 😄


Rely on NEP-18 to dispatch to dask in duck_array_ops

Removes special-casing for dask in duck_array_ops.py, instead relying on NEP-18 to call it when the input is a dask array.
Probably actually don't need the _dask_or_eager_func() (now _module_func()) helper function at all, because all remaining instances look like pandas_isnull = _module_func("isnull", module=pd), which could just be pandas_isnull = pd.isnull.
 Total: %d > max: %d."
                % (self.total_computes, self.max_computes)
            )
E           RuntimeError: Too many computes. Total: 1 > max: 0.

/home/tegn500/Documents/Work/Code/xarray/xarray/tests/__init__.py:118: RuntimeError

[x] Closes #5559
[x] Tests added
[x] Passes pre-commit run --all-files
[x] User visible changes (including notable bug fixes) are documented in whats-new.rst

Hello @TomNicholas! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file xarray/tests/test_units.py:

Line 5591:36: E721 do not compare types, use 'isinstance()'

Right I understand the failure now - everywhere where _dask_or_eager_func was dispatching numpy->dask is working fine via NEP-18, but my change made pandas.isnull no longer dispatch to dask.isnull, which then computes (and raises because we want it to be lazy). The solution is to special-case that one use of pandas (and perhaps any other uses of pandas?).

A net-negative pull request :exploding_head:

Looks great! I don't know the details of this code well, but at the conceptual level it looks good!

A net-negative pull request 🤯

The best type!

Now there is one more mystery: why do some of the tests for padding fail with output that is 0.5 away from what's expected??:
_____________ TestVariableWithDask.test_pad[xr_arg3-np_arg3-mean] ______________
[gw3] linux -- Python 3.7.10 /usr/share/miniconda/envs/xarray-tests/bin/python

self = <xarray.tests.test_variable.TestVariableWithDask object at 0x7f10bd848990>
mode = 'mean', xr_arg = {'x': (3, 1), 'z': (2, 0)}
np_arg = ((3, 1), (0, 0), (2, 0))

    @pytest.mark.parametrize(
        "mode",
        [
            "mean",
            pytest.param(
                "median",
                marks=pytest.mark.xfail(reason="median is not implemented by Dask"),
            ),
            pytest.param(
                "reflect", marks=pytest.mark.xfail(reason="dask.array.pad bug")
            ),
            "edge",
            pytest.param(
                "linear_ramp",
                marks=pytest.mark.xfail(
                    reason="pint bug: https://github.com/hgrecco/pint/issues/1026"
                ),
            ),
            "maximum",
            "minimum",
            "symmetric",
            "wrap",
        ],
    )
    @pytest.mark.parametrize("xr_arg, np_arg", _PAD_XR_NP_ARGS)
    @pytest.mark.filterwarnings(
        r"ignore:dask.array.pad.+? converts integers to floats."
    )
    def test_pad(self, mode, xr_arg, np_arg):
        data = np.arange(4 * 3 * 2).reshape(4, 3, 2)
        v = self.cls(["x", "y", "z"], data)

        actual = v.pad(mode=mode, **xr_arg)
        expected = np.pad(data, np_arg, mode=mode)

>       assert_array_equal(actual, expected)
E       AssertionError:
E       Arrays are not equal
E
E       Mismatched elements: 48 / 96 (50%)
E       Max absolute difference: 0.5
E       Max relative difference: 0.25
E        x: array([[[ 9.5,  9.5,  9. , 10. ],
E               [11.5, 11.5, 11. , 12. ],
E               [13.5, 13.5, 13. , 14. ]],...
E        y: array([[[10, 10,  9, 10],
E               [12, 12, 11, 12],
E               [14, 14, 13, 14]],...

for padding fail with output that is 0.5 away from what's expected

We work around some dask bugs with dask_array_compat.pad I think you'll need to revert to that and not use np.pad until we can bump dask.

The issue mentioned in dask_array_compat.pad was closed around may 2020 (https://github.com/dask/dask/pull/6213).
The min version of dask can be bumped to 2.24 tomorrow (from 2.15 and 2.9), maybe that's enough to fix the errors?

Thanks for the reminder @dcherian - I merged main and all the tests pass so I'll merge this PR now!

The what's new entry for this went in under the wrong edition - I fixed it in https://github.com/pydata/xarray/commit/ebfc6a3db0580cc11418e906766805ff4bf36455


SystemStackError in RailsAdmin::MainController#delete

I would like to know how to solve or prevent the following error when deleting a record with  has_many associations and  dependent: :destroy ?
Thank you

Full stack trace, please.

Please reopen on update.


Timestamp in nuget dependencies

Hi,
just FYI, the 1.2.1 version on nuget:
https://www.nuget.org/packages/LinqKit.Core
has the "TimeStamp" package as a dependency. I don't think this is needed.
Cheers

https://github.com/scottksmith95/LINQKit/pull/171

Thanks! :)


Update README.md #7

Description
Improved README.md, aligned contents to center and some other changes
Fixes # 7
Type of Change:

Documentation

Screenshots

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests/screenshots(If any) that prove my fix is effective or that my feature works

Please resolve these merge conflicts

Resolved the conflicts.

There are some more conflicts, resolve them

Now resolved the conflicts. Please merge it so that I can synchronize my forked repo with the main repo and can work on another issue as well. Thank You :)


As a user, I would love to be able to receive feedback on whether successful or not

Fixed by #307


Error when syncing assets with s3

Fatal error: Failed to list content of bucket xpto.com
Error: The difference between the request time and the current time is too large.

@dynaum that is known problem when using VirtualBox that guest time get out of sync. We are working on a definitive solution.
In the meantime, the workaround to that problem is to restart the azk agent when it happens.


Update the README.md file to describe the repo.

Following the instructions in the Git tutorial and checking if everything works.

@iht  @juliocc


? How To Handle Autocomplete with Source List of 1500 Items?

Thanks for sharing such a great tool!  I can't wait to start using it. :+1:
I have a question about usage:  Can Awesomplete handle a large list of say, 1500 items?  If so, what method would you suggest to get the items?
Here's the background:

I would be using this with JavaScript for Automation (JXA) on a Mac
Via JXA, I have full access to the Mac's files
The use case is for working with Evernote tags
I currently have about 1500 tags
I would like to have an autocomplete tag selection much like Evernote uses in their Chrome and Safari web clipper
As a potential source, I can query Evernote Mac via JXA, and get all of the tags into a JavaScript array.
Once I get this working, I plan to share with the Evernote community

Thanks in advance for your help and any suggestions.

I've successfully used Awesomeplete with much larger lists, accuired similarly by AJAX.
It proved very performant.