sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Terminal toggle size to content width lacks horizontal scroll bar
Labels: bug,terminal-layout

Repro:

1. `ls`
2. Size terminal narrow so lines wrap
3. Press alt+z

  ![Image](https://github.com/user-attachments/assets/1ea1f958-7356-4965-bc51-6fbefde976ac)
5. shift+wheel down

  ![Image](https://github.com/user-attachments/assets/cebaefbf-d0fd-4480-8d82-5a2c18720846)

🐛 there's no horizontal scroll bar (vertical scroll bar position is tracked in https://github.com/microsoft/vscode/issues/235776)
Repository: svelte
Issue: Svelte scoped global styles do not work
Labels: documentation

### Describe the bug

As discussed in this [closed feature request](https://github.com/sveltejs/svelte/issues/14578), the newly introduced scoped global styles do not work in most cases because of CSS specificity. 

Because of CSS specificity if an element has more classes than another then it takes precedence when being rendered. So if in one of my +page.svelte files I want to edit an element to make it work perfectly for that page I will usually add a class to it (in most of my pages I have special cases that need custom styles).
![image](https://github.com/user-attachments/assets/2a471aee-ed1c-4872-ac92-1fe7c7719250)
However as you can see my custom styles are being ignored in favour of the global styles from my +layout.svelte file.

I did try using ID's instead of classes to select the element and that does work in some cases, but would not work if I wanted to select the same class name that is called in the +layout.svelte file (without creating a second selector for every element).
![image](https://github.com/user-attachments/assets/3c47acdb-03f1-4d73-98f5-95af8f1932cd)

Also generally ID's are for javascript and classes for CSS, I have not used them in my design work for a long long time. It would also require an substantial amount of work to change all classes to ID's.

### Reproduction

Download this repository: https://github.com/Loizzus/SvelteScopedGlobalStylesIssue
npm i
npm run dev

### Logs

_No response_

### System Info

```shell
System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 AMD Ryzen 5 3600XT 6-Core Processor
    Memory: 14.93 GB / 31.91 GB
  Binaries:
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (130.0.2849.80)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    svelte: ^5.0.0 => 5.10.1
```


### Severity

annoyance
Repository: deno
Issue: Array.indexOf() returns -1 for negative integers which exist in arrays of length >= 48
Labels: upstream,v8

Version: Deno 2.1.3

poc:
```ts
for (let value = -2; value < 2; value++) {
  for (let fill = -2; fill < 2; fill++) {
    if (value == fill) continue;
    for (let i = 0; i < 3; i++) {
      const length = 5 * Math.pow(10, i);
      const index = Math.floor(length / 2);
      const array = new Array(length).fill(fill);
      array[index] = value;
      const indexOf = array.indexOf(value);
      console.log({ value, fill, length, index, indexOf });
    }
  }
}
```

when run under node with:
```sh
docker run -it node node
.editor
```
[copy and paste poc code above]
[ctrl-d]
the `index` and `indexOf` always correctly match

when run under deno with:
`docker run -it denoland/deno repl`
[copy and paste poc code above]
`indexOf` is -1 when the array is of length>=50 and we're searching for an item whose value is a negative integer

find the array size at which the bug occurs:
```ts
for (let length = 5; length <= 50; length++) {
  const index = Math.floor(length / 2);
  const array = new Array(length).fill(0);
  array[index] = -1;
  const indexOf = array.indexOf(-1);
  console.log({ length, index, indexOf });
}
```
this works as expected under node but starts getting indexOf===-1 at length 48 in deno.
Repository: electron
Issue: net.WebSocket
Labels: enhancement :sparkles:

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

Our application needs to supports web proxies. It also needs to open WebSocket connections from the main process.

The natural choice would be [the `net` module](https://www.electronjs.org/docs/latest/api/net) "uses Chromium's native networking library instead of the Node.js implementation, offering better support for web proxies." However, it only supports HTTP(S) requests; not WebSocket.

### Proposed Solution

[The `net` module](https://www.electronjs.org/docs/latest/api/net) should expose Chromium's WebSocket implementation like this:

```js
const { net } = require('electron')
new net.WebSocket(...)
```

### Alternatives Considered

I have been unable to find any alternative implementation that lets us open WebSocket connections from the main process and support all web proxies. I would also appreciate any advice on alternatives to the Electron `net` module.

I found https://github.com/jfromaniello/mac-ca and https://github.com/ukoloff/win-ca, but

* They are OS-specific. I would like to support all platforms supported by Electron.
* It's unclear to me whether this supports all web proxies. Is the only significant difference between the Node.js and Chromium network stacks their list of root CAs?

### Additional Information

I found [this previous issue](https://github.com/electron/electron/issues/8931) which is very similar. It was closed because "it will take a considerable amount of work since the net layer of chromium doesn't expose it directly as a part of URLRequest." 7.5 years later, perhaps this has changed?
Repository: TypeScript
Issue: Allow `interface extends object` syntax
Labels: Suggestion,In Discussion

### 🔍 Search Terms

interface extends object

### ✅ Viability Checklist

- [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [x] This wouldn't change the runtime behavior of existing JavaScript code
- [x] This could be implemented without emitting different JS based on the types of the expressions
- [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

I propose to allow the following syntax:
```typescript
interface MyInterface extends object {}
```

This would have identical semantics to the following (currently legal) syntax:

```typescript
type _object = object
interface MyInterface extends _object {}
```

Details:
1. No primitive may be assigned to such an interface or an intersection containing such an interface
2. This requirement is inherited by any extending interfaces

I'm requesting this feature mainly because it was the only pain-point mentioned in this [related issue](https://github.com/microsoft/TypeScript/issues/60582). To quote:

> No one is going to turn on this behavior if it means every time they write
> ```
> interface Person {
>   name: string
> }
> ```
> they actually need to write
> ```
> interface _PersonFields {
>   name: string;
> }
> type Person = object & _PersonFields;
> ```

Regardless of the outcome of that other issue however, it would be nice to be able to `extends object` without going through that kind of hassle.

### 📃 Motivating Example

A small usability improvement to allow interfaces to more easily declare that primitives cannot be assigned to them.

### 💻 Use Cases

1. What do you want to use this for? To avoid non-idiomatic verbosity
2. What shortcomings exist with current approaches? Non-idiomatic verbosity
3. What workarounds are you using in the meantime? Non-idiomatic verbosity
Repository: vscode
Issue: javascript output with </script> can close scripts
Labels: bug,notebook-output

### Applies To

- [x] Notebooks (.ipynb files)
- [ ] Interactive Window and\/or Cell Scripts (.py files with \#%% markers)

### What happened?

when the javascript output has a </script> closing tag, it appears to be able to close the script element which is used for running the javascript, so the remainder of the javascript and some of the internal code used to run/render the javascript output end up outside the script as just html

![Image](https://github.com/user-attachments/assets/62c762ab-de33-4a1f-970f-793b403e3ff7)
![Image](https://github.com/user-attachments/assets/fb03584d-4ce3-406b-a639-d8ac95f35cc5)

this happens both when running it the first time and also when viewing a notebook/cell which has already been run

also running multiple times will cause it to output multiple times

![Image](https://github.com/user-attachments/assets/b439ebf9-7c64-4883-aaee-54a9b218a127)


### VS Code Version

Version: 1.95.3 (Universal) Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813 Date: 2024-11-13T14:50:04.152Z (3 wks ago) Electron: 32.2.1 ElectronBuildId: 10427718 Chromium: 128.0.6613.186 Node.js: 20.18.0 V8: 12.8.374.38-electron.0 OS: Darwin arm64 24.1.0

### Jupyter Extension Version

v2024.10.0

### Jupyter logs

```shell
Visual Studio Code (1.95.3, undefined, desktop)
Jupyter Extension Version: 2024.10.0.
Python Extension Version: 2024.20.0.
Pylance Extension Version: 2024.12.1.
Platform: darwin (arm64).
Temp Storage folder ~/Library/Application Support/Code/User/globalStorage/ms-toolsai.jupyter/version-2024.10.0
No workspace folder opened.
22:32:11.797 [info] Starting Kernel (Python Path: ~/opt/anaconda3/bin/python, Conda, 3.9.13) for 'Untitled-1.ipynb' (disableUI=true)
22:32:14.185 [info] Process Execution: ~/opt/anaconda3/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
22:32:14.186 [info] Process Execution: ~/opt/anaconda3/bin/python -m ipykernel_launcher --f=/Users/~/Library/Jupyter/runtime/kernel-v30ee5b0816dd5f6d40229dbe1be4eff4731a31bec.json
    > cwd: /
22:32:14.214 [info] Process Execution: ~/opt/anaconda3/bin/python -m pip list
22:32:14.862 [info] Kernel successfully started
22:32:14.864 [info] Process Execution: ~/opt/anaconda3/bin/python /Users/~/.vscode/extensions/ms-toolsai.jupyter-2024.10.0-darwin-arm64/pythonFiles/printJupyterDataDir.py
```

### Coding Language and Runtime Version

Javascript

### Language Extension Version (if applicable)

_No response_

### Anaconda Version (if applicable)

_No response_

### Running Jupyter locally or remotely?

Local
Repository: neovim
Issue: build from source on Windows using CLion
Labels: build,documentation,platform:windows

### Problem

I find it very difficult to follow the building instructions.. 

I have CLion and Visual Studio 2022 installed and the options mentioned in the linked document do not correspond to what I see.

[BUILD.md](https://github.com/neovim/neovim/blob/master/BUILD.md)

### Expected behavior

It would be very helpful to develop one or more powershell scripts that will clone all necessary repositories and execute the building process automatically and review the provided instructions for Visual Studio and CLion.
Repository: rust
Issue: E0599: incorrect import suggestion for block-scoped trait
Labels: A-diagnostics,T-compiler

### Code

```Rust
fn main() {
    {
        trait Hello {
            fn hello(&self) {
                println!("hello world");
            }
        }
        impl<T> Hello for T {}
    }

    ().hello();
}
```

### Current output

```Shell
error[E0599]: no method named `hello` found for unit type `()` in the current scope
  --> src/main.rs:11:8
   |
4  |             fn hello(&self) {
   |                ----- the method is available for `()` here
...
11 |     ().hello();
   |        ^^^^^ method not found in `()`
   |
   = help: items from traits can only be used if the trait is in scope
help: trait `Hello` which provides `hello` is implemented but not in scope; perhaps you want to import it
   |
1  + use crate::main::Hello;
   |
```

### Desired output

```Shell
error[E0599]: no method named `hello` found for unit type `()` in the current scope
  --> src/main.rs:11:8
   |
4  |             fn hello(&self) {
   |                ----- the method is available for `()` here
...
11 |     ().hello();
   |        ^^^^^ method not found in `()`
   |
   = help: items from traits can only be used if the trait is in scope
help: trait `Hello` which provides `hello` is implemented in a block and cannot be used here
```

### Rationale and extra context

There is no way to import a block-scoped trait and it should not be suggested for import.

### Other cases

```Rust

```

### Rust Version

```Shell
> rustc --version --verbose
rustc 1.83.0 (90b35a623 2024-11-26)
binary: rustc
commit-hash: 90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf
commit-date: 2024-11-26
host: x86_64-unknown-linux-gnu
release: 1.83.0
LLVM version: 19.1.1
```

### Anything else?

_No response_
Repository: pytorch
Issue: We don't have test coverage for aarch64 (ARM64) bfloat16 feature (__ARM_FEATURE_BF16)
Labels: module: build,module: ci,triaged

### 🐛 Describe the bug

As demonstrated by #142370 and #142501, we have no builds that will catch compilation failures under `__ARM_FEATURE_BF16`, let alone running tests in this configuration.

### Versions

N/A

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: pytorch
Issue: DISABLED test_run_decompositions_preserve_handle (__main__.TestNumericDebugger)
Labels: oncall: quantization,triaged,module: flaky-tests,module: macos,skipped

Platforms: mac, macos

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_run_decompositions_preserve_handle&suite=TestNumericDebugger&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/34205786469).

Over the past 3 hours, it has been determined flaky in 9 workflow(s) with 18 failures and 9 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_run_decompositions_preserve_handle`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_quantization.py`

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel @msaroufim @clee2000 @wdvr @malfet @albanD
Repository: PowerToys
Issue: [Peek][PreviewPane] Support for .resx and .resw files
Labels: Idea-Enhancement,Help Wanted,Resolution-Fix Committed,Product-File Explorer,Product-Peek

Allow users to quickly preview resource files (.resx and .resw) in Peek and Explorer PreviewPane. Both are xml files and can be easy previewed in Monaco editor.
Repository: flutter
Issue: [Android] Modify sensitive content support implementation to use JNIgen
Labels: platform-android,framework,P2,team-android,triaged-android

The initial implementation of sensitive content support on Android (to address https://github.com/flutter/flutter/issues/150218) will be implemented with method channels. In the future, the plan is to convert the implementation to use JNIgen to avoid a possible race condition between marking a view as sensitive and displaying the view before it is marked by Flutter. This issue is to track that work.
Repository: flutter
Issue: [Android] Un-mark sensitive content when it is not visible on screen
Labels: platform-android,framework,P2,team-android,triaged-android

The initial implementation of sensitive content support on Android (to address https://github.com/flutter/flutter/issues/150218) will not include logic that detects whether or not a sensitive content widget is no longer visible, meaning a `View` may still be obscured when there is no longer sensitive content on screen. As a follow up to that initial implementation, then, there should be work to make sure that the screen is not obscured when there are no sensitive content widgets on screen to limit over-obscuring the screen as marking any one widget as sensitive will obscure the entire `FlutterView`.

To implement this, the following use cases must be considered:

- [ ] Scrolling: https://docs.flutter.dev/ui/widgets/scrolling
- [ ] Navigation: https://docs.flutter.dev/ui/navigation
- [ ] The [`Visibility`](https://api.flutter.dev/flutter/widgets/Visibility-class.html) widget
Repository: pytorch
Issue: torch.linalg.solve fails on CPU with multiple threads and batch dimension
Labels: triaged,module: mkl,module: linear algebra

Running this code 
```
import torch
torch.set_num_threads(2)
n = 151
xtx = torch.eye(n).unsqueeze(0).repeat(2,1,1).contiguous()
xty = torch.ones(2,n)
x = torch.linalg.solve(xtx, xty)
```

give this error
```
Intel MKL ERROR: Parameter 6 was incorrect on entry to SLASWP.

Intel MKL ERROR: Parameter 6 was incorrect on entry to SLASWP.

Intel MKL ERROR: Parameter 6 was incorrect on entry to SLASWP.

Intel MKL ERROR: Parameter 6 was incorrect on entry to SLASWP.

Intel MKL ERROR: Parameter 6 was incorrect on entry to SLASWP.

Intel MKL ERROR: Parameter 6 was incorrect on entry to SLASWP.
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
Cell In[12], line 6
      4 xtx = torch.eye(n).unsqueeze(0).repeat(2,1,1).contiguous()
      5 xty = torch.ones(2,n)
----> 6 x = torch.linalg.solve(xtx, xty)

RuntimeError: Pivots given to lu_solve must all be greater or equal to 1. Did you properly pass the result of lu_factor?
```

Smaller matrices, single threaded execution, no batch dimension makes the problem go away.

The identity matrix should not cause `linalg.solve` to fail.

### Versions

This happens in 2.5.0 and 2.5.1. Does not happen in 1.12.1. I didn't try other versions.

cc @jianyuh @nikitaved @pearu @mruberry @walterddr @xwang233 @Lezcano
Repository: terminal
Issue: [Group Policy] Process based enforcing single window mode
Labels: Issue-Feature,Product-Terminal,Needs-Tag-Fix,Area-GroupPolicy

Is it possible to add a policy that enforces single window mode based on the process that is executing the PowerShell script or CMD script.

Use case: We have a backup tool that uses multiple PowerShell scripts/commands to do the work. It would be cool if I can configure WT centralized to open the commands called from this specific process in single/independent window mode.

**Implementation details:**

A list of calling process names/paths that should execute their scripts/commands in single window mode.

Example:
- Calling process: `MyApp.exe`
- Command: `powershell.exe -File MyScript.ps1`
- Policy entry: MyApp.exe
Repository: vscode
Issue: "Clear All Output" is greyed out and doesn't clear execution count unless output is available
Labels: feature-request,notebook-commands

### Applies To

- [X] Notebooks (.ipynb files)
- [ ] Interactive Window and\/or Cell Scripts (.py files with \#%% markers)

### What happened?

Create a new cell in an *.ipynb.
run an import statement, the execution count increments.
**expected** that this execution statement could be cleared with the "Clear All Outputs" button it cannot.
![image](https://github.com/microsoft/vscode/assets/58749850/d318f8fe-5122-4ef8-abf9-75dbae118709)

add a print statement to the cell and run.
The "Clear All Outputs" is now available and can be used to clear the execution count as well as outputs.
![image](https://github.com/microsoft/vscode/assets/58749850/18ce5640-4ef1-4114-9c6f-21462405b4b5)

"Clear All Outputs" should be available to clear execution counts even if none of the cells have printed outputs.

### VS Code Version

1.86.2

### Jupyter Extension Version

2024.1.1

### Jupyter logs

_No response_

### Coding Language and Runtime Version

Python v 3.10.10

### Language Extension Version (if applicable)

_No response_

### Anaconda Version (if applicable)

_No response_

### Running Jupyter locally or remotely?

None
Repository: kubernetes
Issue: [FG:InPlacePodVerticalScaling] Inconsistent handling of memory limit decrease
Labels: kind/bug,priority/important-soon,sig/node,triage/accepted

/kind bug

When shrinking the pod-level memory limits (sum of container limits iff all containers have limits), the Kubelet checks the current pod memory usage, and doesn't apply the new limits if the new limits < current usage. However, the Kubelet doesn't place the same restriction on containers, and we don't require container runtimes to make the same check.

In practice, this means that for a single container pod, decreasing the memory limit below usage will result in the resize being indefinitely in progress, but for a multiple container pod, if some containers have sufficient free memory, you can shrink the memory limits below usage for a container in the pod, resulting in that container being OOM-killed.

What is the desired behavior here?

https://docs.google.com/document/d/1cEFLXKwNOSNLAkzyhoJUgkBW0OiX-9bXB_aJV7OAypw/edit?tab=t.0 provides more background information and several options for how this should be handled.

/sig node
/priority important-soon
Repository: react
Issue: [Compiler Bug]: Compiler fails to memoize hooks with no hook calls
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [X] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://github.com/billyjanitsch/react-compiler-hook-detection-bug

### Repro steps

Given the following three custom hooks:

```tsx
import {useDebugValue} from 'react'

function useFoo() {
  return () => 'foo'
}

function useBar() {
  useDebugValue('bar')
  return () => 'bar'
}

function useBaz() {
  return useCallback(() => 'baz', [])
}
```

I'd expect the compiler to memoize all of them, but it only memoizes `useBar` and `useBaz`:

```tsx
import { useCallback, useDebugValue } from "react";
function useFoo() {
  return () => "foo";
}
function useBar() {
  useDebugValue("bar");
  return _temp;
}
function _temp() {
  return "bar";
}
function useBaz() {
  return _temp2;
}
function _temp2() {
  return "baz";
}
```

I'm guessing that it's because the compiler's hook detection logic looks for at least one hook call in the function body. I understand that it generally doesn't make sense to write a custom hook that doesn't use any other hooks, but the exception is when the custom hook would have used only `useMemo` and/or `useCallback`, such as `useBaz`. I expect the compiler to let me remove those hooks without losing memoization.

This doesn't reproduce in the playground. I'm not sure why.

### How often does this bug happen?

Every time

### What version of React are you using?

19.0.0

### What version of React Compiler are you using?

19.0.0-beta-37ed2a7-20241206