Zplug: Terminal load debug logging

[jrock2004]

• Type:
  
  
  
  • [x] Bug
  
  
  • [ ] Enhancement
  
  
  • [ ] Feature Request
  
  
  • [ ] Question
  
  

---

• zplug --version: 2.4.1
• zsh --version: 5.2 (x86_64-ubuntu-linux-gnu)
• uname -a: Linux precision 4.10.0-26-generic #30-Ubuntu SMP Tue Jun 27 09:30:12 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Type: Bug

Minimal zshrc (with less than 30 lines)

if ! [ type "zplug" > /dev/null 2>&1 ]; then                                      
    source ~/.zplug/init.zsh                                                           
fi        

zplug 'zplug/zplug', hook-build:'zplug --self-manage'                               
zplug 'zsh-users/zsh-syntax-highlighting', defer:3                              
zplug 'zsh-users/zsh-autosuggestions'                                               

# Install plugins if there are plugins that have not been installed                  
if ! zplug check; then                                                               
    printf "Install? [y/N]: "                                                          
    if read -q; then                                                                   
        echo; zplug install                                                             
    fi                                                                                 
fi

Step to reproduce

1. Put the above code in my zshrc. Save it
2. Open a new terminal windows

Expected: Get my prompt

Actual: Get the following console output then my prompt

/home/jcostanzo/.zplug/log/load_success.log Stats {
  dev: 66306,
  mode: 33188,
  nlink: 1,
  uid: 1000,
  gid: 1000,
  rdev: 0,
  blksize: 4096,
  ino: 9961819,
  size: 0,
  blocks: 0,
  atimeMs: 1499105161000,
  mtimeMs: 1499105161000,
  ctimeMs: 1499105161925.2686,
  birthtimeMs: 1499105161925.2686,
  atime: 2017-07-03T18:06:01.000Z,
  mtime: 2017-07-03T18:06:01.000Z,
  ctime: 2017-07-03T18:06:01.925Z,
  birthtime: 2017-07-03T18:06:01.925Z }
/home/jcostanzo/.zplug/log/load_failure.log Stats {
  dev: 66306,
  mode: 33188,
  nlink: 1,
  uid: 1000,
  gid: 1000,
  rdev: 0,
  blksize: 4096,
  ino: 9962075,
  size: 0,
  blocks: 0,
  atimeMs: 1499105161000,
  mtimeMs: 1499105161000,
  ctimeMs: 1499105161981.2761,
  birthtimeMs: 1499105161981.2761,
  atime: 2017-07-03T18:06:01.000Z,
  mtime: 2017-07-03T18:06:01.000Z,
  ctime: 2017-07-03T18:06:01.981Z,
  birthtime: 2017-07-03T18:06:01.981Z }

Update 1:
Maybe this has something to do with it. When running zplug --log, I get the following output

{"pid":16599,"shlvl":1,"level":"INFO","dir":"/home/jcostanzo","message":"ZPLUG_LOADFILE is not found","trace":["__zplug::log::write::info:2","__zplug::io::file::load:3","/home/jcostanzo/.zplug/init.zsh:33","/home/jcostanzo/.dotfiles/zsh/zplug.zsh:4","/home/jcostanzo/.zshrc:14","zsh:0"],"date":"2017-07-03T15:37:04-0400"}
{"pid":17692,"shlvl":1,"level":"INFO","dir":"/home/jcostanzo/.dotfiles","message":"ZPLUG_LOADFILE is not found","trace":["__zplug::log::write::info:2","__zplug::io::file::load:3","/home/jcostanzo/.zplug/init.zsh:33","/home/jcostanzo/.dotfiles/zsh/zplug.zsh:4","/home/jcostanzo/.zshrc:14","zsh:0"],"date":"2017-07-03T15:38:15-0400"}

[jrock2004]

Sorry for the bump. Any thoughts on this?

[jrock2004]

Has this tool been abandon by the developer?

[jsahlen]

I'm having the same issue, but it only manifests when zplug is loaded inside a Tmux session – I haven't been able to figure out exactly what differences in the environment will trigger it.

[cpitt]

Having similar issue,

Not sure if relevant but zplug --log output

{"pid":23000,"shlvl":1,"level":"INFO","dir":"/Users/cameron.pitt/.zplug/repos/robbyrussell/oh-my-zsh","message":"ZPLUG_LOADFILE is not found","trace":["__zplug::log::write::info:2","__zplug::io::file::load:3","/Users/cameron.pitt/.zplug/init.zsh:33","/Users/cameron.pitt/.zshrc:15","zsh:0"],"date":"2017-08-22T19:03:49-0700"}
{"pid":23000,"shlvl":1,"level":"INFO","dir":"/Users/cameron.pitt/.zplug/repos/robbyrussell/oh-my-zsh","message":"turn monitor on","trace":["__zplug::log::write::info:2","__zplug::job::polling::periodic:9","zsh:1"],"date":"2017-08-22T19:03:51-0700"}
{"pid":23000,"shlvl":1,"level":"INFO","dir":"/Users/cameron.pitt/.zplug/repos/robbyrussell/oh-my-zsh","message":"turn monitor on","trace":["__zplug::log::write::info:2","__zplug::job::polling::periodic:9","zsh:3"],"date":"2017-08-22T19:04:25-0700"}
{"pid":23000,"shlvl":1,"level":"ERROR","dir":"/Users/cameron.pitt/.zplug/repos/robbyrussell/oh-my-zsh","message":"log","trace":["__zplug::log::write::error:2","__zplug::io::print::f:131","__zplug::core::arguments::auto_correct:33","__zplug::core::arguments::exec:21","zplug:26","zsh:3"],"date":"2017-08-22T19:04:29-0700"}
{"pid":42429,"shlvl":1,"level":"INFO","dir":"/Users/cameron.pitt","message":"ZPLUG_LOADFILE is not found","trace":["__zplug::log::write::info:2","__zplug::io::file::load:3","/Users/cameron.pitt/.zplug/init.zsh:33","/Users/cameron.pitt/.zshrc:15","zsh:0"],"date":"2017-08-22T19:06:49-0700"}
{"pid":43402,"shlvl":2,"level":"INFO","dir":"/Users/cameron.pitt","message":"ZPLUG_LOADFILE is not found","trace":["__zplug::log::write::info:2","__zplug::io::file::load:3","/Users/cameron.pitt/.zplug/init.zsh:33","/Users/cameron.pitt/.zshrc:15","zsh:0"],"date":"2017-08-22T19:06:53-0700"}
{"pid":43402,"shlvl":2,"level":"INFO","dir":"/Users/cameron.pitt","message":"turn monitor on","trace":["__zplug::log::write::info:2","__zplug::job::polling::periodic:9","-zsh:1"],"date":"2017-08-22T19:06:55-0700"}

[heypoom]

In my case, a global node module named "touch" is symlinked in /usr/local/bin/touch, which does output all of that messages when zplug creates a new trace.log file upon shell startup. After I remove it, the problem seems to be gone.

Source: https://stackoverflow.com/questions/44923968/how-to-deactivate-bash-history-stats-print-when-opening-a-new-terminal-window-on

[cpitt]

@phoomparin Wow that's it! I have no idea how touch got installed..... searched my zsh history.... never installed it.... looks like it might be related to this yarn bug yarnpkg/yarn/issues/3824

[jsahlen]

@phoomparin Oh. Same thing for me—a locally installed copy was prioritized in $PATH. Thanks!

[soulomoon]

@phoomparin +1
rm /usr/local/bin/touch

[b4b4r07]

I'm going to delete the log feature in next release: #539 , so closing this once. Please feel free to let me know if you have any comments!