sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tensorflow
Issue: tf.raw_ops.Round outputs zeros for any integer tensor
Labels: stat:awaiting tensorflower,type:bug,comp:ops,regression issue,2.17

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

2.17.0

### Custom code

Yes

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Expects the same tensor as the input according to the specification https://www.tensorflow.org/api_docs/python/tf/raw_ops/Round

### Standalone code to reproduce the issue

```shell
import tensorflow as tf
x = tf.constant([-2, -1, 1, 2, 3])
tf.raw_ops.Round(x=x)
```


### Relevant log output

```shell
>>> import tensorflow as tf
>>> x = tf.constant([-2, -1, 1, 2, 3], dtype=tf.int32)
>>> tf.raw_ops.Round(x=x)
<tf.Tensor: shape=(5,), dtype=int32, numpy=array([0, 0, 0, 0, 0])>
```
Repository: flutter
Issue: Change the default look of CupertinoListSection to the new default
Labels: platform-ios,framework,c: API break,a: fidelity,f: cupertino,has reproducible steps,P3,team-design,triaged-design,found in release: 3.24,found in release: 3.25

From the API docs, `CupertinoListSection` is modeled after the iOS settings screen. However, there seem to be a bunch of fidelity issues when comparing the settings screen and the first example in the API docs (`flutter create --sample=cupertino.CupertinoListSection.1 mysample`):

1. Padding is missing around the list section itself
2. Rounded corners are missing on the list section itself
3. Rounded corners are missing on the leading color box
Repository: vscode
Issue: ERR Illegal value for lineNumber: Error: Illegal value for lineNumber
Labels: bug,editor-sticky-scroll

Sorry, not repro steps but a non-minified stacktrace ⏬ 

```
  ERR Illegal value for lineNumber: Error: Illegal value for lineNumber
    at TextModel.getLineMaxColumn (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/editor/common/model/textModel.js:638:23)
    at CodeEditorWidget.getBottomForLineNumber (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/editor/browser/widget/codeEditor/codeEditorWidget.js:412:50)
    at StickyScrollController.findScrollWidgetState (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/editor/contrib/stickyScroll/browser/stickyScrollController.js:513:62)
    at StickyScrollController._updateState (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/editor/contrib/stickyScroll/browser/stickyScrollController.js:481:38)
    at async StickyScrollController._renderStickyScroll (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/editor/contrib/stickyScroll/browser/stickyScrollController.js:440:21)
```
Repository: PowerToys
Issue: PowerToys Awake - define actions for laptop lid state changes
Labels: Idea-Enhancement,Product-Awake

### Microsoft PowerToys version

0.83.0

### Installation method

Chocolatey

### Running as admin

No

### Area(s) with issue?

Awake

### Steps to reproduce

Turn on "Keep Awake Infedinitely"
Close laptop lid.
Put laptop in a bag.

### ✔️ Expected Behavior

System suspends.

### ❌ Actual Behavior

System stays awake and can't cool down, gets extremely hot and runs fans at max, draining the battery in under an hour and potentially posing a burn hazard, or corrupting firmware. 

The Awake function's main use is for the computer open at a workstation to not suspend when the user gets up from their desk for a few minutes at a time, not usually to keep a computer active when its lid is closed. While that behavior might be desired in rare circumstances, there should be a dedicated setting to indicate that it was intentional. Users who leave this function on all the time will forget to turn it off when putting their laptop in a bag. 

### Other Software

_No response_
Repository: PowerToys
Issue: Preview tool default allaws on top
Labels: Needs-Triage

### Description of the new feature / enhancement

Add an option to make the preview tool automaticaly allaws on top.

### Scenario when this would be used?

- when we want to manually select an other file to preview without loose the preview window
- When we have to compare a file with an other image on a different window

### Supporting information

you can check what Quicklook app do
Repository: ui
Issue: [bug]: Incorrect Usage of <DrawerClose> in Documentation Causes HTML Button Nesting Error
Labels: bug

### Describe the bug

I noticed an issue in the documentation for the <Drawer> component that could cause HTML hydration errors. The current example has a <button> element nested inside another <button> element, which is invalid in HTML and leads to the following warning:

Warning: In HTML `<button>` cannot be a descendant of `<button>`. This will cause a hydration error.

