added android:exported=true in service tag as in Android 11 its compu…

…lsory to have this tag if intent-filter is used

Description
We need to have android:exported="true" tag in services also if we are using intent-filter. This is required in Android 11 + builds.
Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Looking forward to the merge of this and a hotfix release as this currently prevents us from targeting sdk 31 which other plugins require.

The changes in this PR is more then what the title and description talks about.
A single PR should focus on an individual bug or feature. Not a collection of changes.
I created a PR and commited into master the changes that this PR's title and description is targeting.
If the other changes are required, split them out please into seperate PRs.


feat: Add time format helper

Added helper function to format time in seconds to human-readable format.

Please run yarn lint before committing.


Ui rating bugfix

#472

Fix flicker, show loading screen

when you PUT to /worker-requester-rating/:id you dont have to do a GET /rating/requesters_reviews

same goes for POST

@dmorina  what if the request fails?

If request fails you don't update anything on the ui, just notify the user

if not updated #485 will fix this fully

is it ok to close this?

closing due to removing immediate feedback to user.


unhandled exception error when exporting scripts with special chars in name

Frodo CLI version
cli: v0.19.1
lib: v0.17.1
node: v18.5.0

Describe the issue
Following error when exporting scripts with -A if a script name contains special characters, for e.g.: Accept T&C
$ frodo script export -A mytenant
[===========-----------------------------] 27% | 25/91 | Reading script Accept T&Cnode:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting
  code: 'ERR_UNHANDLED_REJECTION'
}

and same error using -a option on same tenant (though script name in output doesn't contain special chars):
$ frodo script export -a mytenant
[===========-----------------------------] 26% | 24/91 | Reading script Facebook Profile Normalizationnode:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting
  code: 'ERR_UNHANDLED_REJECTION'
}

Seems this issue does not show anymore for
cli: v0.19.3
lib: v0.17.5
node: v18.5.0

Fixed in frodo-lib 0.18.1-0


Docker build centos fails on Docker for Mac

Just tried to run this simple Dockerfile:
FROM centos:7
RUN yum update

This fails with the following error:
failed to register layer: rename /var/lib/docker/image/aufs/layerdb/tmp/layer-174610251 /var/lib/docker/image/aufs/layerdb/sha256/5f70bf18a086007016e948b04aed3b82103a36bea41755b6cddfaf10ace3c6ef: directory not empty
Tried to pull an ubuntu image and the problem didn't represent itself.
I am using the latest docker for mac version, and this is my output of docker version :
Client:
 Version:      1.12.0-rc2
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   906eacd
 Built:        Fri Jun 17 20:35:33 2016
 OS/Arch:      darwin/amd64
 Experimental: true

Server:
 Version:      1.12.0-rc2
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   a7119de
 Built:        Fri Jun 17 22:09:20 2016
 OS/Arch:      linux/amd64
 Experimental: true

Just to confirm this isn't a problem with docker 1.12.0-rc2 on linux.
It works in Fedora so I'm assuming this is an aufs issue on Mac beta.
$ sudo docker version
Client:
 Version:      1.12.0-rc2
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   906eacd
 Built:
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.0-rc2
 API version:  1.24
 Go version:   go1.6.2
 Git commit:   906eacd
 Built:
 OS/Arch:      linux/amd64

$ sudo docker info
Containers: 1
 Running: 0
 Paused: 0
 Stopped: 1
Images: 228
Server Version: 1.12.0-rc2
Storage Driver: devicemapper
...

This works fine for me on Docker for Mac. It may be that you have a corrupted aufs filesystem, it has been known to happen. Can you try doing a factory reset from the Preferences menu and see if this fixes the issue?

I can confirm @justincormack : aufs fs was corrupted.
Hard reset on the preferences fixed the problem!


Typescript typings

Hey man! Great library. Just wondering if you're interesting in having typescript definitions for this library (for those wanting to use react native with typescript). I already have stubbed them out in a few of my projects. Let me know @fson

Hey @iRoachie can you please share your typings? 😄

lol @ligaz they're are far from complete since I haven't used all the methods/props. Lol I wish there was a table in readme like showing the all the props and their values

@ligaz I could make it a public gist and we could work on it

