Inconsistent Metadata errors

Describe the bug
I get this when starting my dev server
✘ [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/vue/dist/vue.runtime.esm-bundler.js" when it was imported here:

    node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187:
      6 │ ...eactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';
        ╵                                                                 ~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:vue:2:14:
      2 │ export * from "./node_modules/vue/dist/vue.runtime.esm-bundler.js"
        ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The difference in metadata is displayed below:

   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }

  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an "onResolve" callback. All metadata provided for the same path must be consistent to ensure deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for a given path, so providing inconsistent metadata for the same path can cause non-determinism.

Possible duplicate of https://github.com/vitejs/vite/issues/7683
Reproduction
https://stackblitz.com/edit/vitejs-vite-f48pac?file=package.json
System Info
System:
    OS: macOS 12.0.1
    CPU: (8) arm64 Apple M1
    Memory: 95.61 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.volta/tools/image/node/16.13.1/bin/node
    Yarn: 1.22.17 - ~/.volta/tools/image/yarn/1.22.17/bin/yarn
    npm: 8.6.0 - ~/.volta/tools/image/npm/8.6.0/bin/npm
  Browsers:
    Chrome: 100.0.4896.75
    Safari: 15.1
  npmPackages:
    @vitejs/plugin-vue: ^2.3.1 => 2.3.1
    vite: ^2.9.1 => 2.9.1

Used Package Manager
yarn
Logs
vite:resolve 0.31ms @vue/runtime-dom -><EMAIL_ADDRESS>+0ms
  vite:resolve 0.41ms vue -> /Users/k/fume/tailvue/node_modules/vue/dist/vue.runtime.esm-bundler.js +3ms
✘ [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/vue/dist/vue.runtime.esm-bundler.js" when it was imported here:

    node_modules/@iconify/vue/dist/iconify.mjs:1:35:
      1 │ import { h, defineComponent } from 'vue';
        ╵                                    ~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:vue:2:14:
      2 │ export * from "../node_modules/vue/dist/vue.runtime.esm-bundler.js"
        ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The difference in metadata is displayed below:

   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }

  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
  "onResolve" callback. All metadata provided for the same path must be consistent to ensure
  deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
  a given path, so providing inconsistent metadata for the same path can cause non-determinism.

  vite:resolve 0.33ms @vue/runtime-core -><EMAIL_ADDRESS>+1ms
  vite:resolve 0.27ms @vue/shared -><EMAIL_ADDRESS>+0ms
  vite:resolve 0.39ms @vue/reactivity -><EMAIL_ADDRESS>+10ms
11:03:58 PM [vite] error while updating dependencies:
Error: Build failed with 1 error:

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Happens with React JS and React TS as well

was just going to file an issue
><EMAIL_ADDRESS>dev
> vite

  vite v2.9.1 dev server running at:

  > Local: http://localhost:3000/
  > Network: use `--host` to expose

  ready in 234ms.

X [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:

    node_modules/react/cjs/react-jsx-dev-runtime.development.js:16:20:
      16 │ var React = require('react');
         ╵                     ~~~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:react:1:23:
      1 │ export default require("./node_modules/react/index.js");
        ╵                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The difference in metadata is displayed below:

   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }

  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
  "onResolve" callback. All metadata provided for the same path must be consistent to ensure
  deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
  a given path, so providing inconsistent metadata for the same path can cause non-determinism.

X [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:

    node_modules/react-dom/cjs/react-dom.development.js:16:20:
      16 │ var React = require('react');
         ╵                     ~~~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:react:1:23:
      1 │ export default require("./node_modules/react/index.js");
        ╵                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The difference in metadata is displayed below:

   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }

  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
  "onResolve" callback. All metadata provided for the same path must be consistent to ensure
  deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
  a given path, so providing inconsistent metadata for the same path can cause non-determinism.

9:11:00 PM [vite] error while updating dependencies:
Error: Build failed with 2 errors:
node_modules/react-dom/cjs/react-dom.development.js:16:20: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:
node_modules/react/cjs/react-jsx-dev-runtime.development.js:16:20: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/react/index.js" when it was imported here:
    at failureErrorWithLog (C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:1603:15)
    at C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:1249:28
    at runOnEndCallbacks (C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:1034:63)
    at buildResponseToResult (C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:1247:7)
    at C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:1356:14
    at C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:666:9
    at handleIncomingPacket (C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:763:9)
    at Socket.readFromStdout (C:\Users\gasma\Desktop\projects\test-vite\node_modules\esbuild\lib\main.js:632:7)
    at Socket.emit (node:events:390:28)
    at addChunk (node:internal/streams/readable:315:12)

Happens with VUE JS and React TS as well
`
node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187:
6 │ ...t, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';
╵                                                                                ~~~~~
The original metadata for that path comes from when it was imported here:
dep:vue:2:14:
  2 │ export * from<EMAIL_ADDRESS>    ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The difference in metadata is displayed below:
{

"pluginName": null,

"pluginName": "vite:dep-pre-bundle",
}

This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
"onResolve" callback. All metadata provided for the same path must be consistent to ensure
deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
a given path, so providing inconsistent metadata for the same path can cause non-determinism.
下午12:21:14 [vite] error while updating dependencies:
Error: Build failed with 1 error:
node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path<EMAIL_ADDRESS>when it was imported here:
at failureErrorWithLog (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1603:15)
at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1249:28
at runOnEndCallbacks (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1034:63)
at buildResponseToResult (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1247:7)
at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1356:14
at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:666:9
at handleIncomingPacket (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:763:9)
at Socket.readFromStdout (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:632:7)
at Socket.emit (node:events:390:28)
at addChunk (node:internal/streams/readable:315:12)
Vite Error, /node_modules/.vite/deps/vue-router.js?v=18f23ae8 optimized info should be defined
X [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path<EMAIL_ADDRESS>when it was imported here:
node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187:
  6 │ ...t, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';
    ╵                                                                                ~~~~~

The original metadata for that path comes from when it was imported here:
dep:vue:2:14:
  2 │ export * from<EMAIL_ADDRESS>    ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The difference in metadata is displayed below:
{

"pluginName": null,

"pluginName": "vite:dep-pre-bundle",
}

This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
"onResolve" callback. All metadata provided for the same path must be consistent to ensure
deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
a given path, so providing inconsistent metadata for the same path can cause non-determinism.
下午12:21:19 [vite] error while updating dependencies:
Error: Build failed with 1 error:
node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path<EMAIL_ADDRESS>when it was imported here:
at failureErrorWithLog (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1603:15)
at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1249:28
at runOnEndCallbacks (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1034:63)
at buildResponseToResult (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1247:7)
at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1356:14
at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:666:9
at handleIncomingPacket (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:763:9)
at Socket.readFromStdout (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:632:7)
at Socket.emit (node:events:390:28)
at addChunk (node:internal/streams/readable:315:12)
`

Happens with preact as well

Logs
❯ yarn dev
yarn run v1.22.17
$ vite

  vite v2.9.1 dev server running at:

  > Local: http://localhost:3000/
  > Network: use `--host` to expose

  ready in 389ms.

