🐛 Bug Report: Module not found: Can't resolve 'prop-types'

📜 Description
yarn dev gives errors
👍 Expected behavior
I expect yarn dev not to give error
👎 Actual Behavior with Screenshots
Module not found: Can't resolve 'prop-types' in '/home/******/backstage/.yarn/__virtual__/@backstage-core-compat-api-virtual-276b8ff93b/3/.yarn/berry/cache/@backstage-core-compat-api-npm-0.3.3-387ec573fb-10c0.zip/node_modules/@backstage/core-compat-api/dist/core-app-api/src/apis/system'

yarn/__virtual__/@backstage-core-compat-api-virtual-276b8ff93b/3/.yarn/berry/cache/<EMAIL_ADDRESS>
app]: (node:11081) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.

[app]: (Use `node --trace-deprecation ...` to show where the warning was created)

[app]: Loaded config from app-config.yaml

[app]: <i> [webpack-dev-server] Project is running at:

[app]: <i> [webpack-dev-server] Loopback: http://localhost:3000/, http://<IP_ADDRESS>:3000/

[app]: <i> [webpack-dev-server] Content not from webpack is served from '/home/******/backstage/packages/app/public' directory

[app]: <i> [webpack-dev-server] 404s will fallback to '/index.html'

[app]: <i> [webpack-dev-middleware] wait until bundle finished: /

[app]: WARNING in ../../.yarn/__virtual__/@graphiql-toolkit-virtual-9348e0f5b6/3/.yarn/berry/cache/<EMAIL_ADDRESS>58:33-54

