sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Cannot make `intersect_ray` work with viewport's `own_world`
Labels: bug,topic:physics,topic:3d

### Godot version

v3.4.stable.mono.official [206ba70f4]

### System information

macOS Catalina 10.15.7 (19h15), MacBook Air (Retina, 13-inch, 2020), 1.1 GHz Dual-Core Intel Core i3, 8 GB 3733 MHz LPDDR4X, Intel Iris Plus Graphics 1536 MB

### Issue description

Hi,

I am trying to intersect a ray in a viewport that is not the root viewport but it never detects a collision.

My assumption is that if I create a viewport and set its `world`/`own_world` (in order to isolate its children from those of other viewports) that I should be able to cast a ray via a camera of that scene and detect collisions with children of that viewport.

I've done some sanity testing to ensure I can get a vanilla setup to work but as soon as I introduce an `own_world` to the viewport nothing works.

Am I missing / misunderstanding something? 

<img width="1136" alt="image" src="https://user-images.githubusercontent.com/4316458/176060270-b5aa9ee2-c647-4533-9a17-0e0d065c8c3a.png">

### Steps To Reproduce

Attached minimal repro project has a slowly spinning cylider and displays the result of a ray intersection using the mouse coordinates in an on-screen label each frame. Visible collision shapes is enabled for **testing.**

There is a boolean `var demo_issue = false` that toggles between showing the simple case that works (to show that the minimal repro code is generally valid) and the scenario I expect to work but does not.

Sanity check that works (demo_issue = false):
* The viewport's world/own_world is never set
* We perform the intersect_ray on get_tree().root.world

Example that does not work as expected (demo_issue = true):
* The viewport's world/own_world is set
* We perform the intersect_ray on viewport.world

### Minimal reproduction project

