 You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
npm http fetch POST 426 http://registry.npmjs.org/-/npm/v1/security/advisories/bulk 83ms
npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
npm http fetch POST 426 http://registry.npmjs.org/-/npm/v1/security/audits/quick 56ms
npm verb audit error HttpErrorGeneral: 426 Upgrade Required - POST http://registry.npmjs.org/-/npm/v1/security/audits/quick
npm verb audit error     at /home/caio/.asdf/installs/nodejs/16.13.0/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:95:15
npm verb audit error     at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm verb audit error     at async Map.[getReport] (/home/caio/.asdf/installs/nodejs/16.13.0/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/audit-report.js:337:21)
npm verb audit error     at async Map.run (/home/caio/.asdf/installs/nodejs/16.13.0/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/audit-report.js:107:19)
npm verb audit error  HttpErrorGeneral: 426 Upgrade Required - POST http://registry.npmjs.org/-/npm/v1/security/audits/quick
npm verb audit error     at /home/caio/.asdf/installs/nodejs/16.13.0/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:95:15
npm verb audit error     at processTicksAndRejections (node:internal/process/task_queues:96:5)
npm verb audit error     at async Map.[getReport] (/home/caio/.asdf/installs/nodejs/16.13.0/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/audit-report.js:337:21)
npm verb audit error     at async Map.run (/home/caio/.asdf/installs/nodejs/16.13.0/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/audit-report.js:107:19) {
npm verb audit error   headers: [Object: null prototype] {
npm verb audit error     date: [ 'Thu, 28 Oct 2021 16:47:12 GMT' ],
npm verb audit error     'content-type': [ 'text/plain' ],
npm verb audit error     'content-length': [ '271' ],
npm verb audit error     connection: [ 'keep-alive' ],
npm verb audit error     'npm-notice': [
npm verb audit error       'Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/'
npm verb audit error     ],
npm verb audit error     vary: [ 'Accept-Encoding' ],
npm verb audit error     server: [ 'cloudflare' ],
npm verb audit error     'cf-ray': [ '6a55a5064a5362a7-BSB' ],
npm verb audit error     'x-fetch-attempts': [ '1' ]
npm verb audit error   },
npm verb audit error   statusCode: 426,
npm verb audit error   code: 'E426',
npm verb audit error   method: 'POST',
npm verb audit error   uri: 'http://registry.npmjs.org/-/npm/v1/security/audits/quick',
npm verb audit error   body: <Buffer 42 65 67 69 6e 6e 69 6e 67 20 4f 63 74 6f 62 65 72 20 34 2c 20 32 30 32 31 2c 20 61 6c 6c 20 63 6f 6e 6e 65 63 74 69 6f 6e 73 20 74 6f 20 6e 70 6d 20 ... 221 more bytes>,
npm verb audit error   pkgid: undefined
npm verb audit error }
npm timing auditReport:getReport Completed in 165ms
npm timing reify:audit Completed in 165ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/at-least-node Completed in 1123ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/end-of-stream Completed in 1124ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/shebang-command Completed in 1125ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/strip-final-newline Completed in 1125ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/merge-stream Completed in 1126ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@types/eslint-scope Completed in 1129ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/strip-bom Completed in 1130ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/is-number Completed in 1130ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/os-tmpdir Completed in 1131ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@types/json5 Completed in 1131ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/buffer-from Completed in 1132ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/path-parse Completed in 1132ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/error-ex Completed in 1133ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/brace-expansion Completed in 1134ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/is-extglob Completed in 1134ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/escape-string-regexp Completed in 1134ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/run-async Completed in 1134ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/mute-stream Completed in 1135ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/resolve-from Completed in 1135ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/wrappy Completed in 1135ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/parent-module Completed in 1135ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/path-is-absolute Completed in 1136ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/once Completed in 1136ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/inflight Completed in 1136ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/universalify Completed in 1137ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@types/parse-json Completed in 1137ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@babel/highlight/node_modules/has-flag Completed in 1135ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@babel/highlight/node_modules/ansi-styles Completed in 1137ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/parse-json Completed in 1139ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/color-name Completed in 1137ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/object-assign Completed in 1138ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/normalize-path Completed in 1138ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/require-from-string Completed in 1139ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/p-limit Completed in 1157ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/yocto-queue Completed in 1157ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/shebang-regex Completed in 1157ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/serialize-javascript Completed in 1159ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/path-key Completed in 1158ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/npm-run-path Completed in 1158ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/is-stream Completed in 1159ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/jest-worker/node_modules/supports-color Completed in 1159ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/json-parse-better-errors Completed in 1160ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/ansi-regex Completed in 1162ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/has-flag Completed in 1162ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/is-fullwidth-code-point Completed in 1162ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/lru-cache Completed in 1162ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/mimic-fn Completed in 1163ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/signal-exit Completed in 1163ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/onetime Completed in 1163ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/json-parse-even-better-errors Completed in 1164ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/callsites Completed in 1163ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/ieee754 Completed in 1164ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/macos-release Completed in 1164ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/is-unicode-supported Completed in 1164ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/is-interactive Completed in 1165ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/windows-release Completed in 1166ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/restore-cursor Completed in 1166ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/strip-ansi Completed in 1166ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/figures Completed in 1167ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/cli-cursor Completed in 1167ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/inherits Completed in 1166ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/path-type Completed in 1167ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/import-fresh Completed in 1167ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@babel/highlight Completed in 1166ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@babel/highlight/node_modules/supports-color Completed in 1166ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@babel/code-frame Completed in 1168ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/to-regex-range Completed in 1168ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/string-width Completed in 1167ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/fill-range Completed in 1168ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/is-glob Completed in 1168ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/glob-parent Completed in 1169ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/is-binary-path Completed in 1169ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/anymatch Completed in 1169ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/supports-color Completed in 1170ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/os-name Completed in 1175ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/esrecurse Completed in 1188ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/helper-api-error Completed in 1190ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/glob-to-regexp Completed in 1190ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/defaults Completed in 1191ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/clone Completed in 1191ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/yallist Completed in 1191ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/string_decoder Completed in 1192ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/util-deprecate Completed in 1192ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/base64-js Completed in 1192ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/log-symbols Completed in 1192ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/balanced-match Completed in 1193ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/tmp Completed in 1192ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/ansi-escapes Completed in 1193ms
npm timing<EMAIL_ADDRESS>Completed in 1193ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/js-tokens Completed in 1191ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/minimatch Completed in 1193ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@types/json-schema Completed in 1194ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/ansi-styles Completed in 1194ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/pluralize Completed in 1194ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/tree-kill Completed in 1197ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/which Completed in 1210ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/pump Completed in 1211ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/get-stream Completed in 1211ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/picocolors Completed in 1211ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@xtuc/ieee754 Completed in 1213ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/floating-point-hex-parser Completed in 1213ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/loader-runner Completed in 1213ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/mime-types Completed in 1213ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@types/estree Completed in 1214ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/has Completed in 1215ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/interpret Completed in 1214ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/lines-and-columns Completed in 1215ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/binary-extensions Completed in 1215ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@babel/highlight/node_modules/color-name Completed in 1213ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/readdirp Completed in 1214ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/webpack-node-externals Completed in 1215ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/ora Completed in 1216ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/randombytes Completed in 1231ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/ieee754 Completed in 1231ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/wasm-opt Completed in 1231ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/helper-buffer Completed in 1232ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/helper-numbers Completed in 1233ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/punycode Completed in 1232ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/safe-buffer Completed in 1233ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/is-arrayish Completed in 1233ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/cli-spinners Completed in 1233ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/jsonfile Completed in 1233ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/rimraf Completed in 1235ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/acorn-import-assertions Completed in 1249ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/concat-map Completed in 1248ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@babel/helper-validator-identifier Completed in 1246ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@babel/highlight/node_modules/color-convert Completed in 1246ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/color-convert Completed in 1247ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/ansi-colors Completed in 1250ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/chalk Completed in 1252ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/isexe Completed in 1265ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/estraverse Completed in 1264ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/esrecurse/node_modules/estraverse Completed in 1265ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/wast-printer Completed in 1265ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/chrome-trace-event Completed in 1266ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/wasm-edit Completed in 1266ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/safer-buffer Completed in 1265ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/graceful-fs Completed in 1265ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@babel/highlight/node_modules/chalk Completed in 1263ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/escalade Completed in 1284ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/rechoir Completed in 1284ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/log-symbols/node_modules/chalk Completed in 1284ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/glob Completed in 1282ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/tsconfig-paths-webpack-plugin/node_modules/chalk Completed in 1283ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/ora/node_modules/chalk Completed in 1284ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/inquirer/node_modules/chalk Completed in 1285ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/fork-ts-checker-webpack-plugin/node_modules/chalk Completed in 1286ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@angular-devkit/schematics-cli/node_modules/chalk Completed in 1287ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/terser/node_modules/commander Completed in 1300ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/cross-spawn Completed in 1300ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/node-releases Completed in 1300ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/helper-wasm-bytecode Completed in 1301ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/emoji-regex Completed in 1301ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/wcwidth Completed in 1299ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/buffer Completed in 1310ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/cli-width Completed in 1311ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/schema-utils/node_modules/json-schema-traverse Completed in 1308ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/source-map-support Completed in 1310ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/webpack/node_modules/json-schema-traverse Completed in 1310ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/commander Completed in 1311ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/electron-to-chromium Completed in 1323ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/helper-wasm-section Completed in 1324ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/is-core-module Completed in 1324ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/through Completed in 1322ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/deepmerge Completed in 1321ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/fast-deep-equal Completed in 1321ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@angular-devkit/schematics-cli/node_modules/tslib Completed in 1323ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/leb128 Completed in 1335ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/function-bind Completed in 1335ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/sourcemap-codec Completed in 1333ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/cli-table3 Completed in 1332ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/wasm-gen Completed in 1345ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/watchpack Completed in 1345ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/es-module-lexer Completed in 1345ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/tslib Completed in 1345ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/braces Completed in 1341ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/symbol-observable Completed in 1342ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/execa Completed in 1358ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/browserslist Completed in 1357ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/bl Completed in 1356ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/fs-monkey Completed in 1356ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/utf8 Completed in 1367ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/picomatch Completed in 1362ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/chokidar Completed in 1364ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/human-signals Completed in 1377ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/chardet Completed in 1373ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/mime-db Completed in 1384ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/external-editor Completed in 1381ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/json-schema-traverse Completed in 1379ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/webpack/node_modules/terser-webpack-plugin Completed in 1381ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/ajv-formats Completed in 1387ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/wasm-parser Completed in 1400ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/tapable Completed in 1395ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/fast-json-stable-stringify Completed in 1395ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/eslint-scope Completed in 1408ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@xtuc/long Completed in 1416ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/json5 Completed in 1416ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/minimist Completed in 1418ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/enhanced-resolve/node_modules/tapable Completed in 1435ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/webpack/node_modules/tapable Completed in 1430ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@types/eslint Completed in 1455ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/node-emoji Completed in 1452ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/colors Completed in 1459ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/tsconfig-paths-webpack-plugin Completed in 1480ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/magic-string Completed in 1486ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/webpack/node_modules/schema-utils Completed in 1488ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/webpack-sources Completed in 1499ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/schema-utils Completed in 1505ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/jest-worker Completed in 1522ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/events Completed in 1521ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/readable-stream Completed in 1519ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/schema-utils/node_modules/ajv-keywords Completed in 1527ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/webpack/node_modules/ajv-keywords Completed in 1527ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/source-map Completed in 1531ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/acorn Completed in 1544ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@angular-devkit/schematics-cli/node_modules/inquirer Completed in 1537ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/iconv-lite Completed in 1556ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/inquirer Completed in 1557ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/tsconfig-paths Completed in 1565ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/jsonc-parser Completed in 1573ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/memfs Completed in 1581ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/type-fest Completed in 1591ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/cosmiconfig Completed in 1600ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/shelljs Completed in 1605ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/semver Completed in 1611ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@angular-devkit/schematics-cli Completed in 1613ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/fork-ts-checker-webpack-plugin/node_modules/fs-extra Completed in 1621ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/fs-extra Completed in 1628ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/enhanced-resolve Completed in 1637ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/source-map-support/node_modules/source-map Completed in 1650ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/webpack/node_modules/source-map Completed in 1650ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@webassemblyjs/ast Completed in 1661ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/uri-js Completed in 1688ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/yaml Completed in 1730ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/neo-async Completed in 1813ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/terser Completed in 1908ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/schema-utils/node_modules/ajv Completed in 1905ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/webpack/node_modules/ajv Completed in 1904ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@types/node Completed in 1926ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/resolve Completed in 1931ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@angular-devkit/schematics Completed in 1971ms
npm timing reifyNode:node_modules/@nestjs/cli Completed in 2034ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@angular-devkit/core Completed in 2029ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/fork-ts-checker-webpack-plugin Completed in 2135ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@nestjs/schematics Completed in 2453ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/ajv Completed in 2500ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/caniuse-lite Completed in 2786ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/webpack Completed in 2848ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/lodash Completed in 2910ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/@angular-devkit/schematics-cli/node_modules/rxjs Completed in 3646ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/rxjs Completed in 3950ms
npm timing reifyNode:node_modules/@nestjs/cli/node_modules/typescript Completed in 3958ms
npm timing reify:unpack Completed in 3972ms
npm timing reify:unretire Completed in 0ms
npm timing build:queue Completed in 13ms
npm timing build:link:node_modules/@nestjs/cli Completed in 8ms
npm timing build:link:node_modules/@nestjs/cli/node_modules/@angular-devkit/schematics-cli Completed in 8ms
npm timing build:link:node_modules/@nestjs/cli/node_modules/json5 Completed in 8ms
npm timing build:link:node_modules/@nestjs/cli/node_modules/rimraf Completed in 8ms
npm timing build:link:node_modules/@nestjs/cli/node_modules/browserslist Completed in 9ms
npm timing build:link:node_modules/@nestjs/cli/node_modules/semver Completed in 8ms
npm timing build:link:node_modules/@nestjs/cli/node_modules/shelljs Completed in 8ms
npm timing build:link:node_modules/@nestjs/cli/node_modules/terser Completed in 9ms
npm timing build:link:node_modules/@nestjs/cli/node_modules/tree-kill Completed in 9ms
npm timing build:link:node_modules/@nestjs/cli/node_modules/typescript Completed in 9ms
npm timing build:link:node_modules/@nestjs/cli/node_modules/which Completed in 8ms
npm timing build:link:node_modules/@nestjs/cli/node_modules/webpack Completed in 8ms
npm timing build:link:node_modules/@nestjs/cli/node_modules/acorn Completed in 11ms
npm timing build:link Completed in 12ms
npm timing build:deps Completed in 25ms
npm timing build Completed in 25ms
npm timing reify:build Completed in 25ms
npm timing reify:trash Completed in 1ms
npm timing reify Completed in 13351ms
added 252 packages in 14s
38 packages are looking for funding
run npm fund for details
npm timing command:install Completed in 13355ms
npm verb exit 0
npm timing npm Completed in 13503ms
npm info ok
Reshimming asdf nodejs...`
Actual Behavior
Stop in the initial steps
$ npm install -g @nestjs/cli --verbose
npm verb cli [
npm verb cli   '/home/caio/.asdf/installs/nodejs/16.13.0/bin/node',
npm verb cli   '/home/caio/.asdf/installs/nodejs/16.13.0/bin/npm',
npm verb cli   'install',
npm verb cli   '-g',
npm verb cli   '@nestjs/cli',
npm verb cli   '--verbose'
npm verb cli ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm timing npm:load:whichnode Completed in 0ms
npm timing config:load:defaults Completed in 1ms
npm timing config:load:file:/home/caio/.asdf/installs/nodejs/16.13.0/lib/node_modules/npm/npmrc Completed in 1ms
npm timing config:load:builtin Completed in 1ms
npm timing config:load:cli Completed in 2ms
npm timing config:load:env Completed in 0ms
npm timing config:load:file:/home/caio/ico/cc/cc-backend/.npmrc Completed in 1ms
npm timing config:load:project Completed in 1ms
npm timing config:load:file:/home/caio/.npmrc Completed in 1ms
npm timing config:load:user Completed in 1ms
npm timing config:load:file:/home/caio/.asdf/installs/nodejs/16.13.0/.npm/etc/npmrc Completed in 0ms
npm timing config:load:global Completed in 0ms
npm timing config:load:validate Completed in 1ms
npm timing config:load:credentials Completed in 0ms
npm timing config:load:setEnvs Completed in 1ms
npm timing config:load Completed in 8ms
npm timing npm:load:configload Completed in 8ms
npm timing npm:load:setTitle Completed in 0ms
npm timing npm:load:setupLog Completed in 0ms
npm timing config:load:flatten Completed in 1ms
npm timing npm:load:cleanupLog Completed in 2ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load:projectScope Completed in 1ms
npm timing npm:load Completed in 21ms
npm timing arborist:ctor Completed in 1ms
npm timing idealTree:init Completed in 4ms
npm timing idealTree:userRequests Completed in 1ms
⸨⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⠂⸩ ⠹ idealTree:lib: sill idealTree buildDeps
Diagnostic Logs
https://aka.ms/AAeizd8

I'm getting a similar issue (haven't tried connecting to a vpn) -- my npm install just hangs at buildDeps...

The problem here is ipv6

On Ubuntu 22.04 under WSL2 disabling ipv6 on my NIC immediately fixed npm install
Notes here on my steps for node under WSL2


Ch implement feedback 161456525

what does this PR do?
Implement changes proposed by LFA
Description of task accomplished?
Made the login output more descriptive
Retrieved the role from the database
Displayed the unit price in sales
Fixed validation error
How should this app be manually tested?
Clone the repo to your local machine
run the app by running run.py
test the app by using pytest
What are the relevant Pivotal tracker stories?
#161456525

Pull Request Test Coverage Report for Build 90

51 of 56 (91.07%)  changed or added relevant lines in 8 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.6%) to 91.255%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/api/v1/model/users.py
13
14
92.86%

app/api/v1/views/sales.py
4
5
80.0%

app/api/v1/views/users.py
1
2
50.0%

app/api/v1/model/sales.py
14
16
87.5%

Files with Coverage Reduction
New Missed Lines
%

app/api/v1/views/sales.py
1
80.56%

Totals

Change from base Build 75:
-0.6%

Covered Lines:
240

Relevant Lines:
263

💛  - Coveralls


Allow concatenation of statistics

Allow user to concatenate statistics with & operator.  Will format and combine into a single column.

Not sure about this.


Optimize shard index loading

Required for all non-trivial PRs

[x] Rebased/mergable
[ ] Tests pass
[x] CHANGELOG.md updated

On data sets with many series,  large series keys and many shards,
the cost of parsing the key and re-indexing can be high.
Loading the TSM keys into the index was being done repeatedly for
series that were already loaded into the index by an earlier TSM file.  This was
wasted worked and slows down shard loading.
Parsing the key was also innefficient and allocated a new string
slice.  This was simplified to remove that allocation.
I tested this on a dataset with two databases containing 155 and 85 shards each with ~300k series keys in each DB and keys ~250bytes in length.
0.13.0 (old/new)
5:32 -> 0:32
master (old/new)
4:25 -> 0.33
master cache flushed (old/new)
5:09 -> 1:42
This should help #6250 in some cases although there may still be other bottlenecks that this data set does not bring out.

+1

This is insanely good. Here is a real world change - from nearly 40 minutes to under 2 minutes:
Version 0.12.2-1:
[retention] 2016/05/16 15:43:51 Starting retention policy enforcement service with check interval of 10m0s
[run] 2016/05/16 15:43:51 Listening for signals

Latest nightly:
[run] 2016/05/16 15:53:29 InfluxDB starting, version 0.14.0~n201605160800, branch master, commit 2c9d0fcc04eba3ffc88f2aafe8466874e384d80d
[run] 2016/05/16 15:56:08 Listening for signals

Amazing work!!

+1


Added Pastebin command

Overview
This was a feature mentioned under "Issues" that I wanted to give a shot. Wasn't marked "help wanted" so if you don't want to use it, it's fine.
This uses the Pastebin Api (developer api key must be set in config.js) to allow users to create Pastebin pastes using a "!paste {text}" command and returns a url to their paste. I did my best to stick to ES6 and the procedures set up in other commands.
It passes the test I made, but this was my first encounter with Nock, so it should be double-checked. I used the other test files as a template.
Also added command info under the English "help" section.
Screenshots
![Screenshot 1]
(https://i.gyazo.com/a6771d8c9f966dd1b9a0f628af074a3d.png)
![Screenshot 2]
(https://i.gyazo.com/740d319222fccec520e22cb60fe15314.png)

@etp12 This is great, thanks. Just two very minor comments. Give me a ping once they're fixed and I'll be happy to merge!

@etp12 This is great, thanks. Just four very minor comments. Give me a ping once they're fixed and I'll be happy to merge!

@dustinblackman Let me know if these changes look good!

Perfect, thanks again!


Examples contain misleading version restrictions

Some of your examples reference the sts module terraform-redhat/rosa-sts/aws.
This module has a restriction to only support version 4.x.x  of terraform, not >4.
Whilst that is not related to this provider directly, this projects examples show >= 4.x.x as being allowed.
I am currently using 5.x.x but cannot follow the examples due to the restriction in the sts module. I have raised an issue last week on that repo but have not met a response yet. https://github.com/terraform-redhat/terraform-aws-rosa-sts/issues/23

Hi @OurFriendIrony ,
Thank you for the feedback
We work on improving the examples, targeting this as well

Has any progress been made on this? I believe the module issue still hasn't received any responses highlighting any future changes

Hi @OurFriendIrony ,
We are working on new module which also is going to contain all examples with improvements.
This is the new repository opened for this purpose:
https://github.com/terraform-redhat/terraform-rhcs-rosa
We will update here when this new module will be published

Will this deprecate https://github.com/terraform-redhat/terraform-aws-rosa-sts/issues/23 ?

Hi @OurFriendIrony
Yes, finally the old module will be deprecated
If you need it for now, I can create quick fix changes the AWS version to ">=4.x.x", and release special module tag for this
You will have to change the module source version manually in the examples you use
In case you want this change, what is the module version you use?

No it is fine, I can move over to the new module.
Thanks.
On Wed, 20 Sept 2023, 13:40 Nir Argaman, @.***> wrote:

Hi @OurFriendIrony https://github.com/OurFriendIrony
Yes, finally the old module will be deprecated
If you need it for now, I can create quick fix changes the AWS version to
">=4.x.x", and release special module tag for this
You will have to change the module source version manually in the examples
you use
In case you want this change, what is the module version you use?
—
Reply to this email directly, view it on GitHub
https://github.com/terraform-redhat/terraform-provider-rhcs/issues/207#issuecomment-1727646052,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7MONS4ZCHJCAZ6HUJJQK3X3LP47ANCNFSM6AAAAAA2RRBZXM
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

This was fixed in rosa-sts module in version 0.0.14
Also new module is in work in progress already with this issue solved
Closing this issue


[eslint] Parsing error: Unexpected token

From @AkashiX on May 4, 2017 14:14

VSCode Version: 1.11.1
OS Version: Win 10

I get this error when using async/await keywords to declare a function, what's matter? by the way, I had installed eslint plugin inside Vscode.
Copied from original issue: Microsoft/vscode#25896

@AkashiX What version of eslint are you using? Can you share some example code?

This error usually indicates a problem with your ESLint config file like .eslintrc.json.
I am closing the issue. Please share and example if the explanation is not solving your problem.


To complete a contextMenus.

To complete a contextMenus.
I need to customize mode to assess.

The basic function choosen target has been moved in the website. I created two button tag in the page.

Got it!


Add Property-based Tests (via FsCheck)

Property-based tests should supplement (and not replace) existing unit tests.

This has been started in PR #16


@rendermode InteractiveServer

Description
Error	CS0103	The name 'rendermode' does not exist in the current context	BlazorApp1	C:\SL\BlazorApp1\BlazorApp1\Pages\Index.razor	2	Active
[Enter feedback here]
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/tutorials/signalr-blazor?view=aspnetcore-8.0&tabs=visual-studio
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/tutorials/signalr-blazor.md
Document ID
85af7a99-672c-0438-dcc2-e8edfaf70c54
Article author
@guardrex

Hello @joaocolombo ... Did you install the 8.0 SDK (or fully update your VS)? It sounds like you're using one of the preview releases from back when the render mode was specified by @attribute and not @rendermode.

I'm going to close because I think you'll just need to update to the release SDK. Please post back if that isn't the problem.


Create docker-publish.yml

took starter code + removed on schedule build

1st build failed due to

[6/8] RUN git clone -b develop https://git.pleroma.social/pleroma/pleroma.git /pleroma     && git checkout develop:
0.057 Cloning into '/pleroma'...
0.063 Error relocating /usr/lib/libcurl.so.4: SSL_get0_group_name: symbol not found


About guidance_scale

Hi @luosiallen, I love your work! But I have one question.
As suggested in latent-consistency/lcm-lora-sdv1-5, it is recommended to disable guidance_scale or use values between 1.0 and 2.0. The effect of guidance_scale can be found in this post. But in the paper, it seems that it should be fine to set the guidance_scale to 7.5 for classifier-free guidance. What causes this difference?

The detailed implementation of LCM LoRA is slightly different with the origin LCM training. We do not add additional flexible w_embedding into LCM. We distill a fix cfg scale with 7.5 during LCM training already.

@luosiallen I have a follow-up question on CFG guidance used during training. In the released training code for LCM lora, a random CFG guidance within [w_min, w_max] will be sampled at each iteration, and w_min = 5.0, w_max = 15.0 as shown below.
https://github.com/luosiallen/latent-consistency-model/blob/a9ad79587cc8bd1e404ccd1a3056a3da969b2f62/LCM_Training_Script/consistency_distillation/train_lcm_distill_lora_sd_wds.py#L644-L665
However, in the report it is stated that a fixed CFG scale = 7.5 is used.

I was wondering why there's a difference between the report and the code and if this is something we should take into account when training our own LCM lora. Thanks in advance.

Before the LCM Lora was released, luosiallen released a distilled version of dreamshaper7 as a full model. I'd assume the CFG variation in the training code is a remnant from training that model and LCM Lora was trained strictly with CFG 7.5.
The distilled model accepted the CFG as a direct model parameter rather than being a part of the sampling process. I assume the CFG parameter was omitted to avoid changing the model architecture through the Lora.


Disconnection email failure

@rosuav reported on python-buildbots@ not receiving an email from the master that his worker had disconnected.  As a worker owner, this is a very handy email and we should make sure it's working correctly.

I've determined that this is due to a bug in buildbot; the fix is tracked in buildbot/buildbot#4131.


Mutable TreeMap ignores multiplicities when adding another Map with ++=

I noticed that adding elements to a mutable TreeMap with ++= adds only one element from each bucket.
import scala.collection.mutable

implicit val config = mutable.TreeBag.configuration.compact[Int]

val x1 = mutable.TreeBag.from(1 -> 1)
val x2 = mutable.TreeBag.from(3 -> 3)

x1 ++= x2

println(x1)

This produces Bag(1; 3), but I would expect it to produce Bag(1; 3, 3, 3) instead. Using ++ works, by the way.

OK, seems like that is a problem with my dependency management. When I execute the above code in your project, it produces the expected results. But in other projects that download multisets as a dependency from Maven Central, I get the wrong output.

OK, seems like this was fixed in c82126e, but not released yet.


node_http2.cc: void node::http2::Http2Session::CheckAllocatedSize(size_t) const: Assertion `(current_nghttp2_memory_) >= (previous_size)' failed.

