mozilla :: #bmo

18 Apr 2017
02:38bugbotglob@mozilla.com granted review for attachment 8858069 on bug 1347175.
02:38bugbotAttachment https://bugzilla.mozilla.org/attachment.cgi?id=8858069&action=edit patch, 1347175_3.patch, 1347175_3.patch
02:38bugbotBug https://bugzilla.mozilla.org/show_bug.cgi?id=1347175 Extensions: RequestNagger, critical, P1, dylan, NEW , cron: Invalid local time for date in time zone: America/Los_Angeles
13:37bugbotNew Administration bug 1357408 filed by dylan@mozilla.com.
13:37bugbotBug https://bugzilla.mozilla.org/show_bug.cgi?id=1357408 Administration, normal, --, dylan, NEW , release tracking flag refresh (56)
13:52bugbutlerdylanwh pushed 1 to mozilla-bteam/bmo. Compare: https://github.com/mozilla-bteam/bmo/compare/a05a88ce6774...cfded4d89f70
13:53bugbotdylan@mozilla.com changed the Status on bug 1355142 from NEW --- to RESOLVED FIXED.
13:53bugbotBug https://bugzilla.mozilla.org/show_bug.cgi?id=1355142 General, normal, --, dylan, RESOLVED FIXED, Implement trick_taint in terms of Taint::Util::untaint()
13:59bugbutlerdylanwh pushed 1 to mozilla-bteam/bmo. Compare: https://github.com/mozilla-bteam/bmo/compare/cfded4d89f70...f04f94b31b39
13:59bugbotdylan@mozilla.com changed the Status on bug 1347175 from NEW --- to RESOLVED FIXED.
13:59bugbotBug https://bugzilla.mozilla.org/show_bug.cgi?id=1347175 Extensions: RequestNagger, critical, P1, dylan, RESOLVED FIXED, cron: Invalid local time for date in time zone: America/Los_Angeles
14:02bugbutlerdylanwh pushed 7 to mozilla-bteam/bmo. Compare: https://github.com/mozilla-bteam/bmo/compare/38d3715919bb...287a68316ff6
14:03bugbotNew Infrastructure bug 1357415 filed by dylan@mozilla.com.
14:03bugbotBug https://bugzilla.mozilla.org/show_bug.cgi?id=1357415 Infrastructure, normal, --, dylan, NEW , push updated bugzilla.mozilla.org live
14:58kbrosnannot getting the stylesheet for bmo
14:59dylankbrosnan: just on the index page? try fresh
14:59dylan*refresh
15:00kbrosnani've done a hard refresh 3-5 times
15:01dylanprobably etag caching, I think it may be fine now as I incremented version which should force a new etag.
15:01dylanincidentally if you are logged in and seeing this, that is very weird.
15:23dylankbrosnan: thanks for bringing this to my attention and I'm sorry for the inconvenience. This was a fallout from the Firefox 52 poking bmo mishap
15:32kbrosnanmbrandt was the first to ping about ti
15:52dylanbut you came here and I noticed. :)
20:30jawsDBD::mysql::db do failed: Deadlock found when trying to get lock; try restarting transaction [for Statement "UPDATE bugs SET delta_ts = ? WHERE bug_id = ?"]
20:30jawsdylan: ^
20:31dylanwhat is amazing about that I is I don't have an email from sentry
20:31jawscould have just been a race condition. i just tried it again and the update worked
20:31jawsit *just* happened
20:32dylanjaws: yeah, there are a few data races
20:32jawsso maybe email is delayed by 30 seconds?
20:32dylanthey're pretty fast -- this was the web frontend or the API?
20:32jawsweb frontend
20:33dylanstrange indeed.
20:33dylanthat is a data race though, not harmful but obviously something to fix. :)
20:38jawsdylan: this happened while i was trying to set the "blocks" field and another person was pushing to mozreview
20:40dylanhmm, and the mozreview request is going to be in the API, and probably inside a transaction.
23:39bugbotNew Infrastructure bug 1357600 filed by dylan@mozilla.com.
23:39bugbotBug https://bugzilla.mozilla.org/show_bug.cgi?id=1357600 Infrastructure, normal, --, nobody, NEW , Conflicts between BMO and dockerflow "Containerized App Requirements"
19 Apr 2017
No messages
   
Last message: 158 days and 4 hours ago