I'm following the tutorial here and am stuck at "inserting parties from the console"... I can't run "meteor mongo"
Here is my output:
$ meteor.bat mongo
C:\Users\USER\AppData\Local\.meteor\packages\meteor-tool\1.1.4\mt-os.windows.x86_3 2\dev_bundle\lib\node_modules\fibers\future.js:245
throw(ex);
^ Error: EINVAL, invalid argument
at new Socket (net.js:157:18)
at process.stdin (node.js:687:19)
at Command.main.registerCommand.name [as func] (C:\Users\USER\AppData\Local\.m eteor\packages\meteor-tool\1.1.4\mt-os.windows.x86_32\tools\commands.js:1036:12)
at C:\Users\USER\AppData\Local\.meteor\packages\meteor-tool\1.1.4\mt-os.window s.x86_32\tools\main.js:1363:23
I'm using Cygwin on Windows 7 SP1, and have tried restarting to no use. In case this is relevant using control-C doesn't kill the meteor server, so I have been killing all the node.exe processes manually through the task manager instead.
This is my first time using meteor, and can't find this replicated anywhere.
** EDIT **
This works using the DOS prompt, but not the cygwin terminal
Thank you, and let me know if you need more info about anything!
At this time meteor on Windows can ONLY be used via the "cmd" prompt. Not even PowerShell will work. Nor does git-bash (in case you were wondering -- I tried that too).
Just do all your meteor commands from a "cmd" shell and you should avoid lots of little issues I think.
One nice thing -- when you want to build/deploy your app -- the nice little tool "demeteorizer" DOES work fine on cygwin/git-bash. :)
Related
I've been trying to setup Eclipse for some C developing. I manage to get the example "hello world" program (provided by Eclipse) to compile, however I am unable to run or debug it. Since I am able to compile, I assume that the setup for the compiler is correct, I can also find the executable file in the workspace (which will not run manually).
While trying to run it through Eclipse I get the error "Error Starting Process - Launching Failed, Cannot run program".
While trying to debug it from Eclipse, I get the error "Error in final launch sequence: Failed to execute MI command: -exec-run" and "Error creating process %path to executable%(error 5)".
I've tried changing workspace to one that has no spaces and to reinstall the compiler (MinGW) with no success.
If anyone could provide some insight on the problem I'd be very grateful.
Edit: Attempting to run the executable returns the following error: "Windows cannot access the specified device, path or file. You may not have the appropriate permissions to access the item." This is strange as I am running it as an admin on my machine.
Furthermore, attempting to run the executable from an administrator permission level command prompt window returns "access is denied".
It turned out my anti-virus software was blocking the file's execution, disabled it and the program ran just fine.
Since I have updated windows, my conemu terminal is giving me the following error each time a session is created:
wslbridge error: failed to start backend process
note: backend error output: -v: -c: line 0: unexpected EOF while looking for matching `''
-v: -c: line 1: syntax error: unexpected end of file
ConEmuC: Root process was alive less than 10 sec, ExitCode=0.
Press Enter or Esc to close console...
Has anyone an idea to bring conemu to a wsl terminal? Thank you
A similar error is caused by upgrading WSL from v1 to v2.
If you read through the discussion on this github issue for ConEmu you'll find a variety of instructions that can be distilled into:
Change the command for the task {Bash::bash} to the following:
wsl.exe
A GitHub user posted this workaround which worked for me:
I've fixed the issue by doing this:
Download latest cygwin1-20200531.dll.xz from https://cygwin.com/snapshots/ and unpack the file as cygwin1.dll into ConEmu\wsl\ (replacing the original file there)
Download #Biswa96's wslbridge2 from https://github.com/Biswa96/wslbridge2/releases and unpack to the same directory
Replacing {WSL::bash} task's Command with:
set "PATH=%ConEmuBaseDirShort%\wsl;%PATH%" & %ConEmuBaseDirShort%\conemu-cyg-64.exe %ConEmuBaseDirShort%\wsl\wslbridge2.exe -cur_console:pm:/mnt -eConEmuBuild -eConEmuPID -eConEmuServerPID -l
I can now access my Ubuntu under W10 just like before the W10 upgrade. Backscroll and arrows in VIM work as expected.
The key part of step 3 is to replace conemu-cyg-64.exe --wsl with conemu-cyg-64.exe %ConEmuBaseDirShort%\wsl\wslbridge2.exe.
Longer term, it looks like the author of ConEmu is working on switching to the new Windows PTY API, which will eliminate the need for the wslbridge hack (and many others) entirely.
I had the same issue with last update windows
(Feature update to Windows 10, version 2004 - Successfully installed on 9/1/2020)
the error does not seem to be related to the version of WSL from 1 to 2:
$ wsl -l -v
NAME STATE VERSION
Ubuntu-20.04 Running 1
Nevertheless, this workaround worked for me as well, thank you so much!
Exactly this goes through upgrading WSL from v1 to v2.
You have to open cmder and in the startup command or Task enter {wsl.exe} and ready
cmder is working again.
Yes, the new command for WSL2 is much simpler, but just running wsl does not cause .profile to be read because launching this way does not request login shell, and it launches as root.
A better command is to specify the user id and to invoke the shell of your choice (bash is most common) with the appropriate option. For bash a login shell is desirable so .profile, .bashrc and .bash_aliases get sourced, if present. The -l (lower case L) does that:
wsl -U yourUserName bash -l
I am using Kinetis Design Studio v 3.0 and am trying to launch a C application on my FRDM-K64 board. The project builds just fine; however, when I try to debug, I get this error:
Error in final launch sequence
Failed to execute MI command:
-exec-run
Error message from debugger back end:
Don't know how to run. Try "help target".
Don't know how to run. Try "help target".
I haven't a clue why this is happening. Other projects (such as the "bubble" example) launch just fine, and I am using basically the same launch configuration. I'm using Segger J-Link, although I tried using OpenOCD as well and got the same message. Any ideas of how to fix this?
I solved the problem--apparently my software needed to be updated. So if anyone is getting the same error, be sure you have tried checking for updates.
Play version 2.1.1
The problem I encounter is I try to run the server within the play console and I don't know if I can do it from the batch file.
C:\
cd C:\dev\work\npadmin\trunk
path=C:\Program Files\Java\jdk1.7.0_79\bin;%PATH%
C:\play-2.1.1\play debug
call run -Dnameprofiler.graph.path=c:/nameprofiler-data/graph2/graph_2015-07-14_08-00-00/ono.db -Dnameprofiler.datapath=c:/nameprofiler-data -Ddataloading=lazy
Up until play debug, everything is fine, I get in the console but I have no output of the 'run' within the console.
...
play! 2.1.1 (using Java 1.7.0_79 and Scala 2.10.0), http://www.playframework.org
> Type "help play" or "license" for more information.
> Type "exit" or use Ctrl+D to leave this console.
[npadmin] $
Is there any way to do this?
After some trial and error I found a way to enter the debug and run the play app.. it is way too simple.
use 'play debug' and the 'run YOUR_CODE' in the same like:
C:\play-2.1.1\play debug run -Dnameprofiler.graph.path=c:/nameprofiler-data/graph2/graph_2015-07-14_08-00-00/ono.db -Dnameprofiler.datapath=c:/nameprofiler-data -Ddataloading=lazy
Somehow it forces it into play's command and works.
I am trying to do the equivalent of the following Linux command with a Windows batch file and TortoiseSVN.
svn info > info.txt
I have tried the following with no luck:
start /wait "" "c:\Program Files\TortoiseSVN\bin\TortoiseProc.exe" /command:info >> %CD%\info.txt
I am running Windows with TortoiseSVN v1.6.16 so I don't have access to the command line tools.
Note: We were encountering issues with the newer version of TortoiseSVN so we went back to 1.6 until issues are resolved with a newer version and the company upgrades the server to that version.
Your construction didn't work, doesn't work and will never work due to zero-bits of trueness:
start (with and without /wait) have sense in bat-file only if you have more than one bat-process starting from this bat (compare with call), for called GUI it doesn't differ from direct using program-name
TortoiseProc is GUI-app after all, it emits nothing to stdout
Info was and is unknown command for TortoiseProc, thus you'll get only GUI-window "About"
:about Shows the about dialog. This is also shown if no command is
given
In addition to correct suggestion "Update to at least 1.8 on client and have CLI-tools" you can consider following solutions:
Install from unrelated to TortoiseSVN sources pure CLI SVN-client (also 1.6.* - from WanDisco will be good choice) at the same as TSVN or another location (I done it at the times of 1.6)
Study and use subwcrev (it was part of TortoiseSVN even in 1.6, AFAICR) and emulate some part of svn info in subwcrev's template-file with correct keywords