sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Semantic colorization customization applied even if `editor.semanticTokenColorCustomizations.enabled` is false.
Labels: bug,semantic-tokens

Moving this over from the cpptools repo: https://github.com/microsoft/vscode-cpptools/issues/11311

<!-- ⚠️⚠️ 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. -->
Version: 1.86.0 (user setup)
Commit: 05047486b6df5eb8d44b2ecd70ea3bdf775fd937
Date: 2024-01-31T10:28:19.990Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Windows_NT x64 10.0.22631

(This example uses the C/C++ Extension, though the issue would apply to any scenario involving semantic tokens).
```cpp
namespace myNamespace
{
    void myFunction()
    {}
}


int main()
{
    myNamespace::myFunction();
}
```
Settings to use:
```json
    "C_Cpp.enhancedColorization": "enabled",
    "editor.semanticTokenColorCustomizations": {
        "enabled": false,
        "rules": {
            "namespace": "#f700ff"
        }
    }
```

In the above example, `enabled` is set to false, yet the colorization is still applied.

Steps to Reproduce:

1. Use sample code.
2. use provided settings.
3. Note: run command "Developer: Inspect Tokens and Scopes" to see colorization info of a symbol.

**Actual result:**
![image](https://github.com/microsoft/vscode-cpptools/assets/38734287/5af784bd-e246-4379-b63e-071b451f67a4)

**Expected result:**
![image](https://github.com/microsoft/vscode-cpptools/assets/38734287/6b1afc37-6529-4b71-a4d9-9aa59a964baa)
Repository: TypeScript
Issue: mapped type with remapped keys unexpectedly widens type
Labels: Needs Investigation,Has Repro

### 🔎 Search Terms

keyof, string, record

### 🕗 Version & Regression Information

- This changed between versions 4.4.4 and 4.5.5



### ⏯ Playground Link

_No response_

### 💻 Code

```ts repro
type R = { [K in keyof Record<string,unknown> as K]: unknown; };
//   ^?
type K = keyof R;
//   ^?
let s:string = "a" as K
```

[Workbench Repro](https://www.typescriptlang.org/dev/bug-workbench/?noErrorTruncation=true&ts=4.5.5#code/C4TwDgpgBASlC8UDeUDaBpKBLAdlA1hCAPYBmsEAxsQE4AmAPAM7A24DmANAK4747EA7jgB8UAIZMo6ALoAuKL35CcAbigBfVQCgA9LqiGAegH5toSNIQEiZWDv2Gop7QBsIwKEzks2OdtYAROKBElLoQA)

### 🙁 Actual behavior

`keyof R` is `string | number`.

### 🙂 Expected behavior

`keyof R` is `string`.

### Additional information about the issue

_No response_
Repository: vscode
Issue: Disable "Move" section in the Quick Fix panel
Labels: feature-request,editor-code-actions

<!-- ⚠️⚠️ 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. -->

<!-- Describe the feature you'd like. -->

Sometimes it takes VS Code a while to catch up with the latest Quick Actions and until they are provided by TypeScript and others. "Move to a new file" is the default. I often quickly type `cmd+.` twice to accept the first action, like auto-importing something from another module. However, quite often I am often issuing an action faster than the quick actions can be populated and I end up in a confused state where a random new file like "MyReactComponent.1.tsx" is created or an empty function definition is put at the bottom of my file.

The UX could be better since it unexpectedly reorders the options (from a user perspective). One solution could be to not pick any Move option when quickly pressing `cmd+.` twice, but the most consistent solution should be allowing to disable the "Move" section in quick actions altogether, since I absolutely never use it and it doesn't work the way I'd expect. If it can be disabled, ideally VS Code just does nothing when there are no other actions available.

![CleanShot 2024-02-02 at 09 05 30@2x](https://github.com/microsoft/vscode/assets/13352/c4674033-ed6f-4bc2-b453-82b2a3e38c61)
Repository: stable-diffusion-webui
Issue: [Bug]: Image generation freezes and kills kernel at the beginning if upscale model is changed (related to using --medvram-sdxl) Linux/possible memory leak(?)
Labels: bug-report

### Checklist

- [ ] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

When I run on --medvram-sdxl in the args, I am able to generate one image with the settings as they are, but as soon as I change the upscaler and try to generate another image it freezes at step one and after a while the kernel dies. it is also a pain to get it back on. 

It looks like this issue is related to a new model being loaded, which I assume upscaler counts as a "model".

I apparently need to use the --medvram-sdxl to generate 1024x1024 images with x2 upscale otherwise I get cuda out of memory error on a 15gb VRAM GPU. (I would think I should be able to generate such images with 15gb of vram)
I did tried lbtcmalloc but the error repeated. Everything apparently works normally if I don't use --medvram-sdxl --lowvram and similars.
I've seen in previous posts what appears to be similarly related or the same issue for many people but I couldn't really find any solution unfortunately.

I also did tried other browsers, no difference. 

HELP!

### Steps to reproduce the problem

The error happened using SDXLBase_Notebook_1.9.ipynb for Amazon Sagemaker/on sagemaker/linux os etc
I basically did a clean install and repeated that etc 

### What should have happened?

I should be able to generate images with --medvram-sdxl without it killing the kernel real quickly...

### What browsers do you use to access the UI ?

Google Chrome

### Sysinfo

free sagemaker jupyter notebook, linux etc

### Console logs

```Shell
not abailable right now
```


### Additional information

_No response_
Repository: langchain
Issue: Callback for on_llm_new_token should be invoked before the token is yielded by the model
Labels: help wanted,good first issue,🤖:bug,stale,Ɑ:  models,🔌: openai

### Privileged issue

- [X] I am a LangChain maintainer, or was asked directly by a LangChain maintainer to create an issue here.

### Issue Content

## Goal 

Improve streaming in LangChain for chat models / language models.

## Background

Many chat and language models implement a streaming mode in which they stream tokens one at a time.

LangChain has a callback system that is useful for logging and important APIs like "stream", "stream_log" and "stream_events".

Currently many models incorrectly yield the token (chat generation) before invoking the callback.

## Acceptance criteria

For a PR to be accepted and merged, the PR should:

- [ ] Fix the code to make sure that the callback is called before the token is yielded
- [ ] Link to this issue
- [ ] Change ONE and only ONE model
- [ ] FIx sync and async implementation if both are defined

## Example PR

Here is an example PR that shows the fix for the OpenAI chat model:

https://github.com/langchain-ai/langchain/pull/16909

## Find models that need to be fixed


The easiest way to find places in the code that may need to be fixed is using git grep

```bash
git grep -C 5  "\.on_llm_new"
```

Examine the output to determine whether the callback is called before the token is yielded (correct) or after (needs to be fixed).
Repository: material-ui
Issue: [base-ui][Transitions] Exit transition is broken since v5.0.0-beta.33 in the Popup
Labels: bug 🐛,component: transitions,package: base-ui,regression

### Steps to reproduce

Link to live example: [(required)](https://mui.com/base-ui/react-transitions/)

Steps:
1. Click any of the "Show popup" buttons
2. Click "Hide popup"
3. Notice the exit transition is missing

The previous working example can be found by cloning the repo and checking out  5d7c4e26a4973a3a80bf5f8a9a8ea14f89554fe0 (one commit before #40524) and starting the documentation

Recordings:
v5.0.0-beta.32 (working)
![popup-exit-transition](https://github.com/mui/material-ui/assets/5557143/af701990-4d1b-4f19-babb-d3e83e220ceb)

v5.0.0-beta.33 (broken)
![popup-exit-transition-bug](https://github.com/mui/material-ui/assets/5557143/1a161e93-5fc4-4e83-b066-b2544a63b299)




### Current behavior

Exit transition it not being shown

### Expected behavior

Exit transition should be shown

### Context

_No response_

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: base-ui, transition, exit, popup
Repository: godot
Issue: ThemeDB.get_default_theme() not affect some type on runtime.
Labels: bug,confirmed,topic:gui

### Tested versions

v4.2.1.stable.mono.official [b09f793f5]

### System information

Godot v4.2.1.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 5GB (NVIDIA; 31.0.15.3623) - AMD Ryzen 9 3900X 12-Core Processor (24 Threads)

### Issue description

I'm setup a theme like this:
![image](https://github.com/godotengine/godot/assets/35988767/0cd2612b-ef62-45ec-949e-c349e02cfccc)
everything work correct (the font_color and panel_bg_color).
but when I setup the ThemeDB.get_default_theme(), it not affect the panel_bg_color.
![image](https://github.com/godotengine/godot/assets/35988767/810939e1-71cb-4864-aa36-f079ea1d05fe)

It not make sense. I don't know why it can affect the font_color but can't affect the bg_color. this confuse me.

### Steps to reproduce

just test the MRP


### Minimal reproduction project (MRP)

[ThemeTest.zip](https://github.com/godotengine/godot/files/14132909/ThemeTest.zip)
Repository: storybook
Issue: [Bug]: MDX: Setting overrides on the Markdown block disables all default overrides
Labels: bug,mdx,block: other,sev:S3

### Describe the bug

Hi, I ran into an issue when setting the overrides option on the Markdown block.

Markdown block:
https://storybook.js.org/docs/writing-docs/doc-blocks#markdown

### To Reproduce

## sample code
```mdx
import { Meta, Markdown } from '@storybook/blocks'

export const sample = `
\`\`\`typescript
console.log('This is a code block example')
console.log('This is a code block example')
\`\`\`

[anchor example](https://example.com/)
`

export const overrides = {
  // override the anchor target
  a: ({ href, children }) => {
    return (
      <a href={href} target="_blank">
        {children}
      </a>
    )
  }
}

<Meta title="Markdown block override" />

## Default
<Markdown>{sample}</Markdown>

## Defaults are disabled when overrides are set
<Markdown options={{ overrides }}>{sample}</Markdown>
```

<img src="https://github.com/storybookjs/storybook/assets/45122432/d4002fa2-94d5-4f7a-b65d-00d95ced0e24" width="500" />


### System

```bash
System:
    OS: Linux 6.3 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
    CPU: (8) x64 Intel(R) Core(TM) i7-1060NG7 CPU @ 1.20GHz
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 21.2.0 - ~/.nvm/versions/node/v21.2.0/bin/node
    Yarn: 1.22.21 - ~/.nvm/versions/node/v21.2.0/bin/yarn <----- active
    npm: 10.2.3 - ~/.nvm/versions/node/v21.2.0/bin/npm
  Browsers:
    Chrome: 120.0.6099.129
  npmPackages:
    @storybook/addon-essentials: ^7.6.12 => 7.6.12 
    @storybook/angular: ^7.6.12 => 7.6.12 
    @storybook/blocks: ^7.6.12 => 7.6.12 
    @storybook/jest: ^0.2.3 => 0.2.3 
    @storybook/mdx2-csf: ^1.1.0 => 1.1.0 
    @storybook/testing-library: ^0.2.2 => 0.2.2 
    msw-storybook-addon: 2.0.0--canary.122.06f0c92.0 => 2.0.0--canary.122.06f0c92.0 
    storybook: ^7.6.12 => 7.6.12
```


### Additional context

I think it would be appropriate for this code to be as follows,

https://github.com/storybookjs/storybook/blob/1807f05b65db161f6420b6c952bc006580572032/code/ui/blocks/src/blocks/Markdown.tsx#L38-L47

```typescript
      options={{
        forceBlock: true,
        ...props?.options,
        overrides: {
          code: CodeOrSourceMdx,
          a: AnchorMdx,
          ...HeadersMdx,
          ...props?.options?.overrides,
        },
      }}
```
Repository: vscode
Issue: Allow show menu bar inside of Custom Title Bar, when Title Bar Style is native
Labels: feature-request,titlebar

<!-- ⚠️⚠️ 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. -->

<!-- Describe the feature you'd like. -->
With VSCode 1.86 we can enable 'Custom Title Bar' without a 'Title Bar Style=custom', but application menu uses own space in this case:
![image](https://github.com/microsoft/vscode/assets/12231048/45cbc0cb-601d-4ff3-92da-1dd48faee8aa)

It would be great if the application menu uses spaces in left part of Custom Title Bar, like with 'Title Bar Style=custom':
![image](https://github.com/microsoft/vscode/assets/12231048/33d16392-4384-43b6-b9b6-ac96bc5aef40)
Repository: godot
Issue: Bad Stuttering - AMD Radeon RX 580
Labels: topic:rendering,needs testing,performance

### Tested versions

- Tested in 4.2.1.stable

### System information

Godot v4.2.1.stable - Windows 10.0.22621 - Vulkan (Forward+) - dedicated Radeon RX 580 Series (Advanced Micro Devices, Inc.; 31.0.21910.5) - Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 Threads)

### Issue description

When I'm in the editor the framerate is a consistent 120-130 FPS but when I get in-game it stutters every 2 seconds or so after around 2-3 runs. I tested with any scene and this happens everywhere. This may be caused by AMD but I do not know. There are no physics used in this project.

### Steps to reproduce

N/A

### Minimal reproduction project (MRP)

N/A
Repository: kubernetes
Issue: kubelet started multi-containers for static pods when EventedPLEG is enabled
Labels: kind/bug,priority/important-soon,sig/node,triage/accepted

### What happened?

See context in https://github.com/kubernetes/kubernetes/issues/122721 and we disabeld it in presubmit and periodic CIs. 

> We discussed this in sig-node today. We are temporarily going to not block on these failures to unblock the current release but will target fixing this issue as a priority before the next minor release.

Discussion context about this bug in slack is https://kubernetes.slack.com/archives/C0BP8PW9G/p1706638623162379?thread_ts=1706055745.168469&cid=C0BP8PW9G with @mrunalp and @dchen1107. 

### What did you expect to happen?

Static Pods should be started normally when EventedPLEG is enabled.
- revert to alpha due to this bug: https://github.com/kubernetes/kubernetes/pull/122697

### How can we reproduce it (as minimally and precisely as possible)?

It is observed in alpha CIs like #122721.

### Anything else we need to know?

EventedPLEG has a known issue: https://github.com/kubernetes/kubernetes/issues/121349, and it will cause static pod startup failure(most time)


> I am trying to see why do we need to restart the container if it is in created state even in case of Generic PLEG? what happens if you make the change in this PR for ContainerStateCreated also applicable to the Generic PLEG?
> 
> https://github.com/kubernetes/kubernetes/pull/122737/files#diff-cb70f01a3ac982d9bd1fda913788b2ef7d9862cf6392204f6db00f3cb2292813R90
> 
> Looks like it was introduced with this PR -
> https://github.com/kubernetes/kubernetes/commit/9fa1ad29fd4df650f451522970908869b8199bf3
> 
> But I am not sure if this assumption, https://github.com/kubernetes/kubernetes/commit/9fa1ad29fd4df650f451522970908869b8199bf3#diff-e81aa7518bebe9f4412cb375a9008b3481b19ec3e851d3187b3021ee94148f0dR1214-R1219 is true.
> 
> In the kubelet you can clearly see [create container](https://github.com/kubernetes/kubernetes/blob/c55848a7246a0283be9b78c1b15bbeb922662a17/pkg/kubelet/kuberuntime/kuberuntime_container.go#L254) and [start container](https://github.com/kubernetes/kubernetes/blob/c55848a7246a0283be9b78c1b15bbeb922662a17/pkg/kubelet/kuberuntime/kuberuntime_container.go#L268) are two distinct steps.

@harche 's comments in https://github.com/kubernetes/kubernetes/issues/122721#issuecomment-1915517164.

Other related Issues about EventedPLEG:
- https://github.com/kubernetes/kubernetes/issues/122132
- #121003 
- #120140
Repository: flutter
Issue: tool : proposal : command to allow the user to generate commonly used file formats in a similar way to NestJS.Generative
Labels: c: new feature,tool,c: proposal,team-tool

### Use case

I feel like file structure and adding new components to the app is cumbersome. I presently have a heavy background in frameworks like Angular and NestJS. I feel like Flutter could inspire itself from their cli to reduce devs having to write boilerplate code.
I'm very new to Flutter, but it's the first thing I noticed starting out.

### Proposal

My proposed solution would be integrating in the official cli a generate (g) command allow the user to generate commonly used file formats in a similar way to NestJS.

I believe a package that could kinda do that exists, [mason](https://pub.dev/packages/mason). The issue #77104  is also kinda similar. But I feel they both differ in intent. I feel like their brick/template idea is more for complete part of an app then to just prepare "component".

Thank you for your time
Repository: neovim
Issue: Netrw can't properly open symlinks with netrw_liststyle=3
Labels: bug-vim,netrw

### Problem

When opening a symlink with netrw and netrw_liststyle=3, the path of the file will be FILENAME/FILENAME instead of FILENAME.

### Steps to reproduce

```sh
mkdir foo && echo "Hello from bar" > foo/bar
ln -s foo/bar .
cat <<EOF > min.vim
let netrw_liststyle=3
set nocompatible   " needed for vim
filetype plugin on " needed for vim
EOF
nvim --clean -u min.vim .
```

Now try to open bar. Netrw will try to open bar/bar which obviously doesn't exist

### Expected behavior

Open bar

### Neovim version (nvim -v)

v0.9.4

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

yes, vim 9.0.2116

### Operating system/version

NixOS

### Terminal name/version

XTerm(388)

### $TERM environment variable

xterm

### Installation

NixPkgs
Repository: rust
Issue: suggest mut removal sometimes for static mut ref lint/error
Labels: A-diagnostics

Since #117556 we now lint for code like ([playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=62065b21fdf08aab3eb8ad6a069aaeea)):

```rust
use std::sync::atomic::AtomicI32;
use std::sync::Mutex;

static mut X: AtomicI32 = AtomicI32::new(1);

static mut Y: Mutex<usize> = Mutex::new(0);

fn foo() {
    unsafe {
        let _x = &X;
        let _y = &Y;
    }
}
```

gives:

```
warning: shared reference of mutable static is discouraged
  --> src/lib.rs:12:18
   |
12 |         let _x = &X;
   |                  ^^ shared reference of mutable static
   |
   = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
   = note: reference of mutable static is a hard error from 2024 edition
   = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause undefined behavior
   = note: `#[warn(static_mut_ref)]` on by default
help: shared references are dangerous since if there's any kind of mutation of that static while the reference lives, that's UB; use `addr_of!` instead to create a raw pointer
   |
12 |         let _x = addr_of!(X);
   |                  ~~~~~~~~~~~

warning: shared reference of mutable static is discouraged
  --> src/lib.rs:13:18
   |
13 |         let _y = &Y;
   |                  ^^ shared reference of mutable static
   |
   = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
   = note: reference of mutable static is a hard error from 2024 edition
   = note: mutable statics can be written to by multiple threads: aliasing violations or data races will cause undefined behavior
help: shared references are dangerous since if there's any kind of mutation of that static while the reference lives, that's UB; use `addr_of!` instead to create a raw pointer
   |
13 |         let _y = addr_of!(Y);
   |                  ~~~~~~~~~~~
```

It suggests using `addr_of` which is correct but it requires unsafe and we actually don't need it: we can just remove the `mut` here:

```rust
use std::sync::atomic::AtomicI32;
use std::sync::Mutex;

static X: AtomicI32 = AtomicI32::new(1);

static Y: Mutex<usize> = Mutex::new(0);

fn foo() {
    unsafe {
        let _x = &X;
        let _y = &Y;
    }
}
```

The lint message (error in 2024 edition) should suggest such removal of `mut` where possible.

The tough part is to find out where this is actually possible. With the right wording we might get away with a heuristic that doesn't recognize all cases correctly.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: three.js
Issue: WebXR: Make Depth sensing occlusion tunable
Labels: Enhancement

### Description

We have use cases in mrjs that require we dynamically un-occlude parts of the environment. 

Currently, without depth-sensing, we create plane meshes for the walls and disable colorWrite and set their rendering order to a value ahead of all other objects, then set visible to false when we want to see beyond them. see the screenshot below for an example

<img width="1120" alt="Screenshot 2024-01-30 at 4 13 14 PM" src="https://github.com/mrdoob/three.js/assets/19628643/d6b103bf-1fe6-4fcb-af5f-1d94e3e31c60">


We'd like to be able to benefit from the better body occlusion provided by depth-sensing, without inhibiting our ability to achieve the above. 

### Solution

An API to tune depth-sensing occlusion by distance. something like

```js
renderer.xr.depthSensing.near = 0.1
renderer.xr.depthSensing.far = 1
```

### Alternatives

provide depth-sensing data without enabling occlusion by default.

### Additional context

_No response_
Repository: pytorch
Issue: When concatenating empty variable with non-empty variable, I get CUDA error: illegal memory access encounter
Labels: triaged

### 🐛 Describe the bug

My model looks something like this:`

```
class Model(nn.Module):
    def __init__(self,n):
        super().__init__()
        a = torch.randn(n,5)
        self.a = nn.Parameter(a, requires_grad=True)
        
    def forward(self,x):
        B,D = x.shape
        expanded_a = a.unsqueeze(0).expand(B,-1,-1)
        ab = torch.cat([expanded_a,x], dim=1)
`       return ab
```

If I pass n=0 where constructing the model, then when I run "optimizer.step()", I get the illegal memory access error. But if n is not 0, there is no error.



### Versions

![image](https://github.com/pytorch/pytorch/assets/15025931/516aaf9a-e686-4b6a-ac29-3b3ae5d04765)