On 2017-10-22 11:56:06 +0200 (+0200), Sławek Kapłoński wrote: [...] > I suppose that gertty is looking only for patches which are > already in local database. Is it true?
Basically, yes. As far as I've seen it syncs status for any changes on projects to which you've explicitly subscribed, as well as any for which your account is the owner in Gerrit. I believe it will also include changes which are in its DB because you've directly loaded them, but does not automatically sync/update status changes for those unless you view and refresh them manually. I tend to work around this by subscribing Gertty to all the projects in which I regularly participate. > And is there any possibility to change it? It's software, so probably. That said, I expect Gertty would need some sort of first-class dashboard support where it knows (beyond simple keybindings for arbitrary queries, maybe similar to how it treats owner:self changes?) that you want all changes for dashboards pulled into the local DB and kept in sync so that it has them available for offline operation... not sure what impact that may have on performance either. And of course you'd need to convince its author this is a worthwhile behavior change, since there may be good reasons it was designed to work this way from the outset. I'll bring this thread to Jim's attention once he's around today; he will doubtless have more accurate details and concrete suggestions than I. -- Jeremy Stanley
signature.asc
Description: Digital signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
