 Please consider supporting of core-js on Open Collective or Patreon:
2022-06-13T23:59:15.3254557Z       01 > https://opencollective.com/core-js
2022-06-13T23:59:15.3255944Z       01 > https://www.patreon.com/zloirock
2022-06-13T23:59:15.3257153Z       01
2022-06-13T23:59:15.3258759Z       01 Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
2022-06-13T23:59:15.3260210Z       01
2022-06-13T23:59:16.7793545Z       01 npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
2022-06-13T23:59:16.7796293Z       01 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-13T23:59:16.7798461Z       01 npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
2022-06-13T23:59:16.7800790Z       01 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-13T23:59:16.7802576Z       01
2022-06-13T23:59:16.7854095Z       01 added 2036 packages from 844 contributors and audited 2040 packages in 26.286s
2022-06-13T23:59:18.0696987Z       01
2022-06-13T23:59:18.0698113Z       01 119 packages are looking for funding
2022-06-13T23:59:18.0699213Z       01   run `npm fund` for details
2022-06-13T23:59:18.0700172Z       01
2022-06-13T23:59:18.0701305Z       01 found 13 vulnerabilities (1 low, 1 moderate, 10 high, 1 critical)
2022-06-13T23:59:18.0702696Z       01   run `npm audit fix` to fix them, or `npm audit` for details
2022-06-13T23:59:29.3989895Z       01 npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-06-13T23:59:29.3994708Z       01 npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-06-13T23:59:29.3996743Z       01 npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
2022-06-13T23:59:29.3999321Z       01 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-13T23:59:29.4001825Z       01 npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
2022-06-13T23:59:29.4004319Z       01 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-13T23:59:29.4006034Z       01
2022-06-13T23:59:29.5439656Z       01 audited 2040 packages in 10.397s
2022-06-13T23:59:30.4695442Z       01
2022-06-13T23:59:30.4696567Z       01 119 packages are looking for funding
2022-06-13T23:59:30.4697681Z       01   run `npm fund` for details
2022-06-13T23:59:30.4698640Z       01
2022-06-13T23:59:30.4699750Z       01 found 13 vulnerabilities (1 low, 1 moderate, 10 high, 1 critical)
2022-06-13T23:59:30.4701147Z       01   run `npm audit fix` to fix them, or `npm audit` for details
2022-06-13T23:59:33.3000381Z       01 DEPRECATION: `bowerDependencies` has been deprecated.
2022-06-13T23:59:33.3002647Z       01 If you still need access to the project's Bower dependencies, you will have to manually resolve the project's `bower.json` file instead. [ID: ember-cli.project.bower-dependencies]
2022-06-13T23:59:33.3004730Z       01 at getStackTrace (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:99:15)
2022-06-13T23:59:33.3006555Z       01 at deprecate (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:77:8)
2022-06-13T23:59:33.3008220Z       01 at Project.bowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/models/project.js:412:5)
2022-06-13T23:59:33.3010217Z       01 at EmberCLIDependencyChecker.normalizedBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:138:44)
2022-06-13T23:59:33.3012511Z       01 at EmberCLIDependencyChecker.readBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:148:39)
2022-06-13T23:59:33.3014596Z       01 at EmberCLIDependencyChecker.checkDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:43:28)
2022-06-13T23:59:33.3016452Z       01 at Class.init (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/index.js:18:25)
2022-06-13T23:59:33.3018258Z       01 at Class.superWrapper [as init] (/var/www/violet/releases/20220613235541/client/node_modules/core-object/lib/assign-properties.js:34:20)
2022-06-13T23:59:33.3019920Z       01 at new CoreObject (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:9:15)
2022-06-13T23:59:33.3021500Z       01 at new Class (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:21:5)
2022-06-13T23:59:34.3464473Z       01 DEPRECATION: Node v10.19.0 is no longer supported by Ember CLI. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-13T23:59:34.3467278Z       01 WARNING: Node v10.19.0 is not tested against Ember CLI on your platform. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-13T23:59:35.5362097Z       01 - Building
2022-06-13T23:59:35.5363217Z       01 Environment: production
2022-06-13T23:59:35.5364254Z       01 - Building
2022-06-13T23:59:35.5365250Z       01 - building...
2022-06-14T00:03:36.3552349Z       01 Killed
2022-06-14T00:03:36.5857689Z #<Thread:0x00007f6734120f78@/home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/runners/parallel.rb:10 run> terminated with exception (report_on_exception is true):
2022-06-14T00:03:36.5861719Z /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/runners/parallel.rb:15:in `rescue in block (2 levels) in execute': Exception while executing as ubuntu@***: rake exit status: 137 (SSHKit::Runner::ExecuteError)
2022-06-14T00:03:36.5864310Z rake stdout: ><EMAIL_ADDRESS>postinstall node_modules/core-js
2022-06-14T00:03:36.5865878Z > node -e "try{require('./postinstall')}catch(e){}"
2022-06-14T00:03:36.5866552Z
2022-06-14T00:03:36.5867858Z Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
2022-06-14T00:03:36.5868865Z
2022-06-14T00:03:36.5870019Z The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
2022-06-14T00:03:36.5871641Z > https://opencollective.com/core-js
2022-06-14T00:03:36.5872975Z > https://www.patreon.com/zloirock
2022-06-14T00:03:36.5873636Z
2022-06-14T00:03:36.5874733Z Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
2022-06-14T00:03:36.5875660Z
2022-06-14T00:03:36.5876429Z added 2036 packages from 844 contributors and audited 2040 packages in 26.286s
2022-06-14T00:03:36.5877270Z
2022-06-14T00:03:36.5879694Z 119 packages are looking for funding
2022-06-14T00:03:36.5880763Z   run `npm fund` for details
2022-06-14T00:03:36.5881289Z
2022-06-14T00:03:36.5881959Z found 13 vulnerabilities (1 low, 1 moderate, 10 high, 1 critical)
2022-06-14T00:03:36.5883268Z   run `npm audit fix` to fix them, or `npm audit` for details
2022-06-14T00:03:36.5884491Z audited 2040 packages in 10.397s
2022-06-14T00:03:36.5885047Z
2022-06-14T00:03:36.5885583Z 119 packages are looking for funding
2022-06-14T00:03:36.5886597Z   run `npm fund` for details
2022-06-14T00:03:36.5887113Z
2022-06-14T00:03:36.5887768Z found 13 vulnerabilities (1 low, 1 moderate, 10 high, 1 critical)
2022-06-14T00:03:36.5889073Z   run `npm audit fix` to fix them, or `npm audit` for details
2022-06-14T00:03:36.5891526Z DEPRECATION: Node v10.19.0 is no longer supported by Ember CLI. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-14T00:03:36.5894350Z WARNING: Node v10.19.0 is not tested against Ember CLI on your platform. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-14T00:03:36.5896012Z Environment: production
2022-06-14T00:03:36.5897891Z rake stderr: npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
2022-06-14T00:03:36.5900278Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.5902261Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
2022-06-14T00:03:36.5904684Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.5905865Z
2022-06-14T00:03:36.5907323Z npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-06-14T00:03:36.5909788Z npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-06-14T00:03:36.5911689Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
2022-06-14T00:03:36.5913835Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.5916225Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
2022-06-14T00:03:36.5918582Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.5919953Z
2022-06-14T00:03:36.5920582Z DEPRECATION: `bowerDependencies` has been deprecated.
2022-06-14T00:03:36.5925566Z If you still need access to the project's Bower dependencies, you will have to manually resolve the project's `bower.json` file instead. [ID: ember-cli.project.bower-dependencies]
2022-06-14T00:03:36.5928012Z at getStackTrace (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:99:15)
2022-06-14T00:03:36.5930157Z at deprecate (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:77:8)
2022-06-14T00:03:36.5932394Z at Project.bowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/models/project.js:412:5)
2022-06-14T00:03:36.5935114Z at EmberCLIDependencyChecker.normalizedBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:138:44)
2022-06-14T00:03:36.5939432Z at EmberCLIDependencyChecker.readBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:148:39)
2022-06-14T00:03:36.5942362Z at EmberCLIDependencyChecker.checkDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:43:28)
2022-06-14T00:03:36.5945007Z at Class.init (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/index.js:18:25)
2022-06-14T00:03:36.5947298Z at Class.superWrapper [as init] (/var/www/violet/releases/20220613235541/client/node_modules/core-object/lib/assign-properties.js:34:20)
2022-06-14T00:03:36.5949461Z at new CoreObject (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:9:15)
2022-06-14T00:03:36.5951477Z at new Class (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:21:5)
2022-06-14T00:03:36.5952865Z - Building
2022-06-14T00:03:36.5953705Z - Building
2022-06-14T00:03:36.5954542Z - building...
2022-06-14T00:03:36.5955339Z Killed
2022-06-14T00:03:36.5956878Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/runners/parallel.rb:11:in `block (2 levels) in execute'
2022-06-14T00:03:36.5959230Z /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/command.rb:97:in `exit_status=': rake exit status: 137 (SSHKit::Command::Failed)
2022-06-14T00:03:36.5960812Z rake stdout: ><EMAIL_ADDRESS>postinstall node_modules/core-js
2022-06-14T00:03:36.5962018Z > node -e "try{require('./postinstall')}catch(e){}"
2022-06-14T00:03:36.5962596Z
2022-06-14T00:03:36.5963696Z Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
2022-06-14T00:03:36.5964592Z
2022-06-14T00:03:36.5965572Z The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
2022-06-14T00:03:36.5966984Z > https://opencollective.com/core-js
2022-06-14T00:03:36.5968127Z > https://www.patreon.com/zloirock
2022-06-14T00:03:36.5968691Z
2022-06-14T00:03:36.5969634Z Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
2022-06-14T00:03:36.5970428Z
2022-06-14T00:03:36.5971091Z added 2036 packages from 844 contributors and audited 2040 packages in 26.286s
2022-06-14T00:03:36.5971803Z
2022-06-14T00:03:36.5972269Z 119 packages are looking for funding
2022-06-14T00:03:36.5973150Z   run `npm fund` for details
2022-06-14T00:03:36.5973604Z
2022-06-14T00:03:36.5974170Z found 13 vulnerabilities (1 low, 1 moderate, 10 high, 1 critical)
2022-06-14T00:03:36.5975300Z   run `npm audit fix` to fix them, or `npm audit` for details
2022-06-14T00:03:36.5976362Z audited 2040 packages in 10.397s
2022-06-14T00:03:36.5977039Z
2022-06-14T00:03:36.5977522Z 119 packages are looking for funding
2022-06-14T00:03:36.5978421Z   run `npm fund` for details
2022-06-14T00:03:36.5978878Z
2022-06-14T00:03:36.5979450Z found 13 vulnerabilities (1 low, 1 moderate, 10 high, 1 critical)
2022-06-14T00:03:36.5980579Z   run `npm audit fix` to fix them, or `npm audit` for details
2022-06-14T00:03:36.5982658Z DEPRECATION: Node v10.19.0 is no longer supported by Ember CLI. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-14T00:03:36.5985227Z WARNING: Node v10.19.0 is not tested against Ember CLI on your platform. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-14T00:03:36.5986665Z Environment: production
2022-06-14T00:03:36.5988284Z rake stderr: npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
2022-06-14T00:03:36.5990357Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.5992079Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
2022-06-14T00:03:36.5993935Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.5994950Z
2022-06-14T00:03:36.5996190Z npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-06-14T00:03:36.5998334Z npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-06-14T00:03:36.5999962Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
2022-06-14T00:03:36.6001820Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6003903Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
2022-06-14T00:03:36.6005940Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6006971Z
2022-06-14T00:03:36.6007506Z DEPRECATION: `bowerDependencies` has been deprecated.
2022-06-14T00:03:36.6009450Z If you still need access to the project's Bower dependencies, you will have to manually resolve the project's `bower.json` file instead. [ID: ember-cli.project.bower-dependencies]
2022-06-14T00:03:36.6011497Z at getStackTrace (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:99:15)
2022-06-14T00:03:36.6013327Z at deprecate (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:77:8)
2022-06-14T00:03:36.6015247Z at Project.bowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/models/project.js:412:5)
2022-06-14T00:03:36.6017576Z at EmberCLIDependencyChecker.normalizedBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:138:44)
2022-06-14T00:03:36.6020148Z at EmberCLIDependencyChecker.readBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:148:39)
2022-06-14T00:03:36.6022621Z at EmberCLIDependencyChecker.checkDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:43:28)
2022-06-14T00:03:36.6024922Z at Class.init (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/index.js:18:25)
2022-06-14T00:03:36.6026871Z at Class.superWrapper [as init] (/var/www/violet/releases/20220613235541/client/node_modules/core-object/lib/assign-properties.js:34:20)
2022-06-14T00:03:36.6028912Z at new CoreObject (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:9:15)
2022-06-14T00:03:36.6030735Z at new Class (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:21:5)
2022-06-14T00:03:36.6031948Z - Building
2022-06-14T00:03:36.6032778Z - Building
2022-06-14T00:03:36.6033595Z - building...
2022-06-14T00:03:36.6034373Z Killed
2022-06-14T00:03:36.6035827Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/backends/netssh.rb:170:in `execute_command'
2022-06-14T00:03:36.6037872Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/backends/abstract.rb:148:in `block in create_command_and_execute'
2022-06-14T00:03:36.6039852Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/backends/abstract.rb:148:in `tap'
2022-06-14T00:03:36.6041795Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/backends/abstract.rb:148:in `create_command_and_execute'
2022-06-14T00:03:36.6043669Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/backends/abstract.rb:80:in `execute'
2022-06-14T00:03:36.6045706Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/capistrano-rails-1.6.1/lib/capistrano/tasks/assets.rake:69:in `block (6 levels) in <top (required)>'
2022-06-14T00:03:36.6047673Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/backends/abstract.rb:100:in `with'
2022-06-14T00:03:36.6049702Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/capistrano-rails-1.6.1/lib/capistrano/tasks/assets.rake:68:in `block (5 levels) in <top (required)>'
2022-06-14T00:03:36.6051680Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/backends/abstract.rb:92:in `within'
2022-06-14T00:03:36.6053702Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/capistrano-rails-1.6.1/lib/capistrano/tasks/assets.rake:67:in `block (4 levels) in <top (required)>'
2022-06-14T00:03:36.6055685Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/backends/abstract.rb:31:in `instance_exec'
2022-06-14T00:03:36.6057527Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/backends/abstract.rb:31:in `run'
2022-06-14T00:03:36.6059453Z 	from /home/runner/work/violet_rails/violet_rails/vendor/bundle/ruby/2.6.0/gems/sshkit-1.21.2/lib/sshkit/runners/parallel.rb:12:in `block (2 levels) in execute'
2022-06-14T00:03:36.6060877Z (Backtrace restricted to imported tasks)
2022-06-14T00:03:36.6061784Z cap aborted!
2022-06-14T00:03:36.6063438Z SSHKit::Runner::ExecuteError: Exception while executing as ubuntu@***: rake exit status: 137
2022-06-14T00:03:36.6064875Z rake stdout: ><EMAIL_ADDRESS>postinstall node_modules/core-js
2022-06-14T00:03:36.6066084Z > node -e "try{require('./postinstall')}catch(e){}"
2022-06-14T00:03:36.6066654Z
2022-06-14T00:03:36.6067762Z Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
2022-06-14T00:03:36.6068634Z
2022-06-14T00:03:36.6069616Z The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
2022-06-14T00:03:36.6071101Z > https://opencollective.com/core-js
2022-06-14T00:03:36.6072246Z > https://www.patreon.com/zloirock
2022-06-14T00:03:36.6072807Z
2022-06-14T00:03:36.6073743Z Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
2022-06-14T00:03:36.6074695Z
2022-06-14T00:03:36.6075364Z added 2036 packages from 844 contributors and audited 2040 packages in 26.286s
2022-06-14T00:03:36.6076077Z
2022-06-14T00:03:36.6076543Z 119 packages are looking for funding
2022-06-14T00:03:36.6077418Z   run `npm fund` for details
2022-06-14T00:03:36.6077870Z
2022-06-14T00:03:36.6078504Z found 13 vulnerabilities (1 low, 1 moderate, 10 high, 1 critical)
2022-06-14T00:03:36.6079715Z   run `npm audit fix` to fix them, or `npm audit` for details
2022-06-14T00:03:36.6080798Z audited 2040 packages in 10.397s
2022-06-14T00:03:36.6081277Z
2022-06-14T00:03:36.6081742Z 119 packages are looking for funding
2022-06-14T00:03:36.6082616Z   run `npm fund` for details
2022-06-14T00:03:36.6083065Z
2022-06-14T00:03:36.6083631Z found 13 vulnerabilities (1 low, 1 moderate, 10 high, 1 critical)
2022-06-14T00:03:36.6084752Z   run `npm audit fix` to fix them, or `npm audit` for details
2022-06-14T00:03:36.6086762Z DEPRECATION: Node v10.19.0 is no longer supported by Ember CLI. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-14T00:03:36.6089162Z WARNING: Node v10.19.0 is not tested against Ember CLI on your platform. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-14T00:03:36.6090607Z Environment: production
2022-06-14T00:03:36.6092239Z rake stderr: npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
2022-06-14T00:03:36.6094307Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6096022Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
2022-06-14T00:03:36.6097906Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6098928Z
2022-06-14T00:03:36.6100180Z npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-06-14T00:03:36.6102319Z npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-06-14T00:03:36.6104179Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
2022-06-14T00:03:36.6106057Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6108151Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
2022-06-14T00:03:36.6110220Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6111265Z
2022-06-14T00:03:36.6111821Z DEPRECATION: `bowerDependencies` has been deprecated.
2022-06-14T00:03:36.6113744Z If you still need access to the project's Bower dependencies, you will have to manually resolve the project's `bower.json` file instead. [ID: ember-cli.project.bower-dependencies]
2022-06-14T00:03:36.6115828Z at getStackTrace (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:99:15)
2022-06-14T00:03:36.6117688Z at deprecate (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:77:8)
2022-06-14T00:03:36.6119606Z at Project.bowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/models/project.js:412:5)
2022-06-14T00:03:36.6121936Z at EmberCLIDependencyChecker.normalizedBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:138:44)
2022-06-14T00:03:36.6124453Z at EmberCLIDependencyChecker.readBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:148:39)
2022-06-14T00:03:36.6127094Z at EmberCLIDependencyChecker.checkDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:43:28)
2022-06-14T00:03:36.6129295Z at Class.init (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/index.js:18:25)
2022-06-14T00:03:36.6131268Z at Class.superWrapper [as init] (/var/www/violet/releases/20220613235541/client/node_modules/core-object/lib/assign-properties.js:34:20)
2022-06-14T00:03:36.6133159Z at new CoreObject (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:9:15)
2022-06-14T00:03:36.6134922Z at new Class (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:21:5)
2022-06-14T00:03:36.6136106Z - Building
2022-06-14T00:03:36.6136926Z - Building
2022-06-14T00:03:36.6137752Z - building...
2022-06-14T00:03:36.6138530Z Killed
2022-06-14T00:03:36.6138945Z
2022-06-14T00:03:36.6138966Z
2022-06-14T00:03:36.6139388Z Caused by:
2022-06-14T00:03:36.6140331Z SSHKit::Command::Failed: rake exit status: 137
2022-06-14T00:03:36.6141515Z rake stdout: ><EMAIL_ADDRESS>postinstall node_modules/core-js
2022-06-14T00:03:36.6142747Z > node -e "try{require('./postinstall')}catch(e){}"
2022-06-14T00:03:36.6143430Z
2022-06-14T00:03:36.6144550Z Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
2022-06-14T00:03:36.6145430Z
2022-06-14T00:03:36.6146410Z The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
2022-06-14T00:03:36.6147815Z > https://opencollective.com/core-js
2022-06-14T00:03:36.6148976Z > https://www.patreon.com/zloirock
2022-06-14T00:03:36.6149540Z
2022-06-14T00:03:36.6150489Z Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
2022-06-14T00:03:36.6151304Z
2022-06-14T00:03:36.6151963Z added 2036 packages from 844 contributors and audited 2040 packages in 26.286s
2022-06-14T00:03:36.6152683Z
2022-06-14T00:03:36.6153144Z 119 packages are looking for funding
2022-06-14T00:03:36.6154034Z   run `npm fund` for details
2022-06-14T00:03:36.6154488Z
2022-06-14T00:03:36.6155059Z found 13 vulnerabilities (1 low, 1 moderate, 10 high, 1 critical)
2022-06-14T00:03:36.6156201Z   run `npm audit fix` to fix them, or `npm audit` for details
2022-06-14T00:03:36.6157246Z audited 2040 packages in 10.397s
2022-06-14T00:03:36.6157716Z
2022-06-14T00:03:36.6158173Z 119 packages are looking for funding
2022-06-14T00:03:36.6159057Z   run `npm fund` for details
2022-06-14T00:03:36.6159502Z
2022-06-14T00:03:36.6160066Z found 13 vulnerabilities (1 low, 1 moderate, 10 high, 1 critical)
2022-06-14T00:03:36.6161181Z   run `npm audit fix` to fix them, or `npm audit` for details
2022-06-14T00:03:36.6163188Z DEPRECATION: Node v10.19.0 is no longer supported by Ember CLI. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-14T00:03:36.6165606Z WARNING: Node v10.19.0 is not tested against Ember CLI on your platform. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-14T00:03:36.6167044Z Environment: production
2022-06-14T00:03:36.6168655Z rake stderr: npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
2022-06-14T00:03:36.6170747Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6172470Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
2022-06-14T00:03:36.6174326Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6175482Z
2022-06-14T00:03:36.6176738Z npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-06-14T00:03:36.6178973Z npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-06-14T00:03:36.6180630Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
2022-06-14T00:03:36.6182503Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6184797Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
2022-06-14T00:03:36.6186846Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6187882Z
2022-06-14T00:03:36.6188415Z DEPRECATION: `bowerDependencies` has been deprecated.
2022-06-14T00:03:36.6190361Z If you still need access to the project's Bower dependencies, you will have to manually resolve the project's `bower.json` file instead. [ID: ember-cli.project.bower-dependencies]
2022-06-14T00:03:36.6192438Z at getStackTrace (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:99:15)
2022-06-14T00:03:36.6194282Z at deprecate (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:77:8)
2022-06-14T00:03:36.6196221Z at Project.bowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/models/project.js:412:5)
2022-06-14T00:03:36.6198559Z at EmberCLIDependencyChecker.normalizedBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:138:44)
2022-06-14T00:03:36.6201129Z at EmberCLIDependencyChecker.readBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:148:39)
2022-06-14T00:03:36.6203611Z at EmberCLIDependencyChecker.checkDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:43:28)
2022-06-14T00:03:36.6205708Z at Class.init (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/index.js:18:25)
2022-06-14T00:03:36.6207658Z at Class.superWrapper [as init] (/var/www/violet/releases/20220613235541/client/node_modules/core-object/lib/assign-properties.js:34:20)
2022-06-14T00:03:36.6209527Z at new CoreObject (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:9:15)
2022-06-14T00:03:36.6211289Z at new Class (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:21:5)
2022-06-14T00:03:36.6220895Z - Building
2022-06-14T00:03:36.6221915Z - Building
2022-06-14T00:03:36.6222758Z - building...
2022-06-14T00:03:36.6223682Z Killed
2022-06-14T00:03:36.6224106Z
2022-06-14T00:03:36.6224607Z Tasks: TOP => deploy:assets:precompile
2022-06-14T00:03:36.6225727Z (See full trace by running task with --trace)
2022-06-14T00:03:36.6227201Z The deploy has failed with an error: Exception while executing as ubuntu@***: rake exit status: 137
2022-06-14T00:03:36.6228634Z rake stdout: ><EMAIL_ADDRESS>postinstall node_modules/core-js
2022-06-14T00:03:36.6229861Z > node -e "try{require('./postinstall')}catch(e){}"
2022-06-14T00:03:36.6230433Z
2022-06-14T00:03:36.6231533Z Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
2022-06-14T00:03:36.6232415Z
2022-06-14T00:03:36.6233398Z The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
2022-06-14T00:03:36.6234998Z > https://opencollective.com/core-js
2022-06-14T00:03:36.6236160Z > https://www.patreon.com/zloirock
2022-06-14T00:03:36.6236731Z
2022-06-14T00:03:36.6237678Z Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
2022-06-14T00:03:36.6238557Z
2022-06-14T00:03:36.6239268Z added 2036 packages from 844 contributors and audited 2040 packages in 26.286s
2022-06-14T00:03:36.6239982Z
2022-06-14T00:03:36.6240462Z 119 packages are looking for funding
2022-06-14T00:03:36.6241492Z   run `npm fund` for details
2022-06-14T00:03:36.6241945Z
2022-06-14T00:03:36.6242514Z found 13 vulnerabilities (1 low, 1 moderate, 10 high, 1 critical)
2022-06-14T00:03:36.6243655Z   run `npm audit fix` to fix them, or `npm audit` for details
2022-06-14T00:03:36.6244721Z audited 2040 packages in 10.397s
2022-06-14T00:03:36.6245196Z
2022-06-14T00:03:36.6245663Z 119 packages are looking for funding
2022-06-14T00:03:36.6246536Z   run `npm fund` for details
2022-06-14T00:03:36.6246987Z
2022-06-14T00:03:36.6247517Z found 13 vulnerabilities (1 low, 1 moderate, 10 high, 1 critical)
2022-06-14T00:03:36.6248587Z   run `npm audit fix` to fix them, or `npm audit` for details
2022-06-14T00:03:36.6250593Z DEPRECATION: Node v10.19.0 is no longer supported by Ember CLI. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-14T00:03:36.6252992Z WARNING: Node v10.19.0 is not tested against Ember CLI on your platform. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-14T00:03:36.6254428Z Environment: production
2022-06-14T00:03:36.6256034Z rake stderr: npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
2022-06-14T00:03:36.6258089Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6259812Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
2022-06-14T00:03:36.6261664Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6262677Z
2022-06-14T00:03:36.6264091Z npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-06-14T00:03:36.6266237Z npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2022-06-14T00:03:36.6267862Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
2022-06-14T00:03:36.6269724Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6271818Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
2022-06-14T00:03:36.6273819Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2022-06-14T00:03:36.6274831Z
2022-06-14T00:03:36.6275369Z DEPRECATION: `bowerDependencies` has been deprecated.
2022-06-14T00:03:36.6277316Z If you still need access to the project's Bower dependencies, you will have to manually resolve the project's `bower.json` file instead. [ID: ember-cli.project.bower-dependencies]
2022-06-14T00:03:36.6279361Z at getStackTrace (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:99:15)
2022-06-14T00:03:36.6281188Z at deprecate (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:77:8)
2022-06-14T00:03:36.6283253Z at Project.bowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/models/project.js:412:5)
2022-06-14T00:03:36.6285601Z at EmberCLIDependencyChecker.normalizedBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:138:44)
2022-06-14T00:03:36.6288237Z at EmberCLIDependencyChecker.readBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:148:39)
2022-06-14T00:03:36.6290714Z at EmberCLIDependencyChecker.checkDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:43:28)
2022-06-14T00:03:36.6292776Z at Class.init (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/index.js:18:25)
2022-06-14T00:03:36.6294724Z at Class.superWrapper [as init] (/var/www/violet/releases/20220613235541/client/node_modules/core-object/lib/assign-properties.js:34:20)
2022-06-14T00:03:36.6296605Z at new CoreObject (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:9:15)
2022-06-14T00:03:36.6298338Z at new Class (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:21:5)
2022-06-14T00:03:36.6299498Z - Building
2022-06-14T00:03:36.6300295Z - Building
2022-06-14T00:03:36.6301099Z - building...
2022-06-14T00:03:36.6301876Z Killed
2022-06-14T00:03:36.6302290Z
2022-06-14T00:03:36.6302309Z
2022-06-14T00:03:36.6302686Z ** DEPLOY FAILED
2022-06-14T00:03:36.6303888Z ** Refer to log/capistrano.log for details. Here are the last 20 lines:
2022-06-14T00:03:36.6304575Z
2022-06-14T00:03:36.6304594Z
2022-06-14T00:03:36.6305093Z   run `npm audit fix` to fix them, or `npm audit` for details
2022-06-14T00:03:36.6305712Z
2022-06-14T00:03:36.6306288Z  DEBUG [d61f53b8] 	DEPRECATION: `bowerDependencies` has been deprecated.
2022-06-14T00:03:36.6306985Z
2022-06-14T00:03:36.6308343Z If you still need access to the project's Bower dependencies, you will have to manually resolve the project's `bower.json` file instead. [ID: ember-cli.project.bower-dependencies]
2022-06-14T00:03:36.6309383Z
2022-06-14T00:03:36.6310456Z  DEBUG [d61f53b8] 	at getStackTrace (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:99:15)
2022-06-14T00:03:36.6311369Z
2022-06-14T00:03:36.6312373Z at deprecate (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/debug/deprecate.js:77:8)
2022-06-14T00:03:36.6313195Z
2022-06-14T00:03:36.6314295Z at Project.bowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli/lib/models/project.js:412:5)
2022-06-14T00:03:36.6315164Z
2022-06-14T00:03:36.6316620Z at EmberCLIDependencyChecker.normalizedBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:138:44)
2022-06-14T00:03:36.6317753Z
2022-06-14T00:03:36.6319160Z at EmberCLIDependencyChecker.readBowerDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:148:39)
2022-06-14T00:03:36.6320251Z
2022-06-14T00:03:36.6321629Z at EmberCLIDependencyChecker.checkDependencies (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/lib/dependency-checker.js:43:28)
2022-06-14T00:03:36.6322684Z
2022-06-14T00:03:36.6323704Z at Class.init (/var/www/violet/releases/20220613235541/client/node_modules/ember-cli-dependency-checker/index.js:18:25)
2022-06-14T00:03:36.6324538Z
2022-06-14T00:03:36.6325656Z at Class.superWrapper [as init] (/var/www/violet/releases/20220613235541/client/node_modules/core-object/lib/assign-properties.js:34:20)
2022-06-14T00:03:36.6326535Z
2022-06-14T00:03:36.6327550Z at new CoreObject (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:9:15)
2022-06-14T00:03:36.6328348Z
2022-06-14T00:03:36.6329294Z at new Class (/var/www/violet/releases/20220613235541/client/node_modules/core-object/core-object.js:21:5)
2022-06-14T00:03:36.6330208Z
2022-06-14T00:03:36.6331547Z  DEBUG [d61f53b8] 	DEPRECATION: Node v10.19.0 is no longer supported by Ember CLI. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-14T00:03:36.6332697Z
2022-06-14T00:03:36.6334069Z  DEBUG [d61f53b8] 	WARNING: Node v10.19.0 is not tested against Ember CLI on your platform. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
2022-06-14T00:03:36.6335167Z
2022-06-14T00:03:36.6335625Z  DEBUG [d61f53b8] 	- Building
2022-06-14T00:03:36.6336078Z
2022-06-14T00:03:36.6336533Z  DEBUG [d61f53b8] 	Environment: production
2022-06-14T00:03:36.6337069Z
2022-06-14T00:03:36.6337511Z  DEBUG [d61f53b8] 	- Building
2022-06-14T00:03:36.6337947Z
2022-06-14T00:03:36.6338433Z  DEBUG [d61f53b8] 	- building...
2022-06-14T00:03:36.6338937Z
2022-06-14T00:03:36.6339329Z  DEBUG [d61f53b8] 	Killed
2022-06-14T00:03:36.6339772Z
2022-06-14T00:03:36.6365480Z ##[error]Error: The process '/opt/hostedtoolcache/Ruby/2.6.6/x64/bin/bundle' failed with exit code 1
2022-06-14T00:03:36.6447293Z Post job cleanup.
2022-06-14T00:03:37.2331090Z The IP <IP_ADDRESS> is removed
2022-06-14T00:03:37.2473021Z Post job cleanup.
2022-06-14T00:03:37.3882411Z [command]/usr/bin/git version
2022-06-14T00:03:37.3953662Z git version 2.36.1
2022-06-14T00:03:37.4000203Z Temporarily overriding HOME='/home/runner/work/_temp/30006f6f-9918-4896-be86-0267a0ab3889' before making global git config changes
2022-06-14T00:03:37.4002059Z Adding repository directory to the temporary git global config as a safe directory
2022-06-14T00:03:37.4006789Z [command]/usr/bin/git config --global --add safe.directory /home/runner/work/violet_rails/violet_rails
2022-06-14T00:03:37.4074934Z [command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
2022-06-14T00:03:37.4128550Z [command]/usr/bin/git submodule foreach --recursive git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :
2022-06-14T00:03:37.4410261Z [command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
2022-06-14T00:03:37.4461889Z http.https://github.com/.extraheader
2022-06-14T00:03:37.4472425Z [command]/usr/bin/git config --local --unset-all http.https://github.com/.extraheader
2022-06-14T00:03:37.4528043Z [command]/usr/bin/git submodule foreach --recursive git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :
2022-06-14T00:03:37.5074801Z Cleaning up orphan processes


Implement new architectures for deep RL

DDPG, A2C, etc other deep reinforcement learning models (value vs policy, actor critic, critic only actor only)
Research paper will be attached below for references, 1-2 more will be a great place to start
Quantitively comparing the results and drawing inspiration

@SPChrisW @endernoke here is a document that contains more instructions, pls have a look!
https://docs.google.com/document/d/1Je4PoiwdrvhtXkevswysE7AeqvMultIdIlN4xZEQWOg/edit?tab=t.0


RFC: Source generators

Using AddonHudLayoutScreen for example.
How are vfuncs accessed while still retaining access to the vtbl? Currently the vtbl is in AtkUnitBase.
AddonHudLayoutScreen should get its own vtbl for its own specific functions. Since we don't necessarily have knowledge of what is overridden like in IDA, it'll likely need to inherit all of AtkUnitBase's names too.
Should vfuncs be differentiated from funcs?
Should we get into the including delegate business?
[VTable(0x1418106A0)].   // This I could like
[Func("AddonOverlayMouseMovedEvent", 0x141023730)]    // not a fan of looking these up by string
public unsafe struct AddonHudLayoutScreen { <stuff> }

public unsafe struct AddonHudLayoutScreen
{
    ...
    public static class VTable
    {
        public static readonly IntPtr Address = new IntPtr(0xdeadbeef);
        public static IntPtr this[int index] => Address + 8*index;  // Although you cant have static indexers.
    }
    public static class Functions
    {
        public static readonly IntPtr AddonOverlayMouseMovedEventAddress = new IntPtr(0x141023730);
    }
    public static class Delegates
    {  // How would these be stored, as plaintext in the data.yml?
        public delegate void AddonOverlayMouseMovedEventDelegate(stuff);
    }
}

Some sort of initialize function would also need to exist, so as to feed in the Scanner.Module.BaseAddress ptr, so the updated offsets can be calculated.

ffs. how many times am i going to login and do stuff with my work account

Can delete it and repost if you want.

Anyway.
vtbl addresses dont need to be in the code. You just read them from the current object. This allows polymorphism to actually work.
Function signatures I haven't really thought about. One option is to store them in a header file as actual C++ function signatures then use something like CppSharp's parser to read them during codegen.
It should be possible to use a static initializer to store the game's base address when the dll loads, unless I'm mistaken.

C#9 has [ModuleInitializer]
Prior to that, Fody has ModuleInit
Or the option of a static constructor on something potentially.

Been thinking, generating and stuffing offsets in code is handy dandy, but requires rebuilding every patch. What if it gets generated, but packs data.yml with the dll. If out of date (since ffxiv.ver is in the file now) reach out to github, pull down a new data, if good, update the offsets. Won't be able to generate anything that's new or not, but at the very least it'll have good offsets.

proof of concept: https://github.com/daemitus/FFXIVClientStructs/tree/sourcegen
Pretty sure it forces the TFM to netstandard2.0, which should? leave us compatible with net472. Haven't tried loading it into XL though. I can't find it again, but I swear some Msft doc said netstandard2.0 was on par with net45.

re: Linking original structs to generated data.

1: some stupid getter function on a static class. boo
2: extension class adding a getter to each struct. maybe
3: weave them into each class with something (fody?). My favorite idea, requires adding another thing onto the dependency stack though. Source generators are purely additive, afaik it wouldn't be possible to add to an existing object this way.


Fix link

Hi.
This is a request to correct a link.
Best regards.

Thanks @kojix2. Sorry I missed this before, it was fixed alongside other changes in https://github.com/kowal/ruby-changelog/commit/e8e1f63477d7297cf95bf1902e7e78a695fb653b

@kojix2 Also, please note, that if you want to fix/improve some other things, please do the steps described in https://github.com/kowal/ruby-changelog#new-ruby-version. Cheers.


add haascv module & haascv demo

Signed-off-by: zilin.zxl<EMAIL_ADDRESS>Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Additional context

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zilin.zxl seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add WorkersManager.inspect_worker/2

It provides information about a giving worker based on the job id

Changes Unknown when pulling 55d3c8f761c29fc88f4c4f603ea4b630d4c2e531 on add-inspect-worker into ** on master**.


Inputs: Add BlurAsync()

Description
We have FocusAsync method to focus on inputs. But we doesn't have the opposite method, blur.
Programmatically blur on element can only be done with js. So we need to add 6 lines of js code. I think we really need this, because blur is one of the most common methods and implementing blur outside of Mud code is really needs lots of work.
With this PR users can call BlurAsync and can lose focus programmatically.
This PR primarily affects text field and numeric field. It also can used with autocomplete, select and pickers, but users should be careful of using blur with them. An example, blur only blurs from input, so users also need to write code that closes the autocomplete's popover by manually.
Example 1: The left text field blurs when mouse out
https://user-images.githubusercontent.com/78308169/180099094-f95fa68b-4603-462f-aa12-21af7480409b.mp4
Example 2: The left Autocomplete blurs when user presses "a" key
https://user-images.githubusercontent.com/78308169/180099144-48b17bba-5d0e-477f-a38c-617f5f28431e.mp4
How Has This Been Tested?
Js code can't be tested directly, but manually tried for common situations. Actually blur doesn't affect other methods, so the only risk is a bad working blur method. This doesn't break any event or something like.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

Thanks!

Thanks for this. I am struggling to find examples on how to use this, as the docs do not seem to show any. Would you be able to point a resource? Thank you.

Thanks for this. I am struggling to find examples on how to use this, as the docs do not seem to show any. Would you be able to point a resource? Thank you.

You can use it standart method usage with ref. Like:
<MudTextField @ref="_textField" />

@code{
    MudTextField<string> _textField;

    private async Task SomeMethod()
    {
        await _textField.BlurAsync();
    }
}

Thank you. I had tried exactly that, but I'm constantly getting a null exception. The ref to the MudTextField is not null.

Thank you @mckaragoz. I had tried exactly that, but I'm constantly getting a null exception. The ref to the MudTextField is not null.

You can look at this example, working for me https://try.mudblazor.com/snippet/wkQdkwQwhTIdXilz

Thank you @mckaragoz . I'm still getting the null exception in my case. I'm not able to pinpoint the issue, but as I have another separate hard-to-track issue with the MudTextField, I think it may be a bug with it. Appreciated your help, thanks.


Immunomodulator data file - multiple values

The file im_expr_df has instances where more than one gene expression levels is given
filter(im_expr_df,ParticipantBarcode=="TCGA-BH-A1FC",Symbol=="IL13")
# A tibble: 2 x 3
  ParticipantBarcode Symbol normalized_count
  <chr>              <chr>             <dbl>
1 TCGA-BH-A1FC       IL13              0.588
2 TCGA-BH-A1FC       IL13              6.51

Digging into this it turns out that this due to expression values in the expression matrix (EB++) being available available aliquots, and that participant barcode has not been associated with the representative Aliquot.
TCGA-BH-A1FC-01A-11R-A13Q-07 TCGA-BH-A1FC-11A-32R-A13Q-07
IL13                       0.5885                       6.5089

The representative Aliquot is TCGA-BH-A1FC-01A-11R-A13Q-07 so only 0.5885 should be in im_expr_df

Attached candidate replacement file
im_expr_df.feather.gz

@vthorsson I noticed the same issue and will move this to the repo

Uploaded replacement file may still have had issue with duplicates
New candidate file recreated
im_expr_df.July2019.feather.gz
md5 e4725bc679755c480e1ab5ae84c93420
( un-gz'ed)

@heimannch , will you be able to sanity check

This file meets what we are currently testing for:

there are no duplicated rows;
I was able to merge expression data with the GenExp_All_CKine_genes.tsv from the cytokine-network-dev repo.

Good to hear @heimannch , and thanks for checking.  Please use this version in your branch for later merge into develop.

As I was preparing the file to include it as the im__expr_df.feather file, I've noticed that there are 228 participants IDs missing from this new version, such as:
  ParticipantBarcode
  <chr>
1 TCGA-06-0681
2 TCGA-44-6144
3 TCGA-55-6969
4 TCGA-91-6831
5 TCGA-BR-7704
6 TCGA-EJ-A8FO

Full list of missing participantsBarcodes in im_expr_df.July2019.feather.gz, when compared to im_expr_df.feather in the develop branch: missing_partID.csv.gz
It is also worth mentioning that this doesn't affect the cytokine_network repo and issue #155, as none of the missing ParticipantBarcode is present in the data in GenExp_All_CKine_genes.tsv.

@heimannch I believe those barcodes are ones that do not have a Representative_Expression_Matrix_AliquotBarcode, thus values that may have been filtered for some other reasons.  Are you able to check that ?

Yes, all those barcodes do not have a Representative_Expression_Matrix_AliquotBarcode. There are in total (from fmx_df) 1387 barcodes missing this annotation, and only those 228 remained in the im__expr_df.feather file. I assume that the other 1159 were filtered in some previous step.
If the immunomodulators gene expression data is supposed to have barcodes that have a Representative_Expression_Matrix_AliquotBarcode, the file im_expr_df.July2019.feather.gz is ok to be used.

Yes, correct , we are currently requiring that expression data shown in the app have a Representative_Expression_Matrix_AliquotBarcode, so looks like we are good. Thanks for checking this, @heimannch

Great! I just pushed a commit (4641f098522d1bca6ff5fef87df53cd0b7d52828) to the cytokine-network branch updating the file.

@heimannch Please close this issue if you think that is appropriate. Alternately we could keep an eye on it for the release (there is even a label for that !)

I believe it is better to wait until the updated file is merged into develop before closing this issue. Let's keep an eye on it!

@vthorsson All other issues have been resolved, could you confirm this has been merged into develop?

@heimannch are you able to work with @andrewelamb to get the version you have into 1.2 ? (we know it would make it into 1.3)

The updated immunomodulator data file is now in the develop branch.I will close this issue.


Build fails after migrating from v11 to v15

Command
serve, update
Is this a regression?

[x] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
It was working on angular 11
Description
./src/main.ts - Error: Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):
Error: Emit attempted before Angular Webpack plugin initialization.
./src/polyfills.ts - Error: Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):
Error: Emit attempted before Angular Webpack plugin initialization.
Minimal Reproduction
"dependencies": {
"@angular-material-extensions/password-strength": "^12.0.2",
"@angular-redux/store": "^10.0.0",
"@angular/animations": "^15.0.4",
"@angular/cdk": "^15.0.3",
"@angular/common": "^15.0.4",
"@angular/compiler": "^15.0.4",
"@angular/core": "^15.0.4",
"@angular/forms": "^15.0.4",
"@angular/language-service": "^15.0.4",
"@angular/material": "^15.0.3",
"@angular/platform-browser": "^15.0.4",
"@angular/platform-browser-dynamic": "^15.0.4",
"@angular/router": "^15.0.4",
"@fortawesome/angular-fontawesome": "^0.12.0",
"@fortawesome/fontawesome-svg-core": "^6.2.1",
"@fortawesome/free-regular-svg-icons": "^6.2.1",
"@fortawesome/free-solid-svg-icons": "^6.2.1",
"@ng-bootstrap/ng-bootstrap": "^14.0.0",
"@ng-select/ng-select": "10.0.1",
"@ngx-loading-bar/core": "^6.0.2",
"@ngx-loading-bar/router": "^6.0.2",
"@ngx-translate/core": "^14.0.0",
"@ngx-translate/http-loader": "^7.0.0",
"@swimlane/ngx-charts": "^20.1.2",
"angular-code-input": "^1.3.2",
"angular-font-awesome": "^3.1.2",
"angular-google-tag-manager": "^1.7.0",
"angular2-notifications": "^12.0.0",
"angular2-text-mask": "^9.0.0",
"angularx-qrcode": "^15.0.1",
"animate-sass": "^0.8.2",
"bootstrap": "5.2.3",
"bootstrap-icons": "^1.10.2",
"file-saver": "^2.0.2",
"flag-icon-css": "^3.5.0",
"font-awesome": "^4.7.0",
"ionicons": "^6.0.4",
"jquery": "^3.6.3",
"jsencrypt": "^3.3.1",
"json-server": "^0.17.1",
"jspdf": "^2.2.0",
"linearicons": "^1.0.2",
"loaders.css": "^0.1.2",
"moment": "^2.29.4",
"ng-bootstrap-form-validation": "^9.0.0",
"ng-otp-input": "^1.8.5",
"ng-recaptcha": "^11.0.0",
"ng-select-autocomplete": "^1.4.1",
"ngx-bootstrap": "^10.2.0",
"ngx-clipboard": "^15.1.0",
"ngx-daterangepicker-material": "^6.0.4",
"ngx-device-detector": "^4.0.1",
"ngx-dropzone": "^3.1.0",
"ngx-flip": "^9.0.0",
"ngx-infinite-scroll": "^15.0.0",
"ngx-loading": "^14.0.0",
"ngx-mat-select-search": "^7.0.0",
"ngx-pagination": "^6.0.3",
"ngx-perfect-scrollbar": "^10.0.1",
"ngx-print": "^1.3.0",
"ngx-select-dropdown": "^3.2.0",
"ngx-slick-carousel": "^0.6.0",
"ngx-swiper-wrapper": "^10.0.0",
"ngx-textarea-autosize": "^2.0.3",
"ngx-toastr": "^16.0.1",
"ngx-ui-loader": "^13.0.0",
"ngx-ui-switch": "^14.0.3",
"pe7-icon": "^1.0.4",
"redux": "4.2.0",
"redux-devtools-extension": "^2.13.9",
"rxjs": "^7.8.0",
"sweetalert2": "^11.6.16",
"swiper": "^8.4.5",
"ts-md5": "^1.3.1",
"uuid": "^9.0.0",
"webpack-bundle-analyzer": "^4.7.0",
"xlsx": "^0.18.5",
"zone.js": "~0.12.0"
},
"devDependencies": {
"@angular-devkit/build-angular": "^15.0.4",
"@angular/cli": "^15.0.4",
"@angular/compiler-cli": "^15.0.4",
"@angular/localize": "^15.0.4",
"@fortawesome/fontawesome-free": "^6.2.1",
"codelyzer": "^6.0.2",
"jasmine-core": "~4.5.0",
"jasmine-spec-reporter": "~6.0.0",
"karma": "~6.4.1",
"karma-chrome-launcher": "~3.1.0",
"karma-coverage-istanbul-reporter": "^3.0.3",
"karma-jasmine": "~5.1.0",
"karma-jasmine-html-reporter": "^2.0.0",
"protractor": "~7.0.0",
"ts-node": "~10.9.1",
"tslint": "~6.1.3",
"typescript": "^4.8.2"
}
Exception or Error
./src/main.ts - Error: Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):
Error: Emit attempted before Angular Webpack plugin initialization.
./src/polyfills.ts - Error: Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):
Error: Emit attempted before Angular Webpack plugin initialization.

