sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Debugging indicators can mess with tab spacing
Labels: bug,editor-core

I broke on this line, see how the tab on that line is 3 spaces, not the regular 4:

![image](https://github.com/microsoft/vscode/assets/2193314/520f3817-b14a-4cb6-87d3-a7d53de27673)

Stepping:

![Recording 2023-05-22 at 07 51 02](https://github.com/microsoft/vscode/assets/2193314/134b35ce-6816-4ed0-a1fe-c37ae75c5c57)

Version: 1.79.0-insider (user setup)
Commit: f6be5461f8bc69013a605f5baea834651c6589fb
Date: 2023-05-20T01:18:53.811Z
Electron: 22.5.2
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.22621
Repository: react
Issue: Bug: useId IDs have special characters that conflict with certain DSLs (like CSS)
Labels: Status: Unconfirmed

The ID scheme for the `useId` hook returns IDs that look like `":S1:"`, but `:` is not a valid character for CSS identifiers and must be escaped. On client-only components, you can wrap the ID in `CSS.escape` but the `CSS` global object doesn't exist on the server so this doesn't work for server-component renders.

React version: 18.2

## Steps To Reproduce

1. Try utilizing the id's created by `useId` in CSS identifiers.
2. It doesn't work.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: https://stackblitz.com/edit/react-ts-zhtk6u?file=Example.tsx

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

The current implementation of `useId` creates IDs with special characters which can conflict with certain DSLs (in this example, CSS) that React has to commonly interact with.

## The expected behavior

Don't use special characters in IDs created by `useId`.
Repository: material-ui
Issue: [examples] Better support of Vite examples
Labels: examples

### Summary 💡

Per https://github.com/reactjs/react.dev/pull/5487 and https://npm-stat.com/charts.html?package=vite&package=react-scripts&package=next it doesn't make a lot of sense to have all these Create React App demos.

<img width="407" alt="Screenshot 2023-05-22 at 01 04 20" src="https://github.com/mui/material-ui/assets/3165635/741c5d67-d239-4a26-bbc2-eced80d88584">

https://github.com/mui/material-ui/tree/master/examples

I think that we could either move them to be specialized examples with Vite or create them

### Examples 🌈

_No response_

### Motivation 🔦

_No response_
Repository: flutter
Issue: [file_selector] Add API to query support
Labels: package,team-ecosystem,P2,p: file_selector,triaged-ecosystem

We have platform gaps in what is supported in `file_selector`, and will in the long term:
- Some methods are desktop-only, or non-mobile-only.
- Some methods have min OS requirements, like getting the directory on Android.

To make it easier to write code that handles the differences, we should have API to query support at runtime, so a client can check whether a given method call is supported before calling it, rather than having to hard-code their own OS checks (particularly problematic in the Android case).
Repository: go
Issue: x/pkgsite: paragraph links work incorrectly on mobile
Labels: pkgsite

### What is the URL of the page with the issue?

https://pkg.go.dev/runtime#SetFinalizer


### What is your user agent?

Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Mobile Safari/537.36


### Screenshot

![Screenshot_2023-05-22-19-00-00-43_40deb401b9ffe8e1df2f1cc5ba480b12.jpg](https://github.com/golang/go/assets/29275085/37ed0ebb-a9a4-4ee9-a6d6-dc455253287c)


### What did you do?

1. Got a link to a package, linking specifically to a paragraph (specifically, a function in that case)
2. Opened the link using Chrome



### What did you expect to see?

I expected to see my browser opening the link at that specific paragraph

### What did you see instead?

The browser opened the link correctly, then jumped to the top of the page

Using links like: https://pkg.go.dev/runtime#:~:text=func%20SetFinalizer%20%C2%B6,will%20free%20obj does work.

Video of the issue: https://github.com/golang/go/assets/29275085/70f3e565-4cce-4b5b-bc53-9d1ade23785f
Repository: godot
Issue: Adding elements to the CodeEdit arrays doesn't work
Labels: bug,confirmed,topic:gui

### Godot version

4.0.stable

### System information

Windows 10 ; Nvidea RTX 3060 Ti ; Intel Core i7 10700k

### Issue description

When trying to either add an element to the delimiter_strings, delimiter_comments and code_completion_prefixes in the CodeEdit Node, it does nothing. Except for the CodeCompletion Prefix, where if you  try to add an element, you get an error message : "Code completion prefix cannot be empty", although I am trying to add an element. ( Yes I have enabled code completion ). It still does nothing though.

### Steps to reproduce

1. Create new Project with Control Node as Parent and add CodeEdit as child.
2. Click on either Delimiter Strings, Delimiter Comments or Code Completion Prefixes ( Where you have to enable it first ) and try to add an element.

### Minimal reproduction project

Unneccesarry
Repository: axios
Issue: axios should not use JSON.parse to parse the response when the responseType is set to 'text'
Labels: priority::low

### Describe the bug

When the response is a string, axios parses responses using JSON.parse as the default transformResponse (https://github.com/axios/axios/blob/16b5718954d88fbefe17f0b91101d742b63209c7/lib/defaults.js#L57-L65). JSON.parse tries to make the value a Number (https://github.com/axios/axios/issues/2919), e.g. JSON.parse('646686880670135092987843') => 6.466868806701352e+23. This will cause unexpected result from the client side. 

When client set responseType is to 'text', the axios should not use JSON.parse. Instead, it should return the string directly.

### To Reproduce

_No response_

### Code snippet

_No response_

### Expected behavior

_No response_

### Axios Version

_No response_

### Adapter Version

_No response_

### Browser

_No response_

### Browser Version

_No response_

### Node.js Version

_No response_

### OS

_No response_

### Additional Library Versions

_No response_

### Additional context/Screenshots

_No response_
Repository: next.js
Issue: invalid valorization of query parameters in a server request
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 21.6.0: Wed Aug 10 14:28:23 PDT 2022; root:xnu-8020.141.5~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.18.1
      npm: 8.19.2
      Yarn: 1.22.10
      pnpm: N/A
    Relevant packages:
      next: 13.4.4-canary.1
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.5
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/Byte-Code/next-query-param-issue

### To Reproduce

To reproduce the issue run the project in development mode (starting from 13.3.0 next version) or production mode (latest [as i wrote in the readme i didn't check from which version the problem appeared also in production mode]).

Once the project is started, navigate to localhost:3000 from there you can navigate to one of the user pages or to the test page to see a variable printed in the html.

For better understaing of the issue i added some comment in the readme of the project and in every single page/api that is afflicted by the problem, describing the issue and the steps to reproduce them.

### Describe the Bug

When a query parameter is given to a server request it's incorrectly valued.

Given the urls:

- http://localhost:3000/test?test_param=test//test of a page with a get server side props function, the value of the query param **test_param**:
    -  during a client side navigation is correctly valued as **test//test**
    -  during a server side navigation is wrongly valued as **test/test**
 
- http://localhost:3000/user/3?test_param=test//test of a page without a get server side props function, the value of the query param **test_param**
   -  during a client or server side navigation is correctly valued as **test//test**

- http://localhost:3000/api/users?test_param=test//test of an API request, the value of the query param **test_param** 
   - in the browser network is correctly valued as **test//test**
   - in the api handler, the request query is wrongly value as **test/test**



### Expected Behavior

The expected behavior is that the query parameter **test_param** with value **test//test** is always valued as **test//test** like in the previous NextJs version 13.2.4.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: kubernetes
Issue: test/e2e/storage: reduce privileges granted to pods
Labels: sig/storage,kind/feature,lifecycle/frozen,needs-triage

### What would you like to be added?

Most tests currently run with `f.NamespacePodSecurityEnforceLevel = admissionapi.LevelPrivileged`.

Only the namespace created for the CSI driver needs to allow privileged pods. The main test namespace is often just used to test that a pod using a volume can start up, which might work with `admissionapi.LevelRestricted`.

To achieve this, the level of the additional namespace must get decoupled from `f.NamespacePodSecurityEnforceLevel`: 
https://github.com/kubernetes/kubernetes/blob/ce05a4f7fcc234dd3132a4e40e6afdf0b2ebc94e/test/e2e/framework/framework.go#L451-L455

Then [`runVolumeTesterPod`](https://github.com/kubernetes/kubernetes/blob/ce05a4f7fcc234dd3132a4e40e6afdf0b2ebc94e/test/e2e/framework/volume/fixtures.go#L389) must be extended to run pods with a specific level, ideally `admissionapi.LevelRestricted`.

### Why is this needed?

Testing with more privileges than really needed might hide issues that users will run into when trying to harden their cluster setup by granting pods less privileges.
Repository: godot
Issue: Unable to change CheckButton font color when check button is toggled on and focused on
Labels: bug,topic:gui

### Godot version

4.0.0 - 4.0.3

### System information

Windows 11, AMD CPU, Radeon GPU

### Issue description

I need my CheckButton font to be dim when it is not focused on and white when it is focused on. Unfortunately, however, once a CheckButton is toggled on there is no way for focus to change the font color. It works fine when toggled off, but the font color becomes unchangeable when toggled on (except for by hovering, but I would like users to be able to use the arrow keys). [Here is a video of my problem.](https://youtu.be/MXPv1xJ16Ac)

I found a similar issue where someone had this [same problem but with hover](https://github.com/godotengine/godot/issues/34727), which was resolved. The only difference between our issues is the difference between hover and focus.

I figure the best solution for this is for a theme option to be added called font_focus_pressed_color. Or, font_focus_color should have precedence over font_pressed_color.

NOTE: After further investigation, all toggle-able buttons share the same issue.

### Steps to reproduce

1. Create CheckButton.
2. CheckButton should be alongside other UI elements that you can navigate between using focus (for instance with arrow keys).
3. Create a theme for the UI and apply it to the UI.
4. Set the theme for CheckButton to be something like this:
![example](https://github.com/godotengine/godot/assets/24948718/6ce97c96-b3d0-48b8-8f01-d7cb88cae277)
(transparent colors shown are white with half opacity and white colors just full white)
5. Build and play. Notice that when the CheckButton is toggled off, focus works fine. When CheckButton is toggled on, however, focus has no ability to change the font color so it is impossible to tell if the CheckButton has focus.

### Minimal reproduction project

[Test Example Project.zip](https://github.com/godotengine/godot/files/11536934/Test.Example.Project.zip)
Repository: vscode
Issue: Enable sizing a list's container to match its content width
Labels: feature-request,list-widget

Cleanup from https://github.com/microsoft/vscode/issues/173980

The solution there basically works but is awkward. I think the fundamental issue is that there is no reliable way to check the content width of the list or know when it changed. This makes sense most of the time, because originally horizontal scrolling wasn't supported anyway, and in other scenarios, the list always appears in a fixed-width container.

What the debug hover is trying to do is to show the variable tree in a container that flexes a little with the width of its contents- clamps the container sizes to 400-550px and wants to match the contents size when its between those.

My suggestion is to expose a `contentWidth/onDidChangeContentWidth` which just go along with the height properties that already exist here: https://github.com/microsoft/vscode/blob/01c0fb75fe513271674a783d98bc996fcf5a515a/src/vs/base/browser/ui/list/listView.ts#L221-L222 and the event can be fired when `updateScrollWidth` is called https://github.com/microsoft/vscode/blob/01c0fb75fe513271674a783d98bc996fcf5a515a/src/vs/base/browser/ui/list/listView.ts#L677

https://vscodeteam.slack.com/archives/C03ERNTC03X/p1684365397169389
Repository: pytorch
Issue: [FSDP] Summon buffers in full precision
Labels: oncall: distributed,module: fsdp

### 🐛 Describe the bug

We should check if we are doing this and fix as needed, and update the mixed precision API documentation.

### Versions

main

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu
Repository: pytorch
Issue: [FSDP] Ensure full precision checkpoints
Labels: oncall: distributed,triaged,module: fsdp

### 📚 The doc issue

The FSDP MixedPrecision API docs say that checkpoint in full precision is only ensured for full_state_dict, let's ensure we have support for sharded_state_dict and update.

### Suggest a potential alternative/fix

_No response_

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin
Repository: godot
Issue: TabContainer rearranging broken when `EmbedSubwindows=false` an `ContentScaleFactor!=1.0`
Labels: bug,topic:gui

### Godot version

4.0.2

### System information

Windows 10 Vulkan API 1.2.175 - Forward+ - NVIDIA GeForce GTX 860M

### Issue description

When:
- `gui_embed_subwindows` is `false` and `content_scale_factor` is (for example) `2.0`, it can be observed that the area of the TabBar being used for tab rearranging is in the original scale - half as big as the displayed TabBar
- Enabling `gui_embed_subwindows` immediately causes it to work again

### Steps to reproduce

1. Create TabContainer with any amount of tabs, with tab_rearranging to true
2. Set Embed Subwindows to false in Project Settings
3. Set Window/Stretch/Scale to 2.0
4. Run the project, notice the TabBar area reacting to drag and drop events when rearranging tabs is scaled to half the displayed size
5. What's interesting is the tab preview and insertion highlight display normally as they should

### Minimal reproduction project

The first tab has a checkbox to toggle `gui_embed_subwindows`

[TabContainerTest.zip](https://github.com/godotengine/godot/files/11536279/TabContainerTest.zip)
Repository: PowerToys
Issue: PowerToys Run: Open search results in the new window instead of a new tab
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

When typing "??" in the PowerToys Run I would like to be able to open the search results in the new window instead of new tab. So maybe by default new tab can open, but when clicked ctrl + enter new window would pop up. This could include incognito mode, when clicked ctrl + shift + enter a new window in incognito mode would appear.

### Scenario when this would be used?

Sometimes I want to quickly google something without interrupting my main window, so the results in the new window would be very convenient. 

### Supporting information

_No response_
Repository: tensorflow
Issue: can we customize memory allocation functions(like malloc/free) for inference with C api? 
Labels: stat:awaiting tensorflower,type:feature,comp:runtime

<details><summary>Click to expand!</summary> 
 
 ### Issue Type

Feature Request

### Have you reproduced the bug with TF nightly?

No

### Source

source

### Tensorflow Version

2.8

### Custom Code

No

### OS Platform and Distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/Compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current Behaviour?

When using C api to do inference, I want to customize the memory allocation functions like malloc/free to control how tensorflow allocates memory. I want to make tensorflow use a separate area of memory in some shared memory region to load the model. Is there a way to do this?

### Standalone code to reproduce the issue

```shell
N/A
```


### Relevant log output

_No response_</details>
Repository: godot
Issue: `if x is Type` statement provides autocompletion for `x` in its scope but fails to infer types from properties and function calls
Labels: discussion,topic:gdscript

### Godot version

4.0.3

### System information

linux

### Issue description

consider this: 
```gdscript
extends Node

func do(n):
    if n is Camera3D:
        var f := n.get_frustum()
```

godot provides autocompletion for n in this scope:
![image](https://github.com/godotengine/godot/assets/71937306/82b297b8-e6e6-4840-a273-4226df1f8483)

but then immediately complains about the supposedly unknow return type:
![image](https://github.com/godotengine/godot/assets/71937306/9c2edc3d-5da1-4371-ba35-5d830560f74a)


### Steps to reproduce

Type this script and notice how you get autocompletion prompts and an error.
```gdscript
extends Node

func do(n):
    if n is Camera3D:
        var f := n.get_frustum() # type this
```

### Minimal reproduction project

see above
Repository: rust
Issue: error: `X` does not live long enough doesn't provide enough context
Labels: A-diagnostics,A-lifetimes,C-bug,A-async-await,AsyncAwait-Triaged,D-terse,S-has-mcve,A-GATs

REPRODUCTION: https://www.rustexplorer.com/b/oe3uh4

error:
```
error: `impl Executor` does not live long enough
   --> src/main.rs:136:5
    |
136 | /     async move {
137 | |         dbg!("I'm:", user);
138 | |
139 | |         let mut store = store.unwrap_or_default();
...   |
169 | |     }
170 | |     .boxed()
    | |____________^
```

Some code:

```rust
fn query_teams<'a>(
    user: &'a str,
    db: &'a mut impl Executor,
    store: Option<Store>,
    with_player: bool,
) -> BoxFuture<'a, Store> {
    async move {
        dbg!("I'm:", user);

        let mut store = store.unwrap_or_default();

        let mut query = sqlx::QueryBuilder::new(r#"SELECT "teams".*" FROM "teams"#);

        let teams = query
            .build_query_as::<Team>()
            .fetch_all(db.as_executor())
            .await
            .unwrap();

        for team in teams {
            store.teams.insert(team.id.to_string(), team);
        }

        if with_player {
            store = query_players(user, db, Some(store), false).await;
        }

        store
    }
    .boxed()
}
```

```
error: `impl Executor` does not live long enough
   --> src/main.rs:136:5
    |
136 | /     async move {
137 | |         dbg!("I'm:", user);
138 | |
139 | |         let mut store = store.unwrap_or_default();
...   |
169 | |     }
170 | |     .boxed()
    | |____________^
```

### Meta
```
rustc 1.69.0 (84c898d65 2023-04-16)
binary: rustc
commit-hash: 84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc
commit-date: 2023-04-16
host: x86_64-pc-windows-msvc
release: 1.69.0
LLVM version: 15.0.7
```
Repository: TypeScript
Issue: Crash `Unhandled type Any` on ESM-mode namespace import of `module.exports = null`
Labels: Bug,Help Wanted,Crash

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

unhandled type any

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

### 💻 Code

<!-- Please post the relevant code sample here as well. This code and the Playground code should be the same, do not use separate examples -->
```ts
// @module: nodenext
// @allowJs: true
// @noEmit: true

// @Filename: single-null-export.js
module.exports = null;

// @Filename: index.mts
import * as x from "./single-null-export.js";
```

### 🙁 Actual behavior

```
Error: Debug Failure. Unhandled type Any
    at resolveStructuredTypeMembers (/Users/andrew/Developer/microsoft/eg/crash/node_modules/typescript/lib/tsc.js:53313:15)
    at cloneTypeAsModuleType (/Users/andrew/Developer/microsoft/eg/crash/node_modules/typescript/lib/tsc.js:45963:32)
    at resolveESModuleSymbol (/Users/andrew/Developer/microsoft/eg/crash/node_modules/typescript/lib/tsc.js:45942:20)
    at getTargetOfNamespaceImport (/Users/andrew/Developer/microsoft/eg/crash/node_modules/typescript/lib/tsc.js:44942:22)
    at getTargetOfAliasDeclaration (/Users/andrew/Developer/microsoft/eg/crash/node_modules/typescript/lib/tsc.js:45249:16)
    at resolveAlias (/Users/andrew/Developer/microsoft/eg/crash/node_modules/typescript/lib/tsc.js:45295:22)
    at checkAliasSymbol (/Users/andrew/Developer/microsoft/eg/crash/node_modules/typescript/lib/tsc.js:78629:20)
    at checkImportBinding (/Users/andrew/Developer/microsoft/eg/crash/node_modules/typescript/lib/tsc.js:78745:5)
    at checkImportDeclaration (/Users/andrew/Developer/microsoft/eg/crash/node_modules/typescript/lib/tsc.js:78794:13)
    at checkSourceElementWorker (/Users/andrew/Developer/microsoft/eg/crash/node_modules/typescript/lib/tsc.js:79280:16)
```

### 🙂 Expected behavior

Compiles without error (and the type of `x` should be something like `{ default: null }`)
Repository: flutter
Issue: Would be nice if each API documentation page had a mechanism for providing feedback
Labels: c: new feature,framework,d: api docs,P3,team-framework,triaged-framework

It would be nice if each API documentation page included a link for providing feedback or corrections for the page, similar to MSDN or for what we do for internal g3doc pages. At a minimum it could be a link that starts a GitHub issue with the URL of the page, like: https://github.com/flutter/flutter/issues/new?title=API%20Documentation%20Feedback&body=Feedback%20for%20http%3A%2F%2Fwww.example.com

(Originally filed as https://github.com/flutter/website/issues/1438 )