The project is using SonarCloud static code analysis. The latest results are showing that it has found several blocker and critical severity code smells. In this task those are fixed or marked as false positives. To mark false positives, SuppressWarnings annotation should be used in code as explained in the linked documentation.

Links:
[Blocker and critical severity code smells in SonarCloud](

It is useful to be able to delay state recovery until enough data nodes have joined the cluster, since this gives the shard allocator a decent opportunity to re-use as much existing data as possible. However we also have the option to delay state recovery until a certain number of master-eligible nodes have joined, and this seems unnecessary: we require a majority of master-eligible nodes for stat

While writing the release notes for Spring Boot 2.3.0.M2, I've realized that the structure of the reference doc for the Maven and Gradle plugins are almost identical but not quite.

Now that we use the same infrastructure for both guides, I wonder if there wouldn't be an interest to also harmonize the structure.

The reference doc of Gradle is at https://docs.spring.io/spring-boot/docs/2.3.

• We have BFS and DFS images in both Breadth First Traversal and Depth First Traversal. We should have illustrations in the respective sections.

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

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.

MutableClassToInstanceMap

I think it permits null values but not keys. Eventually we should have nullness annotations that make the clear, but even then, it's nice to document up front, as we do for most other types.

Perhaps the ClassToInstanceMap interface should also be clearer that null keys are forbidden and null values might or might not be.

• 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

假如有一排房子，共 n 个，每个房子可以被粉刷成红色、蓝色或者绿色这三种颜色中的一种，你需要粉刷所有的房子并且使其相邻的两个房子颜色不能相同。

当然，因为市场上不同颜色油漆的价格不同，所以房子粉刷成不同颜色的花费成本也是不同的。每个房子粉刷成不同颜色的花费是以一个 n x 3 的矩阵来表示的。

例如，costs[0][0] 表示第 0 号房子粉刷成红色的成本花费；costs[1][2] 表示第 1 号房子粉刷成绿色的花费，以此类推。请你计算出粉刷完所有房子最少的花费成本。

注意：

所有花费均为正整数。

示例：

输入: [[17,2,17],[16,16,5],[14,3,19]]
输出: 10
解释: 将 0 号房子粉刷成蓝色，1 号房子粉刷成绿色，2 号房子粉刷成蓝色。
  最少花费: 2 + 5 + 3 = 10。

题目地址： ht

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

There should be a README file for each type of design pattern which should include the following points-

• Description of the design pattern
• Common use cases of that design pattern
• Explanation of the code

Describe your idea:
Is there a feature for the cli version of jadx to exclude packages, similar to the GUI version?

Hello everyone,

I would like to propose adding more documentation on this open source project as there is limited information for new contributors (especially English speaking ones). Here are the 2 additional documentation I think should be added to help new contributors to this project:

1. Add Authors / Main Contributors contact section
   In case new contributors have questions, it would

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.

This is in response to #7264, since we decided that PR is not the right way to do it.

I think we decided on: move the non-browser-specific tests out of the browser-specific test files.

So if the "chrome only" tests pass when using Firefox for instance, they should be moved to unit tests or into a common spec file of some kind.

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);
        

Overview of the feature request

entity name should be in @RequestMapping in [entityName]Resource.java, in order to avoid code duplication of entity name in @GetMapping, @PostMapping, @PutMapping, @DeleteMapping etc.

@RestController
@RequestMapping("/api/[entityName]")
// ...
@GetMapping("/{id}")
// ...
@DeleteMapping("/{id}")

instead of

@RestController
@Re

[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