[app]: Module not found: Error: @graphiql/toolkit tried to access graphql-ws (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: graphql-ws

[app]: Required by: @graphiql/toolkit@virtual:e9f17852ebde331b2219033d9dac8a150dfec9efc5c3917331b90e4863e05faafa64e95ee95a26007c2a233048bbfa0755af4c81e98bfba9d21faa14ce733b7c#npm:0.9.2 (via /home/******/backstage/.yarn/__virtual__/@graphiql-toolkit-virtual-9348e0f5b6/3/.yarn/berry/cache/@graphiql-toolkit-npm-0.9.2-f1b0c14e9d-10c0.zip/node_modules/@graphiql/toolkit/esm/create-fetcher/)

[app]:

[app]: Ancestor breaking the chain: @graphiql/react@virtual:02736cbc45d5e20abb0bbe7e8f42a40e039d378dc3268232bc17bfd2b9ffe6d4c81257af4ce770b636974a6c679d2461e14d279b5b2be16c80e3f45a1ecec93c#npm:0.20.4

[app]: Ancestor breaking the chain: @graphiql/react@virtual:4afe9c491b99da45123c11d27418938435cfa1944c42f6bcb3e1f7f6ecbf38062473011144061d82fbf21264364e5db2686067f3ff5c26035e9a5b8f26d9b527#npm:0.23.1

[app]: Ancestor breaking the chain: graphiql@virtual:4afe9c491b99da45123c11d27418938435cfa1944c42f6bcb3e1f7f6ecbf38062473011144061d82fbf21264364e5db2686067f3ff5c26035e9a5b8f26d9b527#npm:3.1.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/@backstage-core-compat-api-virtual-276b8ff93b/3/.yarn/berry/cache/<EMAIL_ADDRESS>2:0-35

[app]: Module not found: Error: Can't resolve 'prop-types' in '/home/******/backstage/.yarn/__virtual__/@backstage-core-compat-api-virtual-276b8ff93b/3/.yarn/berry/cache/@backstage-core-compat-api-npm-0.3.3-387ec573fb-10c0.zip/node_modules/@backstage/core-compat-api/dist/core-app-api/src/apis/system'

[app]:

[app]: ERROR in ../../.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/index.js 3:14-28

[app]: Module not found: Error: ajv-errors tried to access ajv (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: ajv

[app]: Required by: ajv-errors@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:3.0.0 (via /home/******/backstage/.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/index.js 4:18-53

[app]: Module not found: Error: ajv-errors tried to access ajv (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: ajv

[app]: Required by: ajv-errors@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:3.0.0 (via /home/******/backstage/.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/index.js 5:15-55

[app]: Module not found: Error: ajv-errors tried to access ajv (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: ajv

[app]: Required by: ajv-errors@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:3.0.0 (via /home/******/backstage/.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/index.js 6:19-55

[app]: Module not found: Error: ajv-errors tried to access ajv (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: ajv

[app]: Required by: ajv-errors@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:3.0.0 (via /home/******/backstage/.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/index.js 7:17-51

[app]: Module not found: Error: ajv-errors tried to access ajv (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: ajv

[app]: Required by: ajv-errors@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:3.0.0 (via /home/******/backstage/.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/index.js 8:16-49

[app]: Module not found: Error: ajv-errors tried to access ajv (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: ajv

[app]: Required by: ajv-errors@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:3.0.0 (via /home/******/backstage/.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/react-draggable-virtual-5f823067f2/3/.yarn/berry/cache/react-draggable-npm-4.4.6-4867b50158-10c0.zip/node_modules/react-draggable/build/cjs/Draggable.js 15:39-59

[app]: Module not found: Error: react-draggable tried to access react-dom (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: react-dom

[app]: Required by: react-draggable@virtual:2f088a2a99035b057643a4e8eb9fe02ccce5e4081316606fbfab5f849f5fb4b459e0ba26b1b51557ab9df59ead121e1cdf14b997d2db38a505ab2db1bf1c094f#npm:4.4.6 (via /home/******/backstage/.yarn/__virtual__/react-draggable-virtual-5f823067f2/3/.yarn/berry/cache/react-draggable-npm-4.4.6-4867b50158-10c0.zip/node_modules/react-draggable/build/cjs/)

[app]:

[app]: Ancestor breaking the chain: react-resizable@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:3.0.5

[app]:

[app]: ERROR in ../../.yarn/__virtual__/react-draggable-virtual-5f823067f2/3/.yarn/berry/cache/react-draggable-npm-4.4.6-4867b50158-10c0.zip/node_modules/react-draggable/build/cjs/DraggableCore.js 9:39-59

[app]: Module not found: Error: react-draggable tried to access react-dom (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: react-dom

[app]: Required by: react-draggable@virtual:2f088a2a99035b057643a4e8eb9fe02ccce5e4081316606fbfab5f849f5fb4b459e0ba26b1b51557ab9df59ead121e1cdf14b997d2db38a505ab2db1bf1c094f#npm:4.4.6 (via /home/******/backstage/.yarn/__virtual__/react-draggable-virtual-5f823067f2/3/.yarn/berry/cache/react-draggable-npm-4.4.6-4867b50158-10c0.zip/node_modules/react-draggable/build/cjs/)

[app]:

[app]: Ancestor breaking the chain: react-resizable@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:3.0.5

[app]:

[app]: ERROR in ../../.yarn/__virtual__/use-immer-virtual-6ebf1047c8/3/.yarn/berry/cache/use-immer-npm-0.10.0-b79035b5e6-10c0.zip/node_modules/use-immer/dist/use-immer.module.mjs 1:0-44

[app]: Module not found: Error: use-immer tried to access immer (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: immer

[app]: Required by: use-immer@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:0.10.0 (via /home/******/backstage/.yarn/__virtual__/use-immer-virtual-6ebf1047c8/3/.yarn/berry/cache/use-immer-npm-0.10.0-b79035b5e6-10c0.zip/node_modules/use-immer/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: webpack compiled with 10 errors and 1 warning

[app]: <i> [webpack-dev-middleware] wait until bundle finished: /runtime.js

[app]: <i> [webpack-dev-middleware] wait until bundle finished: /module-backstage.js

[app]: <i> [webpack-dev-middleware] wait until bundle finished: /module-material-ui.js

[app]: <i> [webpack-dev-middleware] wait until bundle finished: /module-lodash.js

[app]: <i> [webpack-dev-middleware] wait until bundle finished: /module-core-js-pure.js

[app]: <i> [webpack-dev-middleware] wait until bundle finished: /module-date-fns.js

[app]: WARNING in ../../.yarn/__virtual__/@graphiql-toolkit-virtual-9348e0f5b6/3/.yarn/berry/cache/<EMAIL_ADDRESS>58:33-54

[app]: Module not found: Error: @graphiql/toolkit tried to access graphql-ws (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: graphql-ws

[app]: Required by: @graphiql/toolkit@virtual:e9f17852ebde331b2219033d9dac8a150dfec9efc5c3917331b90e4863e05faafa64e95ee95a26007c2a233048bbfa0755af4c81e98bfba9d21faa14ce733b7c#npm:0.9.2 (via /home/******/backstage/.yarn/__virtual__/@graphiql-toolkit-virtual-9348e0f5b6/3/.yarn/berry/cache/@graphiql-toolkit-npm-0.9.2-f1b0c14e9d-10c0.zip/node_modules/@graphiql/toolkit/esm/create-fetcher/)

[app]:

[app]: Ancestor breaking the chain: @graphiql/react@virtual:02736cbc45d5e20abb0bbe7e8f42a40e039d378dc3268232bc17bfd2b9ffe6d4c81257af4ce770b636974a6c679d2461e14d279b5b2be16c80e3f45a1ecec93c#npm:0.20.4

[app]: Ancestor breaking the chain: @graphiql/react@virtual:4afe9c491b99da45123c11d27418938435cfa1944c42f6bcb3e1f7f6ecbf38062473011144061d82fbf21264364e5db2686067f3ff5c26035e9a5b8f26d9b527#npm:0.23.1

[app]: Ancestor breaking the chain: graphiql@virtual:4afe9c491b99da45123c11d27418938435cfa1944c42f6bcb3e1f7f6ecbf38062473011144061d82fbf21264364e5db2686067f3ff5c26035e9a5b8f26d9b527#npm:3.1.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/@backstage-core-compat-api-virtual-276b8ff93b/3/.yarn/berry/cache/<EMAIL_ADDRESS>2:0-35

[app]: Module not found: Error: Can't resolve 'prop-types' in '/home/******/backstage/.yarn/__virtual__/@backstage-core-compat-api-virtual-276b8ff93b/3/.yarn/berry/cache/@backstage-core-compat-api-npm-0.3.3-387ec573fb-10c0.zip/node_modules/@backstage/core-compat-api/dist/core-app-api/src/apis/system'

[app]:

[app]: ERROR in ../../.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/index.js 3:14-28

[app]: Module not found: Error: ajv-errors tried to access ajv (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: ajv

[app]: Required by: ajv-errors@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:3.0.0 (via /home/******/backstage/.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/index.js 4:18-53

[app]: Module not found: Error: ajv-errors tried to access ajv (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: ajv

[app]: Required by: ajv-errors@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:3.0.0 (via /home/******/backstage/.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/index.js 5:15-55

[app]: Module not found: Error: ajv-errors tried to access ajv (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: ajv

[app]: Required by: ajv-errors@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:3.0.0 (via /home/******/backstage/.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/index.js 6:19-55

[app]: Module not found: Error: ajv-errors tried to access ajv (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: ajv

[app]: Required by: ajv-errors@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:3.0.0 (via /home/******/backstage/.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/index.js 7:17-51

[app]: Module not found: Error: ajv-errors tried to access ajv (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: ajv

[app]: Required by: ajv-errors@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:3.0.0 (via /home/******/backstage/.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/index.js 8:16-49

[app]: Module not found: Error: ajv-errors tried to access ajv (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: ajv

[app]: Required by: ajv-errors@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:3.0.0 (via /home/******/backstage/.yarn/__virtual__/ajv-errors-virtual-0e13d0bc2e/3/.yarn/berry/cache/ajv-errors-npm-3.0.0-cbd6be5a29-10c0.zip/node_modules/ajv-errors/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: ERROR in ../../.yarn/__virtual__/react-draggable-virtual-5f823067f2/3/.yarn/berry/cache/react-draggable-npm-4.4.6-4867b50158-10c0.zip/node_modules/react-draggable/build/cjs/Draggable.js 15:39-59

[app]: Module not found: Error: react-draggable tried to access react-dom (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: react-dom

[app]: Required by: react-draggable@virtual:2f088a2a99035b057643a4e8eb9fe02ccce5e4081316606fbfab5f849f5fb4b459e0ba26b1b51557ab9df59ead121e1cdf14b997d2db38a505ab2db1bf1c094f#npm:4.4.6 (via /home/******/backstage/.yarn/__virtual__/react-draggable-virtual-5f823067f2/3/.yarn/berry/cache/react-draggable-npm-4.4.6-4867b50158-10c0.zip/node_modules/react-draggable/build/cjs/)

[app]:

[app]: Ancestor breaking the chain: react-resizable@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:3.0.5

[app]:

[app]: ERROR in ../../.yarn/__virtual__/react-draggable-virtual-5f823067f2/3/.yarn/berry/cache/react-draggable-npm-4.4.6-4867b50158-10c0.zip/node_modules/react-draggable/build/cjs/DraggableCore.js 9:39-59

[app]: Module not found: Error: react-draggable tried to access react-dom (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: react-dom

[app]: Required by: react-draggable@virtual:2f088a2a99035b057643a4e8eb9fe02ccce5e4081316606fbfab5f849f5fb4b459e0ba26b1b51557ab9df59ead121e1cdf14b997d2db38a505ab2db1bf1c094f#npm:4.4.6 (via /home/******/backstage/.yarn/__virtual__/react-draggable-virtual-5f823067f2/3/.yarn/berry/cache/react-draggable-npm-4.4.6-4867b50158-10c0.zip/node_modules/react-draggable/build/cjs/)

[app]:

[app]: Ancestor breaking the chain: react-resizable@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:3.0.5

[app]:

[app]: ERROR in ../../.yarn/__virtual__/use-immer-virtual-6ebf1047c8/3/.yarn/berry/cache/use-immer-npm-0.10.0-b79035b5e6-10c0.zip/node_modules/use-immer/dist/use-immer.module.mjs 1:0-44

[app]: Module not found: Error: use-immer tried to access immer (a peer dependency) but it isn't provided by its ancestors; this makes the require call ambiguous and unsound.

[app]:

[app]: Required package: immer

[app]: Required by: use-immer@virtual:a7a802bc5340a2e40a3d926ec44287230d65a8c9f8efca5eb3b1bbe92df57f4b06eb9d2a8800f5154bdb1379b3daaa432ce5a6842ac891f0c147044f836c1b70#npm:0.10.0 (via /home/******/backstage/.yarn/__virtual__/use-immer-virtual-6ebf1047c8/3/.yarn/berry/cache/use-immer-npm-0.10.0-b79035b5e6-10c0.zip/node_modules/use-immer/dist/)

[app]:

[app]: Ancestor breaking the chain: @backstage/plugin-scaffolder-react@virtual:61fd75c06494a77bc816fbecd0b16ced200bb99a8ff41c648f6807d6060eaa85f85d26e470db20a9bbcdce3476f6300a1a5970d37f2efbc5d4e25379ace17b65#npm:1.14.1

[app]:

[app]: webpack compiled with 10 errors and 1 warning

👟 Reproduction steps
brand new ab, freshly created
📃 Provide the context for the Bug.
No response
🖥 Your Environment
ubunu 22.04
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

What's the __virtual__ thing? Could you share your yarnrc file perhaps (with secrets redacted), could it be that you are using yarn pnp? If so, you should try disabling that and use the regular node linker instead.

idk, that's your stuffs guys :-)
so far I have to change "link" to "file" in package.json to be able to install the missing package
so I ..

intall the missing package using --legacy-peer-deps (otherwise it is not working)
yarn install
tar ned and see the app complaining another package is missing

and start again
no offense but this sucks, what is the point of using such a complex packaging system and resorting to yarn and everything if stuffs are still missing when running the app ?
and I followed the doc on your site to install it on a regular LTS linux server

Most likely there's something particular about your env. Given massive numbers of users and never seeing a report like this before at least as far as I can recall, I do wonder what could possibly be up. Maybe you have yarn settings in your home directory or company-wide that affect what it does.
Do not use npm commands. Use yarn add instead of npm install.
Do not add dependencies at the root. react-draggable has no business being in /package.json for example. If you want to add things to the app, do it to packages/app. But again, this should all not be happening either way.
We are compatible with node 20 and 22, not 23. Use 20 to be sure it's not some bleeding-edge problem of sorts.

well now you have one user that installed a FRESH ubuntu 24.04 on a vm (virtualbox) and has an issue with it out of the box, without modifying anything on his system (I JUST INSTALLED Ubuntu, did nothing else to it, just good old default install)
I created an issue https://github.com/backstage/backstage/issues/28081
as for this issue, it is on VM at work running a ubuntu 22.04 ... I finally have the app showing the guest box
I had to install all these ajv-errors ajv react-draggable prop-types react-dom react immer graphql-ws graphql

ok I recreated the app and now no more modules to install although the app asks for a guest account, not really in phase with the documentation

ok I recreated the app and now no more modules to install although the app asks for a guest account, not really in phase with the documentation


state keys from component views refactoring in

Refactored state keys by extracting keys from component views to a pub(crate) module state_keys within component crates fixes  #802

Merged, thanks so much for your help with this!


Draggable Canvas GameObject causes problems in Canvas Layout Groups

This is a simple issue. The VRTK Canvas adds a child to itself, which, if its a layout group will actually insert a ghost element and shift all the intended elements down.
One suggestion is to add a checkbox to the VRTK Canvas to allow/disallow making this Draggable Canvas object. Haven't looked into what it does, so my suggestions are limited.

This was also causing me issues, both with messing up the button grid layout as well as preventing interacting with buttons that were in the region of the generated canvas.
As a work around to I added a bool to the code (default on) and disabled the feature for the instances where I want to use the grid layout.
public bool draggableCanvas = true;
...
if (canvas && draggableCanvas && !canvas.transform.FindChild(CANVAS_DRAGGABLE_PANEL))

That is a nice fix @roskelld and it is probably a good idea to allow the users of VRTK to specify whether or not they actually need that dragging support in a canvas. So one could improve performance a bit by not even creating that "helper game object".
I'm currently having a look at solving this problem without that option, though. I think Unity allows to ignore UI elements for layout purposes. That should fix this issue.


Add definition of svelte to readme and homepage

When I'm finally to the point of pushing a first version of this thing out the door, and I'm doing the little finishing touches on the README file and the project home page, I want to include the definition of the word svelte to give people an explanation of why I named the library "CSVelte".

The idea is that the library is supposed to be both slender (lightweight, small size, low memory, fast) and elegant (intuitive OOP interface, well-documented, clear but concise code, sugary syntax, pluggable, etc.)
Maybe I would include the above definition of svelte and then add below it a new definition:
csvelte
svelt,sfelt/
adjective
adjective: csvelte

    (of a CSV document) slender and elegant.

Added graphic to README

I added the graphic but the background color is slightly off so it looks shitty. Fix it.


Support building dynamic libraries by default

I'm having trouble setting up a build for dynamic libraries. I can still do lake build Foo:shared but I'm unable to successfully set up the lakefile such that lake build Foo produces shared libraries.
mwe:
lake init Foo
change lakefile to:
import Lake
open Lake DSL

package foo {}

@[defaultTarget]
lean_lib Foo {}

Now I can do lake build Foo:shared and build/lib/libFoo.so gets created. I would like to lake build to do the same. I should set nativeFacets right?
However, I have tried:
  nativeFacets := #[`dynlib]
  nativeFacets := #[`shared]
  nativeFacets := #[`externLib.dynlib]

None of these work and they all give me application type mismatch error.
Tested on leanprover/lean4:nightly-2022-08-16

This is not currently supported. It is on the TODO list though.

Ohh I see, I will move onto something else in the mean time then.

Thanks for getting this done, any chance getting this in master by the end of the month?

@lecopivo Yes, I certainly hope to have v4.1 out by the end of the month.


Add base unit test suite for repository server controller(#PR1)

Change Overview
This PR add a base suite that would be used to add unit tests for repository server controller
Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[ ] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[ ] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test

Issues

fixes #issue-number

Test Plan

[ ] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

@kale-amruta can you please add test plan in this PR and and the things that are being tested in the PR desc.


MAGETWO-60033 : FIM (Markka) removed from currency

Finland has moved to EUR in 2001

Relevant issue in Magento 2 repo:
https://github.com/magento/magento2/issues/6832

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

@SubrataBauri I think that if we remove the deprecated Finnish currency, we should also remove all other deprecated currencies. For example all other European currencies that were used before the Euro are still in this list. Talking about the German Mark, French Franc, Spanish Peseta, etc. These currencies are deprecated since 2002.
I think other currencies have been deprecated in the past decades as well, but I'm not aware which currencies those are. But I think cleaning up this list with more then just one currency is useful. Not sure if you have the time, but it would be great if you can do this.

@ArjenMiedema can you provide the list of all the deprecated currencies? I can find time to clean them up.

@SubrataBauri I don't know all deprecated currencies. All I know is that back in 2002 the Finnish Markka has been replaced by the Euro. The same goes for the old currencies for the following European countries:

Germany
Ireland
The Netherlands
Greece
France
Luxembourg
Austria
Belgium
Italy
Portugal
Spain

So those currencies can also be related. Big change is that there are more non-European currencies that are deprecated, but I don't know those.

All these XML files come from the external library "CLDR - Unicode Common Locale Data Repository" and you should not modify these files. You need to use a newer version of this library, but this ends up in a dead end:

CLDR v25 is the latest version for ZF1. Newer versions of CLDR means refactoring the Zend_Date class.

https://github.com/zendframework/zf1/issues/436


Update fitness station preset

What

[x] Add Fitness Station Type combo
[x] Remove address field from Fitness Station

Just merged this, and added a bunch of fitness station presets from the osm wiki..
Thanks @JamesKingdom 👍


SQL Injection and Cross-site Scripting in class-validator - '^0.12.2'

In TypeStack class-validator, validate() input validation can be bypassed because certain internal attributes can be overwritten via a conflicting name. Even though there is an optional forbidUnknownValues parameter that can be used to reduce the risk of this bypass, this option is not documented and thus most developers ### configure input validation in the vulnerable default manner. With this vulnerability, attackers can launch SQL Injection or XSS attacks by injecting arbitrary malicious input.
The default settings for forbidUnknownValues has been changed to true in 0.14.0.
Is there any plan to update the version of class-validator  form v0.12.2 to v0.14.0( or latest version)

if there is a plan can you please update the ETA for that.
we are currently using the module ngx-reactive-form-class-validator in a live application, that would be really help full if the upgrade is done ASAP.

Hi @kalyangoud145,
Thanks for flagging this! I’m on it and will be releasing an updated version of ngx-reactive-form-class-validator this week, aligning it with class-validator ^0.14.0 to address the security issue you mentioned.
Stay tuned, and I’ll make sure you can update seamlessly. Appreciate your vigilance and patience!


Buttons on IDE activity popups for free-range tasks

Description of the PR

Adds optional action buttons to the IDE activity popups. Currently used only by free-range tasks
Adds a new optional field in the IDE activity JSON configuration file "freeRange" (default: false)

Testing

unit
integration
e2e
manual

- [ ] new unit tests created
- [X] all unit tests pass

- [ ] new integration tests created
- [X] all integration tests pass

- [ ] new e2e tests created
- [X] all e2e tests pass

- [X] manual testing went well

Have you updated the TESTING.md or other relevant documentation on your branch?

[ ] Yes.
[ ] Not yet. I will do it next.
[x] Not relevant.

Good! 👍 Just curious: when using null actions, is action in JSON null or string "null" or either?

It is "null", not null


Dotnet 5

Codecov Report

Merging #12 (10189f8) into master (cacff65) will decrease coverage by 1.89%.
The diff coverage is 44.00%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
- Coverage   49.05%   47.15%   -1.90%
==========================================
  Files          11       11
  Lines         369      369
==========================================
- Hits          181      174       -7
- Misses        188      195       +7

Impacted Files
Coverage Δ

Mysb/DataAccess/FirmwareDAO.cs
80.62% <0.00%> (-4.11%)
:arrow_down:

Mysb/Liasons/MQTTLiason.cs
0.00% <ø> (ø)

Mysb/Liasons/SourceLiason.cs
0.00% <ø> (ø)

Mysb/Models/Options/MQTTOpts.cs
0.00% <ø> (ø)

Mysb/Program.cs
0.00% <0.00%> (ø)

Mysb/Models/Options/SharedOpts.cs
33.33% <33.33%> (ø)

Mysb/Models/Shared/Firmware.cs
100.00% <100.00%> (ø)

Mysb/Models/Shared/LoadedFirmwareInfo.cs
100.00% <100.00%> (ø)

Mysb/Models/Shared/NodeFirmwareInfoMapping.cs
75.00% <100.00%> (ø)

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 cacff65...a5f87b8. Read the comment docs.


error after password entry

I started harbor for the first time and entered a password similar to "test.1234" and got the following error:
marius@a64:~/harbor$ cargo run --features vendored
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.27s
     Running `target/debug/harbor`
Core loaded
ERROR r2d2 > near ".1234": syntax error

Then, I started again and entered just "test":
marius@a64:~/harbor$ cargo run --features vendored
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.27s
     Running `target/debug/harbor`
Core loaded
 ERROR r2d2 > database is locked
 ERROR r2d2 > database is locked

How do I unlock the DB to try again?

you may need to delete the db and start over it is located in ~/.harbor

that worked, and I can start harbor now 💯


sap_ha_install_hana_hsr: review backup strategy

Follow-up on comment https://github.com/sap-linuxlab/community.sap_install/pull/161#discussion_r909559915

Should also consider on roles/sap_ha_install_hana_hsr/tasks/run_backup.yml:

#161 (comment on 31-34)
#161 (comment on 47-50)


Changing layout button.

Existing Button

To Create

Use of JS and simple CSS.

I am working on it. Please assign the issue to me.

This icon is only to be updated in first year. Right?

Is this icon only to be updated in first year page or any other page too?

Is this icon only to be updated in first year page or any other page too?

Just update in a single page first


Layout issue of nz-table with both nzCustomFilter and sort

Reproduction link
https://ng-zorro-antd-start-e91wps.stackblitz.io
Steps to reproduce
1, make a new nz-table
2, add nzCustomFilter on th with corresponding nz-dropdown-menu
3, add nzShowSort and (nzSortChange) on same th element
What is expected?
sort icon should sit on right side of column name, while filter icon should sit at right side of column cell
What is actually happening?
the filter icon sits at middle and bottom side between column name and sort icon, which is ridiculous

Environment
Info

ng-zorro-antd
8.0.2

Browser
Chrome 75

BTW, there is already an existing issue report: https://github.com/NG-ZORRO/ng-zorro-antd/issues/3722
wondering why it was closed...

same as: https://github.com/NG-ZORRO/ng-zorro-antd/issues/3721


typo: Double word "be"

@nschonni : Thanks for your contribution! The author, @dan-wesley, has been notified to review your proposed change.


Upgrade Gradle and Android SDK versions.

Motivation
Address Path Traversal Vulnerability
Improve build speeds by restricting which dependencies leak their APIs to other modules.
Improve performance on up to date Android phones.
Decrease memory use.
https://developer.android.com/studio/releases/gradle-plugin.html#3-0-0
https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html#new_configurations
To maintain your application along with each Android release, you should increase the value of this attribute to match the latest API level, then thoroughly test your application on the corresponding platform version.
https://developer.android.com/guide/topics/manifest/uses-sdk-element.html
https://medium.com/google-developers/picking-your-compilesdkversion-minsdkversion-targetsdkversion-a098a0341ebd
https://developer.android.com/training/basics/supporting-devices/platforms.html#sdk-versions
Align with FBSDK:
Facebook SDK for Android Changelog 4.x

Changelog and release notes for the Facebook SDK for Android.
4.30.0 - January 24, 2018
Facebook SDK
Added
Protection against Path Traversal Vulnerability: https://support.google.com/faqs/answer/7496913
Support for variant-aware dependency management in Gradle 4.1 and Android Studio 3.0

Path Traversal Vulnerability
What’s happening
Beginning January 16th, 2018, Google Play will block publishing of any new apps or updates which contain the Path traversal Vulnerability. Your published APK version will remain unaffected, however any updates to the app will be blocked unless you address this vulnerability.
Android SDK versions
https://developer.android.com/sdk/api_diff/24/changes.html
https://developer.android.com/sdk/api_diff/25/changes.html
https://developer.android.com/sdk/api_diff/26/changes.html
https://developer.android.com/sdk/api_diff/27/changes.html
https://developer.android.com/about/versions/oreo/android-8.0.html
Various media api improvements
Picture-in-Picture mode
Partial Java 8 support
https://developer.android.com/studio/write/java8-support.html
https://developer.android.com/about/versions/oreo/android-8.1.html

Memory optimizations. Improved memory usage across the platform to ensure that apps can run efficiently on devices with 1GB or less RAM.

Flexible targeting options. New hardware feature constants to let you target the distribution of your apps to normal or low-RAM devices through Google Play.

Google Play.While all apps will be available on devices running Android Oreo (Go edition), Google Play will give visibility to apps specifically optimized by developers to provide a great experience for billions of people with the building for billions guidelines.

Test Plan
Run CI
Related PRs
Update docs
Release Notes
[ANDROID] [ENHANCEMENT] [Framework] - Upgrade to latest stable and hopefully less vulnerable versions.

@hramos any news on this?

Not yet. Current priority is getting all of our tests back to green. Until then, we cannot make this sort of change to the codebase.

@hramos are you referring to internal fb tests? If you're talking about external facing tests is there any place where we can all break them down and hand them out to people to help get them to start passing? I think staying up to date with the native tools are very important so I would be happy to help in anyway that I can.

I was referring to external tests. They run on Circle, you can find the definitions at .circleci/config.yml. These are now green as of last week.
We do have a large suite of tests that run internally, that for the most part concern the use of React Native in our own product's surfaces. I am currently focusing on catching test breakages internally at Facebook before they land and sync to GitHub. There are several reasons this may happen even with our internal tests in place: we use our own test infrastructure that is quite different from Circle; we may be using newer buck builds that have yet to reach open source; we have a monorepo that depends on the latest Metro packager which may also not yet exist in npm; and so on.
While we use buck to build the project internally, we do not do so from within the same open source React Native repo. I am working on resolving that blind spot, in order to catch buck failures that have broken our Circle tests in the past.
Which brings me to this PR: as I am adding buck back to our internal tests, I am running into issues due to the use of different Android SDK versions between internal/open source. Once I solve this, I should come back to this PR and suggest which exact versions we should be using in order to match internal.
Stay tuned.

@hramos looks like Circle CI is needing to upgrade the emulator and download the Android SDK 27 for it to pass test_android

Your emulator is out of date, please update by launching Android Studio:

Start Android Studio
Select menu "Tools > Android > SDK Manager"
Click "SDK Tools" tab
Check "Android Emulator" checkbox
Click "OK"

Error: could not find version  of the Android SDK.
Specifically, the directory /opt/android/sdk/platforms/android- does not exist.
You probably need to specify the right version using the SDK Manager from within Android Studio.

@MarkOSullivan94 Thanks for the heads up.
The error is located here: https://github.com/facebook/react-native/pull/17747/#discussion_r185937805.
Also, it looks like we may have to clear the CircleCI cache, because new Android deps are not installed if $ANDROID_HOME/installed-dependencies is there.

@msand Any time to resolve the conflict ?

I haven't looked into the source code of create-react-native-app in too much detail so perhaps someone here would know the answer to my question: How will this change affect create-react-native-app?
I know the eject command builds the android and ios directories for RN projects but how would it know what gradle version / target API version to use?
#18095 would also be affecting by this.

I think Circle CI is broken. The checks it's showing are from 1 month ago: https://circleci.com/gh/facebook/react-native/41794?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
Current status: 4 failing and 5 successful checks.

Don't you need to update react.gradle file too? That all depends on implementation details of the old version of Android tools.

@gengjiawen @tasomaniac Fixed conflicts and addressed feedback

closing this PR because SDK 27, support library 27.x and android gradle plugin 3.1 is landed in master.


question: is it worth to have two table component?

Hi,
i'm wondering does it have advantages to keep the grid functionality in two directives? I'm almost sure that all other grid components i've seen (i've digged in a lot during my work:-), angular and non-angular ones) has only one directive that handles both ajax and local data sources. That way the writer can easily avoid some code redundances (eg. templates for headers, sorting, pagination, filtering) and is more motivated to design a feature to work with any data source (eg. when implementing a row-drag'n-drop).

You are right. We are planing to merge them into one directive in next major release.

It's fine!


[Internal] Create a lint to make sure java classes are not imported from kotlin classes

When converting to kotlin it's very easy to get crossed imports.
If we see a package foo.kotlin, none of the code in there should import from foo.java

@samstern how are you planning on implementing this?
As some sort of style check or baked into the default lint check?

I think this could be implemented inside the internal module and exported as lintChecks.
I have only done a custom lint check one time, and that's in FirebaseUI-Android.  I may try to copy from that, but I don't actually know if that's the easiest way.
But anyway yeah I can tackle this one, unless you really want to do it just for learning purposes.

I wanted to explore this as I've not done something like this before.
Can you share the relevant code you did in FirebaseUI?
I can use that as reference and try to fix this one by myself and if things hit the fan you can take over.
How does that sound?

Sgtm!  Here's an example lint check in FBUI:
https://github.com/firebase/FirebaseUI-Android/blob/master/internal/lint/src/main/java/com/firebaseui/lint/FirestoreRecyclerAdapterLifecycleDetector.kt
There are others in that folder as well.  We did some really strange
packaging tricks to be able to hide our lints from library users but you
won't have to do any of that.
On Fri, Sep 7, 2018, 4:57 PM Harshit Dwivedi<EMAIL_ADDRESS>wrote:

I wanted to explore this as I've not done something like this before.
Can you share the relevant code you did in FirebaseUI?
I can use that as reference and try to fix this one by myself and if
things hit the fan you can take over.
How does that sound?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/firebase/quickstart-android/issues/643#issuecomment-419595138,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIEw6lFhth1znvolyH8DKvElaMZOdjeOks5uYwfLgaJpZM4WffG6
.


increment version name/version code

increment version name and version code prior to release
also creating pr to verify that github tests pass

merging as these changes are minor updates to build files


Add basic E2E tests

Description

Upgrade CI workflows to Ubuntu 22.04 (new E2E workflows require it because a newer curl version is required)
Add basic E2E tests to the CI pipeline

Build the connector (same as build.yaml for now)
Deploy Kafka broker (w/ Kraft), Kafka Connect (both Bitnami) and Localstack
Deploy the connector
Create SQS queue and EventBridge Rule/Target to send to SQS on pattern match
Send an event
Assert that the connector keeps running, i.e., no exception thrown after sending the event
Dump logs so one can inspect if the event was sent to EventBridge*

Note
Due to a bug in Localstack, we currently can't assert the event was delivered to SQS. Once this bug is fixed, these E2E tests will be replaced by Java E2E tests.

Test Steps
Runs on PRs, commits to main, and scheduled.
Tested in my forked repo since this workflows requires secrets access which are not allowed from forked repos (hence the steps are failing here).
Checklist:

[x] I have tested my changes. No regression in existing tests.
[ ] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue
Closes: #38
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@maschnetwork PTAL


node label management in k8s

Current Behavior
task requirment specified by device
Proposed Behavior
task requirment specified by node label & resource requirements
Solution Proposal
use k8s label management

done


How to use getResultsByKey when querying a field with array of ids

In the following Batchloader I'm querying products which contains an array of ids and I get a result, the part I can't work out is getResultsByKey as the join has an empty result. I'm assuming it's getRecordKeyFunc that I've got wrong but not really sure what I should be returning in this situation.
    context._loaders.items.products = new BatchLoader(
      async (keys, context) => {
        const result = await context.app.service('item').find(
          makeCallingParams(
            context,
            {
              products: { $in: getUniqueKeys(keys) },
              $select: ['title', 'products']
            },
            null,
            { paginate: false }
          )
        );
        console.log(result); // This part works
        return getResultsByKey(keys, result, item => item.products, '[!]', {
          defaultElem: []
        });
      },
      { context }
    );

item.products is plural. Is it an array? getResultsByKey expects

Its keys param to be an array of strings or numbers, each being a record key.
its getRecordKeyFunc to return a string or number which matches one of the keys elements.

Let me know if item.products is an array. I'll see what can be done.
Otherwise give me a sample keys and results.

yes item.products is an array so in my mongoose schema it looks like
const item = new Schema(
    {
      products: [
        {
          type: ObjectId,
          ref: 'product'
        }
      ],
    },
    {
      timestamps: true
    }
  );

I think this issue can be closed now. Feel free to reopen it.


QuickStart is not DuneSQL Compatible

Discord AwesomeQA sent me to this link for an interval question, but this references old interval formatting which fails in DuneSQL:
https://github.com/duneanalytics/docs/blob/master/zh/docs/getting-started/query-quick-start/example.md#blob-path

It sent you to the chinese docs version 😓
It now is indexed on dune.com/docs, should not happen again.


It is not specified how many arguments will be given along with an array, so we cannot determine how to write the code for number of arguments not known.

Challenge Seek and Destroy has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

function destroyer(arr, a, b) {
  arr = arr.filter(function(val) {
    return val!==a;
  });
  arr = arr.filter(function(val) {
    return val!==b;
  });
  return arr;
}

destroyer([2, 3, 2, 3], 2, 3);

I have used two extra arguments here a and b, but that is temporary solution, because the number of extra arguments is not specified.

Hello,
JavaScript functions have a built-in object called the arguments object.
The argument object contains an array of the arguments used when the function was invoked.
Some Code:
` fooBar(1, 123, 500, 115, 44, 88);
function fooBar() {
for (var i = 0; i < arguments.length; i++) {
console.log(arguments[i]);
}
}
Output:
1
123
500
115
44
88
`
fooBar() does not define any parameter however we can insert them since Javascript does not check the number of arguments. To access the arguments you need to access arguments object.
Have a play with the code. :)

I understand the frustration because I remember having trouble with this one as well.
However, I don't believe there is any problem with this challenge. My tip is that you read the links provided in the final part of the instruction. There are ways to handle an unknown number of arguments.
In the future, please click the "Help" button on the challenge on freeCodeCamp instead of asking for help here. This button will take you to the help chatroom for that specific challenge. You can also view our full list of official chatrooms.
If you think I'm wrong in closing this issue, please reopen it and add further clarification. Thank you, and happy coding.

Thank you for the answer as well as the advice.
Big help!
On Fri, Jan 27, 2017 at 2:51 PM, Samuel Plumppu<EMAIL_ADDRESS>wrote:

Closed #12906 https://github.com/freeCodeCamp/freeCodeCamp/issues/12906.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/12906#event-939011838,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV5kwNmHGigCo7N4x8ZPhaFd9B2gog1pks5rWbclgaJpZM4Lvgpa
.


Abstract_text: Add a method to get string representation of float in scientific notation

Add a method to_se to get the string representation of float in scientific notation.
123.45.to_se == "1.2345e+02"
0.001234.to_se  == "1.234e-03"
10860460000.0.to_se == "1.086046e+10"

The to_se method have a precision between 1 to 6 max decimal. The precision is adapted in function of the number.
Add a to_precision_size_with_format and to_precision_fill_with_format method to get the representation in a specific given format

To my knowledge, there is no language that specifically provides a method for returning a string with scientific notation. Generally the conversion is done using a user-specified format. The best solution would be to define a more verbose name. Example to_s_expo_notation or something else.

https://python-reference.readthedocs.io/en/latest/docs/float/scientific.html

@Morriar Your link it's for returns a float multiplied by the specified power. The objective of this pr is to provide a method to return a string representing a float in a scientific notation.

May I suggest something like to_sci for the name? Bit more concise than to_scientific_notation, and slightly more explicit than to_se in my eyes

@R4PaSs nice, the to_sci look good, but to_scientific_notation it's also correct.
@privat what do you prefers?

+0.1e1 for to_sci


[Feature Request] Add pie chart

What is the feature ?
Add pie charts.
(Optional) Why this feature is useful and how people would use the feature ?
This is usefult to represent the parts in a whole.
(Optional) Additional Information
Matplotlib has pie chart that could be used as a reference
https://matplotlib.org/3.1.1/gallery/pie_and_polar_charts/pie_features.html

I'm interested in picking this one up. but I'm not sure what  approach can even be possible.
I was originally thinking of making up a triangle for each of those slices, rotate accordingly, and use a circle as mask to round off the edges, but

I can't find how to rotate a shape
looks like using a shape as a mask isn't possible
Another approach would be defining a circular drawing area, and putting the triangles in there to be cropped accordingly, but that's not going to happen either.
Yet again another idea, giving up on circles and triangles, and just looking at building those with polygons, with ideally a curved line for the arc part (Polygon doesn't support curved lines, so that may be at best defined as 1px lines going along the radius?).

I'm just coming up with worse and worse ideas, and even those don't seem to be easily feasible.
Nevermind allowing something such as exploding a slice, or nested pies.
Can anyone more experienced give some sort of guidance on how that could be implemented?


fix the doc according to code

Overview
fix the doc according to code
Changed
the doc of pagination

Hi @nicholaslee119 thank you for trying to improve the documentation. Though it may sound confusing, but the document you tried to fix explains the properties in the options of Pagination class, that allows you to change the event name the document explains: https://github.com/carbon-design-system/carbon-components/blob/f91ab133304fcc7aa3be48fd341857f6d0f392e5/src/components/pagination/pagination.js#L122-L124
It'd be great if you have any ideas on how to explain that. Using the default event names you may have wanted may be one way to go, but we should change the whole codebase if we'd go this way. Thanks!

@asudoh
Thanks to your review, I misunderstood the mean of name of events in the document. so I can add a  listener to those events just like
this.pagination.element.addEventListener('eventPageChange', (e)=>{ //todo });

until I figure it out in the code of carbon-components.
this.pagination.element.addEventListener('pageChange', (e)=>{ //todo });

I think it is necessary to add the column of default value of event, just like those default selector

Makes sense now 👍 - Thanks @nicholaslee119 for jumping in for other components, too!


Starting truckersmp-cli using proton-tkg

i cant start using proton tkg, the logs shows  :
truckersmp-cli --account bimokn97 --prefixdir '/home/bimo/Game/Steam/steamapps/compatdata/227300' --gamedir '/home/bimo/Game/Steam/steamapps/common/Euro Truck Simulator 2' --protondir /home/bimo/.steam/root/compatibilitytools.d/proton_tkg_6.8.r15.gf308782d --proton --activate-native-d3dcompiler-47 --enable-d3d11 --ets2 --start Traceback (most recent call last):   File "/home/bimo/.local/bin/truckersmp-cli", line 19, in <module>     main()   File "/home/bimo/.local/lib/python3.9/site-packages/truckersmp_cli/main.py", line 153, in main     start_game()   File "/home/bimo/.local/lib/python3.9/site-packages/truckersmp_cli/main.py", line 210, in start_with_proton     activate_native_d3dcompiler_47(prefix, wine)   File "/home/bimo/.local/lib/python3.9/site-packages/truckersmp_cli/utils.py", line 68, in activate_native_d3dcompiler_47     subproc.call(   File "/usr/lib64/python3.9/subprocess.py", line 349, in call     with Popen(*popenargs, **kwargs) as p:   File "/usr/lib64/python3.9/subprocess.py", line 951, in __init__     self._execute_child(args, executable, preexec_fn, close_fds,   File "/usr/lib64/python3.9/subprocess.py", line 1821, in _execute_child     raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: '/home/bimo/.steam/root/compatibilitytools.d/proton_tkg_6.8.r15.gf308782d/dist/bin/wine'
But this can fixed by changing
 wine = os.path.join(Args.protondir, "dist/bin/wine") to   wine = os.path.join(Args.protondir, "files/bin/wine")
on main.py
maybe this need an switcher, but i cant find the code for that.
also maybe you can add env WINEFSYNC=1 by default.
Thanks

Finally, Thanks a lot


fix: add link to new fastify website repository on organisations page

Checklist

[x] run npm run test and npm run benchmark
[x] tests and/or benchmarks are included
[x] documentation is changed or added
[x] commit message and code follows the Developer's Certification of Origin
and the Code of conduct

@HassanBahati could you revert the changes to the *.json files so we can land it?

yah sure, let me do so


Remove extra word 'the' from Trade secrets section

Removed extra word 'the' in Trade secrets paragraph under the the guide, "The Legal Side of Open Source".

Thank you @kylejusticemagnuson!


Upload of an empty file fails

There is a zero division error when calculating progress; but even with that taken care of, there is some issue with multi-part-uploading an empty file.
This old discussion might be of use: https://github.com/kr/s3/issues/30

Hi @bosonogi Thanks for heads-up on the client side we will fix it for the next version for s3 related discussion I will have to check it out and get back to you later.

@bosonogi
We will completely forbid uploading of files with size = 0.

Fixed in 0.7.0

Yes, we have this on the backlog now and we will allow uploading of empty files, although I can't give a timeline just yet.


documents aint detailed enough

http://www.chartjs.org/docs/latest/
lack of examples & code

Did you even bother to look any further than your nose long is:
http://www.chartjs.org/samples/latest/

Samples code & preview, unfortunately we don't have time to add more snippets directly in the documentation so feel free to submit a PR with what you think is missing.

OK , whatever, the sample is awesome , it's better to have more detailed explaination on apis , thx anyway


Move JS Engine classes

Sonar seems to not like the FrankJ2V8LibraryLoader which is a direct copy of the J2V8LibraryLoader with some minor bugfixes.


Update contributing

Towards #4  CONTIRBUTING.md updated to reflect CNCF template

@slashben before approving, please note that I have two open comments in the CONTRIBUTING.md commit that need to be addressed

@slashben completed the requested changes. Ready to merge if you don't see any additional problems.

@matthyx @rotemamsa I guess I need your approvals too to merge.


If "project type" didn't appear, install extension

@Stiles-X : Thanks for your contribution! The author(s) have been notified to review your proposed change.

any progress?

Hey, @ktoliver , can you accept my changes? Then I can sign off.
Thanks!

Hi, @Stiles-X -- your change is in progress. Thanks!

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hey, @ktoliver, can you accept my changes? Then I can sign off.
Thanks!

@maggiesMSFT Done.

#sign-off

Thanks!

Thanks!


Actually enable the webpack global for JASMINE

Just setting process.env.JASMINE isn't enough, webpack needs
to translate it into a global at compile-time.

Coverage remained the same at 87.48% when pulling caa6464094ec8004c308c31edf8355698ab939ef on job13er:actually-enable-jasmine-env into 49b5110aa659bca6123545b4ccaf9e3fe93920cd on cyaninc:master.

@psbanka Self-merging


Increment version for core releases

Increment package version after release of Azure.Core.Experimental

Looks like auto-merge didn't kick in.   Since this was previously approved by the SDK owner, merging.


Update YAMLS

Turns off progress_bar by default to improve UX when using MCLOUD
Update llm/mcloud examples to new format

Reverted the mcloud/ folder as it should not actually be changed until we have a new stable pin, and then those examples should point at the stable pin.


Release automation

This will be triggered whenever a tag starting with "v" is pushed. You will need to generate a PyPI API token and add it as a secret.
I suggest creating a beta tag like "v0.0.5-beta" to test this.
Depends on #10.
Closes #8.

This looks great! I'm currently having difficulties to login to pypi but I will merge this as soon as this gets resolved.

It worked without a hitch!
Many thanks for this!


Merge from upstream

First-time contributors' checklist

[ ] I've signed Contributor License Agreement that's required for repo owners to accept my contribution.

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

[ ] master (the latest development version)
[ ] v5.1 (TiDB 5.1 versions)
[ ] v5.0 (TiDB 5.0 versions)
[ ] v4.0 (TiDB 4.0 versions)
[ ] v3.1 (TiDB 3.1 versions)
[ ] v3.0 (TiDB 3.0 versions)
[ ] v2.1 (TiDB 2.1 versions)

What is the related PR or file link(s)?

This PR is translated from:
Other reference link(s):

Do your changes match any of the following descriptions?

[ ] Delete files
[ ] Change aliases
[ ] Need modification after applied to another branch
[ ] Might cause conflicts after applied to another branch

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 46 committers have signed the CLA.:x: 3pointer:x: ti-chi-bot:x: lance6716:x: chenmin1992:x: fengou1:x: WPH95:x: qiancai:x: en-jin19:x: asddongmen:x: Joyinqin:x: YuJuncen:x: knull-cn:x: 3AceShowHand:x: amyangfei:x: hey-hoho:x: yiwu-arbug:x: ran-huang:x: fgksgf:x: disksing:x: AstroProfundis:x: liuzix:x: TomShawn:x: jackysp:x: LittleFall:x: Liuxiaozhen12:x: NingLin-P:x: glkappe:x: glorv:x: ClSlaid:x: breeswish:x: hfxsd:x: leiysky:x: YiniXu9506:x: windtalker:x: shhdgit:x: jianzhiyao:x: hanfei1991:x: hunterlxt:x: overvenus:x: HunDunDM:x: wzru:x: Reminiscent:x: Connor1996:x: qw4990:x: gozssky:x: YisaerYou have signed the CLA already but the status is still pending? Let us recheck it.


Per-app windows

It would be nice if scrcpy could open multiple windows, for different apps on the phone, and automatically switch between them as needed.
For example, one could have a Twitter window, and when that window gets focus, open the Twitter app on the phone; and at the same time, a Conversations window which switches to Conversations (bonus if there's a way to put each individual conversation in its own window and handle XDG notifications nicely)
To avoid showing the wrong content in other windows, scrcpy could "dim" the last-seen contents and cease updating that window until it is open on the phone again.

https://github.com/Genymobile/scrcpy/issues/1887?


Localization (pt-BR) + fix date validation + interface and visual fixes + other general fixes

I also tested the "Copy from" feature to avoid regressions, but I think we will have to do some work there, because it's deleting the trophies already got and, it is also setting datetime to already synchronized trophies. Also setting datetime lower than the last synchronized trophy.

Forgot to mention that I added some texts to strings.zh-Hant.resx, to remove the texts from the middle of code and let it "language independent", but I don't know if the texts are right (I just used google transation to put text in there). Could you please check if they are right? Thanks.

I'll update localization file later. Thank you for your contribution.


add FAQ entry for compromised passwords

@di or @brainwane any input on the copy in the FAQ entry here?


update draft: no restricted records after grace period

closes https://github.com/inveniosoftware/product-rdm/issues/178

Actually this is not anymore needed as we override the update_draft method in invenio-rdm-records


[bug] coverage no longer report in terminal

Describe the bug
not printing test report results table in the console.
test-runner 0.13.0 results print to terminal as expected
test-runner 0.13.1-next.2 results do not print to terminal
test-runner 0.16.0 results do not print to terminal
To Reproduce
install relevant test runner and run against a sample test
npm test-storybook --coverage
Expected behavior
should print coverage results to terminal
Additional context
noticed when upgrade all storybook packages 7.4.6 > 7.6.3
installing backward test-runner releases issue seems to have been introduced at 0.13.1-next.2

Same observation on my project.
It look like it is a regression of a fix in the v0.12. corrected by @yannbf in https://github.com/storybookjs/test-runner/issues/332

I also had storybook-test runner 0.16 and got no coverage report in output.
Uninstalled and installed 0.13 and now to get coverage report in output.
With 0.16, the following command(s) will generate an output to terminal:
test-storybook --coverage && nyc report --reporter=text -t coverage/storybook --report-dir .storybook

Hey everyone! This is now fixed in version 0.18.0, sorry for the inconvenience and thanks for your patience!


Navigation for the site

Top Nav:
Vulnerabilities
Developers
Filepaths (Code)
Commits (doesn't need to be on top nav)
Releases
Tags
Top left link would be breadcrumb from project dropdown to select case studies
Vulnerability History can change to "Home" or home icon
dropdown has chevron
Icons along top
API, about our project, contacts, github, good for footer

Make sure it's mobile friendly

Look at routes for URLs


Establish an initial SLA for "free deployments"

This is satisfied via agreement B detailed here: https://github.com/polywrap/monorepo/issues/742

Requesting review: @nerfZael

Closing this as it has been covered in #742


Enhance Model with MarkupString Options

This pull request will give an additional option to pass MarkString to the modal.

I'll re-create when i have a more elegent solution


Migrations changing VARCHAR to UNSIGNED BIGINT yields syntax error

Laravel Version
10.15.0
PHP Version
8.1.20
Database Driver & Version
MySQL 8.0.21
Description
I have a column in my database that was created as a VARCHAR years ago for holding foreign key ids when it should have been an unsigned BIGINT. I have a migration to change the column type correctly, however, when I try running the migration I keep getting a syntax error on the query that Laravel is generating for the change.
Error:
SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'NOT NULL, CHANGE part_id part_id BIGINT UNSIGNED DEFAULT 0 NOT NULL' at line 1 (Connection: netsuite, SQL: ALTER TABLE table_name CHANGE category category BIGINT UNSIGNED DEFAULT  NOT NULL, CHANGE part_id part_id BIGINT UNSIGNED DEFAULT 0 NOT NULL)
After inspecting the error a little further I noticed that the default value on the category column change was nothing instead of 0 which was likely the error. Adding an explicit default definition within the migration seemed to fix the issue, but my guess is this shouldn't be required as any other column changes (i.e. int => bigint) implicitly sets the default to 0. What appears to be happening behind the scenes is that this column in it's original non nullable VARCHAR state has a default of empty string ('') which is either being used as the default when changing to a BIGINT or is not being converted from a string to an integer properly. This is just my best guess based on observations of my database and the resulting query that gets generated for this migration, not based on the code itself which I'm still looking through.
Based on previously reported bugs it seems this is an issue with how Laravel is delivering the packaged data to doctrine/dbal which is why I'm posting this bug here.
Current version of doctrine/dbal: 3.6.4
Bad Migration:
Schema::table('table_name', function (Blueprint $table) {             $table->unsignedBigInteger('category')->change();             $table->unsignedBigInteger('part_id')->change();  });
Good Migration:
Schema::table('table_name', function (Blueprint $table) {             $table->unsignedBigInteger('category')->default(0)->change();             $table->unsignedBigInteger('part_id')->change();  });
Steps To Reproduce
Schema::table('table_name', function (Blueprint $table) {             $table->string('column_name');  });
Schema::table('table_name', function (Blueprint $table) {             $table->unsignedBigInteger('column_name')->change();  });

I'm not sure what you expect here? The default is needed. We don't set that for you.

If a column definition is provided without a default and is not nullable I'd expect a default to be implicitly provided matching datatypes. Currently when creating a new column of lets say type BIGINT I don't need to explicitly provide a default if I want the default to be 0. If this is something not being done by Laravel, perhaps it's MySQL setting that


Revert "Add course info and eval links to course popovers"

Reverts TigerPathApp/tigerpath#261

Fixed in #268


Prometheus from catalog don't create pods

Rancher Version:
1.2.2
OS and where are the hosts located? (cloud, bare metal, etc):
AWS, rancherOS
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
HA rancher 3 nodes external DB
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Kubernetes 1.5.1
Steps to Reproduce:
Launch Prometheus stack
Results:
No pods scheduled
Expected:
Launch all pods and services.  (for example MongoDB stack launched ok and is working)
Prometheus stack looks like this when launched from catalog:

any advice on how to troubleshoot this or similar situation, appreciated :)   (I'm new to Rancher)

seems like not a Prometheus issue, "Cloud9" stack behaves the same...

I have enough worker nodes online to host all those stacks.. what might be the reason for them to not even attempt to create their pods?  just lays there with "0" pods... totally weird


[BUG] Feroxbuster doesn't give an option to change Scan Limit using Scan Management Menu

Describe the bug
Once application is launched there is no way to modify Scan Limit using Scan Management Menu.

Agreed, this would be a nice addition! I'd happily help someone work through a PR to make this happen. Thanks for taking the time to submit this!


notification: fix cleaners infinite loop.

The variable holding the next starting id was defined inside the loop instead than outside.
Improve tests to trigger multiple loops

Nice! I ran it locally and it fixes #486 🚢


Instant removal of older messages, not even on the server yet

Describe the bug
I am setting up this bot on a community server in a preset channel. My question is: Why is this bot instantly removing ALL old messages? We use this channel for multiple purposes and I do not want it to remove any messages but it's own. The moment I start the docker, it instantly goes and removes things. This happens with just the Guild ID and a music channel ID
To Reproduce
Steps to reproduce the behavior:

Make sure the bot is NOT on the server
Use the premade docker setup
Fill out all env settings, thus include a Guild ID and Music channel ID
Use a Music Channel ID that has messages in it

Expected behavior
Nothing should happen, the bot isn't even on the server yet. Also it should not instantly start removing messages

tbh it shouldn't remove things, but its probally because of the link scanning thing


[Doc] Update CDC connector guide

Fix https://github.com/apache/pulsar/issues/5015#event-2577499721

LGTM

run java8 tests


x/pkgsite: ./all.bash should attempt to run postgres tests by default

Follow up to #39598:
When running ./all.bash, it's not clear whether the postgres tests are running or not. Users will just see that tests succeeded, even when the change results in postgres failures. For example, here's./all.bash output on the same patchset:
./all.bash output with postgres setup:
https://gist.github.com/julieqiu/c279934ee6054e7d5900274569c5c0d2
./all.bash output without postgres setup:
https://gist.github.com/bharaththiruveedula/dcfb9770fe99b3ecb8ee7891d8343631
I think we should do the following:

Run all tests by default
Provide users with an option to skip postgres tests
When running ./all.bash, first check if we can connect to the test databases, before running tests. If not, exit and inform users about the option to bypass postgres tests.

/cc @jba @mvdan @bharaththiruveedula

Hmm, I'm not sure if I agree. This would once again break go test ./... on a clean clone.
It's true that some test successes are different from others, but that will generally be true for many other reasons. Some tests will require specific programs to be installed, or they might require Linux or Windows to run. Should all of those also fail unless they're actually running properly?
I think you should go the other way around. In all.bash, also run by CI, you could ensure that none of the portable tests are being skipped. You could do this with something like:
NO_DB_SKIP=true go test ./...

and in the Go code to handle the case where the DB isn't available:
if noDB {
    if os.Getenv("NO_DB_SKIP") != "true" {
        t.Fatal("some error")
    }
    t.Skip("skipping")
}

That way, you have the best of both worlds. It's possible for "run all the tests properly" to be done, and you're not messing with people who just want to run the tests on a best-effort basis.
A slight variant is what @bcmills suggested in the original issue, which is to make each TestMain start up a temporary postgres on-demand, and only do the skip-or-error dance when postgres isn't installed, which is less likely to be true than "postgres isn't running".

Ah nice, thanks! I like the NO_DB_SKIP suggestion 👍


[AMBARI-23332] Recommend SSO configuration values for ATLAS and RANGER in the stack advisor

What changes were proposed in this pull request?
Recommend SSO configuration values for ATLAS in the stack advisor
The following values in application-properties need to be set:

atlas.sso.knox.enabled
-- SSO enabled (true) or disabled (false)

atlas.sso.knox.providerurl
-- SSO provider url. Example: https://KNOX_HOST:KNOX_PORT/gateway/TOPOLOGY_NAME/knoxsso/api/v1/websso

atlas.sso.knox.publicKey
-- SSO provider public key. The base64-encoded x509 Public key data (without the certificate header and footer) used for SSO provider cookie verification

atlas.sso.knox.providerurl
-- SSO browser useragents (comma-delimted).  Default: Mozilla,chrome

Also, update the Atlas metainfo.xml file to indicate it supports SSO configuration by Ambari
Recommend SSO configuration values for RANGER in the stack advisor
The following values in ranger-admin-site need to be set:

ranger.sso.enabled
-- SSO enabled (true) or disabled (false)

ranger.sso.providerurl
-- SSO provider url. Example: https://KNOX_HOST:KNOX_PORT/gateway/TOPOLOGY_NAME/knoxsso/api/v1/websso

ranger.sso.publicKey
-- SSO provider public key. The base64-encoded x509 Public key data (without the certificate header and footer) used for SSO provider cookie verification

ranger.sso.cookiename
-- SSO cookie name

ranger.sso.query.param.originalurl
-- Query name for appending original url in SSO url

ranger.sso.browser.useragent
-- SSO browser useragents (comma-delimted).  Default: Mozilla,chrome

Also, update the Ranger metainfo.xml file to indicate it supports SSO configuration by Ambari
How was this patch tested?
Manually tested in the following clusters:

Ambari 2.7.0/HDP 2.6
Ambari 2.7.0 (upgraded from Ambari 2.6.1)/HDP 2.6

Unit tests:
mvn -pl ambari-server -DskipSurefireTests test
...
Total run:1184
Total errors:0
Total failures:0
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:51 min
[INFO] Finished at: 2018-03-29T12:47:58-04:00
[INFO] Final Memory: 91M/1078M
[INFO] ------------------------------------------------------------------------

Please review Ambari Contributing Guide before opening a pull request.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1513/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1532/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1538/
Test PASSed.


Screenshots not visible in readme file

There is an issue with screenshots at readme file as they are shown as markdown language not an image.

If correct location for wanted images exists, or you do not need this section anymore I can update or delete it from readme file.

If there is a correct location for wanted images, or you do not need this section anymore I can update or delete it from readme file.

You can go and check our website over here imgman.herokuapp.com Upload some image, manipulate it and paste the original image along with manipulated images

Hi, I'm Tejas. I would like to add few screenshots of the website. Below are the some screenshots I have taken.
If it's useful then I will create a PR.

@Tejas124  Someone is already working on this issue! You may raise some other issues

Okay 👍🏻


Significant changes/updates have been made to the custom accordions f…

…or HTML and CSS validation. Also, the main header images on select pages were changed from background images to foreground images with alt tags. Other changes have been added, as well.

Reynolds SBIT Change Log
January 4, 2022
Listed below are the most recent changes to the Reynolds SBIT Website as of January 4, 2022.

All Program/Category and Career Outlook pages now pass HTML and CSS validation without error. All pages turn up green with no yellow or red flags.

Added back the Bootstrap  tags to the Bootstrap accordions for HTML validation for the accordions that were failing validation; because these tag’s IDs were considered missing. See below.
 <h2 class="accordion-header" id="panelsStayOpen-headingTwo">

With respect to this, the IDs in these tags were referenced by the aria-labellby reference, as shown below; therefore, these ID’s need to be put back if their aria reference connections were going to be kept.
    aria-labelledby="panelsStayOpen-headingTwo">

Changed all the main header images from background images to foreground images with their appropriate ALT tags. Relative to this, changes were made to the CSS positioning declarations for each image; so, instead of background positioning declarations, there’re now foreground declarations for each image (ex. object-position: 50% 50%;), as needed.

Made significant changes to the custom accordions on the Program/Category pages for proper HTML validation and for more efficient functioning.

a. Changed all tags () within the  elements to  tags to pass HTML validation, as shown below.

DSL 160
Air Brake Systems
Credit Hours: 3

b. Added the  as a container/wrapper for the . This was needed to help with the proper text alignment of the course headings in the custom accordions within Safari on the Mac. It’s interesting to note that this custom accordion functioned well without this extra container/wrapper in Chrome and Firefox on the Mac; but not in Safari; hence, its addition.
c. Added bolding or  tags to leading, text headings within all the accordions for both Bootstrap and custom accordions, as needed. (ex. PURPOSE:, OCCUPATIONAL OBJECTIVES:, Lecture Hours: Semester(s) Offered: and etc. all were bolded).
d. Added CSS transforms and transitions to the open/close arrows for the course listings in the custom accordions. These arrows now turn 180º counterclockwise to open and then reverse clockwise 180º to close per user interaction. Also, these arrows now fade up from lt. gray to fully black as they rotate to open and then fade back from black to lt. gray to close via CSS transitions; however, this is barely noticeable; since, they all rotate at 0.2s; but still, a nice touch to include.
e. The custom accordion arrows now consistently align with the “Credit Hours: X” line-items for both desktop and tablet views as the layouts are resized responsively; however, in the mobile views (550px and lower) these arrows then center vertically between the height of the course heading line-items of text and are positioned on the far right as in the other views.
This was done on purpose and by design. When the “Credit Hours: X” line-item is at the far right, as in the tablet and desktop views, it queues the audience that an arrow should be aligned with it rather than half-way between it and another line of text when the course headings responsively shrink to two or more lines of text. When these arrows moved to the vertical center in these views, as in the previous iterations, this created a misbalance and the notion that the arrows were out of place and weren’t properly connected with their correct line-items.
Conversely, in the mobile views, when all of the line-item text is stacked flush left, having the arrows at the far right and in the center makes the most sense visually as far as visual balance is concerned and the proper queuing of one’s audience. Also, these arrows could exist at the top, across from the course number listings as well; but vertical center alignment has been chosen; because, when these items are selected, they become surrounded by a gray box rather than being completely unbounded by anything. This seems to be the most logical choice for these, at the moment.
f. In the Automotive courses, for the electives, the words, “ Course content to come.” were added to the descriptions. Also, wherever the words “Elective” were shown in all caps, they were lowercase into sentence case and wherever the words, “OR” were shown in a regular font face, they were bolded for consistency with the other program page layouts. This adjustment wasn’t needed in many places.

Bootstrap accordion changes:

a. Added the proper course titles to each major where needed. There’re no longer any generic headings for these.
b. Added the sentence: “To help with course planning, download curriculum planning Roadmap.” where needed to each major to make roadmap access available individually for each major. This sentence was added to the first paragraph under the “Curriculum” headings.
c. Added and linked up all the outstanding roadmaps for download for as many roadmaps that were available, which means about all, but one or two roadmaps are available to the user now. These were added to the “Download Curriculum Roadmaps” dropdown buttons and individually to each major in the first paragraph under each of the “Curriculum” headings and linked to the word “Roadmaps”.

Updated the program-scripts.js file with minor syntactical changes for JSLint code validation. Also, removed the cat-scripts.js file and any references to it in all of the Program/Category and Career Outlook page’s HTML files due to the fact that it’s essentially an exact duplicate of the program-scripts.js file.

Made minor image and name change with the automotive main head image file. Also, removed some unused images from the image’s folder.


Kaz Wolfe: Blacklist neptuneutilities.com

Kaz Wolfe requests the blacklist of the website neptuneutilities.com. See the Metasmoke search here

I only see a single hit in Metasmoke, which is not yet enough according to our blacklisting guidelines.

I am going to close this and add the site to the watchlist instead.


Create image at once with frotend and backend in it.

Feature request
Dir structure:
Common-----|
            Frontend
            Backend

Run
nixpacks plan Common - detect Frontend and Backend configuration for the image.
nixpacks build Common - build an image with Frontend and Backend.
Motivation
No response
Contribution
No response

That is sort of possible currently. You could build both the front and backends during the build phase and then start them both with a process manager like pm2. However, automatically detecting that is not the intended use of Nixpacks and it is recommended that each running container only does a single thing.
If your backend serves your frontend (e.g. rails/nextjs), then this is a different story.


legion: slow startup at 96 nodes with shardrefine

I've started scaling shardrefine on perlmutter and I see slow startup at 96 nodes. Things look ok before that, but at 96 nodes the start up time seems to take more than 10x. I ran it multiple times.
http://sapling2.stanford.edu/~seshu/s3d_perlmutter_subrank/startup_legion_prof.html
Profiles are available here: http://sapling2.stanford.edu/~seshu/s3d_perlmutter_subrank/

Did you run this in debug or release mode?
Did you get any warnings from the profiler about lots of long-latency messages?
Is there a way for me to run the 12-process version on sapling?

Can I get a profile for the 6 process one showing all the nodes?

FWIW, it seems like there is some really bad weirdness occurring when the Hand Off to MPI task runs and then it looks like the OS puts all the processes to sleep for a growing amount of time. Literally all execution stops on all the nodes, and the amount of time that takes scales with the number of nodes.

This was RelWithDebInfo.
I did not get any warnings from the profiler, but I think maybe unless you generate a full profile it doesnt give those warnings anymore? Will have to ask @elliottslaughter.
I will see if the 6 process one runs on sapling on cpu.
There is a full profile from the 6 node run here: http://sapling2.stanford.edu/~seshu/s3d_perlmutter_subrank/pwave_x_6_hept/legion_prof_full/

I did not get any warnings from the profiler, but I think maybe unless you generate a full profile it doesnt give those warnings anymore?

Looking at the code, I believe the checks should be enabled all the time. I don't see any conditions for profiling a subset of nodes.

Ok, I see at least part of the problem (stupid tracing transitive reductions that take forever). I'd still like to have a 6-process test to run on sapling to play with to explore a couple of other things that look strange to me.

The case is setup on sapling, but I'm seeing a new crash with the latest shardrefine. I guess there were some changes today and the one I ran on perlmutter was from Saturday. I will open a separate issue for that.

How do I run the case on sapling?

Please rebuild with the latest shardrefine as I at least fixed one of the issues.

Did not see an improvement on perlmutter: http://sapling2.stanford.edu/~seshu/s3d_perlmutter_subrank/startup_legion_prof.html
New profiles are here: http://sapling2.stanford.edu/~seshu/s3d_perlmutter_subrank/
A full profile from 6 nodes is available as well: http://sapling2.stanford.edu/~seshu/s3d_perlmutter_subrank/pwave_x_6_hept/legion_prof_full/

These profiles are different. The Realm DMA channels are just getting completely swamped. The utility processors no longer look like the bottleneck. The copies were probably the limiter before, but it's even more obvious now that I fixed the most egregious overheads on the utility processors. FWIW, the reason the utility processors look a bit slow at times is because Realm is so swamped with data movement.

I guess this is less of a problem on the 48 and 96 node runs, something else is going on there.

I would still like a way to run the 6-node version on sapling.

Please regenerate the 96-node profile with the latest shardrefine as it has more detailed information about the messages being sent in the profiler.

A new profile is available here: http://sapling2.stanford.edu/~seshu/s3d_perlmutter_subrank/pwave_x_96_hept/legion_prof/

If you want to run the 6 rank case on sapling you can do so now.
salloc -N 1 -p cpu --exclusive
cd /scratch2/seshu/legion_s3d_subranks/Ammonia_Cases
./ammonia_job.sh

Can you try making your projection functions pure functional ones so that Legion can memoize the projection trees that it has to make? It looks like we're doing a ton of redundant communication because Legion can't memoize projection function results. There is an inherent all-gather operation that Legion has to do every time it sees a projection functor invoked from a new region/partition for the first time. The data structure we create out of this all-gather is scalable (it's size is independent of the size of the number of regions used in the projection), but the amount of data exchanged in the all-gather is not really scalable (it grows with the number of subregions used in the projection). If we can memoize the result then we don't have to do it every time like we do right now in this application. If we can't mark the projection functions as being memoizable then I think we're going to need to just fall back to a super pessimistic logical analysis that just assumes that anything that interferes on the roots of the projection interfere in their sub-region usage as well which is going to necessitate merge close op fences all over the place.

I'm not sure we documented this decision, but we need the interface you suggested in https://github.com/StanfordLegion/legion/issues/1410#issuecomment-1459932407. The reason why the Regent projection functors aren't functional via the current interface is described in https://github.com/StanfordLegion/legion/issues/1410#issuecomment-1452651565.

I'm not sure we documented this decision, but we need the interface you suggested in https://github.com/StanfordLegion/legion/issues/1410#issuecomment-1459932407.

The current implementation in shardrefine takes into account memoizing the "state data" passed in on the region requirement, so if that is all you are accessing then you can safely mark the projection functor as "pure functional" and allow Legion to memoize the result.

If that is the only problem, then I suppose we can add a new project method and give you a mechanism to say in the projection functor which interface gets called. What should the project method look like?
class ProjectionFunctor {
 ...
  virtual LogicalRegion project(LogicalRegion upper bound, const DomainPoint &point, const Domain &launch_domain, const void *args, size_t arglen);
  virtual LogicalRegion project(LogicalPartition upper_bound, const DomainPoint &point, const Domain &launch_domain, const void *args, size_t arglen);

Alternatively, we can not add a new interface, I give you a way to just promise that the result is functional on those parameters and trust that you're doing the right thing even though we're calling the older interface.

That interface is fine with me.
I seem to recall you also wanted to deprecate and remove the old non-functional interface. But that is not important to me.

Here is the new interface:
https://gitlab.com/StanfordLegion/legion/-/commit/9dbebae824e3eefa65ee6921e4969d017eec9f62
It will automatically use the new methods if you mark the projection functor as pure functional and you region requirement has projection arguments. Unfortunately there is no way to back-port this before shardrefine. The machinery is just not there in the runtime to support it.

Does this C API look ok?
https://gitlab.com/StanfordLegion/legion/-/commit/8c0c088affa6e661c881cad63df1fc1a55d4d24a

Actually, I keep needing to make fixes, so let's do this via MR: https://gitlab.com/StanfordLegion/legion/-/merge_requests/925

Ok, that MR now has Regent support too, though it's crashing at runtime. Either (a) I failed to correctly register the right kind of projection functor, or (b) the runtime is not calling the correct method.

Something about the projection functor arguments didn't make sense to me. They are supposed to be dynamic in the sense that each new task launch might annotate new arguments on each of its region requirements. Legion is memoizing over the binary value of those arguments. Therefore they shouldn't be member variables on the functor object, but instead something that gets passed through to the project function call.
I do see the CI failing, but I don't know how to interpret the assertion.

That's just how we wrap the C++ API to offer the C API. The members are the pointers to the C API function pointers that are the true projection functors. This is not new, it's how we've always done projection functors in C.
I haven't dug into debugging yet, but glancing through the code I don't see an obvious mismatch on my side. One way or another, it appears that the wrong projection functor method is getting called.

This is my issue. I'll follow up with a fix.

Test pass locally. Feel free to review the MR again. All my changes were inside of the compiler.

Looks good to me, merge when ready. Then we can get @syamajala to try again with the updated Regent code.

Merged to shardrefine. @syamajala please try it out and see what you get.

Runs are in the queue. Some of them have gone through and it at least looks like it runs without crashing.

Nothing past 12 nodes seemed to work correctly. 24 and 48 nodes got stuck after 10 timesteps, 96 nodes never finished the first timestep. I submitted some runs again.

Run with -ll:force_kthreads and dump back traces from all nodes when they
hang.
On Fri, Sep 15, 2023, 7:10 AM Seshu Yamajala @.***>
wrote:

Nothing past 12 nodes seemed to work correctly. 24 and 48 nodes got stuck
after 10 timesteps, 96 nodes never finished the first timestep. I submitted
some runs again.
—
Reply to this email directly, view it on GitHub
https://github.com/StanfordLegion/legion/issues/1539#issuecomment-1721347708,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACHBH7SCT55AA2D6RGIETADX2ROWPANCNFSM6AAAAAA4B6SBS4
.
You are receiving this because you commented.Message ID:
@.***>

Its on Perlmutter, which is slingshot-11. I'm running with Realm flow control on top of shardrefine.

The runs I resubmitted worked through 48 nodes, but 96 doesnt start up after half an hour. Will have to see if I can get stack traces.

I have stacktraces from a 96 node job here: http://sapling2.stanford.edu/~seshu/s3d_perlmutter_subrank/stacktraces/
I took them at 4 different points over the course of half an hour.

There's definitely something strange going on. At least between the last two sets of backtraces nothing changed so it is properly stuck and things are not just running slowly. I didn't check the early backtraces.
Every node has a non-trivial backtrace with at least one thread stuck in the logical dependence analysis waiting on messages from remote nodes. Different nodes have varying number of outstanding operations stuck in the prepipeline stage also waiting on messages from remote nodes. This looks to me like the network is getting stuck like before. Do you want to go through the trouble of confirming that messages are getting stuck?

Its clear that this is a network issue. I ran without Realm flow control and just set the libfabric environment variables and it started up. Maybe thats fine for now though. Running rank/node uses significantly less memory so we can sort of afford to let libfabric go wild.
Long term though, Slingshot 2.1 should be starting to get rolled out to machines soon, and from the initial tests we've heard from the gasnet guys and OLCF it seems to be working. I don't know when it will become available on Perlmutter though, but Frontier should be getting it any day.

Slingshot 2.1 did fix these issues. See #1581.