* apply filters before starting the server, so we can detect whether no test would be executed
* skipTimecritial and skipNondeterministic also qualify for non-errnous empty testcase
* simplify code, if is issued no matching testcase is an error
* Update test-utils.js
* add analyser http API tests
* add more tests
* add tests and lint
* remove print
* add another test
* fix formattig
* add e6 expresseion as key in object
* WIP: add analyzer permissions test
* fix test
* lint
* WIP: try to add analyzer auth-test
* add sleepBeforeStart option
* use basic auth
* fix tests
* change test so it would work if the api was as expected
* fix authentication test
* fit shell client analyzer test
* fix shell-analyzer-rest-api.js
* fix auth-analyzer.js
* fix user-access-right-update-view-arangosearch.js
* remove print statements
* Fixed analyzer parameters for test
* make rspec timeouteable (on windows for now)
* add timeout state, fix windows implementation
* abort testrun if a timeout in rspec occured
* lint
* fix scope of procdump stopper
* fix include scope
* fix invokation
* use proper variable to wait for
* add output before we attempt to talk to the SUT, so we can better insulate startup lockups
* when we timeout a process dump out all we know about the SUT.
* when we timeout a process dump out all we know about the SUT.
* make rspec timeouteable (on windows for now)
* add timeout state, fix windows implementation
* abort testrun if a timeout in rspec occured
* lint
* fix scope of procdump stopper
* fix include scope
* fix invokation
* use proper variable to wait for
* Add failing tests
* Add tests for Buffer#slice
* Add tests for Buffer#new
* Skip failing tests
* Implement changes
* Unskip failing tests
This reverts commit 9f8a34bd74e152b7b3158fea79b12e6da8343001.
* Fix implementation
* Remove meaningless test
This test only succeeded because of a broken implementation of the Buffer constructor. It doesn't really do anything useful.
* Add note to CHANGELOG
* preserve the instance shutdown state, and if its bad, don't clean up the test directory
* Update js/client/modules/@arangodb/testing.js
Co-Authored-By: Tobias Gödderz <github@tobias.goedderz.info>
* Update js/client/modules/@arangodb/testsuites/permissions_server.js
Co-Authored-By: Tobias Gödderz <github@tobias.goedderz.info>
* Update js/client/modules/@arangodb/testsuites/permissions_server.js
Co-Authored-By: Tobias Gödderz <github@tobias.goedderz.info>
* Update js/client/modules/@arangodb/testsuites/single.js
Co-Authored-By: Tobias Gödderz <github@tobias.goedderz.info>
* fix handling in custom start/stop handlers
* remove shutdown state from reporting structure
* fix shutdown of second instance
* one more to adjust
* only add jwt if we run the agency with authentification
* lint
* Began work on generic traversal testing framework
* Translate shard ids to smart attributes
* Minor fixes
* Added a TODO note
* fixed tests
* cleanup
* first tests inside new traversal framework working
* added single server diamond tests
* Enable sharding in aql-graph-traversal-generic-graphs.js
* Tried to fix smart sharding
* Fixed smart graph name clashes, some cleanup
* Added meta tests
* Added TODO note
* Fixed single server
* Added a BFS order check
* Renamed test
* added more dfs and bfs tests for the openDiamond graph
* Added new graph "largeBinTree"
* Fix Map usage
* added smallCircle graph, added three dfs tests
* added smallCircle graph, added three dfs tests
* more smallCircle dfs tests
* Fixed largeBinTree shardings, and long graph names
* Fix long suffixes
* Provided names for shardings
* Added a log message
* more bfs smallCircle tests
* more bfs smallCircle tests - global
* smallCircle picture
* added completeGraph to graph test suite
* added more dfs tests for the complete graph up to depth 3
* Removed duplicate function definitions
* added depth 2 dfs complete graph test, added missing test to the exports
* Added test for largeBinTree
* added three path graphs, easy, advanced and more advanced
* Added a working check for bfs with global uniqueness
* Fixed usage of bfs checks
* Fixed expected input for two tests
* Added some static assertions to largeBinTree
* Oops
* added more advancedPath dfs tests
* better formatting of the visual graph
* more dfs advanced graph tests
* Implemented all easy path test combinations
* Fixed testAqlGraphQuery
* Fix in bfs check error reports
* Removed duplicate test
* Added advancedPath BFS tests
* Updated comments
* Fixed new tests
* Fixed graph description
* added more complete graph bfs tests
* added more complete graph bfs tests
* added testCompleteGraphBfsUniqueEdgesNoneD1 and testCompleteGraphBfsUniqueEdgesNoneD2
* added testCompleteGraphBfsUniqueVerticesUniqueEdgesPathD3 test
* added a few more complete graph bfs checks
* Extended a comment
* Unbreak aardvark when --foxx.api false
The easiest way to disable the aardvark foxx routes is to just skip the
import and mount altogether. The previous approach caused the service to
throw an error because the module doesn't actually export anything.
There's no need to prevent the export if we just don't import the module
to begin with.
* Add an error code for service api disabled
* Throw an actual error when accessing Foxx API routes
* Throw an error when using legacy Foxx API
There's no easy way to use a catch-all here so disable them one by one. No new routes will be added to this API and it'll go away in 4.0 so there's no risk of forgetting to add the throw-check in new routes.
* Render subnav without delay
The subnav doesn't need the perm check results but we need the subnav to exist so we can populate it in other parts of the app. This fixes the subnav not showing up when reloading certain views (e.g. install service via upload).
* Hide ONLY the Foxx store when it is disabled
We still want to allow installing and upgrading/replacing services. We just don't want to show the store.
* Hide Foxx services in frontend if Foxx API is disabled
* Build aardvark
* fixed typo in disable check, fixed tests
* Unbreak aardvark when --foxx.api false
The easiest way to disable the aardvark foxx routes is to just skip the
import and mount altogether. The previous approach caused the service to
throw an error because the module doesn't actually export anything.
There's no need to prevent the export if we just don't import the module
to begin with.
* Add an error code for service api disabled
* Throw an actual error when accessing Foxx API routes
* Throw an error when using legacy Foxx API
There's no easy way to use a catch-all here so disable them one by one. No new routes will be added to this API and it'll go away in 4.0 so there's no risk of forgetting to add the throw-check in new routes.
* Hide Foxx services in frontend if Foxx API is disabled
* Render subnav without delay
The subnav doesn't need the perm check results but we need the subnav to exist so we can populate it in other parts of the app. This fixes the subnav not showing up when reloading certain views (e.g. install service via upload).
* Hide ONLY the Foxx store when it is disabled
We still want to allow installing and upgrading/replacing services. We just don't want to show the store.
* Build aardvark
* splittet one query templates into two seperate files
* fixed syntax error in graphSettingsView
* fixed syntax error in foxxEditView
* rm not needed fix of tooltips
* changed format of ejs files due to pre-compiling templates now
* load templates via script tag
* adjust arango helper to work with new tippy version
* adjust arango templateEngine to work with pre compiled underscore templates
* minify and uglify pre compiled templates
* modified gitignore to not track not minified and uglified templates
* fixed queryViewOutput template
* make tooltips visible again!
* add grunt-contrib-jst to package.json
* make templates.js accessible via aardvark
* ... and enable gzip for em
* added build templates
* move IResearchViewSort into separate unit
* ensure sort is propagated to IResearchLink
* update iresearch and extend some tests
* implement insertion of sorted values, store value comparator in link
* add tests for VPackComparer
* minor cleanup
* fix issue with sort definiton propagation
* propagate error message from index factory
* add integration tests for sorted indexes, single server
* initial implementation of IResearchViewMergeExecutor
* move iresearch::VPackComparer to separate translation unit
* store collection in IndexReadBuffer for IResearchViewMergeExecutor
* set primary sort from optimizer rule
* add some tests for sorted view case
* extend IResearchViewNode tests
* simplify primary sort definition
* pretty print order condition covered by arangosearch in query explanation
* fix compilation with g++-8
* address catch test failures
* fix tests
* adjust arangosearch optimizer rule to optimize sort in case of cluster
* make tests for sorted indexes work in cluster too
* fix tests
* extend js tests for sorted indices
* fix keyword in query explainer
* ensure sort-limit rule works with views
* backport ngram analyzer fix from upstream
* address jslint errors
* modify IResearchViewSort to support boolean direction specification format
* add some tests
* add tests
* add skip functionality
* extend tests
* add more catch tests
* inline some methods
* address jslint errors
* extend catch tests to reproduce the failure
* add some tests for check fullcount
* add more tests
* extend tests
* temporarily comment out broken tests
* extend js tests
* address review comments
* address jslint errors
* update iresearch
* issue 526.9.1: implement swagger interface, add documentation
* address review comments
* add ngram
* Formatting
* Move REST description to new Analyzers top chapter in HTTP book
* Missed a DocuBlock
* Add Analyzers chapter to Manual SUMMARY.md
* Move REST API description back to Manual
Headlines were broken
* Add n-gram example
* Port agency performance tuning for many shards to devel.
* Add more IDs to LOG_TOPIC calls.
* Even more IDs for LOG_TOPIC.
* Fix a duplicate LOG_TOPIC ID.
* Fix an old merging bug in devel.
* Don't hesitate between phases one and two for small clusters.
* don't run compact() on a collection after a truncate() was done in the same transaction
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 we take at transaction start.
Decoupling the truncate transaction from the compact operation allows finishing the truncate transaction first, so we can
get rid of the snapshot. Running compact afterwards is then free to physically remove all the data.
As a nice side effect this change will also speed up the truncation of larger collections, because the compact will run
faster.
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.
* fix documentation anchors
Wilfried Goesgens
Tobias Gödderz
Jan
Jan Christoph Uhde
Andrey Abramov
Lars Maier
Heiko
Markus Pfeiffer
Alan Plum
Frank Celler
Dan Larkin-York
Tobias Gödderz
Michael Hackstein
jsteemann
Vasiliy
KVS85
Lars Maier
Frank Celler
Max Neunhöffer
Simon