HVAC Condenser Coil Leak & Warranty

Outdoors AC Leaking Oil

This is a quick lesson or reminder to anyone who just purchased a new AC system or new construction home. Most HVAC come with ten year warranty. But you need to register your unit with manufacturer for warranty to be valid.

Outdoors AC Leaking Oil

Recently, our AC stopped cooling. Outside unit had visible oil leak. Apparently, oil is mixed in the refrigerant or coolant. Refrigerant evaporates leaving behind oil. So if you have oil leak, then you also have coolant leak. I figured that the fix would be simple as finding a small leaking part, replacing it, and then refilling refrigerant. Apparently our coil is leaking and that is essentially whole unit.

We called the company that installed HVAC originally. The guy initially scared me by saying that if we didn’t register the unit, then it probably is not under warranty and you cannot register now. It is only 3.5 years old unit.

Luckily, the company had registered it on their side, so all parts will be free. We still have to pay for labor which is still pretty high about $1100. But without warranty, it would have been another $1000 or so for the coil.

The Personal MBA

Lately, I have been following /r/financialfreedom. From there someone recommended to read this book. I wasn’t expecting much as I have read many business books but this one is actually really good. It basically summarize ideas and lessons from both business textbooks and popular business books. There is nothing new in it but it is nice to have all this information in one place.

There are a lot of concepts in this book that one can apply to their personal lives too like adopting habits or negotiating purchases.

A good read indeed.

Fisherman & Gun, Germs, and Steel

One of my favorite story is of an executive of a big company who goes to a resort town for a vacation. There he sees a fisherman with a few fish walking away from beach. Executive asks fisherman where he was going. Fisherman replies that he has caught enough fish for the day, now he will go sell these fish to fish vendor in market. Executive asks it is early in morning why don’t you catch more fishes. Fisherman says he has caught enough for him and his family. Executive asks so what he plans to do for rest of his day. Fisherman replies that he will go home, play with his kids, go for a walk with his wife, and hang out with friends in the evening.

Executive says to fisherman but if you stay a little longer, you can catch some more fishes. Then use that extra money to buy a bigger boat. Then catch even more fishes, so on until you have a fleet of fishing boats. Then he can negotiate better terms with fish vendors and make more money. Then he can open his own fish processing plant and sell fishes directly to many vendors all over the country. Then he will be rich.

Fisherman asks how long will it take, executive replies maybe 15 or 20 years. Fisherman asks then what he will do when he is rich. Executive says that then he can relax, play with his kids or at this point grand kids, go for walks with his wife, hang out with his friends. Fisherman just smiles.

This parable is meant to say that one doesn’t need a lot to enjoy life.

I have been reading Guns, Germs, and Steel by Jared Diamond. It is fascinating book. This book discusses how some societies and cultures came to dominate the world while others were subjugated to slavery and destruction. While there are many reasons for it, but one of the main reason seems to be that some cultures encouraged greed. That led to wars in addition to innovations. Which led to taking away resources from cultures that didn’t engage in greed or war.

So now I wonder what would happen in real life in this story. Perhaps executive will see that as an opportunity to expand his firms operations. Might buy big fishing boats and hire local fisherman to work for his firm. Because of his scale, he might be able to undercut the fisherman and force him to work longer or even quit fishing. Perhaps fisherman will become an employee of executive’s fishing company.

I guess the point is we romanticize simple life but sadly it is not possible anymore.

Back to WordPress

Last year, I moved my blog to Github pages. The main reason was that it was programmer centric way of blogging. I could write blog posts using Markdown in SublimeText, my natural habitat. To publish a post, I simply commit and push. And it would be fun to see git log history. I could edit old posts and not only me but everyone can see how it changed overtime. And most of all it was elegantly simple.

But there were some cons. I could not auto-post to social accounts without signing up for another service. If I wanted comments,  I would have to sign up on another different service. That would be no longer elegantly simple.

Then a few months ago, Github disabled a few Markdown plugins which meant I had to update a few posts. Not a big deal but I didn’t want to deal with it again.

So after some contemplation, I decided to move back to WordPress. My biggest concern with WordPress is security issues but most of these issues come from insecure plugins or themes. As long as, I am mindful of which plugins or themes to install, it should not be a big issue.

SublimeText is awesome but WordPress’s editor is also nice. It is pleasure to be using it right now. It generating pretty clean HTML too.

I liked the automatic backup when using git to publish a site but my hosting provides automatic backups and then I have scheduled job to do my own backups. So using Github pages just for backup purposes was not that important.

Then of course, WordPress provides easy ways to post to various social sites, manage comments, categorize posts, and, search capabilities, etc.

