Scully: ERROR: The process "6824" not found.
🐞 Bug report
I'm running Scully for the first time. When I run npm run scully it creates the static files but does not complete and gives the error ### ERROR: The process "6824" not found.
Description
🔬 Minimal Reproduction
I don't know how to reproduce this without sending the whole application over...
💻Your Environment
Angular Version:
Angular CLI: 9.0.0-rc.7
Node: 10.16.3
OS: win32 x64
Angular: 9.0.0-rc.7
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... platform-server, router
Ivy Workspace: Yes
Package Version
--------------------------------------------------------------------
@angular-devkit/architect 0.900.0-rc.7
@angular-devkit/build-angular 0.900.0-rc.7
@angular-devkit/build-optimizer 0.900.0-rc.7
@angular-devkit/build-webpack 0.900.0-rc.7
@angular-devkit/core 9.0.0-rc.7
@angular-devkit/schematics 9.0.0-rc.7
@angular/cdk 9.0.0-rc.6
@angular/fire 5.2.3
@angular/http 7.2.15
@angular/material 9.0.0-rc.6
@ngtools/webpack 9.0.0-rc.7
@nguniversal/express-engine 8.2.6
@nguniversal/module-map-ngfactory-loader 8.2.6
@schematics/angular 9.0.0-rc.7
@schematics/update 0.900.0-rc.7
rxjs 6.5.3
typescript 3.6.4
webpack 4.41.2
Scully Version:
{
"name": "thai-basil-prod",
"version": "1.0.0",
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e",
"webpack:server": "webpack --config webpack.server.config.js --progress --colors",
"scully": "scully",
"scully:serve": "scully serve"
},
"private": true,
"dependencies": {
"@angular/animations": "^9.0.0-rc.7",
"@angular/cdk": "^9.0.0-rc.6",
"@angular/cli": "^9.0.0-rc.7",
"@angular/forms": "~9.0.0-rc.7",
"@angular/http": "^7.2.15",
"@angular/material": "^9.0.0-rc.6",
"@angular/platform-browser": "^9.0.0-rc.7",
"@angular/platform-browser-dynamic": "~9.0.0-rc.7",
"@angular/platform-server": "~9.0.0-rc.7",
"@angular/router": "~9.0.0-rc.7",
"@google/maps": "^1.0.2",
"@nguniversal/express-engine": "^8.2.6",
"@nguniversal/module-map-ngfactory-loader": "^8.2.6",
"@scullyio/init": "0.0.9",
"@scullyio/ng-lib": "latest",
"@scullyio/scully": "latest",
"@types/google-maps": "^3.2.1",
"@types/googlemaps": "^3.38.1",
"angular-material-time-picker": "^1.0.8",
"angular-svg-icon": "^8.0.0",
"bootstrap": "^4.4.1",
"core-js": "^3.6.0",
"cors": "^2.8.5",
"express": "^4.17.1",
"firebase": "^7.6.1",
"luxon": "^1.21.3",
"ngx-material-timepicker": "^5.2.3",
"node-sass": "^4.13.0",
"nodemailer": "^6.4.2",
"rxjs": "~6.5.3",
"stripe": "^7.14.0",
"tslib": "^1.10.0",
"zone.js": "~0.10.2"
},
"devDependencies": {
"@angular-devkit/build-angular": "~0.900.0-rc.7",
"@angular/common": "^9.0.0-rc.7",
"@angular/compiler": "^9.0.0-rc.7",
"@angular/compiler-cli": "~9.0.0-rc.7",
"@angular/core": "^9.0.0-rc.7",
"@angular/fire": "^5.2.3",
"@angular/language-service": "~9.0.0-rc.7",
"@types/jasmine": "~3.5.0",
"@types/jasminewd2": "^2.0.8",
"@types/node": "^12.11.1",
"@types/stripe": "^7.13.18",
"@types/stripe-checkout": "^1.0.3",
"@types/stripe-v3": "^3.1.12",
"bufferutil": "^4.0.1",
"codelyzer": "^5.1.2",
"jasmine-core": "~3.5.0",
"jasmine-spec-reporter": "~4.2.1",
"karma": "~4.4.1",
"karma-chrome-launcher": "~3.1.0",
"karma-coverage-istanbul-reporter": "^2.1.1",
"karma-jasmine": "~2.0.1",
"karma-jasmine-html-reporter": "^1.4.2",
"protractor": "~5.4.0",
"ts-loader": "^6.2.1",
"ts-node": "~8.5.4",
"tslint": "~5.20.1",
"typescript": "~3.6.4",
"utf-8-validate": "^5.0.2",
"webpack-cli": "^3.3.10"
}
}
$ npm run scully
> [email protected] scully C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer
Facing\thai-basil
> scully
The option outFolder isn't configures, we are using "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\ by default now"
Cleaned up C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\ folder.
☺ new Angular build imported
started servers in background
servers available
Finding all routes in application.
Pull in data to create additional routes.
Route list created in files:
src\assets\scully-routes.json
C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\assets\scully-routes.json
Route "/profile" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\profile\index.html"
Route "/Terms-Of-Service" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\Terms-Of-Service\index.html"
Route "/confirm" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\confirm\index.html"
Route "/menu" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\menu\index.html"
Route "/about" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\about\index.html"
Route "" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\index.html"
Route "/ordernow" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\ordernow\index.html"
Route list created in files:
src\assets\scully-routes.json
C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\assets\scully-routes.json
Generating took 14.02 seconds for 7 pages:
That is 0.5 pages per second,
or 2004 milliseconds for each page.
ERROR: The process "6824" not found.
Something I noticed in the static files produced is that the class cdk-global-scrollblock was not removed from the html which I assume is something done by Angular Material. Not sure if this will be fixed after the 6824 bug is fixed.
Marcusg62
All 7 comments
I ran it again and got a different error : 3748
$ npm run scully
> [email protected] scully C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer
Facing\thai-basil
> scully
The option outFolder isn't configures, we are using "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\ by default now"
Cleaned up C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\ folder.
started servers in background
servers available
Finding all routes in application.
Pull in data to create additional routes.
Route list created in files:
src\assets\scully-routes.json
C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\assets\scully-routes.json
Route "/Terms-Of-Service" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\Terms-Of-Service\index.html"
Route "/profile" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\profile\index.html"
Route "/confirm" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\confirm\index.html"
Route "/menu" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\menu\index.html"
Route "" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\index.html"
Route "/about" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\about\index.html"
Route "/ordernow" rendered into file: "C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\ordernow\index.html"
Route list created in files:
src\assets\scully-routes.json
C:\Users\marcu\OneDrive\Documents\Develop Denver Code\Thai Basil\Customer Facing\thai-basil\dist\static\assets\scully-routes.json
Generating took 18.94 seconds for 7 pages:
That is 0.37 pages per second,
or 2707 milliseconds for each page.
ERROR: The process "3748" not found.
I tried with just a hello world app and get a similar error, except:
ERROR: The process "17280" not found.
I put the project in a public repository. https://github.com/Marcusg62/Scully-Test
Marcusg62
on 22 Dec 2019
Update: I ran npm run scully on a Mac and the cli does not throw any errors. However, it does not fix the cdk-global-scrollblock issue.
Like I said, this is an Angular Material css class. My page initializes with a dialog open so, Material adds the class to the html tag to disable scrolling. However, when I close the dialog, the class is not removed and thus the page is not scrollable. Thoughts on why?
Marcusg62
on 22 Dec 2019
The error is a windows artifact, we opened an issue about this in the Nodejs project. You can safely ignore that error on windows. (we are working to get this fixed, but its kind of out of our hands.
Can you create a small reproduction of your cdk-global-scrollblock issue? I willtake a look at that next year.
SanderElias
on 22 Dec 2019
Some extra explanation about the error. We are closing our internal server by force, this might involve closing a process that should already be gone. As we have no way to check this, we can't prevent windows form throwing this "error". That is not an error but is still gets flagged as one in windows. (not on macOs or Linux). This is a known NodeJs issue, and we are trying to get it fixed, or finding a workaround.
SanderElias
on 23 Dec 2019
Thank you Sander. I tried making a minimal reproduce of the cdk-global-scrollblock but cannot reproduce it. Hopefully that's a good thing. 😊
Marcusg62
on 23 Dec 2019
FYI, this appears to be fixed now using latest Scully & Node.
EatonZ
on 1 Dec 2020
Related issues
montella1507
·
5Comments
Splaktar
·
6Comments
spencerb02
·
3Comments
nishimura-yuji
·
4Comments
xmlking
·
3Comments
Most helpful comment
Some extra explanation about the error. We are closing our internal server by force, this might involve closing a process that should already be gone. As we have no way to check this, we can't prevent windows form throwing this "error". That is not an error but is still gets flagged as one in windows. (not on macOs or Linux). This is a known NodeJs issue, and we are trying to get it fixed, or finding a workaround.