text:
Error when adding a webpack plugin

Bug Report
I tried to add the webpack.EnviornmentPlugin. I'm unable to use the PAYLOAD_PUBLIC_ prefix because I need to access two env vars added by my hosting platform that don't follow that convention.
Here is the config I tried:
export default buildConfig({
  // ...
  admin: {
    // ...
    webpack: (config) => {
      const envPlugin = new webpack.EnvironmentPlugin({
        HEROKU_BRANCH: 'main',
        HEROKU_APP_NAME: 'my-app-name'
      });

      config.plugins = [envPlugin, ...config.plugins];

      return config;
    }
  },
  // ...

The app crashed with the following error:
cms:dev: webpack built 3fbf3f9bb7d011f70cd9 in 1419ms
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 12:28-61
cms:dev: Module not found: Error: Can't resolve 'child_process' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 31:40-75
cms:dev: Module not found: Error: Can't resolve './swc.android-arm64.node' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 34:40-74
cms:dev: Module not found: Error: Can't resolve '@swc/core-android-arm64' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 45:40-78
cms:dev: Module not found: Error: Can't resolve './swc.android-arm-eabi.node' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 48:40-77
cms:dev: Module not found: Error: Can't resolve '@swc/core-android-arm-eabi' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 65:40-76
cms:dev: Module not found: Error: Can't resolve './swc.win32-x64-msvc.node' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 68:40-75
cms:dev: Module not found: Error: Can't resolve '@swc/core-win32-x64-msvc' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 79:40-77
cms:dev: Module not found: Error: Can't resolve './swc.win32-ia32-msvc.node' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 82:40-76
cms:dev: Module not found: Error: Can't resolve '@swc/core-win32-ia32-msvc' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 93:40-78
cms:dev: Module not found: Error: Can't resolve './swc.win32-arm64-msvc.node' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 96:40-77
cms:dev: Module not found: Error: Can't resolve '@swc/core-win32-arm64-msvc' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 113:40-72
cms:dev: Module not found: Error: Can't resolve './swc.darwin-x64.node' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 116:40-71
cms:dev: Module not found: Error: Can't resolve '@swc/core-darwin-x64' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 127:40-74
cms:dev: Module not found: Error: Can't resolve './swc.darwin-arm64.node' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 148:32-65
cms:dev: Module not found: Error: Can't resolve './swc.freebsd-x64.node' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 151:32-64
cms:dev: Module not found: Error: Can't resolve '@swc/core-freebsd-x64' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 165:44-80
cms:dev: Module not found: Error: Can't resolve './swc.linux-x64-musl.node' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 168:44-79
cms:dev: Module not found: Error: Can't resolve '@swc/core-linux-x64-musl' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 179:44-79
cms:dev: Module not found: Error: Can't resolve './swc.linux-x64-gnu.node' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 182:44-78
cms:dev: Module not found: Error: Can't resolve '@swc/core-linux-x64-gnu' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 195:44-82
cms:dev: Module not found: Error: Can't resolve './swc.linux-arm64-musl.node' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 198:44-81
cms:dev: Module not found: Error: Can't resolve '@swc/core-linux-arm64-musl' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 209:44-81
cms:dev: Module not found: Error: Can't resolve './swc.linux-arm64-gnu.node' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 212:44-80
cms:dev: Module not found: Error: Can't resolve '@swc/core-linux-arm64-gnu' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 224:40-81
cms:dev: Module not found: Error: Can't resolve './swc.linux-arm-gnueabihf.node' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/binding.js 227:40-80
cms:dev: Module not found: Error: Can't resolve '@swc/core-linux-arm-gnueabihf' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/index.js 62:39-85
cms:dev: Critical dependency: the request of a dependency is an expression
cms:dev:
cms:dev: WARNING in ../../node_modules/@swc/core/spack.js 42:33-46
cms:dev: Critical dependency: the request of a dependency is an expression
cms:dev:
cms:dev: WARNING in ../../node_modules/esbuild/lib/main.js 1798:8-28
cms:dev: Critical dependency: the request of a dependency is an expression
cms:dev:
cms:dev: WARNING in ../../node_modules/esbuild/lib/main.js 1865:15-32
cms:dev: Module not found: Error: Can't resolve 'pnpapi' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/esbuild/lib'
cms:dev:
cms:dev: WARNING in ../../node_modules/esbuild/lib/main.js 1898:21-46
cms:dev: Module not found: Error: Can't resolve 'worker_threads' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/esbuild/lib'
cms:dev:
cms:dev: WARNING in ../../node_modules/jest-worker/build/WorkerPool.js 22:4-29
cms:dev: Module not found: Error: Can't resolve 'worker_threads' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/jest-worker/build'
cms:dev:
cms:dev: WARNING in ../../node_modules/jest-worker/build/base/BaseWorkerPool.js 111:19-46
cms:dev: Critical dependency: the request of a dependency is an expression
cms:dev:
cms:dev: WARNING in ../../node_modules/jest-worker/build/index.js 68:19-38
cms:dev: Critical dependency: the request of a dependency is an expression
cms:dev:
cms:dev: WARNING in ../../node_modules/jest-worker/build/workers/processChild.js 89:15-28
cms:dev: Critical dependency: the request of a dependency is an expression
cms:dev:
cms:dev: WARNING in ../../node_modules/jest-worker/build/workers/processChild.js 105:15-28
cms:dev: Critical dependency: the request of a dependency is an expression
cms:dev:
cms:dev: WARNING in ../../node_modules/loader-runner/lib/loadLoader.js 7:31-45
cms:dev: Module not found: Error: Can't resolve 'url' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/loader-runner/lib'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
cms:dev:         - install 'url'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "url": false }
cms:dev:
cms:dev: WARNING in ../../node_modules/loader-runner/lib/loadLoader.js 19:16-36
cms:dev: Critical dependency: the request of a dependency is an expression
cms:dev:
cms:dev: WARNING in ../../node_modules/terser-webpack-plugin/dist/minify.js 43:118-125
cms:dev: Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
cms:dev:
cms:dev: WARNING in ../../node_modules/webpack/lib/debug/ProfilingPlugin.js 26:13-33
cms:dev: Module not found: Error: Can't resolve 'inspector' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib/debug'
cms:dev:
cms:dev: WARNING in ../../node_modules/webpack/lib/serialization/ObjectMiddleware.js 647:9-25
cms:dev: Critical dependency: the request of a dependency is an expression
cms:dev:
cms:dev: ERROR in ../../node_modules/@swc/core-darwin-arm64/swc.darwin-arm64.node 1:0
cms:dev: Module parse failed: Unexpected character '�' (1:0)
cms:dev: You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
cms:dev: (Source code omitted for this binary file)
cms:dev:
cms:dev: ERROR in ../../node_modules/@swc/core/binding.js 2:37-50
cms:dev: Module not found: Error: Can't resolve 'fs' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: ERROR in ../../node_modules/@swc/core/index.js 70:27-47
cms:dev: Module not found: Error: Can't resolve '@swc/wasm' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/@swc/core'
cms:dev:
cms:dev: ERROR in ../../node_modules/chrome-trace-event/dist/trace-event.js 10:17-34
cms:dev: Module not found: Error: Can't resolve 'stream' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/chrome-trace-event/dist'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
cms:dev:         - install 'stream-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "stream": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/esbuild/lib/main.d.ts 1:7
cms:dev: Module parse failed: Unexpected token (1:7)
cms:dev: You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
cms:dev: > export type Platform = 'browser' | 'node' | 'neutral';
cms:dev: | export type Format = 'iife' | 'cjs' | 'esm';
cms:dev: | export type Loader = 'base64' | 'binary' | 'copy' | 'css' | 'dataurl' | 'default' | 'empty' | 'file' | 'js' | 'json' | 'jsx' | 'text' | 'ts' | 'tsx';
cms:dev:
cms:dev: ERROR in ../../node_modules/esbuild/lib/main.js 1701:9-22
cms:dev: Module not found: Error: Can't resolve 'fs' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/esbuild/lib'
cms:dev:
cms:dev: ERROR in ../../node_modules/esbuild/lib/main.js 1702:9-22
cms:dev: Module not found: Error: Can't resolve 'os' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/esbuild/lib'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "os": require.resolve("os-browserify/browser") }'
cms:dev:         - install 'os-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "os": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/esbuild/lib/main.js 1889:20-44
cms:dev: Module not found: Error: Can't resolve 'child_process' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/esbuild/lib'
cms:dev:
cms:dev: ERROR in ../../node_modules/esbuild/lib/main.js 1894:10-24
cms:dev: Module not found: Error: Can't resolve 'tty' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/esbuild/lib'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "tty": require.resolve("tty-browserify") }'
cms:dev:         - install 'tty-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "tty": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/graceful-fs/graceful-fs.js 1:9-22
cms:dev: Module not found: Error: Can't resolve 'fs' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/graceful-fs'
cms:dev:
cms:dev: ERROR in ../../node_modules/graceful-fs/legacy-streams.js 1:13-37
cms:dev: Module not found: Error: Can't resolve 'stream' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/graceful-fs'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
cms:dev:         - install 'stream-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "stream": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/graceful-fs/polyfills.js 1:16-36
cms:dev: Module not found: Error: Can't resolve 'constants' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/graceful-fs'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "constants": require.resolve("constants-browserify") }'
cms:dev:         - install 'constants-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "constants": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/jest-worker/build/index.js 27:15-28
cms:dev: Module not found: Error: Can't resolve 'os' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/jest-worker/build'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "os": require.resolve("os-browserify/browser") }'
cms:dev:         - install 'os-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "os": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/jest-worker/build/workers/ChildProcessWorker.js 9:15-39
cms:dev: Module not found: Error: Can't resolve 'child_process' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/jest-worker/build/workers'
cms:dev:
cms:dev: ERROR in ../../node_modules/jest-worker/build/workers/ChildProcessWorker.js 19:15-32
cms:dev: Module not found: Error: Can't resolve 'stream' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/jest-worker/build/workers'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
cms:dev:         - install 'stream-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "stream": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/jest-worker/build/workers/NodeThreadsWorker.js 19:15-32
cms:dev: Module not found: Error: Can't resolve 'stream' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/jest-worker/build/workers'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
cms:dev:         - install 'stream-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "stream": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/jest-worker/build/workers/NodeThreadsWorker.js 29:15-40
cms:dev: Module not found: Error: Can't resolve 'worker_threads' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/jest-worker/build/workers'
cms:dev:
cms:dev: ERROR in ../../node_modules/jest-worker/build/workers/messageParent.js 19:39-64
cms:dev: Module not found: Error: Can't resolve 'worker_threads' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/jest-worker/build/workers'
cms:dev:
cms:dev: ERROR in ../../node_modules/loader-runner/lib/LoaderRunner.js 5:9-22
cms:dev: Module not found: Error: Can't resolve 'fs' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/loader-runner/lib'
cms:dev:
cms:dev: ERROR in ../../node_modules/merge-stream/index.js 3:24-41
cms:dev: Module not found: Error: Can't resolve 'stream' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/merge-stream'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
cms:dev:         - install 'stream-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "stream": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/terser-webpack-plugin/dist/index.js 5:11-24
cms:dev: Module not found: Error: Can't resolve 'os' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/terser-webpack-plugin/dist'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "os": require.resolve("os-browserify/browser") }'
cms:dev:         - install 'os-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "os": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/uglify-js/tools/node.js 1:9-22
cms:dev: Module not found: Error: Can't resolve 'fs' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/uglify-js/tools'
cms:dev:
cms:dev: ERROR in ../../node_modules/watchpack/lib/DirectoryWatcher.js 17:15-37
cms:dev: Module not found: Error: Can't resolve 'os' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/watchpack/lib'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "os": require.resolve("os-browserify/browser") }'
cms:dev:         - install 'os-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "os": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/watchpack/lib/LinkResolver.js 7:11-24
cms:dev: Module not found: Error: Can't resolve 'fs' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/watchpack/lib'
cms:dev:
cms:dev: ERROR in ../../node_modules/watchpack/lib/watchEventSource.js 7:11-24
cms:dev: Module not found: Error: Can't resolve 'fs' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/watchpack/lib'
cms:dev:
cms:dev: ERROR in ../../node_modules/watchpack/lib/watchEventSource.js 12:15-37
cms:dev: Module not found: Error: Can't resolve 'os' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/watchpack/lib'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "os": require.resolve("os-browserify/browser") }'
cms:dev:         - install 'os-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "os": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/FileSystemInfo.js 9:19-36
cms:dev: Module not found: Error: Can't resolve 'module' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib'
cms:dev: Did you mean './module'?
cms:dev: Requests that should resolve in the current directory need to start with './'.
cms:dev: Requests that start with a name are treated as module requests and resolve within module directories (node_modules, /Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/payload/node_modules).
cms:dev: If changing the source code is not an option there is also a resolve options called 'preferRelative' which tries to resolve these kind of requests in the current directory too.
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/NormalModule.js 10:20-42
cms:dev: Module not found: Error: Can't resolve 'querystring' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "querystring": require.resolve("querystring-es3") }'
cms:dev:         - install 'querystring-es3'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "querystring": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/config/defaults.js 8:11-24
cms:dev: Module not found: Error: Can't resolve 'fs' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib/config'
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/dependencies/CommonJsImportsParserPlugin.js 8:26-40
cms:dev: Module not found: Error: Can't resolve 'url' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib/dependencies'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
cms:dev:         - install 'url'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "url": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/dependencies/ImportMetaPlugin.js 8:26-40
cms:dev: Module not found: Error: Can't resolve 'url' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib/dependencies'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
cms:dev:         - install 'url'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "url": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/dependencies/URLPlugin.js 8:26-40
cms:dev: Module not found: Error: Can't resolve 'url' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib/dependencies'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
cms:dev:         - install 'url'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "url": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/dependencies/WorkerPlugin.js 8:26-40
cms:dev: Module not found: Error: Can't resolve 'url' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib/dependencies'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
cms:dev:         - install 'url'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "url": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/javascript/JavascriptModulesPlugin.js 9:11-24
cms:dev: Module not found: Error: Can't resolve 'vm' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib/javascript'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "vm": require.resolve("vm-browserify") }'
cms:dev:         - install 'vm-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "vm": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/javascript/JavascriptParser.js 11:11-24
cms:dev: Module not found: Error: Can't resolve 'vm' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib/javascript'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "vm": require.resolve("vm-browserify") }'
cms:dev:         - install 'vm-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "vm": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/schemes/FileUriPlugin.js 8:31-45
cms:dev: Module not found: Error: Can't resolve 'url' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib/schemes'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
cms:dev:         - install 'url'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "url": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/schemes/HttpUriPlugin.js 10:16-30
cms:dev: Module not found: Error: Can't resolve 'url' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib/schemes'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
cms:dev:         - install 'url'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "url": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/schemes/HttpUriPlugin.js 11:64-79
cms:dev: Module not found: Error: Can't resolve 'zlib' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib/schemes'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "zlib": require.resolve("browserify-zlib") }'
cms:dev:         - install 'browserify-zlib'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "zlib": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/serialization/FileMiddleware.js 8:21-38
cms:dev: Module not found: Error: Can't resolve 'stream' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib/serialization'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
cms:dev:         - install 'stream-browserify'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "stream": false }
cms:dev:
cms:dev: ERROR in ../../node_modules/webpack/lib/serialization/FileMiddleware.js 15:4-19
cms:dev: Module not found: Error: Can't resolve 'zlib' in '/Users/lynn/Code/SomeOddPilot/superplastic-next/node_modules/webpack/lib/serialization'
cms:dev:
cms:dev: BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
cms:dev: This is no longer the case. Verify if you need this module and configure a polyfill for it.
cms:dev:
cms:dev: If you want to include a polyfill, you need to:
cms:dev:         - add a fallback 'resolve.fallback: { "zlib": require.resolve("browserify-zlib") }'
cms:dev:         - install 'browserify-zlib'
cms:dev: If you don't want to include a polyfill, you can use an empty module like this:
cms:dev:         resolve.fallback: { "zlib": false }

