-
-
Where has Technitribe been for the last 2 years? The short answer: in domain limbo.
Christmas Islands
.cxis a Christmas Islands top-level domain (TLD). I did not have the domain set to auto-renew because I was trying to get away from my old registrar. At the time it was expiring I didn’t have the cash on hand to renew it. I will admit, I did not read all the Term & Conditions for the.cxTLD before registering. I guess I really screwed the pooch there.It turns out that if you have a
.cxdomain, and it expires, then you have a problem. They will effectively hold it hostage for a period of 4 months. During this time you have the “option” to restore the domain, but at the cost of $400.00 USD. Like I said, I was not very cash flush at the time.Waiting Period
Shortly after the domain expired I moved across the country. While getting set up in my new location the domain left the restoration period and was open to general registration again. As is typical, a reseller had squatted the
lnx.cxdomain and bought it as soon as it became available. I resigned myself to my fate, I would have to let it go for a while.Return of lnx.cx
The blog is now back! A few weeks ago I finally had the cash necessary to register it from a new registrar who isn’t evil (Netim). We have a new SSL Certificate issued by Let’s Encrypt, no more untrusted RapidSSL security alerts in your browser. And, as an aside, the setup for installing this new certificate was incredibly easy. I am genuinely surprised at how smooth it was using the certbot tool.
What’s Next?
I need to start writing more blog posts! I might shift the focus of the blog from being so Tech focused and open it up to capture some of my other interests, too. Such as woodworking. I really enjoy making and restoring furniture. I should write some blog posts about that.
-
20 Jan 2017
[Updated] GitHub + Gmail — Filtering for Review Requests and Mentions
Written by Tim Bielawa
Update – 2017-01-27
Just 3 days after publishing this blog post GitHub made a new blog post:
Pull request reviews are a great way to share the weight of building software, and with review requests you can get the exact feedback you need.
To make it easier to find the pull requests that need your attention, you can now filter by review status from your repository pull request index.
Source: Filter pull request reviews and review requests
I have tried this out and it’s great! Like most everything else on GitHub it’s very intuitive and simple to use. I won’t steal their thunder and describe it all here. So go check out the blog post for yourself and read up on the details (screenshots included!).
Continue reading if you’re still interested in incorporating this kind of filtering and labeling into your Gmail account.
The Problem
I’ve been looking for a way to filter my GitHub Pull Request lists under the condition that a review is requested of me. The online docs didn’t show any filter options for this, so I checked out the @GitHubHelp twitter account. The answer was there on the front page — they don’t support filtering PRs by
review-requested-by:meyet:@zaghnaboot Adding a filter for reviewers is definitely on our radar, though I don’t have a specific timeline to share. –SJ
— GitHub Support (@GitHubHelp) January 19, 2017
So what is one to do? I’m using Gmail so I began considering what filter options were available to me there. My objectives were to clearly label and highlight:
- PRs where review has been requested
- Comments where I am
@mention‘d
Interested in knowing more? Read on after the break for all the setup details.
-
Have you ever had a sub-select where you really needed to reference a value in the outer query? I know I have! The naive way would be to run the outer query and then loop over the results running the inner query on each one. Luckily, there’s a better way. The Correlated subquery. Check it out! The example given is
SELECT employee_number, name FROM employees AS Bob WHERE salary > ( SELECT AVG(salary) FROM employees WHERE department = Bob.department);See how the sub-select references the outer query? It’s SQL magic.
-
bitmath is a Python module I wrote which simplifies many facets of interacting with file sizes in various units as python objects. A few weeks ago version 1.3.1 was released with a few small updates.
Updates
- New function: bitmath.parse_string_unsafe(), a less strict version of bitmath.parse_string()
This new function accepts inputs using non-standard prefix units such as single-letter, or mis-capitalized units. For example,
parse_stringwill not accept a short unit like ‘100k‘, whereasparse_string_unsafewill gladly accept it:- Documentation Refresh: The project documentation has been thoroughly reviewed and refreshed.
Several broken, moved, or redirecting links have been fixed. Wording and examples are more consistent. The documentation also lands correctly when installed via package.
Getting bitmath-1.3.1
bitmath-1.3.1 is available through several installation channels:
Ubuntu builds have not been prepared yet due to issues I’ve been having with Launchpad and new package versions.
-
bitmath is a Python module I wrote for working with file size units (ex:
12GiB,64kB) as objects. You can use them just like you would use regular numbers in python. It’s full of other functionality as well. Objects have native ‘convert to $unit‘ methods, support native arithmetic, are sortable, and include a ‘best human readable prefix’ method.Since March 2014, bitmath had only been available via PyPi and Fedora/EPEL repositories. Now, as of July 2nd 2016, bitmath is natively available to Ubuntu users by means of a new Personal Package Archive (PPA) hosting bitmath builds for Xenial, Wily, Vivid, Trusty, and Precise.
Ubuntu users can install bitmath in the following way:
Ubuntu support wouldn’t have happened if GitHub user hkraal hadn’t submitted an issue. Thanks Henk for getting the fire lit!
- Check out bitmath on GitHub
-
-
h4ck teh world
tbielawa - Issue Comment
openshift/doozer
December 13, 2018 - 8:45 pm UTC - Pull Request Review Comment
openshift/doozer
December 13, 2018 - 8:34 pm UTC - Pull Request Review Comment
openshift/doozer
December 13, 2018 - 8:30 pm UTC - Pull Request Review Comment
openshift/doozer
December 13, 2018 - 8:29 pm UTC - Pull Request
openshift/doozer
December 13, 2018 - 8:29 pm UTC
- Issue Comment
Technitribe by Tim Bielawa is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.