Merge lp:~mterry/ubuntu-app-launch/persistentid into lp:ubuntu-app-launch
| Status: | Merged |
|---|---|
| Approved by: | Ted Gould on 2017-04-04 |
| Approved revision: | 302 |
| Merged at revision: | 313 |
| Proposed branch: | lp:~mterry/ubuntu-app-launch/persistentid |
| Merge into: | lp:ubuntu-app-launch |
| Diff against target: |
216 lines (+113/-11) 5 files modified
debian/changelog (+6/-0) libubuntu-app-launch/appid.h (+20/-3) libubuntu-app-launch/application.cpp (+62/-0) libubuntu-app-launch/helper.cpp (+1/-8) tests/libual-cpp-test.cc (+24/-0) |
| To merge this branch: | bzr merge lp:~mterry/ubuntu-app-launch/persistentid |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Ted Gould (community) | 2017-03-01 | Approve on 2017-04-04 | |
| unity-api-1-bot | continuous-integration | Needs Fixing on 2017-03-30 | |
|
Review via email:
|
|||
Commit Message
Add persistentID and dbusID methods to ual::AppID
Description of the Change
This branch adds two pieces of AppID API:
- persistentID which provides a string that is suitable for writing to disk and back again (i.e. no revision information)
- dbusID which is syntactic sugar for apps that may expose their appID over DBus paths or consume such paths by other apps.
With persistentID, other apps should no longer will have to embed information about appID formats (like manually combining package and command with an underscore). dbusID I care less about, but we talked about it before and since I was there...
- 297. By Michael Terry on 2017-03-02
-
Drop prototype for removed function
| Michael Terry (mterry) wrote : | # |
Instead of homegrown escaping, we could use nih_dbus_path?
| unity-api-1-bot (unity-api-1-bot) wrote : | # |
FAILED: Continuous integration, rev:297
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Ted Gould (ted) wrote : | # |
> Instead of homegrown escaping, we could use nih_dbus_path?
We're dropping deps on libnih, so no :-)
| Ted Gould (ted) wrote : | # |
Slight comment, but glad to get the dbus stuff C++-ified.
| Michael Terry (mterry) wrote : | # |
Fixing your isalpha comment. But I wanted to quickly make explicit that this new API is making a promise that UAL hasn't made yet, and just confirm we are cool with it.
So UAL is saying that if you write this AppID to disk, in a year or two, AppID::find() will definitely still recognize it. That's a longevity of format/parsing that I don't think we have made yet.
And since I'm doing this set of changes to consolidate parsing in UAL, and perhaps give us flexibility to change appID format in the future, when we do so, we'd have to carefully consider what that does to persistentIDs out in the wild.
Not a problem necessarily, just wanted to make sure you were OK with signing up for that.
(We already had this problem -- unity8 was already making its own persistentIDs. But now UAL is making that promise to everyone that uses its API.)
- 298. By Michael Terry on 2017-03-08
-
Use isalpha and isdigit
| Michael Terry (mterry) wrote : | # |
OK fixed to use isalpha and isdigit.
| unity-api-1-bot (unity-api-1-bot) wrote : | # |
FAILED: Continuous integration, rev:298
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Ted Gould (ted) wrote : | # |
I think we have to, don't love it, but I think that we can handle that part of the persistent IDs.
Your isdigit() change dropped the i != 0 check, which is because dbus names can't have a digit as their first character.
- 299. By Michael Terry on 2017-03-13
-
Restore i != 0 check
| Michael Terry (mterry) wrote : | # |
OK, restored the i != 0 check.
| unity-api-1-bot (unity-api-1-bot) wrote : | # |
FAILED: Continuous integration, rev:299
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Michael Terry (mterry) wrote : | # |
Is that CI failure related? Doesn't look it to me, but if other branches are passing...
| Ted Gould (ted) wrote : | # |
Not worried about the CI as much as the conflict in the branch. I'm guessing there might be another with Pete's branches landing.
- 300. By Michael Terry on 2017-03-30
-
Merge trunk
- 301. By Michael Terry on 2017-03-30
-
Fix tests now that click apps are gone
- 302. By Michael Terry on 2017-03-30
-
Fix version
| Michael Terry (mterry) wrote : | # |
Fixed the conflict.
| unity-api-1-bot (unity-api-1-bot) wrote : | # |
FAILED: Continuous integration, rev:302
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/

FAILED: Continuous integration, rev:296 /jenkins. canonical. com/unity- api-1/job/ lp-ubuntu- app-launch- ci/239/ /jenkins. canonical. com/unity- api-1/job/ build/1736/ console /jenkins. canonical. com/unity- api-1/job/ build-0- fetch/1743 /jenkins. canonical. com/unity- api-1/job/ build-2- binpkg/ arch=amd64, release= xenial+ overlay/ 1518/console /jenkins. canonical. com/unity- api-1/job/ build-2- binpkg/ arch=amd64, release= zesty/1518/ console /jenkins. canonical. com/unity- api-1/job/ build-2- binpkg/ arch=armhf, release= xenial+ overlay/ 1518/console /jenkins. canonical. com/unity- api-1/job/ build-2- binpkg/ arch=armhf, release= zesty/1518/ console /jenkins. canonical. com/unity- api-1/job/ build-2- binpkg/ arch=i386, release= xenial+ overlay/ 1518/console /jenkins. canonical. com/unity- api-1/job/ build-2- binpkg/ arch=i386, release= zesty/1518/ console
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild: /jenkins. canonical. com/unity- api-1/job/ lp-ubuntu- app-launch- ci/239/ rebuild
https:/