sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: GPUParticles2D offsets on collision with LightOccluder2D but ONLY when the Camera2D node is rotated. 
Labels: bug,topic:2d,topic:particles

### Tested versions

- Reproducable in Godot 4.2.1 and 4.2.2

### System information

Windows 11 - Godot v4.2.1 - Compatibility Renderer - Intel UHD Graphics 630

### Issue description

![particle_collision_bug_godot](https://github.com/godotengine/godot/assets/83003535/0d3b4941-266d-4608-9524-8a079f63339a)

This is a basic `GPUParticle2D` node colliding with a `LightOccluder2D`. It has collisions mode set as `Rigid` and a `Bounce` of 0.6. While it works without the Camera being rotated, it seems to break when the Camera rotates. **The particles offset _after_ it collides with the Light Occluder, and it ONLY happens when the Camera2D node is rotated.** This issue occurs regardless of `Bounce` or `Friction` being greater than 0. It always occurs when collisions mode is set as `Rigid`. No other option seems to cause the issue. I have checked the project in Mobile and Forward+ as well and the issue persists.

The scale of the particles also doesn't change the outcome nor does the rotation. `Use Scale` is turned on, but turning it off doesn't solve the issue either. `Local Coords` option on the Particle node is off so I don't think that is the issue, and the `GPUParticles2D` node is not the parent of the `Camera2D` node so I don't think it's an issue with SceneTree order either. `Fixed FPS` is set to 0 in this example, but setting it to the default value of 30 doesn't solve the issue, nor does setting it to a higher value. This appears to be an issue with how physics is calculated on Particle instances.

### Steps to reproduce

1. Create a new project and make a new scene.
2. Add a LightOccluder2D to your scene.
3. Add a GPUParticles2D and set collision mode to `Rigid`.
4. Add a Camera2D, rotate the node, then turn `Ignore Rotation` off. 

### Minimal reproduction project (MRP)

[GodotParticles2DCollisionsBug.zip](https://github.com/godotengine/godot/files/15350390/GodotParticles2DCollisionsBug.zip)
Repository: next.js
Issue: Layout doesn't cache and gets 1 server re-render for each broken image link
Labels: bug

### Link to the code that reproduces this issue

https://github.com/Kirill-Ponomarenko/next-cache-bug-2

### To Reproduce

1. Run `pnpm build`
2. Run `pnpm start`
3. Open `http://localhost:3000/`
4. See `Layout render` messages in the server console on every page load indicating Layout re-render

### Current vs. Expected behavior

#### Current:
Layout gets server side re-renders if Page has  images with src to files not presented at the build time
No warnings during build or runtime

#### Expected:
Layout doesn't re-render
or
Warnings during build time



### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro     
  Available memory (MB): 16335
  Available CPU cores: 12
Binaries:
  Node: 18.18.2
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.3.0-canary.68 // Latest available version is detected (14.3.0-canary.68).
  eslint-config-next: N/A
  react: 19.0.0-beta-04b058868c-20240508
  react-dom: 19.0.0-beta-04b058868c-20240508
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next start (local)

### Additional context

_No response_
Repository: pytorch
Issue: Inductor: Codegen for sympy Trunc is incorrect
Labels: triaged,oncall: pt2,module: dynamic shapes,module: inductor

### 🐛 Describe the bug

I'm working on a general refactor that's going to fix this, but this was a really clean test case that I wanted to file for posterity.

This program:

```
import torch
import torch._dynamo.config
import math

torch._dynamo.config.capture_scalar_outputs = True

def f(x):
    r = math.sqrt(x.size(0))
    r = r ** 70
    return torch.tensor(math.trunc(r), dtype=torch.float64, device='cuda')

cf = torch.compile(fullgraph=True, dynamic=True)(f)

print(math.frexp(f(torch.randn(4, device='cuda')).item()))
print(math.frexp(cf(torch.randn(4, device='cuda')).item()))
```

prints

```
(0.5, 71) 
(0.9999999995343387, 31)
```

The problem is:

```
    def _print_Trunc(self, expr):
        assert len(expr.args) == 1
        return (
            f"libdevice.trunc({self._print(expr.args[0])}).to({V.kernel.index_dtype})"
        )
```

trunc on float inputs should not convert to index type

### Versions

main

cc @msaroufim @bdhirsh @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: godot
Issue: VideoStreamPlayer not drawing anything when stopped, including not showing in editor
Labels: discussion,needs testing,topic:gui

### Tested versions

v4.3.dev6.official [89850d553]

### System information

macOS 14.5

### Issue description

It appears the VideoStreamPlayer doesn't render any content when stopped, so it's invisible until playing. What I'd expect is that when a video stream is loaded, it would show the first frame of this video. In the editor this is a bit confusing as it appears like the video isn't loaded and makes layouting more difficult, and in the running project it means you have to do a couple of extra steps to get the video to show in a paused state before you start playing it. 

![Screenshot 2024-05-17 at 15 42 02](https://github.com/godotengine/godot/assets/17763524/a53e0341-04c2-4023-9a1a-6306f2fdbf83)

I can tell that the video is loaded since the control locks its' minimum size to the video size. If you run the project it's the same, the video player is blank until you call `play()` on the player but then the video displays as expected. If you then call `stop()` it becomes blank again.

![Screenshot 2024-05-17 at 15 42 14](https://github.com/godotengine/godot/assets/17763524/cf39bd3a-653f-4ce3-a942-fa96ba24c487)

Once you've played at least one frame you can use `paused = true` to have the video display and not be playing. However, it seems it needs to play at least a little to load a first frame, so setting the player to `autoplay = true` and `paused = true` initially doesn't work. And in the editor there's no way to start playing as far as I can tell.

### Steps to reproduce

- Add a VideoStreamPlayer to a UI scene
- Set the stream to a supported video file (needs to be a Ogg Theora .ogv file), for example this file: [test_video.ogv](https://www.lostminds.com/godot/test_video.ogv)
- Observe the VideoStreamPlayer size change, but nothing showing

### Minimal reproduction project (MRP)

[video_player_test.zip](https://github.com/godotengine/godot/files/15350385/video_player_test.zip)
Repository: storybook
Issue: [Bug]: In 8.1.1 the empty state of controls addon has a bottom bar which wasn’t there before.
Labels: bug,good first issue,help wanted,ui,sev:S4

### Describe the bug
In 8.1.1, the empty state of controls addon has a bottom bar which wasn’t there before. The other empty states don't exhibit this. You can also see it in dark mode, but it's less evident because it's dark.

![image](https://github.com/storybookjs/storybook/assets/263385/20532360-3708-4ea6-92f9-91ac42fa0444)



### To Reproduce

https://stackblitz.com/github/storybookjs/sandboxes/tree/next/react-vite/default-js/after-storybook?file=README.md&preset=node

### System

```bash
It's reproducible in the sandbox
```


### Additional context

_No response_
Repository: electron
Issue: [Bug]: URL did not change after 302 response using protocol handler
Labels: component/protocol,bug :beetle:,status/confirmed,has-repro-gist,30-x-y,31-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

30.0.6

### What operating system are you using?

Windows

### Operating System Version

Windows 10 22H2 19045.4291

### What arch are you using?

x64

### Last Known Working Electron version

Unknown

### Expected Behavior

When using `http`/`https` protocol.handle with `net.fetch` in Electron and the server returns a 302 status code with a new Location header, although Electron accurately shows the correct header and status code in the `onHeadersReceived` and `onBeforeRedirect` events, it returns a 200 status code to the browser and the URL is not changed.

The browser should be redirected to `https://www.google.com`, and the status code should be 302.

### Actual Behavior

The browser returns a 200 status code, and the URL is not changed, but the content from the new page is displayed

### Testcase Gist URL

https://gist.github.com/shadaxv/fe1242885053bdf4ed6a27c9ecc97049

### Additional Information

_No response_
Repository: go
Issue: cmd/go: generate: be more informative/verbose
Labels: NeedsInvestigation,FeatureRequest,GoCommand

Running `go generate ./...` can take a while in a large project, but it is not easy to know why. It doesn't print a summary of what commands it ran, and neither -x nor -v lead to intelligible output. It would be nice if -v would print additional logging of the start and end time of each command, along with the location of the directive that triggered it, in a format such as this:
```
internal/protocol/command/interface.go:5: go run -tags=generate generate.go [start] 
...logs...
internal/protocol/command/interface.go:5: go run -tags=generate generate.go [success, 1.23s] 
```

@matloob
Repository: next.js
Issue: Fill property for Next Image doesn't seem to work.
Labels: bug,Image (next/image)

### Link to the code that reproduces this issue

https://github.com/Elindo586/nextprojectb/blob/main/pages/services/fluid-analysis.js

### To Reproduce

So, I can't get this to work.  Might not be an issue, but I have to report it as an issue because I didn't find a way around it.


Sample code link here:
https://github.com/Elindo586/nextprojectb/blob/main/pages/services/fluid-analysis.js
Line 105
It can be reproduce by turning on the commented lines, and commenting the width and height.

Directions followed from this link:
https://nextjs.org/docs/pages/api-reference/components/image

 ```
<div className="col-md-9">
          <div className=" oil-analysis-span">
            <Image
              // fill={true}
              id="oil-analysis2"
              src="/images/oil-analysis2.png"
              alt="oil-analysis"
              // sizes="(max-width: 768px) 100vw, (max-width: 1200px) 50vw, 33vw"
              width={700}
              height={400}
            />
          </div>
```

Related CSS is this:
Error can be produce by turning on the commenting line of `position: absolute;`

```
.oil-analysis-span {
  padding-left: 2em;
  position: relative;
}

#oil-analysis2 {
  height: auto;
  width: 50%;
  /* position: absolute; */
  object-fit: contain;
  object-position: center;
  margin-right: 1em;
}

```

### Current vs. Expected behavior

The fill property for the Image tag just doesn't show the image at all.

If I give the image container dimensions, then it shows the image, but it isn't responsive to the down-size of the screen.

I am trying to get rid of image size errors from the lighthouse, and apparently using the fill property would automatically re-size the image, and it would be an alternative for scrset.

I would rather use next/image if it can resize the image, instead of manually resizing images and use the plain srcset property.



### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 16263
  Available CPU cores: 8
Binaries:
  Node: 20.12.2
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 4.9.5
Next.js Config:
  output: N/A
```


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

Image (next/image)

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

next dev (local), next build (local), next start (local)

### Additional context

_No response_
Repository: react
Issue: react-compiler transformed conditional useCallback call incorrectly
Labels: Component: Optimizing Compiler

## Summary

Reproduction: https://github.com/beeebox/react-compiler-conditional-access-prop-repro

The reproduction is using react-compiler integration with Next.js

### Steps to reproduce

1. Clone this repository
2. Run `pnpm install`
3. Run `pnpm dev`
4. Open `http://localhost:3000` in your browser
5. You'll see the error in the dialog


### Expected behavior

No error should be thrown

### Actual behavior

Error is thrown

> TypeError: Cannot read properties of null (reading 'name')


### Root cause

The `user` object should be actually conditionally rendered since there's `user ?` condition to check to render the component when `user` is truthy. But react compiler still uses the `user.name` as condition for comparing with the memoized cache value. The check is hoisted in the render where the `user` can be null. This will trigger the error where we don't need to render the sub component where the callback is being used.

```js
// Client output bundle for page.js
    _s();
    const $ = (0,react_compiler_runtime__WEBPACK_IMPORTED_MODULE_1__.c)(10);
    if ($[0] !== "5a27fdcf38c7f1295c3b71a91e1e520dce2311adaca1eb5d5515c0f76ddb4f25") {
        for(let $i = 0; $i < 10; $i += 1){
            $[$i] = Symbol.for("react.memo_cache_sentinel");
        }
        $[0] = "5a27fdcf38c7f1295c3b71a91e1e520dce2311adaca1eb5d5515c0f76ddb4f25";
    }
    const [user, setUser] = (0,react__WEBPACK_IMPORTED_MODULE_2__.useState)(null);
    let t0;
    if ($[1] !== user.name) {
        t0 = ()=>{
            console.log("Log user", user.name);
        };
        $[1] = user.name;
        $[2] = t0;
    } else {
        t0 = $[2];
    }
    const logUser = t0;
```

### Potential Solution

Detect the condition of component rendering and conditionally update the callback?
Repository: vscode
Issue: 'Folders' menu item is disabled in the explorer
Labels: bug,file-explorer

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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.90.0-insider (user setup)
- OS Version: Windows_NT x64 10.0.22631

Commit: 0cd8d6ac480bc5b4e2a2d7f1eb87eaff9f7d47e1
Date: 2024-05-16T05:49:53.998Z
Electron: 29.3.1
ElectronBuildId: 9464424
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0

Steps to Reproduce:
1. Open a folder in vscode
2. Focus on the explorer
3. Open the elipses menu on the explorer

## What is seen in desktop vscode:

![image](https://github.com/microsoft/vscode/assets/13074644/b25ba80a-4531-453c-b18e-e2dd7876925f)

## In github.dev:
![image](https://github.com/microsoft/vscode/assets/13074644/f8380a7a-b221-4062-be62-02909abfec01)


`Folders` is always greyed out and not toggleable. It would be great if there was an option to hide it
Repository: kubernetes
Issue: containerized protobuf codegen does not handle .go-version / GOTOOLCHAIN properly
Labels: kind/bug,sig/testing,sig/architecture,area/code-organization,triage/accepted

Seen in https://github.com/kubernetes/kubernetes/pull/124922

```
+++ command: bash "hack/make-rules/../../hack/verify-codegen.sh"
go version go1.22.3 linux/amd64
+++ [0517 06:22:42] Generating protobufs for 67 targets
+++ [0517 06:22:42] protoc 23.4 not found (can install with hack/install-protoc.sh); generating containerized...
+++ [0517 06:22:42] Verifying Prerequisites....
+++ [0517 06:22:43] Building Docker image kube-build:build-71fc6bd7d6-5-v1.28.0-go1.21.10-bullseye.0
+++ [0517 06:24:57] Creating data container kube-build-data-71fc6bd7d6-5-v1.28.0-go1.21.10-bullseye.0
+++ [0517 06:24:58] Syncing sources to container
+++ [0517 06:25:03] Output from this container will be rsynced out upon completion. Set KUBE_RUN_COPY_OUTPUT=n to disable.
+++ [0517 06:25:03] Running build command...
go: downloading go1.22.3 (linux/amd64)
go: download go1.22.3 for linux/amd64: toolchain not available
!!! [0517 06:25:04] Call tree:
!!! [0517 06:25:04]  1: build/../build/common.sh:489 kube::build::run_build_command_ex(...)
!!! [0517 06:25:04]  2: build/run.sh:39 kube::build::run_build_command(...)
!!! [0517 06:25:04] Call tree:
!!! [0517 06:25:04]  1: hack/update-codegen.sh:919 codegen::protobuf(...)
+++ exit code: 1
+++ error: 1
[0;31mFAILED[0m   verify-codegen.sh	148s
```

Something is not working properly between .go-version → GOTOOLCHAIN when the go version inside this specific container doesn't match

/assign 
/cc @BenTheElder @MadhavJivrajani
Repository: angular
Issue: DevTools cause Firefox to consume high CPU and memory on Microsoft 365 websites
Labels: area: devtools,bug

### Is this a bug report or a feature request?

- [X] Bug Report
- [ ] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

When accessing any Microsoft sharepoint or office page, Firefox starts to use around 50% CPU and uses an increasing amount of memory, way beyond 10GB after a few minutes. 
Disabling Angular DevTools resolves the issue. 

### Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

Expected behavior: No noticeable performance impact by Angular DevTools, especially on non-Angular websites
Actual behavior: Extreme resource usage on some websites when enabling Angular DevTools

### Please provide a screenshot if possible [Bug Report only]

_No response_

### Please provide the exception or error you saw [Bug Report only]

```true
I have tried to get a memory dump or profiling session from Firefox but it is incredibly difficult given that Firefox itself starts to hang after a few seconds and the only way to get it to be responsive again is to close the tab, which will also free up all memory. 

However, I have noticed that the error started roughly 1 week ago, when I also received the latest DevTools update 1.0.16. 
This update mentions: "Adding support for inspecting Angular applications inside iframes"

When I leave the console open when loading sharepoint it reports hundreds of these messages (among other things): 
IFrame: origin https://autologon.microsoftazuread-sso.com is not in the allowed list.
or: 
IFrame: Integrated Windows Authentication failed with status code 401 (Unauthorized).

These messages do not appear once I disable the extension. 

Blind guess: 
I come to the conclusion that the IFrame-inspection causes some issue with the Microsoft SSO mechanism. I read somewhere that authorization inside IFrames requires special attention due to clickjacking attacks: https://datatracker.ietf.org/doc/html/rfc6819#section-4.4.1.9
Maybe the inspection is interfering with this?
```


### Is this a browser-specific issue? If so, please specify the device, browser, and version. [Bug Report only]

```true
Running Firefox 126.0 (64-Bit) on Windows 11
```


### Description [Feature Request only]

_No response_

### Proposed solution [Feature Request only]

_No response_

### Alternatives considered [Feature Request only]

_No response_
Repository: storybook
Issue: [BUG] Addon backgrounds - There is no "Reset background" option
Labels: bug,addon: backgrounds

This is still an issue in storybook 8. There is still no "Reset background" option (as in reset the background to the default of the story).

1. Go to the Image story: 
https://next--630511d655df72125520f051.chromatic.com/?path=/story/addons-backgrounds-parameters--image
2. Select "Clear background", the querystring becomes `...&globals=backgrounds.value:transparent`
3. Go the Gradient story (1 step above in the tree)
![image](https://github.com/storybookjs/storybook/assets/31220528/d15d362b-8376-4b6a-8a65-c63ecb763a9a)
4. The background of the Gradient story is still cleared instead of the default "gradient" background because the querystring still contains  `...&globals=backgrounds.value:transparent`

I agree that the title of this issue can be confusing. It's not about the "Clear background" option being wrong, it's about a "Reset background (to default)" option that's missing.

And combined with the weird behavior that the background is carried over to other stories if it is available, but resets to the default background when it's not available in a story. Which we cannot use as a workaround, because we cannot remove the "Clear background" option from the available backgrounds in a story.

_Originally posted by @WesselKroos in https://github.com/storybookjs/storybook/issues/14030#issuecomment-2115542632_
Repository: angular
Issue: docs: is not recognized as an internal or external command, operable program or batch file
Labels: area: docs-infra

### Describe the problem that you experienced

```
D:\Applications\docs\angular.io\angular>yarn docs
yarn run v1.22.19
$ [[ -n $CI ]] && echo 'Cannot run this yarn script on CI' && exit 1 || yarn bazel run //adev:serve --fast_adev
'[[' is not recognized as an internal or external command,
operable program or batch file.
$ D:\Applications\docs\angular.io\angular\node_modules\.bin\bazel run //adev:serve --fast_adev
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
INFO: Analyzed target //adev:serve (1319 packages loaded, 82779 targets configured).
INFO: Found 1 target...
ERROR: D:/applications/docs/angular.io/angular/adev/src/content/tutorials/homepage/BUILD.bazel:12:20: Action adev/src/content/tutorials/homepage/homepage failed: (Exit 1): playground.bat failed: error executing command bazel-out\x64_windows-opt-exec-2B5CBBC6\bin\external\npm\@angular\docs\pipeline\playground.bat adev/src/content/tutorials/homepage external/npm/@angular/docs/pipeline/tutorials/common ... (remaining 2 arguments skipped)
'""' is not recognized as an internal or external command,
operable program or batch file.
ERROR: D:/applications/docs/angular.io/angular/adev/src/content/tutorials/playground/BUILD.bazel:10:20: Action adev/src/content/tutorials/playground/playground failed: (Exit 1): playground.bat failed: error executing command bazel-out\x64_windows-opt-exec-2B5CBBC6\bin\external\npm\@angular\docs\pipeline\playground.bat adev/src/content/tutorials/playground external/npm/@angular/docs/pipeline/tutorials/common ... (remaining 2 arguments skipped)
'""' is not recognized as an internal or external command,
operable program or batch file.
```

### Describe what you were looking for in the documentation

I'm cloning angular repo and i want to serve locally, but when i run command "yarn docs", i got an error