Hey @lynndylanhurley — this is actually because the Webpack plugin you're using relies on some Node-only modules. But - - the Payload config is executed in both Node and in your browser, which is where all of these errors are coming from. You need to use a Webpack alias to tell Webpack to ignore that package for its browser JS, which will allow you to circumvent this issue.
See more in our docs here:
https://payloadcms.com/docs/admin/webpack#aliasing-server-only-modules
I will convert this to a discussion but am happy to continue to help!

authors: jmikrut lynndylanhurley

repo: payloadcms/payload


text:
Field in drawer cannot be edited

Link to reproduction
Not for now
To Reproduce
This is just a reminder for a closed issue.: https://github.com/payloadcms/payload/issues/2815. More than one of us are reporting this but we got no replies. I guess the reason is the ticket is closed.
Describe the Bug
https://github.com/payloadcms/payload/issues/2815
Payload Version
1.10.2

Hey @Stupidism this should be fixed with 1.11.0, can you give this a shot and let me know how it goes?

source: gharchive/issue

authors: Stupidism jacobsfletch

license: MIT

license_type: permissive

license_source: github-api


text:
Race condition with database transactions when multiple queries are issued through GraphQL

Link to reproduction
https://github.com/diesieben07/payload-transactions-demo/tree/repro-graphql-multi-query
To Reproduce

