{"push_id":1437194459,"size":2,"distinct_size":2,"ref":"refs/heads/madness","head":"6ac5587b0a0033aea11353a4df8e4eb482984969","before":"d5e92706dc7f76281a406211eef62244fdda0fa6","commits":[{"sha":"6c0edadab465abdfdde4dc1249eb1f84ff7cc77a","author":{"name":"Ryan Roden-Corrent","email":"8f18e670ec432ee5e15365d38d203f741b57c02e@rcorre.net"},"message":"Don't double-init url completion.\n\nIf you open URL completion shortly after opening qutebrowser, it will\ninit once to show the completion and once again shortly after due to\nthe signal emmitted by the async history read.\n\nThis means we are doing extra unnecessary work and the initial results\nof history completion may be incomplete. With SQL, it causes the\nadditional problem that we will cause an error trying to create the\nsame table again. We could use `CREATE TABLE IF NOT EXISTS` but that\ncould mask other errors, and we would end up creating duplicate rows\nanyways.\n\nWith this patch, the signal no longer triggers a url completion update.\nInstead, init waits for the signal before it builds the url completion\nmodel.","distinct":true,"url":"https://api.github.com/repos/rcorre/qutebrowser/commits/6c0edadab465abdfdde4dc1249eb1f84ff7cc77a"},{"sha":"6ac5587b0a0033aea11353a4df8e4eb482984969","author":{"name":"Ryan Roden-Corrent","email":"8f18e670ec432ee5e15365d38d203f741b57c02e@rcorre.net"},"message":"Use parameter binding for SQL queries.\n\n_run_query now supports positional parameter binding. This is currently\nused for the key when removing a row. The other parts of existing\nqueries still need to use string formatting, as table and field names\ncannot be bound to.","distinct":true,"url":"https://api.github.com/repos/rcorre/qutebrowser/commits/6ac5587b0a0033aea11353a4df8e4eb482984969"}]}
{"actor":{"display_login":"rcorre"}}