Nodemon is not working proparly in windows? - windows

enter image description hereNodemon is not working propaly in windowns
Nodemon first time start parfectfly but when the cange i made it can't catch the changes

Related

Cypress and WebStorm - when a test fails there is a link to the line number that fails - that link is not bringing me to correct line in IDE

What:
After updating to pretty much all Cypress versions 10.x.x, WebStorm stopped or Cypress stopped opening the correct line number for the below scenarios:
Issue:
Where a test would fail an assertion etc. with link to the line in IDE.
Open In IDE inside specific spec it block .
Inside SCREENSHOT: FAILED_LINE_NUMBER it brings me to that line however that's not the line the test actually failed at.
Similar situation when I click on the link pointed out inside SCREENSHOT: GENERIC_BODY_OPEN_IN_IDE -- clicking the link doesn't bring me to the correct it block.
I am fairly certain this is user error but cannot figure it out.
Setup:
Windows 10
Cypress 10.0.3
WebStorm v221.5921.27
cypress runner > Settings > Device Settings > External Editor = Custom C:\Users\me\AppData\Local\JetBrains\Toolbox\apps\WebStorm\ch-0\221.5921.27\bin\webstorm64.exe
Things I have tried:
Wiping cache inside C:\Users\me\AppData\Local\Cypress\Cache and then running npm i cypress
Reinstalling WebStorm
Images:
FAILED_LINE_NUMBER
GENERIC_BODY_OPEN_IN_IDE

Changes In main.Dart not reflecting insted showing previous code changes

When I done some changes in main.Dart of simple HelloWorld program ,new changes are not reflecting in my mobile.Old UI changes are reflecting.I have restarted my visual studio editor, uninstall app.Still old UI changes are reflecting.
Visual studio provide terminal in bottom,
type Flutter run
then you will see ..
Launching lib/main.dart on SM G615F in debug mode...
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done 16.8s
✓ Built build/app/outputs/apk/debug/app-debug.apk.
Syncing files to device SM G615F...
D/GraphicBuffer(24157): register, handle(0xddbb3680) (w:1080 h:1920 s:1088 f:0x1 u:b00)
Syncing files to device SM G615F... 5,356ms (!)
Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h Repeat this help message.
d Detach (terminate "flutter run" but leave application running).
q Quit (terminate the application on the device).
Type r
Initializing hot reload...
Reloaded 0 of 483 libraries in 523ms.
D/GraphicBuffer(24157): register, handle(0xddbb3920) (w:1080 h:1920 s:1088 f:0x1 u:b00)
After that Type R .
Performing hot restart...
Restarted application in 2,067ms.
Changes are reflecting.Issue get resolved
if your code don't reflect on your UI or real device , you can move to master channel of flutter then run flutter clean
you can move to master channel by run in terminal :
flutter channel master

Where are the controls for debugging Node code in VS Code?

Trying to use VS Code for debugging.
I've got most of the way but stuck on finding the controls as shown in VS Code help. when I press F5 I get Process exited with code 0 and I'm not sure what to do about that.
My screen:
The VScode help screen from https://code.visualstudio.com/docs/editor/debugging:
How do I find these controls:
My launch.json file is:
Three parts:
Need to start node process in the terminal after adding:
"start": "node index.js"
to package.json in the "scripts" section
Now do npm start in the terminal
You will see the debugger controls appear and if you then switch to the 'debug console' mini-tab as shown below you can interact with the process in the debug console, e.g.

Unable to Run Meteor 1.1.0.3 Application Locally Windows 10 (Tasklist.exe)

I need some help please.
I just did a fresh install of Meteor 1.1.0.3 from the website using the windows installer. That worked just fine.
I then created one of the sample applications. That worked just fine.
The problem is when I try to run the app and the first package starts to download, I get an exception error. I have Googled this issue for a couple hours now and cannot find a solution.
Here is the CMD output Error:
C:\Users\jwuli\AppData\Local\.meteor\packages\meteor-tool\1.1.4\mt-os.windows.x86_32\dev_bundle\lib\node_modules\fibers\
future.js:278
throw(ex);
^
Error: Couldn't run tasklist.exe: tasklist wasn't found on your system, it usually can be found at C:\Windows\System32\.
at Object.Future.wait (C:\Users\jwuli\AppData\Local\.meteor\packages\meteor-tool\1.1.4\mt-os.windows.x86_32\dev_bund
le\lib\node_modules\fibers\future.js:398:15)
at findMongoPids (C:\Users\jwuli\AppData\Local\.meteor\packages\meteor-tool\1.1.4\mt-os.windows.x86_32\tools\run-mon
go.js:120:16)
at findMongoAndKillItDead (C:\Users\jwuli\AppData\Local\.meteor\packages\meteor-tool\1.1.4\mt-os.windows.x86_32\tool
s\run-mongo.js:236:14)
at launchOneMongoAndWaitForReadyForInitiate (C:\Users\jwuli\AppData\Local\.meteor\packages\meteor-tool\1.1.4\mt-os.w
indows.x86_32\tools\run-mongo.js:360:7)
at launchMongo (C:\Users\jwuli\AppData\Local\.meteor\packages\meteor-tool\1.1.4\mt-os.windows.x86_32\tools\run-mongo
.js:612:7)
at [object Object]._.extend._startOrRestart (C:\Users\jwuli\AppData\Local\.meteor\packages\meteor-tool\1.1.4\mt-os.w
indows.x86_32\tools\run-mongo.js:712:19)
at [object Object]._.extend.start (C:\Users\jwuli\AppData\Local\.meteor\packages\meteor-tool\1.1.4\mt-os.windows.x86
_32\tools\run-mongo.js:670:10)
at C:\Users\jwuli\AppData\Local\.meteor\packages\meteor-tool\1.1.4\mt-os.windows.x86_32\tools\run-all.js:199:26
- - - - -
at C:\Users\jwuli\AppData\Local\.meteor\packages\meteor-tool\1.1.4\mt-os.windows.x86_32\tools\run-mongo.js:73:24
at exithandler (child_process.js:654:7)
at ChildProcess.errorhandler (child_process.js:670:5)
at ChildProcess.emit (events.js:95:17)
at Process.ChildProcess._handle.onexit (child_process.js:818:12)
I am able to run tasklist.exe in any command window and see all my running process.
There is another user here that had the EXACT same issue but on Windows 7. What worked for him was opening the command prompt directly from the root directory of the project. This solution did not work for me.
That post is here: Other Post
I have also tried Powershell along with CMD both running as the Administrator.
Does anyone have any insight?
Thanks!
So after allot of research, and working with other similar platforms/frameworks. I found out that there are many dependencies that you need to install that are not listed in the normal documentation. Examples being, Python, Ruby for the Saas Gem. A ton of old windows C++ Distributabls.
As a Full Stack .NET developer all these concepts were new to me! Everything is working just fine now.

