minor: CircleCI: remove trailing colons with jobs

Not sure if they were intentionally added in https://github.com/pinax/pinax-stripe/pull/418/commits/e04a512e1a1ebad194e2f720b3432afe730139e3 when merging the no-require-lint PR?!

Merge conflict resolve fail on my part.  Thanks for the fix.


Guide to Algorithms

Hey @aaryahjolia, I am Aman Bagadiya. I would like to contribute to this issue, I will include Bellman Ford Algorithm, Breadth First Search - BFS, Depth First Search - DFS, Dijkstra Algorithm, and Floyd Warshall Algorithm.
All will be covered with theory and their implementations.
Please assign it to me!

I'm a contributor for GSSoC '23, I want to work on this issue. Please assign me.


Cannot remove _zk_state_listener when creating BalancedConsumer failed

When an exception raised from here, the _zk_state_listener is added, but the _running flag is not set yet. So calling stop() is ignored, the _zk_state_listener and _zookeeper connection which is owned by us are still there.
We can set _running to True before _add_self, but we will encounter NoNodeError when stop it.
Another problem, when init BalancedConsumer with auto_start=True(the default setting), and an exception raised from here, we cannot get the  instance reference, so there is no way to do cleanups.

Thanks very much for this. I think we could solve this by 1) calling stop() if exceptions occur during start() (and maybe also adding a __del__() that runs stop()) and 2) instead of preventing stop() when not running, making stop() idempotent. Does that sound right?
If I may ask a favour: you seem to be able to trigger that exception out of _add_self() a lot - any chance you could turn that into a test case for test_balancedconsumer.py? Thanks!

@yungchin OK, I'm going to try it sometime.

I don't think calling stop() in response to exceptions in start() entirely makes sense - isn't that the very thing that's causing the NoNodeError? stop() needs to be changed to not assume that everything in start() ran cleanly - possibly wrapping all of the zookeeper operations in stop() in a try that simply warns and passes on exception is good enough.

This issue can be reproduced with test code like this
_zookeeper = KazooClient('<IP_ADDRESS>:2181', timeout=6)
    _zookeeper.start()
    consumer = topic.get_balanced_consumer("foo",
                                        auto_offset_reset=OffsetType.EARLIEST,
                                        reset_offset_on_start=True,
                                        auto_start=False,
                                        zookeeper=_zookeeper)
    try:
        consumer.start()
    except:
        consumer.stop()

and by adding a True or in the check in _add_self().


fight in

