sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: MacOS export fail with torchchat on Macos-m1-stable
Labels: needs reproduction,triaged,module: macos,module: openmp,oncall: pt2,module: aotinductor

### 🐛 Describe the bug

OMP-compiled macOS export library fails on macos-m1-stable with PyTorch out of the box (OMP library issue):

https://github.com/pytorch/torchchat/actions/runs/9006021620/job/24742618846?pr=723

  ld: warning: -undefined dynamic_lookup may not work with chained fixups
  The generated DSO model can be found at: /Users/ec2-user/runner/_work/torchchat/torchchat/pytorch/torchchat/exportedModels/stories15M.so
  + python3 torchchat.py generate stories15M --dso-path exportedModels/stories15M.so --prompt 'Hello my name is'
  OMP: Error #15: Initializing libomp.dylib, but found libomp.dylib already initialized.
  OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://openmp.llvm.org/
  ./run-readme.sh: line 30: 32241 Abort trap: 6           python3 torchchat.py generate stories15M --dso-path exportedModels/stories15M.so --prompt "Hello my name is"
  Error: Process completed with exit code 1.

### Versions

OMP-compiled macOS export library fails on macos-m1-stable:

https://github.com/pytorch/torchchat/actions/runs/9006021620/job/24742618846?pr=723

  ld: warning: -undefined dynamic_lookup may not work with chained fixups
  The generated DSO model can be found at: /Users/ec2-user/runner/_work/torchchat/torchchat/pytorch/torchchat/exportedModels/stories15M.so
  + python3 torchchat.py generate stories15M --dso-path exportedModels/stories15M.so --prompt 'Hello my name is'
  OMP: Error #15: Initializing libomp.dylib, but found libomp.dylib already initialized.
  OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://openmp.llvm.org/
  ./run-readme.sh: line 30: 32241 Abort trap: 6           python3 torchchat.py generate stories15M --dso-path exportedModels/stories15M.so --prompt "Hello my name is"
  Error: Process completed with exit code 1.

cc @malfet @albanD @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang @desertfire @chenyang78
Repository: PowerToys
Issue: Using Tab key disables PowerRename
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.80.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

PowerRename

### Steps to reproduce

Right-click a file, choose "Rename with PowerRename." Once the renamer dialog pops up, don't use the mouse, try to tab over to the "Apply" button. Every time the tab focus hits the italicized "i" in the circle (for Regex Help) the TEXT of the "Apply" button at the bottom turns black, the control becomes disabled & won't respond to a click. You have to close and reopen to use the tool. Other details: renaming a PDF on the desktop using a regex that was already populated, as I use it all the time. I can repeat this behavior over reboots.

### ✔️ Expected Behavior

Tab over to button, hit space, have my file renamed.

### ❌ Actual Behavior

The Apply button became disabled. File was not renamed. Had to close PowerRename and perform operation again, this time with the mouse.

### Other Software

_No response_
Repository: flutter
Issue: Add Set secure style api for flutter apps 
Labels: c: new feature,platform-android,platform-ios,platform-web,P3,team-framework,triaged-framework

Android has the ability to set secure activities that prevent screenshots see https://commonsware.com/blog/2012/01/16/secure-against-screenshots.html. 

Android team had https://github.com/flutter/flutter/issues/147960 filed against it for respecting the secure activity flag and applying it to flutter content. This bug is to consider a framework level feature for secure content that can be applied at the widget level either as an alternative or addition to #147960.
Repository: next.js
Issue: Web Component Complex Values not working as expected on latest canary
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/jovial-panka-9slgt3

### To Reproduce

1. Load the code sandbox
2. Note that the first web component (one simply using `'use client'`) never gets hydrated with the complex value.
3. Note that the first web component (one simply using `'use client'`) never gets hydrated with the native `onclick` event handler callback, but does get the React built-in `onClick` (synthetic) event handler callback.
4. Note that the second web component (one that uses `dynamic` loading and `ssr: false`) does get all complex values set via the web component's properties and new automatic event listener adding/removal.

### Current vs. Expected behavior

### NOTE: This is on canary for react 19 beta, so these may already be on the the team's radar, in which case feel free to close! Also feel free to reach out if any assistance with nextjs + react 19 + web components would be helpful!