Why am i getting a ENOTEMPTY error?

So i create a default meteor app.
Its runs great.
Now I add a simple insert in the startup function.
its is now giving me exceptions.
Here is my app.js code:
Book = new Meteor.Collection("book");
if (Meteor.isClient) {
Template.hello.greeting = function () {
return "Welcome to app_01.";
};
Template.hello.events({
'click input' : function () {
// template data, if any, is available in 'this'
if (typeof console !== 'undefined')
console.log("You pressed the button");
}
});
}
if (Meteor.isServer) {
Meteor.startup(function () {
if (Book.find().count() === 0) {
var names = ["Ada Lovelace",
"Grace Hopper",
"Marie Curie",
"Carl Friedrich Gauss",
"Nikola Tesla",
"Claude Shannon"];
for (var i = 0; i < names.length; i++)
Book.insert({name: names[i], score: Math.floor(Math.random()*10)*5});
}
});
}
And here is the exception I am getting:
No dependency info in bundle. Filesystem monitoring disabled.
Errors prevented startup:
Exception while bundling application:
Error: ENOTEMPTY, directory not empty 'C:\Users\Office\Workspace\Code\Meteor\app_01\.meteor\local\build\server'
at Object.fs.rmdirSync (fs.js:456:18)
at Object.module.exports.rm_recursive (C:\Program Files (x86)\Meteor\app\lib\files.js:256:10)
at C:\Program Files (x86)\Meteor\app\lib\files.js:254:15
at Array.forEach (native)
at Function._.each._.forEach (C:\Program Files (x86)\Meteor\lib\node_modules\underscore\underscore.js:79:11)
at Object.module.exports.rm_recursive (C:\Program Files (x86)\Meteor\app\lib\files.js:252:9)
at _.extend.write_to_directory (C:\Program Files (x86)\Meteor\app\lib\bundler.js:493:11)
at Object.exports.bundle (C:\Program Files (x86)\Meteor\app\lib\bundler.js:685:12)
at exports.run.restart_server (C:\Program Files (x86)\Meteor\app\meteor\run.js:615:26)
at C:\Program Files (x86)\Meteor\app\meteor\run.js:726:9
Please fix the problem and restart.
The console gives me no useful information at all.
Some more info:
I am using the windows version of meteor 0.5.4
My code has both tabs and spaces as indentation (should that be a problem?)
to add to my perplexity:
If i run the leaderboard example, it runs perfectly.
When I run the default project with my modified startup code, i get the exception. >.<
More info:
when the server crashed, the mongod service was still running in windows. In my infinite wisdom, i thought I'll kill it and maybe try a fresh restart of it.
now i get a new error:
PS C:\Users\Office\Workspace\Code\Meteor\app_01> meteor
[[[[[ C:\Users\Office\Workspace\Code\Meteor\app_01 ]]]]]
Unexpected mongo exit code 100. Restarting.
Unexpected mongo exit code 100. Restarting.
Unexpected mongo exit code 100. Restarting.
Can't start mongod
MongoDB had an unspecified uncaught exception.
Check to make sure that MongoDB is able to write to its database directory.
Edit: now deleted the .meteor/local/db contents. we are now back to the ENOTEMPTY error.
It is because the directory is not getting deleted during the bundling operation.
So when this happens, Stop your server with ctrl + c.
Then delete the contents of .meteor\local\db directory as well as .meteor\local\builds directory and run the server again using meteor command.
Not an ideal way, but it works.
Just tested this on my mac and on my Windows machine, it works fine for me. (Copied and pasted your code into app.js, did not change anything anywhere else, as I understood this is what you did).
There are two ways to go on:
You try meteor reset. Warning: This will empty any databases you had within this app, but I think there isn't anything all to important in there at the moment?
You delete the app and make a new one using meteor create appname, and copy the source code from above into app.js.
I think investing too much time and effort is not worth it, since it is not an app close to production stage. If, however, creating a new app causes the same problem, it will get interesting =)
EDIT: Just searched around and found this: https://github.com/TomWij/meteor/issues/18
Scroll down to the answer; apparently it might be your antivirus scanner preventing Meteor from rebuilding it. Is that possible?
Also, are you starting Meteor from anything else than cmd.exe? I just read through the issue on GitHub, and things seem to be pretty gnarly when using anything else than cmd.exe (eg the GitHub Bash Shell)
Once my pull request goes in, this issue should be resolved:
https://github.com/TomWij/meteor/pull/56

Resources