sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [TextField] Correct the label's `maxWidth` when "select" option is enabled
Labels: bug 🐛,component: text field

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

The label `max-width` is the same as a normal text field, which causes the ellipsed label to be behind the dropdown icon

#### Example
![image](https://user-images.githubusercontent.com/39598117/154798466-ffb9f2c1-aa03-4d1b-a610-ab5bd30838ec.png)


#### Reproduction with Fix
https://stackblitz.com/edit/react-njhcna?file=demo.tsx


### Expected behavior 🤔

The base max-width seems to be `calc(100% - 24px)` but with the `select` option it should be `calc(100% - 48px)` on the `outlined` and `filled` textfield, and `calc(100% - 24px)` on the `standard` textfield

#### Example
![image](https://user-images.githubusercontent.com/39598117/154798535-dbe7f232-3963-4c50-8e35-09c5d9349a0a.png)


### Steps to reproduce 🕹

Steps:

1. Create a TextField.
2. Add the `select` option.
3. Add a super long label (I know we're not supposed to but yea).
4. See the ellipsed label behind the icon.


### Context 🔦
This can be solved manually by adding this to a textfield, but would be nice if this was included out of the box
```jsx
InputLabelProps={{
    sx: {
      // avoid when input is focused or filled
      ["&:not(.MuiInputLabel-shrink)"]: {
        // issue with label padding, see: https://github.com/mui/material-ui/issues/31145
        maxWidth:
          variant !== "filled"
            ? "calc(100% - 48px)"
            : "calc(100% - 24px)",
      },
    },
  }}
```

### Your environment 🌎

<details>
  <summary>npx @mui/envinfo</summary>

```
  System:
    OS: Linux 5.16 Fedora Linux 35 (Workstation Edition)
  Binaries:
    Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v16.13.2/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.2/bin/npm
  Browsers:
    Chrome: 98.0.4758.102
    Firefox: Not Found
  npmPackages:
    @emotion/react:  11.7.1 
    @emotion/styled:  11.6.0 
    @mui/base:  5.0.0-alpha.65 
    @mui/icons-material:  5.3.0 
    @mui/lab:  5.0.0-alpha.65 
    @mui/material:  5.3.0 
    @mui/private-theming:  5.3.0 
    @mui/styled-engine:  5.3.0 
    @mui/system:  5.3.0 
    @mui/types:  7.1.0 
    @mui/utils:  5.3.0 
    @types/react:  17.0.38 
    react:  17.0.2 
    react-dom:  17.0.2 
    typescript:  4.5.5 
```
</details>
Repository: godot
Issue: Zero child of CanvasLayer (which is a child of Camera2D) may render with wrong transform [Windows, Intel HD 630 or lower]
Labels: bug,platform:windows,topic:rendering,confirmed,topic:thirdparty,topic:2d

___

***Bugsquad note:** This issue has been confirmed several times already. No need to confirm it further.*

___

### Godot version

4.0 alpha2 (UPD: alpha5)

### System information

1) Windows 10, Dell Inspiron 7577, Intel HD Graphics 630 (driver version (latest atm) 27.20.100.9664), GTX 1050ti (driver version 30.0.14.7212), Vulkan API 1.2.170
2) PC from my work with Intel HD Graphics 620 and Windows 10

### Issue description

CanvasLayer, being Camera2D child, doesn't "follow" Camera2D if global (0,0) coordinate is in view. "Follow" is not properly word here, but I don't know how to describe, so just look at gifs below. NOTE: It works as expected (like on second gif) in 3.x, so this actually a bug and not wrong use case.
MRP scene tree:
![Godot_v4 0-alpha2_win64_ESlZE3zWcQ](https://user-images.githubusercontent.com/43543909/154797687-5bd3b812-964e-496a-b2d9-36dfc9db7d5b.png)

Broken when running on Intel HD Graphics 630:
<details>
  <summary>Gif</summary>

![RICEamGHyY](https://user-images.githubusercontent.com/43543909/154797395-93817510-48f8-4f48-bd6f-2b844590db64.gif)

</details>

Works as expected on 1050ti:
<details>
  <summary>Gif</summary>

![mNvK53vSxB](https://user-images.githubusercontent.com/43543909/154797753-720b7ece-5815-4a26-b8af-358ab5ce985b.gif)

</details>

Console output is the same and doesn't report anything strange.

If this is driver or hardware issue, I don't understand why it works if global (0,0) coordinate is out of the screen.
Also for Intel HD Graphics 630 this is latest driver version (according to Dell update center).
Actually this could be Intel iGPU problem, see #59802

### Steps to reproduce

Run MRP (on Intel iGPU & Windows10)

### Minimal reproduction project

[G4CanvasLayerBug.zip](https://github.com/godotengine/godot/files/8101961/G4CanvasLayerBug.zip)
Repository: material-ui
Issue: [TextField] Problems with changing the input label fontSize
Labels: bug 🐛,component: text field

I tried to change the fontsize of the lable using 
```
const theme = createTheme({
  components: {
    MuiInputLabel: {
      defaultProps: {
        sx: {
          fontSize: "13px",
        },
      },
    },
  },
});
```
Achieved 
![image](https://user-images.githubusercontent.com/30999510/154799922-7561b526-ebd1-41f3-99b8-88d6011ad266.png)

But On focusing the fontsize appears too small which make a empty space on the right (Look into pic below)
![Screenshot 2022-02-19 at 5 33 47 PM](https://user-images.githubusercontent.com/30999510/154800012-e37410fe-ab3b-4a74-80c2-88c3716336e3.png)

Please let me know how can I get Rid of it.
Or I can change the Font size only when the input is not focused.
What I wanted it to look like is 
![image](https://user-images.githubusercontent.com/30999510/154799922-7561b526-ebd1-41f3-99b8-88d6011ad266.png) (Small font size when Field is empty)
and
![image](https://user-images.githubusercontent.com/30999510/154800240-a87ab565-c8e1-4011-9a29-d0b0f1a54f31.png) (Normal font size when Field is Filled)


_Originally posted by @iamadityaaz in https://github.com/mui/material-ui/issues/13840#issuecomment-1046002798_
Repository: pytorch
Issue: Add nan-safe einsum and bilinear
Labels: triaged,enhancement,module: linear algebra,needs design

### 🚀 The feature, motivation and pitch

Add nan-safe einsum, linear and bilinear functions (similar to nanmean and nansum) 

### Alternatives

alternative is zero filling nans, every time you invoke these functions which slows down operations quite a bit over time.

### Additional context

_No response_

cc @jianyuh @nikitaved @pearu @mruberry @walterddr @IvanYashchuk @xwang233 @Lezcano @VitalyFedyunin @ngimel
Repository: PowerToys
Issue: Customizable right click menu (top mini bar in win11)
Labels: Idea-New PowerToy,Product-Tweak UI Design

### Description of the new feature / enhancement

Hi,
Could it be possible to make the top mini bar of the right click menu customizable so right click items can be added to it for quicker usage? 

### Scenario when this would be used?

A mounted media that needs to be ejected, adding the eject to the top right click mini bar would be handy. 

### Supporting information

I have none.
Repository: vscode
Issue: Accessibility: allow advanced styling of explorer decorations
Labels: feature-request,accessibility,file-decorations

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
I have been working on a light color theme to reduce eyestrain and comply with contrast requirements as specified by the [WCAG guidelines](https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html).  These guidelines specify that text have a contrast ratio of at least 4.5:1 (level AA) or 7:1([level AAA](https://www.w3.org/WAI/WCAG21/Understanding/contrast-enhanced)). This greatly reduces the number of colors that can be used for styling text that is not appreciably large, which the file explorer text is not. WCAG guidelines are [much more permissive](https://www.w3.org/TR/WCAG21/#non-text-contrast) for non-text elements, such as badges or underlining/wavy underlining, allowing for a ratio of 3:1, however, since the only styling provided is for the color of the filename (and not the background or text-decoration) it is impossible to meaningfully style these items in a light theme and still comply with accessibility guidelines.

I propose the addition of styling options for such things as:

`"gitDecoration.modifiedResourceBackground": "<hex value>",` Which would allow the text to stay the same high-contrast color.
`"gitDecoration.modifiedResourceIndicatorBackground": "<hex value>",` Allowing for styling of the indicator (`M`, `U` `⚫`, etc) background (ideally this could be rounded)
Or some styling directive allowing these items to have a wavy underline of a particular color.
Repository: rust
Issue: Missing trait bounds error without justification
Labels: T-compiler,C-bug,E-needs-mcve,F-generic_const_exprs

Taking Rust's const generic expressions for a drive and ran into a situation where the compiler identifies a missing trait bound, but not which bound is missing.

Code: https://github.com/jlogan03/catnip/blob/0ea28658e2d76874258569a89f42ad0091e6e26f/catnip/src/udp.rs#L66

I expected to see this happen: 
* Evaluate without error

Instead, this happened: 
* Trait bounds error, but with no indication of which bound is missing

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.59.0-nightly (cfa3fe5af 2021-12-31)
binary: rustc
commit-hash: cfa3fe5af339e724209b25715282adae0c61628f
commit-date: 2021-12-31
host: x86_64-apple-darwin
release: 1.59.0-nightly
LLVM version: 13.0.0
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
Jamess-MacBook-Pro:catnip jlogan$ cargo check
    Checking catnip v0.1.0 (/Users/jlogan/git/catnip/catnip)
warning: the feature `generic_const_exprs` is incomplete and may not be safe to use and/or cause compiler crashes
 --> src/lib.rs:6:12
  |
6 | #![feature(generic_const_exprs)]
  |            ^^^^^^^^^^^^^^^^^^^
  |
  = note: `#[warn(incomplete_features)]` on by default
  = note: see issue #76560 <https://github.com/rust-lang/rust/issues/76560> for more information

error[E0599]: no method named `total_length` found for struct `IPV4Header<'a, M>` in the current scope
  --> src/udp.rs:66:41
   |
66 |           self.ip_header = self.ip_header.total_length(ip_length);
   |                                           ^^^^^^^^^^^^ method cannot be called on `IPV4Header<'a, M>` due to unsatisfied trait bounds
   |
  ::: src/ip.rs:40:1
   |
40 | / pub struct IPV4Header<'a, const N: usize>
41 | | where
42 | |     [u8; 4 * N + 20]:,
43 | | {
44 | |     /// The actual content of the header as bytes
45 | |     pub value: [u8; 4 * N + 20],
46 | | }
   | |_- method `total_length` not found for this

For more information about this error, try `rustc --explain E0599`.
warning: `catnip` (lib) generated 1 warning
error: could not compile `catnip` due to previous error; 1 warning emitted
```

</p>
</details>
Repository: go
Issue: cmd/compile,go/types: improve error messages when go version is too low 
Labels: NeedsInvestigation,compiler/runtime

### What version of Go are you using (`go version`)?

<pre>
go version go1.18rc1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
yes 


### What did you do?

Tried to play with generics after installing go 1.18 RC1, but was a little confused by the error message 
when trying to use 1.18 feature like the `any` keyword  because I totally forgot about the go version in `go.mod`.

`./main.go:30:25: undeclared name: any (requires version go1.18 or later)`

Mentioning `go.mod` in the error message would have helped fixing the error directly instead of having to re-check my config and search for this error message etc 


### What did you expect to see?

./main.go:30:25: undeclared name: any (requires version go1.18 or later, current min version in go.mod: go1.16)

### What did you see instead?

./main.go:30:25: undeclared name: any (requires version go1.18 or later)
Repository: godot
Issue: DirectionalLight3D shadows don't use the Shadow Max Distance property when the camera is in orthogonal mode (it uses the camera's Far distance instead)
Labels: bug,topic:rendering,confirmed,documentation,topic:3d

### Godot version

499eec13a3

### System information

Arch, Vukan, X11, NVIDIA GeForce GTX 1070/PCIe/SSE2

### Issue description

Shadows don't appear to be rendered correctly when using an orthogonal perspective. 

Orthogonal:
![Screenshot from 2022-02-19 19-05-44](https://user-images.githubusercontent.com/80655527/154823344-165daca9-b68d-479b-a499-2e6f67a7b327.png)

Perspective: 
![Screenshot from 2022-02-19 19-06-02](https://user-images.githubusercontent.com/80655527/154823345-3ffecb55-7fb9-4a71-aa46-317d1cc0f2c0.png)

Scene uses a directional light. 


### Steps to reproduce

Any scene with a directional light and an orthogonal camera perspective should recreate the issue, but I've attached a project for convenience. 

### Minimal reproduction project

[Uploading minimal_project.zip…]()
Repository: pytorch
Issue: How do we handle metadata-modifying in-place operators (like `squeeze_`) with `__torch_dispatch__`?
Labels: triaged,module: __torch_dispatch__


```
import torch
from torch.utils._pytree import tree_map

aten = torch.ops.aten
class LoggingTensor(torch.Tensor):
    elem: torch.Tensor

    __slots__ = ['elem']

    @staticmethod
    def __new__(cls, elem, *args, **kwargs):
        # The wrapping tensor (LoggingTensor) shouldn't hold any
        # memory for the class in question, but it should still
        # advertise the same device as before
        r = torch.Tensor._make_wrapper_subclass(  # type: ignore[attr-defined]
            cls, elem.size(),
            strides=elem.stride(), storage_offset=elem.storage_offset(),
            # TODO: clone storage aliasing
            dtype=elem.dtype, layout=elem.layout,
            device=elem.device, requires_grad=kwargs.get("requires_grad", False)
        )
        # ...the real tensor is held as an element on the tensor.
        r.elem = elem.detach() if r.requires_grad else elem
        return r

    def __repr__(self):
        return f"LoggingTensor({self.elem})"

    @classmethod
    def __torch_dispatch__(cls, func, types, args=(), kwargs=None):
        def unwrap(e):
            return e.elem if isinstance(e, LoggingTensor) else e

        def wrap(e):
            return LoggingTensor(e) if isinstance(e, torch.Tensor) else e

        # no_dispatch is only needed if you use enable_python_mode.
        # It prevents infinite recursion.
        rs = tree_map(wrap, func(*tree_map(unwrap, args), **tree_map(unwrap, kwargs)))
        return rs

a = LoggingTensor(torch.randn(1, 5))
print(a.shape, a.elem.shape)
a.squeeze_(0)
print(a.shape, a.elem.shape)
```
This doesn't modify the tensor's shape, as it's in-place.

Usually, we can address this by checking whether an operator is in-place or not (https://github.com/pytorch/functorch/blob/main/functorch/_src/python_key.py#L123), but that only allows us to modify the underlying `elem` tensor.

How do we update the metadata here?

cc: @zou3519 @albanD @ezyang 

cc @albanD @zou3519
Repository: godot
Issue: bbcode tags effect line spacing in RichTextLabel node
Labels: documentation,topic:gui

### Godot version

3.4 stable

### System information

Windows 10, NVidia 1050ti, GLES2

### Issue description

When using bbcode tags in the RichTextLabel node the tags after the effects are applied still change the line spacing.

### Steps to reproduce

Formatting like you would write code:
[rainbow freq=0.2 sat=10 val=20]
     [wave amp=50 freq=2]
          [font=res://Fonts/Source Serif/Source Serif - Norm_Title.tres]
                [center]~~~~~~~ What are you looking for today? ~~~~~~~[/center]
          [/font]
     [/wave]
[/rainbow]

And all as one line:
[rainbow freq=0.2 sat=10 val=20][wave amp=50 freq=2][font=res://Fonts/Source Serif/Source Serif - Norm_Title.tres][center]~~~~~~~ What are you looking for today? ~~~~~~~[/center][/font][/wave][/rainbow]

Produce different text spacing results

![image](https://user-images.githubusercontent.com/54188782/154827032-b18f2032-e708-48e7-82e9-3644d2184985.png)

![image](https://user-images.githubusercontent.com/54188782/154827094-4ed274c7-607b-4de5-a18b-2c0799947457.png)



### Minimal reproduction project

_No response_
Repository: godot
Issue: bbcode [font] tag extra spacing is not applied
Labels: bug,topic:gui

### Godot version

3.4 stable

### System information

Windows 10, NVidia 1050ti, GLES2

### Issue description

When using the font tag the extra spacing values of a dynamic font will not apply

### Steps to reproduce

1. Have a dynamic font set in the normal font slot in the richtextlabel node
2. Have an a seperate dynamic font with extra spacing values changed referenced in text wrapped in the font tag (_[font=res://myfont.tres]your text here[/font]_)

### Minimal reproduction project

_No response_
Repository: three.js
Issue: Nodes: Sometimes when using CondNode extra parentheses are generated
Labels: Enhancement

**Describe the bug**

Sometimes when using the CondNode extra parentheses are generated. For example, in example https://jsfiddle.net/5a01skvw/ from https://github.com/mrdoob/three.js/issues/23170 there is a pair of extra parentheses in the condition - it is written `if ( ( nodeVar5 > 0.0 ) )` instead of just `if ( nodeVar5 > 0.0 )`.
I am not sure that this is a bug that should be fixed but I think that it would be nice if such extra parentheses would not be generated.

***Live example***

* [jsfiddle-dev](https://jsfiddle.net/5a01skvw/)

**Expected behavior**

Extra parentheses would not be generated.
Repository: rust
Issue: rustdoc: macro calls in alias (stringify!)
Labels: T-rustdoc

When working with ffi, sometimes I need to alias the rust function to the foreign one.
```rust
#[doc(alias = "ffi_fun")]
fn myfun() {
  // ...
  ffi_fun()
}
```

Since I need to wrap many foreign functions, I use a macro (created with macro_rules) which looks roughly like this:
```rust
#[doc(alias = stringify!($ffi_fun))]
fn $fun() {
  // ...
  $ffi_fun()
}
```

`stringify!`, `concat!` and other similar macros are really useful to generate the alias. It would be nice being able to use them
Repository: go
Issue: cmd/go: vcs info not stamped when built listing .go files directly
Labels: help wanted,NeedsInvestigation,GoCommand,modules

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18rc1 windows/amd64
</pre>

### Does this issue reproduce with the latest release?

N/A

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\max\AppData\Local\go-build
set GOENV=C:\Users\max\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\max\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\max\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Users\max\sdk\go1.18rc1
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Users\max\sdk\go1.18rc1\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.18rc1
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=C:\Users\max\Code\go-vcs-issue-repro\go.mod
set GOWORK=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\max\AppData\Local\Temp\go-build2053103368=/tmp/go-build -gno-record-gcc-switches
</pre></details>

### What did you do?

```powershell
git clone https://github.com/mlcdf/go-vcs-issue-repro.git
cd go-vcs-issue-repro
go1.18rc1 build main.go
.\main.exe
```

### What did you expect to see?

VCS info appearing in the console :
[{-compiler gc} {CGO_ENABLED 1} {CGO_CFLAGS } {CGO_CPPFLAGS } {CGO_CXXFLAGS } {CGO_LDFLAGS } {GOARCH amd64} {GOOS windows} {GOAMD64 v1} {vcs git} {vcs.revision 2d1c081410d0f5f23fd1dd7e08794041955a2119} {vcs.time 2022-02-20T11:01:47Z} {vcs.modified false}]

### What did you see instead?

[{-compiler gc} {CGO_ENABLED 1} {CGO_CFLAGS } {CGO_CPPFLAGS } {CGO_CXXFLAGS } {CGO_LDFLAGS } {GOARCH amd64} {GOOS windows} {GOAMD64 v1}]

If I run `go1.18rc1 build` instead of `go1.18rc1 build main.go` and run the `.\go-vcs-issue-repro.exe` binary, it works fine. Is it expected behavior?
Repository: node
Issue: TLSv1.3 cipher suites supported
Labels: question,tls,crypto,doc

### Affected URL(s)

https://nodejs.org/api/tls.html

### Description of the problem

The page states:

https://github.com/nodejs/node/blob/53364a2ec61594ced5b56da804554a2acc09673a/doc/api/tls.md?plain=1#L360-L370

However executing [`tls.getCiphers()`](https://nodejs.org/api/tls.html#tlsgetciphers) shows:

```js
[
  'aes128-gcm-sha256',
  'aes128-sha',
  'aes128-sha256',
  'aes256-gcm-sha384',
  'aes256-sha',
  'aes256-sha256',
  'dhe-psk-aes128-cbc-sha',
  'dhe-psk-aes128-cbc-sha256',
  'dhe-psk-aes128-gcm-sha256',
  'dhe-psk-aes256-cbc-sha',
  'dhe-psk-aes256-cbc-sha384',
  'dhe-psk-aes256-gcm-sha384',
  'dhe-psk-chacha20-poly1305',
  'dhe-rsa-aes128-gcm-sha256',
  'dhe-rsa-aes128-sha',
  'dhe-rsa-aes128-sha256',
  'dhe-rsa-aes256-gcm-sha384',
  'dhe-rsa-aes256-sha',
  'dhe-rsa-aes256-sha256',
  'dhe-rsa-chacha20-poly1305',
  'ecdhe-ecdsa-aes128-gcm-sha256',
  'ecdhe-ecdsa-aes128-sha',
  'ecdhe-ecdsa-aes128-sha256',
  'ecdhe-ecdsa-aes256-gcm-sha384',
  'ecdhe-ecdsa-aes256-sha',
  'ecdhe-ecdsa-aes256-sha384',
  'ecdhe-ecdsa-chacha20-poly1305',
  'ecdhe-psk-aes128-cbc-sha',
  'ecdhe-psk-aes128-cbc-sha256',
  'ecdhe-psk-aes256-cbc-sha',
  'ecdhe-psk-aes256-cbc-sha384',
  'ecdhe-psk-chacha20-poly1305',
  'ecdhe-rsa-aes128-gcm-sha256',
  'ecdhe-rsa-aes128-sha',
  'ecdhe-rsa-aes128-sha256',
  'ecdhe-rsa-aes256-gcm-sha384',
  'ecdhe-rsa-aes256-sha',
  'ecdhe-rsa-aes256-sha384',
  'ecdhe-rsa-chacha20-poly1305',
  'psk-aes128-cbc-sha',
  'psk-aes128-cbc-sha256',
  'psk-aes128-gcm-sha256',
  'psk-aes256-cbc-sha',
  'psk-aes256-cbc-sha384',
  'psk-aes256-gcm-sha384',
  'psk-chacha20-poly1305',
  'rsa-psk-aes128-cbc-sha',
  'rsa-psk-aes128-cbc-sha256',
  'rsa-psk-aes128-gcm-sha256',
  'rsa-psk-aes256-cbc-sha',
  'rsa-psk-aes256-cbc-sha384',
  'rsa-psk-aes256-gcm-sha384',
  'rsa-psk-chacha20-poly1305',
  'srp-aes-128-cbc-sha',
  'srp-aes-256-cbc-sha',
  'srp-rsa-aes-128-cbc-sha',
  'srp-rsa-aes-256-cbc-sha',
  'tls_aes_128_ccm_8_sha256',
  'tls_aes_128_ccm_sha256',
  'tls_aes_128_gcm_sha256',
  'tls_aes_256_gcm_sha384',
  'tls_chacha20_poly1305_sha256'
]
```

Notice how `tls_aes_128_ccm_sha256` and `tls_aes_128_ccm_8_sha256` is part of that list.

How can it then be true that the first example states they are not enabled?