| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
needed by others"
This reverts commit b78ae1d600f227bd4b77744648d5cde4e09d4640.
|
|
|
|
| |
Use use_data_free_func in g_bus_watch_name().
|
|
|
|
|
|
|
|
| |
- Fixed memory leaks
- Used const types for const returns
- Avoided duplicate messaging
- Added checks for valid UUID returns
- Avoided freeing const char*
|
|
|
|
|
|
|
|
| |
This method indexes a given path and watches the request sender bus
name. It stops the indexing process when no bus names are associated
with the given file.
Fixes GB#680834
|
|
|
|
|
|
|
| |
This function allows adding a mount point to the store, regardless
of the state of the index-removable-devices and index-optical-discs
gsettings options. It is a mechanism to escape the strict duality
dictated by these gsettings keys.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=743250
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SPARQL update strings can be very long if the entire text of a document
is being stored. Dumping these huge strings to the log eats up disk
space and makes them harder to follow.
However, often, the occurence of such an error indicates a broken
extractor. In those cases, knowing part of the SPARQL can help in
identifying the file that triggered the error.
Usually the "nie:plainTextContent" property is the last one in the
string, so we truncate the error messages at the first occurance of
this property to achieve the best of both worlds.
https://bugzilla.gnome.org/show_bug.cgi?id=735406
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=742391
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If Tracker can't resolve special dirs like &DOCUMENTS to real path
names, it now gives a warning like this:
(tracker-miner-fs:7207): Tracker-WARNING **: Unable to get XDG user
directory path for special directory &DOCUMENTS. Ignoring this
location.
Previously (since commit 5f06c134f4f6da02027c813322e13c220b51cd0a) the
user would see this rather more scary output:
(tracker-miner-fs:6046): GLib-GIO-CRITICAL **: g_file_new_for_path:
assertion 'path != NULL' failed
(tracker-miner-fs:6046): GLib-GIO-CRITICAL **: g_file_equal: assertion
'G_IS_FILE (file1)' failed
(tracker-miner-fs:6046): GLib-GObject-CRITICAL **: g_object_unref:
assertion 'G_IS_OBJECT (object)' failed
This situation is rare (you need to manually change or break
XDG_CONFIG_HOME to really see it) but it's always nice to avoid showing
critical errors!
|
|
|
|
|
| |
The config file format changed in commit
2b53cd5d3aaf046c413fd4afb188c16d7e611f48.
|
|
|
|
|
|
|
|
| |
Firstly, allow specifying multiple --content options, and allow
specifying --content-non-recursive if you really want as well.
Also, don't generate an XDG user directories config. It seems a bit
weird to be doing this and setting each directory to the same location.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=742035
|
|
|
|
|
|
| |
media_art_process is not set when running tracker-extract-info tests
https://bugzilla.gnome.org/show_bug.cgi?id=742035
|
|
|
|
|
|
|
|
|
|
|
| |
Identified by functional-tests/17-ontology-changes timeouting randomly.
Documentation for g_unix_signal_source_new() explains why it is not safe
to call g_main_loop_quit() from a regular UNIX signal handler.
Intentionally removed the (main_loop != NULL) tests - this cannot happen.
https://bugzilla.gnome.org/show_bug.cgi?id=739234
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=663687
|
|\ |
|
| |
| |
| |
| |
| |
| | |
This test adds data that would normally be added by the FS miner.
In order for the resource to be correctly deleted when the file is
removed, it must set nie:isStoredAs correctly.
|
|/ |
|
|\ |
|
| | |
|
| | |
|
|/
|
|
|
|
|
| |
This makes the following error less likely, and clearer when it does
occur:
(tracker-miner-fs:28886): Tracker-WARNING **: Could not open directory 'file:///home/sam/tracker-tests/writeback': Not a directory
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Tests shouldn't break just because --enable-guarantee-metadata is not
specified at configure time. This feature is off by default so we
shouldn't depend on it. See GB#733536.
|
|/
|
|
|
|
| |
If extraction with GstDiscoverer fails due to lack of a plugin, we can
display exactly what plugin was missing rather than just giving a
generic error. This makes it a bit easier to fix the problem.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since commit 41e6ab84e7a540b20f8173c2bbaee11de6ef381f, the contents of
directories listed in 'index-single-directories' is be ignored. The
directory itself appears in the store but the contents do not.
The intention of passing max_depth=1 if TRACKER_DIRECTORY_FLAG_RECURSE
is false must be to prevent unnecessarily processing any subdirectory
nodes that are hanging around in the TrackerFileSystem. However, the
documentation of g_node_traverse says:
"If depth is 1, only the root is visited. If depth is 2, the root
and its children are visited. And so on."
Thus, we must pass max_depth+1 to the tracker_file_system_traverse()
function so that the files in the directory are processed as well as
the directory itself.
See also: 243c97fa96a2f6b19bce1acf26946d1a516a0a1c which introduced the
'max_depth' parameter as a way of reducing the number of GFile objects
in memory at the same time during crawling.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rather than running all the tests in one environment, create a new
environment for each test. Although it's slower this way, it's just too
hard to debug test failures when the tests can interfere with each
other.
I also made them all use the same 'minertest' base class.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Instead of using `tracker daemon --kill=miners` to stop the miners, use
the Python 'subprocess' module. This ensures only the correct miner
process gets killed if more than one is running. (I also found that
`tracker daemon --kill-miners` was hanging my system, which was the real
motivation for fixing this, but I have no idea why that happened).
If a process fails to terminate after we sent it TERM, it now gets sent
KILL. Previously the test would wait forever.
|
| |
| |
| |
| | |
All 3xx tests should now pass except 2 of the 310-fts-indexing tests.
|
|/
|
|
|
| |
This allows detecting when a file move has been done, and probably other
useful things too.
|
| |
|
|
|
|
|
|
|
| |
Bring SQL injection to the front of people’s minds when using the APIs
so that hopefully they don’t write injectable code.
https://bugzilla.gnome.org/show_bug.cgi?id=741777
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=678986
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Identified by MinerCrawlTest::test_07_move_from_monitored_to_monitored
(300-miner-basic-ops.py)
In item_move() it fails to get source_iri, does not check it's validity and
uses it in the DELETE expression of the SPARQL query constructed there.
Broken since d836f00 (libtracker-miner: Store iri transiently as GFile
qdata) - tracker_file_notifier_get_file_iri() is added 'force' argument
and (wrapped with lookup_file_urn) passed force=FALSE from item_move().
This call then fails for regular files because only directories are
cached once crawling has completed as stated in the comment in
finish_current_directory() in libtracker-miner/tracker-file-notifier.c.
https://bugzilla.gnome.org/show_bug.cgi?id=678986
|
| |
|
| |
|
|
|
|
|
| |
Only 2 left, mainly because they're a NOP or don't work currently and need
fixing.
|
|
|
|
|
| |
This covers tracker_config_get_crawling_interval() and
_get_removable_days_threshold() which were returning just 0.
|
| |
|
|
|
|
| |
Use _CRAWLER_ in there so we know where it comes from.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This patch does 3 things:
1. Fix the --with-enca (which should have been --enable-enca and was failing)
2. If JHBUILD_PREFIX is set, use that when no args are given
3. If no args are given, use the make distcheck default args in place
This will ensure documentation and unit tests are build most of the time and
things don't break so often :)
|