angular 17 rc initial project with SSR throw NG04002

Which @angular/* package(s) are the source of the bug?
platform-server
Is this a regression?
Yes
Description
when you generate a new project, without changing a single file it will throw this NG04002 error in production
steps to reproduce
npx @angular/cli@next new ng-rc-0
cd ng-rc-0
ng b
node .\dist\ng-rc-0\server\server.mjs

and open localhost:4000
Please provide a link to a minimal reproduction of the bug
https://github.com/robertIsaac/ng-rc-0
Please provide the exception or error you saw
Node Express server listening on http://localhost:4000
ERROR Error: Uncaught (in promise): Error: NG04002
Error: NG04002
    at up.noMatchError (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72160)
    at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72834
    at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:16649
    at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:5513)
    at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
    at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
    at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
    at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
    at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
    at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
    at y (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:15945)
    at y (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:15480)
    at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:4:617
    at l.invokeTask (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:7209)
    at Object.onInvokeTask (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:10:38149)
    at l.invokeTask (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:7130)
    at B.runTask (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:2523)
    at b (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:9247) {
  rejection: J [Error]: NG04002
      at up.noMatchError (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72160)
      at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72834
      at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:16649
      at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:5513)
      at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
      at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
      at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
      at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
      at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
      at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842) {
    code: 4002
  },
  promise: E [Promise] {
    __zone_symbol__state: 0,
    __zone_symbol__value: J [Error]: NG04002
        at up.noMatchError (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72160)
        at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72834
        at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:16649
        at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:5513)
        at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
        at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
        at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
        at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
        at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
        at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842) {
      code: 4002
    }
  },
  zone: <ref *1> B {
    _parent: B {
      _parent: null,
      _name: '<root>',
      _properties: {},
      _zoneDelegate: [l]
    },
    _name: 'angular',
    _properties: { isAngularZone: true },
    _zoneDelegate: <ref *2> l {
      _taskCounts: [Object],
      zone: [Circular *1],
      _parentDelegate: [l],
      _forkZS: null,
      _forkDlgt: null,
      _forkCurrZone: null,
      _interceptZS: null,
      _interceptDlgt: null,
      _interceptCurrZone: null,
      _invokeZS: [Object],
      _invokeDlgt: [l],
      _invokeCurrZone: [Circular *1],
      _handleErrorZS: [Object],
      _handleErrorDlgt: [l],
      _handleErrorCurrZone: [Circular *1],
      _scheduleTaskZS: [Object],
      _scheduleTaskDlgt: [l],
      _scheduleTaskCurrZone: [Circular *1],
      _invokeTaskZS: [Object],
      _invokeTaskDlgt: [l],
      _invokeTaskCurrZone: [Circular *1],
      _cancelTaskZS: [Object],
      _cancelTaskDlgt: [l],
      _cancelTaskCurrZone: [Circular *1],
      _hasTaskZS: [Object],
      _hasTaskDlgt: [l],
      _hasTaskDlgtOwner: [Circular *2],
      _hasTaskCurrZone: [Circular *1]
    }
  },
  task: u {
    _zone: <ref *1> B {
      _parent: [B],
      _name: 'angular',
      _properties: [Object],
      _zoneDelegate: [l]
    },
    runCount: 0,
    _zoneDelegates: null,
    _state: 'notScheduled',
    type: 'microTask',
    source: 'Promise.then',
    data: E [Promise] { __zone_symbol__state: 0, __zone_symbol__value: [J] },
    scheduleFn: undefined,
    cancelFn: undefined,
    callback: [Function (anonymous)],
    invoke: [Function (anonymous)]
  }
}
ERROR Error: Uncaught (in promise): Error: NG04002
Error: NG04002
    at up.noMatchError (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72160)
    at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72834
    at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:16649
    at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:5513)
    at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
    at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
    at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
    at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
    at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
    at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
    at y (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:15945)
    at y (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:15480)
    at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:4:617
    at l.invokeTask (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:7209)
    at Object.onInvokeTask (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:10:38149)
    at l.invokeTask (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:7130)
    at B.runTask (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:2523)
    at b (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:9247) {
  rejection: J [Error]: NG04002
      at up.noMatchError (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72160)
      at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72834
      at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:16649
      at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:5513)
      at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
      at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
      at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
      at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
      at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
      at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842) {
    code: 4002
  },
  promise: E [Promise] {
    __zone_symbol__state: 0,
    __zone_symbol__value: J [Error]: NG04002
        at up.noMatchError (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72160)
        at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72834
        at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:16649
        at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:5513)
        at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
        at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
        at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
        at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
        at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
        at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842) {
      code: 4002
    }
  },
  zone: <ref *1> B {
    _parent: B {
      _parent: null,
      _name: '<root>',
      _properties: {},
      _zoneDelegate: [l]
    },
    _name: 'angular',
    _properties: { isAngularZone: true },
    _zoneDelegate: <ref *2> l {
      _taskCounts: [Object],
      zone: [Circular *1],
      _parentDelegate: [l],
      _forkZS: null,
      _forkDlgt: null,
      _forkCurrZone: null,
      _interceptZS: null,
      _interceptDlgt: null,
      _interceptCurrZone: null,
      _invokeZS: [Object],
      _invokeDlgt: [l],
      _invokeCurrZone: [Circular *1],
      _handleErrorZS: [Object],
      _handleErrorDlgt: [l],
      _handleErrorCurrZone: [Circular *1],
      _scheduleTaskZS: [Object],
      _scheduleTaskDlgt: [l],
      _scheduleTaskCurrZone: [Circular *1],
      _invokeTaskZS: [Object],
      _invokeTaskDlgt: [l],
      _invokeTaskCurrZone: [Circular *1],
      _cancelTaskZS: [Object],
      _cancelTaskDlgt: [l],
      _cancelTaskCurrZone: [Circular *1],
      _hasTaskZS: [Object],
      _hasTaskDlgt: [l],
      _hasTaskDlgtOwner: [Circular *2],
      _hasTaskCurrZone: [Circular *1]
    }
  },
  task: u {
    _zone: <ref *1> B {
      _parent: [B],
      _name: 'angular',
      _properties: [Object],
      _zoneDelegate: [l]
    },
    runCount: 0,
    _zoneDelegates: null,
    _state: 'notScheduled',
    type: 'microTask',
    source: 'Promise.then',
    data: E [Promise] { __zone_symbol__state: 0, __zone_symbol__value: [J] },
    scheduleFn: undefined,
    cancelFn: undefined,
    callback: [Function (anonymous)],
    invoke: [Function (anonymous)]
  }
}
ERROR Error: Uncaught (in promise): Error: NG04002
Error: NG04002
    at up.noMatchError (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72160)
    at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72834
    at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:16649
    at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:5513)
    at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
    at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
    at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
    at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
    at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
    at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
    at y (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:15945)
    at y (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:15480)
    at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:4:617
    at l.invokeTask (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:7209)
    at Object.onInvokeTask (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:10:38149)
    at l.invokeTask (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:7130)
    at B.runTask (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:2523)
    at b (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:3:9247) {
  rejection: J [Error]: NG04002
      at up.noMatchError (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72160)
      at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72834
      at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:16649
      at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:5513)
      at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
      at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
      at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
      at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
      at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
      at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842) {
    code: 4002
  },
  promise: E [Promise] {
    __zone_symbol__state: 0,
    __zone_symbol__value: J [Error]: NG04002
        at up.noMatchError (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72160)
        at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:45:72834
        at file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:16649
        at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:5513)
        at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
        at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
        at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
        at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842)
        at Pu.error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2602)
        at Pu._error (file:///C:/Users/rober/test/ng-rc-0/dist/ng-rc-0/server/chunk-NL6MILSZ.mjs:6:2842) {
      code: 4002
    }
  },
  zone: <ref *1> B {
    _parent: B {
      _parent: null,
      _name: '<root>',
      _properties: {},
      _zoneDelegate: [l]
    },
    _name: 'angular',
    _properties: { isAngularZone: true },
    _zoneDelegate: <ref *2> l {
      _taskCounts: [Object],
      zone: [Circular *1],
      _parentDelegate: [l],
      _forkZS: null,
      _forkDlgt: null,
      _forkCurrZone: null,
      _interceptZS: null,
      _interceptDlgt: null,
      _interceptCurrZone: null,
      _invokeZS: [Object],
      _invokeDlgt: [l],
      _invokeCurrZone: [Circular *1],
      _handleErrorZS: [Object],
      _handleErrorDlgt: [l],
      _handleErrorCurrZone: [Circular *1],
      _scheduleTaskZS: [Object],
      _scheduleTaskDlgt: [l],
      _scheduleTaskCurrZone: [Circular *1],
      _invokeTaskZS: [Object],
      _invokeTaskDlgt: [l],
      _invokeTaskCurrZone: [Circular *1],
      _cancelTaskZS: [Object],
      _cancelTaskDlgt: [l],
      _cancelTaskCurrZone: [Circular *1],
      _hasTaskZS: [Object],
      _hasTaskDlgt: [l],
      _hasTaskDlgtOwner: [Circular *2],
      _hasTaskCurrZone: [Circular *1]
    }
  },
  task: u {
    _zone: <ref *1> B {
      _parent: [B],
      _name: 'angular',
      _properties: [Object],
      _zoneDelegate: [l]
    },
    runCount: 0,
    _zoneDelegates: null,
    _state: 'notScheduled',
    type: 'microTask',
    source: 'Promise.then',
    data: E [Promise] { __zone_symbol__state: 0, __zone_symbol__value: [J] },
    scheduleFn: undefined,
    cancelFn: undefined,
    callback: [Function (anonymous)],
    invoke: [Function (anonymous)]
  }
}

Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 17.0.0-rc.0
Node: 18.16.0
Package Manager: npm 9.6.7
OS: win32 x64

Angular: 17.0.0-rc.0
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router, ssr

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1700.0-rc.0
@angular-devkit/build-angular   17.0.0-rc.0
@angular-devkit/core            17.0.0-rc.0
@angular-devkit/schematics      17.0.0-rc.0
@schematics/angular             17.0.0-rc.0
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.0

Anything else?
the same issue exist in angular 16.2.10 if you migrate to the application builder manually

Transferring to CLI repo. The issue here is that the skeleton app provides the router but does not have any routes so the initial navigation fails to match any routes.

@robertIsaac, I am not able to replicate this using the reproduction provided. Can you run the the build in dev mode and report back with the error message that has the url segment?

In dev it doesn't error

@robertIsaac, that is even stranger.
Unfortunately, I am still unable to replicate it both prod and dev mode.
Those this happen in incognito mode?

This error is throwing in the server not the browser
So it doesn't matter what triggered it
I will test it from another machine now

It's even stranger
From another machine it doesn't happen
I installed the same npm and node version
It still doesn't happen
The only difference is the OS
it's working on windows 10 but not 11

@robertIsaac, that is even stranger. Unfortunately, I am still unable to replicate it both prod and dev mode.
Those this happen in incognito mode?

I tried it and surprise if I opened it from incognito it doesn't reproduce the error
it only reproduce the error when I open it from normal chrome tab
but the error is in the server, it doesn't make any sense to me
but after I cleared the localhost data, it doesn't throw the errors now
it's up to you to keep the issue or close it

Haha, this actually makes a lot of sense to me and that is why I suggested to use Incognito.
What was likely happening is that you has a service-worker registered for localhost:4000 which was sending requests to the server for unknown routes. This cause errors on the server as the route does not exists.

Haha, this actually makes a lot of sense to me and that is why I suggested to use Incognito  😀.
What was likely happening is that you had a service-worker registered for localhost:4000 which was sending requests to the server for unknown routes. This cause errors on the server as the route does not exists.

that's very interesting, is there any documentation for this behavior of the service worker?
because I don't understand why these requests were made and this confuses me a lot

I might not even be the Angular service-worker. You might have had any service worker registered on localhost:4000 and upon accessing localhost:4000 it was trying to sync or do something.
Since know you are unable to replicate it, it not something that you can now check debug.


How to set milisec?

Let's say I have a date:
10.10.2018 12:02:16.024
and I want to update milisec value to 7, so my result should looks like this:
10.10.2018 12:02:16.007
I tried to use:
date.dateBySet([.nanosecond: 7])
without success
Is is a bug? Lack of functionality? I can't find proper method. Can you help me?
For now I created Date extension as a workaround:
func set(milisec: Int) -> Date {
    var timestamp = timeIntervalSince1970.rounded(.down)
    timestamp += Double(milisec) / 1000.0

    return Date(timeIntervalSince1970: timestamp)
}

Hi,
Since 5.0.12 both Date and DateInRegion dateBySet() function has an extra ms optional parameter you can use to set the milliseconds value of the receiver.
let originalDate = "2018-10-10T12:02:16.024".toISODate()!
let newDate = originalDate.dateBySet(hour: nil, min: nil, secs: nil, ms: 7)
print(newDate.toISO()) // 2018-10-10T12:02:16.007Z


[FYI] quick hack for switching to nan-2.0.9 for node-4.0

I made a quick patch for updating to nan-2.0.9 for running on nodejs-4
"npm test" not passed, but the ursa module works as

ursa.generatePrivateKey
priv.toPublicPem
ursa.createPublicKey
pub.encrypt
priv.decrypt

So from a quick search i think there might be a solution to the travis build errors: https://github.com/travis-ci/travis-ci/issues/4771
just add the env config:
env:
  - CXX=g++-4.8

to your travis.yml file

Thanks! I'm going to merge this in, and when I find some time figure out the travis stuff :)


Update nodemon.json

I excluded webpack.config.prod.js from nodemon.json because it doesn't need to be watched in dev mod.
Sometimes it's annoying that the server restarted when I updated webpack.config.prod.js

@ZeroCho Thanks! This makes sense. Merging!


steptypeservice only support one layer of service definition

steptypeservice can't embed another service in current implementation

repeat data refresh needs to be applied on stepTypeService


Transforms are not being applied on server side

Curiously transforms are not working on server site. I can see on the request payload that transforms are working fine on client side but when it gets to the serve they are ignored. I don't see why we want to have transforms on the client though. If I just transform a string to number on the client side, it should throw an error on the server since the validation would need a string instead of a number.

Hey, @wladiston!
I just ran a test with your code and it seems to be working for me. Let me check if I understand the idea: if I type 1234,56 on the field, values inside your mutation should be { values: 123456 }? That's what I'm getting.

Correct, yeap, I actually forgot to close this cause I got it working


⚠ ClamAV has degraded performance

In a04eea1, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 72 ms

Resolved: ClamAV performance has improved in c1aec72.


Maximum call stack exceeded in one-to-many association

I have a strange error while moving app to production:
MY_PROJECT_DIR/node_modules/sails-mongo/node_modules/waterline-cursor/cursor/buffer.js:47
  values.forEach(function(val) {
         ^
RangeError: Maximum call stack size exceeded

I decided to trace where it may come from. Added a console.log right before this 47 line in buffer.js:
console.log('SAILS DEBUG ' + JSON.stringify(values));

It showed me this:
SAILS DEBUG [{"attrName":"subscriptions","parentPK":"5467303cb1ca0e377777051d","pkAttr":"id","keyName":"subscriptions"}]
SAILS DEBUG [{"attrName":"subscriptions","parentPK":"5467303cb1ca0e377777051e","pkAttr":"id","keyName":"subscriptions"}]
SAILS DEBUG [{"attrName":"subscriptions","parentPK":"5467303cb1ca0e377777051f","pkAttr":"id","keyName":"subscriptions"}]
SAILS DEBUG [{"attrName":"subscriptions","parentPK":"5467303cb1ca0e3777770520","pkAttr":"id","keyName":"subscriptions"}]
2014-11-15T14:40:00.874Z - verbose: Lowering sails...
2014-11-15T14:40:00.874Z - verbose: Sent kill signal to child process (2871)...
2014-11-15T14:40:00.879Z - verbose: Shutting down socket server...

util.js:35
  var str = String(f).replace(formatRegExp, function(x) {
                      ^
RangeError: Maximum call stack size exceeded

It's look like Sails is having troubles with adding one-to-many association to the User model . The model attribute looks like this:
attributes: {
    ...
    subscriptions: {
      collection: 'subscription',
      via: 'user'
    },
    ...
}

When I removed the user collection from MongoDB problem disappeared. On smaller collections there were no problems like this. The size of collection Sails crushes on is 10913.

Thanks!  Move conversation to https://github.com/balderdashy/waterline-cursor/issues/3 .


about code

thank you for nice work. when would you release the codes?

非常感谢你关注这项工作
目前代码还没来得及整理，如果需要的话，以下是代码实现的一些基本信息：
这项工作的模型训练是基于 BasicSR框架：
[BasicSR](https://github.com/XPixelGroup/BasicSR) 得益于[XPixelGroup](https://github.com/XPixelGroup) 的杰出贡献。
关于MHDLSA的实现是基于以下工作:
On the Connection between Local Attention and Dynamic Depth-wise Convolution [paper](https://arxiv.org/abs/2106.04263) [github](https://github.com/Atten4Vis/DemystifyLocalViT)
SparseGSA的实现是基于以下工作:
Restormer: Efficient Transformer for High-Resolution Image Restoration [paper](https://arxiv.org/abs/2111.09881) [github](https://github.com/swz30/Restormer)
Improving Image Restoration by Revisiting Global Information Aggregation [paper](https://arxiv.org/abs/2112.04491) [github](https://github.com/megvii-research/TLC)
We sincerely appreciate your interest in our efforts.
We haven't had chance to organize the code as of yet. The following is some fundamental knowledge about how the code is implemented, should it be needed:
The foundation for the training process is [BasicSR](https://github.com/XPixelGroup/BasicSR) , which profited from the outstanding contribution of [XPixelGroup](https://github.com/XPixelGroup) .
The following research forms the foundation for the MHDLSA implementation:
On the Connection between Local Attention and Dynamic Depth-wise Convolution [paper](https://arxiv.org/abs/2106.04263) [github](https://github.com/Atten4Vis/DemystifyLocalViT)
And the following research forms the foundation for the Sparse implementation:
Restormer: Efficient Transformer for High-Resolution Image Restoration [paper](https://arxiv.org/abs/2111.09881) [github](https://github.com/swz30/Restormer)
Improving Image Restoration by Revisiting Global Information Aggregation [paper](https://arxiv.org/abs/2112.04491) [github](https://github.com/megvii-research/TLC)

非常感谢你关注这项工作
目前代码还没来得及整理，如果需要的话，以下是代码实现的一些基本信息：
这项工作的模型训练是基于 BasicSR框架： [BasicSR](https://github.com/XPixelGroup/BasicSR) 得益于[XPixelGroup](https://github.com/XPixelGroup) 的杰出贡献。
关于MHDLSA的实现是基于以下工作:
On the Connection between Local Attention and Dynamic Depth-wise Convolution [paper](https://arxiv.org/abs/2106.04263) [github](https://github.com/Atten4Vis/DemystifyLocalViT)
SparseGSA的实现是基于以下工作:
Restormer: Efficient Transformer for High-Resolution Image Restoration [paper](https://arxiv.org/abs/2111.09881) [github](https://github.com/swz30/Restormer)
Improving Image Restoration by Revisiting Global Information Aggregation [paper](https://arxiv.org/abs/2112.04491) [github](https://github.com/megvii-research/TLC)
We sincerely appreciate your interest in our efforts.
We haven't had chance to organize the code as of yet. The following is some fundamental knowledge about how the code is implemented, should it be needed:
The foundation for the training process is [BasicSR](https://github.com/XPixelGroup/BasicSR) , which profited from the outstanding contribution of [XPixelGroup](https://github.com/XPixelGroup) .
The following research forms the foundation for the MHDLSA implementation:
On the Connection between Local Attention and Dynamic Depth-wise Convolution [paper](https://arxiv.org/abs/2106.04263) [github](https://github.com/Atten4Vis/DemystifyLocalViT)
And the following research forms the foundation for the SparseGSA implementation:
Restormer: Efficient Transformer for High-Resolution Image Restoration [paper](https://arxiv.org/abs/2111.09881) [github](https://github.com/swz30/Restormer)
Improving Image Restoration by Revisiting Global Information Aggregation [paper](https://arxiv.org/abs/2112.04491) [github](https://github.com/megvii-research/TLC)

谢谢您分享的教程。❤


Test: JS Heap Snapshots viewer

Refs: https://github.com/microsoft/vscode/issues/191920

[ ] anyOS @eleanorjboyd
[x] anyOS @aiday-mar

Complexity: 3
Create Issue

This month I added a custom editor to allow viewing JavaScript heap snapshots.

Debug any JavaScript, and run Take Performance Profile > Heap Snapshot. That will collect a .heapsnapshot file into your workspace folder. (Doing this in browsers is fairly fast, but Node is slow and can take several moments)
Open the file. Poke around the table view and check that things are sane and work as they should. The numbers should match the same file opened in the Memory tab in Chrome (not Edge, Edge tweaks Chrome's calculation)
Click on the "graph" button beside a node and see that it opens a graph of its retaininers. You will be prompted to install the flame chart visualizer if not installed, as it contains the heavier-weight graphing components.
Check that graph navigation is sane and works well. You can change the distance of displayed retaininers, but be warned that high numbers may take increasing amounts of time to chart, especially for Node.js profiles.

Loving the graphic functionality ^^

Thank you for the thorough testing :)

The julia language Profile stdlib provides a way to record .heapsnapshot files that can be viewed in chrome devtools, but they hang indefinitely in this viewer and print the following error
2023-12-30 19:27:38.621 [info] ExtensionService#_doActivateExtension ms-vscode.vscode-js-profile-table, startup: false, activationEvent: 'onCustomEditor:jsProfileVisualizer.heapsnapshot.table'
2023-12-30 19:27:38.772 [error] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "invalid profile JSON".

Is there any way to get any further debug information?
Here is a zipped example 81416_881767189633791.heapsnapshot.zip
I thought I wouldn't open a dedicated issue until we can rule out the issue being on the julia side


Enums with string conversion do not become required (non-nullable) in model snapshot

When enum property is configured like
t.Property(p => p.Enum).HasConversion<string>()

the valid migration is scaffolded
migrationBuilder.CreateTable(
                name: "TableName",
                columns: table => new
                {
                    Enum = table.Column<string>(nullable: false)
                },
...);

But when it goes to updating the model snapshot it missed ".IsRequired()" modifier on that column. So the next migration looks like the following
migrationBuilder.AlterColumn<string>(
                name: "Enum",
                table: "TableName",
                nullable: false,
                oldClrType: typeof(string),
                oldNullable: true);

Even if you append ".IsRequired()" manually to the snapshot, on the next migration scaffolding it will be deleted and the subsequent migrations will have that  redundant "AlterColumn ... nullable: false ... oldNullable: true".
Further technical details
EF Core version: 2.1.0-preview2-final
EF Core Tools version: 2.1.0-preview2-final
EF Core Tools.DotNet version: 2.1.0-preview1-final
Database Provider: Npgsql.EntityFrameworkCore.PostgreSQL

Duplicate of #11343
Fixed in the nightly builds of 2.1.


Include used invite_link in supergroup, identical to private groups

Currently, when new members join a private group using an invite link, the link they used is listed under update.chat_member.invite_link.
However, if the group is a supergroup, this attribute is not passed on.
Expected behavior:
update.chat_member.invite_link should be present with the used invite link regardless if the group is a supergroup or private.

If new member joins a public group using an invite link, then the invite link is also included in the update. You can check this by using joinChatByInviteLink request from TDLib. It is a specific app, which directly joins the public group, instead of joining it via invite link.

Resolved here


EmrEtlRunner: fail fast in build script

set -e

Failing tests don't cancel deploy currently.

@chuwy heads up I renamed the ticket

Got it!


Qt translations

At the moment some parts of qt/locale/*.* are broken. The proper way to fix these gaps would be establishing transifex.com account.

https://www.transifex.com/axecore/public/


Change SealedTx to have dual representations, stub signTx endpoint

This improves the SealedTx type so that it can be used in either bytestring or Cardano.Tx form, whichever is more convenient.
Comments
A couple tests needed to be disabled for this change to be separated from PR #2754, but they will be put back in a later PR.
Based on the PR #2895 branch - merge that first.
Issue Number
ADP-919

bors r+

Added weeder roots for temporarily unused functions.
bors r+


Add Chrome, Edge, and Edge Dev on Windows

Adds exporting from Chrome, Edge, and Edge's Dev prerelease builds on Windows.

Hey, looks good :+1: , didnt know expandvars could handle the localappdata on windows
could you update the list of browsers in the readme and link to the edge/edge dev websites (Im not sure if edge dev is just the dev channel or something else?)

will push a new version tonight

Thanks! Yeah Edge Dev is just a prerelease channel (the one I use most often). I was pleasantly surprised that I didn't have to jump through hoops to resolve %LocalAppData% properly.
I have a few other browsers on another machine, I might throw another PR out with the rest of the paths for Windows just out of principle 😁.

That would be great, thanks!


Fix MPI PETSc error when run by Travis

Attempting to fix issue #64

I cannot reliably reproduce this error. For now I can only move forward without using Travis to test MPI.


Incorrect Parent Folder Name When Moving Folders

Description
I have encountered a potential issue when using the telescope-file-browser.nvim plugin. When I mark a folder for moving, navigate to another folder, and then press Alt + m to move the marked folder, the moved folder's name becomes the parent of the desired folder instead of retaining its original name.
Neovim version
NVIM v0.9.4
Build type: Release
LuaJIT 2.1.1692716794

Operating system and version
Debian12
Steps to reproduce
Open the telescope-file-browser.nvim file browser.
Mark a folder for moving (e.g., using Tab).
Navigate to another folder.
Press Alt + m(insert mode) or m (normal mode) to move the marked folder.

Expected behavior
I expect the marked folder to be moved to the current location, the moved folder should be keep its original name.
Actual behavior
The moved folder's name becomes the parent of the desired folder.
Minimal config
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  {
    "nvim-telescope/telescope-file-browser.nvim",
    dependencies = {
      "nvim-telescope/telescope.nvim",
      "nvim-lua/plenary.nvim",
    },
    config = function()
      require("telescope").setup({})
      require("telescope").load_extension("file_browser")
    end,
  },
}

require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

I believe this was fixed not too long ago.
https://github.com/nvim-telescope/telescope-file-browser.nvim/pull/344
Can you update telescope-file-browser and see if the issue still persists?

Hi @jamestrew,
Thanks for investigating the issue. I wanted to let you know that I've updated the telescope-file-browser plugin, and you can verify the changes in the Git log below: `~/.local/share/nvim/lazy/telescope-file-browser.nvim$ git log --oneline --graph

6dd6522 (HEAD -> master, origin/master, origin/HEAD) fix(git): show status for git submodules (#356)

6f735a6 chore: format minimal config (#355)

ee7e5aa chore: update bug report minimal config to use lazy (#354)

4bd5657 fix(action): prevent collapse_dirs from trying to open file (#351)
*** 8e05433 fix(action.move): moving folders (#344)**

afb612a Revert "fix(action.move): moving folders (#342)" (#343)
 However, I regret to inform you that the issue is not yet resolved on my end. If you have any insights or suggestions, I would greatly appreciate your assistance. I use lazyvim, and this is my configuration for telescope-file-browser:return {
"nvim-telescope/telescope-file-browser.nvim",
dependencies = {
"nvim-telescope/telescope.nvim",
"nvim-lua/plenary.nvim",
},
keys = {
{
"v",
":Telescope file_browser path=%:p:h select_buffer=true",
desc = "Browse Files",
},
},
config = function()
require("telescope").load_extension("file_browser")
-- Apply the settings to Telescope
require("telescope").setup({
results_prompt = true,
extensions = {
file_browser = {
hidden = true,     -- Show hidden files
no_ignore = false, --false: see gitignore files, true to ignore them
grouped = true,    -- Group directories first
},
},
defaults = {
path_display = { "absolute" }, -- Use absolute paths in the file browser
previewer = true,
initial_mode = "insert",
--layout_config = { height = 40 }
},
})
end,
}
`

Can you provide more details on how to reproduce this.
I've tried precisely this

Open the telescope-file-browser.nvim file browser.
Mark a folder for moving (e.g., using Tab).
Navigate to another folder.
Press Alt + m(insert mode) or m (normal mode) to move the marked folder.

with the minimal config and I'm not getting any strange behaviors.
https://github.com/nvim-telescope/telescope-file-browser.nvim/assets/66286082/e964ab0f-1b4d-4436-a8a8-4f8dd52be727

I hope this message finds you well. I wanted to update you on the situation regarding the issue we discussed. I attempted to resolve it by cleaning up my Neovim configurations using the following steps:
rm -rf ~/.config/nvim ~/.local/share/nvim ~/.local/state/nvim ~/.cache/nvim

Afterwards, I created a new ~/.config/nvim/init.lua from here file with the following content:
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "https://github.com/folke/lazy.nvim.git",
    "--branch=stable", -- latest stable release
    lazypath,
  })
end
vim.opt.rtp:prepend(lazypath)

and another ~/.config/nvim/min.lua
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  {
    "nvim-telescope/telescope-file-browser.nvim",
    dependencies = {
      "nvim-telescope/telescope.nvim",
      "nvim-lua/plenary.nvim",
    },
    config = function()
      require("telescope").setup({})
      require("telescope").load_extension("file_browser")
    end,
  },
}

require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

I then tested the setup using:
~/.config/nvim$ nvim -u min.lua

https://github.com/nvim-telescope/telescope-file-browser.nvim/assets/16093179/4bef844a-766c-4570-a4a9-200fec33f81d
However, it did not work as expected. If you have any insights or suggestions on how to resolve this, I would greatly appreciate your assistance.
Thank you for your time and help.

I'm sorry. I tried to follow exactly your steps, even downgraded to neovim v0.9.4 but I'm still not able to replicate this issue.
Without the ability to replicate this, I'm not able to debug what is causing this issue for you.

Thank you for your continued efforts in trying to help me resolve this issue. I've done some tracking down on my end, and it seems that the problem might be related to the line:
local new_path_absolute = new_path:absolute()
which is part of the fb_actions.move function in the file "lua/telescope/_extensions/file_browser/actions.lua" . This line is giving unexpected results for me. For example, when I attempt to move "folder1" into "folder2," the result is something like "parent_of_folder1/folder2/parent_of_folder1," which is not the expected behavior. I hope this information helps in identifying the root cause of the issue.

Interesting.
If you can, can you put
      vim.print {
        selection = old_path_absolute,
        basename = basename,
        target_dir = target_dir,
        new_path = new_path_absolute,
      }

below that line

local new_path_absolute = new_path:absolute()

then repeat the reproduction steps and share the results?
I don't think it's the new_path:absolute() that's the issue but something before that.

Thanks for your suggestion. I've added the debug print statements below the line:
{
  basename = "parent_of_folder1",
 new_path = "/home/m/parent_of_folder1/folder2/parent_of_folder1",
 selection = "/home/m/parent_of_folder1",
 target_dir = "/home/m/parent_of_folder1/folder2"
}

before :
 m@debian:  ~/parent_of_folder1$ tree

├──   folder1
└──   folder2
moving folder1 into folder2
after:
m@debian:~/parent_of_folder1$ tree
.
└── folder2
      └── parent_of_folder1

...
if new_path:exists() then
  table.insert(skipped, basename)
else
  local new_path_absolute = new_path:absolute()

  vim.print {
    selection = old_path_absolute,
    basename = basename,
    target_dir = target_dir,
    new_path = new_path_absolute,
  }
  selection:rename {
    new_name = new_path_absolute,
  }
...

Wow. I'm thoroughly confused.
Does using <tab> to select and delete directories work as expected?
If it does and you're willing, can you try adding a couple of print statements a few lines higher?
  local target_dir = get_target_dir(finder)
  local moved = {}
  local skipped = {}

  for idx, selection in ipairs(selections) do
    local old_path_absolute = selection:absolute()
    print(old_path_absolute)
    if vim.fn.isdirectory(old_path_absolute) == 1 then
      old_path_absolute = vim.fs.dirname(old_path_absolute)
    end
    local basename = vim.fs.basename(old_path_absolute)
    print(basename, old_path_absolute)

And just to double check, nothing but the print statements should be different here.

I've confirmed that using  to select, delete, and copy directories works as expected. However, I've also tested this in WSL Ubuntu on Windows 10, and I'm encountering the same unexpected results when moving directories.
/home/m/parent_of_folder1/folder1
nil /home/m/parent_of_folder1
[file_browser.actions.move] Moved: parent_of_folder1

before :
 m@debian:  ~/parent_of_folder1$ tree

├──   folder1
└──   folder2
moving folder1 into folder2
after:
m@debian:~/parent_of_folder1$ tree
.
└── folder2
      └── parent_of_folder1

  for idx, selection in ipairs(selections) do
    local old_path_absolute = selection:absolute()
    print(old_path_absolute)
    if vim.fn.isdirectory(old_path_absolute) == 1 then
      old_path_absolute = vim.fs.dirname(old_path_absolute)
    end
    print(basename, old_path_absolute)
    local basename = vim.fs.basename(old_path_absolute)
    local new_path = Path:new { target_dir, basename }
    if new_path:exists() then
      table.insert(skipped, basename)

Ohhh I see what the issue is and why I couldn't reproduce it.
You're not using fd, am I correct? I'm able to reproduce this when I disable the use of fd.
I'll work on a fix for this. Thanks for helping me debug this.

@FadeDreams If you can try out the linked PR, that would be great.

You're correct; I haven't installed fd. However, I tested the linked PR 358, and it worked for me in the situation even without installing fd. Thanks for your quick response and efforts to fix the issue!


[Rust Shell] Implement a few dot commands

partially satisfies #142

hii @psarna, I think PR this is ready to review


Colored output

I just started with implementing #7.
Right now it only does automatic detection and colouring, and I made the header row bold to make it more distinctive.
Still needs the flag, so don't merge yet.

Ok, the color flag was also simple to add.
@BurntSushi ready for review.

@BurntSushi: Do you have time to review this? It's a small diff..

@BurntSushi: Since I have your attention, can you review this PR too? It's a tiny change :)

Let's do it. Thanks!


Rancher Errors with Deploying Monitoring Charts to Cluster

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Enable cluster monitoring

Result:
The internal JIT tiller throws a bunch of errors about credentials being required for config maps it seems?
Other details that may be helpful:
Other catalog entries from the Library do not seem to be affected, I was able to install redis and mysql without issue.
Logs:
[main] 2019/03/07 03:32:49 Starting Tiller v2.10+unreleased (tls=false)
[main] 2019/03/07 03:32:49 GRPC listening on :49213
[main] 2019/03/07 03:32:49 Probes listening on :42696
[main] 2019/03/07 03:32:49 Storage driver is ConfigMap
[main] 2019/03/07 03:32:49 Max history per release is 0
[tiller] 2019/03/07 03:32:49 getting history for release monitoring-operator
[storage] 2019/03/07 03:32:49 getting release history for "monitoring-operator"
[storage/driver] 2019/03/07 03:32:49 query: failed to query with labels: the server has asked for the client to provide credentials (get configmaps)
[tiller] 2019/03/07 03:32:49 getting history for release cluster-monitoring
[storage] 2019/03/07 03:32:49 getting release history for "cluster-monitoring"
[storage/driver] 2019/03/07 03:32:49 query: failed to query with labels: the server has asked for the client to provide credentials (get configmaps)
[tiller] 2019/03/07 03:32:49 preparing update for monitoring-operator
[storage] 2019/03/07 03:32:49 getting deployed releases from "monitoring-operator" history
[storage/driver] 2019/03/07 03:32:49 query: failed to query with labels: the server has asked for the client to provide credentials (get configmaps)
2019/03/07 03:32:49 [ERROR] AppController p-kctht/monitoring-operator [helm-controller] failed with : failed to install app monitoring-operator. Error: UPGRADE FAILED: the server has asked for the client to provide credentials (get configmaps)

[tiller] 2019/03/07 03:32:49 preparing update for cluster-monitoring
[storage] 2019/03/07 03:32:49 getting deployed releases from "cluster-monitoring" history
[storage/driver] 2019/03/07 03:32:49 query: failed to query with labels: the server has asked for the client to provide credentials (get configmaps)
2019/03/07 03:32:49 [ERROR] AppController p-kctht/cluster-monitoring [helm-controller] failed with : failed to install app cluster-monitoring. Error: UPGRADE FAILED: the server has asked for the client to provide credentials (get configmaps)

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.2.0-rc3
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Imported
Machine type (cloud/VM/metal) and specifications (CPU/memory): Metal 4core/16gb
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-03-01T23:34:27Z", GoVersion:"go1.12", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.3", GitCommit:"435f92c719f279a3a67808c80521ea17d5715c66", GitTreeState:"clean", BuildDate:"2018-11-26T12:46:57Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

@ekristen , I have no idea about this error. It seems tiller cannot get configmap from API server, as it doesn't provide any credentials in the process. Do you have any other progress?

Nope it just sits on this error and repeats. Unfortunate the JIT tiller spins up, throws the error, tearsdown and repeats and spams the logs a lot.
What troubleshooting data can I provide?

It seems like based on Google, this is an error with how tiller is started. For some reason it does not have the correct permissions to access the namespace it's requesting.

Ok I found the root cause.
If you deactivate the default admin, this fails to deploy because it uses a token generated by the default user.
The default user should be able to be deactivated or deleted ... so should there be a system user that gets created that can't be modified by the end user?

Close in favor of https://github.com/rancher/rancher/issues/18787

@ekristen I'm having this same problem when Rancher starts up. How did you reactive your default user? FOr me, I can't access Rancher.


Warnings while parsing netlify.toml file

- Do you want to request a feature or report a bug?
Report a bug.
- What is the current behavior?
Running "netlify dev" with a local netlify.toml file that includes a [[redirects]] section results in a runtime error.
Warnings while parsing netlify.toml file:
TypeError: Cannot convert object to primitive value
    at ~/.nvm/versions/node/v12.16.3/lib/node_modules/netlify-cli/src/utils/rules-proxy.js:15:46
    at Array.forEach (<anonymous>)
    at parseFile (~/.nvm/versions/node/v12.16.3/lib/node_modules/netlify-cli/src/utils/rules-proxy.js:14:19)
    at async parseRules (~/.nvm/versions/node/v12.16.3/lib/node_modules/netlify-cli/src/utils/rules-proxy.js:31:22)
    at async createRewriter (~/.nvm/versions/node/v12.16.3/lib/node_modules/netlify-cli/src/utils/rules-proxy.js:68:15)
    at async startProxy (~/.nvm/versions/node/v12.16.3/lib/node_modules/netlify-cli/src/commands/dev/index.js:179:20)
    at async DevCommand.run (~/.nvm/versions/node/v12.16.3/lib/node_modules/netlify-cli/src/commands/dev/index.js:449:19)
    at async DevCommand._run (~/.nvm/versions/node/v12.16.3/lib/node_modules/netlify-cli/node_modules/@oclif/command/lib/command.js:42:20)
    at async Config.runCommand (~/.nvm/versions/node/v12.16.3/lib/node_modules/netlify-cli/node_modules/@oclif/config/lib/config.js:172:9)
    at async Main.run (~/.nvm/versions/node/v12.16.3/lib/node_modules/netlify-cli/node_modules/@oclif/command/lib/main.js:21:9)

I've installed the netlify-cli into the project in an attempt to debug what is going on. When I step through the code, I'm seeing the error is starting with isPlainObj() in the netlify-redirect-parser/common.js file. If change the function to output what is getting passed...
function isPlainObj(o) {
  console.error( "object:", o )
  console.error( "typeof o:", typeof o );
  console.error( "o.constructor:", o.constructor );
  return typeof o == 'object' && o.constructor == Object
}

I see the following output:
object: [Object: null prototype] {
  from: '/api/*',
  to: '/.netlify/functions/:splat',
  status: 200
}
typeof o: object
o.constructor: undefined

Hopefully that gives you a clue to what is going on.
- If the current behavior is a bug, please provide the steps to reproduce.

Create a node.js project
Create a netlify.toml file
Add any [[redirects]] block to the toml file.

[[redirects]]
  from = "/api/*"
  to = "/.netlify/functions/:splat"
  status = 200

- What is the expected behavior?
Netlify dev server starts without error.
- Local Environment Information
  System:
    OS: macOS 10.15.4
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
  Binaries:
    Node: 12.16.3 - ~/.nvm/versions/node/v12.16.3/bin/node
    npm: 6.14.4 - ~/.nvm/versions/node/v12.16.3/bin/npm
  Browsers:
    Chrome: 81.0.4044.129
    Firefox: 75.0
    Safari: 13.1
  npmGlobalPackages:
    netlify-cli: 2.48.0

@reverentgeek Thank you for reporting this issue. It seems like a bug. I'm wondering how the tests passed because we actually have that include these redirect rules.
This has been fixed in master branch. We're currently block on another issue and will try to release the fixes as soon as possible.
Thanks again!

<EMAIL_ADDRESS>has just been released which contains a fix for this issue. Thank you all for your patience!


ufoLib.glifLib [TypeError: Expected a path string or fs object, found tuple]

I was saving a normalized ufo using fontParts.fontshell.font RFont, where I got the following error:
  File "user/Desktop/test2.py", line 21, in <module>
    f.save()
  File "user/Github/fontParts/Lib/fontParts/base/font.py", line 203, in save
    formatVersion=formatVersion)
  File "user/Github/fontParts/Lib/fontParts/fontshell/font.py", line 49, in _save
    self.naked().save(path=path, formatVersion=formatVersion)
  File "/usr/local/lib/python3.7/site-packages/defcon/objects/font.py", line 862, in save
    self.layers.save(writer, saveAs=saveAs, progressBar=progressBar)
  File "/usr/local/lib/python3.7/site-packages/defcon/objects/layerSet.py", line 321, in save
    glyphSet = writer.getGlyphSet(layerName=None, defaultLayer=True, validateRead=self.ufoLibReadValidate, validateWrite=self.ufoLibWriteValidate)
  File "/usr/local/lib/python3.7/site-packages/fontTools/ufoLib/__init__.py", line 1383, in getGlyphSet
    return self._getGlyphSetFormatVersion1(validateRead, validateWrite, glyphNameToFileNameFunc=glyphNameToFileNameFunc)
  File "/usr/local/lib/python3.7/site-packages/fontTools/ufoLib/__init__.py", line 1400, in _getGlyphSetFormatVersion1
    validateWrite=validateWrite,
  File "/usr/local/lib/python3.7/site-packages/fontTools/ufoLib/glifLib.py", line 148, in __init__
    % type(path).__name__
TypeError: Expected a path string or fs object, found tuple

It seems your source UFO is in format 1, and in that code path there's a bug. #1667 should fix this.

Thank You just for such a fast response! Exactly! I just saved the UFO in RF3 and it got fixed!


[New] Adding console.* polyfill

While IE9 is still supported add a polyfill for console.* statement
@pnachum @ljharb

Okay updated the comment.

Will you rebase this so it does not contain any merge commits?

okay rebased

Okay @ljharb based on the post mortem is seemed like a reasonable idea, it seemed like this was low effort and high-reward for the case when people eslint-disable.  Regardless if you prefer to keep the current behavior thats fine.

@nicksorrentino hopefully nobody ever blindly does eslint-disable and only disables specific rules :-/

I mean more a specific rule so they can do a console.log or warn.  I think if we don't want this then we need to make console statements a error in eslint.  We do have some branches where they are only an eslint warn.

I disagree with @ljharb on this one.

It would be great if all of our code was tested, but it's not
For whatever reason, the warning from DLS did not break tests in monorail.
If all else fails, as it did in my case (ie I saw no lint/test failures), it would be better to not break the page.

Is there any downside to adding this?

Also, doesn't console.log also break IE9, but not fail tests?

Yes, those are good points that our tests don't fail on console.log, and that "if all else fails, it'd be better not to break the page".

Released as v1.5.0


RowanClassService does not understand appendToStream:

Some Projects Browser menu items such as Class > Add Missing Accessors and Remove Prior Versions gets this error.

Fixed in 3.0.11. No rowan support for either menu item.


Error in annotating new data: Preprocessor' object has no attribute 'include_morph'

When trying to annotate new data, with a model that includes morphology (label or multilabel), I encounter the following error:
Loading known lemmas...
Tagger loaded, now annotating...
	 + test.txt
Traceback (most recent call last):
  File "tagger.py", line 6, in <module>
    cli_tagger()
  File "/home/jbc/Data/F/pandora/pandora_testing/hipster-philology/pandora/pandora/cli.py", line 255, in cli_tagger
    tag_dir(**vars(args))
  File "/home/jbc/Data/F/pandora/pandora_testing/hipster-philology/pandora/pandora/cli.py", line 186, in tag_dir
    annotations = tagger.annotate(unseen_tokens)
  File "/home/jbc/Data/F/pandora/pandora_testing/hipster-philology/pandora/pandora/tagger.py", line 689, in annotate
    predictions=preds['morph_out'])
  File "/home/jbc/Data/F/pandora/pandora_testing/hipster-philology/pandora/pandora/preprocessing.py", line 619, in inverse_transform_morph
    if self.include_morph == 'label':
AttributeError: 'Preprocessor' object has no attribute 'include_morph'
Exception ignored in: <bound method BaseSession.__del__ of <tensorflow.python.client.session.Session object at 0x7f94ac47bf60>>
Traceback (most recent call last):
  File "/home/jbc/Data/F/pandora/pandora_testing/hipster-philology/pandora/env/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 587, in __del__
AttributeError: 'NoneType' object has no attribute 'TF_NewStatus'

Ignoring the final exception, it seems that the parameter include_morph is not available at this point. I started looking, but do not find the problem for now.

Ok, apparently it is because the Preprocessor.load does not include morph, and I don't see it being saved either. Did we loose those functionalities at some point ?

This is not a main issue fix but I have something to avoid this issue.
This comes down to variable not being set to None before the if,

Solved by #75 .


Triggering Bubbled Component Events

I want to report for a:

[x] Feature
[ ] Bug

HTML components have a built-in function that lets you dispatch an event.
<input ref={(input) => this.input = input}/>
....
this.input.dispatchEvent (new Event(...));

As far as I searched, there isn't such feature in Semantic-UI components. Is there? Since I didn't find anything regarding such feature, I would suggest the creation of it.

For example, I want to trigger manually an event, but if I do it like this:
randomFunction(e) {
  this.inputChanged({target: {value: newValue}});
}

And I have a component in this shape:
<div onChange={this.divChanged.bind(this)}>
  <Input onChange={this.inputChanged.bind(this)/>
</div>

It's gonna be buggy. Parent components, in this case, div's onChange, won't be triggered because the bubbling event is not there.
And as far as I know we can't achieve bubbling in Semantic-UI-React, can we? Excuse me if I'm wrong.

I really don't understand what you trying to do. There is a React way to handle changes of Input:
class Example extends React.Component {
  state = { value: '' }

  handleChange = (e, { value }) => {
    // call any other actions
    this.setState({ value })
  }

  render() {
    const { value } = this.state

    return <Input onChange={this.handleChange} value={value} />
  }
}

I don't see neither the logic, nor the value in your proposal now. Please make a valid code example where we will can see the usefulness of your proposal.

You didn't understand what I described.
What you do is to Handle User Input Changes. What I want to do is to Handle Programmatically Input Changes. And when you change a Component's properties programmatically, events are not naturally called.
Naturally, there is a function called dispatchEvent() in which you dispatch a Event object where you can even select bubble property to be true, so if you're gonna call onChange() then all the parent components are gonna called as well.
PS
Forgive me if I'm being rude or anything but ... Can you explain me why the culture in Git Issues is to close the Issue before it's being solved? I mean you didn't even understand my issue right there because I was clearly talking about Bubbling and Programmatically changing input and you talked about User Changing the Input, two fundamentally different things.
Sorry again if I'm being inappropriate, but it's a thing I just don't understand why you do it in Git Issues. I mean isn't the target to Solve the issues instead of just ... closing them before even you let the person who initially made the issue answer first?

You didn't understand what I described.

And I still don't understand your practical need in this. dispatchEvent() is part of DOM API, it's foreign to React which tries keep away from the real DOM tree.
If it is so necessary, then use findDOMNode(). You will receive a DOM node and then you can call dispatchEvent(). You can also wait for innerRef prop, it will be shipped in #1879, it will always return a DOM node.

Can you explain to me why the culture in Git Issues is to close the Issue before it being solved?

I don't see issue there, there is a workaround with findDOMNode if there is real need. You still didn't show me a practical example in React.

I mean you didn't even understand my issue right there because I was clearly talking about Bubbling and Programmatically changing input and you talked about User Changing the Input, two fundamentally different things.

It's one thing, React offers a one-way data flow, anything another is bad solution in most cases.
setFoo() {
  this.input.value = 'foo';
  this.inputChange();
}

The code above would never have gone through my code review because there is a direct DOM manipulation. It's the antipattern, possible you don't need React at all?

Possible you don't need React at all

... you know you're saying that because you're pissed right? And I can see it as well. Because there is not really any point of saying such thing for a productive discussion. Obviously, I have my reasons for using React and that's none of anyone's concerns.

The code above would never have gone through my code review because there is a direct DOM manipulation.

This code obviously is code just to present my point fast. Not to demonstrate to anyone my coding skills.
Obviously, behind this, I'm changing the component's state/or redux or whatever in your preference, which state is input's value, instead of changing directly the components property.
But, if I change the state programmatically, then onChange is not gonna be triggered.
And if it's not gonna be triggered, then I have to call it manually.
And if I have to call it manually, then there is no Bubble property to be true, so the parent components will not trigger onChange event.

Having similar issue. My situation is that I'm building a number picker to feed into the control of the Semantic UI's Form field. After changing the internal state of my control using onKeyDown(), the value of input changes but the onChange is not fired. I need it to fire in order to pass the data to the parent component, which originally supplies the onChange function. Reminder that onChange callback has (event, data).


How to get seconds picker also

Question
I cant find a place where is documented about seconds, i managed to get it working with hour and minute, but i also like to have second support, is it possible or not?

hello, thanks for asking, no, this is not possible. I do not think the native functionality for this exists so I don't think it can be done in this module, you'll have to create a custom solution for this.


Agency Pilot: AAD 2.1 Legacy Authentication False positive

AAD 2.1 "Legacy authentication SHALL be blocked" produced a false positive for an agency pilot. The agency has legacy authentication blocked but only for locations outside of the US. For this they configured the "locations" and "client apps" sections within the conditions for a conditional access policy. Please email Andrew Huynh for the provider json for further investigation.

P.S. the results was found using the Scubagear module version 0.2.1

tied to #92

@ahuynhMITRE Since this appears to be a real-world manifestation of the bug described in #92 and not a separate bug, do we need this separate issue? Can we take the description of this issue and put it into #92, then close this one?

closing due to consolidation of issue into #86


fix: wait for chokidar ready event before listening to function builder src directory

- Summary
Fixes https://github.com/netlify/cli/issues/904
- Test plan
You can follow my comment here to reproduce
- Description for the changelog
chokidar sends an initial add event for each existing file in the watched directory.
In the case of the bug, that event was fired for each file under functions/node_modules spawning multiple build commands.
You can ignore those initial events by waiting for the ready event or passing ignoreInitial:
https://github.com/paulmillr/chokidar#path-filtering
Also debounced the build command to make sure only one instance of it executes at a single point in time.
- A picture of a cute animal (not mandatory but encouraged)
🐈

Thank you for this PR @erezrokah

My pleasure 😄


Remove diacritics from filenames

Remove diacritics from example filenames, causing problem on MacOS:
Package operations: 7 installs, 0 updates, 0 removals
  - Installing pear/pear_exception (v1.0.1): Downloading (100%)
  - Installing pear/console_getopt (v1.4.3): Loading from cache
  - Installing pear/pear-core-minimal (v1.10.10): Loading from cache
  - Installing pear/mail_mime (1.10.7): Loading from cache
  - Installing pear/mail (v1.4.1): Loading from cache
  - Installing vitexsoftware/ease-core (dev-master 766a8bd): Downloading (100%)
  - Installing spoje.net/flexibee (dev-master 9e5c1ee): Downloading (100%)
    Failed to execute unzip -qq  '/Users/VojtaSvoboda/Www/project-name/vendor/spoje.net/flexibee/8042c06751d8b43c294d845a1572cd55' -d '/Users/VojtaSvoboda/Www/project-name/vendor/composer/9993345d'

error:  cannot create /Users/VojtaSvoboda/Www/project-name/vendor/composer/9993345d/Spoje-NET-php-flexibee-9e5c1ee/Examples/Naskladn-�n+�.php
        Illegal byte sequence
error:  cannot create /Users/VojtaSvoboda/Www/project-name/vendor/composer/9993345d/Spoje-NET-php-flexibee-9e5c1ee/Examples/P+�evodka.php
        Illegal byte sequence

    The archive may contain identical file names with different capitalization (which fails on case insensitive filesystems)

Thanks @vojtasvoboda !


User session timeouts

We want to implement a feature where user sessions automatically expire after a specified period of inactivity within the app. Achieving this requires delving into the functionality of next-auth and configuring session expiry settings accordingly. Ideally, we'd like to extend user sessions while they actively engage with the app, ensuring that sessions expire only when users cease app usage.

Checked on test account. The session was 24 hours.


Update repository name in install instructions

github.com/pion/webrtc-example-applications ->
github.com/pion/example-webrtc-applications

Thank you so much for the fix @stevedenman!
Would you mind fixing the other places I got this wrong?
38f9d359441f:example-webrtc-applications seaduboi$ grep -r 'go get'  .
./gstreamer-receive/README.md:go get github.com/pion/webrtc-example-applications/gstreamer-receive
./sfu-ws/README.md:go get github.com/pion/webrtc/examples/sfu-ws
./README.md:    go get github.com/webrtc-example-applications
./gstreamer-send/README.md:go get github.com/pion/webrtc-example-applications/gstreamer-send

You also failed the following checks in CI.
Please add the following contributors to the README
stevedenman

and
Update repository name in install instructions
-------------------------------------------------
The preceding commit message is invalid
it failed 'Separate subject from body with a blank line' of the following checks
* Separate subject from body with a blank line
* Limit the subject line to 50 characters
* Capitalize the subject line
* Do not end the subject line with a period
* Wrap the body at 72 characters
The command "bash .github/lint-commit-message.sh" exited with 1.

If you have any questions happy to help here, and I am also available on Slack thanks!


Replace swig with a maintained templating system

Replace Swig templates with either Mustache or Handlebars or any other templating syste,

The author of Swig recommends Nunjucks.


Fix typo: change some description in slack.md

All "微信交流群" appeared in slack.md should be "slack " or "slack group"，this commit fix it.
Signed-off-by: Guoqiang QI<EMAIL_ADDRESS>

Thanks for fixing the typos. @guoqiangqi


Inconsistency with unique and exists validators on other connections

Laravel Version: 7.7.1
PHP Version: 7.4.0
Database Driver & Version: MySQL 5.7.28

When you need the unique and exists validators on other connections, there are several options, but they don't work always the same.
Assuming we have a model like this:
class User extends Model
{
    protected $connection = 'other';
}

These rules work correctly:
'unique:other.users'
'unique:'.User::class
Rule::unique('other.users')

But the following does not, as it ignores the connection:
Rule::unique(User::class)

Same with the exists rule.

Fixed on master branch. I'm not comfortable fixing on a patch release because some applications may be depending on this "bug" using the default connection if no other connection is specified. You can use one of the alternative approaches for now.

Okay, thanks!


"Class" vs "Model"

Why:
CLASS(...
extendsModel
...)
Rather than:
MODEL(...
extendsModel
...)
or:
CLASS(...
extendsClass
...)
?

extends and class are both reserved words in Javascript, so we avoid using them.
The original phrasing was MODEL and extendsModel. FOAM's models really are models, in the "modeling language" sense, but that's a very unfamiliar world to most programmers. The use of "class" in our docs and CLASS in code is hoping to make things more familiar.
Since we're doing metaprogramming at runtime in Javascript, it's harder to see the distinction. In our own discussions on the team, we tend to refer to the JSONish object you pass to CLASS() as the "model", which describes the "class". The "class" is what FOAM generates based on the model you provide, and the "prototype" is the Javascript prototype we actually create instances of.
For most purposes, though, there isn't much distinction between models and classes in this parlance. We wish we could use better syntax and spellings, but Javascript reserved lots of handy words and never used them.
As for why it isn't CLASS and extendsClass (and class_ instead of model_) that's mostly historical. We added CLASS but didn't change "model" for "class" everywhere.

We now use extends rather than extendsModel, which definitely helps this confusion. Closed either way; there's nothing actionable here.


Enable token transfers

[ ] #404
[ ] #405
[ ] #406
[ ] prepare vesting batch & execute it
[ ] deploy runtime change

Sry


Selecting the right address for checkout steps

Steps to reproduce the problem

Add a product to bag and go to checkout as an authenticated user.
Fill the shipping address (note that at this point this form is empty, while we might have the default address assigned to the user) and select option Use as Billing Address.

Continue to the billing address step. Instead of the address from the first step, there is a different address which is assigned to my account.

First we should make sure that Use as billing checkbox actually works properly. Second, user should be able to use his default addresses that are already saved in his account. I'm not sure about the UI/UX of this - e.g. in the old storefront we show a selection of existing addresses or a form to add new address. Don't know how do we want to approach it here (question to @pwgryglak, but maybe we already have that on mockups).

@piotrgrundas
We'll be moving "use this as billing address" to billing address section. We'll rename it to same as shipping. It should fill up the form.
Updates will be on Figma.


build(docker): pin pip requirements in requirements.txt for dockerfiles

Change Overview
To make it possible to pin and bump pip requirements by dependabot in docker images, the versions are now specified in requirements.txt files
Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[ ] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[ ] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test
[x] :building_construction: Build

Issues

fixes #issue-number

Test Plan
Build images using docker buildx build -f <dockerfile> . from the repo root (for postgres images --build-arg="TOOLS_IMAGE=<tools image>" is required.
Validate that pip packages are the same versions as specified and the same set as in published packages.

[x] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

Relates to security scanning:
https://github.com/kanisterio/kanister/security/code-scanning/76
https://github.com/kanisterio/kanister/security/code-scanning/77
https://github.com/kanisterio/kanister/security/code-scanning/111


RC2: "Unable to find provider assembly with name EntityFramework.MicrosoftSqlServer" error

An attempt to scaffold database as described here:
https://docs.efproject.net/en/latest/platforms/full-dotnet/existing-db.html
results in error:
"Unable to find provider assembly with name EntityFramework.MicrosoftSqlServer. Ensure the specified name is correct and is referenced by the project."
All three required packages have been successfully installed. It worked for RC1

Your scaffold command has a provider package name in it, you need to swap to the RC2 provider name - which is Microsoft.EntityFrameworkCore.SqlServer (the error suggests you are still specifying the RC1 package name of EntityFramework.MicrosoftSqlServer).

That's the error you would see if you executed Scaffold-DbContext "Server=(localdb)\mssqllocaldb;Database=Blogging;Trusted_Connection=True;" EntityFramework.MicrosoftSqlServer.
For RC2 you need to do Scaffold-DbContext "Server=(localdb)\mssqllocaldb;Database=Blogging;Trusted_Connection=True;" Microsoft.EntityFrameworkCore.SqlServer. Note the change to the provider name.

I have a WPF 4.61 app using EF6. When I try to follow this article and scaffold in my repository project, I get this error:
PM> Scaffold-DbContext "Server=(localdb)\mssqllocaldb;Database=MyDB;Trusted_Connection=True;" Microsoft.EntityFrameworkCore.SqlServer
Unable to find provider assembly with name Microsoft.EntityFrameworkCore.SqlServer. Ensure the specified name is correct and is referenced by the project.
The reference to the assembly is definitely in the project. Is it a problem because the project is also still using EF6? I can't compile without that and EF Core 2 requires it to build.
I was able to convert a separate console app from EF6 to EF Core 2.0.


Disk resize is limited to 500GB in sunstone

Author Name: Venko Moyankov (Venko Moyankov)
Original Redmine Issue: 5440, https://dev.opennebula.org/issues/5440
Original Date: 2017-10-06

When trying to resize disk to size larger than 500GB on existing VM using sunstone, new size is limited to 500GB. Any subsequent try returns error: New disk size has to be greater than current one.
When using XML-RPC everything is OK.
To reproduce:

create VM
start VM
on running VM, resize disk
enter new size 550GB using the text box
disk will be resized to 500GB
on running VM resize disk
enter new size 550GB using the text box

The code with the limit of 500GB is located at:
src/sunstone/public/app/tabs/vms-tab/dialogs/disk-resize.js:85
max: Humanize.sizeToMB("500GB")*1024,

This is already solved in #1486


Update Invoicing.md

fix screen shots

Docs Build status updates of commit fbd7e9c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/distribution/Invoicing.md
:warning:Warning
View
Details

dynamics-gp/distribution/Invoicing.md

Line 186: [Warning] Invalid file link:(~/distribution/media/INVSM.jpg).
Line 201: [Warning] Invalid file link:(~/distribution/media/INVISO.jpg).
Line 524: [Warning] Invalid file link:(~/distribution/media/873d155296f235a43b3de1db75a2dfc6.jpg).
Line 748: [Warning] Invalid file link:(~/distribution/media/a583ab85a5fd23a26953e229a8e6af98.jpg).
Line 797: [Warning] Invalid file link:(~/distribution/media/e8b31efbbf5a1cb8bd7b002f0abe02d3.jpg).
Line 1004: [Warning] Invalid file link:(~/distribution/media/66dd8e2d7a25c58f2c1efbeb54c24f1b.jpg).
Line 1191: [Warning] Invalid file link:(~/distribution/media/889aa564c305239ce95705b11812c921.jpg).
Line 1321: [Warning] Invalid file link:(~/distribution/media/56c495143606260b358edb18bdab928f.jpg).
Line 1613: [Warning] Invalid file link:(~/distribution/media/5707e44a41ccfca2721eb419bc1db795.jpg).
Line 1659: [Warning] Invalid file link:(~/distribution/media/496f5b7262fb001a23d01d1c21a3fa4d.jpg).
Line 1885: [Warning] Invalid file link:(~/distribution/media/bb3b2302a95a7f4a0903252d1d018f69.jpg).
Line 1947: [Warning] Invalid file link:(~/distribution/media/9e22f7a16c489ea2fec8b5b57f133815.jpg).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit a54cc80:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamics-gp/distribution/Invoicing.md
:warning:Warning
View
Details

dynamics-gp/distribution/Invoicing.md

Line 186: [Warning] Invalid file link:(~/distribution/media/INVSM.jpg).
Line 201: [Warning] Invalid file link:(~/distribution/media/INVISO.jpg).
Line 537: [Warning] Invalid file link:(~/distribution/media/INVRQE.jpg).
Line 740: [Warning] Invalid file link:(~/distribution/media/66dd8e2d7a25c58f2c1efbeb54c24f1b.jpg).
Line 927: [Warning] Invalid file link:(~/distribution/media/889aa564c305239ce95705b11812c921.jpg).
Line 1057: [Warning] Invalid file link:(~/distribution/media/56c495143606260b358edb18bdab928f.jpg).
Line 1349: [Warning] Invalid file link:(~/distribution/media/5707e44a41ccfca2721eb419bc1db795.jpg).
Line 1395: [Warning] Invalid file link:(~/distribution/media/496f5b7262fb001a23d01d1c21a3fa4d.jpg).
Line 1621: [Warning] Invalid file link:(~/distribution/media/bb3b2302a95a7f4a0903252d1d018f69.jpg).
Line 1683: [Warning] Invalid file link:(~/distribution/media/9e22f7a16c489ea2fec8b5b57f133815.jpg).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


The text is correct?

Guys,
(https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-cosmosdb-v2-trigger?tabs=in-process%2Cextensionv4&pivots=programming-language-csharp)
This page is talking about Azure Cosmos DB trigger but in the following text the service Event Grid is mentioned suddenly. Is there something that I did not get in text or the name of event grid was put in the place of cosmos db accidentally?
(the text below was extracted from the page talking about azure cosmos db trigger)
Usage
The parameter type supported by the Event Grid trigger depends on the Functions runtime version, the extension package version, and the C# modality used.

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

ID: 28aac762-b154-1d0e-9afc-67889fdf9762
Version Independent ID: 9a406f60-6c72-d3d9-2bc9-8d8e8c1922ae
Content: Azure Cosmos DB trigger for Functions 2.x and higher
Content Source: articles/azure-functions/functions-bindings-cosmosdb-v2-trigger.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@RBVieira we'll review your feedback and get back to you shortly. Thanks.

#reassign:ggailey777

Thanks @RBVieira for reporting this, which is likely a copy-paste error. I'll investigate.


Correctly use fallback for default fonts

closes #39235

closes #39235

All font issues from the #39235 seems to be fixed.
Editor icon issues are not (probably unrelated to theme):

File dialog icons are missing in the following dialogs:
- All file dialogs opened from "Export"
- All file dialogs opened from "Inspector"

good

closes #39235

All font issues from the #39235 seems to be fixed.
Editor icon issues are not (probably unrelated to theme):

Should be fixed now.

Thanks!


'React/RCTBridgeModule.h' file not found

Hi,
I'm using RCTBridgeModule in my project actually due to a problem moved the code from one system to another in my old system the code was working fine but now after moving to my new system it's showing me a error that 'React/RCTBridgeModule.h' file not found. Can anyone help me with this issue plesase

No response so closing.


GLB loaded incorrectly

The model included in the playground below loads with transparent faces even though the model is supposed to be fully opaque. The same model loads correctly in the this GLTF Viewer I've tested on OSX on Chrome and Firefox.
http://www.babylonjs-playground.com/#6MZV8R#60

Ping @bghgary

Actually, parsing the glb leads to this json for materials:
"materials": [
{
"alphaMode": "BLEND",
"name": "Naranaja ",
"pbrMetallicRoughness": {
"baseColorFactor": [
0.866666734218597,
0.666666686534882,
0.133333340287209,
1
],
"metallicFactor": 0.100000001490116,
"roughnessFactor": 0.400000005960464
}
},
{
"alphaMode": "BLEND",
"name": "Gris 01",
"pbrMetallicRoughness": {
"baseColorFactor": [
0.572549045085907,
0.572549045085907,
0.572549045085907,
1
],
"metallicFactor": 0.100000001490116,
"roughnessFactor": 0.400000005960464
}
},
{
"alphaMode": "BLEND",
"name": "Vidrio",
"pbrMetallicRoughness": {
"baseColorFactor": [
0.901960849761963,
0.90588241815567,
0.913725554943085,
1
],
"metallicFactor": 0.100000001490116,
"roughnessFactor": 0.400000005960464
}
},
{
"alphaMode": "BLEND",
"emissiveFactor": [
1,
1,
1
],
"name": "Light",
"pbrMetallicRoughness": {
"baseColorFactor": [
0,
0,
0,
1
],
"metallicFactor": 0.100000001490116,
"roughnessFactor": 0.400000005960464
}
},
{
"alphaMode": "BLEND",
"name": "Gris_oscuro con rallas",
"pbrMetallicRoughness": {
"baseColorFactor": [
0.223529428243637,
0.223529428243637,
0.223529428243637,
1
],
"metallicFactor": 0.100000001490116,
"roughnessFactor": 0.400000005960464
}
},
{
"alphaMode": "BLEND",
"name": "Naranaja ",
"pbrMetallicRoughness": {
"baseColorFactor": [
0.866666734218597,
0.666666686534882,
0.133333340287209,
1
],
"metallicFactor": 0.100000001490116,
"roughnessFactor": 0.400000005960464
}
},
{
"alphaMode": "BLEND",
"name": "Black_1",
"pbrMetallicRoughness": {
"baseColorFactor": [
0.0784313753247261,
0.0784313753247261,
0.0784313753247261,
1
],
"metallicFactor": 0.100000001490116,
"roughnessFactor": 0.400000005960464
}
},
{
"alphaMode": "BLEND",
"name": "Rojo_1",
"pbrMetallicRoughness": {
"baseColorFactor": [
0.647058844566345,
0,
0.0745098069310188,
1
],
"metallicFactor": 0.100000001490116,
"roughnessFactor": 0.400000005960464
}
},
{
"alphaMode": "BLEND",
"name": "Grey",
"pbrMetallicRoughness": {
"baseColorFactor": [
0.572549045085907,
0.572549045085907,
0.572549045085907,
1
],
"metallicFactor": 0.100000001490116,
"roughnessFactor": 0.400000005960464
}
}
]
As you can see all the materials are flagged as "BLEND" which explains the behavior.

You can then force all materials to turn blending off by setting material.transparencyMode = BABYLON.PBRMATERIAL_OPAQUE

@FreakTheMighty , you can see a sample here: https://www.babylonjs-playground.com/#6MZV8R#64

This was definitely FBX2glTF's fault, and it was fixed just the other day. The model will output as OPAQUE now.
I am curious, though; shouldn't the 1.0 alpha in baseColor (and the absent of either diffuse texture or vertex colour) essentially make BLEND meaningless?

I guess this could be animated and having it flagged as blend would prevent switching render queues or shader during the animation but this is a bit of an edge case I agree.
Maybe this could be flagged in the gltf-validator?

@zellski shouldn't the 1.0 alpha in baseColor (absent either diffuse texture or vertex colour) essentially make BLEND meaningless?

Blend in BabylonJS does not write depth, so sorting is an issue. I suppose we can force it back to opaque if alpha is 1.0 in the loader, but the asset is still inherently incorrect.

@sebavan Maybe this could be flagged in the gltf-validator?

@lexaknyazev Is this easy to add to the validator?


Replace EMRFS with hadoop-aws S3A libraries

Please delete the branch after you've merged it into master so we don't have all these redundant branches hanging around. I'll delete this one now (you get a "delete branch" button to click after you've done the merge in the UI which makes it really easy).


Update thoughtbot section of README

Include 2015 in the copyright.
Update logo to use new HTTPS version.
Change header from "Credits" to "About thoughtbot".
Move "thank you" to contributors section.
Make "About thoughtbot" the last thing in the README,
with the copyrights grouped closer to the LICENSE information.
Link to LICENSE.
Make the community link more obvious that we have other projects.
Finish with a CTA to hire us.
Include utm_source codes to improve tracking.

Looks great to me.

For what it's worth after a slack convo in January, we removed the year
from the clearance copyright.
On Saturday, March 7, 2015, Dan Croak<EMAIL_ADDRESS>wrote:

Merged #534 https://github.com/thoughtbot/suspenders/pull/534.
—
Reply to this email directly or view it on GitHub
https://github.com/thoughtbot/suspenders/pull/534#event-248052236.

Ah, cool. Yeah, it's kind of annoying to keep it updated.


Run tests in parallel

Using some tips and ticks from Symfony that I learned on PHP-Geocoder we should run tests in parallel.

Codecov Report

Merging #170 into master will decrease coverage by 76.5%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master   #170       +/-   ##
===========================================
- Coverage      76.5%     0%   -76.51%
- Complexity        0    544      +544
===========================================
  Files            26     26
  Lines          1481   2093      +612
===========================================
- Hits           1133      0     -1133
- Misses          348   2093     +1745

Impacted Files
Coverage Δ
Complexity Δ

src/Adapter/Illuminate/IlluminateCachePool.php
0% <0%> (-100%)
14% <0%> (+14%)

src/Adapter/Doctrine/DoctrineCachePool.php
0% <0%> (-100%)
16% <0%> (+16%)

src/Prefixed/PrefixedCachePool.php
0% <0%> (-100%)
13% <0%> (+13%)

src/Bridge/SimpleCache/SimpleCacheBridge.php
0% <0%> (-100%)
34% <0%> (+34%)

src/Namespaced/NamespacedCachePool.php
0% <0%> (-100%)
13% <0%> (+13%)

src/Adapter/Redis/RedisCachePool.php
0% <0%> (-100%)
14% <0%> (+14%)

src/Adapter/MongoDB/MongoDBCachePool.php
0% <0%> (-100%)
15% <0%> (+15%)

src/Hierarchy/HierarchicalCachePoolTrait.php
0% <0%> (-100%)
9% <0%> (+9%)

src/Adapter/Common/CacheItem.php
0% <0%> (-97.68%)
36% <0%> (+36%)

src/Adapter/Predis/PredisCachePool.php
0% <0%> (-97.15%)
15% <0%> (+15%)

... and 13 more

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 5c41c7c...4d7e3c8. Read the comment docs.

Finally!