Dependency of @types/react-loadable causes type conflict issues in 2.0.0-beta.7/8

🐛 Bug Report
Prerequisites

[x] I'm using the latest version of Docusaurus.
[x] I have tried the npm run clear or yarn clear command.
[x] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[x] I have tried creating a repro with https://new.docusaurus.io ( N.A. because those samples are using JavaScript and this is TypeScript issue. There is a repository linked below)
[x] I have read the console error message carefully (if applicable)

Description
In the PR https://github.com/facebook/docusaurus/pull/5601 a change was made to ensure @types packages are in the dependencies instead of the dev-dependencies. This however introduced a regression issue in @docusaurus/module-type-aliases through @types/react-loadable. Specifically, those types still depend on @types/webpack ^4 which conflicts with Docusaurus using Webpack 5 as of https://github.com/facebook/docusaurus/pull/4089.
I have already added "skipLibCheck": true to my /tsconfig.json but that is completely to no avail. I don't know how Docusaurus reads the tsconfig exactly but it seems to disregard at least that property.
My suggestion for the fix is one of:

Remove the entire @types/react-loadable dependency.  I'm not sure why @docusaurus/module-type-aliases is even depending on the types? Why not add the necessary types that you do need to your fork so you have no dependency at all anymore on the original work?
Move at least @types/react-loadable back to dev-dependencies
Ensure @types/react-loadable starts using Webpack v5 by contributing that to DefinitelyTyped

Here are some console outputs and yarn lockfile dumps:
yarn why @types/webpack -R
└─ root-website@workspace:.
   └─ @docusaurus/module-type-aliases@npm:2.0.0-beta.8 (via npm:2.0.0-beta.8)
      └─ @types/react-loadable@npm:5.5.6 (via npm:*)
         └─ @types/webpack@npm:4.41.31 (via npm:^4)

"@docusaurus/module-type-aliases@npm:2.0.0-beta.8":
  version: 2.0.0-beta.8
  resolution: "@docusaurus/module-type-aliases@npm:2.0.0-beta.8"
  dependencies:
    "@types/react": "*"
    "@types/react-helmet": "*"
    "@types/react-loadable": "*"
    "@types/react-router-config": "*"
    "@types/react-router-dom": "*"
  checksum: 995ea7c62fab5968abd2b0d61b2ec6f0362e32d5fd27363eb15f90cd8e299777c56e4d82f1b09aebd45b18a6601f9e122ccb1b1d7dea6dc74f0e2f2116167628
  languageName: node
  linkType: hard

"@types/react-loadable@npm:*":
  version: 5.5.6
  resolution: "@types/react-loadable@npm:5.5.6"
  dependencies:
    "@types/react": "*"
    "@types/webpack": ^4
  checksum: 395ff992cf8dbbd425aa79cc298987b464eab875b7057cb4475bfcabd17780d074cf3b7e2511f494fb8e4105a3fe5c9218237f8205f498c38b63671605463415
  languageName: node
  linkType: **hard**

"@types/webpack@npm:^4":
  version: 4.41.31
  resolution: "@types/webpack@npm:4.41.31"
  dependencies:
    "@types/node": "*"
    "@types/tapable": ^1
    "@types/uglify-js": "*"
    "@types/webpack-sources": "*"
    anymatch: ^3.0.0
    source-map: ^0.6.0
  checksum: 8aa4b4ad68bb7a6ee5bd027005014e6242434162ed4c14cd251713ad6041e42bf7629fc56a5edc5a2124b49cc0dce273d6ee3386fae9a9cfe02e1f7e82087ea2
  languageName: node
  linkType: hard

Have you read the Contributing Guidelines on issues?
Yes 😄!
Steps to reproduce
Use https://new.docusaurus.io to create a CodeSandbox reproducible demo of the bug., N.A. because those samples are using JavaScript and this is TypeScript issue. I have a branch on my repo, however.

Clone the repo with submodules: git clone --recurse-submodules -j8 https://github.com/sapphiredev/website.git && git submodule update --init --recursive
Checkout the branch called feat/update-to-docusaurus-beta-8
Run yarn install to setup the dependency tree (note: due to submodules being in the yarn workspace this takes a bit)
Run yarn start.

Expected behavior
Everything builds fine without type errors. I have no breaking changes to cover between betas 6 and 8.
Actual behavior
When running docusaurus start with 2.0.0-beta.8 I get all of these type errors from node_modules directories:
 click me to expand large code block
Error: node_modules/@types/webpack/index.d.ts:32:3 - error TS2305: Module '"tapable"' has no exported member 'Tapable'.

32   Tapable,
     ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1081:23 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1081             resolver: SyncWaterfallHook;
                           ~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1082:22 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1082             factory: SyncWaterfallHook;
                          ~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1083:28 - error TS2707: Generic type 'AsyncSeriesWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1083             beforeResolve: AsyncSeriesWaterfallHook;
                                ~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1084:27 - error TS2707: Generic type 'AsyncSeriesWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1084             afterResolve: AsyncSeriesWaterfallHook;
                               ~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1085:27 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1085             createModule: SyncBailHook;
                               ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1086:21 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1086             module: SyncWaterfallHook;
                         ~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1087:27 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1087             createParser: HookMap;
                               ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1089:30 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1089             createGenerator: HookMap;
                                  ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1090:24 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1090             generator: HookMap;
                            ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1099:33 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1099                 evaluateTypeof: HookMap;
                                     ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1100:27 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1100                 evaluate: HookMap;
                               ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1101:37 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1101                 evaluateIdentifier: HookMap;
                                         ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1102:44 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1102                 evaluateDefinedIdentifier: HookMap;
                                                ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1103:47 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1103                 evaluateCallExpressionMember: HookMap;
                                                   ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1104:28 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1104                 statement: SyncBailHook;
                                ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1105:30 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1105                 statementIf: SyncBailHook;
                                  ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1106:24 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1106                 label: HookMap;
                            ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1107:25 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1107                 import: SyncBailHook;
                             ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1108:34 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1108                 importSpecifier: SyncBailHook;
                                      ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1109:25 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1109                 export: SyncBailHook;
                             ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1110:31 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1110                 exportImport: SyncBailHook;
                                   ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1111:36 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1111                 exportDeclaration: SyncBailHook;
                                        ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1112:35 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1112                 exportExpression: SyncBailHook;
                                       ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1113:34 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1113                 exportSpecifier: SyncBailHook;
                                      ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1114:40 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1114                 exportImportSpecifier: SyncBailHook;
                                            ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1115:33 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1115                 varDeclaration: SyncBailHook;
                                     ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1116:36 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1116                 varDeclarationLet: HookMap;
                                        ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1117:38 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1117                 varDeclarationConst: HookMap;
                                          ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1118:36 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1118                 varDeclarationVar: HookMap;
                                        ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1119:28 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1119                 canRename: HookMap;
                                ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1120:25 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1120                 rename: HookMap;
                             ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1121:27 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1121                 assigned: HookMap;
                               ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1122:25 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1122                 typeof: HookMap;
                             ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1123:29 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1123                 importCall: SyncBailHook;
                                 ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1124:23 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1124                 call: HookMap;
                           ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1125:32 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1125                 callAnyMember: HookMap;
                                    ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1126:22 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1126                 new: HookMap;
                          ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1127:29 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1127                 expression: HookMap;
                                 ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1128:38 - error TS2314: Generic type 'HookMap<H>' requires 1 type argument(s).

1128                 expressionAnyMember: HookMap;
                                          ~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1129:48 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1129                 expressionConditionalOperator: SyncBailHook;
                                                    ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1130:44 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1130                 expressionLogicalOperator: SyncBailHook;
                                                ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1131:26 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1131                 program: SyncBailHook;
                              ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1140:28 - error TS2707: Generic type 'AsyncSeriesWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1140             beforeResolve: AsyncSeriesWaterfallHook;
                                ~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1141:27 - error TS2707: Generic type 'AsyncSeriesWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1141             afterResolve: AsyncSeriesWaterfallHook;
                               ~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1142:33 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1142             contextModuleFiles: SyncWaterfallHook;
                                     ~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1143:27 - error TS2707: Generic type 'AsyncSeriesWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1143             alternatives: AsyncSeriesWaterfallHook;
                               ~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1163:21 - error TS2707: Generic type 'SyncHook<T, R, AdditionalOptions>' requires between 1 and 3 type arguments.

1163             unseal: SyncHook;
                         ~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1164:19 - error TS2707: Generic type 'SyncHook<T, R, AdditionalOptions>' requires between 1 and 3 type arguments.

1164             seal: SyncHook;
                       ~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1166:40 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1166             optimizeDependenciesBasic: SyncBailHook<Module[]>;
                                            ~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1167:35 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1167             optimizeDependencies: SyncBailHook<Module[]>;
                                       ~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1168:43 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1168             optimizeDependenciesAdvanced: SyncBailHook<Module[]>;
                                               ~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1171:23 - error TS2707: Generic type 'SyncHook<T, R, AdditionalOptions>' requires between 1 and 3 type arguments.

1171             optimize: SyncHook;
                           ~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1173:35 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1173             optimizeModulesBasic: SyncBailHook<Module[]>;
                                       ~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1174:30 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1174             optimizeModules: SyncBailHook<Module[]>;
                                  ~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1175:38 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1175             optimizeModulesAdvanced: SyncBailHook<Module[]>;
                                          ~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1190:27 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1190             shouldRecord: SyncBailHook;
                               ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1209:25 - error TS2707: Generic type 'SyncHook<T, R, AdditionalOptions>' requires between 1 and 3 type arguments.

1209             beforeHash: SyncHook;
                             ~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1210:24 - error TS2707: Generic type 'SyncHook<T, R, AdditionalOptions>' requires between 1 and 3 type arguments.

1210             afterHash: SyncHook;
                            ~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1216:33 - error TS2707: Generic type 'SyncHook<T, R, AdditionalOptions>' requires between 1 and 3 type arguments.

