sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Compile is too slow 
Labels: A-type-system,I-compiletime,T-compiler,C-bug,E-needs-mcve,T-types

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code ([`issue code repo`](https://github.com/araraloren/example) (c1421faeeb9b8a2775d3ce460ee56e42064ea709)):

```rust
let unit = neu::ascii_alphabetic()
    .or(neu::ascii_alphanumeric())
    .or('_');
let ident = unit.repeat_one_more();
let ty = neu::ascii_alphabetic()
    .or('_')
    .repeat_one()
    .then(ident)
    .pat();
// compile about 25s+
let layer1 = ty
    .then(ty.quote("<", ">"))
    .map(|(w, ty)| Ok(Ty::Layer1(w, ty)));
let layer2 = ty
    .then(ty.then(ty.quote("<", ">")).quote("<", ">"))
    .map(|(w1, (w2, ty))| Ok(Ty::Layer2(w1, w2, ty)));
let layer0 = ty.map(|ty| Ok(Ty::Layer0(ty)));
let field = ident.sep_once(":", layer2.or(layer1.or(layer0)));
// let layer1 = ty
//     .then(ty.quote("<", ">"))
//     .map(|(w, ty)| Ok(Ty::Layer1(w, ty)));
// let layer0 = ty.map(|ty| Ok(Ty::Layer0(ty)));
// let field = ident.sep_once(":", layer1.or(layer0));
// comment 55 ~ 62 and uncomment current block, compile about 2s+
let public = field
    .padded("pub")
    .map(|(name, ty_name)| Ok(Field::public(name, ty_name)));
let private = field.map(|(name, ty_name)| Ok(Field::private(name, ty_name)));
let parser = public.or(private).sep(",");

let data = "abc: Option<i32>";
let b_policy = re_policy(neu::whitespace().repeat_full());

dbg!(PolicyCtx::new(CharsCtx::new(data), b_policy).ctor(&parser)?);
```

I expected to see this happen: compile in several seconds.

Instead, this happened: compile in 27s+.

```
   Compiling api-gen v0.1.0 (E:\Rust\issue-example)
warning: field `public` is never read
  --> src\main.rs:23:5
   |
   |            ----- field in this struct
...
23 |     public: bool,
   |     ^^^^^^
   |
   = note: `Field` has derived impls for the traits `Clone` and `Debug`, but these are intentionally ignored during dead code analysis
   = note: `#[warn(dead_code)]` on by default

warning: `api-gen` (bin "api-gen") generated 1 warning
    Finished dev [unoptimized + debuginfo] target(s) in 27.29s
```

`neure` is a crate write for parsing string or binary data, 
### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.77.0-nightly (3cdd004e5 2023-12-29)
binary: rustc
commit-hash: 3cdd004e55c869faa2b7b25efd3becf50346e7d6
commit-date: 2023-12-29
host: x86_64-pc-windows-msvc
release: 1.77.0-nightly
LLVM version: 17.0.6
```
Repository: go
Issue: x/website/_content/doc: add note about how much memory the Go runtime retains to the GC guide
Labels: Documentation,NeedsInvestigation

Hello,
I spent a lot of time to find the reason of a "memory leak" which did not exist. There was a fundamental misunderstanding about memory management. We thought that the garbage collector returns unused heap memory back to the operating system, which was wrong.

The explanation is in https://github.com/golang/go/issues/41444#issuecomment-720677766 :
"Since the Go garbage collector is designed to retain about twice as much memory as your live heap size, debug.FreeOSMemory is expected to free about half of your memory"

Would you please add this information to https://tip.golang.org/doc/gc-guide ?

I think is is very important to know.
Repository: godot
Issue: C# Non-exported variable becomes null after build for Tool classes
Labels: bug,topic:editor,needs testing,topic:dotnet

### Tested versions

- Reproducible in v4.2.1.stable.mono.official [b09f793f5]

### System information

Godot v4.2.1.stable.mono - Windows 10.0.22631 - GLES3 (Compatibility) - AMD Radeon(TM) Graphics (Advanced Micro Devices, Inc.; 31.0.21018.9001) - AMD Ryzen 5 PRO 5650U with Radeon Graphics (12 Threads)

### Issue description

On classes with [Tool] annotation, private variables can become null when recompiling the project. Manually changing exported properties in the editor fixes this, even if exported variable is unrelated to the private variable. Reloading the scene in the editor also fixes this.

The MRP below uses GetNode to fetch a node during _Ready. This works fine when loading the scene for the first time, however when changing the code and rebuilding, the private variable is null and _Ready is not called again.

### Steps to reproduce

- Load the MRP and open the "secondary.tscn" scene
- Output messages should read:
```
Ready
Target sprite is not null
End Ready
```
- Change the ParentNode.cs file, e.g. modify the comment on line 26
- Build project in Godot
- Output messages should have:
```
Target sprite is null
Target sprite is null
```
- Change "ShowTargetSprite" boolean from the "Node2D" inspector window
- Output messages should have:
```
Set ShowTargetSprite
Target sprite is not null
```

### Minimal reproduction project (MRP)

[LostState - MRP.zip](https://github.com/godotengine/godot/files/13859799/LostState.-.MRP.zip)
Repository: flutter
Issue: Generated Podspec doesn't escape single quotes
Labels: platform-ios,tool,platform-mac,has reproducible steps,P3,team-tool,triaged-tool,found in release: 3.16,found in release: 3.19

### Steps to reproduce

1. run `flutter create -t plugin`
2. Edit `{{ projectRoot }}/pubspec.yaml`
   ```yaml
   name: rotation_sensor
   description: >
     A package provides a stream of device's attitude in three different representations a rotation
     matrix, a quaternion, and Euler angles (azimuth, pitch, roll).
   version: 0.0.1
   #...
   ```
3. run `flutter pub get` in `{{ proejctRoot }}` and `{{ projectRoot }}/example`
4. run `pod install` in `{{ projectRoot }}/example/ios`

### Actual results

The generated `{{ projectRoot }}/ios/{{ projectName }}.podspec` contain syntax error.
The single quotation mark `'` in summary should be escaped but actually not.

```ruby
Pod::Spec.new do |s|
  s.name             = 'rotation_sensor'
  s.version          = '0.0.1'
  s.summary          = 'A package provides a stream of device's attitude in three different representations a rotation matrix, a quaternion, and Euler angles (azimuth, pitch, roll).'
  s.description      = <<-DESC
A package provides a stream of device's attitude in three different representations a rotation matrix, a quaternion, and Euler angles (azimuth, pitch, roll).
  #...
end
```

### Logs

<details open>
<summary>Logs</summary>

```console

Analyzing dependencies
[!] Failed to load 'rotation_sensor' podspec: 
[!] Invalid `rotation_sensor.podspec` file: syntax error, unexpected local variable or method, expecting `end'
...e provides a stream of device's attitude in three different ...
...                              ^
.

 #  from /Users/6y/Programming/flutter_rotation_sensor/example/ios/.symlinks/plugins/rotation_sensor/ios/rotation_sensor.podspec:8
 #  -------------------------------------------
 #    s.version          = '0.0.1'
 >    s.summary          = 'A package provides a stream of device's attitude in three different representations a rotation matrix, a quaternion, and Euler angles (azimuth, pitch, roll).'
 #    s.description      = <<-DESC
 #  -------------------------------------------


```

</details>


### Flutter Doctor output

<details open>
<summary>Doctor output</summary>

```console

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.16.5, on macOS 14.1.1 23B81 darwin-arm64, locale zh-HK)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] Connected device (2 available)
[✓] Network resources

• No issues found!

```

</details>
Repository: vscode
Issue: SCM Graph - history item context menu contribution proposal
Labels: feature-request,scm,api-proposal

Continuation points:
* `scm/historyItem/context`
Repository: vscode
Issue: Uncaught Error: Assertion Failed  Error: Assertion Failed     at N (vscode-file://vscode-app//out/vs/base/worker/workerMain.js#editorWorkerService:13:8080)     at L (vscode-file://vscode-app//out/vs/base/worker/workerMain.js#editorWorkerService:37:7895)   
Labels: error-telemetry

```javascript
Uncaught Error: Assertion Failed

Error: Assertion Failed
at N in src/vs/base/common/assert.ts:47:21
at L in out/vs/base/worker/workerMain.js:37:7895
at $IZ in src/vs/editor/common/diff/defaultLinesDiffComputer/defaultLinesDiffComputer.ts:142:19
at l in src/vs/editor/common/services/editorSimpleWorker.ts:422:32
at l.computeDiff in src/vs/editor/common/services/editorSimpleWorker.ts:413:29
at i.d in src/vs/base/common/worker/simpleWorker.ts:470:56
at Object.handleMessage in src/vs/base/common/worker/simpleWorker.ts:451:71
at L.k in src/vs/base/common/worker/simpleWorker.ts:204:32
at L.h in src/vs/base/common/worker/simpleWorker.ts:168:17
at L.handleMessage in src/vs/base/common/worker/simpleWorker.ts:160:8
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2&bH=3ff187e4-cebb-8bd1-4abf-18e7bd60a74c)
Repository: vscode
Issue: ListError [codeActionWidget] Invalid start index: 2
Labels: error-telemetry