Make sure database transactions are in use
Create two globals, allow read access from everyone for both
Log in to the Admin and save both globals
Log out of the Admin (!)
Attempt to query both globals in one GraphQL query

The above repository allows you to do this easily. Simply run docker compose up --attach payload and you will get a running Payload instance plus a MongoDB ReplicaSet in Docker. Create a dummy user in the Admin, save the Globals and log out. Go to the GraphQL Playground and run the following query:
query test {
  Global1 {
    testText
  }
  Global2 {
    testText
  }
}

You will see that only one of the queries succeeds and you get an internal server error.
The repository uses patch-package to add some trace logging to see where transactions are begun and committed.
I would recommend to disable Schema-Polling in the GraphQL-Playground settings to avoid spamming the logs from Schema-Introspection requests.
If you look at the logs, you will see that Payload creates two transactions, but then keeps using only one of them, attempting to commit and end it twice.
Describe the Bug
Payload Transactions are bound to the PayloadRequest object. However, multiple operations can happen during one request. This leads to a race condition, because all operations will try to create and commit the transaction as well as end the session.
If you are unlucky, the "asynchronous Gods" will decide that one operation tries to commit on a session which has already been ended.
If you are a little more lucky (I guess), things will "appear to work", but you're not really getting the benefit of transactions, because not everything will or will not be committed/rolled back.
Either Payload should reliably create a new transaction for every operation or it should use one transaction for the whole request, but only actually commit it at the end.
Payload Version
2.0.4
Adapters and Plugins
@payloadcms/db-mongodb@1.0.3

This seems to be what's causing our payload server to crash in production for very large GraphQL queries, did you get the "rollbackTransaction called when no transaction exists" error too because of the race condition?

did you get the "rollbackTransaction called when no transaction exists" error too because of the race condition?

Yes, this warning log also happens immediately before "TypeError: Cannot read properties of undefined" when this issue occurs.

Hey all, just quick update. This is first up on our radar to investigate this coming week. Will report back soon!

The latest PayloadCMS release 2.0.10 seems to have shipped some changes to address this, @DanRibbens?

#3795 didn't seem to completely resolve the race condition issue with mongodb graphql transactions:

@DanRibbens Re-validate fix

Same error here. For me it seems to only happen when I query on the clientside with GraphQL. I use the URQL client. When I query with SSR (getServerSideProps, etc.), it works just fine, no errors, doesn't crash my node server.

I'm pretty sure it's any time when you bundle multiple queries in a single graphql request.

@xHomu Oh yeah you're right. Scratch what I said earlier. Thanks for this. Yeah just confirmed again it crashes when I bundle two queries in one request lol.

Getting this a bunch with 2.0.14. All my gql requests are single queries. Downgrading to 2.0.13 (which also requires downgrading richtext-lexical from 0.1.16 to 0.1.15) fixes it, even when keeping the latest db-mongo v1.0.5

What we need is a config that let us disable transactions altogether for Mongo.

authors: Blankeos denolfe diesieben07 jmikrut revnelson xHomu


text:
Lexical editor features not compatible with next-payload

Link to reproduction
https://github.com/adampilks/lexical-blocks-issue
Describe the Bug
When trying to add features to the lexical editor, nextjs errors out due to server components accessing the static getType method of the blocks feature from the server:
Server Error
Error: Cannot access BlockNode.getType on the server. You cannot dot into a client module from a server component. You can only pass the imported name through.

This error happened while generating the page. Any console logs will be displayed in the terminal window.
Source
cms/Pages.ts (42:28) @ eval

  40 |   name: 'content',
  41 |   type: 'richText',
> 42 |   editor: lexicalEditor({
     |                        ^
  43 |     features: [BlocksFeature({ blocks: [] })],
  44 |   }),
  45 | },

@AlessioGr  The above reproduction is based on the reproduction repo for https://github.com/payloadcms/payload/issues/3705 with the only change to add the blocks feature into the lexical editor.
To Reproduce

Clone above repo
npm install
npm run dev
Visit localhost:3000

Payload Version
2.0.13
Adapters and Plugins
db-mongodb, bundler-webpack, next-payload, editor-lexical

Just saw in discord that this fixed and will be released soon so will clode


text:
Windows 11 can't stop

ElectronShutdownHandler.on('shutdown', async () => {
      logger.warn('shutdown quit 1')
     await sleep(3000) // = wind reg ProxyEnable
      logger.warn('shutdown quit 2')
      ElectronShutdownHandler.releaseShutdown()
      app.quit()
})

Now it shuts down when the "shutdown quit 2" is not executed

