I'm trying to get Wallaby.js running on my solution in VS2013 and I'm getting some weird behaviour.
If it is running and I change the config file I have to stop it. It errors with the following message
wallaby.js started core v1.0.159 Failed to start stop operation,
Error: ENOENT: no such file or directory, unlink
'C:\Users\XXXX\AppData\Local\Temp\1.wallaby\projects\FG57vVlzA+WewEWCpi1WInb+g1k=\cache\instrumented\somepath\somefile.ts.compiled.js'
at Error (native) at Object.fs.unlinkSync
(evalmachine.:931:18) at EventEmitter.u.unlinkFileSync
[as _unlinkFileSync] (C:\Users\XXXX.wallaby\core\server.js:18:11095)
at C:\Users\XXXX.wallaby\core\server.js:16:6022 at baseFor
(C:\Users\XXXX.wallaby\core\node_modules\lodash\index.js:1971:13)
at baseForOwn
(C:\Users\XXXX.wallaby\core\node_modules\lodash\index.js:2025:14)
at baseEach
(C:\Users\XXXX.wallaby\core\node_modules\lodash\index.js:1814:16)
at Function.forEach
(C:\Users\XXXX.wallaby\core\node_modules\lodash\index.js:5701:11)
at EventEmitter._.extend.stop
(C:\Users\XXXX.wallaby\core\server.js:16:5651) at Object.i.receive
(C:\Users\XXXX.wallaby\core\server.js:14:1177) at
WebSocket. (C:\Users\XXXX.wallaby\core\server.js:18:12016)
at emitTwo (events.js:87:13) at WebSocket.emit (events.js:169:7)
at Receiver.self._receiver.ontext
(C:\Users\XXXX.wallaby\core\node_modules\ws\lib\WebSocket.js:682:10)
at Receiver.opcodes.1.finish
(C:\Users\XXXX.wallaby\core\node_modules\ws\lib\Receiver.js:391:14)
at Receiver.expectHandler
(C:\Users\XXXX.wallaby\core\node_modules\ws\lib\Receiver.js:372:33)
at Receiver.add
(C:\Users\XXXX.wallaby\core\node_modules\ws\lib\Receiver.js:87:24)
at Socket.firstHandler
(C:\Users\XXXX.wallaby\core\node_modules\ws\lib\WebSocket.js:663:22)
at emitOne (events.js:77:13) at Socket.emit (events.js:166:7) at
readableAddChunk (_stream_readable.js:146:16) at
Socket.Readable.push (_stream_readable.js:109:10) at TCP.onread
(net.js:517:20)
wallaby.js stopped
Then I start Wallaby.js and it hangs on the initialization stage, as indicated in the bottom left corner of VS2013
Wallaby.js: Initializing runner
and the console output never moves past
wallaby.js started
core v1.0.159
I then stop Wallaby.js and nothing happens.
I then stop Wallaby.js and the console reports Wallaby.js has stopped (The context menu for my config file show stop, restart, and start cmd's)
wallaby.js started
core v1.0.159
wallaby.js stopped
Then I start Wallaby.js again, and it works...
I followed the steps outline for installing Wallaby.js and have been fumbling my way through the configuration doco. Any help on this would be appreciated.
It is most certainly the result of leading ./ in your files/tests paths/patterns in your wallaby config. Please remove t and try again.
Related
Cannot even build in sidekick after a simple change
I created a new Core/TS project in Sidekick, I built the app and developed some stuff, but later I changed the icon to a nicer one (which requires a new build, no HMR for this type of change obviously), now I cannot build my app (cloud build, because I don't have Android Studio).
I checked the /main/assets/app/ and the icons were successfully changed there and they were existed.
What is happening? How do I fix this big issue? My patience bottle with all these critical errors even after simple changes is getting emptied.
I also tried "removing .cloud and folder directories", and clicking "clean cloud processes", adding "clean" option, etc...
But none worked.
I also updated the webpack.config.js file, with node_modules.bin\update-ns-webpack --configs
The file got successfully updated, but still did not solve the problem and I still cannot build.
Still after many hours cannot cloud build my app in sidekick. I also tried tns platform remove android, tns install, etc, etc... none worked out.
this is the error message:
[00:00:18.521] [WARN] Executing webpack failed with exit code 2.
[00:00:18.681] [ERROR] clean-webpack-plugin: /mnt/storage/builds/_/af8fe992d35e76b54f5523261a83dac973ffc9ed/5.3.4/5.3.1/Spread/platforms/android/app/src/main/assets/app/**/* has been removed.
Executing webpack failed with exit code 2.
'Build failed with error code 2'.
[19-06-10 19:13:56.767] Couldn't enable debugging for EP7333JKFA, Error: Couldn't enable debugging for EP7333JKFA
at Errors.fail (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\common\errors.js:126:28)
at Errors.failWithoutHelp (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\common\errors.js:136:21)
at LiveSyncService.<anonymous> (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:253:30)
at Generator.next (<anonymous>)
at C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:13:71
at new Promise (<anonymous>)
at __awaiter (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:9:12)
at LiveSyncService.enableDebuggingCoreWithoutWaitingCurrentAction (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:250:16)
at LiveSyncService.enableDebuggingCoreWithoutWaitingCurrentAction (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\common\decorators.js:67:47)
at LiveSyncService.<anonymous> (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:290:25)
at Generator.next (<anonymous>)
at fulfilled (C:\Users\Bridge\AppData\Roaming\npm\node_modules\nativescript\lib\services\livesync\livesync-service.js:10:58)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
OUTPUT 2
EDIT:
SOLVED
https://github.com/NativeScript/sidekick-feedback/issues/384#issuecomment-508028462
I know this isn't an answer, but it is happening to me, too. I am running Nativescript 5.4.1. I can build with webpack, but as soon as I try to run with AOT or Uglify, I can't build and the error message isn't very helpful.
Try to remove and add 'nativescript-dev-webpack'-plugin using nativescript-sidekick-GUI, this resolve my issue...
When I launch app sometimes I get this error and sometimes no:
2017-11-10 14:00:37.119701+0000 XXX[768:176399] [DYGLInitPlatform] connection to host has failed: Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"
2017-11-10 14:00:37.123363+0000 XXX[768:176399] aborting: platform initialization failed
(lldb)
What can cause this problem ?
There could be some corrupt files in your build folder.
Try running Clean (⌘+⇧+K) and Clean build folder... ( ⌘+⇧+⌥+K ) and rebuild your application.
In my case, the error was related to Launch Screen, most likely it was corrupt.
Deleting the launch screen under General Tab, fixed the issue.
I'm trying to run the getting started example in windows for android but after running
react-native run-android
I get the following error:
TypeError: Object doesn't support property or method 'isNative'
at CallSiteToString (X:\code\react_native\AwesomeProject\node_modules\source-map-support\source-map-support.js:195:3)
at Anonymous function (X:\code\react_native\AwesomeProject\node_modules\source-map-support\source-map-support.js:304:5)
at Array.prototype.map (native code)
at prepareStackTrace (X:\code\react_native\AwesomeProject\node_modules\source-map-support\source-map-support.js:303:3)
at stackGetter (Unknown script code:208:9)
at socketErrorListener (_http_client.js:303:3)
at emitOne (events.js:96:5)
at emit (events.js:188:7)
at emitErrorNT (net.js:1265:3)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
maybe you have a problem with your code ! what is 'isNative' in your code ?
it's better to to copy your code and paste it here.
Figured it out. In case anyone else faces this problem it seems I had both a regular node installation and a node (chakra) installation and the chakra one was causing problems with react-native. After uninstalling node(chakra), react-native runs fine.
I'm trying to get my meteor app up and running, but I don't understand the error that its throwing at all, which is:
/Users/ten3/.meteor/packages/meteor- tool/.1.1.10.1b51q9m++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:278
throw(ex);
^
Error: EACCES, unlink '/Users/ten3/Desktop/git/ten/website/prospect-recovery/prospect-recovery/.meteor/local/db/mongod.lock'
at Object.Future.wait (/Users/ten3/.meteor/packages/meteor-tool/.1.1.10.1b51q9m++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:398:15)
at /tools/fs/files.js:1331:28
at Object.wrapper [as unlink] (/tools/fs/files.js:1334:20)
at findMongoAndKillItDead (/tools/runners/run-mongo.js:318:11)
at launchOneMongoAndWaitForReadyForInitiate (/tools/runners/run-mongo.js:400:7)
at launchMongo (/tools/runners/run-mongo.js:656:7)
at [object Object]._.extend._startOrRestart (/tools/runners/run-mongo.js:756:19)
at [object Object]._.extend.start (/tools/runners/run-mongo.js:714:10)
at /tools/runners/run-all.js:168:26
- - - - -
I'm running a shell script before I try to run a local copy of my meteor app. It supposed to stop my application from interacting with other APIs. When I run the script (I'm on a mac) through my terminal, it returns '0' which as I read means that there are zero errors. I know that the error message is guiding me to certain lines of code, but I don't understand why I would change them if my co-worker could get his copy up and running. He is running his application on a windows computer. Thank you. I'm pretty new to this.
It was a permission error just as #thatgibbyguy first suggested. I was able to run it buy using sudo meteor to override the permission restrictions. I wasn't about to remove my mongod.lock file since that my coworker had the file and was able to get it up and running.
Setup a new angular project under linux. Committed it to git and cloned it to windows. Using bower and npm, I managed to get everything loaded, except, I have this one error (only on windows)
A recursive grep for ../time/convert in the project shows me:
./node_modules/grunt-contrib-imagemin/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/mout/date/diff.js:var convert = require('../time/convert');
./node_modules/grunt-contrib-imagemin/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/mout/src/date/diff.js:define(['./totalDaysInMonth', './totalDaysInYear', '../time/convert'], function(totalDaysInMonth, totalDaysInYear, convert){
./node_modules/grunt-contrib-imagemin/node_modules/optipng-bin/node_modules/bin-wrapper/node_modules/mout/date/diff.js:var convert = require('../time/convert');
./node_modules/grunt-contrib-imagemin/node_modules/pngquant-bin/node_modules/bin-wrapper/node_modules/mout/date/diff.js:var convert = require('../time/convert');
./node_modules/grunt-contrib-imagemin/node_modules/pngquant-bin/node_modules/bin-wrapper/node_modules/mout/src/date/diff.js:define(['./totalDaysInMonth', './totalDaysInYear', '../time/conve
but ls -l shows:
$ ls ./node_modules/grunt-contrib-imagemin/node_modules/gifsicle/node_modules/bin-wrapper/node_modules/mout/time
convert.js now.js parseMs.js toTimeString.js
Which says that convert.js is actually there. Being new to grunt and angular, I'm puzzled where this could be coming from and how to troubleshoot it.
After this I end up getting stuck here:
Running "karma:unit" (karma) task
INFO [karma]: Karma v0.10.4 server started at http://localhost:8080/
INFO [launcher]: Starting browser Chrome
WARN [watcher]: Pattern ".../test/mock/**/*.js" does not match any file
WARN [launcher]: Chrome have not captured in 60000 ms, killing.
INFO [launcher]: Trying to start Chrome again.
WARN [launcher]: Chrome have not captured in 60000 ms, killing.
INFO [launcher]: Trying to start Chrome again.
Wondering if angular work using grunt is just not possible on Windows....
My solution was to quit using windows. Moved dev work to linux, and no more crazy problems like this. Oh, and my machine now seems a good deal faster too.