Not opposed to have typings, but they need to stay up-to-date. So if you want to maintain them, feel free to send a PR with the typings (also maybe a test case to ensure I don't break them accidentally) :D
The library is fully-typed with Flow. You can find the exported flow types at https://github.com/react-native-community/react-native-tab-view/blob/master/types.js
For the prop types of individual components like TabBar and TabViewAnimated, you need to check the individual files.

@satya164 Thanks! That makes it 10x easier. Will start work on it

Closing (waiting for @iRoachie PR 😉).

@CharlesMangwa Haha thanks for reminder

WIP here #271


clarifies at what size we will review this policy

I agree with this sentiment. Two thoughts:

My sense is that we should be open to re-evaluating this before we reach the 10 person size limit. Maybe the language could be changed so it includes this option, while also guaranteeing that at the size limit there will be an explicit re-evaluation.
This re-evaluation policy applies to everything in the handbook. Is there a reason to explicitly call it out here (other than that this is a contentious policy) or could we just do a better job at messaging how we plan to continuously improve this (with fixed, encoded moments for re-evaluation as well).

cc @b

I'm okay with adding this here, because it is one of the more contentious policies in the handbook. In general, we'll be able to update the hosted versions of these policies regularly, but in order to "apply" them to our work at Clef, we'll all need to re-sign the acknowledgement of receipt, which we'll probably want to do regularly.
It may also be possible to change that acknowledgement with some sort of schedule of notifications about changes, but not require new signatures each time, but I don't have a firm plan for that yet.

:+1:


[IRGen] Mix -profile-generate into module hash

When rebuilding a .o file, we hash the IR generated by IRGen and compare it to a hash embedded in the .o file. If they match, we simply skip asking LLVM to optimize and generate code. Certain flags that control our LLVM configuration are mixed into the hash, but the -profile-generate flag was not one of them. This usually wouldn’t matter because profiling would insert additional code into the IR, but in edge cases like empty files or files containing only protocol declarations, it could cause linker errors when profiling was turned off.
This change adds the GenerateProfile flag into the IR hash, ensuring that we always recompile, even if the IR was identical.
Fixes rdar://problem/54126622.

@swift-ci please smoke test

This is for @eeckstein

Thanks for working on this. To be on the safe side, should other types of instrumentation be included here as well (say, {a,t}san)?

Question. Would it be possible to change this into some sort of exhaustive switch for Options? That way if someone adds a new option like this, they get a warning telling them that they may need to update this code.

In other words, I am worried that the code as written will cause this same bug to occur again. If we had some sort of switch associated with it, at least we could get a compile time warning in such a case. This will cause the writer to at least think about... should this be used in the IR hash?

It's only required for options that don't affect the IR as generated, but arguably being forced to say that explicitly would be nice. You could do this with a .def file but that might feel heavyweight.

@jrose-apple exactly. My fear is that someone will just add the option and not think about it. But if one at least has to explicitly do something, that can not happen.

@vedantk Good idea to check. -sanitize=address and -sanitize=thread emit different IR for an empty source file. -sanitize=undefined emits the same IR, but also the same assembly on x86_64 at least. -sanitize=fuzzer emits the same IR but different assembly, so that one should be mixed in too.

@gottesmm @jrose-apple I don't think the problem here is that someone forgot to update the function when they added an option; I think it's that someone didn't think about this edge case of an empty file, or didn't know about LLVM's behavior in this situation. -profile-generate doesn't usually need to be mixed into the flags because it will normally cause IR changes; only in files with no executable code does it behave incorrectly.

We could do that in +Asserts builds. We're only losing incrementality by doing so.

This is probably the most complicated and expensive "assertion" I've ever written, but it's in and it works.

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - ef3868fba3b7c8bf548ea413a3e33cc5e297f9fb

Build failed
Swift Test Linux Platform
Git Sha - ef3868fba3b7c8bf548ea413a3e33cc5e297f9fb

Thanks for the refactor!

@swift-ci please smoke test

@jrose-apple I mixed in all of the sanitizers, and also redesigned the hash slightly to avoid any issues when we add more sanitizers/optimization modes/values to these fields in general.

@swift-ci please smoke test


[Bug] validatePoliciesReadOnlyAccessAsync is missing from internalRevokePermissionsOnTopic

Search before asking

[X] I searched in the issues and found nothing similar.

Read release policy

[X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version
after 62c6f0872f65a9861c07fb3555d0364ddcd2d0c1 / PR #20478
Minimal reproduce step
validatePoliciesReadOnlyAccessAsync is missing from internalRevokePermissionsOnTopic
What did you expect to see?
validatePoliciesReadOnlyAccessAsync to be called like it's the case for internalGrantPermissionsOnTopic
What did you see instead?
The method call is missing
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@Technoboy- Do you have a chance to handle this?


Combine from different files?

Hello. Is possible combine from different files? I am using webpack and mini-css-extract-plugin.

Hello @bilalmalkoc. Plugin work only with one stream (like gulp) and it's not support combine from different files. Before sorting you need combine all files into one file or one stream.


[cmake-user] Test multi-config cmake usage

What does your PR fix?
Extends port cmake-user to cover usage with multi-config.
Confirms #26833. Validates #27369.

Which triplets are supported/not supported?
I am still working on this PR.

Example output,
buildtrees/cmake-user/x64-linux-3.24.0-find-package-ICU-release-out.log:
-- find_package(ICU) check: success
-- ICU_LIBRARIES: /home/dg0yt/vcpkg/installed/x64-linux/debug/lib/libicudata.a;/home/dg0yt/vcpkg/installed/x64-linux/debug/lib/libicudata.a
-- Configuring incomplete, errors occurred!

buildtrees/cmake-user/x64-linux-3.24.0-find-package-ICU-release-err.log:
CMake Error at CMakeLists.txt:103 (message):
  Unguarded debug lib during multi-config usage:
  /home/dg0yt/vcpkg/installed/x64-linux/debug/lib/libicudata.a

CMake Error at CMakeLists.txt:103 (message):
  Unguarded debug lib during multi-config usage:
  /home/dg0yt/vcpkg/installed/x64-linux/debug/lib/libicudata.a

Multi config will always be a bit buggy because of vendored/custom Find<pkg>.cmake scripts which doesn't concern themselves with multi config at all. There is also no way to fix it since adding vcpkg-cmake-wrappers for all those custom scripts is not really and option. Furthermore FindPkgConfig itself doesn't work in multi config.

Multi config will always be a bit buggy because of vendored/custom Find.cmake scripts which doesn't concern themselves with multi config at all.

I don't care much about vendored copies. All the tests in cmake-user are for Kitware's Find modules. Still, vcpkg gets the bug reports (cf. port giflib).
Results from CI, x64-windows release
-- Running tests with CMake 3.24.0 for 'release'
--   find_package(BZip2)
--   find_package(CURL)
--   find_package(EXPAT)
--   find_package(Fontconfig)
--   find_package(Freetype)
--   find_package(Intl)
CMake Error at scripts/test_ports/cmake-user/portfile.cmake:209 (message):
    CMake 3.24.0: configuration with `find_package(Intl)` failed.
    See logs for more information:
      D:/buildtrees/cmake-user/x64-windows-3.24.0-find-package-Intl-release-out.log
      D:/buildtrees/cmake-user/x64-windows-3.24.0-find-package-Intl-release-err.log

Call Stack (most recent call first):
  scripts/test_ports/cmake-user/portfile.cmake:232 (test_cmake_project)
  scripts/ports.cmake:147 (include)

--   find_package(GIF)
CMake Error at scripts/test_ports/cmake-user/portfile.cmake:209 (message):
    CMake 3.24.0: configuration with `find_package(GIF)` failed.
    See logs for more information:
      D:/buildtrees/cmake-user/x64-windows-3.24.0-find-package-GIF-release-out.log
      D:/buildtrees/cmake-user/x64-windows-3.24.0-find-package-GIF-release-err.log

Call Stack (most recent call first):
  scripts/test_ports/cmake-user/portfile.cmake:232 (test_cmake_project)
  scripts/ports.cmake:147 (include)

--   find_package(ICU)
--   find_package(Iconv)
CMake Error at scripts/test_ports/cmake-user/portfile.cmake:209 (message):
    CMake 3.24.0: configuration with `find_package(Iconv)` failed.
    See logs for more information:
      D:/buildtrees/cmake-user/x64-windows-3.24.0-find-package-Iconv-release-out.log
      D:/buildtrees/cmake-user/x64-windows-3.24.0-find-package-Iconv-release-err.log

Call Stack (most recent call first):
  scripts/test_ports/cmake-user/portfile.cmake:232 (test_cmake_project)
  scripts/ports.cmake:147 (include)

--   find_package(JPEG)
--   find_package(LibLZMA)
--   find_package(PNG)
--   find_package(PostgreSQL)
CMake Error at scripts/test_ports/cmake-user/portfile.cmake:209 (message):
    CMake 3.24.0: configuration with `find_package(PostgreSQL)` failed.
    See logs for more information:
      D:/buildtrees/cmake-user/x64-windows-3.24.0-find-package-PostgreSQL-release-out.log
      D:/buildtrees/cmake-user/x64-windows-3.24.0-find-package-PostgreSQL-release-err.log

Call Stack (most recent call first):
  scripts/test_ports/cmake-user/portfile.cmake:232 (test_cmake_project)
  scripts/ports.cmake:147 (include)

--   find_package(LibXml2)
CMake Error at scripts/test_ports/cmake-user/portfile.cmake:209 (message):
    CMake 3.24.0: configuration with `find_package(LibXml2)` failed.
    See logs for more information:
      D:/buildtrees/cmake-user/x64-windows-3.24.0-find-package-LibXml2-release-out.log
      D:/buildtrees/cmake-user/x64-windows-3.24.0-find-package-LibXml2-release-err.log

Call Stack (most recent call first):
  scripts/test_ports/cmake-user/portfile.cmake:232 (test_cmake_project)
  scripts/ports.cmake:147 (include)

--   find_package(LibXslt)
CMake Error at scripts/test_ports/cmake-user/portfile.cmake:209 (message):
    CMake 3.24.0: configuration with `find_package(LibXslt)` failed.
    See logs for more information:
      D:/buildtrees/cmake-user/x64-windows-3.24.0-find-package-LibXslt-release-out.log
      D:/buildtrees/cmake-user/x64-windows-3.24.0-find-package-LibXslt-release-err.log

Call Stack (most recent call first):
  scripts/test_ports/cmake-user/portfile.cmake:232 (test_cmake_project)
  scripts/ports.cmake:147 (include)

--   find_package(TIFF)
--   find_package(wxWidgets)
--   find_package(ZLIB)
--   find_package(ZLIBviaPkgConfig)

Closing this PR because it's been in draft without changes for more than a year. Please feel free to recreate or reopen!

Cannot reopen...

yes

Hmm... reopening a PR shouldn't require permissions

Hmm... reopening a PR shouldn't require permissions

It does, in this repo. And we are complaining almost every time.


Deployment failed: An image does not exist locally with the tag: default-route-openshift-image-registry.apps.domain6733fa.eastus.aroapp.io/project6733fa/image6733fa

Azure tenant: WAS-MSFT-TEAM
Resource group: ir-demoaro-dec3
Initial analysis of deployment failure:
{
"code": "DeploymentScriptError",
"message": "An image does not exist locally with the tag: default-route-openshift-image-registry.apps.domain6733fa.eastus.aroapp.io/project6733fa/image6733fa"
},

Full deployment failure:
{
    "status": "failed",
    "error": {
        "code": "DeploymentScriptError",
        "message": "The provided script failed with multiple errors. First error:\r\nConnecting to mirror.openshift.com (<IP_ADDRESS>:443). Please refer to https://aka.ms/DeploymentScriptsTroubleshoot for more deployment script information.",
        "details": [
            {
                "code": "DeploymentScriptError",
                "message": "Connecting to mirror.openshift.com (<IP_ADDRESS>:443)"
            },
            {
                "code": "DeploymentScriptError",
                "message": "saving to '/root/openshift-client-linux.tar.gz'"
            },
            {
                "code": "DeploymentScriptError",
                "message": "openshift-client-lin 100% |********************************| 47.1M 0:00:00 ETA"
            },
            {
                "code": "DeploymentScriptError",
                "message": "'/root/openshift-client-linux.tar.gz' saved"
            },
            {
                "code": "DeploymentScriptError",
                "message": "error: x509: certificate signed by unknown authority"
            },
            {
                "code": "DeploymentScriptError",
                "message": "No resources found in openshift-marketplace namespace."
            },
            {
                "code": "DeploymentScriptError",
                "message": "No resources found in openshift-marketplace namespace."
            },
            {
                "code": "DeploymentScriptError",
                "message": "No resources found in openshift-marketplace namespace."
            },
            {
                "code": "DeploymentScriptError",
                "message": "No resources found in openshift-marketplace namespace."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Error from server (NotFound): deployments.apps \"open-liberty-operator\" not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Error from server (NotFound): deployments.apps \"open-liberty-operator\" not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Error from server (NotFound): deployments.apps \"open-liberty-operator\" not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Error from server (NotFound): deployments.apps \"open-liberty-operator\" not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Error from server (NotFound): deployments.apps \"open-liberty-operator\" not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Error from server (NotFound): deployments.apps \"open-liberty-operator\" not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Error from server (NotFound): deployments.apps \"open-liberty-operator\" not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Error from server (NotFound): deployments.apps \"open-liberty-operator\" not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Error from server (NotFound): deployments.apps \"open-liberty-operator\" not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Error from server (NotFound): secrets \"htpass-secret\" not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Adding password for user manager"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Warning: resource oauths/cluster is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by oc apply. oc apply should only be used on resources created declaratively by either oc create --save-config or oc apply. The missing annotation will be patched automatically."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Warning: User 'manager' not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Warning: User 'manager' not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Warning: User 'manager' not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "SSH key files '/root/.ssh/id_rsa' and '/root/.ssh/id_rsa.pub' have been generated under ~/.ssh to allow SSH access to the VM. If using machines without permanent storage, back up your keys to a safe location."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Command ran in 64.533 seconds (init: 0.228, invoke: 64.304)"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Deployment failed. Correlation ID: 726809e8-8c22-4928-887d-f514be62b6f4. VM has reported a failure when processing extension 'liberty-aro-image-script'. Error message: \"Enable failed: failed to execute command: command terminated with exit status=1"
            },
            {
                "code": "DeploymentScriptError",
                "message": "[stdout]"
            },
            {
                "code": "DeploymentScriptError",
                "message": "amd64 2.4-1 [57.4 kB]"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Get:2 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 dbus-user-session amd64 1.12.2-1ubuntu1.2 [9392 B]"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Get:3 https://download.docker.com/linux/ubuntu bionic/stable amd64 containerd.io amd64 1.4.12-1 [23.7 MB]"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Get:4 http://azure.archive.ubuntu.com/ubuntu bionic/main amd64 libltdl7 amd64 2.4.6-2 [38.8 kB]"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Get:5 https://download.docker.com/linux/ubuntu bionic/stable amd64 docker-ce-cli amd64 5:20.10.11~3-0~ubuntu-bionic [38.8 MB]"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Get:6 https://download.docker.com/linux/ubuntu bionic/stable amd64 docker-ce amd64 5:20.10.11~3-0~ubuntu-bionic [21.2 MB]"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Get:7 https://download.docker.com/linux/ubuntu bionic/stable amd64 docker-ce-rootless-extras amd64 5:20.10.11~3-0~ubuntu-bionic [7920 kB]"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Get:8 https://download.docker.com/linux/ubuntu bionic/stable amd64 docker-scan-plugin amd64 0.9.0~ubuntu-bionic [3518 kB]"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Fetched 95.3 MB in 2s (60.6 MB/s)"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Selecting previously unselected package pigz."
            },
            {
                "code": "DeploymentScriptError",
                "message": "(Reading database ..."

            },
            {
                "code": "DeploymentScriptError",
                "message": "Unpacking pigz (2.4-1) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Selecting previously unselected package containerd.io."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Preparing to unpack .../1-containerd.io_1.4.12-1_amd64.deb ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Unpacking containerd.io (1.4.12-1) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Selecting previously unselected package dbus-user-session."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Preparing to unpack .../2-dbus-user-session_1.12.2-1ubuntu1.2_amd64.deb ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Unpacking dbus-user-session (1.12.2-1ubuntu1.2) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Selecting previously unselected package docker-ce-cli."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Preparing to unpack .../3-docker-ce-cli_5%3a20.10.11~3-0~ubuntu-bionic_amd64.deb ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Unpacking docker-ce-cli (5:20.10.11~3-0~ubuntu-bionic) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Selecting previously unselected package docker-ce."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Preparing to unpack .../4-docker-ce_5%3a20.10.11~3-0~ubuntu-bionic_amd64.deb ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Unpacking docker-ce (5:20.10.11~3-0~ubuntu-bionic) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Selecting previously unselected package docker-ce-rootless-extras."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Preparing to unpack .../5-docker-ce-rootless-extras_5%3a20.10.11~3-0~ubuntu-bionic_amd64.deb ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Unpacking docker-ce-rootless-extras (5:20.10.11~3-0~ubuntu-bionic) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Selecting previously unselected package docker-scan-plugin."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Preparing to unpack .../6-docker-scan-plugin_0.9.0~ubuntu-bionic_amd64.deb ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Unpacking docker-scan-plugin (0.9.0~ubuntu-bionic) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Selecting previously unselected package libltdl7:amd64."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Preparing to unpack .../7-libltdl7_2.4.6-2_amd64.deb ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Unpacking libltdl7:amd64 (2.4.6-2) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Setting up containerd.io (1.4.12-1) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /lib/systemd/system/containerd.service."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Setting up docker-scan-plugin (0.9.0~ubuntu-bionic) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Setting up dbus-user-session (1.12.2-1ubuntu1.2) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Setting up libltdl7:amd64 (2.4.6-2) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Setting up docker-ce-cli (5:20.10.11~3-0~ubuntu-bionic) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Setting up pigz (2.4-1) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Setting up docker-ce (5:20.10.11~3-0~ubuntu-bionic) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Setting up docker-ce-rootless-extras (5:20.10.11~3-0~ubuntu-bionic) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Processing triggers for systemd (237-3ubuntu10.52) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Processing triggers for man-db (2.8.3-2ubuntu0.1) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Processing triggers for ureadahead (0.100.0-21) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Processing triggers for libc-bin (2.27-3ubuntu1.4) ..."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Login Succeeded"
            },
            {
                "code": "DeploymentScriptError",
                "message": "The push refers to repository [default-route-openshift-image-registry.apps.domain6733fa.eastus.aroapp.io/project6733fa/image6733fa]"
            },
            {
                "code": "DeploymentScriptError",
                "message": "[stderr]"
            },
            {
                "code": "DeploymentScriptError",
                "message": "debconf: unable to initialize frontend: Dialog"
            },
            {
                "code": "DeploymentScriptError",
                "message": "debconf: (TERM is not set, so the dialog frontend is not usable.)"
            },
            {
                "code": "DeploymentScriptError",
                "message": "debconf: falling back to frontend: Readline"
            },
            {
                "code": "DeploymentScriptError",
                "message": "debconf: unable to initialize frontend: Readline"
            },
            {
                "code": "DeploymentScriptError",
                "message": "debconf: (This frontend requires a controlling tty.)"
            },
            {
                "code": "DeploymentScriptError",
                "message": "debconf: falling back to frontend: Teletype"
            },
            {
                "code": "DeploymentScriptError",
                "message": "dpkg-preconfigure: unable to re-open stdin:"
            },
            {
                "code": "DeploymentScriptError",
                "message": "debconf: unable to initialize frontend: Dialog"
            },
            {
                "code": "DeploymentScriptError",
                "message": "debconf: (TERM is not set, so the dialog frontend is not usable.)"
            },
            {
                "code": "DeploymentScriptError",
                "message": "debconf: falling back to frontend: Readline"
            },
            {
                "code": "DeploymentScriptError",
                "message": "debconf: unable to initialize frontend: Readline"
            },
            {
                "code": "DeploymentScriptError",
                "message": "debconf: (This frontend requires a controlling tty.)"
            },
            {
                "code": "DeploymentScriptError",
                "message": "debconf: falling back to frontend: Teletype"
            },
            {
                "code": "DeploymentScriptError",
                "message": "dpkg-preconfigure: unable to re-open stdin:"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Error response from daemon: manifest for icr.io/appcafe/open-liberty:full-java11-openj9 not found: manifest unknown: manifest unknown"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Error response from daemon: No such image: icr.io/appcafe/open-liberty:full-java11-openj9"
            },
            {
                "code": "DeploymentScriptError",
                "message": "WARNING! Using --password via the CLI is insecure. Use --password-stdin."
            },
            {
                "code": "DeploymentScriptError",
                "message": "WARNING! Your password will be stored unencrypted in /root/.docker/config.json."
            },
            {
                "code": "DeploymentScriptError",
                "message": "Configure a credential helper to remove this warning. See"
            },
            {
                "code": "DeploymentScriptError",
                "message": "https://docs.docker.com/engine/reference/commandline/login/#credentials-store"
            },
            {
                "code": "DeploymentScriptError",
                "message": "An image does not exist locally with the tag: default-route-openshift-image-registry.apps.domain6733fa.eastus.aroapp.io/project6733fa/image6733fa"
            },
            {
                "code": "DeploymentScriptError",
                "message": "\""
            },
            {
                "code": "DeploymentScriptError",
                "message": "More information on troubleshooting is available at https://aka.ms/VMExtensionCSELinuxTroubleshoot"
            },
            {
                "code": "DeploymentScriptError",
                "message": "Error from server (NotFound): deployments.apps \"app6733fa\" not found"
            },
            {
                "code": "DeploymentScriptError",
                "message": "The OpenLibertyApplication app6733fa is not available."
            }
        ]
    }
}

Please assign this to @majguo .

The root cause of the reported error (An image does not exist locally with the tag: default-route-openshift-image-registry.apps.domain6733fa.eastus.aroapp.io/project6733fa/image6733fa) can be found from the list of error messages:
{
    "code": "DeploymentScriptError",
    "message": "Error response from daemon: manifest for icr.io/appcafe/open-liberty:full-java11-openj9 not found: manifest unknown: manifest unknown"
}

From the inputs of the deployment, icr.io/appcafe/open-liberty:full-java11-openj9 is specified as the value of parameter appImagePath, which is required to be anonymously accessible without credentials. However, I verified that it can't be pulled with my local Docker:
docker pull icr.io/appcafe/open-liberty:full-java11-openj9
Error response from daemon: manifest for icr.io/appcafe/open-liberty:full-java11-openj9 not found: manifest unknown: manifest unknown

So, my suggestion is either changing the input value of appImagePath to be anonymously accessible, or enhancing the current offer by allowing user to provide credentials for accessing private images.

Please put a prominent info box on the Configure application blade that reminds the user they must ensure the image they are specifying is "anonymously pullable".

Please see https://github.com/WASdev/azure.liberty.aks/issues/13 for a similar overlap.

See thread discussion from Slack for more info about the root cause of the issue.


Intellisense can't find symbols for files in package hierarchy that aren't part of workspace

I have looked and do not see any tickets specifically addressing this issue, nor with explicit repro instructions to triage. My apologies if my search failed to find existing relevant tickets, but hopefully my repro instructions can help regardless.
Environment data

VS Code version: 1.55.2 and 1.56.0-insider
Extension version (available under the Extensions sidebar): 2021.4.765268190
OS and version: Win 10 20H2 (19042.928) x64 10.0.19042. WSL 2 using Ubuntu 20.04 (4.19.128-microsoft-standard)
Python version: 3.9.4 (Anaconda 4.10.1)
Type of virtual environment used : anaconda
Relevant/affected Python packages and their versions: all?
Relevant/affected Python-related VS Code extensions and their versions: no other extensions, disabled everything for repro.
Value of the python.languageServer setting: jedi | jediLSP

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
I wrote all the repro before starting this report. Pylance seems to work fine! HOWEVER, it is not the default language server. As such, I feel this is still valuable, although it may be a Jedi issue. I am happy to file this with them if that is the more appropriate place for this issue.
Expected behaviour
I am developing part of a shared package hierarchy. That is, my module 'labtech.utils.api' needs to reference elements of 'labtech.utils.log' which is not in the workspace, and is pip-installed from a separate repo/workspace. I expect typing
from labtech.utils.
would allow me to auto-complete and reference definitions of the 'log' package within there.
Actual behaviour
Working on a file in the 'api' package should be able to use Intellisense on symbols in the 'log' package that is pip-installed. Instead, because the 'labtech.utils' dir within the 'api' workspace lacks the 'log' code, intellisense sees nothing and only gives me elements from the current workspace - those under 'api' - which completely cripples intellisense. It is vice-versa for working on a file in 'log' and trying to reference 'api' or anything else besides 'log'
Everything works normally if the workspace doesn't contain the 'labtech' directory. (e.g. for something completely different)
Steps to reproduce:
Files and structure are in this repo for superb convenience: https://github.com/gegorohoff/vscode_intellisense_repro
WSL2 Bash:
    conda create --name goto_def python
    conda activate goto_def
    cd ~
    git clone git@github.com:gegorohoff/vscode_intellisense_repro.git goto_def
    cd goto_def
    # populate with contents. Should have ~/goto_def/pkg_A and ~/goto_def/pkg_B

    # The helper files don't YET work because the libraries aren't installed with pip:
    python pkg_A/labtech/utils/log/helper.py
    #   ModuleNotFoundError: No module named 'labtech.utils.log'
    python pkg_B/labtech/utils/api/helper.py
    #   ModuleNotFoundError: No module named 'labtech.utils.api'

    pip install ./pkg_A
    pip install ./pkg_B
    # You will see that ~/anaconda3/envs/goto_def/lib/python3.9/site-packages has labtech/utils/api and labtech/utils/log and associated libs underneath

    # The helper files now work:
    python pkg_A/labtech/utils/log/helper.py
    #   the logs are empty
    python pkg_B/labtech/utils/api/helper.py
    #   login failed
    python pkg_A/labtech/utils/log/runner.py # this imports labtech.utils.api.helper:Helper
    #   login failed

    # Now we open code to demonstrate the issue with intellisense
    code pkg_A

In Code, using workspace as directory pkg_A (not the root of this repro repo!):
    Set the Python interpreter to the goto_def conda env.

    Open the file labtech/utils/log/Runner.py
    Try intellisense on this 'Helper' or any part of this line.
        from labtech.utils.api.helper import Helper
    Try to re-write the import; note how you can only reference labtech.utils.log and nothing in labtech.utils.api which clearly works based on the output of the previous step.

Logs
https://github.com/gegorohoff/vscode_intellisense_repro/blob/main/vscode_python_log.txt

@gegorohoff Can you try setting this "python.autoComplete.extraPaths": [], to include packages outside of your workspace?
If that does not help then you might want to file a bug on https://github.com/davidhalter/jedi since we rely on that for intelisense. Also note that, Jedi (language server setting will be deprecated soon), JediLSP is the replacement for Jedi.
If you need to generate detailed logs you can do so by setting "python.trace.server": "verbose", in the User settings. This will generate language server logs under Output > Python Language Server panel.

@karthiknadig, in his bug report, @gegorohoff writes:

my module labtech.utils.api needs to reference elements of labtech.utils.log which is not in the workspace, and is pip-installed from a separate repo/workspace

Don't Jedi and JediLSP look at the current virtualenv for finding symbols?


[3|HR - Setting Page] Reveal Test Account

#88
We worked on it with @Euginia821
Added UI part, seeding data to DB and fetching Test account from DB

can you solve the conflict in src/app/hr/settings/page.tsx

can you solve the conflict in src/app/hr/settings/page.tsx

Resolved


Can you show the details of the compilation？

My camera is D435i, and the librealsense I have installed.  I'm not sure how to configure parameters， and I run the calibrate_radiometric_response, resulting in "Failed to create a grabber for camera realsense"

Unfortunately, I can not provide support with this camera. Try to debug the program and see what exactly goes wrong.

Thank you!
发送自 Windows 10 版邮件应用
发件人: Sergey Alexandrov
发送时间: 2020年7月14日 15:19
收件人: taketwo/radical
抄送: WangyuHIT; Author
主题: Re: [taketwo/radical] Can you show the details of the compilation？ (#13)
Unfortunately, I can not provide support with this camera. Try to debug the program and see what exactly goes wrong.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


[Beta 22] having various Metal clusters w/o having ingots registered

Not sure how long this is been happening, but Thaumcraft adds Copper, Tin, Silver, and Lead Clusters even w/o mods that add those ingots. That causes at least Mekanism, Magic Bees, and Binnie's Bees to have content related to those metals. Mekanism doesn't have a problem with Copper or Tin, since they have their own Copper and Tin Ingots, but Lead and Silver don't have any ingots with these mods.

So Mekanism tries to use silver and lead even though no mod generates it?

It's more Thaumcraft adds the clusters w/o any mod that adds ingots.

Yea but what difference does it make? If they're unobtainable and have no use there's no problem leaving it.

If I had to guess, these mods see that Thaumcraft has Lead Clusters, so they assume that there is Lead Ingots, so they load their features that use Lead.

I don't think the clusters are the problem, Thaumcraft also adds nuggets.
MagicBees checks if "nuggetMetalname" is initialized, but not if "blockMetalname" is. TC could maybe add a check to not register the nuggets if the metal is not present, but any other mod which only adds nuggets but no blocks could break MagicBees as well...

There won't be a simple way for me to disable specific nuggets in their current implementation. Not without breaking everyone's saves.
MagicBees should maybe check more than just nuggets in their code - it isn't too unreasonable to do.

Ok then, reporting to Magic Bees, thanks Azanor for checking it out


inochi-session: 0.8.5 -> 0.8.7, fix aarch64-linux

Things done
Now we can do VTuber stuff on Ampere Altra and Asahi NixOS!

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Seems fine, can't test it ATM.
Is this patch from somewhere, or did you come up with it for this PR?

Like the comment mentions, it comes from upstream.

Just noticed: PR and commit message says 0.8.5 instead of 0.8.4

Typo

Also, would it not make sense to also update inochi-creator?

Does creator use Lua as well and could have the same issue so a similar patch would have to be made?

Also, would it not make sense to also update inochi-creator?

Does creator use Lua as well and could have the same issue so a similar patch would have to be made?

Nope, just a version bump. But if you think it's better, we can keep it in another PR.

Ok, I got creator updated too.


RUNTIME_ASSERT fail without Terminate called without an active exception in BaseDaemon.cpp

What problem does this PR solve?
Issue Number: close #7451
Problem Summary:
What is changed and how it works?

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/cc @JaySon-Huang @breezewish @windtalker @ywqzzy

/merge


Video Captioning and VideoQA results

Hi,
Are the code and models available for Video Captioning and QA?
Thank you.

yes. it supports. Check out the following. Also updated the README about how to run inference on multiple images.
https://github.com/microsoft/GenerativeImage2Text/blob/bdc455b98a4bc9e20a3900be53d1018b6e8e02f3/generativeimage2text/layers/decoder.py#L846


Loyalty Program thankyou page

This is still WIP but would be nice if you could review this.

[x] Use the correct size of margins/paddings
[ ] Make it responsible (change the font sizes depending on the screen size)  we will re-visit this.
[x] Change the color for the "EARLY ACCESS" to gray
[x] When the user click the button the user should be taken to the homepage
[ ] Set up analytics we will re-visit this.

When the user click the button the user should be taken to... which page?

I’d think to the home page.

Set up analytics

That has to still happen for all pages, so maybe keep it out of the scope of this PR.
@xtina-starr Remind me, were you gonna talk to @anipetrov about the requirements here?

@xtina-starr Remind me, were you gonna talk to @anipetrov about the requirements here?

@alloy I did. They said they'd prioritize it next sprint (slack convo). There is a trello card for it but I don't know if an issue has been created. I'll follow up again.

Nice @yuki24 ! I think there's a tweak to the logic for which template to show (or redirect back to /loyalty), but looks great! 🎉

I just pushed some tweaks and I think this PR should be ready to merge.


Incorrect since value for AppInfo

The since value for appInfo in RegisterAppInterface states it was introduced in version 2.0. However the struct it uses as its type wasn't introduced until 4.2.
See here

Closed via https://github.com/smartdevicelink/rpc_spec/pull/311

Closed via https://github.com/smartdevicelink/rpc_spec/pull/311


feat(fx-2739): updates filter menu component styling

The type of this PR is: Enhancement
This PR resolves FX-2739
Description
https://user-images.githubusercontent.com/112297/113778132-084a2780-96fa-11eb-9166-f74f81dbf415.mov
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a CHANGELOG.yml entry or my changes do not require one.

Looks good 🎉 Feel free to merge once you solve the merge conflicts


TypeError: undefined is not an object (evaluating '_reactNative.NativeModules.RNSearchBarManager.ComponentHeight')

People have reported this is in the past. Not sure if it remains unfixed or if I'm experiencing a problem with my environment. I'm new to react-native so please bear with me.
I tried to create the most simple case I could to reproduce this. I'm on OS X 10.13.6.
console input:
expo init TestProject
cd TestProject
npm install
npm install react-native-search-bar@latest --save
react-native link react-native-search-bar
expo start

package.json:
{
  "name": "empty-project-template",
  "main": "node_modules/expo/AppEntry.js",
  "private": true,
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "eject": "expo eject"
  },
  "dependencies": {
    "expo": "^30.0.1",
    "react": "16.3.1",
    "react-native": "https://github.com/expo/react-native/archive/sdk-30.0.0.tar.gz",
    "react-native-search-bar": "^3.4.2"
  }
}

console output:
TypeError: undefined is not an object (evaluating '_reactNative.NativeModules.RNSearchBarManager.ComponentHeight')

This error is located at:
    in SearchBar (at App.js:10)
    in RCTView (at View.js:60)
    in View (at App.js:8)
    in App (at registerRootComponent.js:35)
    in RootErrorBoundary (at registerRootComponent.js:34)
    in ExpoRootComponent (at renderApplication.js:33)
    in RCTView (at View.js:60)
    in View (at AppContainer.js:102)
    in RCTView (at View.js:60)
    in View (at AppContainer.js:122)
    in AppContainer (at renderApplication.js:32)

This is a native library. Expo does not support native libraries.

You can try using the SearchBar from 'react-native-elements'  https://react-native-training.github.io/react-native-elements/docs/next/searchbar.html.

Oh, okay, thanks. Pardon the interruption.


Form or language contributors should use

to say "yes I understand the terms of this database: open and free for use, although proper citations are strongly requested and co-authorship opportunities encouraged whenever possible"

The Google form has following language:
I understand that contributed datasets will be made available under a CC-BY or similar license. This means that the COSORE database will be open without restriction to the science community; we encourage database users to cite original publications and offer co-authorship, but it's not required.
I have all necessary authority and permissions (legal or otherwise) to provide these data to the COSORE database.


Security Review

We need to put the app through security review. Any help you can provide would be great.

Closed as we are through security review!


CI intermitent failures

We are chasing some bugs on CI (different from https://github.com/openservicemesh/osm/issues/2661).
It seems the client envoy receives a Unknown error code 104 details Connection reset by peer.
Last failure observed: https://github.com/openservicemesh/osm/runs/2041825948?check_suite_focus=true
Seems envoys are not getting SDS popuilated/unwarmed properly, and getting stuck with uninitialized SSL socket (NotReadySslSocket)

Dataplane/SMI       [X]

Environment:

OSM version (use osm version): main (3/5/2021)
Kubernetes version (use kubectl version): 1.18

Corrected summary, not TCP related. Found by @shashankram :)

The failures in the CI seem to be due to some sort of a race in osm-controller resulting in the SDS config not being realized. In all the failures I have looked at, the SSL socket is not ready.
2021-03-05T17:59:18.703510532Z stderr F [2021-03-05 17:59:18.702][14][debug][config] [source/extensions/transport_sockets/tls/ssl_socket.cc:422] Create NotReadySslSocket

ENVOY_LOG(debug, "Create NotReadySslSocket");
stats_.upstream_context_secrets_not_ready_.inc();

This indicates the secrets haven't been pushed, or they aren't warmed in Envoy.

Another symptom of this (most likely) bug is the presence of dynamic_warming_secrets or generally warming in the Envoy config.
This script uses osm and kubectl CLIs to search for warm in Envoy configs:
#!/bin/bash

for ns in $(kubectl get namespaces --no-headers | awk '{print $1}' | grep -Ev '^kube-'); do
    for pod in $(kubectl get pods -n $ns --no-headers | grep Running | cut -d' ' -f1); do
        echo -e "Checking $ns/$pod"
        ./osm proxy get config_dump -n $ns $pod | grep warm || true
    done
done

Relevant PRs:

[ ] envoy/ads: program upsteam's service cert when making all secrets #2939
[ ] xds: handle wildcard TypeURI #2938
[ ] pkg/ticker: reintroduce ticker concept #2937

Another symptom of this (most likely) bug is the presence of dynamic_warming_secrets or generally warming in the Envoy config.
This script uses osm and kubectl CLIs to search for warm in Envoy configs:
#!/bin/bash

for ns in $(kubectl get namespaces --no-headers | awk '{print $1}' | grep -Ev '^kube-'); do
    for pod in $(kubectl get pods -n $ns --no-headers | grep Running | cut -d' ' -f1); do
        echo -e "Checking $ns/$pod"
        ./osm proxy get config_dump -n $ns $pod | grep warm || true
    done
done

Relevant PRs:

[ ]  envoy/ads: program upsteam's service cert when making all secrets #2939
[ ]  xds: handle wildcard TypeURI #2938
[ ]  pkg/ticker: reintroduce ticker concept #2937

This bug manifested itself while troubleshooting issue #2930
I have been able to repro more often than not with the following demo script: https://gist.github.com/draychev/787e2b9f63e99dba0f0290351825f89c

Note: remove the readinessProbe, which may mask the bug

@draychev the secrets might initially be in warming state, but should eventually transition to active. Would you mind augmenting your script to keep polling for a certain duration instead to check if they ever transition from warming to active?
$ osm proxy get config_dump azure-vote-front-78dc4ff55b-w5jn4 -n test | grep -A 2 warming
     "warming_state": {
      "version_info": "2",
      "listener": {
--
     "warming_state": {
      "version_info": "2",
      "listener": {
--
     "warming_state": {
      "version_info": "2",
      "listener": {
--
   "dynamic_warming_secrets": [
    {
     "name": "root-cert-for-mtls-inbound:test/azure-vote-front",
$ osm proxy get config_dump azure-vote-front-78dc4ff55b-w5jn4 -n test | grep -A 2 warming
$ osm proxy get config_dump azure-vote-front-78dc4ff55b-w5jn4 -n test | grep -A 2 warming

There were multiple issues, some of which have been addressed.

[X] SDS secrets not being pushed correctly
[X] SDS assumption regarding service and service account names
[ ] XDS state machine dropping requests with the same version but newer subscriptions


Mark jax typing Protocols as @runtime_checkable

Please:

[x] Check for duplicate requests.
[x] Describe your goal, and if possible provide a code snippet with a motivating example.

Goal: Ensure "isinstance" works to check if a type (not a value) is a jax Array type.
Problem: When deserializing data containing jax arrays, one must check if the types are jax Array types. However, "jaxlib.xla_extension.ArrayImpl is jax.Array" evaluates False (normal, but annoying)
Opportunity: Could we make these typing protocols runtime checkable to faciliate serialization/deserialization logic?
TLDR Fix: from typing import runtime_checkable & use @runtime_checkable decorator on Protocol subclasses
Reproduction
import jax, jax.numpy as jnp
from jax._src.typing import DuckTypedArray
from jaxlib.xla_extension import ArrayImpl

def test_jaxlib__extensions_arraylike_is_array():
    try:
        assert ArrayImpl is jax.Array, f"{ArrayImpl=} is not {jax.Array=}"
    except Exception as e:
        print(f"{e=}")
    print("This is normal.")

def test_duck_typed_array_is_runtime_checkable():
    arr = jnp.ones(3, int)
    print("arr", arr)
    assert isinstance(
        arr,
        DuckTypedArray,
    ), "jax._src.typing.DuckTypedArray is not runtime_checkable"

test_jaxlib__extensions_arraylike_is_array()
test_duck_typed_array_is_runtime_checkable()

Result

System:
../jax (main) $
> python -c 'import jax; jax.print_environment_info()'
jax:    0.4.31.dev20240627+4c70a94c8
jaxlib: 0.4.30
numpy:  1.26.4
python: 3.12.0 | packaged by conda-forge | (main, Oct  3 2023, 08:43:22) [GCC 12.3.0]
jax.devices (1 total, 1 local): [cuda(id=0)]
process_count: 1
platform: uname_result(system='Linux', node='WIN-QVRBL09D89C', release='<IP_ADDRESS>-microsoft-standard-WSL2', version='#1 SMP Fri Mar 29 23:14:13 UTC 2024', machine='x86_64')

$ nvidia-smi
Thu Jun 27 11:25:54 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 555.52.01              Driver Version: 555.99         CUDA Version: 12.5     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 4090        On  |   00000000:01:00.0  On |                  Off |
|  0%   50C    P2             29W /  450W |   19984MiB /  24564MiB |      1%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A      4192      C   /python3.12                                 N/A      |
|    0   N/A  N/A    198001      C   /python3.12                                 N/A      |
+-----------------------------------------------------------------------------------------+

References / Links (not strictly needed)
[1] from a Python array API standard, but it's really long to paste here.
[2] Another resource for protocols is DLPack C API, seems clear on data type sizes of things
Here's the short notes on those, I'll add class attributes to the tree_plus eventually, but it can get noisy.

Workaround
from typing import TypeGuard

from jaxlib.xla_extension import ArrayImpl

import jax, jax.numpy as jnp

# test_duck_typed_array_is_runtime_checkable()
def is_jax_array_type(type_x: type, *, debug: bool = DEBUG) -> bool:
    if type_x is ArrayImpl:
        decision = True
    elif type_x is jax.Array:
        decision = True
    else:
        decision = False

    if debug:
        print(f"is {type_x=} a jax.Array? {decision=}")

    return decision

def is_jax_array_value(x: Any, *, debug: bool = DEBUG) -> TypeGuard[jax.Array]:
    type_x = type(x)
    return is_jax_array_type(type_x, debug=debug)

def test_typeguard_workaround():
    arr = jnp.ones(3, int)
    print("arr", arr)
    arr_is_jax_array = is_jax_array_value(arr)
    print(f"{arr_is_jax_array=}")
    assert (
        arr_is_jax_array
    ), "the is_jax_array TypeGuard[jax.Array] failed to classify a jax Array"
    assert not is_jax_array_value(1)
    assert not is_jax_array_value(False)
    assert not is_jax_array_value((1, 2, 3))

test_typeguard_workaround()

Cheers, love me some jax!

Assigning @superbobry because he has thought a lot about this kind of typing issue, and may have good feedback!

I don't mind making DuckTypedArray runtime-checkable, but the guarantees these runtime checks give are pretty weak. In particular, they do not do any type checking:
>>> from typing import Protocol, runtime_checkable
>>> @runtime_checkable
... class P(Protocol):
...   def f(self) -> int: ...
...
>>> class A:
...   f = 42
...
>>> isinstance(A(), P)
True

Note also, that DuckTypedArray only has two methods and thus the runtime check is equivalent to hasattr(..., "shape") and hasattr(..., "dtype"), which means that e.g. a NumPy array will be considered an instance of DuckTypedArray. Is that the behavior you expect?

Oh, you're right, that wouldn't work, since it would make code think it sees jax arrays when it sees numpy arrays.
I just want to round-trip serialize/deserialize all the things, and hit a situation where I needed to check if a type is jax.Array or not, but T is jax.Array didn't work for ArrayImpl. The typeguard function solved my problem, could be fine to just stick with that.
Seems like a lot of python typing is still Work in Progress, if there's a solution which python type system supports better than protocols, like dataclasses or abstract base classes, just hopeful we can support both type and value level checks, so we can handle both the abstract case to check if type T is jax Array, and the concrete case to check if value V is an instance of a jax Array
I'm agnostic about the implementation details, so whatever you think is best with the state of Python, I'm down to test it

jax.Array is a base class, so to check if x is a JAX array you can use isinstance(x, jax.Array), or to check if T = type(x) is an array type, you can use issubclass(T, jax.Array).

sounds good! only thing i'd add would be, make sure to use try/except with issubclass, it's pretty flaky, crashes with annotations (oof)

given that, here's a working solution with issubclass, thank you ! closing
from typing import TypeGuard, Any

from jaxlib.xla_extension import ArrayImpl
import jax, jax.numpy as jnp

def is_jax_array_subclass(x: type) -> bool:
    "check if a type is a subclass of jax.Array"
    try:
        return issubclass(x, jax.Array)
    except Exception as _e:
        return False

def is_jax_array(x: Any) -> TypeGuard[jax.Array]:
    "check if a value is an instance of jax.Array"
    try:
        return is_jax_array_subclass(x.__class__)
    except Exception as _e:
        return False

def test_is_jax_array_subclass():
    assert is_jax_array_subclass(jax.Array)
    assert is_jax_array_subclass(ArrayImpl)
    assert not is_jax_array_subclass(tuple[int, ...])
    assert not is_jax_array_subclass(jnp.ones(3))

def test_is_jax_array():
    assert not is_jax_array(jax.Array)
    assert not is_jax_array(ArrayImpl)
    assert not is_jax_array(tuple[int, ...])
    assert is_jax_array(jnp.ones(3))

test_is_jax_array_subclass()
test_is_jax_array()


JSON-RPC deserialization exception during initialization

I've recently started getting this error in VS2022 when loading up a project using Svelte:

More info from the VS logs.
Newtonsoft.Json.JsonSerializationException: Deserializing JSON-RPC result to type InitializeResult failed with JsonSerializationException: Exception of type 'Newtonsoft.Json.JsonSerializationException' was thrown.
   at StreamJsonRpc.JsonMessageFormatter.JsonRpcResult.GetResult[T]()
   at StreamJsonRpc.JsonRpc.<InvokeCoreAsync>d__143`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.LanguageServer.Client.JsonRpcExtensionMethods.<SendMethodRequestAsync>d__1`2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.LanguageServer.Client.RemoteLanguageClientInstance.<SendInitializeRequestAsync>d__101.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.LanguageServer.Client.RemoteLanguageClientInstance.<InitializeAsync>d__100.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.VisualStudio.LanguageServer.Client.RemoteLanguageClientInstance.<InitializeAsync>d__100.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Threading.ThreadingTools.<WithCancellationSlow>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.LanguageServer.Client.RemoteLanguageClientInstance.<ActivateLanguageClientAsync>d__107.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)

My VS version:
Version 17.1.6
VisualStudio.17.Release/17.1.6+32421.90
The Svelte For Visual Studio extension is updated to the latest 1.9.0 version.

Thanks for the report. It is a new feature in the svelte language server that is incompatible. I release 1.19.2 with a downgraded deps version. And would see what can I to fix this in the upstream.

Working nicely again with 1.9.2, thanks!


Improve docs for the getting started guide for oauth2_proxy

I want to enable people to use Dex with Bitly's OAUTH2 proxy. These are some
docs and fixture improvements to make that work really quickly.
See the PR here: https://github.com/bitly/oauth2_proxy/pull/163

Can I merge now? :)

@philips No you can't, because I already did!


WASD Camera stuck

Describe the bug
WASD camera controls get stuck if released during loading events.
To Reproduce
Steps to reproduce the behavior:

Hold down a WASD key
Trigger a "loading" event in game (walking to a new area, teleporting to unrendered area, taking a boat, etc)
Release the WASD key during the loading event
See error

Expected behavior
Screen rotation should stop.
Environment (please complete the following information):

OS: Windows
RuneLite version: 1.5.1
Launcher version: 1.5.2

Duplicate of #6548


Change compiler options

/intelci: run

What are the reasons of these changes?

This change is required to workaround changes in new compiler that exposed problem with zero relocation in core library


Float docs TOC navbar when scrolling

Some of the doc pages, like the walkthrough, have a navigation bar linking to the subheaders on the page. This changes that sidebar to float with you as you scroll, so that you don't have to jump back up to the top to navigate to another section in the page.
Preview available at https://deploy-preview-1994--svc-cat.netlify.com/docs/walkthrough/

Really nice & many thanks for the live preview link.  LGTM


vectordb = Chroma.from_documents(texts, embeddings) is giving error!

Please help me with same error.
Everytime,I restart  the notebook,it is throwing same error.

This code  works for me second time again after restarting it throw same error
class MyDocument:
def init(self, text, metadata=None):
self.text = text
self.metadata = metadata
self.page_content = text  # add this line to define page_content attribute
metadata = [{'source': str(i)} for i in range(len(texts))]
documents = [MyDocument(text, metadata=metadata[i]) for i, text in enumerate(texts)]
docsearch = Chroma.from_documents(documents, embeddings)

The square bracket for builtin types syntax (list[str]) only works from Python 3.9 onwards.
This is fixed in https://github.com/chroma-core/chroma/issues/160 just need to pip install 'chromadb>=0.3.5'
Or use at least Python 3.9

While Creating the Chain Getting ValidationError: 1 validation error for LLMChain
prompt
none is not an allowed value (type=type_error.none.not_allowed)

The square bracket for builtin types syntax (list[str]) only works from Python 3.9 onwards.
This is fixed in chroma-core/chroma#160 just need to pip install 'chromadb>=0.3.5'
Or use at least Python 3.9

not working at all. using python 3.10 and chromedb version already >= 0.3.5
this is not solved.

You can solve the problem by import the following library
from langchain.vectorstores.chroma import Chroma
I face the same problem. I solve my problem by importing the above library.
I hope it will be helpful for you.

I continually get this error, although I've run pip install chromadb on my Mac.

Looks like they still haven't fixed it. Similar issue with from_texts


Add paysonwallach.com

Hey! Make sure to read thoroughly through the readme 😉 you were supposed to include where on your site the webring logo is. Are you able to fix the merge conflict?

I'm terribly sorry! I can't believe I missed that. The logo is on the homepage.


test: flaky test udp_recv_in_a_row

not ok 412 - udp_recv_in_a_row
# exit code 6
# Output from process `udp_recv_in_a_row`:
# Assertion failed in /Users/runner/work/libuv/libuv/test/test-udp-recv-in-a-row.c on line 54: `sizeof(send_data) == nread` (10 == 0)

That's the consequent in this if statement:
https://github.com/libuv/libuv/blob/874363f652f0aafb3ed58a4da65940258e5ee713/test/test-udp-recv-in-a-row.c#L53-L57
And this comment may be relevant:
https://github.com/libuv/libuv/blob/874363f652f0aafb3ed58a4da65940258e5ee713/test/test-udp-recv-in-a-row.c#L63-L68

Also happens on macOS

No, only on macos (so far anyway.) See also https://github.com/libuv/libuv/pull/4344#discussion_r1516908865.


01-What is an Object? 就算按翻译说明2来看：原文和译文是不是差的有点远？

翻译说明：
2. 由于中英行文差异，完全的逐字逐句翻译会很冗余啰嗦。所以本人在翻译过程中，去除了部分主
题无关内容、重复描写。
原文：
The genesis of the computer revolution was in a machine. Our programming languages thus tend to look like that machine.
But computers are not so much machines as they are mind amplification tools ("bicycles for the mind," as Steve Jobs was fond of saying) and a different kind of expressive medium. As a result, tools are beginning to look less like machines and more like parts of our minds.
Programming languages are the fabric of thought for creating applications. Languages take inspiration from other forms of expression such as writing, painting, sculpture, animation, and filmmaking.
Object-oriented programming (OOP) is one experiment in using the computer as an expressive medium.
Many people feel uncomfortable wading into object-oriented programming without understanding the big picture, so the concepts introduced here give you an overview of OOP. Others might not understand such an overview until they are exposed to the mechanism, becoming lost without seeing code. If you're part of this latter group and are eager to get to the specifics of the language, feel free to jump past this chapter---skipping it now will not prevent you from writing programs or learning the language. However, come back here eventually to fill in your knowledge so you understand why objects are important and how to design with them.
This chapter assumes you have some programming experience, although not necessarily in C. If you need more preparation in programming before tackling this book, work through the Thinking in C multimedia seminar, freely downloadable from www.OnJava8.com.
译文：
计算机革命的起源来自机器。编程语言就像是那台机器。它不仅是我们思维放大的工具与另一种表达媒介，更像是我们思想的一部分。语言的灵感来自其他形式的表达，如写作，绘画，雕塑，动画和电影制作。编程语言就是创建应用程序的思想结构。
面向对象编程（Object-Oriented Programming OOP）是一种编程思维方式和编码架构。本章讲述 OOP 的基本概述。如果读者对此不太理解，可先行跳过本章。等你具备一定编程基础后，请务必再回头看。只有这样你才能深刻理解面向对象编程的重要性及设计方式。

对照原文看了01-What is an Object? 感觉更像是笔记，而不是原文的翻译。


feat: 🔥 update CRA

Generate Source Map must be off (cf facebook/create-react-app#11767)
The craco config should be the bare minimum to polyfill the lib used.
Move some deps to devDependencies

Ah wrong repo 😬


Addresses issue where fetch fails while repo is in detached head state.

Codecov Report

Merging #227 into master will increase coverage by 1.75%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #227      +/-   ##
==========================================
+ Coverage   57.76%   59.51%   +1.75%
==========================================
  Files          85       85
  Lines        4231     4503     +272
==========================================
+ Hits         2444     2680     +236
- Misses       1551     1581      +30
- Partials      236      242       +6

Impacted Files
Coverage Δ

snapshot/git/gitdb/checkout.go
46.23% <100%> (+1.18%)
:arrow_up:

runner/runners/polling.go
68.57% <0%> (-9.69%)
:arrow_down:

binaries/scheduler/main.go
0% <0%> (ø)
:arrow_up:

scootapi/server/setup.go
0% <0%> (ø)
:arrow_up:

sched/scheduler/cluster_state.go
96.22% <0%> (+1.35%)
:arrow_up:

runner/runners/status_manager.go
88.03% <0%> (+1.78%)
:arrow_up:

snapshot/git/gitdb/bundlestore.go
50.84% <0%> (+1.82%)
:arrow_up:

runner/runners/queue.go
98.66% <0%> (+2.23%)
:arrow_up:

sched/scheduler/stateful_scheduler.go
76.34% <0%> (+2.29%)
:arrow_up:

ice/eval.go
94.26% <0%> (+4.13%)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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


Clarify number of held-out workloads in documentation

Make sure that the documentation accurately reflects that we use 6 held-out workloads for scoring as opposed to 8.

Addressed in https://github.com/mlcommons/algorithmic-efficiency/pull/640/files


add potentiometer for setting extrusion speed for main extruder

installation depends on issue #12
coding can be done in parallel

closing this because we can control speed via gcode and analog reading of potentiameter in ESP seems to have very poor resolution


WAF Sensors can not match the rule

Environment
Platform: K8s
Kubernetes/Platform Version(s): v1.19.1
Neuvector Version: preview-3
Describe the bug
I'm not sure if this is a bug,maybe it is my configuration issue；
I have configure rgxp to waf sensors,like this:

we can see that "and 1=1" can matched rgxp .
Then i add this policy to dvwa group:

Then i access dvwa and test it,but the payload can not match the waf rule.

I want to know why,who can tell me the reason or principle，there are many rgxp that come from imperva signature can not match the waf sensors rule.
The rgxp come from imperva waf signature,imperva waf can matched it.
Thanks!

Your regex pattern looks good, please go to network activity page and right click the group you are testing and select packet capture, then you can submit the form(sql injection), then stop and save capture. Please attach your pcap file here. Thanks

01119c16cf2b4b2409a90a99e2c9f2fbc3f0aba82aa097235cddfb50f3ac87bbcb32c869.pcap.zip
Hi
I upload the capture packet,pls help check

source ip : <IP_ADDRESS>
dest ip: <IP_ADDRESS>
you can filter out the <IP_ADDRESS>
i tigger the traffic by "and 1=1" ,there is no any custome waf rule  log

Hi
As I expected, the url request is url encoded and also there are other characte in the url request. I provided a solution regex in attached picture.
Regards,


Adding review changes from PR 15604

Fixes #16211. Created a table with volume type and feature state support for PV expandable feature.
Ref: https://github.com/kubernetes/website/pull/15604

/assign @bradtopol
/cc @gnufied

/lgtm

I have squashed all the commits into one. Can @sftim & @jaypipes review again and approve this PR, please?

/lgtm
/approve


Hide user's listings when user account is disabled

Listings should not be considered active.

https://github.com/yzernik/squeakroad/pull/516


feat: add tooltip trigger

Brief Information
This pull request is in the type of (more info about types):

[ ] build
[ ] ci
[ ] docs
[x] feat
[ ] fix
[ ] perf
[ ] refactor
[ ] test

Related issues (all available keywords):

close #692

Details

Added a TooltipTrigger component with a question mark icon (accepts color and size as a string).

Added a tooltip visibility toggle at the top of the page

Added a small margin at the bottom for the main content (it could overlap with the operating system navigation menu)

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA

Others

Demo:
https://github.com/hypertrons/hypertrons-crx/assets/32329117/788d1878-9dcb-4a8c-99fd-e4d76924c825

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Vlad116 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi, Harry) Sure, i can move the icon like on your screnshot and edit tooltip area how on it, also remove switch.
I did not move TooltipTrigger to components, because often non-reusable components are made as subcomponents with index file.
Okay, I'll correct all comments. Could you clarify on the 5th point what exactly is wrong with the organization of the code if we abstract from the points indicated earlier?

Is the current icon right for you? @wxharry

I was expecting an information mark like in the previous screenshot if possible.

Hi, Harry) Sure, i can move the icon like on your screnshot and edit tooltip area how on it, also remove switch. I did not move TooltipTrigger to components, because often non-reusable components are made as subcomponents with index file.

I understand. I was expecting it to be resuable because we are planning some new features in this option page, so we might reuse the tooltips in the near future.

Could you clarify on the 5th point what exactly is wrong with the organization of the code if we abstract from the points indicated earlier?

Sure. For example, you could refer to src/pages/ContentScripts/features/developer-networks to extract the icon. I understand it might not be the best way to do this, but we need to keep it identical within the project. Thanks for understanding.

Hello!)
I tried to make a dark background with transparency like in your screenshot, but it turned out to be not so easy with the implementation of the tooltip in this library. I removed the switch (and moved the TooltipTrigger to shared components), brought the tooltips to the following form:

Are there any other changes needed to the current version or will we be able to close this PR soon? @wxharry

Are there any other changes needed to the current version or will we be able to close this PR soon? @wxharry

Slow down. Thanks for your passion but there is no need to rush. I am running some tests and thinking about some improvements.

Are there any other changes needed to the current version or will we be able to close this PR soon? @wxharry

Slow down. Thanks for your passion but there is no need to rush. I am running some tests and thinking about some improvements.

Of course, I'll just find out if any more updates are needed, I will check this thread once a day to find out

It's fine if we cannot make it transparent. just make it to the default style as before will do.

It's fine if we cannot make it transparent. just make it to the default style as before will do.

I'm update MR and add fix default style for TooltipTrigger

@wxharry  Okay, no problem. I can change to default cursor style, sorry for awaiting


has this network spec been implemented?

https://github.com/zero-os/0-orchestrator/tree/despiegk-specs/specs/gateway

Yes


Ignore IntelliJ IDEA files

@satterly This kind of ignore belongs in a personal gitignore file, not for the project. http://stackoverflow.com/questions/5724455/can-i-make-a-user-specific-gitignore-file

Didn't know you could do that. Thanks.


有没有更详细的文档材料？

No there is no more documentation then what is in the readme. (used Google translate to understand the question :sweat_smile: )


Add link to Erik's company in STEERING.md

I checked that this was the correct site in standup on 2024-09-10!

/approve
/lgtm


Add release notes for v0.5.0

Signed-off-by: Harsh Vardhan<EMAIL_ADDRESS>

Codecov Report

Merging #138 (cbf1c53) into develop (c28dff9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #138   +/-   ##
========================================
  Coverage    69.96%   69.96%
========================================
  Files           26       26
  Lines         2151     2151
========================================
  Hits          1505     1505
  Misses         630      630
  Partials        16       16

Continue to review full report at Codecov.

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


Fix Unpublishing update bug

When updating an existing Unpublshing record, we erroneously returned
a boolean from update_attributes instead of returning the updated object.
Add a test and return the value expected by client code.
@benhyland and @davidslv

👍


stage: fix block signature back-compatibility under Ruby 1.8.7

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[X] Have you successfully ran brew tests with your changes locally?

Description
The new stage() signature introduced by #66 breaks back-compatibility under Ruby 1.8.7. This fixes it by switching back to a one-argument block signature and using a new class to wrap both the Resource and Mktemp info for the staging context. It's done in a signature-back-compatible way, using duck typing to be compatible with Resource for where Formula DSL was using it.
I think the block-argument design is much better than using globals. This lets us keep the block design but switch to a fully back-compatible signature for Formula API purposes.
Tested under Ruby 2.0 and 1.8.7 on OS X 10.9.5. Testing log here. Worked fine for me, and I verified that it fixes the breakage with docbook, cracklib, dcadec, and odt2txt.
Closes homebrew/homebrew-core#529

:+1: Too bad none of us thought of this, but I'm happy you found an elegant solution.

(Should probably also close Homebrew/homebrew-core#524 when it's merged.)

Merging this now since it's a regression with end user impact. If anyone finds issues with it, just let me know by commenting here.

(In the longer term, maybe all those stage and brew methods should switch to a single XxxContext block argument, for consistency, and to avoid potential future problems with adding arguments to the yield-block signature instead of additional methods to the block context parameter. But want to fix existing breakage first, with minimal changes.)

Thanks for fixing this so quickly and 👍 to immediately merging regression fixes.


[website] Update main data grid demo on X landing page

[x] I have followed (at least) the PR section of the contributing guide.

Preview: https://deploy-preview-37001--material-ui.netlify.app/x/

I'm coming from a recent regression in https://search.google.com/search-console/core-web-vitals/drilldown?resource_id=sc-domain%3Amui.com&item_key=CAIQAhgD

A few things I can spot we can improve:

Runtime issue. I don't think that we can keep the demo like this: https://deploy-preview-37001--material-ui.netlify.app/x/

https://github.com/mui/material-ui/assets/3165635/28fd1fa2-573e-489a-b2f1-8b5d5bac0057
Maybe the issue comes from that we render too many rows, but it seems to be 10,000 it's not 100,000, I would expect it to be much faster. I would feel more comfortable with what we were displaying before.

Reduce the row height, it feels almost x2 too tall for the use cases of aggregation. Since the height is small, we can only see 3.4 rows. It's limiting to analytics the data set.

The image displays https://pagespeed.web.dev/analysis/https-mui-com-x/yeun3a5279?utm_source=search_console&form_factor=desktop&hl=en

Set the height on the images so the layout doesn't jump https://pagespeed.web.dev/analysis/https-mui-com-x/yeun3a5279?utm_source=search_console&form_factor=desktop&hl=en

For example, we can copy what's done in https://mui.com/core/, it doesn't jump.

@oliviertassinari

Runtime issue. I don't think that we can keep the demo like this: deploy-preview-37001--material-ui.netlify.app/x.

This performance issue is tracked in https://github.com/mui/mui-x/issues/8579, we are working on a fix.

Every now and then, the grouping is broken, I get this:

Yes, we had an issue with data generator 😅 It's fixed now 👍

Regarding the rest of your points - I will submit a PR to address them, thanks for your feedback!

@cherniavskii Awesome thanks, very thorough.


Handle data with multiple clusters

From @sarnoldlds:

The clusters don’t necessarily have to be on different pressure levels (could also be different location etc).
In the trajectory file header there is a field called “CLUSTER POINTERS”. These are the trajectory numbers that correspond to the first trajectory in each cluster. In this case, they are just sequential consecutive numbers as there is only one trajectory per cluster. In other examples, there may be more than one per cluster and these numbers give the first in each cluster.
The usual way the model and the clusters would work is that the trajectories within a single file would have the same time of release (in some whole reanalysis interval  -in our case a 3 hour UT time point within the day to align with the reanalysis data times). The clusters would then be at different pressure or location releases at that same time. This is the case for the example ALPACA files I sent you.
The release at different times is a specific case for the model which is not actually the standard operation. I don’t think I have so far used clusters with timed release but it could be an option.

Commit 1d2b287 includes initial work to handle clustered data structure in trajectory plotting code, but this needs to be extended to implement plotting for data with multiple clusters. Need to decide how this will be done e.g. could use different colours for clusters.


Allow Docker to connect with long IDs

Currently, Docker connections only succeed when the 12 character
"short ID" of a container is used. When a full container ID is
provided, connections fail despite the container being present
and running. This is because the Docker transport searches for the
container ID in the output of docker ps and docker ps only returns
short ID values unless the --no-trunc flag is used.
This commit updates the connection logic to pass the --no-trunc flag
and match container IDs using start_with? instead of an equality
check.
Fixes puppetlabs/bolt#2791.

The commit message already has a !bug tag --- it's missing from the PR description because I added it after the check failed.


whalebird: 4.5.4 -> 4.6.0

Description of changes

changelog: https://github.com/h3poteto/whalebird-desktop/releases/tag/4.6.0
notable changes:

upgrades vue 2.6.14 -> 3.2.31
fixes spoiler button style

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 176181 run on x86_64-linux 1

1 package built:

whalebird

closing in favor of #176476


TF 2.9.0 and TFDF 0.2.5 no distribution found messages

Dear Gentlemen,
I tried to install TFDF according to Compatibility table and I an got error:
(metal-venv) jayokocha@Aleksandrs-MacBook-Pro Light_weight_network % pip install tensorflow-decision-forests==0.2.5
ERROR: Could not find a version that satisfies the requirement tensorflow-decision-forests==0.2.5 (from versions: 0.2.3, 0.2.4, 1.0.1, 1.1.0, 1.2.0)
ERROR: No matching distribution found for tensorflow-decision-forests==0.2.5

Hi,
Tensorflow Decision Forests 0.2.5 was not released for MacOS, so please use an earlier version of TF-DF, if possible.
Additional note: We've recently gotten reports that TF-DF is incompatible with tensorflow-metal. If you experience this issue, please let us know.

Hi! Yes, I'm using tensorflow-metal. Earlier version of TF-DF incompatible with TF 2.9.0

Closing this since we have a parallel discussing in https://github.com/tensorflow/decision-forests/issues/152#issuecomment-1436571168


Update README.md

Added instruction to update the keras.json to use Theano

Thanks for this change!


Added requireDefaultRecords to AccountPage

Added requireDefaultRecords function to AccountPage as it is needed to use the checkout.

Thanks for the pull request, @RVXD. One small thing - would you mind squashing these commits into one so we can keep the commit log clear and easier to make sense of? (https://ariejan.net/2011/07/05/git-squash-your-latests-commits-into-one/ - you can just force push to your same branch to update this PR)
On a bigger picture note, I wonder if the config setting here should be moved to ShopConfig and defaulted to true. That would be a backwards-incompatible change so would have to wait for 2.0 unless we checked for both values in which case it could be a 1.1 thing. At minimum I'd say we ought to add these flags to example_config.yml so they can get some use. @jedateach do you have any thoughts about that?

Sorry if I confused the issue here. I'm happy to merge this PR once it's squashed and we can deal with the configuration issues in another PR.

Thanks for your reply. I'll try to 'squash' the commits into one and request a pull again.
The config setting is also in other requireDefaultRecords, that's why I copied it in.

I squashed these and merged this manually. Welcome to the committers list, @RVXD


Does holoscan-sdk support GPUs with Kepler architecture (e.g. NVIDIA Quadro K4000)?

Please describe your question
We are trying to use holoscan-sdk with a machine with NVIDIA Quadro K4000 (Kepler architecture). We wonder if holoscan-sdk support GPUs with Kepler architecture? It would be great if you share steps on what we can do in the case that Kepler architecture is not supported.
Thanks, Miguel

Hi @mxochicale , thanks for reaching out. We do not support Kepler architecture in Holoscan SDK testing at this time. For alternatives please refer to the Holoscan SDK user guide for discrete GPU and driver requirements.


[Feature]: Option to hide Type errors originating due to undefined data properties

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
The user wants an option to hide the errors originating from undefined data properties. Usually, these can be safely ignored  as they'll go away when the data is available later in the app flow.
Why should this be worked on?
This pollutes the error pane and can lead to a user missing other important errors like query failures etc.

@pranavkanade  They can use nullish coalescing to prevent these errors from throwing up. eg: {{appsmith.store.name ?? "Anonymous"}}


bug(COMPONENT): TITLE

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Expected: The page does not have a scroll bar. The HTML tag is not added with cdk-global-scrollblock.
Actually:  When zoom the browser to 90%,drag the browser so that the width of the body is 1398.890px and there is no horizontal or vertical scroll bar.as a result,  body.scrollWidth is 1399px,  viewport.width is 1398px. cdk-global-scrollblock is added to the html tag.
private _canBeEnabled(): boolean {
// Since the scroll strategies can't be singletons, we have to use a global CSS class
// (cdk-global-scrollblock) to make sure that we don't try to disable global
// scrolling multiple times.
const html = this._document.documentElement!;
if (html.classList.contains('cdk-global-scrollblock') || this._isEnabled) {
  return false;
}

const body = this._document.body;
const viewport = this._viewportRuler.getViewportSize();
return body.scrollHeight > viewport.height || body.scrollWidth > viewport.width;

}
Reproduction
Steps to reproduce:

zoom the browser to 90%,
2.drag the browser so that the width of the body is 1398.890px

Expected Behavior
The page does not have a scroll bar. The HTML tag is not added with cdk-global-scrollblock.
Actual Behavior
The page does not have a scroll bar. The HTML tag is added with cdk-global-scrollblock.
Environment

Angular: 14.2.0
CDK/Material: 14.2.0
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): window 10

Could you provide a stackblitz example of the issue using the latest version of Angular? This would make verifying and debugging the issue much easier on our end


Add description to the repo

The repo currently has no description:
No description or website provided.

Maybe something like this could be used:
A collection of easy to use JavaScript helpers.

@peregrinogris, nice catch! I would use the one that already exists on the readme:

A JavaScript utility library oriented to real world tasks

@hmammana, do you have permissions to do this? Because I can't.

I asked around and only the architecture team can modify this. I'll check if there are other public repos that need to add/modify its description, so they can update all at once.

Closed! Thanks to @fyadon.


Update packages for release 0.2.0

This PR updates the packages for the 0.2.0 release. I was able to conda-build locally, as well as install all the updated packages with a conda env.
After this PR is merged, I will proceed with the release by bumping the version in the setup.py and the following steps for both pypi and conda-forge.
For the regressions discussions check https://github.com/coiled/coiled-runtime/issues/526
cc: @hayesgb

The failure on the pip build is because there was a release of coiled that is already up on pypi but not on conda-forge yet. I would ignore it for the time being.
E       AssertionError: assert <Version('0.2.51')> == <Version('0.2.50')>

tests/runtime/test_build.py:115: AssertionError


Adds option to disable public IP address

This PR adds a variable to the tfvars option so that a user can disable a public IP in AWS when standing up via a terraform

Sorry this never got merged David :(