summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* libtracker-data: Do not error on NULL arguments in tracker:uri-is-parentwip/carlosg/uri-is-parent-checksCarlos Garnacho2020-11-041-1/+1
| | | | | | | | | | | This may happen during query evaluation, without the query explicitly specifying any NULL value. If we error out, query execution will definitely stop, and the error may propagate further up. Just tiptoe over those values, and let query evaluation continue further, the right results will be eventually returned. Fixes: https://gitlab.gnome.org/GNOME/tracker/-/issues/235
* libtracker-data: Issue fatal g_error() if next resource ID cannot be foundCarlos Garnacho2020-11-041-1/+1
| | | | | | | | | | | This breaks fundamental assumptions (e.g. that getting a next resource ID is not failable), breaks even further if those resources don't get the specified ID. It is preferrable to hard error altogether, and let users report the backtrace/error. Related: https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/150
* libtracker-data: Propagate errors when looking for next resource IDCarlos Garnacho2020-11-041-18/+22
| | | | | Instead of warning in place, let these errors propagate up, so they're handled centrally.
* Merge branch 'sam/faq-memory' into 'master'Carlos Garnacho2020-10-311-0/+8
|\ | | | | | | | | website/faq: Add note about RAM usage See merge request GNOME/tracker!334
| * website/faq: Add note about RAM usageSam Thursfield2020-10-311-0/+8
|/
* Merge branch 'sam/website-faq-update' into 'master'Sam Thursfield2020-10-201-20/+39
|\ | | | | | | | | website: FAQ updates See merge request GNOME/tracker!329
| * website/faq: Add more info about recursive $HOMESam Thursfield2020-10-201-1/+5
| | | | | | | | See https://gitlab.gnome.org/GNOME/tracker/-/merge_requests/329#note_933276
| * website/faq: More Tracker 3 related updatesSam Thursfield2020-10-201-20/+21
| | | | | | | | | | Use 'Tracker Miner FS' instead of 'Tracker' in more places, and `tracker3` instead of `tracker`.
| * website/faq: Add info on troubleshooting indexing errorsSam Thursfield2020-10-201-0/+14
|/
* Merge branch 'sam/more-docs' into 'master'Sam Thursfield2020-10-202-21/+20
|\ | | | | | | | | Tracker3 updates for README and website See merge request GNOME/tracker!331
| * website/overview: Some Tracker 3 related updatessam/more-docsSam Thursfield2020-10-141-14/+11
| |
| * README: Some tracker3 related updatesSam Thursfield2020-10-141-7/+9
| |
* | Merge branch 'wip/carlosg/parallel-stmts' into 'master'Sam Thursfield2020-10-182-9/+46
|\ \ | | | | | | | | | | | | Improve behavior on parallel queries See merge request GNOME/tracker!333
| * | libtracker-data: Favor free interfaces over new ones harderwip/carlosg/parallel-stmtsCarlos Garnacho2020-10-181-7/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We typically do that, but once we've found that the first interface in the pool is already busy with other statements, we assume they're all busy and jump into creating a new interface. Even worse, if that interface is kept busy indefinitely, every new query will opt for creating a new interface, quickly filling the allotment. There might be other interfaces in the pool that are already free, so check all of them before trying to create a new interface. This makes us more conservative at creating new interfaces on load periods, only doing so if all interfaces are actually busy.
| * | libtracker-sparql: Batch TrackerNotifier queriesCarlos Garnacho2020-10-181-2/+27
|/ / | | | | | | | | | | | | | | | | | | | | | | If we happen to get a high enough amount of updates, batched changes accumulate, all querying for the additional information. This accumulation of the same query leads at best to compiling new statements (as the cached one is already in use). At worst, it leads to the creation of a new TrackerDBInterface, with the initialization cost involved. Serializing this work, we're more likely to reuse a TrackerDBInterface and a pre-compiled statement from previous runs.
* | build: Fix docs buildSam Thursfield2020-10-171-1/+0
| | | | | | | | It broke after c32f172f1b48f6cfe9845ca233f643bde81abd0c.
* | Merge branch 'tintou/gptrarray-vala' into 'master'Sam Thursfield2020-10-171-1/+1
|\ \ | | | | | | | | | | | | libtracker-data: Change GPtrArray into GenericArray See merge request GNOME/tracker!332
| * | libtracker-data: Change GPtrArray into GenericArraytintou/gptrarray-valaCorentin Noël2020-10-161-1/+1
|/ / | | | | | | This is the vala-preferred way of handling GPtrArray
* | Merge branch 'sam/docs-flatpak' into 'master'Carlos Garnacho2020-10-153-121/+53
|\ \ | |/ |/| | | | | docs: Add information related to Flatpak See merge request GNOME/tracker!330
| * docs: Add information related to Flatpaksam/docs-flatpakSam Thursfield2020-10-133-121/+53
| | | | | | | | | | | | | | | | 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
* | Merge branch 'sam/website-link-fix' into 'master'Carlos Garnacho2020-10-131-1/+1
|\ \ | |/ |/| | | | | website: Fix broken link in preview API docs See merge request GNOME/tracker!328
| * website: Fix broken link in preview API docssam/website-link-fixSam Thursfield2020-09-241-1/+1
| | | | | | | | | | | | 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.
* | build: Bump version early for GNOME 40Carlos Garnacho2020-10-121-1/+1
| | | | | | | | Next stable release will be 3.1.0.
* | Merge branch 'wip/carlosg/iterative-update' into 'master'Sam Thursfield2020-10-121-15/+30
|\ \ | | | | | | | | | | | | | | | | | | libtracker-data: Process Update rule iteratively Closes tracker-miners#91 See merge request GNOME/tracker!327
| * | libtracker-data: Process Update rule iterativelywip/carlosg/iterative-updateCarlos Garnacho2020-10-111-15/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Merge branch 'wip/carlosg/invalid-reads' into 'master'Sam Thursfield2020-10-121-1/+2
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | libtracker-data: Break out of all loops on transaction errors Closes tracker-miners#130 See merge request GNOME/tracker!326
| * | | libtracker-data: Break out of all loops on transaction errorswip/carlosg/invalid-readsCarlos Garnacho2020-10-111-1/+2
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Merge branch 'wip/carlosg/datetime-fixes' into 'master'Sam Thursfield2020-10-129-7/+34
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Fixes to date/time parsing Closes tracker-miners#146 See merge request GNOME/tracker!324
| * | | tests: Add some tests for dates far in the past/futurewip/carlosg/datetime-fixesCarlos Garnacho2020-10-106-0/+13
| | | | | | | | | | | | | | | | To ensure these work as intended.
| * | | libtracker-common: Ensure to print at least 4 year digitsCarlos Garnacho2020-10-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | libtracker-data: Forward errors from datetime conversions in SparqlTimeSortCarlos Garnacho2020-10-101-1/+1
| | | | | | | | | | | | | | | | | | | | Let this helper SQLITE function forward the datetime conversion, should there be one.
| * | | libtracker-data: Check better for errors in datetime parsingCarlos Garnacho2020-10-101-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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) {}
| * | | libtracker-data: Use correct binding types for datetimesCarlos Garnacho2020-10-101-2/+12
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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) { }
* | | Merge branch 'wip/carlosg/ttl-parser-improvements' into 'master'Sam Thursfield2020-10-128-28/+56
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Wip/carlosg/ttl parser improvements Closes #260 See merge request GNOME/tracker!323
| * | | tests: Add long string with langtag in testswip/carlosg/ttl-parser-improvementsCarlos Garnacho2020-10-101-0/+1
| | | | | | | | | | | | | | | | | | | | 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.
| * | | libtracker-data: Forward langtag from TTL filesCarlos Garnacho2020-10-101-3/+3
| | | | | | | | | | | | | | | | | | | | Instead of forwarding plain strings, forward the langtag info so it is stored.
| * | | libtracker-data: Add tracker_sparql_make_langstring()Carlos Garnacho2020-10-102-12/+25
| | | | | | | | | | | | | | | | | | | | This function takes a string and langtag, and produces a GBytes as the internals do expect it.
| * | | libtracker-data: Forward langtag from TTL parserCarlos Garnacho2020-10-105-10/+18
| | | | | | | | | | | | | | | | Pass this as an argument, unused so far.
| * | | libtracker-data: Parse LANGTAG in turtleCarlos Garnacho2020-10-101-4/+10
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | libtracker-data: Parse STRING_LITERAL_LONG before STRING_LITERAL in turtleCarlos Garnacho2020-10-101-4/+4
| |/ / | | | | | | | | | | | | The STRING_LITERAL terminal may mistakenly match STRING_LITERAL_LONG strings. Invert the order here, so we correctly trimp quotes around.
* | | Merge branch 'sam/web-overview' into 'master'Sam Thursfield2020-10-121-15/+23
|\ \ \ | | | | | | | | | | | | | | | | Updates to 'overview' page on website See merge request GNOME/tracker!321
| * | | website/overview: Add some more projects that use Trackersam/web-overviewSam Thursfield2020-10-021-0/+7
| | | |
| * | | website/overview: s/Tracker/Tracker Miner FS/Sam Thursfield2020-10-021-15/+16
| | | | | | | | | | | | | | | | | | | | This is a bit less easy to read but hopefully makes it clearer that Tracker SPARQL and Tracker Miner FS are separate things.
* | | | Update Chinese (Taiwan) translationCheng-Chia Tseng2020-10-121-242/+236
| | | |
* | | | Merge branch 'wip/jtojnar/drop-nm-opt' into 'master'Carlos Garnacho2020-10-111-2/+0
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | build: Remove forgotten network_manager option See merge request GNOME/tracker!325
| * | | build: Remove forgotten network_manager optionwip/jtojnar/drop-nm-optJan Tojnar2020-10-111-2/+0
|/ / / | | | | | | | | | It is not used since https://gitlab.gnome.org/GNOME/tracker/commit/a88e0f23df07308670020926285549b0ed8a55a2.
* | | Merge branch 'wip/carlosg/portal-initialization' into 'master'Sam Thursfield2020-10-051-11/+7
|\ \ \ | | | | | | | | | | | | | | | | portal: Fix initialization order See merge request GNOME/tracker!322
| * | | portal: Fix initialization orderwip/carlosg/portal-initializationCarlos Garnacho2020-10-041-11/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | website: s/tracker/tracker3Sam Thursfield2020-10-022-2/+2
|/ / /
* | | Release 3.0.13.0.1Carlos Garnacho2020-10-022-1/+15
| | |
View Lorry Controller Status