2023-12-14T16:56:57.753+0100	DEBUG	The license file "node_modules/flatted/cjs/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.758+0100	DEBUG	License names are missing in "node_modules/nanoid/async/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.758+0100	DEBUG	The license file "node_modules/nanoid/async/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.758+0100	DEBUG	License names are missing in "node_modules/nanoid/non-secure/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.758+0100	DEBUG	The license file "node_modules/nanoid/non-secure/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.758+0100	DEBUG	License names are missing in "node_modules/nanoid/url-alphabet/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.758+0100	DEBUG	The license file "node_modules/nanoid/url-alphabet/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.758+0100	DEBUG	License names are missing in "node_modules/nth-check/lib/esm/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.758+0100	DEBUG	The license file "node_modules/nth-check/lib/esm/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.760+0100	DEBUG	License names are missing in "node_modules/rechoir/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.764+0100	DEBUG	License names are missing in "node_modules/regjsparser/node_modules/jsesc/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.764+0100	DEBUG	The license file "node_modules/regjsparser/node_modules/jsesc/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.764+0100	DEBUG	License names are missing in "node_modules/resolve/test/module_dir/zmodules/bbb/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.764+0100	DEBUG	The license file "node_modules/resolve/test/module_dir/zmodules/bbb/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.764+0100	DEBUG	License names are missing in "node_modules/resolve/test/resolver/baz/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.764+0100	DEBUG	The license file "node_modules/resolve/test/resolver/baz/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.764+0100	DEBUG	License names are missing in "node_modules/resolve/test/resolver/browser_field/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.764+0100	DEBUG	The license file "node_modules/resolve/test/resolver/browser_field/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.764+0100	DEBUG	License names are missing in "node_modules/resolve/test/resolver/dot_main/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.764+0100	DEBUG	The license file "node_modules/resolve/test/resolver/dot_main/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.764+0100	DEBUG	License names are missing in "node_modules/resolve/test/resolver/dot_slash_main/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.764+0100	DEBUG	The license file "node_modules/resolve/test/resolver/dot_slash_main/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.764+0100	DEBUG	License names are missing in "node_modules/resolve/test/resolver/false_main/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.764+0100	DEBUG	The license file "node_modules/resolve/test/resolver/false_main/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.764+0100	DEBUG	License names are missing in "node_modules/resolve/test/resolver/incorrect_main/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.764+0100	DEBUG	The license file "node_modules/resolve/test/resolver/incorrect_main/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.764+0100	DEBUG	License names are missing in "node_modules/resolve/test/resolver/invalid_main/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.764+0100	DEBUG	The license file "node_modules/resolve/test/resolver/invalid_main/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.764+0100	DEBUG	Walk error	{"file_path": "node_modules/resolve/test/resolver/malformed_package_json/package.json", "error": "unable to parse \"node_modules/resolve/test/resolver/malformed_package_json/package.json\": JSON decode error: unexpected EOF", "errorVerbose": "unable to parse \"node_modules/resolve/test/resolver/malformed_package_json/package.json\":\n    github.com/aquasecurity/trivy/pkg/fanal/analyzer/language/nodejs/license.(*License).Traverse.func1\n        /home/runner/work/trivy/trivy/pkg/fanal/analyzer/language/nodejs/license/license.go:36\n  - JSON decode error:\n    github.com/aquasecurity/go-dep-parser/pkg/nodejs/packagejson.(*Parser).Parse\n        /home/runner/go/pkg/mod/github.com/aquasecurity/go-dep-parser@v0.0.0-20231030050624-4548cca9a5c9/pkg/nodejs/packagejson/parse.go:39\n  - unexpected EOF"}
2023-12-14T16:56:57.764+0100	DEBUG	License names are missing in "node_modules/resolve/test/resolver/symlinked/package/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.764+0100	DEBUG	The license file "node_modules/resolve/test/resolver/symlinked/package/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.768+0100	DEBUG	License names are missing in "node_modules/svg-tags/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.773+0100	DEBUG	License names are missing in "node_modules/tslib/modules/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.773+0100	DEBUG	The license file "node_modules/tslib/modules/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.774+0100	DEBUG	License names are missing in "node_modules/vue/compiler-sfc/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.774+0100	DEBUG	The license file "node_modules/vue/compiler-sfc/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.774+0100	DEBUG	License names are missing in "node_modules/vue/packages/compiler-sfc/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.774+0100	DEBUG	The license file "node_modules/vue/packages/compiler-sfc/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.775+0100	DEBUG	License names are missing in "node_modules/yaml/browser/dist/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.775+0100	DEBUG	The license file "node_modules/yaml/browser/dist/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.775+0100	DEBUG	License names are missing in "node_modules/yargs/helpers/package.json", an attempt to find them in the "LICENSE" file
2023-12-14T16:56:57.775+0100	DEBUG	The license file "node_modules/yargs/helpers/LICENSE" was not found or the license could not be classified
2023-12-14T16:56:57.816+0100	DEBUG	OS is not detected.
2023-12-14T16:56:57.816+0100	DEBUG	Detected OS: unknown
2023-12-14T16:56:57.816+0100	INFO	Number of language-specific files: 24
2023-12-14T16:56:57.816+0100	INFO	Detecting pom vulnerabilities...
2023-12-14T16:56:57.816+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-tl-javacoap-server/pom.xml
2023-12-14T16:56:57.818+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: build-config/pom.xml
2023-12-14T16:56:57.818+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: build-config/demo-build-config/pom.xml
2023-12-14T16:56:57.818+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: build-config/lib-build-config/pom.xml
2023-12-14T16:56:57.818+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-client-demo/pom.xml
2023-12-14T16:56:57.819+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-integration-tests/pom.xml
2023-12-14T16:56:57.821+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-server-core/pom.xml
2023-12-14T16:56:57.822+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-tl-javacoap-client/pom.xml
2023-12-14T16:56:57.823+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-client-cf/pom.xml
2023-12-14T16:56:57.824+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-core-cf/pom.xml
2023-12-14T16:56:57.825+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-core-demo/pom.xml
2023-12-14T16:56:57.826+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: pom.xml
2023-12-14T16:56:57.843+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-server-cf/pom.xml
2023-12-14T16:56:57.844+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-server-core-demo/pom.xml
2023-12-14T16:56:57.845+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-server-redis/pom.xml
2023-12-14T16:56:57.846+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-server-demo/pom.xml
2023-12-14T16:56:57.847+0100	INFO	Detecting pnpm vulnerabilities...
2023-12-14T16:56:57.847+0100	DEBUG	Detecting library vulnerabilities, type: pnpm, path: leshan-server-demo/webapp/node_modules/<EMAIL_ADDRESS>2023-12-14T16:56:57.849+0100	INFO	Detecting yarn vulnerabilities...
2023-12-14T16:56:57.849+0100	DEBUG	Detecting library vulnerabilities, type: yarn, path: leshan-server-demo/webapp/yarn.lock
2023-12-14T16:56:57.850+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-tl-javacoap-core/pom.xml
2023-12-14T16:56:57.851+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-bsserver-demo/pom.xml
2023-12-14T16:56:57.853+0100	DEBUG	Detecting library vulnerabilities, type: pnpm, path: leshan-bsserver-demo/webapp/node_modules/<EMAIL_ADDRESS>2023-12-14T16:56:57.855+0100	DEBUG	Detecting library vulnerabilities, type: yarn, path: leshan-bsserver-demo/webapp/yarn.lock
2023-12-14T16:56:57.855+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-client-core/pom.xml
2023-12-14T16:56:57.856+0100	DEBUG	Detecting library vulnerabilities, type: pom, path: leshan-core/pom.xml

leshan-bsserver-demo/pom.xml (pom)

Total: 2 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 2, CRITICAL: 0)

┌────────────────────────────────┬───────────────┬──────────┬────────┬───────────────────┬────────────────────────┬──────────────────────────────────────────────────────────┐
│            Library             │ Vulnerability │ Severity │ Status │ Installed Version │     Fixed Version      │                          Title                           │
├────────────────────────────────┼───────────────┼──────────┼────────┼───────────────────┼────────────────────────┼──────────────────────────────────────────────────────────┤
│ ch.qos.logback:logback-classic │ CVE-2023-6378 │ HIGH     │ fixed  │ 1.3.11            │ 1.3.12, 1.4.12, 1.2.13 │ logback: serialization vulnerability in logback receiver │
│                                │               │          │        │                   │                        │ https://avd.aquasec.com/nvd/cve-2023-6378                │
├────────────────────────────────┤               │          │        │                   │                        │                                                          │
│ ch.qos.logback:logback-core    │               │          │        │                   │                        │                                                          │
│                                │               │          │        │                   │                        │                                                          │
└────────────────────────────────┴───────────────┴──────────┴────────┴───────────────────┴────────────────────────┴──────────────────────────────────────────────────────────┘

leshan-bsserver-demo/webapp/node_modules/<EMAIL_ADDRESS>(pnpm)

Total: 7 (UNKNOWN: 0, LOW: 0, MEDIUM: 1, HIGH: 5, CRITICAL: 1)

┌──────────────┬────────────────┬──────────┬────────┬───────────────────┬─────────────────────┬─────────────────────────────────────────────────────────────┐
│   Library    │ Vulnerability  │ Severity │ Status │ Installed Version │    Fixed Version    │                            Title                            │
├──────────────┼────────────────┼──────────┼────────┼───────────────────┼─────────────────────┼─────────────────────────────────────────────────────────────┤
│ json5        │ CVE-2022-46175 │ HIGH     │ fixed  │ 0.5.1             │ 2.2.2, 1.0.2        │ json5: Prototype Pollution in JSON5 via Parse Method        │
│              │                │          │        │                   │                     │ https://avd.aquasec.com/nvd/cve-2022-46175                  │
│              │                │          │        ├───────────────────┤                     │                                                             │
│              │                │          │        │ 1.0.1             │                     │                                                             │
│              │                │          │        │                   │                     │                                                             │
├──────────────┼────────────────┼──────────┤        ├───────────────────┼─────────────────────┼─────────────────────────────────────────────────────────────┤
│ loader-utils │ CVE-2022-37601 │ CRITICAL │        │ 1.4.0             │ 2.0.3, 1.4.1        │ loader-utils: prototype pollution in function parseQuery in │
│              │                │          │        │                   │                     │ parseQuery.js                                               │
│              │                │          │        │                   │                     │ https://avd.aquasec.com/nvd/cve-2022-37601                  │
│              ├────────────────┼──────────┤        │                   ├─────────────────────┼─────────────────────────────────────────────────────────────┤
│              │ CVE-2022-37599 │ HIGH     │        │                   │ 1.4.2, 2.0.4, 3.2.1 │ loader-utils: regular expression denial of service in       │
│              │                │          │        │                   │                     │ interpolateName.js                                          │
│              │                │          │        │                   │                     │ https://avd.aquasec.com/nvd/cve-2022-37599                  │
│              ├────────────────┤          │        │                   │                     ├─────────────────────────────────────────────────────────────┤
│              │ CVE-2022-37603 │          │        │                   │                     │ loader-utils:Regular expression denial of service           │
│              │                │          │        │                   │                     │ https://avd.aquasec.com/nvd/cve-2022-37603                  │
├──────────────┼────────────────┼──────────┤        ├───────────────────┼─────────────────────┼─────────────────────────────────────────────────────────────┤
│ postcss      │ CVE-2023-44270 │ MEDIUM   │        │ 7.0.39            │ 8.4.31              │ An issue was discovered in PostCSS before 8.4.31.  The       │
│              │                │          │        │                   │                     │ vulnerability af ......                                     │
│              │                │          │        │                   │                     │ https://avd.aquasec.com/nvd/cve-2023-44270                  │
├──────────────┼────────────────┼──────────┤        ├───────────────────┼─────────────────────┼─────────────────────────────────────────────────────────────┤
│ pug          │ CVE-2021-21353 │ HIGH     │        │ 2.0.4             │ 3.0.1               │ user provided objects as input to pug templates can achieve │
│              │                │          │        │                   │                     │ remote code...                                              │
│              │                │          │        │                   │                     │ https://avd.aquasec.com/nvd/cve-2021-21353                  │
└──────────────┴────────────────┴──────────┴────────┴───────────────────┴─────────────────────┴─────────────────────────────────────────────────────────────┘

pom.xml (pom)

Total: 2 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 2, CRITICAL: 0)

┌────────────────────────────────┬───────────────┬──────────┬────────┬───────────────────┬────────────────────────┬──────────────────────────────────────────────────────────┐
│            Library             │ Vulnerability │ Severity │ Status │ Installed Version │     Fixed Version      │                          Title                           │
├────────────────────────────────┼───────────────┼──────────┼────────┼───────────────────┼────────────────────────┼──────────────────────────────────────────────────────────┤
│ ch.qos.logback:logback-classic │ CVE-2023-6378 │ HIGH     │ fixed  │ 1.3.11            │ 1.3.12, 1.4.12, 1.2.13 │ logback: serialization vulnerability in logback receiver │
│                                │               │          │        │                   │                        │ https://avd.aquasec.com/nvd/cve-2023-6378                │
├────────────────────────────────┤               │          │        │                   │                        │                                                          │
│ ch.qos.logback:logback-core    │               │          │        │                   │                        │                                                          │
│                                │               │          │        │                   │                        │                                                          │
└────────────────────────────────┴───────────────┴──────────┴────────┴───────────────────┴────────────────────────┴──────────────────────────────────────────────────────────┘

as we can see in the log it's detected and scanned by trivy

I seems (not sure) to not only focus on maven dependencies but on everything it founds.
E.g. :
2023-12-14T16:56:52.161+0100	DEBUG	Start parent: org.infinispan:infinispan-build-configuration-parent:11.0.17.Final
2023-12-14T16:56:52.161+0100	DEBUG	Resolving org.infinispan:infinispan-bom:11.0.17.Final...
2023-12-14T16:56:52.162+0100	DEBUG	Start parent: org.jboss:jboss-parent:36

And also why scanning node_modules content, too ?
Maybe this is doable to configure it too only check a given pom.xml + 2 yarn.lock files.
I see it is also possible to give it a SBOM at SPDX or SPDX JSON, maybe this is a better way so we know exactly what it checks.
But there is still a real drawback with trivy, this one more tooling to install if you want to use it locally where OWAS Project Dependency Check has a maven plugin.

I think it's a good idea to do a full scan of the fs + dependencies because you never know what ends up in your build system (especially using heavy internet crawlers like maven and npm).
If you want to use Maven you can use owasp or snyk

I think it's a good idea to do a full scan of the fs + dependencies because you never know what ends up in your build system (especially using heavy internet crawlers like maven and npm).

Mmmh :thinking:
Initially, The goal was just to be sure that artifacts was not dependent of library with known vulnerability.
Maybe scanning everything could make sense if there are risks that build system could be "attack" to alter generated artifacts, I guess. I don't know if we should take this seriously. :thinking:

If you want to use Maven you can use owasp or snyk

I understand that snyk is not really open source.
So I will keep focus on OWAS or trivy. I will discuss about that with eclipse security team.
By the way, Thx for taking time to explore this way. :pray:


Bound RewardPointsin pallet-staking

... and add a log every time a validators is rewarded.
This is a very low hanging fruit in the direction of bounding the staking pallet i.e. https://github.com/paritytech/substrate/issues/8629

@kianenigma attempting this as well

Replaced with https://github.com/paritytech/substrate/issues/12039


Blocks in contraptions don't render when shaderpack real-time shadows are enabled

I'm using:

Forge 47.1.0 on 1.20.1
Create 0.5.1.d
Oculus 1.6.4
Rubidium 0.4.20
Oculus Flywheel Compat 0.2.0
Complementary Reimagined shaders

This is running on Linux, with an AMD RX 6800 XT GPU. When the real-time shadows in this or any other shaderpack are enabled, contraptions fail to render any ordinary blocks that are part of them. Disabling this mod fixes the issue, but at the expense of reasonable framerates.
Mod enabled:

Mod disabled:

I can attest to these findings with rendering set to instancing. In addition, there is some serious log spam:

and the Complementary Re-imagined shaderpack.

this is still an issue with 0.2.1, at least on fabric

fabric loader 0.14.24
fabric api 0.90.4
sodium 0.5.3
iris 1.6.10
create 0.5.1d from  https://github.com/Treetrain1/Create
iris flywheel compat 0.2.1
complimentary reimagined (but is an issue with any shader)

also running on linux with a 6800 XT. did anyone either of you find a workaround?

Confirmed this is happening for me as well.

Happening on my end as well. RX 6800 XT on Linux. Currently playing the Create Astral modpack. Viewing a contraption while shaders are enabled brings my framerate down into single digits, gives me the GL_INVALID_OPERATION in glDrawElements error repeatedly in my logs, and most blocks in the contraptions don't render.
Disabling real-time shadows does seem to fix it, at least in the Complimentary-based shaderpacks (I haven't tested any others yet).
Currently using:

OS: Linux
GPU: RX 6800 XT
Minecraft version 1.18.2
Fabric Loader 0.14.22
Create 0.5.0.i
Sodium 0.4.1
Iris 1.6.10
Iris Flywheel Compat 0.2.0
Tested with Complimentary Reimagined, Complimentary Unbound, BSL, AstraLex, and MakeUp UltraFast. All of them have the same issue.

I've been googling around for exactly the same Create Astral issue. I'm away from my home PC for a couple more days for the US holiday, but will test if disabling real-time shadows also fixes the issue for me.

I was able to confirm that turning off real-time shadows fixes the issue for me. I was unfortunately not able to get any debugging done - both RenderDoc and ApiTrace cause java to crash immediately if I try to launch minecraft with them loaded.

I got ApiTrace working, and managed to track this down :sunglasses:
The issue is that Create's ContraptionProgram hardcodes one of its samplers, which causes a conflict with Iris.
I've tested rebuilding Create with that sampler set to 31 (just to get it way out of the range that Iris might use), and things seem to work now?
I think the correct fix for this is probably to try to use a Mixin to override the Iris list of reserved samplers, but that is far beyond my java skills to implement as a quick PR to this repo without doing a lot more learning about how Mixins work.

Sorry for the issue update spam, but I dug through the Mixin docs and got this fixed!
The PR is in #86, but for anyone who feels like trusting a jar from a stranger on the internet, you can replace iris-flywheel-compat-1.18.2-0.2.0.jar in your mods folder with my version

My good friend, you're amazing.
I can confirm the fix is working on my end. I tested with the same set of shaders as last time, all are working fine even with realtime shadows re-enabled.

Sorry for the issue update spam, but I dug through the Mixin docs and got this fixed!
The PR is in #86, but for anyone who feels like trusting a jar from a stranger on the internet, you can replace iris-flywheel-compat-1.18.2-0.2.0.jar in your mods folder with my version

WIll this work as a replacement for the Oculus equivalent compatibility mod?


Update manage-agent.md

The note on supported proxy types was incorrect.

@edyoung - when you're ready for this to be reviewed, can you take it out of draft mode and ping the article author: @johnmarco to review the proposed changes?
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Converted SDF doesn't parse successfully.

Environment

OS Version: Debian bullseye
Source or binary build? Source: 17a4cf853a097b9adfa508876250044f367a4090

Description

Expected behavior: Either

Parses the SDF correctly (this SDF parses in libsdformat version 6.2).
Produces an error saying that it could not be converted properly.

Actual behavior: Produces an SDF that cannot be parsed correctly.

Note: using ::sdf::readString directly seems to work fine, but using the available API, this doesn't give access to an ::sdf::Root object.
Steps to reproduce
Run the following program:
#include <string>
#include <sstream>
#include <iostream>

#include "sdf/sdf.hh"

int main(int argc, char** argv) {
  const std::string sdf_text = R"(
    <?xml version="1.0"?>
    <sdf version="1.6">
      <model name="box">
        <pose>1 2 3 0 0 0</pose>
      </model>
    </sdf>)";

  ::sdf::SDFPtr sdf_ptr(new ::sdf::SDF);
  ::sdf::init(sdf_ptr);
  if (!::sdf::convertString(sdf_text, SDF_PROTOCOL_VERSION, sdf_ptr)) {
    std::cerr << "Error converting SDF";
    return 1;
  }

  std::cout << sdf_ptr->ToString();

  ::sdf::Root sdf_root;
  auto errors = sdf_root.Load(sdf_ptr);
  if (!errors.empty()) {
    std::stringstream status_string;
    for (const auto& error : errors) {
      status_string << error << "\n";
    }
    std::cerr << status_string.str();
    return 1;
  }

  std::cout << "Parsed sdf correctly!";
  return 0;
}

Output
<?xml version='1.0'?>
<sdf version='1.8'>
  <model name='box'>
    <pose>1 2 3 0 -0 0</pose>
  </model>
</sdf>
Error Code 16 Msg: A model must have at least one link.
Error Code 16 Msg: A model must have at least one link.
Error Code 24 Msg: FrameAttachedToGraph error: scope context name[] does not match __model__ or world.

The DOM classes sdf::Root, sdf::World, sdf::Model, etc add more semantic structure to the parsed SDFormat file than what is available through the sdf::Element API. An example of this structure is pose frame semantics, which was added in SDFormat 1.7 (http://sdformat.org/tutorials?tut=pose_frame_semantics&cat=specification&). This feature adds extra constraints, such as valid relative_to references and the requirement that non-static models have at least one link. However, the conversion that happens via sdf::convertString is more geared toward converting syntax changes between versions of the SDFormat spec.
It would be nice for the converter to know that the model is semantically invalid in SDFormat 1.8 and report that it can't be converted properly as you suggested, but I don't think that functionality should go in sdf::convertString. Perhaps we can update ign sdf -p to validate the converted string and report any errors. By the way, ign sdf -k does that already, but it doesn't print out the converted SDFormat.


Error loading CDN

WEB PART NOT LOADING: If you are getting the error: "Microsoft 365 learning pathways has a configuration issue. Ask your administrator for assistance". Please review the Diagnosing Pre-Check guidance before submitting your bug.

Submit your question
What is the context of your question

[X ] Installation
[ ] Learning Pathways Content
[ X] SharePoint Success Content
[ ] Administration
[ ] Custom Content
[ ] Viewer Web Part

Does our tenant have to have a CDN configured for the webpart to load

I was having issues with the M365 learning pathway and I had the above error. I downloaded the site again and deleted the old site and it appeared to fix. However the SharePoint Success site will not load correctly. We don't have a CDN set up in our tenant. I also don't understand how to run the PowerShell script for the manual configuration.

Hi @smcclements,
Thanks for reaching out to us and sorry for the delay in response!
Can you please run this script in PowerShell? Once that is done, refresh the LP site and then navigate to Success Center and see if that works. Thanks!


fix: update sentry issue url

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

#210  👈
#209
#208
main

This stack of pull requests is managed by Graphite.


Refresh on live Dashboard

Hi,
I’ve created Power BI dashboard using two different streaming datasets. First one is responsible for live data – so it’s refreshing every 1-2 seconds. The other dataset stores only text for scroller visual – and it’s refreshed every 2 hours.
My problem is – when live data are refreshed the scroller is also refreshed and starts over again making it impossible to read whole text.
I’ve also tried to change dataset from streaming to normal one (publishing from desktop) and it didn’t resolve the problem.

Have you tried playing around with this field, make it that it will only update the date once in a while. If not the best thing to do would be to implement a feature that when toggled will only update data once the data has been looped through. Maybe an idea like that can be a good solution.


Add more detail to contributing.md

Building off of #80 .. need more detail on how to contribute, what to change, etc for our future selves :)

tidy = FALSE  to suppress styler

relevant to #99


url_handlers vs scope_extensions

Hi Edge Devs,
can you please tell me which property is now supported? url_handlers or scope_extensions? None works for me. We have a multi tenant web application for which we would like develop mobile apps using pwa. Of course we would like to have only one app, not for every tenant. We have the root domain that is being used as a starting point and it can direct users to their instances. This works fine for ios using allowedOrigins, works fine from android using additionalTrustedOrigins, but I cannot make it work for windows. There is no such configuration option for windows and I get the address bar for my domains outside the root domain. I was trying to use url_handlers and scope_extensions in my manifest, but nono of that worked out. Can you please help me with this?
Thanks in advance for your help.
[Enter feedback here]

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

ID: d7f49d04-dd9e-9d95-6bc3-f158e4eacada
Version Independent ID: 5e3a5695-0978-7051-45d1-623dbb757f22
Content: Publish a Progressive Web App to the Microsoft Store - Microsoft Edge Development
Content Source: microsoft-edge/progressive-web-apps-chromium/how-to/microsoft-store.md
Product: microsoft-edge
Technology: pwa
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Hola @jaroslawdabrowski,
Here's some light on what is going on with url_handlers and scope_extensions. At the moment, url_handlers as a manifest field is not being considered nor worked on in Chromium. On the Edge side of things, we have a browser behaviour that is launching very soon that pretty much does the same thing as handling links for a specific domain. When you install a PWA on Windows, this PWA will automatically become the default link (or URL, if you wish) handler for the scope. For example, once I install Youtube as a PWA on Windows, if I click on www.youtube.com/some-video-address it will open in the Youtube PWA instead of in the browser. The user can control this behaviour from the app details page in edge://apps. There is a toggle that allows them to turn on/off this behaviour.
Regarding scope_extensions, this is actively being worked on atm and being led by the MS Edge team for Chromium. It is not ready, but when it lands on stable it will allow developers to expand the scope defined by the PWA, which could be used, for example, to include all TLD into the scope associated with a site.
But in summary, you are correct. url_handlers and scope_extensions currently do not work. One replaced by a modern browser behaviour, the other one still in development. Any other question I can help you with I am more than happy to reply.

Cześć Diego!
Thank you for your response, it is very helpful. Do you have any idea when scope_extensions will be supported? Any chance it will be available until end of this year? I am especially interested in edge, as we want to mobilize our app using PWABuilder, desktop windows app is using the edge windows and there we are facing an issue with our multi tenant architecture. Scope extensions would be very helpful. Thank you in advance for your response.

Thanks Diego.
We had added a note at the beginning of https://docs.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/handle-urls to that regard. It might actually be even better if we removed that page entirely. There's not much value in documenting url_handlers if it's going away.
Or we could keep it to document the customizable link handling behavior on Windows. And then, once scope_extensions is ready, add that to the same page.

Pinging @diekus on this thread so he can see the questions above.

Closing this as the related page has been updated: https://docs.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/handle-urls


Enable workloadidentity

Description of your changes
This PR sets workloadidentity and oidcissuer as enabled on the AKS cluster, and stores the OIDC issuer url into a configmap on the AKS cluster
I have:

[x] Read and followed Upbound's contribution process.
[x] Run make reviewable to ensure this PR is ready for review.

How has this code been tested
Deployed into Upbound-hosted control plane and provisioned an AKS cluster.

/test-examples

@djeremiah sorry for the long review, I clearly missed that one. Thanks a lot for the contribution! 👍


In some fps, pine resets the set_pos(x, y)

Hi there,
First of all great job. Im studying the project for research analysis also.
FYI in some fps (apex, Pubg), pine seems to work on main menu (autoaims main character selected) but aiming seems to reset to the ground in-game, when cursor comes across an enemy.
If I would take a guess, I would say that object detection returns null coordinates (?) and maybe give no input to said function. Didnt check code or input received, just brainstorming.
G

It happens with me too. If I press escape mouse is going to enemy, but if I not in Escape menu, it's resets mouse (0,0) when I looking to the enemy.


fix #1221 ConcurrentModificationException in TextReporter by returning new list

Fixes #1221
Did you remember to?

[ ] Add test case(s)
[x] Update CHANGES.txt

the fix here is returning new list of test result, to bypass ConcurrentModificationException when iterating in TestReporter.

@juherr , @cbeust , @krmahadevan , please help review the code and my comments. thanks

LGTM 👍

LGTM :+1: Ping @cbeust


replace user avatars with avatar image

Coverage remained the same at 22.876% when pulling f1531860956cc2dccf0ce27da421879393c8219f on theseyi:replace-user-avatars-with-avatar-image into 97f08e0b81ec677c65bbb399e5197c4c2dc176e3 on linkedin:master.

@cptran777 pretty much, if the image url errors out we fallback to a default image currently hosted on a cdn or somewhere else


feat(spec): Add API implementation

⚠ Best reviewed commit-by-commit

This PR

This PR adds the API object that implements the specifications from api-initialization-and-configuration
This PR does not implement anything else, as I would like to break up the implementations into several PR for clearer intent

Related Issues

References #7
Notes

Add concurrent-ruby for thread safe data structures

Follow-up Tasks

[ ] Add client implementation

How to test

Pull down branch
Run bundle exec rspec

Team going to merge this, but please let me know if there are any follow ups. I will continue to provide easy to review PR instead of everything in one PRs


....\src\get_str.c:100: GNU MP assertion failed: f > (‑n * (64 ‑ 0))

Description
What steps will reproduce the problem?

I ran this code to try out gmpy2 but sometimes it just fails and I have no idea what the error means. Can someone please tell me what this means and if there are any solutions.
Thanks,
import numpy as np
import gmpy2 as mp
mp.get_context().precision = 200
fish = np.empty(shape = 2,dtype = object)
for x in range(len(fish)):
fish[x] = mp.mpfr(np.random.random_sample())
fish[x] *= 10
'''for x in range(len(fish)):
fish[x] = fish[x] // 1
fish[x] = int(fish[x])'''
print(fish)
Traceback
  File "C:\Users\2wings\Anaconda3\lib\site-packages\psutil\_pswindows.py", line 679, in wrapper
    return fun(self, *args, **kwargs)
  File "C:\Users\2wings\Anaconda3\lib\site-packages\psutil\_pswindows.py", line 933, in create_time
    user, system, created = cext.proc_times(self.pid)
ProcessLookupError: [Errno 3] No such process (originated from GetExitCodeProcess != STILL_ACTIVE)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\2wings\Anaconda3\lib\site-packages\psutil\__init__.py", line 373, in _init
    self.create_time()
  File "C:\Users\2wings\Anaconda3\lib\site-packages\psutil\__init__.py", line 723, in create_time
    self._create_time = self._proc.create_time()
  File "C:\Users\2wings\Anaconda3\lib\site-packages\psutil\_pswindows.py", line 681, in wrapper
    raise convert_oserror(err, pid=self.pid, name=self._name)
psutil.NoSuchProcess: psutil.NoSuchProcess process no longer exists (pid=143812)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\2wings\Anaconda3\lib\site-packages\qtconsole\manager.py", line 27, in poll
    super(QtKernelRestarter, self).poll()
  File "C:\Users\2wings\Anaconda3\lib\site-packages\jupyter_client\restarter.py", line 113, in poll
    self.kernel_manager.restart_kernel(now=True, newports=newports)
  File "C:\Users\2wings\Anaconda3\lib\site-packages\jupyter_client\manager.py", line 390, in restart_kernel
    self.shutdown_kernel(now=now, restart=True)
  File "C:\Users\2wings\Anaconda3\lib\site-packages\jupyter_client\manager.py", line 350, in shutdown_kernel
    self._kill_kernel()
  File "C:\Users\2wings\Anaconda3\lib\site-packages\spyder\plugins\ipythonconsole\utils\manager.py", line 78, in _kill_kernel
    self.kill_proc_tree(self.kernel.pid)
  File "C:\Users\2wings\Anaconda3\lib\site-packages\spyder\plugins\ipythonconsole\utils\manager.py", line 44, in kill_proc_tree
    parent = psutil.Process(pid)
  File "C:\Users\2wings\Anaconda3\lib\site-packages\psutil\__init__.py", line 346, in __init__
    self._init(pid)
  File "C:\Users\2wings\Anaconda3\lib\site-packages\psutil\__init__.py", line 386, in _init
    raise NoSuchProcess(pid, None, msg)
psutil.NoSuchProcess: psutil.NoSuchProcess no process found with pid 143812
WARNING:traitlets:kernel died: 45.00029921531677
WARNING:traitlets:kernel died: 45.000248432159424

Versions

Spyder version: 4.1.1
Python version: 3.7.4
Qt version: 5.9.6
PyQt5 version: 5.9.2
Operating System: Windows 10

Dependencies

# Mandatory:
atomicwrites >=1.2.0           :  1.3.0 (OK)
chardet >=2.0.0                :  3.0.4 (OK)
cloudpickle >=0.5.0            :  1.3.0 (OK)
diff_match_patch >=20181111    :  20181111 (OK)
intervaltree                   :  None (OK)
IPython >=4.0                  :  7.13.0 (OK)
jedi =0.15.2                   :  0.15.2 (OK)
nbconvert >=4.0                :  5.6.1 (OK)
numpydoc >=0.6.0               :  0.9.2 (OK)
paramiko >=2.4.0               :  2.7.1 (OK)
parso =0.5.2                   :  0.5.2 (OK)
pexpect >=4.4.0                :  4.8.0 (OK)
pickleshare >=0.4              :  0.7.5 (OK)
psutil >=5.3                   :  5.7.0 (OK)
pygments >=2.0                 :  2.6.1 (OK)
pylint >=0.25                  :  2.4.4 (OK)
pyls >=0.31.9;<0.32.0          :  0.31.9 (OK)
qdarkstyle >=2.8               :  2.8 (OK)
qtawesome >=0.5.7              :  0.7.0 (OK)
qtconsole >=4.6.0              :  4.7.1 (OK)
qtpy >=1.5.0                   :  1.9.0 (OK)
rtree >=0.8.3                  :  0.9.3 (OK)
sphinx >=0.6.6                 :  2.4.0 (OK)
spyder_kernels >=1.9.0;<1.10.0 :  1.9.0 (OK)
watchdog                       :  None (OK)
zmq >=17                       :  18.1.1 (OK)

# Optional:
cython >=0.21                  :  0.29.15 (OK)
matplotlib >=2.0.0             :  3.1.3 (OK)
numpy >=1.7                    :  1.18.1 (OK)
pandas >=0.13.1                :  1.0.2 (OK)
scipy >=0.17.0                 :  1.4.1 (OK)
sympy >=0.7.3                  :  1.5.1 (OK)

Duplicate of #11872

It'll be fixed in our next version.

I'm sorry if the answer to my questions are obvious but why do i have the same problem with the code when using JupyterLab and Jupyter notebook?
Is there any way around it for now?

I'm sorry if the answer to my questions are obvious but why do i have the same problem with the code when using JupyterLab and Jupyter notebook?

You shouldn't, so I have no idea, sorry.

Is there any way around it for now?

You can downgrade to Spyder 4.0.1 in the meantime.

Downgrading to Spyder 4.0.1 didn't solve the problem for me, but thanks for the help anyways.


Phoenix ELN Server Package

A lot of things on this project are not really functional yet. The link that is supposed to lead to Phoenix ELN Server Package generates a 404 error coz it is not available and when you download the phoenix-eln-help.github.io, the index.html greets you with
"Ssdsdsdsds
Dsdsdsdsds
Dsdsdsdsds..."

The Phoenix-ELN Wiki and the readme file is the current 'official' source of the help documentation on the Phoenix ELN project page. Don't worry about Phoenix-eln-help.github.io, since it's work in progress to be linked later for consumption by the first non-beta Phoenix ELN release. And please let me know about the many other things you mentioned not to be working yet, to get them fixed if possible. Thanks.


Footer broken out of layout and title tag picks up document title in compaspkg

I made the footer its own file and I changed the title tag just like #3 for compaspkg, so it tracks the main compas theme more closesly.

@tetov sorry for the late reply. is this still relevant in the meantime?

No worries. The breaking out of footer is not necessary, but the title tag tweak is I would say. I'll update the PR.

@brgcode Ok, now it's only title tag change (and some whitespace that got picked up by my editor).


Uncontrolled tooltip

The uncontrolled tooltip with disableHoverListener set on true.
Expected Behavior
The setup disableHoverListener property affects the visibility of the standard html title property
Current Behavior
When the disableHoverListener prop is true and open prop is't present then standart html title is appear on wrapped elemen by on hover event.
Examples
  <Tooltip
      disableHoverListener
      title="text"
      <TextField />
  </Tooltip>

Isn't that what it's supposed to do? Don't prevent the default behavior and fallback to native tooltip behavior?
What is to use case for this? Why would you use the Tooltip component if you never want to display a tooltip?
I guess you issue is that you're passing undefined to open while you consider that Tooltip controlled? Have you considered casting to a boolean e.g.
 <Tooltip
      open={Boolean(possiblyUndefinedControlledOpen)}
      title="text"
      <TextField />
  </Tooltip>

@eps1lon I believe it's a bug. We shouldn't be displaying the native title even when people are using disableHoverListener. We need to change the handler a bit. It shouldn't be too hard to fix.

@eps1lon  I mean a behavior that @oliviertassinari showed. In the docs in trigger sections same case https://material-ui.com/demos/tooltips/


StorageType 'Azure_Ephemeral_OS_Disk' is invalid

When attempting to create a machine catalog with a provisioning scheme using an ephemeral OS disk, it fails as follows:
2024-04-24T10:04:17.386+0100 [ERROR] provider.terraform-provider-citrix_v0.5.5: Response contains error diagnostic:
  diagnostic_detail=
  | TransactionId: f3365277-c4e3-429f-bb91-629b4fbbbf84
  | JobId: f184f5f2-b8ac-4fd4-83c0-614cc72ad66f
  | Error message: Failure result exists during validating provisioning scheme creation.
   tf_req_id=18293840-229b-970c-6a72-d28efbc43b8c tf_resource_type=citrix_machine_catalog @caller=github.com/hashicorp/terraform-plugin-go@v0.22.2/tfprotov6/internal/diag/diagnostics.go:58 @module=sdk.proto diagnostic_severity=ERROR diagnostic_summary="Error creating Machine Catalog" tf_proto_version=6.4 tf_provider_addr=registry.terraform.io/citrix/citrix tf_rpc=ApplyResourceChange timestamp="2024-04-24T10:04:17.386+0100"
2024-04-24T10:04:17.390+0100 [ERROR] vertex "citrix_machine_catalog.MC09-AVDdaasCMP-009" error: Error creating Machine Catalog
╷
│ Error: Error creating Machine Catalog
│
│   with citrix_machine_catalog.MC09-AVDdaasCMP-009,
│   on catalogs.tf line 1, in resource "citrix_machine_catalog" "MC09-AVDdaasCMP-009":
│    1: resource "citrix_machine_catalog" "MC09-AVDdaasCMP-009" {
│
│ TransactionId: f3365277-c4e3-429f-bb91-629b4fbbbf84
│ JobId: f184f5f2-b8ac-4fd4-83c0-614cc72ad66f
│ Error message: Failure result exists during validating provisioning scheme creation.

Upon checking the error details in Citrix DaaS, under Manage, it implies the StorageType is invalid:
Failure result exists during validating provisioning scheme creation.
Stack Trace:
   at Citrix.Orchestration.Base.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.ThrowOnTerminatingError(SdkProvisioningSchemeAction sdkProvisioningSchemeAction)
   at Citrix.Orchestration.Base.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.WaitForProvisioningSchemeActionCompletion(Guid taskId, Action`1 actionResultsObtained)
   at Citrix.Orchestration.Base.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeCreationTask.StartProvisioningAction()
   at Citrix.Orchestration.Base.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeCreationTask.RunTask()
   at Citrix.Orchestration.Base.PowerShellSdk.BackgroundTaskService.BackgroundTask.Task.Run()

StudioErrorId : ProvisioningTaskError
ErrorCategory : NotSpecified
TaskState : ValidationFailure
TaskStateInformation : Terminated
ErrorId : ValidationFailure
Operation : ValidatingInputs
ErrorMessage : Error: The following custom properties have invalid storage type values: 'StorageType'

From my experience and limited testing using the code I shared in PR (#45), the custom property UseEphemeralOsDisk is required to provision ephemeral OS disks, as described here: https://docs.citrix.com/en-us/citrix-daas/install-configure/machine-catalogs-create/create-machine-catalog-citrix-azure.html#create-a-machine-catalog-with-an-azure-ephemeral-disk

I had hoped to work around this by setting storage_type = "Standard_LRS" and using the new custom_properties argument, as follows, to provision ephemeral OS disks:
custom_properties = [
  {
    name  = "UseEphemeralOsDisk"
    value = "true"
  }
]

However, that failed too, unfortunately 😞
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to citrix_machine_catalog.MC09-AVDdaasCMP-009, provider
│ "provider[\"registry.terraform.io/citrix/citrix\"]" produced an unexpected new value: .provisioning_scheme: inconsistent
│ values for sensitive attribute.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Thanks @j7lloyd for pointing this out. We will work on a fix for this.
Aneesh


Rename the "master" branch to "main"

Understandably this might be too complex and risky to do for Solid org-wide, so doing it on a repo-by-repo basis would also be a good start and help to test things out.

Identify what might break.
Note back references (eg. in documentation, code) that might need changing.
Document repositories to omit, if any.
Document how people can update their cloned repositories.
Set a date for the announcement and send it out.
Switch
Update back references.

Anything else that should be recorded here?

This appears to have been done.


Currently, smoke tests fail due to timeouts being to low on CI/CD environment. Increase timeouts to observe passing tests.

smoke tests fail because mozart API is not storing and returning job IDs properly. pele service is not running. figaro UI does not display new jobs in CI environment.
pele.log file reveals that issue is caused by pele/bach incompatibility due to breaking change in Flask/werkzeug dependency.
Solution may be to pin 2.0.x version in bach-api setup.py rather than 2.1.x

OK - yeah curious to see if reverting to 2.0.x removes this issue...

pinning the older version has allowed pele and bach-api to run upon deployment. Tests still fail.
We found that disk utilization is at 100% on mozart instance.
Partially caused by the large test-files that get downloaded as part of build+deployment.
I'll address this by adding increasing the disk size as configured in terraform script main.tf
Separately, we should review disk usage by the terraform scripts (delete test files as last deployment step, remove any unnecessary download procedures, etc).
We should also review any instance type we had previously increased before we knew about being able to increase disk size without changing instance types.
There is also an issue with the python environment the cluster sets up. bach-api and pele (or any other distinct service) should have their own python environments. this is a common practice in other teams/orgs when managing python applications.

@chrisjrd - we should set up alerts for OPS to be able to be notified in critical disk situations like this.
What's the best way for @niarenaw to monitor disk-usage on Mozart in an operational setting? Are these disk metrics reported to Kabana and can we set up an alert if above 90% disk usage?


[FR] Option to resize columns

Ability to drag and resize the columns.

The pluigin borns with that feature, but now we have a visual conflict with drag and drop columns, so its disable at the moment until find a better way to achive it

This feature is already developed with https://github.com/RafaelGB/obsidian-db-folder/issues/189


Homebridge doesn't seem to receive device status updates

The plugin doesn't seem to receive any device status updates.
As an example, in my case I have a simple electric outlet that I've added to my Tuya IoT Cloud project. If I update the state outside of Homebridge (e.g. turning it off physically by pressing the on/off switch on the plug itself, changing the state via a Tuya automation, etc.), the stale state will remain in Homebridge until I change the state in Homebridge (or until I restart the Homebridge service).
If this is unexpected, is there anything that I should check to make sure the Tuya Homebridge plugin is properly set up? Thanks for help.

I created a new project with "Smart Home" selected as the "Development Method" and it started receiving those messages. Not sure what the differences are between the different development methods but that fixed it. Thanks for the help!


Fix updateClusterInc for overlapping ports

It is possible that a service will have multiple ports, with the same
port number. The typical example here is kube-dns, which uses port 53
for UDP and TCP. When we do an incremental push, we would select the
first port to match the port number, which would sometimes causes us to
ignore the correct port. This fix searches through all matching ports.
Hopefully fixes https://github.com/istio/istio/issues/11658

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: howardjohn
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: vadimeisenbergibm
If they are not already assigned, you can assign the PR to them by writing /assign @vadimeisenbergibm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio_auth_sds_e2e

prow/istio-integ-k8s-tests.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio_auth_sds_e2e

prow/istio-integ-k8s-tests.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio_auth_sds_e2e

prow/istio-integ-k8s-tests.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio-pilot-multicluster-e2e

prow/e2e-mixer-no_auth.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: costinm, howardjohn
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [costinm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e_pilotv2_auth_sds.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio-pilot-multicluster-e2e

prow/e2e-mixer-no_auth.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test e2e-mixer-no_auth

prow/istio-integ-k8s-tests.sh
1947de4da453a12315c52c9043db10192ea3f4e6
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
b2d5d92d86c2562cc879e3c3a26cf11a4be5b1cf
link
/test e2e-mixer-no_auth

prow/istio-integ-k8s-tests.sh
1947de4da453a12315c52c9043db10192ea3f4e6
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
1947de4da453a12315c52c9043db10192ea3f4e6
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn since there is uncertainty about the change (and since it's a good idea regardless), how about a few test cases?
@Stono heads up, targeted for 1.1.2 which should be available April 1st (not joking)

@duderino awesome thanks for the update.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
1947de4da453a12315c52c9043db10192ea3f4e6
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
9b546a83872b586a22c7463b56ab1f46582c0196
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
9b546a83872b586a22c7463b56ab1f46582c0196
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
9b546a83872b586a22c7463b56ab1f46582c0196
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn Have you tested the case without the first two commits?

Yes, test fails without the changes

Then /lgtm, let it in and we'll see if the issue can happen again.

/test e2e-bookInfoTests-trustdomain

@rshriram @duderino this is ready to merge


Update ANF APRL related to AZ

Overview/Summary
Updated ANF APRL related to Availability Zone based on feedback from Sean Luce and Igor Pagliai.
A. Use availability zones for high availability in Azure NetApp Files: High Availability (specifically at the application level)
B. Enable Cross-zone replication of Azure NetApp Files volumes: Unchanged.
C. Deploy ANF volumes in the same availability zone with Azure compute and other services: Other Best Practices
Related Issues/Work Items
Replace this with a list of related GitHub Issues and/or ADO Work Items (Internal Only)

To associate a GitHub Issue, use a key word preceded with the GitHub issue number.
To associate an ADO Work Item, use the key word AB# succeeded with the ADO Work Item ID.

This PR fixes/adds/changes/removes

A. Use availability zones for high availability in Azure NetApp Files. Changes to the wordings to improve clarity.
C.  Deploy ANF volumes in the same availability zone with Azure compute and other services: Other Best Practices.
ARG automation not possible, since we are not able to know what are the compute and other services that should be in the same zone as ANF.

Breaking Changes
N/A
As part of this pull request I have

[X] Read the Contribution Guide and ensured this PR is compliant with the guide
[X] Checked for duplicate Pull Requests
[ ] Associated it with relevant GitHub Issues or ADO Work Items (Internal Only)
[X] Ensured my code/branch is up-to-date with the latest changes in the main branch
[X] Ensured PR tests are passing
[ ] Performed testing and provided evidence (e.g. screenshot of output) for any changes associated to ARG queries: // cannot-be-validated-with-arg
[ ] Updated relevant and associated documentation (e.g. Contribution Guide, Docs etc.)

@igorpag and @seanluce , please kindly review. Thanks!

It's been reviewed offline by Igor and Sean.


iOS: Possible Daylight savings issue

On Sunday March 13, 2016. It was "spring forward" in the US.
Select an end time for Sunday, say 5pm.
When it is saved and retrieved, end time changes from 5pm to 6pm.
This is a bug. However, a question that arises is how prevalent is this? Is it just for the Sunday schedule? What happens for days beyond March 13? Will test those and enter findings in this ticket.

This issue occurrs because when we are updating a schedule time using the UI, the SAM is basing the date off of the initial date that the schedule was created, and appending the time that we selected to it. So if the the schedule was created in February and we are making a change in May, the SAM will perform calculations using the date in February. When the SAM then calculates when the next alarm time in May should be, that time is one hour off.
There is a comment in the code where it is suggested that we should be using NSCalendar arithmetic. We are currently computing the next alarm time by increasing the previous alarm time by the repeat interval in seconds. This computation is prone to the errors that we are seeing here.


Gold Virtual Airlines Livery

Hi There,
Can you please add the attached liveries to the Bluebell list? VA name is Gold Virtual Airlines, our callsign starts with "GLD".
Liveries attached: A319, A320, B738, C172, PC12.

There is no PC12 in the Bluebell package, so I can't add that one. I can only add liveries for aircraft that are in the package.
Your C172 looks like it was created for a different aircraft model than the one that is in the Bluebell set, causing it to look malformed (see attached image) so I can't add that one either.
I can add your A319, A320, and B738.

Thanks for the information and quick reply! Can you please move forward with A319, A320 and B738?
Regarding PC12, that's okay, I have an object list related to PC12 which works good when we add it manually in Bluebell folder, if you want to take a look at the objects I will be glad to share with you.
Regarding C172, the aircraft model was the attached one, if this one is different from Bluebell set, would you mind sharing the aircraft model so we can create the livery based on that?

Sure, I'll add the Airbus and Boeing to my list to be added to the package when I next get a chance.
The C172 in the Bluebell package looks like this:

Airbus and Boeing have been added.


Switch to next row when using tab to go through cells

If a user uses tab hotkey to go through all cells, I expect that it goes to the next row if it reaches the end of the first row. However, it does switch to the next selectable element on the page instead:
https://user-images.githubusercontent.com/2852129/222752434-6b023204-dd49-4be1-8bfa-3408b1aa2360.mov

Wonder if onKeyDown can be used as a work-around for now.

I think what we need to do is add a callback for this event so that the user can decide what to do. In our app we actually want it to tab into the rightElement.

For this I used the onFinishedEditingCallback.  In it you get the movement and with the columns you can check if there is a cell on the right. If not, just set the gridselection to the next row.


Card crash when there is no data

When using a boolean to limit updates of hasl-platform, I receive the following:
https://<host>:8123/local/hasl-traffic-status-card.js:243:59 Uncaught TypeError: Cannot read property 'toLowerCase' of undefined
I noticed this when I restarted, with the sensor disabled, such that there is no data retrieved. Unfortunately it also crashes Lovelace for me, in the sense that I am no longer able to edit the UI of that specific tab.

I'll look into it asap and try to reproduce it.

I'm using Chrome on Windows 10 by the way. And I've had similar experience when I was working on my own card, so the issue that I cannot modify Lovelace is probably more of an issue with Lovelace and not the card itself.
But it is still good to see if it can be fixed.


On first succesfull login against LDAP, created user.id is not propagated

On first succesfull login against LDAP, created user.id is not propagated to next(), hence login fails although user is successfully created in Konga's datastore

we also found this issue during LDAP auth login

We are using LDAP also and same fix did the trick. Thanks


Release 1.0.0

[x] Fix bot payments when there aren't enough megacredits and you need to overshoot on resources: https://github.com/jankeromnes/terraforming-mars-bot/blob/513eff412420903d587dd771f79b8b9323fc0736/bots/quantum.js#L250
[x] Fix other runtime errors (e.g. run node play-bot --games=100 successfully without --ignore-errors)
[x] Make bots support multi-player games by polling for game.waitingFor
[ ] Allow node play-bot to resume a game in progress (i.e. skip choosing corporation & initial cards if already done)
[x] Teach Quantum Bot to claim milestones

I played a game against Quantum Bot today. It was pretty good! I'd place it between "easy" and "moderate":

Fixed by https://github.com/jankeromnes/terraforming-mars-bot/commit/ed3e072ee8dd16f3c13e98bc5cde225223e502c7

I played another game against both Quantum and Random bot to celebrate 1.0.0.
Here are the results:


Change the view bounds to match the parent

Is it possible to change the view bounds of the ticker so it matches the parent? The problem is that i can see animation starts just a little above the the ticker, not from the top of the view. i have set ticker to match the parent and gravity to center, the ticker pop up in the center but the view doesn't match the parent, more like wrap content.

Sorry for the late reply. I'm not too sure of the problem you are describing. Is the width or height not being set to match_parent? A video demonstrating the effect would be awesome.


Property configurable on product detail page

Description
Add checkboxe to the property set configuration to choose wether to show a property on the PDP. If the checkbox is not checked, the property should not be shown on the frontend.

Hello,
Within our company roadmap and work capacity, we try to address each bug or improvement request but admit that not each one will be resolved. To continue our culture of honesty and openness, we are closing this issue to focus on our roadmap on behalf of all Shopware users.
If you feel like this issue is still impacting you, please create a new issue and let us know.
Thank you again for your valuable feedback.


add missing events

Codecov Report
Base: 96.73% // Head: 96.84% // Increases project coverage by +0.10% :tada:

Coverage data is based on head (0d906e9) compared to base (2b4545d).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
+ Coverage   96.73%   96.84%   +0.10%
==========================================
  Files           3        3
  Lines          92       95       +3
  Branches       18       18
==========================================
+ Hits           89       92       +3
  Misses          3        3

Impacted Files
Coverage Δ

contracts/ERC20Pods.sol
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.