Per standard hydration behavior and what I _**believe**_ were the intentions of @josepharhar's work on the design here, I'd expect complex values to be populated on the client after initial load, e.g.:
* https://docs.google.com/document/d/1wwL_YZ5TnYorEEr2Lkeh9rgbnsynDXXI7tCejVcpE6I/edit#heading=h.27i19bfdx6qi
* https://github.com/facebook/react/blob/main/packages/react-dom-bindings/src/client/DOMPropertyOperations.js#L189-L231

### Provide environment information

```bash
Operating System: (NOTE: This is not unique to a particular OS)
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 8198
  Available CPU cores: 4
Binaries: (NOTE: I'm highly confident that this is not unique to particular binaries)
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.3.0-canary.53 // Latest available version is detected (14.3.0-canary.53).
  eslint-config-next: N/A
  react: 19.0.0-canary-fd0da3eef-20240404
  react-dom: 19.0.0-canary-fd0da3eef-20240404
  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 dev (local), next build (local), next start (local), Vercel (Deployed)

### Additional context

Per callout above, I'm happy to help out with any additional questions/comments/concerns, either for this particular issue or with getting Next + React 19 + Web Components into a good spot.
Repository: pytorch
Issue: `torch.nn.LazyLinear` custom weight initialization 
Labels: module: nn,triaged,enhancement

### 🚀 The feature, motivation and pitch

currently, the torch.nn.LazyLinear module cannot be initialized until the first forward pass. This makes sense and is fine but it would be nice if we could choose a distribution to init from instead of using the uniform distribution. For example if we could pass an `init_dist` param that takes a function from `nn.init` so that when it is initialized it uses that distribution.

### Alternatives

_No response_

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: kubernetes
Issue: add EndpointSlice consumer helper functions
Labels: sig/network,priority/important-longterm,triage/accepted

As discussed in the SIG Network meeting on May 9, we should provide "EndpointSlice helpers" to help people get away from Endpoints (without using EndpointSlices in a naive way that breaks for large services).

In particular, we want something that acts sort of like an `Informer`/`Lister`, but where it deals with merging together multiple slices for the same service, so that, eg, if a service has 3 slices, and you do a `Get` on that service, you get all of the endpoints across all three slices, and if 1 of the slices gets updated, you get an `Updated` event that includes the new combined set of endpoints, not just the endpoints for that one slice.

(I'm not totally sure exactly what this API should look like. One possibility would be that `Get` would return a `[]*discoveryv1.EndpointSlice` rather than a single `*discoveryv1.EndpointSlice`. Though this would mean that when endpoints were being moved between slices, there would be temporary states where a single endpoint appeared in two different slices. Another possibility would be to have it synthesize fake `EndpointSlice` objects that just ignored the normal maximums and included all of the endpoints from across all of the slices (with the cache code dealing with de-duping). Though, actually, that doesn't work, because the different slices might have different `Ports`, so you'd still need to return an array of slices. So maybe we do want the first idea, just with a prominent warning that duplicates may exist.)

kube-proxy's [`EndpointSliceCache`](https://github.com/kubernetes/kubernetes/blob/v1.30.0/pkg/proxy/endpointslicecache.go) may provide a starting point, though it's too tied to other internal kube-proxy APIs to actually be useful as-is.

The code should go in some staged repo. I guess maybe `k8s.io/endpointslice` would be an obvious place? (It's currently only EndpointSlice controller code, but it could have EndpointSlice consumers too?) If not there, then maybe `k8s.io/component-helpers`.

/sig network
/priority important-longterm
/triage accepted
/cc @robscott
Repository: material-ui
Issue: [material][Tabs] Disable scroll animation via prop
Labels: new feature,waiting for 👍,component: tabs,package: material-ui

### Summary

An additional prop should be added to `Tabs` that disables the scroll animations. The functionality for disabling the scroll animation is already built-in, but it is not exposed as a prop. I'd recommend `disableScrollAnimation`.

### Examples

None needed.

### Motivation

When using scrollable tabs in frameworks with ssr and rehydration, scrolling occurs when the tabs are first loaded. 

While preventing scroll on initial mounting was said to be fixed in  #25469, this solution does not appear to work when using frameworks like Next.js (though it does work in vanilla react).

This is especially annoying as in Next.js layout components are remounted on navigation, causing the tabs to re-scroll on every navigation in some scenarios.

I'd like to be able to disable the scroll animations directly.

You can see this problem in action on my website in mobile view on certain pages: https://panfactum.com/docs/reference/infrastructure-modules/aws_dnssec.

Source code here: https://github.com/Panfactum/stack/blob/5fec677b42707b0dc49fd6b7d5bd76352f7985dc/packages/website/src/components/layout/web/secondary/tabs/CustomRenderedTabs.tsx#L58

**Search keywords**: tabs disable scroll
Repository: godot
Issue: Clear Inheritance on Inherited Scene from base Scene with children with signals does not unlock signals until editor restart
Labels: bug,topic:editor

### Tested versions

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

### System information

Godot v4.2.1.stable - Ubuntu 22.04.4 LTS 22.04 - X11 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 860M (nvidia; 535.161.07) - Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz (8 Threads)

### Issue description

When editing an inherited scene, you can right-click > Clear Inheritance to break the link with the inherited scene and make it its own scene. This is similar to Make Local on an instantiated scene, but the special wording only appears when the scene root itself is the instance.

![image](https://github.com/godotengine/godot/assets/1067772/8869a16b-f936-4396-aa33-9212e3ec679d)

When the base scene has children with connected signals, and you Clear Inheritance, the signals remain displayed in yellow, indication a locked, read-only state. Right-clicking on them will show that Edit... and Disconnect are indeed grayed out.

![image](https://github.com/godotengine/godot/assets/1067772/b3f86d69-84c8-4a35-9c1e-6f91588623f6)

Restarting the editor will clear the read-only state, showing that this was just a bug indeed.

### Steps to reproduce

1. In MWE, open prefab_child_to_test.tscn
2. Right-click on its root > Clear Inheritance and confirm undoable action
3. Select the child Node2D
4. Go to Node tab > Signals > draw > observe how `.. :: _on_node_2d_draw()` is still yellow
5. Since Clear Inheritance is undoable, to repeat, delete prefab_child_to_test.tscn, duplicate prefab_child.tscn into prefab_child_to_test.tscn and repeat steps from 1.
6. Bonus: restart the editor and see how signal is now in white, and editable

### Minimal reproduction project (MRP)

[v4.2.1 - Clear inheritance of instantiated scene keeps signals locked.zip](https://github.com/godotengine/godot/files/15266966/v4.2.1.-.Clear.inheritance.of.instantiated.scene.keeps.signals.locked.zip)
Repository: vscode
Issue: Flash Opening Issue Reporter
Labels: bug,issue-reporter

Type: <b>Bug</b>

1. Open VS Code
2. Go to Help>Issue Reporter

VS Code version: Code 1.89.1 (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:13:33.891Z)
OS version: Windows_NT x64 10.0.22631
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 2304)|
|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>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|15.71GB (3.82GB free)|
|Process Argv|--crash-reporter-id 158a4efb-0873-4103-8de8-d29eb4dc1d84|
|Screen Reader|no|
|VM|67%|
</details>Extensions: none
<!-- generated by issue reporter -->

https://github.com/microsoft/vscode/assets/103131515/727f4ae6-42ee-417d-90e4-6a4c3518cc4b
Repository: ollama
Issue: Feature Request: Generate embedding for images using `/api/embeddings` endpoint
Labels: feature request,api

I think this feature would make a lot of sense.
I can add an `"images"` field in requests to `/api/generate` when using a multi-modal model, why can't I do the same for requests to `/api/embeddings`?

```sh
curl http://localhost:11434/api/embeddings -d '{
  "model": "llava",
  "images": ["iVBORw0KGgoAAAANSUhEUgAAAG0A..."]
}'
```

Possible use case:
Store embeddings of images in a vector database for enhanced personal image search
Repository: go
Issue: cmd/cgo/internal/testplugin: unrecognized failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/cgo/internal/testplugin" && test == ""
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/37939a56d81b89dc0ef2453f143267754ddd8ed2)):

    mkdir -p $TMPDIR/src/testplugin
    rsync -a testdata/ $TMPDIR/src/testplugin
    echo 'module testplugin' > $TMPDIR/src/testplugin/go.mod
    mkdir -p $TMPDIR/alt/src/testplugin
    rsync -a altpath/testdata/ $TMPDIR/alt/src/testplugin
    echo 'module testplugin' > $TMPDIR/alt/src/testplugin/go.mod
    cd $TMPDIR/alt/src/testplugin
    ( GOPATH=$TMPDIR/alt PWD=$TMPDIR/alt/src/testplugin /tmp/buildlet/go/bin/go build -gcflags '' -buildmode=plugin -o $TMPDIR/src/testplugin/plugin-mismatch.so ./plugin-mismatch )
    cd $TMPDIR/src/testplugin
    ( GOPATH=$TMPDIR PWD=$TMPDIR/src/testplugin LD_LIBRARY_PATH=$TMPDIR/src/testplugin /tmp/buildlet/go/bin/go build -gcflags '' -buildmode=plugin ./plugin1 )
    ...
    panic: test timed out after 3m0s
    	running tests:
    		TestForkExec (3s)
    
    goroutine 258 gp=0xc00012bdc0 m=0 mp=0x8dd0960 [running]:
    panic({0x8cb71c0?, 0xc00068e5f0?})
    	/tmp/buildlet/go/src/runtime/panic.go:778 +0x168 fp=0xc0001b9f10 sp=0xc0001b9e60 pc=0x8b7d7a8
    testing.(*M).startAlarm.func1()
    	/tmp/buildlet/go/src/testing/testing.go:2367 +0x385 fp=0xc0001b9fe0 sp=0xc0001b9f10 pc=0x8c249c5
    runtime.goexit({})
    ...
    os/exec.(*Cmd).writerDescriptor.func1()
    	/tmp/buildlet/go/src/os/exec/exec.go:577 +0x34 fp=0xc000634760 sp=0xc000634700 pc=0x8c2c5d4
    os/exec.(*Cmd).Start.func2(0x8ce5500?)
    	/tmp/buildlet/go/src/os/exec/exec.go:724 +0x2c fp=0xc0006347c8 sp=0xc000634760 pc=0x8c2d24c
    os/exec.(*Cmd).Start.gowrap1()
    	/tmp/buildlet/go/src/os/exec/exec.go:736 +0x24 fp=0xc0006347e0 sp=0xc0006347c8 pc=0x8c2d1e4
    runtime.goexit({})
    	/tmp/buildlet/go/src/runtime/asm_amd64.s:1699 +0x1 fp=0xc0006347e8 sp=0xc0006347e0 pc=0x8bb8981
    created by os/exec.(*Cmd).Start in goroutine 202
    	/tmp/buildlet/go/src/os/exec/exec.go:723 +0x98b


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: pytorch
Issue: Pytorch nightly docker image invalidated layers
Labels: module: binaries,triaged,module: docker

### 🐛 Describe the bug

Is there something that is invalidating Docker nightly image layers?

It seems that every time I am going to pull a new nightly image it is going to download all the heavy layers.

### Versions

pytorch nightly

cc @seemethere @malfet @osalpekar @atalman
Repository: neovim
Issue: `json_encode()` assert false on c0 or c1 utf-8 chars
Labels: vimscript,bug-crash,unicode  💩

### Problem

When passing a c0 or c1 UTF-8 char (except for `\xc0\x80`) to `json_encode()` it will make an assert fail (if neovim is built with debug).

(c0 and c1 UTF-8 characters are the extended versions of the normal ascii characters and are considered invalid (though vim and neovim sometimes handle them fine))

### Steps to reproduce

```
nvim --clean
:echo json_encode("\xc0\x81")
```

### Expected behavior

Don't fail assert.

### Neovim version (nvim -v)

v0.10.0-dev-c18d794  (built with Debug)

### Vim (not Nvim) behaves the same?

no, vim 9.1

### Operating system/version

linux 6.8.9-arch1-2

### Terminal name/version

kitty 0.33.1

### $TERM environment variable

xterm-kitty

### Installation

build from repo
Repository: react
Issue: Bug: onChange is not triggered when the 'input' event listener changes the target's value.
Labels: Status: Unconfirmed

React version: 18.3.1

## Steps To Reproduce

1. Create a root component.
2. Insert an input tag that contains an `onChange` prop.
3. Call `useRef` to get the input.
4. In a `useEffect` call, add an event listener with "input" as the listener.
5. Observe how the `onChange` prop will not be triggered.

[Link to code example](https://codesandbox.io/s/eager-gates-fpnyvy?file=%2Fsrc%2FApp.js%3A13%2C7)

[Vanilla JavaScript example](https://codepen.io/timbo-dev/pen/ZENEXae?editors=1111)

### Current Behavior
After typing some characters into the input, the `input` event listener is triggered, changing the `target.value` property. However, for some reason, the `onChange` prop is not being triggered. If we comment out the line that changes the `target.value`, both listeners are triggered as expected.

## Expected Behavior
The `onChange` prop should be triggered after the `input` event listener changes the `target.value` property.
Repository: material-ui
Issue: [docs][material-ui] Improve documentation regarding slot pattern
Labels: docs,on hold,package: material-ui

After the slot pattern is standardized in Material UI (https://github.com/mui/material-ui/issues/41279, https://github.com/mui/material-ui/issues/41281), we should invest in documentation to share its mental model and mechanisms.

## To do

- [ ] Copy [Overriding component structure](https://mui.com/joy-ui/customization/overriding-component-structure/) from Joy's docs
- [ ] Fix: not all components have the slots section in their API, for example:
    - Slider doesn't: https://mui.com/material-ui/api/slider/#slider-prop-slots
    - Accordion does: https://mui.com/material-ui/api/accordion/#slots
- [ ] Figure out slot visualization. Inspiration:
    - https://next.mui.com/x/react-date-pickers/date-picker/#customization
    - https://mantine.dev/core/autocomplete/#styles-api

**Search keywords**: docs slot pattern
Repository: go
Issue: build: build failure on x_tools-go1.21-linux-amd64_c2s16-perf_vs_gopls_0_11
Labels: NeedsInvestigation

```
#!watchflakes
default <- builder == "x_tools-go1.21-linux-amd64_c2s16-perf_vs_gopls_0_11" && repo == "tools" && mode == "build"
```

Issue created automatically to collect these failures.

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

    go: downloading github.com/BurntSushi/toml v1.0.0
    go: downloading github.com/kballard/go-shellquote v0.0.0-20180428030007-95032a82bc51
    2024/05/09 00:15:04 Load average: 1.18 1.74 2.29 1/393 1531306
    2024/05/09 00:15:04 Waiting for load average to drop below 0.20...
    2024/05/09 00:15:34 Load average: 0.86 1.60 2.23 1/393 1531306
    2024/05/09 00:15:34 Waiting for load average to drop below 0.20...
    2024/05/09 00:16:04 Load average: 0.52 1.45 2.16 1/392 1531306
    2024/05/09 00:16:04 Waiting for load average to drop below 0.20...
    2024/05/09 00:16:34 Load average: 0.31 1.31 2.09 1/392 1531306
    2024/05/09 00:16:34 Waiting for load average to drop below 0.20...
    ...
    go: downloading golang.org/x/sync v0.7.0
    go: downloading golang.org/x/vuln v1.0.4
    go: downloading honnef.co/go/tools v0.4.7
    go: downloading mvdan.cc/gofumpt v0.6.0
    go: downloading mvdan.cc/xurls/v2 v2.5.0
    go: downloading golang.org/x/text v0.15.0
    go: downloading golang.org/x/exp/typeparams v0.0.0-20221212164502-fae10dda9338
    2024/05/09 02:17:03 Error running subrepo tests: error running sub-repo tools benchmark "experiment" with toolchain baseline in dir /home/swarming/.swarming/w/ir/x/w/tools/gopls/internal/test/integration/bench: exit status 1
    2024/05/09 02:17:03 FAIL
    exit status 1


— [watchflakes](https://go.dev/wiki/Watchflakes)