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 says there is good resources and the first title on the landing page says that those practices are bad and should not be used any more. Maybe find something else to link to make that point?

I think it would be useful to add a mention about Async streams (IAsyncEnumerable) when a developer wants to tackle 'Handle streams of data' problem.

在解决了上面两个issue后，按照123页运行后，还是无法启动两个gpu:worker，加一个cpu：PS分布式训练。求问命令行应该如何输入，还是代码的问题。

our prior recommendation, removed in 4bb8d76177c40c9a0405ca66da9a40dcbded4505, caused issues with makefiles on ubuntu 16.x (xenial), i.e., on our staging server, such that all recipes failed with the error "No such file or directory". do some research on directives, identify the culprit, and add a new, portable set of default directives.

Need to have section or separate document where we will place trivial problems descriptions and how to fix them.

For example:

N+1 Problem

Short description, like we have extra queries

Diagnostic

We can review log file ourselves or setup gem bullet for auto-detection

Solution

Add include

References

1. Some links for best posts about this problem