In the App class of the abstract-factory pattern, there are several methods which seemingly only serve to confuse readers.
Is there a point to having a method that returns a King, from a passed in KingdomFactory?

King getKing(final KingdomFactory factory) {
     return factory.createKing();
   }

Rewriting exists queries to a MatchNoneQueryBuilder when the field is unmapped would help skip shards in the can_match phase.

A How-to about Testcontainers would be quite useful.

The heap.png image in the readme (https://raw.githubusercontent.com/kdn251/interviews/master/images/heap.png) shows a tree that does indeed respect the heap order property. The problem is when you mention the time complexities. In order to have O(log(n)) insert / remove time you also need for your heap to be a complete binary tree. The heap in the picture is not a complete binary tree. I think it

The transparent ones look terrible with dark-themed IDEs or non-light background:

Only looks fine in Eclipse:

Write a program that goes through the images in `https://g

英雄招募

成为 Doocs 项目维护者

本项目 advanced-java，包括 Doocs 开源组织下的所有项目，都欢迎各位朋友参与完善。

如果你提交的内容有价值，且具备规范性，将有机会提升为项目的维护者，直接参与项目的 review、merge 等维护工作，提交内容时也可以直接 push 到 doocs/advanced-java 主分支 master 下，无须提交 PR 等待 review。

目前 advanced-java 只有 [yanglbme](http

...assuming that that's how we feel nowadays; it's been a while :) There are probably exceptions, including maybe for cases in which one service wants to express a dependency on another, but again, I'm not sure how we feel about that today.

I'd like to be able to limit the retry count in Authenticator to 3. At the moment it appears to be 20. I don't see anything to do this and didn't get an answer in StackOverflow, so assuming it's not possible at the moment.

• Documentation:

It would be nice if the official documentation explains how to use Retrofit together with co-routines together with the best practices regarding the asynchronous handling of requests. My students need to implement their calls using Retrofit and co-routines (following the tutorials in the Udacity course, but for documentatio

I found a bug, clear data while I'm scrolling，the chart will zoom in and out abnormally.
It need to call mChartTouchListener.stopDeceleration() in chart.clear()

对于数组[1, 2, 3, 4] 和 [4, 3, 2, 1] 你的冒泡排序算法是否都能获得不错的效率？

Run following commands and enjoy the stream of warnings from Dokka:

rm -rf docs/api
./gradlew leakcanary-android-core:dokka leakcanary-android-instrumentation:dokka leakcanary-android-process:dokka leakcanary-object-watcher-android:dokka leakcanary-object-watcher:dokka shark-android:dokka shark-graph:dokka shark-hprof:dokka shark-log:dokka shark:dokka

Review errors and see if any of t

static <T extends Comparable> void flip(T[] array, int left, int right) {
while (left <= right) {
swap(array, left++, right--);
}
}
Change 'left <= right' to 'left < right', can improve efficiency in some cases

It would be helpful to new users who want to communicate with the site administrator or get on a mailing list to include a contact subsection under the README.md file as a subsection.

Many users confuse about no class, no method, expression error.

Arthas should add a verbose/debug option, to print the command arguments and the debug info in command execution.

Ruby has updated the Profile code (SeleniumHQ/selenium#7376) in preparation for 4.0. Ensuring the proper working order of this code will require manual evaluation in addition to unit testing. This shouldn't be too complicated. @kapoorlakshya volunteered to look at it, but I'm creating this issue to make sure it doesn't fall by the wayside.

What's the ETA for updating the massively outdated documentation?

Please update all documents that are related building CNTK from source with latest CUDA dependencies that are indicated in CNTK.Common.props and CNTK.Cpp.props.
I tried to build from source, but it's a futile effort.

Issue details

Camera.unproject does not return original value

Reproduction steps/code

    public void create() {
        Vector2 tmpvec = new Vector2();
        tmpvec.set(0, 0);

        Stage stage = new Stage(new ScreenViewport());
        stage.stageToScreenCoordinates(tmpvec); // has the correct screen coords;
        stage.screenToStageCoordinates(tmpvec);
        

[REQUIRED] Use case description

Gradle provides both way to write build script - Groovy, and Kotlin.
While both languages are perfectly fine to write typical build logic, they have different APIs in some cases.

To build locally in Kotlin, one should use gradle.extra - ExtraPropertiesExtension, which is not defined in the class definition of Gradle.

// ExtraPropertiesExte