Tagged: development

Sequelize has less opaque errors

Good news:  sequelize no longer has opaque global leak errors when using mocha:  https://github.com/sequelize/sequelize/pull/1051

The errors are MUCH less opaque and much more relevant to the test failure when watching your tests fail.  For example, when you try to create a model with a column that does not exist in your schema:

Error: SQLITE_ERROR: table articles has no column named ‘new_column’

Which is much more useful than a notification that the library that you’re using is leaking globals.  Yay!

Build from source, Luke

I went to spend a bit of time with Go today, and attempted to update go from 1.03 to 1.1.  I tried:

sudo add-apt-repository ppa:gophers/go

sudo apt-get update

sudo apt-get install golang-stable

But this resulted in nothing; still 1.03.  I went to the PPA page for Go and saw version 1.1, but it was not showing up on my local box.  Perplexed, I started poking around and found the package details page for golang-stable.  The build had failed on the 15th and it hasn’t been updated since.

So, it’s simple enough to build from source:

sudo apt-get build-dep golang-stable

cd golang-stable-1.1

dpkg-buildpackage

dpkg -i ../golang-stable*.deb

And now I have the newer version.  Hopefully the build will be fixed when the package is published next and I won’t have to do this again.