When upgrading from grpc to grpc-js, we encountered the following error in tests/integration.spec.ts:
https://github.com/wechaty/grpc/blob/920bebdf4ccce5567a50557d7baabf2fd0777426/tests/integration.spec.ts#L91-L93
node[122920]: ../src/node_http2.cc:449:void node::http2::Http2Session::CheckAllocatedSize(size_t) const: Assertion `(current_nghttp2_memory_) >= (previous_size)' failed.

Node Versions
All node major versions will be affected: 10/12/14/15
Similiar Issues

https://github.com/ExchangeUnion/xud/pull/1605#issuecomment-744070598
https://github.com/EventStore/EventStore-Client-NodeJS/issues/125
https://github.com/grpc/grpc-node/issues/1652
https://github.com/grpc/grpc-node/issues/1464

Workaround
+ await new Promise(resolve => setImmediate(resolve))
eventStream.cancel()

I opened https://github.com/nodejs/node/issues/38964 against nodejs as I ran into the same assertion failure you saw. The same setImmediate fix you suggested helps with my repro case as well, but thought you might want to track the issue on nodejs side as well.

Thanks for filing the issue on the nodejs side, I believe there must be a bug in nodejs and it should be definitely fixed.

According to https://github.com/nodejs/node/issues/38964#issuecomment-863917244 I believe this problem will be fixed in the next major version of Node.js


UI kits alternatives

Guys,
I have no idea what to give up first, if ractive (and use other projects just because of lack of UI kits), or give up react, (because it's just a mess, setting up babel, compilers, precompilers, post compilers, compiler's compilers, etc)
So I decided to try to start a project for ractive, based on components. I need great UI design, but dont want to use jquery and really like material design principles.
Couldn't find anything worth it out there, so the idea is to build components based on Material-UI for React but using RactiveJS.
Before writing this, I even tried to implement react into my new project.  I REALLY want to use ractive but I was no able to find any solid UI kit.
Maybe this should have been better posted on stackoverflow, but I think here will find people already using ractive on production and might get something out of this.
GOAL: Implement Material-UI components for Ractive without using JQuery (I could have just used materialized and jquery for example)
I chose Material-UI because it's components are really solid, and there is almost anything you would need to build a project.
Things I already tried but failed, or required more work than implementing UI from zero:

PhononJS+Ractive: Works fine, but some components have problems when rendered dynamically
Material Design Lite: Started to look good, but got problems when "upgrading the dom" and they even confirmed that the project was not intended to use in dynamic environments.

It would be amazing if I get some positive feedback and maybe form a small team to do this on any way, since the idea of "forking" material-ui it's just an idea, I'm totally open to new ones.
Thanks, and sorry for long post.

Having gone over the components documentation yesterday, I'd say it's entirely possible. The only problem we have when doing these sort of things is the lack of momentum, especially when you have to keep up with the times and have frameworks outpace you every time.
In related news, there have been attempts to integrate Ractive with other UI libraries. The one I remember is @dagnelies 's Ractive-Bootstrap. Maybe you could get in touch with him on this adventure.
For me, this is a 👍

Having the same need as you, some weeks ago I investigated "porting" Material Design Lite into Ractive components world.
As for updating DOM, take a look at MDL v2 (master branch) - they introduced quite clean way to integrate JS-based MD components with DOM-oriented view libraries. There are examples for some popular libs included - e.g. https://github.com/google/material-design-lite/tree/master/examples/vue/src/v-mdl-drawer.
Unfortunately, version 2 is still in progress and not all MD components are rewritten yet.

I'm definitely :+1: to an "official" ui library. I think it would help tremendously to have some common components, decorators, events, etc that were available in a conveniently bundle-able way. Most of the components I run across a need for exist in some form in the community (or are super simple to make), but I think a material design collection would be awesome.

Thanks for such nice replies.
@fskreuz I totally agree with you, and it was the first problem i thought of. But I have already 2 or 3 weeks searching around for options. I checked almost all "view" js frameworks and their respective UI kits. I literally have more than 100 folders in a folder called TempAndTesting. I think in 3 weeks I could have already something running  by now :(  I checked vue, and their options, and digging around all the Chinese docs I found that there is no solid alternative, but a bunch of small (but good) pieces to build the UI, but that lacks the uniformity that an UI should have.
I will totally poke him and see if he can at least point the project in the right direction (or maybe get him involved, muahaha).
@mefjuu I also checked v2, but since it's not quite released yet, i dont know if it's a good idea or not, maybe it's the best shot we have, at least the easiest, since it's design for that. But i still havent checked the entire project and it's ambitions and scope.  But yes, it's an option for sure.
@evs-chris exactly! it's not much about the component's behavior, but more about design. And material for me is the way to go for enterprise apps, they just look good enough without being all flashy.
From this convo i see that we have those two options, port Material-UI or wrap around MDLv2.
Now i will do small research, to see how both implementations will look like. Because wrapping can be sometimes "ugly", and who knows how sexy the final code for a React port will be.
What do you think?
Thanks again guys!!!

SMALL UPDATE: I really liked it, but seems like material-ui for react cant be elegantly ported, since they (i didn't know) hardcode the styles on each component. Which maybe "nice", but make too hard to implement different styles/themes. And also more stuff to port and keep the project up to date.
Last option is to do it via MDLv2. OR of course, read all design guides and do it our way.
I'm going to build a small code pen with it, and see how it looks.
Thoughts?
Question:  Should we keep these stuff in this issue? or you want to move it somewhere else?

What I normally do with Ractive components with regards to theming is to not bake in the CSS into the component at all.
Instead, I use BEM to give a predictable name to the elements as well as have very low-specificity selectors. I'd have two stylesheets, one is for a wireframe-y rendering (structure, no colors and specifics) and another for the actual theme, the same way Bootstrap 3 does it. The first CSS file is required, the other can be swapped out depending on the theme.
const MyMaterialComponent = Ractive.extend({
  template: `

