sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [Button] using nested custom `color`
Labels: discussion,package: system

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

Currently, we can define new colors with the theme:
https://mui.com/customization/palette/#adding-new-colors

Unfortunately it seems that we can't use the nested property directly within the `color` prop of the `Button`
```typescript
 <Button color="secondary.darker" /> // Error
```

It would be nice if we could use it in the same way we use `sx` prop.
```typescript
<Box sx={{ backgroundColor: 'secondary.darker' }} /> // Working
```

### Examples 🌈

```typescript
 <Button color="secondary.darker" />
 <Button color="secondary.200" />
```

### Motivation 🔦

I know it's two very different implementations between the `sx` and `color` properties, but maybe it would help having a common API.
To be honest, I setup my whole theme thinking I would be able to pass nested custom colors. I was quite disappointed when I found out it was only possible within the `sx` prop
Repository: neovim
Issue: Empty buffer after slow read from fifo in some terminals
Labels: io,has:repro,bug-regression,has:bisected

### Neovim version (nvim -v)

0.6.0, 0.5.1, 0.5.0, but not 0.4.4

### Vim (not Nvim) behaves the same?

no, vim 8.2.3565

### Operating system/version

Debian bookworm/sid with Linux 5.15

### Terminal name/version

xfce4-terminal 0.8.10 (but not foot 1.6.4)

### $TERM environment variable

xterm-256color or xterm

### Installation

Debian package or nvim-linux64.tar.gz from releases

### How to reproduce the issue

nvim --clean <(sleep 2; seq 1 100)

### Expected behavior

