Created a default project without modifications, no build errors, but it failed to run and showed errors when running Ripple-Nexus(Galaxy).
As mentioned in here copying your config.xml into your www directory should resolve the ripple.js not found error.
Anyway it seems that the Ripple Simulator works well, even if you get the error, so in the end I found myself ignoring it.
Related
The Problem:
next.js is failing to run the build command, even though I can run it in development mode with no problems. Its saying there is a missing semicolon in the css. Of course there isn't one, it wouldn't compile in dev mode if there was. And for general information, I am using css modules for this project. So all my css is name.module.css.
here is the warning the console gives, and it is the entire stack trace. Doesn't change if I run --debug flag either. and Im running npm run build which corresponds to the script "build": "next build" in my package.json.
> projectName#0.1.0 build
> next build
info - Using webpack 5. Reason: no next.config.js https://nextjs.org/docs/messages/webpack5
info - Checking validity of types
info - Creating an optimized production build
Failed to compile.
HookWebpackError: <css input>:61:1: Missed semicolon
> Build error occurred
Error: > Build failed because of webpack errors
at /Users/name/Documents/coding_files/personal_projects/projectName/node_modules/next/dist/build/index.js:17:924
at async Span.traceAsyncFn (/Users/name/Documents/coding_files/personal_projects/projectName/node_modules/next/dist/telemetry/trace/trace.js:6:584)
What I have tried:
First I looked up the issue here. I found a few posts with similar errors.
Post 1 From post claification: this is my full stack trace shown.
Post 2 I ran npm install and it found nothing to update. and changed my import to "next/app" instead. Didn't help either.
Other than posts I did a dive into the next.js code in node_modules to try to understand what was happening and I got no where because its a webpack thing, which I did not realize. I also saw another post that I cannot find that said that this error happens with importing google fonts sometimes, so I commented out all my google fonts and this is still happening. I do not quite understand how it could give errors on build but not on dev.
Closing thoughts
I suspect that something is being imported into some file somewhere, as that seemed to be the issue in the other post I read (the one I cannot find), however I cannot find it. That or my lack of next.config.js file is causing the issue ( I am a next.js beginner). Also, I am using typescript, if that helps.
Any help is really appreciated.
Thank you everyone 😄
I have a little problem concerning cache:clear following a tutorial that told me if I have an error while running the command, I could delete the dev folder by hand in var/cache/dev
So when running the command to clear the cache, I got this error:
[Symfony\Component\Filesystem\Exception\IOException]
Failed to remove file "/var/www/html/Symfony/var/cache/de~/profiler/26/75/2d7526":
So as the error appeared I decided to delete the dev folder in /var/dev
But then I couldn't go anymore on my browser checking if everything worked fine. This error came up.
RuntimeException in ClassCollectionLoader.php line 309: Failed to write cache file "/var/www/html/Symfony/var/cache/dev/classes.php".
I have no idea as how to make it work again.
My dev and prod cache folders are back in my cache folder as expected, but that doesn't do anything. It won't work anymore.
So I'm a bit desperate.
Have you setup correctly the file permissions for the var folder?
See this link: http://symfony.com/doc/current/setup/file_permissions.html
I'm trying to set up my project with PHPUnit. I tried to configure PHPUnit with my project on PhpStorm following steps explained on this article.
http://blog.jetbrains.com/webide/2013/03/phpunit-installation-via-composer-in-phpstorm/
But when I try to run tests I continuously getting following error.
Warning: require_once(PHPUnit/Runner/Version.php): failed to open stream: No such file or directory in C:\Users\win 8\AppData\Local\Temp\ide-phpunit.php on line 49
Fatal error: require_once(): Failed opening required 'PHPUnit/Runner/Version.php' (include_path='.;C:\wamp\bin\php\php5.6.19\pear') in C:\Users\win 8\AppData\Local\Temp\ide-phpunit.php on line 49
Process finished with exit code 255
I tried setting up number of new projects and in all the cases I get this stupid error. I don't know how to fix this. Please, your help is highly appreciated.
It seems that you are using PHPUnit through your IDE, and that the IDE has not provided PHPUnit with the correct include path items.
To understand about include path, and what is happening in your problem, see this post, part on inclusions by relative or absolute path and the include path.
To solve your problem, you will need to change a setting in your IDE, either to include the PHPUnit library in the general include path of running PHP, or in the include path of running PHPUnit.
It was version mis-match. I tried to integrate PHPUnit 5.3+ with PHPstorm 8.+ version. When I try PHPUnit 5.3+ with PHPStorm 2016.1 it worked as a charm.
I have a really strange error in a symfony 2 installation.
Everything worked fine until I suddenly ran into this error. The cache cannot be cleared because of the error, which is also preventing me from checking/updating dependencies with Composer.
InvalidArgumentException: The service definition "security.encoder_factory.responses" does not exist
I tried to manually clear the cache (removing the folder, recreating it and setup permissions again) without succes. The error persists and is the result of every request even when a new cache is build.
Is there anybody with a suggestion as to where to look, or how to solve this problem?
The proposed grep of Pazi (see comments) gave no results, zero.
It seemed to be a magic dependency error. After clearing the vendor/ directory, removing the composer.lock file and installing vendors from scratch (with update) it works again.
Maybe it was a not correctly updated autoloader from composer or not complete deleted vendor after removing from composer.json. Sometime magic happens :)
Help!
I've been working with Meteor for about two months now, and everything is going swimmingly in my OSX home environment. But I recently brought some of that code into our Windows 7 environment at work, and Meteor isn't behaving the same on Windows.
Specifically, code bundling keeps getting borked. When I make changes to the code base, instead of flushing the old .meteor/local directory, and rebundling the application, it's barfing a ENOTEMPTY exception at me in the server console. If I halt the mongod process in Task Explorer and manually delete the .meteor/local directory, I can restart the application, and it will bundle and deploy the app with the new code changes.
Running on: http://localhost:3000/
No dependency info in bundle. Filesystem monitoring disabled.
Errors prevented startup:
Exception while bundling application:
Error: ENOTEMPTY, directory not empty 'c:\Users\Abigail\My Documents\GitHub\canvas tracker\.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.
But it doesn't do on-the-fly code changes and re-bundles anymore. :( I'm also getting EPERM errors sometimes when I try launching the application.
Running on: http://localhost:3000/
No dependency info in bundle. Filesystem monitoring disabled.
Errors prevented startup:
Exception while bundling application:
Error: EPERM, operation not permitted 'c:\Users\Abigail\My Documents\GitHub\canvas-tracker\.meteor\local\.build.build'
at Object.fs.renameSync (fs.js:439:18)
at _.extend.write_to_directory (c:\Program Files (x86)\Meteor\app\lib\bundler.js:628:8)
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
at Object.exports.launch_mongo (c:\Program Files (x86)\Meteor\app\lib\mongo_runner.js:146:5)
at exports.run.launch (c:\Program Files (x86)\Meteor\app\meteor\run.js:712:39)
at Server.exports.run (c:\Program Files (x86)\Meteor\app\meteor\run.js:770:5)
at Server.g (events.js:193:14)
at Server.EventEmitter.emit (events.js:90:17)
Please fix the problem and restart.
Any ideas on how to resolve this? I'm using Meteor 0.5.4 on Windows 7 Ultimate, SP1, x64.
Edit: I should mention that these errors occur whenever there's an error in the code. In my OSX environment, if I have an error, the code will still compile, minify, and bundle, and the page might not render and I'll get various Javascript errors in the Chrome console which I then have to debug. In my Win7 environment, I'm doing the exact same thing, but instead of compiling a semi-broken app that I can then debug in Chrome, it's halting during the bundle process. In either case, there's an error in my Javascript code (I know that much). But in OSX, it will still bundle and I can proceed to debugging. In Win7, I can't get to the debugging step because of these ENOTEMPTY and EPERM exceptions...
Edit: And, yes, I've tried nuking the permissions on the entire project directory by giving Full Access to Everyone. That didn't do the trick, unfortunately.
Win7. Two Steps to made it work.
1) Delete the DB Lock From MongoDB
C:\Users**USERNAME**\leaderboard.meteor\local\db
mongod.lock
2) Close all Open Editors pointing to files in project
C:\Users**USERNAME**\leaderboard.meteor\local\build\programs\client\app
leaderboard.js
In my case i kept an editor open to edit the leaderboard.js
It needs to be shut down, as the open file handle seems to interrupt.
Okay, so with the help of Tom Wijsman, we managed to track down the issue. The short answer is that it was the GitHub Bash shell.
The long answer is that ENOTEMPTY and EPERM are caused by a directory not getting deleted correctly during the bundling process. The directory not getting deleted correctly was caused by the code using an exec() command, which passed the delete command off to a shell. Turned out I was using the GitHub Bash shell, which is case sensitive, unlike the standard Windows cmd.exe, which is case insensitive. The case sensitivity was causing the shell not to recognize the path that should be removed, thus not removing it, thus causing a break during the bundle process.
100x thanks to Rahul for finding the previous bug reports on this issue! You were the hero that found the needle in the haystack!
Had the exact problem in windows 8. Turning off my McAfee antivirus (Real time scanning) just while running meteor cmd solved it.