| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
When stopping the DBus service, we don't unset the SIGTERM handler
that tries to stop the DBus service. This results in race conditions
around subprocess.wait().
Remove first the handler, then terminate.
|
| |
|
|
|
|
|
|
|
| |
I changed the name of the logger in
https://gitlab.gnome.org/GNOME/tracker/-/merge_requests/254.
This updates tracker-sandbox accordingly so that log messages from
the DBus daemons appear on stdout by default.
|
|
|
|
| |
We now got it at hand, and it's useful for debug.
|
| |
|
|
|
|
| |
Fixes: https://gitlab.gnome.org/GNOME/tracker/-/issues/218
|
|
|
|
|
|
|
|
| |
URNs are the preferred way to identify resources in a tracker store,
don't treat them as an afterthought here and query the URNs right
away. Drop the flags argument entirely as it becomes unneeded, any
further information cannot be inferred and should be performed by
the user.
|
|
|
|
| |
I renamed some files without updating meson.build, in 12a23d2e88d6b44e.
|
|\
| |
| |
| |
| | |
Print timeout values in await timeout errors
See merge request GNOME/tracker!267
|
| |
| |
| |
| | |
Helpful to debug https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/209
|
|/
|
|
|
|
|
|
|
|
| |
This models what gobject-introspection does with its giscanner library,
which is the model I think we should copy (it's a Python module but
we consider it Tracker-specific rather than part of the regular Python
module ecosystem).
Previously we tried to put it into lib/ rather than lib64/ on 64-bit
systems. This causes unneeded friction.
|
|
|
|
| |
This allows us to work with umockdev to simulate hardware events.
|
|
|
|
| |
This saves a small amount of copy-paste code in tracker-miners.git.
|
|
|
|
| |
These two modules aren't related, it's cleaner to split them.
|
|
|
|
| |
The shell script that wraps the Python module was not quoting arguments properly :/
|
|
|
|
|
| |
Use argparse mutually-exclusive option groups instead of checking
these manually.
|
|
|
|
|
| |
We overwrite the user's real DConf settings in this case, which is
confusing for everyone.
|
|
|
|
|
|
| |
The new `--dbus-session-bus` argument can be used to run a command
inside an existing sandbox. This is useful when developing and
debugging.
|
| |
|
|
|
|
|
|
| |
It is better to set up the paths in the top level, rather than cobbling them up at place of use.
Joining paths using string concatenation also breaks alternative Meson implementations that support absolute libdir option.
|
|
|
|
|
| |
This can be used for interacting with your "real" Tracker store
(in ~/.cache) with an uninstalled build of Tracker.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
In particular, a new --index-recursive-tmpdir flag is designed for use
by app test suites. They can run the set with a temporary directory
already set up for indexing, and when they create content in this
TRACKER_INDEXED_TMPDIR directory it'll automatically be indexed by
the miner-fs and can be used in their tests.
|
|
|
|
|
|
| |
We were configuring index-recursive-directories and
index-single-directories with the same value, which let
to all directories being indexed non-recursively.
|
|
|
|
|
| |
In preparation for adding a new `--index` option that controls which
locations to index.
|
|
|
|
| |
Commit f3913b15e801327c48b didn't set the path properly.
|
|
|
|
|
|
| |
There are now two kinds of updates, property updates, and whole
information updates where a resource is deleted and a new one inserted.
Let's treat them separately.
|
|
|
|
|
|
| |
Database queries should always specify the graph(s) they want to
query from. This is how we enforce data isolation and it's also
faster than running a query against the union of all graphs.
|
|
|
|
|
|
| |
The stop_miner_fs() function is now stop_daemon() and the caller
supplies the busname. This makes it more flexible and avoids hardcoding
the miner-fs busname.
|
|
|
|
|
| |
Calling .stop_miner_fs() could trigger a crash if the miner
wasn't running (perhaps if it had itself crashed).
|
|
|
|
|
| |
I didn't make this a proper feature, but it's a clue that you can
turn on D-Bus monitoring inside the sandbox.
|
|
|
|
|
| |
If Tracker is installed into /opt/tracker3 for example then the
introspection data will be missed. Let's make this just work.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All of these are unused within tracker-miners, and as far as we know
they are also unused in GNOME.
Each ontology has a cost on database size and on time to create a
new database, so it's good to limit these as much as we can.
Alternatives:
- nid3: use nmm ontology
- ncal, scal: use evolution-data-server as GNOME Calendar does
- mlo: use slo ontology
|
|
|
|
|
| |
I don't think any of this is being used by anyone. Let me know
if that's not true! :)
|
|
|
|
|
| |
Check things through nie:isStoredAs, even though it currently points
to self in most situations.
|
|
|
|
|
|
| |
With DataObject and InformationElement being split, a file update may result
in the InformationElement being torn out and completely recreated. Add code
to handle this situation to await_update.
|
|\
| |
| |
| |
| |
| |
| | |
Rework debug logging for 3.0
Closes #178
See merge request GNOME/tracker!219
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Users should now use G_MESSAGES_DEBUG=Tracker to see debug messages
on the console.
The TRACKER_VERBOSITY only worked if tracker_log_init() had been called,
which can't be done when libtracker-sparql is being used from an
application outside of Tracker.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our ontology URLs now use a namespace that we manage, at
http://tracker.api.gnome.org/. This domain won't expire and can
redirect anywhere we want, so that it can always link to the
correct documentation for the ontologies.
We are going to continue using the Nepomuk name in the ontologies
that were developed by the Nepomuk project, despite changing the
URL. This way we acknowledge that we have downstream changes to
the Nepomuk ontologies but still provide a link to the original
shared vocabularies.
Fixes https://gitlab.gnome.org/GNOME/tracker/-/issues/162 and https://gitlab.gnome.org/GNOME/tracker/-/issues/104
|
|
|
|
| |
It's bumping to org.freedesktop.Tracker3.*
|
|\
| |
| |
| |
| | |
Functional test improvements
See merge request GNOME/tracker!207
|
| | |
|
|\ \
| |/
|/|
| |
| | |
Remove maemo ontology and tracker:defaultValue setting
See merge request GNOME/tracker!194
|
| |
| |
| |
| | |
It's very obsolete.
|
|\ \
| | |
| | |
| | |
| | | |
Some improvements for tracker-sandbox / run-uninstalled script
See merge request GNOME/tracker!197
|
| | |
| | |
| | |
| | |
| | |
| | | |
This code never executed because the sandbox would probably
have already crashed due to the D-Bus daemon exiting before
we wanted it to.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This means that if the user presses CTRL+C, the sandbox process will
handle it and will shut down processes cleanly, but the D-Bus daemon
will not receive the CTRL+C and will keep running until the sandbox
process tells it to stop. This prevents errors during shutdown of
Tracker processes which don't expect the message bus to have
already disappeared.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This means that Tracker instances created for testing and development
will begin empty, and will only contain content explicitly added by the
developer.
|