The current documentation demonstrates the usage of the Drawer component as follows:
```jsx
<Drawer>
  <DrawerTrigger>Open</DrawerTrigger>
  <DrawerContent>
    <DrawerHeader>
      <DrawerTitle>Are you absolutely sure?</DrawerTitle>
      <DrawerDescription>This action cannot be undone.</DrawerDescription>
    </DrawerHeader>
    <DrawerFooter>
      <Button>Submit</Button>
      <DrawerClose> // <---
        <Button variant="outline">Cancel</Button>
      </DrawerClose>
    </DrawerFooter>
  </DrawerContent>
</Drawer>
```

The recommended fix is to update the documentation to include the asChild property on <DrawerClose>, as shown below:

```jsx
<Drawer>
  <DrawerTrigger>Open</DrawerTrigger>
  <DrawerContent>
    <DrawerHeader>
      <DrawerTitle>Are you absolutely sure?</DrawerTitle>
      <DrawerDescription>This action cannot be undone.</DrawerDescription>
    </DrawerHeader>
    <DrawerFooter>
      <Button>Submit</Button>
      <DrawerClose asChild> // <---
        <Button variant="outline">Cancel</Button>
      </DrawerClose>
    </DrawerFooter>
  </DrawerContent>
</Drawer>
```

### Affected component/components

DrawerClose

### How to reproduce

- Implement the code as per the current documentation.

- Observe the hydration error in the browser console.

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Operating System: Windows 11
Browser: Microsoft Edge
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: PowerToys
Issue: Regression on Enviroment Variable Profile Path handling
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.83.0

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

Environment Variables

### Steps to reproduce

- Create a Profile, in this profile set a variable named Path with value "%Path_PowerToys_ProfileName%"
- Activate the profile, it will automatically create Path_PowerToys_ProfileName holding your normal Path variable

### ✔️ Expected Behavior

Old behavior: Path_PowerToys_ProfileName would be resolved on the overloaded Path variable so printing $env:Path would show the original Path content

### ❌ Actual Behavior

New behavior: Path_PowerToys_ProfileName is not resolved on the overloaded Path variable so printing $env:Path shows only "%Path_PowerToys_ProfileName%"

This is a problem as this was the only way for adding more content to path depending on profile as the resolving of this references happens on enviroment load and adding a variable %porfile_Path% and a reference on the normal Path to %profile_Path% (which would be more intuitive) does not work. so now there is no way to add content to path depending on profile which was one of the only reasons I used this tool...

### Other Software

_No response_
Repository: PowerToys
Issue: File Explorer: Preview Pane - Source code file preview shrinks on a monitor with a smaller scale factor
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.83.0

### Installation method

GitHub

### Running as admin

None

### Area(s) with issue?

File Explorer: Preview Pane

### Steps to reproduce

1. Connect at least 2 monitors.
2. Set the scaling of the main monitor to 225% (or just something bigger than 100).
3. Set the external monitor scaling to 100%
4. Open a preview of a "source code" file
5. Move the explorer window with an open file preview between the monitors 

### ✔️ Expected Behavior

The same size (visually) of the file preview.

### ❌ Actual Behavior

File preview shrinks on the screen with a lower scaling (probably proportionally to the scaling factor difference).

## Details
In my case it's:
<img src="https://github.com/user-attachments/assets/fc158579-b760-4e8a-98c3-717fae69c5fe" width="500">
1: 3840 x 2400 (scale 225%) - native Dell XPS 17 9720 screen
2: 2560 x 1440 (scale 100%) - Dell U2722D
3: 2560 x 1440 (scale 100%) - Dell U2722D

### Screen 1 (native one) preview:
<img src="https://github.com/user-attachments/assets/5e99506d-3dcf-489f-a510-ab1d91896887" width="500">

### Screen 2 and 3 (Dell) preview:
<img src="https://github.com/user-attachments/assets/47cd0f0e-3bc0-4380-9351-afe6ec8f2fb6" width="500">

### Other Software

_No response_
Repository: tauri
Issue: [bug] tauri cli rebuild dependencies every time I save file
Labels: type: bug,status: needs triage

### Describe the bug

Every time I save file cargo check invoked from rust analyzer. then tauri trigger reload and recompile.
However it recompile a lot of crates each time I save which takes a lot of time. maybe it has conflict with rust analyzer.
It's affect the development and it's hard to develop when each time I save file it recompile for a minute.

### Reproduction

`bunx tauri dev` in v2 project in vscode in macos with rust analyzer.

### Expected behavior

If I didn't changed anything, it shouldn't rebuild anything.

### Full `tauri info` output

