<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tips on Notes</title>
    <link>https://www.simplicidade.org/tags/tips/index.xml</link>
    <description>Recent content in Tips on Notes</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>melo@simplicidade.org (Pedro Melo)</managingEditor>
    <webMaster>melo@simplicidade.org (Pedro Melo)</webMaster>
    <copyright>(c) 2016 Pedro Melo.</copyright>
    <atom:link href="/tags/tips/index.xml" rel="self" type="application/rss+xml" />
    <atom:link rel="hub" href="https://pubsuhhubbub.superfeedr.com/"/>
    
    <item>
      <title>User interaction is not allowed</title>
      <link>https://www.simplicidade.org/notes/2017/03/24/user-interaction-is-not-allowed/</link>
      <pubDate>Fri, 24 Mar 2017 18:23:03 +0000</pubDate>
      <author>melo@simplicidade.org (Pedro Melo)</author>
      <guid>https://www.simplicidade.org/notes/2017/03/24/user-interaction-is-not-allowed/</guid>
      <description>&lt;p&gt;This errors happened to me sometime ago, but today I saw it again on a coworker Mac.&lt;/p&gt;

&lt;p&gt;You&amp;rsquo;ll get the error on the Terminal, with commands that want to use MacOS Keychain passwords. I&amp;rsquo;m sure there is another element at work here, but I could not find it.&lt;/p&gt;

&lt;p&gt;In this case, the error on &lt;code&gt;docker login&lt;/code&gt; was this (you&amp;rsquo;ll get a similar error with &lt;code&gt;git fetch&lt;/code&gt; or &lt;code&gt;git pull&lt;/code&gt;):&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;Error saving credentials: error storing credentials - err: exit status 1, out: `User interaction is not allowed`
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;The command line tool is trying to access a Keychain Item, and this item is protected to only be used by some applications. On normal conditions, this would trigger a graphical pop-up asking for permission for this new application to access said item, but in this case he fails to launch the pop-up and therefore, rejects the action.&lt;/p&gt;

&lt;p&gt;To fix, open the Keychain Access application, search for the domain you were trying to access (in the case of &lt;code&gt;docker login&lt;/code&gt; it would be the private registry address, or &lt;code&gt;hub.docker.com&lt;/code&gt;), edit the entry, select the tab &amp;ldquo;Access Control&amp;rdquo;.&lt;/p&gt;

&lt;p&gt;&lt;img src=&#34;https://www.simplicidade.org/img/user_interaction_not_allowed_screenshot_1.png&#34; alt=&#34;&#34; /&gt;&lt;/p&gt;

&lt;p&gt;You can then add permission to the application you need by taping the &amp;ldquo;+&amp;rdquo; button on the lower left, and picking the correct file, but I don&amp;rsquo;t have a easy way to discover what is the correct file to add. If the problem is &lt;code&gt;docker login&lt;/code&gt; you could first try to add the command &lt;code&gt;/Applications/Docker.app/Contents/Resources/bin/docker-credential-osxkeychain.bin&lt;/code&gt;. For &lt;code&gt;git pull&lt;/code&gt; or &lt;code&gt;git fetch&lt;/code&gt; issues, try to add &lt;code&gt;/Library/Developer/CommandLineTools/usr/libexec/git-core/git-credential-osxkeychain&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;If you don&amp;rsquo;t know which command line application is the culprit, you can just disable access control for this password item by making sure that the &amp;ldquo;Allow all applications to access this item&amp;rdquo; option is selected and &amp;ldquo;Save Changes&amp;rdquo;.&lt;/p&gt;

&lt;p&gt;You should try to find the correct application if possible, but the second options will work. No security, but it would work.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>brew info</title>
      <link>https://www.simplicidade.org/notes/2017/03/17/brew-info/</link>
      <pubDate>Fri, 17 Mar 2017 08:40:15 +0000</pubDate>
      <author>melo@simplicidade.org (Pedro Melo)</author>
      <guid>https://www.simplicidade.org/notes/2017/03/17/brew-info/</guid>
      <description>&lt;p&gt;Small, quick, tip: before installing the latest wow app with &lt;code&gt;brew install wow-app&lt;/code&gt;, take a minute to scan &lt;code&gt;brew info wow-app&lt;/code&gt; in a separate terminal.&lt;/p&gt;

