更新Heroku CLI时出错:写锁存在:更新

时间:2018-01-19 19:15:34

标签: heroku command-line-interface heroku-cli

我正在尝试更新Heroku CLI,但没有成功。

Heroku CLI的当前版本是

heroku-cli/6.15.5-1f03166 (win32-x64) node-v9.3.0

运行时

heroku update

我收到以下错误

enter image description here

C:\>heroku update
CLI is updating... !
 !    'ELOCK': write lock exists: update

我没有'找到这个问题的任何解决方案,因为我犹豫是卸载并重新安装Heroku CLI(我的所有配置都丢失了)。

6 个答案:

答案 0 :(得分:2)

我通过卸载heroku并通过命令行安装解决了这个问题:  npm install -g heroku 所以我得到了最新的版本。

答案 1 :(得分:0)

不确定原因是什么,但重新启动解决了我的问题。祝你好运!

11:53:26 | ~  : heroku update
heroku-cli: Updating CLI from 6.15.26-5726b6f to 6.15.30-e7b41cd... 
done
Updating plugins, node version changed to 9.7.1... done
heroku-cli: Updating plugins... done

答案 2 :(得分:0)

我遇到了同样的问题,我解决了删除此文件的问题:

/Users/YOUR_USER/Library/Caches/heroku/update.lock

我使用mac,但我想你会在类似的位置拥有相同的文件

答案 3 :(得分:0)

在Mac上,我遇到了同样的问题-通过运行Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... Got context from element 'autovideosink0': gst.gl.GLDisplay=context, gst.gl.GLDisplay=(GstGLDisplay)"\(GstGLDisplayCocoa\)\ gldisplaycocoa0"; Redistribute latency... Redistribute latency... Redistribute latency... Setting pipeline to PLAYING ... New clock: GstSystemClock ** (gst-launch-1.0:93573): CRITICAL **: 13:45:42.402: gst_video_scaler_new: assertion 'out_size != 0' failed ** (gst-launch-1.0:93573): CRITICAL **: 13:45:42.402: gst_video_scaler_get_max_taps: assertion 'scale != NULL' failed ** (gst-launch-1.0:93573): CRITICAL **: 13:45:42.402: gst_video_scaler_new: assertion 'out_size != 0' failed ** (gst-launch-1.0:93573): CRITICAL **: 13:45:42.402: gst_video_scaler_combine_packed_YUV: assertion 'y_scale != NULL' failed ** (gst-launch-1.0:93573): CRITICAL **: 13:45:42.402: gst_video_scaler_free: assertion 'scale != NULL' failed ** (gst-launch-1.0:93573): CRITICAL **: 13:45:42.402: gst_video_scaler_free: assertion 'scale != NULL' failed ERROR: from element /GstPipeline:pipeline0/GstAutoVideoSink:autovideosink0/GstGLImageSinkBin:autovideosink0-actual-sink-glimage/GstGLImageSink:sink: Quit requested Additional debug info: gstglimagesink.c(1768): GstFlowReturn gst_glimage_sink_show_frame(GstVideoSink *, GstBuffer *) (): /GstPipeline:pipeline0/GstAutoVideoSink:autovideosink0/GstGLImageSinkBin:autovideosink0-actual-sink-glimage/GstGLImageSink:sink Execution ended after 0:00:06.161227000 Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces, or set CA_ASSERT_MAIN_THREAD_TRANSACTIONS=1 to abort when an implicit transaction isn't created on a main thread. Freeing pipeline ... ** (gst-launch-1.0:93573): CRITICAL **: 13:45:48.734: gst_video_scaler_free: assertion 'scale != NULL' failed ,通过htop过滤并杀死所有进程来解决。

TLDR;杀死正在运行的Heroku进程

答案 4 :(得分:0)

我也遇到了同样的问题,并通过从Windows 10的以下目录中删除error.log来解决了该问题:C:\ Users \ Behzad.heroku \ error.log

答案 5 :(得分:0)

更新heroku对我有用:

npm update -g heroku