Error on checking out Chrome V8 Wiki from Git Hub - github

I am using Tortoise SVN v1.9.5 to checkout Google Chrome V8 Wiki (trunk) content in my Windows Server 2016 machine from GitHub link of https://github.com/v8/v8.wiki.git and I am getting the following error:
Error: Failed to run the WC DB work queue associated with
Error: 'D:\ChromeV8\wiki\trunk\images', work item 44 (file-install
Error: trunk/What-should-I-do-if-my-CL-broke-the-Node.js-integration-build?.md 1 0 1
Error: 1)
Error: Can't move 'D:\ChromeV8\wiki\.svn\tmp\svn-B67F3A8B' to
Error: 'D:\ChromeV8\wiki\trunk\What-should-I-do-if-my-CL-broke-the-Node.js-integration-build?.md':
Error: The filename, directory name, or volume label syntax is incorrect.
Any help to fix this issue or understand the cause of this error will be of great help.

I guess Windows doesn't support ? occurring in file names. Why do you want to clone the wiki? Can you use a non-Windows OS (e.g. a Linux virtual machine)?

Related

Facing invalid path error when I tried to get a new remote branch created by a mac user to my local windows

Tried multiple ways but getting following error.
error: invalid path 'build\ios/Runner.build/Release-iphoneos/Runner.build/dgph'
Please let me know if you need additional information. Thanks.

What causes error "Connection test failed: spawn npm; ENOENT" when creating new Strapi project with MongoDB?