&lt;p&gt;Two main reasons:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;some of the time, it will tell you that you have a lot of options to enable or disable some features. You might need some of them, and usually this requires a new compilation;&lt;/li&gt;
&lt;li&gt;most of the time this includes what next steps are required of you to properly configure, and you can read them while the app installs.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Either way, this will save you some time, and you might learn something new.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Tip: notify long running terminal jobs via Growl</title>
      <link>https://www.simplicidade.org/notes/2005/10/01/tip-notify-long-running-terminal-jobs-via-growl/</link>
      <pubDate>Sat, 01 Oct 2005 20:10:18 +0000</pubDate>
      <author>melo@simplicidade.org (Pedro Melo)</author>
      <guid>https://www.simplicidade.org/notes/2005/10/01/tip-notify-long-running-terminal-jobs-via-growl/</guid>
      <description>&lt;p&gt;Sometimes you need to run some script or program that will take a long time.&lt;/p&gt;

&lt;p&gt;What I usually do is opening a new window, start the script, and then minimize or send to the back that terminal, leaving a small corner visible to serve as a status. I could glance to the visible corner and look for the prompt to see if had ended.&lt;/p&gt;

&lt;p&gt;Now, I use this little super simple script (could also be a bash alias, probably):&lt;/p&gt;

&lt;pre&gt;&lt;code&gt; #!/bin/sh
 #
 # Runs script, and prints a notification with growl when it finishes
 #

 $*
 growlnotify -m &amp;quot;Script &#39;$*&#39; completed&amp;quot; -s &amp;quot;Background script notification&amp;quot; &amp;amp;
 # --script ends here--
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;My version is called &lt;code&gt;n&lt;/code&gt;, just &lt;code&gt;n&lt;/code&gt;. So I can type &lt;code&gt;n update_mini_cpan&lt;/code&gt; and have a nice notification when it finishes via Growl.&lt;/p&gt;

&lt;p&gt;Test with &lt;code&gt;n ls -la&lt;/code&gt; if you want.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Some things you learn or discover</title>
      <link>https://www.simplicidade.org/notes/2005/02/19/some-things-you-learn-or-discover/</link>
      <pubDate>Sat, 19 Feb 2005 15:53:21 +0000</pubDate>
      <author>melo@simplicidade.org (Pedro Melo)</author>
      <guid>https://www.simplicidade.org/notes/2005/02/19/some-things-you-learn-or-discover/</guid>
      <description>&lt;p&gt;During the last 48 hours a lot of things have happened and I dealt with a lot of hardware. I took some notes for future reference.&lt;/p&gt;

&lt;p&gt;First, always take a camera with you. Take pictures of everything, and then catalog them. You can always go back and see how things where inside your servers or around them. Don&amp;rsquo;t remember if a ethernet cable is connected to the onboard ethernet or the external one? Just go and look.&lt;/p&gt;

&lt;p&gt;Second, some vendors have some &lt;a href=&#34;http://www.flickr.com/photos/melo/sets/127151/&#34; title=&#34;The missing screw&#34;&gt;strange notions about accessibility&lt;/a&gt;, so be prepared.&lt;/p&gt;

&lt;p&gt;Third, forget about boot floppies and CDs, just install a recent linux distribution in a brand new IDE disk, and use that as a rescue system.&lt;/p&gt;

&lt;p&gt;Fourth, make sure your backups work, and make sure they are compreensive.&lt;/p&gt;

&lt;p&gt;Fifth, if your monitoring system is hosed, don&amp;rsquo;t wait a month or two to put the new one in place.&lt;/p&gt;

&lt;p&gt;That&amp;rsquo;s all folks,&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Mail.app enhancements</title>
      <link>https://www.simplicidade.org/notes/2004/06/24/mail.app-enhancements/</link>
      <pubDate>Thu, 24 Jun 2004 17:39:24 +0000</pubDate>
      <author>melo@simplicidade.org (Pedro Melo)</author>
      <guid>https://www.simplicidade.org/notes/2004/06/24/mail.app-enhancements/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://nowhereland.nunonunes.org/&#34;&gt;Nuno&lt;/a&gt; was complaining about the lousy support of multiple profiles in Mail.app. I agree with him, but today I noticed that I already was using some obscure features that make it all easy :).&lt;/p&gt;

&lt;p&gt;First, in the preferences account panel, you can put several email addresses, comma separated. They will all show up in the drop-down in the Compose window, so you can change the From address easily. With &lt;a href=&#34;http://home.insightbb.com/%7En9yty1/MailEnhancer/&#34;&gt;MailEnhancer&lt;/a&gt;, you can even change the signatures auto-magically.&lt;/p&gt;

&lt;p&gt;For this and more plugins, try this &lt;a href=&#34;http://maczealots.com/&#34;&gt;MacZealots&lt;/a&gt; &lt;a href=&#34;http://maczealots.com/articles/mail-enhancements/&#34;&gt;article&lt;/a&gt;, or this &lt;a href=&#34;http://www.tikouka.net/mailapp/&#34;&gt;list&lt;/a&gt;.&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>