Inbox Development Newsletter for July 21st, 2014

[Christine Spang]

Hi inbox-dev subscribers,

It's been a busy couple weeks here at Inbox HQ since our launch on July 7th. It's been incredibly exciting to see the outpouring of support and interest from developers around the world. Thanks to everyone who's downloaded the code, run it, and submitted issue reports.

We've decided it'd be beneficial to the community to summarize development activity that's happened since the launch. Our team will be working on a 'dev' branch and incorporating bug fixes and new features into that branch. Every so-often we will push these changes to master with an update to these changes. Here's what's landed on master in the last two weeks:

** New Features **

* The logging infrastructure has been ported to Hynek Schlawack's excellent structlog[1] package and now directly emits JSON, intended to be consumed by a logging aggregation system such as LogStash.

* Yahoo accounts now synchronize IMAP flag changes on messages.

** Notable Bugfixes **

* Gmail messages are no longer occasionally duplicated in the metadata database. We now enforce the constraint that there is only one Message row per (account, X-GM-MSGID) pair.

* Gmail account syncs now degrade gracefully if a user has disabled some folders such as "Important" from showing up in the IMAP interface.

* Account syncs now store message metadata for messages which fail to decode, and properly skip re-downloading them.

* Several fields are now properly truncated when messages or portions of messages exceed size limits.

* API responses correctly use the order_by parameter.

* Performance of the API client sync protocol is improved.

* API calls to /n/<ns_id>/send correctly use the reply_to_thread parameter.

* Messages sending no longer fails if a subject parameter is not provided.

* Adding periods in a Gmail address no longer affects API result filtering. 

* Many improvements and fixes to Monocle, the Inbox account dashboard.

* Crashed syncs now properly restart themselves when the sync process is restarted.

** Upgrading **

If you're running Inbox on your own infrastructure, make sure you've disabled the sync and API processes and run the following to upgrade:

    git pull origin master

    alembic upgrade head

    cp etc/config-dev.json /etc/inboxapp

We highly recommend upgrading, as a lot of important fixes have landed.

The following folks contributed to this release (GitHub usernames by # of commits):

emfree, spang, kav-ya, charlesg3, grinich, bengotow, lheyberger, khamidou

Links:

http://www.structlog.org/en/0.4.1/