This post was composed on March 20, 2018, and I never published it. I thought it was interesting looking back.
March 20, 2018
That is where all the money is at, right? Strive for what you want to be for your career, if all fails, use software development as a fallback career? Work for Google? Maybe Apple? How about Amazon? Or Facebook?
My WordPress site is now on AWS! I spent a good chunk of my time debugging the All-in-One WP Migration plugin to get my migration working, and I finally realized I skipped an important step in their migration documentation:
It’s funny, I was confident I was going to post more often this year. I promise myself I would back in January, and here we are, half a year later, for my second post of the year. So many things have happened, which I hope to write about in later posts.
I recently took an AWS class under the UCLA extension program. It felt like a long 10 weeks, but I am very glad I went through with it. With some AWS experience now under my belt, I feel like I have enough knowledge to start my migration from Hostmonster to AWS.
Happy new year! I have been lazy with my posts the past months (years?) so as part of my new resolutions I plan to write more.
While I am here, I will leave a tip on how to better yourself as a software developer/enthusiast: practice, learn, practice. Continue to learn, and repetition is key to nailing information in your brain! Also, check out https://www.pluralsight.com or https://www.lynda.com for study material.
While working on ETL (Extract, Transform, Load) projects at work, I ran into an unusual issue using xlsjs:
Error: Unrecognized ExtProp type: 2 0
After digging through the `xlsjs` source code, I realized that it was following the MS-XLS Specifications, as it should, and section 2.5.108 ExtProp, the extType value that I was running into was not defined in the table. Seeing as the format structure was related to formatting, I forked the `xlsjs` library and created a version that was more forgiving.
If you are running into this issue and want a workaround, try xlsjs2.
I get frustrated when I browse a file from a git repository only to realize its history was lost due to improper renaming/moving of the file. It seems common for developers to manually rename/move a file in a git repository by using regular file system commands rather than git commands.
For example, let’s look at the following:
$ mkdir test
$ cd test
$ git init
$ echo "hi" > test.txt
$ git add test.txt
$ git commit -m"add test.txt"
$ mv test.txt test2.txt
$ git status
So what have we here? We start off by creating a new directory called test. We then go into the directory and start a new local git repository using git init. Next we create a new file called test.txt that contains simple text “hi”. test.txt is then added and committed to the repository. Finally, we use the mv command to rename the file to test2.txt.
git status shows us the result:
Result of git status
This is not what we were expecting. This shows that the original file test.txt was deleted and now there is an untracked new file called test2.txt, when it really should say that test.txt was renamed to test2.txt.
Btw, this goes for moving files as well. For example, rather than renaming the file, if it was moved to, say, a different folder, e.g. newFolder/test.txt, the result would be the same.
So how can this be solved? It’s actually not far off from the steps above. Let’s start with backtracking by reverting the rename:
When running EB CLI, do you run into the following error?
$ eb deploy
Traceback (most recent call last):
File "C:Python34libsite-packagespkg_resources__init__.py", line 635, in _build_master
ws.require(__requires__)
File "C:Python34libsite-packagespkg_resources__init__.py", line 942, in require
needed = self.resolve(parse_requirements(requirements))
File "C:Python34libsite-packagespkg_resources__init__.py", line 834, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (colorama 0.3.3 (c:python34libsite-packages), Requirement.parse('colorama==0.3.7'), {'awsebcli'})
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:Python34Scriptseb-script.py", line 5, in <module>
from pkg_resources import load_entry_point
File "C:Python34libsite-packagespkg_resources__init__.py", line 2900, in <module>
@_call_aside
File "C:Python34libsite-packagespkg_resources__init__.py", line 2886, in _call_aside
f(*args, **kwargs)
File "C:Python34libsite-packagespkg_resources__init__.py", line 2913, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "C:Python34libsite-packagespkg_resources__init__.py", line 637, in _build_master
return cls._build_from_requirements(__requires__)
File "C:Python34libsite-packagespkg_resources__init__.py", line 650, in _build_from_requirements
dists = ws.resolve(reqs, Environment())
File "C:Python34libsite-packagespkg_resources__init__.py", line 829, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'colorama==0.3.7' distribution was not found and is required by awsebcli
I ran into this error today. Apparently it was caused by installing AWS CLI after EB CLI: pip install awscli
Reinstalling EB CLI solved the issue: pip install awsebcli
I have been learning React for the past few weeks, and I am loving it. I spent today learning react-router at https://github.com/reactjs/react-router-tutorial. After going through it and implementing a lot of it in my app, I realized that it did not cover one thing that I really need: dynamic page title.
I have googled and looked at different examples of how others have done it (e.g. react-document-title, document.title) but I finally decided to tinker on my own and see if I can come up with my own implementation. (I know… another one???)
My sample code will be added to the result of lesson 3 from the tutorial I linked above:
I was routinely upgrading my packages on Homebrew when I ran into the following error:
$ brew upgrade
==> Upgrading 1 outdated package, with result:
homebrew/php/php70 7.0.4
==> Upgrading homebrew/php/php70
==> Downloading https://php.net/get/php-7.0.4.tar.bz2/from/this/mirror
Already downloaded: /Library/Caches/Homebrew/php70-7.0.4
==> ./configure --prefix=/usr/local/Cellar/php70/7.0.4 --localstatedir=/usr/local/var --sysconfdir=/usr/local/etc/php/7.0 --with-config-file-path=/usr/local/etc/php/7.0 --wi
Last 15 lines from /Users/johnro/Library/Logs/Homebrew/php70/01.configure:
checking for OpenSSL support... yes
checking for Kerberos support... /usr
checking whether to use system default cipher list instead of hardcoded value... no
checking for krb5-config... /usr/bin/krb5-config
checking for RAND_egd... no
checking for pkg-config... no
checking for OpenSSL version... >= 0.9.8
checking for CRYPTO_free in -lcrypto... yes
checking for SSL_CTX_set_ssl_version in -lssl... yes
checking for PCRE library to use... bundled
checking whether to enable the SQLite3 extension... yes
checking bundled sqlite3 library... yes
checking for ZLIB support... yes
checking if the location of ZLIB install directory is defined... no
configure: error: Cannot find libz
Of course, I did the first thing I always do when running into an error, Google it! And I found this link that suggested running the following: