Cloud9 tries to recreate .settings file -
i've installed cloud9 ide on linux machine in order play around bit (i had use nodejs 0.8 because cloud9 uses package depends on node-waf, no longer supported higher versions of nodejs).
i can start without problems, when try access cloud9 via browser, gives me error message: file exists.
. here's trace log:
error: file exists. @ module.exports.from (/home/xyz/repos/cloud9/node_modules/vfs-local/localfs.js:678:35) @ object.fs.exists [as oncomplete] (fs.js:91:19)
relevant code section:
exists(topath, function(exists){ if (options.overwrite || !exists) { // rename file fs.rename(frompath, topath, function (err) { if (err) return callback(err); // rename metadata if (options.metadata !== false) { rename(wsmetapath + from, { to: wsmetapath + to, metadata: false }, function(err){ callback(null, meta); }); } }); } else { var err = new error("file exists."); err.code = "eexist"; callback(err); }
when error occurs, topath
variable set workspace settings file (/home/xyz/repos/cloud9/workspace/.settings
)
has else had error this? how can resolve it?
thx in advance
reinstalling cloud9
first option, maybe try using workaround installation procedure: https://github.com/ajaxorg/cloud9/issues/2904#issuecomment-22518669
second option, if willing use older node-version running cloud9 indicated, used following installation procedure , worked (assuming installed nvm). can still use cloud9.sh-file starting:
git clone git://github.com/ajaxorg/cloud9.git cd cloud9 nvm install 0.8.8 sed -i -e 's/~//g' package.json npm config set ca="" npm install sed -i s/connect.session.file/connect.session.memory/ configs/default.js
not sure if 0.8.8 best node-version cloud9 works me :) last step seems necessary because of https://github.com/ajaxorg/cloud9/issues/2005#issuecomment-11372587 :)
then before starting cloud9 have enter:
nvm use 0.8.8
or set 0.8.8 default node version if don't use node otherwise:
nvm alias default 0.8.8
fix problem without reinstalling
third option, if don't want repeat installation procedure try reinstalling vfs-local-module in cloud9 directory:
npm install vfs-local@0.3.4
haven't tested though :)
Comments
Post a Comment