seen from Iraq
seen from Chile
seen from Australia
seen from Russia
seen from Italy
seen from United States
seen from Armenia
seen from Germany
seen from Singapore
seen from United States
seen from United States
seen from United States
seen from T1
seen from Germany
seen from United States
seen from Germany
seen from United States
seen from Netherlands
seen from United Kingdom
seen from United States
Lockfiles richtig nutzen: Reproduzierbarkeit gegen Sicherheit
Ein Lockfile ist die stille Instanz in fast jedem Projekt. Es entscheidet, welche Version jeder Abhängigkeit wirklich installiert wird, und trotzdem schaut kaum jemand hinein. Dabei liegt genau hier der Punkt, an dem Reproduzierbarkeit und Sicherheit sich treffen und manchmal gegeneinander ziehen. Wer den Umgang mit package-lock.json, yarn.lock, poetry.lock oder Cargo.lock versteht, hat einen der…
由 pnpm 做出來的效能比較：npm、yarn 以及 pnpm
找資料的時候看到 pnpm 有在做幾個常見的 javascript package manager 的比較：「Benchmarks of JavaScript Package Managers」。 裡面測了九個項目，其中前八個剛好就是 cache 的有無、lockfile 的有無以及 node_modules 的有無，這三者的組合剛好八個，最後一個是測 update 的速度。 pnpm 因為用了 hard link，我先跳過去，只先關注 npm 與 yarn 的差異。 其中幾個比較重要的項目是 (由最重要開始列)： with cache, with lockfile, with node_modules：這個會是一般開發的情境。 update：套件有更新時的時間。 with lockfile：這個會是第一次 clone 下來後的環境，以及 CI 的環境。 在一般開發環境下，npm…
View On WordPress
Irritating chef-client zombie lock
Occasionally attempting to run chef-client will result in the message INFO: Chef client is running, will wait for it to finish and then run.. Yet a cursory ps aux | grep chef will show no running chef-client. Recovering from this involves first locating the lock file and then explicitly killing the process associated with it.
$ sudo -i find /var/ -iname "*chef*" -print | grep client /var/chef/cache/cookbooks/chef-client /var/chef/cache/cookbooks/chef-client/templates/default/debian/default/chef-client.erb /var/chef/cache/cookbooks/chef-client/templates/default/debian/init.d/chef-client.erb /var/chef/cache/cookbooks/chef-client-wrapper /var/chef/cache/cookbooks/chef-client-wrapper/templates/default/chef-client.erb
$ sudo -i lsof /var/chef/cache/chef-client-running.pid COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME chef-clie 32098 root 7uW REG 8,17 0 70386635 /var/chef/cache/chef-client-running.pid
$ kill -15 32098
Then re-run chef-client and all should be fine.