```javascript
Error: ListError [codeActionWidget] Invalid start index: 2
at ne.splice in src/vs/base/browser/ui/list/listWidget.ts:1539:10
at n.t in src/vs/platform/actionWidget/browser/actionList.ts:335:16
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2&bH=31f7428f-1b90-2689-a51f-865b87b532d2)
Repository: material-ui
Issue: [material-ui][Rating] Error with precision decimal numbers
Labels: bug 🐛,package: material-ui,component: rating

### Steps to reproduce

import { Rating } from '@mui/material';

<Rating precision={0.3} />

![image](https://github.com/mui/material-ui/assets/30044390/4d176c11-3f4e-40fc-a0e5-59ac04a3d259)
It looks like it happened because of 

`if (precision < 1) {
        const items = Array.from(new Array(1 / precision));`

### Current behavior

Rating Component doesn't work with the decimal **precision** values such as 0.4, 0.3, 0.6

### Expected behavior

_No response_

### Context

- @mui/material 5.14.17

### 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**: rating component decimal numbers error
Repository: tauri
Issue: [bug] The generated Android debug program is running normally. There is an error in the publishing mode.
Labels: type: bug,status: needs triage

### Describe the bug

FATAL EXCEPTION: main
Process: com.gyoyo.okapp, PID: 12614
java.lang.NoSuchMethodError: no non-static method "Lcom/gyoyo/okapp/RustWebView;.evalScript(ILjava/lang/String;)V"
	at android.os.MessageQueue.nativePollOnce(Native Method)
	at android.os.MessageQueue.next(MessageQueue.java:335)
	at android.os.Looper.loop(Looper.java:183)
	at android.app.ActivityThread.main(ActivityThread.java:7656)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 120.0.2210.121
    ✔ MSVC: Visual Studio ���ɹ��� 2022
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (environment override by RUSTUP_TOOLCHAIN)

[-] Packages
    - tauri [RUST]: 2.0.0-alpha.20
    - tauri-build [RUST]: 2.0.0-alpha.13
    - wry [RUST]: 0.35.2
    - tao [RUST]: 0.24.0
    - tauri-cli [RUST]: 2.0.0-alpha.20
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 2.0.0-alpha.20

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: next.js
Issue: Client-side navigation prefetches wrong data JSON on Vercel when using Middleware, SSG and Rewrites
Labels: bug,Navigation,Runtime,Pages Router

### Link to the code that reproduces this issue

https://github.com/jkondela/next-rewrites-repro

### To Reproduce

1. Open https://next-rewrites-repro.vercel.app/
2. Click on the link
3. Next.js prefetches `book.json`, but page has url `books`, so Router will render page with empty props.
4. Try reload the current page, it will print correct props. Only client-side navigation does not work.

### Current vs. Expected behavior

Expected: When using client-side navigation (for route which has rewrite, middleware and dynamic SSG), it should work.
Current: Client-side navigation does not work, page has empty props. Hard refresh has correct props.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Thu Oct 5 21:02:42 UTC 2023
Binaries:
  Node: 18.17.1
  npm: 9.6.7
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.5-canary.43
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Data fetching (gS(S)P, getInitialProps), Middleware / Edge (API routes, runtime), Routing (next/router, next/navigation, next/link)

### Which stage(s) are affected? (Select all that apply)

Vercel (Deployed)

### Additional context

After upgrade to Next 13, it stopped working. Also tested on 14 and 14-canary.

It works correctly on localhost, but not on Vercel.

It only does not work when using combination of SSG dynamic page with middleware and Next config rewrite.
If I remove middleware.ts (which has only `Response.next()`), it will start working as expected.
Repository: vscode
Issue: vscode 1.85.1 with devcontainer and alpine 3.15 not working properly
Labels: vscode-website

<!-- ⚠️⚠️ 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.85.1
- OS Version: Windows 10, Debian WSL2

Steps to Reproduce:
1. Create a dev-container based on alpine-3.15
2. Use the search function in vscode -> doesn't show any results and spins indefinitely

More details:
I found a similar issue from April 2023 (https://github.com/microsoft/vscode/issues/179490) which is closed. I now wonder if it is the same issue or a different one or if alpine 3.15 is just unsupported now? If I leave everything as is and just use alpine-3.17 everything is back to normal.
Repository: material-ui
Issue: [material-ui][Select][Radio] Please enable the Select Option value and radio buttons to accept any value
Labels: waiting for 👍,component: select,component: radio,typescript,status: expected behavior,enhancement

### What's the problem?

We are using the react hook form each time we have a different schema and because of that we face issues with MUI example schema accepts boolean values or null and the component that we are using is select that accepts only string | number | readonly string[] | undefined



### What are the requirements?

Return the same value that is passed to the `select` or `radio` options without conversion to string

### What are our options?

Fallbacks that I didn't like and the solution should be fixed from the library why limiting the library to be reusable with different tools

### Proposed solution

_No response_

### Resources and benchmarks

_No response_

**Search keywords**:
Repository: godot
Issue: Crash related to mutex locking
Labels: bug,platform:linuxbsd,topic:porting,needs testing,crash

### Tested versions

Godot Engine v4.2.1.stable.arch_linux

### System information

Vulkan API 1.3.246 - Forward+ - Using Vulkan Device #0: Intel - Intel(R) UHD Graphics (ICL GT1)

### Issue description

This is my first time encountering this crash. I am pretty used to some libx11 error that causes regular crashes which unfortunately seems to be out of the dev teams control. First time seeing this particular error though which may or may not be related.

A quick search yielded no godot related results so I thought I should open an issue tracker here. I haven't been able to reproduce it. However the search brought up something about mutex locking, which I do not know what is but maybe to some clever people here that rings a bell.

I run godot via the terminal with "godot --single-window"

Log:

```
Godot Engine v4.2.1.stable.arch_linux - https://godotengine.org
USER WARNING: Error setting locale modifiers
   at: DisplayServerX11 (platform/linuxbsd/x11/display_server_x11.cpp:5903)
USER WARNING: XOpenIM failed
   at: DisplayServerX11 (platform/linuxbsd/x11/display_server_x11.cpp:5951)
USER WARNING: XCreateIC couldn't create wd.xic
   at: _create_window (platform/linuxbsd/x11/display_server_x11.cpp:5575)
Vulkan API 1.3.246 - Forward+ - Using Vulkan Device #0: Intel - Intel(R) UHD Graphics (ICL GT1)
 
USER ERROR: Condition "arr.size() == 0" is true.
   at: set_data (servers/physics_2d/godot_shape_2d.cpp:588)
_the above is all from project launch_

Fatal glibc error: pthread_mutex_lock.c:94 (___pthread_mutex_lock): assertion failed: mutex->__data.__owner == 0
```

Other perhaps useful info:
Manjaro 23.1.2
Libx11-1.8.4

### Steps to reproduce

Unknown. Could be related to file-saving.

### Minimal reproduction project (MRP)

Unable to reproduce?
Repository: node
Issue: OS/architecture compatiblility list for nodejs versions
Labels: feature request,stale

### What is the problem this feature will solve?

There is no offical overview, which operating system versions are supported. Recently I tried to install Node 20 on RHEL7 and it failed due to an old glibc version. Same goes for SLES12 for example.

### What is the feature you are proposing to solve the problem?

A simple json file to show the operating system compatibilities:

```json
{
  "20.x":{
    "rhel8":{
      "supported":true,
      "arch":{
        "x86_64":true,
        "arm64":true,
        "s390x":true
      }
    },
    "rhel7":{
      "supported":false,
      "arch":{
        ...
      }
    },
    "sles15":{
      ...
    },
    "sles12":{
      ...
    }
  },
  "18.x":{
    "rhel8":{
      "supported":true,
      "arch":{
        "x86_64":true,
        "arm64":true,
        "s390x":true
      }
    },
    "rhel7":{
      "supported":false,
      "arch":{
        ...
      }
    },
    "sles15":{
      ...
    },
    "sles12":{
      ...
    }
  },
...
}
```

### What alternatives have you considered?

Looking it up on unoffical websites or try it out on different virtual machines
Repository: stable-diffusion-webui
Issue: [Feature Request]:  Implement stable-fast
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Implement stable-fast as an optimization strategy along xformers

https://github.com/chengzeyi/stable-fast?tab=readme-ov-file

### Proposed workflow

N.A


### Additional information

_No response_
Repository: vscode
Issue: Definition Completion is not invoked for non-word tokens (like ++ operators) when ctrl-hovering
Labels: feature-request,editor-symbols

<!-- ⚠️⚠️ 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. -->
See https://github.com/microsoft/vscode-languageserver-node/issues/1383 .

In language server onDefinition() is not called. According to the above issue this is because VS-Code does only call definition completion on word tokens. I would like though to also show definition completion for operators like "++" and so forth.

Would it be possible to add somehow the support to call onDefinition also on non-operators?

It would be fine enough if there is added a new language server property which allows to declare a list of tokens that should trigger definition completion although they are not text tokens. Maybe something like:

additionalDefinitionTokens = ['++', '--', '+', ... ]