Hi!
First of all: did you execute the setup step? (as shown here: https://github.com/paymoapp/electron-shutdown-handler#example, setting up the window handle with setWindowHandle and calling blockShutdown afterwards)
If you don't call blockShutdown it can not be guaranteed that the async operations will be finished. Also note that blockShutdown must be called before the actual shutdown event (before the callback is called).

Also! Please refer to the demo. If you don't prevent the default behavior of before-quit and close events, then the electron app might just exit at a shutdown event, because even though preventShutdown is called, windows tries to close all the applications in the event of a shutdown.

app.on('before-quit', e => {
     e.preventDefault();
});

win.on('close', e => {
     e.preventDefault();
});

function sleep(ms) {
   return new Promise(resolve => setTimeout(resolve, ms));
}

async function writeFile(text) {
return new Promise((resolve, reject) => {
	fs.writeFile('test.txt', text, (err) => {
		if (err) {
			reject(err);
		} else {
			resolve();
		}
	})
})
}

ShutdownHandler.setWindowHandle(win.getNativeWindowHandle());
ShutdownHandler.blockShutdown('Yayy! It works! Shutdown in 10 seconds');
writeFile('!!!!!!!!!!!!!!!!!!!!!!!!!!!');
ShutdownHandler.on('shutdown', async () => {
     await writeFile('! System is shutting down !');
     await sleep(10000);
     await writeFile('Shutting down NOW');
     ShutdownHandler.releaseShutdown();
     app.quit();
});

text.txt = ! System is shutting down !
"Shutting down NOW" No Write

I currently don't have a windows 11 system on hands, but I will look into this ASAP.

It seems that the handling of Promise type is missing.

authors: 07ke ACCia gergof

repo: paymoapp/electron-shutdown-handler


text:
Gem and Cocoapod refactor

This is the same as #27 but rebased off of master.

Needs docs, but that will be #31 so we don't have to delay this.

source: gharchive/pull-request

repo: paypal/Illuminator

license_source: bigquery


text:
Mouse interferes with keyboard navigation

downshift version: 1.22.3
node version: 7.9.0
npm (or yarn) version: 4.2.0

Relevant code or config
I made a sandbox, which is just the "basic" example from the site with some extra items: https://codesandbox.io/s/x3y2xzppyw
What you did:
What happened:
Here's a video: http://jlongster.com/s/downshift-scroll.mov
In Chrome, if you hover over an item and then try to use the keyboard to scroll down, it keeps highlighting the item that the mouse is hovered on. This is probably because whenever the element is scrolled, the onMouseEnter event is firing.
Suggested solution:
I have no idea. I actually started looking into this because I'm experiencing a different, but related bug, in my app but I can't boil it down to a reproducible test case. I'm hoping that whatever fix is made for this that it might help my bug too.

Thanks James. I think this is a duplicate of: https://github.com/paypal/downshift/issues/240

It does look like the same. Ideally we'd ignore all mouseenter events if we are manually scrolling. I don't have a local version of downshift right now to try that, but you could set this.scrolling = true before setting the scrollTop and then set this.scrolling = false afterwards.
I'm surprised because I thought mouseenter events weren't fired due to scrolling. It's problematic for me in a weirder way because when I scroll with the trackpad, it's firing these events as well, but  for some reason downshift thinks it needs to scroll the element that just fired mouseenter into view, causing janky scrolling. I don't know why it thinks it needs to scroll it into view (obviously it doesn't if it's an element triggering mouseenter from scrolling it into the cursor). I can look into that separately, but I'm hoping whatever fix for this bug will fix my bug too. (Although I just realized it probably won't, since it'll be specific to the above workflow)

Finally able to reproduce my original issue! Opening a new bug.

authors: jlongster kentcdodds

repo: paypal/downshift

license: mit


text:
No protocol in Nightscout uploader

Your Environment

Uploader Version Number: v0.7.3
Your Android Phone Model Name : Samsung S3 Galaxy
Android Version Number (e.g. use 4.4 for 4.4.4): Android Version 4.3
Network Connection at the time the issue occurred (Wi-Fi, Mobile): Wifi
(if relevant) Nightscout website version (e.g. 0.8.4 Funnel cake, master / dev branch): no issue on Nightscout

Brief Explanation of Issue
I changed the uploader phone since the old one broke down, I stayed on a Samsung S3 since it has still a battery I can switch. The uploader version v0.7.3 works and also the upload to Nightscout works. BUT on the uploader app below the graph with the glucose there is NO protocol. Usually it tells me things like: next poll due in 30 seconds, or Nightscout available etc. But now it is just blank. What could be the issue? I tried deleting the protocol (although not existing), I tried re-starting the app. I don't know if there is some setting I need to change.
Since the uploader phone is always with our kid in kindergarten, the protocol is really helpful when communicating with the teachers on possible errors. Thanks.
Uploader Error Code

Steps to Reproduce (for bugs)

Severity Score

There could be issues with really android versions and newer versions of the uploader. Try uninstalling version 0.7.3 and installing 0.7.1
https://github.com/pazaan/600SeriesAndroidUploader/releases/tag/v0.7.1

There could be issues with really android versions and newer versions of the uploader. Try uninstalling version 0.7.3 and installing 0.7.1
https://github.com/pazaan/600SeriesAndroidUploader/releases/tag/v0.7.1

Thank you. Indeed that seems to be the problem. I managed to get the protocol with the 0.7.1 version. As of 0.7.2 it doesn't work anymore. Good to know. I'll keep a copy of the 0.7.1 version just in case for future use.
Thanks a lot for your support!

Thank you. Indeed that seems to be the problem. I managed to get the protocol with the 0.7.1 version. As of 0.7.2 it doesn't work anymore. Good to know. I'll keep a copy of the 0.7.1 version just in case for future use.
Thanks a lot for your support!

authors: Pogman lulukuhl


text:
Update README.rst

api keys are deprecated and will no longer be supported next year but using an access key as generated at https://airtable.com/developers/web/guides/personal-access-tokens in the airtable.Airtable method works just the same as the API_KEY currently does. lets shift the language to what it will be in the future.

Thanks.


text:
typo fix

replace from fecth to fetch.
Thank you for providing good material about git branch.

Thanks for catching this!

repo: pcottle/learnGitBranching


text:
PDFKit, with page-break-inside: avoid enabled, fails to not create inside row page breaks on my file.

Example of the problem:
Using PDFKit w/ Python:
import pdfkit
options = {
    'user-style-sheet': 'htmltopdf.css'
}

file_p = myfile.html
pdfkit.from_file(file_p, file_p[:-5] + '.pdf', options=options)

CSS, htmltopdf.css:
<style type="text/css">
tr {
	page-break-inside: avoid !important;
}

thead, tfoot {
	display: table-row-group
}
</style>

I've attached the file I'm attempting to work with in which problems occur at page breaks (replace extension w/ .html).
D - Yadgir_July.txt

The actual rendering of PDFs is done by wkHTMLtoPDF. You should report this there. We just wrap the project to provide a Ruby interface to it.

repo: pdfkit/pdfkit


text:
Added test case for CCITTFaxDecoder

Copy of #642

Thanks for this great project!
The tostring method has been deprecated since Python 3.2 and was
removed altogether in 3.9. In Python 3.2 the method was renamed
to "tobytes"
Without this fix, using the ccit module will lead to an AttributeError and a crash on Python 3.9+.
Will close #641
How Has This Been Tested?
Ran locally with python 3.9
Checklist
I have added tests that prove my fix is effective or that my feature
works.
I have added docstrings to newly created methods and classes not relevant
I have optimized the code at least one time after creating the initial
version
I have updated the README.md or I am verified that this
is not necessary
I have updated the readthedocs documentation or I
verified that this is not necessary
I have added a consice human-readable description of the change to
CHANGELOG.md

Actual error was already fixed by #661. So only adding test case.


text:
set selectTextStyle propType to Text.propTypes.style

https://github.com/peacechen/react-native-modal-selector/issues/25

Sure, Maybe this could be done under a different issue ticket tho.

If it's not too much trouble, would you mind updating all the style props with PropTypes.oneOfType ?  I won't be able to get to it right now and it'll likely fall through the cracks with my bad memory :D

I have tried to investigate prop types for arrays in style-properties, but it seems that this is somehow included in Text.propTypes.style (and other prop types for styles from RN). There is no warning in debug-mode when using arrays without explicit specifying it.
In Text from RN all properties goes trough a function which flattens any array present. So as far as I can see Text.propTypes.style accepts both objects and arrays with objects. ViewPropTypes uses the same function.
Other well maintained react-native modules seem to just use Text.propTypes.style, and not PropTypes.oneOfType to include array, e.g. react-native-elements Search inputStyle.
So I think this PR is good to go, and no further editing is necessary.

Thanks @mikaello for clarifying the style proptypes behavior.  Wasn't aware that arrays are automatically flattened first.

authors: mienaikoe mikaello peacechen

repo: peacechen/react-native-modal-selector


text:
bitmap is recycled at android.opengl.GLUtils.texImage2D

Hello Pedro,
In many devices app crashes bellow line.
public int[] load(Bitmap[] bitmaps) {
    int[] textureId = new int[bitmaps.length];
    GlUtil.createTextures(bitmaps.length, textureId, 0);
    for (int i = 0; i < bitmaps.length; i++) {
      if (bitmaps[i] != null) {
        GLES20.glBindTexture(GLES20.GL_TEXTURE_2D, textureId[i]);
        GLUtils.texImage2D(GLES20.GL_TEXTURE_2D, 0, bitmaps[i], 0);
        bitmaps[i].recycle();
        bitmaps[i] = null;
      }
    }
    return textureId;
  }

fixed here:
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/commit/97fa5ffb2b311ddcf674be47f1468c1b6c0e38ed#diff-9080294adb04c773eead376b12617643d1c5d16ca24039d43d20e1d7720f997dR40
Compile library version 2.2.4 and the error should be solved


text:
It is possible to capture series of photos using OpenGL RTSP?

As in title it is possible?
Or have any ideas how I can do it? I need to capture 16 photos before stream will starting.

I haven't a specific mode to do it but you can try call takePhoto method multiple times.

Yeah, it is some solution, but capture 16 photos takes too long, anyway thanks for fast answer. :)


text:
AuthenticationManager null in DefaultVaadinSharedSecurity

Hi.
First of all thanks for these great addons and extensions, just the things that people need!
I used Vaadin Shared security and copied the code from the example (the application class + loginUi).
However, after
        vaadinSecurity.login(userName.getValue(), passwordField.getValue(), rememberMe.getValue());

I have an exception being thrown from the DefaultVaadinSharedSecurity class (line 70).
Apparently authenticationManager is null.
I tried to implement AuthenticationManager interface and annotate it with @Component but it's the same behavior.
If I put the breakpoint in the afterPropertiesSet of the AbstractVaadinSecurity when authenticationManager there is an exception with the following message being thrown:
No qualifying bean of type [org.springframework.security.authentication.AuthenticationManager] is defined: expected single matching bean but found 2: authenticationManagerBean,authenticationManager
Am I doing something wrong?
Can you provide a bit more details what needs to be implemented and how to annotate it, compared to what you have in the example application?

I found some old code that was messing it up.
Sorry!


text:
🛑 Web Bekasikota is down