Skip to content
Search or jump to…
Pull requests
Issues
Marketplace
Explore
@saiterralogic06
jlord
/
sheetsee.js
Public
Code
Issues
65
Pull requests
5
Actions
Projects
Wiki
Security
Insights
Options in a Worksheet #26
Closed
jlord opened this issue on Aug 22, 2013 · 84 comments
Closed
Options in a Worksheet
#26
jlord opened this issue on Aug 22, 2013 · 84 comments
Comments
@jlord
Owner
jlord commented on Aug 22, 2013
Have a second worksheet in each spreadsheet file that contains some options for the generated page...
@jlord jlord added the big/crazy ideas label on Mar 11, 2014
@beeos beeos mentioned this issue on Sep 5, 2014
Создать текстовый файл с различными примерами разметки beeos/corpus#1
Open
b1thunt3r added a commit to b1thunt3r/hairy-octo-dangerzone that referenced this issue on Dec 7, 2014
@b1thunt3r
Update README.md …
f2b5a4e
@janwirth janwirth mentioned this issue on Jan 8, 2015
Add jade2php adapter jescalan/accord#65
Closed
@wireddown wireddown mentioned this issue on Jan 21, 2015
The Phrenic Shrine Reveals Itself wireddown/ghpages-ghcomments#5
Open
@lukejanicke lukejanicke mentioned this issue on Feb 16, 2015
GitHub Flavored Markdown atom/atom#5574
Closed
@izuzak izuzak mentioned this issue on Feb 16, 2015
GitHub Flavored Markdown atom/markdown-preview#201
Open
@cssmagic cssmagic mentioned this issue on Jul 7, 2015
[译] GitHub 上的书写方式 baixing/FE-Blog#5
Open
@lilydjwg lilydjwg mentioned this issue on Sep 8, 2015
您好,依云,请问Github是不是关闭里issues之间关联的功能? lilydjwg/dotvim#4
Closed
@petrosh petrosh mentioned this issue on Sep 24, 2015
sniþþetrosh petrosh/snippetrosh#7
Closed
4 tasks
@linqiao710 linqiao710 mentioned this issue on Nov 4, 2015
Test certify/template-everyone#40
Closed
9 tasks
@gberche-orange gberche-orange mentioned this issue on Oct 15, 2016
Prevent side-effects from mirrored markdown syntax orange-cloudfoundry/pivotaltrackermirror#1
Open
@djrobstep djrobstep mentioned this issue on Feb 24, 2017
Doesn't work on Windows? djrobstep/migra#6
Closed
@jlord
Owner
Author
jlord commented on May 27, 2017
I'm just closing this to see if it will get less spammy comments ¯_(ツ)_/¯
@jlord jlord closed this as completed on May 27, 2017
Repository owner deleted a comment on Jun 12, 2017
Repository owner deleted a comment from alghurbaalthaneh on Jun 12, 2017
@davepeary220
davepeary220 commented on Jul 4, 2017
[@@_**](### `
`
@1. url
`
`)
**_
@popey456963 popey456963 mentioned this issue on Jul 17, 2017
Redirect Output SBoudrias/Inquirer.js#519
Closed
@mjd0
mjd0 commented on Sep 30, 2017
application/vnd.github.v3+json
lairdshaw added a commit to lairdshaw/fups that referenced this issue on Feb 17, 2018
@lairdshaw
Fixed jlord/sheetsee.js#26
0bd8362
@vaheqelyan vaheqelyan mentioned this issue on Feb 21, 2018
Out vaheqelyan/babel-plugin-promise#1
Closed
@Angel1976
Angel1976 commented on Mar 3, 2018
Duplicate of #11
@galileo galileo bot mentioned this issue on Mar 23, 2018
More to learn papadavis47/markdown-portfolio1#5
Closed
@v0000oooooooo v0000oooooooo mentioned this issue on Mar 24, 2018
Options in a Worksheet #26 #157
Open
@Menu33
Menu33 commented on Mar 28, 2018
img_20180322_172341
@galileo galileo bot mentioned this issue on Apr 12, 2018
More to learn akbarratt/markdown-portfolio#5
Open
@github-learning-lab github-learning-lab bot mentioned this issue on Apr 20, 2018
More to learn magitz/markdown-portfolio#5
Open
@github-learning-lab github-learning-lab bot mentioned this issue on Apr 20, 2018
More to learn javarv87/markdown-portfolio#5
Open
@github-learning-lab github-learning-lab bot mentioned this issue on Apr 20, 2018
More to learn n704/markdown-portfolio#5
Closed
162 hidden items
Load more…
@Wolfm4
Wolfm4 commented on Feb 26
@Wolfm4 Wolfm4 mentioned this issue on Feb 26
Update index.md github/docs#15875
Closed
5 tasks
Wolfm4 added a commit to Wolfm4/docs that referenced this issue on Feb 26
@Wolfm4
Update index.md …
99457de
@huuduyentinh14020201
huuduyentinh14020201 commented on Mar 2

@Jakkree2538 Jakkree2538 mentioned this issue on Mar 9
[~~~~](https://github.com/huuduyentinh14020201/markdown-portfolio/issues/1) #309
 Closed
@lkim100
lkim100 commented on Mar 10
Have a second worksheet in each spreadsheet file that contains some options for the generated page...

#26 (comment)

@Tomcherry117687
Tomcherry117687 commented on Mar 11
I am trying to learn but failed, again and again..someone pls help

@Clydecedric
Clydecedric commented on Mar 15
h

@Kumartalan Kumartalan mentioned this issue on Mar 25
[Uploading Bulk Credit Card Details (colorschemer.com).txt…]() learn-co-students/rails-form_tag-readme-teacher-onboarding#5
 Open
@Kumartalan Kumartalan mentioned this issue on Mar 25
[Uploading Bulk Credit Card Details (colorschemer.com).txt…]()fastag facebook/jest#12603
 Closed
@adpichaerdo
adpichaerdo commented on Mar 29 •
( lock all apps also. ) #0415 ♡ lock links.

@Chhoukra577
Chhoukra577 commented on Mar 29
https://pages.github.com/

@hadimvdm
hadimvdm commented on Mar 31
https://pages.github.com/

@hadimvdm
hadimvdm commented on Mar 31
good

@hadimvdm
hadimvdm commented on Mar 31
@ # #290

@hadimvdm
hadimvdm commented on Mar 31
@rodneyrb147

@hadimvdm
hadimvdm commented on Mar 31
``

@luisuimi
luisuimi commented on Apr 7
<EMAIL_ADDRESS>
@mail731212
mail731212 commented on Apr 17
file:///storage/emulated/0/Download/_B.4a4fg7x.l22qkho2.html

@ahmedrem55538 ahmedrem55538 mentioned this issue on May 14
[@@_**](### ` ahmedrem55538/www.ahmed55538.com#1
 Open
1 task
@Sandimmmmmmm
Sandimmmmmmm commented on May 17
Have a second worksheet in each spreadsheet file that contains some options for the generated page...

@CentUreoN
CentUreoN commented on May 27
Это кошелёк Global, он пополняет мобильный и интернет без комиссии! Между кошельками тоже бесплатно и анонимно. Вывод с мобильного на карту, переводы с карты на карту, платежи по расписанию
https://ref.global24.pro/18449978910269

@Hima88888888 Hima88888888 mentioned this issue on May 28
#237 #226 #289 #237 #290 Hima88888888/laughing-barnacle#2
 Open
YaroslavPodorvanov added a commit to YaroslavPodorvanov/json-to-go that referenced this issue on Jun 4
@YaroslavPodorvanov
Omitempty setting jlord/sheetsee.js#26
628cd09
mholt pushed a commit to mholt/json-to-go that referenced this issue 26 days ago
@YaroslavPodorvanov
Parameter to omitempty for all fields (#112) …
2b15550
@hauta123
hauta123 commented 22 days ago
https://mdisk.me/convertor/427x240/xoypnz

@Mustafatarakci
Mustafatarakci commented 8 days ago
#1453#

@Worldpeace666666
 Worldpeace666666 commented 8 days ago
我沒訂閱。謝謝告知☺

取得 Android 版 Outlook<https://aka.ms/AAb9ysg>
…
@Miladew Miladew mentioned this issue 7 days ago
Duplicate of #11 #338
 Closed
@saiterralogic06

Leave a comment
No file chosen
Attach files by dragging & dropping, selecting or pasting them.
Remember, contributions to this repository should follow its contributing guidelines.
Assignees
No one assigned
Labels
big/crazy ideas
enhancement
Projects
None yet
Milestone
No milestone
Development
No branches or pull requests

Notifications
Customize
You’re not receiving notifications from this thread.
147 participants
@jlord
@davepeary220
@rodneyrb147
@minge007
@mjd0
@LuckyRabbitFeet
@Angel1976
and others
Footer
© 2022 GitHub, Inc.
Footer navigation
Terms
Privacy
Security
Status
Docs
Contact GitHub
Pricing
API
Training
Blog
About
You have no unread notifications

Heh, was confused.  Surprise ping!


[BUG] The Activate Page no longer works

OK, I'm following the instructions, just spent roughly $140, and the activate page doesn't work: https://www.palomachain.com/purchase/activate/

Fixed with #2207


Exclude pages for a given language

Thank you for this plugin!
I am testing things out but I cannot find the proper way to do what I need here. Thank you for your help.
Is your feature request related to a problem? Please describe.
I have pages that I don't want to generate for a given language.
I tried this way, but I get an error at build time:
{
  locale: `af-ZA`,
  prefix: `af`,
  slugs: {
    '/page-1': '/bladsy-1',
    '/page-2': false, // also tried `''` but it just changes the URL
  },
  messages: afMessages,
}

The error I get is TypeError: The "path" argument must be of type string. Received type boolean ( #0 5.155   false).
In dev mode, Gatsby doesn't seem to complain though. And the plugin responds well because it then hides the locale in the language switcher when on this page.
Describe the solution you'd like
It would be great if setting a path to false in a language would result in the page not being generated for this locale.
Additional context

Thank you for using this plugin and raising the request. I've added a new option pageBlacklist, which lets you prevent the creation of pages for given paths and languages.
      {
        locale: `de-CH`,
        prefix: `de`,
        slugs: {
          '/products': '/produkte',
          '/products#donut-filled-with-jam': '/produkte#berliner',
          '/services/software-development': '/dienstleistungen/softwareentwicklung'
        },
        pageBlacklist: ['/do-not-translate-to-german'], // If there is a page with the a given path it won't be translated
        messages: {
          "language": "Deutsch"
        },
        ```

I'm happy to hear, if this works out for you! Cheers

Thank you very much @openscript ! Sounds perfect!
I'll try that out when I get some time and will let you know 😃


gNOI-6.1 refactor proposal

use gNOI File Put to push a file to the dut
use gNOI File Stat to verify presence of file
remove the requirement for altering the behavior of the test based on encryption
update readme with according information
change testbed file in metadata.textproto to TESTBED_DUT

resolves #3053
"This code is a Contribution to the OpenConfig Feature Profiles project ("Work") made under the Google Software Grant and Corporate Contributor License Agreement ("CLA") and governed by the Apache License 2.0. No other rights or licenses in or to any of Nokia's intellectual property are granted for any other purpose. This code is provided on an "as is" basis without any warranties of any kind."

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls


Support Following Include Macros

This tool is a wonderful extension for developing with Asciidoc, especially in situations where you need to be offline. However, there is one thing I find cumbersome. Currently, if a rendered Asciidoc file includes other Asciidoc files via include::someFile.adoc[], those are not rendered as part of the document, but represented as a clickable link to the secondary file.
This makes it difficult to preview documents when the text content is broken down into smaller modules (with each in their own file).

A related issue: if the files included contain custom attribute definitions, those attributes are not expanded since the document where they were defined isn't rendered.

The behavior your observing happens when the safe mode is set to "secure". If you set the safe mode on the options page to something other than "secure", then includes will work. I recommend setting it to "unsafe" as the safety checks are not really relevant in the context.

Ah! So much better. @mojavelinux, I owe you a beer.

\o/

Hi guys,
for me include macros are not working in chrome. I'm trying to include a source code file inside code blocks. I set safe mode to unsafe in chrome extension options, here is output in chrome and firefox (which works):

I also tried to set safe mode inside adoc file but didnt worked, here is the adoc file:
:icons: font
:toc: right
:numbered:
:sectanchors:
:source-highlighter: coderay
:safe-mode-0:
:safe: 0
= Document Title
Doc Writer<EMAIL_ADDRESS>v1.0, 2013-01-01: Initial version
http://asciidoc.org[AsciiDoc^] is a lightweight markup language.
This is the optional preamble (an untitled section body), useful for
writing simple sectionless documents consisting only of a preamble.
NOTE: The abstract, preface, appendix, bibliography, glossary and
index section titles are significant (specialsections).
== Section zero
== First section
Document sections start at level 1 and can nest four levels deep.

Item 1
Item 2

[source,java,linenums]
public class HelloAsccidoctor {
public void aMethod(String param) {
System.out.println("Hello Asciidoctor");
}
}
include::hello.java[]
== Second section
Document sections start at level 1 and can nest four levels deep.

Item 1
Item 2

[source,ruby]
puts 'Hello, World!'
=== Sub section
Document sections start at level 1 and can nest four levels deep.

Item 1
Item 2

[source,ruby]
puts 'Hello, World!'

@rmpestano You are saying that this is working in the Firefox Addon but not in the Chrome Extension ?
And the source of your document is:
[source,java,linenums]
----
public class HelloAsccidoctor {
  public void aMethod(String param) {
    System.out.println("Hello Asciidoctor");
  }
}

include::hello.java[]
----

I think there a bug on the options page in the Chrome Extension. Could you try to set Safe mode to unsafe again and click the save button ? Then reload your file.

Hi @Mogztter,
yes, the problem is with include macro inside code block, in chrome it renders that "link".
I have set unsafe and saved in extension options, I also restarted the browser and checked the unsafe is set. The problem persists.

You are using link:: or include:: ?
The following is working with the Chrome Extension (and at least server safe mode):
= Test

[source,java,linenums]
----
public class HelloAsccidoctor {
  public void aMethod(String param) {
    System.out.println("Hello Asciidoctor");
  }
}

include::hello.java[]
----

.hello.java
public static void hello() {
  System.out.println("Hello");
}

Hi again,
i'm using include, tried your sample and it still doesn't, take a look at my config:

I'm using the zip from here: https://github.com/asciidoctor/asciidoctor-chrome-extension/releases/tag/v<IP_ADDRESS>

Oww it works on safe mode here too, sorry for the confusion but I thought it should work in UNSAFE mode. thanks for your time

It should work with unsafe too. But safe is actually the recommended setting. unsafe actually causes problems in Asciidoctor.js because we haven't enabled all the features that unsafe tries to use. The documentation should recommend "safe" I think.


[2.0.6] Problem with completion "from" path

With TypeScript Version:  2.0.6 (same problem with 2.0.3) when I open completion for "from":
import {} from " // Ctrl+Space to open completion

I have this error:
TypeError: Cannot read property 'length' of undefined
    at getCompletionEntriesFromTypings (...\node_modules\typescript\lib\tsserver.js:48159:79)
    at getCompletionEntriesForNonRelativeModules (...\node_modules\typescript\lib\tsserver.js:48038:17)
    at getStringLiteralCompletionEntriesFromModuleNames (...\node_modules\typescript\lib\tsserver.js:47929:31)
    at getStringLiteralCompletionEntries (...\node_modules\typescript\lib\tsserver.js:47833:28)
    at Object.getCompletionsAtPosition (...\node_modules\typescript\lib\tsserver.js:47717:24)
    at IOSession.Session.getCompletions (...\node_modules\typescript\lib\tsserver.js:54911:64)
    at Session.handlers.ts.createMap._a.(anonymous function) (...\\node_modules\typescript\lib\tsserver.js:54156:61)
    at IOSession.Session.executeCommand (...\node_modules\typescript\lib\tsserver.js:55223:28)
    at IOSession.Session.onMessage (...\node_modules\typescript\lib\tsserver.js:55243:35)
    at Interface.<anonymous> (...\node_modules\typescript\lib\tsserver.js:56300:27)

With TypeScript 2.1.0-dev.20161012, I have not this error.
More, when I write with TypeScript Version:  2.0.6
import {} from "./ // Ctrl+Space to open completion

completion shows only directory entries and not script files.
With TypeScript 2.1.0-dev.20161012,  completion shows directory entries and script files both.

@angelozerr can you give tonight's drop a try?

@mhegazy you wish that I test with TypeScript that I install with "npm install typescript@next", is that?

Yes. That would be appreciated.

@mhegazy worls like a charm with 2.2.0-dev.20161120. Completion shows files and directories both:

thanks for confirming.


Unresolved type in Goland go code

Description of the bug:
For some reason the types from external packages don't resolve. The code I'm working on compiles just fine.

The external code shows up as flat individual files in Goland.

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I'll try to do this later today.
Which Intellij IDE are you using? Please provide the specific version.
Goland 2022.2
What programming languages and tools are you using? Please provide specific versions.
golang
What Bazel plugin version are you using?
2<IP_ADDRESS>.1-api-version-222
Have you found anything relevant by searching the web?
No
Any other information, logs, or outputs that you want to share?
No response

It also happens in intellij

I figured out the issue. Goland by default doesn't provide code insight for files bigger than 2MB. The type that wasn't resolving was from a file that was 6MB. I had to raise the limit according to this SO question. I can close this out. Thanks!


fix storage gap for EIP712Upgradeable

Actually this PR is addressing inconsistency, not a bug.
Adjusts the gap in the EIP712Upgradeable contract to reserve storage for up to 50.
The variables _HASHED_NAME and _HASHED_VERSION use a total of 2 storage slots. To reserve storage for 50 slots like other Upgradeable contracts, the gap should be reduced to 48.

Fixes #????

PR Checklist

[x] Tests
[x] Documentation
[x] Changeset entry (run npx changeset add)

This is by design for backwards compatibility, due to an oversight in the initial releases this contract has always had 52 slots total:
https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable/blob/e3baf02f69405476107df1707721d4e28cbe3299/contracts/utils/cryptography/EIP712Upgradeable.sol#L33


Include backtick to surroundingPairs

Thanks for the PR! But we following this config with https://github.com/microsoft/vscode/blob/24e73f3551a59166d34d0deecbb623c24af67645/extensions/html/language-configuration.json#L19-L26, could you explain what problem will be resolve with adding "`"?

.vue files have <script> section and bits of javascript in directives and :attributes="".
Backticks\Template literals are working just fine inside vue templates, it is kinda surprising, to select some text, hit ` and watch it disappear.
try rewriting
<th class="table-header">

to
<th :class="`table-header-colspan-${computedColspan}`"

Add { "open": "`", "close": "`" } to vue-language-configuration.json cannot resolve this problem to me.
If you typing ` at <th :class=" | "> it will be working, because the embedded language is typescript so it's already using javascript-language-configuration.json.

But with <th :class="|"> it's not working anyway, it may a intentional vscode behavior.

I think I found the reason, it may need to fix in https://github.com/johnsoncodehk/volar/blob/master/extensions/vscode-vue-language-features/syntaxes/vue.tmLanguage.json, nice to have a issue for tracking.


Fix Typos and Minor Grammatical Errors in Documentation

This pull request addresses a few typos and grammatical inconsistencies in the README documentation to improve clarity and readability. The changes include:

Corrected "different different" to "different" for clarity in describing node arrangements.
Fixed the typo "AgnetKit" to "AgentKit" in the "Citing AgentKit" section.
Changed "evoke" to "invoke" to use the correct term for starting the command line interface (CLI).

These minor fixes enhance the overall quality of the documentation.

hey @Holmeswww, please review these changes and merge this.


Purple Emoji is different based on the system's emoji pack

The heart emoji from the footer is different on all tested devices.

To fix this problem the emoji should be stored as a PNG or SVG and loaded on the right spot instead of the heart emoji 💜

 - purple heart icon


Error compilation NVCC for TF 2.5 from source using Clang-11 for Debian 11

Hi all!
System information

OS Platform and Distribution: Linux Debian 11, kernel 5.10.0-8-amd64
Mobile device : No
TensorFlow installed from: try compile from source
TensorFlow version: 2.5.1
Python version: 3.8.12
Installed using: virtualenv
Bazel version: 3.7.2
Compiler version: Debian Clang version 11.1.0-++20210804031632+1fdec59bffc1-1~exp1~20210804132251.11 installed from https://apt.llvm.org/
CUDA version:  Driver Version: 460.32.03  /  CUDA Version: 11.2 installed from run
cuDNN version: Cudnn_v<IP_ADDRESS>
GPU model and memory: GeForce GTX 1050 2GB RAM single
NCCL:  2.8.4, for CUDA 11.2, February 03,2021
RAM:  16GB

Problem description
Permanently  when I trying  compile TF 2.5.1 from source using Clang-11 raising  error compilation.
Before compile TF 2.5.1 with Clang-11 I successful compiled  TF 2.5.1  for verification  from source using standard  Debian gcc compiler version 10.2.1-6 - it was compiled without problems but with a permanenty  warning in the IPython console
: I tensorflow / compiler / mlir / mlir_graph_optimization_pass.cc: 176] None of the MLIR Optimization Passes are enabled
1. Configure TF 2.5.1  screen  before compilation:
tf251) mvg@debian:~/tensorflow$ ./configure
You have bazel 3.7.2 installed.
Please specify the location of python. [Default is /home/mvg/tf251/bin/python3]:

Found possible Python library paths:
  /home/mvg/tf251/lib/python3.8/site-packages
Please input the desired Python library path to use.  Default is [/home/mvg/tf251/lib/python3.8/site-packages]

Do you wish to build TensorFlow with ROCm support? [y/N]: n
No ROCm support will be enabled for TensorFlow.

Do you wish to build TensorFlow with CUDA support? [y/N]: y
CUDA support will be enabled for TensorFlow.

Do you wish to build TensorFlow with TensorRT support? [y/N]: n
No TensorRT support will be enabled for TensorFlow.

Found CUDA 11.2 in:
    /usr/local/cuda-11.2/targets/x86_64-linux/lib
    /usr/local/cuda-11.2/targets/x86_64-linux/include
Found cuDNN 8 in:
    /usr/local/cuda-11.2/targets/x86_64-linux/lib
    /usr/local/cuda-11.2/targets/x86_64-linux/include

Please specify a list of comma-separated CUDA compute capabilities you want to build with.
You can find the compute capability of your device at: https://developer.nvidia.com/cuda-gpus. Each capability can be specified as "x.y" or "compute_xy" to include both virtual and binary GPU code, or as "sm_xy" to only include the binary code.
Please note that each additional compute capability significantly increases your build time and binary size, and that TensorFlow only supports compute capabilities >= 3.5 [Default is: 6.1]:

Do you want to use clang as CUDA compiler? [y/N]: y
Clang will be used as CUDA compiler.

Do you wish to download a fresh release of clang? (Experimental) [y/N]: n
Clang will not be downloaded.

Please specify which clang should be used as device and host compiler. [Default is /usr/lib/llvm-11/bin/clang]:

Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is -Wno-sign-compare]:

Would you like to interactively configure ./WORKSPACE for Android builds? [y/N]: n
Not configuring the WORKSPACE for Android builds.

Preconfigured Bazel build configs. You can use any of the below by adding "--config=<>" to your build command. See .bazelrc for more details.
	--config=mkl         	# Build with MKL support.
	--config=mkl_aarch64 	# Build with oneDNN and Compute Library for the Arm Architecture (ACL).
	--config=monolithic  	# Config for mostly static monolithic build.
	--config=numa        	# Build with NUMA support.
	--config=dynamic_kernels	# (Experimental) Build kernels into separate shared objects.
	--config=v2          	# Build TensorFlow 2.x instead of 1.x.
Preconfigured Bazel build configs to DISABLE default on features:
	--config=noaws       	# Disable AWS S3 filesystem support.
	--config=nogcp       	# Disable GCP support.
	--config=nohdfs      	# Disable HDFS support.
	--config=nonccl      	# Disable NVIDIA NCCL support.
Configuration finished

2. Run compilation command and their console output:
(tf251) mvg@debian:~/tensorflow$ bazel build --config=opt --copt=-march=native --copt=-Wno-sign-compare \
--copt=-mavx --copt=-mfma  --copt=-mfma4  \
--copt=-msse4.1 --copt=-msse4.2 --jobs=4 //tensorflow/tools/pip_package:build_pip_package --verbose_failures
WARNING: The following configs were expanded more than once: [cuda_clang, cuda]. For repeatable flags, repeats are counted twice and may lead to unexpected behavior.
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=80
INFO: Reading rc options for 'build' from /home/mvg/tensorflow/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /home/mvg/tensorflow/.bazelrc:
  'build' options: --define framework_shared_object=true --java_toolchain=@tf_toolchains//toolchains/java:tf_java_toolchain --host_java_toolchain=@tf_toolchains//toolchains/java:tf_java_toolchain --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --noincompatible_prohibit_aapt1 --enable_platform_specific_config --define=with_xla_support=true --config=short_logs --config=v2
INFO: Reading rc options for 'build' from /home/mvg/tensorflow/.tf_configure.bazelrc:
  'build' options: --action_env PYTHON_BIN_PATH=/home/mvg/tf251/bin/python3 --action_env PYTHON_LIB_PATH=/home/mvg/tf251/lib/python3.8/site-packages --python_path=/home/mvg/tf251/bin/python3 --action_env CUDA_TOOLKIT_PATH=/usr/local/cuda-11.2 --action_env TF_CUDA_COMPUTE_CAPABILITIES=6.1 --config=cuda_clang --action_env CLANG_CUDA_COMPILER_PATH=/usr/lib/llvm-11/bin/clang --config=cuda_clang
INFO: Found applicable config definition build:short_logs in file /home/mvg/tensorflow/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file /home/mvg/tensorflow/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:cuda_clang in file /home/mvg/tensorflow/.bazelrc: --config=cuda --repo_env TF_CUDA_CLANG=1 --@local_config_cuda//:cuda_compiler=clang
INFO: Found applicable config definition build:cuda in file /home/mvg/tensorflow/.bazelrc: --repo_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --@local_config_cuda//:enable_cuda
INFO: Found applicable config definition build:cuda_clang in file /home/mvg/tensorflow/.bazelrc: --config=cuda --repo_env TF_CUDA_CLANG=1 --@local_config_cuda//:cuda_compiler=clang
INFO: Found applicable config definition build:cuda in file /home/mvg/tensorflow/.bazelrc: --repo_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --@local_config_cuda//:enable_cuda
INFO: Found applicable config definition build:opt in file /home/mvg/tensorflow/.tf_configure.bazelrc: --copt=-Wno-sign-compare --host_copt=-Wno-sign-compare
INFO: Found applicable config definition build:linux in file /home/mvg/tensorflow/.bazelrc: --copt=-w --host_copt=-w --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --define=PROTOBUF_INCLUDE_PATH=$(PREFIX)/include --cxxopt=-std=c++14 --host_cxxopt=-std=c++14 --config=dynamic_kernels
INFO: Found applicable config definition build:dynamic_kernels in file /home/mvg/tensorflow/.bazelrc: --define=dynamic_loaded_kernels=true --copt=-DAUTOLOAD_DYNAMIC_KERNELS
INFO: Build option --action_env has changed, discarding analysis cache.
INFO: Analyzed target //tensorflow/tools/pip_package:build_pip_package (426 packages loaded, 36834 targets configured).
INFO: Found 1 target...

3. Error log:
ERROR: /home/mvg/.cache/bazel/_bazel_mvg/196ae8161680bc9ae310a4b3aee3f0d6/external/nccl_archive/BUILD.bazel:54:17: C++ compilation of rule '@nccl_archive//:device_lib' failed (Exit 1): clang failed: error executing command
  (cd /home/mvg/.cache/bazel/_bazel_mvg/196ae8161680bc9ae310a4b3aee3f0d6/execroot/org_tensorflow && \
  exec env - \
    PATH=/home/mvg/tf251/bin:/usr/lib/llvm-11/bin:/usr/local/nccl_2.8.4/lib:/usr/local/nccl_2.8.4/lib/pkgconfig:/usr/local/cuda-11.2/nsight-systems-2020.4.3/bin/:/usr/local/cuda-11.2/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games \
    PWD=/proc/self/cwd \
  /usr/lib/llvm-11/bin/clang -MD -MF bazel-out/host/bin/external/nccl_archive/_objs/device_lib/min_f16_reduce_scatter.cu.d '-frandom-seed=bazel-out/host/bin/external/nccl_archive/_objs/device_lib/min_f16_reduce_scatter.cu.o' -iquote external/nccl_archive -iquote bazel-out/host/bin/external/nccl_archive -iquote external/local_config_cuda -iquote bazel-out/host/bin/external/local_config_cuda -Ibazel-out/host/bin/external/nccl_archive/_virtual_includes/device_hdrs -Ibazel-out/host/bin/external/nccl_archive/_virtual_includes/include_hdrs -Ibazel-out/host/bin/external/local_config_cuda/cuda/_virtual_includes/cuda_headers_virtual -Ibazel-out/host/bin/external/nccl_archive/_virtual_includes/src_hdrs -isystem external/local_config_cuda/cuda -isystem bazel-out/host/bin/external/local_config_cuda/cuda -isystem external/local_config_cuda/cuda/cuda/include -isystem bazel-out/host/bin/external/local_config_cuda/cuda/cuda/include -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -fPIE -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -Wall -Wno-invalid-partial-specialization -fno-omit-frame-pointer -no-canonical-prefixes -DNDEBUG -g0 -O2 -ffunction-sections -fdata-sections '--cuda-path=/usr/local/cuda-11.2' -g0 -w -Wno-sign-compare -g0 '-std=c++14' -x cuda '-DGOOGLE_CUDA=1' '-Xcuda-fatbinary=--compress-all' '--no-cuda-include-ptx=all' '--cuda-include-ptx=sm_61' '--cuda-gpu-arch=sm_61' -O3 -fcuda-rdc -Xcuda-ptxas '-maxrregcount=96' -c bazel-out/host/bin/external/nccl_archive/src/collectives/device/min_f16_reduce_scatter.cu.cc -o bazel-out/host/bin/external/nccl_archive/_objs/device_lib/min_f16_reduce_scatter.cu.o)
Execution platform: @local_execution_config_platform//:platform
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:432:
In file included from /usr/include/strings.h:144:
/usr/include/x86_64-linux-gnu/bits/strings_fortified.h:23:8: error: exception specification in declaration does not match previous declaration
__NTH (bcopy (const void *__src, void *__dest, size_t __len))
       ^
/usr/include/strings.h:38:13: note: previous declaration is here
extern void bcopy (const void *__src, void *__dest, size_t __n)
            ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:432:
In file included from /usr/include/strings.h:144:
/usr/include/x86_64-linux-gnu/bits/strings_fortified.h:29:8: error: exception specification in declaration does not match previous declaration
__NTH (bzero (void *__dest, size_t __len))
       ^
/usr/include/strings.h:42:13: note: previous declaration is here
extern void bzero (void *__s, size_t __n) __THROW __nonnull ((1));
            ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:31:8: error: exception specification in declaration does not match previous declaration
__NTH (memcpy (void *__restrict __dest, const void *__restrict __src,
       ^
/usr/include/string.h:43:14: note: previous declaration is here
extern void *memcpy (void *__restrict __dest, const void *__restrict __src,
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:38:8: error: exception specification in declaration does not match previous declaration
__NTH (memmove (void *__dest, const void *__src, size_t __len))
       ^
/usr/include/string.h:47:14: note: previous declaration is here
extern void *memmove (void *__dest, const void *__src, size_t __n)
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:45:8: error: exception specification in declaration does not match previous declaration
__NTH (mempcpy (void *__restrict __dest, const void *__restrict __src,
       ^
/usr/include/string.h:378:14: note: previous declaration is here
extern void *mempcpy (void *__restrict __dest,
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:59:8: error: exception specification in declaration does not match previous declaration
__NTH (memset (void *__dest, int __ch, size_t __len))
       ^
/usr/include/string.h:61:14: note: previous declaration is here
extern void *memset (void *__s, int __c, size_t __n) __THROW __nonnull ((1));
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:81:8: error: exception specification in declaration does not match previous declaration
__NTH (explicit_bzero (void *__dest, size_t __len))
       ^
/usr/include/string.h:436:13: note: previous declaration is here
extern void explicit_bzero (void *__s, size_t __n) __THROW __nonnull ((1));
            ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:88:8: error: exception specification in declaration does not match previous declaration
__NTH (strcpy (char *__restrict __dest, const char *__restrict __src))
       ^
/usr/include/string.h:122:14: note: previous declaration is here
extern char *strcpy (char *__restrict __dest, const char *__restrict __src)
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:95:8: error: exception specification in declaration does not match previous declaration
__NTH (stpcpy (char *__restrict __dest, const char *__restrict __src))
       ^
/usr/include/string.h:452:14: note: previous declaration is here
extern char *stpcpy (char *__restrict __dest, const char *__restrict __src)
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:103:8: error: exception specification in declaration does not match previous declaration
__NTH (strncpy (char *__restrict __dest, const char *__restrict __src,
       ^
/usr/include/string.h:125:14: note: previous declaration is here
extern char *strncpy (char *__restrict __dest,
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:116:8: error: exception specification in declaration does not match previous declaration
__NTH (stpncpy (char *__dest, const char *__src, size_t __n))
       ^
/usr/include/string.h:460:14: note: previous declaration is here
extern char *stpncpy (char *__restrict __dest,
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:126:8: error: exception specification in declaration does not match previous declaration
__NTH (strcat (char *__restrict __dest, const char *__restrict __src))
       ^
/usr/include/string.h:130:14: note: previous declaration is here
extern char *strcat (char *__restrict __dest, const char *__restrict __src)
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:133:8: error: exception specification in declaration does not match previous declaration
__NTH (strncat (char *__restrict __dest, const char *__restrict __src,
       ^
/usr/include/string.h:133:14: note: previous declaration is here
extern char *strncat (char *__restrict __dest, const char *__restrict __src,
             ^
13 errors generated when compiling for sm_61.

FAILED: Build did NOT complete successfully

4. About compability CUDA  v11.2.2 and Clang-11
1. Official documentation in the partition Installation Guide Linux Clang-11 support  declared.
2.  file in the CUDA directory  '/usr/local/cuda-11-2/include/crt/host_config.h` explicitly next stated:
#if defined(__clang__) && !defined(__ibmxl_vrm__) && !defined(__ICC) && !defined(__HORIZON__) && !defined(__APPLE__)
#if (__clang_major__ >= 12) || (__clang_major__ < 3) || ((__clang_major__ == 3) &&  (__clang_minor__ < 3))
#error -- unsupported clang version! clang version must be less than 12 and greater than 3.2 . The nvcc flag '-allow-unsupported-compiler' can be used to override this version check; however, using an unsupported host compiler may cause compilation failure or incorrect run time execution. Use at your own risk.

File  /home/mvg/tensorflow/.bazelrc contains pointer for in the next tensofrlow distibution in the partiotion Remote build execution options (only configured to work with TF team projects for now.) :
build:rbe_linux_cuda_clang_base --crosstool_top="@ubuntu18.04-clang_manylinux2010-cuda11.2-cudnn8.1-tensorrt7.2_config_cuda//crosstool:toolchain"
I have installed Clang-11 - hence following the infomation above I should compile normally TF 2.5.1 from source with Clang-11.

5. The appointment of a responsible specialist for this ticket
I ask for the solution of this problem to appoint responsible Artem Belevich Artem-B and not to football me like balls for various person who haven't knoweledge in the subject and turn the solution into an eternal groundhog day - since every time I retell a human problem, after a while it disappears, a new person appears , I will explain again, the opat disappeared and so on ad infinitum.
Best regards, Vadim Maklakov.
P.S. Information for Artem-B - I think that   problem is somehow related to nccl. It doesn't matter if nccl is installed or not - it is constantly mentioned in the compilation error log.
P.P.S /home/mvg/tf251/bin: - path for Python 3.8.12 virtual environment whe installef all required modules how in this instruction.

Hi all!
Uninstall nccl and try compile without nccl with thist command remain setting above:
(tf251) mvg@debian:~/tensorflow$  bazel build --config=opt --copt=-march=native --copt=-Wno-sign-compare \
--copt=-mavx --copt=-mfma  --copt=-mfma4  \
--copt=-msse4.1 --copt=-msse4.2 --jobs=4 //tensorflow/tools/pip_package:build_pip_package --verbose_failures
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
WARNING: The following configs were expanded more than once: [cuda_clang, cuda]. For repeatable flags, repeats are counted twice and may lead to unexpected behavior.
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=80
INFO: Reading rc options for 'build' from /home/mvg/tensorflow/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /home/mvg/tensorflow/.bazelrc:
  'build' options: --define framework_shared_object=true --java_toolchain=@tf_toolchains//toolchains/java:tf_java_toolchain --host_java_toolchain=@tf_toolchains//toolchains/java:tf_java_toolchain --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --noincompatible_prohibit_aapt1 --enable_platform_specific_config --define=with_xla_support=true --config=short_logs --config=v2
INFO: Reading rc options for 'build' from /home/mvg/tensorflow/.tf_configure.bazelrc:
  'build' options: --action_env PYTHON_BIN_PATH=/home/mvg/tf251/bin/python3 --action_env PYTHON_LIB_PATH=/home/mvg/tf251/lib/python3.8/site-packages --python_path=/home/mvg/tf251/bin/python3 --action_env CUDA_TOOLKIT_PATH=/usr/local/cuda-11.2 --action_env TF_CUDA_COMPUTE_CAPABILITIES=6.1 --config=cuda_clang --action_env CLANG_CUDA_COMPILER_PATH=/usr/lib/llvm-11/bin/clang --config=cuda_clang
INFO: Found applicable config definition build:short_logs in file /home/mvg/tensorflow/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file /home/mvg/tensorflow/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:cuda_clang in file /home/mvg/tensorflow/.bazelrc: --config=cuda --repo_env TF_CUDA_CLANG=1 --@local_config_cuda//:cuda_compiler=clang
INFO: Found applicable config definition build:cuda in file /home/mvg/tensorflow/.bazelrc: --repo_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --@local_config_cuda//:enable_cuda
INFO: Found applicable config definition build:cuda_clang in file /home/mvg/tensorflow/.bazelrc: --config=cuda --repo_env TF_CUDA_CLANG=1 --@local_config_cuda//:cuda_compiler=clang
INFO: Found applicable config definition build:cuda in file /home/mvg/tensorflow/.bazelrc: --repo_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --@local_config_cuda//:enable_cuda
INFO: Found applicable config definition build:opt in file /home/mvg/tensorflow/.tf_configure.bazelrc: --copt=-Wno-sign-compare --host_copt=-Wno-sign-compare
INFO: Found applicable config definition build:linux in file /home/mvg/tensorflow/.bazelrc: --copt=-w --host_copt=-w --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --define=PROTOBUF_INCLUDE_PATH=$(PREFIX)/include --cxxopt=-std=c++14 --host_cxxopt=-std=c++14 --config=dynamic_kernels
INFO: Found applicable config definition build:dynamic_kernels in file /home/mvg/tensorflow/.bazelrc: --define=dynamic_loaded_kernels=true --copt=-DAUTOLOAD_DYNAMIC_KERNELS
DEBUG: Rule 'io_bazel_rules_docker' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1556410077 -0400"
DEBUG: Repository io_bazel_rules_docker instantiated at:
  /home/mvg/tensorflow/WORKSPACE:23:14: in <toplevel>
  /home/mvg/tensorflow/tensorflow/workspace0.bzl:105:34: in workspace
  /home/mvg/.cache/bazel/_bazel_mvg/196ae8161680bc9ae310a4b3aee3f0d6/external/bazel_toolchains/repositories/repositories.bzl:37:23: in repositories
Repository rule git_repository defined at:
  /home/mvg/.cache/bazel/_bazel_mvg/196ae8161680bc9ae310a4b3aee3f0d6/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in <toplevel>
INFO: Analyzed target //tensorflow/tools/pip_package:build_pip_package (426 packages loaded, 36834 targets configured).

and get this error log with contain pointers to nccl:
ERROR: /home/mvg/.cache/bazel/_bazel_mvg/196ae8161680bc9ae310a4b3aee3f0d6/external/nccl_archive/BUILD.bazel:54:17: C++ compilation of rule '@nccl_archive//:device_lib' failed (Exit 1): clang failed: error executing command
  (cd /home/mvg/.cache/bazel/_bazel_mvg/196ae8161680bc9ae310a4b3aee3f0d6/execroot/org_tensorflow && \
  exec env - \
    CLANG_CUDA_COMPILER_PATH=/usr/lib/llvm-11/bin/clang \
    CUDA_TOOLKIT_PATH=/usr/local/cuda-11.2 \
    PATH=/home/mvg/tf251/bin:/usr/lib/llvm-11/bin:/usr/local/cuda-11.2/nsight-systems-2020.4.3/bin/:/usr/local/cuda-11.2/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games \
    PWD=/proc/self/cwd \
    PYTHON_BIN_PATH=/home/mvg/tf251/bin/python3 \
    PYTHON_LIB_PATH=/home/mvg/tf251/lib/python3.8/site-packages \
    TF2_BEHAVIOR=1 \
    TF_CUDA_COMPUTE_CAPABILITIES=6.1 \
  /usr/lib/llvm-11/bin/clang -MD -MF bazel-out/k8-opt/bin/external/nccl_archive/_objs/device_lib/functions.cu.d '-frandom-seed=bazel-out/k8-opt/bin/external/nccl_archive/_objs/device_lib/functions.cu.o' -iquote external/nccl_archive -iquote bazel-out/k8-opt/bin/external/nccl_archive -iquote external/local_config_cuda -iquote bazel-out/k8-opt/bin/external/local_config_cuda -Ibazel-out/k8-opt/bin/external/nccl_archive/_virtual_includes/device_hdrs -Ibazel-out/k8-opt/bin/external/nccl_archive/_virtual_includes/include_hdrs -Ibazel-out/k8-opt/bin/external/local_config_cuda/cuda/_virtual_includes/cuda_headers_virtual -Ibazel-out/k8-opt/bin/external/nccl_archive/_virtual_includes/src_hdrs -isystem external/local_config_cuda/cuda -isystem bazel-out/k8-opt/bin/external/local_config_cuda/cuda -isystem external/local_config_cuda/cuda/cuda/include -isystem bazel-out/k8-opt/bin/external/local_config_cuda/cuda/cuda/include -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -fPIE -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -Wall -Wno-invalid-partial-specialization -fno-omit-frame-pointer -no-canonical-prefixes -DNDEBUG -g0 -O2 -ffunction-sections -fdata-sections '--cuda-path=/usr/local/cuda-11.2' -w -DAUTOLOAD_DYNAMIC_KERNELS -Wno-sign-compare '-march=native' -Wno-sign-compare -mavx -mfma -mfma4 -msse4.1 -msse4.2 '-std=c++14' -x cuda '-DGOOGLE_CUDA=1' '-Xcuda-fatbinary=--compress-all' '--no-cuda-include-ptx=all' '--cuda-include-ptx=sm_61' '--cuda-gpu-arch=sm_61' -O3 -fcuda-rdc -Xcuda-ptxas '-maxrregcount=96' -c external/nccl_archive/src/collectives/device/functions.cu.cc -o bazel-out/k8-opt/bin/external/nccl_archive/_objs/device_lib/functions.cu.o)
Execution platform: @local_execution_config_platform//:platform
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:432:
In file included from /usr/include/strings.h:144:
/usr/include/x86_64-linux-gnu/bits/strings_fortified.h:23:8: error: exception specification in declaration does not match previous declaration
__NTH (bcopy (const void *__src, void *__dest, size_t __len))
       ^
/usr/include/strings.h:38:13: note: previous declaration is here
extern void bcopy (const void *__src, void *__dest, size_t __n)
            ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:432:
In file included from /usr/include/strings.h:144:
/usr/include/x86_64-linux-gnu/bits/strings_fortified.h:29:8: error: exception specification in declaration does not match previous declaration
__NTH (bzero (void *__dest, size_t __len))
       ^
/usr/include/strings.h:42:13: note: previous declaration is here
extern void bzero (void *__s, size_t __n) __THROW __nonnull ((1));
            ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:31:8: error: exception specification in declaration does not match previous declaration
__NTH (memcpy (void *__restrict __dest, const void *__restrict __src,
       ^
/usr/include/string.h:43:14: note: previous declaration is here
extern void *memcpy (void *__restrict __dest, const void *__restrict __src,
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:38:8: error: exception specification in declaration does not match previous declaration
__NTH (memmove (void *__dest, const void *__src, size_t __len))
       ^
/usr/include/string.h:47:14: note: previous declaration is here
extern void *memmove (void *__dest, const void *__src, size_t __n)
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:45:8: error: exception specification in declaration does not match previous declaration
__NTH (mempcpy (void *__restrict __dest, const void *__restrict __src,
       ^
/usr/include/string.h:378:14: note: previous declaration is here
extern void *mempcpy (void *__restrict __dest,
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:59:8: error: exception specification in declaration does not match previous declaration
__NTH (memset (void *__dest, int __ch, size_t __len))
       ^
/usr/include/string.h:61:14: note: previous declaration is here
extern void *memset (void *__s, int __c, size_t __n) __THROW __nonnull ((1));
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:81:8: error: exception specification in declaration does not match previous declaration
__NTH (explicit_bzero (void *__dest, size_t __len))
       ^
/usr/include/string.h:436:13: note: previous declaration is here
extern void explicit_bzero (void *__s, size_t __n) __THROW __nonnull ((1));
            ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:88:8: error: exception specification in declaration does not match previous declaration
__NTH (strcpy (char *__restrict __dest, const char *__restrict __src))
       ^
/usr/include/string.h:122:14: note: previous declaration is here
extern char *strcpy (char *__restrict __dest, const char *__restrict __src)
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:95:8: error: exception specification in declaration does not match previous declaration
__NTH (stpcpy (char *__restrict __dest, const char *__restrict __src))
       ^
/usr/include/string.h:452:14: note: previous declaration is here
extern char *stpcpy (char *__restrict __dest, const char *__restrict __src)
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:103:8: error: exception specification in declaration does not match previous declaration
__NTH (strncpy (char *__restrict __dest, const char *__restrict __src,
       ^
/usr/include/string.h:125:14: note: previous declaration is here
extern char *strncpy (char *__restrict __dest,
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:116:8: error: exception specification in declaration does not match previous declaration
__NTH (stpncpy (char *__dest, const char *__src, size_t __n))
       ^
/usr/include/string.h:460:14: note: previous declaration is here
extern char *stpncpy (char *__restrict __dest,
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:126:8: error: exception specification in declaration does not match previous declaration
__NTH (strcat (char *__restrict __dest, const char *__restrict __src))
       ^
/usr/include/string.h:130:14: note: previous declaration is here
extern char *strcat (char *__restrict __dest, const char *__restrict __src)
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:133:8: error: exception specification in declaration does not match previous declaration
__NTH (strncat (char *__restrict __dest, const char *__restrict __src,
       ^
/usr/include/string.h:133:14: note: previous declaration is here
extern char *strncat (char *__restrict __dest, const char *__restrict __src,
             ^
13 errors generated when compiling for sm_61.
Target //tensorflow/tools/pip_package:build_pip_package failed to build
INFO: Elapsed time: 889.248s, Critical Path: 59.41s
INFO: 11776 processes: 8278 internal, 3498 local.

Check --copt=-D_FORTIFY_SOURCE=0
with running  this command:

(tf251) mvg@debian:~/tensorflow$ bazel build --config=opt --copt=-march=native --copt=-Wno-sign-compare \
--copt=-mavx --copt=-mfma  --copt=-mfma4  \
--copt=-msse4.1 --copt=-msse4.2 --copt=-D_FORTIFY_SOURCE=0 --jobs=4 //tensorflow/tools/pip_package:build_pip_package --verbose_failures

output for command above:
Starting local Bazel server and connecting to it...
WARNING: The following configs were expanded more than once: [cuda_clang, cuda]. For repeatable flags, repeats are counted twice and may lead to unexpected behavior.
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=80
INFO: Reading rc options for 'build' from /home/mvg/tensorflow/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /home/mvg/tensorflow/.bazelrc:
  'build' options: --define framework_shared_object=true --java_toolchain=@tf_toolchains//toolchains/java:tf_java_toolchain --host_java_toolchain=@tf_toolchains//toolchains/java:tf_java_toolchain --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --noincompatible_prohibit_aapt1 --enable_platform_specific_config --define=with_xla_support=true --config=short_logs --config=v2
INFO: Reading rc options for 'build' from /home/mvg/tensorflow/.tf_configure.bazelrc:
  'build' options: --action_env PYTHON_BIN_PATH=/home/mvg/tf251/bin/python3 --action_env PYTHON_LIB_PATH=/home/mvg/tf251/lib/python3.8/site-packages --python_path=/home/mvg/tf251/bin/python3 --action_env CUDA_TOOLKIT_PATH=/usr/local/cuda-11.2 --action_env TF_CUDA_COMPUTE_CAPABILITIES=6.1 --config=cuda_clang --action_env CLANG_CUDA_COMPILER_PATH=/usr/lib/llvm-11/bin/clang --config=cuda_clang
INFO: Found applicable config definition build:short_logs in file /home/mvg/tensorflow/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file /home/mvg/tensorflow/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:cuda_clang in file /home/mvg/tensorflow/.bazelrc: --config=cuda --repo_env TF_CUDA_CLANG=1 --@local_config_cuda//:cuda_compiler=clang
INFO: Found applicable config definition build:cuda in file /home/mvg/tensorflow/.bazelrc: --repo_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --@local_config_cuda//:enable_cuda
INFO: Found applicable config definition build:cuda_clang in file /home/mvg/tensorflow/.bazelrc: --config=cuda --repo_env TF_CUDA_CLANG=1 --@local_config_cuda//:cuda_compiler=clang
INFO: Found applicable config definition build:cuda in file /home/mvg/tensorflow/.bazelrc: --repo_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --@local_config_cuda//:enable_cuda
INFO: Found applicable config definition build:opt in file /home/mvg/tensorflow/.tf_configure.bazelrc: --copt=-Wno-sign-compare --host_copt=-Wno-sign-compare
INFO: Found applicable config definition build:linux in file /home/mvg/tensorflow/.bazelrc: --copt=-w --host_copt=-w --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --define=PROTOBUF_INCLUDE_PATH=$(PREFIX)/include --cxxopt=-std=c++14 --host_cxxopt=-std=c++14 --config=dynamic_kernels
INFO: Found applicable config definition build:dynamic_kernels in file /home/mvg/tensorflow/.bazelrc: --define=dynamic_loaded_kernels=true --copt=-DAUTOLOAD_DYNAMIC_KERNELS
INFO: Analyzed target //tensorflow/tools/pip_package:build_pip_package (426 packages loaded, 36834 targets configured).
INFO: Found 1 target...

compilation failed with next messages:
ERROR: /home/mvg/.cache/bazel/_bazel_mvg/196ae8161680bc9ae310a4b3aee3f0d6/external/nccl_archive/BUILD.bazel:54:17: C++ compilation of rule '@nccl_archive//:device_lib' failed (Exit 1): clang failed: error executing command
  (cd /home/mvg/.cache/bazel/_bazel_mvg/196ae8161680bc9ae310a4b3aee3f0d6/execroot/org_tensorflow && \
  exec env - \
    PATH=/home/mvg/tf251/bin:/usr/lib/llvm-11/bin:/usr/local/cuda-11.2/nsight-systems-2020.4.3/bin/:/usr/local/cuda-11.2/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games \
    PWD=/proc/self/cwd \
  /usr/lib/llvm-11/bin/clang -MD -MF bazel-out/host/bin/external/nccl_archive/_objs/device_lib/max_f64_sendrecv.cu.pic.d '-frandom-seed=bazel-out/host/bin/external/nccl_archive/_objs/device_lib/max_f64_sendrecv.cu.pic.o' -iquote external/nccl_archive -iquote bazel-out/host/bin/external/nccl_archive -iquote external/local_config_cuda -iquote bazel-out/host/bin/external/local_config_cuda -Ibazel-out/host/bin/external/nccl_archive/_virtual_includes/device_hdrs -Ibazel-out/host/bin/external/nccl_archive/_virtual_includes/include_hdrs -Ibazel-out/host/bin/external/local_config_cuda/cuda/_virtual_includes/cuda_headers_virtual -Ibazel-out/host/bin/external/nccl_archive/_virtual_includes/src_hdrs -isystem external/local_config_cuda/cuda -isystem bazel-out/host/bin/external/local_config_cuda/cuda -isystem external/local_config_cuda/cuda/cuda/include -isystem bazel-out/host/bin/external/local_config_cuda/cuda/cuda/include -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -fPIC -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -Wall -Wno-invalid-partial-specialization -fno-omit-frame-pointer -no-canonical-prefixes -DNDEBUG -g0 -O2 -ffunction-sections -fdata-sections '--cuda-path=/usr/local/cuda-11.2' -g0 -w -Wno-sign-compare -g0 '-std=c++14' -x cuda '-DGOOGLE_CUDA=1' '-Xcuda-fatbinary=--compress-all' '--no-cuda-include-ptx=all' '--cuda-include-ptx=sm_61' '--cuda-gpu-arch=sm_61' -O3 -fcuda-rdc -Xcuda-ptxas '-maxrregcount=96' -c bazel-out/host/bin/external/nccl_archive/src/collectives/device/max_f64_sendrecv.cu.cc -o bazel-out/host/bin/external/nccl_archive/_objs/device_lib/max_f64_sendrecv.cu.pic.o)
Execution platform: @local_execution_config_platform//:platform
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:432:
In file included from /usr/include/strings.h:144:
/usr/include/x86_64-linux-gnu/bits/strings_fortified.h:23:8: error: exception specification in declaration does not match previous declaration
__NTH (bcopy (const void *__src, void *__dest, size_t __len))
       ^
/usr/include/strings.h:38:13: note: previous declaration is here
extern void bcopy (const void *__src, void *__dest, size_t __n)
            ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:432:
In file included from /usr/include/strings.h:144:
/usr/include/x86_64-linux-gnu/bits/strings_fortified.h:29:8: error: exception specification in declaration does not match previous declaration
__NTH (bzero (void *__dest, size_t __len))
       ^
/usr/include/strings.h:42:13: note: previous declaration is here
extern void bzero (void *__s, size_t __n) __THROW __nonnull ((1));
            ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:31:8: error: exception specification in declaration does not match previous declaration
__NTH (memcpy (void *__restrict __dest, const void *__restrict __src,
       ^
/usr/include/string.h:43:14: note: previous declaration is here
extern void *memcpy (void *__restrict __dest, const void *__restrict __src,
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:38:8: error: exception specification in declaration does not match previous declaration
__NTH (memmove (void *__dest, const void *__src, size_t __len))
       ^
/usr/include/string.h:47:14: note: previous declaration is here
extern void *memmove (void *__dest, const void *__src, size_t __n)
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:45:8: error: exception specification in declaration does not match previous declaration
__NTH (mempcpy (void *__restrict __dest, const void *__restrict __src,
       ^
/usr/include/string.h:378:14: note: previous declaration is here
extern void *mempcpy (void *__restrict __dest,
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:59:8: error: exception specification in declaration does not match previous declaration
__NTH (memset (void *__dest, int __ch, size_t __len))
       ^
/usr/include/string.h:61:14: note: previous declaration is here
extern void *memset (void *__s, int __c, size_t __n) __THROW __nonnull ((1));
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:81:8: error: exception specification in declaration does not match previous declaration
__NTH (explicit_bzero (void *__dest, size_t __len))
       ^
/usr/include/string.h:436:13: note: previous declaration is here
extern void explicit_bzero (void *__s, size_t __n) __THROW __nonnull ((1));
            ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:88:8: error: exception specification in declaration does not match previous declaration
__NTH (strcpy (char *__restrict __dest, const char *__restrict __src))
       ^
/usr/include/string.h:122:14: note: previous declaration is here
extern char *strcpy (char *__restrict __dest, const char *__restrict __src)
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:95:8: error: exception specification in declaration does not match previous declaration
__NTH (stpcpy (char *__restrict __dest, const char *__restrict __src))
       ^
/usr/include/string.h:452:14: note: previous declaration is here
extern char *stpcpy (char *__restrict __dest, const char *__restrict __src)
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:103:8: error: exception specification in declaration does not match previous declaration
__NTH (strncpy (char *__restrict __dest, const char *__restrict __src,
       ^
/usr/include/string.h:125:14: note: previous declaration is here
extern char *strncpy (char *__restrict __dest,
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:116:8: error: exception specification in declaration does not match previous declaration
__NTH (stpncpy (char *__dest, const char *__src, size_t __n))
       ^
/usr/include/string.h:460:14: note: previous declaration is here
extern char *stpncpy (char *__restrict __dest,
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:126:8: error: exception specification in declaration does not match previous declaration
__NTH (strcat (char *__restrict __dest, const char *__restrict __src))
       ^
/usr/include/string.h:130:14: note: previous declaration is here
extern char *strcat (char *__restrict __dest, const char *__restrict __src)
             ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-11/lib/clang/11.1.0/include/__clang_cuda_runtime_wrapper.h:211:
In file included from /usr/include/string.h:495:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:133:8: error: exception specification in declaration does not match previous declaration
__NTH (strncat (char *__restrict __dest, const char *__restrict __src,
       ^
/usr/include/string.h:133:14: note: previous declaration is here
extern char *strncat (char *__restrict __dest, const char *__restrict __src,
             ^
13 errors generated when compiling for sm_61.
Target //tensorflow/tools/pip_package:build_pip_package failed to build
ERROR: /home/mvg/tensorflow/tensorflow/lite/python/BUILD:59:10 C++ compilation of rule '@nccl_archive//:device_lib' failed (Exit 1): clang failed: error executing command
  (cd /home/mvg/.cache/bazel/_bazel_mvg/196ae8161680bc9ae310a4b3aee3f0d6/execroot/org_tensorflow && \
  exec env - \
    PATH=/home/mvg/tf251/bin:/usr/lib/llvm-11/bin:/usr/local/cuda-11.2/nsight-systems-2020.4.3/bin/:/usr/local/cuda-11.2/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games \
    PWD=/proc/self/cwd \
  /usr/lib/llvm-11/bin/clang -MD -MF bazel-out/host/bin/external/nccl_archive/_objs/device_lib/max_f64_sendrecv.cu.pic.d '-frandom-seed=bazel-out/host/bin/external/nccl_archive/_objs/device_lib/max_f64_sendrecv.cu.pic.o' -iquote external/nccl_archive -iquote bazel-out/host/bin/external/nccl_archive -iquote external/local_config_cuda -iquote bazel-out/host/bin/external/local_config_cuda -Ibazel-out/host/bin/external/nccl_archive/_virtual_includes/device_hdrs -Ibazel-out/host/bin/external/nccl_archive/_virtual_includes/include_hdrs -Ibazel-out/host/bin/external/local_config_cuda/cuda/_virtual_includes/cuda_headers_virtual -Ibazel-out/host/bin/external/nccl_archive/_virtual_includes/src_hdrs -isystem external/local_config_cuda/cuda -isystem bazel-out/host/bin/external/local_config_cuda/cuda -isystem external/local_config_cuda/cuda/cuda/include -isystem bazel-out/host/bin/external/local_config_cuda/cuda/cuda/include -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -fPIC -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -Wall -Wno-invalid-partial-specialization -fno-omit-frame-pointer -no-canonical-prefixes -DNDEBUG -g0 -O2 -ffunction-sections -fdata-sections '--cuda-path=/usr/local/cuda-11.2' -g0 -w -Wno-sign-compare -g0 '-std=c++14' -x cuda '-DGOOGLE_CUDA=1' '-Xcuda-fatbinary=--compress-all' '--no-cuda-include-ptx=all' '--cuda-include-ptx=sm_61' '--cuda-gpu-arch=sm_61' -O3 -fcuda-rdc -Xcuda-ptxas '-maxrregcount=96' -c bazel-out/host/bin/external/nccl_archive/src/collectives/device/max_f64_sendrecv.cu.cc -o bazel-out/host/bin/external/nccl_archive/_objs/device_lib/max_f64_sendrecv.cu.pic.o)
Execution platform: @local_execution_config_platform//:platform
INFO: Elapsed time: 1133.000s, Critical Path: 65.14s
INFO: 3000 processes: 8 internal, 2992 local.
FAILED: Build did NOT complete successfully

Well, one way or another something ends up running with _FORTIFY_SOURCES defined.
I can't tell you why that happens. The fix has already been committed to clang, so if you were to use a nightly build (not sure if it has NVPTX back-end enabled, though) or build it yourself from sources, that should get you past this build issue.

@Hi, Artem-B
Version of my installed clang-11  from https://apt.llvm.org/ bellow:
"""
mvg@debian:~$ sudo dpkg-query -l clang-11
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version                                                     >
+++-==============-============================================================>
ii  clang-11       1:11.1.0~++20210804031632+1fdec59bffc1-1~exp1~20210804132251>
"""
Patch fixed this trouble added in the end of September this year
How I understand I must have to build all LLVM-11 bundle from source?

clang-11 or any other release currently out there will not have the changes I've committed just few days ago.
You choices are:

move to linux distro which does not enable fortified sources by default, or
figure out how to disable fortified sources on your Debian machine, or
build and use your own clang from sources, or
try using nightly snapshot of prebuilt packages from https://apt.llvm.org/, or
apply the following diff to clang headers you have installed on your machine : https://github.com/llvm/llvm-project/commit/29e00b29f76adb15a51c1ccd6c1fdb6fce5f4d7b.diff

Let's keep things simple. If you need it to work just on your machine, just find __clang_cuda_runtime_wrapper.h installed  by clang and make this change there:
diff --git a/clang/lib/Headers/__clang_cuda_runtime_wrapper.h b/clang/lib/Headers/__clang_cuda_runtime_wrapper.h
index 98fb561ca51b5..33aa25fb2d73c 100644
--- a/clang/lib/Headers/__clang_cuda_runtime_wrapper.h
+++ b/clang/lib/Headers/__clang_cuda_runtime_wrapper.h
@@ -41,6 +41,7 @@
 #include <cmath>
 #include <cstdlib>
 #include <stdlib.h>
+#include <string.h>
 #undef __CUDACC__

 // Preserve common macros that will be changed below by us or by CUDA
@@ -205,11 +206,6 @@ inline __host__ double __signbitd(double x) {
 #endif

 #if CUDA_VERSION >= 9000
-// CUDA-9.2 needs host-side memcpy for some host functions in
-// device_functions.hpp
-#if CUDA_VERSION >= 9020
-#include <string.h>
-#endif
 #include "crt/math_functions.hpp"
 #else
 #include "math_functions.hpp"

If you need the build to work for everyone on Debian, you'll either need to wait until fixed clang package is available.
They do seem to have recent enough versions already: https://packages.debian.org/sid/clang-14
I do not know how to turn off fortified compilation on Debian, so I can't help you there beyond what you've already tried.


Fix map validator for basemaps

This is an incomplete solution. Just consider the following example:
{
    "layers": [
        {
            "id": "globals",
            "options": {
                "cartocss": "@landmass_fill: #0e0e0e;",
                "cartocss_version": "2.3.0",
                "sql": "SELECT null::geometry AS the_geom_webmercator LIMIT 0"
            },
            "type": "mapnik"
        },
        {
            "id": "borders",
            "options": {
                "cartocss": "#background { polygon-fill: @landmass_fill; }",
                "cartocss_version": "2.3.0",
                "sql": "SELECT the_geom_webmercator FROM world_borders"
            },
            "type": "mapnik"
        },
        {
            "id": "capitals",
            "options": {
                "cartocss": "#labels { text-face-name: \"INVALID FONT\"; }",
                "cartocss_version": "2.1.1",
                "sql": "SELECT * FROM world_capitals"
            },
            "type": "mapnik"
        }
    ]
}

The "INVALID FONT" in "id": "capitals" will raise a general error, but later when validating layers individually the error presented to the client will be related to "id": "borders" as it won't be able to resolve the @landmass_fill global variable.

How could we resolve @landmass_fill global variable to validate one layer??


[FLINK-5441] [table] Directly allow SQL queries on a Table

Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your pull request. For more information and/or questions please refer to the How To Contribute guide.
In addition to going through the list, please provide a meaningful description of your changes.

[x] General

The pull request references the related JIRA issue ("[FLINK-XXX] Jira title text")
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message (including the JIRA id)

[ ] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[x] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

This PR allows calling SQL directly on a table :
myTable.sql("SELECT a, b, c FROM _ WHERE d = 12")

Hi @KurtYoung , thank your for reviewing. I'm not sure about that. Do you mean omitting the "FROM" syntax ?  But it will be hard to validate SQL syntax. Because the query can follow a WHERE clause or JOIN/UNION with other tables.  For example, it's wired and hard to validate the query like this:
mytable.sql("SELECT * WHERE a > 13 UNION SELECT * FROM TABLE_B")

I think allowing query on other tables is fine here.  What do you think ?

I still think this is weird. Currently all API from Table is somehow act on the table object, just like a normal OOP program. After introducing sql method to Table, it can do something completely unrelated to the current object.

@KurtYoung I agree that this syntax can be misused like table.sql("SELECT * FROM otherTable"). But right now it is very inconvenient to always register a table first, especially if you want to define multiple queries subsequently.
We could also think about env.sql("SELECT * FROM _ JOIN _", table, otherTable). Other suggestions are very welcome.
Another idea that just came to my mind. We could also use the toString method of a Table. This method could implicitly register the Table under a unique name and return that. Then we could support env.sql(s"SELECT * FROM $table JOIN $otherTable").

What about using slf4j syntax env.sql("SELECT * FROM {} JOIN {}", table1, table2) ?

Hi, I like @twalthr's suggestion to use env.sql("SELECT * FROM _ JOIN _", table, otherTable).
I'd also be fine with slf4j syntax as @wuchong proposed.
What do you think @KurtYoung?

Hi @fhueske, both solutions are fine with me.

What do you think about my solution of env.sql(s"SELECT * FROM $table JOIN $otherTable")? It would be much more readable.

Hi @twalthr , the env.sql(s"SELECT * FROM $table JOIN $otherTable") is a nice way. But how to handle the table's table name and register it to env ?

Agreed, for Scala the inlined variant looks really good. Like @wuchong,
I'm curious how we can intercept the inlined string arguments. Do you know how to do that @twalthr?

We don't have to intercept inline string arguments. We just have to make sure that Table.toString() returns an unique identifier that the method previously registered in it's table environment. Table.toString() should then always return the same identifier.

@twalthr do you mean register table in his toString method ?

It's for this reason that I think that Flink needs a "source catalog"
somewhere..
On 22 February 2017 at 09:35, twalthr<EMAIL_ADDRESS>wrote:

We don't have to intercept inline string arguments. We just have to make
sure that Table.toString() returns an unique identifier that the method
previously registered in it's table environment. Table.toString() should
then always return the same identifier.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/flink/pull/3107#issuecomment-281603488, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADmeJYvF3DJZFWQ2oYcR_mUgC-2WFll8ks5re_NdgaJpZM4Lhz5Y
.

An external catalog would not help in this case. It's actually quite the opposite. The issue is to run a SQL query on an ad-hoc table without the need to explicitly add it to a catalog.

@wuchong if toString is called for the first time. It calls tEnv.registerTableInternal(this) which uses an atomic counter and generates a unique identifier such as UnnamedTable$232. This identifier is returned and saved in the table. Every further call of toString return this identifier.

Thank you @twalthr , I like the idea. So Java users can also use env.sql("SELECT * FROM " + table1 + " JOIN " + table2) as a shortcut. What do you think @fhueske ?

Hmm, I think registering tables in toString() (which IMO should be free of side effects) is not very clean, but I have to admit that the API looks good. So, I would be OK doing this like that.
Would we also take care to unregister the tables after the query was optimized?

Do we have to take care of unregistering the tables? Right now fromDataSet/fromDataStream do also not unregister their unique names.

But what's the point of keeping tables that will never be used again?

I think the point is that we don't know if the table will ever be used again. If we unregister them after optimization, we can not have multiple toDataStream() calls for one table.

Yes, you are right. Forgot that we lazily translate the plans. :-/
Let's keep the tables then.

@wuchong any plans to update this PR?

@twalthr Yes,  I will update it in these days.

@twalthr  I have updated this PR regarding to the idea you proposed that env.sql(s"SELECT * FROM $table JOIN $otherTable")

Thanks for the quick update @wuchong. The code looks good to merge. Can you add some documentation to the SQL section?

updated the documentation.

Thanks @wuchong. Will merge this.


vmware Fusion

Hi There,
Is there a easyway to use the vagrant file with VMware Fusion?

You can modify the vagrant file to work with VMware fusion but the underlying vagrant images need to support VMware as a provider. Short answer: no.


Interpolation error for sqrt(x)

Graph of square root function has some bump next to zero x. See attached image.

I am also attaching source code.
code.zip
To reproduce run:
$ python3 -m manim nerav.py WarpSquare -s
I tabulated function call (also attached) and there's gap between 0.0002-0.08.
tabulated.zip
Therefore I conclude next to 0, between 0.0002777777777777778 and 0.08305555555555555 function is interpolated instead of tabulated.

This issue should now be fixed.


[feature] Logging to file

Expected Behavior
In config, you can set logging on or off. And then it's logging to folder "logs", with filename "logs-$NAME-YYYY-MM-DD-HH-MM-SS".
Actual Behavior
Bot isn't logging.
Steps to Reproduce
...
Other Information
OS: all
Git Commit: all

Would be a great feature, because you don't need to use screen and you are able to review what happened.

When I use screen and it crashed I don't know what happend because only what I see is "screen is terminating"... And I don't have idea how to have screen output to file and posibility to attach to screen.

pretty simple to do this with bash:
# run bot, output to console AND log.txt file
python pokecli.py | tee log.txt

pretty simple to do this with bash:

run bot, output to console AND log.txt file
python pokecli.py | tee log.txt
Of course, but you also need run it in screen. If you run it normally it won't work. But now I have method to do that, but I think bot should have this feature.

A logging option would be really nice! any plans to do this?


codegen from palette json

rather than writing all the colours out by hand we should have a way to generate the relevant python code automatically using the latest palette json.

Just saw this issue again, I've just (finally!) updated the palette JSON to that more detailed format we talked about a while ago: https://github.com/catppuccin/palette/blob/v1.0.1/palette.json

lovely stuff, thanks for the update. i shall roll this into the next version and get rid of the custom hsla methods i added!


HAWKULAR-614 Web socket closing because of no auth. Also resourceId c…

…hanged to resourcePath. Adding additional typesafety around Resource List.

Wow, finally. After 4 builds!


papermc: allow version override

Description of changes
The version of papermc cannot easily be overridden because the version and fetchurl expressions are in a let .. in clause. This PR makes them parameters in a recursive attrset for easier overriding.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1768


[TensorIR][M2a] CacheRead/Write

This PR is part of the TensorIR upstreaming effort (#7527), which adds a schedule primitive: cache_read/write.
CC: @junrushao1994 @vinx13 @MasterJH5574 @comaniac @jcf94
Co-authored-by: Bohan Hou<EMAIL_ADDRESS>Co-authored-by: Ruihang Lai<EMAIL_ADDRESS>Co-authored-by: Hongyi Jin<EMAIL_ADDRESS>Co-authored-by: Wuwei Lin<EMAIL_ADDRESS>Co-authored-by: Junru Shao<EMAIL_ADDRESS>

Will review tomorrow. Thanks a lot!

Thanks @Hzfengsy for the PR! I did a pass on the schedule primitive and it overall looks pretty good. I nitpicked quite a bit and let's get it merged quickly after those comments are addressed. Thanks a lot!


CUDAOptimizer fails with large block sizes

cuda.py stores the following global parameters:
threads_per_item_pair = 8
item_pairs_per_block = 8
If you change these to 128x8, 256x4, or 512x2, static_correctness test breaks with incorrect dividers. Additionally, with other tests, even though the dividers may be correct, the variance is wrong.

reproduce with:
cuda.py:
threads_per_item_pair = 256
item_pairs_per_block = 4
test_histoptimizer.py:
items = [5, 1, 6, 8, 5]
num_buckets = 3


Migrate devices

Good morning,
Is there a way to migrate devices from ZNDMWG02LM to the new ZNDMWG04LM without losing the configuration in HA and Xiaomi Home?
Thanks.

You don't need migrate BLE/Mesh devices. But you need to repair all Zigbee devices. There is no other way.


Added BowerInstall command to install bower components of modules

Thanks for the feedback, I'll take a look at it tomorrow.

Is this ready to merge, @nWidart? :smile:


[vcpkg-cmake] Fix vcpkg_copy_pdbs false alarm

Describe the pull request

What does your PR fix?
Fixes #...

Which triplets are supported/not supported? Have you updated the CI baseline?
<all / linux, windows, ...>, <Yes/No>

Does your PR follow the maintainer guide?
Your answer

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
<Yes / I am still working on this PR>

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

The baseline issue would be fixed by https://github.com/microsoft/vcpkg/pull/19361.

/azp run

I think something breaks the pipeline test.

I think something breaks the pipeline test.

The CI errors seem unrelated.

ptex:x86-windows had issues before, cf. https://github.com/microsoft/vcpkg/pull/18961. Maybe it isn't triggered often enough in CI.
The rbdl-orb problems are not original build errors (no failure logs!), but duplicate installations with port rbdl. Interesting: They happened only x86-compatible windows builds other native x64-windows.

@dg0yt, thanks for your comments! the baseline issue would be fixed by https://github.com/microsoft/vcpkg/pull/19453

@dan-shaw, could you help merge this PR?


added mean hit position in CRTVD::Trigger class

Small update from what was presented here : https://indico.fnal.gov/event/61808/
CRTVD::Trigger now store the mean spatial position of hit positions in CRT modules, possibly allowing for angle calculation of tracks triggering coincidences.

Hi Thomas,
Starting from ~v09_78_06 tag, one gets :
Failed to parse the configuration file '/cvmfs/dune.opensciencegrid.org/products/dune/dunesw/v09_78_06d00/fcl/protodunevd_refactored_detsim.fcl' with exception
---- search_path BEGIN
  Can't find file "CRTVD.fcl"
---- search_path END

I indeed don't find your CRTVD.fcl file on /cvmfs:
ls /cvmfs/dune.opensciencegrid.org/products/dune/duneprototypes/v09_78_06d00/fcl/CRT*.fcl
/cvmfs/dune.opensciencegrid.org/products/dune/duneprototypes/v09_78_06d00/fcl/CRT.fcl

ls /cvmfs/dune.opensciencegrid.org/products/dune/duneprototypes/v09_79_00d02/fcl/CRT*.fcl
/cvmfs/dune.opensciencegrid.org/products/dune/duneprototypes/v09_79_00d02/fcl/CRT.fcl

So the current ProtoDUNE-VD simulation chain seems to be broken and I'm surprised you get it working.
Am I missing something?

Hi Yoann, thanks for pointing this out. I had forgotten to add the command line 'install_fhicl()' in the CMakeList.txt. I added it later "https://github.com/DUNE/duneprototypes/blob/23b869bef2b3df2c4115ac444096e8ebde6f57ee/duneprototypes/Protodune/vd/CRT/CMakeLists.txt#L22".
You said you are running with dunesw v09_78_06 ?
In more recent I think the problem should not appear

As I said, in v09_79_00d02 it does not seem to be there as well:
ls /cvmfs/dune.opensciencegrid.org/products/dune/duneprototypes/v09_79_00d02/fcl/CRT*.fcl
/cvmfs/dune.opensciencegrid.org/products/dune/duneprototypes/v09_79_00d02/fcl/CRT.fcl

Can you double check?

Ok I investigated a bit more. The first pull request I made was accepeted 20th october (previous friday), so the changes are currently in develop but I'm not sure there has been a new release since. Indeed I had a look at duneprototype v09_79_00d02 and indeed there is not sign of the repository I created in duneprototype/
https://github.com/DUNE/duneprototypes/tree/v09_79_00d02/duneprototypes/Protodune.
I remember now that it's what I meant when on slide 7 of my talk (https://indico.fnal.gov/event/61808/) I said that these changes would be available in versions strictly greater than v09_79_00d02. I guess that's the part you were missing :)

Got it. Thanks for this feedback! I indeed forgot about your statement.
We may want to have a testing routine for ProtoDUNE-VD sim/reco chain to point out such issues right ahead and do not remain over multiple versions. I'll contact the FNAL IT team.

What's the status on this PR?  Is it all set to go in?  I realize it's been a while waiting for review.

Should we proceed with this PR?

Hi @tomjunk
Let me try it first as it starts to be an old development by Thomas who left DUNE few months ago.

@YoannKermaidic let me know when you can try this out.  Let's get it into the release in a future week.

Closed at request of developers


pickZones ZoneRedundant Resource Documentation update

Hi,
Can we update documentation for the pickZones ARM template function? pickZones does not work for Zone Redundant (resources that are deployed across multiple availability zones for resiliency) resource deployments. As a result if pickZones is used with say CosmosDB pickZones("Microsoft.DocumentDB", "databaseAccounts", "westus"), it returns empty zones array (since this resource is not zonal), even though CosmosDB can be created ZR in Westus.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0551fca9-d710-15d1-9141-baf2121a4ab1
Version Independent ID: cc554f24-a13d-d3ab-a3c6-c610f4d0b461
Content: Template functions - resources - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/template-functions-resource.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

@shae-hurst Thanks for your comment. We will review the issue and get back to you shortly.

@shae-hurst Thanks for valuable feedback. I have tested from my end and seems there is issue with the function.
Assigning to content author @mumian for doc-enhancement

Yeah, I am internal w/ Azure Global feel free to ping me. I want to try to update this documentation because there is confusion around use of this function.

@shae-hurst - thank you for your comments. I have updated the article.
#please-close


Other factions have guns (and other tech) for sale and as rewards.

According to Will on Discord, "So I'm not entirely sure if this is a known issue but with the base third age mod (Not unlimited) whilst I can't access tech beyond medieval other factions can (not the mod factions though) and I can trade for guns and such and I even get the friendly AI quest, I have tried reinstalling the mod  I've even tried turning off every mod bar Hugslibs and JecsTools and this still happens"

Will's log.
https://git.io/fxMra


Trim strings before converting to a number

Not a big deal for Convert (it anyway has null checks), but may save a lot of headache when converting such strings as "9999 ", especially when they come as objects from external systems.

@alniks thanks for suggestion!


KAFKA-12343: Handle exceptions better in TopicAdmin, including UnsupportedVersionException

Refactored the KafkaBasedLog logic to read end offsets into a separate method to make it easier to test. Also changed the TopicAdmin.endOffsets method to throw the original UnsupportedVersionException, LeaderNotAvailableException, and TimeoutException rather than wrapping, to better conform with the consumer method and how the KafkaBasedLog retries those exceptions.
Added new tests to verify various scenarios and errors.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Thanks for the quick review, @chia7712. I've incorporated several of your suggestions, and added comments/responses on the others.
BTW, a run of the relevant Connect distributed system tests passed with this branch: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/4390/

@chia7712, for what it's worth, I still think your #10152 PR is still an important fix.

@chia7712 and @kkonstantine: thanks for the reviews. I've incorporated your recent feedback, with the exception of @kkonstantine's suggestion to move the topicAdminSupplier.get() from start() into the constructor, as mentioned above in one of the comment threads.
Please take another look. Thanks!


Merge tag 1.1.5 into master

release was pushed but it looks like master is still behind.

Done, tks!