Lots of warnings when building project with Vite 5, Material UI and sourcemaps enabled

Describe the bug
When running vite build in a React project that uses Material UI components and is set up to emit sourcemaps, lots of warning messages of the type<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error. are printed.
This issue appeared first with Vite 5.0.0, everything worked fine in Vite 4.5.0.
(If this is an actual issue of Material UI which was now discovered by Vite 5 for the first time, please let me know so I can report it there. But since everything worked fine before upgrading to a new major version of Vite, I report it here first.)
Reproduction
https://github.com/marvinruder/vite-warn
Steps to reproduce
Open the repository in a GitHub Codespace, then run npm install followed by npm run build.
System Info
System:
    OS: Linux 6.2 Ubuntu 20.04.6 LTS (Focal Fossa)
    CPU: (2) x64 AMD EPYC 7763 64-Core Processor
    Memory: 5.93 GB / 7.74 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 20.9.0 - ~/nvm/current/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 10.1.0 - ~/nvm/current/bin/npm
    pnpm: 8.10.2 - ~/nvm/current/bin/pnpm
  npmPackages:
    @vitejs/plugin-react: 4.2.0 => 4.2.0
    vite: 5.0.0 => 5.0.0

Used Package Manager
npm
Logs

Click to expand!
vite v5.0.0 building for production...
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
✓ 1012 modules transformed.
dist/index.html                  0.24 kB │ gzip:  0.19 kB
dist/assets/index-fH2xQxY4.js  215.15 kB │ gzip: 71.89 kB │ map: 730.91 kB
✓ built in 6.34s

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 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.

having the same problem with other packages too. i.e react-query

Seems like it's coming from Rollup. It's likely not a bug in @material/ui. Linking Rollup locally, the error is coming from here.
The original error is this:
{
  code: 'MODULE_LEVEL_DIRECTIVE',
  id: '/Users/bjorn/Work/repros/vite-warn/node_modules/.pnpm/@mui+material@5.14.18_@emotion+react@11.11.1_@emotion+styled@11.11.0_react-dom@18.2.0_react<EMAIL_ADDRESS>  message: 'Module level directives cause errors when bundled, "use client" in "node_modules/.pnpm/@mui+material@5.14.18_@emotion+react@11.11.1_@emotion+styled@11.11.0_react-dom@18.2.0_react<EMAIL_ADDRESS>was ignored.',
  pos: 0
}

The pos and location in the linked Rollup code is 0 and { line: 1, column: 0, character: 0 }. Seems like an issue at here. We should maybe also ignore the use client warnings in the first place but that's another issue.
A workaround for now:
  build: {
    sourcemap: true,

    rollupOptions: {
      onLog(level, log, handler) {
        if (log.cause && log.cause.message === `Can't resolve original location of error.`) {
          return
        }
        handler(level, log)
      }
    }
  },