The big advantage of WordPress is that I can now just focus on writing blog posts instead of looking for ways to add features to Github pages.

Magento – Get All Products with Categories in a Flat View

SELECT 
    w1.website_id,
    w1.name as website_name,
    s1.store_id,
    s1.name as store_name,
    p1.entity_id as product_id,
    p1.sku,
    pname.value as product_name,
    url.value as url_path,
    small_image.value as small_image,
    msrp.value as msrp_price,
    price.value as price,
    p1.created_at as product_created_at,
    p1.updated_at as product_updated_at,
    visibility.value as visibility,
    pstatus.value as status,
    case
        when
            (pstatus.value = 1
                and visibility.value > 1)
        then
            1
        else 0
    end as enable_flag,
    c1.entity_id as category_id,
    cname.value as category_name,
    c1.parent_id,
    c1.created_at as category_created_at,
    c1.updated_at as category_updated_at
FROM
    catalog_product_entity p1
        inner join
    eav_attribute p_attr ON p1.entity_type_id = p_attr.entity_type_id
        and p_attr.attribute_code = 'name'
        inner join
    catalog_product_entity_varchar pname ON pname.entity_id = p1.entity_id
        and pname.attribute_id = p_attr.attribute_id
        inner join
    eav_attribute p_attr2 ON p1.entity_type_id = p_attr2.entity_type_id
        and p_attr2.attribute_code = 'url_path'
        inner join
    catalog_product_entity_varchar url ON url.entity_id = p1.entity_id
        and url.attribute_id = p_attr2.attribute_id
        and pname.store_id = url.store_id
        inner join
    eav_attribute p_attr3 ON p1.entity_type_id = p_attr3.entity_type_id
        and p_attr3.attribute_code = 'small_image'
        inner join
    catalog_product_entity_varchar small_image ON small_image.entity_id = p1.entity_id
        and small_image.attribute_id = p_attr3.attribute_id
        and pname.store_id = small_image.store_id
        inner join
    eav_attribute p_attr4 ON p1.entity_type_id = p_attr4.entity_type_id
        and p_attr4.attribute_code = 'msrp'
        inner join
    catalog_product_entity_decimal msrp ON msrp.entity_id = p1.entity_id
        and msrp.attribute_id = p_attr4.attribute_id
        and pname.store_id = msrp.store_id
        inner join
    eav_attribute p_attr5 ON p1.entity_type_id = p_attr5.entity_type_id
        and p_attr5.attribute_code = 'price'
        inner join
    catalog_product_entity_decimal price ON price.entity_id = p1.entity_id
        and price.attribute_id = p_attr5.attribute_id
        and pname.store_id = price.store_id
        inner join
    eav_attribute p_attr6 ON p1.entity_type_id = p_attr6.entity_type_id
        and p_attr6.attribute_code = 'visibility'
        inner join
    catalog_product_entity_int visibility ON visibility.entity_id = p1.entity_id
        and visibility.attribute_id = p_attr6.attribute_id
        and pname.store_id = visibility.store_id
        inner join
    eav_attribute p_attr7 ON p1.entity_type_id = p_attr7.entity_type_id
        and p_attr7.attribute_code = 'status'
        inner join
    catalog_product_entity_int pstatus ON pstatus.entity_id = p1.entity_id
        and pstatus.attribute_id = p_attr7.attribute_id
        and pname.store_id = pstatus.store_id
        inner join
    catalog_category_product ccp ON ccp.product_id = p1.entity_id
        inner join
    catalog_category_entity c1 ON c1.entity_id = ccp.category_id
        inner join
    eav_attribute c_attr ON c1.entity_type_id = c_attr.entity_type_id
        and c_attr.attribute_code = 'name'
        inner join
    catalog_category_entity_varchar cname ON cname.entity_id = c1.entity_id
        and cname.attribute_id = c_attr.attribute_id
        and pname.store_id = cname.store_id
        inner join
    catalog_category_product_index store1 ON store1.product_id = p1.entity_id
        and store1.category_id = c1.entity_id
        inner join
    core_store s1 ON store1.store_id = s1.store_id
        inner join
    core_website w1 ON s1.website_id = w1.website_id

OpenShift Error: Layer 7 Wrong Status, Invalid Response

I have been playing with OpenShift for past several hours. It looks great. But a while back I started to get 503 Internal Server error.

When I checked logs using rhc tail , I saw this error: Layer 7 Wrong Status, Invalid Response 404.

I spent an hour or so troubleshooting. Turns out the issue was Netbeans had added src/main/web/app/WEB-INF/jboss-web.xml when I ran the application locally on my machine. I committed this file, thinking I might need it. Deleting it from repo and repushing, fixed the issue.