{portal} Migrate to AAZ

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). After that please run the following commands to enable git hooks:
pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

Please make sure the following breaking change are by design

❌Azure CLI Extensions Breaking Change Test

❌portal
rule
cmd_name
rule_message
suggest_message
❌ 1008 - ParaPropAdd
portal dashboard import
cmd portal dashboard import update parameter name: added property required=True
please remove property required=True for parameter name of cmd portal dashboard import


Missing form on neuro research page

The following paragraph appears under Registering for Independent Study on the neuro research page:
"In order to register for Independent Study, you need a Special Course Approval form. These forms can be found on this website under student resources Special Course Form or they can be found at the Neuroscience Advising office in room 638 Weiss Hall."
I can't find this form anywhere. Any ideas (besides deleting the part about finding it online)?

Hey Sarah! So they never had a form for this in doc or pdf, uploaded to the old site under student resources. I would just remove the "available online" text. Thanks!

Great, thanks!

You are more than welcome!


Improved, Fixed and Added Features

Descriptive Summary
Fixes / Improved / Enhanced:

Fixed Code Structure: Placed the files where they should belong and changed the code with their new location reference.
Fixed Sidebar: Added link attribute to sidebar and rearranged the sidebar alphabetically also added attribute for links to be opened in new tab as well.
Improved Go to Top Button: Made the Go to top button matching to that of our theme.
Improved copyright text formatting and added link attribute to be used in future reference.

Added New Feature:

Added Most important social channels to the footer. (Footer is changed accross all the pages)
Added option in the drop-down menu to contribute to Projects which will bring users to Algo-Phantoms to contribute to project issues at ease.

List any dependencies that are required for this change
None are required
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ✔] New feature (non-breaking change which adds functionality)
[ ✔] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

Locally, XAMPP and GitHub Pages
Changes can be previewed here

Checklist:

[✔ ] My code follows the style guidelines of this project
[✔] I have performed a self-review of my own code
[ ✔] My changes generate no new warnings
[ ✔] New and existing unit tests pass locally with my changes

Looking forward to contribute more with major fixes and improvements issues!

@harikesh409 @ravikr126 Can you look into the pull request?

Nice @cmulay


Just cloned the repo and the configuration package does not exist

This import import com.porterhead.integration.configuration.ApplicationConfiguration;  does not allow to compile.

Thanks for that.
Did not realise I had missed pushing those files


fix(snap): defer service startup till after configure hook runs

This PR modifies the way the snap install and configure hooks when the snap in installed in order to ensure that snap configuration provided at install time is processed before services are started. This is working around an issue with snapd where snap configuration at install time is not made available to the snap until the configure hook is called, which is after the services have already been started.
So, this PR disables all of the services in the install hook, and then in the configure hook, the services are started after configuration has been processed.

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[*] I have added unit tests for the new feature or bug fix (if not, why?)

units tests to be added before this is taken out of draft status

[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[NA] I have opened a PR for the related docs change (if not, why?)

This fix relates to the install behavior of the snap, and as such should be transparent to the installer.

Testing Instructions

Install the snap built from this PR and verify that all of the expected services start
Confirm that device-virtual can be enabled ($ sudo snap set edgexfoundry device-virtual=on)
Confirm that kuiper can be enabled ($ sudo snap set edgexfoundry kuiper=on); ensure that both kuiper and app-service-configurable are started
Confirm that support-notifications and support-scheduler can be started (e.g. snap set... support-scheduler=on)
Confirm that security-proxy can be disabled ($sudo snap set security-proxy=off)

Additional test instructions will be added to this PR as it progresses. The more advanced cases require a custom gadget snap which provides default configuration. This is currently the only way to disable secret-store usage. If possible, this PR will be extended to support dynamically disabling secret store usage, but this is currently blocked on issue #3712.
Also note, this has been tested using our in-progress checkbox provider for Jakarta and all of the tests pass.
New Dependency Instructions (If applicable)

FYI, just force pushed a minor update to address a minor gofmt error which was tripping up the CI build.

Just a general comment that the change to remove the device-virtual service seems to be also deleted but it isn't mentioned in the commit messages or the PR description.

Just a general comment that the change to remove the device-virtual service seems to be also deleted but it isn't mentioned in the commit messages or the PR description.

@anonymouse64 First, thanks for review!
Re: your device-virtual comment, if you look again, you'll notice that what I removed was an actual case statement for device-virtual. That's because the original case for device-virtual in handleAllServices had additional logic to re-enable core-data and core-metadata when device-virtual is enabled.  In the Ireland (2.0) release of EdgeX, device services now publish events direct to the message bus by default, so core-data is no longer a hard-dependency. Regarding core-metadata, if it's not running the whole system falls apart, so we should really remove the ability to disable it, but I decided to leave that for another day. Since there are no dependencies to handle, device-virtual is simply handed like any other service without dependencies (i.e. by the default case).

You can upgrade the edgex-snap-hooks to use the newly added function. See https://github.com/canonical/edgex-snap-hooks/releases/tag/v2.1.0
go get<EMAIL_ADDRESS>
I've explained here that the EnabledServices function is not useful when called in the install hook.

I just force-pushed a rebase which uses the new edgex-snap-hooks version @farshidtz recently published. This uses the new UnsetConfig and StartMultiple methods. I've re-run the checkbox tests against the snap, and all continue to pass.

Just force-pushed a rebase to update go.mod/go.sum to edgex-snap-hooks 2.1.1 to pickup @siggiskulason's fix for TLS configuration.

Just pushed a new commit which enables the Secret Store to be disabled at runtime. Thanks again @farshidtz for figuring out issue #3712.

Closing as this PR has now been superseded by PR #3813.


Upgrade to python 3.10

Codecov Report

Merging #28 (767d966) into master (0a4324e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #28   +/-   ##
=======================================
  Coverage   91.48%   91.48%
=======================================
  Files          23       23
  Lines        1210     1210
=======================================
  Hits         1107     1107
  Misses        103      103

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 0a4324e...767d966. Read the comment docs.


add swap for windows, add debug for macos, rerender

Checklist

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

Debug build issues

Could you try removing
https://github.com/conda-forge/ray-packages-feedstock/blob/548b853555ba75c89151eb2bdf9b8da8c705d048/recipe/build-core.sh#L11
?

cc @h-vetinari
This all seems so fragile. The windows builds are newly failing with
external/com_google_protobuf/upb/message/internal/message.c(22): error C2099: initializer is not a constant

and macOS arm64 is newly failing with
In file included from external/zlib/zutil.c:10:
In file included from external/zlib/gzguts.h:20:
In file included from /Users/runner/miniforge3/conda-bld/ray-packages_1730357054105/_build_env/include/c++/v1/stdio.h:108:
/Applications/Xcode_15.2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.0.sdk/usr/include/stdio.h:210:7: error: expected identifier or '('
  210 | FILE    *fdopen(int, const char *) __DARWIN_ALIAS_STARTING(__MAC_10_6, __IPHONE_2_0, __DARWIN_ALIAS(fdopen));
      |          ^
external/zlib/zutil.h:147:33: note: expanded from macro 'fdopen'
  147 | #        define fdopen(fd,mode) NULL /* No fdopen() */

It would be nice if we could refactor bazel build to use the conda-provided system libraries instead of building everything from source.

Anyhow, to the point of the PR: the macOS x64_86 builds show CXXFLAGS has -stdlib=libc++ just before the build:
CXXFLAGS=-march=core2 -mtune=haswell -mssse3 -ftree-vectorize -fPIC -fstack-protector-strong -O2 -pipe -stdlib=libc++ -fvisibility-inlines-hidden -fmessage-length=0 -isystem /Users/runner/miniforge3/conda-bld/ray-packages_1730357074667/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh/include -fdebug-prefix-map=/Users/runner/miniforge3/conda-bld/ray-packages_1730357074667/work=/usr/local/src/conda/ray-core-2.38.0 -fdebug-prefix-map=/Users/runner/miniforge3/conda-bld/ray-packages_1730357074667/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh=/usr/local/src/conda-prefix

Could you try removing ...

I removed all the bug-fixes I put in over what is needed for a cross-platform build. Let's see which are still needed

This blog post provides a recipe for using system libraries in a bazel build.

@h-vetinari looking again at the exploded compilation arguments, I see
-isysroot __BAZEL_XCODE_SDKROOT__ \
    -f__BAZEL_XCODE_SDKROOT__/System/Library/Frameworks \
    -f__BAZEL_XCODE_DEVELOPER_DIR__/Platforms/MacOSX.platform/Developer/Library/Frameworks \

That seems wrong. I think the __BAZEL_XCODE_SDKROOT__ is meant to be replaced with an actual path, maybe from the $SDKROOT env variable?

Yeah that looks suspect. You can try and check if you find something on the bazel-toolchain feedstock related to the SDK that bazel uses. If there's nothing there, then it's likely coming from bazel itself.

My bad, I need to use the bazel-toolchain recipe on both arm64 and x86_64 builds. If I recall correctly, on the macOS-12 image, using it on x86_64 broke the build, but on later images it is required.

This PR is part of #188, closing.


Update kubernetes to a supported version

In the Plattform Setup guide, the used k8s version is v1.18.19 (see kind create cluster --name apollo --image kindest/node:v1.18.19) and this version is a little bit outdated and EOL was on 18 Jun 2021.
Bumping k8s version to a supported one, we need to keep in mind that we also have to update a lot of dependencies like istio / knative / postgres operator etc.

Resolving this requires the following updates to be made:

[ ] Update the tutorials in the website
[ ] Update the Ephemeral Network CRD as CRDs seem to be checked more rigorously in newer versions in K8s which leads to the ports not being set.
[ ] Perform an E2E test

@strieflin PR have been reviewed.
E2E test successful (Millionaires Problem) as described by the updated instructions

Thank you @sbckr and @varasu for helping with this. All PRs have been merged. Closing this.


Bug: Cypress command {selectall} is not captured by Lexical

Lexical version: 0.3.8
Steps To Reproduce

Write any cypress test that types text and then select it using .type('{selectall}')

Example: cy.get('myText').type('It should be selected').type('{selectall}');
The current behavior
$getSelection would be null, but window.getSelection() would have proper data

The expected behavior
Lexical should capture selectall command and update selection

It seems to work fine in cypress v10, and selectall command itself is also handled properly
https://user-images.githubusercontent.com/132642/183543568-4e34b0ee-00f5-45cb-9a32-f2e33bb1b579.mov
https://user-images.githubusercontent.com/132642/183543598-ae22093f-3415-44f7-bc06-4f2c50d2c41a.mov

Will close for now, feel free to reopen if have steps to reproduce


Feature/plugin support

XRTK - Mixed Reality Toolkit Pull Request
Overview
Added plugin utility

Gotta get it passing CI/CD first. I think I need to open a PR on the main repo to add an assembly definition to the LeapCSharp files

@acolgan I'd also like your blessing about this strategy as well.

Blocked by https://github.com/leapmotion/UnityModules/pull/1111

leapmotion/UnityModules#1111 has been merged into UnityModules/develop.


[MXNET-1434] Fix a broken link for basic C++ tutorial

Description
Fix a broken link for basic C++ tutorial
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Restarted the unix-cpu test...

Thanks!


Added support for multiple Azkaban Host URL

Currently Auto Tuning does not support job execution IDs from different azkaban host and it fails while calling azkaban rest api. This PR have changes to support multiple azkaban host and it also takes care of creating new session every hour for azkaban rest api.

I have approved the changes only to unblock you guys. Please make sure you address them asap.


mint button is not showing and it keeps loading

Open your network tab, resource is probably throwing 404 error. Change candyMachineInfo.js accordingly. Note that collection name should be same as the config.json

yeah, it worked. how can i use arweave to upload nfts?

I am getting the same error, what exactly should I do?

in candyMachineInfo.js(frontend) file the collection name should be the same as the config.json file.

yeah, I am getting the same error. what i do?

Yes I have the same loading issue even that the config.js and candyMachineInfo.js have the same collection name? really grateful if someone knows what could be the issue

Get this error in consol


Windows: Review cannot read from SOLR

The Tomcat part does not reach SOLR

It was a specific user problem, probably due to his computer port configuration


Modify error string "Could not load unit test config from launch.json" to be more specific about which fields are missing

I had a lot of trouble getting "justMyCode" = false to work because I kept getting "Could not load unit test config from launch.json". This was despite that fact that launch configs showed up fine in the debug configuration dropdown and that debugging worked.
The issue was a missing "version" attribute in launch.json but I had to read the source to find this. I'm posting an issue hoping that the error message is improved or maybe it helps somebody else, this error bugged me for quite a while.
The following message is seen in "Python" output tab:
Error 2020-10-13 02:54:01: could not get debug config [Error: malformed launch.json
	at _.readAllDebugConfigs (/home/leonard/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:931824)
	at runMicrotasks (<anonymous>)
	at processTicksAndRejections (internal/process/task_queues.js:94:5)
	at async _.readDebugConfig (/home/leonard/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:932663)
	at async _.getLaunchArgs (/home/leonard/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:932363)
	at async _.launchDebugger (/home/leonard/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:931326)
	at async h.runTest (/home/leonard/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:1036991)
	at async c.runTestImpl (/home/leonard/.vscode-oss/extensions/ms-python.python-2020.9.112786/out/client/extension.js:56:1034988)]

Exception is thrown from here: https://github.com/microsoft/vscode-python/blob/main/src/client/testing/common/debugLauncher.ts#L58
You can probably reproduce this by removing "version" from launch.json.

Hi there thanks for suggesting this! A more specific error message would help.

Hi @karrtikr! I would like to take this issue as my first OS contribution, can I get a green light from someone to work on this?

@ShahzaibP Sure go ahead

Hi, does this issue have any pending tasks?

Hi, does this issue have any pending tasks?

Nope thanks to @ShahzaibParacha this can be closed. Thanks for reminding!

Nope thanks to @ShahzaibParacha this can be closed. Thanks for reminding!


Backend forms and event creation

Going to also add a thing for the leaderboard, just so that it's ready to go.


int(simd.h): Make the simd types trivially_copyable

Basically, this is a way of saying memcpy of any of these simd types is fine. It doesn't matter a lot for OIIO itself, but it helps quiet some static analysis warnings for OSL.

Could the approach from https://github.com/AcademySoftwareFoundation/OpenImageIO/pull/4110#discussion_r1451873540 be used?

Could the approach from #4110 (comment) be used?

I think that can't work in this case (I tried) because these types contain a union. I've tried a bunch of different things, and I can't seem to coax C++ into figuring it out on its own for these oddball types, even though we humans know that it's just memory and are indeed trivially copyable.

In my quick test it seems to work: https://gcc.godbolt.org/z/bdxYbY7dv (toggle the #if to see the assert fail and then pass with the default). Could it be maybe that there's only some of the classes that won't work?

Just as an update, looking into this sent me down a rathole that might end up being a much larger overhaul to the simd internals. Will post an update in a few days, I'm working on it in dribs and drabs.

I'm going to withdraw this PR and start a new one, I got this working in a better way.


When navigation is prevented, URI path should not change

Preventing navigation in router works as it does keep the previous context, but the behavior is  different when trying to navigate through page links or history buttons, in the first case the URI is kept and aligned with the active view, but in the case of back/forward buttons URI and view are not aligned.
The screen-shot attached for the code in the snippet demonstrates the issue
import { Router } from '@vaadin/router';

const routes = [
    {
        path: '(.*)',
        action: async (cfg) => {
            const elm = document.createElement('div');
            elm.textContent = 'Hi ' + cfg.pathname;
            elm.onBeforeEnter = function(ctx, args) {
                return window.preventNavigation && args.prevent();
            }
            return elm;
        }
    }
];

const router = new Router(document.querySelector('#outlet'), {});
router.setRoutes(routes);

duplicate of #329


Error when building image

Hey, I tried building the image for pg14 and I'm getting the following errors
Step 8/22 : RUN go get -u github.com/timescale/timescaledb-backup/ || true &&     cd<EMAIL_ADDRESS>&&     sed -i 's/github.com\/timescale\/ts-dump-restore/github.com\/timescale\/timescaledb-backup/g' go.mod &&     cd cmd/ts-dump &&     go mod tidy &&     go build -o /usr/local/go/bin/ts-dump &&     cd ../ts-restore &&     go mod tidy &&     go build -o /usr/local/go/bin/ts-restore
 ---> Running in 521db1870e5c
go: go.mod file not found in current directory or any parent directory.
	'go get' is no longer supported outside a module.
	To build and install a command, use 'go install' with a version,
	like 'go install example.com/cmd@latest'
	For more information, see https://golang.org/doc/go-get-install-deprecation
	or run 'go help get' or 'go help install'.
/bin/sh: cd: line 1: can't cd to<EMAIL_ADDRESS>No such file or directory
The command '/bin/sh -c go get -u github.com/timescale/timescaledb-backup/ || true &&     cd<EMAIL_ADDRESS>&&     sed -i 's/github.com\/timescale\/ts-dump-restore/github.com\/timescale\/timescaledb-backup/g' go.mod &&     cd cmd/ts-dump &&     go mod tidy &&     go build -o /usr/local/go/bin/ts-dump &&     cd ../ts-restore &&     go mod tidy &&     go build -o /usr/local/go/bin/ts-restore' returned a non-zero code: 2

Thanks for the heads up. I've just pushed a fix for this, to install only with the binaries instead of using go get. I'm also pushing a new image for Postgres 14 👍


ItemsRepeater - slow scrolling performance

Hello!
I`ve attached a small sample with ItemsRepeater. I use the data-dependent layout sample from [this] (https://docs.microsoft.com/en-us/windows/uwp/design/layout/attached-layouts#virtualizing-layouts) article. I notice that scrolling is slow. If I set HorizontalCachLength and VerticalCacheLength to 0, the scrolling becomes faster.
Steps to reproduce the bug
Steps to reproduce the behavior:

Open and run project in attachment
Scroll items by mouse. Notice, that perfomance of scrolling is slow.
Open app.xaml and add HorizontalCacheLength="0" VerticalCacheLength="0" properties to ItemsRepeater.
Run app again and notice, that scrolling becomes faster.

Version Info
Windows 10 1903 (OS Build 18362.1082)
WinUI 3.0.0-preview2.200713.0
Windows app type:

UWP
Win32

Yes

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Project:
App24.zip

@ranjeshj can you weigh in?

possibly the same issues as https://github.com/microsoft/microsoft-ui-xaml/issues/3008


🐛 Fixed Free album should be downloadable

Fixed Login prompt will happen once user click buy button

Fix for #150


WIP - 150 - Support for yaml extension in project conf files

Description
Support for yaml (and potentially others) extension in project config files
Related Issue
https://github.com/Nike-Inc/brickflow/issues/150
Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] 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.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Is this PR ready for review?

Not yet, I still need to add tests to cover the changes


bosh interpolate does not merge objects

When we use bosh interpolate with more than one vars file, we don't see nested properties merging.
For example, with the following YAML files.
test.yml
d: ((a.b))
e: ((a.c))

vars1.yml
a:
  b: testing

vars2.yml
a:
  c: 123

When we run bosh int test.yml --vars-file vars1.yml --vars-file vars2.yml, we expected to see:
d: testing
e: 123

When we actually see:
Finding variable 'a.b':
  Expected to find a map key 'b' for path '/b' (found map keys: 'c')

Exit code 1

Is this intended behaviour?

It looks like there is a great library that can do this out of the box™.

Connected to #117, I am not sure if the great library will fix that case as well.

@cppforlife has informed that this issue is intentional.

@cppforlife: I think there might be some inconsistent behaviour.
If we present the vars yml file above using dot notation instead of YAML object notation, it works.
vars1.yml
a.b: testing

vars2.yml
a.c: 123

When we run bosh int test.yml --vars-file vars1.yml --vars-file vars2.yml, we see:
d: testing
e: 123

Why is this different?


[TASK] Rook should error out if there are missing required parameters in testers

Issue Description
Is your feature request related to a problem? Please describe.
Rook should raise an error in case of missing parameters in Differs or Testers (if required)
Describe the solution you'd like
Just a RAISE should suffice
Describe alternatives you've considered
N/A

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

Approved to close via #1164.


Fix double check current missing

Updated tests
Made an oopsie --> current balance must be gte 2x bet not lte

Lesson learnt: run tests in the pipeline when merging! Practice what you preach!


Add CodeBuild job for Sidetrail tests.

**Issue #469 **
Description of changes:
Add Configs to create CodeBuild jobs for SideTrail.
Reworked some scripts so a pre-built smack Docker image can be used in CodeBuild to significantly speed-up run times.
HOLD on this... between github actions and building a smack docker image- this work might not be needed.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Is this still relevant?

Closing as #1534 moves sidetrail into codebuild.


fix empty placeholder not shown on remove from group

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes

If the last element is removed from a group, an empty placeholder for the group is not shown on outliner tree.
Following steps can reproduce this:

import the following flow

[{"id":"e14b8c7f.8eac5","type":"tab","label":"Flow 1","disabled":false,"info":""},{"id":"d49ec8fc.6158c8","type":"group","z":"e14b8c7f.8eac5","style":{"stroke":"#999999","stroke-opacity":"1","fill":"none","fill-opacity":"1"},"nodes":["6b15a0dc.9f785"],"x":175,"y":80,"w":80,"h":80},{"id":"6b15a0dc.9f785","type":"comment","z":"e14b8c7f.8eac5","g":"d49ec8fc.6158c8","name":"","info":"","x":215,"y":120,"wires":[],"l":false}]

select comment node
Select menu item: Groups > Remove from group
empty placeholder for the outer group is not shown on outliner as follows:

Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 77.335% when pulling 842cd1ecf0e1ee95763f76a3147c42070fc2f282 on node-red-hitachi:fix-remove-from-group into 81a4f4267364ae748e85ff0f225496e01e6261a0 on node-red:dev.

Thanks for this. On my todo list are two other related items:

The Global Configuration nodes entry does not have an 'empty' entry
The 'Subflows' entry does not have an 'empty' entry

Could you take a look at fixing those?

Hi.  I'll check them.

Commit a fix to make Subflows and Global Configuration Nodes be  able to have empty placeholder at the beginning.


chore: semantic-release setup

:tada: This PR is included in version 1.0.0-develop.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Create dependabot.yml

.github/dependabot.yml
version: 2
updates:

  - package-ecosystem: "github-actions"
    directory: "/"
    schedule:
      interval: "weekly"

  - package-ecosystem: "gomod"
    directory: "/"
    schedule:
      interval: "weekly"

@fxamacker after you review this, I'll open same PR for fxamacker/cbor.


docs: documentation added for callbacks middleware

Description
This PR adds documentation for the callbacks middleware.
closes: #4050
Commit Message / Changelog Entry
docs: documentation added for callbacks middleware

see the guidelines for commit messages. (view raw markdown for examples)

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (see CONTRIBUTING.md).
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] ~Code follows the module structure standards and Go style guide.~
[x] ~Wrote unit and integration tests.~
[x] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[x] ~Added relevant godoc comments.~
[x] Provide a commit message to be used for the changelog entry in the PR description for review.
[x] Re-reviewed Files changed in the Github PR explorer.
[x] Review Codecov Report in the comment section below once CI passes.

Do you think that with the information you have added in section Interfaces this PR can also close https://github.com/cosmos/ibc-go/issues/3350?

Yes, I think so @crodriguezvega. So, let's aim to close it with this PR too?


Build failure: nyx

Steps To Reproduce
Steps to reproduce the behavior:

Add nyx as package.
Run nyx by itself or with flags.

Build log
Traceback (most recent call last):
  File "/nix/store/448af4xx2al196xsh8q7wamk14mcjz6h-nyx-2.1.0/bin/.nyx-wrapped", line 6, in <module>
    from nyx.__init__ import main
  File "/nix/store/448af4xx2al196xsh8q7wamk14mcjz6h-nyx-2.1.0/lib/python3.11/site-packages/nyx/__init__.py", line 767, in <module>
    import nyx.panel.log
  File "/nix/store/448af4xx2al196xsh8q7wamk14mcjz6h-nyx-2.1.0/lib/python3.11/site-packages/nyx/panel/log.py", line 69, in <module>
    NYX_LOGGER = log.LogBuffer(log.Runlevel.DEBUG, yield_records = True)
                 ^^^^^^^^^^^^^
AttributeError: module 'stem.util.log' has no attribute 'LogBuffer'

Notify maintainers
@offlinehacker
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.8.11-xanmod1, NixOS, 24.11 (Vicuña), 24.11.20240603.4a4ecb0`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/store/fjs1x9gz2n1dvjqcyyl6qsw110qxc2zn-source`

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

https://github.com/torproject/nyx/issues/15

pushed a commit to gentoo/gentoo that referenced this issue on Mar 6, 2022

That time frame sure is disheartening.

Closed as completed; but I can reproduce the original issue. @Layer-09, do you know the current state of affairs?

The nyx project is deprecated, and the last commit was from two years ago. The original issue in their repo has not seen a solution and probably never will, @iblech.
With that in mind, I suppose this would be the ideal time to ping somebody and request the removal of this broken package. Perhaps @dawidd6 or @offlinehacker are aware of the correct way to go about this.

Tor Metrics and TorMap provide an easy way to find details about your relay, though not to the extent of a monitoring application such as nyx.
If you're interested in seeing details per session, you may use systemctl status tor.service to see the total of internet data you contributed (e.g. 60GB) until that moment. The internet panel in btop allows you to see how much data you contribute per second.
Other than that, there is Wireshark if you want analyze internet traffic thoroughly, @iblech.

Thank you for your comprehensive answer, @Layer-09, very much appreciated!


Failed to resolve component

Failed to resolve component: Vue3Lottie
If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.
Not working in Nuxt3, done according to provided guidelines
import { Vue3Lottie } from 'vue3-lottie'

export default defineNuxtPlugin((nuxtApp) => {
  nuxtApp.vueApp.component(Vue3Lottie, { name: 'Vue3Lottie' })
})

Nuxt: 3.9.3

Regular import works well
<template>
    <client-only>
      <Vue3Lottie :animationData="animationData" :height="200" :width="200" />
    </client-only>
</template>

<script setup lang="ts">
import { Vue3Lottie } from 'vue3-lottie'
</script>

Thank you @Mini-ghost, i'll make those changes in the docs

This solution from @Mini-ghost returns same error for me, and when using import it works using animationLink, but not working when using json file.


Travis-CI: peg osx to a specific PY version

OSX was reverting to using Python 2.7.  Apparently, it needs all three numbers specified, so "3.6.8".
sudo: true is no longer needed on xenial.

Nice 👍


failed to unzip quilt_instruct.zip

Hello!
I failed while unzipping the quilt_instruct.zip on linux. When I use unzip quilt_instruct.zip, an error is reported as shown in Figure 1.When I use jar xvf quilt_instruct.zip, an error is reported as shown in Figure 2.
Looking forward to your reply, thanks!
Figure1:

Figure2:

Hmm, I will try to replicate this now on a new env and with the exact download you have and get back to you.

Just unzipped a fresh download of the zip file and it went without a hitch.
please try to use unzip -n quilt_instruct.zip on a complete download with ls -lh showing 26G.
If this issue persists, let me know I can find other ways to get you the dataset.
Apologies for the late reply as well.

Hello! Thank you for your reply!
I re-downloaded the complete quilt_instruct.zip file, this time I didn't encounter an error. But the folder size after I unzipped it is 16G, which doesn't match your 26G, which makes me confused.

This happens when zipping already well compressed file types like .png, so here the single .zip files serves as a bundler much like a folder would do but its also aids faster download speeds as its a single bundle. see


Error message when using sort but the sort ranking rule is not defined

Following this spec patch: https://github.com/meilisearch/specifications/pull/68/files
It should be implemented on Milli's side first, then released and integrated on MeiliSearch.
Expected behavior: Sending a sort parameter while the sort ranking rule is not specified in the ranking rules settings will lead to a 400 Bad Request - **invalid_sort** error.
{
    "message": "The sort ranking rule must be specified in the ranking rules settings to use the sort parameter at search time.",
    "errorCode": "invalid_sort",
    "errorType": "invalid_request_error",
    "errorLink": "https://docs.meilisearch.com/errors#invalid_sort"
}

Closed by #1686


Cannot access local machine IP

For some reason, if I try to ping my local machine's IP it cannot connect. I'm trying to setup a Ruby on Rails server, but it's unable to connect to my local windows postgres server. When I try to ping my local IP: <IP_ADDRESS> from the ubuntu machine (running on <IP_ADDRESS>) it won't ping back. However, I can ping google just fine from the wsl ubuntu terminal.)

You must set first the listen_addresses to * or your Ubuntu IP in postgresql.conf and set your pg_hba.conf so that it can accept incoming connection.
Example:

Why not?

What's hilarious is I ended up figuring it out. Windows firewall actually blocks Ubuntu from WSL. Once I allow connection from the Ubuntu IP it all works fine.

And this tools can work as well

https://github.com/shayne/wsl2-hacks


Requests don't need to be compared deeply

Request IDs are derived from request parameters, for example:
https://github.com/api3dao/airnode/blob/696ebad7207b02ffba9b85f2bb57430425c7cd32/packages/protocol/contracts/Airnode.sol#L51-L55
and these IDs are verified when the request is received. After this point, two requests with the same IDs have to be identical
Here, we only need to test for requestId:
https://github.com/api3dao/airnode/blob/fd1fdf209ea22aba8b2bf980d4980011e850c955/packages/node/src/core/requests/api-calls.ts#L7

We can skip this because we'll now be doing #82


build: support for asan/tsan/msan/ubsan and gcov

Modern versions of gcc and clang support various runtime sanitizers that
can be used to find nasty bugs at runtime. Including support for these
in the build is useful, but also it is useful to know how much code
coverage you're getting with tests when using these sanitizers.
This patch adds build-time support for the sanitizers as well as gcov
support to get code coverage metrics on varnish tests. To get HTML
output of this information, "lcov" is a useful tool. The general
workflow is:
    make
    lcov -o varnish_initial.info -i -c -d `pwd`
    make check
    lcov -o varnish_test.info -c -d `pwd`
    lcov -a varnish_initial.info -a varnish_test.info -o varnish_total.info

HTML output can then be generated using lcov's genhtml tool. This
information can then be evaluated to determine whether more tests are
needed to provide more test-time safety guarantees based on an initial
lack of warnings or errors from sanitizer tools.

FYI, there is a separate repo with gcov at https://github.com/varnish/varnish-gcov

Thanks; if that's intended to be the canonical place for coverage testing, I'll remove that part.
Also it seems this failing the Travis build, but it looks related to previous commits, not this one.

Not sure whether is canonical. I will let others (phk?) answer that.
Regarding travis, I'm afraid your diff is triggering some issue somewhere else.
I cannot build varnish after applying this PR in my box but from a quick check I cannot see anything obvious.

 Thanks for taking the time to look.

I messed up my repo and this was broken, so I'm gonna try again in a new PR. Build failed due to a missing \, which will be fixed in the new PR.


Progress bar

This is nice. Just make the changes I suggested, check them in locally, and push to this branch. Then I'll merge it. It seems to work!


Series K

Hi , i have a SAMSUNG UE65KS9000 , and i have some issues with home bridge , and maybe there is a thing i do not understand.
First, in home on iOS, samsungTv is show like a switch, so you can just on or off...
Second problem, if i tried to switch Off Tv with the switch, my homebridge stop running because a problem....
Can you help me, if you need i can give log for error.
Thanks your you're help ;)

Well, right now it's just a switch, you can only turn it on or off, so nothing wrong there, is working as expected...
It works for me (using the home app, siri or other third party apps), so maybe you can post the logs so we can see what's going on?

I retest Today and it's working ....I just only see the samsung ask me autorisation for home bridge, maybe it's that, but it's working !! Thank's a lot for you're plugin ;)

and it's working in wifi too ;)

sometime i have this error and my home bridge stop.
It's lookalike same error than first time events.js:160
stdout
14:04:46
throw er; // Unhandled 'error' event
stdout
14:04:46
^
stdout
14:04:46
stdout
14:04:46
Error: connect ECONNREFUSED <IP_ADDRESS>:8001
stdout
14:04:46
at Object.exports._errnoException (util.js:1036:11)
stdout
14:04:46
at exports._exceptionWithHostPort (util.js:1059:20)
stdout
14:04:46
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1080:14)
but maybe because it's in wifi ....
but after it's reworking... strange

and now seems to reworking normally... i'm still in wifi
so i want and tell you ...

i think if it' off, after too much time there is no communication ....
i will retest in ethernet

I will jump into this, sadly with a problem but no much to add on how to find a solution. I have a:
  "name": "[TV] Samsung 6 Series (50)",
  "version": "2.1.0",
  "device": {
    "type": "Samsung SmartTV",
    "modelName": "UN50KU6300",
    "ip": "<IP_ADDRESS>",
    "firmwareVersion": "Unknown",
    "name": "[TV] Samsung 6 Series (50)",
    "resolution": "3840x2160",
    "countryCode": "US",
    "msfVersion": "2.1.0",
    "smartHubAgreement": "true",
    "OS": "Tizen"

Once this plugin installed, I can see it in the Home app as an accessory, and also on the Homebridge. It stays the TV is on. When I try to turn it off, instantaneously the TV asks me for an allow permission. I allow. But the switch off, doesn't work.
At the same time, I can't change the location of the TV (to living room), or the name of the TV on the Home app.
Also using another app: Koogeek Home brings this error: https://imgur.com/gallery/v3xBg
If anyone has an idea on how to fix this, I am all ears and eyes.
ps. I research all other Samsung TV plugins, this work better with 2016 tvs. Thank you for your work.

You have to change the name of the accessory in your homebridge config. I had no issues moving between rooms in the Home app. I have no clue what that other app is doing.
The issue with turning off is being tracked in github issue #11 - it may be fixed in npm release 0.0.6


Allow the exclusion of specific dependencies or wildcards

I.e. Packager should be able to compile More without Core, allowing the developer to include in their site both core.js and more.js as individual files.
Related: https://github.com/Behavior-UI/behavior-ui/issues/40

I can follow up on this in a few days if not fixed yet.


Demonstration of CI Tool For fastpages

When receiving PRs from the community it can be cumbersome to validate PRs, as you have to pull down the new branch, build and serve the site locally and inspect it for changes.
This is why I have created an Actions workflow that is triggered by the magic word /preview in a PR Comment, which will build the code on the PR and serve you a live preview.

Okay here it goes!
/preview

@jph00 see the PR comments by the bot above.  let me know if this useful or any thoughts on the interface.
P.S. I took a break from working on the blog to setup some better CI tools to help develop and maintain the blog

Wow what an awesome idea! :) I love it.

LOL weren't supposed to merge it, was a demo 😆  No big deal just funny

Ah I always merge PRs unless the title says not to - haven't seen a PR that hides "don't merge" inside the content like that ;)
I'll know to be on the lookout in the future...


Update TodoistProject partial

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Does not work with WSL + Cling on Windows

I have WSL 2 installed; I built Cling from scratch in WSL on Windows and I can execute the cling binary in a WSL console without error; I have cling in the ~/.bashrc PATH so it can be executed in the WSL console via, simply, cling; it can also be executed via the absolute path.
However, it is not possible to get the C++ settings to work for the Execute Code plugin.

Enable WSL option (and I also tried with this option disabled trying both paths below)

Paste absolute path in Windows to cling (as in E:\path\to\cling)
*** or ***

Past absolute path in WSL to cling (as in /mnt/e/path/to/cling)

...and there is always an ENOENT error when attempting to run the code block.
Note: Python running in WSL (enabling the WSL setting and simply having 'python3' as the path to Python in the Execute Code settings for Python) succeeds, so WSL is being accessed.
It's just that C++ does not work, unfortunately. Alas! Took me two days to get Cling finally building in WSL hoping it would work with Execute Code - so just creating this issue so perhaps others will think twice before embarking on this route.
Thanks!

I have the same problem.


Adjust height for output video?

I need to adjust the height for the output video.. any idea how can that be achieved?
Thanks

Hey, did this ever get added at all?


[image_picker] remove unnecessary camera permmision

fixed https://github.com/flutter/flutter/issues/19806

@mklim done


V. 10.67 broken

The latest update seems to have broken something at the plugin. I'm attaching the console log in case it helps.
obsidian.md-1631169609500.log

@enjolrs weird... I've not seen that error before about unit locals...
I think that is an issue with dataview.
Do you use dates in dataview fields?

 I turned off dataview and the hierarchies from the hierarchy note still exist.
Sorry to keep bothering you, I'm not a programmer so I'm never sure which plugin is causing issues.

And it seems to have been fixed! Sorry again for the bother.

No worries, glad to hear it's working again!
It isn't always obvious where the error comes from


Live HTML Doesn't Get Minified

The output for "Automatic Live Optimizations" doesn't really seem to minifiy. At the moment it just breaks up the lines awkwardly with no real space saving.
Source:

    Repairs
    Services
    Pricing

Output:

Repairs
Services
Pricing

Expected:
RepairsServicesPricing

You're mistaken. That output IS minified. The minifier is just using a newline instead of a space.

I'm getting the same output now. How do you change it so it uses a space instead of a newline?

You can't.

Take it up with https://github.com/mrclay/minify if you don't like it. Nothing I can really do.

Then, might I ask, what is the point of using your plugin to "minify" the HTML if it cannot completely minify it down to one line?

Because it IS minified. Newline characters are 1 byte as are spaces, so the result is the same size.

Sorry, I deleted the comment after I saw your comment about there being nothing you could do because I didn't feel my comment was constructive after that point. But, thank you for still responding to it. You're right, a space/newline are both 1 byte, so it does accomplish that same thing. The OCD in me just would rather see things all on one line. Thanks for the good information. Hopefully, this helps ease anyone else's concerns who might stumble upon this.

Sure. I do prefer it on one line too, but it's the same size either way so I live with it. Better than trying to write my own algorithm. :)


aws1: Add version 1.18.144

See https://github.com/ScoopInstaller/Main/pull/1395
Updated aws in main bucket to 2.x and migrated 1.x to aws1 versions bucket

/verify

Shouldn't be updated to 1.18.139 ? This is the current latest tag of aws-cli 1.x, see https://github.com/aws/aws-cli/releases/tag/1.18.139
I don't why the aws is stuck to v1.18.44 in main repo, it seem the autoupdate system doesn't work anymore on aws. I put a notice here https://github.com/ScoopInstaller/Main/pull/835#issuecomment-642926655 but no one take care of it...

it probably should be 1.18.139. i have just migrated it as-is from the main bucket as I saw that the last update was rolled back for some reason.

It seems it was a problem of decompression on a specific release (https://github.com/ScoopInstaller/Main/issues/1021) you could test with the latest version, if the problem is gone ?

It seems it was a problem of decompression on a specific release (ScoopInstaller/Main#1021) you could test with the latest version, if the problem is gone ?

Updated to (1.18.144)[https://github.com/aws/aws-cli/blob/master/CHANGELOG.rst]

Any value getting this merged? I don't think so.


stable/mongodb  Unable to mount volumes for pod: timeout expired waiting for volumes to attach/mount for pod.

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Version of Helm and Kubernetes:
Helm:
Client: &version.Version{SemVer:"v2.10.0".....
Server: &version.Version{SemVer:"v2.10.0", ....

Kubernetes:
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.1", ....
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3",...

Which chart:
mongodb
What happened:
Trying to install mongodb with a persisted volume, fails to mount the volume.  I'm getting:
 Unable to mount volumes for pod "mongodb-staging-7b7f7b4bbb-99m8t_staging(6c0e872f-b000-11e8-95f4-066ec59557cc)": timeout expired waiting for volumes to attach/mount for pod "staging"/"mongodb-staging-7b7f7b4bbb-99m8t". list of unattached/unmounted volumes=[data]

What you expected to happen:
I can see one volume being mounted, based on the PVC from the storage class I have specified.  But inspecting the pod shows it's trying to attached to another 'data' volume, which I don't have controller over?
How to reproduce it (as minimally and precisely as possible):
Here is are my mongodb values that I've replaced from the defaults:
image:
  registry: docker.io
  repository: bitnami/mongodb
  tag: 3.6.7
  pullPolicy: Always
usePassword: false
mongodbEnableIPv6: false

mongodbExtraFlags: ["--wiredTigerCacheSizeGB=6"]

service:
  annotations: {}
  type: ClusterIP
  port: 27017

nodeSelector:
  type: mongodb-staging

persistence:
  enabled: true
  storageClass: "mongodb-ebs-staging"
  accessModes:
    - ReadWriteOnce
  size: 30Gi
  annotations: {}

storage class:
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: mongodb-ebs-staging
provisioner: kubernetes.io/aws-ebs
reclaimPolicy: Retain
parameters:
  type: io1
  zones: ap-southeast-2c
  encrypted: "true"
  kmsKeyId: yadayadayada

running helm install successfully loads the PV, the PVC, and tries to load the pod in to my node.  My node exists.
Output from kubectl describe pod....
Name:           mongodb-staging-7b7f7b4bbb-99m8t
Namespace:      staging
Node:           ip-172-32-1-214.ap-southeast-2.compute.internal/<IP_ADDRESS>
Start Time:     Tue, 04 Sep 2018 17:07:29 +1200
Labels:         app=mongodb
                chart=mongodb-4.2.2
                pod-template-hash=3639360666
                release=mongodb-staging
Annotations:    <none>
Status:         Pending
IP:
Controlled By:  ReplicaSet/mongodb-staging-7b7f7b4bbb
Containers:
  mongodb-staging:
    Container ID:
    Image:          docker.io/bitnami/mongodb:3.6.7
    Image ID:
    Port:           27017/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Liveness:       exec [mongo --eval db.adminCommand('ping')] delay=30s timeout=5s period=10s #success=1 #failure=6
    Readiness:      exec [mongo --eval db.adminCommand('ping')] delay=5s timeout=5s period=10s #success=1 #failure=6
    Environment:
      MONGODB_USERNAME:
      MONGODB_DATABASE:
      MONGODB_EXTRA_FLAGS:  --wiredTigerCacheSizeGB=6
    Mounts:
      /bitnami/mongodb from data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-ct27h (ro)
Conditions:
  Type           Status
  Initialized    True
  Ready          False
  PodScheduled   True
Volumes:
  data:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  mongodb-staging
    ReadOnly:   false
  default-token-ct27h:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-ct27h
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  type=mongodb-staging
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason                 Age               From                                                      Message
  ----     ------                 ----              ----                                                      -------
  Normal   Scheduled              11m               default-scheduler                                         Successfully assigned mongodb-staging-7b7f7b4bbb-99m8t to ip-172-32-1-214.ap-southeast-2.compute.internal
  Normal   SuccessfulMountVolume  11m               kubelet, ip-172-32-1-214.ap-southeast-2.compute.internal  MountVolume.SetUp succeeded for volume "default-token-ct27h"
  Warning  FailedMount            32s (x5 over 9m)  kubelet, ip-172-32-1-214.ap-southeast-2.compute.internal  Unable to mount volumes for pod "mongodb-staging-7b7f7b4bbb-99m8t_staging(6c0e872f-b000-11e8-95f4-066ec59557cc)": timeout expired waiting for volumes to attach/mount for pod "staging"/"mongodb-staging-7b7f7b4bbb-99m8t". list of unattached/unmounted volumes=[data]

pvc status:
Name:          mongodb-staging
Namespace:     staging
StorageClass:  mongodb-ebs-staging
Status:        Bound
Volume:        pvc-4b1f2890-b000-11e8-95f4-066ec59557cc
Labels:        app=mongodb
               chart=mongodb-4.2.2
               heritage=Tiller
               release=mongodb-staging
Annotations:   pv.kubernetes.io/bind-completed=yes
               pv.kubernetes.io/bound-by-controller=yes
               volume.beta.kubernetes.io/storage-provisioner=kubernetes.io/aws-ebs
Finalizers:    []
Capacity:      30Gi
Access Modes:  RWO
Events:
  Type    Reason                 Age   From                         Message
  ----    ------                 ----  ----                         -------
  Normal  ProvisioningSucceeded  20m   persistentvolume-controller  Successfully provisioned volume pvc-4b1f2890-b000-11e8-95f4-066ec59557cc using kubernetes.io/aws-ebs

Thanks

I discovered that attaching an EBS to an M5 is not supported by Kops 1.9.
I changed to an M4 and everything worked.  I will investigate upgrading Kops too.
For reference:

https://github.com/kubernetes/kops/blob/master/docs/releases/1.8-NOTES.md#significant-changes
https://github.com/kubernetes-incubator/kube-aws/issues/1053
https://github.com/kubernetes/kubernetes/issues/49926#issuecomment-367306608


Model streaming API enhancement

Stream request load-balance for multi-workers for predictor.
More parameters for model.generate api
Stream support  for class DefaultTransformersPipeline
RouterDeployment api support format "/{model}/run/predict"
Model id mapping for api server, like mapping facebook/opt-125m to facebook--opt-125m

#82

Done


Repo: https://github.com/slsa-framework/example-package/tree/v22.0.10
Run: https://github.com/slsa-framework/example-package/actions/runs/2547260921
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.tag.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.tag.branch1.default.slsa3.yml
Trigger: push
Branch: v22.0.10
Date: Thu Jun 23 06:53:45 UTC 2022
Tests are passing now. Closing this issue.


[FEAT+REFACTOR]: authorization via email, code optimization, tests, kafka

Is it breaking change?
Yes, it breaks previous features such as auth via google & notes because they were removed.
Have you synchronized changes with other repositories?
Not yet
Specify linked issues or discussions
close #40
close #39
close #34
close #26

blocked by #45


Fix typo in Get Started documentation (updating Ackee on Heroku)

When updating Ackee on Heroku, after pulling the latest changes, when I try to push it back up to Heroku:
git push origin heroku master

I get the following errors:
error: src refspec heroku does not match any
error: failed to push some refs to 'https://github.com/electerious/Ackee.git'

I think this is a typo, and instead I should only push back to the heroku remote; not attempt to push to the origin remote. So it should look like this:
git push heroku master

Pull Request Test Coverage Report for Build 432

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 57.837%

Totals

Change from base Build 422:
0.0%

Covered Lines:
482

Relevant Lines:
721

💛  - Coveralls

Pull Request Test Coverage Report for Build 432

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 57.837%

Totals

Change from base Build 422:
0.0%

Covered Lines:
482

Relevant Lines:
721

💛  - Coveralls

Thanks! :)

Why do I still see git push origin heroku master in the docs ?


error: fork/exec /bin/sh: argument list too long

What happened?
Running pulumi up -s dev -y fails when run consecutively.  Although, if I change the resource_name, the build runs successfully.
Similar thread I found: #285
Example
build_image = command.local.Command(
    "build-service-image",
    create=(
    "buildah --signature-policy=policy.json build "
    f" --build-arg=FRAPPE_VERSION='{frappe_commit_sha}'"
    f" --build-arg=PYTHON_VERSION='{python_version}'"
    f" --build-arg=NODE_VERSION='{node_version}'"
    f" --tag='{image_name}'"
    " --jobs=4"
    " --file=Containerfile"
    )
)

publish_image = command.local.Command(
    "publish-service-image",
    create=(
        f"buildah login ghcr.io -u {os.environ['GITHUB_USER']} --password-stdin && "
        f"buildah --signature-policy=policy.json push {image_name}"
    ),
    opts=pulumi.ResourceOptions(depends_on=[build_image]),
    stdin=os.environ["GITHUB_PAT"],
)

Output of pulumi about
CLI
Version      3.137.0
Go Version   go1.23.2
Go Compiler  gc

Plugins
KIND      NAME     VERSION
resource  aws      6.58.0
resource  command  1.0.1
language  python   unknown

Host
OS       nixos
Version  24.05 (Uakari)
Arch     x86_64

This project is written in python: executable='/***/venv/bin/python' version='3.12.7'

Backend
Name           pulumi.com
URL            https://app.pulumi.com/***
User           ***
Organizations  ***
Token type     personal

Dependencies:
NAME            VERSION
pip             24.3.1
pre_commit      4.0.1
pulumi_aws      6.58.0
pulumi_command  1.0.1

Pulumi locates its logs in /tmp by default
warning: Failed to get information about the current stack: No current stack

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

btw, I'm not approaching this further, just thought I should report it nevertheless. I moved on to just continue using pulumi_docker_build library instead.

Thanks for reporting this @gavindsouza  you can work around this error in by setting addPreviousOutputInEnv = false, but I think at minimum we should keep this issue open to track improving the error message to suggest the workaround. (And even better if we can find a way to avoid the error altogether, though that might be challenging.)


SSR warning useLayoutEfect

There's a warning when you're working with Server Side Render due to useLayoutEffect.
Warning: useLayoutEffect does nothing on the server, because its effect cannot be encoded into the server renderer's output format. This will lead to a mismatch between the initial, non-hydrated UI and the intended UI. To avoid this, useLayoutEffect should only be used in components that render exclusively on the client.

Cool, but now the isBrowser checks are kind of redundant. So we can remove them.


torchdata.datapipes.map.Shuffler should return a MapDataPipe

🐛 Describe the bug
I am working on mixing two speech datasets, both of them are indexable datasets. Using MapDataPipe, shuffle one of the speech datasets, and zip them together with one zipper:
import torchdata.datapipes as dp

dp1 = dp.map.SequenceWrapper([0, 1, 2, 3, 4, 5]) # speech 1
dp2 = dp.map.SequenceWrapper(['a', 'b', 'c']) # speech 2
dp1 = dp.map.Shuffler(dp1) # shuffle one
dpz = dp.map.Zipper(dp1, dp2)

print(list(dpz))
print(list(dpz))
print(list(dpz))
print()

However, the shuffler returns one IterDataPipe... So the code above raises an Error:
Traceback (most recent call last):
  File "/mnt/home/quancs/projects/NBSS_pmt/testxxx.py", line 6, in <module>
    dpz = dp.map.Zipper(dp1, dp2)
  File "/mnt/home/quancs/miniconda3/envs/torch2/lib/python3.10/site-packages/torch/utils/data/datapipes/map/combining.py", line 80, in __init__
    raise TypeError("Expected all inputs to be `MapDataPipe`")
TypeError: Expected all inputs to be `MapDataPipe`

I tried to use IterDataPipe, but I don't know how to sample it in ddp situation (in one epoch, each sample is sampled only once).
Versions
Collecting environment information...
PyTorch version: 2.0.0
Is debug build: False
CUDA used to build PyTorch: 11.8
ROCM used to build PyTorch: N/A
OS: CentOS Linux 7 (Core) (x86_64)
GCC version: (GCC) 8.3.1 20190311 (Red Hat 8.3.1-3)
Clang version: Could not collect
CMake version: version <IP_ADDRESS>
Libc version: glibc-2.17
Python version: 3.10.0 (default, Mar  3 2022, 09:58:08) [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-3.10.0-1160.el7.x86_64-x86_64-with-glibc2.17
Is CUDA available: True
CUDA runtime version: 11.3.109
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA A100-SXM4-40GB
GPU 1: NVIDIA A100-SXM4-40GB
GPU 2: NVIDIA A100-SXM4-40GB
GPU 3: NVIDIA A100-SXM4-40GB
GPU 4: NVIDIA A100-SXM4-40GB
GPU 5: NVIDIA A100-SXM4-40GB
GPU 6: NVIDIA A100-SXM4-40GB
GPU 7: NVIDIA A100-SXM4-40GB
Nvidia driver version: 530.30.02
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                128
On-line CPU(s) list:   0-127
Thread(s) per core:    1
Core(s) per socket:    64
Socket(s):             2
NUMA node(s):          8
Vendor ID:             AuthenticAMD
CPU family:            23
Model:                 49
Model name:            AMD EPYC 7742 64-Core Processor
Stepping:              0
CPU MHz:               1500.000
CPU max MHz:           2250.0000
CPU min MHz:           1500.0000
BogoMIPS:              4491.63
Virtualization:        AMD-V
L1d cache:             32K
L1i cache:             32K
L2 cache:              512K
L3 cache:              16384K
NUMA node0 CPU(s):     0-15
NUMA node1 CPU(s):     16-31
NUMA node2 CPU(s):     32-47
NUMA node3 CPU(s):     48-63
NUMA node4 CPU(s):     64-79
NUMA node5 CPU(s):     80-95
NUMA node6 CPU(s):     96-111
NUMA node7 CPU(s):     112-127
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 cpb cat_l3 cdp_l3 hw_pstate sme retpoline_amd ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif umip overflow_recov succor smca
Versions of relevant libraries:
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.23.5
[pip3] pytorch-lightning==2.0.1.post0
[pip3] torch==2.0.0
[pip3] torchaudio==2.0.0
[pip3] torchdata==0.6.0
[pip3] torcheval==0.0.6
[pip3] torchmetrics==0.11.4
[pip3] torchtnt==0.0.7
[pip3] torchvision==0.15.0
[pip3] triton==2.0.0
[conda] blas                      1.0                         mkl
[conda] ffmpeg                    4.3                  hf484d3e_0    pytorch
[conda] mkl                       2021.4.0           h06a4308_640
[conda] mkl-service               2.4.0           py310h7f8727e_0
[conda] mkl_fft                   1.3.1           py310hd6ae3a3_0
[conda] mkl_random                1.2.2           py310h00e6091_0
[conda] numpy                     1.23.5          py310hd5efca6_0
[conda] numpy-base                1.23.5          py310h8e6c178_0
[conda] pytorch                   2.0.0           py3.10_cuda11.8_cudnn8.7.0_0    pytorch
[conda] pytorch-cuda              11.8                 h7e8668a_3    pytorch
[conda] pytorch-lightning         2.0.1.post0              pypi_0    pypi
[conda] pytorch-mutex             1.0                        cuda    pytorch
[conda] torchaudio                2.0.0               py310_cu118    pytorch
[conda] torchdata                 0.6.0                    pypi_0    pypi
[conda] torcheval                 0.0.6                    pypi_0    pypi
[conda] torchmetrics              0.11.4                   pypi_0    pypi
[conda] torchtnt                  0.0.7                    pypi_0    pypi
[conda] torchtriton               2.0.0                     py310    pytorch
[conda] torchvision               0.15.0              py310_cu118    pytorch

Hi,
We intentionally made this change in release 0.5.0 (release note) and more discussion can be found here: https://github.com/pytorch/pytorch/pull/83202
We are happy to discuss any other use case further to see if we can improve our API.

@NivekT I just think it's wired to return a IterDataPipe after shuflling a MapDataPipe. I think it's a better choice to make Shuffler return a MapDataPipe which returns a tuple (original index, data corresponding to the original index) given a shuflled index.

For my situation, the current API is OK if I can use IterDataPipe to easily achieve that in one epoch, each sample is sampled only once with ddp used. I know it's easy to achieve that for a MapDataPipe by using DistributedSampler.

I tried to use IterDataPipe, but I don't know how to sample it in ddp situation (in one epoch, each sample is sampled only once).

@quancs There is no Sampler concept anymore in TorchData and that's one of the reasons that we convert MapDataPipe.shuffle to IterDataPipe. And, it's not intuitive for me that MapDataPipe has an order because it's intentionally for the random-access pattern rather than sequential access pattern

@ejguan Could you tell me how to sample each sample only once in one epoch with ddp used if I use IterDataPipe in my case?


feat: unordered channel

Description:
Commit Message
feat: unordered channel

see the guidelines for commit messages.
Changelog Entry
version: <log entry>

Checklist:

[x] I have performed a self-review of my own code
[ ] I have documented my code in accordance with the documentation guidelines
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have run the unit tests
[ ] I only have one commit (if not, squash them into one commit).
[ ] I have a descriptive commit message that adheres to the commit message guidelines

Please review the CONTRIBUTING.md file for detailed contributing guidelines.

Codecov Report

Merging #437 (1e91645) into main (4df1f9c) will increase coverage by 0.07%.
The diff coverage is 95.45%.

@@             Coverage Diff              @@
##               main     #437      +/-   ##
============================================
+ Coverage     66.93%   67.01%   +0.07%
  Complexity      551      551
============================================
  Files           191      191
  Lines         17298    17324      +26
  Branches        352      352
============================================
+ Hits          11578    11609      +31
+ Misses         5541     5536       -5
  Partials        179      179

Flag
Coverage Δ

rust
64.86% <95.45%> (+0.09%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...bc-core/src/ics04_channel/packet/receive_packet.rs
81.25% <ø> (-0.45%)
:arrow_down:

...s/cosmwasm-vm/cw-icon-light-client/src/contract.rs
47.34% <0.00%> (+0.08%)
:arrow_up:

...smwasm-vm/cw-ibc-core/src/ics04_channel/handler.rs
89.50% <91.66%> (+0.07%)
:arrow_up:

contracts/cosmwasm-vm/cw-common/src/commitment.rs
77.51% <100.00%> (+0.77%)
:arrow_up:

...smwasm-vm/cw-ibc-core/src/ics04_channel/channel.rs
86.54% <100.00%> (-1.29%)
:arrow_down:

...osmwasm-vm/cw-ibc-core/src/ics04_channel/events.rs
99.53% <100.00%> (+0.05%)
:arrow_up:

...bc-core/src/ics04_channel/handler/close_confirm.rs
89.47% <100.00%> (+4.17%)
:arrow_up:

.../cw-ibc-core/src/ics04_channel/handler/open_try.rs
89.47% <100.00%> (ø)

...vm/cw-ibc-core/src/ics04_channel/packet/timeout.rs
61.81% <100.00%> (-0.14%)
:arrow_down:

.../rust/common/src/ibc/core/ics04_channel/channel.rs
51.76% <100.00%> (+1.40%)
:arrow_up:

... and 1 file with indirect coverage changes


Make available the name of the archive when running custom command

People need to know the name of the archive that has to be created.

Passing it as an argument can cause problems to people that do not needed.
Using environemnt variable can be used as well.

Related https://github.com/packit-service/packit/issues/481

It seems to me that the creation of tarball breaks at random times.
See this PR for example: https://github.com/osbuild/osbuild/pull/82
There was no problem, but suddenly in the following PR after the first force-push it started failing:
https://github.com/osbuild/osbuild/pull/83
We use only {version}.tar.gz instead of {name}-{version}.tar.gz.

@msehnout it's true that we had a bug in prod that it did not check out the PR when creating the archive - I assume you were hitting this bug. We deployed a fix for that today and planning doing another update tomorrow. I'll try to watch prod logs to see if the error you were seeing appears again.

Merged in master and it will be included in 0.6.0 release


Change DatePicker icon based on TimeOnly parameter.

Issue: The DatePicker's button icon is calendar_today even if the DatePicker's TimeOnly parameter is set to true.
Proposed Solution: Substitute the calendar_today icon with the schedule icon when the DatePicker's TimeOnly parameter is set to true.
This PR updates the DatePicker's CSS, code and template to support the icon logic. I've also included two new unit tests in this PR to test which icon is displayed.

I noticed the build failed on the PR. It failed on data-grid-related code. I haven't touched that code in this PR, so I think it may be unrelated.


Add simple pagination,remove --profile parameter, use AWS_PROFILE env…

… instead.

Hey @mgla thanks for the contribution but after testing this change it fails to find any Glacier objects in the bucket:
./s3-remove-glacier-objects.sh
Enter S3 Bucket name: example-bucket
Warning: this will delete all objects from the S3 bucket with storage type Glacier!  Proceed? (y/n) y
Failure: No (more) Glacier objects found in this S3 bucket.


Parameterized (De)Activate Workflow Steps

Adding new feature for parameterized workflow activation steps; Giving the ability to select replication agents instead of triggering a mass activation processes.
We've seen the use case where clients have a preview environment which needs content replication without triggering a default agent. These allow the workflows to have a subset of replication agents be triggered, and subsequent approval step executed, before triggering another subset of agents (this time for the production publish systems).
It's possible to get the arguments correct, on a normal WF process step. But to make life easier for WF editors, i included three custom WF Components.

Activate
Flush
Deactivate

The Activate/Deactivate only show those replication agents which are not cache invalidators. Of course the flush will only list agents which are invalidators.
I used an inheritance model to manage not doing a CPD on the dialog, JSON generation; but that means that the dialog titles and other attributes aren't unique to the different types. Let me know if you think it's better to be explicit.
The thread local variables are use because I am pretty sure that the processes can be used by multiple threads; and I needed to keep state (which agents were selected).
Here's some screen shots:

If it's accepted, i'll write up the documentation and do a PR on that repo.

In general, I think this looks good. My only real requests are to:

Minimize/eliminiate the non-relevant formatting changes in the pom files.
Ensure that that the new dependency versions are correct for 5.6.1

Reverted changes to poms as requested. I think I now have the correct versions of libraries based on 5.6.1.


luci-mod-network: Can't setup static route with "unspecified" interface.

Steps to reproduce:
Example: Replace the following lines and remove this

go to: Network → routing
add new
try to set interface "unspecified"

Actual behavior:
There is now option to set  "unspecified" interface.
The interface we would like to use does not appear on the list, eg. zerotier.
Additional Information:
OpenWrt version [OpenWrt 23.05-SNAPSHOT (r24016-f791ec1f6d)]
If we set the route manually from the console, the display in Luci is correct. The interface is undefined, but the route works properly.

The interface value is mandatory for uci declared routes. If your interface (zerotier) is not managed by uci, you cannot use uci route declarations for it.

No, you are wrong. Uci accepts a route without an interface, and that's how I set it.
For example:
#uci add network route
#uci set<EMAIL_ADDRESS>#uci set<EMAIL_ADDRESS>#uci set<EMAIL_ADDRESS>#uci commit network
give us:

Ok.


Unable to run tests: RLMObject subclasses with the same name cannot be included twice in the same target

Goals
I want to be able to run unit tests in a project with a RealmSwift dependency
Expected Results
Being able to run unit tests
Actual Results
Depending on target memberships of model files, either the app crashes or Xcode is unable to build the test target
Steps to Reproduce
I've attached a sample app to demonstrate the issue
Code Sample
See attached sample app
Version of Realm and Tooling
See attached sample app
Xcode version: 8.3.3
iOS/OSX version: iOS 10 - osx: 10.12.6
Dependency manager + version: ?
Cocoapods
RealmTest.zip

Thanks for getting in touch with us, and for providing a sample project.
To get things to work, I went to the project in the Project Navigator, clicked the RealmTestTests target, went to Build Phases, went to Compile Sources, and removed all the files from the list that were not part of the test target. See the screenshot:

More generally, since you are linking the application against your test target as if it were a framework (e.g. @testable import RealmTest), you don't need to ask the test target to compile the application source files. I suspect that you didn't run into any non-Realm related projects because your test application doesn't expose anything as public or open, but Realm (even Realm Swift) works at the Objective-C level and does not benefit from the same visibility restrictions.

👍 Thank you for your help Austin.


subsys: power: initialize states as disabled

This commit makes behavior enabled previously via SYS_PM_STATE_LOCK
Kconfig option the default and removes the option. Upon boot all power
states are disabled and need to be explicitely enabled by the
application or the power management subsystem by calling
sys_pm_ctrl_enable_state function.
This PR is currently not tested and requires further work, e.g. the documentation needs to be updated.
The proposed solution should fix #11908, #20775 and partially #20792.

@mnkp any plans to continue work on this PR? At least one of the issue it's marked as (potentially) fixing is of medium priority, hence it's of interest for Zephyr 2.2.

@wentongwu could you have a look at the PR.

@mnkp can you please rebase and add a bit of documentation regarding the change in behavior?
@wentongwu since @pabigot is currently neutral on this one, can you voice your opinion on whether this should go in?

But it need current working platforms to do some extra initialization.

In short this just switches the default behavior

That's exactly the problem, the default behavior was incorrect. We can't keep it. It definitely would be better to introduce the change along all the other rework that power management subsystem needs to undergo. Still, the change is a bug fix and without it the power management subsystem is broken. The system can enter sleep mode even if user didn't intended it. It's a rather serious deficiency.
This part will not change in the future. We can't start with power states enabled before the power management system is all set up.

I agree remove SYS_PM_STATE_LOCK Kconfig option and enable the code under it by default. But IMHO to avoid unexpectedly power off system because of long timeout or sleep forever, we can separate system off state from deep sleep states as a individual and specific state so that it can be determined by user instead of residency policy, and this won't break the current working platform.

@wentongwu Please either approve or reject this PR on the basis of what's in it, not on what could be in it.   We will be discussing this in dev-review tomorrow, and if the consensus is that the existing behavior is a bug that should be fixed using this approach I will remove my NAK and it will probably get merged as-is (after a rebase).

I'd like to clarify my position on this PR in anticipation of dev-review discussion.
There is absolutely no question that a power management system that by default allows entry to deep sleep as currently defined based solely on the duration of expected sleep ("residency") is wrong.  This is not a behavior most developers would expect, and that should have been addressed during review.
However: This behavior was added in fall of 2018.  Existing code depends on this behavior, and existing code uses the API as implemented to avoid this behavior.
There has been churn in this API in the past: #22084 reversed a previous change in #20950 that removed deep-sleep states from the residency policy to solve this exact problem.  The reversal was required because existing code depends on a residency-based support for deep sleep, and because enabling deep-sleep states at all is opt-in.
The problematic state from #11908 may be called "system off" in Nordic terms but it is a true deep sleep state as currently defined by Zephyr: it loses execution context that must be recovered somehow.  It is simply a deep-sleep state that must not be entered using the residency policy because it cannot be exited based on the passage of time.  On other systems deep sleep states can safely be entered and exited based on residency.  This suggests the flaw is not in the states, but the set of states that are affected by the residency policy.
This PR proposes one way to change that: making the individual states opt-in.
My reject was influenced by the lack of non-comment reviews from people involved in the previous decisions including but not limited to @wentongwu @nashif @andrewboie @erwango @mnkp @vanti.  I'll replace my reject with approval if it seems we won't be re-re-reversing the default behavior in another six months.

Adding my two-cents. I tend to think of default behavior such as this as something that should only be changed as last resort - it can be error-prone for people who have been relying on the existing behavior. In this particular case, there seems to be a similar concern as I had regarding the deep sleep (shutdown) state on the TI CC13x2. The way I approached it was by defining our own residency policy (there were other reasons why I did so, but preventing the residency policy from entering our DEEP_SLEEP_1 state was one of them). If you look at subsys/power/policy/policy_residency_cc13x2_cc26x2.c , you would see I left out entries for deep sleep states in the pm_min_residency array and made sure sys_pm_policy_next_state() does not return the SYS_POWER_STATE_DEEP_SLEEP_1 state. Maybe this is an approach you can consider as an alternative to changing the defaults.
FWIW, I do like the idea of eliminating the SYS_PM_STATE_LOCK option. It seems to me this is functionality that is needed in most cases.

I would like to clarify rationale for this PR in a bit more detail. There was a lot of talk regarding handling of deep sleep states since this is the issue reported by #11908. However, the problem is not limited to deep sleep states. Entering prematurely a sleep state can be just as deadly.
Looking at the Zephyr tree the SoC series/families that support System Power Management are: mec1501, nordic_nrf, silabs_exx32 and TI cc13x2_cc26x2. The Nordic supports deep sleep only. However, all the remaining SoC series/families have sleep states that turn off high frequency clocks. When System Power Manager schedules entry into a sleep state that turns off high frequency clock it ultimately shuts off most of the peripherals and (unless it was planned) renders the system unusable. Additionally, if we don't configure (or happen to configure) a wake up event the SoC will never leave the low power state it entered.
Automatic entry into a low power stated requires careful planning and coordination between System Power Management and Device Power Management subsystem (or an application if it's an application that wants to manage the system). Both need to be enabled and supported on a given SoC for automatic entry into low power state to make any sense.
At present only TI cc13x2_cc26x2 has support that looks complete enough that we may want to enable automatic entry into low power state during system initialization. @vanti would need to speak to that.
This PR doesn't aim to solve all the issues with the power management subsystem. And there are quite a few that are significant. We defined "Sleep State" as a state that doesn't lose execution context and "Deep Sleep State" as a state that does. However there are SoCs where CPU  may not lose execution context but peripherals are power gated and do lose configuration. We don't really know how to handle this scenario. So we had #22084, #20950 the churn that @pabigot was complaining about and are coming up with new terms like "system off" state that are not clearly defined. Also, the documentation talks about distributed and central method for device power management. While in fact we don't give user a clear choice to have the application or Zephyr manage the power. There are still a lot of issues that need to be resolved.
In any case, regardless if it's an application or Zephyr controlling power management the power states can only be enabled once the system and wake up events are properly configured. They simply cannot be enabled by default (or otherwise the policies cannot be enabled by default).
That said, I agree that it would make more sense to update Power Management Subsystem in one go and if there is no pressure on reducing the bug count we may well handle this issue later.

Dev-review (May 28): Decided to defer for post 2.3

At present only TI cc13x2_cc26x2 has support that looks complete enough that we may want to enable automatic entry into low power state during system initialization. @vanti would need to speak to that.

@mnkp From the cc13x2_cc26x2 standpoint I am not aware of any issue regarding automatic entry of power states in idle, which is why I am curious to learn more about the use-cases you have in mind. Is there a test/scenario you can share that would cause a premature entry to sleep? My understanding is that, short of the application forcing a (system) power state, the power state can only changed while the CPU is idle, which I'd expect to happen after initialization has completed and main() is entered. It should be fair for the policy function to run after that point in time and determine which state to transition to. And if for some reason we can end up in idle prior to main() before the devices are initialized, then it seems to me there may be a problem with the system's design.

Looking at the Zephyr tree the SoC series/families that support System Power Management are: mec1501, nordic_nrf, silabs_exx32 and TI cc13x2_cc26x2. The Nordic supports deep sleep only. However, all the remaining SoC series/families have sleep states that turn off high frequency clocks. When System Power Manager schedules entry into a sleep state that turns off high frequency clock it ultimately shuts off most of the peripherals and (unless it was planned) renders the system unusable.

To take an example, standby mode (SLEEP_2) on cc13x2_cc26x does indeed turn off most of the peripherals. Consequently it should only be entered when the peripherals are not needed. The way I conveyed this to power policy is by calling sys_pm_ctrl_enable/disable_state in the driver, to prevent SLEEP_2 from being entered while the peripheral is needed for an ongoing transfer for instance. So when a power state is enabled, it means it is ok for the policy to choose that state, and to "render the system unusable" since the CPU and the peripherals are not currently needed. Upon waking up the system would be restored to a state that is "usable" again.

Additionally, if we don't configure (or happen to configure) a wake up event the SoC will never leave the low power state it entered.

Not sure why you wouldn't configure a wakeup source. Typically something like a timer or a gpio should be set up to wake up the system.

Automatic entry into a low power stated requires careful planning and coordination between System Power Management and Device Power Management subsystem (or an application if it's an application that wants to manage the system). Both need to be enabled and supported on a given SoC for automatic entry into low power state to make any sense.

I agree with this. While separating system pm and device pm into two separate knobs seem intuitively appealing, in practice I found it is hard to live with one without the other. On cc13x2_cc26x2, I had to do some extra work to determine whether the user has only enabled system pm, and if so, I had to make sure to lean on the TI HAL to let me add a hook function that would reinitialize the peripheral when coming out of SLEEP_2, given device_set_power_state() would not be called. Doing system power management without regards to the devices isn't really realistic imho.

However there are SoCs where CPU may not lose execution context but peripherals are power gated and do lose configuration. We don't really know how to handle this scenario.

This is exactly the case we have for SLEEP_2 on cc13x2_cc26x2. We reinitialize the peripherals on exit of the sleep state.

Also, the documentation talks about distributed and central method for device power management. While in fact we don't give user a clear choice to have the application or Zephyr manage the power. There are still a lot of issues that need to be resolved.

I agree this needs to be clarified. I was in same the boat when I first read the doc, and thought to myself: what is this distributed method it is talking about?  From what I understand central method is the only one that is supported today, and distributed method means "you are on your own" and "cook up your own power management in the application".

From the cc13x2_cc26x2 standpoint I am not aware of any issue regarding automatic entry of power states in idle, which is why I am curious to learn more about the use-cases you have in mind. Is there a test/scenario you can share that would cause a premature entry to sleep? My understanding is that, short of the application forcing a (system) power state, the power state can only changed while the CPU is idle, which I'd expect to happen after initialization has completed and main() is entered. It should be fair for the policy function to run after that point in time and determine which state to transition to. And if for some reason we can end up in idle prior to main() before the devices are initialized, then it seems to me there may be a problem with the system's design.

So indeed we can end up in idle prior to main(). The system power management _sys_suspend() function will be run the moment the kernel is initialized. Any code run in POST_KERNEL and later stage, including majority of the driver initialization code, can trigger entry into low power state. On TI cc13x2/cc26x2 this shouldn't be a major issue since you've implemented device power management code and wake up from idle. However, as I mentioned the TI cc13x2/cc26x2 is the only platform where power management implementation seems complete. On all other platforms any call to idle that is longer than the values defined by CONFIG_SYS_PM_MIN_RESIDENCY_SLEEP_x will put the SoC to sleep. We don't run into many issues with Zephyr's sample apps since the defaults for CONFIG_SYS_PM_MIN_RESIDENCY_SLEEP_x are unrealistically large 5, 10 and 30 s. Typically, depending on which parts of the clock tree are being turned off, entry and exit from a low power state takes between dozens of microseconds to a few milliseconds. So, in a real life application the values of CONFIG_SYS_PM_MIN_RESIDENCY_SLEEP_x will be in range of ms. It's likely to have small delays in the range of milliseconds in the driver code which would be enough to trigger entry into low power state.
Even on TI cc13x2/cc26x2 platform with its pretty complete power management support things will break quickly if the device power management code is not enabled. Enabling System Power Management but not Device Power Management is one way how user can configure Zephyr to let the application control entry into power states.
Things will also break if CONFIG_SYS_POWER_DEEP_SLEEP_STATES is enabled and user's application runs some initialization code at POST_KERNEL stage, prior to driver initialization, that calls k_sleep with value large enough to trigger entry into low power mode. That's not an unusual scenario. In a low power design it is quite common to power gate external components on the PCB, e.g. external flash, sensors that may be connected via I2C bus, etc. Application that wants to initialize those components during system boot would need to enable first respective power supplies. This would happen after the kernel is initialized but before the driver initialization. A call to  k_sleep would be there to wait until power supplies stabilize.

Additionally, if we don't configure (or happen to configure) a wake up event the SoC will never leave the low power state it entered.

Not sure why you wouldn't configure a wakeup source. Typically something like a timer or a gpio should be set up to wake up the system.

We should of course configure a wake up source but this is not done automatically on all the platforms. E.g. SiLabs is using standard SysTick running on high frequency clock which is turned off the moment it enters a low power state. On this platform the Device Power Management is not implemented. It's a responsibility of the application to manage entry into low power states and set up a wake up source.

So indeed we can end up in idle prior to main(). The system power management _sys_suspend() function will be run the moment the kernel is initialized. Any code run in POST_KERNEL and later stage, including majority of the driver initialization code, can trigger entry into low power state.

@mnkp Thanks for the detailed explanation. The ability to switch to the idle thread before entering main() is something I am not used to, coming from my prior experience on TI-RTOS, where interrupts and threads aren't enabled til exiting main(). I'd have thought calling k_sleep()/k_sem_take() etc. would at least be frowned upon during driver initialization. Meanwhile, I personally haven't seen _sys_suspend() being called prior to main() while working on the cc1352r1_launchxl, given the existing drivers do not call functions that block the main thread during initialization.
In any event, it sounds like the issue you are facing is that the code responsible for setting up the devices that can act as wake-up sources doesn't get run prior to entering idle, potentially leading to a permanent sleep. Thinking out loud, instead of changing the defaults, there seem to be a few possibilities:

Change the drivers to not make calls that would block the main thread

Change the drivers of the devices that could act as wake-up sources to be initialized prior to POST_KERNEL initialization. Or maybe they can be prioritized to be initialized earlier in POST_KERNEL init, before the drivers that make blocking calls

Plug a PRE_KERNEL init function to call sys_pm_ctrl_disable_state() on the states that should not be entered during initialization, and re-enable them later after the drivers are initialized and when it is safe. This allows "lighter" sleep states that aren't relying on power-gating for example to stay enabled throughout, thereby saving power when k_sleep() or some other blocking call is made during driver initialization, which I think is the goal given it was preferred to k_busy_wait().

Add a system pm policy function that distinguishes initialization stage vs. when it is safe to sleep more deeply, and enter appropriate sleep states accordingly.

Would any of these (or a combination) work? Again, just throwing out some ideas.


[stable/pomerium] Pomerium v0.3.0 release

What this PR does / why we need it:
Updates helm chart to support Pomerium v0.3.0
Which issue this PR fixes

Related pomerium#292

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

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

/approve

/lgtm


[SCHEMA] Refactor channel types

We have lists of coordinate systems for different modalities

For example: MEG, EEG

Coordinate systems from EEG may also be used in MEG

This is nicely expressed in the schema, see the $ref items: https://github.com/bids-standard/bids-specification/blob/24dbe58010d96c0ce4d4c775230cef94605c6068/src/schema/objects/metadata.yaml#L60-L72

The situation is similar for channel types: we have types defined in different modalities (search for type__ieeg_channels, type__eeg_channels, type__meg_channels)

For example types like "EEG", "RESP", or "PUPIL" -- these are the same, regardless for which modality they are used (that is, specifying PUPIL in an EEG dataset is the same as PUPIL in an MEG dataset)

Currently these are organized as such: https://github.com/bids-standard/bids-specification/blob/24dbe58010d96c0ce4d4c775230cef94605c6068/src/schema/objects/columns.yaml#L471-L509

Meaning we have lots of duplication

Should we just have a single type__channels metadata entry? that is shared across the spec?
Or should we keep them modality specific in "overarching variables", but then have a type__channels defined as
type__channels:
  name: ....
  description: ...
  anyOf:
  - $ref: _type__meg_channels
  - $ref: _type__eeg_channels
  - $ref: _type__ieeg_channels
  - $ref: ...

closed in #919


a question for using autonlp for very little data

Hello, I was planning to use autonlp for a personal project of mine for multi class classification. I have generated sentence embeddings for a lot of sentences and they have labels, which I am planning to use as data. I have very little data for training the model, around 200 data points. Shall I try using autonlp or shall I use something else? Thanks.

Hi @deven367 !
You should definitely try out AutoNLP for your use case.
Bear in mind that AutoNLP only accepts text as input for now.
AutoNLP will generate a cost estimate for you before the training actually gets started, and you will have the opportunity to cancel or proceed with the training at that time.

That helps! Thank you.