The buffer would show the some number of lines with sequential digits, as Vim does and as NVim did in 0.4.4 (and does for `{ sleep 2; seq 1 100; } | nvim --clean` or in [foot](https://codeberg.org/dnkl/foot)).

### Actual behavior

The lines with sequential digits appear very briefly, then disappear and the buffer appears empty.  The buffer behaves as if it were empty (e.g. does not permit cursor movement, `:w !wc -c` prints 0) so I don't think it is a result of display corruption.

I was able to bisect the issue.  The commit which introduced the issue appears to be 8bee2ff19d8d3a94d6d8e1912c46cb33f8481a5b.
Repository: rust
Issue: Potential optimization: Bounds check hoisting
Labels: C-enhancement,A-mir-opt,C-optimization

It'd be nice if we had a MIR-level optimization pass that could rewrite bounds checks. Here's an example of something Rust couldn't optimize, from https://twitter.com/dougallj/status/1475236088096571392:

> I wanted to explore this for bounds checking, where Rust (last I checked) couldn't optimise the checks for `a[i]; a[i+1]; a[i+2]; a[i+9]` to `len > 9 && i < len-9` because it needs to fail at exactly the right place.

This seems like something that MIR could optimize, since we're responsible for the bounds checks at the language/core library level. However, there's some question as to what the right semantics are: is it OK to fail early? Should we hoist bounds checks only if we detect there's no state in between where the bounds check "should" be and where we hoist it to that could be visible to other threads?

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"JakobDegen"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: neovim
Issue: API guidance: class vs primitive
Labels: enhancement,documentation,api,code-standards,architecture

In API design, one needs to decide whether to model data as primitives (simple types: string/number/map/list) or classes (special-purpose types: metatable-enhanced objects in Lua).

Special-purpose types are more "rich" and often feel more ergonomic initially--especially to the API designer, who is most intimate with the interface. But can be cumbersome because authoring data then requires the runtime, or a translation format. Example: Vim uses a special type for its [job](https://vimhelp.org/channel.txt.html#job) objects whereas Nvim uses a primitive (number = job id).

## Guidance: when to use primitives vs special types

This question is ever-present when designing APIs so we would benefit from a framework for deciding when to use primitives vs special types.

### Primitives

- Pros
    - Primitives are more portable: copy/paste, serialization, Vimscript bridge, RPC, …
    - Easy to inspect: `print(o)`, debuggers
    - Easy to author and store raw data (e.g. for tests)
- Cons
    - No structure/shape, must be parsed/normalized.

### Special types

- Pros
    - Ergonomics (API discovery?). Methods are on the object and/or the object is only compatible with specific functions)
    - Shape enforcement / validation.
        - Example: `Uri` or `Path` object is always "normalized" because its segments are structural. #16800
- Cons
    - Cumbersome outside of the prescribed interface (requires de/serialization)
    - At "edges" the data must be normalized anyway. RPC, Vimscript <=> Lua, …, all require normalization when marshalling.
        - Example: `Uri` or `Path` object will need to be normalized (deterministically de/serialized).
Repository: terminal
Issue: [Terminal]: JAWS Screen Reader Cursor mode does not work inside Terminal app.
Labels: Issue-Bug,Area-TerminalControl,Area-Accessibility,Product-Terminal,HCL-E+D,A11yUsable,HCL-WindowsTerminal,A11yCO

### Windows Terminal version

1.12.3472.0

### Windows build number

10.0.22504.1010

### Other Software

**Test Environment:**
OS: Windows 11 Version Dev (OS Build 22504.1010)
App: Windows Terminal Preview
Screen Reader: JAWS 2021

### Steps to reproduce

**Repro Steps:**
1. Open Windows Terminal.
2. Open Settings page using 'Ctr+,'.
3. Activate 'Actions' tab and then Add a new actions 'Set tab color' with shortcut key 'Ctrl + Shift + c'.
4. Open JAWS 2021 Screen Reader.
5. Navigate inside Terminal window.
6. Turn on Cursor mode using 'Insert + Z' and then try to read static/non-interactive/non-tab able content. 
7. Observe the issues.

**User Experience:**
JAWS Screen Reader users are impacted here as JAWS users are not able to read static/non-interactive/non-tab able content.

**Attachments:**
[JAWS Screen Reader Cursor mode does not work inside Terminal app..zip](https://github.com/microsoft/terminal/files/7782791/JAWS.Screen.Reader.Cursor.mode.does.not.work.inside.Terminal.app.zip)


### Expected Behavior

JAWS Cursor mode should work inside Terminal app.

### Actual Behavior

JAWS Screen Reader Cursor mode does not work inside Terminal app as result JAWS users are not able to read static/non-interactive/non-tab able content.

**Observation:** 
Issue does not repro with Narrator & NVDA as Scan mode work fine inside Terminal app.
Repository: terminal
Issue: [Terminal> Actions]: Keyboard Focus did not jump inside 'Add New Actions' pop-up when user activate 'Add new' button.
Labels: Issue-Bug,Area-Accessibility,Product-Terminal,Priority-3,HCL-E+D,A11yWCAG,HCL-WindowsTerminal,A11yCO,A11ySev3

### Windows Terminal version

1.12.3472.0

### Windows build number

10.0.22504.1010

### Other Software

**Test Environment:**
OS: Windows 11 Version Dev (OS Build 22504.1010)
App: Windows Terminal Preview
Screen Reader: Narrator

### Steps to reproduce

**Repro Steps:**
1. Open Windows Terminal.
2. Open Settings page using 'Ctr+,'.
3. Activate 'Actions' tab and then activate 'Add new' button.
4. Observe the issue.

**User Experience:**
Screen Reader users UX will not be good as they are not able to know what happen when they activate a control.

**Guideline Reference:**
https://www.w3.org/WAI/WCAG21/Understanding/focus-order

**Attachments:**
[Keyboard Focus did not jump inside 'Add New Actions' pop-up when user activate 'Add new' button..zip](https://github.com/microsoft/terminal/files/7783119/Keyboard.Focus.did.not.jump.inside.Add.New.Actions.pop-up.when.user.activate.Add.new.button.zip)

### Expected Behavior

Keyboard Focus should jump inside 'Add New Actions' pop-up when user activate 'Add new' button.

### Actual Behavior

Keyboard Focus did not jump inside 'Add New Actions' pop-up when user activate 'Add new' button.
Repository: terminal
Issue: [Terminal]: Screen Reader does not announce Pop-up name when its focus first jump inside pop-up.
Labels: Help Wanted,Issue-Bug,Area-Accessibility,Product-Terminal,Priority-3,HCL-E+D,A11yWCAG,HCL-WindowsTerminal,A11yCO,A11ySev3

### Windows Terminal version

1.12.3472.0

### Windows build number

10.0.22504.1010

### Other Software

**Test Environment:**
OS: Windows 11 Version Dev (OS Build 22504.1010)
App: Windows Terminal Preview
Screen Reader: Narrator

### Steps to reproduce

**Repro Steps:**
1. Open Windows Terminal.
2. Open Narrator using 'Win + Ctrl + Enter' keys.
3. Press 'Ctrl + Shift + space' keys to open new tab Dropdown pop-up, Observe the issues.
4. Press 'Ctrl + Shift + r' keys to open Set tab color pop-up, Observe the issues.

**User Experience:**
Screen Reader users UX will not be good as they will not be able to know the purpose pop-ups.

**Guideline Reference:**
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships

**Attachments:**
[Screen Reader does not announce Pop-up name when its focus first jump inside pop-up.zip](https://github.com/microsoft/terminal/files/7783133/Screen.Reader.does.not.announce.Pop-up.name.when.its.focus.first.jump.inside.pop-up.zip)

### Expected Behavior

Screen Reader announces Pop-up name when its focus first jumps inside 'New Tab Dropdown' & 'Set tab color' pop-up.
i.e. When user open 'New Tab Dropdown' using 'Ctrl + Shift + space' using Screen Reader should announce 'New Tab Dropdown pop-up window ....' and When user open 'Reset tab color' using 'Ctrl + Shift + r' using Screen Reader should announce 'Set tab Color pop-up window....'
 
### Actual Behavior

Screen Reader does not announce Pop-up name when its focus first jumps inside 'New Tab Dropdown' & 'Set tab color' pop-up.

**Observation:** Same issue repro with NVDA and JAWS Screen Reader.
Repository: terminal
Issue: [Terminal]: Screen Reader does not announce Confirmation message after actions executed successfully.
Labels: Issue-Bug,Area-Accessibility,Product-Terminal,Priority-3,HCL-E+D,A11yWCAG,HCL-WindowsTerminal,A11yCO,A11ySev3

### Windows Terminal version

1.12.3472.0

### Windows build number

10.0.22504.1010

### Other Software

**Test Environment:**
OS: Windows 11 Version Dev (OS Build 22504.1010)
App: Windows Terminal Preview
Screen Reader: Narrator

### Steps to reproduce

**Repro Steps:**
1. Open Windows Terminal.
2. Open Settings page using 'Ctr+,'.
3. Activate 'Actions' tab.
4. Open Narrator using 'Win + Ctrl + Enter' keys.
5. Perform all available actions present inside 'Actions' tab. 
6. Observe the issues.

**User Experience:**
Screen Reader users UX will not be good as they will not be able to know whether the actions performed successfully or not.

**Guideline Reference:**
EN 301 549 V3.2.1: 11.5.2.15 Change notification

**Attachments:**
[Screen Reader does not announce Confirmation message after actions executed successfully..zip](https://github.com/microsoft/terminal/files/7783208/Screen.Reader.does.not.announce.Confirmation.message.after.actions.executed.successfully.zip)

### Expected Behavior

 Screen Reader announce Confirmation message after any actions executed successfully.
i.e. When users reset tab color, Screen Reader should announce 'Tab Color reset successfully'

### Actual Behavior

 Screen Reader does not announce Confirmation message after actions executed successfully. Issue repro with all available actions present inside Actions tab page. 

**Observation:** Issue also repro with NVDA and JAWS Screen Reader.
Repository: opencv
Issue: "make install": the build starts all over again
Labels: category: build/install,category: gpu/cuda (contrib)

##### System information (version)
<!-- Example
- OpenCV => 4.2
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2017
-->

- OpenCV => 4.5.4
- Operating System / Platform => ubuntu18.04
- Compiler => gcc 7.5
- CUDA => 11.1
- CUDANN => 8.0
- ffmpeg => 4.4
- GPU => 2080Ti
- Nvidia Driver => 455.45

##### Detailed description

<!-- your description -->
when building opencv with gpu vidoe decoder from the source, upon invoking "make install", the build starts all over again.
my steps:
cmake [PARAMS] ..
make -j$(nproc) 
make install

when using "make install VERBOSE=1", the log is:
/usr/local/bin/cmake -S/opt/opencv/opencv -B/opt/opencv/opencv/build --check-build-system CMakeFiles/Makefile.cmake 0
Re-run cmake file: Makefile older than: modules/videostab/CMakeFiles/cuda_compile_1.dir/src/cuda/cuda_compile_1_generated_global_motion.cu.o.depend
...

I guess that some new objects are updated after "make -j$(nproc) ", but i don't know why.


##### Steps to reproduce

<!-- to add code example fence it with triple backticks and optional file extension
    ```.cpp
    // C++ code example
    ```
 or attach as .txt or .zip file
-->
cmake cmdline:
```bash
cmake -D BUILD_SHARED_LIBS=ON \
            -D CMAKE_BUILD_TYPE=RELEASE \
            -D CMAKE_INSTALL_PREFIX=/usr/local \
            -D OPENCV_ENABLE_NONFREE=ON \
            -D WITH_CUDA=ON \
            -D ENABLE_FAST_MATH=1 \
            -D CUDA_FAST_MATH=1 \
            -D WITH_CUBLAS=1 \
            -D INSTALL_C_EXAMPLES=OFF \
            -D INSTALL_PYTHON_EXAMPLES=OFF \
            -D BUILD_NEW_PYTHON_SUPPORT=ON \
            -D BUILD_opencv_python3=ON \
            -D HAVE_opencv_python3=ON \
            -D PYTHON_DEFAULT_EXECUTABLE=/usr/bin/python3.6 \
            -D OPENCV_GENERATE_PKGCONFIG=ON \
            -D OPENCV_EXTRA_MODULES_PATH=/opt/opencv/opencv_contrib/modules \
            -D CUDA_nvcuvid_LIBRARY=/opt/Video_Codec_SDK/Video_Codec_SDK_11.0.10/Lib/linux/stubs/x86_64/libnvcuvid.so \
            -D BUILD_EXAMPLES=OFF \
            -D BUILD_TESTS=OFF \
            -D BUILD_PERF_TESTS=OFF \
            -D WITH_NVCUVID=ON \
            -D WITH_FFMPEG=ON \
            -D WITH_OPENGL=OFF \
            -D WITH_GTK=OFF \
            -D BUILD_opencv_cudacodec=ON ..
```
Repository: terminal
Issue: [Terminal >Actions]: Screen Reader users are not able to know the purpose of Actions List inside Actions tab page.
Labels: Issue-Bug,Area-Accessibility,Product-Terminal,Priority-3,HCL-E+D,A11yWCAG,HCL-WindowsTerminal,A11yCO,A11ySev3

### Windows Terminal version

1.12.3472.0

### Windows build number

10.0.22504.1010

### Other Software

**Test Environment:**
OS: Windows 11 Version Dev (OS Build 22504.1010)
App: Windows Terminal Preview
Screen Reader: Narrator

### Steps to reproduce

**Repro Steps:**
1. Open Windows Terminal.
2. Open Settings page using 'Ctr+,'.
3. Open Narrator using 'Win + Ctrl + Enter' keys.
4. Activate 'Actions' tab and then navigate to actions list using tab/arrow keys and observe the issue.

**User Experience:**
Screen Reader users UX will not be good as they are not able to know the purpose of list item when they navigate to them.

**Guideline Reference:**
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships

**Attachments:**
[Screen Reader users are not able to know the purpose of Actions List inside Actions tab page..zip](https://github.com/microsoft/terminal/files/7783331/Screen.Reader.users.are.not.able.to.know.the.purpose.of.Actions.List.inside.Actions.tab.page.zip)


### Expected Behavior

Screen Reader users should be able to know the purpose of Actions List inside Actions tab page.
i.e. When user first time jumps to 'Actions' list item control, Screen Reader should announce something like this 'Actions List item, Use these actions to perform available functionality inside Terminal Text Area....'

### Actual Behavior

Screen Reader users are not able to know the purpose of Actions List inside Actions tab page.

**Observation:** Same issue repro with NVDA and JAWS Screen Reader.
Repository: storybook
Issue: "MetaDataError: CSF missing default export" on *.stories.tsx files which has companion .mdx files
Labels: bug,csf

**Describe the bug**
Using SB 6.4.9 and feature flag storyStoreV7: true.
In the terminal (running server) I get a lot of info Skipping <path-to-file> NoMetaError: CSF: missing default export <path-to-file> (line 1, col 0 . These  *.stories.tsx files, that gets these NoMetaError, have all a companion mdx file, ex. Button.stories.tsx & Button.stories.mdx.
In this case the .tsx files should not have export default { title: 'Button', ...}  according to documentation.

**To Reproduce**
See description.

**System**
Environment Info:

  System:
    OS: macOS 12.0.1
    CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
  Binaries:
    Node: 14.17.6 - ~/.nvm/versions/node/v14.17.6/bin/node
    Yarn: 1.22.15 - ~/.yarn/bin/yarn
    npm: 7.24.2 - ~/Work/develop/spx-react-ui/node_modules/.bin/npm
  Browsers:
    Chrome: 96.0.4664.110
    Firefox: 93.0
    Safari: 15.1
  npmPackages:
    @storybook/addon-actions: ^6.4.9 => 6.4.9 
    @storybook/addon-docs: ^6.4.9 => 6.4.9 
    @storybook/addon-essentials: ^6.4.9 => 6.4.9 
    @storybook/addon-interactions: ^6.4.9 => 6.4.9 
    @storybook/addon-links: ^6.4.9 => 6.4.9 
    @storybook/addons: ^6.4.9 => 6.4.9 
    @storybook/core-events: ^6.4.9 => 6.4.9 
    @storybook/react: ^6.4.9 => 6.4.9 
    @storybook/testing-library: 0.0.7 => 0.0.7 
    @storybook/theming: ^6.4.9 => 6.4.9
Repository: excalidraw
Issue: Feature request: select all objects inside an enclosing shape
Labels: enhancement,discussion

Often, I need to select all objects that lie within an enclosing shape like a rectangle or ellipse. To do that, I usually need to zoom out so that the whole enclosing shape completely visible and small enough to easily select by dragging the mouse or trackpad. Then I do the selection, either move or group and zoom in again.
It would be nice to have a menu item and / or a keyboard shortcut to select all the objects that lie completely inside the enclosing shape.
Repository: PowerToys
Issue: Task manager has gaps when using fancy zones
Labels: Issue-Bug,Product-FancyZones,Needs-Triage,Needs-Team-Response,Area-App Compat

### Microsoft PowerToys version

v0.51.1

### Running as admin

- [X] Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

I would create a fancy zone layout and would use it as normal but when i try to  snap task manager into one of the sections it always seems to produce a gap on the edges of the screen (the yellow space)(this only seems to be happening to task manager)

![A3Zo7Kp](https://user-images.githubusercontent.com/75196287/147543725-05e1563f-9c81-4934-94b8-fb1fab58842f.png)



### ✔️ Expected Behavior

I was expecting there to be no gaps

![gVCBdIE](https://user-images.githubusercontent.com/75196287/147544178-8946df65-3a75-4032-b45c-bc4a4d6b2ac2.png)



### ❌ Actual Behavior

I got a gap when snapping task manager

![A3Zo7Kp](https://user-images.githubusercontent.com/75196287/147544226-dd213f89-f1f1-40fa-8a79-a49fdd2fe357.png)



### Other Software

_No response_
Repository: vscode
Issue: Use modern (CSS color level 4) syntax for colors in the color picker
Labels: feature-request,editor-color-picker

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

When converting colors using the color picker, the old comma-based syntax is used:

![image](https://user-images.githubusercontent.com/261509/147552254-feb09a98-fbee-494c-ba33-7d86ca371349.png)
(it should also show `hsl` here, at the top of the picker, not `rgba`)

Please update the picker to use the modern (CSS color level 4) syntax for colors.

With regard to the exact syntax, I agree with these suggestions from `@mathiasbynens`:

> - consider being opinionated w.r.t. how to represent alpha values. IMHO using percentage notation is most readable, as it clarifies the range: e.g. 70% vs 0.7
> - consider being opinionated about using the deg suffix where applicable, e.g. in the first parameter for hsl() and the last non-alpha parameter for lch(). Again, because this clarifies that the range lies between 0-360.

i.e. Use percentages for alpha, and always include the `deg` suffix.

This also matches the syntax displayed in Chrome developer tools.
Repository: excalidraw
Issue: Make text container padding adapt to size
Labels: discussion,Text containers
Repository: pytorch
Issue: The same code can not be reproduced on multiple GPUs with dataparallel
Labels: triaged,module: data parallel,Stale

environment:
torch1.2
Tesla V100-SXM2
Fixed all random seeds
```
def seed_torch(seed=21):
    random.seed(seed)
    os.environ['PYTHONHASHSEED'] = str(seed)
    np.random.seed(seed)
    torch.manual_seed(seed)
    torch.cuda.manual_seed(seed)
    torch.cuda.manual_seed_all(seed)
    torch.backends.cudnn.deterministic = True
    torch.backends.cudnn.benchmark = False
    torch.backends.cudnn.enabled = False
```
The same code can be reproduced on a single GPU, but it cannot be reproduced when using dataparallel to run the code on multiple GPUs. This non-reproducibility generally begins to appear in the loss of the second batch, and at the beginning, there was only a difference in 4 digits after the decimal point.

The following figure records the result of loss when the same program is trained on two GPUs
![image](https://user-images.githubusercontent.com/12276152/147681105-5cfbee1b-5454-4b27-a099-c6b7adcaea29.png)
Repository: vscode
Issue: VS Code fails to open files from relative paths
Labels: bug,quick-open

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.63.2 and going back at least a year or two
- OS Version: at least Ubuntu 18.04 and Windows 10 and 11

Steps to Reproduce:

1. Open a file which contains a parent, `../`, directory from either the "Go to File..." (Ctrl-P) option or click on such a path as part of compiler output.
2. Observe that the file exists but that VS Code reports "No matching results"
3. Normalise the path so that the `../` is gone. The file can now be opened by VS Code, even though the physical path is unchanged.

Note that I opened [an issue](https://github.com/microsoft/vscode/issues/113322) as a feature request but have since determined that this is plain broken. (IIRC it works in other tools such as CLion.) Despite [a request to reconsider the status of the issue](https://github.com/microsoft/vscode/issues/113322#issuecomment-791901383), it remains closed and various open file features remain broken.

Thanks