Meeseeker Mosly Minor Steem Engine Fixes - 0.0.7

Most of these changes address bugs involving Steem Engine sync capability. If you're just using meeseeker for following steem blocks, this update will have almost no impact.

Having said that, if you run the Docker version of meeseeker, it might be a good idea to update because this version affects the internal ruby version and adds stability. I only observed instability problems around Steem Engine sync, but there might be issues I didn't discover around steem sync (see section entitled Dockerfile Overhaul, below).

What Changed ...

I'll go over each commit that affects meeseeker version 0.0.7.

Publishing Steem Engine Contract Namespace 60c9908

In addition to each specific contract actions, meeseeker now publishes the contract itself. This means that if you wanted, you could subscribe to the #steem_engine:market channel to get notifications for all three contract actions (buy, sell, cancel).

Fixed Steem Engine Sync Resume 7d6784f

There was a bug in meeseeker sync steem_engine that caused resumed syncs to start over if they were originally started on a specific block (e.g.: If you first started on block 9001 with: meeseeker sync steem_engine 9001, then ^C to stop the sync, the next meeseeker sync steem_engine would start on block 1).

Renamed Internal Steem Engine Block Number Cursor ec8df4

Internally, the name of the cursor was incorrect which caused the reset task to effectively drop both the steem and steem_engine namespace at once. This change will cause existing redis databases to skip to the latest block once, unless you specify meeseeker sync steem_engine [block_num] once.

Steem Engine Diagnostics Task 585d18d

This is mostly just for my own curiosity and not a feature exposed in the meeseeker command. If you execute this task (rake steem_engine_ref_blocks), meeseeker will iterate all of the steem_engine:* keys and verify that the blocks on the main chain match the side-chain.

Added "Until Block" Option 642585e

Again, more of an internal feature. I needed a way for tests to stop processing rather than stream forever.

Dockerfile Overhaul 6c9c981

Although this affects both the steem and steem_engine namespaces, it only affects people who run meeseeker in Docker. This specifically fixes a bug in the steem_engine streaming functionality, but in doing so, updates steem streaming as well.

What I did was switch from the debian distribution of ruby over to rvm (Ruby Version Manager). This is because the docker image I use is on stretch, which is a pretty old version that, by default, can only install ruby-2.3.

This change puts the Docker version of meeseeker on ruby-2.6.

Just like before, this will launch meeseeker in a docker container, so you can immediately attach to it on port 6380.

docker run -d -p 6380:6379 inertia/meeseeker:latest
redis-cli -p 6380

---

To update your gem:

gem update meeseeker

^{Previous posts:}

• ^{Meeseeker Steem Engine Support - 0.0.6}
• ^{Meeseeker Op Timestamps - 0.0.5}
• ^{Meeseeker Witness Schedule Pub/Sub - 0.0.4}
• ^{Meeseeker on Docker}
• ^{Meeseeker Update - 0.0.3pre1}
• ^{I'm Mr. Meeseeks! Look at me!}