idea git提交文件报错 runnerw.exe: CreateProcess failed with error，无法提交改变的文件

转载 已于 2023-11-24 11:01:24 修改 · 3.9k 阅读 · 2 ·
CC 4.0 BY-SA版权
原文链接：https://blog.youkuaiyun.com/moneyshi/article/details/81298861
文章标签：

#intellij-idea #git #java

于 2021-12-16 10:01:03 首次发布
描述了作者在工作空间切换后遇到文件提交问题，包括文件不显示、无法拉取推送。通过点击OK并重新提交解决了问题的过程。

切换了工作空间后发现有这个问题，
修改的文件死活提交不了，并且有部分修改的文件不在提交的列表里显示，无法拉取也无法推送，
##第一步
找到setting
在这里插入图片描述
在这里插入图片描述
点击ok，再次提交发现就可以了

IntelliJ IDEA （PhpStorm）操作 Git 慢的问题分析与解决
记录一些平时遇到的一些好的文章的转载、bug及解决方案
11-14 948
删除或重命名或文件解决 IntelliJ IDEA 操作 Git 慢的问题。公司电脑按上述方法处理；私人电脑可删除“IP Guard”。
解决idea git慢
qq_43985303的博客
12-29 2227
我们遇到过一些类似的例子，如果你把这两个应用改名了有用的话，有可能是你的本地安装的某个杀毒软件或者防火墙，在 IDE 通过这个程序新建子进程的时候，这个软件需要很多的时间才能放行这个创建子进程的操作。折腾半天，最后发现修改C:\Program Files\JetBrains\IntelliJ IDEA 2020.3.2\bin目录下面的runnerw(64).exe文件名（或者删除），注意两个都要改名，比如改成runnerw.exe.bak和runnerw64.exe.bak，再试试看，马上好了。
解决IDEA突然报错：Git is not installed
最新发布
casually的博客
10-16 825
解决IDEA突然报错：Git is not installed
idea 提交代码过慢
Ellen_Tangxiang的博客
03-22 3004
修改idea bin目录下的runnerw.exe和runnerw64.exe的后缀名，就可以解决提交速度过慢的问题了，无需重启 IDEA。
Pycharm 配置git报错：Can not Run Git:runnerw.exe:CreateProcess failed with error
LOVE_XUAN521的专栏
07-22 2508
导致报错原因，是由于没有配置Git 环境变量。 对于git的安装完成之后，就需要对git配置环境变量，这个可以cmd来进行调用。 使用cmd来确定git的环境是否配置成功，进行输入git 如果弹出git相关信息，说明是配置成功了。 然后进行打开pycharm的后，进行点击菜单中file 菜单，弹出了下拉菜单选中为 settings 的选项。 进入到了settings的界面当中，进行点击 version control 的中的 git 的选项。 然后在path to git...
IntelliJ IDEA: Clone failed runnerw.exe CreateProcess failed with error 2
热门推荐
zhangbeizhen18的博客
12-18 1万+
使用IntelliJ IDEA 从github仓库导入项目报错: Clone failed runnerw.exe CreateProcess failed with error 2 检查如下步骤: 1. 安装Git工具,下载地址: https://gitforwindows.org/     检验成功安装,在任意文件夹上点击右键,下拉菜单左键点击"Git Bash Here" 出现命令行...
C:\Users\czr\.jdks\ms-21.0.7\bin\java.exe -Dmaven.multiModuleProjectDirectory=E:\git\ruoyi-main\ruoyi-admin -Djansi.passthrough=true -Dmaven.home=D:\idea\plugins\maven\lib\maven3 -Dclassworlds.conf=D:\idea\plugins\maven\lib\maven3\bin\m2.conf "-Dmaven.ext.class.path=C:\Program Files\JetBrains\IntelliJ IDEA 2024.1.7\plugins\maven\lib\maven-event-listener.jar" -Dfile.encoding=UTF-8 -Dsun.stdout.encoding=UTF-8 -Dsun.stderr.encoding=UTF-8 -classpath D:\idea\plugins\maven\lib\maven3\boot\plexus-classworlds-2.6.0.jar;D:\idea\plugins\maven\lib\maven3\boot\plexus-classworlds.license org.codehaus.classworlds.Launcher -Didea.version=2024.1.7 -DskipTests=true -Dexec.workingdir=E:/git/ruoyi-main "-Dexec.args=-agentlib:jdwp=transport=dt_socket,address=52225,suspend=y,server=y -javaagent:C:\Users\czr\AppData\Local\JetBrains\IntelliJIdea2024.1\captureAgent\debugger-agent.jar=file:/C:/Users/czr/AppData/Local/Temp/capture839.props -classpath \"%classpath;C:\Program Files\JetBrains\IntelliJ IDEA 2024.1.7\lib\idea_rt.jar\" org.dromara.DromaraApplication" -Dexec.executable=C:\Users\czr\.jdks\ms-21.0.7\bin\java.exe exec:exec [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.dromara:ruoyi-admin:jar:5.3.1-BETA2 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-jar-plugin is missing. @ org.dromara:ruoyi-admin:${revision}, E:\git\ruoyi-main\ruoyi-admin\pom.xml, line 164, column 21 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] ----------------------< org.dromara:ruoyi-admin >----------------------- [INFO] Building ruoyi-admin 5.3.1-BETA2 [INFO] --------------------------------[ jar ]--------------------------------- [INFO] [INFO] --- exec-maven-plugin:3.5.0:exec (default-cli) @ ruoyi-admin --- [ERROR] Command execution failed. java.io.IOException: Cannot run program "C:\Users\czr\.jdks\ms-21.0.7\bin\java.exe" (in directory "E:\git\ruoyi-main"): CreateProcess error=206, 文件名或扩展名太长。 at java.lang.ProcessBuilder.start (ProcessBuilder.java:1170) at java.lang.ProcessBuilder.start (ProcessBuilder.java:1089) at org.codehaus.mojo.exec.ExtendedExecutor.launch (ExtendedExecutor.java:62) at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:295) at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:253) at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:903) at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:863) at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:454) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289) at org.apache.maven.cli.MavenCli.main (MavenCli.java:193) at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103) at java.lang.reflect.Method.invoke (Method.java:580) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) at org.codehaus.classworlds.Launcher.main (Launcher.java:47) Caused by: java.io.IOException: CreateProcess error=206, 文件名或扩展名太长。 at java.lang.ProcessImpl.create (Native Method) at java.lang.ProcessImpl.<init> (ProcessImpl.java:506) at java.lang.ProcessImpl.start (ProcessImpl.java:159) at java.lang.ProcessBuilder.start (ProcessBuilder.java:1126) at java.lang.ProcessBuilder.start (ProcessBuilder.java:1089) at org.codehaus.mojo.exec.ExtendedExecutor.launch (ExtendedExecutor.java:62) at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:295) at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:253) at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:903) at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:863) at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:454) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289) at org.apache.maven.cli.MavenCli.main (MavenCli.java:193) at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103) at java.lang.reflect.Method.invoke (Method.java:580) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) at org.codehaus.classworlds.Launcher.main (Launcher.java:47) [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 3.255 s [INFO] Finished at: 2025-05-16T10:52:29+08:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:3.5.0:exec (default-cli) on project ruoyi-admin: Command execution failed.: Cannot run program "C:\Users\czr\.jdks\ms-21.0.7\bin\java.exe" (in directory "E:\git\ruoyi-main"): CreateProcess error=206, 文件名或扩展名太长。 -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException Process finished with exit code 1
05-17
### Maven 构建过程中 'CreateProcess error=206, 文件名或扩展名太长' 的解决方案 此错误通常发生在 Windows 系统上，当命令行参数过长或者文件路径超出系统限制时触发。以下是几种可能的解决方法： #### 方法一...
Failed to execute goal org.bytedeco:javacpp:1.5.9:build (javacpp-cppbuild-compile) on project libnd4j: Failed to execute JavaCPP Builder: Cannot run program "sh" (in directory "D:\IDEA2018\deeplearning4j-master\libnd4j"): CreateProcess error=2, 系统找不到指定的文件。
06-10
It seems like you are facing an error while executing the JavaCPP Builder in your Maven project. The error message states that the program "sh" cannot be found in the specified directory, which is ...
idea创建仓库报错“Сannot Run Git: runnerw.exe: CreateProcess failed with error 216:”
InterfaceToL的博客
06-15 714
问题原因：集成git使用的是bin目录下的可执行文件Git\bin\git.exe。解决方案：改为cm的目录下的可执行文件Git\cmd\git.exe。
Golang: runnerw.exe: CreateProcess failed with error 216 (no message available)错误详解
pengpengsays
03-22 1万+
前言最近在学着写Golang，这门语言对于并发和区块链真的是很配。初学者，不免会遇到一些小问题。如题所指出的报错。下面是节觉的方法问题详解runnerw.exe: CreateProcess failed with error 216 (no message available)看描述，创建进程失败，应该是main这个入口文件的问题。检查包名。发现问题，IDE自动将包名导成了当前的目录名（模块）解...
runnerw.exe: CreateProcess failed with error 216 (no message available)
Fabio的博客
01-10 1125
 runnerw.exe: CreateProcess failed with error 216: Process finished with exit code 216 运行go项目抛此异常   解决办法：如果运行main方法的话，引入的包名应改为main   ...
runnerw.exe: CreateProcess failed with error 5:
lxh的博客
01-28 5946
在idea配置Git时遇到这个问题： 后来发现是我路径设置错了： 解决方案 修改设置里的路径即可（Setings-Version Control-Git）
GO异常 | runnerw.exe: CreateProcess failed with error 21
Eshare分享
08-30 1668
背景 今天创建了一个GO项目，写了几行代码 package chapter1 import "fmt" func main() { fmt.Println("hello world") } 运行后抛出如下异常： runnerw.exe: CreateProcess failed with error 216: Process finished with exit cod...
golang运行报错：runnerw.exe: CreateProcess failed with error 216 (no message available)
hallen41的博客
12-20 515
golang运行报错：runnerw.exe: CreateProcess failed with error 216 (no message available) 在运行go文件时，你是不是也遇到这种问题了？ 导致这个问题的有两种情况： 第一种就是packag不是main，单文件运行，要确保package是main，还有个main函数，是程序的主入口。 第二种就是运行的GOOS不是你本系统的，比如你是windows，那么GOOS就得是windows，设置GOOS的方式：set GOOS=windows
runnerw.exe: CreateProcess failed with error 216 (no message available) 解决
liuqun of program life
07-01 573
golang IDE工具创建包文件时候 动将包名导成了当前的目录名（模块） 解决方案 package main 修改包名，改成main
runnerw.exe: CreateProcess failed with error 216: Process finished with exit code 216 运行go项目抛此异常
ScutKevinYzy的博客
12-07 405
把包名由test改为main即可
001- CreateProcess failed with error 216 (no message available)错误详解
weixin_30708329的博客
10-10 470
问题详解 runnerw.exe: CreateProcess failed with error 216 (no message available) 看描述，创建进程失败，应该是main这个入口文件的问题。 检查包名。发现问题，IDE自动将包名导成了当前的目录名（模块） 解决方案 package main 修改包名，改成main 注：一个model下只能有一个main...
runnerw.exe: CreateProcess failed with error 216:
彭世瑜的博客
07-09 4136
goland中运行报错： runnerw.exe: CreateProcess failed with error 216: 原因package的名称不是main，改为main之后ok
git apply报错什么原因 error: patch failed: services/inputflinger/dispatcher/InputDispatcher.cpp:8131
10-15
</think>`git apply` 报错 `error: patch failed: services/inputflinger/dispatcher/InputDispatcher.cpp:8131` 的核心原因是**补丁文件与目标代码的当前版本不匹配**，导致 Git 无法在指定位置应用更改。...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值