sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: electron
Issue: [Bug]: capturePage image quality degraded when capturing transformed webContents
Labels: platform/linux,bug :beetle:,has-repro-gist,29-x-y,30-x-y,33-x-y,34-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

29.0.0-alpha.1 and up

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

Ubuntu

### Operating System Version

23.04

### What arch are you using?

x64

### Last Known Working Electron version

28.x

### Expected Behavior

When calling capturePage on a transformed webContents, the image remains sharp.

### Actual Behavior

Up to Electron 29, Screenshots made with `capturePage()` of a `webContents` that has an applied transform (such as a `<webview>` with a `transform: scale()` in its CSS) were captured at the original size, creating sharp screenshots. 

From Electron 29 onwards, it seems to capture not of the original view but of the transformed view. The size properties of the created nativeImage still reflect the `webContents` original size and this results in much blurrier images.

### Testcase Gist URL

https://gist.github.com/Kilian/3fdb897d2e3c290ed53b3c2402a8aeec

### Additional Information

1. Open the fiddle with Electron 28.x (any version) and click on the "capture screenshot" button. 
2. See that the resulting image in the canvas below the button is relatively sharp
3. Start the fiddle with any Electron 29 (starting with alpha.1)
4. See that the resulting image in the canvas is much less sharp

### Screenshots

