Compiling @angular/material/slider : main as umd
Compiling @angular/material/snack-bar : fesm5 as esm5
Compiling @angular/cdk/stepper : fesm5 as esm5
Compiling @angular/material/snack-bar : esm2015 as esm2015
Compiling @angular/material/snack-bar : esm5 as esm5
Compiling @angular/cdk/stepper : esm2015 as esm2015
Compiling @angular/cdk/stepper : esm5 as esm5
Compiling @angular/material/snack-bar : main as umd
Compiling @angular/cdk/stepper : main as umd
Compiling @angular/material/stepper : fesm5 as esm5
Compiling @angular/material/stepper : esm2015 as esm2015
Compiling @angular/material/stepper : main as umd
Compiling @angular/cdk/table : fesm5 as esm5
Error: Failed to compile entry-point @angular/material/stepper (esm2015 as esm2015) due to compilation errors:
node_modules/@angular/common/common.d.ts:115:22 - error NG6002: Appears in the NgModule.imports of MatStepperModule, but could not be resolved to an NgModule class.

This likely means that the library (@angular/common) which declares CommonModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if
a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Iv
y.

115 export declare class CommonModule {
                         ~~~~~~~~~~~~

Compiling @angular/material/stepper : esm5 as esm5
Compiling @angular/cdk/table : esm2015 as esm2015
Compiling @angular/cdk/table : main as umd
Warning: Skipping processing of @angular/material/tooltip because its dependency @angular/material/tooltip failed to compile.
Warning: Skipping processing of @angular/material/tooltip because its dependency @angular/material/tooltip failed to compile.
Warning: Skipping processing of @angular/material/tooltip because its dependency @angular/material/tooltip failed to compile.
Warning: Skipping processing of @angular/material/tooltip because its dependency @angular/material/tooltip failed to compile.
Warning: Skipping processing of @angular/material/paginator because its dependency @angular/material/tooltip failed to compile.
Warning: Skipping processing of @angular/material/paginator because its dependency @angular/material/tooltip failed to compile.
Warning: Skipping processing of @angular/material/paginator because its dependency @angular/material/tooltip failed to compile.
Warning: Skipping processing of @angular/material/paginator because its dependency @angular/material/tooltip failed to compile.
Compiling @angular/cdk/table : esm5 as esm5
Compiling @angular/material/select : fesm5 as esm5
Warning: Skipping processing of @angular/material/table because its dependency @angular/material/tooltip failed to compile.
Warning: Skipping processing of @angular/material/table because its dependency @angular/material/tooltip failed to compile.
Warning: Skipping processing of @angular/material/table because its dependency @angular/material/tooltip failed to compile.
Warning: Skipping processing of @angular/material/table because its dependency @angular/material/tooltip failed to compile.
Compiling @angular/material/select : esm2015 as esm2015
Error: Failed to compile entry-point @angular/material/select (esm2015 as esm2015) due to compilation errors:
node_modules/@angular/common/common.d.ts:115:22 - error NG6002: Appears in the NgModule.imports of MatSelectModule, but could not be resolved to an NgModule class.

This likely means that the library (@angular/common) which declares CommonModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if
a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Iv
y.

115 export declare class CommonModule {
                         ~~~~~~~~~~~~

Compiling @angular/material/sort : fesm5 as esm5
Compiling @angular/material/sort : esm2015 as esm2015
Compiling @angular/material/select : esm5 as esm5
Compiling @angular/material/select : main as umd
Compiling @angular/material/sort : esm5 as esm5
Compiling @angular/material/sort : main as umd
Compiling @angular/material/tabs : fesm5 as esm5
Compiling @angular/material/toolbar : fesm5 as esm5
Compiling @angular/material/toolbar : esm2015 as esm2015
Compiling @angular/material/tabs : esm2015 as esm2015
Compiling @angular/material/tabs : main as umd
Compiling @angular/material/toolbar : esm5 as esm5
Error: Failed to compile entry-point @angular/material/tabs (esm2015 as esm2015) due to compilation errors:
node_modules/@angular/common/common.d.ts:115:22 - error NG6002: Appears in the NgModule.imports of MatTabsModule, but could not be resolved to an NgModule class.

This likely means that the library (@angular/common) which declares CommonModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if
a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Iv
y.

115 export declare class CommonModule {
                         ~~~~~~~~~~~~

Compiling @angular/material/toolbar : main as umd
Compiling @angular/material/tabs : esm5 as esm5
Compiling @angular/cdk/tree : esm5 as esm5
Compiling @angular/cdk/tree : esm2015 as esm2015
Compiling @angular/cdk/tree : fesm5 as esm5
Compiling @angular/cdk/tree : main as umd
Compiling @angular/material/tree : fesm5 as esm5
Compiling @angular/material/tree : esm2015 as esm2015
Compiling @angular/material/tree : esm5 as esm5
Compiling @angular/material/tree : main as umd
Compiling @angular/core/testing : fesm5 as esm5
Compiling @angular/platform-browser-dynamic : fesm5 as esm5
Compiling @angular/core/testing : esm5 as esm5
Compiling @angular/core/testing : main as umd
Compiling @angular/core/testing : esm2015 as esm2015
Compiling @angular/platform-browser-dynamic : esm2015 as esm2015
Compiling @angular/platform-browser-dynamic : main as umd
Compiling @angular/platform-browser-dynamic : esm5 as esm5
Compiling @angular/platform-browser/testing : fesm5 as esm5
Compiling @angular/platform-browser/testing : esm2015 as esm2015
Compiling @angular/platform-browser/testing : esm5 as esm5
Compiling @angular/platform-browser/testing : main as umd
Compiling @angular/common/testing : fesm5 as esm5
Compiling @angular/common/testing : esm2015 as esm2015
Compiling @angular/common/testing : esm5 as esm5
Compiling @angular/platform-browser-dynamic/testing : esm5 as esm5
Compiling @angular/platform-browser-dynamic/testing : esm2015 as esm2015
Compiling @angular/platform-browser-dynamic/testing : main as umd
Compiling @angular/platform-browser-dynamic/testing : fesm5 as esm5
Compiling @angular/common/testing : main as umd
Compiling @angular/router : fesm5 as esm5
Compiling @angular/router/testing : fesm5 as esm5
Compiling @angular/router/testing : esm5 as esm5
Compiling @angular/router/testing : esm2015 as esm2015
Compiling @angular/router : main as umd
Compiling @angular/router/testing : main as umd
Compiling @angular/router : esm2015 as esm2015
Compiling @angular/router : esm5 as esm5
Compiling @ngrx/store : fesm5 as esm5
Compiling @ngrx/store : main as umd
Compiling @ngrx/store : esm5 as esm5
Compiling @ngrx/store : esm2015 as esm2015
Compiling @ngrx/effects : fesm5 as esm5
Compiling @ngrx/effects/testing : fesm5 as esm5
Compiling @ngrx/effects : esm2015 as esm2015
Compiling @ngrx/effects : main as umd
Compiling @ngrx/effects : esm5 as esm5
Compiling @ngrx/effects/testing : esm5 as esm5
Compiling @ngrx/effects/testing : esm2015 as esm2015
Compiling @ngrx/effects/testing : main as umd
Compiling @ngrx/entity : fesm5 as esm5
Compiling @ngrx/entity : esm2015 as esm2015
Compiling @ngrx/entity : esm5 as esm5
Compiling @ngrx/entity : main as umd
Compiling @ngrx/router-store : fesm5 as esm5
Compiling @ngrx/store/testing : fesm5 as esm5
Compiling @ngrx/router-store : esm5 as esm5
Compiling @ngrx/router-store : main as umd
Compiling @ngrx/store/testing : esm5 as esm5
Compiling @ngrx/store/testing : esm2015 as esm2015
Compiling @ngrx/router-store : esm2015 as esm2015
Compiling @ngrx/store/testing : main as umd
Compiling angular-draggable-droppable : fesm5 as esm5
Compiling angular-resizable-element : fesm5 as esm5
Compiling angular-draggable-droppable : main as umd
Compiling angular-draggable-droppable : esm5 as esm5
Warning: Unable to fully load <project-path>/node_modules/angular-draggable-droppable/bundles/angular-draggable-droppable.umd.js for source-map flattening: Circular
 source file mapping dependency: <project-path>/node_modules/angular-draggable-droppable/bundles/angular-draggable-droppable.umd.js.map -> <project-path>/nod
e_modules/angular-draggable-droppable/bundles/angular-draggable-droppable.umd.js.map
Compiling angular-resizable-element : esm2015 as esm2015
Compiling angular-draggable-droppable : esm2015 as esm2015
Compiling angular-resizable-element : esm5 as esm5
Compiling angular-resizable-element : main as umd
Compiling angular-calendar : fesm5 as esm5
Compiling angular-calendar : main as umd
Compiling ngx-papaparse : fesm5 as esm5
Compiling angular-calendar : esm2015 as esm2015
Compiling angular2-highcharts : main as commonjs
Compiling angular-calendar : esm5 as esm5
Compiling ag-grid-angular : main as commonjs
Compiling ngx-papaparse : esm5 as esm5
Compiling ngx-papaparse : esm2015 as esm2015
Warning: Unable to fully load <project-path>/node_modules/ag-grid-angular/main.js for source-map flattening: ENOENT: no such file or directory, lstat '<project-path>/node_modules/ag-grid-angular/exports.js.map'
Compiling ngx-papaparse : main as umd
Compiling angular-tree-component : module as esm5
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\@angular\compiler-cli\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\ng-packagr\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 1662 packages from 1166 contributors and audited 23300 packages in 351.309s

45 packages are looking for funding
  run `npm fund` for details

found 101 vulnerabilities (94 low, 1 moderate, 6 high)
  run `npm audit fix` to fix them, or `npm audit` for details

@nac0n Thanks, that is very helpful. It does indeed look like the issue that Pete mentioned, but as @angular/common is affected and not @angular/core it is not caused by @angular/cdk/coercion (I checked and there is no import of @angular/common there).
Could you share your package.json so that I can try running ngcc myself? Just the package.json should be enough to just kick off ngcc. If there's any private dependencies feel free to remove them, hopefully I can reproduce without those being present)

@nac0n - could you provide us with a reproduction that we could play with?

@JoostK @petebacondarwin  We have a some scripts to start the application with, so i removed them. If you need them, then i'll add them and edit this comment.
{
  "name": "app",
  "version": "0.0.0",
  "license": "MIT",
  "angular-cli": {},
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "postinstall": "ngcc"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^9.1.1",
    "@angular/cdk": "^9.1.1",
    "@angular/common": "^9.1.1",
    "@angular/compiler": "^9.1.1",
    "@angular/core": "^9.1.1",
    "@angular/flex-layout": "^9.0.0-beta.29",
    "@angular/forms": "^9.1.1",
    "@angular/material": "^9.1.1",
    "@angular/platform-browser": "^9.1.1",
    "@angular/platform-browser-dynamic": "^9.1.1",
    "@angular/router": "^9.1.1",
    "@ngrx/effects": "^9.0.0",
    "@ngrx/entity": "^9.0.0",
    "@ngrx/router-store": "^9.0.0",
    "@ngrx/store": "^9.0.0",
    "ag-grid-angular": "^20.2.0",
    "ag-grid-community": "^20.2.0",
    "ag-grid-enterprise": "^20.2.0",
    "angular-calendar": "^0.28.5",
    "angular-tree-component": "^8.5.6",
    "angular2-highcharts": "^0.5.5",
    "calendar-utils": "^0.7.0",
    "core-js": "^2.6.9",
    "date-fns": "^2.10.0",
    "dexie": "^2.0.1",
    "highcharts": "^6.0.7",
    "highcharts-multicolor-series": "^2.2.1",
    "intl": "^1.2.5",
    "jquery": "^3.4.1",
    "jwt-decode": "^2.2.0",
    "moment": "^2.24.0",
    "moment-duration-format": "^1.3.0",
    "ngrx-store-freeze": "^0.2.4",
    "ngx-papaparse": "^4.0.4",
    "platform": "^1.3.4",
    "rxjs": "^6.5.3",
    "tslib": "^1.10.0",
    "typescript": "^3.7.5",
    "web-animations-js": "^2.3.2",
    "zone.js": "~0.10.2"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.900.7",
    "@angular-devkit/build-ng-packagr": "~0.900.7",
    "@angular/cli": "^9.1.1",
    "@angular/compiler-cli": "^9.1.1",
    "@angular/language-service": "^9.1.1",
    "@types/jasmine": "~2.5.53",
    "@types/jasminewd2": "~2.0.2",
    "@types/node": "^12.11.1",
    "codelyzer": "^5.1.2",
    "jasmine-core": "~2.99.1",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~3.0.0",
    "karma-chrome-launcher": "~2.2.0",
    "karma-coverage-istanbul-reporter": "^2.1.0",
    "karma-jasmine": "~1.1.2",
    "karma-jasmine-html-reporter": "^0.2.2",
    "karma-scss-preprocessor": "^3.0.0",
    "ng-packagr": "^9.0.0",
    "node-sass": "^4.12.0",
    "protractor": "~5.4.0",
    "ts-node": "~7.0.0",
    "tslint": "~5.11.0",
    "webpack-bundle-analyzer": "^3.5.1"
  }
}

@nac0n Thanks, it fails for me too! This should allow us to establish the root cause and work towards a fix.

We have a problem with our jenkins build since we migrated to Angular 9.
Everything works fine on our local machines, but when we run the build job on jenkins it fails. npm and node versions are the same on all machines.
The error appears only with "ng build --prod" - "ng build" works on jenkins.
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
npm info lifecycle<EMAIL_ADDRESS>Failed to exec build script
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR<EMAIL_ADDRESS>build: `ng build --prod`
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm timing npm Completed in 161871ms

I already put it on stackoverflow a few days ago: https://stackoverflow.com/questions/61223286/angular-9-ng-build-prod-with-devextreme-failing-only-on-jenkins

Today I updated to Angular Cli 9.1.3 - my problem (one comment above) is still there.

Same here:
Error: Call retries were exceeded
    at ChildProcessWorker.initialize (/root/app/node_modules/jest-worker/build/workers/ChildProcessWorker.js:230:21)
    at ChildProcessWorker._onExit (/root/app/node_modules/jest-worker/build/workers/ChildProcessWorker.js:307:12)
    at ChildProcess.emit (events.js:189:13)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)

Exited with code exit status 1```

Upgrading to v8 > v9.1 resulted in increased memory consumption and out-of-memory crash when using Atlassian BitBucket Pipelines.
Solved by increasing resources available to build step (size: 2x in .yaml).
This works fine but Atlassian charges double $$ when using the "2x" option! So this is a very unhappy side effect...
Current assignment: {entryPoint: @angular/platform-browser-dynamic, formatProperty: es2015, processDts: true}
Error: Process unexpectedly crashed, while processing format property es2015 for entry-point '/opt/atlassian/pipelines/agent/build/precise-our/node_modules/@angular/platform-browser-dynamic'.
at ClusterMaster.onWorkerExit (/opt/atlassian/pipelines/agent/build/precise-our/node_modules/@angular/compiler-cli/ngcc/src/execution/cluster/master.js:153:23)
at /opt/atlassian/pipelines/agent/build/precise-our/node_modules/@angular/compiler-cli/ngcc/src/execution/cluster/master.js:51:101
at ClusterMaster. (/opt/atlassian/pipelines/agent/build/precise-our/node_modules/@angular/compiler-cli/ngcc/src/execution/cluster/master.js:246:57)
at step (/opt/atlassian/pipelines/agent/build/precise-our/node_modules/tslib/tslib.js:139:27)
at Object.next (/opt/atlassian/pipelines/agent/build/precise-our/node_modules/tslib/tslib.js:120:57)
at /opt/atlassian/pipelines/agent/build/precise-our/node_modules/tslib/tslib.js:113:75
at new Promise ()
at Object.__awaiter (/opt/atlassian/pipelines/agent/build/precise-our/node_modules/tslib/tslib.js:109:16)
at EventEmitter. (/opt/atlassian/pipelines/agent/build/precise-our/node_modules/@angular/compiler-cli/ngcc/src/execution/cluster/master.js:240:32)
at EventEmitter.emit (events.js:200:13)
Compiling @angular/platform-browser/animations : es2015 as esm2015
Compiling @angular/router/testing : es2015 as esm2015
An unhandled exception occurred: NGCC failed.

Terser works for a very long and needs a lot of memory. Changing optimizations in angular.json helps.
"optimization": {
    "scripts": false,
    "styles": true
},

Upgrading to v8 > v9.1 resulted in increased memory consumption and out-of-memory crash when using Atlassian BitBucket Pipelines.
Solved by increasing resources available to build step (size: 2x in .yaml).
This works fine but Atlassian charges double $$ when using the "2x" option! So this is a very unhappy side effect...
Current assignment: {entryPoint: @angular/platform-browser-dynamic, formatProperty: es2015, processDts: true}
Error: Process unexpectedly crashed, while processing format property es2015 for entry-point '/opt/atlassian/pipelines/agent/build/precise-our/node_modules/@angular/platform-browser-dynamic'.
at ClusterMaster.onWorkerExit (/opt/atlassian/pipelines/agent/build/precise-our/node_modules/@angular/compiler-cli/ngcc/src/execution/cluster/master.js:153:23)
at /opt/atlassian/pipelines/agent/build/precise-our/node_modules/@angular/compiler-cli/ngcc/src/execution/cluster/master.js:51:101
at ClusterMaster. (/opt/atlassian/pipelines/agent/build/precise-our/node_modules/@angular/compiler-cli/ngcc/src/execution/cluster/master.js:246:57)
at step (/opt/atlassian/pipelines/agent/build/precise-our/node_modules/tslib/tslib.js:139:27)
at Object.next (/opt/atlassian/pipelines/agent/build/precise-our/node_modules/tslib/tslib.js:120:57)
at /opt/atlassian/pipelines/agent/build/precise-our/node_modules/tslib/tslib.js:113:75
at new Promise ()
at Object.__awaiter (/opt/atlassian/pipelines/agent/build/precise-our/node_modules/tslib/tslib.js:109:16)
at EventEmitter. (/opt/atlassian/pipelines/agent/build/precise-our/node_modules/@angular/compiler-cli/ngcc/src/execution/cluster/master.js:240:32)
at EventEmitter.emit (events.js:200:13)
Compiling @angular/platform-browser/animations : es2015 as esm2015
Compiling @angular/router/testing : es2015 as esm2015
An unhandled exception occurred: NGCC failed.

Same problem here! my build minutes from angular 8 to angular 9 uses are 2X (2 charge $$
:( )

Any solution on the horizon? Memory consumption of Version 9 is truly terrible. Using Angular 9 for large projects is now practically impossible.

@AlexRixhardson where's your problem? I'm building a pretty large project without any major troubles
Generating ES5 bundles for differential loading...
 ES5 bundle generation complete.
 chunk {3} runtime-es2015.4965776ca9db06ea6ab6.js (runtime) 2.86 kB [entry] [rendered]
 chunk {3} runtime-es5.4965776ca9db06ea6ab6.js (runtime) 2.86 kB [entry] [rendered]
 chunk {0} 0-es2015.b1fa1202a26db9b38672.js () 16.5 kB  [rendered]
 chunk {0} 0-es5.b1fa1202a26db9b38672.js () 18 kB  [rendered]
 chunk {1} 1-es2015.b3c8e85e279b551522a2.js () 32.9 kB  [rendered]
 chunk {1} 1-es5.b3c8e85e279b551522a2.js () 37.9 kB  [rendered]
 chunk {4} 4-es2015.b288d2c3dba8989e8209.js () 48.6 kB  [rendered]
 chunk {4} 4-es5.b288d2c3dba8989e8209.js () 52.6 kB  [rendered]
 chunk {2} common-es2015.21de0086f202963abc5d.js (common) 5.19 kB  [rendered]
 chunk {2} common-es5.21de0086f202963abc5d.js (common) 7.98 kB  [rendered]
 chunk {5} 5-es2015.0e864f4b779ed5944987.js () 21.8 kB  [rendered]
 chunk {5} 5-es5.0e864f4b779ed5944987.js () 25.1 kB  [rendered]
 chunk {19} 19-es2015.fad9bfd683e0ae8f6e80.js () 16.8 kB  [rendered]
 chunk {19} 19-es5.fad9bfd683e0ae8f6e80.js () 19.3 kB  [rendered]
 chunk {20} 20-es2015.fb6c1ffb5a53d5ff7e14.js () 7.58 kB  [rendered]
 chunk {20} 20-es5.fb6c1ffb5a53d5ff7e14.js () 9.41 kB  [rendered]
 chunk {6} 6-es2015.9c42f869f6f75a2c3773.js () 23.5 kB  [rendered]
 chunk {6} 6-es5.9c42f869f6f75a2c3773.js () 27.4 kB  [rendered]
 chunk {22} 22-es2015.121f628a284dc1a861aa.js () 13.3 kB  [rendered]
 chunk {22} 22-es5.121f628a284dc1a861aa.js () 15.7 kB  [rendered]
 chunk {23} 23-es2015.d478e567e3ef5e3b6217.js () 14.8 kB  [rendered]
 chunk {23} 23-es5.d478e567e3ef5e3b6217.js () 17 kB  [rendered]
 chunk {9} polyfills-es2015.fe8ff8fb8f06df801155.js (polyfills) 99.9 kB [initial] [rendered]
 chunk {24} 24-es2015.89e3f46eab8620576688.js () 16.9 kB  [rendered]
 chunk {24} 24-es5.89e3f46eab8620576688.js () 18 kB  [rendered]
 chunk {7} 7-es2015.d6e3d102d855e7f564e4.js () 245 kB  [rendered]
 chunk {7} 7-es5.d6e3d102d855e7f564e4.js () 248 kB  [rendered]
 chunk {10} polyfills-es5.0db8ce23004d0757760e.js (polyfills-es5) 191 kB [initial] [rendered]
 chunk {12} 12-es2015.e46b75966667ba544a78.js () 115 kB  [rendered]
 chunk {12} 12-es5.e46b75966667ba544a78.js () 118 kB  [rendered]
 chunk {13} 13-es2015.2fe8ec05e34382b7ac09.js () 108 kB  [rendered]
 chunk {13} 13-es5.2fe8ec05e34382b7ac09.js () 117 kB  [rendered]
 chunk {14} 14-es2015.5be464a2142c02795b36.js () 61 kB  [rendered]
 chunk {14} 14-es5.5be464a2142c02795b36.js () 68.2 kB  [rendered]
 chunk {16} 16-es2015.436e31a1a7056354405f.js () 36 kB  [rendered]
 chunk {16} 16-es5.436e31a1a7056354405f.js () 39.9 kB  [rendered]
 chunk {17} 17-es2015.5fa846ad1bee0417d828.js () 56.1 kB  [rendered]
 chunk {17} 17-es5.5fa846ad1bee0417d828.js () 59.4 kB  [rendered]
 chunk {18} 18-es2015.5c3a601afb63aff21ea6.js () 61.4 kB  [rendered]
 chunk {18} 18-es5.5c3a601afb63aff21ea6.js () 67.4 kB  [rendered]
 chunk {15} 15-es2015.9424c24a8d6d8b75d26f.js () 246 kB  [rendered]
 chunk {15} 15-es5.9424c24a8d6d8b75d26f.js () 258 kB  [rendered]
 chunk {21} 21-es2015.d668bdde8cc5d92a0750.js () 60.1 kB  [rendered]
 chunk {21} 21-es5.d668bdde8cc5d92a0750.js () 66.1 kB  [rendered]
 chunk {26} 26-es2015.b2d3a9144f9c518d6e64.js () 27.2 kB  [rendered]
 chunk {26} 26-es5.b2d3a9144f9c518d6e64.js () 29 kB  [rendered]
 chunk {27} 27-es2015.8d21eafe922c9a415acc.js () 40.2 kB  [rendered]
 chunk {27} 27-es5.8d21eafe922c9a415acc.js () 42.5 kB  [rendered]
 chunk {25} 25-es2015.2a5fcda8ad90042edfa3.js () 86.9 kB  [rendered]
 chunk {25} 25-es5.2a5fcda8ad90042edfa3.js () 96.3 kB  [rendered]
 chunk {29} 29-es2015.521b20b20c39a6eb7e87.js () 34.9 kB  [rendered]
 chunk {29} 29-es5.521b20b20c39a6eb7e87.js () 36.7 kB  [rendered]
 chunk {28} 28-es2015.1f904f7877adb26b28b5.js () 95.7 kB  [rendered]
 chunk {28} 28-es5.1f904f7877adb26b28b5.js () 102 kB  [rendered]
 chunk {8} main-es2015.5947390bf32c1ba51521.js (main) 3.17 MB [initial] [rendered]
 chunk {8} main-es5.5947390bf32c1ba51521.js (main) 3.39 MB [initial] [rendered]
 chunk {11} styles.c1933f821925b4bbac07.css (styles) 125 kB [initial] [rendered]
 Date: 2020-06-11T12:41:04.537Z - Hash: dae24c9daafaa63c50f6 - Time: 334649ms

I've been dealing with this issue for two nights now. Started with Bitbucket pipeline crashing yesterday with OOM exception. I've bumped up the memory to size 2x which is the max on Bitbucket cloud (8mb). I've tested locally using a local Docker instance and have been able to reproduce the same error 137.
I've tried the following changes:

I've changed a few libraries around and removed unused ones with no avail.
Set the node --max_old_space_size=8192 at build and added debugging to the pipeline stage. I can confirm it exceeds the 8192 allocation.
played with tsconfig.json configurations and angular.json configurations for AOT, optimization, sourceMap, and buildOptimizer. No help.
I was running CLI 9.1.7 and tried the latest 9.1.9 as well. No luck.
recently upgraded typescript to 3.8.3. Not the cause.

All the above would either crash with 137 error either during 40% of webpack or during es2015 to esm2015 conversion. Typically at the same spots.
.....
Compiling ngx-permissions : es2015 as esm2015
Compiling ngx-smart-popover : es2015 as esm2015
Compiling ngx-stripe : es2015 as esm2015
Compiling ngx-timeago : es2015 as esm2015
Compiling saturn-datepicker : es2015 as esm2015

<s> [webpack.Progress] 39% building 248/249 modules 1 active /opt/atlassian/pipelines/agent/build/node_modules/mini-css-extract-plugin/dist/loader.js!/opt/atlassian/pipelines/agent/build/node_modules/css-loader/dist/cjs.js??ref--13-1!/opt/atlassian/pipelines/agent/build/node_modules/postcss-loader/src/index.js??extracted!/opt/atlassian/pipelines/agent/build/node_modules/sass-loader/dist/cjs.js??ref--13-3!/opt/atlassian/pipelines/agent/build/src/styles.scss
<s> [webpack.Progress] 39% building 248/250 modules 2 active /opt/atlassian/pipelines/agent/build/node_modules/@angular-devkit/build-optimizer/src/build-optimizer/webpack-loader.js??ref--6-0!/opt/atlassian/pipelines/agent/build/node_modules/ngx-bootstrap/__ivy_ngcc__/utils/fesm2015/ngx-bootstrap-utils.js
<s> [webpack.Progress] 39% building 249/250 modules 1 active /opt/atlassian/pipelines/agent/build/node_modules/mini-css-extract-plugin/dist/loader.js!/opt/atlassian/pipelines/agent/build/node_modules/css-loader/dist/cjs.js??ref--13-1!/opt/atlassian/pipelines/agent/build/node_modules/postcss-loader/src/index.js??extracted!/opt/atlassian/pipelines/agent/build/node_modules/sass-loader/dist/cjs.js??ref--13-3!/opt/atlassian/pipelines/agent/build/src/styles.scss
<s> [webpack.Progress] 39% building 249/251 modules 2 active /opt/atlassian/pipelines/agent/build/node_modules/@angular-devkit/build-optimizer/src/build-optimizer/webpack-loader.js??ref--6-0!/opt/atlassian/pipelines/agent/build/node_modules/ngx-bootstrap/__ivy_ngcc__/component-loader/fesm2015/ngx-bootstrap-component-loader.js
<s> [webpack.Progress] 40% building 250/251 modules 1 active /opt/atlassian/pipelines/agent/build/node_modules/mini-css-extract-plugin/dist/loader.js!/opt/atlassian/pipelines/agent/build/node_modules/css-loader/dist/cjs.js??ref--13-1!/opt/atlassian/pipelines/agent/build/node_modules/postcss-loader/src/index.js??extracted!/opt/atlassian/pipelines/agent/build/node_modules/sass-loader/dist/cjs.js??ref--13-3!/opt/atlassian/pipelines/agent/build/src/styles.scss
<s> [webpack.Progress] 40% building 250/252 modules 2 active /opt/atlassian/pipelines/agent/build/node_modules/@angular-devkit/build-optimizer/src/build-optimizer/webpack-loader.js??ref--6-0!/opt/atlassian/pipelines/agent/build/node_modules/ngx-bootstrap/__ivy_ngcc__/datepicker/fesm2015/ngx-bootstrap-datepicker.js

Here is the original Angular configuration that crashes:
[line redacted]
--configuration=[redacted] --source-map --build-optimizer
     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 9.1.9
Node: 13.6.0
OS: linux x64
Angular: 9.1.11
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router, service-worker
Ivy Workspace: Yes
Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.901.9
@angular-devkit/build-angular     0.901.9
@angular-devkit/build-optimizer   0.901.9
@angular-devkit/build-webpack     0.901.9
@angular-devkit/core              9.1.9
@angular-devkit/schematics        9.1.9
@angular/cdk                      9.2.4
@angular/cli                      9.1.9
@angular/flex-layout              9.0.0-beta.31
@angular/material                 9.2.4
@angular/pwa                      0.901.9
@ngtools/webpack                  9.1.9
@schematics/angular               9.1.9
@schematics/update                0.901.9
rxjs                              6.5.5
typescript                        3.8.3
webpack                           4.42.0

I then decided to downgrade the CLI to 9.0.7 which then allowed for things to work sometimes. I then bumped up the memory allocation locally to 16GB and the build worked properly. So it teams the memory consumption has jumped at some point recently to over 8GB based on the number of dependencies, components, etc.
For me it keeps stopping at 69% progress on the build instances before exceeding 8GB. When I run it locally with 16GB of memory in a Docker container I can get it to build. Here is some more data that may help:
of modules when it completes successfully
<s> [webpack.Progress] 70% building 1674/1674 modules 0 active

of modules approximately where it stops at 69%.
<s> [webpack.Progress] 69% building 1697/1698 modules 1 active /opt/atlassian/pipelines/agent/build/node_modules/mini-css-extract-plugin/dist/loader.js!/opt/atlassian/pipelines/agent/build/node_modules/css-loader/dist/cjs.js??ref--13-1!/opt/atlassian/pipelines/agent/build/node_modules/postcss-loader/src/index.js??extracted!/opt/atlassian/pipelines/agent/build/node_modules/sass-loader/dist/cjs.js??ref--13-3!/opt/atlassian/pipelines/agent/build/src/styles.scss
<s> [webpack.Progress] 69% building 1697/1699 modules 2 active /opt/atlassian/pipelines/agent/build/node_modules/moment/locale/es-us.js
<s> [webpack.Progress] 69% building 1698/1699 modules 1 active /opt/atlassian/pipelines/agent/build/node_modules/mini-css-extract-plugin/dist/loader.js!/opt/atlassian/pipelines/agent/build/node_modules/css-loader/dist/cjs.js??ref--13-1!/opt/atlassian/pipelines/agent/build/node_modules/postcss-loader/src/index.js??extracted!/opt/atlassian/pipelines/agent/build/node_modules/sass-loader/dist/cjs.js??ref--13-3!/opt/atlassian/pipelines/agent/build/src/styles.scss
<s> [webpack.Progress] 69% building 1698/1700 modules 2 active /opt/atlassian/pipelines/agent/build/node_modules/moment/locale/es-do.js
<s> [webpack.Progress] 69% building 1699/1700 modules 1 active /opt/atlassian/pipelines/agent/build/node_modules/mini-css-extract-plugin/dist/loader.js!/opt/atlassian/pipelines/agent/build/node_modules/css-loader/dist/cjs.js??ref--13-1!/opt/atlassian/pipelines/agent/build/node_modules/postcss-loader/src/index.js??extracted!/opt/atlassian/pipelines/agent/build/node_modules/sass-loader/dist/cjs.js??ref--13-3!/opt/atlassian/pipelines/agent/build/src/styles.scss
<s> [webpack.Progress] 69% building 1699/1701 modules 2 active /opt/atlassian/pipelines/agent/build/node_modules/moment/locale/eo.js

By turning off sourceMaps I was able to go from 40% of the way to 69%. By disabling "optimization" and "buildOptimization" in angular.json I was able to get to 92% in my latest build before it died at 8GB.
I have yet to figure out why it jumped so bad in the last week. Maybe it was near the limit and just went over but I was using the same version of CLI and Angular before the error started.
Any additional thoughts on what to tweak?

We've identified a memory regression in copy-webpack-plugin that affects both v9 and v10.
More info here.

Same here moving from 9 to 10.0.1, node 14.4 ' Ineffective mark...'

This issue is affecting hundreds of people with real-world apps.   If there is no workaround, then this needs to be fixed as soon as possible.

Upgrading ng9 to ng10 has caused our builds in Bitbucket to fail even with max memory using 2x option. Build also spits out:
...
Compiling @angular/router : fesm2015 as esm2015
Compiling @angular/common/testing : fesm2015 as esm2015
**Warning: Worker #1 exited unexpectedly (code: null | signal: SIGKILL).
  Current task: {entryPoint: @angular/platform-browser/testing, formatProperty: fesm2015, processDts: true}
  Current phase: compiling**
Compiling @angular/material/core : fesm2015 as esm2015
Compiling @angular/platform-browser/testing : fesm2015 as esm2015
Compiling @angular/cdk/overlay : fesm2015 as esm2015
Compiling @angular/flex-layout/core : es2015 as esm2015
...

Two people have spent a whole day trying to fix this, to no avail. Looks like we'll have to abandon the update.

@kleky - are you running ngcc separately or is it being run as part of a CLI build? Also, are you running multiple builds in parallel? One thing you could try is running ngcc as a postinstall step on your CI to avoid it having to be run during builds, where there would be additional memory pressure from the build tooling.

@kleky - are you running ngcc separately or is it being run as part of a CLI build? Also, are you running multiple builds in parallel? One thing you could try is running ngcc as a postinstall step on your CI to avoid it having to be run during builds, where there would be additional memory pressure from the build tooling.

It appears that the out of memory was maybe caused by ngcc running async. I had a postinstall script running ngcc, but after making it ngcc --async false, this fixed a Worker error.
This issue helped
We also thought bitbucket was running at 2x memory, but it wasn't. After adding size: 2x globally this ensured it was working, so now we're building ok:
options:
  size: 2x

Facing the same issue after upgrading from 9.x.x to 10.0.8

Had this issue, after updating a project from angular 9 to 10.
After running the command ng s I get the memory error

<--- Last few GCs --->
[10905:0x102844000] 150961 ms: Mark-sweep 1377.7 (1455.9) -> 1364.3 (1455.9) MB, 913.0 / 0.0 ms (average mu = 0.185, current mu = 0.118) allocation failure scavenge might not succeed
[10905:0x102844000] 151869 ms: Mark-sweep 1364.3 (1455.9) -> 1364.3 (1455.9) MB, 907.2 / 0.0 ms (average mu = 0.094, current mu = 0.001) allocation failure GC in old space requested
<--- JS stacktrace --->
==== JS stack trace =========================================
0: ExitFrame [pc: 0x1a0d6925be3d]
Security context: 0x088ec4a9e6e9
1: /* anonymous */ [0x88e2c42ce59] [/Users/filipefreitas/dev/webfuel/doutorfinancas/clinica.doutorfinancas.pt/node_modules/webpack-sources/node_modules/source-map/lib/source-node.js:~342] [pc=0x1a0d6b8a9ede](this=0x088ec560d481 ,chunk=0x088e4a03c0e1 <String[56]: angular_core__WEBPACK_IMPORTED_MODULE_0_["\x275\x...
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 0x10003d051 node::Abort() [/usr/local/bin/node]
2: 0x10003d25b node::OnFatalError(char const*, char const*) [/usr/local/bin/node]
3: 0x1001b90e5 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
4: 0x100587042 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/usr/local/bin/node]
5: 0x100589b15 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [/usr/local/bin/node]
6: 0x1005859bf v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/usr/local/bin/node]
7: 0x100583b94 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/bin/node]
8: 0x100590458 v8::internal::Heap::AllocateRawWithLigthRetry(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/usr/local/bin/node]
9: 0x1005904af v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/usr/local/bin/node]
10: 0x10055fdf4 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [/usr/local/bin/node]
11: 0x1007e84d9 v8::internal::Runtime_AllocateInTargetSpace(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
12: 0x1a0d6925be3d
13: 0x1a0d6b8a9ede
Abort trap: 6

Was facing the same issue running our bitbucket pipeline after upgrading from Angular8 to Angular 10. Was fixed by upgrading node version from 10.x to 12.x and adding "NODE_OPTIONS=--max_old_space_size=4096" command to the pipeline steps before the ng test step.

I think it has more to do with the fact that at some point a angular-cli application now uses dart-sass, but where I'd see maybe 5 seconds tops to recompile my scss files after styling update or initial build (so basically negligible), now take a good 2+ minutes. 2 minutes each and every time scss changes made.

`93% after chunk asset optimization SourceMapDevToolPlugin styles.js generate SourceMap
<--- Last few GCs --->
[31376:000001C33EB258D0]   102015 ms: Mark-sweep 2024.1 (2065.3) -> 2018.9 (2061.4) MB, 567.8 / 0.1 ms  (average mu = 0.131, current mu = 0.041) allocation failure scavenge might not succeed
[31376:000001C33EB258D0]   102468 ms: Mark-sweep 2025.5 (2068.0) -> 2021.1 (2063.1) MB, 445.5 / 0.1 ms  (average mu = 0.081, current mu = 0.018) allocation failure scavenge might not succeed
<--- JS stacktrace --->
==== JS stack trace =========================================
0: ExitFrame [pc: 00007FF7BD3EB3BD]

Security context: 0x0020073008d1
1: /* anonymous */ [000000E426478111] [C:\Websites\gym.com\node_modules\source-map\lib\source-node.js:~174] [pc=0000027A46E8A8F5](this=0x00e426478151 ,0x03dbd9d97779 )
2: arguments adaptor frame: 3->1
3: new SourceNode [0000015CEC704389] [C:\Websites\gym.com\node_modules\sour...
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 00007FF7BC7D5EBF napi_wrap+114095
2: 00007FF7BC780B46 v8::base::CPU::has_sse+66998
3: 00007FF7BC781946 v8::base::CPU::has_sse+70582
4: 00007FF7BCF96E4E v8::Isolate::ReportExternalAllocationLimitReached+94
5: 00007FF7BCF7EF21 v8::SharedArrayBuffer::Externalize+833
6: 00007FF7BCE4B18C v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1436
7: 00007FF7BCE563C0 v8::internal::Heap::ProtectUnprotectedMemoryChunks+1312
8: 00007FF7BCE52EE4 v8::internal::Heap::PageFlagsAreConsistent+3204
9: 00007FF7BCE486E3 v8::internal::Heap::CollectGarbage+1283
10: 00007FF7BCE46D54 v8::internal::Heap::AddRetainedMap+2452
11: 00007FF7BCE681DB v8::internal::Factory::NewFixedArrayWithFiller+107
12: 00007FF7BCE68161 v8::internal::Factory::NewFixedArray+65
13: 00007FF7BCD44DFF v8::Object::GetIsolate+7631
14: 00007FF7BCBF57DA v8::internal::interpreter::JumpTableTargetOffsets::iterator::operator=+162938
15: 00007FF7BD3EB3BD v8::internal::SetupIsolateDelegate::SetupHeap+546637
16: 0000027A46E8A8F5`

Was there another regression in v10? Our build with max-old-space=3072 was building OK but got flaky after upgrade to 10. Setting max space to 4096 did not help either, but maybe 8192 will be enough - at least build got green once!
The only error I could see was: this
11-Nov-2020 16:41:32 | Option "lazyModules" is deprecated: 'SystemJsNgModuleLoader' is deprecated, and this is part of its usage. Use 'import()' syntax instead.
-- | --
11-Nov-2020 16:45:33 | Generating ES5 bundles for differential loading...
11-Nov-2020 16:46:12 | An unhandled exception occurred: Call retries were exceeded

So maybe it's not memory related?
Anyway for context, here is the output of successful build:
12-Nov-2020 09:22:27	> ng build --prod --source-map=true "*****"
12-Nov-2020 09:22:27
12-Nov-2020 09:22:30	Option "lazyModules" is deprecated: 'SystemJsNgModuleLoader' is deprecated, and this is part of its usage.  I have been trying different values for: --max_old_space_size=xxxx, but it just keeps throwing same error. Habe been upgrading node 12.x to 14.x and also deleting node_module and package-lock.json and executing npm install once again. But always same error. For me the error occurs when I try to serve the app in specific language: ng serve myApp --configuration=it. Build for specific language, does run and build without issues.
It's really a weird issue.

Little update, bumping --max_old_space_size to 8gb did not help.
I ended prioritizing and migrating to node 14, which so far looks promising. Did not see the same error yet. Sad part is that underlying cause is still unclear.
Anyway, when it comes to dependencies I only had to bump node-sass to 4.14.1 instead of 4.12 to start using v14 - hard to believe that this could have this effect.
So my/our issue does not seem to be related to memory. Any tips how would one debug something like this?

Now with Angular 11...

FATAL ERROR: MarkCompactCollector: young object promotion failed Allocation failed - JavaScript heap out of memory

I was facing the same issue after updating angular 9 to 10. it took 4 days to figure out the issue.
Solution: just install a node-sass library or if already installed then update the supported version. (i reinstalled node v14 and<EMAIL_ADDRESS>

Ugly hack workaround:
node --require ${PWD}/jenkins-build-patch-worker-count.js node_modules/.bin/ng build  --prod
jenkins-build-patch-worker-count.js
const MAX_CPUS = 1;
const os = require('os');
if (process.env.JENKINS_URL) {
  // Only warn on the parent process
  if (process.env.JENKINS_URL !== 'patch_warned') {
    console.warn(`JENKINS_URL=${process.env.JENKINS_URL} detected, forcing reduced workers`);
    process.env.JENKINS_URL = 'patch_warned';
  }
  const cpus = os.cpus;
  os.cpus = () => cpus().slice(0, MAX_CPUS);
  const utils = require('@angular-devkit/build-angular/src/utils/workers');
  if (utils.maxWorkers > 1) {
    throw new Error('Failed to patch maxWorkers in @angular-devkit/build-angular');
  }
  os.cpus = cpus;
}

@jamie-pate, thanks. It is really helpful! Was searching for this last 3 days.
I'm running ng build --prod of Angular 9in Docker on CentOS virtual machine with 8GB RAM and 15 CPUs seen.
Usually build needs up to 4GB RAM (works with --max-old-space-size=4096), but at the end TerserPlugin starts 7 new node workers, and each of them additionally requires 1-2GB RAM to finish. So additionally ~10GB of temporary RAM was needed to finalize the build.
This script finally saved my day.

Ugly hack workaround.
 RAM usage spike went from 3.5GiB to 2GiB for all processes during ng build --prod:
node --require ${PWD}/jenkins-build-patch-worker-count.js node_modules/.bin/ng build --prod

@filipesilva Please, we really need a configuration parameter to manually control the Terser workers count.

Downgrading ts-node package from ~8.3.0 to ^7.0.1 fixed the issue for me.

We have the same problem after migrating from angular 9 to angular 11. Fixed it by setting target to es5  in tsconfig.json.
Any updates on this issue?

I upgraded my node version from 10 to 14, solved the issue for me.

A lot has changed since version 9. Please update to the most recent version of Angular CLI.
v12 build time performance issues are being tracked here: https://github.com/angular/angular-cli/issues/20792


embedded contains any key

Steps to reproduce the problem
I have a table with embedded map field and NOTUNIQUE_HASH_INDEX...
now I am runnning next queries:
select from testTable where restrictionsMap containskey 'blah1'
select from testTable where restrictionsMap.keys() in ['blah1', 'blah2']

Expected behavior and actual behavior
Expecting: both queries will use index
Actual: first does, and second one does not.
If I'm doing something wrong, is there any way to speed up 'map contains any key' queries?
Important Questions
Runninng Mode

[x ] Embedded, using PLOCAL access mode

OrientDB Version

[ x] v2.1.x - Please specify last number: 2.1.13

Operating System

[ x] Linux

Thank you!!!!

Hi @facelessTT
The second query cannot use an index because the comparison is made on an expression (restrictionsMap.keys()) not on an indexed field.
For the second query, the syntax is not properly correct, you should do
select from testTable where restrictionsMap.keys() contains 'blah1' or restrictionsMap.keys() 'blah2'

Thanks
Luigi

This looks like possible workaround, but my target is to make this query work fast....
select from testTable where restictionsMap.keys() in (select list(restriction) from..... )
Which is one of situations I would use it. In fact it would be handy in many other situations.
It would be great if there will be 'contains any key' operator that uses Indexes.
Anyway, Thank you!

Hi @facelessTT
I'm marking it as an enhancement, it will be taken into consideration in next releases
Thanks
Luigi

No need for such optimization because the first query works and it's the right way to do that.

Hi @lvca I have similar query to select from testTable where restrictionsMap containskey 'blah1' .
What do you think about the clear and prettier to have the following query to avoid the multiple OR  statements in sql query :
select from testTable where restrictionsMap containskey in ['blah1','blah2','blah3'] .
Thanks
Saeed Tabrizi


Remember panel sizes in local-storage.

Cross referencing this issue over to the actual repo: https://github.com/storybooks/react-storybook/issues/466

Would be great if the action-logger panel, and the index panel, didn't not lose their size between page loads.

Would love to see that width can be remembered if down panel is configured to be displayed on right.

PR is very much welcome @willowcheng ❤

Does this previous change not solve this issue as well @willowcheng ? Haven't tried it out though, but if not, it could at least be an idea of how to tackle it.
https://github.com/storybooks/storybook-ui/pull/74/files#diff-45accb91d04d726de15be9e2a89530ebR172

Hi @benediktvaldez, it actually works and I thought it's already available to newest storybook release.
Created #80 to remember both width and height in case of use cases that need to switch panel position. I found that by dragging splitter and then changing down panel position, the height would be instantly carried to width without applying rendering, no idea how to solve it.

Please open an issue over at the new repo if you're still experiencing this issue, thanks!


Run tests on pull requests

Should now run tests in pull requests from forked repositories (assuming they have actions turned on https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#pull_request)

Coverage remained the same at 97.701% when pulling 186042ce71f6a07114baaefa947c1cc0b7e45c99 on run-builds-on-prs into cd716d8eb433aafadbf2ecdfb0235296e2602ee4 on master.


Bug: Instructor dashboard enrollments exclude current day

Currently the default instructor dashboard filter is for the last month, but it ends that month at midnight of the current day:
SELECT toStartOfDay(toDateTime(`enrollment_status_date`)) AS `__timestamp`,
       count(*) AS `count`
FROM
...
WHERE `enrollment_status_date` >= '2023-08-01'
  AND `enrollment_status_date` < '2023-08-03'
  AND `org` IN ('UMONTREAL')
  AND `enrollment_status` = 'registered'
GROUP BY toStartOfDay(toDateTime(`enrollment_status_date`))
LIMIT 100000;

This is going to be confusing to instructors and cause a lot of issues on launch day of their course, when they most want to watch enrollments. We should find a way to make this inclusive in the same way that the other enrollment charts are.

I think we can address this by using a "custom" time filter and setting the end of the window to one day after the current time. Does it make sense to leave the time frame start date as 1 month ago, or is there a better default value?

That makes sense to me


More Features

If you have any feature you would like let us know

Add a prop for weekStartDay.  Can use the Date day object index range.  For example:
<DatePicker
  value={value}
  locale="en-AU"
  weekStartDay={1}
/>

Should then display the calendar grid as:

Mon
Tue
Wed
Thu
Fri
Sat
Sun

1
2
3
4
5
6

7
8
9
10
11
12
etc

Oh cool

Implemented. Please Upgrade to version 0.4.1. You can also check it out on the Demo. Customize Dates no 4 and 5


[Feature]: Responsive and adaptive Sidebar component with full customization

Description
I propose the implementation of a highly customizable and extensible Sidebar component in Shadcn Extension.
This feature aims to provide developers with a versatile and adaptable navigation solution.
Shadcn does not provide this component, and there is an open feature request for that.
How it will work

Composable of built-in components from Shadcn.

It should contains:

2.1 Logo
2.2. Brand.
2.3 More button with popover of actions.
2.4 Navigation items ( with or without icons).
2.5 Bottom navigation.
2.6 Support card.

It should be

3.1 Adptive and dynamic width
3.2 Support RTL and LTR - Optional
Example
Desktop

Tablet

Phone

This is underway by Shadcn.
Link: https://x.com/shadcn/status/1795920507851911443


Cleanup workbench listener

Follow up on the deeplink work, I suspect those listener and buildQuery function to not be used anymore. Removing in an isolated commit in case

How are we testing this change specifically to ensure nothing breaks?

it is only manual testing for the frontend so here making sure the 2 modal still open/close fine in the workbench


Disallow spaces around dot notation

How do I enforce the following:
// valid
foo.bar();

// invalid
foo. bar();
foo .bar();
foo . bar();

Sometimes those spaces sneak in when joining lines.
I tried these options:
{
	"disallowSpaceBeforeBinaryOperators": ["."],
	"disallowSpaceAfterBinaryOperators": ["."]
}

but it did not work

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27088957-disallow-spaces-around-dot-notation?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github).

. isn't a binary operator I don't think doing what you did will work - It's a MemberExpression in that case. I'm not sure if we have a rule for spaces around . - I thought we did for new lines or something. http://jscs.info/rule/disallowOperatorBeforeLineBreak
Yeah maybe we need a new rule for that

@hzoo Can i work on this feature?

{
  "disallowSpaceBeforeMemberExpression": false,
  "disallowSpaceAfterMemberExpression": false
}

var foo = function(){console.log('foo');};
foo.prototype.boo = function(){console.log('boo');};
var obj = new foo();
obj . boo();
obj['boo']();

Wondering if we have to consider both MemberExpression here i.e obj . boo and obj ['boo']?

If you are going to name it that then maybe? Or you could create an option to turn it on for a.b and/or a['b'].Maybe true does it for both?
"disallowSpaceBeforeMemberExpression": {
  "allExcept": "" // not sure how we want to name either type
}

But yeah definitely encourage you to try sending in a PR. Most of the team will be busy working on 3.0 issues instead of adding new rules/options so help would be greatly appreciated!

@samarpanda : are you working on this? I have some time off and was considering giving this one a go.

@hzoo , I went ahead and took the initiative on this (one catchall rule for the aforementioned cases). I'm close to sending a PR, but my tests are failing with:
      at Context.<anonymous> (test/specs/rules/disallow-spaces-around-property-accessors.js:15:10)
All errors:
 - : Unsupported rule: disallowSpacesAroundPropertyAccessors

Is "unsupported rule" a normal error until it's implemented? Or am I missing something? I created the rule (per the instructions) in /lib/rules and the respective test in /test/specs/rules...
Thanks, and please bear with me as this is literally my first "IRL" PR;)

Ping us up if you are still interested


Clicking on the LPC Commons returns a 404 error

Again, this silently fails to load any information in the same manner as #285.

Fixed, rooms are no longer displayed.


Ingestion of cross-pipelines between snowflake and tableau

Hi!
When we access to view the snowflake pipelines, we see that the Tableau metadata loading pipelines also appear, it isn´t a imporant issue and we do not know if it is correct, but in previous versions it was not in such a way and if we do not call it “tableau” in the name it is confusing because we do not know if it is a snowflake or Tableau metadata loading.

Our expectation is that the ingests from tableau or any other technology other than Snowflake would not appear.
Thanks,
Carlos
Version:

OpenMetadata version: 1.5.7

Fixed as 1.6 here: https://github.com/open-metadata/OpenMetadata/pull/17990


Mapillary photo overlay can't get disabled

Hello
After enabling Mapillary photo overlay and later disabling them, the overlay doesn't disappear:

There is no problem with OpenStreetCam overlay, though.
As this misbehaviour is new, I suspect it has been introduced with the last update of iD.
Browser used: Safari 11.0.3 on macOS 10.12.6

I found out that this bug was introduced in commit https://github.com/openstreetmap/iD/commit/f54d201eb2dd8e41c083fe0ebe7d67c44d95d236
If I comment the 4 lines of this commit in master, the bug disapears.
Nonetheless, I don't know how to fix it yet =)


Use client_side_validation library API

The API is deprecated as a part of dependency tree simplification described in https://github.com/RGB-WG/rgb-core/issues/129


Added Information to create the release branch

Description
Added Information to create the release branch.
Issues Resolved
N/A
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Adding @minalsha.


Setting up a D455 Camera on Windows 11 rp

Windows 11 Pro
I have 2 cameras D455 and trying to finish a body tracking app, can you let me know where to download the set up or how I can set this up?
Thanks

Hi @javier369  If you are seeking to download and install the Windows version of the RealSense SDK then you can do so by visiting the link below and left-clicking on the Intel.RealSense.SDK-WIN10 link in the 'Assets' file list at the bottom of the page, which is an automated installer program.
https://github.com/IntelRealSense/librealsense/releases/tag/v2.53.1

Once the file has downloaded, run the installer and simply click on 'Next' a few times without changing any settings to complete installation of the SDK on Windows 11.

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

Case closed due to no further comments received.


[#11] Add 404 page.

Fix #11
Add a 404 page on which there is a link to the github issue that was searched.
Example:
https://twisted.org/trac/ticket/4567 -> https://github.com/twisted/twisted-trac-migration-3/issues/4567
Reviewers: @adiroiban
To test
With JS enabled and JS disable go to this URL:
https://deploy-preview-14--twistedmatrix.netlify.app/trac/ticket/5678/ goes to GitHub ticket page
https://deploy-preview-14--twistedmatrix.netlify.app/tra/la renders 404 page

I have reconfigured the structure of folders.
Automatic redirect to ticket on GitHub.
Other unknown links go to 404 page.
@adiroiban is this ok?


style: check manifest

Adds a manual check for the manifest (runs when running nox -s lint, but won't auto-run on pre-commit install or on pre-commit.ci, because it's kind of slow).
This adds the missing tests folder to the SDist. Some users (especially packagers like conda-forge and linux distros) like having it in the SDist.
See #550.

LGTM 👍🏻


Scrolling doesn't work for the Text keyValue

Appium version : v1.17.0-beta.1
Appium logs:
https://gist.github.com/ahashmi24/62e7638996d5da6b0d6bca02a5ae7f89
Using below code snippet to perform scrolling:
driver.executeScript("flutter:scrollUntilVisible", find.byKey("uniqueListView"), new HashMap<String, Object>() {{
put("item", find.byKey("uniqueKeyForVisibleTextOnScreen"));
put("dxScroll", 90);
put("dyScroll", -400);
}});
driver.executeScript("flutter:scroll", find.byKey("uniqueListView"), new HashMap<String, Object>() {{
  put("item", find.byKey("uniqueKeyForVisibleTextOnScreen"));
  put("dx", 50);
  put("dy", 100);
  put("durationMilliseconds", 200);
  put("frequency", 30);
}});

driver.executeScript("flutter:scrollIntoView", find.byKey("uniqueListView"), new HashMap<String, Object>() {{
  put("alignment", 0.1);
}});

Using key for ListView and visible text. I also tried with the different offset (dx & dy) to perform vertical scrolling.
Note: It is working if I use the key of any button in place of Text.

According to this code, flutter-driver simply sends flutter_driver API to the DartVM. So I assume this issue is in the Flutter side rather than flutter-driver specific.


turnOffWithDelay fails for anything over 9 seconds (P100)

turnOffWithDelay fails with the error:
raise Exception(f"Error Code: {errorCode}, {errorMessage}")
Exception: Error Code: -1003, JSON formatting error
def logonPlug():
  p100 = PyP100.P100("x.x.x.x"<EMAIL_ADDRESS>"xxxx") #Creating a P100 plug object
  p100.handshake() #Creates the cookies required for further methods
  p100.login() #Sends credentials to the plug and creates AES Key and IV for further methods
  return p100
p = logonPlug()
p.turnOffWithDelay(30)

tunOnWithDelay seems to work. Is this a feature of the plug itself p100?

Hi all, would anyone be able to help? I’m trying to use delayed power off to support a controlled shutdown of a remote pi.


[GOBBLIN-852]Reorganize the code for hive registration to isolate function

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following GOBBLIN-852 issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-852

Description

[x] Here are some details about my PR, including screenshots (if applicable):
Reorganize HiveRegistrationPublisher to isolate function. And make some filed protected to be reused in the subclass.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Run streaming job on azkaban.

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@sv2000 @autumnust Can you help review this?

Codecov Report

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

@@             Coverage Diff              @@
##             master    #2708      +/-   ##
============================================
- Coverage     44.87%   44.86%   -0.01%
- Complexity     8708     8709       +1
============================================
  Files          1879     1879
  Lines         70095    70098       +3
  Branches       7704     7705       +1
============================================
- Hits          31455    31451       -4
- Misses        35728    35735       +7
  Partials       2912     2912

Impacted Files
Coverage Δ
Complexity Δ

...e/gobblin/publisher/HiveRegistrationPublisher.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...in/java/org/apache/gobblin/cluster/SingleTask.java
73.58% <0%> (-7.55%)
9% <0%> (ø)

...a/org/apache/gobblin/cluster/GobblinHelixTask.java
76.08% <0%> (-4.35%)
5% <0%> (ø)

.../org/apache/gobblin/cluster/GobblinTaskRunner.java
64.78% <0%> (-0.94%)
29% <0%> (ø)

...main/java/org/apache/gobblin/util/HadoopUtils.java
30.53% <0%> (+0.33%)
24% <0%> (ø)
:arrow_down:

...lin/restli/throttling/ZookeeperLeaderElection.java
72.22% <0%> (+2.22%)
13% <0%> (ø)
:arrow_down:

...lin/util/filesystem/FileSystemInstrumentation.java
92.85% <0%> (+7.14%)
3% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


GoogleDataTransportCCTSupport error after pod update

On iOS 13, errors inside GoogleDataTransport
Xcode version: 11.0
Firebase SDK version: 6.10.0
Firebase Component: Core
Component version: latest
I am getting this error
Pods/GoogleDataTransportCCTSupport/GoogleDataTransportCCTSupport/GDTCCTLibrary/GDTCCTUploader.m:119:65: runtime error: null pointer passed as argument 1, which is declared to never be null
Pods/GoogleDataTransportCCTSupport/GoogleDataTransportCCTSupport/GDTCCTLibrary/Private/GDTCCTNanopbHelpers.h:110:52: note: _Nonnull type annotation specified here
Any solution ?

I will second this issue. This too occurs with the manual installation of the SDK. When will this be fixed? Apps are breaking in iOS 13.

Working on it right now.
On Wed, Oct 9, 2019 at 12:33 PM Jay Cambron<EMAIL_ADDRESS>wrote:

I will second this issue. This too occurs with the manual installation of
the SDK. When will this be fixed? Apps are breaking in iOS 13.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/firebase/firebase-ios-sdk/issues/4027?email_source=notifications&email_token=AAIILAQADB5ZLULQN7CE7DDQNYWY3A5CNFSM4I64RZX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAZB2FI#issuecomment-540155157,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIILAX6DYNU3HHLG4NCTTTQNYWY3ANCNFSM4I64RZXQ
.

GoogleDataTransport 3.0.1 and GoogleDataTransportCCTSupport 1.2.1 were just pushed and they should address this issue. Because this is an out-of-band release, please report back quickly if you encounter any issues!

thanks @mikehaney24 I will check to see if the build will work. I implement the sdk in my cordova plugin https://www.npmjs.com/package/cordova-firebase-plugin

@mikehaney24  I am using the current release 6.11.0 from here https://firebase.google.com/docs/ios/setup#frameworks, which i believe has your changes in it. However, I am now seeing another issue. See the attached screenshot.

@cambronjay Please verify that the project is actually linking GoogleDataTransport.framework and it's the version from the 6.11.0 release.

@paulb777 it is using the 6.11.0 release and the GoogleDataTransport.framwork is included with the  analytics portion of the SDK. I don't how else it would/could be linked. The past version worked with no errors. These past two releases have not worked.

@mikehaney24  i am still experiencing an issue in 6.11.0 Any chance there will be a fix soon?

@cambronjay 6.12.0 was released yesterday.  However, since no one else has reported this problem that would break any zip distribution usage, it seems highly likely that there is something going on with your particular configuration.

@paulb777 The issue has been reported in a different thread, but i believe you have closed it. I will retest with 6.12.0 and see if the issue is resolved.


fix: Alpha are unable to perform a second modification to a Dataset when in Explore

SUMMARY

Fix issue when Alpha users want to make a secondary change in Edit Dataset. The issue lies with the API from datasource/save returning a different payload for datasource.owners. To handle we'll add an additional check for the key value to make sure the user will still be able to edit moving forward.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up


Could support other port instead of 5432 of postgresql?

Just specify the port in the connection parameters.
See:

https://miniflux.app/docs/configuration.html#dsn
https://godoc.org/github.com/lib/pq#hdr-Connection_String_Parameters


[WIP] Integrate draggable with connectToSortable support

Implementation for draggable/connectToSortable integration.

This is still a WIP. Added this PR for easier discussion.

@nickschot Please rebase this against upstream master and we'll go from there.

Will do!

Alright...so we have a few tests to make pass or rewrite.

Yes part of it can be removed if we decide to remove the content mutation from the addon (which is why at least part of the tests fail).
My next step will be a small example scenario in the dummy app so you can see what exactly I wanted to achieve.
Also I'm not yet sure of the way I'm taking care of the "out" and "over" events. Might be cleaner to implement those as actions (like "moved") instead of options (as they are not options...).

I agree with out and over being handled via actions.

@nickschot One change I'd like to see. It looks like you're implementing the ui-draggable component as an array rather than a single draggable. {{ui-draggable}} should be a single draggable instance, same as how you'd apply it the plugin if you were using only jQuery.

@ToddSmithSalter agreed. I'll do that.

I would only support block form. The only instance where someone might not, would be a text only draggable item. It would be best to simply {{yield}} whatever is passed in the block, text or more. At least it would make for a simple and understandable API.

The connectWith option also works fine by just adding the option.

We need an integration test for ui-draggable before merging and publishing.

Definitely. Unfortunately I don't have any time until Friday. So if you can wait that long I can give it a go :)
Also there's still the out/over thing. It's doing console.log's now? It should just be a bindable function/action right? Don't think the addon has to do anything else with it. I currently use those binds to change the appearance of the draggable during drag.

Still a little short on time. I'll try to work it out later this week.

I'm not sure what the devil is going on with Travis + npm. Will have to peek later.

I'll also update the readme a bit within the weekend


Switch mode: Unable to view the content. Getting error pop up when switched from designer to code view and viceversa

Describe the Bug with repro steps
1.Create a consumption-based logic app.
2.Open designer.
3, Add request trigger.

Select the “Google sheet – insert row”

File: your excel file
Worksheet: select the sheet
5.Switch mode, from designer to code view and code view to designer, make sure the content does not change

Expected: Content should not change and should be able to see the previous added content.
**Actual:**Unable to view the content. Getting error pop up
What type of Logic App Is this happening in?
Consumption (Portal)
Which operating system are you using?
Windows
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos

Browser
Edge
Additional context
Version: 2.41007.1.5

Eric says that this is nonblocking for this release, we can look into this

Issue not repro in latest test pass. Closing this issue
Version: 2.41028.1.6

Issue repro in latest test pass. Reopening the issue
Version: 0.2022.1.794

Issue not repro in latest updated test pass. Closing this issue
Version: 0.2022.1.796
https://github.com/user-attachments/assets/7898c9c0-d23b-41aa-945d-fabae524b226


Update -pool.md

Metadata fix

@EliotSeattle,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Added typical Korean keyboard function

I remembered that we had made the keyboard function a little different from a typical Korean keyboard. The biggest thing is backspacing will delete the whole Hangul character and not the Jamo within it. Since you also have the physical backspace that functions this way, we figured it might be nice to add this deleting Jamo function.
I want ahead and changed the code to allow for a more typical Korean Keyboard function, because I figured you might want that instead.

This certainly simplifies the code at least. Hrms...
So physical Korean keyboards only delete entire Hangul when pressing backspace, even the one you're currently working on? This differs from the behaviour of the online Korean keyboards I tried which delete jamo-by-jamo.
https://www.branah.com/korean
https://www.typingkeyboard.com/korean-keyboard/
https://gate2home.com/Korean-Keyboard
In addition to this, I'm also interested in the Complete button you've added. The Korean layouts online don't seem to include such a button. Is there another way to trigger a "complete hangul" on a physical keyboard? Like spacebar perhaps?

My bad, it is still supposed to delete jamo-by-jamo for the one you're working on. Didn't noticed it was doing this when I made the changes last night, my bad. We based it behavior partly off of Windows OSK for Korean, which does delete the Hangul characters and not the jamo if it's not the one you're working on. As for the complete button, you can also just click the text box to complete the Hangul, but we figured it'd be easier to just have a complete button to do this. Physical keyboards, you can just use the arrow keys.
I would personally keep the complete button, people who aren't familiar using a Korean layout might find it very helpful. People who are will probably not really need to use it that much, but it might be helpful if they need it.
I can go ahead fix the changes I made so it does delete jamo for the current Hangul you're on, but if you like deleting jamo-by-jamo just in general, I don't really think there's much harm in keeping it that way.


balena-dash doesn't seem to support HLS/MPEG-DASH video streams?

Great work, Balena may be exactly what we've been looking for.
I've been trying to run the following web application using balena-dash: https://d1174xcjip7dlv.cloudfront.net
The web app plays HLS streams (using https://github.com/CookPete/react-player). In regular Webkit browsers, this works fine (e.g. Safari) - but not in belena-dash. Not sure how to debug, it simply shows a black screen.
Any tips?

@fabdrol This seems to be a problem stemming from WPE foundation of this project. I also experienced issues like this; especially when trying to view live streams.
You may find this project useful.  It's a fork of the old Resin-ElectronJS project, and an alternative to this one.


Python blog refactor

Closes #29

Section division validated
missing headings added
fixed code cells wherever required

Deploy preview looks good: https://deploy-preview-32--ayush-blog.netlify.app/Python/01-Quick-Tips/. Will merge.

There is still scope of creating sub-articles out of this. For now, the sections are ok.


chore: archive and redirect

Update the readme to redirect users to the monorepo where this package has been migrated.
Merge this when the migration PR has been merged.

I wouldn’t delete the content of the repository! There’s a way to archive and mark the repository as read-only in the settings. :)


Display DOI and Metax information for published folders

Description

As a follow-up of #455 we need to be able to display to the users information about the Datacite published DOI.
In the folder there is a key extraInfo with the necessary information:
"extraInfo": {
        "studyIdentifier": {
            "accessionId": "acccessionId",
            "identifier": {
                "identifierType": "DOI",
                "doi": "https://doi.url"
            },
            "url": "https://etsin.url",
            "types": {
                "resourceTypeGeneral": "Collection"
            }
        },
        "datasetIdentifiers": [
            {
                "accessionId": "acccessionId1",
                "identifier": {
                    "identifierType": "DOI",
                    "doi": "https://doi.url"
                },
                "url": "https://etsin.url",
                "types": {
                    "ris": "DATA",
                    "bibtex": "misc",
                    "citeproc": "dataset",
                    "schemaOrg": "Dataset",
                    "resourceTypeGeneral": "Collection"
                }
            },
            {
                "accessionId": "acccessionId2",
                "identifier": {
                    "identifierType": "DOI",
                    "doi": "https://doi.url"
                },
                "url": "https://etsin.url",
                "types": {
                    "ris": "DATA",
                    "bibtex": "misc",
                    "citeproc": "dataset",
                    "schemaOrg": "Dataset",
                    "resourceTypeGeneral": "Collection"
                }
            }
        ],
        "publicationYear": 2020,
        "publisher": "CSC"
    }

to display:

the DOI id from key doi with the corresponding URL
publication year
publisher
types -> resourceTypeGeneral

should be visible when opening a published folder

Optional: display also information from doiInfo key from folder
DoD (Definition of Done)

DOI info is listed for published folders
Testing

Integration Testing

This issue will be proceeded as soon as its UI design is ready.


[Build] Update scripts to use dyld_info

Cherry-pick of https://github.com/apple/swift/pull/60532 to fix the dyldinfo vs dyld_info difference in Xcode 13 vs 14.

@swift-ci please test


Multiple UI Improvements

Acceptance Criteria

[x] login and register box have the same height
[ ] button in "Hochladen-Banner" should be smaller (xs -tag)
[x] rename label "Über XX Tage" in "Umfang: XX Tage"

@hefowe: Could you please check the "Hochladen-Banner" ?

I suppose you mean @hendraet?

Yes :D

:purple_heart:


Test in the adb-over-network environment

tl;dr
Seems to work fine. Closing for now.

Used three Nexus 9 devices for testing. Connected each device via USB cable one at a time, in order to enable the TCP mode for the device.
<for each device...>
$ adb tcpip 5555

Then, I disconnected all the USB data cables, and connected to these devices with their IP addresses. These devices were all on the same WiFi network, including the laptop on which I ran these adb commands.
<for each device...>
$ adb connect 192.168.86.xxx:5555

After this setup, the output of adb devices looks like this:
$ adb devices
List of devices attached
<IP_ADDRESS>:5555	device
<IP_ADDRESS>:5555	device
<IP_ADDRESS>:5555	device

I gave some nicknames (WiFi01~WiFi03) to these devices. The <ip addr:port> can be used in place of the serial number.
$ madb name set <IP_ADDRESS>:5555 WiFi01
$ madb name set <IP_ADDRESS>:5555 WiFi02
$ madb name set <IP_ADDRESS>:5555 WiFi03
$ madb name list
Serial          Nickname
========================
<IP_ADDRESS>:5555	WiFi01
<IP_ADDRESS>:5555	WiFi02
<IP_ADDRESS>:5555	WiFi03

Finally, here's the output of running madb start command from one of our example projects.
[WiFi02]	372 KB/s (21315064 bytes in 55.930s)
[WiFi02]		pkg: /data/local/tmp/app-universal-debug.apk
[WiFi01]	360 KB/s (21315064 bytes in 57.805s)
[WiFi03]	357 KB/s (21315064 bytes in 58.173s)
[WiFi01]		pkg: /data/local/tmp/app-universal-debug.apk
[WiFi03]		pkg: /data/local/tmp/app-universal-debug.apk
[WiFi02]	Success
[WiFi02]	Stopping: io.v.android.apps.reader
[WiFi02]	Starting: Intent { cmp=io.v.android.apps.reader/.DeviceSetChooserActivity }
[WiFi03]	Success
[WiFi03]	Stopping: io.v.android.apps.reader
[WiFi03]	Starting: Intent { cmp=io.v.android.apps.reader/.DeviceSetChooserActivity }
[WiFi01]	Success
[WiFi01]	Stopping: io.v.android.apps.reader
[WiFi01]	Starting: Intent { cmp=io.v.android.apps.reader/.DeviceSetChooserActivity }
$


Feat/reloaded coop

thingy
the way i changed timer resuming after load is super jank, maybe better way?

Merged.


App should remember the last size and position

🤷🏽♂ Current Behaviour
When you start the app, it will always start with a portrait layout of the same size, even if you have resized when running it the last time. (Note that the initial dimensions don't make sense anyway, since a large part of the content is not visible, only the menu fits in.)
🎯 Expected Behaviour
Remember the size (and maybe the position) of the window from the previous run.
👟 Steps to Reproduce (S2R)
Start the app, resize the app, quit the app and then start the app again.
🏡 Environmental Context

App Version
v5.9.6
Installation Type
Deb package
Operating System
Ubuntu 17.04

Hi @atleta
This issue has been addressed in v6.1.6.
Looking forward to your feedback 😎.
Cheers, S


ros: 1.14.2-0 in 'lunar/distribution.yaml' [bloom]

Increasing version of package(s) in repository ros to 1.14.2-0:

upstream repository: https://github.com/ros/ros.git
release repository: https://github.com/ros-gbp/ros-release.git
distro file: lunar/distribution.yaml
bloom version: 0.6.1
previous version for package: 1.14.1-0

mk

No changes

rosbash

No changes

rosboost_cfg

No changes

rosbuild

No changes

rosclean

No changes

roscreate

No changes

roslang

No changes

roslib

No changes

rosmake

No changes

rosunit
* use python constants rather than hardcoded integers for error codes (#153 <https://github.com/ros/ros/issues/153>)

holding until lunar sync

sync is out.
Holding for synchronized release


Clarify OpenSSL version to install

Added clarity that v1.0.2u should be installed
Using a newer version may cause issues per https://github.com/ros2/ros2_documentation/issues/488
From OpenSSL website:

"OpenSSL 1.1.0 and later are quite different from previous releases"
"Version 1.0.2 is no longer supported"
long term we will need to address why v1.1.0 results in the issue linked above

@nbbrooks Can you make corresponding updates to the Dashing and Foxy installation instructions, for completeness?

@nbbrooks @mjcarroll Friendly ping. Can the other docs be updated?

FYI @nuclearsandwich (dashing) and @jacobperron (foxy)

Thanks Michael! I didn't realize the installation .mds for all versions lived in master, was thinking I'd need new PRs for foxy/dashing branches.


您好，不好意思打扰到您了，我想问一下数据集的问题

您在论文中只给出了一个数据集的地址，请问另外2个数据集的地址方便给出么？
另外两个数据集是Search advertising dataset 和 News feed advertising dataset

此外，我想问一下您，您在readme中介绍了Avito data 的处理方式，
Search advertising dataset 和 News feed advertising dataset 怎么处理呢？

Search and News feed advertising datasets are private industry datasets that cannot be released.
If you work in a company with an advertising department, you can collect your own ad data.
All these datasets can be processed using similar data processing pipeline:
https://github.com/oywtece/dstn/blob/master/data/README.md
If your original data contain the following two features: 1) search id or request id & 2) ad position, you can augment the original data with contextual ads.
If your original data contain the following two features: 3) user id & 4) time stamp, you can augment the original data with clicked and unclicked ads.
If your original data contain the aforementioned 4 features, you can augment the original data with contextual, clicked and unclicked ads.


ape of kitti00, 03-07 is bigger than that in paper

Thank you for your excellent work!
I have run this with kitti-stereo 00 - 07, but only ape of 01,02 is near that in paper.
I use https://github.com/MichaelGrupp/evo to get the ape.
Here is the compare between my test and paper.

Do I misunderstand something?

I have check the result with tum_rgbd evaluate_ate, the result is the same.


[feature] Containerize with docker for easier installing and testing

The project needs versions of nodejs, pnpm, and mysql installed.
My request  would be to containerize it:

users that prefer docker can run one command and have everything running with the right versions.
It would lower the barrier to contribution
Once containerized it would also make adding tests much easier, especially email tests, which are required to login and use most of the features (I would be happy to contribute those)

https://github.com/shadcn-ui/taxonomy/pull/266


SAK-33407 - Site Info should order Plugin tools

Has part of #4846 included, needs that merged first


Fixes case where modelObjects in an array wouldn't receive a scope if their parent is attached to a scope.

LGTM, should probably write some tests either here or in the future for childModelObjects accessor

Added test to test childModelObjects accessor.


🐞 - The text in the notification on the Android and iOS platforms is not aligned relative to the icon

Reproduction url
https://stackblitz.com/edit/angular-bjy2eq?file=src%2Fapp%2Fapp.template.html
Description
The text in the notification on the Android and iOS platforms is not aligned relative to the icon

Taiga UI version
4.11.1
Browser Used
Chrome
OS Used
macOS

Fixed in today's release


WACS crashes on Windows Server???

Why
Trying to run WACS on Windows Server 2019, create certificate
How
Attempting to run wacs.exe does shows a command prompt window that immediately closes, sometimes displays red text but too quick to read.
Documentation improvements
Please suggest which part of the documentation could be added or improved.

Try running it as an administrator, at least the first time, that will probably solve this issue. Should be fixed in the next release.


fix document error about how to call HashHistory

Hi,all:
I fix a document error about how to call HashHistory in document.
{new HashHistory} will cause an error when we use webpack, {new HashHistory({})} should be better.
97:30  error    Missing '()' invoking a constructor  new-parens

This error is being thrown by your eslint config. Try editing the value of your new-parens rule.


Running into Reached max simple mode retries issue

as provided after a certain amount of time I consistently get this error.
I have tried batch downloading these in smaller increments (as little as 50), as soon as I start the download I still run into this issue?
Some episodes seem to download but im missing a fair few and all give this error.

They're working for me. I believe it is just cloudflare being annoying, but am finishing that implementation when simple mode does fail. It will come alongside the m3u8 update

Would it be possible to add a export completed v selected file, which could then be added to the paste & start option to allow picking up from the last working download?
Manually selecting 300+ episodes is a challenge

Would it be possible to add a export completed v selected file, which could then be added to the paste & start option to allow picking up from the last working download?
Manually selecting 300+ episodes is a challenge

Oops i haven't been getting emails.
There's already a feature to select from point a to point b. All you do is hold the shift key and it will select everything from the first checked, to the last.

This should be fixed in 1.0.6
Let me know if the issue still happens.

Well at least it's a new error message.

 Well at least it's a new error message.

Can you go into the settings and turn on the debug messages?
Do that, only download 3 because the log would be huge or clear otherwise and post it here
I still believe it's cloudflare which I can't do much about, but it could be something else

I do believe it's a cloudflare issue, as by downloading the last episodes first it seems to be working without issue.
Maybe a stop gap for larger downloads being capped to 100episodes batches would be a better work around.
I think this would mitigate the other issues posted here if anime in excess of 200 episodes are capped to 100 episode batches.

Big Debug screen, yay.

I do believe it's a cloudflare issue, as by downloading the last episodes first it seems to be working without issue. Maybe a stop gap for larger downloads being capped to 100episodes batches would be a better work around.
I think this would mitigate the other issues posted here if anime in excess of 200 episodes are capped to 100 episode batches.

It seems to be a timeout issue on your end. Go into the settings and increase the timeout 10-30 seconds higher. Go even higher if the issue persists.
You have to factor in: your internet speed, your pc speed, the websites speed and cloudflare.
I'm not saying this program is 100# efficient (far from it), but it does get the job done under normal circumstances.

Would it be possible to add a export completed v selected file, which could then be added to the paste & start option to allow picking up from the last working download?
Manually selecting 300+ episodes is a challenge

Oops i haven't been getting emails. There's already a feature to select from point a to point b. All you do is hold the shift key and it will select everything from the first checked, to the last. This is inside the download confirm window.
Importing a huge list of urls isn't something I want to add. The primary focus is always going to be the database window.

Have you been able to get the shift mode to select the episodes between the checks? Mine goes into shift mode but doesnt select the episodes. It also doesnt bring up a window to confirm the between episodes. It just downloads the 2 with the check marks. I am sorry for all my issues lol

Would it be possible to add a export completed v selected file, which could then be added to the paste & start option to allow picking up from the last working download?
Manually selecting 300+ episodes is a challenge

Oops i haven't been getting emails. There's already a feature to select from point a to point b. All you do is hold the shift key and it will select everything from the first checked, to the last. This is inside the download confirm window.
Importing a huge list of urls isn't something I want to add. The primary focus is always going to be the database window.

Have you been able to get the shift mode to select the episodes between the checks? Mine goes into shift mode but doesnt select the episodes. It also doesnt bring up a window to confirm the between episodes. It just downloads the 2 with the check marks. I am sorry for all my issues lol

You hold shift and click the first episode you want to start from

Let go of shift and scroll down to where ever you want to multi select. Hold shift again, click the episode and let go of shift. Then press the "Select % Highlighted Episodes" button

Just wanted to say what I was doing wrong with the shift mode for others who may do the same thing. Dont click the checkmark box during shift mode. Just click the line the episode is on. Clicking the checkmark box doesnt allow it to highlight. That was my fault there.


Create generator function for display question

This is an optimization change recommended by Barak.
It lowers the memory usage by using a lazy-iterator.
fix #179
The changes are in the models.py and display question test file

I could not find information on how there is more reduced memory usage as you mentioned.
I will continue to search and check, I would love for you to update me on how the improvement here is being made once you will know.

I could not find information on how there is less memory usage in these cases as you mentioned.
I will continue to search and check, I would love for you to update me on how the improvement here is being made once you will know.

@avivz450  - Barak clarified this to me, the improvement of the memory utilization is noticeable mostly on a deployment env. where for example imagine the Django server is handling with thousands of users requests, and if at once many users will request this view, which will trigger the function and every function call will generate a list full of answers, then you might reach the max capacity of the memory available. When on the other end, the generator function will only return 1 answer at a time, so in this case the generator function is better.


conformance-data/LinearGradient

The gradient should be updated after navigation and/or zooming.

As a first solution, I tried to use the MutationObserver in index.js to re-add the gradients each time a navigation or zooming is detected (TO BE IMPLEMENTED)

click on show conformance data button

activity SRM subprocess is filled with LinearGradient (function createLinearGradient in src/conformance.js)

After navigating or zooming the diagram, the linearGradient disappears

After inspecting the html, I found that after navigation or zooming, the LinearGradient element is still there, but the fill property of the svg rect is reinitialized.
after navigation

As a first solution, I tried to use the MutationObserver in index.js to re-add the gradients each time a navigation or zooming is detected. I just added the code skeleton but didn't implemented it yet.

ℹ Same root cause as in https://github.com/process-analytics/icpm-demo-2022/issues/4#issuecomment-1228709866


Automate_projects.yml Action fails

The github action automate_projects.yml fails when submitting a new PR.
The step "add-new-pull-request-to-repository-based-project-column" fails.
Fix this Action (compare with other Compas repo).

The problem was that ORG_GITHUB_ACTION_SECRET expired.
I updated it it it fixes the problem.
See https://com-pas.github.io/contributing/ACCESS_TOKENS.html for token expiration date


Part 5 - Section II

Everything has been a sucess so far, but on the "Installing arm9loaderhax" part, the link in step 2 opens OTPHelper and there's no "Full Install" option like on step 3. I only get "Dump otp.bin (0x100), Dump otp.bin (0x108), validate otp.bin..."
What's wrong?
Thanks

You put the wrong arm11 and arm9 bin files in look at step six of part 5.
You must drag the arm9.bin and arm11.bin from the a9lhinstaller folder.
On Jul 25, 2016, at 10:03 PM, 3dsm <notifications<EMAIL_ADDRESS>wrote:
Everything has been a sucess so far, but on the "Installing arm9loaderhax" part, the link in step 2 opens OTPHelper and there's no "Full Install" option like on step 3. I only get "Dump otp.bin (0x100), Dump otp.bin (0x108), validate otp.bin..."
What's wrong?
Thanks

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Plailect/Guide/issues/260, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANJZLmL7wKwJ1vdDrGasgBXpxAd1QUwiks5qZWrqgaJpZM4JUt78.

I took the files from the "SAFEA9LHinstaller zip". Didnt supose to take from threre?

Inside the safe arm 9 loader hax zip there is a arm9.bin and arm11.bin replace it with the ones are your ad card.
You took the arm9 and arm11 files from OTPhelper witch you are not suppose to do.
On Jul 25, 2016, at 10:25 PM, 3dsm <notifications<EMAIL_ADDRESS>wrote:
I took the files from the "SAFEA9LHinstaller zip". Didnt supose to take from threre?

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/Plailect/Guide/issues/260#issuecomment-235144701, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANJZLuYFpqgfk3oTWFIcmcO3F3PnwD78ks5qZXAMgaJpZM4JUt78.


healthcare and human internal organs icon

It would be nice if icons that could be used in hospitals, pharmacies, or healthcare fields such as healthcare and human internal organs were added!
It would be nice if it could be used to express a disease or the department of a hospital.
thank you!
(This article was written with Google Translate, so it may be awkward.)

Thanks for the request! Added bone, tooth, stethoscope, dna, virus  in v2.0.0

We also already have pill, prescription, brain, face-mask, heart, heartbeat, syringe, and a number of first-aid icons.