In 315eade, Web Bekasikota (https://www.bekasikota.go.id/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Web Bekasikota is back up in 2c08b40.

repo: pemkotbekasi/website-status


text:
🛑 Dinas Sosial is down

In 60349f8, Dinas Sosial (https://dinsos.bekasikota.go.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dinas Sosial is back up in 85c8ed5.


text:
Add mpu registers for armv8m

The mpu registers defination from:
Armv8-M Architecture Reference Manual(https://developer.arm.com/documentation/ddi0553/latest/)
Have tested on my cortex-m55 board, and when input
(gdb)arm mpu
It shows:
SCB MPU registers:
MPU_TYPE                         = 00001000
DREGION                        ....10.. - 10
MPU_CTRL                         = 00000005
PRIVDEFENA                     .......4 - 1
ENABLE                         .......1 - 1
MPU MAIR registers:
mair  0xe000edc0:	0x00447722
ATTR 0
Normal memory,  Outer Write-Through transient, Read allocation
Normal memory,  Inner Write-Through transient, Read allocation
ATTR 1
Normal memory,  Outer Write-Back Transient, Read/Write allocation
Normal memory,  Inner Write-Back Transient, Read/Write allocation
ATTR 2
Normal memory,  Outer Non-cacheable
Normal memory,  Inner Non-cacheable
ATTR 3
Device memory,   nGnRnE
mair  0xe000edc4:	0x00000000
ATTR 4
Device memory,   nGnRnE
ATTR 5
Device memory,   nGnRnE
ATTR 6
Device memory,   nGnRnE
ATTR 7
Device memory,   nGnRnE
MPU region number 16
mpu region:  1
region start at 0x0
region end   at 0xffe0
MPU_RBAR                         = 00000003
SH                             ......00 - Non-shareable
AP                             .......2 - read/write by any privilege level
XN                             .......1 - Disallow program execution in this region
MPU_RLAR                         = 0000ffe5
LIMIT                          0000ffe. - 00007ff
PXN                            ......0. - Execution only permitted if read permitted
AttrIndx                       .......4 - 2
EN                             .......1 - Region enable
mpu region:  2
region start at 0x68000000
region end   at 0x68017fe0
MPU_RBAR                         = 68000003
BASE                           6800000. - 3400000
SH                             ......00 - Non-shareable
AP                             .......2 - read/write by any privilege level
XN                             .......1 - Disallow program execution in this region
MPU_RLAR                         = 68017fe5
LIMIT                          68017fe. - 3400bff
PXN                            ......0. - Execution only permitted if read permitted
AttrIndx                       .......4 - 2
EN                             .......1 - Region enable
mpu region:  3
region start at 0x6d020000
region end   at 0x6d03bfe0
MPU_RBAR                         = 6d020003
BASE                           6d02000. - 3681000
SH                             ......00 - Non-shareable
AP                             .......2 - read/write by any privilege level
XN                             .......1 - Disallow program execution in this region
MPU_RLAR                         = 6d03bfe5
LIMIT                          6d03bfe. - 3681dff
--Type  for more, q to quit, c to continue without paging--
PXN                            ......0. - Execution only permitted if read permitted
AttrIndx                       .......4 - 2
EN                             .......1 - Region enable
mpu region:  4
region start at 0x71000000
region end   at 0x727fffe0
MPU_RBAR                         = 71000003
BASE                           7100000. - 3880000
SH                             ......00 - Non-shareable
AP                             .......2 - read/write by any privilege level
XN                             .......1 - Disallow program execution in this region
MPU_RLAR                         = 727fffe5
LIMIT                          727fffe. - 393ffff
PXN                            ......0. - Execution only permitted if read permitted
AttrIndx                       .......4 - 2
EN                             .......1 - Region enable
mpu region:  5
region start at 0x80000000
region end   at 0x8fffffe0
MPU_RBAR                         = 80000003
BASE                           8000000. - 4000000
SH                             ......00 - Non-shareable
AP                             .......2 - read/write by any privilege level
XN                             .......1 - Disallow program execution in this region
MPU_RLAR                         = 8fffffe5
LIMIT                          8fffffe. - 47fffff
PXN                            ......0. - Execution only permitted if read permitted
AttrIndx                       .......4 - 2
EN                             .......1 - Region enable
mpu region:  6
region start at 0x1e0000
region end   at 0x1e17a0
MPU_RBAR                         = 001e0006
--Type  for more, q to quit, c to continue without paging--
BASE                           001e000. - 000f000
SH                             ......00 - Non-shareable
AP                             .......6 - Read only by any privilege level
XN                             .......0 - Allow program execution in this region
MPU_RLAR                         = 001e17a3
LIMIT                          001e17a. - 000f0bd
PXN                            ......0. - Execution only permitted if read permitted
AttrIndx                       .......2 - 1
EN                             .......1 - Region enable

Oh, thanks for the big PR :) looks really interesting
I'm out a few days on vacation, and will check it more when I have access to anything more than my phone

Hi, thanks
I'm glad to see your interest. I don't know much about GDB Python, so any comments or feedback would be very helpful for me

Thanks for your review, I will generate a new PR for address your advice.
For arm m55 board, maybe the qemu will help, there is a board called mps-an547, which is a m55 cpu.
and zephy support the board.
Br,
yingchun

Replaced by https://github.com/pengi/arm_gdb/pull/9

authors: pengi swordligit


text:
华为mate8上崩溃

在华为mate8上，安卓6.0系统，用您的demo打开相机，照完相后崩溃

我也是，请问你有解决方案么？是不是需要root才行

repo: pengjianbo/GalleryFinal


text:
关卡综合性理智收益计算

请问是否可以增加功能：∑（各种掉落材料的消耗理智（除了家具）x掉落率）/关卡消耗理智
从而给出一个综合性的关卡性价比并且从高到低排序。
新人基本什么材料（甚至包括赤金和经验书）都缺，导致刷精二材料的时候任何副产物掉落对我来说都很有意义。哪怕是低级材料都可以拿来升级一些后抽到干员的技能。所以很希望能用综合性的理智收益来排序一下关卡。毕竟精二可以稍微慢一点但是理智真的是一点点都不想浪费。

此功能已在 ArkPlanner 中实现～

authors: GalvinGao iceinjure


text:
Update README.md

No verification steps.
Update README.md to include further documentation and examples.

Coverage remained the same at 88.797% when pulling 66ffaaf47257b9c2dfaf55a11cca26671fd8bf46 on feature/readme into 295d4aebc8537c638430e375757e090ef95732a9 on master.

authors: coveralls rightlag

repo: pennsignals/aptos


text:
[BACKLOG-36356] Consolidate logic for setting dialog state and clean up

inconsistencies. Also handle the case in KettleVFS when opening a transformation for the first time and the variablespace is null.

:white_check_mark: Build finished in 9m 46s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
core,plugins/file-open-save-new/core

:exclamation: No tests found!
:information_source:  This is an automatic message

:white_check_mark: Build finished in 9m 52s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
core,plugins/file-open-save-new/core

:exclamation: No tests found!
:information_source:  This is an automatic message

authors: buildguy peterrinehart

repo: pentaho/pentaho-kettle


text:
WIP: Alt fee tests

Describe your changes
Issue ticket number and link
Checklist before requesting a review

[ ] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

REPLACE THIS TEXT WITH RATIONALE (CAN BE BRIEF)

I'm going to work out from an alternative branch, thanks for starting on this.

authors: erwanor zbuc

repo: penumbra-zone/penumbra


text:
Jsonified

instead of aliasing jsonvalue, actually derive json-compatible type information
use it like:
const x = new AnyMessage({});
const xJson = x.toJson() as Jsonified<AnyMessage>;

minimized for @jessepinho use, but more wip available

Not sure what you mean by "expanding the type," but the idea here is that Jsonified<X> is more useful than JsonValue since we know what shape it takes. That said, if we shouldn't be interacting with JSON-serialized objects directly, I suppose it's not that useful except as documentation of what object type it's serialized from.

authors: jessepinho turbocrime

repo: penumbra-zone/web


text:
K8SPS-173: K8SPS-173: Log setting safe size if the unsafe config is not allowed

CHANGE DESCRIPTION
Problem:
Resetting a component size to the minimum size allowed when allowUnsafeConfig is not set is invisible to the user and can lead to confusion.
Solution:
Log setting safe size if the unsafe config is not allowed
CHECKLIST
Jira

[x] Is the Jira ticket created and referenced properly?
[x] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
[x] Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

[x] Is an E2E test/test case added for the new feature/change?
[x] Are unit tests added where appropriate?

Config/Logging/Testability

[x] Are all needed new/changed options added to default YAML files?
[x] Are the manifests (crd/bundle) regenerated if needed?
[x] Did we add proper logging messages for operator actions?
[x] Did we ensure compatibility with the previous version or cluster upgrade process?
[x] Does the change support oldest and newest supported PS version?
[x] Does the change support oldest and newest supported Kubernetes version?

Test name
Status

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-haproxy
passed

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
failure

gr-scaling
passed

gr-self-healing
passed

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

service-per-pod
passed

sidecars
passed

smart-update
passed

tls-cert-manager
passed

users
passed

version-service
passed

We run 30 out of 30

commit: https://github.com/percona/percona-server-mysql-operator/pull/524/commits/d089af94e398af242c56bded375c83e761990f70
image: perconalab/percona-server-mysql-operator:PR-524-d089af9

authors: JNKPercona inelpandzic

repo: percona/percona-server-mysql-operator


text:
add initial icon pack for percussion tinymce theme

Initial checkin still needs testing

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@Yashdeep2001  Thanks! Is it still missing some of the plugin icons?  Like should there be 6 icons or are we using some default icons for some plugins?

authors: CLAassistant Yashdeep2001 natechadwick

repo: percussion/percussioncms


text:
percySnapshot is not defined

I started getting this issue on CI this morning. No percy related changes.
https://travis-ci.org/kellyselden/package-hint-historic-resolver/jobs/264821527#L2740

Hi @kellyselden.  Did you upgrade ember-exam or anything else in the testing pipeline?  We haven't made a change recently that would obviously lead to this.

I haven't. What happened was, greenkeeper gave me a PR for ember-cli-content-security-policy bumping to 1.0.0. Tests pass. Merged, then the failure. I haven't added new code to the project in forever, so what most likely happened is the npm cache got invalidated, and some dep is causing this now.

hmmm I have a hunch it is ember-cli-babel 6.8.0, which was just released...

@kellyselden Thanks Kelly, it'd be great to hear if that's the cause.  Otherwise, we're happy to help troubleshoot.

Here't the issue https://github.com/babel/ember-cli-babel/issues/178
I'm pretty sure it's related.

https://github.com/ember-cli/babel-plugin-ember-modules-api-polyfill/pull/19 is the root cause

basically import './helpers/percy-snapshot' is being removed, making the test helper undefined 😢

ember-cli-babel@6.8.1 has been published, which should fix this

Thanks @rwjblue.  @kellyselden, I'm closing this issue.  But please do feel welcome to re-open or resubmit if there's anything we can assist with.

authors: kellyselden rwjblue timhaines

repo: percy/ember-percy


text:
🛑 PeriodO legacy subdomain is down

In 3a6f8d9, PeriodO legacy subdomain (https://test.perio.do) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PeriodO legacy subdomain is back up in 7591bda after 14 minutes.

repo: periodo/periodo-status


text:
Grammar.parse talks about :c but it is actually :pos

grammar G { regex TOP { \d } }; my $str = ‘123’; my $g = G.new; for ^3 { $g.parse($str, :pos(2)).say }

｢3｣
｢3｣
｢3｣

Same with .subparse.
Also, maybe we should provide a .subparse example? For example:
grammar G { regex TOP { \d } }; my $str = ‘123’; my $g = G.new; for ^3 { $g.subparse($str, :pos($/.to // 0)).say }

:c() and :pos() should both work. They don't do the same function (:pos() implicitly anchors the search at the position, :c() does not).

@AlexDaniel where is its location? I cannot see this sentence inside the doc grammar or grammar_tutorial now

I think the issue was about this:

Additional named arguments are used as options for matching, so you can specify things like :c(4) to start parsing from the fourth character

https://docs.perl6.org/routine/parse#(Grammar)_method_parse
https://github.com/perl6/doc/blob/0b5126a5772e5047cbd9acda83be81e4b9da8d10/doc/Type/Grammar.pod6#L44

@AlexDaniel #1645 , how about other adverbs, I cannot figure it out

@W4anD0eR96 I think this can be closed? The original issue says that it should not talk about “:c(123)” and it no longer does, so that is it? I don't know about %opts, maybe create another issue for it?

@AlexDaniel , agree with you.

authors: AlexDaniel W4anD0eR96 softmoth


text:
Update community page

https://perl6.org/community/

[x] Add link to perl6weekly
[x] Make sure the mailing lists are still being maintained / used?
[x] Add a whole block section about how to contribute

Help with docs

show an example of how to Fork the docs repo, add an example, and submit a PR

Help with education resources

write tutorials
blog about your learning experience with Perl 6
blog about a module or script you wrote in perl 6
contribute to exercism.io

Help with ecosystem

link to state of the ecosystem document and most wanted modules document
write modules

Perl6Weekly is already in the blogroll on the homepage.

As of 2014, the lists have very low traffic (because most activity is on #perl6), but every question sent to it usually gets answered swiftly by at least one person.

This answers my question about the mailing lists.
Keeping the section on how to contribute more generic than the examples I gave, for now

https://github.com/perl6/perl6.org/pull/77


text:
Recommend neovim as one of the editors

Neovim does have a perl6 syntax file, but it is outdated: https://github.com/neovim/neovim/blob/master/runtime/syntax/perl6.vim
In any case, maybe it is actually usable? Perhaps somebody can try it and if it works even a little bit, we can list it too.

afaik this is available in normal vim too, but there exists https://github.com/vim-perl/vim-perl6.git which should work on both.

I'll try compiling neovim and give it a whirl, and see if the vim-perl/vim-perl6.git bundle works nicely with it as well. If the results are positive, I'll add it as a recommendation.

authors: AlexDaniel Tyil


text:
Update fs2-core to 2.4.1

Updates co.fs2:fs2-core from 2.3.0 to 2.4.1.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "co.fs2", artifactId = "fs2-core" } ]

labels: library-update, semver-minor

Codecov Report

Merging #117 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #117   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files          24      24
  Lines         234     234
  Branches        9       9
======================================
  Misses        234     234

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 7969631...2d88031. Read the comment docs.

authors: codecov-commenter scala-steward


text:
Update fs2-core to 2.3.0

Updates co.fs2:fs2-core from 2.2.2 to 2.3.0.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "co.fs2", artifactId = "fs2-core" } ]

labels: library-update, semver-minor

Codecov Report

Merging #79 into master will not change coverage by %.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #79   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files          24      24
  Lines         229     229
  Branches        7       7
======================================
  Misses        229     229

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 087542a...1c8cc49. Read the comment docs.

authors: codecov-io scala-steward


text:
Refactor Package & make it more consistent.

Since all the features of the package are now available, I think we need a refactoring to make everything more consistent.
We should word on following tasks:

core feature dart file should have the name of the feature.

if the name of the feature is commas the file name should have a name of commas.dart.

all the models classes should implement in the model.dart file.
all the constant for the specific feature should move to lib/src/constants/feature_name/constants.dart file.
Values that are not used as public APIs must be converted to private access.

@EhsanAramide  @m-khooryani If you are interested, you can do one of the tasks defined in our current project.  If you have any suggestion for this issue please leave comment and let me know.

Hi
I'd like to contribute to refactoring.

Ok khosro, so I will assign you to this issue.

Is refactoring ended or not?
@makhosravi
@payam-zahedi

Hi,
I'm working on it and will be ready soon

@all-contributors please add @makhosravi  for code, doc, example and test

@all-contributors please add @makhosravi for code, doc, example and test

@all-contributors please add @makhosravi for code, doc, example and test

@all-contributors please add @makhosravi for code

@all-contributors please add @makhosravi for review

authors: EhsanAramide makhosravi payam-zahedi

repo: persian-tools/dart-persian-tools


text:
Small PlannerParams fixes

Newer versions of OpenRAVE added an int options argument to the Planner::PlannerParameters::serialize() member function, which caused the attempted overrides in OMPLPlannerParameters and OMPLHolonomicPlannerParameters (which did not have the correct function signature) to not be called on copy.  This was causing bugs in parameter loading from pr-constraint.  This PR includes a configure-time check to see which to use.
This PR also renames the processing flag to be clearly specific to the derived class, to not confuse it with the similar flag in the base class.

Good catch! We got burned by this in CBiRRT before. :frowning:
I'm a bit concerned about using a flag set by add_definitions in a header file. The flag won't be set for packages that depend on or_ompl (e.g. those in pr-constraint), since it is passed as a compile-time flag. If this is necessary, then we should generate a header file that contains the flag using generate_export_header and #include it in the OMPLPlannerParameters.h.
However, it would be simpler to unconditionally define both functions. Is there any harm in defining the int overload if the user is building against an older version of OpenRAVE?

I chatted with @mkoval about the transient definition issue (good catch Mike!), and the problem with simply implementing both signatures is that it can't be determined which version of the base class method to call.  So the revised PR generates a config.h file in order to preserve the result of the test for dependent packages.  (This also simplifies those packages, which can simply include this file instead of duplicating the test, e.g. personalrobotics/pr-constraint@62c53ede77aaba93f22136e22951193dfd7380f3).
While mucking with include paths to get this to work, I noticed that the headers in or_ompl were referenced locally (#include "blah.h") instead of fully-qualified (#include <or_ompl/blah.h>).  I believe the latter convention is more widespread, easier to handle in dependent packages, and is also more consistent with auto-generated headers, so I switched to it.

:+1: Thanks for making the fix. Can you update pr-constraint to use this macro, too?
Good catch on the header include paths, too.

Yes, pr-constraint already does!

authors: cdellin mkoval


text:
Inheritance of ACL from Cell to Box

Enable to set Box Level ACL to Cell and inherit to all Boxes in Cell.

Released in v1.4.2

repo: personium/personium-core


text:
Move pacman logic to server

Will move pacman movement, score calculation to server.
Note: It has just moved client logic to server. Will be refactored.

Will change the data structure for pacman while refactoring.

@nimish-gupta we will be changing the data structure for Pacman and names as well.


text:
Ensure compatibility with Twig 3

The classes \Twig_Extension and \Twig_SimpleFunction have been removed in Twig 3 in favor of Twig\Extension\AbstractExtension and Twig\TwigFunction respectively. As these classes were only introduced in Twig 2.4.0, we have to drop support for older Twig versions here.
Silex support is dropped because the CalendRServiceProviderTest fails now without the \Twig_Extension class. As Silex is not maintained anymore, it should not be a problem to drop it's support. This should be considered as a BC-break.

Due to the BC-break, I think we consider releasing the 3.2.0 version.
What do you think about that?

If you want to follow Sem er, this would be a 4.0.0.

Is anything still unclear here that I could help with?

I've merged this PR and prepare to release the 4.0.0 version.

Great, thank you

Hey, it's been a while. Are you still planning to release version 4.0.0? Can I help with something?

The 4.0.0 is released and sorry for my delay response.
https://github.com/peter279k/fork-CalendR/releases/tag/4.0.0

Thank you!


text:
#1930  Modified copy_ros_msg.cpp file

… loops to range based forloop.
Description
MoveIt Python Library: Replace Traditional For Loops with Range-based For Loops #1930
All the traditional for loops within moveit_py folder are replaced with range based for loop.
Checklist

[x] Required by CI: Code is auto formatted using clang-format
[ ] Extend the tutorials / documentation reference
[ ] Document API changes relevant to the user in the MIGRATION.md notes
[ ] Create tests, which fail without this PR reference
[ ] Include a screenshot if changing a GUI
[ ] While waiting for someone to review your request, please help review another open pull request to support the maintainers

Hi @Sujeendra,
I am going to cherry pick your changes and add you as a coauthor on the commit. Ideally I would ask for you to rebase this but it is likely quicker to simply cherry pick in this case.

Hi @Sujeendra,
There are some errors when building the library based off of your changes see output below for details:
Starting >>> moveit
--- stderr: moveit_py
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp: In function ‘shape_msgs::msg::Mesh moveit_py::moveit_py_utils::MeshToCpp(const pybind11::object&)’:
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:152:44: error: invalid initialization of reference of type ‘const pybind11::object&’ from expression of type ‘pybind11::handle*’
  152 |     mesh_cpp.vertices.push_back(PointToCpp(&vertex));
      |                                            ^~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:86:56: note: in passing argument 1 of ‘geometry_msgs::msg::Point moveit_py::moveit_py_utils::PointToCpp(const pybind11::object&)’
   86 | geometry_msgs::msg::Point PointToCpp(const py::object& point)
      |                                      ~~~~~~~~~~~~~~~~~~^~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:157:52: error: invalid initialization of reference of type ‘const pybind11::object&’ from expression of type ‘pybind11::handle’
  157 |     mesh_cpp.triangles.push_back(MeshTriangleToCpp(triangle));
      |                                                    ^~~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:134:67: note: in passing argument 1 of ‘shape_msgs::msg::MeshTriangle moveit_py::moveit_py_utils::MeshTriangleToCpp(const pybind11::object&)’
  134 | shape_msgs::msg::MeshTriangle MeshTriangleToCpp(const py::object& mesh_triangle)
      |                                                 ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp: In function ‘moveit_msgs::msg::BoundingVolume moveit_py::moveit_py_utils::BoundingVolumeToCpp(const pybind11::object&)’:
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:172:29: error: invalid initialization of reference of type ‘const pybind11::object&’ from expression of type ‘pybind11::handle’
  172 |         SolidPrimitiveToCpp(primitive));
      |                             ^~~~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:120:71: note: in passing argument 1 of ‘shape_msgs::msg::SolidPrimitive moveit_py::moveit_py_utils::SolidPrimitiveToCpp(const pybind11::object&)’
  120 | shape_msgs::msg::SolidPrimitive SolidPrimitiveToCpp(const py::object& primitive)
      |                                                     ~~~~~~~~~~~~~~~~~~^~~~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:179:19: error: invalid initialization of reference of type ‘const pybind11::object&’ from expression of type ‘pybind11::handle’
  179 |         PoseToCpp(primitive_pose));
      |                   ^~~~~~~~~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:55:54: note: in passing argument 1 of ‘geometry_msgs::msg::Pose moveit_py::moveit_py_utils::PoseToCpp(const pybind11::object&)’
   55 | geometry_msgs::msg::Pose PoseToCpp(const py::object& pose)
      |                                    ~~~~~~~~~~~~~~~~~~^~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:185:52: error: invalid initialization of reference of type ‘const pybind11::object&’ from expression of type ‘pybind11::handle’
  185 |     bounding_volume_cpp.meshes.push_back(MeshToCpp(mesh));
      |                                                    ^~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:145:51: note: in passing argument 1 of ‘shape_msgs::msg::Mesh moveit_py::moveit_py_utils::MeshToCpp(const pybind11::object&)’
  145 | shape_msgs::msg::Mesh MeshToCpp(const py::object& mesh)
      |                                 ~~~~~~~~~~~~~~~~~~^~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:191:56: error: invalid initialization of reference of type ‘const pybind11::object&’ from expression of type ‘pybind11::handle’
  191 |     bounding_volume_cpp.mesh_poses.push_back(PoseToCpp(mesh_pose));
      |                                                        ^~~~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:55:54: note: in passing argument 1 of ‘geometry_msgs::msg::Pose moveit_py::moveit_py_utils::PoseToCpp(const pybind11::object&)’
   55 | geometry_msgs::msg::Pose PoseToCpp(const py::object& pose)
      |                                    ~~~~~~~~~~~~~~~~~~^~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp: In function ‘moveit_msgs::msg::CollisionObject moveit_py::moveit_py_utils::CollisionObjectToCpp(const pybind11::object&)’:
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:281:28: error: conversion from ‘pybind11::handle’ to non-scalar type ‘pybind11::object’ requested
  281 |     py::object primitive = py_primitive;
      |                            ^~~~~~~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:290:33: error: conversion from ‘pybind11::handle’ to non-scalar type ‘pybind11::object’ requested
  290 |     py::object primitive_pose = py_primitive_pose;
      |                                 ^~~~~~~~~~~~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:300:23: error: conversion from ‘pybind11::handle’ to non-scalar type ‘pybind11::object’ requested
  300 |     py::object mesh = py_mesh;
      |                       ^~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:309:28: error: conversion from ‘pybind11::handle’ to non-scalar type ‘pybind11::object’ requested
  309 |     py::object mesh_pose = py_mesh_pose;
      |                            ^~~~~~~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp: In function ‘moveit_msgs::msg::Constraints moveit_py::moveit_py_utils::ConstraintsToCpp(const pybind11::object&)’:
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:329:35: error: conversion from ‘pybind11::handle’ to non-scalar type ‘pybind11::object’ requested
  329 |     py::object joint_constraint = py_joint_constraint;
      |                                   ^~~~~~~~~~~~~~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:338:38: error: conversion from ‘pybind11::handle’ to non-scalar type ‘pybind11::object’ requested
  338 |     py::object position_constraint = py_position_constraint;
      |                                      ^~~~~~~~~~~~~~~~~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:347:41: error: conversion from ‘pybind11::handle’ to non-scalar type ‘pybind11::object’ requested
  347 |     py::object orientation_constraint = py_orientation_constraint;
      |                                         ^~~~~~~~~~~~~~~~~~~~~~~~~
/home/peterdavidfagan/Code/ws_moveit2/src/moveit2/moveit_py/src/moveit/moveit_py_utils/src/copy_ros_msg.cpp:356:40: error: conversion from ‘pybind11::handle’ to non-scalar type ‘pybind11::object’ requested
  356 |     py::object visibility_constraint = py_visibility_constraint;
      |                                        ^~~~~~~~~~~~~~~~~~~~~~~~
gmake[2]: *** [src/moveit/moveit_py_utils/CMakeFiles/moveit_py_utils.dir/build.make:76: src/moveit/moveit_py_utils/CMakeFiles/moveit_py_utils.dir/src/copy_ros_msg.cpp.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:263: src/moveit/moveit_py_utils/CMakeFiles/moveit_py_utils.dir/all] Error 2
gmake: *** [Makefile:146: all] Error 2
---
Failed   <<< moveit_py [4.85s, exited with code 2]
Aborted  <<< moveit [0.26s]

Would it be possible to address these, I will retest your changes and merge them after these issues have been resolved.

authors: Sujeendra peterdavidfagan


text:
再起動後に正常に画面回転が動作しなくなる (MiniBook X)

iio-sensor-proxyとの兼ね合いかもしれない
関連: #7

根拠はないがたぶん完了

repo: petitstrawberry/minibook-support


text:
Unexpected error trying to integrate Ax Hub

Hi
I am trying to integrate my AX Hub and I get an Unexpected error
In the integration dialog, I select "Use internal API lib (AXHub)", is that right?
This is what I find in the logs
Source: custom_components/hikvision_axpro/config_flow.py:178
Integration: hikvision_axpro
First occurred: 16:40:55 (2 occurrences)
Last logged: 16:44:24

Unexpected exception
Traceback (most recent call last):
  File "/config/custom_components/hikvision_axpro/hikax/hikax.py", line 38, in get_session_params
    session_cap = self.parse_session_response(response.text)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hikvision_axpro/hikax/hikax.py", line 66, in parse_session_response
    session_cap = SessionLoginCap.SessionLoginCap(
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: SessionLoginCap.__init__() missing 1 required positional argument: 'session_id_version'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/config/custom_components/hikvision_axpro/config_flow.py", line 178, in async_step_user
    info = await validate_input(self.hass, user_input)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hikvision_axpro/config_flow.py", line 151, in validate_input
    if not await hub.authenticate():
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hikvision_axpro/config_flow.py", line 116, in authenticate
    is_connect_success = await self.hass.async_add_executor_job(self.axpro.connect)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hikvision_axpro/hikax/hikax.py", line 93, in connect
    params = self.get_session_params()
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hikvision_axpro/hikax/hikax.py", line 41, in get_session_params
    raise errors.IncorrectResponseContentError()
errors.errors.IncorrectResponseContentError: Response content is not in expected form.````

AXHub internal lib is deprecated. Should not be used.

Ok, but when I don't use it, it throws an invalid authentication error. I am using my user/pwd from hikconnect app.

Yes but you have to be admin. Some users reported that when they do not use Admin user it does not work. Seems that normal user has no access to ISAPI.

Sorry, my mistake, I was introducing a wrong password. But with the right one I get an Unexpected Error. I am admin. Actually if I install SADP the admin password works

Well you are writing about Unexpected Error but not providing any logs...

Sorry I am not sure what is exactly happening. There are no logs in Home Assistant but what I see is that my hikvision central devices appears with several IPs in my router. When I open SADP there are two different entries with two IPs.
Maybe that is part of the problem.
When I try to add the integration, it sometimes throw me an Unexpected Error and sometimes Invalid Authentication, even the user/pwd is right.
I am going to try to reboot it to see what happens

Ok, after rebooting I still have two IPs. Anyway if I try any of them, the error is Invalid Authentication. I am using as username and password the same credentials as in HikConnect app. As far as I know, the user is admin because is the only user I have. Is there any way to really check if the user has the proper admin rights?

Well one IP will be ETH and second will be WiFi I guess.
During the setup try to check "debug output" and try again to get logs.
You can check in web UI of device.

Ok, that makes sense, thanks for the explanation.
I enabled debug output in the dialog but there are still no logs...

Ok, I got it. Instead or using my hikvision account user (my email), I had to use "admin". Probably is somewhere is the documentation and I did not see it

Anyway is fantastic, I see now all my AX-hub sensors and I can now trigger a snapshot from my frigate cameras when the sensors status change.
Thanks a lot

authors: MnemoBRMC petrleocompel


text:
Update Documentation

closes https://github.com/petuum/adaptdl/issues/44

Codecov Report

Merging #73 (d097a36) into master (780db06) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #73   +/-   ##
=======================================
  Coverage   61.16%   61.16%
=======================================
  Files          30       30
  Lines        2243     2243
  Branches      338      338
=======================================
  Hits         1372     1372
  Misses        806      806
  Partials       65       65

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 780db06...d097a36. Read the comment docs.

authors: codecov-io yukiontheiceberg

repo: petuum/adaptdl


text:
TEAM section to be extended with TESTING team

@AdelinaGuliman as Head of Testing will provide the list with people involved in testing of our software products developed by ASOCIATIA OPORTUNITATI SI CARIERE
We need their name, link to their linkedin account, link to github account and discord account
We also need a photo for each, moment where they give approval for their personal data stated above to be published on our website
@talidag

Diana Dragoi: GitHub, Linkedin, Discord: deedee_diana3

Florin Nistor: GitHub, Linkedin,  Discord: florin201092

Beatrix Racasanu: GitHub, Linkedin, Discord: itsybixyspider (

Elena Instratescu:GitHub, Linkedin, Discord: elena130399 (

Catalina Ion: GitHub, Linkedin, Discord: catalina.i (

Ionut Pintilie: GitHub, Linkedin, Discord: ionut0678

Bogdan Dumitrache: GitHub Linkedin, Discord: bogi1492

Melinte Camelia: GitHub Linkedin, Discord: kamikaze4616

The list is not over. I will come with more additions

@AdelinaGuliman please check what we added so far. Can you close this issue and continue to add members for another issue?

Caterina Bocaniciu, github: cati2023, https://www.linkedin.com/in/caterina-bocaniciu-121033305, Discord: cati2023

Silvia Podac, https://github.com/SilviaP27, linkedin.com/in/silvia-podac-621391268, Id-ul de discord: silvia13ps

To be continued...

@talidag this issue remains open as @DeedeeDL has started filling in the list of testers that will appear on the Opportunities and Careers site

Lucian Lodin, https://github.com/LucianLCI, www.linkedin.com/in/lodin-lucian-30527a294, Discord: lcigaming

Radu Lutu, https://github.com/RaduLutu, https://www.linkedin.com/in/radu-l-b37409252/, Discord: raduww

Andreea Plugaru, https://github.com/aplugaru,  https://www.linkedin.com/in/andreea-plugaru-1a496ba8, Discord: andreea_60587  ; poza nu are

Roxana Danalache, https://github.com/RoxanaDanalache, http://www.linkedin.com/in/roxana-danalache, Discord ID: 465862

authors: AdelinaGuliman DeedeeDL sebiboga talidag

repo: peviitor-ro/oportunitatisicariere


text:
"George Enescu", "Popeni" and "Stânca" are listed in the drop-down menu

Description:
"George Enescu", "Popeni" and "Stânca" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "George Enescu" in the search bar.

Expected results
The location is listed in the drop-down menu as "George Enescu, Botoșani (George Enescu)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Popeni" in the search bar.

Expected results
The location is listed in the drop-down menu as "Popeni, Botoșani (George Enescu)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Stânca" in the search bar.

Expected results
The location is listed in the drop-down menu as "Stânca, Botoșani (George Enescu)".


text:
Verify that "Lancrăm" is listed in the dropdown menu when searched

Description:
"Lancrăm" should appear in the dropdown menu with correct spelling and locality information.
Preconditions:
The website is up and running.

Step 1
Type "Lancrăm" in the search bar.
Expected results:
The dropdown is listing "Lancrăm" as the first location in the dropdown menu.


text:
"Rădăuți-Prut", "Miorcani" and "Rediu" are listed in the drop-down menu

Description:
"Rădăuți-Prut", "Miorcani" and "Rediu" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Rădăuți-Prut" in the search bar.

Expected results
The location is listed in the drop-down menu as "Rădăuți-Prut, Botoșani (Rădăuți-Prut)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Miorcani" in the search bar.

Expected results
The location is listed in the drop-down menu as "Miorcani, Botoșani (Rădăuți-Prut)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Rediu" in the search bar.

Expected results
The location is listed in the drop-down menu as "Rediu, Botoșani (Rădăuți-Prut)".


text:
"Scoroșești", "Valea Fântânei" and "Valea Ștefanului" are listed in the drop-down menu

Description:
"Scoroșești", "Valea Fântânei" and "Valea Ștefanului" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Scoroșești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Scoroșești, BUZĂU (Odăile)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Valea Fântânei" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Valea Fântânei, BUZĂU (Odăile)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Valea Ștefanului" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Valea Ștefanului, BUZĂU (Odăile)".


text:
”Sântandrei”, ”Șăulești”, ”Uroi” are listed in the drop-down menu

Description:
When user writes ”Sântandrei”, ”Șăulești”, ”Uroi” the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Sântandrei"

Expected results
The location appears in the drop-down menu as "Sat Sântandrei, HUNEDOARA (SIMERIA)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Șăulești"

Expected results
The location appears in the drop-down menu as "Sat Șăulești, HUNEDOARA (SIMERIA)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Uroi"

Expected results
The location appears in the drop-down menu as "Sat Uroi, HUNEDOARA (SIMERIA)".


text:
"Firtănuș", "Laz-Firtănuș", "Laz-Șoimuș" and "Medișoru Mic" are listed in the drop-down menu

Description:
"Firtănuș", "Laz-Firtănuș", "Laz-Șoimuș" and "Medișoru Mic" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Firtănuș" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Firtănuș, HARGHITA (Avrămești)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Laz-Firtănuș" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Laz-Firtănuș, HARGHITA (Avrămești)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Type "Medișoru Mic" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Medișoru Mic, HARGHITA (Avrămești)".