| Electron 28 | Electron 29 |
|------------------|-----------------|
| ![Image](https://github.com/user-attachments/assets/53093145-ad8a-456a-bf6c-0f189892c84d) | ![Image](https://github.com/user-attachments/assets/c962c617-a8af-408d-ba33-49689806bc58) |
Repository: tensorflow
Issue: tf.math.special.bessel_* has inconsistent result with scipy
Labels: stat:awaiting tensorflower,type:bug,comp:ops,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?

Based on the documentation, special function such as bessel_y0 should have consistent result with scipy. However, when receiving `-inf`, it has inconsistent results with scipy. Please check the reproducible for details.

### Standalone code to reproduce the issue

```shell
import scipy
import numpy as np
import tensorflow as tf
x = tf.constant(-np.inf, dtype='float64')
print("TF:", tf.math.special.bessel_y1(x))
print("Scipy: ", scipy.special.y1(x))
print("TF:", tf.math.special.bessel_y0(x))
print("Scipy: ", scipy.special.y0(x))
print("TF:", tf.math.special.bessel_k0(x))
print("Scipy: ", scipy.special.k0(x))
print("TF:", tf.math.special.bessel_k1(x))
print("Scipy: ", scipy.special.k1(x))
```


### Relevant log output

```shell
TF: tf.Tensor(-inf, shape=(), dtype=float64)
Scipy:  nan
TF: tf.Tensor(-inf, shape=(), dtype=float64)
Scipy:  nan
TF: tf.Tensor(inf, shape=(), dtype=float64)
Scipy:  nan
TF: tf.Tensor(inf, shape=(), dtype=float64)
Scipy:  nan
```
Repository: pytorch
Issue: Any plan to support flash attention 3 for hopper GPUs?
Labels: triaged,module: sdpa

### 🚀 The feature, motivation and pitch

Flash Attention 3 (https://github.com/Dao-AILab/flash-attention) has been in beta for some time. I tested it on H100 GPUs with CUDA 12.3 and also attempted a simple merge with PyTorch. I understand that it will take some time before the stable release is ready, but I believe some structural refactoring can be started first. e.g., The FA3 highly relies on the hopper architecture. Therefore, for other architectures, the `enable_flash` option of the SDP kernel still needs to go to FA2 backend.

I wonder if anyone has already planned or been working on this. As I can see, @drisspg is still working on adding 2.6.2. I am willing to contribute but don't want to repeat any effort.

### Alternatives

_No response_

### Additional context

_No response_

cc @jbschlosser @bhosmer @cpuhrsch @erichan1 @drisspg @mikaylagawarecki
Repository: deno
Issue: truncate inlay hint by setting
Labels: upstream,suggestion,lsp

I would like to request a feature to truncate inlay hints via a setting, similar to how VTSLS handles it. This would allow for cleaner, more concise hints in the editor, improving readability.

Could you add a setting to control inlay hint truncation?

https://github.com/yioneko/vtsls/commit/95b51bde14b098ffb4760630821027c6a2fe84da
Repository: storybook
Issue: [Bug]: Storybook ArgsTypes not extracting component imported types props
Labels: bug,vue,argtypes,docgen

### Describe the bug

I have a simple vue button component, and the props type is imported from another type

example component:
![Image](https://github.com/user-attachments/assets/60e48020-f8c6-4c96-ad5a-bacbace607ae)


But why does the storybook props table not extract the ButtonVariant & ButtonSize types?
![Image](https://github.com/user-attachments/assets/9e08bc1e-87a6-41d7-b1fc-1ec5416bdf80)


any help, or did I set it up wrong?

Thank you

### Reproduction link

https://github.com/ardiansah47/storybook-issue

### Reproduction steps

1. Clone the repository
2. npm install
3. npm run storybook

### System

Storybook Environment Info:

  System:
    OS: macOS 15.0.1
    CPU: (8) arm64 Apple M1
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.17.0 - ~/.nvm/versions/node/v20.17.0/bin/node
    npm: 10.8.2 - ~/.nvm/versions/node/v20.17.0/bin/npm <----- active
    pnpm: 9.1.4 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 129.0.6668.91
    Edge: 117.0.2045.55
    Safari: 18.0.1
  npmPackages:
    @storybook/addon-essentials: ^8.3.5 => 8.3.5 
    @storybook/addon-interactions: ^8.3.5 => 8.3.5 
    @storybook/addon-links: ^8.3.5 => 8.3.5 
    @storybook/addon-onboarding: ^8.3.5 => 8.3.5 
    @storybook/blocks: ^8.3.5 => 8.3.5 
    @storybook/test: ^8.3.5 => 8.3.5 
    @storybook/vue3: ^8.3.5 => 8.3.5 
    @storybook/vue3-vite: ^8.3.5 => 8.3.5 
    storybook: ^8.3.5 => 8.3.5 

### Additional context

_No response_
Repository: go
Issue: internal/coverage/cfile: TestCoverageApis/emitToDir failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "internal/coverage/cfile" && test == "TestCoverageApis/emitToDir"
```

Issue created automatically to collect these failures.

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

    === RUN   TestCoverageApis/emitToDir
    === PAUSE TestCoverageApis/emitToDir
    === CONT  TestCoverageApis/emitToDir
        emitdata_test.go:166: running: /home/swarming/.swarming/w/ir/x/t/TestCoverageApis1302527043/001/build1/harness.exe -tp emitToDir -o /home/swarming/.swarming/w/ir/x/t/TestCoverageApis1302527043/001/emitToDir-edir-y with rdir=/home/swarming/.swarming/w/ir/x/t/TestCoverageApis1302527043/001/emitToDir-rdir-y and GOCOVERDIR=false
        emitdata_test.go:166: running: /home/swarming/.swarming/w/ir/x/t/TestCoverageApis1302527043/001/build1/harness.exe -tp emitToDir -o /home/swarming/.swarming/w/ir/x/t/TestCoverageApis1302527043/001/emitToDir-edir-x with rdir=/home/swarming/.swarming/w/ir/x/t/TestCoverageApis1302527043/001/emitToDir-rdir-x and GOCOVERDIR=true
        emitdata_test.go:232: 
            internal error in coverage meta-data tracking:
            encountered bad pkgID: 0  at slot: 3432  fnID: 6  numCtrs: 1
            list of hard-coded runtime package IDs needs revising.
            [see the comment on the 'rtPkgs' var in 
    ...
            panic: runtime error: slice bounds out of range [:4294975528] with capacity 27058
            
            goroutine 1 gp=0xc000002380 m=0 mp=0x6f9da0 [running]:
            panic({0x5a08e0?, 0xc00001a198?})
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/panic.go:806 +0x2c5 fp=0xc000076968 sp=0xc0000768b8 pc=0x4edea5
            runtime.goPanicSliceAcap(0x100002028, 0x69b2)
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/panic.go:141 +0xb4 fp=0xc0000769a8 sp=0xc000076968 pc=0x46e214
            internal/coverage/cfile.(*emitState).VisitFuncs(0xc0000de000, 0xc00000e078)
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/internal/coverage/cfile/emit.go:478 +0x1154 fp=0xc000076c00 sp=0xc0000769a8 pc=0x5759b4
            internal/coverage/encodecounter.(*CoverageDataWriter).writeCounters(0xc0000120f0, {0x5dc960, 0xc0000de000}, 0xc00009a040)
    ...
            runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?)
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/proc.go:435 +0x24a fp=0xc000063e20 sp=0xc000063e00 pc=0x4ee5aa
            runtime.runfinq()
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/mfinal.go:193 +0x3ce fp=0xc000063fe0 sp=0xc000063e20 pc=0x42bf6e
            runtime.goexit({})
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/asm_amd64.s:1700 +0x1 fp=0xc000063fe8 sp=0xc000063fe0 pc=0x4f7fe1
            created by runtime.createfing in goroutine 1
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/mfinal.go:163 +0x86
        emitdata_test.go:233: running 'harness -tp emitDir': exit status 2
    --- FAIL: TestCoverageApis/emitToDir (0.04s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: flutter
Issue: [Impeller] remove filter graph and replace with saveLayer/restore operations
Labels: P3,e: impeller,team-engine,triaged-engine

Impeller's filter graph is analgous to the saveLayer/restore system that is present in the canvas dispatcher. I believe that we could replace the filter graph with this system for a smaller/simpler renderer. Essentially:

Today we have a system that conditionally wraps entites with FilterEntities based on paint state:

```
Paint paint;
Entity render_entity;

if (paint.image_filter) {
  render_entity = paint.image_filter.wrap(render_entity);
}

render(render_entity);

```

I am proposing replacing that with:

```
Paint paint;
Entity render_entity;
if (paint.image_filter) {
  SaveLayer(...);
}
render(render_entity);
if (paint.image_filter) {
  Restore();
}


```


Along with https://github.com/flutter/engine/pull/55843, this would allow us to remove more impeller code to delegate to display list. Essentially the filter entites would only need to handle other texture inputs, as the saveLayer with single contents is exactly analgous to entity.getSnapshot();

The only exception here is filter entities applied to textures, which should avoid writing the texture contents to a new save layer. I believe that can be special cased.

Questions:

## Depth/Clipping?

Should work fine, all filter entities are unclipped, just the final resul.t

## Order of operations?

I believe saveLayers apply color/image filters in different order. We just need to make that configurable.
Repository: ui
Issue: [bug]: Playground Model Combobox HoverCard bugs
Labels: bug

### Describe the bug

https://ui.shadcn.com/examples/playground

Two bugs I found for this playground example.

1. The HoverCard of the Model will not update after "No Models found." shows
![recording](https://github.com/user-attachments/assets/7a88bedf-27bd-415d-822d-41d93076eda6)

2. When clicking on the HoverContent, the HoverContent will flash!
![recording](https://github.com/user-attachments/assets/c53d9aaa-84fb-461e-a5a5-394c5dee7963)



### Affected component/components

Popover, Combobox, HoverCard

### How to reproduce

1. Go to: https://ui.shadcn.com/examples/playground
2. Click on Model
3. Type something until "No Models found." shows and then hover on the CommandItem again, you'll find that the HoverCard will not update anymore
4. Also another bug is the flashing issue, when clicking on the HoverContent, the HoverContent will flash!


### Codesandbox/StackBlitz link

https://github.com/shadcn-ui/ui/blob/main/apps/www/app/(app)/examples/playground/components/model-selector.tsx

### Logs

_No response_

### System Info

```bash
Chrome Version 129.0.6668.101 (Official Build) (64-bit)
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: next.js
Issue: [turbopack]: Can't specify issuer with @svgr/webpack loader, causes invalid url transformation in css
Labels: bug,Webpack,Turbopack,linear: turbopack

### Link to the code that reproduces this issue

https://github.com/MaciejWiatr/svgr-nextjs-css-url-repro

### To Reproduce

1.  Create new nextjs app with turbopack enabled for dev server (`next dev --turbo`)
2. Add `@svgr/webpack` as an dependency and loader to nextjs config like the following
```js
/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: true,
  experimental: {
    turbo: {
      rules: {
        "*.svg": {
          loaders: ["@svgr/webpack"],
          as: "*.js",
        },
      },
    },
  },
};
```
3. Install external library that utilizes css svg url imports, i.e flag-icons `npm install flag-icons` ( i will use it as an example for next steps)
4. Add html element: `<span className="fi fi-gr"></span>`
5. Start development server `npm run dev`
6. Inspect generated css: 
![image](https://github.com/user-attachments/assets/7d93e5ac-6858-4bb7-bb5d-856c3e123f58)
7. Notice the invalid svg -> js transformation and missing flag icon in the page itself




### Current vs. Expected behavior
Current behavior: Svgr transforms all svg imports to js files breaking ones in css
Expected: I should be able to specify what files and when are transformed via i.e issuer. This is possible in webpack-land and svgr has a documented way of avoiding this bug:
https://react-svgr.com/docs/webpack/#use-svg-in-css-files

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home
  Available memory (MB): 32713
  Available CPU cores: 12
Binaries:
  Node: 22.2.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.15 // Latest available version is detected (14.2.15).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Developer Experience, Turbopack, Webpack

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: ui
Issue: [bug]: The component at https://ui.shadcn.com/r/colors/violet.json was not found.
Labels: bug

### Describe the bug

I followed instructions to add the _select_ component https://ui.shadcn.com/docs/components/select

When I install : `pnpm dlx shadcn@latest add select`, I have directly an error: 

```
pnpm dlx shadcn@latest add select                                                                                                             ─╯

.../Library/pnpm/store/v3/tmp/dlx-63619  | +180 ++++++++++++++++++
.../Library/pnpm/store/v3/tmp/dlx-63619  | Progress: resolved 180, reused 180, downloaded 0, added 180, done
✔ Checking registry.
✔ Installing dependencies.
⠋ Updating files.

Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

The component at https://ui.shadcn.com/r/colors/violet.json was not found.
It may not exist at the registry. Please make sure it is a valid component.

 ERROR  Command failed with exit code 1: shadcn add select

pnpm: Command failed with exit code 1: shadcn add select
    at makeError (/snapshot/dist/pnpm.cjs)
    at handlePromise (/snapshot/dist/pnpm.cjs)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async Object.handler [as dlx] (/snapshot/dist/pnpm.cjs)
    at async /snapshot/dist/pnpm.cjs
    at async main (/snapshot/dist/pnpm.cjs)
    at async runPnpm (/snapshot/dist/pnpm.cjs)
    at async /snapshot/dist/pnpm.cjs
    ```


### Affected component/components

Select

### How to reproduce

```sh
pnpm dlx shadcn@latest add select
```

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Mac M1, iOS 18


 "react": "^18.3.1",
 "react-dom": "^18.3.1",
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: go
Issue: proposal: cmd/go: make build cache trimming cutoff configurable
Labels: Proposal

### Proposal Details

The current policy assumes that caching is being used by a single developer. However, there are scenarios where the cache is shared across multiple developers and the cache size accumulation can have meaningful impact.

For example, CI where there can be many developers contributing code in a single day and leveraging a shared cache (e.g. GitHub Actions Cache where there is a cache size limit and also time spent loading and saving the cache). In these cases, 5 days of cache accumulation can have meaningful impacts.

Thank you for your consideration!
Repository: flutter
Issue: [Impeller] Work around compiler errors on amd64 bots.
Labels: P1,team-engine,triaged-engine

We are running [into errors on presub on amd64 bots](https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20Engine%20Drone/1217442/infra) we don't know how to debug. A workaround is to switch to Apple Silicon bots instead (and maybe file a radar).
Repository: terminal
Issue: Consolidate Tray Icons OR (alternatively) Distinguish between Elevated and Unelevated Instances
Labels: Issue-Feature,Help Wanted,Area-UserInterface,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

Currently, if we have two instances of Terminal running (one elevated and one not), we get two _identical_ icons in the task bar.  This can be a slight inconvenience when Terminal is set to minimize to tray, as often, it requires that we activate both windows to determine which is the one with which we actually want to interact:

![Image](https://github.com/user-attachments/assets/3c8c3cc0-5a42-435f-a6dc-975caf9558e4)

An improvement could be as simple as a change of color, or a small shield badge to differentiate the two icons.  Or even better, (if it's even possible) consolidate the icons into one, and allow the user to select the desired window from a context menu.

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: deno
Issue: Support `workspace:` dependencies with an alias in a package.json
Labels: bug,workspaces

Version: Deno 2.0.0

I thought try out new Deno2.0 in my project where i have configured the workspace with local package aliasing like the following i have been using with pnpm.
```javascript
"eslint-config-standard-kf": "workspace:eslint-config-standard-kf@latest",
```

But it did not work as expected throwing following error in console
```
error: Failed to install from package.json

Caused by:
    0: Invalid version requirement
    1: Unexpected character.
         eslint-config-standard-kf@latest
         ~

```
Repository: ollama
Issue: Hugging Face Idefics3
Labels: model request

There is a new Idefics3 model on Hugginf Face, based on Llama3:
https://huggingface.co/docs/transformers/main/en/model_doc/idefics3#idefics3

Any chance you can add this to Ollama?
Repository: Python
Issue:  Feature Request: Add LSTM Algorithm to Neural Network Algorithms
Labels: enhancement

### Feature description

Add LSTM Algorithm to Neural Network Algorithms

**Feature Description:**

I would like to propose adding an LSTM (Long Short-Term Memory) algorithm to the existing neural network algorithms in the repository. LSTMs are a type of recurrent neural network (RNN) that excel in handling sequential and time-series data, making them particularly valuable for tasks such as language modeling, text generation, and time-series forecasting.

**Proposed Improvements:**

1. **Implementation of LSTM**: Develop a comprehensive LSTM class that includes essential functionalities such as:
   - Forward propagation through LSTM layers.
   - Backpropagation through time (BPTT) for training.
   - Methods for saving and loading the model.
   - Support for various activation functions (sigmoid, tanh, softmax).

2. **Example Usage**: Include example usage code demonstrating how to train the LSTM on a dataset, such as predicting the next character in Shakespeare's text.

3. **Documentation**: Provide detailed documentation on the LSTM algorithm's implementation, explaining its structure, hyperparameters, and training process.

4. **Unit Tests**: Implement unit tests to ensure the correctness and robustness of the LSTM functionality.

**Rationale:**

Adding LSTM capabilities will enhance the versatility of the neural network algorithms available in this repository, allowing users to tackle a wider range of problems involving sequential data. Given the growing importance of time-series analysis and natural language processing, this addition would significantly benefit the community.
Repository: godot
Issue: HTCXR XR Elite does not load the android editor in XR Mode
Labels: bug,platform:android,topic:editor,topic:porting,topic:xr

### Tested versions

- Reproducible https://github.com/godotengine/godot/commit/db66bd35af704fe0d83ba9348b8c50a48e51b2ba

### System information

HTC XR Elite

### Issue description

The HTC XR Elite does not load the editor in XR. The editor works in "flat" editor mode.

See also Bastian's commentary on how to implement on the manifests. https://github.com/godotengine/godot/issues/97907

Split from https://github.com/godotengine/godot/issues/97907

### Steps to reproduce

1. Download from github actions the android editor build
2. Notice that there is not htcvive xrelite build
3. The XRElite can run the android flat build
3. The XRElite fails in android openxr

### Minimal reproduction project (MRP)

https://github.com/user-attachments/files/17271320/demo-bug.zip