Closed
Bug 1360684
Opened 8 years ago
Closed 8 years ago
Please deploy autopush 1.29.0 to STAGE
Categories
(Cloud Services Graveyard :: Operations: Autopush, task)
Cloud Services Graveyard
Operations: Autopush
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: rpapa, Assigned: oremj)
Details
------------------
RELEASE NOTES
------------------
https://github.com/mozilla-services/autopush/releases
COMPARISONS
https://github.com/mozilla-services/autopush/compare/1.26.0...1.27.0
https://github.com/mozilla-services/autopush/compare/1.27.0...1.28.0
https://github.com/mozilla-services/autopush/compare/1.28.0...1.29.0
TAGS
https://github.com/mozilla-services/autopush/releases/tag/1.29.0
https://github.com/mozilla-services/autopush/commit/991b0071010d5f1fe5860b101bb6696bf2a20b72
CHANGELOG
<a name="1.29.0"></a>
## 1.29.0 (2017-04-28)
#### Refactor
* refine the Handler validation ([b1312db7](https://github.com/mozilla-services/autopush/commit/b1312db7e2e9932daf997c5ade72e9353aaa9bd0))
#### Bug Fixes
* revert registration's strict critical failure check ([caf2ed8d](https://github.com/mozilla-services/autopush/commit/caf2ed8d12372918475b619c391c39a62eb1d9c3))
* Do not report InvalidSignature as unhandled ([0d243556](https://github.com/mozilla-services/autopush/commit/0d2435566598af35d3583467a26d82016259fe53))
* enforce `senderID` for gcm/fcm ([569dd1ff](https://github.com/mozilla-services/autopush/commit/569dd1ff6baeead93b98abe5996de3208771dfc9))
#### Features
* add parquet unified schema and cleanup logging messages ([63d2981c](https://github.com/mozilla-services/autopush/commit/63d2981c3e804adc84877ccb643515f139ce7787), closes [#882](https://github.com/mozilla-services/autopush/issues/882))
* add tracking for content-encoding ([c236f725](https://github.com/mozilla-services/autopush/commit/c236f72505344261c530e13ea61f42aaffd06bbd))
* Add VAPID Draft 02 support ([e17129db](https://github.com/mozilla-services/autopush/commit/e17129dbc2022ae6d3c856e7c94354bd4151df89))
Reporter | ||
Comment 1•8 years ago
|
||
----------------------------
URL CHECKS (STAGE)
----------------------------
curl -s 'https://updates-autopush.stage.mozaws.net/health' | python -mjson.tool
{
"clients": 0,
"stage.autopush.routerv2": {
"status": "OK"
},
"stage.autopush.storage": {
"status": "OK"
},
"status": "OK",
"version": "1.29.0"
}
curl -s 'https://updates-autopush.stage.mozaws.net/status' | python -mjson.tool
{
"status": "OK",
"version": "1.29.0"
}
Assignee: nobody → oremj
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 2•8 years ago
|
||
--------------------------------
SENTRY TEST
--------------------------------
MY IP: 63.245.221.198
updates-autopush.stage.mozaws.net
{
"code": 418,
"errno": 999,
"error": "Test Failure",
"message": "FAILURE:Success",
"more_info": "http://autopush.readthedocs.io/en/latest/http.html#error-codes"
}
{'ami_id': 'ami-35dbbc23', 'authorization': [Filtered], 'message_ttl': None, 'python_version': '2.7.12 (aff251e54385, Nov 09 2016, 18:02:49)
[PyPy 5.6.0 with GCC 4.8.2]', 'remote_ip': '63.245.221.198, 172.31.15.249', 'request_id': '3f30dd0e-24be-4aee-8b6d-369e80a3ab72', 'uri': '/v1/err/crit', 'user_agent': 'curl/7.51.0'}
Reporter | ||
Comment 3•8 years ago
|
||
--------------------------------
E2E TEST: TOPICS
--------------------------------
Additional E2E-test which includes testing of notification bundling for stored messages
https://github.com/jrconlin/topics - follow README
Desktop (Nightly). -- OK!
Android -- Not Yet Implemented (per :jrconlin)
Reporter | ||
Comment 4•8 years ago
|
||
----------------------------
E2E-TESTS
----------------------------
setting STAGE config to:
dom.push.serverURL = autopush.stage.mozaws.net
DESKTOP E2E PUSH TEST
setup:
start browser with new profile
open: about:config
set: dom.push.loglevel=debug (instead of 'off')
open: Tools > WebDeveloper > BrowserConsole
open: https://mozilla-services.github.io/autopush-e2e-test/
choose: "service-worker.js"
click: "register Service Worker"
click: "subscribe to push"
observe push registration in console
click: "Always Receive Notifications" (in pop-up window)
1. registration test
steps:
click: "XHR to webpush app-server"
observe: successful registration in console
2. message delivery test
setup:
set: Repeat = 2
set: Delay (seconds) = 15
steps:
click: "XHR to webpush app-server"
observe: 2 pop notifications 15 seconds apart
3. payload test
setup:
set: Title = PAYLOAD TEST
set: Body = BODY TEXT HERE
set: TTL = 360
set: Repeat = 4
set: Delay (seconds): 20
steps:
click: "XHR to webpush app-server"
observe:
should see delayed pop notifications with Title, Body specified
4. storage test
purpose: verify that a request is stored on autopush for delayed delivery
setup:
(same as 3 above)
steps:
click: "XHR to webpush app-server
wait for pop notification, then immediately close browser
wait 25 seconds
re-open browser
observe:
should see 3 more delayed messages delivered on browser restart
Reporter | ||
Comment 5•8 years ago
|
||
----------------------------
E2E-TESTS: VAPID (+Android)
----------------------------
VAPID tests failing on Nightly and Release w/ error:
"Send Failed:-: Unable to deliver message"
Reporter | ||
Comment 6•8 years ago
|
||
Halting this release in favor of autopush 1.29.1
See:
Please deploy autopush 1.29.1 to STAGE
Reporter | ||
Updated•8 years ago
|
Resolution: FIXED → INVALID
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•