| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
It is generated during the build.
|
| |
| |
| |
| |
| |
| |
| | |
... to cover events coming from multiple stores spanning several days
where multiple events might have the same timestamp.
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| |
| |
| |
| | |
... to cover events coming from multiple stores spanning several days
where multiple events might have the same timestamp.
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| |
| |
| |
| | |
The actual test case will be added later. Existing test cases have
been adjusted accordingly.
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| |
| |
| | |
... to cover text events spanning multiple days.
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| |
| |
| | |
... to cover text events spanning multiple days.
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| |
| |
| |
| | |
... to cover text events spanning multiple days, and a mix of call and
text events.
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| |
| |
| |
| | |
... to cover text events spanning multiple days, and a mix of call and
text events.
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/53345
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This represents the order in which events were handed over to the user
from each iterator. Lets say we have 10 events numbered from 0 to 9,
with 0 being the oldest and 9 the latest event, and we have 3
iterators Ia, Ib and Ic. If they were returned in batches of 5 as:
+-----+--------+
|event|iterator|
+-----+--------+
| 5 | Ia |
| 6 | Ib |
| 7 | Ia |
| 8 | Ia |
| 9 | Ic |
+ - - + - -- - +
| 0 | Ic |
| 1 | Ic |
| 2 | Ib |
| 3 | Ib |
| 4 | Ia |
+-----+--------+
Then the list would be:
(Ic, 2), (Ib, 2), (Ia, 2), (Ib, 1), (Ia, 2), (Ic, 1)
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| |
| |
| |
| | |
Since the TplLogWalker API is asynchronous, we do not want multiple
overlapping calls to stamp on each others' toes.
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| |
| |
| |
| |
| | |
It a sign of completion if the number of events returned is less than
num_events. NULL is returned when there are no more events left in the
log.
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| |
| |
| |
| |
| | |
It a sign of completion if the number of events returned is less than
num_events. NULL is returned when there are no more events left in the
log.
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
| |
| |
| |
| | |
Without it you can't have properties of type TPL_TYPE_LOG_STORE.
|
| |
| |
| |
| | |
Fixes: https://bugs.freedesktop.org/41772
|
|/
|
|
| |
Fixes: https://bugs.freedesktop.org/41772
|
| |
|
|
|
|
|
|
| |
That interface is used only to prepare TplTextChannel and TplCallChannel,
but they now have a CORE feature doing that job, so they can be prepared
like any other proxy.
|
| |
|
|
|
|
|
| |
Give a TplClientFactory to the TplObserver, so we get already prepared
TplTextChannel and TplCallChannel subclasses.
|
|
|
|
|
| |
It is a TpAutomaticClientFactory subclass that creates
TplTextChannel and TplCallChannel instances
|
| |
|
|
|
|
| |
It is not needed since only one operation is actually async
|
| |
|
|
|
|
| |
It is not needed since only one operation is actually async
|
|
|
|
| |
TpBaseClient already ensure that before handing the channel
|
|
|
|
| |
It can be taken from the TpConnection
|
| |
|
| |
|
|
|
|
| |
This avoid single include from generated code
|
|
|
|
| |
This is needed for the fixed meta headers
|