I am trying to create a new Strapi app on Ubuntu 16.4 using MongoDB. After stepping through the tutorial, here: https://strapi.io/documentation/3.0.0-beta.x/guides/databases.html#mongodb-installation, I get the following error: Connection test failed: spawn npm; ENOENT
The error seems obvious, but I'm having issues getting to the cause of it. I've installed latest version of MongoDB and have ensured it is running using service mongod status. I can also connect directly using nc, like below.
$ nc -zvv localhost 27017
Connection to localhost 27017 port [tcp/*] succeeded!
Here is an image of the terminal output:
Any help troubleshooting this would be appreciated! Does Strapi perhaps log setup errors somewhere, or is there a way to get verbose logging? Is it possible the connection error would be logged by MongoDB somewhere?
I was able to find the answer. The problem was with using npx instead of Yarn. Strapi documentation states that either should work, however, it is clear from my experience that there is a bug when using npx.
I switched to Yarn and the process proceeded as expected without error. Steps were otherwise exactly the same.
Update: There is also a typo in Strapi documentation for yarn. They include the word "new" before the project name, which will create a project called new and ignore the project name.
Strapi docs (incorrect):
yarn create strapi-app new my-project
Correct usage, based on my experience:
yarn create strapi-app my-project
The ENOENT error is "an abbreviation of Error NO ENTry (or Error NO ENTity), and can actually be used for more than files/directories."
Why does ENOENT mean "No such file or directory"?
Everything I've read on this points toward issues with environment variables and the process.env.PATH.
"NOTE: This error is almost always caused because the command does not exist, because the working directory does not exist, or from a windows-only bug."
How do I debug "Error: spawn ENOENT" on node.js?
If you take the function that Jiaji Zhou provides in the link above and paste it into the top of your config/functions/bootstrap.js file (above module.exports), it might give you a better idea of where the error is occurring, specifically it should tell you the command it ran. Then run the command > which nameOfCommand to see what file path it returns.
"miss-installed programs are the most common cause for a not found command. Refer to each command documentation if needed and install it." - laconbass (from the same link, below Jiaji Zhou's answer)
This is how I interpret all of the above and form a solution. Put that function in bootstrap.js, then take the command returned from the function and run > which nameOfCommand. Then in bootstrap.js (you can comment out the function), put console.log(process.env.PATH) which will return a string of all the directories your current environment is checking for executables. If the path returned from your which command isn't in your process.env.PATH, you can move the command into a path, or try re-installing.

Slamdata error when mounting: An unknown error ocurred: 500 ""

I have once before mounted this same database, so I am confident that I have the correct credentials.
During the last session that I had it mounted I was experimenting with my queries, visuals etc. and the session all of a sudden crashed.
Then when I reloaded slamdata, the mount for my database was gone.
Obviously I then tried to remount the same database with the same credentials in order to continue my work. However when I did this I got an error:
There was a problem saving the mount: An unknown error ocurred: 500 ""
And then there is a never ending spin wheel that sits on the mount button. I can leave this pop up and go to the original screen, but nothing occurs. And then if I try to remount again the same error occurs.
I have verified that I can still access my db and collections using robomongo. So if anyone knows what this error message refers to please let me know! I have yet to find its meaning online.
Note: I have already tried uninstalling and reinstalling/ restarted my computer.
In SlamData 4.2.1 this bug has been identified and fixed an issue with the MongoDB connecter that would corrupt the metastore if you use the _id field in a query. The fix is available in the SlamData 4.2.2 release soon
Below is the fix:
Delete the current metastore. Below is the location of this file for each supported operating system:
Mac OS:
$HOME/Library/Application Support/quasar/quasar-metastore.db.mv.db
Microsoft Windows:
%HOMEDIR%\AppData\Local\quasar\quasar-metastore.db.mv.db
Linux (various vendors):
$HOME/.config/quasar/quasar-metastore.db.mv.db
Open a terminal and switch to the location that you stored SlamData into. You should find a quasar-web.jar file in the following location based on your installed operating system based on default installation paths:
Mac OS:
/Applications/SlamData 4.2.1.app/Contents/java/app/quasar-web.jar
Microsoft Windows:
C:\Program Files (x86)\slamdata 4.2.1\quasar-web.jar
Linux (various vendors):
$HOME/SlamData 4.2.1/quasar-web.jar
Run the following command in a terminal:
java -jar quasar-web.jar initUpdateMetaStore
This will rebuild your metastore. Once complete it will return you to your operating system prompt.
Rerun the SlamData application as you normally would
Remount your database
At this point in time you can access your saved workspaces.
NOTE: You will not want to open the workspace you were using that caused this issue as it will cause the same problem.

Studio + java 6 + Snow Leopard

For stability reasons (OS X stability) I decided to use 10.6.8 with java 6 again. When I try to use studio I get the following
2015-11-17 10:16:34:828 SEVERE Internal server error:
com.orientechnologies.orient.core.exception.OConfigurationException: Database 'XXXXX' is not configured on server (home=XXXXX/orientdb-community-2.0.12/databases/) [ONetworkProtocolHttpDb]
2015-11-17 10:16:41:062 SEVERE Internal server error:
com.orientechnologies.orient.core.exception.OConfigurationException: Database 'XXXX' is not configured on server (home=XXXXXX/orientdb-community-2.0.12/databases/) [ONetworkProtocolHttpDb]
And studio asks for the login info endlessly without showing any data.
Any workarounds? This didn't happen with mavericks and java 7
Seems there is no database under that path. Please check the database folder if exists or it's empty.
Ok, after I eliminated the "." from the database dir name the severe error did not appear anymore.
But the endless credentials pop-up did not stop. Even when I managed to issue a "select from e", the query never returned.
BUT if I checked the "store pair in keychain" box everything started to work as always. It should not be mandatory.
Forget about this one

iPython notebook won't open some files

I have a git folder with several ipython notebook files in it. I've just got a new comp and installed ipython. When I open some files, it works fine, others, however, display this error:
Error loading notebook, bad request.
The log looks like:
2014-07-16 00:20:11.523 [NotebookApp] WARNING | Unreadable Notebook: /nas-6000/wclab/Ahmed/Notebook/01 - Boundary Layer.ipynb [Errno 5] Input/output error
WARNING:tornado.access:400 GET /api/notebooks/01%20-%20Boundary%20Layer.ipynb?_=1405434011080 (127.0.0.1) 3.00ms referer=linktofile
The read/write and owner permissions are the same for each of the files. The files open fine on my other computers, it's just this new one. Any ideas?
Cheers,
James
Errno 5 is a low level error usually reported when your disk has bad sectors.
I don't think the error is related to the file or ipython, check your disk with an appropriate tool (fsck if you are using Linux).