text:
2023.05.20: sphinx warnings reference target not found

What's happening?
First of all currently it is not possible to use straight sphinx-build command to build documentation out of source tree

+ /usr/bin/sphinx-build -n -T -b man docs build/sphinx/man
Running Sphinx v6.2.1

Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/sphinx/registry.py", line 442, in load_extension
    mod = import_module(extname)
  File "/usr/lib64/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 961, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'furo'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/sphinx/cmd/build.py", line 280, in build_main
    app = Sphinx(args.sourcedir, args.confdir, args.outputdir,
  File "/usr/lib/python3.8/site-packages/sphinx/application.py", line 229, in __init__
    self.setup_extension(extension)
  File "/usr/lib/python3.8/site-packages/sphinx/application.py", line 404, in setup_extension
    self.registry.load_extension(self, extname)
  File "/usr/lib/python3.8/site-packages/sphinx/registry.py", line 445, in load_extension
    raise ExtensionError(__('Could not import extension %s') % extname,
sphinx.errors.ExtensionError: Could not import extension furo.sphinxext (exception: No module named 'furo')

Extension error:
Could not import extension furo.sphinxext (exception: No module named 'furo')

This can be fixed by patch like below:
--- a/docs/conf.py
+++ b/docs/conf.py
@@ -7,6 +7,8 @@
 import sys
 from typing import Any, Dict

+sys.path.insert(0, os.path.abspath("../src"))
+
 # add the demo python code to the path, so that it can be used to demonstrate
 # source links
 sys.path.append(os.path.abspath("./kitchen-sink/demo_py"))

This patch bases on sphinx example copy.py https://www.sphinx-doc.org/en/master/usage/configuration.html#example-of-configuration-file
Than .. on building my packages I'm using sphinx-build command with -n switch which shows warmings about missing references. These are not critical issues.
Here is the output with warnings:

+ /usr/bin/sphinx-build -n -T -b man docs build/sphinx/man
Running Sphinx v6.2.1
making output directory... done
loading intersphinx inventory from https://docs.python.org/3/objects.inv...
loading intersphinx inventory from https://www.sphinx-doc.org/en/master/objects.inv...
myst v1.0.0: MdParserConfig(commonmark_only=False, gfm_only=False, enable_extensions={'colon_fence', 'deflist'}, disable_syntax=[], all_links_external=False, url_schemes=('http', 'https', 'mailto', 'ftp'), ref_domains=None, fence_as_directive=set(), number_code_blocks=[], title_to_header=False, heading_anchors=3, heading_slug_func=None, html_meta={}, footnote_transition=True, words_per_minute=200, substitutions={}, linkify_fuzzy_links=True, dmath_allow_labels=True, dmath_allow_space=True, dmath_allow_digits=True, dmath_double_inline=False, update_mathjax=True, mathjax_classes='tex2jax_process|mathjax_process|math|output_area', enable_checkboxes=False, suppress_warnings=[], highlight_code_blocks=True)
building [mo]: targets for 0 po files that are out of date
writing output...
building [man]: all manpages
updating environment: [new config] 44 added, 0 changed, 0 removed
reading sources... [100%] stability
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
writing... python-furo.3 { quickstart customisation/index customisation/logo customisation/announcement customisation/edit-button customisation/colors customisation/fonts customisation/footer customisation/landing-page customisation/sidebar customisation/sidebar-title customisation/toc customisation/injecting reference/index reference/text-formatting reference/admonitions reference/api reference/code-blocks reference/hyperlinks reference/images reference/lists reference/tables reference/tabs recommendations contributing/index contributing/workflow contributing/internals contributing/design kitchen-sink/index kitchen-sink/admonitions kitchen-sink/api kitchen-sink/blocks kitchen-sink/generic kitchen-sink/images kitchen-sink/lists kitchen-sink/really-long kitchen-sink/sphinx-design kitchen-sink/structure kitchen-sink/tables kitchen-sink/typography stability changelog license } /usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:20: WARNING: py:class reference target not found: urllib3.exceptions.MaxRetryError
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:1: WARNING: py:class reference target not found: iterable
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:83: WARNING: py:attr reference target not found: Retry.DEFAULT_ALLOWED_METHODS
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:1: WARNING: py:class reference target not found: iterable
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:108: WARNING: py:func reference target not found: sleep
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:108: WARNING: py:attr reference target not found: Retry.DEFAULT_BACKOFF_MAX
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:123: WARNING: py:meth reference target not found: Retry.increment
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:123: WARNING: py:class reference target not found: RequestHistory
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:128: WARNING: py:attr reference target not found: Retry.RETRY_AFTER_STATUS_CODES
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:1: WARNING: py:class reference target not found: iterable
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry.increment:5: WARNING: py:class reference target not found: urllib3.response.HTTPResponse
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.clone:7: WARNING: py:class reference target not found: Timeout
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.Timeout.connect_timeout:7: WARNING: py:attr reference target not found: Timeout.DEFAULT_TIMEOUT
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.from_float:3: WARNING: py:class reference target not found: Timeout
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.from_float:1: WARNING: py:class reference target not found: integer
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.from_float:1: WARNING: py:class reference target not found: sentinel default object
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.from_float:11: WARNING: py:class reference target not found: Timeout
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.get_connect_duration:1: WARNING: py:meth reference target not found: start_connect
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.get_connect_duration:1: WARNING: py:exc reference target not found: urllib3.exceptions.TimeoutStateError
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.Timeout.read_timeout:6: WARNING: py:exc reference target not found: urllib3.exceptions.TimeoutStateError
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.Timeout.read_timeout:12: WARNING: py:attr reference target not found: Timeout.DEFAULT_TIMEOUT
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.Timeout.read_timeout:1: WARNING: py:exc reference target not found: urllib3.exceptions.TimeoutStateError
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.Timeout.read_timeout:13: WARNING: py:meth reference target not found: start_connect
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.start_connect:1: WARNING: py:exc reference target not found: urllib3.exceptions.TimeoutStateError
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:20: WARNING: py:class reference target not found: urllib3.exceptions.MaxRetryError
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:1: WARNING: py:class reference target not found: iterable
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:83: WARNING: py:attr reference target not found: Retry.DEFAULT_ALLOWED_METHODS
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:1: WARNING: py:class reference target not found: iterable
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:108: WARNING: py:func reference target not found: sleep
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:108: WARNING: py:attr reference target not found: Retry.DEFAULT_BACKOFF_MAX
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:123: WARNING: py:meth reference target not found: Retry.increment
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:123: WARNING: py:class reference target not found: RequestHistory
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:128: WARNING: py:attr reference target not found: Retry.RETRY_AFTER_STATUS_CODES
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry:1: WARNING: py:class reference target not found: iterable
/usr/lib/python3.8/site-packages/urllib3/util/retry.py:docstring of urllib3.util.retry.Retry.increment:5: WARNING: py:class reference target not found: urllib3.response.HTTPResponse
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.clone:7: WARNING: py:class reference target not found: Timeout
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.Timeout.connect_timeout:7: WARNING: py:attr reference target not found: Timeout.DEFAULT_TIMEOUT
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.from_float:3: WARNING: py:class reference target not found: Timeout
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.from_float:1: WARNING: py:class reference target not found: integer
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.from_float:1: WARNING: py:class reference target not found: sentinel default object
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.from_float:11: WARNING: py:class reference target not found: Timeout
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.get_connect_duration:1: WARNING: py:meth reference target not found: start_connect
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.get_connect_duration:1: WARNING: py:exc reference target not found: urllib3.exceptions.TimeoutStateError
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.Timeout.read_timeout:6: WARNING: py:exc reference target not found: urllib3.exceptions.TimeoutStateError
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.Timeout.read_timeout:12: WARNING: py:attr reference target not found: Timeout.DEFAULT_TIMEOUT
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.Timeout.read_timeout:1: WARNING: py:exc reference target not found: urllib3.exceptions.TimeoutStateError
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.Timeout.read_timeout:13: WARNING: py:meth reference target not found: start_connect
/usr/lib/python3.8/site-packages/urllib3/util/timeout.py:docstring of urllib3.util.timeout.Timeout.start_connect:1: WARNING: py:exc reference target not found: urllib3.exceptions.TimeoutStateError
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/blocks.rst:106: WARNING: 'token' reference target not found: suite
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/blocks.rst:106: WARNING: 'token' reference target not found: expression
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/blocks.rst:106: WARNING: 'token' reference target not found: target
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/blocks.rst:106: WARNING: 'token' reference target not found: suite
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/blocks.rst:106: WARNING: 'token' reference target not found: suite
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/blocks.rst:106: WARNING: 'token' reference target not found: suite
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/blocks.rst:106: WARNING: 'token' reference target not found: suite
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/blocks.rst:106: WARNING: 'token' reference target not found: suite
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/generic.rst:42: WARNING: py:class reference target not found: api_sample.RandomNumberGenerator
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/customisation/toc.md:7: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/customisation/toc.md:15: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/text-formatting.md:6: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/text-formatting.md:43: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/admonitions.md:8: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/admonitions.md:37: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/admonitions.md:36: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/admonitions.md:63: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/admonitions.md:139: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/admonitions.md:178: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/admonitions.md:205: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/admonitions.md:228: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/api.md:8: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/api.md:35: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/code-blocks.md:6: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/code-blocks.md:57: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/hyperlinks.md:6: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/hyperlinks.md:33: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/images.md:8: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/images.md:23: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/images.md:22: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/images.md:41: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/images.md:40: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/images.md:59: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/images.md:68: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/images.md:99: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/lists.md:8: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/lists.md:39: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/lists.md:37: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/lists.md:50: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/lists.md:50: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/lists.md:69: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tables.md:6: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tables.md:: WARNING: "table cell spanning" not supported
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tables.md:: WARNING: "table row spanning" not supported
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tables.md:: WARNING: "table row spanning" not supported
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tables.md:: WARNING: "table cell spanning" not supported
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tables.md:67: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tabs.md:12: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tabs.md:26: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tabs.md:30: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tabs.md:35: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tabs.md:46: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tabs.md:50: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tabs.md:38: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/reference/tabs.md:65: WARNING: "unsupported "label"
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/tables.rst:: WARNING: "table cell spanning" not supported
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/tables.rst:: WARNING: "table row spanning" not supported
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/tables.rst:: WARNING: "table row spanning" not supported
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/tables.rst:: WARNING: "table cell spanning" not supported
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/tables.rst:: WARNING: "table cell spanning" not supported
/home/tkloczko/rpmbuild/BUILD/furo-2023.05.20/docs/kitchen-sink/tables.rst:: WARNING: "table cell spanning" not supported
done
build succeeded, 109 warnings.

You can peak on fixes that kind of issues in other projects
https://github.com/RDFLib/rdflib-sqlalchemy/issues/95
https://github.com/RDFLib/rdflib/pull/2036
https://github.com/click-contrib/sphinx-click/commit/abc31069
https://github.com/frostming/unearth/issues/14
https://github.com/jaraco/cssutils/issues/21
https://github.com/latchset/jwcrypto/pull/289
https://github.com/latchset/jwcrypto/pull/289
https://github.com/pypa/distlib/commit/98b9b89f
https://github.com/pywbem/pywbem/pull/2895
https://github.com/sissaschool/elementpath/commit/bf869d9e
https://github.com/sissaschool/xmlschema/commit/42ea98f2
https://github.com/sqlalchemy/sqlalchemy/commit/5e88e6e8
Reproducer
Just run /usr/bin/sphinx-build -n -T -b man docs build/sphinx/man in root source tree.
Expectation
sphinx should not generate warninx with -n option.
Code of Conduct

[X] I agree to follow the Code of Conduct.

Hey, I believe this should not be related to Furo. Sphinx separates out "content" from "presentation". What happens if you change html_theme = "alabaster", i.e. one of the builtin themes.

Those warnings are about references incorrectly defined,
As you see I'm generating man page to show you that it has nothing to do with theme.

Generating man pages is something I recommend that you do not try; that's not something that I expect to be necessary for an HTML theme. If you're using this website theme, it is expected that you'll be able to use a browser.
Beyond that, https://github.com/pradyunsg/furo/blob/490527b2aef00b1198770c3389a1979911ee1fcb/noxfile.py#L68 for how to build the documentation of this theme.
The errors and nitpicks are because you aren't installing things that need to be installed in the documentation build environment.
Finally, this is not a "trackable task" for the project, which is the template used to file this issue. You've explicitly ignored "Please only use this, if you've been advised to do so after discussion." that was in the issue template selection page, which is not appreciated on my end.

I'll also point out that you could have figured out what the right thing to do here would be by reading https://pradyunsg.me/furo/contributing/workflow/#documentation-generation, which is the documentation of this project and linked to from multiple places.

Hmm... @wuch-g2v looks like a sock-puppet account for @kloczek, to circumvent direct blocking? The issues filed have the exact same style (and level of ignorance of written instructions + lack of research) as that user, and looking at the user's history, they've only filed issues in repositories where I know @kloczek is banned from interacting.

sigh
Yes, it is. From https://github.com/seleniumbase/SeleniumBase/issues/1899:
+ PYTHONPATH=/home/tkloczko/rpmbuild/BUILDROOT/python-seleniumbase-4.14.14-2.fc35.x86_64/usr/lib64/python3.8/site-packages:/home/tkloczko/rpmbuild/BUILDROOT/python-seleniumbase-4.14.14-2.fc

You've put no effort into looking at the project documentation.
You've actively attempted to engage with someone who has blocked you, and proactively engaged in ban evasion (from https://discourse.nixos.org/t/github-block-evasion-is-not-acceptable/12763, "Forcing people to continue engaging [after they've blocked you] is a form of harassment").
You've ignored instructions provided in the template selection screen about how to engage with the project.
What you're reporting is bogus, and you could have figured that out by spending less than 5 minutes looking at the project (especially, given that you've now interacted with a large portion of the Python ecosystem.

Again. I'm working with person which you've blocked.
Incorrect references exposed by -n option are affecting html, qch and pdf output.
We are providing as general feedback what has been found during use our packaging procedure. If you want to ignore that issue that is perfectly fine as on packaging python modules used out approach is generated roff output out packages are not affected by what has been reported.
Reported issue is not critical by any meaning.
If want to punish messenger that is a bit odd ..
Ticket has been closed. Maintainer has been informed about that issue. That was my goal.
Everything else is out of the scope of this ticket.

sigh
I hope that you'd be willing to do any amount of self-reflection and understand what I'm trying to tell you.
Tomasz, please read project documentation for instructions and investigate the issue yourself before asking the project to investigate by filing issues, follow the contribution process of the project you're interacting with, and don't create sock puppets to circumvent bans.
We're done here.

authors: Eric-Arellano pradyunsg wuch-g2v

repo: pradyunsg/furo


text:
Openhelpd 54 create message board

@codiebeulaine ready for review (also @jpaidoussi @rudigiesler )

+1

source: gharchive/pull-request

authors: jpaidoussi miltontony

repo: praekelt/casepro

license_type: permissive

license_source: bigquery


text:
Update config.yml to allow free-form issues

I don't see the point of having too stringent requirements on issues at this stage.

I suspect that what you want from issue now by doing this change is probably what I rather have us do in discussions?
My intent with constraining issues as such was to keep issues exclusively for bug reports, while discussions would be more of a free form format with category/topics.

I suspect that what you want from issue now by doing this change is probably what I rather have us do in discussions?

No. I just want to be able to use issues to build a reasonably useful roadmap and clarify things that need to be done.

authors: KtorZ abailly

repo: pragma-org/amaru

license_source: github-api


text:
Create CI pipeline for running test scripts

This GitHub Actions workflow will run the test.sh and test.ps1 scripts upon pushes and pull requests.
The test.ps is extended to run through all katas that have a setup.ps1 file.
During the workflow creation I found a small issue in the submodules kata that failed the workflow, this was also corrected.

Create CI pipeline running test scripts
Make test.ps1 go through all exercises
Fix setup.ps1 for submodules kata (may conflict with PR #258)

TODO: Make test.sh also go through all katas where applicable.
Related issue: #154

i just realized that i merged this branch back to master in my repo, which messed it up.
i'll close this one and start a new.

repo: praqma-training/git-katas

license: MIT


text:
Generate Fake User for Seeding

Title: Generate Fake User for Seeding
Description:
This GitHub issue aims to create a function named generateFakeUser for generating a fake user that can be used for seeding purposes. The function should utilize various libraries and utilities to generate realistic-looking user data.
Tasks:

Implement generateFakeUser Function:

[ ] Create a function named generateFakeUser in the seeder/utils.ts file.
[ ] Generate a fake user with the following properties:

Email: Generate using the faker library.
Password: Generate using the faker library.
Username: Generate using the faker library.
User ID (UUID): Generate using the faker library.
Full Name: Generate using the faker library.

[ ] Return the generated user data as an object.

Acceptance Criteria:

The generateFakeUser function is successfully implemented.
The function generates a fake user with the specified properties.
The generated user data is returned as an object.

Additional Information:

This function is intended for seeding purposes and will generate a fake user with realistic-looking data.
The issue should be considered resolved once the function is successfully implemented and tested.

@prasenjeet-symon Review my pull request #151

@prasenjeet-symon Review my pull request #151

Merged successfully

source: gharchive/issue

repo: prasenjeet-symon/intellectia


text:
Tvsupport2

ok

This still has some errors

repo: prashanthgadwala/Structuraloptproject


text:
🛑 ChatGPT + DALL-E is down

In 1fd2a1f, ChatGPT + DALL-E (https://streamlit-chatgpt-dalle2.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGPT + DALL-E is back up in 3cf9e29 after 5 minutes.

repo: prateekralhan/status


text:
🛑 ChatGPT Beyond 2021 is down

In 1a3d7fa, ChatGPT Beyond 2021 (https://chatgpt-beyond-2021.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGPT Beyond 2021 is back up in b1d2067 after 3 minutes.


text:
🛑 Prateek Ralhan-Resume is down

In 9328418, Prateek Ralhan-Resume (https://prateek-online-resume-render.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Prateek Ralhan-Resume is back up in 29e3833 after 13 minutes.


text:
🛑 ChatGPT Beyond 2021 is down

In 307f5ce, ChatGPT Beyond 2021 (https://chatgpt-beyond-2021.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGPT Beyond 2021 is back up in 1006ef0 after 21 minutes.


text:
Update to Rust 1.62.0

Rust 1.56.1 fixes a CVE (https://blog.rust-lang.org/2021/11/01/Rust-1.56.1.html) and is required for some packages: https://results.pre-commit.ci/run/github/1970795/1657566379.jpN4rJQVSxquC199vZ6zNQ

can you bump to latest stable instead?

Done!

@asottile when will this be live?

I've gotta deploy it still

repo: pre-commit-ci/runner-image


text:
Does prettier read the .prettierrc config file inside a git repo when ran via pre-commit?

I thought my .prettierrc was being read but it doesn't seem to be changing anything. I've seen other people changing the config per language like this by feeding the args in :
# format java. Seperate from the above for different tab width
  - repo: https://github.com/pre-commit/mirrors-prettier
    rev: v3.0.0-alpha.6
    hooks:
      - id: prettier
        name: prettier-java
        types: [java]
        additional_dependencies:
          - prettier
          - prettier-plugin-java
        args: ["--tab-width", "4", "--print-width", "100"]

pre-commit just executes prettier directly -- so it's not different or special.  it works fine for me

I switched to debug and found the config file wasn't being read!

How bizarre that it doesn't seem to pick up a config file if it exists:-
Config options:

  --config <path>          Path to a Prettier configuration file (.prettierrc, package.json, prettier.config.js).
  --no-config              Do not look for a configuration file.
  --config-precedence <cli-override|file-override|prefer-file>
                           Define in which order config files and CLI options should be evaluated.
                           Defaults to cli-override.
  --no-editorconfig        Don't take .editorconfig into account when parsing configuration.
  --find-config-path <path>
                           Find and print the path to a configuration file for the given input file.
  --ignore-path <path>     Path to a file with patterns describing files to ignore.
                           Defaults to .prettierignore.
  --plugin <path>          Add a plugin. Multiple plugins can be passed as separate `--plugin`s.
                           Defaults to [].
  --plugin-search-dir <path>
                           Custom directory that contains prettier plugins in node_modules subdirectory.
                           Overrides default behavior when plugins are searched relatively to the location of Prettier.
                           Multiple values are accepted.
                           Defaults to [].
  --with-node-modules      Process files inside 'node_modules' directory.

authors: asottile gilesw

repo: pre-commit/mirrors-prettier


text:
Header bidding and Prebid intros

🏷 Type of documentation

[ ] text edit only (wording, typos)
New Intro to Header Bidding and updated/re-written Intro to Prebid

📋 Checklist

Thanks @bretg, updates look good. The top header providers also came from Sincera. It was something Mike and I talked about but I don't think he wanted that one dynamic so I just did a screenshot. But I'm fine with taking it out.
I'll add the centering, thanks for the link.

Ok - we can leave the picture in for now -- will bring up the conversation with Mike.
Once the pictures are centered, will sign off!

@jeanstemp - a request from Sincera. Please add
"Data by Sincera" that's a link to https://app.sincera.io/

to the bottom-right of each picture or iframe coming from them.
And heads up there may be a change coming to the 'top header providers' static picture

@bretg Thanks for checking on that. I've added the links as requested.

authors: bretg jeanstemp


text:
Fix issue 178

#178
This fix is for the Issue from the link above. It was closed recently... However, I have been requested to fix this as a part of the GE team.

Taken forward in #207

repo: predixdesignsystem/px-data-table


text:
Scheduled Task error with install.ps1

Getting this error from range when deploying probes:
Determining OS\n[+] Provisioning Detect Endpoint Token...\n[+] Downloading Probe...\n[+] Creating task\n[+] Task started\n[=] Detect setup complete\nRegister-ScheduledTask : No mapping between account names and security IDs was done.\r\n(14,8):UserId:\r\nAt C:\Windows\system32\install.ps1:69 char:12\r\n+     [void](Register-ScheduledTask -TaskName $name -InputObject $task)\r\n+            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n    + CategoryInfo          : NotSpecified: (PS_ScheduledTask:Root/Microsoft/...S_ScheduledTask) [Register-ScheduledTa \r\n   sk], CimException\r\n    + FullyQualifiedErrorId : HRESULT 0x80070534,Register-ScheduledTask\r\n \r\n",0],["[+] Detect setup started\n[+] Determining OS\n[+] Provisioning Detect Endpoint Token...\n[+] Downloading Probe...\n[+] Creating task\n[+] Task started\n[=] Detect setup complete\nRegister-ScheduledTask : No mapping between account names and security IDs was done.\r\n(14,8):UserId:\r\nAt C:\Windows\system32\install.ps1:69 char:12\r\n+     [void](Register-ScheduledTask -TaskName $name -InputObject $task)\r\n+            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n    + CategoryInfo          : NotSpecified: (PS_ScheduledTask:Root/Microsoft/...S_ScheduledTask) [Register-ScheduledTa \r\n   sk], CimException\r\n    + FullyQualifiedErrorId : HRESULT 0x80070534,Register-ScheduledTask\r\n \r\n",0]]]%

dupe of a bug in the range/ repo (https://github.com/preludeorg/range/issues/15)

repo: preludeorg/libraries


text:
Update root.go

the status code should be in the range [0, 125].
https://pkg.go.dev/os#Exit

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant alexsuslov

repo: prest/prest


text:
Add Select form component

Fixes #71

Codecov Report

Merging #221 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #221   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          34     35    +1
  Lines         409    413    +4
=====================================
+ Hits          409    413    +4

Impacted Files
Coverage Δ

src/Select.js
100% <100%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b8c46fc...d63b62a. Read the comment docs.

authors: codecov-io jxnblk

repo: pricelinelabs/design-system

license: mit


text:
FeatureRequest: SelectPanel without save and cancel buttons

Describe the bug
Recently the SelectPanel component was updated to add cancel and save buttons at the bottom of the component, this is great but in some cases i think it's innecesary (for example when you can only select 1 option instead of an array, due the component allows to do that) so...
a prop that allows hide or show the buttons can be usefull
or even maybe a bottom prop, so the dev can choose what he wants to show there
Screenshots

Thanks for writing this up!
@alliethu could you take a look at this request from the accessibility design perspective and let us know if this pattern without the save and cancel buttons would still be accessible?

👋 @deleonjuan I recorded a call with @jscholes, one of our Screen reader expert consultants, to explore your proposal.
📹 Our meeting recording
User scenario:
A user activates a selectPanel, clicks/presses to select an option, the option is automatically saved, and the dialog closes.
As @jscholes mentions here, although this may seem like an accessible solution to mouse users, this is an inaccessible pattern for keyboard users. Reason being, there is no cue for keyboard users to know that pressing enter selects and saves the option, thus closing the dialog. Keyboard users need the opportunity to arrow through the options, select an option (pressing enter), and then be able to tab to save/cancel the options.

@alliethu Just to clarify: keyboard users don't need to press Enter to select an option, and then Tab to "Save".  Having Enter choose an item and close the select panel is fine, it's just non-obvious to users who don't know they can do so.  So for those users, they must be able to arrow to an option, and discover the "Save" button.

Thank you for that clarification, @jscholes!

Thanks for the accessibility review!
Given that this proposal would lead us to implementing an inaccessible design pattern, it's not something we'll be moving forward with. Please feel free to comment back, even once this issue is closed, if there are further questions or concerns.

I'd like to challenge this and ask if we can find a solution to this without the Save button. Are there some cues we can give users that pressing Enter would select and Close?
I'm all for adding the Save button if it leads to a more accessible experience, but one of our main customer complaints is that it requires a lot of clicks to do something.
A competitor of ours, Linear, uses a pattern that I feel works quite well: Pressing Enter in a select panel selects and closes it. Pressing Space selects but keeps it open.
Another difference in their implementation is that changes are applied instantly (as in the user doesn't have to close or save the panel to see changes take effect) - I'm wondering if that's an inaccessible solution or if they're doing something that makes this a great experience for all users.

@six7 I'd like to try and clear up some points of confusion:

I'm all for adding the Save button if it leads to a more accessible experience, but one of our main customer complaints is that it requires a lot of clicks to do something.

These clicks should not be required.  In my accessibility sign off review for this component (https://github.com/github/primer/issues/1245#issuecomment-1242376489), I indicated that the behaviour for single-select use cases is currently suboptimal, and that Enter/click should be available to choose an item and close the panel.  That is not currently implemented within the component, but hopefully will be in the near future.
At that point, using the "Save" button will not be strictly required for single-select, for any user.  However, it's important that it still be present from a usability and consistency perspective, so that users unfamiliar with the "Enter to select" pattern can still work out what to do.  It also keeps the component UI balanced, in terms of having a "Cancel" button too, and not only relying on the "Close" button at the top of the dialog for dismissal.
For multi-select, the "Save" button is required at all times, although pressing Enter on an option can close the panel without toggling that option.  It would not be accessible to have a multi-select pattern in place without explicit save/cancel buttons.

Another difference in their implementation is that changes are applied instantly (as in the user doesn't have to close or save the panel to see changes take effect) - I'm wondering if that's an inaccessible solution

It is not.  This is universally bad for accessibility across the board, as it limits exploration, and can leave users in an unintended state without having the means to undo it.  See 3.2.2 On Input (level A) in WCAG for more context.

I don't have anything else to add here other than I 100% agree with @jscholes!

Can we do something to mark https://github.com/primer/react/issues/2342 as blocked until the above changes are implemented and this has had a chance for user feedback?
As @six7 has covered this would have some major customer pushback for us if it were to be released as is. This essentially would block us from any primer upgrades if it become part of a major version release as seems to be indicated here - https://github.com/primer/react/issues/2342#issuecomment-1251650056
Where is is not clear if the plan is to put it in draft because it is not ready to be consumed yet (until the feedback from @jscholes is implemented) or to put it in draft for minor version and then release fully in the next major version.

@azenMatt:

Can we do something to mark https://github.com/primer/react/issues/2342 as blocked until the above changes are implemented and this has had a chance for user feedback?

Noting here that #2342 has been cross-linked to this issue.

Where is is not clear if the plan is to put it in draft because it is not ready to be consumed yet (until the feedback from @jscholes is implemented) or to put it in draft for minor version and then release fully in the next major version.

The feedback @jscholes referenced above https://github.com/github/primer/issues/1245#issuecomment-1242376489 was actually already implemented and released in a recent Primer React minor version, but in doing so we broke the semver expectations for our consumers because the work introduced a breaking change. I'll work with the team to get an update on when the next major version is likely to go out https://github.com/github/primer/issues/1294#issuecomment-1278477990.

After discussing with PRC maintainers, we've determined that releasing the next major before Universe risks bugs, churn, and frustration from consumers. As per https://github.com/github/primer/issues/1294#issuecomment-1289723555, we're currently planning to release the version with SelectPanel fixes in January 2023. FYI @azenMatt

authors: alliethu azenMatt deleonjuan ichelsea jscholes lesliecdubs six7

repo: primer/react


text:
[question] how can I force an item to expand?

Description
I see the library currently provides a collapse public method. is there anything like it to expand a group?

hi, you can pass a list of ids for this public method.
items with those ids will become/stay open while others get/stay closed.

authors: marcelo-dexla primetwig

repo: primetwig/react-nestable

license: ISC