Please help to fix the issue.

| Generating browser application bundles (phase: setup)...Warning: Entry point 'ngx-swiper-wrapper' contains deep imports into 'D:/Codebase/noqodi-apps/noqodi-web-revamp/noqodi-ui/noqodi-customer-angular-ui/noqodi-customer-angular-u
i-frontend/src/main/ngapp_latest/node_modules/swiper/types/swiper-events'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
Warning: Entry point 'angular2-text-mask' contains deep imports into 'D:/Codebase/noqodi-apps/noqodi-web-revamp/noqodi-ui/noqodi-customer-angular-ui/noqodi-customer-angular-ui-frontend/src/main/ngapp_latest/node_modules/text-mask-co
re/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
√ Browser application bundle generation complete.
Initial Chunk Files   | Names         |  Raw Size
styles.css, styles.js | styles        |   1.49 MB |
polyfills.js          | polyfills     | 208.80 kB |
vendor.js             | vendor        | 208.04 kB |
scripts.js            | scripts       | 146.87 kB |
runtime.js            | runtime       |   6.53 kB |
main.js               | main          |   1.00 kB |
                  | Initial Total |   2.05 MB

Build at: 2022-12-26T07:16:20.398Z - Hash: 4a49a6a23a4453c6 - Time: 42102ms
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
Angular Material themes should be created from a map containing the keys "color", "typography", and "density". The color value should be a map containing the palette values for "primary", "accent", and "warn". See https://material.a
ngular.io/guide/theming for more information.
<EMAIL_ADDRESS>185:5  define-light-theme()
src\assets\components\material_base.scss 88:27                  @import
src\assets\base.scss 62:9                                        @import
src\styles.scss 1:9                                              root stylesheet
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
Deprecation Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($custom-control-indicator-size, 2) or calc($custom-control-indicator-size / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
src\assets\components\bootstrap4_variables.scss 559:49  @import
src\assets\base.scss 5:9                                 @import
src\styles.scss 1:9                                      root stylesheet
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
Deprecation Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($input-height-inner * 3, 4) or calc($input-height-inner * 3 / 4)
More info and automated migrator: https://sass-lang.com/d/slash-div
src\assets\components\bootstrap4_variables.scss 577:45  @import
src\assets\base.scss 5:9                                 @import
src\styles.scss 1:9                                      root stylesheet
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
Deprecation Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($input-height-inner, 2) or calc($input-height-inner / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
src\assets\components\bootstrap4_variables.scss 579:46  @import
src\assets\base.scss 5:9                                 @import
src\styles.scss 1:9                                      root stylesheet
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
Deprecation Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($input-height-inner, 2) or calc($input-height-inner / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
src\assets\components\bootstrap4_variables.scss 579:72  @import
src\assets\base.scss 5:9                                 @import
src\styles.scss 1:9                                      root stylesheet
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
Deprecation Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($spacer, 2) or calc($spacer / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
src\assets\components\bootstrap4_variables.scss 303:31  @import
src\assets\base.scss 5:9                                 @import
src\styles.scss 1:9                                      root stylesheet
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
148 repetitive deprecation warnings omitted.
Run in verbose mode to see all warnings.
null
./src/main.ts - Error: Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):
Error: Emit attempted before Angular Webpack plugin initialization.
./src/polyfills.ts - Error: Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):
Error: Emit attempted before Angular Webpack plugin initialization.
Error: Failed to initialize Angular compilation - The target entry-point "ngx-swiper-wrapper" has missing dependencies:

swiper/bundle

** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
× Failed to compile.
√ Browser application bundle generation complete.
Initial Chunk Files | Names   | Raw Size
runtime.js          | runtime |  6.53 kB |
5 unchanged chunks
Build at: 2022-12-26T07:16:31.541Z - Hash: c3ad6d980cf1dfe7 - Time: 10024ms
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
Angular Material themes should be created from a map containing the keys "color", "typography", and "density". The color value should be a map containing the palette values for "primary", "accent", and "warn". See https://material.a
ngular.io/guide/theming for more information.
<EMAIL_ADDRESS>185:5  define-light-theme()
src\assets\components\material_base.scss 88:27                  @import
src\assets\base.scss 62:9                                        @import
src\styles.scss 1:9                                              root stylesheet
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
Deprecation Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($custom-control-indicator-size, 2) or calc($custom-control-indicator-size / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
src\assets\components\bootstrap4_variables.scss 559:49  @import
src\assets\base.scss 5:9                                 @import
src\styles.scss 1:9                                      root stylesheet
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
Deprecation Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($input-height-inner * 3, 4) or calc($input-height-inner * 3 / 4)
More info and automated migrator: https://sass-lang.com/d/slash-div
src\assets\components\bootstrap4_variables.scss 577:45  @import
src\assets\base.scss 5:9                                 @import
src\styles.scss 1:9                                      root stylesheet
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
Deprecation Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($input-height-inner, 2) or calc($input-height-inner / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
src\assets\components\bootstrap4_variables.scss 579:46  @import
src\assets\base.scss 5:9                                 @import
src\styles.scss 1:9                                      root stylesheet
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
Deprecation Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($input-height-inner, 2) or calc($input-height-inner / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
src\assets\components\bootstrap4_variables.scss 579:72  @import
src\assets\base.scss 5:9                                 @import
src\styles.scss 1:9                                      root stylesheet
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
Deprecation Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.
Recommendation: math.div($spacer, 2) or calc($spacer / 2)
More info and automated migrator: https://sass-lang.com/d/slash-div
src\assets\components\bootstrap4_variables.scss 303:31  @import
src\assets\base.scss 5:9                                 @import
src\styles.scss 1:9                                      root stylesheet
./src/styles.scss - Warning: Module Warning (from ./node_modules/sass-loader/dist/cjs.js):
148 repetitive deprecation warnings omitted.
Run in verbose mode to see all warnings.
null
./src/main.ts - Error: Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):
Error: Emit attempted before Angular Webpack plugin initialization.
./src/polyfills.ts - Error: Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):
Error: Emit attempted before Angular Webpack plugin initialization.

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

Closing as no reproduction was provided.


.html is stripped along with query params from URL

When visiting localhost:3000/foo.html?query=bar serve strips the .html?query=bar
Library version of serve is 14.0.1

Original issue: https://github.com/vercel/serve/issues/732
Can't use serve at the moment. It breaks apps.

I think setting cleanUrls option to false stops this from happening.


Could we have a "CBC" the cipher list to control enable or disable all CBC mode ciphers?

There is raising need to disable all CBC mode ciphers, but adding them one by one is really tedious, could we have a "CBC/GCM/CCM" mode control in the cipher list, so '!CBC' would disable all CBC mode cipher?

I do like this:
ECDHE+AESGCM:ECDHE+ARIAGCM:DHE+AESGCM:DHE+ARIAGCM:!DSS:@STRENGTH
It's not so tedious. As you see i'm including only GCM ciphers 😃

Marking as inactive, to be closed at the end of 3.4 dev barring further input


Update modifying_package_json.md

The first section in "Other helpful commands" contradicts the paragraph i removed here

This is not entirely correct.  For example, suppose you have a package.json like this:
  "dependencies": {
    "foo": "^1.2.3"
  }

...and your shrinkwrap file (e.g. pnpm-lock.yaml) stores version 1.2.9 for foo.  And suppose the released versions in the NPM registry look like this:
1.2.2, 1.2.3, 1.2.4, 1.3.0, 1.3.1, 2.0.0, 2.0.1
The "Other helpful commands" text says:

Normally rush update only makes the minimal incremental changes necessary to satisfy the the project package.json files. If you want to update everything to the latest version, you would do this:
# This effectively deletes the old shrinkwrap file and re-solves everything
# using the latest compatible versions
$ rush update --full

The above text is talking about upgrading pnpm-lock.yaml to version 1.3.1.

Upgrading to newer versions of your NPM packages
Today, Rush does not yet have an integrated equivalent of npm update or npm-check-updates.  So you if you want to update the SemVer patterns across all your package.json files, you'll need to use an external tool.

The above text is talking about upgrading package.json to look like this:
  "dependencies": {
    "foo": "^2.0.1"
  }

So they are really discussing two different kinds of "upgrades."  It does seem confusing as-is.
Maybe we can clarify it somehow?

I clarified the docs to address this issue in https://github.com/microsoft/rushjs.io-website/commit/5d85a72cd02963f5c0ee2c8bc160538ec3a03db9


Favorites place?

Hi.  Thanks for this fantastic app.
Can you please tell me where does your app store the numbers of favorite manga?
I want to add my favorite folder from the official app but i don't know where to put it.

They are stored in internal_sdcard/NClientV2/GALLERYNAME

Thanks for your reply.
But i noticed that the galleries stored are the downloaded manga only,not the favorites.
I found there 3 folders only while i liked more than 30 manga.
The favorites must be stored else where because  i cleared cache and disconnected from wifi but my favourites still show up.

The favorites are stored into a Database saved into a private folder with the settings of the app


apple dns: add more details on DNS failure

Commit Message: apple dns: add more details on DNS failure
Risk Level: low, new telemetry
Testing: added tests

@Reflejo I know you were curious about more observability in the Apple DNS resolver. I added more details to both the synchronous and async failure path.


Don't app-silo outgoing viewing keys anymore

Check with @benesjan whether this can be actually done.

It is still done. In all the constrained callsites we get the ovsk_app via this function on private context. Unconstrained callsites use this getter.

I think my comment was referencing the fact that someone (@sklppy88?) mentioned they thought you had found an issue with the removal of this siloing, and that you had said we could not get rid of it.


Discovery service endpoint

Fixes #124

Coverage increased (+0.1%) to 90.144% when pulling f280888fdeeac7207e9c014ccabbad78d87c24b8 on rafaelcaricio:discovery-service-endpoint into 1712fa83d86df4fef2910321b5a4bb43f791f5ba on zalando:release2.0.

:+1:


DNS Configuration for On Premise Scenario wanted to be enriched if those are possible.

In case connecting Private Endpoint of PaaS like App Service/Functions etc from On Premise via Express Route, is below DNS configuration possible? There may be the case who want to achieve private connection only by on-premise DNS configuration. (not using Azure Public & Private DNS)
・Add A record to resolve PaaS domain directly to its private IP.

Also in the current on-premise scenario, always forwarder is configured. If it's mandatory, It would be great help to be mentioned why it's mandatory.
Thank you very much!!

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

ID: a88af182-32aa-a8f3-359d-b92ae1cfb8c7
Version Independent ID: 01ce07fc-4bc2-def5-9ecd-a80330ad9488
Content: Azure Private Endpoint DNS configuration
Content Source: articles/private-link/private-endpoint-dns.md
Service: private-link
GitHub Login: @asudbring
Microsoft Alias: allensu

Thanks for the feedback! I have assigned the issue to the content author to investigate this and update the document as appropriate.

Thanks for the feedback! We are currently investigating and will update you shortly.

Thanks for the confirmation!
Understood this is not supported scenario. While updating docs, It would be great help to mention the reason why such scenario is not supported by Azure..! Thank you!

@asudbring Hi, this is just a friendly reminder but is there any update on this? Thank you.

Sending to PM for review
#reassign:@ivapplyr

Thank you for you dedication to our documentation.?
?
Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.?
?
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.?
?
#please-close


UN-780: Record, Focused, and Article page types in "More Stories"

Ticket URL: UN-780
About these changes
Added the three page types to the "More Stories" and "You may also be interested in" sections.
How to check these changes
Open an article page, scroll to the bottom and see that the new page types are being included.
Before assigning to reviewer, please make sure you have

[x] Checked things thoroughly before handing over to reviewer.
[x] Checked PR title starts with ticket number as per project conventions to help us keep track of changes.
[x] Ensured that PR includes only commits relevant to the ticket.
[x] Waited for all CI jobs to pass before requesting a review.
[x] Added/updated tests and documentation where relevant.

Merging PR guidance
Follow docs\developer-guide\contributing.md
Deployment guidance
Follow docs\infra\environments.md

@TNA-Allan to kindly review this PR please

Hi @jamesbiggs

Open an article page, scroll to the bottom and see that the new page types are being included.

The pages showing in "More stories" appear to be fixed and not changing when a page is update and published.
Ex 2 below The Monteagle Letter - updated and published but does not appear in More stories

Admin latest : 2 focus articles, 1 article v/s Display: 2 focus articles, 1 article - Ok

Admin latest : 1 record article, 1 focused article, 1 article v/s Display: 2 focus articles, 1 article - missing record article
Updated with 1 record article

Hi @jamesbiggs

Open an article page, scroll to the bottom and see that the new page types are being included.

The pages showing in "More stories" appear to be fixed and not changing when a page is update and published.
Ex 2 below The Monteagle Letter - updated and published but does not appear in More stories

Admin latest : 2 focus articles, 1 article v/s Display: 2 focus articles, 1 article - Ok

Admin latest : 1 record article, 1 focused article, 1 article v/s Display: 2 focus articles, 1 article - missing record article
Updated with 1 record article

Hi Allan, was it a new page? Or just updated an old one? Because this is working via first published date, not the last published date :)


New Feature: Subscribe button

It's a an entry. If user enters their email and click subscribe then it should save the email into the list of subscribers

Please assign it to me @takumade  I have done this type of task

Hello @PiyushSinghjnp let me assign you

Assigned


Problems in Thread Commissioning App

i am created a thread network uisng EFR32MG12 as RCP and BeagleBone as Border Router...i have faced some issues while commissioning..
1.When using the  Thread Commissioning App, after selecting the border router, typed the PSKc of the network as admin password. But the app shows incorrect password after  5-10 minutes. My doubt is that what is the admin password? is it the PSKc of the network
2. When using the Thread commissioning using CLI commands, after join success when we type the state cli command it shows detached. What will be the treason
anyone please find the answer for this doubts and help for commissioning the network

Hi @rohithanayady thanks for creating this issue. Are you using Cascoda hardware and the cascoda SDK for this project? This repository and issue page is specifically for the Cascoda SDK. For other hardware platforms you will be able to find assistance on either the openthread github or user group.
But I'll try and answer your questions anyway:

No, the 'Admin Password' refers to the 'commissioning credential' which is defined when the network is first formed. This is used along with some other parameters to create the PSKc (PSKc is basically a hash of this, see section <IP_ADDRESS>.1 of the Thread 1.1.1 spec). It is called 'passphrase' on the openthread border router form network page, I think.
Join success is good and means the device has all of the network parameters, including key. But you still need to start the thread stack using the thread start cli command. The device will then join the network. (Note the network parameters are then stored in nonvolatile storage, so you don't need to commission every time, just ifconfig up thread start.

Hello @CiaranWoodward, i am using the Silicon Lab WSDK hardware.(EFR32MG12)
1.In the dataset there is no passphrase is shown. How do we know the passphrase. i think this passphrase is we have to use as the admin password.is it right? Also one more doubt is that if we use a mobile phone as the external commissioner, its name(say eg: vivo1901) is the admin password? please clarify my doubts
2.No sir. After join success i have typed ### thread start .Then after used the ### state. But it shows ### Detached. What would be the reason

Hi @rohithanayady, this repo (and organisation) is for Cascoda hardware - specifically the CA-8210 and CA-8211. Unfortunately we have no experience with any Silicon Labs hardware, so you will need to contact either Silicon Labs' support, or use one of the links I provided above.

The passphrase cannot be obtained from the PSKc, as it is created with a one-way function and cannot be extracted. The only way to know the passphrase (which is called the admin key & commissioner credential too) is to choose it when the network is formed.
At this point, its difficult to know what went wrong, so I would ask you to check out the silicon labs & openthread generic support. The guide for Cascoda's hardware probably won't address your issue.

I hope you can find a solution to your issue, but as it isn't related to the Cascoda SDK or Cascoda hardware, i'm going to close this now.


koordlet: revise base collectors and system status check

Ⅰ. Describe what this PR does

koordlet:

Fix panics of node and pod collectors when the device collector is disabled.
Revise the initialization of the system-supported status.

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/lgtm
/approve


Split long log messages on Android for logcat

Work around the built-in logcat limit on Android (about 1000 characters)
by splitting some hand-picked debug messages known to generally be
longer than that. This prevent those messages from being truncated in
logcat.

Notes:

The logcat limit could be retrieved dynamically I guess, don't want to bother here, that sounds complex from C#, and not sure it can be changed dynamically anyway so would not provide much benefit (I think it's hard-coded in the Android kernel).
Unity normally appends the C# callstack, which therefore here gets completely truncated since we already use up to 1000 characters per call. We could do better, but it's unlikely to be worth the effort. Also the last bit of the message likely will have enough space left for that callstack.


Unit testing?

Ive been expanding the compass a bit at https://github.com/gabevenberg/micro-bit-led-compass, adding things like tilt compensation and more directions than just the 8 using a line drawing algorithm. (in progress).
its gotten to the point where I need to unit test some of my non-hardware dependent functionality. Im not trying to do HIL testing or anything like that, I just want to logically test a few modules that are well separated from the hardware-dependent code. I tried implementing what is suggested in this post, but was not able to get tests working on the separate (no-std) crates. How should I set up unit tests for testing individual modules in embedded projects? Examples would be massively appreciated.

I did eventually figure it out and documented what I did in https://gabevenberg.com/posts/rustembeddedunittesting/. Im not entirely sure how id fit it into the book, but if there's an interest I can try to make a rough draft.


[SPARK-33210][SQL][DOCS][FOLLOWUP] Fix descriptions of the SQL configs for the parquet INT96 rebase modes

What changes were proposed in this pull request?
Fix descriptions of the SQL configs spark.sql.legacy.parquet.int96RebaseModeInRead and spark.sql.legacy.parquet.int96RebaseModeInWrite, and mention EXCEPTION as the default value.
Why are the changes needed?
This fixes incorrect descriptions that can mislead users.
Does this PR introduce any user-facing change?
No
How was this patch tested?
By running ./dev/scalastyle.

Test build #135139 has started for PR 31557 at commit 4e7f173.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39720/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39720/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39720/

Test build #135139 has finished for PR 31557 at commit 4e7f173.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135139/

@dongjoon-hyun @cloud-fan Could you review this PR, please.

Merged to master and branch-3.1.


Q: How can I extract all the names of an expression?

Assuming I have a document map[string]interface{}{ "Age" : ..., "Income": ..., "other" : .... }, and a generic expression.
I want to be able to know all the names that are in the expression.
> expr.GetNames("Age > 25 AND Income > 25,000" )
[ "Age", "Income"]

Visitor will help with this. But now it isn’t implemented, so there is no way now of extracting names. But I think this is good feature and if I have time, I’ll implement it.

Now it's possible:
ast package provides Visitor interface and BaseVisitor implementation.
You can use it for traveling ast tree of compiled program.
For example if you want to collect all variable names:
import "github.com/antonmedv/expr/ast"

type visitor struct {
	ast.BaseVisitor
	identifiers []string
}

func (v *visitor) IdentifierNode(node *ast.IdentifierNode) {
	v.identifiers = append(v.identifiers, node.Value)
}

program, err := expr.Compile("foo + bar", expr.Env(env))

visitor := &visitor{}
ast.Walk(node, visitor)

fmt.Printf("%v", visitor.identifiers) // outputs [foo bar]


test: add basic parallel unit tests

This PR adds http integration tests for the proxy.
It runs parallel with a port allocated for the server and one for the proxy for each test. For example you could see with ngrep
$ sudo ngrep -d lo
###########                                                                                [2/543]
T <IP_ADDRESS>:58094 -> <IP_ADDRESS>:12397 [AP] #151
  GET /500 HTTP/1.1..host: localhost:12397....
#
T <IP_ADDRESS>:55480 -> <IP_ADDRESS>:12396 [AP] #152
  GET /foo HTTP/1.1..host: localhost:12396....
#########
T <IP_ADDRESS>:39576 -> <IP_ADDRESS>:12399 [AP] #161
  GET /500 HTTP/1.1..host: localhost:12397..x-forwarded-for: <IP_ADDRESS>....
#
T <IP_ADDRESS>:56454 -> <IP_ADDRESS>:12398 [AP] #162
  GET /foo HTTP/1.1..host: localhost:12396..x-forwarded-for: <IP_ADDRESS>....
###
T <IP_ADDRESS>:12399 -> <IP_ADDRESS>:39576 [AP] #165
  HTTP/1.1 500 Internal Server Error..content-length: 0..date: Sat, 12 Mar 2022 19:36:37 GMT....
##
T <IP_ADDRESS>:12398 -> <IP_ADDRESS>:56454 [AP] #167
  HTTP/1.1 200 OK..content-length: 0..date: Sat, 12 Mar 2022 19:36:37 GMT....
##
T <IP_ADDRESS>:12396 -> <IP_ADDRESS>:55480 [AP] #169
  HTTP/1.1 200 OK..date: Sat, 12 Mar 2022 19:36:37 GMT..content-length: 0....
#
T <IP_ADDRESS>:12397 -> <IP_ADDRESS>:58094 [AP] #170
  HTTP/1.1 500 Internal Server Error..date: Sat, 12 Mar 2022 19:36:37 GMT..content-length: 0....
##############

@bamthomas tried to rebase your branch to have the changes from master as I think these tests are really useful. Somehow I keep on getting merge conflicts after a successful rebase on the gh pr page.
I see 2 option, you rebase it yourself or me targeting @felipenoris repository co-authoring your commit due to rebasing

I made a branch integration_tests on our repository merging the conflicts on Cargo.toml
it builds locally, and tests are green.


implement list.Unzip

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 360 (0.56%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-3.1%) to 12.65%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

list/zip_gen.go
2
30
6.67%

list/unzip_gen.go
0
330
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-3.1%

Covered Lines:
211

Relevant Lines:
1668

💛  - Coveralls


Remove Git conflict code

In the template, you have HEAD/master conflicts, which show in the template when building a new site

thanks a lot!


Verbose Header Object documentation (3.0.4)

Fixes:

#1965

This copies the relevant Parameter Object fields to the Header Object instead of relying on implicit guidance.  The text for the fields has been edited to reflect that only headers are being described.
This also include an example of describing a header using the content field, and explaining why it is necessary to do so.
NOTE: Includes some appendix headings to placate the PR markdown validation check.

This has two TSC approvals and a third positive-comment-with-questions-that-have-been-resolved near-approval so I'm going to merge this to start to reduce the amount of conflicts with empty sections and the like.


Deconflicting plugin name with VORC

The name Gymkhana plugin name was already in use by VORC, so introducing the same name in VRX introduces a build error.  This changes the plugin library name, leaving the source file names that same.
Currently working on testing with VORC - would appreciate someone testing with the VRX Gymkhana task scoring.

I verified that the base case for VRX works - roslaunch vrx_gazebo vrx.launch


[SPARK-28157][CORE] Make SHS clear KVStore LogInfo for the expired blacklist entries

What changes were proposed in this pull request?
At Spark 2.4.0/2.3.2/2.2.3, SPARK-24948 delegated access permission checks to the file system, and maintains a blacklist for all event log files failed once at reading. The blacklisted log files are released back after CLEAN_INTERVAL_S seconds.
However, the released files whose sizes don't changes are ignored forever due to info.fileSize < entry.getLen() condition (previously here and now at shouldReloadLog) which returns false always when the size is the same with the existing value in KVStore. This is recovered only via SHS restart.
This PR aims to remove the existing entry in KVStore during blacklist expiring.
How was this patch tested?
Pass the Jenkins with the updated test case.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12101/
Test PASSed.

Test build #106886 has started for PR 24966 at commit 36fe7cc.

cc @dbtsai , @mgaido91 , @jerryshao , @mridulm .

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106886/
Test FAILed.

Test build #106898 has started for PR 24966 at commit f61bcc6.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12106/
Test PASSed.

Test build #106898 has finished for PR 24966 at commit f61bcc6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106898/
Test PASSed.

Test build #106900 has started for PR 24966 at commit c472d47.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12107/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12108/
Test PASSed.

Test build #106901 has started for PR 24966 at commit 956a93c.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12109/
Test PASSed.

Test build #106900 has finished for PR 24966 at commit c472d47.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106900/
Test PASSed.

Test build #106901 has finished for PR 24966 at commit 956a93c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106901/
Test PASSed.

Test build #106906 has started for PR 24966 at commit a551aff.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12112/
Test PASSed.

Thank you so much for the review, @mgaido91 !

Test build #106906 has finished for PR 24966 at commit a551aff.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106906/
Test PASSed.

Hi, @vanzin .
Could you review this PR?

Hi, @dbtsai .
Could you review this PR?

LGTM. Thanks. Merged into master.

Thank you for review and merging!


providers/studio: Fine tune Studio APIs in provider

Description
This is to increment the LivepeerProvider for the Studio API to also include a bunch of other
APIs that are (currently) specific to Studio so not exposed as a generic interface on the provider
interface. These are necessary to use the full power of the Studio API to build applications, and
some of them actually need to be called from a proper backend with access to a full-powered API
key as well.
Some of the changes include:

Cleaning up internal fields from the schema (cc @adamsoffer helpful when we do the OpenAPI schema cleanup as well)
Document all fields and reorganize them in the types
Implement some Task awareness in Studio provider, including an easy way to wait for a task completion when starting them (e.g. upload or changing asset storage)
Implement List and Delete APIs for assets and streams

Additional Information

[x] I read the contributing docs (if this is your first contribution)

I just pushed a few docs updates with these new API updates and tiny tweaks to the API based on playing around with the developer experience and seeing how it felt. 🚢


Plaintext export client

Added plaintext to export list

nohup.out is already in .gitignore, see pull request: https://github.com/N4SJAMK/teamboard-client-react/commit/320e3ae7561bf38e1843a2b13446e8a47aa80e26

Looks ok. If that nohup.out is still somewhere there we'll just take it out later.


Unit tests for SciDataLib class

Would like to start adding the test suite by adding unit tests for the SciDataLib class.
Plan to use pytest
Why?
From writing lots of unittest tests (previously called PyUnit) from the standard library, have found pytest to be much better both for starting to write tests (no need to create classes or use the class methods of unittest) and more extensible for mature projects (fixtures are key!)
The number of plugins for pytest is also very impressive and helpful.
Our group has also settled on pytest for all python projects by default.
I tried to find some reviews to point that the Python community is also leaning more towards pytest:

Blog article that recommends pytest
Slant's 3 best Python test frameworks shows that pytest has 92% rating
One of the Hitchhiker's Guid to Python recommended testing tools noted for its simplicity

Above all, pytest can run tests written using unittest!

This is a duplicate of #28  so closing as well


Intiated Node js and Express

Closing this as this has nothing to do with the code in the YouTube video.