Ian Sabey
Hello I am still seeing this NPE stack in DataGrip 2018.2 I have tried the main release version as well as the snapshot version. My server is hosted on mLab.com...
The ability to detect/fail on missing targets would greatly benefit CI/CD Kubeval pipeline jobs, was shocked to see that this doesn't happen currently.
Wrote up #110 to allow custom handling of disconnects.
@motionharvest this is the workaround i have found to be successful (just confirmed today) on the bot im working with ```javascript let bot const startBot = () => { bot...
keep in mind the logging does refer to my logger.. i figure you would know but i wanted to throw the disclaimer on there. im pretty sure other than that...
If you run lsof -i :5000 then grab the id from the output then run kill then npm run dev you should be good.
The command needs to be syntactically identical to what I put. make sure there is a space before typing the port. On Wed, Jun 13, 2018, 11:22 PM Jarvis Potter...
@Samyaryal [this](https://github.com/StephenGrider/FullstackReactCode/issues/24#issuecomment-397097815) the error is stating that the connection to Port 5000 was refused. So make sure you don't have anything running on it.
Welp, i decided i should read up on that link.. oops. Deleting the whole package for is still not something that should be done.
I had this issue as well. Only on the dev server though. Seems to be an issue with nodemon not killing the port when restarting. Simple work around is to...