1216             beforeModuleAssets: SyncHook;
                                     ~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1217:40 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1217             shouldGenerateChunkAssets: SyncBailHook;
                                            ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1218:32 - error TS2707: Generic type 'SyncHook<T, R, AdditionalOptions>' requires between 1 and 3 type arguments.

1218             beforeChunkAssets: SyncHook;
                                    ~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1223:31 - error TS2707: Generic type 'AsyncSeriesHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1223             additionalAssets: AsyncSeriesHook;
                                   ~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1229:33 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1229             needAdditionalSeal: SyncBailHook;
                                     ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1230:24 - error TS2707: Generic type 'AsyncSeriesHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1230             afterSeal: AsyncSeriesHook;
                            ~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1238:33 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1238             needAdditionalPass: SyncBailHook;
                                     ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1239:28 - error TS2707: Generic type 'SyncHook<T, R, AdditionalOptions>' requires between 1 and 3 type arguments.

1239             childCompiler: SyncHook;
                                ~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1243:43 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1243             optimizeExtractedChunksBasic: SyncBailHook<Chunk[]>;
                                               ~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1244:38 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1244             optimizeExtractedChunks: SyncBailHook<Chunk[]>;
                                          ~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1245:46 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1245             optimizeExtractedChunksAdvanced: SyncBailHook<Chunk[]>;
                                                  ~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1258:27 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1258             jsonpScript?: SyncWaterfallHook<string, Chunk, string> | undefined;
                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1259:22 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1259             require: SyncWaterfallHook<string, Chunk, string>;
                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1260:32 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1260             requireExtensions: SyncWaterfallHook<string, Chunk, string>;
                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1261:28 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1261             requireEnsure: SyncWaterfallHook<string, Chunk, string>;
                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1262:24 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1262             localVars: SyncWaterfallHook<string, Chunk, string>;
                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1263:27 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1263             afterStartup: SyncWaterfallHook<string, Chunk, string>;
                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1277:22 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1277             content: SyncWaterfallHook;
                          ~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1278:21 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1278             module: SyncWaterfallHook;
                         ~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1279:21 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1279             render: SyncWaterfallHook;
                         ~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1280:22 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1280             package: SyncWaterfallHook;
                          ~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1281:19 - error TS2707: Generic type 'SyncHook<T, R, AdditionalOptions>' requires between 1 and 3 type arguments.

1281             hash: SyncHook;
                       ~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1375:25 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1375             shouldEmit: SyncBailHook<Compilation>;
                             ~~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1377:29 - error TS2707: Generic type 'AsyncSeriesHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.

1377             additionalPass: AsyncSeriesHook;
                                 ~~~~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1393:25 - error TS2707: Generic type 'SyncHook<T, R, AdditionalOptions>' requires between 1 and 3 type arguments.

1393             watchClose: SyncHook;
                             ~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1394:26 - error TS2707: Generic type 'SyncHook<T, R, AdditionalOptions>' requires between 1 and 3 type arguments.

1394             environment: SyncHook;
                              ~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1395:31 - error TS2707: Generic type 'SyncHook<T, R, AdditionalOptions>' requires between 1 and 3 type arguments.

1395             afterEnvironment: SyncHook;
                                   ~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1398:26 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1398             entryOption: SyncBailHook;
                              ~~~~~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1418:25 - error TS2707: Generic type 'SyncHook<T, R, AdditionalOptions>' requires between 1 and 3 type arguments.

1418             watchClose: SyncHook;
                             ~~~~~~~~

Error: node_modules/@types/webpack/index.d.ts:1485:24 - error TS2707: Generic type 'SyncBailHook<T, R, AdditionalOptions>' requires between 2 and 3 type arguments.

1485         _pluginCompat: SyncBailHook<compilation.Compilation>;
                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Your environment

Public source code: https://github.com/sapphiredev/website/tree/feat/update-to-docusaurus-beta-8
Public site URL: N.A. We're currently do not yet have a production release.
Docusaurus version used: 2.0.0-beta.8
Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0): Vivaldi | 4.3.2439.44, Node.js v16.12.0, Yarn v3.0.2
Operating system and version (e.g. Ubuntu 20.04.2 LTS): Windows 11 Build 22000.282

Reproducible demo
Use https://new.docusaurus.io to create a CodeSandbox reproducible demo of the bug. N.A., see reason above.

Clone the repo with submodules: git clone --recurse-submodules -j8 https://github.com/sapphiredev/website.git && git submodule update --init --recursive
Checkout the branch called feat/update-to-docusaurus-beta-8
Run yarn install to setup the dependency tree (note: due to submodules being in the yarn workspace this takes a bit)
Run yarn start.

@slorber I just tried out Canary (0.0.0-4137) and can confirm that this issue is fixed. I no longer need the cross-env NODE_OPTIONS=\"--max-old-space-size=5120\" I mentioned in my previous comment. Thanks for the awesome work!

Great, thanks 😜
Le ven. 29 oct. 2021 à 22:06, Jeroen Claassens @.***> a
écrit :

@slorber https://github.com/slorber I just tried out Canary (0.0.0-4137)
and can confirm that this issue is fixed. I no longer need the cross-env
NODE_OPTIONS="--max-old-space-size=5120" I mentioned in my previous
comment. Thanks for the awesome work!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/docusaurus/issues/5772#issuecomment-955017386,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFW6PWONOYCE4WQ3KGY5LTUJMEDXANCNFSM5GRPWZ2A
.


Documentation overhaul

What is the expected enhancement?
As we've been rapidly growing the functionality in retworkx the flat docs structure we were using before doesn't really scale. Before we push out the 0.9.0 we should work on reorganizing the documentation. The basic structure I had in mind was at the top level:

README
Graph Classes
Algorithms
Universal Functions and functions that are only applicably to single type
Generators and Random Graph functions
Visualization

