| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
This is the vala-preferred way of handling GPtrArray
|
| |\
| |
| |
| |
| | |
docs: Add information related to Flatpak
See merge request GNOME/tracker!330
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Also some general cleanups, in particular removing domain-ontology
feature which now belongs in tracker-miners.git, and can be
documented there with an example app.
See: https://gitlab.gnome.org/GNOME/tracker/-/issues/236
|
| |\ \
| |/
|/|
| |
| | |
website: Fix broken link in preview API docs
See merge request GNOME/tracker!328
|
| | |
| |
| |
| |
| |
| | |
This fixes a broken link that was in the header of each page of the
preview API documentation, pointing to
https://gnome.pages.gitlab.gnome.org/tracker/docs/ which gives a 404.
|
| | |
| |
| |
| | |
Next stable release will be 3.1.0.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
libtracker-data: Process Update rule iteratively
Closes tracker-miners#91
See merge request GNOME/tracker!327
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The Update rule is defined upon itself, we interpret this a bit too
literally, and do the same thing when interpreting the parse tree. This
makes the maximum stack size an indirect factor that limits how big a
series of updates can possibly be. (e.g. the array at
tracker_sparql_connection_update_array_async)
This is obviously bad, so process the updates iteratively, this will avoid
hitting stack limits by just concatenating legit updates together.
Fixes: https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/91
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
libtracker-data: Break out of all loops on transaction errors
Closes tracker-miners#130
See merge request GNOME/tracker!326
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If an error is found when flushing a transaction on a specific, we'd
inadvertently still try to handle operations in other graphs, possibly
reusing the GError location, and leading to invalid reads/writes.
After finding an error, the transaction is going to be rolled back
anyway, so break on the first error found.
Fixes: https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/130
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes to date/time parsing
Closes tracker-miners#146
See merge request GNOME/tracker!324
|
| | | | |
| | | |
| | | |
| | | | |
To ensure these work as intended.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Expand the %F in strftime() to %4Y-%M-%D, otherwise for years < 1000
we end up eating digits, and producing a not quite ISO8601 string.
Fixes: https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/146
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Let this helper SQLITE function forward the datetime conversion, should
there be one.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When parsing iso8601 strings, we may end up with a legit negative
timestamp. Checking for it being negative makes us fail (with no
error!) for dates before the epoch, check the error instead.
Fixes parsing issues with queries with ancient datetimes like:
select ("0100-12-31T21:00:00-03:00"^^xsd:dateTime as ?date) {}
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When creating a binding from a literal datetime value, we mistakenly
use doubles (as used to be the common thing in Tracker 2.x). We now
store datetimes as either iso8601 strings or int64 timestamps, so
forward these types.
This code is in consistence with the update bits at tracker-data-update.c.
Fixes select queries like:
SELECT ("2020-01-01T01:01:01Z"^^xsd:dateTime AS ?date) { }
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Wip/carlosg/ttl parser improvements
Closes #260
See merge request GNOME/tracker!323
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
We don't test directly for LOAD, so squeeze these sneaky cases
(long strings and langtags) in a test where we load a TTL file.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Instead of forwarding plain strings, forward the langtag info so it
is stored.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This function takes a string and langtag, and produces a GBytes as
the internals do expect it.
|
| | | | |
| | | |
| | | |
| | | | |
Pass this as an argument, unused so far.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Allow LANGTAG after STRING_LITERAL* and STRING_LITERAL_LONG. We don't
propagate the language tag so far yet, just parsing of these tags is
fixed.
|
| | |/ /
| | |
| | |
| | |
| | | |
The STRING_LITERAL terminal may mistakenly match STRING_LITERAL_LONG strings.
Invert the order here, so we correctly trimp quotes around.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Updates to 'overview' page on website
See merge request GNOME/tracker!321
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is a bit less easy to read but hopefully makes it clearer that
Tracker SPARQL and Tracker Miner FS are separate things.
|
| | | | | |
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
build: Remove forgotten network_manager option
See merge request GNOME/tracker!325
|
| |/ / /
| | |
| | |
| | | |
It is not used since https://gitlab.gnome.org/GNOME/tracker/commit/a88e0f23df07308670020926285549b0ed8a55a2.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
portal: Fix initialization order
See merge request GNOME/tracker!322
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The portal is currently first claiming the bus name, then adding
the portal object+interface. This may break things with autostart
as clients are able to send a message to an object path that is not
there yet.
Changing the order means the object path is there when the DBus name
is made known, so clients are able to talk immediately to it.
Fixes the error reported at
https://github.com/flathub/org.gnome.Music/pull/24#issuecomment-702565846
|
| |/ / / |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
libtracker-data: Unset graph after Modify clause
See merge request GNOME/tracker!320
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the Modify clause sets a graph via 'WITH' the graph token remains
but the solution underneath gets freed. That means the graph token's
literal is kept "set" but containing garbage, and may wreak havoc if
there are more Update clauses in the same update string that don't
specify a graph, as that garbage value will be used. This may lead
to warnings, crashes, and bogus graph databases being created. Eek.
The 'WITH' graph is not meant to be carried over, so ensure it gets
unset after dealing with the Modify clause.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Add some more tests
See merge request GNOME/tracker!319
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Add an specific test for portal things, at the moment some minimal tests
about allowed/disallowed services and graphs is done.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Make the artifacts for the Coverage target contain a fully detailed
HTML summary of the coverage status (including visualizing that info
together with source code).
This proves useful for knowing what is missing tests, so make it
readily available for everyone.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
These files are not tested, just build-checked. We don't intend these
to be tested either.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Add a base test class that runs the portal and an arbitrary set of endpoints
in a DBus sandbox, so that different combinations of permissions can be tested.
|
| | | | |
| | | |
| | | |
| | | | |
Otherwise we try to error out, but never really finish the DBus invocation.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This will be used by our functional test suite to test portal workings.
Likewise, use this envvar presence to force the use of the Tracker portal
in the bus TrackerSparqlConnection.
|
| | | | |
| | | |
| | | |
| | | | |
tracker_sparql_connection_new() allows NULL store/ontology arguments.
|
| | | | | |
|
| | | | | |
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With a hack really, up in the parse tree we do force "COLLATE TRACKER"
on all string arguments passed on ORDER BY. Make this return "unknown"
just so this is avoided.
tracker:title-sort() is not meant to produce a pretty visible string,
more a collation key, perhaps it is somewhat fitting, perhaps I'm
making up an excuse.
|
| |/ / |
|
| |/ |
|
| |\
| |
| |
| |
| | |
build: Use specific Meson options to enable debug flags
See merge request GNOME/tracker!316
|
