Lifestream

Results for #fail

05:24 utc apr 18 2019 permalink

I generated FFI bindings for mruby with bindgen! I wrote a C extension library for wrapping mruby macros! #win I wrote (a lot of) unsafe #rust code. Clippy helps a lot to make sure I'm not doing anything stupid. I have caused quite a few segfaults #fail

05:22 utc apr 18 2019 permalink

I overflowed the compiler (which didn't crash it) and crashed the linter with an ICE #win #fail

05:05 utc apr 18 2019 permalink

I found an ICE (internal compiler error) in clippy in #rust nightly #fail https://github.com/rust-lang/rust/issues/60067

03:46 utc apr 03 2019 permalink

looks like I didn't finalize the deploy in January so I had a few extra AMIs kicking around that I was needlessly paying for #aws #cost #fail #automation

03:42 utc apr 03 2019 permalink

The true motivation for getting me to mess with hyperbola today was an instance retirement notification from AWS. I had to muck with poetry to cycle my ASG #fail #aws

03:08 utc apr 03 2019 permalink

Uninstalling python 3.7.1 from pyenv broke my local poetry venv for hyperbola which prevented me from managing my deps #fail #python

03:05 utc apr 03 2019 permalink

Yikes haven't done a deploy since January 6. I've definitely been ignoring all of the USNs about Linux kernel vulnerabilities. #fail Django 2.2 release is what got me to get to upgrading #django #win

Photo for post 668
07:03 utc mar 14 2019 permalink

Deck making for an internal tech talk called "How to Implement the Chromecast Protocol in Rust When You Don't Know Rust" #rust futures and impl trait 😭 #fail

23:07 utc dec 28 2018 permalink

The most expensive part of hyperbola's #aws infrastructure is the SSM PrivateLink endpoint in 3 AZs #fail #cost

07:39 utc nov 17 2018 permalink

Just accidentally truncated my .bash_history. Restored from backup but the latest was 55 days ago. #fail

16:49 utc nov 11 2018 permalink

I was hard down for ~5min last night while rolling out secrets in parameter store. 0.149.0, 0.149.1, 0.149.2, and 0.149.3 were bad releases #fail. 0.149.4 is stable: https://github.com/lopopolo/hyperbola/compare/v0.148.0...v0.149.4. Postmortem pending.

23:12 utc nov 04 2018 permalink

The computers did exactly what I told them to do 😕 #fail

23:11 utc nov 04 2018 permalink

Add in some manual #terraform state edits and deleting things in the #aws console and we're recovered #fail #win

23:05 utc nov 04 2018 permalink

The cleanup script didn't error because my set flags were in the shebang but #packer was invoking the script via bash instead of directly #fail So many yaks.

23:04 utc nov 04 2018 permalink

This change was introduced in 0.146.0 but did not manifest due to a bug in the cleanup script. I was not passing -y to apt autoremove, which caused the command to abort and end the script with an error. #fail

22:57 utc nov 04 2018 permalink

Got into an undeployable state due to differences in #provisioning between local and prod environments #fail https://github.com/lopopolo/hyperbola/commit/a914992

02:25 utc oct 28 2018 permalink

I accidentally skipped v0.139.0 today because prettier barfed during cutting the release and I forgot to reset my git tree. I guess I forgot to run prettier on my whole repo when I enabled it. #fail

02:48 utc apr 03 2018 permalink

Sometimes using the #AWS cost and usage reports is just not fun, mostly due to the myriad of columns being undocumented. #fail

06:10 utc feb 24 2018 permalink

Semantic versioning is a lie (looking at you #packer). My config stopped working because a key was deprecated between 1.1.x and 1.2.x. Somehow this prevented the config from validating. #fail

06:13 utc feb 11 2018 permalink

So it turns out I shouldn't have ignored that MySQL backtrace when printing the help text of my new django management command in dev. That's why it hung when building the AMI. #fail One line fix: https://github.com/lopopolo/hyperbola/commit/728f1d68