sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Skybox does not write to velocity render layer
Labels: bug,topic:rendering,topic:3d

### Tested versions

v4.3.beta2.official https://github.com/godotengine/godot/commit/b75f0485ba15951b87f1d9a2d8dd0fcd55e178e4

### System information

Windows 10 - Godot v4.3.beta https://github.com/godotengine/godot/commit/16f98cd7079c2b22248ec358371f17bca355e42e

### Issue description

This comes from testing the motion blur implementation made by me and the one made by @wojtekpil. In the debug view in the demo I made, you can see the velocity texture at the top left, being left at (0, 0) when nonoccluded skybox is in view, regardless of camera motion and rotation.
![image](https://github.com/godotengine/godot/assets/61445300/59fe8443-ac04-452b-82f2-e332fc6a0e69)

Discussion has started here:
https://discord.com/channels/809721752019402762/1250813037221384245/1259859226336034916

### Steps to reproduce

1. download and open the demo at https://github.com/sphynx-owner/JFA_driven_motion_blur_demo
2. press play, and then Z to enable the debug view
3. look at the sky and keep it in view while looking around to see that is does not feed to the velocity buffer displayed at the top left, and thus does not get blurred.

### Minimal reproduction project (MRP)

https://github.com/sphynx-owner/JFA_driven_motion_blur_demo
Repository: vscode
Issue: "Opening URIs can be insecure" warning appears, but link is still opened.
Labels: bug,terminal-links

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: Version: 1.92.0-insider
- OS Version: macOS 12.7.5

Steps to Reproduce:

1. In the terminal, run 
      - `echo -e "\e]8;;spotify://\e\hello\e]8;;"` (if you have Spotify installed)
      - `echo -e "\e]8;;ical://\e\hello\e]8;;" ` (on a Mac)
      - `echo -e "\e]8;;ms-windows-store://\e\hello\e]8;;"  ` (on Windows)
2. Click the link in the terminal.
You will get a popup prompt asking if you want to open the URI, but the URI will also be opened immediately (even if you don't click Allow)

Seems like the check is here: https://github.com/microsoft/vscode/blob/a4a56d80b3d5569ca810014f92400314cb486d64/src/vs/workbench/contrib/terminalContrib/links/browser/terminalLinkManager.ts#L115-L134, but it only checks when showing the notification. The link is opened unconditionally.
Repository: godot
Issue: FSR2 viewport 3D scaling mode overrides velocity render layer values
Labels: bug,topic:rendering,topic:3d

### Tested versions

v4.3.beta2.official https://github.com/godotengine/godot/commit/b75f0485ba15951b87f1d9a2d8dd0fcd55e178e4

### System information

Windows 10 - Godot v4.3.beta https://github.com/godotengine/godot/commit/16f98cd7079c2b22248ec358371f17bca355e42e

### Issue description

This comes from testing the motion blur implementation made by me and the one made by @wojtekpil. When FSR2 interpolation is enabled, the debug view reveals that the velocity render layer (showed at the top right) gets flushed to values of (1, 1) and above, evident by the yellow color the across the velocity texture and the tone mapping dimming the entire screen when those textures are displayed, while keeping the original velocity values for some foreground elements like the player and street sign in that case. This results in extreme diagonal constant smear of the environment when the blur effect attempts to use it even when no motion is being performed like in the images below.

![image](https://github.com/godotengine/godot/assets/61445300/e5777613-41e8-4132-9937-2776b00f402a)

![image](https://github.com/godotengine/godot/assets/61445300/a394a4fd-a4cd-4084-b55d-1f5631e9ddc7)


### Steps to reproduce

1. download and open the demo at https://github.com/sphynx-owner/JFA_driven_motion_blur_demo
2. go to Resources/ScalabilitySettings.tres, double click it, and in the Normal setting resource, set the Scaling parameter to Viewport Scaling 3D Mode Fsr2
3. press play, and then Z to enable the debug view
4. look at the sky and keep it in view while looking around to see that is does not feed to the velocity buffer displayed at the top left, and thus does not get blurred.

### Minimal reproduction project (MRP)

https://github.com/sphynx-owner/JFA_driven_motion_blur_demo
Repository: kubernetes
Issue: Make churnOp in scheduler_perf more useful for recreating the pods
Labels: sig/scheduling,kind/feature,needs-triage

### What would you like to be added?

Recreate mode in `churnOp` in scheduler_perf tests is not well suited for gradually adding and deleting the pods. Especially, it doesn't ensure the pod is scheduled before deleting it, which can result in measuring different paths of the code implicitly within one test case like in [this example](https://github.com/kubernetes/kubernetes/pull/125504#discussion_r1644424572). 

/sig scheduling

### Why is this needed?

It will make the tests more stable and result in more meaningful measurements. Adding the test cases like #125504 will be much easier in the future.
Repository: ui
Issue: [bug]: 'k' is defined but never used.
Labels: bug

### Describe the bug

In `chart.tsx` or in `components/ui/charts.tsx` in line 11:

```ts
export type ChartConfig = {
  [k in string]: {
  ^^
    label?: React.ReactNode
    icon?: React.ComponentType
  } & (
    | { color?: string; theme?: never }
    | { color?: never; theme: Record<keyof typeof THEMES, string> }
  )
}
```

An error occured saying "'k' is defined but never used.".

Any ways or solutions to fix this?

### Affected component/components

chart.tsx

### How to reproduce

1. Go to `components/ui/chart.tsx`
2. Check line 11

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
OS Name:                   Microsoft Windows 11 Home Single Language
OS Version:                10.0.22621 N/A Build 22621
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          asus
Registered Organization:   N/A
Product ID:                XXXXXXXXXXXXXXXXXXXX
Original Install Date:     21/07/2023, 1:48:39 pm
System Boot Time:          09/07/2024, 10:03:39 am
System Manufacturer:       ASUSTeK COMPUTER INC.
System Model:              VivoBook_ASUSLaptop X515DAP_M515DA
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ui
Issue: [bug]: Select removes scrollbar
Labels: bug

### Describe the bug

When using a select somewhere and the body has a scrollbar, this scrollbar gets removed as soon as the select is used.
![showcase](https://github.com/shadcn-ui/ui/assets/38015859/12ca8516-baa0-447f-b75a-78aa82cd9c66)

### Affected component/components

Select

### How to reproduce

1. Give the body a scrollbar
2. Add a Select
3. Open the Select

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: opencv
Issue: CV_Bool support is not complete
Labels: feature,category: core

### Describe the feature and motivation

Currently OpenCV 5.x has 2 options for flags/bools:
- cv::Mat with CV_Bool type
- cv::Mat with CV_8U type or std::vector<bool> treated as bit array.

cv::norm does not support  CV_Bool as input
cv::norm interprets CV_8U matrix as regular integer matrix for NORM_INF and NORM_2 and as bit array for NORM_HAMMING
Also CV_Bool is not supported by cv::Hamming, HAL functions.

Options:
- Add CV_Bool support for Hamming, NORM_HAMMING case and all related functions
- Added a way to squeeze / unsqueeze the bit arrays from/to CV_Bool type.

### Additional context

_No response_
Repository: ui
Issue: [bug]: chart not rendering
Labels: bug

### Describe the bug

Hey, I am using charts, and everything was working fine, but now suddenly the pie chart is not rendering. This happens when I use two pie charts side by side.
but it rendered the data. 
see the below image

![charts-bug](https://github.com/shadcn-ui/ui/assets/111105752/1cd0a328-afbb-4e13-97d8-1c10ecc1c0c9)


### Affected component/components

chart

### How to reproduce

no

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
node-20
next-14
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: rust
Issue: On Windows a `static` address changes when copied into another `static` across a module boundary
Labels: O-windows,C-bug

Technically not the address of the `static` itself, but it is a confusing interaction

I tried this code:

```rust
mod m {
    pub static IN_MOD: &str = &"s";
    pub static IN_MOD_2: &str = IN_MOD;
}

static OUTSIDE: &str = m::IN_MOD;

fn main() {
    println!("{:p}", m::IN_MOD);
    println!("{:p}", m::IN_MOD_2);
    println!("{:p}", OUTSIDE);
}

```

I expected to see this happen:

The same address printed 3 times as it is on Linux

Instead, this happened:

```
0x7ff6dba2a370
0x7ff6dba2a370
0x7ff6dba2a3c8
```

In `--release` mode the three addresses are the same

### Meta

Stable behaves the same

`rustc --version --verbose`:
```
rustc 1.81.0-nightly (35b658fb1 2024-07-08)
binary: rustc
commit-hash: 35b658fb1071d752d092751d9f17a9fa7b154ec4
commit-date: 2024-07-08
host: x86_64-pc-windows-msvc
release: 1.81.0-nightly
LLVM version: 18.1.7
```
Repository: pytorch
Issue: why not enable expandable_segments by default？
Labels: module: performance,module: cuda,triaged

### 🚀 The feature, motivation and pitch

I see someone mentioned earlier about enabling expandable_segments  by default. What are the risks of this being enabled by default? Why isn't it on by default?
https://github.com/pytorch/pytorch/pull/99093

### Alternatives

_No response_

### Additional context

_No response_

cc @ptrblck @msaroufim
Repository: TypeScript
Issue: tsserver with `"module": "Preserve"` and `"moduleResolution": "Bundler"` adds .js extensions to imports
Labels: Bug,Help Wanted

### 🔎 Search Terms

Preserve, Bundler, .js extension

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about completions



### ⏯ Playground Link

https://github.com/segevfiner/typescript-js-extension-issue

### 💻 Code

Completion in the `"./foo"` in the lines below uncommented results in `./foo.js` despite using `"moduleResolution": "Bundler"`.
```ts
// import { FOO } from "./foo";
// import { FOO } from "./foo.js";
```


### 🙁 Actual behavior

It completes to `./foo.js`

### 🙂 Expected behavior

It should complete to `./foo` as we are in `"moduleResolution": "Bundler"` but `"module": "Preserve"` causes it to add the `js` extension.

### Additional information about the issue

_No response_
Repository: ui
Issue: [bug]: Tooltips on Firefox Jitter
Labels: bug

### Describe the bug

Tooltips on charts jitters/moves choppily on firefox, works fine on chrome.

### Affected component/components

Charts

### How to reproduce

1. Use firefox
2. Go to https://ui.shadcn.com/docs/components/chart
3. Hover over a chart
4. Observe choppiness
5. test again on chrome


### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Firefox
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: react-native
Issue: Secure text entry flickers on iOS
Labels: Platform: iOS,Issue: Author Provided Repro

### Description

On iOS (With a Simulator or a real device), if you have a `TextInput` component with `secureTextEntry={true}` and a custom font, the text flickers when you enter a character and remove it.

Note: this also happens with the old renderer.

### Steps to reproduce

1. Install the application with `yarn ios`
2. Focus on the text input
3. Enter a character and then remove it

### React Native Version

0.74.3

### Affected Platforms

Runtime - iOS

### Areas

Fabric - The New Renderer

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.3
  CPU: (10) arm64 Apple M1 Pro
  Memory: 98.19 MB / 16.00 GB
  Shell:
    version: 0.91.0
    path: /Users/burakguner/.cargo/bin/nu
Binaries:
  Node:
    version: 21.7.1
    path: ~/.nix-profile/bin/node
  Yarn:
    version: 4.3.1
    path: ~/.nix-profile/bin/yarn
  npm:
    version: 10.5.0
    path: ~/.nix-profile/bin/npm
  Watchman:
    version: 2024.01.22.00
    path: /Users/burakguner/.nix-profile/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/burakguner/.local/share/gem/ruby/3.1.0/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.0
      - iOS 17.0
      - macOS 14.0
      - tvOS 17.0
      - watchOS 10.0
  Android SDK: Not Found
IDEs:
  Android Studio: Hedgehog 2023.1.1 Patch 2 Hedgehog 2023.1.1 Patch 2
  Xcode:
    version: 15.0.1/15A507
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.8
    path: /usr/bin/javac
  Ruby:
    version: 3.1.4
    path: /Users/burakguner/.nix-profile/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.3
    wanted: 0.74.3
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: true
```
```


### Stacktrace or Logs

```text
There is no stack trace.
```


### Reproducer

https://github.com/atlj/secure-text-entry-flicker

### Screenshots and Videos


https://github.com/facebook/react-native/assets/23079646/7a260380-eb2c-434c-97f3-af14dd51a5af
Repository: ollama
Issue: ollama env cmd  and  http api！
Labels: feature request

can get or  set ollama all env vars

for exsample 

OLLAMA_HOST


:= os.Getenv("OLLAMA_HOST")



	hipVD := os.Getenv("HIP_VISIBLE_DEVICES")   // zero based index only
	rocrVD := os.Getenv("ROCR_VISIBLE_DEVICES") // zero based index or UUID, but consumer cards seem to not support UUID
	gpuDO := os.Getenv("GPU_DEVICE_ORDINAL")    // zero based index
Repository: next.js
Issue: Back/forward cache incorrectly applied on a force-dynamic page when starting from static page
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/HarroE/nextjs-bug 

### To Reproduce

**Setup:**
- NextJS app with a static page with a link to a dynamic page
- The dynamic page with a button that redirects to an external website that also changes some state when you click on the button

**Steps to reproduce bug:**
1. Build app (npm build)
2. Start the app (npm start)
3. Directly open the static page (important!)
4. Navigate to a dynamic page by clicking on the Link on the static page
5. On the dynamic page, click on the button to be redirected to an external website
6. Use the browser back button to go back to the dynamic page



### Current vs. Expected behavior

When you get back to the dynamic page you will still see the loading state and not the initial state as expected.

When you refresh the dynamic page (so not starting from the static page) and then click on the external link and click browser back, you will see the initial state as expected.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:14:38 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6020
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 21.1.0
  npm: 10.2.0
  Yarn: 1.22.21
  pnpm: 8.14.0
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: 14.2.4
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure, Navigation

### Which stage(s) are affected? (Select all that apply)

next start (local)

### Additional context

Turning off the back/forward cache in your browser would fix it for your particular browser
In chrome you can turn it off here: chrome://flags/#back-forward-cache
Repository: tauri
Issue: [bug] `window.set_cursor_visible(false)` does not work.
Labels: type: bug,status: needs triage

### Describe the bug

When creating a window, and running `window.set_cursor_visible(false)`, the cursor should be hidden when the window opens. It isn't.

### Reproduction

during setup, run the following:
```rs
tauri::Builder::default()
    // ... initial tauri context builder calls
    app.setup(|app| {
        let window = app.get_webview_window("main").unwrap();
        // Cursor
        window.set_cursor_visible(false)?;
    })
    // ... rest of tauri init
    .run(tauri::generate_context!())
```

### Expected behavior

The cursor should be hidden/invisible.

### Full `tauri info` output

```text
`cargo tauri info`

[✔] Environment
    - OS: Windows 10.0.19045 X64
    ✔ WebView2: 126.0.2592.87
    ✔ MSVC: 
        - Visual Studio Community 2019
        - Visual Studio Community 2022
    ✔ rustc: 1.78.0 (9b00956e5 2024-04-29)
    ✔ cargo: 1.78.0 (54d8815d0 2024-03-26)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (environment override by RUSTUP_TOOLCHAIN)
    - node: 20.13.1
    - yarn: 1.22.15
    - npm: 10.5.2

[-] Packages
    - tauri [RUST]: 2.0.0-beta.23      
    - tauri-build [RUST]: 2.0.0-beta.18
    - wry [RUST]: 0.41.0
    - tao [RUST]: 0.28.1
    - tauri-cli [RUST]: 2.0.0-beta.17  
    - @tauri-apps/api [NPM]: 2.0.0-beta.14
    - @tauri-apps/cli [NPM]: 2.0.0-beta.17

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite
```


### Stack trace

```text
N/A - Not a crash
```


### Additional context

Setting the CSS `cursor: none;` property works, but requires user interaction to take effect.

(to help this come up if someone else searches for it: the method set_cursor_visible on window is not working)
Repository: godot
Issue: GPUParticles with trails enabled have inconsistent rendering for particles at high speed and big lifetime
Labels: bug,topic:rendering,topic:particles

### Tested versions

- Reproducible in 4.2.2 stable mono

### System information

Godot v4.2.2.stable.mono - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 SUPER (NVIDIA; 31.0.15.5212) - AMD Ryzen 7 3800X 8-Core Processor (16 Threads)

### Issue description



https://github.com/godotengine/godot/assets/28916549/0eab1d86-fc5a-44a5-955c-72bfece537eb

When using GPUParticles with trails enabled, if a particle has a high initial velocity, particles starting position does not stay in place, and flickers between frames, causing the effect from the above

I expect particles starting position to remain still unless trail's lifetime ends.

I also experimented with speed scale and got very weird flickering like in the example below:

https://github.com/godotengine/godot/assets/28916549/06a81aac-4a68-44c2-87fd-bf3720301d1f




### Steps to reproduce

- Create a GPUParticle3D
- Add new ParticleProcessMaterial
- Enable Trails
- In ParticleProcessMaterial->Spawn->Velocity set initial velocity min to something like 150
- In Draw Passes add new RibbonTrailMesh or TubeTrailMesh
- In Pass settings create a new Material
- In Material->Transform enable Use Particle Trails

### Minimal reproduction project (MRP)

[effects_bug.zip](https://github.com/user-attachments/files/16145952/effects_bug.zip)
Repository: stable-diffusion-webui
Issue: [Bug]: Out of memory while using Upscaler
Labels: bug-report

### Checklist

- [ ] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

Upscaling the image with R-ESRGAN 4x+ (512x512 to 2048x2048) in Hires.fix tab consumes more than 32 GB of memory.
Just don't give me the nonsense that this operation needs that much memory.
Looks like there's some kind of memory leak in the webui.
So much memory is not consumed when upscaling an image in Extras tab.

### Steps to reproduce the problem

-
### What should have happened?

-

### What browsers do you use to access the UI ?

Microsoft Edge

### Sysinfo

-

### Console logs

```Shell
-
```


### Additional information

_No response_
Repository: godot
Issue: AudioStreamInteractive does not scale with editor & other minor visual issues
Labels: bug,topic:editor

### Tested versions

- Reproducible in godot v4.3 beta 2. 

### System information

Godot v4.3.beta2 - macOS 14.5.0 - Vulkan (Forward+) - integrated Apple M2 - Apple M2 (8 Threads)

### Issue description

There are a few broken interfaces in the new AudioStreamInteractive node. 

Overlapping text/buttons. 
If these texts are buttons, they do not respond. 
<img width="1538" alt="Screenshot 2024-07-09 at 10 55 29 AM" src="https://github.com/godotengine/godot/assets/164022421/7463a9e9-504b-4df8-9259-56bbf5b5730a">

Empty dialogue
<img width="350" alt="Screenshot 2024-07-06 at 8 50 58 AM" src="https://github.com/godotengine/godot/assets/164022421/9c381d78-89fc-4ef8-be9f-990e7ae6d2ee">

If you have no clips, this is blank. May be intentional?
<img width="1582" alt="Screenshot 2024-07-06 at 8 50 42 AM" src="https://github.com/godotengine/godot/assets/164022421/f9af230c-df08-4097-a61b-4151be674001">


### Steps to reproduce

Create a new project on the specified hardware. 
Create a Node. Give it an AudioStreamPlayer as a child. 
In Inspector, select Interactive for Stream. 

Issue 1: click on switch to clip - a very very small empty box appears. 
Inside stream:
Add a clip. Leave it blank. 
Click on Edit Transitions. 
Issue 2: The text "To" "Fro-" and "Any" appear on top of each other. 



### Minimal reproduction project (MRP)

[IssueProject.zip](https://github.com/user-attachments/files/16146484/IssueProject.zip)