```text
bunx tauri info   

[✔] Environment
    - OS: Mac OS 14.5.0 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.79.0 (129f3b996 2024-06-10)
    ✔ cargo: 1.79.0 (ffa9cf99a 2024-06-03)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 20.15.1
    - npm: 10.7.0
    - bun: 1.1.18

[-] Packages
    - tauri [RUST]: 2.0.0-rc.8
    - tauri-build [RUST]: 2.0.0-rc.7
    - wry [RUST]: 0.42.0
    - tao [RUST]: 0.29.1
    - @tauri-apps/api [NPM]: 2.0.0-rc.3
    - @tauri-apps/cli [NPM]: 2.0.0-beta.23

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite
```


### Stack trace

```text
Comment too long to paste here
https://gist.github.com/thewh1teagle/cc78a89afe1d6496e41899bb6aab79b9
```


### Additional context

_No response_
Repository: pytorch
Issue: Setting a negative, `int` and `bool` value to `label_smoothing` argument of `nn.CrossEntropyLoss()` works against the error messages
Labels: module: loss,triaged

### 🐛 Describe the bug

Setting the positive value `3.` to `label_smoothing` argument of [nn.CrossEntropyLoss()](https://pytorch.org/docs/stable/generated/torch.nn.CrossEntropyLoss.html) gets the error message as shown below:

```python
import torch

tensor1 = torch.tensor([[0.4, 0.8, 0.6], [0.3, 0.0, 0.5]])
tensor2 = torch.tensor([[0.2, 0.9, 0.4], [0.1, 0.8, 0.5]])

cel = nn.CrossEntropyLoss(label_smoothing=3.)
cel(input=tensor1, target=tensor2) # Error
```

> RuntimeError: label_smoothing must be between 0.0 and 1.0. Got: 3

But setting the negative value `-3.` to `label_smoothing` argument works against the error message above as shown below. *`-3.` doesn't affect to the result:

```python
import torch

tensor1 = torch.tensor([[0.4, 0.8, 0.6], [0.3, 0.0, 0.5]])
tensor2 = torch.tensor([[0.2, 0.9, 0.4], [0.1, 0.8, 0.5]])

cel = nn.CrossEntropyLoss(label_smoothing=-3.)
cel(input=tensor1, target=tensor2)
# tensor(1.5941)
```

And, setting `1.+0.j`(`complex`) to `label_smoothing` argument gets the error message as shown below.

```python
import torch

tensor1 = torch.tensor([[0.4, 0.8, 0.6], [0.3, 0.0, 0.5]])
tensor2 = torch.tensor([[0.2, 0.9, 0.4], [0.1, 0.8, 0.5]])

cel = nn.CrossEntropyLoss(label_smoothing=1.+0.j)
cel(input=tensor1, target=tensor2) # Error
```

> TypeError: cross_entropy_loss(): argument 'label_smoothing' (position 6) must be float, not complex

But setting `1`(`int`) and `True`(`bool`) to `label_smoothing` argument works against the error message above as shown below:

```python
import torch

tensor1 = torch.tensor([[0.4, 0.8, 0.6], [0.3, 0.0, 0.5]])
tensor2 = torch.tensor([[0.2, 0.9, 0.4], [0.1, 0.8, 0.5]])

cel = nn.CrossEntropyLoss(label_smoothing=1)
cel(input=tensor1, target=tensor2)
# tensor(1.1156)

cel = nn.CrossEntropyLoss(label_smoothing=True)
cel(input=tensor1, target=tensor2)
# tensor(1.1156)
```


### Versions

```python
import torch

torch.__version__ # 2.4.0+cu121
```
Repository: flutter
Issue: Support WasmGC on Safari
Labels: engine,platform-web,P2,e: wasm,e: web_skwasm,team-web,triaged-web

### Steps to reproduce

WasmGC is now officially supported on Safari Technology Preview 202: https://developer.apple.com/documentation/safari-technology-preview-release-notes/stp-release-202#Web-Assembly

1. Use Safari Technology Preview 202
2. Go to https://flutterweb-wasm.web.app
3. Open the dev tools and see "main.dart.js" being loaded

### Expected results

main.dart.wasm being loaded

### Actual results

main.dart.js was loaded

### Code sample

N/A

### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>
<img width="862" alt="Screenshot 2024-08-29 at 10 42 12 AM" src="https://github.com/user-attachments/assets/a9d16fae-bb95-4942-beac-2c59815bf58e">

</details>


### Logs

N/A

### Flutter Doctor output

N/A
Repository: pytorch
Issue: Setting the tensor of the values out of `[0,1]` to `target` argument of `nn.CrossEntropyLoss()` with class probabilities works against the doc
Labels: module: docs,module: loss,triaged

### 🐛 Describe the bug

[The doc](https://pytorch.org/docs/stable/generated/torch.nn.CrossEntropyLoss.html) of `nn.CrossEntropyLoss()` says that `target` argument with class probabilities should be between `[0, 1]` as shown below:

> `Target`: ... If containing class probabilities, same shape as the input and each value should be between `[0,1]`.

But setting the tensor of the values out of `[0,1]` to `target` argument with class probabilities works against the doc above as shown below:

```python
import torch

input = torch.tensor([[0.4, 0.8, 0.6], [0.3, 0.0, 0.5]])
target = torch.tensor([[6.2, -7.9, 3.4], [2.1, 8.6, -12.5]]) # Here

cel = nn.CrossEntropyLoss()

cel(input=input, target=target) # tensor(3.9178)
```

### Versions

```python
import torch

torch.__version__ # 2.4.0+cu121
```

cc @svekars @brycebortree @tstatler
Repository: vscode
Issue: Add jsdoc to all classes extending ViewPart giving a basic explanation of what they are
Labels: debt

While reviewing view parts, I found it hard differentiating some of them like all the different decoration types. It would be nice to have a description that explains them and maybe points to a common example in the case of decorations

- [ ] blockDecorations @hediet 
- [x] editorScrollbar
- [x] lines
- [ ] marginDecorations @hediet
- [x] rulers
- [x] viewZones
- [x] contentWidgets
- [ ] glyphMargin @hediet 
- [ ] linesDecorations @hediet 
- [x] minimap
- [ ] scrollDecoration @ulugbekna @alexdima 
- [x] whitespace
- [x] currentLineHighlight
- [x] indentGuides
- [x] linesGpu
- [x] overlayWidgets
- [x] selections
- [ ] decorations @hediet 
- [x] lineNumbers
- [x] margin
- [x] overviewRuler
- [x] viewCursors
Repository: kubernetes
Issue: add to kubectl explain config APIs
Labels: kind/feature,sig/cli,lifecycle/rotten,needs-triage

### What would you like to be added?

At the moment `kubectl explain` only allows to explain all resource that are returned by `kubectl api-resources`.
I'd like seeing to add the configuration APIs as well to explain.

### Why is this needed?

When creating kubelet configuration files or other external resources like kubeadm config files or pod-security files and it would be easier to spin up `kubectl explain` rather than going to kubernetes docs and read the provided documentation there: https://kubernetes.io/docs/reference/config-api/
Repository: vscode
Issue: Editor GPU: Review all editor.* settings and ensure they are tracked
Labels: plan-item,editor-gpu
Repository: vscode
Issue: Editor GPU: Reduce memory use in the atlas glyph storage buffers
Labels: plan-item,perf,editor-gpu

The buffer that stores all the texture atlas information is fixed to `FloatsPerEntry*5000`. This should be more dynamically sized to reduce memory usage.

https://github.com/microsoft/vscode/blob/bd21f3c8f268b741edac137fc109d75a555c0541/src/vs/editor/browser/viewParts/linesGpu/viewLinesGpu.ts#L291-L292
Repository: vscode
Issue: Editor GPU: Support sub-pixel AA
Labels: plan-item,editor-gpu

We draw to a clear canvas right now:

https://github.com/microsoft/vscode/blob/bd21f3c8f268b741edac137fc109d75a555c0541/src/vs/editor/browser/gpu/raster/glyphRasterizer.ts#L75

xterm.js works by drawing to a solid background which then gives us 0xff alpha valids with SPAA working. The complication then is that our shader needs to intelligently merge these values, otherwise rendering will look strange when glyphs overlap.
Repository: vscode
Issue: Editor GPU: Make first glyph in first page 0x0 without wasting space in the texture
Labels: bug,editor-gpu

There's a hack currently to ensure that zeroed out cells in the cell buffer do not get rendered using an actual glyph. This currently wastes the entire first slab since it's reserved for 0x0 glyphs. We should add a special glyph without touching the texture that just points at a 0 width, 0 height rectangle.

https://github.com/microsoft/vscode/blob/bd21f3c8f268b741edac137fc109d75a555c0541/src/vs/editor/browser/gpu/atlas/textureAtlas.ts#L69-L72
Repository: go
Issue: runtime: mapassign_fast64ptr crashes in malloc
Labels: NeedsInvestigation,gopls,Tools,compiler/runtime,gopls/telemetry-wins

This stack `cysh5A` was [reported by telemetry](https://storage.googleapis.com/prod-telemetry-merged/2024-08-28.json):



```
crash/crash
runtime.systemstack_switch:+4
runtime.persistentalloc:+2
runtime.newBucket:+11
runtime.stkbucket:+53
runtime.mProf_Malloc:+13
runtime.profilealloc:+6
runtime.mallocgc:+270
runtime.newarray:+8
runtime.makeBucketArray:+18
runtime.hashGrow:+10
runtime.mapassign_fast64ptr:+64
go/types.(*Checker).recordSelection:+4
go/types.(*Checker).selector:+232
go/types.(*Checker).exprInternal:+308
go/types.(*Checker).rawExpr:+10
go/types.(*Checker).exprOrType:+1
```
```
golang.org/x/tools/gopls@v0.16.1 go1.23.0 windows/amd64 neovim (1)
```

Issue created by golang.org/x/tools/gopls/internal/telemetry/cmd/stacks.
Repository: vscode
Issue: Editor GPU: Add device pixel support to ElementSizeObserver
Labels: debt,editor-gpu

We have a `ElementSizeObserver` helper already, we should merge the capabilities of `observeDevicePixelDimensions` (from xterm.js) into it.

https://github.com/microsoft/vscode/blob/bd21f3c8f268b741edac137fc109d75a555c0541/src/vs/editor/browser/gpu/gpuUtils.ts#L24-L25
Repository: vscode
Issue: Editor GPU: Consider changing the strategy for allocating glyphs into slabs
Labels: plan-item,perf,editor-gpu

Slabs right now are reserved for glyphs of the exact width and height of the slab. This could be wasteful and will likely just be more so as the device pixel ratio increases. We should consider using a different strategy as called out here:

https://github.com/microsoft/vscode/blob/bd21f3c8f268b741edac137fc109d75a555c0541/src/vs/editor/browser/gpu/atlas/textureAtlasSlabAllocator.ts#L98-L120
Repository: vscode
Issue: Editor GPU: Review scaling of open region allocator code
Labels: plan-item,perf,editor-gpu

Does this perform ok when there are many slabs?

https://github.com/microsoft/vscode/blob/bd21f3c8f268b741edac137fc109d75a555c0541/src/vs/editor/browser/gpu/atlas/textureAtlasSlabAllocator.ts#L136-L201
Repository: vscode
Issue: Editor GPU: Reconsider using measureText for the bounding box calculate
Labels: plan-item,perf,editor-gpu

Earlier I did some profiling and found that measureText was slower than expected. We should verify this but still probably go that route over the manual bounding box calculation as we can then ensure the glyph will be drawn within the bounds of the glyph rasterizer canvas (which is currently sized to 3xfontSize).

https://github.com/microsoft/vscode/blob/bd21f3c8f268b741edac137fc109d75a555c0541/src/vs/editor/browser/gpu/raster/glyphRasterizer.ts#L96-L147
Repository: vscode
Issue: Editor GPU: Support custom glyphs
Labels: feature-request,editor-gpu

The terminal has a feature that allows box drawing and block characters to be rendered pixel perfect instead of being pulled from the font. The biggest win here is that boxes in the editor will connect perfectly, even if line height or letter spacing changes.

Current DOM-based using font 12px Hack:



![Image](https://github.com/user-attachments/assets/d5bdd598-9e2f-4c2e-a33e-140f729f5546)



Compare with terminal's rendering:



![Image](https://github.com/user-attachments/assets/9a4cf7b2-21cb-4504-8835-dee411a08399)
Repository: vscode
Issue: Editor GPU: Support ligatures (editor.fontLigatures)
Labels: feature-request,editor-gpu

Ligatures aren't supported out of the box when using canvas. [The approach xterm.js uses](https://github.com/xtermjs/xterm.js/tree/master/addons/addon-ligatures) (which is not yet in vscode due to some bundling problems) is to read the font file to get the ligatures (requires a accepting permissions on web) and render those together using the concept of a "character joiner".
Repository: vscode
Issue: Editor GPU: Support editor.fontVariations
Labels: plan-item,editor-gpu

Is this just a matter of passing it to the rasterizer canvas context?
Repository: vscode
Issue: Editor GPU: Support editor.fontWeight
Labels: plan-item,editor-gpu

Test case: Make sure Cascadia code with font weight 350 works. See https://github.com/microsoft/vscode/issues/221145#issuecomment-2587698553
Repository: vscode
Issue: Editor GPU: Support editor.roundedSelection
Labels: plan-item,editor-gpu