[62474.zip](https://github.com/godotengine/godot/files/8996504/62474.zip)
Repository: pytorch
Issue: Tracker: Slow gradcheck failures possibly indicating incorrect gradients
Labels: module: autograd,triaged,actionable

### 🐛 Describe the bug

For a very long time, most tests are being [skipped](https://ossci-raw-job-status.s3.amazonaws.com/log/7032407678) by slow gradcheck (see https://github.com/pytorch/pytorch/issues/80314#issuecomment-1168074007):
At least the following are failing in slow gradcheck (There are probably a lot more, but we can't see those right now because the test is timing out): 

- [ ] test_fn_fwgrad_bwgrad___rmod___cuda_float64 (non-differentiable points encountered when sample inputs are large)
- [ ] test_fn_fwgrad_bwgrad__masked_prod_cuda_complex128
- [ ] test_fn_fwgrad_bwgrad__masked_prod_cuda_float64
- [ ] test_fn_fwgrad_bwgrad_cat_cuda_complex128
- [ ] test_fn_fwgrad_bwgrad_cholesky_inverse_cuda_complex128
- [ ] test_fn_fwgrad_bwgrad_copysign_cuda_float64
- [ ] test_fn_fwgrad_bwgrad_fft_*
- [ ] test_fn_fwgrad_bwgrad_float_power_cuda_complex128
- [ ] test_fn_fwgrad_bwgrad_float_power_cuda_float64
- [ ] test_fn_fwgrad_bwgrad_fmod_cuda_float64 (probably same issue as `__fmod__`)
- [ ] test_fn_fwgrad_bwgrad_linalg_householder_product_cuda_complex128
- [ ] test_fn_fwgrad_bwgrad_linalg_lu_cuda_float64
- [ ] test_fn_fwgrad_bwgrad_linalg_lu_factor_ex_cuda_float64
- [ ] test_fn_fwgrad_bwgrad_linalg_matrix_power_cuda_complex128
- [ ] test_fn_fwgrad_bwgrad_remainder_cuda_float64
- [ ] test_fn_fwgrad_bwgrad_repeat_cuda_complex128
- [ ] test_fn_fwgrad_bwgrad_prod_cuda_complex128
- [ ] test_fn_fwgrad_bwgrad_slice_scatter_cuda_float64
- [ ] test_fn_fwgrad_bwgrad_tile_cuda_complex128
- [ ] test_fn_fwgrad_bwgrad_pow_cuda_float64
- [ ] test_fn_fwgrad_bwgrad_pow_cuda_complex128
- [ ] test_fn_fwgrad_bwgrad_zero__cuda_complex128
- [ ] test_fn_gradgrad_linalg_lu_factor_cuda_float64
- [ ] test_fn_grad_div_trunc_rounding_cuda_float64
- [ ] test_fn_grad_div_floor_rounding_cuda_float64

See https://ossci-raw-job-status.s3.amazonaws.com/log/7034710626

The failures don't necessarily mean the formulas are wrong, `__rmod__` (and possibly also `fmod`) for example only fails when perturbation of eps will crosses a point of non-differentiability, and when sample inputs are large enough that happens with high probability.


### Versions

main

cc @ezyang @gchanan @zou3519 @albanD @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: next.js
Issue: Next loads a library's CommonJS module on the server and the ES Module in the browser
Labels: bug,linear: next

### Verify canary release

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

### Provide environment information

   Operating System:
      Platform: linux
      Arch: x64
      Version: #43-Ubuntu SMP Wed Jun 15 12:54:21 UTC 2022
    Binaries:
      Node: 16.15.0
      npm: 8.8.0
      Yarn: 1.22.15
      pnpm: 6.11.0
    Relevant packages:
      next: 12.1.7-canary.50
      eslint-config-next: 12.1.6
      react: 18.2.0
      react-dom: 18.2.0

### What browser are you using? (if relevant)

Chrome 103 (though it's not relevant)

### How are you deploying your application? (if relevant)

Happens in local development

### Describe the Bug

See the README of the minimal repro here: https://github.com/srmagura/skeleton-min-2.

### Expected Behavior

The ES module should be loaded for both the server and browser.

### Link to reproduction

https://github.com/srmagura/skeleton-min-2

### To Reproduce

See the README of the minimal repro here: https://github.com/srmagura/skeleton-min-2.
Repository: pytorch
Issue: [c10d] Async object-based collectives
Labels: oncall: distributed,triaged,module: c10d

### 🚀 The feature, motivation and pitch

Feature request for supporting an async mode for object-based collectives was raised in https://discuss.pytorch.org/t/how-can-i-receive-the-outputs-from-dist-all-gather-object-asynchronously/155004. Creating this issue to track support for all object-based collectives to be async.

### Alternatives

_No response_

### Additional context

_No response_

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang @kwen2501
Repository: pytorch
Issue: [DDP] output_device argument appears completely unused
Labels: oncall: distributed,triaged,better-engineering,module: ddp

### 🐛 Describe the bug

In current DDP implementation, the only reference to `self.output_device` is in DDP logging to log construction data: https://github.com/pytorch/pytorch/blob/master/torch/nn/parallel/distributed.py#L760.

It does not actually appear used anywhere, possibly we should mark this argument as deprecated / unused.



### Versions

main

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang @kwen2501
Repository: yt-dlp
Issue: Add ability to filter (skip) download of specific fragments
Labels: enhancement,core:downloader

### Checklist

- [X] I'm requesting a feature unrelated to a specific site
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I'm running yt-dlp version **2022.06.22.1** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues including closed ones. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Description

Couldn't find any information anywhere else so asking here. I think it would be a very beneficial feature to allow for the skipping of fragments in the hls/dash downloader, either by index or by matching the URL to a regex (or both). This would come in very handy, especially for videos with many `#EXT-X-DISCONTINUITY`s.  For example, I have a playlist like:

```
#EXTM3U
#EXT-X-VERSION:3
#EXT-X-TARGETDURATION:6
#EXT-X-PLAYLIST-TYPE:EVENT
#EXT-X-MEDIA-SEQUENCE:0
#EXT-X-DISCONTINUITY
#EXT-X-DISCONTINUITY
#EXT-X-DISCONTINUITY
#EXT-X-DISCONTINUITY
#EXT-X-DISCONTINUITY
#EXT-X-DISCONTINUITY
#EXT-X-DISCONTINUITY
#EXT-X-PROGRAM-DATE-TIME:2022-06-26T19:59:59.253Z
#EXT-X-KEY:METHOD=NONE
#EXTINF:5.005,
https://dai.google.com/linear/pods/v1/seg/cmsid/2473515/video/7237a134-b40b-4b95-b5f8-53138971fe48/pod/4/profile/5600K/36.ts?pd=210010&sd=5005&so=175175&cust_params=evnt%3D0%26podID%3D4
#EXTINF:1.568233,
https://dai.google.com/linear/pods/v1/seg/cmsid/2473515/video/7237a134-b40b-4b95-b5f8-53138971fe48/pod/4/profile/5600K/37.ts?pd=210010&sd=1568&so=180180&cust_params=evnt%3D0%26podID%3D4&last=true
#EXT-X-DISCONTINUITY
#EXT-X-KEY:METHOD=AES-128,URI="https://playback.svcs.mlb.com/silk/events/98dc33c2-1c33-46f5-9571-c23fbf6c2c95/media/b2babd8e-5de3-42ef-b139-e93075891cc9/keys/c25fe137-47c5-422e-a59f-fea8820f7e5d",IV=0xB076CAF2AB75251CAD08EB89954DB438
#EXTINF:5.005,
177/20/00/05_872.ts
#EXTINF:5.005,
177/20/00/10_877.ts
#EXTINF:5.005,
177/20/00/15_882.ts
...
```

The segments with `https://dai.google.com` are advertisements, and not only would it be great to have these simply skipped, but in this case, the default postprocessor arguments result in a video that is only the advertisements and nothing else, due to the way ffmpeg handles the different streams. Allowing users to filter out fragments meeting certain criteria would greatly assist in the ease of downloading funky streams.

e.g. `--skip-fragments:regex 'dai.google.com'` or `--skip-fragments:index 1:100`

Considering the hls downloader already automatically filters out uplynk ads and the like, hopefully this wouldn't be too difficult to implement. Happy to help with this too if there is interest.

### Verbose log

_No response_
Repository: deno
Issue: lsp: support quick fix "update specifier to its redirected specifier" in import maps
Labels: suggestion,lsp

It's currently supported in modules but there are no diagnostics available in the import map.
![CleanShot 2022-06-28 at 10 12 25](https://user-images.githubusercontent.com/29819102/176094755-8dac0d3a-84e9-4df1-95e0-3613f63fbbce.gif)
![CleanShot 2022-06-28 at 10 14 58@2x](https://user-images.githubusercontent.com/29819102/176094832-e063d76c-fd88-4781-8546-e06fd045b781.png)
Repository: kubernetes
Issue: client library module versioning
Labels: sig/api-machinery,sig/architecture,triage/accepted

> I am well aware of the storied past that kubernetes has had with module versioning, thus I will try and work off the [current state](https://github.com/kubernetes/client-go#versioning) of the world, but it would be interesting to understand how this impacts old projects virally entangled with [replace](https://go.dev/doc/modules/gomod-ref#replace).

If I am developing an internal tool that only imports `k8s.io/client-go/...` and only runs on a cluster that I control, I can trivially pick the exact kubernetes version that I am running, `go get k8s.io/client-go@v0.X.Y` and be happy.

Per [KEP 917](https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/917-go-modules), "consumers are limited to a single copy of kubernetes libraries among all dependencies". As such, if I am running two clusters with different versions and I actually need `v0.20.0` and `v0.21.0`, say due to a feature deprecation, I need to maintain two different versions of my tool?

Taking this a step further, if I maintain a tool that contains a library component and links against the `k8s.io/...` packages, do I need to release separate versions for every kubernetes minor?

Finally, I apologize if this is covered in a document or manual somewhere, but I cannot find it documented anywhere; hence my creation of this issue.
Repository: pytorch
Issue: Torch fx print line number of each node
Labels: triaged,module: fx

### 🚀 The feature &motivation

It can be very helpful if each node in the graph, generated by symbolic_trace, would include the full path and line number of this operator, similarly to torch.onnx.export verbose output. For example:
%180 : Float(1, 512, 7, 7, strides=[25088, 49, 7, 1], requires_grad=1, device=cpu) = onnx::**Add**(%240, %243) # **C:\ProgramData\Miniconda3\lib\site-packages\torchvision\models\resnet.py:80:0**
One of possible use cases for such feature is to locate specific functions or attribute queries such as: x.size(), x.reshape 

Best regards


### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @SherlockNoMad
Repository: pytorch
Issue: CMake Error: File /opt/pytorch/build_variables.bzl does not exist.
Labels: triaged,module: regression,module: docker

### 🐛 Describe the bug

Following #80212, the docker build command failed again today on a freshly cloned repo:

```sh
$ git clone --recursive https://github.com/pytorch/pytorch
$ cd pytorch
$ DOCKER_BUILDKIT=1 docker build . > log.txt 2>&1
```

[log.txt](https://gist.github.com/iago-lito/61358872444050cfbbff05d18ccfea00)

Maybe related:  #78542 ?

### Versions

```sh
$ python collect_env.py
Collecting environment information...
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A

OS: Arch Linux (x86_64)
GCC version: (GCC) 12.1.0
Clang version: 13.0.1
CMake version: version 3.23.2
Libc version: glibc-2.35

Python version: 3.10.5 (main, Jun  6 2022, 18:49:26) [GCC 12.1.0] (64-bit runtime)
Python platform: Linux-5.18.7-arch1-1-x86_64-with-glibc2.35
Is CUDA available: N/A
CUDA runtime version: 11.7.64
GPU models and configuration: GPU 0: NVIDIA GeForce GTX 960M
Nvidia driver version: 515.48.07
cuDNN version: Probably one of the following:
/usr/lib/libcudnn.so.8.4.0
/usr/lib/libcudnn_adv_infer.so.8.4.0
/usr/lib/libcudnn_adv_train.so.8.4.0
/usr/lib/libcudnn_cnn_infer.so.8.4.0
/usr/lib/libcudnn_cnn_train.so.8.4.0
/usr/lib/libcudnn_ops_infer.so.8.4.0
/usr/lib/libcudnn_ops_train.so.8.4.0
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A

Versions of relevant libraries:
[pip3] numpy==1.22.4
[pip3] torch==1.11.0
[pip3] torchvision==0.12.0a0+1665451
[conda] Could not collect
```
Repository: flutter
Issue: "flutter test" does not recognize generated test files ("my_gen_test.g.dart")
Labels: a: tests,c: new feature,tool,c: proposal,P3,team-tool,triaged-tool

## Use case

we have an internal code gen tool to save us time from writing boilerplate code for our projects. in addition to the generated code that gets used in the actual app, we also generate tests for the generated code. this is an extra step we took to ensure that the code generation does not have unforeseen bugs or issues. this has actually been helpful a few times already in order to correct the code generation itself.

however, "flutter test" won't recognize generated test files because the file name won't end in "_test.dart" but rather "_test.g.dart". this is undesired since we then have to go through each generated test file and run flutter test per file. this can become costly in CI pipelines since the alternate scenario would be to just run "flutter test" once.

## Proposal

the "flutter test" command should recognize generated test files
Repository: material-ui
Issue: [Stepper] Reuse from component library causes StepperContext props to not work properly
Labels: component: stepper

### Duplicates

- [x] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

Reusing MUI Stepper from own component library causes it to misbehave. Properties that come form the StepperContext are not working properly and/or missing.

### Expected behavior 🤔

Reusing MUI Stepper from own component library should not introduce Context related issues.

### Steps to reproduce 🕹

Steps:

1. Re-export a Stepper component from a library
2. Use it in another application
3. Use children directly from MUI (ex: `Step` component)

### Context 🔦

Not sure if this is a bug or an intended behavior. I tried to isolate it and came to the conclusion that something gets messed up with the Context Provider. We have a requirement to build a reusable react component library with the following stack: React, Typescript, MUI, Storybook. Some of the components are just going to be 1:1 with what exists in MUI, and so, to avoid importing components from multiple libraries, we decided to re-export every MUI component that we use. Our Stepper re-export looks something like this(we tried different variations, with no mapping as well, just returning plain `<MUIStepper {...props} />`):
```
export const Stepper = ({ children, ...rest }: StepperProps) => {
    return (
        <Stack sx={{ width: '100%' }} spacing={4}>
            <MUIStepper {...rest}>
                {React.Children.map(children, (child) =>
                    React.isValidElement(child)
                        ? React.cloneElement(child)
                        : child
                )}
            </MUIStepper>
        </Stack>
    );
};
```

Since it would take a while to also do it for every descendent type of Stepper (StepButton, StepConnector etc.), and to probably write tests for them, we gave up on the idea of re-exporting everything and tried to use descendants directly from MUI, but this breaks the behavior of the root component. 

We've also tested the issue with the `Accordion` component, which renders the same behavior, but works as intended when we re-export `AccordionSummary` and `AccordionDetails` and use them from our library

Is there a way to correctly approach this issue without the constraint of using components from a single library? (either our own or MUI)? Can the Context be somehow controlled here?

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
Browser used: Chrome 103.0.5060.53
  System:
    OS: macOS 12.4
  Binaries:
    Node: 16.14.2 - /usr/local/opt/node@16/bin/node
    Yarn: Not Found
    npm: 8.5.0 - /usr/local/opt/node@16/bin/npm
  Browsers:
    Chrome: 103.0.5060.53
    Edge: Not Found
    Firefox: Not Found
    Safari: 15.5
```
</details>
Repository: ant-design
Issue: select组件开启inputSearch时，mode为mutiple时，输入操作后点击输入框外blur不会触发重置value为空字符串的onsearch事件。与另外两个mode表现不一致
Labels: Inactive

### Reproduction link

[https://zssky4.csb.app/](https://zssky4.csb.app/)

### Steps to reproduce

1.点击选择框，输入文字
2.点击选择框外

### What is expected?

多选时失焦操作时也触发重置value为空字符串的onsearch事件

### What is actually happening?

mode为mutiple时失焦未触发重置输入字符串的onsearch事件

| Environment | Info |
| --- | --- |
| antd | 4.21.4 |
| React | 17.0.1 |
| System | macOS 11.6.7 |
| Browser | Chrome 102.0.5005.115 |

---
https://github.com/react-component/select/blob/HEAD/src/BaseSelect.tsx#L561
看了源码里面这个逻辑时有意为之，但不理解为什么。业务中使用起来带来困惑与不便
业务场景：拉取远端选项列表，输入后失焦不再拉取一次会导致在下一次聚焦时展现缓存的上一次查询得到的远端列表，选项可能为空。

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: scatter_reduce choosed indices
Labels: triaged,enhancement,module: scatter & gather ops

### 🚀 The feature, motivation and pitch

Can i get choosed indices for scatter_reduce function? **like torch.max() -> return: max, max_indices**

### Alternatives

_No response_

### Additional context

_No response_

cc @mikaylagawarecki
Repository: deno
Issue: Missing `ku` and `ckb` locales on `Intl`
Labels: feat,web

There are some locales missing in the `Intl` implementation. Two of them are `ku` and `ckb`. They are available on browser implementations, and on Node. I am not sure if there are more missing locales.

![image](https://user-images.githubusercontent.com/49933115/176162785-cedb769d-37d4-49c7-9b35-a70adfa633a2.png)

![image](https://user-images.githubusercontent.com/49933115/176162800-7ee7140f-9631-4287-abbf-7c567f7a783e.png)

This issue was opened after @lucacasonato's [request](https://discord.com/channels/684898665143206084/684898665151594506/991289806854311947).
Repository: PowerToys
Issue: [Settings] enable CanReorderItems property again
Labels: Product-Settings,Area-User Interface,Priority-3

- Dashboard #31020
- Color Picker
- Image Resizer
- Keyboard Manager
Repository: vscode
Issue: Profiles: Workbench startup scaffolding should take profile into account
Labels: bug,workbench-rapid-render,user-profiles

Every time I open a workspace on a different profile, in which I have a different theme, the workbench starts up with the wrong colors:

![Recording 2022-06-28 at 14 15 46 (1)](https://user-images.githubusercontent.com/22350/176176133-f88761fe-0165-4165-8196-d752ee3a3ac9.gif)

Should we save these base colors per profile?
Repository: vscode
Issue: Debug fails to show debug toolbar and toggle status bar color
Labels: bug,debug

Testing #153344

I just pressed <kbd>F5</kbd> and this happened:

![image](https://user-images.githubusercontent.com/22350/176184484-53d6242d-c923-47d8-8453-5afecd750c91.png)

No idea how to repro.
Repository: kubernetes
Issue: Set Sticky bit for `emptyDir` folders
Labels: sig/storage,kind/feature,needs-triage

### What would you like to be added?

It would be nice that the `emptyDir` volumes would use the Sticky bit attribute. So `1777` instead of `0777`.
Alternatively, we could allow the `FileMode` to be set by the user and default to the current `0777`.

### Why is this needed?

One reason is that some security scanners highlight the `emptyDir` permissions as an issue.
Another, maybe a bit more specific, is that we would like to be able to run our `Pods` with `readOnlyRootFilesystem` set to `true` and use an `emptyDir` volume to allow write access to `/tmp` the problem is that, with this setup, Ruby applications, as an example, will fail with an error like `could not find a temporary directory (ArgumentError)` and being able to set the sticky bit would solve this issue.
Repository: PowerToys
Issue: Always On Top across desktops
Labels: Idea-Enhancement,Product-Always On Top

### Description of the new feature / enhancement

For the current tool "Always On Top" add the option to keep on top even if you change desktops.

### Scenario when this would be used?

My principal scenario would be to have a window fixed mostly videoconference/streaming. With this option I can keep looking the video/streaming even when I'm switching desktops. Without it I'm sort of forced to stay in the one I'm working or moving it.

### Supporting information

_No response_
Repository: vscode
Issue: Starting to debug should be snappier
Labels: debug,polish

This is based on my VS Code selfhosting of the debug feature.

Startup to debug always feels janky and laggy because the following things happen in between noticeable millisecond intervals:

1. I press <kbd>F5</kbd>
2. The debug toolbar appears
3. The Debug viewlet is focused
4. The debug toolbar shows a dropdown since it knows there are multiple debug targets
5. The status bar turns orange

I think all 5 things should occur _immediately_ even if the result of the operation won't work due to some error.

I think something specific to our selfhost is our dependance on the `Ensure Prelaunch Dependencies` pre-launch task, which takes ~1 second on my machine. This makes up for very noticeable lag which I attribute to the tool being slow.
Repository: vscode
Issue: Stopping debug while pre-launch task runs causes popups
Labels: bug,debug

1. Start our selfhosting debug
2. Stop while the pre-launch task runs
3. Start again while the pre-launch task is still running

🐛 There's a bunch of these coming: 

![image](https://user-images.githubusercontent.com/22350/176192007-7142cd67-fdd3-4f44-b006-6cc914ad585f.png)

After cancelling all popups, I am successfully debugging.