Lifestream

Results for #win

15:34 utc aug 12 2019 permalink

I reported an undocumented panic in #rust that was fixed today #patch #win https://github.com/rust-lang/rust/issues/63456

Photo for post 732
08:16 utc aug 06 2019 permalink

#artichoke is the top trending repo on all of #github right now #win

Photo for post 729
03:37 utc aug 01 2019 permalink

I built an #artichoke #Wasm playground in the browser https://artichoke.github.io/artichoke/ #win

Photo for post 728
03:34 utc aug 01 2019 permalink

That is a lot of code #artichoke #github #patch #win

Photo for post 727
03:33 utc aug 01 2019 permalink

That is a lot of code #artichoke #github #patch #win

04:41 utc jul 29 2019 permalink

The biggest accomplishment was redoing the #artichoke README https://github.com/artichoke/artichoke#readme Thought about project goals and differentiators from MRI. Added milestones to track progress in achieving goals #win #ruby #artichoke

04:39 utc jul 29 2019 permalink

Being forced to set up the repository infra from scratch in cactusref was a good way to fix everything I disliked about my dev environment. CircleCI build and scripts/lint.sh got overhauled #win #artichoke #shell #bash #node #lint

04:36 utc jul 29 2019 permalink

ferrocarril had different goals than artichoke: it wanted to run Rails. To do that, it had a lot of extra bits in it like gems, a Rack server, and sample apps. Nuked all of it #win #artichoke

06:28 utc jul 10 2019 permalink

I had a PR accepted in mruby! #patch #ruby #mruby #win https://github.com/mruby/mruby/pull/4560

07:59 utc jun 01 2019 permalink

I have Regexp#match? https://github.com/lopopolo/ferrocarril/pull/93 #win #rust #ruby

12:58 utc may 27 2019 permalink

It has been a really productive weekend. Merged 23 #github PRs for ferrocarril #win #rust #git https://github.com/lopopolo/ferrocarril/pulls?utf8=%E2%9C%93&q=is%3Apr+created%3A2019-05-24..2019-05-27+is%3Aclosed+

07:13 utc may 24 2019 permalink

Adding #ci to a project is encouraging such better code hygiene. Because I want to make sure the build stays green, I actually make PRs even if it is only me approving them. Seeing the code in the browser makes it easier to review than #git diff #win

07:10 utc may 24 2019 permalink

In a related note, I now peg the nightly version in the rust-toolchain file to a specific date archive #ci #rust #win

07:09 utc may 24 2019 permalink

My #ci builds of ferrocarril caught a bug in rustyline that made compilation fail on the latest nightly #rust #win #patch https://github.com/kkawakam/rustyline/issues/217

07:08 utc may 24 2019 permalink

I reported a #segfault in mruby and spoke directly with @matz! #win https://github.com/mruby/mruby/issues/4460 #patch

Photo for post 688
01:35 utc may 17 2019 permalink

Excluding generated and vendored sources, ferrocarril is 8700 lines of #rust, #c, and #ruby. This is a lot of code. In very uncharacteristic fashion for a side project, a big chunk is tests #win https://github.com/lopopolo/ferrocarril/commit/fe2febc

01:23 utc may 17 2019 permalink

You can tell which parts of ferrocarril are new to me based on how many consecutive commits are dedicated to a feature. By this measure, the new (and hard) things were sys crates, #ci, and TryFrom traits #rust #win #fail

01:21 utc may 17 2019 permalink

I tried to explain continuous integration to my Dad and he synthesized it as "spellcheck for code" which is pretty good tbh #win #ci

08:47 utc may 16 2019 permalink

It only took 49 build jobs, but the ferrocarril build is passing on CircleCI https://circleci.com/gh/lopopolo/ferrocarril/47 This is the first time I've ever set up #ci for a side project #win