macos-sierra

Maven with Surefire (TestNG) is slow after update to MacOS Sierra

自古美人都是妖i 提交于 2019-12-02 19:44:26
Before the update my MacBook Pro to MacOs Sierra, the command: mvn clean install -U took about 40 sec to run, with several hundreds of tests in several maven sub-modules. After the update to MacOS Sierra, with no changes to the code, the same command takes over 12 minutes. It looks to me that the when the Surefire plugin is going to print the result of the current module, it hangs for 2-3 minutes before continuing. The speed of the test-execution up to this point is as fast as before the update to MacOS Sierra. Example of a TestNG result printout from on of the modules: Tests run: 101,

Jenkins does not start on macOS 10.12 (Sierra)

社会主义新天地 提交于 2019-12-02 19:06:34
After upgrading my macOS to Sierra, when I start Jenkins using launchctl load I cannot connect to localhost:8080. If I call launchctl load again, I see response "service already loaded". There is no log file at the default location /var/log/jenkins/ (as set in jenkins-ci.plist). I also tried to create jenkins.log there and chown to jenkins user, but still nothing is printed there. If I try to start Jenkins using java -jar jenkins.war, I can connect to localhost, but Jenkins runs as a new installation. I have the latest JRE 1.8.0_102 installed. How to diagnose the problem? Seems that Sierra

Installing pip on macOS Sierra

我们两清 提交于 2019-12-02 18:43:12
I've been trying to install pip on macOS sierra via brew, but every time it completes without installing the binaries in /usr/local/Cellar/python/2.7.13/bin . I've tried: MacBook-Pro ➜ brew reinstall python then: MacBook-Pro ➜ ~ which pip pip not found I found the path to python, which is /usr/local/Cellar/python/2.7.13/bin but no binary for pip there. I also tried the easy_install approach: MacBook-Pro ➜ sudo easy_install pip Traceback (most recent call last): File "/usr/bin/easy_install-2.7", line 11, in <module> load_entry_point('setuptools==18.5', 'console_scripts', 'easy_install')() File

MySQL Compatibility with MacOS Sierra

最后都变了- 提交于 2019-12-02 17:39:58
Does anybody know of any compatibility issues or quirks with MySQL Community Server/Workbench on macOS Sierra? I recently did an installation on a Mac that had never held MySQL before and it doesn't seem to be working correctly. (Now maybe I just set it up wrong, but the since the installer offers no advanced options that doesn't seem to be the case.) I can create schemas and tables, but when I go to actually query the table nothing happens. The activity indicator spins endlessly. I took a look at Activity Monitor and it doesn't show mysqld actually doing anything—the whole setup just appears

.ssh/config: “Bad configuration option: UseKeychain” on Mac OS Sierra 10.12.6

雨燕双飞 提交于 2019-12-02 17:37:06
I am trying to set up my ssh config on the Mac (Mac OS Sierra 10.12.6) in such a way that it stores the passphrase for my ssh key in the keychain. Previously I could do that with ssh-add -K ~/.ssh/id_rsa But recently this doesn't seem to work anymore. Following this article there seems to be a change in the behaviour of the ssh config in Mac OS > 10.12.2 and the recommended way to fix this issue is to add UseKeychain yes to your ssh config. So here's my .ssh/config section the Host * : Host * Port 22 ServerAliveInterval 60 ForwardAgent yes IdentityFile ~/.ssh/id_rsa AddKeysToAgent yes

Clipboard failure in tmux + vim after upgrading to MacOS Sierra

∥☆過路亽.° 提交于 2019-12-02 17:00:58
Yesterday, I upgraded to MacOS Sierra and it broke my clipboard functionality in my tmux + neovim setup. Here is the behavior: I can use the standard ctrl+c, ctrl+p to copy/paste between system <-> vim I can yank/paste between two VIM instances when NOT in a tmux session I cannot yank/paste between two VIM instances when in a tmux session Whenever I use the clipboard in vim within a tmux session, I get the following vim error: clipboard: error: My .vimrc is huge, but here's what I think might be relevant: set clipboard=unnamed In my .tmux.conf (also truncated for brevity): set -g prefix ` #

Unable to launch IBM MobileFirst foundation studio 8.0 in eclipse

杀马特。学长 韩版系。学妹 提交于 2019-12-02 02:19:52
问题 OS Version: Mac OS Sierra: 10.12.3 Eclipse Version: Neon.3 Release (4.6.3) Steps Downloaded the latest Eclipse version. Installed IDE for Java Developers. Installed IBM mobile first foundation studio 8.0 from Eclipse Marketplace. Restarted the Eclipse No mobile first option available in Eclipse. 回答1: In MobileFirst v8.0 you no longer use Studio to create "projects" to create Hybrid apps, rather you use the Cordova CLI to create a Cordova app, and also use the Cordova CLI to add the

Unable to launch IBM MobileFirst foundation studio 8.0 in eclipse

…衆ロ難τιáo~ 提交于 2019-12-02 00:19:39
OS Version: Mac OS Sierra: 10.12.3 Eclipse Version: Neon.3 Release (4.6.3) Steps Downloaded the latest Eclipse version. Installed IDE for Java Developers. Installed IBM mobile first foundation studio 8.0 from Eclipse Marketplace. Restarted the Eclipse No mobile first option available in Eclipse. In MobileFirst v8.0 you no longer use Studio to create "projects" to create Hybrid apps, rather you use the Cordova CLI to create a Cordova app, and also use the Cordova CLI to add the MobileFirst SDK (plug-in) to the Cordova app. The Studio plug-in for Eclipse in v8.0 is used to expose functionality

Nokogiri fails to install on OS X

ぐ巨炮叔叔 提交于 2019-12-01 14:34:26
There are many posts on this issue, however, there can be a couple of reasons why Nokogiri (version 1.6.x, 1.7.x or 1.8.x) fails to install on OS X. Related articles: OS X 10.6 Installing Nokogiri cann't install nokogiri 1.6.1 on Mac OS X 10.9 Maveriks Command Line not installed: This is the easiest one to check and fix: run xcode-select --install in a terminal window to install it, then try installing Nokogiri one more time by running gem install nokogiri . Some are reporting that they used gem install nokogiri -- --use-system-libraries Libxml, libxlt are too recent: This situation is due to

Nokogiri fails to install on OS X

微笑、不失礼 提交于 2019-12-01 12:45:11
问题 There are many posts on this issue, however, there can be a couple of reasons why Nokogiri (version 1.6.x, 1.7.x or 1.8.x) fails to install on OS X. Related articles: OS X 10.6 Installing Nokogiri cann't install nokogiri 1.6.1 on Mac OS X 10.9 Maveriks 回答1: Command Line not installed: This is the easiest one to check and fix: run xcode-select --install in a terminal window to install it, then try installing Nokogiri one more time by running gem install nokogiri . Some are reporting that they