@bluwy plugin-react does ignore the warning (https://github.com/vitejs/vite-plugin-react/blob/3748fc7493cf0a07a2ae275fbd1ae035f01010cc/packages/plugin-react/src/index.ts#L307-L323).

The issue upstream at rollup is pretty much stale in my opinion - the last member commented on June 8th 2023..
Additionally a member of rollup suggested to either install a plugin or to use a workaround (as suggested here) to fix this.
He even commented this:

Yes, imports are removed and completely rewritten in the finalizers. To preserve directives, one would need to pass the directive to the finalizer, which is a bigger refactoring of the Rollup code base.

So i wouldn't have too much hope in the issue getting fixed upstream soon..
Now with the things i pointed out let's get to the question i wanted to ask in the first place.
How much willpower do you guys have to handle the warnings in vite itself without the need of the workaround?
Would hate to apply the workaround and then find out you handled the issue in vite itself few days later...
Note:
plugin-react does ignore some of the warnings but in our case at autobrr our warning messages do not contain
use client so we still get warnings during building and we use plugin-react-swc anyway..
(Haven't looked if some of these warnings are handled in plugin-react-swc to be honest)

There's not much to be fixed in Vite if I understand the issue. Someone would need to debug what happens in https://github.com/rollup/rollup/blob/1df8b4924f014e0cabd4c0364370801a658cc489/src/utils/getOriginalLocation.ts#L10-L27 that's causing the error. Maybe it's a bug in that code, or Vite is generating incorrect sourcemaps that's tripping it up.

Little plugin to ignore those pesky warnings
const muteWarningsPlugin = (warningsToIgnore: string[][]): Plugin => {
  const mutedMessages = new Set()
  return {
    name: 'mute-warnings',
    enforce: 'pre',
    config: (userConfig) => ({
      build: {
        rollupOptions: {
          onwarn(warning, defaultHandler) {
            if (warning.code) {
              const muted = warningsToIgnore.find(
                ([code, message]) =>
                  code == warning.code && warning.message.includes(message),
              )

              if (muted) {
                mutedMessages.add(muted.join())
                return
              }
            }

            if (userConfig.build?.rollupOptions?.onwarn) {
              userConfig.build.rollupOptions.onwarn(warning, defaultHandler)
            } else {
              defaultHandler(warning)
            }
          },
        },
      },
    }),
    buildEnd() {
      const diff = warningsToIgnore.filter((x) => !mutedMessages.has(x.join()))
      if (diff.length > 0) {
        this.warn(
          'Some of your muted warnings never appeared during the build process:',
        )
        diff.forEach((m) => this.warn(`- ${m.join(': ')}`))
      }
    },
  }
}

const warningsToIgnore = [
  ['SOURCEMAP_ERROR', "Can't resolve original location of error"],
  ['INVALID_ANNOTATION', 'contains an annotation that Rollup cannot interpret'],
]

export default defineConfig(({ mode }) => ({
  plugins: [
   ...
    muteWarningsPlugin(warningsToIgnore),
  ],

Also tells you what message were not needed  @martylukyy as  it was a concern of yours.

Rollup tries to map the position to the original position using the source map generated by esbuild (used by Vite to handle define option). But because the source map doesn't contain the mapping for the directive, Rollup fails to output the warning with the original position. I made a issue to esbuild about this (https://github.com/evanw/esbuild/issues/3548).

Hello,
We're hit by this too since the addition of sourcemap: true in our Vite configuration. Anything I can do to help?
Cheers,
David

same issue without setting sourcemap config in vite.config.ts

@cgaube Nice trick, thanks a lot!  However I get:
(!) Plugin typescript: @rollup/plugin-typescript TS2353: Object literal may only specify known properties, and 'enforce' does not exist in type 'Plugin'.
vite.config.ts: (35:5)

35     enforce: 'pre',
       ~~~~~~~

The other workaround from @bluwy fails for me like this:
(!) Plugin typescript: @rollup/plugin-typescript TS2339: Property 'message' does not exist on type 'unknown'.
vite.config.ts: (77:36)

77         if (log.cause && log.cause.message === `Can't resolve original location of error.`) {
                                      ~~~~~~~

I m getting same error when I try run yarn run build then  this erro ( error<EMAIL_ADDRESS>(1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error. ) as well  m unitest showing too much uncovered lines

and I have same update version vite -5.0.8

For now, this is what I have done to silence the warning.
  ...
  build: {
    sourcemap: true,
    rollupOptions: {
      onwarn(warning, defaultHandler) {
        if (warning.code === 'SOURCEMAP_ERROR') {
          return
        }

        defaultHandler(warning)
      },
    },
    ...
  }

I'm not sure if that's the case for anybody else but I have the same errors and the resulting source maps are completely wrong (i.e. errors in the built code don't map at all to the real source code, and funnily enough all map to a file whose name is within these warnings), I believe that this warning is a sign of something happening and corrupting these source maps.

same issue. We cannot use source-map-explorer for bundle analysis

Hey guys, so are we doomed with this issue? As a consumer of both mui and react-query we see lots of these warnings during builds... Anything I can do to help?

I was also receiving this issue when I have sourcemap: true however it was also causing my build to crash.
In my case I'm using AntDesign which also makes use of the use-client directive, similar to MaterialUI.
Running vite build with sourcemap: true I'd get
....
// Lots more similar errors
node_modules/antd/es/table/hooks/useFilter/FilterWrapper.js (1:0) Error when using sourcemap for reporting an error: Can't resolve original location of error.
✓ 3357 modules transformed.
rendering chunks (5)...
<--- Last few GCs --->

[5698:0x158008000]    18390 ms: Mark-Compact 2019.6 (2085.0) -> 2013.3 (2095.1) MB, 1008.67 / 0.00 ms  (average mu = 0.407, current mu = 0.193) allocation failure; scavenge might not succeed
[5698:0x158008000]    20420 ms: Mark-Compact 2019.1 (2095.6) -> 2016.9 (2098.4) MB, 2002.54 / 0.00 ms  (average mu = 0.176, current mu = 0.013) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 0x100d80bf4 node::Abort() [/Users/.../.nvm/versions/node/v20.10.0/bin/node]

If I set sourcemap: false my build would work fine.
What helped my build process complete was putting the antd dependency into its own chunk - it still logs the errors but I think that can be dealt with separately using some of the suggestions above.
  build: {
    sourcemap: true,
    outDir: 'build',
    rollupOptions: {
      output: {
        manualChunks: {
          antd: ['antd'],
        },
      }
    }
  },

I don't have a great explanation as to why this works but it seems to so hopefully it might help some others facing similar 🤷

@rowanwins
U can get away from the heap error with sourcemap: true enabled, if u change the build command as: export NODE_OPTIONS=--max-old-space-size=8192 && vite build

For my situation (ant-design sourcemap), this issue can be bypassed using the plugin rollup-preserve-directives.
The solution is taken from: https://github.com/pmndrs/jotai/issues/2269#issuecomment-1826427962

So the core of the issue is that Rollup is removing JavaScript directives such as "use client"?
Indeed the warnings went away after using this plugin https://github.com/huozhi/rollup-preserve-directives.
That plugin seems to tax build time quite a bit though. I suspect you're going to have more people land on this issue as more libraries update for React Server Components.

What's the current status here? Is it simply to disable source maps? Is a fix incoming/scheduled?

For now, this is what I have done to silence the warning.
{
  build: {
    sourcemap: true,
    rollupOptions: {
      onwarn(warning, defaultHandler) {
        if (warning.code === 'SOURCEMAP_ERROR') {
          return
        }

        defaultHandler(warning)
      },
    },
  }
}

too dirty

This error happens while using shadcn ui. I build two more projects but none of them cause any issues. I had no clue how can I fix this.

This error happens while using shadcn ui. I build two more projects but none of them cause any issues. I had no clue how can I fix this.

maybe u can use this solution
{
  build: {
    sourcemap: true,
    rollupOptions: {
      onwarn(warning, defaultHandler) {
        if (warning.code === 'SOURCEMAP_ERROR') {
          return
        }

        defaultHandler(warning)
      },
    },
  }
}

Having the same issue with shadcn, it seems the error is thrown if there is "use client" directive on top of the component

Having the same issue while using the Shadcn UI, searched the gpt for this issue it's also not able to resolve anyone knows please help?

@alpharsh The best answer for now is to use the answer posted above by @cgaube. I've had this in place since last year, and it still works great. See comment https://github.com/vitejs/vite/issues/15012#issuecomment-1825035992.

I'm having the same issue in svelte I treid the rollup but noting, anyone know how to hide this warning in terminal


feat: Add checks for title and description in intent extras. (#1273)

In case other apps want to send a title and description along with the
image, we check if those have been passed as intent extras and set the
EditText values accordingly.
Fixes: #1273
See also: #892

Codecov Report

Merging #1292 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1292      +/-   ##
=========================================
- Coverage    3.77%   3.77%   -0.01%
=========================================
  Files         125     125
  Lines        5881    5886       +5
  Branches      579     581       +2
=========================================
  Hits          222     222
- Misses       5644    5649       +5
  Partials       15      15

Impacted Files
Coverage Δ

.../free/nrw/commons/upload/SingleUploadFragment.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks @yashshah7197


Add go.mod and go.sum files

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


[DO NOT MERGE] Remove keycloak syncing

To be merged as last PR in the branch, after stopping keycloak.

I think you'll also need to remove the related specs for the removed code, as well as the Keycloak stubbing in Rspec and the user/team/org setup methods in Minitest.

I have searched the code and I think we need to refactor the tests in psd-web/test/controllers/teams_controller_test.rb as they are using/stubbing the Keycloak clients. We might choose to do this separately. Apart from that it should be good to go.


Add SendGrid documentation to SendGridOut

We need to add documentation to the SendGridOut doc. Specifically, we should mention you need to set an App Setting for it to work, or you'll get host errors.

#496


Jnolley/overlay UUID callchain

Pull Request Checklist

[ ] Did you pull latest and merge develop (or master) into your branch?
[ ] Did you add tests?
[ ] Did you run the front-end tests (if applicable)?
[ ] Did you run the back-end tests (if applicable)?
[ ] Did you include screenshots or a demo video (if applicable)?
[ ] Did you include a descriptive title and description with your PR?
[ ] Did you perform a self-review before assigning reviewers?

https://github.com/user-attachments/assets/d12002e3-835f-451e-938b-cfa3a3c43957


Footnote: formatting, hyperlinks

Footnotes — in the same syntax as on GitHub — do show up. However,

the default formatting doesn't shift the footnotes to the bottom of each page. I can probably fix this on my own in CSS.
the HTML of the footnotes contains appropriate anchors (so you can jump from the text to its explanatory footnote, and back), and these show up visually in the PDF, but don't seem to have a hyperlink action in the PDF

(Note that Azure DevOps Wikis itself doesn't yet have footnotes support anyway. However, it would be quite nice to have this in PDFs.)

I want to bring this tool to GitHub Actions and of course then convert GitHub wikis... so thanks for sharing!

Please do give it a try - please let us know if it works or not.
I started to work on this for #80 - same problem and is solvable. Not sure when tho.


Improve the «3D Secure» configuration section

The current state is here: [AlphaCommerceHub] Extension settings

I need to clarify the following questions first:

[AlphaCommerceHub] What will happen if a not configured for 3D Secure merchant will pass 3DSecureBypass = N in an AlphaHPP request?
[AlphaCommerceHub] What will happen if a not configured for 3D Secure merchant will pass 3DSecureBypass = Y in an AlphaHPP request?

The questions above are answered!
I continue to work on this task.

An improved form:

Implemented in https://github.com/mage2pro/alphacommercehub/releases/tag/0.6.9.


Add option to persist instance between reboots

An opt-in option for platform-specific startup scripts.

The original comment was https://github.com/ipfs/electron-app/pull/13#discussion_r32900249

Separately, i think we want to add two checkboxes to this initial "setup dialog":

[ ] Add IPFS Node to Login Items[0]. This opens the IPFS menubar item. If it is switched to "On", it will also start your IPFS Node.[1]

[0] this is platform specific. may need different language per platform.
[1] there's got to be a better, simpler way to say this. the tricky part is it must capture (a) the on/off switch, (b) "IPFS Node" app remembering the state user left it in (on/off), (c) that it will start the IPFS node iff the node was left "On". (all without being too verbose. design is hard :) ).

not sure if we mean the same thing ("persist instance between reboots"). i just mean an option for the daemon to be launched on startup


Pod historical metrics API PoC

This PR is meant to start discussing / designing historical metrics API.
It adds the sinceSeconds query parameter,  to the existing metrics API, that enables to specify the duration before the current time from which to retrieve historical metrics for pod resources usage (CPU and memory as defined in the Metrics API).
It provides a public API for retrieving events from long-term storage and can be queried with:
$ kubectl get --raw /apis/metrics.k8s.io/v1beta1/namespaces/kube-system/pods/metrics-server-689bb87859-725wx?sinceSeconds=120
{"kind":"PodMetricsList","apiVersion":"metrics.k8s.io/v1beta1","metadata":{},"items":[{"metadata":{"name":"metrics-server-689bb87859-pnr2f","namespace":"kube-system","creationTimestamp":"2018-05-22T13:52:03Z"},"timestamp":"2018-05-22T13:51:00Z","window":"1m0s","containers":[{"name":"metrics-server","usage":{"cpu":"0","memory":"14148Ki"}}]}]}

It enables basic dashboarding of historical data, e.g.:

This PR provides the working basis on which to iterate on the design of an historical API. With this, It would be possible to implement an API compatible with that of Hipster, as documented in  https://github.com/kubernetes/heapster/blob/master/docs/model.md#cluster-level-metrics, if that's the chosen direction, so that it'd be a drop-in replacement for Dashboard.
For practical reasons, the types are defined in the github.com/kubernetes-incubator/metrics-server/metrics/api/v1alpha1 package.
/cc @brancz

Thanks for taking a stab at this. Fundamentally I am not sure whether the historical metrics API can be implemented by the metrics-server, as is changes some assumptions made in terms of scalability of the metrics-server, meaning the size of data kept in memory now multiplies by time, not only # of nodes + # of pods/containers. This sounds like it would violate the scalability requirements we have on the metrics-server.
Aside from that it is unclear what extend the historical metrics API should have. We have a discussion scheduled on it for the next meeting, I encourage you to join (but I also encourage everyone to write their opinions here).
Once we have a better idea on a historical metrics API, I would prefer to start with a design doc on the features repository, as this is going to involve sig-autoscaling as well as the dashboard.
@piosz @DirectXMan12

@brancz Thanks for the feedback. I agree with you.
Regarding the scalability requirements, that would indeed scale linearly (or approximately) with the number of extra data points, that is the long term store time window / resolution. With the default configuration, that would be a factor of 15 (15 minutes window, and 1 minute resolution).
Whether short-term historical metrics API is served by the metrics-server or not, I tend to think it'd be valuable that such an API be available to clients, out-of-the-box on most cluster setups, in the form of an aggregated API. Scalability requirements being mitigated with configuration parameters and sensible defaults. Or, that the deployment of such an API does not require cluster admin permission and can accommodate multi-tenancy.
If you agree, I'd be inclined to keep that PR open until discussion has started and / or other people comment on it, and close it once things have moved forward a bit.

Happy with keeping it open and starting the larger discussion.

I'd assert that this is not the right place to support the historical metrics API.  The metrics-server is supposed to have a very limited scope.  It happens to keep historical metrics right now due to legacy code, but that's going away shortly.
I'd love to have this discussion, but this is not the right place to do it.  We should have it in a design doc, in a PR in the kubernetes/metrics repository (where all metrics APIs are stored), etc.  Not in the repo of one implementation of one of the APIs.

Thanks for your feedback. Let's close this then and start discussing this in a design doc.


Getting bad request

Even after updating the firmware of my MKR1000, I get bad request as the errorReason(). Is there a way to get more detail on the errorReason() function; maybe an error code or solution?

The bad request  is from many reasons:

FIREBASE_HOST is not valid. Check it should not end with  / and should not start with http://
FIREBASE_AUTH is not valid.
You set or push the JSON serialized string which contains some invalid tokens or invalid characters that cause the invalid JSON.
The node path parameter contains invalid tokens or empty.

The above list is total possible reasons of this error.
It's better to post the code here to check.

Yea, here's the code:
#include "Firebase_Arduino_WiFi101.h"

FirebaseData firebaseData;

void setup() {
    Serial.begin(115200);
    delay(30000);
    Serial.println("Starting program");
    int status = WL_IDLE_STATUS;
    while (status != WL_CONNECTED){
        status = WiFi.begin(WIFI_SSID, WIFI_PASS);
        delay(300);
    }
    Firebase.begin(FIREBASE_URL, FIREBASE_TOKEN, WIFI_SSID, WIFI_PASS);

    String firstName;
    if (Firebase.getString(firebaseData, "firstName")) {
        firstName = firebaseData.stringData();
        Serial.println(firstName);
    } else {
        Serial.println(firebaseData.errorReason());
    }
}

void loop() {}

Things I've check so far:

FIREBASE_URL starts with https and does not include a trailing /
I assume FIREBASE_AUTH is my FIREBASE_TOKEN which is valid.
I've tried connecting it to other WiFi sources like my phone's hotspot but still returns the same error.

Yea, here's the code:
#include "Firebase_Arduino_WiFi101.h"

FirebaseData firebaseData;

void setup() {
    Serial.begin(115200);
    delay(30000);
    Serial.println("Starting program");
    int status = WL_IDLE_STATUS;
    while (status != WL_CONNECTED){
        status = WiFi.begin(WIFI_SSID, WIFI_PASS);
        delay(300);
    }
    Firebase.begin(FIREBASE_URL, FIREBASE_TOKEN, WIFI_SSID, WIFI_PASS);

    String firstName;
    if (Firebase.getString(firebaseData, "firstName")) {
        firstName = firebaseData.stringData();
        Serial.println(firstName);
    } else {
        Serial.println(firebaseData.errorReason());
    }
}

void loop() {}

Things I've check so far:

FIREBASE_URL starts with https and does not include a trailing /
I assume FIREBASE_AUTH is my FIREBASE_TOKEN which is valid.
I've tried connecting it to other WiFi sources like my phone's hotspot but still returns the same error.

Solved it! Thanks.

Solved it! Thanks.


depends as a List of Str may be to stupid

I am checking if a dep is already in a META6.json and with "Git::Config:ver<0.1.1>" that failed.
note BOLD "Dependency to $add-dep already in META6.json."; return) if $add-dep ∈ $meta6<depends>

Module descriptors may need their own type that know how to sort by version

I solved it but am not happy with the .split(':ver') part
multi sub MAIN(Str :$add-dep, Str :$base-dir = '.', Str :$meta6-file-name = 'META6.json') {
   my IO::Path $meta6-file = ($base-dir ~ '/' ~ $meta6-file-name).IO;
   my $meta6 = read-meta6($meta6-file) or die RED "Failed to process ⟨$meta6-file⟩.";

   sub simple-version(Str $s is copy) {
       my ($n, $v) = $s.split(':ver');
       with $v {
           $v = Version.new($v) if $v;
           $s = $n;
       } else {
           $v = Version.new(*);
       }
       $s but role :: { method version { $v } }
   }

   if my $stored-dep = ($meta6<depends>.grep: *.&simple-version eq $add-dep.&simple-version).first {
       if $stored-dep.&simple-version.version > $add-dep.&simple-version.version {
           note BOLD "Dependency to $add-dep younger then version already in META6.json.";
           return
       } else {
           $meta6<depends> = ($meta6<depends>.grep: *.&simple-version !eq $add-dep.&simple-version).Array;
       }
   }

   # (note BOLD "Dependency to $add-dep already in META6.json."; return) if $add-dep.&simple-version ∈ $meta6<depends>».&simple-version;

   $meta6<depends>.push($add-dep);
   dd $meta6<depends>;
   exit 0;
   $meta6-file.spurt($meta6.to-json);
}

depends may be a list, but it may also be a matrix of (build/test/runtime)/(requires/suggests/recommends) in the form of nested hashes. Individual entries may be strings or hashes with a "name" key and optionally additional information.
We are making progress on getting meta-version 1 as specified by S22 into the toolchain.


Wh acs new

@mbaldessari  Can you look at this CI error and tell me what's going on?

Yeah so we need to add two helm template outputs for each chart: the naked one (i.e. helm template without parameters) and the normal one (helm template with some parameters). I'll write something up for the others as well and I'll walk you through it on Monday

The latest commit works btw.  Let’s chat on Monday.  Turns out I needed to define the global.localClusterName in a values file and it gets over ridden. But one I figure that out (with Lester) o got it to work.
-William
ipbabble

On Apr 2, 2022, at 11:03 AM, Michele Baldessari @.***> wrote:

Yeah so we need to add two helm template outputs for each chart: the naked one (i.e. helm template without parameters) and the normal one (helm template with some parameters). I'll write something up for the others as well and I'll walk you through it on Monday
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.


Code cleanup and fixes

This pull request is not ready yet to be merged but it will be soon
The biggest changes are:

Require Dart version 3 as a minimum (migrate to it as well)
Fix the bug of the link reg exp, since it was always using the default instead of the custom one
Code cleanup

Hmm why automated publishing is not working

Hmm why automated publishing is not working

It needs more changes, I can test it more update it, and search for it more, I don't prefer using automated publishing as we should not publish many versions with every single version, I don't mind but users don't like this
let me know if you are still interested, I will test this on fresh_quill_extensions and when it works in efficient way I will bring it here

It is not totally automated.
You need to create a release in order to create a git tag and then is the automated publishing


{Compute} Bump up azure-mgmt-compute SDK to 24.0.0

Description

Bump up azure-mgmt-compute SDK to 24.0.0
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

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

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Compute


Illuminate\Support\Carbon does not accept Carbon\Carbon with ide-helper

Larastan Version: #.#.#
--level used: 5
Pull request with failing test:

Description
I don't know if i'm doing something wrong or i have a missing configuration, but running larastan on my project with the laravel-ide-helper package makes this error to appear in every single date from my models.

Hello @Sergiobop!
Could you please add some sample code of yours?

Hey @szepeviktor. I have a fresh laravel + ide-helper + larastan install and some models which looks like this:
<?php

namespace App\Models;

use Eloquent;
use Illuminate\Database\Eloquent\Collection;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Database\Eloquent\SoftDeletes;
use Illuminate\Database\Query\Builder;
use Illuminate\Support\Carbon;

/**
 * App\Models\Test
 *
 * @property int $id
 * @property string $name
 * @property Carbon|null $created_at
 * @property Carbon|null $updated_at
 * @property Carbon|null $deleted_at
 *
 * @method static \Illuminate\Database\Eloquent\Builder|Zone newModelQuery()
 * @method static \Illuminate\Database\Eloquent\Builder|Zone newQuery()
 * @method static Builder|Zone onlyTrashed()
 * @method static \Illuminate\Database\Eloquent\Builder|Zone query()
 * @method static \Illuminate\Database\Eloquent\Builder|Zone whereCreatedAt($value)
 * @method static \Illuminate\Database\Eloquent\Builder|Zone whereDeletedAt($value)
 * @method static \Illuminate\Database\Eloquent\Builder|Zone whereId($value)
 * @method static \Illuminate\Database\Eloquent\Builder|Zone whereName($value)
 * @method static \Illuminate\Database\Eloquent\Builder|Zone whereUpdatedAt($value)
 * @method static Builder|Zone withTrashed()
 * @method static Builder|Zone withoutTrashed()
 *
 * @mixin Eloquent
 */
class Test extends Model
{
    use SoftDeletes;
....

Running
./vendor/bin/phpstan analyse
Makes the error appear.
Bonus:
If i do:
$now = CarbonInmutable::now();
$model = new Test();
$model->created_at = $now->addDay();

The error transforms to:
Illuminate\Support\Carbon does not accept Carbon\CarbonInmutable

I see! If you remove all work of ide-helper it'll be okay.

What do you mean? I want to use both packages (which are awesome) in my development environment. Maybe the problem is that the ide-helper (and other Laravel internal files) use the Illuminate\Support\Carbon instead of Carbon\Carbon.
I think the Illuminate\Support\Carbon is not necessary now since Carbon is macroable itself, but i don't know for sure

What do you mean?

Remove all comments by ide-helper.
There are many issues regarding ide-helper: https://github.com/nunomaduro/larastan/issues?q=is%3Aissue+sort%3Aupdated-desc+ide-helper+is%3Aclosed
These two packages are not compatible.

Try using a Laravel-compatible IDE!

I use PhpStorm. If PHPStorm is not Laravel-compatible, let me know 😨

Try https://plugins.jetbrains.com/plugin/13441-laravel-idea
It costs one 🍔 each quarter.

Ok thank you for your time and your fast responses @szepeviktor 👍

I know this issue is closed, but I wanted to add a solution to the thread in case someone else runs into this and like me, they're working at a company and changing the package may be a bit more difficult.
You can still use ide-helper. Instead, you need to make sure the ide-helper config is published (see their github page for instructions) and then add an override to the config file under type_overrides for \Carbon\Carbon => \Carbon\CarbonInterface


Set up commands to add/remove profile pics and enable saving of pics in application

Procedure is as such, to add a profile pic:

Name your photo with the same title as the name that exists in addressbook. i.e. AlexYeoh.jpg if your name is Alex Yeoh in addressbook.
Use Setpath command to set your destination folder to import from. i.e. C:\Users\acer\Desktop\SE\profilepic\
Use Addpic command and select the person you want to add by the index
Image is updated and saved inside addressbook. Close and reopen the app, the image remains.
Use Delpic command to delete a profile pic from a contact.

Currently the requirement is to use only JPG files.

Coverage decreased (-0.8%) to 91.123% when pulling 946861d5be35e70adadb789082911e86b0127394 on jaivigneshvenugopal:save_image into 92d02e7c222538352b98e0c41540d06680814ef4 on CS2103AUG2017-T17-B1:master.

Coverage decreased (-0.8%) to 91.123% when pulling 49a0da738643088c2178a6f41174ac67553379c1 on jaivigneshvenugopal:save_image into 92d02e7c222538352b98e0c41540d06680814ef4 on CS2103AUG2017-T17-B1:master.

Coverage decreased (-1.05%) to 90.774% when pulling<PHONE_NUMBER>feebed70796b733dd5bfbdf1135d17 on jaivigneshvenugopal:save_image into 8aaec8b76bd64ab2f283983e58e06481989dc819 on CS2103AUG2017-T17-B1:master.


refactor: new dashboard with Next.js and MUI.

What type of PR is this?
/kind feature
What this PR does / why we need it:
A new dashboard with Next.js and Material UI.
Which issue(s) this PR fixes:

For #22
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

/lgtm


add timestamp

This would allow us to use this API
let data = stream.receive(upTo: 1024, timingOut: 1.second.fromNow)

I propose we also add byte, bytes, megabytes etc. So we can use this API:
let data = stream.receive(upTo: 1.kilobyte, timingOut: 1.second.fromNow)

I like this a lot, my only question is whether or not we need the global constants. Something about hour hanging out in the ether is a little strange, especially when it's so easy to do 1.hour, 1.second, etc.

I think we should get some opinions on the func and the constants, then whatever the verdict -> :shipit:

I see no problem in getting rid of the globals.

Got rid of the globals and moved to a different file. Need some more input on:
let data = stream.receive(upTo: 1024, timingOut: 1.second.fromNow)

vs
let data = stream.receive(upTo: 1024, timingOut: 1.second.fromNow())

I'll just go ahead and change to a function. I think now should become now() as well.
let then = now()
longComputation()
let interval = now() - then

LGTM, though personally I prefer indenting the code inside the #if blocks.

@paulofaria to use or not to use () is a tough one. I think the reason Apple uses it for lowercase() is because it's mutating? And property getters can't be mutating.
I'd say this fits within the realm of computed property. It's tough tho. I wish the guidelines were more clear (maybe I've missed something).

@tannernelson I think the function is better. They changed from lowercased to lowercased(). Makes sense to be a function.

Why do extensions return Int, not Int64?

Also, I vote for .fromNow(), because the result of this function varies, and it's make more sense for function than for property.

@tannernelson the strange thing about lowercased() is that it neighbors with capitalized which is a property, not a function. ¯_(ツ)_/¯

They return Int cause that's what apple recomends. You think we can have problems with this? How does Int work exactly? If the CPU is 32 bitsInt will be 32 bits? Is that it? If so, would we be in trouble casting Int64 to Int?

With never as a property we would have this?
let data = socket.receive(upTo: 1024, timingOut: .never)

would we be allowed to use .never as a default value for function parameters?

@paulofaria I don't know exactly what are the pros and cons of using Int instead of more specific ones, I just noticed that Venice is using Int64 for duration and Annecy is using UInt64, I just hope they will adopt Int fine.
About .never - yes, we would be allowed to use it as a default value (I checked :smile:). Swift static variables are nice, and I think .never is better than global variable (which are evil).

https://en.wikipedia.org/wiki/Year_2038_problem

I think we can use Int64 or even IntMax to be safe until the year<PHONE_NUMBER>72363u3949272636272i2u373628823y3y28

@paulofaria Int itself is a "A 64-bit signed integer value type", so I think it will be just fine. Or we can have UInt and don't worry about negative duration.

actualy UInt64 is better than Int64

For now, as I see, UInt and UInt64 are completely identical.

Because you have a 64bit OS. haha.

@paulofaria it seems logical that Int must be 32-bit on 32-bit systems, but Apple documentation is unclear about it, so I'm not sure :)
https://developer.apple.com/library/mac/documentation/Swift/Reference/Swift_Int_Structure/index.html

Anyway, I think UInt/`UInt64' are the best options, because then functions that take time will not have preconditions.

https://developer.apple.com/library/ios/documentation/Swift/Conceptual/Swift_Programming_Language/TheBasics.html#//apple_ref/doc/uid/TP40014097-CH5-ID309
Int

In most cases, you don’t need to pick a specific size of integer to use in your code. Swift provides an additional integer type, Int, which has the same size as the current platform’s native word size:

On a 32-bit platform, Int is the same size as Int32.
On a 64-bit platform, Int is the same size as Int64.
Unless you need to work with a specific size of integer, always use Int for integer values in your code. This aids code consistency and interoperability. Even on 32-bit platforms, Int can store any value between -2,147,483,648 and 2,147,483,647, and is large enough for many integer ranges.

I'll ask some apple guys about this. It would be awesome if we could ger away with just Int.

Oh, my bad, should've been more attentive. So, UInt it is? Or we stay with Int?

Joe Groff replied. It's 32 bits on 32-bit platforms. So we have to go for at least Int64 if we want our standard to live for more than 20 years. I think Int64 is fine. It will give us some billion years ahead.

@paulofaria nice! Anyway, maybe UInt64 will be better? Because really, I can’t think of what behavior we should expect from after(-1.second)

Yeah! makes sense. UInt64 is better.

maybe we could have problems with UInt64 when calculating intervals. timestampA - timestampB will underflow if B is bigger than A. So one would have to cast to Int64 when doing the operation. This could be enough of a pain. But on the other hand, unsigned (or abslotue) is really the most correct definition of an interval of time.

My opinion is that pain is better that undetermined state. Because someone can write a method that takes Int64, and if he doesn’t check that it’s absolute, we might have much more problems. Requiring UInt64 is surely more reliable than «always check if the value is absolute» documentation.

@tannernelson TimeRepresentable is created mostly for Int extensions. I don’t think it needs to be used anywhere else. More than that, it will lead to mistake. For example:
public init(for stream: Stream, timingOut deadline: TimeRepresentable)
It will be impossible to use init(stream: stream, timingOut: 1.second), because UInt64 itself is not TimeRepresentable.
I guess we only need to rename TimeRepresentable so it will be more clear. Maybe TimeRepresentor will be fine.

I agree with @dreymonde in both last arguments haha.

I'm fine with TimeReresentor.

Also, maybe it's better to rename to TimeIntervalRepresentor, because it actually doesn't produce time, but an interval of time.


get the code coverage of .vue files while running the project,  similar to istanbul

What problem does this feature solve?
Business vue code write unit tests is too inefficient, but the code needs coverage report。Using intanbul to get the coverage of the compiled js is ugly...wish to be supported
What does the proposed API look like?
vue.toCoverageVersionCode = true;
//return the code which contains some extends code which add to get the coverage data
vue.prototype.getCoverageData = () => {//return the coverage data}

Istanbul does support source map.
I don't think such utilities should be implemented in the core library.


@pixi/display documentation

Closes #6889

Codecov Report

Merging #6893 into dev will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               dev     #6893   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        15
  Lines          671       671
=========================================
  Hits           671       671

Continue to review full report at Codecov.

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

ReAdY fOr ReViEw guys 😃

cc @irongaze some new material added here that could be useful for the guides


Intent to release 7.0

I tackled everything I wanted to include in 7.0 (including all identified cancellation bugs).
I'll release it this week, unless someone brings up objections or suggestions in this issue.

Done in 1138974fc7dd003d6626faf0b5f3a13f3a44c13d, sdist is available on PyPI, wheels will be available shortly.
https://pypi.org/project/websockets/#files


Graphcache: mutations with different files in parallel, results lost

Describe the bug
Results get lost if you upload multiple files in parallel and use Graphcache.
Seems like it happens because of stringify in variables.ts in core package
If you will add
if (x instance File) {
  const key = cache.get(x) || Math.random().toString(36).slice(2);
  cache.set(x, key);
  return stringify({ __key: key });
}

everything works fine
Reproduction
https://codesandbox.io/p/devbox/mystifying-borg-g7zgym?file=%2Fsrc%2FFileUpload.jsx%3A22%2C1
Urql version
urql v4.0.6, urql/exchange-graphcache v6.5.0
Validations

[X] I can confirm that this is a bug report, and not a feature request, RFC, question, or discussion, for which GitHub Discussions should be used
[X] Read the docs.
[X] Follow our Code of Conduct

We used to do that before https://github.com/urql-graphql/urql/pull/3169 however that didn't work out. I guess the issue is that we are using operation.key in GraphCache for mutations while we decided a while ago to use a different type of _identity for that.
I guess this could be the cause for missing a few results with parallel identical (observably identical) mutations

I'm having a similar issue I think.
I like to use my client directly without a hook if I do not need the result state to be in the react tree.
I have a function that gets called in parallel to retrieve an upload URL from the backend:
mutation GetUploadUrl {
    getUploadUrl {
        path
        url
        __typename
    }
}

allUploads.map(getUploadUrl)

async function getUploadUrl() {
  console.log("before getUploadUrl");
  const { error, data } = await client
    .mutation(GetUploadUrlDocument, {})
    .toPromise();
  console.log("after getUploadUrl");

I notice that only the last result resolves the promise.
Is there a way to bypass this behavior for now?

@ursarik that does not reproduce for me, see attached screenshot

@JoviDeCroock looks strange
that's what I get. see attached screenshot

UPD:
I guess I figured out what happens in your screenshot.
Dunno how that happened simultaneously, but you selected two files twice, then pressed Upload twice, and then you got only 1 response from each selection(2 in total), but you should get 4 responses in total (2 responses from each upload).


node algorithm cant work with data larger then 1G

HKube micro-service
To which micro-service the bug related to, Dashboard ,Monitor-Server etc.
Describe the bug
when trying to work with data larger than 1G getting error
node: ../../nan/nan.h:890: Nan::MaybeLocalv8::Object Nan::NewBuffer(char*, size_t, node::Buffer::FreeCallback, void*): Assertion `length <= imp::kMaxLength && "too large buffer"' failed.
Info
1111/10/20 09:15:14Abo

zmq nodejs 5.x uses nan for the binding to c++. nan has a limitation 1GB when allocating node Buffer objects.
zmq nodejs 6.x (which is in beta for now) uses NAPI which allows the maximum size of Buffer in node (in node 14.8.0 it is MAX_LENGTH:<PHONE_NUMBER>, or 4GB)


setup.py

Can I send a pull request about packaging?

Hi @pylover ,
Yes, any changes or suggestions to make this code better are very appreciated.

Ok, I'll make a setup.py for this project


chore: deprecate aws-sdk instrumentation

related to #194 and https://github.com/aspecto-io/opentelemetry-ext-js/issues/169

@blumamir There's another reference in conventions.md:

aws-sdk is using http for the internal RPC requests to various services

it's just an example which is still valid, not a reference


Better message log while installing through quelpa

Right now the log is presented it as below.
https://github.com/jcs090218/jcs-emacs/blob/76202182461ef90ade0b32bfcb360ac95616d07f/.emacs.jcs/jcs-package.el#L437
The message is pretty straight forward, yet I think is better if I can use process reporter to improve the hanging experience while doing the installation.

This could also be an issue from quelpa due to my first attempt to log it with process reporter yet there is some process hampering the process reporter to work. 😕

quelpa has been replaced by github-elpa, see here.


[develop] Add indexer feature to Rosetta

See #15564

!ci-toolchain-me

!ci-toolchain-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me


Update to VuePress v2

VuePress v1 doesn't work well anymore with node 17+ it seems:
https://github.com/webpack/webpack/issues/14532

Fixed the node version in the CI to 16.x, but this means we also can't use it locally with more recent node versions:
https://github.com/Open-EO/openeo.org/blob/master/.github/workflows/actions.yml#L14


Consume InputType package from MGC instead of own input models in autoret.csharp

Library name
N/A
Please describe the feature.
In CodeModelConverter, we are converting CodeModel.yml from M4 output to input models, we should replace the existing input models with the package containing the input models from MGC.

This should be done when we finish the implementation of Azure plugin, by then we can remove most of the duplicated logic of input types in autorest.csharp.


Inconsistent/Unexpected Results: Sorting Query Results with Nulls in SQL Notebook

Issue Type: Bug
When SQL notebook query results return NULLs, "Sort Ascending" and "Sort Descending" functions in the query results table yield inconsistent and unexpected results.
Sample Query:
DROP TABLE IF EXISTS #Temp_A
DROP TABLE IF EXISTS #Temp_B;

CREATE TABLE #Temp_A
(
    id char(3),
    first_name VARCHAR(30)
)

CREATE TABLE #Temp_B
(
    id char(3),
    sales numeric(19,4)
)

INSERT INTO #Temp_A
VALUES
('1', 'eric'),
('2', 'bob'),
('3', 'sally'),
('4', 'joe'),
('5', 'nancy'),
('6', 'frank'),
('7', 'alice'),
('8', 'rico')

INSERT INTO #Temp_B
VALUES
('1', '200000'),
('5', '60000'),
('7', '750000'),
('4', '250000'),
('8', '130000')

SELECT
    a.id,
    a.first_name,
    SUM(b.sales) as Sum_Sales
FROM
    #Temp_A as a
    LEFT OUTER JOIN #Temp_B as b
        ON a.id = b.id
GROUP BY
    a.id,
    a.first_name
ORDER BY
    id ASC

Initial Results

Actual Results after "Sort Ascending"

Expected Results after "Sort Ascending"

Actual Results after "Sort Descending"

Expected Results after "Sort Descending"

I should note that the results seem to be inconsistent - after alternating between "Sort Ascending" and "Sort Descending" numerous times, eventually I am able to manipulate the results to this, with all NULLS finally grouped together, at which point a subsequent "Sort Ascending" or "Sort Descending" operation finally returns the desired result (after many clicks).

These results are unexpected, and can be difficult to catch when a query returns more than ≈ a dozen rows.
Azure Data Studio version: azuredatastudio 1.33.1 (0b9ef714c823d662815f441aec4a94eaa21940f8, 2021-11-04T17:45:15.872Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-10310U CPU @ 1.70GHz (8 x 2208)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.78GB (4.11GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

azdata-sanddance
msr
3.3.0

@alanrenmsft looks like this also affects query editor grids. Any idea what could be going wrong here?
Happy to look into this myself, got any pointers?

I'll take a look @chlafreniere


Remove internal module from d.ts file

I updated the dts-bundle-generator to dts-generator, which has options to exclude particular d.ts files.

@DrSammyD It seems all the issues could simply be solved with stripInternal: true on? If my assessment is correct, then what else did you find that required you to fix other parts?

@DrSammyD It seems all the issues could simply be solved with stripInternal: true on? If my assessment is correct, then what else did you find that required you to fix other parts?

I initially tried that, but I think that only works for properties not modules.

Good to merge @bigopon @DrSammyD ???

Unless @bigopon knows a way to strip internal for declared modules, I'm good.

Ill have a test one more time to9. If needed, ill commit based on @DrSammyD changes

This PR over at e2e tests should make main circleci pass https://github.com/aurelia/e2e-tests/pull/3#issue-296494897

@DrSammyD I resolved the issue here https://github.com/bigopon/aurelia-dependency-injection/commit/363635d09146a8637a77c853bc6165cccc6f7137#diff-ab4d9046ca9b8b80b3d5a561a7846b1eR2
Mostly it's just import the declaration into the main to propagate the extensions to other modules, instead of using
And please use dts-bundle-generator, it's used across all other plugins/repos of Aurelia. We would want to unify this.

Pop Pop!

One final look from @bigopon and we can get this in and released.

🎉

Lgtm 😀


⚠ Thumbnails API Endpoint has degraded performance

In 539b8fe, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 1739 ms

Resolved: Thumbnails API Endpoint performance has improved in 8a199d9 after 9 minutes.


Test Release KubeOne 1.8 - Test Cluster Upgrading on GCE

### GCE (Ubuntu)
- [x] `/test pull-kubeone-e2e-gce-default-stable-upgrade-containerd-external-from-v1.27.11-to-v1.28.7`
- [x] `/test pull-kubeone-e2e-gce-default-stable-upgrade-containerd-external-from-v1.28.7-to-v1.29.2`
- [x] `/test pull-kubeone-e2e-gce-default-stable-upgrade-containerd-from-v1.27.11-to-v1.28.7`

pull-kubeone-e2e-gce-default-stable-upgrade-containerd-external-from-v1.27.11-to-v1.28.7
failed with:
time="07:42:14 UTC" level=warning msg="Task failed, error was: runtime: .cloudProvider.external is enabled\ncluster is using in-tree provider. run ccm/csi migration by running 'kubeone migrate to-ccm-csi'"

tests have passed

We have to repeat v1.27 to v1.28 tests, see #3159
/reopen


Incorrect silkscreen for RXD

The pinout diagram lists RXD as P0.26, and the silkscreen says P25. P0.25 is the bottom most GPIO on the other side, also labeled P25, so I imagine the silk for the RXD pin should be P26

@nitz the silkscreen and examples are correct, but the pinout diagram need to be updated. Thanks for your feedback.


Issue #354: Add taint and untaint command

The TerraformTaintPlugin adds new parameters to a build for resources to taint / untaint. If nothing is specified, then the plugin does nothing. If a value is provided in one of the parameters, then the corresponding command will be ran prior to the terraform plan command. It also includes support for restricting the execution to a given branch or set of branches, as well as restricting based the origin repository of the code checked out in the workspace.
// Jenkinsfile
<EMAIL_ADDRESS>_

Jenkinsfile.init(this, env)

// This enables the "taint" and "untaint" functionality
// It will only apply to the master branch (default behavior)
// and will only apply if the current worspace code is checked out from the
// MyOrg/myrepo repository.
TerraformTaintPlugin.init()
TerraformTaintPlugin.onlyOnOriginRepo("MyOrg/myrepo")

def validate = new TerraformValidateStage()

def destroyQa = new TerraformEnvironmentStage('qa')
def destroyUat = new TerraformEnvironmentStage('uat')
def destroyProd = new TerraformEnvironmentStage('prod')

validate.then(destroyQa)
        .then(destroyUat)
        .then(destroyProd)
        .build()

Fixes #354

In the meantime, @duckpuppy, how would you feel about removing the onlyOnOriginRepo() functionality?  If it's really needed, it could be purely additive in a fast-follow PR.  Otherwise, the discussion in #356 might bring up a better alternative.

Looks good, :shipit:


Cannot add citations to figure legends

Trying to add a figure citation in a figure legend just adds a new space. For references, the ??? is not displayed but I was (once) able to get the pop-up list of references to appear; however I could not get the reference to actually insert (though the list did respond as if I was selecting things). I could not then get the reference list to reappear and after clicking about, I saw this error in the console:

(I think I may have reported this elsewhere so please delete if this is a duplicate issue!

Seems that we have forgotten to enable <xref> in the captions.

Assigning this to 2.0 milestone as a backlog item.

After further investigation, I found the source, and this can even be considered as critical.
doc.findAll() is not working for regular DocumentNodes yet. Thus, in this case, the citation manager does not consider xrefs inside figures.

Fixed via #1050


Priv'd intents requirements missing from README

On start:
 python gpt-discord.py
2023-11-14 15:59:27.105 INFO: logging in using static token
Traceback (most recent call last):
  File "gpt-discord.py", line 110, in <module>
    if __name__ == "__main__": asyncio.run(main())
  File "/usr/lib/python3.8/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "gpt-discord.py", line 109, in main
    async def main(): await discord_client.start(os.environ["DISCORD_BOT_TOKEN"])
  File "/home/someUser/.local/lib/python3.8/site-packages/discord/client.py", line 778, in start
    await self.connect(reconnect=reconnect)
  File "/home/someUser/.local/lib/python3.8/site-packages/discord/client.py", line 704, in connect
    raise PrivilegedIntentsRequired(exc.shard_id) from None
discord.errors.PrivilegedIntentsRequired: Shard ID None is requesting privileged intents that have not been explicitly enabled in the developer portal. It is recommended to go to https://discord.com/developers/applications/ and explicitly enable the privileged intents within your application's page. If this is not possible, then consider disabling the privileged intents instead.
2023-11-14 15:59:27.884 ERROR: Unclosed connector
connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0x7f1880b31220>, 36723372.991516)]']
connector: <aiohttp.connector.TCPConnector object at 0x7f187fd64e80>

Which intents do we need aside from  "message content intent" (already checked)?

Used some deduction here: Oddly, it requires ALL intents enabled. How come? I thought this bot only uses message.

Good catch, thanks! Just pushed a fix.


Resolves #18 - add in other files after tests run to get accurate covera...

arrgh - this closes the gap by covering (after the test run) any other files that should have been covered.
Hopefully this will keep folks moving while we step back and assess where this is going.
Dynamically annotating code in the browser leaves a few edge cases that are going to be tough to fix w/o hacking on other ember-cli bits (loader.js etc)
I have started toying with compile time coverage annotation - the upside is that it is super clean, the downside is that coverage testing is then an explicit act and not a browser checkbox
Oh, and this whole thing feels a bit dirty with globals popping etc

Yeah, that's fairly hacktastic, but I've said it before and I'll say it again - so is the rest of the project.  Thanks for keeping the project moving forward, hopefully we'll find time at some point to make it clean, but it's good to keep up the momentum!


Running Jellyfin LXC Update does not update to 10.10.x, breaking use.

✅ Have you read and understood the above guidelines?
Yes
📜 What is the name of the script you are using?
Jellyfin Media Server LXC
📂 What was the exact command used to execute the script?
update
📝 Provide a clear and concise description of the issue.
Jellyfin Server is currently operating on version 10.10x. Servers need to be upgraded to this version of Android TV based usage fails with error (You are using an older server version 10.9 which is no longer supported).
Executing Update in the Jellyfin LXC is triggering an update, however the server is not updating to 10.10.x
Attempting Sudo apt-get update and upgrade results in the following

The following packages have been kept back:
jellyfin jellyfin-server ubuntu-advantage-tools ubuntu-pro-client-l10n
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

⚙ What settings are you using?

[X] Default Settings
[ ] Advanced Settings

🖥 Which Linux distribution are you using?
Ubuntu 24.10
🔄 Steps to reproduce the issue.

Open Proxmox container console
Type Update

Expected functionality : Update script executes and upgrades server version.
Actual functionality: Update script executes and completes, but server is not updated.
❌ Paste the full error output (if available).
N/A
🖼 Additional context (optional).
No response

OK typical I finally got it working
sudo apt-get dist-upgrade got it working

OK typical I finally got it working
sudo apt-get dist-upgrade got it working


Doubt about Race Condition in Second Notebook

If Python has GIL (which prevents race condition & creates thread safety), then how come the multi-threaded program in notebook2 resulted in a wrong value of COUNTER?
I am guessing the example was wrong because for me, I let the threads execute fully before running the assert statement. (Code below):
Cell 1
import time, random, threading
Cell 2
# Race Condition example (Part 1)
COUNTER = 0

# Race Condition example (Part 2)
def increement(n):
    global COUNTER # Use the global variable declared above
    for _ in range(n):
        COUNTER += 1
        time.sleep(0.001)
    print( f"\n{threading.current_thread().name} finished counting")

ITERATIONS = 100000 # set no of iterations to increase counter

# create 10 threads each set to run the increement() function for 1k iteations
threads = [threading.Thread(target=increement, args=(ITERATIONS,) )\
               for _ in range(10) ]

print(COUNTER)

Cell 3
[ t.start() for t in threads] # start computation
[ t.join() for t in threads ]

Cell4
print('\nCounter: ', COUNTER, '\n')
assert COUNTER == (len(threads) * ITERATIONS),\
 f"Invalid value for counter: {COUNTER}, expected value: {len(threads) * ITERATIONS}"

I guess a better example to demonstrtate race condition would be something like the following since in this case updation of the COUNTER is no longer atomic.  (Kindly let me know if this makes sense so that I can apply for a Pull request).
def increement(n):
    global COUNTER # Use the global variable declared above
    for _ in range(n):
        x =  COUNTER
        COUNTER = x + 1
        time.sleep(0.001)
    print( f"\n{threading.current_thread().name} finished counting")

Despite its appearance as a one-liner, COUNTER += 1 actually consists of multiple bytecode instructions, which you can inspect using the dis module from the standard library.
As seen below, 3 distinct bytecode instructions are actually needed to carry out COUNTER += 1.
>>> counter = 0
>>> def inc_global_counter():
...     global counter
...     counter += 1

>>> import dis
>>> dis.dis(inc_global_counter)
  3           0 LOAD_GLOBAL              0 (counter)
              2 LOAD_CONST               1 (1)        # Load global variable `counter`
              4 INPLACE_ADD                           # Increment by 1
              6 STORE_GLOBAL             0 (counter)  # Update with new value
              8 LOAD_CONST               0 (None)
             10 RETURN_VALUE

The GIL doesn't help prevent the kind of race conditions presented in the notebook. Specifically, if multiple threads are running the increment function, it's possible for a thread to get interrupted right before the STORE_GLOBAL bytecode is executed (which updates the counter value). Accumulated over thousands of iterations, this will result in a final counter value that's less than the expected number.
I highly recommend the following post. It's got a nice visual that explains this exact race condition.
https://realpython.com/intro-to-python-threading/#two-threads

This is a great explanation @zzhengnan, thanks for helping out.


Generic IDP support

Hi @paulb777 we're going to release this in M44.  Do you know what might be causing the travis error below?
I didn't change the podspec at all.
 -> FirebaseAuth (5.3.0)
    - ERROR | [iOS] unknown: Encountered an unknown error (409: unexpected token at '{
        "availability" : "(available)",
        "state" : "Shutdown",
        "isAvailable" : true,
        "name" : "iPhone 5s",
') during validation.
[!] FirebaseAuth did not pass validation, due to 1 error.
You can use the `--no-clean` option to inspect any issue.
The command "./scripts/if_changed.sh ./scripts/pod_lib_lint.sh FirebaseAuth.podspec" failed. Retrying, 3 of 3.

The paste you show above is a network flake, but there are real issues ...
Running locally in the branch shows the issues below.  You should be able to debug in an Xcode workspace if you add the -no-clean option.
Let me know if you're still stuck after that.
pod lib lint FirebaseAuth.podspec

 -> FirebaseAuth (5.3.0)
    - NOTE  | xcodebuild:  note: Using new build system
    - NOTE  | xcodebuild:  note: Planning build
    - NOTE  | xcodebuild:  note: Constructing build description
    - NOTE  | xcodebuild:  warning: Skipping code signing because the target does not have an Info.plist file. (in target 'App')
    - ERROR | xcodebuild: Returned an unsuccessful exit code. You can use `--verbose` for more information.
    - NOTE  | xcodebuild:  /Users/paulbeusterien/github/firebase-ios-sdk/Firebase/Auth/Source/AuthProviders/OAuth/FIROAuthProvider.m:26:9: fatal error: 'FIRAuthURLPresenter.h' file not found
    - WARN  | xcodebuild:  /Users/paulbeusterien/github/firebase-ios-sdk/Firebase/Auth/Source/FIRAuth.m:256:17: warning: method definition for 'signInWithProvider:UIDelegate:completion:' not found [-Wincomplete-implementation]
    - NOTE  | xcodebuild:  /Users/paulbeusterien/github/firebase-ios-sdk/Firebase/Auth/Source/Public/FIRAuth.h:513:1: note: method 'signInWithProvider:UIDelegate:completion:' declared here
    - WARN  | [tvOS] xcodebuild:  /Users/paulbeusterien/github/firebase-ios-sdk/Firebase/Auth/Source/FIRAuthWebUtils.m:168:24: warning: 'stringByReplacingPercentEscapesUsingEncoding:' is deprecated: first deprecated in tvOS 9.0 - Use -stringByRemovingPercentEncoding instead, which always uses the recommended UTF-8 encoding. [-Wdeprecated-declarations]
    - NOTE  | [tvOS] xcodebuild:  /Users/paulbeusterien/Downloads/Xcode-beta.app/Contents/Developer/Platforms/AppleTVSimulator.platform/Developer/SDKs/AppleTVSimulator12.2.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSURL.h:593:1: note: 'stringByReplacingPercentEscapesUsingEncoding:' has been explicitly marked deprecated here

[!] FirebaseAuth did not pass validation, due to 1 error and 2 warnings.
You can use the `--no-clean` option to inspect any issue.

All tests passed! Submitting.


[FEATURE]: Show bays in diagram overview

https://github.com/sprinteins/oscd-plugins/issues/221

Findings:
https://github.com/sprinteins/oscd-plugins/blob/52aa7d31622a092f5bac4ac9307aa3c88785f4ce/packages/uilib/src/lib/plugins/communication-explorer/_func-layout-calculation/get-ieds.ts#L16-L26
Put the var root in this function to get extract Bays.

This branch is based on the branch feat/show-bays-in-diagram. Therefore we need to wait until feat/show-bays-in-diagram in ready to  merged in main.

see: https://github.com/sprinteins/oscd-plugins/issues/221#issuecomment-2514843719


messd up in worker of cluster

it's ok in master, but messd up in worker of cluster.

it's ok with console.log:

it turns better when I use setTimeout between debug log.
how to fix this?

This isn't debug's fault. This is because you have three processes printing out to stderr (a non-line-buffered file descriptor) and whatever it is that's managing your cluster isn't performing line buffering for you.
There's nothing debug can do about this other than to output to stdout, which isn't the correct solution. Please open a ticket with the cluster manager you're using.

@Qix- It seems to be ok on linux, I really don't know how to make it right on win.
how to perform beauty on each platform?


Flux Vae broke for float16, force bfloat16 or float32 were compatible

Summary
The Flux VAE, like many VAEs, is broken if run using float16 inputs returning black images due to NaNs
This will fix the issue by forcing the VAE to run in bfloat16 or float32 were compatible
Related Issues / Discussions
Fix for issue https://github.com/invoke-ai/InvokeAI/issues/7208
QA Instructions
Tested on MacOS, VAE works with float16 in the invoke.yaml and left to default.
I also briefly forced it down the float32 route to check that to.
Needs testing on CUDA / ROCm
Merge Plan
It should be a straight forward merge,

I went ahead and made a small change in eaf4e08. Other than that, LGTM. I smoke tested text-to-image and image-to-image.


Android shield + handler

In the provided android video example, I can see the screenshot gets "shielded" by  covering the screen with green, but in my case (using 0.3.6) when using the register function the screenshot gets blocked entirely.
I think that's causing the android handler not to trigger, and I need both features working at the same time (blocking + handling).
Is there a way to achieve this? Or is there a mismatch between the code and the documentation?
Thanks.

Hello @ncoen97, version 1.0.0 is successfully released. Please check document, install and rebuild.
Thanks!

Hello @gbumps.
I've tested with the las version (android 14) and the screenshot handler is still getting blocked.
I've followed the "Post-installation setting for Android" steps and this is my current implementation
  useFocusEffect(
    useCallback(() => {
      ScreenGuardModule.register({backgroundColor: '#252C30'});
      ScreenGuardModule.registerScreenshotEventListener(
        false,
        openModal,
      );
      ScreenGuardModule.registerScreenRecordingEventListener(
        openModal,
      );
      return ScreenGuardModule.unregister;
    }, [openModal]),
  );

After looking at ScreenGuardModule.java, I noticed the activateShield function is still setting the FLAG_SECURE flag.
I tried to make it work by removing the setFlags and running my app via react-native run-android. It did let the screenshot go through, but it's not showing the screen blocker while taking the screenshot.

As told in previous comment, handler won't work until the FLAG_SECURE is removed. This is a characteristic of the Android platform, and there is no way to handle this issue. So basically you cannot have both handler + screen block at the same time on Android.
You can somehow get the info of the latest image (usually saved in Photos or in ScreenShot folder) and check if it is a newly screenshot or not. But it's not always reliable since you may have to ask permission Storage before proceed, and users can customize file saving on other location.

As told in previous comment, while the FLAG_SECURE is turned on, all screenshot and screen record attempting is fully blocked by Android system. This is a characteristic of the platform, and there is no way to handle this issue. So basically you cannot have both handler + screen block at the same time on Android.
Handler is still working in case you use another screenshot or screen recording app, or screenshot system app (scroll down from top to see Notification and Panel setting -> screenshot) by device manufacturer (but may vary).
There is another way, You can somehow get the info of the latest image (usually saved in Photos or in ScreenShot folder) and check if it is a newly screenshot or not. But it's not always reliable since you may have to ask permission Storage before proceed, and users can customize file saving on other locations.

I don't get what's the difference between register and registerWithoutEffect in android then. Both are blocking the screenshot entirely and I can't achieve the functionality seen in the android example video (screenshot gets covered by the black color and handler gets executed).
Is that correct? or am I missing something?
Thanks for the follow up.

register is cover screen with a background color while registerWithoutEffect is just screen guarding only without background color or any other effects like blur view or image view.

Okay.
The register function is not working for me, and as per my last comment, the activateShield function is still setting the FLAG_SECURE flag and NOT showing the background color nor executing the handler as expected.

if you want to receive handler, you must use registerScreenshotEventListener first. You can check for my example here.
The background color you received on Android is after calling any register function and go out of your application for a while, and the jump right back in, you will see a background color as you've set up. After 2 or 3 secs based on your settings, it's will automatically come back to your main application.
the activateShield function is still setting the FLAG_SECURE flag.....

Still don't understand your intention here ?

Is this code from the example working for you in android?
<Pressable
  onPress={() => {
    ScreenGuardModule.register({
      backgroundColor: color,
      timeAfterResume: 2000,
    });
    ScreenGuardModule.registerScreenshotEventListener(false, event =>
      Alert.alert(`register screenshot,`),
    );
    ScreenGuardModule.registerScreenRecordingEventListener(_ =>
      Alert.alert('register screen record'),
    );
    setCurrentState('1');
  }}>
  <Text
    style={{
      color: currentState === '1' ? '#00FF00' : Colors.white,
    }}>
    Turn on screenguard with color
  </Text>
</Pressable>

I want to replicate the same behaviour it has on iOS but also in android, and I'm not able to do that.
I need the screenshot to get blocked in some way and the handler to get executed. How can I achieve that?

I've already stated on previous comment that you can't do it on Android cause it a characteristic of the platform, when the flag FLAG_SECURE is active, it means all of screen capture and screen recording is blocked by system, so that it's why the handler is not get executed except when you use a screenshot or screen recording application, handler still active and got executed normally, but may vary on some devices.
on iOS you can capture and image and got handler executed because it's just only the filter itself and the system it's not blocking anything.

I think I might put an end to this and not let it go too far, by a short summarization:
on Android, screenshot handler will not executed when the FLAG_SECURE is turned on. However, when using a screenshot application (like AZ, Xrecoder, etc...), handler will be triggered normally, but may vary on some devices.
The background color, or the blur image view you saw on the example screen recording video is one of my custom implementation on Android, and of course, it's way different from the iOS and I've stated very clearly in README and TS code definition. Please revise carefully before submitting new issue.


Priority countries appearing twice in the country drop-down

For some reason, priority countries are appearing twice in the drop-down: once in the priority section and later among all countries. Not sure if this is intended behavior.
Thoughts?

That is the intended behavior currently and there are tests that make sure the first one is the selected one. Are you  running into problems with it generating two identical option tags?

Not really, I just didn't expect that - it's fine. Thanks!


benchmark code of four navigation algorithms

Hi,
Will the benchmark code of four navigation algorithms in the paper be released?
Also, how long does it take to train the agents? My english is poor, so I have some confusion about the following sentences in paper

The agents are trained and tested over episodes lasting up to 500 time steps, with 10 steps per second of simulated time. Each agent is trained for a total of 13.2Mtime steps, corresponding to roughly 15 days of experience. Average training speed with four simulation threads is about 167 steps per second, amounting to approximately 14.4M steps per day. We run four such training processes (four simulation threads each) on a single Nvidia Titan X Pascal GPU, yielding a total of 57.6M steps per day (668 steps per second).

My confusion is What the training speed is? The above words mentioned two kinds of speed: "10 steps per second" or "668 steps per second with four simulation threads"? What are the differences between them?
Thanks.

Hi @nina124 ,
The benchmark code for three out of four of the navigation algorithms is released at https://github.com/minosworld/unreal (A3C, A3C-LSTM and UNREAL), while the DFP baseline is at https://github.com/minosworld/dfp .  Please let us know if you have any issues running the baselines (the latter one in particular is a somewhat preliminary release).
With regards to training speed: the 668 steps per second is the effective speed when running four experiments with four simulation threads each on a single Titan X Pascal GPU.  The total training time for a given experiment varies somewhat depending on the specifics of the environment and the modalities used.  Note that the "10 steps per second" refers to the time within the simulation itself (i.e. how much time elapses inside the simulation per agent step, or equivalently how many agent steps there are in a simulation second).

Thanks @msavva
I will try these baselines.
Another question. Now I successfully run minos on headless server, but without gpu rendering.
For faster rendering speed, Is it possible to render with GPU on headless server, like using virgualgl or turbovnc?
I just found the instructions on "Run CARLA without display and selecting GPUs". I guess it might offer some hint on this. But I have no idea about these area.

Hi @nina124 ,
We have some instructions for running headless (see https://github.com/minosworld/minos/blob/master/FAQ.md#how-can-i-run-headless-on-a-server)
Using VirtualGL + TurboVNC is also supported but we don't have instructions here.  Actually, can you summarize the steps you took to run headless without gpu rendering?  They would be helpful for others who want to run on machines with no gpu resources.

Hi @msavva
I tried the unreal baseline with python3 main.py --env_type indoor --env_name pointgoal_suncg_se --parallel_size 10. But the agent failed to learn something meaningful.
The tensorboard score is shown below.

Did your team use the default hyperparameter settings(flags in options.py) when training all the three environments in the following?
python3 main.py --env_type indoor --env_name pointgoal_suncg_se
python3 main.py --env_type indoor --env_name objectgoal_suncg_mf
python3 main.py --env_type indoor --env_name roomgoal_mp3d_s
And, could you share the learning curve of score(the tensorboard result)?

As I am not sure about pointgoal task, I can't state anything here, except that there is another issue #38, which can shed light on this one.

@kvas7andy Thanks, I have commented on that issue and hope I can get some useful training experience.