- 17 7月, 2019 3 次提交
-
-
由 彭勇升 pengys 提交于
-
由 Daming 提交于
* Using ArrayList to instead of LinkedList
-
由 kezhenxu94 提交于
* Add docs of e2e development guide
-
- 16 7月, 2019 2 次提交
-
-
由 kezhenxu94 提交于
The e2e containers' names of single mode and cluster mode would conflict when they start up simultaneously in Jenkins job.
-
由 彭勇升 pengys 提交于
* Correct spelling errors in the network protocol. * update protocol submodule commit id.
-
- 15 7月, 2019 4 次提交
-
-
由 彭勇升 pengys 提交于
-
由 Jared Tan 提交于
-
由 li.can 提交于
-
由 kezhenxu94 提交于
* Fix wrong logger name * Fix more wrong logger names in agent side
-
- 14 7月, 2019 2 次提交
-
-
由 kezhenxu94 提交于
* Add e2e cluster tests
-
由 wu-sheng 提交于
-
- 13 7月, 2019 2 次提交
-
-
由 Daming 提交于
* setup your idea * add anchors * fix * Update docs/en/guides/How-to-build.md Co-Authored-By: Nkezhenxu94 <kezhenxu94@163.com> * Update docs/en/guides/How-to-build.md Co-Authored-By: Nkezhenxu94 <kezhenxu94@163.com>
-
由 wu-sheng 提交于
-
- 12 7月, 2019 6 次提交
-
-
由 Daming 提交于
-
由 于玉桔 提交于
-
由 Alan Lau 提交于
-
由 彭勇升 pengys 提交于
-
由 Alan Lau 提交于
-
由 zhangwei 提交于
* fix deleteIndex repeat append namespace * fix deleteIndex repeat append namespace * fix checkStyle * fix * fix test assert * update test method name * fix test * fix * del elastic.search.namespace * fix check style * update ITElasticSearchNamespaceClient to ITElasticSearchClientOfNamespace * move undoFormatIndexName to ITElasticSearchClien * move #getIndex to ITElasticSearchClient * add deleteByModelName and deleteByIndexName * add deleteByModelName and deleteByIndexName * revert ITElasticSearchClient#getIndex * Use whitebox get from powermock to get this. * undo namespacePrefix
-
- 10 7月, 2019 2 次提交
- 09 7月, 2019 1 次提交
-
-
由 贺爷 提交于
-
- 08 7月, 2019 1 次提交
-
-
由 Jared Tan 提交于
* add 富国基金管理有限公司 to powered by page. * Update powered-by.md
-
- 04 7月, 2019 1 次提交
-
-
由 zygfengyuwuzu 提交于
* Update powered-by.md 北京宅急送快运股份有限公司 * Update powered-by.md
-
- 03 7月, 2019 3 次提交
-
-
由 Gao Hongtao 提交于
-
由 Gao Hongtao 提交于
* Set up 10 seconds deadline after gRPC client sending * The duration of deadline contains three segments: connecting, request and response For blocking stub, I just set deadline before invoke service. For bi-streaming stub, I found all of them are used as a blocking style, that after getting streaming response client stub just close current streaming. Base on above reality, I pick the same way as blocking one.
-
由 kezhenxu94 提交于
-
- 02 7月, 2019 2 次提交
-
-
由 zhousiliang163 提交于
* fix issue #2979 * remove the unused import, which causes the CI failed
-
由 于玉桔 提交于
* spring_async_plugin * fix * fix * fix * fix * format fix * rename * fix * fix version * Update SWCallable.java * Update Supported-list.md * Update Supported-list.md
-
- 01 7月, 2019 4 次提交
-
-
由 Xin,Zhang 提交于
-
由 于玉桔 提交于
* AsyncAppender * improve performance * fix mdc issue * fix mdc * add Async demo
-
由 wu-sheng 提交于
* Enhance module manager
-
由 wu-sheng 提交于
* etcd configuration is not implemented and the provider definition is copied from cluster management, which could cause multiple loading by module manager. * Fix a missing delete.
-
- 30 6月, 2019 1 次提交
-
-
由 kezhenxu94 提交于
e2e test setup. cc @hanahmily @peng-yongsheng @IanCao @zhaoyuguang @JaredTan95 # e2e test case One single standalone Spring service, accessing H2 database. This service has been installed the agent. OAP runs in single mode with H2 storage too. The e2e test will verify the results through GraphQL query 1. Traces exist. 2. Service/Service Instance/Endpoint exist and have expected metrics. 3. Topology exists and match expected.
-
- 29 6月, 2019 3 次提交
-
-
由 Roshi 提交于
V3(this commit) has 20% performance improvement leverages from no `false-sharing` of CPU cache mechanism. /** * Benchmark Mode Cnt Score Error Units * AtomicRangeIntegerTest.testGetAndIncrementV1Performance thrpt 5 13496720.554 ± 240134.803 ops/s * AtomicRangeIntegerTest.testGetAndIncrementV2Performance thrpt 5 39201251.850 ± 1005866.969 ops/s * AtomicRangeIntegerTest.testGetAndIncrementV3Performance thrpt 5 45832615.061 ± 2987464.163 ops/s */
-
由 wu-sheng 提交于
* [maven-release-plugin] prepare release v6.2.0 * [maven-release-plugin] prepare for next development iteration
-
由 kezhenxu94 提交于
-
- 28 6月, 2019 3 次提交
-
-
由 于玉桔 提交于
-
由 caoyixiong 提交于
No password in demo env
-
由 wu-sheng 提交于
-