sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: `GPUParticles3D` is_emitting is incorrectly toggled
Labels: bug,topic:editor,needs testing,topic:particles

### Tested versions

- Reproducible in 4.4 dev3

### System information

Godot v4.4.dev (0a9ad8f9d) - Artix Linux #1 SMP PREEMPT_DYNAMIC Wed, 02 Oct 2024 15:03:06 +0000 on Tty - X11 display driver, Multi-window, 1 monitor - OpenGL 3 (Compatibility) - NVIDIA GeForce GTX 1050 Ti (nvidia; 560.35.03) - AMD Ryzen 5 2600 Six-Core Processor (12 threads)

### Issue description

I have an `GPUParticles3D` with the property `one-shot` enabled. Let's say 2 seconds lifetime. And there is the scene of the `GPUParticles3D` itself and a main scene where it is placed multiple times.

The problem is that if the emitting stops in 2 seconds in its own scene, it also stops in the scenes this is located in. Whatever, its a chore but not a big issue because I can manually start it on `_enter_tree()`. And there is a [proposal opened for an autoplay](https://github.com/godotengine/godot-proposals/issues/10936)

But the real bug is that if it is emitting in its own scene, and I close that scene, then start the main scene, it emits (as expected) but once the emitting ends for all particles in the main scene, it also ends in its own scene (dirty flag?)
And if you then open the particle scene itself, it has `is_emitting` disabled/false, but it IS emitting in the editor.

### Steps to reproduce

1. Create a `GPUParticles3D` with one-shot property, lifetime 10 seconds, and save it as its own scene.
2. Place the above scene in your main scene, any amount of times.
3. On the particle scene itself, enable `is_emitting` and close the scene.
4. Start/Play the main scene
5. Await for lifetime to end
6. Close the game, and open the `GPUParticles3D` scene

Or just open the MRP below, open `smoke_scene.tscn`, enable `is_emitting` and reduce the lifetime (so you dont wait 60 seconds), close the scene, run the main scene, await lifetime to end, then open `smoke_scene.tscn`

### Minimal reproduction project (MRP)

[smoke-grenade-room.zip](https://github.com/user-attachments/files/17277806/smoke-grenade-room.zip)
Repository: pytorch
Issue: Add indication in symbols or FakeTensor whether ranges is set via mark_dynamic
Labels: triaged,enhancement,oncall: pt2,module: dynamic shapes

### 🚀 The feature, motivation and pitch

Currently when a tensor is marked dynamic via mark_dynamic API.  The range is reflected in the graph via ShapeEnv. However, no indication is present whether it is a user-provided range or a default range. The implication of this being hardship to differentiate user provided ranges to default ranges [2, INT_MAX]. Different backends have different implementation of dynamic ranges and it would be beneficial if a distinction is available between user set ranges and default ranges. For instance,  a backend may choose to use the user ranges and discard or manipulate default ranges.

The tensor marked dynamic has an attribute set "_dynamo_dynamic_range" which can be checked for confirming if tensor range is set by user through mark_dynamic API. However this information is available during launch(__call__) and not __init__(although graph module has ranges in shapeEnv).  The attribute however has no relation to symbols being used for that tensor and cannot be easily correlated to other input using same symbol.

The ask here is to set an indication in Symbol whether the range is set externally or internally.

### Alternatives

If information can be queried on a symbol that its range is set by the mark_dynamic API or is default, the backends can implement their logic effeciently.

### Additional context

_No response_

cc @ezyang @chauhang @penguinwu @bobrenjc93
Repository: ollama
Issue: Raw mode in `/api/generate` should return eos tokens
Labels: bug,api

### What is the issue?

Currently setting `"raw": true` does not return end of sequence tokens such as EOS, EOM, EOT, etc.

### OS

_No response_

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_
Repository: three.js
Issue: Add Flag to Disable Rendering Object in Transmission Pass
Labels: Suggestion

### Description

We render an object with the `MeshPhysicalMaterial` with `transmission` set to `1`. We allow users to apply clipping planes to that object. Because we want to render the "inside" of the object, we set the `side` to `DoubleSide`. However, we also want to render the object with a specific color.

Displaying the object with a certain color is tricky with this configuration though, because when `side` is set to `DoubleSide` the object will be rendered in the transmission pass with `side` set to `BackSide` and consequently transmit through itself, as it were. This is often desirable, I guess, but in our case it will distort the color in a way we do not want. We want to use double side rendering just to show the backsides of the object when clipping is applied.

Rendered with `FrontSide`:
<img alt="transmission_issue_w_front-side" src="https://github.com/user-attachments/assets/36a80bf2-86a3-472d-acd8-f5d504e24fc4" width="255">
Rendered with `DoubleSide`:
<img alt="transmission_issue_w_double-side" src="https://github.com/user-attachments/assets/5d89a006-2d86-4e6e-b9a3-f99b5b969b26" width="255">

You can also see the effect here: https://codesandbox.io/p/sandbox/2jpp8k (Modify line 32 to switch between front side and double side rendering)

An entry to the relevant code can be found here: https://github.com/mrdoob/three.js/blob/dev/src/renderers/WebGLRenderer.js#L1542

### Solution

Introduce a local (material-level) or a global flag to control whether objects with `transmission !== 0` and `side === DoubleSide` will be rendered in the transmission pass. The current behavior could be preserved by setting the flag to `true` by default.

If it is agreed upon that this is a desirable feature, I'd be willing to contribute a PR.

### Alternatives

We can work around the problem by setting the `drawRange.count` to 0 via the `onBeforeRender` for just the transmission pass, effectively hiding the object. This, however, has the shortcoming of still issuing a draw call during the transmission pass for the object.

### Additional context

_No response_
Repository: excalidraw
Issue: Text outside of shape when rotating and using text align effects
Labels: bug

https://github.com/user-attachments/assets/355a1462-6084-47a4-ad4c-9dea8465b3df
Repository: PowerToys
Issue: New+ freezing on Contex Menu (by Keyboard Key)
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

New+

### Steps to reproduce

In some situations when I access the Context Menu via keyboard, as my keyboard has a key to activate this menu, the focus is not available for navigation via the keyboard (up arrow and down arrow), that is, the menu opens but remains When stuck, I can only use it when I position the mouse on it so that the focus is reestablished and with the mouse I can finish it, but with the keyboard, I can't.

I think the trigger is when you open the window and activate the menu without clicking on the container (where the files and folders are located).

### ✔️ Expected Behavior

Opening the Context Menu with focus for use on the keyboard as we have in Windows (as it always worked)

### ❌ Actual Behavior

Unwanted crash bypassed only by mouse access when the menu is open!

### Other Software

_No response_
Repository: angular
Issue: Vite dev server crashes when HttpClient receives non-200 code
Labels: area: server,core: zoneless

### Command

serve

### Is this a regression?

- [x] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

v17

### Description

Basically, it's a duplicate of https://github.com/angular/angular-cli/issues/26192

But now it's here again with v19, zoneless and outputMode: 'server'.
Is this behaviour expected and not-an-issue on new setup?

### Minimal Reproduction

ng serve

### Exception or Error

_No response_

### Your Environment

HttpErrorResponse

### Anything else relevant?

_No response_
Repository: ollama
Issue: use the macOS electron app for Windows and Linux
Labels: feature request

I don't understand why the electron app is only for macOS when electron is perfectly capable of running on Windows and Linux.

features like #7097 can easily be adopted for all platforms if electron is used.
Repository: tensorflow
Issue: fatal error: 'NEON_2_SSE.h' file not found - macOS x86_64 build tensorflowlite_c library
Labels: stat:awaiting tensorflower,type:build/install,comp:lite,subtype:macOS,2.17

### Issue type

Build/Install

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

2.17.0

### Custom code

Yes

### OS platform and distribution

macOS

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

AppleClang 15.0.0.15000309

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

When trying to build the tensorflowlite_c lib according to [this](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/g3doc/guide/build_cmake.md) guide, the build fails on macOS x86_64 plattform with the following error code:
```output
 In file included from /Users/runner/work/tflite-c-lib/tflite-c-lib/tensorflow/tensorflow/lite/delegates/xnnpack/quantization_util.cc:21:
In file included from /Users/runner/work/tflite-c-lib/tflite-c-lib/tensorflow/tensorflow/lite/kernels/internal/optimized/optimized_ops.h:32:
In file included from /Users/runner/work/tflite-c-lib/tflite-c-lib/tensorflow/tensorflow/lite/kernels/internal/common.h:35:
/Users/runner/work/tflite-c-lib/tflite-c-lib/tensorflow/tensorflow/lite/kernels/internal/optimized/neon_check.h:25:10: fatal error: 'NEON_2_SSE.h' file not found
#include "NEON_2_SSE.h"  // IWYU pragma: export
         ^~~~~~~~~~~~~~
1 error generated.
```

### Standalone code to reproduce the issue

The error happens when I build using github workflows. [This](https://github.com/faressc/tflite-c-lib/actions/runs/11238016239/job/31241774171) is the action run.

### Relevant log output

```shell
In file included from /Users/runner/work/tflite-c-lib/tflite-c-lib/tensorflow/tensorflow/lite/delegates/xnnpack/quantization_util.cc:21:
In file included from /Users/runner/work/tflite-c-lib/tflite-c-lib/tensorflow/tensorflow/lite/kernels/internal/optimized/optimized_ops.h:32:
In file included from /Users/runner/work/tflite-c-lib/tflite-c-lib/tensorflow/tensorflow/lite/kernels/internal/common.h:35:
/Users/runner/work/tflite-c-lib/tflite-c-lib/tensorflow/tensorflow/lite/kernels/internal/optimized/neon_check.h:25:10: fatal error: 'NEON_2_SSE.h' file not found
#include "NEON_2_SSE.h"  // IWYU pragma: export
         ^~~~~~~~~~~~~~
1 error generated.
```
Repository: go
Issue: internal/trace: TestTraceStress/Stress failures
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
default <- pkg == "internal/trace" && test == "TestTraceStress/Stress"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8734639118266472945)):

    === RUN   TestTraceStress/Stress
        exec.go:213: test timed out while running command: /home/swarming/.swarming/w/ir/x/w/goroot/bin/go run testdata/testprog/stress.go
        trace_test.go:610: signal: killed
    --- FAIL: TestTraceStress/Stress (828.23s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: PowerToys
Issue: V0.85.1 does not install properly
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

V0.85.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

When I opened General -> Check for Updates it did NOT show that V0.85.1 was available.
Yet, I had received email alerts that this new version - bug fixes - was available.
You need to check that this "Check for Updates" feature works before releasing it to the public!!


### ✔️ Expected Behavior

Isn't this obvious to you??
When I "Check for Updates" I expect to see one of two responses:
1: Update available
2: You are already on latest release.

### ❌ Actual Behavior

Nothing happened!!
No responses whatsoever when I clicked on "Check for Updates"
BTW: why do you think I am reporting this?? Duh!!

### Other Software

_No response_
Repository: electron
Issue: [Bug]: Unfocusable panel does not respond to hover if it has a parent
Labels: platform/macOS,bug :beetle:,status/confirmed,component/BrowserWindow,has-repro-gist,32-x-y,33-x-y

### 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 bug report that matches the one I want to file, without success.

### Electron Version

32.1.2

### What operating system(s) are you using?

macOS

### Operating System Version

15.1 Beta

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

_No response_

### Expected Behavior

1. create a BrowserWindow with `type: "panel"`, `focusable: false`, and `parent: someOtherWindow`.
2. Hover over elements that have hover styles.
3. Hover styles should be displayed

### Actual Behavior

1. create a BrowserWindow with `type: "panel"`, `focusable: false`, and `parent: someOtherWindow`.
2. Hover over elements that have hover styles.
3. Hover styles are not displayed

### Testcase Gist URL

https://gist.github.com/e303ffd23323d240700cb12b681963e9

### Additional Information

_No response_
Repository: vscode
Issue: Signature verification failed with 'PackageIntegrityCheckFailed' error.
Labels: bug,extension-signature


Type: <b>Bug</b>

Ever since upgrading to the most recent release of vscode I cannot install or upgrade any vscode extensions.

Cannot install ... extension because Visual Studio Code cannot verify the extension signature

Signature verification failed with 'PackageIntegrityCheckFailed' error.

VS Code version: Code 1.94.0 (Universal) (d78a74bcdfad14d5d3b1b782f87255d802b57511, 2024-10-02T13:08:12.626Z)
OS version: Darwin arm64 23.6.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M1 Pro (10 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|2, 2, 2|
|Memory (System)|32.00GB (1.83GB free)|
|Process Argv|--crash-reporter-id dfc65e10-fbb4-4b6c-919e-dce0edfa49eb|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (23)</summary>

Extension|Author (truncated)|Version
---|---|---
unique-lines|bib|1.0.0
ruff|cha|2024.50.0
gitlens|eam|15.5.1
terraform|has|2.32.3
vscode-duplicate|mrm|1.2.1
vscode-docker|ms-|1.29.3
debugpy|ms-|2024.10.0
isort|ms-|2023.10.1
python|ms-|2024.14.1
vscode-pylance|ms-|2024.9.2
datawrangler|ms-|1.10.0
jupyter|ms-|2024.8.1
jupyter-renderers|ms-|1.0.19
vscode-jupyter-cell-tags|ms-|0.1.9
remote-ssh|ms-|0.114.3
remote-ssh-edit|ms-|0.87.0
remote-explorer|ms-|0.4.3
vscode-thunder-client|ran|2.27.0
vscode-xml|red|0.27.1
vscode-yaml|red|1.15.0
stardog-rdf-grammars|sta|0.2.1
even-better-toml|tam|0.19.2
gistfs|vsl|0.6.0


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
bdiig495:31013172
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
impr_priority:31102340
nativerepl1:31139838
refactort:31108082
pythonrstrctxt:31112756
flighttreat:31134774
wkspc-onlycs-t:31132770
nativeloc2:31134642
wkspc-ranged-t:31151552
cf971741:31144450
defaultse:31146405
iacca2:31150323
notype1:31151523
cc771715:31146322

```

</details>

<!-- generated by issue reporter -->
Repository: excalidraw
Issue: Word search highlighting is flipped in RTL languages
Labels: bug

The highlighting is in the wrong direction in RTL langs:
![Image](https://github.com/user-attachments/assets/a33752ab-dfaf-4346-98b9-f4b14d0cd4ab)
Repository: PowerToys
Issue: Please remove the artificial smooth scrolling from the Powertoys user interface
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

When scrolling in the PowerToys user interface, there is an annoying smooth scrolling effect that prevents fast and exact scrolling.
Power users usually hate it when smooth scrolling is forced upon them, at least if it's not configurable or can't be switched off.

### Scenario when this would be used?

Just use the type of scrolling that the user has set up in their Windows performance settings, and don't overwrite it with something you consider more appropriate. If reading the Windows settings should not be possible, just don't use smooth scrolling at all, which is the standard behavior of everything anyway.
![image](https://github.com/user-attachments/assets/f38ecb31-f571-4796-8f6f-091cc89ebf14)

### Supporting information

https://simonscodes.blogspot.com/2014/12/hello.html
https://github.com/simonzack/rich_edit_scroll
https://stackoverflow.com/questions/29683527/laggy-slow-mouse-wheel-scrolling-in-rich-edit-control-how-to-fix-this
https://www.pcreview.co.uk/threads/reward-how-the-can-i-disable-smooth-scrolling-in-wordpad.2817099
Repository: deno
Issue: Deno 2.0 RC Fails to Compile to Binary on Windows for Non-Administrator Users
Labels: needs info

Version: deno 2.0.0-rc.10 
v8 12.9.202.13-rusty
typescript 5.6.2

When trying to compile a simple Deno script (console.log("deno 2.0");) into binary on Windows, non-administrator users encounter the error below that prevent successful compilation.
<pre>
deno compile --output test.exe consolelog.ts
Check file:///C:/Users/User/workspace/work2024/consolelog.ts
Compile file:///C:/Users/User/workspace/work2024/consolelog.ts to test.exe
error: Writing temporary file 'test.exe.tmp-0468b123c82c0498'

Caused by:
    0: Failed reading: C:\Users\User\Application Data
    1: Access is denied. (os error 5)
</pre>
Repository: deno
Issue: `deno serve` should support `onListen` callback
Labels: feat,serve

Currently with `Deno.serve` you're able to know on which address you're listening to with `onListen`, but `deno serve` does not implement it:

```ts
export default {
  onListen:() => { /* call me maybe */ },
  fetch:() => new Response()
}
```

Use-case:
- knowing which port was chosen (useful when `--port 0`)
- dynamically set `--location` to allow `fetch()` on self
- post-listening setup
- etc
Repository: PowerToys
Issue: New+ enhanced feature request - multiple folders at once.
Labels: Needs-Triage

### Description of the new feature / enhancement

I have to create multiple folders
![SeasonFoldersExample](https://github.com/user-attachments/assets/06d8ea5b-8e76-49ca-9f24-148cb4981178)
 (e.g. S00, S01, S02, etc.) It would be nice to be able to use New+ to create those folders automatically. The way New+ seems to work now I'd have to put these folders inside a folder, then I'm just cutting and pasting those out of there manually (which I do already). It would be even better being able to highlight/select which folders to have New+ create. Because you may need 1 thru 4 or 0 thru 9, etc. 

### Scenario when this would be used?

For things like TV shows when there are multiple seasons.

### Supporting information

_No response_
Repository: rust
Issue: High memory usage with cargo build in match statement
Labels: I-crash,T-compiler,I-compilemem,C-bug,A-patterns

<!--
Thank you for finding an Internal Compiler Error! 🧊  If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.
http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/
-->
The memory usage gets high really quickly which causes my pc to crash.

### Code
Full git repo: https://github.com/Joshix-1/cargo-memory-leak
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=03d0fd2c2ceeb588e5297389a01f9fa9
```Rust
#[derive(Copy, Clone, Debug, Eq, PartialEq)]
#[repr(u8)]
pub enum FieldType {
    Air,
    Wood,
    SandSource,
    BlackHole,
    SandC0, SandC1, SandC2, SandC3, SandC4, SandC5, SandC6, SandC7,
    WaterC0, WaterC1, WaterC2, WaterC3, WaterC4, WaterC5, WaterC6, WaterC7,
}

macro_rules! sand { () => {
    FieldType::SandC0 | FieldType::SandC1 | FieldType::SandC2
    | FieldType::SandC3 | FieldType::SandC4 | FieldType::SandC5
    | FieldType::SandC6 | FieldType::SandC7
}; }

macro_rules! water { () => {
    FieldType::WaterC0 | FieldType::WaterC1 | FieldType::WaterC2
    | FieldType::WaterC3 | FieldType::WaterC4 | FieldType::WaterC5
    | FieldType::WaterC6 | FieldType::WaterC7
}; }

macro_rules! falls {() => { sand!() | water!() };}

macro_rules! not_solid {
    () => { FieldType::Air | water!() };
}

impl FieldType {
    pub const fn is_sand(self) -> bool { matches!(self, sand!()) }

    pub const fn is_water(self) -> bool { matches!(self, water!()) }
}

fn main() {
    let arr = &mut [FieldType::Air; 4];
    let [ref mut a, ref mut b, ref mut c, ref mut d] = arr; 
    let cell: (
        (&mut FieldType, &mut FieldType),
        (&mut FieldType, &mut FieldType),
    ) = ((a, b), (c, d));
    match cell {
        (
            (sand0 @ falls!(), sand1 @ falls!()),
            (unsolid0 @ not_solid!(), unsolid1 @ not_solid!()),
            // compiles without the if in the next line
        ) if unsolid0.is_water() != sand0.is_water() || unsolid1.is_water() != sand1.is_water() => {
            if unsolid0.is_water() != sand0.is_water() {
                (*sand0, *unsolid0) = (*unsolid0, *sand0);
            }
            if unsolid1.is_water() != sand1.is_water() {
                (*sand1, *unsolid1) = (*unsolid1, *sand1);
            }
        }
        _ => {}
    }
}
```


### 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 --version --verbose
rustc 1.81.0 (eeb90cda1 2024-09-04)
binary: rustc
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c
commit-date: 2024-09-04
host: x86_64-unknown-linux-gnu
release: 1.81.0
LLVM version: 18.1.7
```
also on playground, nightly and stable

### Error output

```sh
$ env RUST_BACKTRACE=1 cargo build 2> build.err > build.out
# crash of xserver
$ du -bs build.*
49	build.err
0	build.out
$ cat build.err
   Compiling sandrs v0.1.1 (/tmp/tmp.aULMeIa66O)
```
Repository: Python
Issue: Request to review my Pull Request which was created a week ago (#11671)
Labels: awaiting triage

### What would you like to share?

I create a pull request for the Implementation of Density-based spatial clustering of applications with noise (DBSCAN) ML Algorithm #11671. Its been a week and I still didn't get any approval or response in order to change the code if there is anything necessary to do so. Hence, I kindly request the maintainers to look into my PR and give your valuable feedback to do the necessary changes and then merge it to the main branch. Thanks for your time.

### Additional information

_No response_