...

  `
});

.my-material-component{}
.my-material-component__something{}
.my-material-component__something-else{}
.my-material-component__something-else--modifier{}

Should we keep these stuff in this issue? or you want to move it somewhere else?

If you have a separate repo, sure you can move. Just make sure everyone's informed. 😄

True, me too, but now I think we should stick to whatever "base" project's nomenclature they chose.
Otherwise this project would require a complete rewrite, which I would love, but probably we wont have time for.
Right now, I'm evaluating MDL v2,.
I also found this: https://www.muicss.com , looks fine. I will keep you guys posted.
Any ideas are fully accepted (and needed)
Will create repo as soon as decide what project we will base the components from.

+1 for BEM
+1 for keeping styles externally in *.css file
MDL v2 has very nice architecture (but looks too overcomplicated somewhere).
I will check MUICSS...

UPDATE: Google's MDLv2 is going to take too long probably (i accept suggestions on how to implement it), and they don't have any docs (yet) on how to implement everything, and source code lacks any comment whatsoever.  I dont want to go and start guessing or asking around for something they haven't event release, if they ever do.
Still gonna keep trying on MDL, @mefjuu  if you like MUICSS let me know, maybe try a small component on codepen if you have the time.

Jesus, i have this internal fights with myself, about MDL, do it from scratch or try MUICSS xD

A bit off topic, but for simple UI wrappers, I'd be nice to have something like #1535 implemented in the future.

@dagnelies nice issue, i will comment there something I was thinking before.

+1 for MaterializeCss

Everyone is welcome here:
https://github.com/andreujuanc/Ractive-Materialize
@paulocoghi  🎱
@mefjuu Checked MUICSS?
@fskreuz Gonna stick with materialize for now. Maybe some day if we gonna start our own UI project, we will use BEM for that, for sure.


Mod Conflict with ???? is hiding UI when resizing GSE Windows

Resizing the main GSE3 window, makes WOW UI totally disappear.
Seems the UI to still be there in the background in some form ( can hear sound from menu )
Not providing any screenshow, because its the same as pressing ALT+Z
PS: have 2 screens, but 2nd was off atm.

I cannot make this happen.  Mate I need a ton more information as if I follow your directions nothing changes for me except the windows change size.

This is one of those GSE + something on your computer is causing this.  Need to know which other mod causes the conflict.

Uploading a video right now.
As you can see resizing sideways, make this bug appear.
I know it has to do with the second screen for sure ( even when its off ).
Ths options to move desktop icons ( or even clone taskbar ) to 2nd screen are off.
https://mega.nz/file/Uh02yTIb#4ewbayGEX42arGujxzf9o9XmVRrenybjx7VvAFgTlzE
PS: video was around 200mb so i could not upladed here.

I have three monitors - did the exact same thing and didn't get the result
you get.
On Thu, 8 Jul 2021 at 17:26, lloskka @.***> wrote:

Uploading a video right now.
As you can see resizing sideways, make this bug appear.
I know it has to do with the second screen for sure ( even when its off ).
Ths options to move desktop icons ( or even clone taskbar ) to 2nd screen
are off.
https://mega.nz/file/Uh02yTIb#4ewbayGEX42arGujxzf9o9XmVRrenybjx7VvAFgTlzE
PS: video was around 200mb so i could not upladed here.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/TimothyLuke/GnomeSequencer-Enhanced/issues/948#issuecomment-876219058,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEMCFKMRLZ6UFPNJYURL23TWVK2XANCNFSM476U2OOA
.

--
Timothy Minahan**M 0406 413 680  |  E @.**

I have tried with both normal wow and elv and i cant make this happen.

Well, i could think its a VGA software issue.
ATM, im runnning on a 5700xt sapphire with AMD updated drivers, and never happened this .
Or maybe even a TBC client issue.
Re-launching the game, its the only way to solve this
PS: 2nd screen is 4k monitor plugged via hdmi ( atm 4:4:4 10bit 23.9hz )

That sucks.
I mean the monitor sounds awesome - it sucks that it does that to it.
On Thu, 8 Jul 2021 at 18:10, lloskka @.***> wrote:

Well, i could think its a VGA software issue.
ATM, im runnning on a 5700xt sapphire with AMD updated drivers, and never
happened this .
Or maybe even a TBC client issue.
Re-launching the game, its the only way to solve this
PS: 2nd screen is 4k monitor plugged via hdmi ( atm 4:4:4 10bit 23.9hz )
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/TimothyLuke/GnomeSequencer-Enhanced/issues/948#issuecomment-876250240,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEMCFLL2QIBLJB2UNJMNSTTWVP77ANCNFSM476U2OOA
.

Update on this.
The moment i change display mode, from full screen to windowed problem goes away.
You can close this @TimothyLuke , plus im pretty sure its because software radeon bug on multiple screens.

Sorry mate.
GSE just doesn’t have the power to affect things at that level.
TimothyLuke

On 9 Jul 2021, at 6:23 pm, lloskka @.***> wrote:

Update on this.
The moment i change display mode, from full screen to windowed problem goes away.
You can close this @TimothyLuke , plus im pretty sure its because software radeon bug on multiple screens.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


[onnx][importer] Add support for externalized params

This patch adds support to externalize params, and store them to the given path as an IRPA file.
The IR imported with externalization should now prevent possible OOM errors happening due to large inlined parameters.

cc @kumardeepakamd.

There is a failure for models with dynamic dims when the parameters are externalized: https://github.com/iree-org/iree/issues/18881.

Please tag related issues on PRs (https://github.com/iree-org/iree/issues/18289 here). Also, have you read through the discussions on https://github.com/iree-org/iree/pull/18365?
(the top of https://iree.dev/developers/general/contributing/ has a note about communicating so work isn't duplicated)

Also, have you read through the discussions on https://github.com/iree-org/iree/pull/18365?

Thanks, read it now.
(The changes there, though similar, seem to me to be unrelated to this PR, and it is mentioned there that this should have had been implemented separately).

Also, have you read through the discussions on #18365?

Thanks, read it now.
(The changes there, though similar, seem to me to be unrelated to this PR, and it is mentioned there that this should have had been implemented separately).

Yep, I just want us to be coordinated via public GitHub issues discussions. The issue and PR I linked were tossing around the idea of replacing iree-import-onnx with a new API, while this PR extends the existing tool. There are architectural discussions to be had there on the issue. This component needs an owner that can manage those discussions and coordinate work between contributors/maintainers.

@ScottTodd my apologies for the delay, I have addressed all your comments in the latest commit. Also added a new flag that allows configuring the parameter scope.

How big is the model.onnx file? I'd be fine with a test using small weights just to make sure the api works.

How big is the model.onnx file? I'd be fine with a test using small weights just to make sure the api works.

The model file is 9.8M in size. Would you like me to make it smaller?

Yeah, we want a functionality test, so the file size isn't necessary. Just big enough to work for the default size threshold would be ideal.

@zjgarvey reduced the model file size to 8.0K.

Okay, resolve outdated conversations with @ScottTodd and we will wait for his approval.

8KB is fine - thanks for making it small - git never forgets and every KB added is future pain.

@ScottTodd thanks for the approval! I have addressed the remaining comments and rebased the PR.

Will you follow up with documentation, or should we file an issue?

I should be able to open a PR to follow up with the documentation too.

@vinayakdsci would you like me to merge this now?


add cf-security-entitlement plugin

thanks for the future merge

Hi @ArthurHlt thanks for this pull request!
The CLI team recently sent out a document announcing upcoming changes to the plugin interface - supporting the v3 CC API endpoints and eventually deprecating the CLI codebase which calls the v2 endpoints. We would love to hear your thoughts about our approach, and the implications for your plugin.  Thanks again.


Resource naming: name cannot contain '-'

Documentation says that
The Azure Data Factory team recommends using '_' or '-' characters instead of spaces
Howevr '-' is not available for names, ADF gives an error message:
"name should only contain letters, numbers, underscores (_), or spaces."
The documentation should be updated to avoid confusion.

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

ID: 237d79bb-0601-dc47-b6c4-e3f1edc1a25f
Version Independent ID: b73cce3a-18ef-fd98-f6e7-8c508f6adc13
Content: Continuous integration and delivery - Azure Data Factory
Content Source: articles/data-factory/continuous-integration-delivery.md
Service: data-factory
Sub-service: ci-cd
GitHub Login: @nabhishek
Microsoft Alias: abnarain

@peterbud Thank you for sharing your valuable feedback. We are actively validating it. We will share updates soon.

@peterbud ADF allows '-' in data factories. I tried same. Its working fine. Please check below screenshot. Kindly review same and share updates. Thank you.

@ShaikMaheer-MSFT the document and the issue at hand is NOT about the naming of the data factory itself, but the resources within the data factory. Try to create a pipeline in ADF where the name contains a '-', it won't work.
Here is the lisleading paragraph:

Resource naming. Due to ARM template constraints, issues in deployment may arise if your resources contain spaces in the name. The Azure Data Factory team recommends using '_' or '-' characters instead of spaces for resources. For example, 'Pipeline_1' would be a preferable name over 'Pipeline 1'.

@peterbud Thank you for updates. I tried even pipeline names with - symbol. Its working fine. I published also pipeline.

Having - Symbol at starting or ending of pipeline is not allowed. Otherwise - symbol to use instead of space is working good as per document.

Kindly review above screenshots and share updates. Thank you.

Looks like it's not very consistent: you are right, pipelines can contain '-', but datasets cannot:

Same goes for linked services, no '-' allowed:

I'm not sure what's so special that these two resource types are picky for dashes.
Anyhow, let's close this issue here.


added instruction how migrate from version 3.1.5 to 6.7.0

I've created new instruction how migrate from version 3.1.5 to 6.7.0. According to issue #61

THANKS <3 <3


is that any function can replace pathFor function in iron:router?

The full question is on stackoverflow:
http://stackoverflow.com/questions/34647098/which-function-is-the-replacement-function-of-pathfor-function-of-iron-routing
just ask if there is any function like iron:router pathFor function in flow-router?

https://github.com/zimme/meteor-active-route

https://github.com/arillo/meteor-flow-router-helpers

https://gist.github.com/TechplexEngineer/684b7ffd142ce5170467e868138f32f3


Feature Request: Create a preference variable to turn Off/On path normalization

I want to tell PowerShell to leave my "/" path delims alone when I am on Windows and "" alone when I am on *nix. Perverse I know!

I had an similar issue today where I used Split-Path on a URL stem on Windows and it autocorrected the path delimiter. Would be nice if there was a switch for this particular cmdlet to ignore translation.
PS C:\> Split-Path -Parent -Path /one/two
\one

We should have both:

Global preference variable with default value a platform depended.
Switch -Normalize or parameter -Style [Windows | Unix]
What cmdlets  is affected by the issue?

@iSazonov -Style [Windows | Unix] make more sense from a discovery point of view. Also -Normalize could get confusing if you have preferenced something else already, better to avoid the ambiguity.

We should have switches (in different parameter sets):
-StyleWindows - default true on Windows
-StyleUnix - default on Linux and IOS.
And we should consider remoting and remote sessions  Windows -> Unix, Unix -> Windows. Is it possible and reasonable to make implicit conversions?

-PathDelimiter [Windows|Unix]
$PSPathDelimier = [Windows|Unix] defaults to platform.
This should be a cosmetic styling.
Sent from my Windows 10 phone
From: Ilya
Sent: Sunday, February 12, 2017 4:40
To: PowerShell/PowerShell
Cc: Richard Burte; Author
Subject: Re: [PowerShell/PowerShell] Feature Request: Create a preferencevariable to turn Off/On path normalization (#3118)
We should have switches (in different parameter sets):
-StyleWindows - default true on Windows
-StyleUnix - default on Linux and IOS.
And we should consider remoting and remote sessions Windows -> Unix, Unix -> Windows. Is it possible and reasonable to make implicit conversions?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Battery system testing

The battery tool should have the ability to tell you how much power each of the following draws (percent / hour):

[ ] GPS
[ ] Sensors (compass, barometer)
[ ] Flashlight
[ ] Camera
[ ] Processor
[ ] Screen
[ ] Custom test - record before, enable the feature, record after

It could potentially do this by calculating a baseline power draw then turning on one of the systems and calculating the difference between the two. Not sure how accurate that would be, but more research is needed.

Screen at lowest brightness
Screen at highest brightness


Fix issue #6955 - find LLVM_ROOT correctly on macOS.

Change Description

Set cmake policy CMP0074 to NEW to allow LLVM_ROOT variable to be found correctly on macOS. Current build scripts ignores the LLVM_ROOT variable on macOS.
Consensus Changes

[ ] Consensus Changes

No changes.
API Changes

[ ] API Changes

No Changes.
Documentation Additions

[ ] Documentation Additions

No changes.

closing this per discussion in #6955 -- we're not going to regress the macos builds to clang4. Also, LLVM_ROOT is used to find LLVM libraries; not the version of clang being used.


Encorporate line ratio machine learning work

We can use the line ratio estimates from the neural network to constrain the fits and hopefully make them better!

I've decided against including this for the moment.


Failure to upgrade gem if a yanked gem is required by an unrelated gem in Gemfile

As far as I can tell, that's what is happening here.  Here's the output of bundle update -V
Updating git://github.com/hyperoslo/capistrano-foreman.git
Updating https://github.com/bryanrite/carrierwave-sequel
Updating https://github.com/pnomolos/bamfcsv
HTTP GET https://bundler.rubygems.org/api/v1/dependencies
HTTP 200 OK
Fetching gem metadata from https://rubygems.org/
Query List: ["bundler", "rake", "oj", "unicorn", "flowdock", "grit", "clockwork", "capistrano", "cape", "foreman", "sinatra", "pg", "sinatra-sequel", "sequel", "upsert", "activesupport", "sentry-raven", "carrierwave", "fog", "rest-client", "resque", "resque-batched-job", "redis-lock", "uuidtools", "rubyzip", "zippy", "rabl", "mail", "mime-types", "padrino-core", "padrino-mailer", "padrino-helpers", "php-serialize", "nokogiri", "bill-parser", "carrier-scraper", "tux", "ruby-prof", "pry", "pry-byebug", "fixture_dependencies", "rspec", "webmock", "vcr", "fuubar", "rake-compiler", "sqlite3", "capistrano-bundler"]
Query Gemcutter Dependency Endpoint API: bundler,rake,oj,unicorn,flowdock,grit,clockwork,capistrano,cape,foreman,sinatra,pg,sinatra-sequel,sequel,upsert,activesupport,sentry-raven,carrierwave,fog,rest-client,resque,resque-batched-job,redis-lock,uuidtools,rubyzip,zippy,rabl,mail,mime-types,padrino-core,padrino-mailer,padrino-helpers,php-serialize,nokogiri,bill-parser,carrier-scraper,tux,ruby-prof,pry,pry-byebug,fixture_dependencies,rspec,webmock,vcr,fuubar,rake-compiler,sqlite3,capistrano-bundler
HTTP GET https://bundler.rubygems.org/api/v1/dependencies?gems=bundler,rake,oj,unicorn,flowdock,grit,clockwork,capistrano,cape,foreman,sinatra,pg,sinatra-sequel,sequel,upsert,activesupport,sentry-raven,carrierwave,fog,rest-client,resque,resque-batched-job,redis-lock,uuidtools,rubyzip,zippy,rabl,mail,mime-types,padrino-core,padrino-mailer,padrino-helpers,php-serialize,nokogiri,bill-parser,carrier-scraper,tux,ruby-prof,pry,pry-byebug,fixture_dependencies,rspec,webmock,vcr,fuubar,rake-compiler,sqlite3,capistrano-bundler
HTTP 200 OK
Query List: ["ruby-progressbar", "chalofa_ruby-progressbar", "rspec-instafail", "progressbar", "ripl", "ripl-rack", "ripl-multi_line", "redis", "archive-tar-minitar", "rcov", "hoe", "multi_json", "httparty", "win32console", "method_source", "slop", "coderay", "spoon", "ruby_parser", "yard", "tzinfo", "ffi", "tlsmail", "treetop", "i18n", "rack", "tilt", "mongrel", "shotgun", "rack-test", "rack-protection", "backports", "rspec-mocks", "rspec-expectations", "rspec-core", "cucumber", "diff-lcs", "syntax", "spicycode-rcov", "kgio", "raindrops", "padrino-support", "dotenv", "thor", "term-ansicolor", "posix-spawn", "json", "crack", "addressable", "tmail", "launchy", "redis-namespace", "vegas", "json_pure", "mono_logger", "http_router", "usher", "rdoc", "netrc", "mini_portile", "racc", "tenderlove-frex", "rexical", "weakling", "bacon", "highline", "net-ssh", "net-sftp", "net-scp", "net-ssh-gateway", "echoe", "sshkit", "fakeweb", "opennebula", "fog-terremark", "fog-vmfusion", "fog-voxel", "fog-profitbricks", "fog-radosgw", "fog-sakuracloud", "fog-softlayer", "fog-brightbox", "ipaddress", "fog-xml", "fog-json", "fog-core", "builder", "excon", "formatador", "ruby-hmac", "named-parameters", "google-api-client", "unicode", "thread_safe", "minitest", "memcache-client", "activemodel", "metaid", "ParseTree", "ruby2ruby", "sequel_core", "sequel_model", "assistance", "RubyInline", "faraday", "yajl-ruby", "hashie", "byebug"]
Query Gemcutter Dependency Endpoint API: ruby-progressbar,chalofa_ruby-progressbar,rspec-instafail,progressbar,ripl,ripl-rack,ripl-multi_line,redis,archive-tar-minitar,rcov,hoe,multi_json,httparty,win32console,method_source,slop,coderay,spoon,ruby_parser,yard,tzinfo,ffi,tlsmail,treetop,i18n,rack,tilt,mongrel,shotgun,rack-test,rack-protection,backports,rspec-mocks,rspec-expectations,rspec-core,cucumber,diff-lcs,syntax,spicycode-rcov,kgio,raindrops,padrino-support,dotenv,thor,term-ansicolor,posix-spawn,json,crack,addressable,tmail,launchy,redis-namespace,vegas,json_pure,mono_logger,http_router,usher,rdoc,netrc,mini_portile,racc,tenderlove-frex,rexical,weakling,bacon,highline,net-ssh,net-sftp,net-scp,net-ssh-gateway,echoe,sshkit,fakeweb,opennebula,fog-terremark,fog-vmfusion,fog-voxel,fog-profitbricks,fog-radosgw,fog-sakuracloud,fog-softlayer,fog-brightbox,ipaddress,fog-xml,fog-json,fog-core,builder,excon,formatador,ruby-hmac,named-parameters,google-api-client,unicode,thread_safe,minitest,memcache-client,activemodel,metaid,ParseTree,ruby2ruby,sequel_core,sequel_model,assistance,RubyInline,faraday,yajl-ruby,hashie,byebug
HTTP GET https://bundler.rubygems.org/api/v1/dependencies?gems=ruby-progressbar,chalofa_ruby-progressbar,rspec-instafail,progressbar,ripl,ripl-rack,ripl-multi_line,redis,archive-tar-minitar,rcov,hoe,multi_json,httparty,win32console,method_source,slop,coderay,spoon,ruby_parser,yard,tzinfo,ffi,tlsmail,treetop,i18n,rack,tilt,mongrel,shotgun,rack-test,rack-protection,backports,rspec-mocks,rspec-expectations,rspec-core,cucumber,diff-lcs,syntax,spicycode-rcov,kgio,raindrops,padrino-support,dotenv,thor,term-ansicolor,posix-spawn,json,crack,addressable,tmail,launchy,redis-namespace,vegas,json_pure,mono_logger,http_router,usher,rdoc,netrc,mini_portile,racc,tenderlove-frex,rexical,weakling,bacon,highline,net-ssh,net-sftp,net-scp,net-ssh-gateway,echoe,sshkit,fakeweb,opennebula,fog-terremark,fog-vmfusion,fog-voxel,fog-profitbricks,fog-radosgw,fog-sakuracloud,fog-softlayer,fog-brightbox,ipaddress,fog-xml,fog-json,fog-core,builder,excon,formatador,ruby-hmac,named-parameters,google-api-client,unicode,thread_safe,minitest,memcache-client,activemodel,metaid,ParseTree,ruby2ruby,sequel_core,sequel_model,assistance,RubyInline,faraday,yajl-ruby,hashie,byebug
HTTP 200 OK
Query List: ["sexp_processor", "SexpProcessor", "ZenTest", "bond", "termios", "multi_xml", "jnunemaker-crack", "mocha", "newgem", "signet", "httpadapter", "extlib", "liquid", "autoparse", "jwt", "retriable", "rspec-support", "multipart-post", "daemons", "fastthread", "gem_plugin", "cgi_multipart_eof_fix", "safe_yaml", "multi_test", "gherkin", "cucumber-core", "polyglot", "configuration", "tins", "test-spec", "camping", "fcgi", "ruby-openid", "thin", "spruz", "erubis", "rubyforge", "gemcutter", "allison", "facets", "escape_utils", "fuzzyhash", "bones", "needle", "jruby-pageant", "bcrypt-ruby", "url_mount", "validatable", "atomic", "rbvmomi", "dotenv-deployment", "colorize", "debugger-linecache", "columnize", "pry-debugger", "inflecto", "fission"]
Query Gemcutter Dependency Endpoint API: sexp_processor,SexpProcessor,ZenTest,bond,termios,multi_xml,jnunemaker-crack,mocha,newgem,signet,httpadapter,extlib,liquid,autoparse,jwt,retriable,rspec-support,multipart-post,daemons,fastthread,gem_plugin,cgi_multipart_eof_fix,safe_yaml,multi_test,gherkin,cucumber-core,polyglot,configuration,tins,test-spec,camping,fcgi,ruby-openid,thin,spruz,erubis,rubyforge,gemcutter,allison,facets,escape_utils,fuzzyhash,bones,needle,jruby-pageant,bcrypt-ruby,url_mount,validatable,atomic,rbvmomi,dotenv-deployment,colorize,debugger-linecache,columnize,pry-debugger,inflecto,fission
HTTP GET https://bundler.rubygems.org/api/v1/dependencies?gems=sexp_processor,SexpProcessor,ZenTest,bond,termios,multi_xml,jnunemaker-crack,mocha,newgem,signet,httpadapter,extlib,liquid,autoparse,jwt,retriable,rspec-support,multipart-post,daemons,fastthread,gem_plugin,cgi_multipart_eof_fix,safe_yaml,multi_test,gherkin,cucumber-core,polyglot,configuration,tins,test-spec,camping,fcgi,ruby-openid,thin,spruz,erubis,rubyforge,gemcutter,allison,facets,escape_utils,fuzzyhash,bones,needle,jruby-pageant,bcrypt-ruby,url_mount,validatable,atomic,rbvmomi,dotenv-deployment,colorize,debugger-linecache,columnize,pry-debugger,inflecto,fission
HTTP 200 OK
Query List: ["CFPropertyList", "trollop", "cdb-full", "tokyocabinet", "metaclass", "english", "RedCloth", "rubigen", "bcrypt", "ruby-yadis", "flexmock", "abstract", "activerecord", "markaby", "mab", "eventmachine", "eventmachine-le", "http_parser.rb", "preforker", "little-plugger", "loquacious", "bones-git", "bones-extras", "debugger-ruby_core_source", "ruby_core_source", "debugger", "psych"]
Query Gemcutter Dependency Endpoint API: CFPropertyList,trollop,cdb-full,tokyocabinet,metaclass,english,RedCloth,rubigen,bcrypt,ruby-yadis,flexmock,abstract,activerecord,markaby,mab,eventmachine,eventmachine-le,http_parser.rb,preforker,little-plugger,loquacious,bones-git,bones-extras,debugger-ruby_core_source,ruby_core_source,debugger,psych
HTTP GET https://bundler.rubygems.org/api/v1/dependencies?gems=CFPropertyList,trollop,cdb-full,tokyocabinet,metaclass,english,RedCloth,rubigen,bcrypt,ruby-yadis,flexmock,abstract,activerecord,markaby,mab,eventmachine,eventmachine-le,http_parser.rb,preforker,little-plugger,loquacious,bones-git,bones-extras,debugger-ruby_core_source,ruby_core_source,debugger,psych
HTTP 200 OK
Query List: ["git", "libxml-ruby", "thoughtbot-shoulda", "language", "bones-rcov", "bones-rubyforge", "bones-rspec", "bones-zentest", "arel", "activerecord-deprecated_finders"]
Query Gemcutter Dependency Endpoint API: git,libxml-ruby,thoughtbot-shoulda,language,bones-rcov,bones-rubyforge,bones-rspec,bones-zentest,arel,activerecord-deprecated_finders
HTTP GET https://bundler.rubygems.org/api/v1/dependencies?gems=git,libxml-ruby,thoughtbot-shoulda,language,bones-rcov,bones-rubyforge,bones-rspec,bones-zentest,arel,activerecord-deprecated_finders
HTTP 200 OK
Query List: []
Fetching additional metadata from https://rubygems.org/
Query List: ["chalofa_ruby-progressbar"]
Query Gemcutter Dependency Endpoint API: chalofa_ruby-progressbar
HTTP GET https://bundler.rubygems.org/api/v1/dependencies?gems=chalofa_ruby-progressbar
HTTP 200 OK
Query List: []
HTTP GET https://privategemserver/api/v1/dependencies
HTTP 200 OK
HTTP GET https://bundler.rubygems.org/api/v1/dependencies
HTTP 200 OK
Fetching gem metadata from https://fd937aa9b1989f4d2fdf33aa86a92e98.simplexmobility.com/
Query List: ["chalofa_ruby-progressbar"]
Query Gemcutter Dependency Endpoint API: chalofa_ruby-progressbar
HTTP GET https://privategemserver/api/v1/dependencies?gems=chalofa_ruby-progressbar
HTTP 200 OK
Query List: []
Fetching gem metadata from https://rubygems.org/
Query List: ["chalofa_ruby-progressbar"]
Query Gemcutter Dependency Endpoint API: chalofa_ruby-progressbar
HTTP GET https://bundler.rubygems.org/api/v1/dependencies?gems=chalofa_ruby-progressbar
HTTP 200 OK
Query List: []
Resolving dependencies...
Could not find gem 'carrier-scraper (~> 0.19.3) ruby' in the gems available on this machine.

It appears that because chalofa_ruby-progressbar has been yanked, bundler goes on a chase down the rabbit-hole trying to find it, then gives up.
Note that bundle update -V carrier-scraper also produces a similar result.

@indirect @TimMoore Just wondering if you guys had any luck figuring out what's causing this?  Thanks! :)

Sorry, haven't looked into it yet.
On Tuesday, 27 January 2015, pnomolos<EMAIL_ADDRESS>wrote:

@indirect https://github.com/indirect @TimMoore
https://github.com/TimMoore Just wondering if you guys had any luck
figuring out what's causing this? Thanks! :)
—
Reply to this email directly or view it on GitHub
https://github.com/bundler/bundler/issues/3265#issuecomment-71520345.

Finally getting to this... sorry that it's taken so long @pnomolos.
I think it's triggered by the use of rubygems.org as both a top-level source and attached to a specific gem. This Gemfile works fine, for example:
source<EMAIL_ADDRESS>#source 'https://rubygems.org'

gem 'rake', '10.2.2', source: 'https://rubygems.org/'
gem 'rack', source: 'https://rubygems.org/'

This is definitely an unintended bug, and I'll work on a fix, but it's also not the way the feature was really intended to be used. If you're using a source for specific gems, you shouldn't also put it a the top level. You can probably work around the bug by changing your Gemfile to have one top-level source, and use source blocks around any gems that are supposed to come from an alternate gem server.

@TimMoore I would have to see if I can replicate it, but right now in my gem file I am using source blocks for both the private gem server and for rubygems and that still triggers the error - should I try a source block for only the private gem server and leave rubygems at the top level?

@pnomolos do you have any gems outside of source blocks?

@TimMoore Nope, all of them are inside of the source blocks.  The private gemserver source block comes first, if that would make any difference.

@indirect looks like you were right... this change seems to cause the problem: 1eb62f21d24e32029d5df1a279cecd957764f827
Commenting out s.specs.each { |spec| dependency_names.delete(spec.name) } fixes it for me.

@indirect I'm going to revert that change and disable the test introduced in that commit for now. I agree that it is probably causing a few of the recent issues. I'll add a test to reproduce this issue, too.
That means that it will go back to querying gem servers for path gems and gemspecs, which isn't ideal but AFAIK isn't too harmful either. We'll need to find another solution for that. Really, path gems (and git gems/gemspecs, which are both special cases of path gems) shouldn't ever go into the list of dependencies to query remotely in the first place, but right now the code doesn't distinguish between them internally.
/cc @dubek, @grosser

The original issue was no showstopper / just a bad implementation detail,
so I think it's fine to revert as long as we come up with a solution that
does what as described ("shouldn't ever go into the list of dependencies to
query remotely in the first place")
On Fri, Feb 6, 2015 at 5:03 PM, Tim Moore<EMAIL_ADDRESS>wrote:

@indirect https://github.com/indirect I'm going to revert that change
and disable the test introduced in that commit for now. I agree that it is
probably causing a few of the recent issues. I'll add a test to reproduce
this issue, too.
That means that it will go back to querying gem servers for path gems and
gemspecs, which isn't ideal but AFAIK isn't too harmful either. We'll need
to find another solution for that. Really, path gems (and git
gems/gemspecs, which are both special cases of path gems) shouldn't ever go
into the list of dependencies to query remotely in the first place, but
right now the code doesn't distinguish between them internally.
/cc @dubek https://github.com/dubek, @grosser
https://github.com/grosser
—
Reply to this email directly or view it on GitHub
https://github.com/bundler/bundler/issues/3265#issuecomment-73341211.

Related: #3368

I just finished a fix for this, and a test to prevent a regression, while on the bus to the animal sanctuary... I'll push in a few hours. :)
On Sat, Feb 7, 2015 at 2:14 PM, Tim Moore<EMAIL_ADDRESS>wrote:

Related: #3368
Reply to this email directly or view it on GitHub:
https://github.com/bundler/bundler/issues/3265#issuecomment-73347391

Oh whoops!

This should be fixed in 1.7.13. Please try upgrading and let us know if you still have any problems.

@TimMoore  yep it appears to be fixed.  Thanks so much!

Hello everyone I'm installing ubuntu 14.04 LTS bigbluebutton and I get the following error, agradecere your help:
Gem files will remain installed in /var/lib/gems/1.9.1/gems/nokogiri-1.4.4 for inspection.
Results logged to /var/lib/gems/1.9.1/gems/nokogiri-1.4.4/ext/nokogiri/gem_make.out
Your Gemfile.lock is corrupt. The following gems are missing from the DEPENDENCIES section: 'archive-tar-minitar' 'hoe'
'rcov'
dpkg: error processing package bbb-record-core (--configure):
subprocess installed post-installation script returned error exit status 20
dpkg: dependency problems prevent configuration of bbb-playback-presentation:
bbb-playback-presentation depends on bbb-record-core; however:
Package bbb-record-core is not configured yet.
dpkg: error processing package bbb-playback-presentation (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of bbb-config:
bbb-config depends on bbb-web; however:
Package bbb-web is not configured yet.
bbb-config depends on bbb-playback-presentation; however:
Package bbb-playback-presentation is not configured yet.
dpkg: error processing package bbb-config (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of bigbluebutton:
bigbluebutton depends on bbb-config; however:
Package bbb-config is not configured yet.
dpkg: error processing package bigbluebutton (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.19-0ubuntu6.7) ...
Errors were encountered while processing:
bbb-web
bbb-record-core
bbb-playback-presentation
bbb-config
bigbluebutton
E: Sub-process /usr/bin/dpkg returned an error code (1)


Add a lint for shadowed names

 Issue by cmr
Monday Apr 07, 2014 at 04:42 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/13372
This issue was labelled with: A-an-interesting-project, A-diagnostics, A-lint, A-resolve in the Rust repository

Our shadowing behavior can be somewhat surprising, especially around method lookup. A lint (allow by default) for name shadows would be incredibly useful.

@joshtriplett does this warrant a lint in the compiler, or is clippy enough?

Personally, I'd rather see it in the compiler, but I know that there's a higher bar to meet for that. But either would be better than nothing.

I would like to note that this exists in clippy by the way under three different  names that all are slightly different. the three lints areshadow sameshadow reuse
shadow unrelated

For safeness reasons allowing such thing is error prone.
As example:
fn main() {
    let pi = 3.1415;
    println!("{}", pi);
    let pi= "3.1415";
    println!("{}", pi);
}

Allowing such thing as the default behavior is a bit weird, since it can leads developers to shadow variables without the intend.
Such thing can be a common thing, but should be used only if the programmer opt-in for that.
I understand that is useful and can help programmers and some use cases, but since:
const, constexpr, const functions and others are opt-in in C++ (and considered good practices). Allowing variable shadowing as the default behavior forces the programmer to opt-in for safeness and not other way around. The safeness option should be the default IMO to help programmers to avoid self sabotage.

For safeness reasons allowing such thing is error prone.
As example:
fn main() {
    let pi = 3.1415;
    println!("{:?}", pi); // 3.1415
    let pi = "3.1415";
    println!("{:?}", pi); // "3.1415"
}

To me, this example's behavior is clear and reasonable. I suggest you pick a (perhaps more complex) example that really exhibits a counterintuitive behavior.

For safeness reasons

Rust has an established meaning for the word safety that I don't believe is what you intend here. You may wish to be more precise about what exactly the pitfalls you see are.
(I also do not mind shadowing and I make liberal use of it)


tflite Model Maker installation Error metadata-generation-failed, No such file or directory: '..\VERSION'

Click to expand!
Issue Type
Build/Install
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
2.11.0
Custom Code
No
OS Platform and Distribution
Windows 11
Mobile device
No response
Python version
3.10.4
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Hello everyone, I hope you can help me with the following problem

I have checked the requirements several times but always get the same error:

pip install tflite-model-maker results in FileNotFoundError: [Errno 2] No such file or directory: '..\\VERSION'

Clone source code from GitHub and install results in TypeError: 'WindowsPath' object is not subscriptable

Standalone code to reproduce the issue
pip install tflite-model-maker

Relevant log output
Using cached sentencepiece-0.1.83.tar.gz (497 kB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [8 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "C:\Users\1\AppData\Local\Temp\pip-install-uny2d85u\sentencepiece_d8babf4dcc3a48be9b4874119d6463fb\setup.py", line 29, in <module>
          with codecs.open(os.path.join('..', 'VERSION'), 'r', 'utf-8') as f:
        File "C:\Users\1\AppData\Local\Programs\Python\Python310\lib\codecs.py", line 905, in open
          file = builtins.open(filename, mode, buffering)
      FileNotFoundError: [Errno 2] No such file or directory: '..\\VERSION'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

-------------------------------------------------------------------------

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [12 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "C:\Users\1\Desktop\Dev\tflite_model_maker\examples\tensorflow_examples\lite\model_maker\pip_package\setup.py", line 122, in <module>
          INTERNAL_NAME).run()
        File "C:\Users\1\Desktop\Dev\tflite_model_maker\examples\tensorflow_examples\lite\model_maker\pip_package\setup_util.py", line 163, in run
          namespace_packages = find_namespace_packages(where=self.build_dir)
        File "C:\Users\1\Desktop\Dev\tflite_model_maker\tfliteMM-venv\lib\site-packages\setuptools\__init__.py", line 64, in find
          convert_path(where),
        File "C:\Users\1\AppData\Local\Programs\Python\Python310\lib\distutils\util.py", line 123, in convert_path
          if pathname[0] == '/':
      TypeError: 'WindowsPath' object is not subscriptable
      [end of output]

Hello @Erik6209, I have tested the pip install tflite-model-maker code on my system of windows 11, and its working great. I think  the problem is with your side only.

Here are a couple of things you can try to resolve the issue:

Make sure that you have the latest version of pip installed by running pip install --upgrade pip

Try installing the package using pip install --no-dependencies tflite-model-maker

Try installing the package using a virtual environment.

Check the compatibility of the package with the version of python you are using.

Try installing the package from the source code by running pip install . in the directory where you cloned the source code.

The package is not fully compatible with Windows, so it's better to use it in a Linux or MacOS environment.

Please let me know if you have more information about the error message and the environment you are running on, so I can help you more specifically.

Thank you @DURGESH716. Point two and three helped me. additionally while using python 3.9 i noticed that the latest numpy version is not compatible. I had to downgrade numpy to get rid of importerrors. But now everything works, thanks for the quick help!

@Erik6209
Could you please close the issue if it is resolved ?
Thank you!

It's My Pleasure, @Erik6209. If everything seems perfect, You can close the issue as Completed.
Thank You !!!

@DURGESH716 Hello. I am trying to install tflite-model-maker package in order to use it for training of mobile models.
I found only once source for the installation https://pypi.org/project/tflite-model-maker/
I have tried all 3 methods mentioned there, but every time I try to import the package, there is always some issues or errors.
In all cases the issue is connected mostly with scann package.
Could not find a version that satisfies the requirement scann==1.2.6 (from tflite-model-maker) (from versions: none)
No matching distribution found for scann==1.2.6
Do you know how is possible to successfully install tflite-model-maker package for Windows 11? Thanks a lot in advance!

The TFLite model maker library is broken. We can not install it. Not in Windows or Colab(Linux):
Also, the following code did not help resolve the issue.
pip install --no-dependencies tflite-model-maker
You can test it for yourself; I can not install it on Colab when I run TFLite model maker examples provided by Google people;
https://colab.research.google.com/github/khanhlvg/tflite_raspberry_pi/blob/main/object_detection/Train_custom_model_tutorial.ipynb
TFLite model maker installation on Tensorflow.org is not up to date either. It does not explain what dependencies are needed.

This package is absolutely broken. I never found other package that make so very hard to install. Not work by using no way.

Any solution so far for installing TFlite Model Maker

omg, what should i do haha

There's something wrong. It doesn't even install in collab

There's something wrong. It doesn't even install in collab

yess... still not working today (2023-08-08) in google collab

I installed it in a env, however I can't call it. It's there but callable; If someone is interest I build the env in Colab with the following commands.
!pip install virtualenv
!virtualenv venv
!source venv/bin/activate
!python3 -V
!sudo add-apt-repository ppa:deadsnakes/ppa
!sudo apt install python3.9
!sudo update-alternatives --install /usr/bin/python3 python3 /usr/bin/python3.10.12
!sudo update-alternatives --install /usr/bin/python3 python3 /usr/bin/python3.9 2
!sudo update-alternatives --config python3!pip install virtualenv
!virtualenv venv
!source venv/bin/activate
!python --version
!sudo apt install python3.9-distutils -y
!sudo apt install python3.9-lib2to3 -y
!sudo apt install python3.9-gdbm -y
!sudo apt install python3.9-tk -y
!sudo apt install python3-pip
!python -m pip install --upgrade pip
!pip install -q tflite-model-maker
!pip install -q tflite-support

still aint working ffs

This package is absolutely broken. I never found other package that make so very hard to install. Not work by using no way.

Just crazy mate!
Being here all night trying to get this package installed on an Ubuntu server sitting thousands of miles around from me.


Typescript-webpack - Visual Code debug

I'm submitting a bug report

Aurelia Skeleton Version
skeleton-typescript-webpack

Framework Version:
<EMAIL_ADDRESS>

Please tell us about your environment:

Operating System:
Windows 10

Node Version:
6.9.2

NPM Version:
4.0.5

JSPM OR Webpack AND Version
webpack 2.1.0-beta.27

Browser:
Chrome 55

Language:
TypeScript 2.1.4

Current behavior:
With default webpack.config.ts setting, I Could not debug
Expected/desired behavior:
1- In Visual Code I have installed the extension Debugger for Chrome 2.4.2
2- I create the file launch,json:
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Debug in Chrome",
            "type": "chrome",
            "port": 9222,
            "url": "http://localhost:9000/",
            "sourceMaps": true,
            "smartStep":true
        }
    ]
}

3- The execution not stop in breakpoints in Visual Code
4- I did a lot of testing and research and with the following changes in webpack.config.ts it works fine:
output: {
      path: outDir,
      devtoolModuleFilenameTemplate        : '[absolute-resource-path]',
      devtoolFallbackModuleFilenameTemplate: '[absolute-resource-path]?[hash]'
    },
(....)
  ENV === 'test' || ENV === 'development' ?
    envDev({devtool: 'inline-source-map'}) :
    envProd({ /* devtool: '...' */ }),

5- The debug in chrome also work good, but when I start debugging in Visual Code, if I try to open the "chrome developer tools", the chrome closes.
In my tests the debug in chrome developer tools is also not working, because this line:
ENV === 'test' || ENV === 'development' ?
  envDev(**ENV !== 'test' ? {} :** {devtool: 'inline-source-map'}) :
  envProd({ /* devtool: '...'
The debug works with default configurations.

I changed this in my webpack.config and now i can debug in chrome.
 ENV === 'test' || ENV === 'development' ?         envDev(ENV === 'test' ? {} : { devtool: 'inline-source-map' }) :         envProd({ /* devtool: '...' */ }),

Thank you @cluka , thanks to you we can now debug in chrome again. I think it´s a bug in the skeleton template. Changing !== to === corrected our wrong sourcemaps.

can be closed


IntelrealSense D455 cannot detect the device in mac environment with python programming

profile = pipe.start()
RuntimeError: No device connected

Hi @HiWiQiao  A RealSense user at https://github.com/IntelRealSense/librealsense/issues/9687 created a pre-built version of pyrealsense2 for Mac, though it has only been tested with MacOS Catalina and Big Sur.

Hi @HiWiQiao  Was the pre-built version of pyrealsense2 for Mac helpful to you, please?  Thanks!

Hi @HiWiQiao  Do you require further assistance with this case, please?  Thanks!

Hi @HiWiQiao Was the pre-built version of pyrealsense2 for Mac helpful to you, please? Thanks!

I can successfully import pyrealsense2, but when I connect to D455, it shows that the device is not detected.

Hi @HiWiQiao Do you require further assistance with this case, please? Thanks!

Still not working, my macOS system is Ventura 13.3.1 and when I use the Intel version of MacBook Big sur is no problem.

At the time of writing this, the most recent MacOS version that has pyrealsense2 setup advice available for it is Ventura's predecessor Monterey - see https://github.com/IntelRealSense/librealsense/issues/5275#issuecomment-1059876482

Hi @HiWiQiao  Do you have an update about this case that you can provide, please?  Thanks!

Case closed due to no further comments received.