Visualization Functions
Layout Functions
Examples (this can be in a follow up since we'd have to write all of these)

Detailed API Docs

Per graph type algorithm/functions
custom return types
exceptions

But this isn't set in stone, that's just the idea I had in my head, feel free to propose alternative structures. The key here though is to make the docs organization a bit more clear.
As part of this we also should update the graph class docstrings to include explicit mention that node and edge indices are stable unique identifiers of a node or edge for the lifetime of the graph. This isn't really explicitly called out anywhere and it's very important.

I will work on this. I will start by splitting the Detailed API docs (graph_*, digraph_* and methods that are less important for the user let's say) from the Algorithms section.


Change fail body

Is it possible to change fail body to JSON if token not present?
I tryed to set callback, but it not fires.

Closing as there is not enough information to answer this question.
If you can provide a succinct and self-contained code example or a failing unit test to illustrate the problem, please feel free to reopen and elaborate on your question.


ci: Use fossa-cli to check dependency licenses in CI

Closes #744

All 22 flagged license issues have been resolved. No changes need to be made to the SDK's dependencies.


Add Merchants Importer

Add Merchant importer responsible for reading the order CSV file and creating new merchants

Resolved in https://github.com/fernandesleticia/merchantsdisbursementspayouts/pull/12


Search crashes by customized properties

It would be great if App Center supports searching crashes by customized properties, sometimes a user id is not enough for locating a specific user or session.
Btw, looks iOS SDK does not have [MSAppCenter setUserId:@"your-user-id"] method in the latest SDK, but the Docs uses this method for seting the user id.

Hello @levey, thanks a lot for your feedback. While we don't have an ETA for that feature yet, we will take a note of it and use it for future prioritization in the Diagnostics service.
Best regards,
Blanca

@levey Are you using the latest SDK version? That method should definitely be there: https://github.com/Microsoft/AppCenter-SDK-Apple/blob/036d0c4281dbf072cf8afa6d2cc73f3b709445a1/AppCenter/AppCenter/MSAppCenter.h#L192-L207

@levey Are you using the latest SDK version? That method should definitely be there: https://github.com/Microsoft/AppCenter-SDK-Apple/blob/036d0c4281dbf072cf8afa6d2cc73f3b709445a1/AppCenter/AppCenter/MSAppCenter.h#L192-L207

I was using CocoaPods to install it, but looks this method was not included....

@lumaxis I do have this method in my codebase by using cocoaPods, however, the comments at this method indicates that the AppCenter backend is actually NOT using this UserId.
I've tried in my code by calling setUserId after starting the AppCenter, however, in the crash report, the userId attribute is always N/A:

So my question is, when will this feature be ready for use? Or are there any other ways to set the userId in crash report? (Because we need this attribute to search for the crash).
Thanks.
cc: @levey @blparr

@blparr @winnieli1208 @lumaxis Any updates?
https://github.com/Microsoft/appcenter/issues/84#issuecomment-470678401

@TLiu2121999 The comment is out of date. Will fix. Thanks for bringing it up!
As for why you still don't see User ID, just to double-check, is this what you followed? https://docs.microsoft.com/en-us/appcenter/sdk/other-apis/ios#identify-users . If it still doesn't work, you can reach out to us via chat bubble at bottom right of our portal, so that we can collect more information about your app to troubleshoot.

@levey I reached out via email for troubleshooting, and got feedback from Kevin:

However I never got further response after that.
Is there a link that tracks the status of this issue?

@TLiu2121999 please refer to this comment.

Hi @levey
Is the search-by-properties feature request still off the table?
If so, is there any workaround or other option how to find a specific issue by a unique value in a custom property?
Thanks

Hi @levey
Is the search-by-properties feature request still off the table?
If so, is there any workaround or other option how to find a specific issue by a unique value in a custom property?
Thanks


(test) Establish skeleton for protractor end-to-end testing

html id attributes make puppies cry :(
change to classes, or locate them differently in the test maybe?


Dark theme issue

Top-left corner has some issues if you switch to dark theme.

This showed up first after merging in the PR on May 16th.


Security issue

At line 98 in EnvironmentManager you have a hardcoded key. This should at least be generated at install, or you should replace value by value in the .env file instead of overwriting the whole file (leaving custom config values alone).
One way or another, the key should not be hardcoded.

A PR would be nice :)

Sure, I can do that.

Just double checked. There are no security issues or what so ever.
We regenerate a new key on the final step: https://github.com/RachidLaasri/LaravelInstaller/blob/master/src/Helpers/FinalInstallManager.php#L20

Hello, I don't know how that works. But it's still overwriting it, so everyone are still getting a hardcoded
"base64:bODi8VtmENqnjklBmNJzQcTTSC8jNjBysfnjQN59btE=" key, just try it yourself on a fresh one and you will see that everyone gets this key, AKA this is still quite the security issue.

The key is pulled from the newly created .env file. and as you can see here
https://github.com/RachidLaasri/LaravelInstaller/blob/master/src/Helpers/EnvironmentManager.php#L98
That's a hard coded key. So why you closed my patch I have no clue.

Hi,
I did try it and that's why I closed your issue.
The final page you see when the installation is done is this one https://github.com/RachidLaasri/LaravelInstaller/blob/master/src/Routes/web.php#L49 and as you can see it is calling a finish method inside the FinalController class. If you take a look at that  https://github.com/RachidLaasri/LaravelInstaller/blob/master/src/Controllers/FinalController.php you can clearly see that it is calling a runFinal on the FinalInstallManager class and that method https://github.com/RachidLaasri/LaravelInstaller/blob/master/src/Helpers/FinalInstallManager.php#L16-L24 itself is calling a private generateKey method which does the generation once the installer finished. So we actually do update it on the final step.

That key is not getting stored. Please download a fresh laravel and require your package and wall thru the install and you can see for yourself.

I just did, and I can confirm that it's the same key in the .env file as the one in the environment helper.

Just tried it again on a fresh Laravel install and the key gets updated on the final step.

Did you open the .env file and see yourself or are you trusting the output from the console? I would trust the file over the console...

Trust me, I did check the file itself.

Odd that on what ever platform I do this on I get this key in the .env file after the installer is done:
base64:bODi8VtmENqnjklBmNJzQcTTSC8jNjBysfnjQN59btE=

Do you have this set to true or false?
https://github.com/RachidLaasri/LaravelInstaller/blob/master/src/Config/installer.php#L21

It's true

This was fixed in #179 so it's no longer a concern.


How to call methylation on secondary alignments ? (e.g. translocated elements)

Hi,
Many thanks for this nice tool !
I am using nanopolish call-methylation (versions 0.13.2 and 0.13.3), which work fine for samples perfectly matching the reference genome, but I cannot find methylations in the case of structural variations (for instance, if a small portion of chromosome A has been translocated to the end of chromosome B, I can find methylations of chromosome B but not of the small part of chromosome A).
After the minimap2 and samtools sort commands, the secondary alignments can be found in the output file (I looked at the sam file, I guess it is similar in the bam), but when running the final command (nanopolish call-methylation) I don't get methylations for them.
Is there a specific command to enable calling methylations on the secondary alignment parts of the reads ?
Thank you for your attention !
Attached are a sam file, output of :
minimap2 -a -x map-ont CC-1690_17chr.fa Spacer_16_R_tel-m2-1.fastq | samtools sort -T tmp -o Spacer_16_R_tel-m2-1.sorted.sam
and the methylation file, output of :
nanopolish call-methylation -t 8 -r Spacer_16_R_tel-m2-1.fastq -b Spacer_16_R_tel-m2-1.sorted.bam -g CC-1690_17chr.fa > Spacer_16_R_tel-m2-1_methylation_calls.tsv
2022-03-17_methylations.zip

Try setting --min-mapping-quality 0 in call-methylation.

Thank you very much, it seems to work nicely.
Have a good day,
Best regards
Fred Chaux,
Post-Doc
Sorbonne Universite/CNRS, Paris, France
Le mar. 22 mars 2022 à 20:29, Jared Simpson @.***> a
écrit :

Try setting --min-mapping-quality 0 in call-methylation.
—
Reply to this email directly, view it on GitHub
https://github.com/jts/nanopolish/issues/996#issuecomment-1075545967,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYLTABBCBU3X4D3NFYB4CILVBINRDANCNFSM5RL3A5KA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Need more documentation on how to use ChatAsyncViewController

In the example, it would have been nice if the VIewController is doing something different by overriding behavior and state from what is already present in ChatAsyncViewController.

Hello @rajahimanath
Recently I have been busy with some other work, Will definitely update the documentation
by next week

Thank you.. Appreciate it.


Suggest to use the standard readme badge

I'm always reading this specification and when I get to this section I get lost a little trying to find the badge.

Thanks!


enhancementshut down fast throw JVM might do when throwing exception

Proposed changes
As discussed in 16107
Sometimes jvm would try to reduce the whole stack to just one line, it's kind of confusing for debugging.
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[x] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[x] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[x] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.8 seconds
load time: 493 seconds
storage size:<PHONE_NUMBER>2 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230128053025_clickbench_pr_85356.html


Support more architectures

Currently the docker image is build for linux/amd64. It would really help to have it build for more architectures e.g. linux/arm (raspberry pi 2) or linux/arm64 (raspberry pi 3/4).

Hello @Noki,
That makes sense, especially since we provide binaries for Raspberry Pi.
It seems like the best approach is to use arm32v7/alpine as base image. Their supported architectures include amd64, arm32v6, arm32v7, arm64v8 which should cover all Pi models.
I have limited experience with Pi, especially with the later models. If you have any concerns about the chosen base image or if you have any tips on useful parameters for the Pi that need to be built into the image - please let me know.

@ro-tex Alpine images are great, however arm32v7/alpine is just the alpine image for the arm32v7 architecture. As far as I know you have to build an image for each architecture and combine them using a manifest file. There are plenty of guides out there, however I've never done it on Docker Hub.
Here is an docker multi arch example: https://github.com/ckulka/docker-multi-arch-example
You can see that there are multiple arch specific docker files and a manifest combining them.
Hope this helps.

A multi-arch image sounds like a good idea but it has some drawbacks. One of them is that the complexity seems to outweigh the benefits of having such an image.
Another issue is that running siad on Raspberry Pi 1/2/Zero is problematic. Those devices are underpowered and have very limited amount of RAM. Providing an official image is not exactly promising support but it's close enough for people to open bugs which we will need to triage and debug before we can definitively say that they are caused by the limited resources of the system. At this point this doesn't seem like the best use of the limited developer time we have.
That said, building siad for ARMv6 and running it on a Raspberry Pi 1 is possible. I did it today on my old Pi 1B in order to assess the feasibility of the setup. (I waited for more than half an hour for siad to start up and begin syncing the blockchain and I gave up before it managed to succeed.) Given that we have the dev image which provides the "get the source and build it" step and the new pi image which provides the "pack it in an ARM container" step, writing an ARMv6 image is trivial, should anyone really need it. (Just replace make release with GOOS=linux GOARCH=arm GOARM=6 make release and you should be set.)
I've opened an MR (#18) which introduces an ARMv8 image which covers Pi 3 and 4. This is in alignment with the binaries we provide - we only provide pre-compiled binaries for ARMv8.

Multi-arch docker images reduce the complexety of documentation, setup and orchestration, and is less error prone than providing individual images. This helps people to get started and reduces frustration. Even if the setup to build the images is slightly more complex, it's usually worth the effort to onboard more users.
Regarding the hardware of the Raspberry Pi 1/2/Zero you are absolutely right, however there are quite some older alternatives out there based on arm32v6 and arm32v7 that are way more powerful than the old raspberry pi's (some NAS systems and quite some of this list). In my opinion it is better to support the architectures and give recommendations regarding minimal hardware requirements.
Instead of packaging the pre compiled binaries into the docker images you could also just build them from source directly on docker hub.

This makes sense. I see value in providing a readily available image to pretty much everyone running an ARM-based machine. The downside is that this will take some time and right now there are higher priority items on the agenda.
I'll do this:

I'll keep this ticket open, so it doesn't fall through the cracks and it gets followed up on when time allows.
I'll publish the already made ARMv8 image as an interim solution until enough time is available for the fully-fledged one.

Thanks for the pointer to the guide for building multi-arch images, this will be my starting point. If you happen across another/better - please share. :)

If you're compiling Sia from source you can use docker buildx --platforms linux/amd64,linux/arm64,linux/arm/v6,linux/arm/v7 -t nebulouslabs/sia:latest --push to build and push the platforms all at once without having to mess with the manifest manually.

I finally managed to get a Raspberry Pi 4 and a Raspberry Pi 1B and found some time to play with them.
Unfortunately, what I found out is not that good - Sia needs a 64bit system in order to run. The 64bit ARM is the aarch64 architecture, supported by Pi 3 and 4. The reason for this is that boltdb, which we use for storing and processing the consensus, uses memory mapped I/O, meaning that it's capped at a little under 4GB while our consensus set is north of 20GB at this point. So, you can compile siad and run it and it will start without a problem but once it syncs the first 4GB of the blockchain it will die with either panic: runtime error: index out of range [21476556800] with length<PHONE_NUMBER> or file too small. I experienced the first one on the Pi 4 with a 32bit Raspberry Pi OS (armv7l) and the second on the Pi 1B (armv6l). Running siad on the Pi 4 with a 64bit Raspberry Pi (aarch64) OS is not a problem at all.
This means that while we have the 64bit limitation set by boltdb we cannot support 32bit architectures and we already support the only 64bit ARM architecture available.
The good news is that we might have something in mind that could help with that but it's far too early to talk about it because it's (at best) on a whiteboard level.


Result wrong when Fcos model convert to tensorrt in fp16 mode.

TorchVision: 0.7.0
OpenCV: 4.5.3
MMCV: 1.3.17
MMCV Compiler: GCC 7.5
MMCV CUDA Compiler: 10.2
MMDetection: 2.18.1+c76ab0e
When Fcos model convert tensorrt not in fp16 mode, the result is right:
Not equal to tolerance rtol=0.001, atol=1e-05 The numerical values are different between Pytorch and ONNX, but it does not necessarily mean the exported ONNX model is problematic. (shapes (96, 5), (95, 5) mismatch)  x: array([[8.482639e+01, 3.473854e+02, 1.173454e+02, 3.846374e+02,         6.540170e-01],        [1.858925e+02, 1.993301e+02, 2.043786e+02, 2.202240e+02,...  y: array([[8.482641e+01, 3.473855e+02, 1.173454e+02, 3.846374e+02,         6.540173e-01],        [1.858925e+02, 1.993301e+02, 2.043786e+02, 2.202240e+02,...
When Fcos model convert tensorrt in fp16 mode,the result is different from onnx model.
The numerical values are different between Pytorch and ONNX, but it does not necessarily mean the exported ONNX model is problematic. (shapes (96, 5), (97, 5) mismatch)  x: array([[8.482639e+01, 3.473854e+02, 1.173454e+02, 3.846374e+02,         6.540170e-01],        [1.858925e+02, 1.993301e+02, 2.043786e+02, 2.202240e+02,...  y: array([[5.502793e+01, 2.728699e+02, 1.446555e+02, 3.893784e+02,         9.597778e-03],        [0.000000e+00, 0.000000e+00, 0.000000e+00, 0.000000e+00,...

Would you mind taking a look at this issue?
@RunningLeon

@jiejie1993 Hi, as is shown: The numerical values are different between Pytorch and ONNX, but it does not necessarily mean the exported ONNX model is problematic.
You could compare drawn predictions and evaluate models with https://github.com/open-mmlab/mmdetection/blob/master/tools/deployment/test.py

I have tested using the python script. The model converted in fp32 mode can detect object right, but the model converted in fp16 mode can not detect even one object. As is shown above, the max confidence in detecting result is  9.597778e-03, which is much lower than the default threadhold 0.3

@jiejie1993 Maybe the values are out of range for FP16 in some layers. Better to check it.


rfgs.txt

Our domain was already accepted in 2014 , but the person who created it did it wrong :D

Its located under lib/domains/de/rfgs/Schule.txt


People Loading in different seeds

So we might be running to many mods at the same time, And sadly i was never the one having the issues. But we had people in different seeds of the map.
Example: different layout of staircases. could walk trough doors that were not there for the rest of us.
Could drown because for him the world was flooded, while for us it was normal, he was host at one point and the world was eclipsed for him but for us it was normal... We got eaten when we landed by dogs.
ima throw my logoutput and you can try to find something in there. maybe it helps maybe it does not.. Alot of fart cushin calls.
LogOutput.zip
im not sure if the logs are reset between sessions so maybe it wont help you at all. otherwise yeah we were in the middle of playing so i had no time i just reset the mod pack we ran to a version without the lethalexpansion.
Tell me if you need something more from me and i can see what i can do.

i have the same problem except it target only 1 specific players

i have the same problem except it target only 1 specific players

did you noticed a different seed displayed at the loading ?

@DigitalIver @DrouDrougar
did you noticed a different seed displayed at the loading ?
btw your log file display 89470 times the word error, you should begin to clean your modpack

Is lethal escape compatible with this mod if it is i don't think any other mods can cause this type of desync

Is lethal escape compatible with this mod if it is i don't think any other mods can cause this type of desync

I really dunno.. i fail to pinpoint the origin of the problem

yeah i don't know, and alot of the errors is because of small things that i think we have mostly fixed. Like there is one error that is  because of an audifile that i have no idea where i should place it. Because it does not tell me where it needs to go. Cause some devs just do a hard required it to be in a specific folder, and then just place the audio file or image file in the open instead of in that specific folder.
And the seed i don't know exactly because i was not the one suffering the error, it happened to two people this time around, and since they deleted their log files when they replaced the mod packs i can't even send you that, i could clear out the log file, install the thing and test around and see if we could replicate for you?

@DrouDrougar @DigitalIver let me know if upcoming 1.2.14 fix the desync

less go hopefully it finally fix


File is too large.

Hi，
My 3D model has been put in nunustudio for more than 900M. Now nunustudio always crashes when it is half opened. Is there any way to solve this problem?
Thanks！

Hi
The parsers in nunuStudio are not optimized for high memory usage, specially in the browser were the whole files are preloaded into memory is easy to run out of memory.
Unfortunately there is not a lot that i can do to fix this problem. If possible break the model into smaller chunks.
Thanks a lot!


net/url: URL.Parse Multiple Parsing Issues

What version of Go are you using (go version)?

$ go version
go version go1.11.2 windows/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\wir3less\AppData\Local\go-build
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\wir3less\go
set GOPROXY=
set GORACE=
set GOROOT=C:\Go
set GOTMPDIR=
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\wir3less\AppData\Local\Temp\go-build829182294=/tmp/go-build -gno-record-gcc-switches

What did you do?

While playing around with URL.Parse I found a few problems I'd like to share.
I'll gladly share more details if anything is unclear or if someone is interested.
Normally, javascript:alert(1) when parsed by url.parse has no Hostname()
But javascript://alert(1) has a hostname of alert(1)
This can be taken further...
<EMAIL_ADDRESS>has a hostname of google.com and will pop an alert if relocated to by a browser (after decoding)
IPV6 support also has it's issues...
this URL http://[google.com]:80 has the hostname of google.com
But also do all of these:
http://google.com]:80
http://google.com]:80__Anything_you'd_like_sir
http://[google.com]FreeTextZoneHere]:80
Even without thinking about how this would interact with other systems and parsers,
Just considering code used URL hostname validations and Go's https functions (http.Get() for instance) leveraging url.parse should explain how this could be used maliciously.
Again, will be glad to provide more details if needed.
All POCs can be found here
https://play.golang.org/p/UoqEcxCFY8z
What did you expect to see?
Errors for most of it...
What did you see instead?
Hostnames

/cc @bradfitz

What did you see instead?
Hostnames

I think an invalid error is more appropriate.

I agree. Thats what I wrote on the "Expected" field.
Recieving a Hostname is what currently happens.

I've take a look into url_test.go https://github.com/golang/go/blob/5e1727892bf36076ee45c417b56bba32801ffbd7/src/net/url/url_test.go#L433
You can see this is design on purpose.

I see...
Well this is still the wrong behaviour, both in my opinion as well as by the spec.
The fact that we have tests for it doesn't make it right...

I don't know if this is the right place to mention this but url.Parse("localhost") sets the Path to "localhost" and the host is empty. I believe this is also an error in the parsing

@mees- Why would that be an error? You have provided a valid relative path.

I'm sorry, I misunderstood the documentation

Can I provide any more info to get this issue resolved? No point in leaving this issue open for nothing...

Try testing other parsers, non will allow that kind of parsing

If you can take each case, and show a comparison of the behavior in Python, Node and Ruby, it will help us understand the situation better.

So I've taken the time and compiled the following table
https://docs.google.com/spreadsheets/d/1HNyNO6dVYNhdsd_oLZELw4L17L3hK0r2OcZZv1lrx3Y/edit?usp=sharing
You can notice that for the Javascript URLs, Chrome is the only one actually following the spec, and python is doing a half decent job (has hostname, but ignored http specific chars like '@' in non http schemes.)
For the IPv6 URLs, you can see that Go is by far the most permissive parser.
Please keep in mind that all these vectors can be used to trick and bypass code trying to validate the host of a user-supplied URL.
I'm also going to open bugs for Node and Ruby as they are also in risk of that.

Thank you for spending time on this !

I've dug a little dipper on the Node cases.
I used node 10.0.13 for my testing, apperantly there's already 10.0.15
One of the patched is of interest to this issue - https://nodejs.org/en/blog/vulnerability/november-2018-security-releases/#hostname-spoofing-in-url-parser-for-javascript-protocol-cve-2018-12123

Glad to see this is getting fixed, I'm be happy to assist or just verify the fix if you'd like.

@wir3less We'd definitely appreciate it if you could verify the fix. For a security patch we needed to reduce disruption as much as possible, so we focused on protecting against validation bypasses, rather than rejecting all invalid hostnames (which will come in Go 1.14 as much as possible).
If you can still see validation bypass avenues, please let us know. Also, please let us know how you'd like to be credited for reporting this, if at all.
For next time, this kind of issue is worth reporting to<EMAIL_ADDRESS>rather than the issue tracker.

Great, and I completely understand. I'll go over the patch and let you know if I find anything interesting (via the security email this time :) ).
As for credit, the following would be great
Adi Cohen - adico.me
Thanks

/cc @mikesamuel who might also be interested

@gopherbot Please backport this to 1.12 and 1.11. This was a security problem.

Is net/url based on STD66 or https://url.spec.whatwg.org/ ?

@mikesamuel STD66. It cites RFC 3986 and RFC 2396. Is it relevant here? Do either allow non-numeric ports?

@FiloSottile
I don't know that they differ around ports.
IIRC, url.spec does differ around javascript://example.com/%0aalert(1).
The Appendix B regex is perfectly happy with non-numeric ports, so it really depends on whether you're strictly matching the grammar or doing approximate decomposition.

So I've taken the time and compiled the following table
https://docs.google.com/spreadsheets/d/1HNyNO6dVYNhdsd_oLZELw4L17L3hK0r2OcZZv1lrx3Y/edit?usp=sharing
You can notice that for the Javascript URLs, Chrome is the only one actually following the spec, and python is doing a half decent job (has hostname, but ignored http specific chars like '@' in non http schemes.)
For the IPv6 URLs, you can see that Go is by far the most permissive parser.
Please keep in mind that all these vectors can be used to trick and bypass code trying to validate the host of a user-supplied URL.
I'm also going to open bugs for Node and Ruby as they are also in risk of that.

Python also has the behavior (Python 3.6.4 (default, Apr  4 2019, 19:58:46))
>>> from urllib.parse import urlparse
>>><EMAIL_ADDRESS>ParseResult(scheme='javascript'<EMAIL_ADDRESS>path="/a'a", params='', query='', fragment='')
>>> a = _
>>> a.hostname
'google.com'
>>> a.username
"%250aalert(1)+'aa"

But in my opinion, this behavior<EMAIL_ADDRESS>isn't a security bug. Developer should filter XSS while writing to HTML.
And somthing following the indicator of hierarchical URL is authentication and hostname, even if the URL is non-hierarchical, parser dont need to confirm which protocols are hierarchical.

The following custom URI was accepted before, but isn't now:
s://1:2.3
A port is extracted as 2.3, which is not a valid port, but our scheme does not define the concept of a port.

The following custom URI was accepted before, but isn't now:
s://1:2.3
A port is extracted as 2.3, which is not a valid port, but our scheme does not define the concept of a port.

As far as I can tell, that's not a valid URL according to any spec. I realize it can be useful to use the URL parser for similar formats, but that convenience comes with the security cost of accepting invalid URLs that are surprising to applications that expect well formed URLs, and the name of the package is net/url.

Fair enough, I know that is not a URL.
Would you say "file://1:2.3" should fail parsing too?

Would you say "file://1:2.3" should fail parsing too?

I think it should, as the correct format for it is file:///1:2.3, where the host is empty. Does it not?

I see. I forgot about the third / meaning the part after that is treated as a path, so that wasn't a valid example.
My issue is with the assumption that any hostname that is not an IP will end with a port number.
"http://host:sub" doesn't parse either. I couldn't find if the RFC3986 mandates that the second part of any host string must be a port, but if it is I'll have to live with it. If it isn't I would prefer that the behavior of parse gets relaxed and just return the entire host name string as is.

If there is a colon in the authority, the part after it is a port, and ports can only be digits.
  authority   = [ userinfo "@" ] host [ ":" port ]
  port        = *DIGIT

https://tools.ietf.org/html/rfc3986#section-3.2

It sounds like everything was done?
If there are more problems, please file a new issue (with a more specific title).


Facing problem while using Hidden columns along with flexibilty to move visible columns

Description
Expected-
When using the HandsonTable , i want to use hidden columns and the flexibilty to move the visible columns in Angular 7 application. Is it possible to use both the functionality together and any sample present over jsfiddle?
Current behaviour-
When visible columns are moved over hidden columns, the value of columns become blank and again moving away from hidden columns the values becomes visible
Steps to reproduce
In the example below-

Columns are hidden - D,F,J
Select two visible columns and move over hidden columns
The Visible columns values become blank
When moving the values of visible columns should not become blank.

Demo
example - https://jsfiddle.net/enwLmg80/
Your environment

Angular version: 7
Handsontable version<EMAIL_ADDRESS>Wrapper version: --
Browser Name and version: Chrome
Operating System: Win 7

Hi @saurabhpandey2010
this issue has been reported for the vanilla version https://github.com/handsontable/handsontable/issues/5598 and should be fixed in the stable 8.0.0
I will update you once it happens.


Typo in "parseTempalte"

Just had a look at the code and it looked good overall. I've just noticed a typo in "parseTempalte" => "parseTemplate", and since you use this function a lot it would be better to fix it now:
https://github.com/joplin/plugin-templates/blob/1eeed0e69beba172b85a190499c7e0246bdbc2be/src/parser.ts#L1

Fixed by 4efaa84e0d7adc7dbd1a7a7eab2c3ea3fe638246


Tone.Clock.stop() without a second argument; onend is undefined

When calling stop (without a second argument) on a Tone.Clock, it tries to execute onend but it's undefined.
Chrome throws the following error:
Uncaught TypeError: onend is not a function
It breaks the whole function containing the stop call.
A jsfiddle example:
http://jsfiddle.net/rn76Ly4n/1/

The method was documented as a non-optional second argument, but i'll remove the callback from the stop method and switch it to an instance member called onended so it's more similar to the sources. it's easy enough.


about sft model

what is sft model?
in text2semantic_sft.yaml, it have
"
ckpt_path: checkpoints/text2semantic-medium-v1-2k.pth
resume_weights_only: true
"
What is the difference between sft and without sft?

For large data, there is no lots of difference. But if your data is less than 1 hour, it's recommend to begin with sft model.

what is sft model? in text2semantic_sft.yaml, it have " ckpt_path: checkpoints/text2semantic-medium-v1-2k.pth resume_weights_only: true " What is the difference between sft and without sft?

"Supervised fine-tuning" is just meaning the dataset is curated and defined in a way that the model is adjusted explicitly. Unsupervised fine tuning means youre just throwing a ton of data at the model and eventually it'll make sense of it.


[WIP] Add prose linter and basic rules

This is a WIP PR to test valelint as a possible solution for auto-checking docs against at least some of our style conventions.
For now, I've added 4 rules to check against:

Abbreviations.yml: Checks for incorrect instances of e.g., and i.e.,.
Contractions.yml: Checks for don't, can't, won't, and shouldn't.
Headings.yml: Checks that all headings use title case. This rule needs work since "step" headings in tutorials are more sentence case. A topic for further discussion.
OxfordComma.yml: Checks for this non-contentious convention :).

To try this out, first install vale:
brew tap ValeLint/vale
brew install vale

Then clone this PR and at the root of the docs repo, run:
vale v2.1

That'll run the checks against all files in the v2.1 directory.
The output is pretty intuitive, e.g.:
v2.1/view-node-details.md
 90:238  warning  Use 'will not' instead of       CockroachDB.Contractions
                  'won't'
 160:5   warning  'List node IDs' should be in    CockroachDB.Headings
                  title case
 179:5   warning  'Show the status of a single    CockroachDB.Headings
                  node' should be in title case
 195:5   warning  'Show the status of all nodes'  CockroachDB.Headings
                  should be in title case
 215:5   warning  'Decommission nodes' should be  CockroachDB.Headings
                  in title case
 219:5   warning  'Recommission nodes' should be  CockroachDB.Headings
                  in title case

 v2.1/views.md
 18:5  warning  'Hide query complexity' should  CockroachDB.Headings
                be in title case
 77:5  warning  'Limit access to underlying     CockroachDB.Headings
                data' should be in title case

✖ 4 errors, 789 warnings and 0 suggestions in 295 files.

Addresses #3125

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/7225a548f555383e6b138477414a010aa1bc9e6a/

Looks like this is the package that handles title case checking: https://github.com/jdkato/prose/blob/master/transform/title.go

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/5e6c090b90aca96ac41c451c5c3bc526a004512b/

Thanks, @rmloveland and @lhirata! I'm going to add more rules (and fix one that's not working) before merging. Probably should demo/discuss a bit in our team meeting before merging, too.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/55edebd8bc7951ff74ca22ac716938d2a7ce9a98/


[Driver] Failed to install driver 410.73

PAI Version: v0.11.0
Add a new machine to an existing cluster with 410.73 driver version, but failed to run driver-one-shot and report the following error:
ERROR: Failed to run '/usr/sbin/dkms build -m nvidia -v 410.73 -k 4.4.0-62-generic':
            Kernel preparation unnecessary for this kernel.   Skipping...

            Building module:
            cleaning build area....
            'make' -j32 NV_EXCLUDE_BUILD_MODULES=''
            KERNEL_UNAME=4.4.0-62-generic  IGNORE_CC_MISMATCH=''
            modules......(bad exit status: 2)
            Error! Bad return status for module build on kernel:
            4.4.0-62-generic(x86-64)
           Consult /var/lib/dkms/nvidia/410.73/build/make.log for more information.
ERROR: Failed to install the kernel module through DKMS.  No kernel module was installed; please
            try installing again without DKMS, or check the DKMS logs for more information.
ERROR: Installation has failed. please see the file '/var/log/nvidia-installer.log' for details. You may
            find suggestions on fixing installation problems in the README available on the linux
           driver download page at www.nvidia.com
+ echo === Loading NVIDIA UVM module
+ modprobe nvidia-uvm
=== Loading NVIDIA UVM module
modprobe: FATAL: Module nvidia-uvm not found in directory /lib/modules/4.4.0-62-generic
+ exit 1
+ exit 1

How should I do to fix this? thanks.

I tried the solution #2446 , but not work.


What are the differences between 'load_from' and 'resume_from' in config files?

For example, in configs/faster_rcnn_r50_fpn_1x.py, we have
load_from = None
resume_from = None

I have no idea what are the differences between these two properties.
Anyway, thx a lot for the great work! 😊

from the GETTING_STARTED.md:
Difference between resume_from and load_from: resume_from loads both the
model weights and optimizer status, and the epoch is also inherited from
the specified checkpoint. It is usually used for resuming the training
process that is interrupted accidentally. load_from only loads the model
weights and the training epoch starts from 0. It is usually used for
finetuning.
On Wed, Jul 17, 2019 at 2:44 PM Ye Liu<EMAIL_ADDRESS>wrote:

For example, in configs/faster_rcnn_r50_fpn_1x.py, we have
load_from = None resume_from = None
I have no idea what are the differences between these two properties.
Anyway, thx a lot for the great work!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/open-mmlab/mmdetection/issues/1012?email_source=notifications&email_token=AC7IWC5EGCTDWHO2UCSKGBLP72BSJA5CNFSM4IEJ73PKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G7TXDJQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC7IWCZ5V6HWDUCBCYJ7YM3P72BSJANCNFSM4IEJ73PA
.

from the GETTING_STARTED.md: Difference between resume_from and load_from: resume_from loads both the model weights and optimizer status, and the epoch is also inherited from the specified checkpoint. It is usually used for resuming the training process that is interrupted accidentally. load_from only loads the model weights and the training epoch starts from 0. It is usually used for finetuning.
…
On Wed, Jul 17, 2019 at 2:44 PM Ye Liu @.***> wrote: For example, in configs/faster_rcnn_r50_fpn_1x.py, we have load_from = None resume_from = None I have no idea what are the differences between these two properties. Anyway, thx a lot for the great work! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1012?email_source=notifications&email_token=AC7IWC5EGCTDWHO2UCSKGBLP72BSJA5CNFSM4IEJ73PKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G7TXDJQ>, or mute the thread https://github.com/notifications/unsubscribe-auth/AC7IWCZ5V6HWDUCBCYJ7YM3P72BSJANCNFSM4IEJ73PA .

Got it. I missed the message in GETTING_STARTED.md.
Thank you very much!


Toast not compatible with previous coding syntax

Winphone 8 is not supported
Please refrain from +1's, nuget library update requests (this is not an issue with the library), and requesting timelines for something.  Please also make sure you have read the FAQ section on the README

Please check all of the platforms you are having the issue on

[] iOS
[] Android
[] UWP
[x] PCL

Please state the issue to the best of your ability below

Previous coding usage of Toast does not work with this version 6.1.1.
Example call to Toast method:
Toast(ToastEvent.Error, Result.Message, 5);
void Toast(ToastEvent @event, String Message, Int32 DurationSeconds)
{
UserDialogs.Instance.Toast(new ToastConfig(@event, @event.ToString(), Message)
{
Duration = TimeSpan.FromSeconds(DurationSeconds)
});
}
3) Please copy and paste the exception details below.  If you are having a crash and this detail is missing, your issue will be closed without warning.

It's not supposed to be.  This is why I released a new major version

How is it used now, do you have a sample?

There is a folder right in the repo called samples.  The API isn't complex either, look at intellisense

Yes, I found that and come up with the below, but the background of the message is not Red as indicated in my code
UserDialogs.Instance.Toast(new ToastConfig("Error"))
{
BackgroundColor = System.Drawing.Color.Red,
Duration = TimeSpan.FromSeconds(3),
Message = Result.Message,
MessageTextColor = System.Drawing.Color.White
});


Error unmarshalling the following into a cloud controller error:

C:\Users\rohit\OneDrive\Desktop\Microfrofile\Day5\test>cf login -u passcode -p cmbZfThGaC
API endpoint: https://cloud.ibm.com
Error unmarshalling the following into a cloud controller error:
FAILED
C:\Users\rohit\OneDrive\Desktop\Microfrofile\Day5\test>cf7 push
No API endpoint set. Use 'cf7 login' or 'cf7 api' to target an endpoint.
FAILED
C:\Users\rohit\OneDrive\Desktop\Microfrofile\Day5\test>cf7 login
API endpoint: cloud.ibm.com
Error unmarshalling the following into a cloud controller error:
FAILED

Hello @basurohit77
Thanks for reporting this!
Can you please include your cf api and cf CLi versions, which OS you're using (obviously Windows in your case but is it 7 or 10?)
Also having what terminal you are using for this would be helpful so we can try to reproduce your error.
Thanks!
Jenna

I'm getting the same trying to login using sso:
>cf login --sso
API endpoint: https://api.sys.cfd04.aws.xxxx.cloud
Error unmarshalling the following into a cloud controller error:
<title>403 Forbidden</title>

403 Forbidden

Windows 11 Pro
cf.exe version 8.7.8+515cf4e5c.2024-02-08
From what I can see, my colleagues on Mac does not get this error.

What CAPI version you are using?


Livestream frontend improvements

Livestream frontend improvements as requested in #214

I tested this a bit earlier today and it seemed to work perfectly so I'm happy to merge this.


Using Vites Javascript API, createServer's server fails silently.

Describe the bug
I am wrapping the Vite Javascript API with some other tooling in a CLI tool. As part of this, at one point I want to start a development server. I am able to build successfully - even testing the built output with a static file server and it works fine.
But, when I run the createServer commands, fairly similar to how the docs state:
const startDevServer = ({
  buildEnv,
  rootPath,
  externalModules,
  port,
}: Options) => {
  const devServerConfig: InlineConfig = {
      mode: buildEnv,
      plugins: [react()],
      root: rootPath,
      base: './',
      envPrefix: 'CHEESE_',
      build: {
          sourcemap: true,
          rollupOptions: {
              external: externalModules ?? [],
              output: {
                  globals: {},
              },
          },
      },
      server: {
          port: port ?? DEFAULT_PORT,
          open: true,
      },
  };

   try {
      const server = await createServer(devServerConfig);
      await server.listen().then(() => {
          server.printUrls();
          console.log(chalk.cyan(`Server listen on port ${port} promise fulfilled.`));
      });
  } catch (e) {
      console.log(chalk.red(`Failure starting development server.`));
      throw e;
  }
}

Running this, everything goes successfully according to the outputs:
  ➜  Local:   http://localhost:6969/
  ➜  Network: use --host to expose
Server listen on port 6969 promise fulfilled.

Yet, it just exits immediately.
Reproduction
NA
Steps to reproduce
Take the code I pasted above and run it in a repository with a simple index.html pointing to a js file. I'm hoping this doesn't need a minimal reproduction as I am working out of a repository with private code at the moment. I can supply if this is a totally unknown condition.
System Info
System:
    OS: macOS 13.2.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 55.72 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.11.0 - ~/.nvm/versions/node/v18.11.0/bin/node
    npm: 9.4.0 - ~/.nvm/versions/node/v18.11.0/bin/npm
  Browsers:
    Chrome: 111.0.5563.146
    Firefox: 111.0.1
    Safari: 16.3

Used Package Manager
npm
Logs
No response
Validations

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

It seems there are bugs in your code:
await server.listen().then(() => {
  server.printUrls();
  console.log(chalk.cyan(`Server listen on port ${port} promise fulfilled.`));
});

You are using a mix of await and .then. server.listen() returns a promise of ViteDevServer which can be either consumed by await or .then but not both. Checkout https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises for more infomation.
I'm afraid this is as far as I can tell from the given info and further diagnosis needs a proper minimal reproduction.

 Thanks for looking anyway. It took 2 whole days to notice the process.exit so I was losing my mind.


Empty Output (non-memory-related issue)

Hello,
I've been trying to run Racon for the first time on one ONT dataset (here)
Each time I try to run it, with or without the specified options, it runs very quickly with no errors and spits out an empty file. What is happening here? Any help would be so appreciated!!
My command:
racon -m 8 -x -6 -g -8 SRR12390956.fastq aln-se.sam assembly.fasta > polished1_assembly.fasta
Log:
[racon::Polisher::initialize] loaded target sequences 0.001896 s
[racon::Polisher::initialize] loaded sequences 0.364408 s
[racon::Polisher::initialize] loaded overlaps 0.328071 s
[racon::Polisher::initialize] aligning overlaps [====================] 0.563149 s
[racon::Polisher::initialize] transformed data into windows 0.046840 s
[racon::Polisher::polish] generating consensus [====================] 0.002845 s
[racon::Polisher::] total = 1.317226 s
Racon is being operated in its own conda env.
Data on the read input file:
number of sequences:  7911
number of base pairs: 54 Mbp
Read file size: 2.2G
Assembly file generate with Flye (metaFlye)
SAM file generated with BWA
according to metaQUAST assembly QC, the assembly file has 25 contigs ( if that's helpful, idk)
all three input files are valid and full, no corruption.
Not sure how/why, but when I check racon version it says 1.5.0 despite that appearing to be too high of a version? I can't explain that

Hello,
The fastq file you are using has all qualities set to $ which is QV3, while racon has:
    -q, --quality-threshold <float>
        default: 10.0
        threshold for average base quality of windows used in POA

which means all reads are filtered out and no polishing is done.
Regarding v1.5.0, racon development has been transfered to lbcb-sci/racon repository some while ago.
Best regards,
Robert

If this does not resolve your issue, please reopen.

Thank you so much!! I will let you know if anything else pops up asap.
On Fri, May 12, 2023, 1:41 PM Robert Vaser @.***> wrote:

Hello,
The fastq file you are using has all qualities set to $ which is QV3,
while racon has:
-q, --quality-threshold <float>
    default: 10.0
    threshold for average base quality of windows used in POA

which means all reads are filtered out and no polishing is done.
Regarding v1.5.0, racon development has been transfered to lbcb-sci/racon
repository some while ago.
Best regards,
Robert
—
Reply to this email directly, view it on GitHub
https://github.com/isovic/racon/issues/236#issuecomment-1546076377, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A6ZWZXVBMTHKCGTTW7MQITLXFZY4ZANCNFSM6AAAAAAX2JDDYI
.
You are receiving this because you authored the thread.Message ID:
@.***>


WORMS REVOLUTION EXTREME [PCSB00332]

Game summary

Game name: WORMS REVOLUTION EXTREME
Game serial: PCSB00332

Vita3K summary

Version: v0.1
Build number: 295-930b9fd
Commit hash: https://github.com/vita3k/vita3k/commit/930b9fd

Test environment summary

Tested by: HorrorTroll
OS: Windows 8.1
CPU: Intel Core i5-4200H
GPU: Nvidia Geforce GTX 950M
RAM: 6 GB DDR3

Issues

Softlock
Screenshots

Log
vita3k.log
Recommended labels

Softlock

Vita3K summary

Version: v0.1
Build number: 1781
Commit hash: https://github.com/vita3k/vita3k/commit/a989885

Log
vita3k.log

Vita3K summary

Version: v0.1.5
Build number: 2630
Commit hash: https://github.com/vita3k/vita3k/commit/18dacae2
CPU backend: Dynamic

Test environment summary

Tested by: othmanead
OS: Windows 11
CPU: Intel i5-10300H
GPU: RTX 3060 mobile
RAM: 16 GB

Issue:

Game goes to menu and stays in loading screen after start

Screenshots:

Log
vita3k.log
Recommended labels

Menu


Fix metatensor-torch-related docs

Fixes #47
I also moved around some files.

📚 Documentation preview 📚: https://metatensor-models--74.org.readthedocs.build/en/74/

Docs look good now

@PicoCentauri what's going on here?

weird. RTD raises an circular import error 🤔. I will try to fix it.

Docs are looking good, thanks!


Fix host page reflow upon display of intro modal

It looks like opening the modal injects some global css. See <html> element computed properties before and after opening modal:
Before

After

I think this is part of a larger problem that the ui library is injecting global styles.

Why we have a default border colour set on the * selector is a particular mystery.


CAMEL-10139: added unit tests for all/most REST DSL components, and s…

…eeing that only camel-undertow throws an HTTP status code 405 on some operations

Adds more HTTP method tests for most / all REST DSL components, AND fixes path bug in camel-undertow


[POC]: Porting WPT utilities in Node.js core

Per the request from @mcollina , this is a proof of concept on how to use the WPT utilities in Node.js core to run WPT outside Node.js core.
Here is an outline of how the WPT currently works in Node.js core:

There are scripts in node-core-utils (git node wpt) that download tests into a specific folder and keep them in sync while maintaining a map of commit hashes. node-core-utils is a stand-alone CLI toolkit available on npm.
There is a WPT driver in Node.js core's test directory that can load a status file about expected failures, prerequisites of tests, etc., run the test in a vm, then display the results in an ad-hoc format.
The actual tests are merely calls to the driver mentioned above, which are used to communicate with the python test runner in Node.js core and to specify the globals that needs to expose to the vm (roughly what gets exposed in the IDL). For example, see the console tests.

On how the current workflow looks like, and how the status file works the detailed documentation can be found in test/wpt/README.md in Node.js core.
These are the steps run to create this PR:
git clone git@github.com:nodejs/whatwg-stream.git
cd whatwg-stream

# See https://github.com/nodejs/node/tree/2742f38/test/wpt#how-to-add-tests-for-a-new-module
mkdir -p test/wpt/status
echo "{}" > test/wpt/status/streams.json

# Pull the WPT subtree. `npm install -g node-core-utils` if you don't have it already
git node wpt streams    # for stream tests
git node wpt resources # for test harness
# Note: whatwg streams don't currently have IDL tests
# otherwise we need to run `git node wpt interfaces` to pull the IDL

# Copy the test driver
mkdir -p test/common
curl https://raw.githubusercontent.com/nodejs/node/master/test/common/wpt.js -o test/common/wpt.js

# Download and install the reference implementation for POC
git submodule add git@github.com:whatwg/streams.git streams
cd streams/reference-implementation
npm install

# Mock Node.js core test utilities
vim test/common/index.js
vim test/common/fixtures.js
# Write the test script
vim test/wpt/test-whatwg-streams.js
# Write package.json
vim package.json

Result:
npm run test

><EMAIL_ADDRESS>test /Users/joyee/projects/whatwg-stream
> node --expose-internals --experimental-worker --expose_gc test/wpt/test-whatwg-streams.js

(node:62844) ExperimentalWarning: The fs.promises API is experimental
---- byte-length-queuing-strategy.any.js ----
[PASSED] Can construct a ByteLengthQueuingStrategy with a valid high water mark
[PASSED] Can construct a ByteLengthQueuingStrategy with any value as its high water mark
[PASSED] ByteLengthQueuingStrategy constructor behaves as expected with strange arguments
[PASSED] ByteLengthQueuingStrategy size behaves as expected with strange arguments
[PASSED] ByteLengthQueuingStrategy.prototype.size should work generically on its this and its arguments
[PASSED] ByteLengthQueuingStrategy instances have the correct properties
[PASSED] ByteLengthQueuingStrategy's highWaterMark property can be set to anything
[PASSED] ByteLengthQueuingStrategy.name is correct
---- count-queuing-strategy.any.js ----
[PASSED] Can construct a CountQueuingStrategy with a valid high water mark
[PASSED] Can construct a CountQueuingStrategy with any value as its high water mark
[PASSED] CountQueuingStrategy constructor behaves as expected with strange arguments
[PASSED] CountQueuingStrategy.prototype.size should work generically on its this and its arguments
[PASSED] CountQueuingStrategy size behaves as expected with strange arguments
[PASSED] CountQueuingStrategy instances have the correct properties
[PASSED] CountQueuingStrategy's highWaterMark property can be set to anything
[PASSED] CountQueuingStrategy.name is correct

As you can see here, we are not quite there yet - the WPT runner in Node.js core currently only runs tests found in the top level of the specified directory, but the stream tests are placed in subdirectories - though it should be easy to fix with some recursive readdirs in https://github.com/nodejs/node/blob/2742f38/test/common/wpt.js
AFAICT, the differences between the WPT runner and https://github.com/domenic/wpt-runner which is used to run the tests of the reference implementation are:

wpt-runner uses JSDOM, the WPT runner in Node.js core only has a very thin abstraction over vm (this also means that the Node.js core runner cannot run tests in HTML files and doesn't understand a lot of browser stuff).
wpt-runner runs a clone of WPT (managed as a git submodule), the WPT runner in Node.js core only runs a subset of WPT that can be checked in since we don't do git submodules in Node.js core. We also need to pin the version of tests rolled into our repository, it's somewhat convenient to maintain if different subsets are versioned independently as we are still in the process of porting and fixing more tests.
wpt-runner does not seem to support status files, Node.js core has a custom status file format in order to play nice with our python test runner and the Jenkins CI, as the implementations in Node.js core are not always spec-compliant, or not spec-compliant in special builds e.g. builds without i18n support.

I don't have an opinion on how the tests should be run in this repo, but I hope an explanation would help since the this project may eventually end up being in Node.js core.
cc @domenic

Good work! I'll go through this asap, and use it as a basis for an initial implementation PR.


Low resolution help fix

the resolution is blurry, its not something unbearable but its not appealing

That's likely because of display scaling. I have it at 150%, and it is blurry for me as well.

@MurtazaJawadwala
@FeuerTiger86
I made a pull request fixing this specific issue because it was bothering me too much.
See here:
Fixed icon and UI on HiDPi-enabled devices. #255
Please comment the pull request to give it more traction. 😄
Also, here's a beta build of the HDPi version:
TaskbarGroups_HiDpi.zip
Have a great day ! 👋


feat: add egctl experimental dashboard  envoy-proxy to render the admin dashboard for the proxy

What type of PR is this?
/feature

What this PR does / why we need it:
Render the admin dashboard for the proxy, to see things like configdumps without extra steps.

Sample cmd out:
 ./egctl x dashboard envoy-proxy -n envoy-gateway-system envoy-engw-eg-a9c23fbb-558f94486c-82wh4
http://localhost:19000

@shawnh2 Thank you for the review! I think I have addressed all the comments.


Add SDS stats back into bootstrap config.

Describe the feature request
https://github.com/istio/istio/pull/10184 introduced a stats_matcher. cluster and listener stats are not in the inclusion list. There are SDS stats that are not shown in the /stats. listener.<LISTENER_IP>.server_ssl_socket_factory.ssl_context_update_by_sds and cluster.<CLUSTER_IP>.client_ssl_socket_factory.ssl_context_update_by_sds. These stats are useful for testing, monitoring, and debugging key/cert provisioning via SDS in Istio.
Describe alternatives you've considered
Add the stats back with minimum CPU and memory cost.
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[x] Policies and Telemetry
[x] Security
[ ] Test and Release
[ ] User Experience

/cc @wattli @myidpt @quanjielin

/cc @douglas-reid

There is a statsInclusion annotation that should work - can provide a link soon on my phone right now though

I am going to add listener.<LISTENER_IP>.server_ssl_socket_factory.ssl_context_update_by_sds and cluster.<CLUSTER_IP>.client_ssl_socket_factory.ssl_context_update_by_sds into the inclusion list. I am wondering if there are other useful stats we can add to monitor and debug ADS.

you can add it just to the test if it isn't universally useful as well

yeah, if these are for debugging, I wonder if we really need them on by default.  @JimmyCYJ do you think these should be on for every proxy in the mesh all the time?

@JimmyCYJ sorry couldn't give more details later. if it is just for the tests we can just add an annotation like:
sidecar.istio.io/statsInclusionPrefixes: cluster.outbound,cluster_manager,listener_manager,http_mixer_filter,tcp_mixer_filter,server,cluster.xds-grpc (except with your stats)
Or statsInclusionSuffixes or statsInclusionRegexps if those are better

@howardjohn @douglas-reid Thanks for the response. I think we need these two SDS counters on by default. If customers hit a production issue with SDS, these counters are useful for debugging. Right now we don't have a convenient view of SDS secret pushes. Is it okay for me to add requiredEnvoyStatsMatcherInclusionSuffixes="ssl_context_update_by_sds", and pass it here?https://github.com/istio/istio/blob/52e9659759c01fa91701dfc1d4da72abd9aa1f1a/pkg/bootstrap/bootstrap_config.go#L124.

@JimmyCYJ I think the required ones are actually required. Pilot-agent will not function without them, they can never be disabled.
So we could potentionally turn it on by default but cannot make it required

Add the following annotion to the POD sidecar.istio.io/statsInclusionSuffixes: ssl_context_update_by_sds
For ingress you need to add it directly as env.
https://github.com/istio/istio/wiki/Envoy-native-telemetry


Update README.md

Update README indexing a few newly published explainers.

Can we also add a link to PAS overview here?

I updated overall README for Protected Auctions from "Protected Audience", and explained what is Protected Auction that it includes both Protected Audience and Protected App Signals.
Linked in the client side explainers for those products.
Please review.


Introduce Snapshot Scheduler Support in Maya

Snapshots are supported via the K8s snapshots API. The schedules etc., will be triggered via the K8s Jobs. Currently there is no plan to support this via mayactl.


Mongo authencation enable

Please ! , how to config mongod username and password if mongo auth is enable ?

Hi, Were you able to find answer for this?
Thank you in advance


Sequence Diagram

Expected Outcome

Completed Sequence Diagram for all Use case

Current State

Nothing Done

[ ] Register
[ ] Login
[ ] Logout
[ ] Link with Facebook
[ ] Create Market
[ ] Edit Market
[ ] Remove Market
[ ] Approve Reservation
[ ] View Vendor’s payment status
[ ] Edit Profile
[ ] Edit Product/shop
[ ] View Feeds
[ ] View Received Money
[ ] View Feeds
[ ] Verify Receipt
[ ] Confirm money transfer
[ ] Become a Lessor
[ ] Upload bank account
[ ] View Market Info Page
[ ] Reserve
[ ] Propose Bank Reservation
[ ] Deposit 30%
[ ] Confirm Rental (Pay 70%)
[ ] Make Full Payment
[ ] Pay
[ ] Pay via Bank Account
[ ] Pay via Credit Card
[ ] Upload Receipt
[ ] View Reservation
[ ] View vendor profile
[ ] View Lessor Profile
[ ] Rate Lessor
[ ] Report Vendor


Resetting auth credentials is broken

When running litestream:auth more than once, creating the credentials folder fails:
mkdir: cannot create directory ‘/var/lib/dokku/config/litestream/credentials’: File exists

Need to adjust the mkdir command.
Temporary workarounds:

delete the directory prior to running the auth command
update the credentials inside the directory manually

Should be resolved by above PR


[Bug]: Need touched state set in Input, Textarea, Dropdown

Describe the bug
Touched= The user has interacted with the form control, e.g., by clicking or focusing on it.
Requirement: BA ask us to show required error when user tab-into or click into a field. We depend on touched (not dirty) state to show the errors (if any)
To Reproduce

Goa-input on keyboard-tab-in/tab-out (not mouse click) with a goa-input, most time touched state is set,
1.1 but for first-goa-input on a page (with or without focused="true"), the first tab-out 50% chance will not set
touched-state. the next time (shift-tab-back and out), it will set.
1.2 If only use mouse-click in a goa-input, then click on other fields/places, the touched state is not set.
Goa-textarea did not set touched state at all, for both keyboard-tab and mouse-eveny.
only after user input + delete, to make it dirty, then we can show errors.
Goa-dropdown:
3.1 If user focus in, expand or shrink, up/down, without make a selection, then tab-away or click-away, touched state is not set.
3.2 we can only add (focus) event-handler in it, not able to add (blur) event in it. (blur) is more useful for us to do validation.
3.3 Alt + down or alt + up to open/expand-droplist seems not working in goa-dropdown
3.4 up/down + tab-away to pick/make selection seemds not working in goa-dropdown, only "enter" or click-in-list works

Our MVP launch is coming soon in Mar 2024, but we'll need some time to QA updated components. How soon will this bug fix get into production?

@jim-muirhead The context for this states that you're trying to validate when a user is done in an input. Would validating using the _blur or onBlur event make sense for you, in this case. Basically this event allows you to validate when the user leaves the input.

Yes, validation using the onBlur event would work great.


[RFC] Separate "source" and "name" for input?

I currently have a pretty big compatibility problem with AOR and my API. I am not sure how to fix this problem without touching to the core. I am willing to contribute but I'd like to get your opinion on the solution first. If this is not the right place to discuss this, please close this issue.
My API (which is powered by api-platform/core) sends documents like this:
{
  '@id': '/api/my_resource/123,
  'Name: 'Foobar',
  'association': {
     '@id': '/api/my_other_resource/456',
     'title': 'my-other-resource-456',
  }
}

I configure an Edit page for my_resource like this:
<Edit>
<SimpleForm>
<ReferenceInput
    source="association.@id"
    reference="my_other_resource"
    allowEmpty
>
    <SelectInput optionValue="@id" optionText="title" />
</ReferenceInput>
</SimpleForm>
</Edit>

As the API returns embedded objects instead of ID relations, I have to put source="association.@id" for AOR to fill the SelectInput with the current value. If I don't do it, the Select doesn't get populated with the current value.
When I choose a different association with the Select field, and that I submit the form, the submitted data obviously looks like this:
{
  '@id': '/api/my_resource/123,
  'Name: 'Foobar',
  'association': {
     '@id': '/api/my_other_resource/789',
     'title': 'my-other-resource-456'
  }
}

When the API received this payload, it interprets it as:

Change association to point to MyOtherResource#789
Set the title of MyOtherResource#789 to 'my-other-resource-456'

Which is of course, something I do not want.
I basically need AOR to send this data:
{
  '@id': '/api/my_resource/123,
  'Name: 'Foobar',
  'association': '/api/my_other_resource/789',
}

But right now it doesn't seem to be doable as the "name" of the input field is equal to the "source" value. I am not sure what is the correct solution here. Should I create a custom ReferenceInput for my own sake that handle this case? Should we add to the core an optional props inputName that takes precedence to source if it is defined? What do you think?

If I understand correctly, the my_other_resource id is never exposed outside of the association? Your API can't expose something like:
{
  '@id': '/api/my_resource/123,
  'Name: 'Foobar',
  'association@id': '/api/my_other_resource/789',
}

If that's the case, I see 2 options:

Change your restClient to flatten the response from API platform
Write a custom input for that case.

I'm -1 for adding more configuration in the inputs. Mapping to the API is the restClient's responsibility.
I'm closing this as it's an RFC (and I try to keep the number of open issues down), but I'm interested in reading other opinions on this one.

I think you are right with your solution 1. I'll try. Thanks François!


We can speed up insertion of links up to 10 or 100 times?

https://github.com/linksplatform/Collections.Methods/blob/0f6e9e2d2d372e2dbf9ed26b772b570080e3536b/csharp/Platform.Collections.Methods/Trees/SizeBalancedTreeMethods.cs#L41-L50
Well, if we delay execution of Maintain methods, this may improve performance of Attach method.
For example we can do it only once in 10/100 or N insertions.

https://www.gitpod.io/docs/introduction/languages/dotnet

Benchmarks results:
Threashold == 0

6170ms (in order) for RecursionlessSizeBalancedTreeMethods
5354ms (in order) for SizeBalancedTreeMethods
3936ms (random) for RecursionlessSizeBalancedTreeMethods
3204ms (random) for SizeBalancedTreeMethods

Threashold == 1

6389ms (in order) for RecursionlessSizeBalancedTreeMethods
4570ms (in order) for SizeBalancedTreeMethods 4570 / 5354 = 0.85
3925ms (random) for RecursionlessSizeBalancedTreeMethods
2707ms (random) for SizeBalancedTreeMethods 2707 / 3204 = 0.84

Threashold == 2

6258ms (in order) for RecursionlessSizeBalancedTreeMethods
4764ms (in order) for SizeBalancedTreeMethods 4764 / 5354 = 0.89
4041ms (random) for RecursionlessSizeBalancedTreeMethods
2526ms (random) for SizeBalancedTreeMethods 2526 / 3204 = 0.78

Threashold == 3

6188ms (in order) for RecursionlessSizeBalancedTreeMethods
4808ms (in order) for SizeBalancedTreeMethods 4808 / 5354 = 0.90
3913ms (random) for RecursionlessSizeBalancedTreeMethods
2479ms (random) for SizeBalancedTreeMethods 2479 / 3204 = 0.77

Threshold == 4

6135ms (in order) for RecursionlessSizeBalancedTreeMethods
4827ms (in order) for SizeBalancedTreeMethods
3875ms (random) for RecursionlessSizeBalancedTreeMethods
2377ms (random) for SizeBalancedTreeMethods

Threshold == 10

6130ms (in order) for RecursionlessSizeBalancedTreeMethods
5601ms (in order) for SizeBalancedTreeMethods
3963ms (random) for RecursionlessSizeBalancedTreeMethods
2342ms (random) for SizeBalancedTreeMethods

So the most universal and optimal result is at Maintain Threshold == 1. Meaning just skip each odd maintain. This halfs the amount of Maintains, and we get about 15% performance improvement in all cases (sorted data insertion and random data insertion).


Catch errors/exceptions in hook and return non-0 status code

I'm using https://github.com/BehatExtension/DoctrineDataFixturesExtension to load fixtures before running my tests. But I made a small mistake that caused a TypeError to be raised. The output looked like this:
$ vendor/bin/behat

In LoadData.php line 56:

  Type error: Too few arguments to function App\DataFixtures\ORM\Scenarios\LoadData::__construct(), 0 passed in /var/www/symfony/vendor/doctrine/data-fixtures/lib/Doctrine/Common/DataFixtures/Loader.php on line 210 and exactly 1 expected

behat [-s|--suite SUITE] [-f|--format FORMAT] [-o|--out OUT] [--format-settings FORMAT-SETTINGS] [--init] [--lang LANG] [--name NAME] [--tags TAGS] [--role ROLE] [--story-syntax] [-d|--definitions DEFINITIONS] [--snippets-for [SNIPPETS-FOR]] [--snippets-type SNIPPETS-TYPE] [--append-snippets] [--no-snippets] [--strict] [--order ORDER] [--rerun] [--stop-on-failure] [--dry-run] [--] [<paths>]

$ echo $?
0

It seems that Behat just thinks everything is fine. It doesn't continue with the tests, but it reports a 0 as return code. The issue is that since the return code is 0 our CI thinks that everything is 👍
Should this be handled better by Behat? Or should the DoctrineDataFixturesExtension capture this somehow?

Can't reproduce anymore