Automatic email forwarding for certain emails can be quite handy. Here is a quick guide how you create forwarding filters in Google Mail.
To start off with we need to add a new forwarding email address and verify that we are allowed to forward emails to this address. In order to do this open up Google Mail settings and click the Forwarding and POP/IMAP tab.
Within the upcoming tab click on the Add forwarding address button and enter an email address in the new dialogue.
As soon as the new forwarding email address is added the owner should get an email containing a verification code. With this code one can verify that one is allowed to forward emails to this address. The code can be entered within the Forwarding and POP/IMAP tab.
After verification emails can be forwarded to this address. Google Mail provides two options for forwarding emails. First option is to forward all emails to a certain address. The second option is to define filters which identify certain emails and forward these to a specific email address. The later option is of interest for us.
In order to create a new filter navigate to the settings Filters tab. Here one can see existing and create new filters.
Creating a filter is very simple. First of all one has to define the filter criteria, which can also be done by simply typing search terms into Google Mail’s email search field.
Secondly, one has to define which actions should be applied to emails matching the defined filter criteria. In order to forward emails one has to check the Forward it to action and select the desired destination email address.
After creating the filter all actions, including Forward it to, should be applied to emails matching the filter criteria.
As I prefer Git as version control system I often end up working with it as client for Subversion (SVN) repositories. Recently, I had to interact with a SVN repository which was moved to another location after my initial cloning.
As Git stores the SVN URL and includes it into the SHA-1 hash calculation you can end up having the following problem as soon as you change the repository URL and try to push your changes to the remote repository:
Unable to determine upstream SVN information from HEAD history.
Perhaps the repository is empty. at /usr/libexec/git-core/git-svn line 519.
The problem is that by changing the SVN repository URL calculated SHA-1 hashes differ and Git cannot determine the proper commit to push to. In order to overcome these problems you can add the rewriteRoot option to your configuration file and afterwards change the URL:
Recently I had some problems staying under my monthly mobile bandwidth cap. One reason being an increased travel and tethering time. Although working on an up to date system is preferable most of the time, I started to turn off automatic updates on my Mac while working using my mobile connection.
The automatic update settings can be found under System Preferences -> App Store.
When traveling you can uncheck all but the “Automatically check for updates” check box. That way you get notified if new updates are available and can set yourself a reminder to update your system when a landline connection is available.
When working on SOA projects I am used to create some developer test suites for myself in order to do some initial web service QA. For this purpose SoapUI is a commonly used functional testing tool. Depending on the project these “small” test suites can actually become quite big. That is fine as long only one service endpoint has to be tested, however most likely you end up with several endpoints for different development stages (development, integration, production). Gladly SoapUI provides a functionality to set web service endpoints for all service request. Only problem is to find this functionality 😉
To demonstrate the functionality I took a standard global weather service and created a small SoapUI project.
Within the project I created some requests and test suites for both operations. Furthermore, I added some additional endpoints to the GlobalWeatherSoap Interface. You can access this view by double clicking the respective web service interface.
In order to set the endpoint required for the next test run, you have to select it from the list and click the Assign button in the top menu. As result an additional dialogue opens which provides several options.
In this example we want to set the new endpoint for all requests and test requests, therefore this option has to be selected. Afterwards all requests point to the new endpoint and the test suite can be executed.
Just required some Oracle Metadata Repository (MDS) partitions for some testing. If you ever get to the same situation just use MDS_INTERNAL_COMMON.getOrCreatePartitionID procedure which is shipped with the MDS Schema when installing it using the Repository Creation Utility (rcu):
While setting up my new developer VM I came to the point where I had to configure git again. As I keep on configuring git on several VMs and systems required for and provided by my clients, I thought it might be a good idea to create a small shell script which sets up my standard configuration.
Options I normally use are:
# Set username
git config user.name
# Set user email
git config user.email
# Set standard editor
git config core.editor
# Activate colors in output
git config color.ui true
# Some helpful aliases
git config alias.s status
git config alias.au '!git add -u && git status'
git config alias.spull 'svn rebase'
git config alias.spush 'svn dcommit'
Just experienced some weird behaviour on my fresh Oracle Enterprise Linux 6.5 installation. After installing a fresh VM I updated the system using system tools. Everything seemed fine until I rebooted the VM and started a new Gnome session. Unfortunately desktop icons were missing. The icons are normally provided by a nautilus process which starts on login. However, since the update nautilus kept being killed by signal 11 (SIGSEGV). Nevertheless, Gnome kept trying to open a new nautilus process which in ended up in a nautilus starting and killing spree 😉
In order to solve the problem I had a look at dmesg:
$ dmesg | tail
Within the output I found that not nautilus was the core problem but the librsvg library used by it. So I checked the software center application and found two versions:
After the first update process version 2.26.0-6.el6_5.2 was installed, so I tried 2.26.0-6.el6_5.3. Afterwards nautilus could start properly and the problem seems to be solved for the moment.
I just installed a fresh Oracle Linux 6.5. (64 Bit) development virtual machine for myself. One tool I learned to appreciate a lot is JD-GUI. Unfortunately, the binary provided does not run on a 64 Bit Linux (virtual) box as it was compiled for i686 architecture. However, in order to run it without any errors just install the following packages: