running compact() in the same transaction will only increase the data size on disk due to
RocksDB not being able to remove any documents physically due to the snapshot that is
taken at transaction start.
This change also exposes db.<collection>.compact() in the arangosh, in order to manually
run a compaction on the data range of a collection should it be needed for maintenance.
* Backport active-failover fix for Windows into 3.4
* Backport stop/resume for Windows from devel
* Backport changes from devel into tests also
* Fix tests
* Remove forgotten whitespaces
* Remove procdump usage while taring archives
* Add 3.2 upgrade-data tests to oskar blacklist for 3.4
* Fix typo
* Add 3.4 upgrade-data tests to oskar blacklist for 3.4
* wait for procdump to exit too.
* move running process check up, propagate status. First check whether processes are still running before attempting to force kill them
* only list processes, don't change their state
* add stopping procdump in all places
* Bug fix/update foxx services after restore (#6774)
* triggers foxx queue update which leads to the internal selfHeal function of a foxx app to make foxx apps publicy visible after a foxx app is restored
* this will also add the recognition of imported foxx services
* Testing JS refactoring
* Added test case for Foxx dump -> restore cases
* Fixed check, sth- i tries to contact to the foxx service. Test is red now.
* Fixed tests for dump / restore using Foxx. Also first draft to fix the fox side. Blocked by sth. fixed in the Main Repositorx already
* Fixed typo in dump/restore testsuite
* Removed old version of the fix
* Fixed JSLint
* Removed debug-log output from foxx manager
when just starting the arangosh without a connection to a server
and running code such as `require("internal")`, the shell always
printed "connection class corrupted", which is somewhat misleading.
just don't print this error here, as it is useless