sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tensorflow
Issue: `SIGSEGV ` (Address boundary error) in `tf.io.gfile` with `TF_USE_MODULAR_FILESYSTEM=1`
Labels: stat:awaiting tensorflower,type:bug,TF 2.16

### Issue type

Bug

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

Yes

### Source

binary

### TensorFlow version

2.16.1, 2.17.0rc0, 2.18.0.dev20240617

### Custom code

No

### OS platform and distribution

macOS 14.5

### Mobile device

_No response_

### Python version

3.11

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

A `SIGSEGV` (Address boundary error) fault can be caused by trying to call tensorflow gfile API when a `TF_USE_MODULAR_FILESYSTEM=1` is set. This can be reproduced in version 2.16.1 and 2.17.0rc0 and the latest nightly.

### Standalone code to reproduce the issue

```shell
TF_USE_MODULAR_FILESYSTEM=1 python -c 'import tensorflow as tf;tf.io.gfile.exists("gs://tfds-data/dataset_info/mnist/3.0.1/dataset_info.json")'
```


### Relevant log output

```shell
Job 1, 'TF_USE_MODULAR_FILESYSTEM=1 pyt…' terminated by signal SIGSEGV (Address boundary error)
```
Repository: opencv
Issue: Tests failed on Loongarch platform because of divided by 0 is being handled incorrectly
Labels: bug,RFC,platform: loongson

### System Information

CI: auto test on LoongArch platform

### Detailed description

Two modules failed to pass the tests, namely Performance:gapi and Python3. 

The analysis shows that the cause of the error in python3 occurs in the test of the `cv::divide` interface. The python interface will do data processing. When the divisor is 0, it will be changed to the maximum value of its data type. Then the result of the division operation is 0, but when `cv::divide` divides by 0, it returns 0x7f800000, and the final result is saturated to 255. The same reasons apply to the gapi module. 

The solution is to perform a check for INF within the **cv_round** function in the include/opencv2/core/hal/intrin_lasx.hpp file. When submitting the pull request last year, the issue regarding cv_round was discussed. For more details, please see https://github.com/opencv/opencv/pull/23929.

### Steps to reproduce

none

### Issue submission checklist

- [X] I report the issue, it's not a question
- [ ] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [ ] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: three.js
Issue: Shader unit test framework
Labels: Suggestion

### Description

We have many many GLSL functions that use all over the place in our shaders.

These functions can have subtle bugs or problems with their extremes.

We really do not check if these functions operate correctly via unit tests because we do not have unit tests that work with shaders.

### Solution

For threeify, I implemented a quick and dirty shader unit test system.

You could write tests in this fashion:

```glsl
#pragma import "../tests/fragment.glsl"
#pragma import "./normalPacking.glsl"

void testEquivalency(inout TestSuite suite, int testId, vec3 normal) {
  vec3 rgb = normalToRgb(normal);
  vec3 normal2 = rgbToNormal(rgb);
  assert(suite, testId, eqAbs(normal, normal2, 0.0001));
}

void tests(inout TestSuite suite) {
  vec3 px = vec3(1.0, 0.0, 0.0);
  vec3 py = vec3(0.0, 1.0, 0.0);
  vec3 pz = vec3(0.0, 0.0, 1.0);

  testEquivalency(suite, 3, px);
  testEquivalency(suite, 4, -px);
  testEquivalency(suite, 5, py);
  testEquivalency(suite, 6, -py);
  testEquivalency(suite, 7, pz);
  testEquivalency(suite, 8, -pz);

}
```

Another example here: https://github.com/bhouston/threeify/blob/main/packages/core/src/shaders/math/unitIntervalPacking.test.glsl

And then it would be executed so that each test would write to a pixel in an output texture 0 or 1.  And then you could read back that texture and see if all unit tests pass -- all 1s:

```ts
  const passMaterial = new ShaderMaterial(
        'index',
        vertexSource,
        glslUnitTest.source
      );
      const unitProgram = await shaderMaterialToProgram(context, passMaterial);

      framebuffer.clear(BufferBit.All);
      renderPass({
        framebuffer,
        program: unitProgram,
        uniforms: unitUniforms
      });

      const result = frameBufferToPixels(framebuffer) as Uint8Array;

      for (let i = 0; i < result.length; i += 4) {
        const runResult = result[i + 2];
        const id = i / 4;
        switch (runResult) {
          case 0:
            failureIds.push(id);
            break;
          case 1:
            passIds.push(id);
            break;
          case 3:
            duplicateIds.push(id);
            break;
        }
      }
```

Full source code here: https://github.com/bhouston/threeify/blob/main/examples/src/units/glsl/index.ts

Adding this to Three.js would extend the robustness of Three to the shader level.  It would also help identify GPU hardware / drivers that are misbehaving in a much faster way than we currently do.  Basically you will see specific tests fail for GPU X and know exactly what you have to do to fix it.


### Alternatives

Unsure of alternatives, maybe something new with TSL?

### Additional context

We identified recently that some of our packing / unpacking code for GLSL is buggy and has been for many years: https://github.com/mrdoob/three.js/issues/28692
Repository: TypeScript
Issue: JSDoc: property access within static initialization block of @extends annotated class from different file
Labels: Bug,Help Wanted

### 🔎 Search Terms

"jsdoc class @extends", "static initialization block", "static properties/methods", "class extends", "class is referenced directly or indirectly in its own base expression"

### 🕗 Version & Regression Information

- Static initialization blocks don't seem to be supported on versions `<= 4.3.5`
- From `4.4.2` to `4.6.4` everything seems to work fine - types are correct and no linting errors
- Every version from `4.7.2` onwards has the behaviour described in this issue


### ⏯ Playground Link

_No response_

### 💻 Code

`a.js`:
```js
export class A {
  static a() {}
}
```

`b.js`:
```js
// @ts-check
import { A } from "./a";

/**
 * @extends A
 */
export class B extends A { // 'B' is referenced directly or indirectly in its own base expression.ts(2506)
  static {
    B.a(); // Property 'a' does not exist on type 'typeof B'. ts(2339)
  }

  constructor() {
    super();

    B.a(); // Property 'a' does not exist on type 'typeof B'. ts(2339)
  }

  b() {
    B.a(); // Property 'a' does not exist on type 'typeof B'. ts(2339)
  }

  c = () => {
    B.a(); // Property 'a' does not exist on type 'typeof B'. ts(2339)
  };

  static d() {
    B.a(); // Property 'a' does not exist on type 'typeof B'. ts(2339)
  }

  get e() {
    B.a(); // Property 'a' does not exist on type 'typeof B'. ts(2339)

    return;
  }

  set e(value) {
    B.a(); // Property 'a' does not exist on type 'typeof B'. ts(2339)
  }
}
```


### 🙁 Actual behavior

- Linting error under extending class's name: `'B' is referenced directly or indirectly in its own base expression.`.
- Linting error/unknown type for any use of `B.a()`.

### 🙂 Expected behavior

`B.a()` type is correct across files with no linting errors.

### Additional information about the issue

- Removing `@extends` fixes the issue
- Removing `B.a()` from the `static` block fixes the issue
- Defining `A` in the same file fixes the issue

Possibly related to #51786.
Repository: PowerToys
Issue: Host File Editor - Comment in own column
Labels: Needs-Triage

### Description of the new feature / enhancement

Please move the comments to a separate column instead of writing it behind the host(s) separated by a hyphen:

![image](https://github.com/microsoft/PowerToys/assets/158451102/fce6ecc8-9712-4b9d-8d18-35ac2167c138)


### Scenario when this would be used?

Watching the host entries in the list.

### Supporting information

_No response_
Repository: ollama
Issue: `ollama show` should have the exact parameter count rounded to 3 digits
Labels: bug,api

### What is the issue?

```
% ollama show llama3
  Model                                              
  	arch            	llama	                              
  	parameters      	8.0B 	                              
  	quantization    	Q4_0 	                              
  	context length  	8192 	                              
  	embedding length	4096 	         
```

should be the same as

<img width="793" alt="Screenshot 2024-06-20 at 10 21 28 AM" src="https://github.com/ollama/ollama/assets/251292/3e9ac431-e205-45b9-91ef-b63ddc8fe0f9">


### OS

_No response_

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_
Repository: flutter
Issue: [flutter_markdown] Disposes gesture recognizers when reparenting
Labels: package,team-ecosystem,has reproducible steps,P2,p: flutter_markdown,triaged-ecosystem,found in release: 3.22

Example to reproduce
```dart
class _BaseContextMenu extends StatefulWidget {
  @override
  State<_BaseContextMenu> createState() => _BaseContextMenuState();
}

class _BaseContextMenuState extends State<_BaseContextMenu> {
  bool pointerDown = false;
  final key = GlobalKey();

  @override
  Widget build(BuildContext context) {
    final child = MarkdownBody(
      key: key,
      data: 'What is this [content](https://example.com)',
      onTapLink: (text, _, __) {
        print('Clicked on $text');
      },
    );
    return Listener(
      onPointerDown: (event) {
        setState(() {
          pointerDown = true;
        });
      },
      onPointerUp: (event) {
        setState(() {
          pointerDown = false;
        });
      },
      child: pointerDown
          ? ColoredBox(
              color: Colors.green,
              child: child,
            )
          : child,
    );
  }
}
```

The recognizer is never triggered, because gesture detectors are disposed inside `_MarkdownWidgetState.didChangeDependencies()` (through `_parseMarkdown`).  During element reparenting the element is deactivated and activated, and `didChangeDependencies` is called during element activation.
Repository: ollama
Issue: florance vision model
Labels: model request

https://huggingface.co/microsoft/Florence-2-large/tree/main uses pytorch 
https://huggingface.co/spaces/SixOpen/Florence-2-large-ft
Repository: storybook
Issue: [Bug]: previewMainTemplate Option Ignored, Default Template Used Instead
Labels: bug,needs triage

### Describe the bug

In the Storybook configuration, there is an option called previewMainTemplate which is intended to allow users to override the default template.ejs used by the Storybook build-manager when creating the main index.html of the standalone application.

However, when a custom path to an .ejs template is provided for the previewMainTemplate option and either `storybook build` or `storybook dev` is run, the custom template is not utilized as expected. Instead, the build process continues to use the default `template.ejs` , ignoring the previewMainTemplate configuration. 

### Reproduction link

https://stackblitz.com/edit/github-sbmzvp?file=.storybook%2FcustomIndex.ejs&view=editor

### Reproduction steps

1. Go to the link above
2. Wait for the execution of `yarn build-storybook` or execute it manually in the integrated terminal
3. Open the generated `storybook-static/index.html` a
4. Compare the mentioned file with `.storybook/customIndex.ejs` template if the correct changes are being applied from the template to the static html file.

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.2
    CPU: (12) arm64 Apple M2 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.19.1 - ~/.nvm/versions/node/v18.19.1/bin/node
    npm: 10.2.4 - ~/.nvm/versions/node/v18.19.1/bin/npm
    pnpm: 8.9.0 - ~/Library/pnpm/pnpm <----- active
  Browsers:
    Chrome: 122.0.6261.129
    Safari: 17.2
  npmPackages:
    @storybook/addon-essentials: ^8.1.10 => 8.1.10 
    @storybook/addon-interactions: ^8.1.10 => 8.1.10 
    @storybook/addon-links: ^8.1.10 => 8.1.10 
    @storybook/addon-onboarding: ^8.1.10 => 8.1.10 
    @storybook/blocks: ^8.1.10 => 8.1.10 
    @storybook/react: ^8.1.10 => 8.1.10 
    @storybook/react-vite: ^8.1.10 => 8.1.10 
    @storybook/test: ^8.1.10 => 8.1.10 
    eslint-plugin-storybook: ^0.8.0 => 0.8.0 
    storybook: ^8.1.10 => 8.1.10
```


### Additional context

This is happening because in this line
https://github.com/storybookjs/storybook/blob/56b17c6683fc15732acae95538bda8110f891bd6/code/builders/builder-manager/src/utils/data.ts#L18
 the value of the the path to the template is being harcoded and resolved to the template.ejs of the library instead of resolving from the options.
 
 In the meantime I provided a turn around while I work in the solution
 #28301
Repository: puppeteer
Issue: [Feature]: Document the use of abort controller / signal
Labels: feature,documentation,P3

### Feature description

- dedicated mention in the locators section
- document all other wait functions
Repository: excalidraw
Issue: Whitelist the site
Labels: Embeddable

The website www.sureshsubedi.info.np is not whitelisted and hence can't be added on the whiteboard.
Repository: go
Issue: x/tools/gopls: test flakes cleaning module cache on openbsd: directory not empty
Labels: NeedsInvestigation,gopls,Tools

```
#!watchflakes
default <- pkg ~ `golang.org/x/tools/gopls/internal/test/.*` && goos == "openbsd" && `cleaning sandbox: cleaning modcache`
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8744603519900203745)):

    === RUN   TestUnknownRevision/bad/nested/default
    goroutine profile: total 9
    1 @ 0x434011 0x47309d 0x5ff551 0x5ff385 0x5fc3ab 0xe94cb0 0xe9493a 0x547df4 0x47cfc1
    #	0x5ff550	runtime/pprof.writeRuntimeProfile+0xb0						/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/pprof/pprof.go:773
    #	0x5ff384	runtime/pprof.writeGoroutine+0x44						/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/pprof/pprof.go:732
    #	0x5fc3aa	runtime/pprof.(*Profile).WriteTo+0x14a						/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/pprof/pprof.go:374
    #	0xe94caf	golang.org/x/tools/gopls/internal/test/integration.(*Runner).Run.func1.1+0x6f	/home/swarming/.swarming/w/ir/x/w/targetrepo2483330872/gopls/internal/test/integration/runner.go:198
    #	0xe94939	golang.org/x/tools/gopls/internal/test/integration.(*Runner).Run.func1+0xeb9	/home/swarming/.swarming/w/ir/x/w/targetrepo2483330872/gopls/internal/test/integration/runner.go:252
    #	0x547df3	testing.tRunner+0xf3								/home/swarming/.swarming/w/ir/x/w/goroot/src/testing/testing.go:1690
    
    ...
    #	0x4c8667	os.(*file).close+0x87							/home/swarming/.swarming/w/ir/x/w/goroot/src/os/file_unix.go:333
    #	0xc2968c	os.(*File).Close+0x2c							/home/swarming/.swarming/w/ir/x/w/goroot/src/os/file_posix.go:23
    #	0xc2932e	golang.org/x/tools/internal/gopathwalk.(*walker).walk+0x74e		/home/swarming/.swarming/w/ir/x/w/targetrepo2483330872/internal/gopathwalk/walk.go:337
    #	0xc28207	golang.org/x/tools/internal/gopathwalk.walkDir+0x347			/home/swarming/.swarming/w/ir/x/w/targetrepo2483330872/internal/gopathwalk/walk.go:120
    #	0xc3af25	golang.org/x/tools/internal/gopathwalk.WalkSkip+0x305			/home/swarming/.swarming/w/ir/x/w/targetrepo2483330872/internal/gopathwalk/walk.go:77
    #	0xc3ae12	golang.org/x/tools/internal/imports.(*ModuleResolver).scan.func4+0x1f2	/home/swarming/.swarming/w/ir/x/w/targetrepo2483330872/internal/imports/mod.go:643
    
        runner.go:199: closing the sandbox: error(s) cleaning sandbox: cleaning modcache: go command failed (stdout: ) (stderr: go: unlinkat /home/swarming/.swarming/w/ir/x/t/gopls-test-3713062884/TestUnknownRevision/bad/nested/default/gopath/pkg/mod: directory not empty
            ): exit status 1; removing files: unlinkat /home/swarming/.swarming/w/ir/x/t/gopls-test-3713062884/TestUnknownRevision/bad/nested/default/gopath/pkg/mod/cache/download/example.com/@v: directory not empty
    --- FAIL: TestUnknownRevision/bad/nested/default (34.95s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: yt-dlp
Issue: WARNING: [vimeo:user] unable to extract list title
Labels: site-bug

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm reporting that yt-dlp is broken on a **supported** site
- [X] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
- [X] I've checked that all URLs and arguments with special characters are [properly quoted or escaped](https://github.com/yt-dlp/yt-dlp/wiki/FAQ#video-url-contains-an-ampersand--and-im-getting-some-strange-output-1-2839-or-v-is-not-recognized-as-an-internal-or-external-command)
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [X] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and I'm willing to share it if required

### Region

_No response_

### Provide a description that is worded well enough to be understood

WARNING: [vimeo:user] unable to extract list title


### Provide verbose output that clearly demonstrates the problem

- [X] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [X] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

```shell
F:\_distr\yt>f:\_distr\yt\yt-dlp  --cookies-from-browser firefox --no-check-cert
ificate -f "best[height=360]"  "https://vimeo.com/coachingupuniversity?ysclid=lx
n9ho0jcr780330475"
[vimeo:user] Extracting URL: https://vimeo.com/coachingupuniversity?ysclid=lxn9h
o0jcr780330475
[vimeo:user] coachingupuniversity?ysclid=lxn9ho0jcr780330475: Downloading page 1

Extracting cookies from firefox
Extracted 3016 cookies from firefox
WARNING: [vimeo:user] unable to extract list title; please report this issue on
 https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue
template. Confirm you are on the latest version using  yt-dlp -U
[download] Downloading playlist: coachingupuniversity?ysclid=lxn9ho0jcr780330475

[vimeo:user] Playlist coachingupuniversity?ysclid=lxn9ho0jcr780330475: Downloadi
ng 0 items
[download] Finished downloading playlist: coachingupuniversity?ysclid=lxn9ho0jcr
780330475

F:\_distr\yt>yt-dlp -U
Latest version: stable@2024.05.27 from yt-dlp/yt-dlp
yt-dlp is up to date (stable@2024.05.27 from yt-dlp/yt-dlp)
```
Repository: flutter
Issue: [Impeller] shader hot reload doesn't handle UBO structure changes on vulkan backend.
Labels: P2,e: impeller,team-engine,triaged-engine

Repro, flutter run --enable-vulkan-validation with the following shader:

```
#include <flutter/runtime_effect.glsl>

uniform vec2 size;
uniform sampler2D u_texture;

out vec4 frag_color;

void main() {
  frag_color = texture(u_texture, FlutterFragCoord().xy / vec2(400, 400));
}

```

Then change it to the following and hot reload.

```
#include <flutter/runtime_effect.glsl>

uniform vec2 size;
uniform sampler2D u_texture;

out vec4 frag_color;

void main() {
  frag_color = texture(u_texture, FlutterFragCoord().xy /size));
}
```
Repository: stable-diffusion-webui
Issue: [Bug]: ADetailer + Ultimate SD Upscale + Soft Inpainting in img2img return a nearly black image
Labels: bug-report

### Checklist

- [X] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [X] 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?

Hey peeps,

I'm using the API, so when sending a payload for img2img with Ultimate SD Upscale, Adetailer and Soft Inpainting, the init image is lost in the process, after the first tile.

It's processing the first tile, then run ADetailer in the tile, then return the first tile using Soft Inpainting in a black picture.
The black image is processed until the end.
No error in the console.

It was working fine, before 1.9.0 i think.


Here is the test in the webui : 

Input image :
![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/22177081/5a525fd3-bead-44a5-85c4-d2aa3b98d727)


Here is a screenshot of the preview :
![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/22177081/f8259a18-c958-4122-ba8b-3b4d0019cb28)


It's happening whatever the settings.

I don't find any issue here about this, anyone using this ?
This is kind of a big deal for me.

Cheers ! 🥂

### Steps to reproduce the problem

1. Go to img2img
2. Add an 1MP image as input
3. Enable Soft Inpainting
4. Enable ADetailer
5. Enable USDU 
6. Generate a black image
7. Delete the black image (: 

### What should have happened?

The init image shouldn't be lost after the first tile.

### What browsers do you use to access the UI ?

Other

### Sysinfo

[sysinfo-2024-06-20-15-30.json](https://github.com/user-attachments/files/15916448/sysinfo-2024-06-20-15-30.json)


### Console logs

```Shell
No console error
```


### Additional information

_No response_
Repository: ollama
Issue: AMD Ryzen NPU support
Labels: feature request,amd

Hello! I'm want to buy Lenovo Xiaoxin 14 AI laptop on AMD Ryzen 7 8845H on my birthday and I will install Artix Linux to this. Do you will to add AMD Ryzen NPU support to Ollama on Linux and Windows? If anything, AMD Ryzen NPU driver for Linux is already available on Github:
https://github.com/amd/xdna-driver.git
Sorry for my bad English, please!
Repository: godot
Issue: Analog action deadzones interfere with key-based actions strength
Labels: bug,needs testing,topic:input

### Tested versions

- Reproducible from 4.2 onwards
- Not reproducible with 4.1.4 or earlier

### System information

Godot v4.1.4.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated GeForce RTX 3070 () - 13th Gen Intel(R) Core(TM) i7-13700K (24 Threads)

### Issue description

When using `Input.get_vector`, if any of the actions involved have an analog input bound (for example a joystick axis), the negative_x input will not have a strength of 1 when used with a non-analog input (such as a keyboard key). Instead, the strength will depend on the deadzone configured in the action.

If the deadzone param of `Input.get_vector` is set to 1, the negative_x axis will stop working altogether.

Removing the analog input from all the actions makes the issue go away.

### Steps to reproduce

In any blank project, add the following code to an empty script and attach it:

```
func _process(delta: float) -> void:
	var input := Input.get_vector("ui_left", "ui_right", "ui_down", "ui_up")
	print(input.length())
```

Run the scene and notice that, when pressing the left key, the vector strength is less than 1. For the default deadzone of 0.5, it will read around 0.81. Right, Up and Down are not affected.

### Minimal reproduction project (MRP)

N/A