This allows for better error reporting. Instead of logging a CRITICAL
about the context of the error, prefix it to the GError so that it can
be sent back to the caller.

https://gitlab.gnome.org/GNOME/gnome-online-miners/-/merge_requests/3
https://gitlab.gnome.org/GNOME/gnome-online-miners/-/merge_requests/6

GOA disabled the Documents provider feature, so use the Files one
when a documents miner is requested, instead.

https://gitlab.gnome.org/GNOME/gnome-documents/issues/34

https://bugzilla.gnome.org/show_bug.cgi?id=779947

No code changes needed, it is expected to remain compatible with current
usage in gnome-online-miners.

These were added to the copy of this code in gnome-documents, but we
don't use that there anymore.
Move them to the right place.

https://bugzilla.gnome.org/show_bug.cgi?id=770899

We will need this in the insert_shared_content implementation to add
the nie:links and nie:relatedTo properties.

https://bugzilla.gnome.org/show_bug.cgi?id=770899

https://bugzilla.gnome.org/show_bug.cgi?id=770899

This will let us use this code from the insert_shared_content
implementation.

https://bugzilla.gnome.org/show_bug.cgi?id=770899

This will let us use this code from the insert_shared_content
implementation.

https://bugzilla.gnome.org/show_bug.cgi?id=770899

https://bugzilla.gnome.org/show_bug.cgi?id=770899

https://bugzilla.gnome.org/show_bug.cgi?id=770899

https://bugzilla.gnome.org/show_bug.cgi?id=770899

Untangling gom_account_miner_job_ensure_datasource from
GomAccountMinerJob will let us reuse it in the implementation of
InsertSharedContent in a subsequent commit.

https://bugzilla.gnome.org/show_bug.cgi?id=770899

This will help us reuse the parts of the RefreshDB code for
implementing InsertSharedContent.

https://bugzilla.gnome.org/show_bug.cgi?id=770899

This will help us reuse the parts of the RefreshDB code for
implementing InsertSharedContent.

https://bugzilla.gnome.org/show_bug.cgi?id=770899

This will help us reuse the parts of the RefreshDB code for
implementing InsertSharedContent.

https://bugzilla.gnome.org/show_bug.cgi?id=770899

The list of pending GomAccountMinerJobs is specific to each invocation
of gom_miner_refresh_db_async. It shouldn't be instance wide.

https://bugzilla.gnome.org/show_bug.cgi?id=770889

This will make the subsequent commit easier to read.

https://bugzilla.gnome.org/show_bug.cgi?id=770889

There is no need to track it separately because we can get it from the
GTask.

https://bugzilla.gnome.org/show_bug.cgi?id=770889

Just as each invocation of gom_miner_refresh_db_async should have a
separate GTask, it should also use the GCancellable specifically passed
by the caller. Having an instance variable in the GomMiner class
violates this principle.

There is also no need for a separate GCancellable in
GomAccountMinerJob. We can use the one passed in by the caller.

https://bugzilla.gnome.org/show_bug.cgi?id=770889

We should have a separate GTask for each invocation of
gom_miner_refresh_db_async. Otherwise subsequent invocations on the
same instance will trample over each others state.

This also prevents a leak if gom_miner_refresh_db_async was invoked
twice on the same GomMiner instance.

https://bugzilla.gnome.org/show_bug.cgi?id=770889

The port to GTask has simplified gom_miner_complete_error to the point
where we can directly use g_task_return_error.

https://bugzilla.gnome.org/show_bug.cgi?id=770889

Otherwise, we will violate our own assertion in
gom_miner_complete_error.

https://bugzilla.gnome.org/show_bug.cgi?id=770889

https://bugzilla.gnome.org/show_bug.cgi?id=770889

https://bugzilla.gnome.org/show_bug.cgi?id=770889

https://bugzilla.gnome.org/show_bug.cgi?id=770889