fix(deps): update dependency cn.dreamtobe.threaddebugger:threaddebugger to v1.6.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
cn.dreamtobe.threaddebugger:threaddebugger	1.3.3 -> 1.6.3

---

Release Notes

Jacksgong/ThreadDebugger (cn.dreamtobe.threaddebugger:threaddebugger)

v1.6.3

2019-12_15

• Fix: Fix low case for stack overflow when ExceedWait no active and exceed-queue more then one wait job
• Fix: Fix small case exceed queue can't be consume but wait for new task

v1.6.2

2019-08-01

• Fix: fix the count of thread not right exactly.
• Fix: fix thread category can't match since not ignore its case

v1.6.0

2019-07-29

• Prefs: optimize getting all threads operation without get their stack traces

v1.5.3

2018-09-28

• Fix stackoverflow on ExceedWait when worker count is meet max-pool-size and one-worker-thread is blocked waiting for queue available and cpu time slice not alloc for blocked thread after queue available

v1.5.2

2017-03-23

New Interfaces

• Add ThreadDebugger#ignoreUnknownCategory: Only print thread info which you explicitly add through ThreadDebugger#add for method ThreadDebugger#drawUpEachThreadInfo, ThreadDebugger#drawUpEachThreadInfo, ThreadDebugger#drawUpEachThreadSizeDiff, ThreadDebugger#drawUpEachThreadInfoDiff, ThreadDebugger#isChanged, ThreadDebugger#isSizeChanged.

Fixes

• Fix: fix delete split on wrong opportunity.
• Fix: fix can't match start-with-thread-name exactly.

v1.4.0

2016-10-09

New Interfaces

• Add ThreadPools#newNoCorePool: If there are threadCount tasks are running, the further task will be enqueued to the waiting queue, and will be executed when the size of running tasks less than threadCount. If the thread in this pool is turn to idle and the interval time of waiting for new tasks more keepAliveTime, it will be terminate to reduce the cost of resources.

Enhancement

• Improve Stability: If corePoolSize is equal to 0 when ThreadPools.newExceedWaitPool is called, then we will create NoCorePool instead of ExceedWaitPool to avoid the small probability of StackOverflow because getActiveCount() may return 0 when corePoolSize is 0 in ExceedWaitPool and performs a large number of tasks at high frequencies, but the actual running thread The number is greater than 0.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.