✘ [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/preact/dist/preact.module.js" when it was imported here:

    node_modules/preact/jsx-runtime/dist/jsxRuntime.module.js:1:38:
      1 │ import{options as r,Fragment as _}from"preact";export{Fragment}from"preact";var o=0;function e(_,e,n,t,f){var l,s,u={};for(s in e)"ref"==s?l=e[s]:u...
        ╵                                       ~~~~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:preact:2:14:
      2 │ export * from "./node_modules/preact/dist/preact.module.js"
        ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The difference in metadata is displayed below:

   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }

  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
  "onResolve" callback. All metadata provided for the same path must be consistent to ensure
  deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
  a given path, so providing inconsistent metadata for the same path can cause non-determinism.

✘ [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/preact/dist/preact.module.js" when it was imported here:

    node_modules/preact/jsx-runtime/dist/jsxRuntime.module.js:1:67:
      1 │ import{options as r,Fragment as _}from"preact";export{Fragment}from"preact";var o=0;function e(_,e,n,t,f){var l,s,u={};for(s in e)"ref"==s?l=e[s]:u...
        ╵                                                                    ~~~~~~~~

  The original metadata for that path comes from when it was imported here:

    dep:preact:2:14:
      2 │ export * from "./node_modules/preact/dist/preact.module.js"
        ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The difference in metadata is displayed below:

   {
  -  "pluginName": null,
  +  "pluginName": "vite:dep-pre-bundle",
   }

  This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an
  "onResolve" callback. All metadata provided for the same path must be consistent to ensure
  deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for
  a given path, so providing inconsistent metadata for the same path can cause non-determinism.

9:23:20 AM [vite] error while updating dependencies:
Error: Build failed with 2 errors:
node_modules/preact/jsx-runtime/dist/jsxRuntime.module.js:1:38: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/preact/dist/preact.module.js" when it was imported here:
node_modules/preact/jsx-runtime/dist/jsxRuntime.module.js:1:67: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path "node_modules/preact/dist/preact.module.js" when it was imported here:
    at failureErrorWithLog (/preact-project/node_modules/esbuild/lib/main.js:1603:15)
    at /preact-project/node_modules/esbuild/lib/main.js:1249:28
    at runOnEndCallbacks (/preact-project/node_modules/esbuild/lib/main.js:1034:63)
    at buildResponseToResult (/preact-project/node_modules/esbuild/lib/main.js:1247:7)
    at /preact-project/node_modules/esbuild/lib/main.js:1356:14
    at /preact-project/node_modules/esbuild/lib/main.js:666:9
    at handleIncomingPacket (/preact-project/node_modules/esbuild/lib/main.js:763:9)
    at Socket.readFromStdout (/preact-project/node_modules/esbuild/lib/main.js:632:7)
    at Socket.emit (node:events:390:28)
    at addChunk (node:internal/streams/readable:315:12)

i use another version in vue-router is result for me, in react sorry i dont know
i think, this error is in the vite compilation, i have another project with this version vue:

it works normally but when i create a new project it throws the error

i use another version in vue-router is result for me, in react sorry i dont know
i think, this error is in the vite compilation, i have another project with this version vue:

it works normally but when i create a new project it throws the error

you delete the node_modules,reinstall then try it

Happens with VUE JS as well ` node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187: 6 │ ...t, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue'; ╵ ~~~~~
The original metadata for that path comes from when it was imported here:
dep:vue:2:14:
  2 │ export * from<EMAIL_ADDRESS>    ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The difference in metadata is displayed below:
{
* "pluginName": null,

* "pluginName": "vite:dep-pre-bundle",
  }

This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an "onResolve" callback. All metadata provided for the same path must be consistent to ensure deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for a given path, so providing inconsistent metadata for the same path can cause non-determinism.
下午12:21:14 [vite] error while updating dependencies: Error: Build failed with 1 error: node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path<EMAIL_ADDRESS>when it was imported here: at failureErrorWithLog (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1603:15) at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1249:28 at runOnEndCallbacks (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1034:63) at buildResponseToResult (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1247:7) at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1356:14 at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:666:9 at handleIncomingPacket (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:763:9) at Socket.readFromStdout (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:632:7) at Socket.emit (node:events:390:28) at addChunk (node:internal/streams/readable:315:12) Vite Error, /node_modules/.vite/deps/vue-router.js?v=18f23ae8 optimized info should be defined X [ERROR] [plugin vite:dep-pre-bundle] Detected inconsistent metadata for the path<EMAIL_ADDRESS>when it was imported here:
node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187:
  6 │ ...t, onUnmounted, onDeactivated, onActivated, computed, unref, watchEffect, defineComponent, reactive, h, provide, ref, watch, shallowRef, nextTick } from 'vue';
    ╵                                                                                ~~~~~

The original metadata for that path comes from when it was imported here:
dep:vue:2:14:
  2 │ export * from<EMAIL_ADDRESS>    ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The difference in metadata is displayed below:
{
* "pluginName": null,

* "pluginName": "vite:dep-pre-bundle",
  }

This is a bug in the "vite:dep-pre-bundle" plugin. Plugins provide metadata for a given path in an "onResolve" callback. All metadata provided for the same path must be consistent to ensure deterministic builds. Due to parallelism, one set of provided metadata will be randomly chosen for a given path, so providing inconsistent metadata for the same path can cause non-determinism.
下午12:21:19 [vite] error while updating dependencies: Error: Build failed with 1 error: node_modules/.pnpm/vue-router@4.0.14_vue@3.2.31/node_modules/vue-router/dist/vue-router.esm-bundler.js:6:187: ERROR: [plugin: vite:dep-pre-bundle] Detected inconsistent metadata for the path<EMAIL_ADDRESS>when it was imported here: at failureErrorWithLog (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1603:15) at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1249:28 at runOnEndCallbacks (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1034:63) at buildResponseToResult (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1247:7) at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:1356:14 at E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:666:9 at handleIncomingPacket (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:763:9) at Socket.readFromStdout (E:\demo\2022\my-vue-app\node_modules.pnpm\esbuild@0.14.35\node_modules\esbuild\lib\main.js:632:7) at Socket.emit (node:events:390:28) at addChunk (node:internal/streams/readable:315:12) `

Same error here
Using vue3-latest
I literally just now uninstalled vue-router and downgraded to v3 of router and works. This is a fresh install btw so i can't tell yet how this will behave

The issue seems related to esbuild
A temporary workaround is to add resolution to your package.json:
"resolutions": {
  "esbuild": "0.14.34"
}

Same issue here.
PM: pnpm
Vite: 2.9.1
@Geebrox's temporary workaround works well.

The issue seems related to esbuild
A temporary workaround is to add resolution to your package.json:
"resolutions": {
  "esbuild": "0.14.34"
}

I hava the same error, when the version is
"vue": "3.2.26",
"vue-router": "4.0.12",
"@vitejs/plugin-vue": "1.9.4",
"@vue/compiler-sfc": "3.2.22",
"vite": "2.6.14",

things are ok,no error.
But when the version is
"vue": "3.2.31",
"vue-router": "4.0.12",
"@vitejs/plugin-vue": "2.2.4",
"@vue/compiler-sfc": "3.2.31",
"vite": "2.8.6",

the version of vite is 2.8.6 or 2.9.1 , same error

Unfortunately, I'm unable to replicate @Geebrox's solution... are resolutions PNPM specific?

The issue seems related to esbuild
A temporary workaround is to add resolution to your package.json:
"resolutions": {
  "esbuild": "0.14.34"
}

Working on  Reactjs too, Thanks man!

Unfortunately, I'm unable to replicate @Geebrox's solution... are resolutions PNPM specific?

maybe is yarn

Thank you, works.
Also, i'm using npm not yarn so if anyone comes here using npm, fyi its equivalent is overrides
"overrides": {
    "esbuild": "0.14.34"
  },

The issue seems related to esbuild
A temporary workaround is to add resolution to your package.json:
"resolutions": {
  "esbuild": "0.14.34"
}

The issue seems related to esbuild
A temporary workaround is to add resolution to your package.json:
"resolutions": {
  "esbuild": "0.14.34"
}

Thank man 👍！

请问解决这个问题了吗，我也是这个问题 vue项目

解决了，删除 node_modules 重新install一下就行了

Please remove the custom resolutions, esbuild 0.14.36 has been released reverting the problematic change

The issue seems related to esbuild
A temporary workaround is to add resolution to your package.json:
"resolutions": {
  "esbuild": "0.14.34"
}

that's useful for me.


 Done
W: GPG error: http://archive.ubuntu.com trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 16126D3A3E5C1192

Actually in earlier iterations I've tried adding this pubkey using GPG following advice given to a similar error on a true Ubuntu system. This caused other errors, so I did a total uninstall and reinstall for this error report:

uninstalled (lxrun /uninstall /full)
uninstalling the Linux subsystem via the Windows features window
rebooted
installed it again
rebooted a 2nd time

Windows build number: 1607, OS build 14393.82
This is the content of my /etc/hosts (the only file I modified):
<IP_ADDRESS> localhost DESKTOP-xxxxxxx

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

This does not seem specific to WSL. Can you try some of the workarounds suggested in the web such as this one? Also, just to make sure you are able to connect to network, you can open an admin prompt and try ping.

I specifically said I already tried adding the key, and completely scratched my WSL since that solution didn't work and I wanted to debug this from scratch, but here it goes:
(username/hostname removed from prompt)
$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 16126D3A3E5C1192
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.XB69n9K8zE --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv-keys 16126D3A3E5C1192
gpg: requesting key 3E5C1192 from hkp server keyserver.ubuntu.com
gpg: key 3E5C1192: public key "Ubuntu Extras Archive Automatic Signing Key<EMAIL_ADDRESS>imported
gpg: Total number processed: 1
gpg:               imported: 1
udif@DESKTOP-R7AHPGD:~$ sudo apt-get update
Get:1 http://security.ubuntu.com trusty-security InRelease [65.9 kB]
Ign http://archive.ubuntu.com trusty InRelease
Get:2 http://archive.ubuntu.com trusty-updates InRelease [65.9 kB]
Get:3 http://archive.ubuntu.com trusty Release.gpg [72 B]
Get:4 http://archive.ubuntu.com trusty Release [11.9 kB]
Hit http://security.ubuntu.com trusty-security/main amd64 Packages
Get:5 http://security.ubuntu.com trusty-security/restricted amd64 Packages [13.0 kB]
Hit http://archive.ubuntu.com trusty-updates/main amd64 Packages
Get:6 http://archive.ubuntu.com trusty-updates/restricted amd64 Packages [15.9 kB]
Hit http://security.ubuntu.com trusty-security/universe amd64 Packages
Get:7 http://security.ubuntu.com trusty-security/multiverse amd64 Packages [4,990 B]
Hit http://archive.ubuntu.com trusty-updates/universe amd64 Packages
Get:8 http://archive.ubuntu.com trusty-updates/multiverse amd64 Packages [14.8 kB]
Hit http://security.ubuntu.com trusty-security/main Translation-en
Get:9 http://security.ubuntu.com trusty-security/multiverse Translation-en [2,570 B]
Get:10 http://security.ubuntu.com trusty-security/restricted Translation-en [3,206 B]
Hit http://archive.ubuntu.com trusty-updates/main Translation-en
Get:11 http://security.ubuntu.com trusty-security/universe Translation-en [78.9 kB]
Hit http://archive.ubuntu.com trusty-updates/multiverse Translation-en
Hit http://archive.ubuntu.com trusty-updates/restricted Translation-en
Hit http://archive.ubuntu.com trusty-updates/universe Translation-en
Get:12 http://archive.ubuntu.com trusty/main amd64 Packages [14 B]
Fetched 277 kB in 0s (298 kB/s)
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release  Unable to find expected entry 'restricted/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.
$

This is exactly what I got on the previous time I've tried this.

The last time appears to show a different error.
Is this on the first time you've run apt-get after an install? You haven't installed other repositories? Since I haven't seen anyone else report that the key was missing from a default WSL install, something else must be going on. Maybe it is a networking problem at heart, as @sunilmut suggests?

Yes, I know this is strange. I never found a single report of this error in google, which is why I hesitated opening it here, but I tried recreating this several times, including totally removing WSL and reinstalling it from scratch. I never managed to get this to work.
I also got the same result (in an earlier iteration when I tried lxrun /update on the Windows prompt.
C:\WINDOWS\system32>lxrun /update
Checking for updates...
Ign http://archive.ubuntu.com trusty InRelease
Get:1 http://security.ubuntu.com trusty-security InRelease [65.9 kB]
Get:2 http://archive.ubuntu.com trusty-updates InRelease [65.9 kB]
Get:3 http://archive.ubuntu.com trusty Release.gpg [72 B]
Get:4 http://archive.ubuntu.com trusty Release [11.9 kB]
Get:5 http://security.ubuntu.com trusty-security/main amd64 Packages [523 kB]
Get:6 http://archive.ubuntu.com trusty-updates/main amd64 Packages [889 kB]
Get:7 http://archive.ubuntu.com trusty-updates/restricted amd64 Packages [15.9 kB]
Get:8 http://archive.ubuntu.com trusty-updates/universe amd64 Packages [372 kB]
Get:9 http://archive.ubuntu.com trusty-updates/multiverse amd64 Packages [14.8 kB]
Get:10 http://archive.ubuntu.com trusty-updates/main Translation-en [430 kB]
Get:11 http://security.ubuntu.com trusty-security/restricted amd64 Packages [13.0 kB]
Get:12 http://security.ubuntu.com trusty-security/universe amd64 Packages [135 kB]
Get:13 http://archive.ubuntu.com trusty-updates/multiverse Translation-en [7,661 B]
Get:14 http://archive.ubuntu.com trusty-updates/restricted Translation-en [3,699 B]
Get:15 http://archive.ubuntu.com trusty-updates/universe Translation-en [197 kB]
Get:16 http://security.ubuntu.com trusty-security/multiverse amd64 Packages [4,990 B]
Get:17 http://security.ubuntu.com trusty-security/main Translation-en [287 kB]
Get:18 http://archive.ubuntu.com trusty/main amd64 Packages [14 B]
Get:19 http://security.ubuntu.com trusty-security/multiverse Translation-en [2,570 B]
Get:20 http://security.ubuntu.com trusty-security/restricted Translation-en [3,206 B]
Get:21 http://security.ubuntu.com trusty-security/universe Translation-en [80.8 kB]
Fetched 3,123 kB in 8s (361 kB/s)
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release  Unable to find expected entry 'restricted/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.

C:\WINDOWS\system32>

I am also having the same issue with a newly installed WSL. Please has anyone found a way around this issue?

Try disabling your anti-virus firewall (if you have an anti-virus application installed).  I have McAfee IS 2016 and had the same problem reported here, and when I disabled my firewall apt-get update went through fine. I then re-enabled my firewall, tried the command again, and it went through fine again. So my guess is that one may need to disable the firewall to download the public key whenever it changes - that's my guess.

Much has changed since 2016, please reopen if you continue to have issues on newer builds of Windows.


Pinning GeoTrust root CA instead of unique server certs.

Removed server-specific pins, added GeoTrust CA certs to the client. This will enable us to keep updating the spideroak.com certificate without having to carefully coordinate certificate updates.

This pull request is now managed with CodeReviewHub. Refresh.

@merickson, do the certs all just get pulled in by the build, or does some code have to change to get the new ones? Ie, is this change self-contained, or is there more pending?

@kenmanheimer , completely self-contained as long as there's no dangling build artifacts- I think you added grunt debug:! for this sorta thing. The code in both Cordova-HTTP and File Download Plugin slurp up all the certs and will return OK if one of these certs appears anywhere in the certificate chain presented by the server.

Too good! (-%


BUG: Repo.assets returns all Repo.files

This bug prevents inclusion of non-asset files (such as README.md) in and Onyo repo.
The fix for this is simple, thanks to valid_name() to filter. The problem is that valid_name() logs errors whenever it returns false, which leads to widespread test breakage elsewhere.
It needs to be assessed:

should valid_name() log these and/or should the log-level be downgraded
how to make sure onyo new still prints relevant error messages to stderr
which tests should be updated/fixed to use valid asset file names (many don't, due to laziness on our part)

While out-of-scope, it's also worth keeping in mind the goals of #255 when fixing this.

def valid_name(logging=True): as a default case, but from Repo.get_assets(logging=False) comes to my mind, since it does not change the current behavior, but enables the re-usability of the function.
That does obviously not work for #255, as long as we don't want to add this type of solution to all functions with logging, but I think might be part of solutions as a whole, when we want to use functions in multiple ways like here.


DOC-727: Convert Workflow reference to MD

Update the docs:

Convert workflow-reference.md to Markdown and review the functions.
Update analytics.md to better reflect Workflow class functionality.
Update structure.md to fix listed functions and attributes under the Catalog class and update Job class description.
Update project-reference.md to fix some argument overviews and attribute descriptions.
Update job-reference.md to update description text.

Corresponds to Documentation JIRA task DOC-727.

Because we’re not publishing the docs currently, we’ve added the new project_id string to the Workflow reference page (more details here).


Anti-spam message shows plain text over the URL

Noticed in https://github.com/jenkins-infra/helpdesk/issues/3217, the link to the infra helpdesk is shown in plain text, rather than being an actual link.

I think we were planning to get rid of this anti spam anyway as it's just causing problems


Do not change component displayName

When using inject or for that matter containers this code https://github.com/mobxjs/mobx-react/blob/ab90ae65991c95da73406accd1048e225e63f02e/src/inject.js#L37 changes the component names, which makes it impossible to debug in React DevTools because you don't know which component is which.

Nobody else seems to be bothered by this so closing.


bug: C++ multi line comments with asterisks aren't respected

For example:
  /***
   * This is an example of the error:
   * this line is considered a new sentence.
   */

This also applies to TypeScript comments.

This has been fixed as of the latest commits. Myself and anyone building from source will test it out for a bit longer before we release, but I'm going to mark the issue as closed for now.
If you continue experiencing problems (either building from source, or in the eventual release) please reopen this issue.


docs: bytecode storage

Pull Request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Resolves: #
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

@Eikix last check and merge?


MultiMAP using precomputed distance matrices

Hi!
I would like to try MultiMAP for integrating a variety of datasets on a specific protein family.
This includes classical omics data like RNA-seq or targeted metabolomics, and also structural information and protein annotations.
For each of the different data modalities, I derived distance matrices which I can generate nice individual UMAPs on (using the metric='precomputed' parameter).
And as MultiMAP is a generalization of UMAP, would it theoretically work to create a MultiMAP based on these distances?
I am aware that the current implementation does not support this, but I would like to know if conceptually this would be possible.
I tried to figure out by looking at your source code, but I am unfortunately neither a mathematician nor a Python expert...
Many thanks!
Ulrich

I had a root around Mika's source code and in principle this could be possible (not with the current code, like you noticed). The algorithm generates a set of distances and KNN indices for each individual dataset, and then for each pairwise combination of datasets. I'm not sure how that would work with your data though, as you need shared features to compute a pairwise representation.


Add Travis

Checks format and run tests with codecov.

Sorry - created using the wrong branch. Hence closing.


[WFCORE-1114] Avoid NPE if getStatus() is called on stopped service

Linux Build 3295 outcome was FAILURE using a merge of 7fb18495677aed288f2a279ce71244f4713c8239
Summary: Execution timeout (new); tests passed: 3429, ignored: 64 Build time: 01:00:10


add support for width: :full

[Closes #638]

@manuelpuyol I just tried that and ran into issues with needing width and height to support falling back to integer values.
Is there a way to support that in Utilities? If not, I guess I could add a special case to Classify for the integers and let Utilities handle the mapping to CSS.

I guess I could add a special case to Classify for the integers and let Utilities handle the mapping to CSS.

I think this would be the ideal case 🤔


virtcontainers: process the case that kata-agent doesn't start in VM

virtcontainers: process the case that kata-agent doesn't start in VM
If kata-agent process is not launched to run in VM, kata-runtime will exit because of timeout,
however kata-proxy and qemu process will still resident in host
Call Check grpc function to check whether grpc server is running in kata-agent process in VM,
if not and then do some rollback operation to stop kata-proxy and qemu processes
Fixes: #297
Signed-off-by: flyflypeng<EMAIL_ADDRESS>

PSS Measurement:
Qemu: 144708 KB
Proxy: 6742 KB
Shim: 8796 KB
Memory inside container:
Total Memory: 2045972 KB
Free Memory:  2013332 KB

PSS Measurement:
Qemu: 144050 KB
Proxy: 6795 KB
Shim: 10930 KB
Memory inside container:
Total Memory: 2045972 KB
Free Memory:  2011712 KB

PSS Measurement:
Qemu: 142416 KB
Proxy: 6825 KB
Shim: 10819 KB
Memory inside container:
Total Memory: 2045972 KB
Free Memory:  2011464 KB

PSS Measurement:
Qemu: 163900 KB
Proxy: 6792 KB
Shim: 10786 KB
Memory inside container:
Total Memory: 2045972 KB
Free Memory:  1996624 KB

@woshijpf  do me a favour, run next command with this patch
docker run --runtime=kata-runtime -ti busybox bash

if you don't see a qemu process running  then this patch looks good to me

You have to look closely at the previous command to notice that it won't work as bash isn't included with busybox. Equivalent:
$ docker run --runtime=kata-runtime -ti does-not-exist

@jodh-intel I think you mean
docker run --runtime=kata-runtime -ti busybox does-not-exist

@devimc - I do! Thanks! :smile:

@devimc I test this patch in my ubuntu 16.04 x86_64 laptop is good with next two cases:

kata-agent is running in VM
This case works well, container can run in VM

# need to run as root
# docker run --runtime=kata-runtime -ti busybox sh
/ # ls
bin   dev   etc   home  proc  root  sys   tmp   usr   var

no kata-agent  in VM
First, we need to create a rootfs image without kata-agent, you can follow next steps:

$ cd <kata-containers>/osbuilder/rootfs-builder

# use euleros as example
$ ./rootfs.sh euleros

# remove kata-agent.service, so systemd can't launch the kata-agent process
$ cd ./rootfs-EulerOS/usr/lib/systemd/system/
$ rm kata-agent.service
$ rm rm kata-containers.target

# make rootfs-EulerOS into rootfs.img
$ cd <kata-containers>/osbuilder/image-builder

# we need to modify the rootfs make shell scipt
$ cp image_builder.sh image_builder-no-agent.sh
$ vim image_builder-no-agent.sh
 # comment follow lines
129 # [ "${AGENT_INIT}" == "yes" ] || [ -x "${ROOTFS}/usr/bin/${AGENT_BIN}" ] || \
130 #        die "/usr/bin/${AGENT_BIN} is not installed in ${ROOTFS}
131  #       use AGENT_BIN env variable to change the expected agent binary name"
132 # OK "Agent installed"

$ next, we can run  image_builder-no-agent.sh to make rootfs image
$ ./image_builder-no-agent.sh ../rootfs-builder/rootfs-EulerOS/

# finally, we get the Euleros rootfs.img without kata-agent
$ ls
 ls
Dockerfile  image_builder-no-agent.sh  image_builder.sh  kata-containers.img   README.md

# we can copy kata-containers.img to anywhere, but you need to modify the "image = "  field in the /usr/share/defaults/kata-containers/configuration.toml file

Now, we can use the same command as previous case to test this patch
# need to run as root
# docker run --runtime=kata-runtime -ti busybox sh
docker: Error response from daemon: OCI runtime create failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded: unknown.

# we get the error output as expected, and let's see if any kata-proxy and qemu processed is resident in host system
$ ps -auxww --sort=start_time

......
root     10857  0.0  0.0      0     0 ?        S    23:11   0:00 [kworker/0:1]
root     10858  0.0  0.0      0     0 ?        S    23:11   0:00 [kworker/1:3]
root     11118  0.0  0.0  44744  3752 pts/17   R+   23:14   0:00 ps -auxww --sort=start_time

we get the result as expected, so this patch works well.

@woshijpf nice and thanks, and what about docker run --runtime=kata-runtime -ti busybox does-not-exist " ?   is qemu running?

@devimc Yep，I just run the command docker run --runtime=kata-runtime -ti busybox does-not-exist, the result surprises me that qemu and kata-proxy processes both still reside in the host system, it is a bug need to be fixed.
Maybe we need to do some rollback if container doesn't run successfully.

@woshijpf there is a lot of work related to rollback, and I'd be more than happy if you want to look into it. We need to be careful about not having rollbacks that would collide with each others.

@sboeuf Thanks for your careful review.I'm glad to deep into it to solve rollback related problems.

@sboeuf @jodh-intel @devimc Hi buddies~I am fixing the problem of qemu and kata-proxy processes reside in system while createSandboxFromConfig() is failed, but I meet a problem and I want to get help from your nice guys.
The problem is that how can I get to know whether qemu process  is running or not in system when err := s.startVM()  return error in createSandboxFromConfig() function, since the error return by s.startVM() may caused by s.hypervisor.startSandbox() or s.hypervisor.waitSandbox or s.agent.startSandbox() in startVM() function.Thanks!

PSS Measurement:
Qemu: 164140 KB
Proxy: 6803 KB
Shim: 10818 KB
Memory inside container:
Total Memory: 2045972 KB
Free Memory:  1996136 KB

PSS Measurement:
Qemu: 162063 KB
Proxy: 4597 KB
Shim: 12829 KB
Memory inside container:
Total Memory: 2045972 KB
Free Memory:  1997252 KB

@sboeuf Thanks for your detailed reviews and suggestion, I learn a lot from your reviews, and I will finish this work as soon as possible.

@sboeuf I'm sorry to do this work so late. Now, I follow your suggestion to refactor the code and split modified code into 4 commits which make the code more clearly.

@sboeuf Could you help me to review the code again, I modify the code as you suggested.
Finally thanks for your patient and detailed reviews, I have learned a lot from you.

@woshijpf I have just added one last comment. Thanks for your quick fixes !

@woshijpf we just fixed the CI, could you rebase this PR on latest master, and it's good to be merged once the CI will pass.

@woshijpf any updates on this ?

@sboeuf he is out of office for about a mouth. And will be back next week ,so updates will be promoted next week~

@jshachm thx for the info !

@jshachm @woshijpf  -- back yet?  I want to get this contribution merged.

@egernst I'm sorry for leaving so long time, and I am going to rebase the code to pull a new request.

no worries @woshijpf - hope it was a good break.  Hope the CI goes through smoothly.


fix organization notifications issues

re: https://github.com/CartoDB/cartodb/issues/11957
acceptance (test mostly in firefox, but also this should still work in the rest)

cancel button should work as ESC and close icon
form submit should work in chrome as well as in Firefox, with Ctrl + Enter, and button click

Acceptance results are in: the delete dialog is working perfectly now.
However, the send notification form has still the same issues. You have to press the "Send" button twice, and control+enter does not work (in Firefox).

Development!

😞 sorry for the duplicated work testing, I'l definitely take a look but I was sure this was solved when pushing the changes
sorry again

Haha, don't worry. Now it's when you discover this was due to the change requested in CR, and shift the blame to @xavijam (now that he can't hear us :P)

just found out when you modify a form and then try to submit via javascript firefox prevents behaviour, the solution is cloning the form and appending to the body :/

Tested in staging, works like a charm in firefox. If you wanna try with your Linux ( 😛 ) @javitonino, it is deployed in ded07. 💋

Giving my personal seal of approval for Firefox/Linux compatibility.
Yay! 🙌


Copy to clipboard in log screen

A button that copy the log to clipboard in Log screen.
The logs must be merged to string with line break \n for each line.

/cib


fix: 🐛 change the path of module in go.mod

Modify go.mod to fix  module decalres errors when getting packages by using go get -u github.com/aceld/zinx

the new version of Go does not recommend to use go get, please try go mod instead.

when i require github.com/aceld/zinx@latest in go.mod, it will also attend a warning , parsing go.mod: unexpected module path "zinx" , cause of go.mod file module zinx has been set. when i download zinx from github by myself, i can move it to gopath or vendor path. so i hope the module name could be set to github.com/aceld/zinx.


[Deploy] Roundcube

Service
Roundcube webmail client
Link to your repository
The recipe can be found here.
Additional Information
Roundcube doesn't have any hi res or vector format logo around that I could find, so I included a basic e-mail icon. If anyone knows where I can find a vector icon, please let me know. :)

Where does this icon come from or what's the license of it?

Icon attribution and license info is included in the recipe. The color modifications are done by me and in the public domain.

Oh sorry, I've missed that!

No prob, thanks for the inclusion. :)


add GitHub URL for PyPi

Warehouse now uses the project_urls provided to display links in the sidebar on this screen, as well as including them in API responses to help the automation tool find the source code for Requests.
Docs: packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/#project-urls

Thanks for the PR, adding more info to PyPI is certainly a good idea. Some questions:

Would it make sense to add also link to issues? It can obviously be easily found via the GitHub project main page. Do you know how other projects are using this?
If we just add link to the GitHub project main page, perhaps the text should be "GitHub" instead of "Source". Again, knowing how others do this would help.
Which setuptools versions support project_urls? Do older emit warnings/errors if they see it? We can obviously make sure we use recent setuptools version when creating packages, but we cannot control what users have when they install them.

Did little searching and via this StackOverflow question found a good example project: https://pypi.org/project/PyScaffold/. They have various links like this and we could at least use source, issues and Twitter.
It's cool that PyPI also automatically adds icons for links it recognizes. Based on the aforementioned SO question, icons are set according to rules here. On a quick look at the rules it seems we could also add Slack.
Possibly we could also add Changelog/What's New, but then that URL needed to be updated with each release to point to the correct release notes. We have invoke task that updates version info in setup.py and it could handle this as well.

I'm in general very much in favor of doing this, but I'm still worried about setuptools compatibility with project_urls. Although these links are really nice, warnings/errors when users are installing Robot Framework are not.

setuptools compatibility

It looks like project_urls was added in 38.3.0, in early 2018. Installing e.g. pyscaffold from a .tar.gz (latest) with setuptools as old as 32 doesn't say anything about project_urls, so this is probably safe... a release like 5.0 which drops python major versions is probably as good a time as any to actually declare a mininum setuptools... debian/buster, usually a good indicator of "ain't broke,"  ships 40.0.8, and might be a reasonable candidate.

2. If we just add link to the GitHub project main page, perhaps the text should be "GitHub" instead of "Source". Again, knowing how others do this would help.

https://github.com/pypa/warehouse/issues/5947

Quick update:

Let's do this!
I added issue #4312 to track this. We should discuss there what URLs to add.
According to the setuptools docs linked above by @bollwyvl, project_urls is new in setuptools 38.3 and long_description_type that we are already using is new in 38.6. Using project_urls thus ought to be pretty safe. We can add it at least in RF 5.1. Possibly already in RF 5.0.1, but then I'd like this to be tested with old setuptools versions.


MP Evaluation Report - Add Header with EPA Logo

Implement the header with the EPA Logo for the MP Evaluation Report
https://xd.adobe.com/view/bdf8fe62-0af2-4fbd-8672-0b7959f8bb88-e8ab/
Notes:
MP Evaluation Report (Separate tab) has been implemented and is available to access through the URL from MP Evaluation Notification email. This task is to add the header to the existing Report

Test Case: TC532
Test Passed


Gardenlet certificate rotation

How to categorize this PR?

/area security
/area usability
/kind enhancement
/priority normal
What this PR does / why we need it:
Introduces Certificate Rotation for the Gardenlet.
Currently the client certificate generated during the initial bootstrap is only valid for 1 year.
The certificate needs to be renewed before it expires to avoid disruption.
Which issue(s) this PR fixes:
Fixes #1721
Special notes for your reviewer:

I will update this PR with proper documentation

Depends on #2544
Release note:

Introduces Certificate Rotation for the Gardenlet.

/hold until v1.7 is released

/unhold as v1.7.0 is released

@danielfoehrKn wanted to push some missing changes.
/status author-action
/needs rebase
I can take a look afterwards.

/status author-action check verify errors

/assign

Thanks @danielfoehrKn for updating the PR. I will re-review today :)

I updated the PR @tim-ebert  PTAL

Thank you @danielfoehrKn for updating the PR. I will start a build. Once started, the build URL will be posted here.

A build of this pull request has started. You can check on its progress here: https://concourse.ci.gardener.cloud/teams/gardener/pipelines/gardener-master/jobs/master-pull-request-job/builds/168

/status author-action

PTAL

I tested it again and addressed the last comments.

I'm doing a final test run, otherwise I have no further comments.
thanks.  I also did a change to the seedClient creation in the gardenlet that would be good if someone takes a closer look at.

I also did a change to the seedClient creation in the gardenlet that would be good if someone takes a closer look at.

That change looks good to me.
As discussed in person, we need a small improvement for the Subject field handling because at the moment we only use a fixed Subject for renewals.

As discussed in person, we need a small improvement for the Subject field handling because at the moment we only use a fixed Subject for renewals.

Allowing to rotate, but not auto-approving certificates that do not stem from the gardenlet TLS bootstrap. Added some documentation. PTAL

Applied suggestions.
Additionally added, that the IP SANS and DNS SANS of a cert to be rotated are also set in the CSR.
This is to not drop any possibly required information from the cert.

I will take another look tomorrow and hope that we can get it in afterwards. Sorry for the delay.


Enter key

The Enter key is not repeated when call last macro.

This is a huge limitation, and should at least be much more prominently mentioned


Removes deprecated promise API

Did you check performance with those changes ?

Yes I did, but better to test in other devices.
El 25 jul. 2017 7:11 p. m., "Cedric Pinson"<EMAIL_ADDRESS>escribió:

Did you check performance with those changes ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cedricpinson/osgjs/pull/831#issuecomment-317804050,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABs8RALMJPRkS7L8PPCz-8zCKwYteIeEks5sRiGkgaJpZM4Od8W8
.

For me it was the same performance.
El 25 jul. 2017 11:30 p. m., escribió:

Yes I did, but better to test in other devices.
El 25 jul. 2017 7:11 p. m., "Cedric Pinson"<EMAIL_ADDRESS>escribió:

Did you check performance with those changes ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cedricpinson/osgjs/pull/831#issuecomment-317804050,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABs8RALMJPRkS7L8PPCz-8zCKwYteIeEks5sRiGkgaJpZM4Od8W8
.

The PR fails the tests actually see
https://travis-ci.org/cedricpinson/osgjs/builds/255721797#L3213
I think there is an issue with the PR that ensured unittest fails if no test ran

That's good. It means the PR I did about make the node process fail when a test fail is working. There was indeed a test fail and a subtle bug that is now fixed. ready for review now!

Need to add some performance tests to make sure we don't loose a ms :)

@jtorresfabra ping, what's the status ?


Set blue channel as used for compressed normal maps

Fix  #61039.
Fix Basis Universal and VRAM Compressed compressions with normal maps via setting blue channel as used.

@cow-neaz Did you mean to close this PR, or was that a mistake?


n-ary BoolOps with Hpc Input and OutPut

Algorithm
According to our methods based on arrangements, we need four interface functions:
- UNION : STRUCT() ->  Hpc
- INTERSECTION : STRUCT() ->  Hpc
- DIFFERENCE : STRUCT() ->  Hpc
- XOR : STRUCT() ->  Hpc

Any complex Boolean expression
must have the semantics of a STRUCT including one or more such operators.
They are also alias of STRUCT:
UNION = STRUCT
INTERSECTION = STRUCT
DIFFERENCE = STRUCT
XOR = STRUCT

First step:
Transform the input in a list of Breps ::Hpc type of dimension $d$ in the sameb reference frame.
If intrinsic and embedding dimension of all terms (Hpc) are not equal to $d$ and $d-1$, respectively, give the ERROR("dimension error in BoolOps", <first childs[i] errored>)
Second step
Execute ARRANGE3D and get ordered INNER atoms
as Boolean string (binary) arguments of  length LEN(INNER(atoms))
Third step
Execute n-ary Boolean (logical)  operation,   say
UNION || INTERSECTION || DIFFERENCE || XOR  on arguments string
Return 'solution' string;  convert via atoms to Hpc return value.

@apaoluzzi  all clear. need to find some time to implement it

fixed


stellar-core: 17.0.0 -> 18.5.0

Description of changes
Update stellar-core to latest version (see https://github.com/stellar/stellar-core/releases/tag/v18.5.0).
Made as a replacement of https://github.com/NixOS/nixpkgs/pull/159781 due to that version being both unable to build with glibc >= 2.34 and it no longer being the latest version.

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

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

1 package built:

stellar-core

I've ran stellar-core test and received the same results as on a ubuntu machine doing the exact same test run on the same release version (18.5.0).

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

1 package built:

stellar-core


Interesting stuff here:

Interesting stuff here:
https://developer.mozilla.org/en-US/docs/Web/CSS/box-decoration-break

This issue was imported from Google Moderator
Moderator votes: +4
Issue added by vince357 on 2014-09-26
To vote this issue up or down, simply include +1 or -1 in your comment.

Duplicate of #1281.


Should have confirm to delete dial

New Issue Checklist (tick off like this: [x])

[x ] I checked existing issues (open and closed) for possible duplicates
[x ] I can reproduce the problem on the latest stable version (not nightly!)

What is your browser?

[ x] Firefox
[ ] Chrome

What is your operating system?

[ ] Linux
[ ] Mac
[x ] Windows

Description (please include examples/screenshots where applicable)
I really like this addon better than the rest  but sometimes I accidentally delete a dial clicking the x even when I don't know it. Please add a confirm to delete from the main dials page.

I agree, happens to me as well every now and then. I'll see how I can do it when I find some time.


Update quickstart version to testing

The soroban-dev image is using an outdated version of soroban-rpc, and this should point to testing anyways now that Soroban is on testnet.

Preview is available here:http://soroban-docs-pr691.previews.kube001.services.stellar-ops.com/

Preview is available here:http://soroban-docs-pr691.previews.kube001.services.stellar-ops.com/


Unable to parse template pattern (: in path)

Google API guides recommend custom verbs/actions be specified using the semicolon (:) as a separator. However, this results in a parsing error that I was able to track down to this plugin.
In the following definition, note the :suspend suffix.
rpc SuspendUser(SuspendUserRequest) returns (SuspendUserResponse) {
    option (google.api.http) = {
        post: "/v1/users/{user_id}:suspend"
        body: "*"
        response_body: "user"
    };
}

Attempting to generate with this results in an error:
2024/09/04 00:11:24 WARN unable to parse template pattern error="unrecognized word at position: 10: {user_id}:suspend" template=/v1/users/{user_id}:suspend

Thanks for this report. Can you try installing the plugin from the main branch to see if this is properly fixed? I just pushed up a change which should hopefully fix this issue. For now these names are discarded but maybe they should be used in the operationId

It parsed the template, but the :suspend should be part of the path itself. Right now, it appears to be stripping off the part after :. For example, /v1/users/{user_id}:suspend becomes /v1/users/{user_id}. The expectation is that the full path remain intact as part of this, including the :suspend verb.

Hey, I think I forgot to update this. This should be how it works since v0.9.6. Let me know if this looks correct now. Until then, I'm going to close this issue


Save Additional Information

Hi,
This tool is great. it works as expected with simple key value options; however is it possible to store additional information with the request?
I have a belongsToManyThrough in which i am using this tool to populate a BelongsToMany field. The issue i am having is that i have a singular table, say attributes, that stores the 2 primary keys and a third enum field. An example is product categories, in the attributes table i store the product_id, category_id and type (enum, value = 'category')
When doing this with this package i find that the type field always defaults to the default type - i need to be able to set the type for each multiselect, of which there are many. Is this possible?

sorry, wrong multiselect. However this one does function better than the one i am using. but stores data as json rather than a relationship insatnce.


Ctrl+click not work

in logseq 0.64, it not work when ctrl+click to link ,only work with block，
#bug

The failure occurred, but I restarted the program and it worked fine, I'm sorry

The failure occurred, but I restarted the program and it worked fine, I'm sorry

No need to feel sorry! I think there are some cases that ctrl click does not work indeed.


To Allow specify (at least) description in response definition when $ref is used

It would be very useful to be able to add (at least) description to the $ref in case of (at least) response part of the API specification.
It would allow me to specify generic reusable response that could be refined for every concrete use case. Because there are a lot of cases of responses that have the same structure, only the difference is the information why / when the error occurred.
Oxample of the use case:

In more generic perspective, it could be useful to allow to "override" some parts of references (examples, parameters ...).

For Schema Objects, this is addressed by PR #1977 for OAS 3.1
I'm not sure what the plan is for $ref outside of Schema Objects.

@ratermir yes, this is the correct repo.
@whitlockjc @webron more $ref fun that we should track for OAS 3.1.  I think it falls under things we're already talking about.

PR: #2181


chore: update FloatBorder bg color

I think the border looks cleaner when not setting a bg color.
Before

After

Good catch, thanks 🥰


Issue & Pr-Templates.MD Files

It is Need for Easy communication!
I

For this fix - templates can be taken from https://github.com/oneapi-src/oneDAL/tree/master/.github repo

Thank you @napetrov :))

@ritiksoni00  - PR templates are working now.
But not issues templates.  could you please take a look why they don't work?

Even with last one - issue templates are not applied

i saw somewhere i think :-
go to  setting of repo
then in the Feature section, we have to add issues templates by checking the box like this

I've add it via interface

idk why my template didn't work?

i guess path - as you can see in repo now - they are different.


Support eslint 4

The ecmaVersion option moved into parserOptions in eslint 2, but in eslint 4 it will cause an error at the top level.

Thank you very much @gmeeker


AD410 - Request for a copy of a Working config file please

I have an AD410 doorbell camera and have the sound from the microphone, but am unable to send audio to it's speaker.
I have seen from a previous issue raised (#141) that webrtc needs to have audio output of PCMA/8000 or OPUS/48000/2.  However, I am unable to figure out how to do this.  I have read the "codec-madness" section but it was still not clear to me.
"medias": [
        "video, recvonly, H.264 Main 5.0",
        "audio, recvonly, MPEG4-GENERIC/8000"

Please help.

mqtt:
  host: <IP_ADDRESS>
  user: admin
  password: psw

detectors:
  coral:
    type: edgetpu
    device: usb

ffmpeg:
  hwaccel_args: preset-nvidia-h264
  input_args: preset-rtsp-restream-low-latency
  output_args:
    record: preset-record-generic-audio-copy

go2rtc:
  webrtc:
    candidates:
      - localhost:8555
      - stun:8555
  api:
    origin: '*'

  rtsp:
    default_query: flac

  streams:
    doorbell:
      - rtsp://usr:psw@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=1#backchannel=0
    doorbell_2way_audio:
      - rtsp://usr:psw@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0#backchannel=0
      - "ffmpeg:doorbell_2way_audio#audio=opus"
snapshots:
  enabled: true
  clean_copy: false

ui:
  live_mode: webrtc

You have disabled 2way audio for both your streams in config

If I don't do both then my doorbell doesn't work. Thanks for the reply.
On Mon, Dec 25, 2023, 4:17 AM Alex X @.***> wrote:

You have disabled 2way audio for both your streams in config
—
Reply to this email directly, view it on GitHub
https://github.com/AlexxIT/go2rtc/issues/844#issuecomment-1868879341,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFZ7S2IZEAWEGV6UBIXVDC3YLE777AVCNFSM6AAAAABBBUIYLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYHA3TSMZUGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Also, I have tried it without the backchannel on both lines and it still
didn't work.
On Mon, Dec 25, 2023, 8:24 AM dhtguru @.***> wrote:

If I don't do both then my doorbell doesn't work. Thanks for the reply.
On Mon, Dec 25, 2023, 4:17 AM Alex X @.***> wrote:

You have disabled 2way audio for both your streams in config
—
Reply to this email directly, view it on GitHub
https://github.com/AlexxIT/go2rtc/issues/844#issuecomment-1868879341,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFZ7S2IZEAWEGV6UBIXVDC3YLE777AVCNFSM6AAAAABBBUIYLOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYHA3TSMZUGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

You need to provide more useful information for debugging


Alert for magic not working as intended #2

Hey very sorry to reopen this issue but could you do the same thing you did for divine magic potions, to the forgotten brew as that is still not working as intended, thank you so much!!!!!!
Having the forgotten brew in the inventory

Having the divine magic pot in inventory working now THANK YOU!!!!!!!!

Thanks for fixing the last issue though legend! my callisto trips will be more chill now!


Fence/Blit Encoder for Metal Frames

Implement a memory blit encoder for filling in the various UBOs.
Then put a MTLFence at the end of the frame/beginning of the encoder.
This will let us encode frames without having to worry about trashing the UBO buffers.

Went a different way.


Fixes upload by disabling import of empty or whitespace labels

Test with refinery respectively with release state
While uploading with records with and without labels it could come to
the sitation where records got labeled with empty values
solves https://github.com/code-kern-ai/refinery-gateway/issues/5
sample data sets which should now work
label-bug.json.zip
clickbait mini 2 - Labels and non-labels.json.zip

I tested with the sample data sets and some more, everything worked fine.


flutter

Type: Feature Request
Context

Managed Dependencies: on
Cloud SDK Version: 419.0.0
Skaffold Version: v2.1.0
Minikube Version: 1.29.0

VS Code version: Code 1.75.1 (441438abd1ac652551dbe4d408dfcec8a499b8bf, 2023-02-08T21:32:34.589Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

/needsMoreInfo

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Support AzureSQL Database Tier for *.bacpac import

Is your feature request related to a problem? Please describe.
The Data Tier Application Wizard does not give you the ability to specify the settings for the restored database.
When you have certain types of features present in the backup, it will fail to restore with the general purpose edition used as the default.  I just saw this limitation with a customer when In-Memory tables were captured in the backup:
https://learn.microsoft.com/en-us/azure/azure-sql/in-memory-oltp-overview?view=azuresql#benefits-of-in-memory-technology
Their import fails with error:
Import bacpac: Could not import package.Error SQL72014: Core Microsoft SqlClient Data Provider: Msg 40536, Level 16, State 2, Line 1 'MEMORY_OPTIMIZED tables' is not supported in this service tier of the database.
Describe the solution or feature you'd like
Provide a setting for Service Tier during import.
Describe alternatives you've considered
I was able to work around this with a simple database by:

Start the *.bacpac import wizard
Select the *.bacpac and give it the name of a database which doesn't exist, but don't click "next"
Create the database with the appropriate tier setting
After the database is created, click "next" to continue the wizard

(This fails on more complex databases so is not a perfect workaround)
I've also advised working around this in powershell or AZ CLI, which exposes these options.
https://learn.microsoft.com/en-us/powershell/module/az.sql/new-azsqldatabaseimport?view=azps-9.4.0#-edition
https://learn.microsoft.com/en-us/cli/azure/sql/db?view=azure-cli-latest#az-sql-db-import

Adding to this, it should give a warning about this. Creating the database with default settings which may result in increased costs for testing databases and lower performance for production scenarios if the user is not aware of this and don't change the settings in the Azure portal/CLI afterwards.


How can i open local file using pdf.js ? i need this for create cordova application

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: cordova android 8.0.0
Operating system and its version: cordova android app
PDF.js version: pdfjs-2.4.456-dist
Is a browser extension: no

Steps to reproduce the problem:

i want to view a pdf file using pdf.js dist so that i can create a offline pdf reading app but it dont open local pdf file how can i fix this. is there any way to some code into my index html so that it can open default od any local pdf ?
i just want to open a local pdf with pdf.js without any help of servers. i want to use something like file:///book.pdf without http:// or https:// is there any way? help me with that

What is the expected behavior? (add screenshot)
https://imgur.com/Zqbdw4V
What went wrong? (add screenshot)
https://imgur.com/arzBl2N
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Browsers by default disallow access to local files; refer to https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-xhr for solutions.

Is there any way to forcefully open pdf by using viewer.html from local? when i use open file button to select pdf then it can show pdf normally so i think there must be a way to do this. @timvandermeij please helm me with that i want to create cordova cross platform app using pdf.js and i don't want to use any other pdf reader.


Shows error if json body is empty

Hi,
While making a post request I gave the header as application/json but kept the body empty and and it resulted it
Unexpected end of JSON input.
Then I checked the code and saw that there is no handling if json body is ''. Probably you could add try catch for these errors.
Hoping an early fix.

What are the request headers?

Content-type set to application/json.

As seen in the code, I understood that json() only parses while this header is added and unless it doesn't

@Kamrulhasan12345 should it be able to parse empty body then? it already expects to have JSON from you

@talentlessguy Thanks for making concept correct. Now I understood that my concept was wrong. Sorry for disturbing you.


ets elastic transcoder pipeline example

hell there,
can someone advise how to use troposphere to create a aws elastic transcoder pipeline please? There is not an example in the repository.
Thanks,
Jianfang

I can't seem to find any example for elastic transcoder pipeline either.
If there is one could you let me know.
Thanks


API For Changing Sources

It'd be nice if something like player.source('some new url') could be called to stop and remove whatever is currently playing, then replace it with a new source without re-instantiating the player.  Fullscreen would be preserved if it was turned on, as would audio levels.

+1 for this. Might be related to: https://github.com/Selz/plyr/issues/3. A playlist would require the player to switch sources anyway.

Great idea. I'll look into it. It would need to accept an array I'd think for multiple formats as well. Easily done though.
Cheers!

+1

+1

Looking into this next as it fits well with playlists as @dvdheiden mentioned. Give me a day or two.

o/

Almost done with this. It'll go out later today.
Basically I've written the method so it'll take either:

A single string source
An object of attributes (src, type, etc)
An array of attribute objects

Depending on what's been passed will effect how it's rendered (src attribute on the element vs child <source> elements)
Does this sound about right? Currently working through some quirky Webkit behaviour and I'll merge it to master and push v1.0.22.
Cheers for the support :+1:

It sounds ok for me.

This should be fixed in v1.0.22 - let me know.
I ended up just accepting a string source which sets the src attribute on the video or audio element and also an array of objects which will output <source> elements with the provided keys as attributes.
Check out https://github.com/Selz/plyr#api for more info and let me know if you find anything wrong!


Respect smtp port when sending email

Fixes #87

Thanks a lot for all your contributions :heart:

Thanks @srid! This also solved it for me, i.e. #60


⚠ Bofrost.at has degraded performance

In b807199, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1822 ms

Resolved: Bofrost.at performance has improved in ce25661 after 6 minutes.


Bug find in exec rkt run, test result of rkt is not correct yet.

Bug find in exec rkt run, test result of rkt is not correct yet, because rkt can not return the error code  from the entry process,.
The bug will cause wrong success result of testing rkt.
I and @wangkirin  just fixing the bug.

@liangchenye @wangkirin  I have fixed the bug in my local git registry, using the another way of "rkt status" to replace using return code of "rkt run".
But I find another problem in using ocitool in the situation of rkt, just thinking about how to fix it.

@wangkirin Can u fix the bugs on ocitools/cmd/runtimetest to support RKT?
It is not support RKT yet, if u can fix it , it should be very nice.

@liangchenye @wangkirin The supporting of rkt have been work properly, but we have to fix some bugs in ocitools for rkt supporting later.

@zenlinTechnofreak Cool!
Do you plan to announce the OCT progress to OCI?


Issue 1082 - vscode settings file causes issues if not using Corretto or if Java 11 is not installed

Make sure you have checked all steps below.
Issue

[x] My PR addresses the following issues and references them in the PR title. For example, "Issue 1234 - My Sleeper
PR"

Resolves https://github.com/gchq/sleeper/issues/1082

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

No tests needs just an update to settings.json and the README

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it, or I have linked to a
separate issue for that below.

.vscode/README.md updated

I have tested this locally by moving my JAVA home settings to the machine settings file and left the vscode settings commented out. It loads and compiles in VSCode without any issues.


Move buildkite to new central

And use climacommon :)

Ok, one conceptual issue is that the threaded tests are being launched with --threads 8, and runsingleton does not take this into account. I think reverting the runsingleton change should fix this.

Ok, one conceptual issue is that the threaded tests are being launched with --threads 8, and runsingleton does not take this into account. I think reverting the runsingleton change should fix this.

I don't thinks that's the case. If we are not running with MPI (as in the threaded test), the context should be singleton. It is the device that would change to CPUMultiThreaded.

I don't think it's the problem we're seeing, but it is a conceptual issue: we end up reducing coverage if we don't run basic.jl in multithreaded mode.

I don't think it's the problem we're seeing, but it is a conceptual issue: we end up reducing coverage if we don't run basic.jl in multithreaded mode.

Singleton and mutli-threaded are not mutually exclusive.
This is how singleton is picked by ClimaComms.context:
function context(device = device())
    name = get(ENV, "CLIMACOMMS_CONTEXT", nothing)
    if !isnothing(name)
        if name == "MPI"
            return MPICommsContext()
        elseif name == "SINGLETON"
            return SingletonCommsContext()
        else
            error("Invalid context: $name")
        end
    end
    # detect common environment variables used by MPI launchers
    #   PMI_RANK appears to be used by MPICH and srun
    #   OMPI_COMM_WORLD_RANK appears to be used by OpenMPI
    if haskey(ENV, "PMI_RANK") || haskey(ENV, "OMPI_COMM_WORLD_RANK")
        return MPICommsContext(device)
    else
        return SingletonCommsContext(device)
    end
end

What I understand from this is that the context should be singleton when you are not running with MPI.

Singleton and mutli-threaded are not mutually exclusive.

I understand that, but Base.julia_cmd() in the launch
function runsingleton(file)
    Base.run(
        Cmd(
            `$(Base.julia_cmd()) --startup-file=no --project=$(Base.active_project()) $file`,
            env = ("CLIMACOMMS_CONTEXT" => "SINGLETON",),
        ),
    )
end

does not propagate multiple threads:
Base.julia_cmd(juliapath=joinpath(Sys.BINDIR, julia_exename()); cpu_target::Union{Nothing,String}=nothing)

  Return a julia command similar to the one of the running process. Propagates any of the --cpu-target, --sysimage,
  --compile, --sysimage-native-code, --compiled-modules, --pkgimages, --inline, --check-bounds, --optimize,
  --min-optlevel, -g, --code-coverage, --track-allocation, --color, --startup-file, and --depwarn command line arguments
  that are not at their default values.


Implement correct compact mode for SpaceInsideArrayLiteralBrackets

The compact mode for Layout/SpaceInsideArrayLiteralBrackets wasn't implemented according to the expected behavior in the tests, this PRs makes the relevant fixes for the tests to pass.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Nice!


Remove REQUEST_INSTALL_PACKAGES permission from my project

Google rejects my app updates because of REQUEST_INSTALL_PACKAGES permission. When i have checked it was inside the open_file package that is located  ->> /flutter/.pub-cache/hosted/pub.dartlang.org/open_file-3.2.1/android/src/main/AndroidManifest.xml.
I cleaned the project with 'flutter clean' and removed that package manually.(even replaced it with open_file_safe package ).
But when I run the project or build appbundle, it will appear again.
inside pubspec.yaml file, there is no such package.
I'm going to delete that permission, so that google accepts my next app updates.

I have attached that package's AndroidManifest.xml file.

@Lazizbek97

inside pubspec.yaml file, there is no such package.

There may be another package using open_file internally. You can check the Merged Manifests portion of the AndroidManifest.xml to see if you find that permission is being used in your project.
Please see old related issues: #108011, #111947 that may help you find clues. Also, I find there is an open issue on open_file repository that addressing this case: https://github.com/crazecoder/open_file/issues/204.
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it. Thanks!


feat: VideoTexture support video from scene's file

What?
support loading video files from scene
mp4, mov, ogg, webm

Can we have a little test scene with a small video to know exactly how this is supposed to be used?

I will add a test scene about in next PR when adding new functionalities to the video... I sent this PR so I don't send a big PR later


Fix coordinates

Pull Request
Description

Fix the OSGB coordinates issue: Use the original x and y geostationary coordinates as the 'main' coordinates. Also add a 2D x_osgb coordinate, and a 2D y_osgb coordinate.
Serialize the dataarray.attrs in a way that makes all the information easy to recover from the Zarr.
Fix the ordering of the GEOGRAPHIC_BOUNDS.

How Has This Been Tested?
py.test runs and the GitHub actions CI tests pass.  (Well, the linting doesn't pass, but that'll be fixed separately in issue #54)

[ ] No
[x] Yes

Checklist:

[x] My code follows OCF's coding style guidelines
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have checked my code and corrected any misspellings

Thanks for the very quick review!
Before re-running the script, we should probably implement issue #59... (which should speed things up a bit).
When you do run the script, please give me a shout when a month of Zarr data is ready, and I'll have a poke around the Zarr to make sure this PR hasn't broken anything!

No problem! And yeah, I can add a quick thing for that before I start the script

That is being fixed in #60


Can not link a calendar

I try to link a calendar in the settings by pressing the "+" button. When I hover over the button, it changes to a forbidden sign "   ⃠" (barred circle).
Is there a setting to change to enable that?

Can you share a video showcasing the error? We're unable to reproduce on our end

Thank you for your quick reply.
Can you read this file?
Hope this helps.
Best
Le dim. 7 janv. 2024 à 13:44, David Vargas @.***> a
écrit :

Can you share a video showcasing the error? We're unable to reproduce on
our end
—
Reply to this email directly, view it on GitHub
https://github.com/RoamJS/google/issues/24#issuecomment-1880049712, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BCPCYFTBZMLW7TWOZBO7EILYNKKD5AVCNFSM6AAAAABBQFP6WGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBQGA2DSNZRGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


Release version 0.0.13

Codecov Report
Patch and project coverage have no change.

Comparison is base (77b090a) 100.00% compared to head (529638f) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #249   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          315       315
  Lines         9714      9714
  Branches       949       949
=========================================
  Hits          9714      9714

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


[Feature Request] Add ability to modify devirt-type by providing props mapper

Let's imagine you want use data-devirt-type as selector for auto tests and you have case:
devirt();
const Button = ({children}) => <button>{children}</button>

const Form = () => (
    <form>
        <Button>Save</Button>
        <Button>Cancel</Button>
    </form>
);

This code will produce:
<form data-devirt-type="Form">
    <button data-devirt-type="Button">Save</button>
    <button data-devirt-type="Button">Cancel</button>
</form>

Will be cool to have ability add suffix to devirt type
devirt(Target, ({ testContext }) => ({ testContext }));
const Button = ({children}) => <button>{children}</button>

const Form = () => (
    <form>
        <Button testContext="save">Save</Button>
        <Button testContext="cancel">Cancel</Button>
    </form>
);

<form data-devirt-type="Form">
    <button data-devirt-type="Button::save">Save</button>
    <button data-devirt-type="Button::cancel">Cancel</button>
</form>

This approach could be automated by provided name prop from field hoc and so on.

Done


Modify Trapezium working.

Is your feature request related to a problem? Please describe.

In trapezium under calculator for shapes, it asks user to input height as well as all sides .

Describe the solution you'd like
-if user inputs all sides , we can find height using heron's formula and then equate accordingly.
I would like to add working of finding height and then accordingly using it to find area, perimeter.

Go ahead
Deadline 11 April,2021 11:59 PM IST

I have added.
Please have a look

i have added reference image also.

Is it okay? @sairish2001

put image at top of the modal, as it is in other modals

Image is already there at the top,

should i replace it or add (then there will be 2 image)?

@sairish2001

Remove your image and go ahead with PR


[Tests] Fixes random test failures

PR Details
Description
Some of the tests in Stride.GameStudio.Tests must not run in parallel as they access a shared class which is not thread safe.
Related Issue

Motivation and Context

Types of changes

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

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] I have built and run the editor to try this change out.

@Kryptos-FR I've updated the PR.

@Kryptos-FR Done

Looks like the tests passed fine. Thanks.


Only disallow hyphens in lib target names

Examples, tests, binaries, etc, are all allowed to have hyphens (cargo does some
renaming internally).
 Was about to open a PR for https://github.com/oferrigni/cargo/commit/2c819c0108b780e30396dc003bfb69739faaab8f

r=me with or without changing the function name (your choice).
(Travis failed, but it looks rather spurious.)

@bors: r=huonw 3a7d175

:hourglass: Testing commit 3a7d175 with merge 00b99e0...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32, cargo-win-64


Create a pre-defined temporal train/test/val split

We should require everyone using the benchmark to use it under the same challenge setting. That means we should have it preconfigured to do the train/test/val split.
Have the data already separated in an easy-to-use format.

I had a similar function that did the same thing in my notebook. We can let user decide the distribution of train/test/val? We can find a day to cut that will approximate the distribution so the data is cut at the end of each day.

I had a similar function that did the same thing in my notebook. We can let user decide the distribution of train/test/val? We can find a day to cut that will approximate the distribution so the data is cut at the end of each day.

We can create a function that lets the user decide, but we should make a setting to get the predefined splits so that everyone is working on the same benchmark.
Similar to how the data loader classes work for pytorch geometric:
https://pytorch-geometric.readthedocs.io/en/latest/generated/torch_geometric.datasets.Planetoid.html#torch_geometric.datasets.Planetoid
Essentially, specify where the data should be saved, which specific dataset you want (by name), and which split of the data you want (train/test/val).


Some questions in the dataset are wrong with {tail2}

Hi! @apoorvumang Amazing work here!
I found that some questions in the dataset with the type of "time_join" are wrong, in which there's a {tail2} in the template that is not correctly mapped. Some examples are:
"When Q300269 was the Q37303731 , who was the {tail2}"
"Who was {tail2} when Q6105302 was the Q41582582"
I wonder if there are some problems with templates like the following or something else?
"Who was the {tail2} when {head} was the {tail}"
Thanks!
Best,
Yonghao

Hi Yonghao
Thanks for your interest!
Yes this question template unfortunately did not get filled properly during dataset construction, and there exist some faulty questions like you mentioned. We will fix these in a v2 of the dataset, but in order to keep consistency in the reported numbers we are not changing anything in the current version.

Thanks a lot! Looking forward to v2 :)

Closing issue here, but will leave it pinned since its important

In v2 training data, 'uniq_id': 119922 still contains tail2. How could I fix it?

KeyError: Caught KeyError in DataLoader worker process 0.
Original Traceback (most recent call last):
File "/home/jupyter/miniforge3/envs/env8/lib/python3.8/site-packages/torch/utils/data/_utils/worker.py", line 308, in _worker_loop
data = fetcher.fetch(index)
File "/home/jupyter/miniforge3/envs/env8/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 51, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/jupyter/miniforge3/envs/env8/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 51, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/jupyter/workspace/CronKGQA-main/qa_datasets.py", line 372, in getitem
head = data['head'][index]
KeyError: 'head'

have same error，did you fix it?

Yes, in each question dictionary, there are two keys: "template" and
"question" (I cannot remember clearly). One shows a question like "Who is
the {head} of {tail}", one shows a question like "Who is the Q124 of Q456".
You can identify {tail2} by matching these two. The sequence of each word
is the same in them.
On Fri, May 19, 2023 at 11:09 AM liwenju0 @.***> wrote:

have same error，did you fix it?
—
Reply to this email directly, view it on GitHub
https://github.com/apoorvumang/CronKGQA/issues/13#issuecomment-1553939091,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKVPXQPIOFNNIULESXVSRFTXG3QAPANCNFSM5LX34PAQ
.
You are receiving this because you commented.Message ID:
@.***>


How can I fix this problem?

Now every time you die in the game, the skin will be replaced with the original skin.

i have the same problem

me too

me too

Commit 9928813 fixes the problem.


Game uploaded , Readme added, SS uploaded

PR Description 📜
String game using HTML,CSS Javascript
Fixes

Mark the task you have completed ✅

[ ] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[ ] I have performed a self-review of my own code or work.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] My changes generates no new warnings.
[ ] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[ ] I have added screenshot for website preview in assets/images
[ ] I have added entries for my game in main README.md
[ ] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[ ] I have specified the respective issue number for which I have requested the new game.

Thank you soo much for contributing to our repository 💗

Thank you @kushaljgec2025 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Hey @kushaljgec2025,
Please make sure to link the relevant issue using the appropriate syntax, such as "#issueNumber" 👀.
Follow the proper guideline and make a new PR again 😀.
Happy Hacking 💗

Thank you  @kushaljgec2025 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Misstransration about "advisories" for Japanese article

The word of "Advisories" translates to "アドバイザリ" in Microsoft Admin Center.
But now, the word of "Advisories" translates "勧告" in the below article.

https://docs.microsoft.com/ja-jp/office365/enterprise/view-service-health?source=docs#incidents-and-advisories
Could you check and fix it?
Thank you!

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

ID: dd2a834a-296b-1c7d-7358-6f6a19f8f3c3
Version Independent ID: 9ab6adbe-c651-d833-f395-64b7cddb2dd2
Content: How to check Office 365 service health
Content Source: Enterprise/view-service-health.md
Service: o365-administration
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@kefujino - Thank you for submitting feedback.
I will get this issue over to the Enterprise writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@officeglobal @tinamcN - Can you please assist with this Translation/Localization issue?
Thank you.

Working on a fix

@OfficeGlobal - Do you have any updates on this?
Thank you.

@OfficeGlobal - Please update the status.Thanks