Content hub getpeers API fails
Bug #1398916 reported by
Alexandre Abreu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
Unassigned | |||
unity-webapps-qml |
Fix Released
|
High
|
Alexandre Abreu | |||
unity-webapps-qml (Ubuntu) | ||||||
Utopic |
Fix Released
|
Undecided
|
Unassigned | |||
unity-webapps-qml (Ubuntu RTM) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
In the Javascript HTML5 application API, the content hub getPeers() API fails. It does not return any value due to some changes in the ContentHub's structure.
[Test Case]
- take the sample application there:
- launch it with, ubuntu-
- you should see a list of content hub peers in the loaded html,
[Regression Potential]
None
Related branches
lp://staging/~abreu-alexandre/unity-webapps-qml/content-hub-getpeers-failure-14-10
Approved
for merging
into
lp://staging/unity-webapps-qml/14.10
- David Barth (community): Approve
-
Diff: 37 lines (+7/-12)1 file modifiedsrc/Ubuntu/UnityWebApps/bindings/content-hub/backend/content-hub.js (+7/-12)
Superseded
for merging
into
lp://staging/unity-webapps-qml
- WebApps: Pending requested
-
Diff: 15 lines (+4/-0) (has conflicts)1 file modifiedsrc/Ubuntu/UnityWebApps/bindings/content-hub/backend/content-hub.js (+4/-0)
lp://staging/~abreu-alexandre/unity-webapps-qml/backport-oxide-contenthub-fixes-1409
- Alexandre Abreu (community): Approve
-
Diff: 47 lines (+8/-14)1 file modifiedsrc/Ubuntu/UnityWebApps/bindings/content-hub/backend/content-hub.js (+8/-14)
description: | updated |
Changed in unity-webapps-qml: | |
assignee: | nobody → Alexandre Abreu (abreu-alexandre) |
importance: | Undecided → High |
status: | New → In Progress |
Changed in canonical-devices-system-image: | |
status: | In Progress → Fix Released |
Changed in unity-webapps-qml: | |
status: | In Progress → Fix Released |
Changed in unity-webapps-qml (Ubuntu Utopic): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The fix has already been released for Vivid in revision 141.