sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tensorflow
Issue: tf.raw_ops.QuantizeAndDequantizeV3: Aborted (core dumped)
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.15

### Issue type

Bug

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

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.9

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Under specific input, `tf.raw_ops.QuantizeAndDequantizeV3` encounters "Aborted (core dumped)".

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

input_data = tf.constant([1.5, 2.5, 3.5, 4.5])
input_min = tf.constant([[[0.0, 0.0], [0.0, 0.0]], [[0.0, 0.0], [0.0, 0.0]], [[0.0, 0.0], [0.0, 0.0]]])

input_max = tf.constant(5.0)
num_bits = tf.constant(8)
signed_input = True
range_given = True
narrow_range = False
axis = -1

output_data = tf.raw_ops.QuantizeAndDequantizeV3(input=input_data, input_min=input_min, input_max=input_max, num_bits=num_bits, signed_input=signed_input, range_given=range_given, narrow_range=narrow_range, axis=axis)

print(output_data)
```


### Relevant log output

```shell
2024-03-14 05:50:03.159345: F tensorflow/core/framework/tensor.cc:852] Check failed: 1 == NumElements() (1 vs. 2)Must have a one element tensor
Aborted (core dumped)
```
Repository: tensorflow
Issue: tf.raw_ops.ResourceApplyMomentum: Aborted (core dumped)
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.15

### Issue type

Bug

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

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.9

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Under specific input, `tf.raw_ops.ResourceApplyMomentum` encounters "Aborted (core dumped)".

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

var = tf.Variable([1.0, 2.0, 3.0])
accum = tf.Variable([0.1, 0.2, 0.3], dtype=tf.complex64) 
lr = 0.01
grad = tf.constant([0.1, 0.2, 0.3])
momentum = 0.9

output = tf.raw_ops.ResourceApplyMomentum(var=var.handle, accum=accum.handle, lr=lr, grad=grad, momentum=momentum)

print(output)
```


### Relevant log output

```shell
2024-03-14 05:55:18.324852: F tensorflow/core/framework/tensor.cc:844] Check failed: dtype() == expected_dtype (8 vs. 1) float expected, got complex64
Aborted (core dumped)
```
Repository: tensorflow
Issue: tf.raw_ops.ResourceApplyProximalAdagrad: Aborted (core dumped)
Labels: awaiting review,type:bug,comp:ops,TF 2.15

### Issue type

Bug

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

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.9

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Under specific input, `tf.raw_ops.ResourceApplyProximalAdagrad` encounters "Aborted (core dumped)".

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

var = tf.Variable([1.0, 2.0, 3.0])
accum = tf.Variable([0.1, 0.2, 0.3])
lr = 0.01
l1 = 0.1
l2 = 0.01
grad = tf.constant([0.1, 0.2, 0.3], dtype=tf.float64)

var_resource = tf.raw_ops.VarHandleOp(dtype=var.dtype, shape=var.shape)
accum_resource = tf.raw_ops.VarHandleOp(dtype=accum.dtype, shape=accum.shape)

assign_var = tf.raw_ops.AssignVariableOp(resource=var_resource, value=var)
assign_accum = tf.raw_ops.AssignVariableOp(resource=accum_resource, value=accum)

result = tf.raw_ops.ResourceApplyProximalAdagrad(var=var_resource, accum=accum_resource, lr=lr, l1=l1, l2=l2, grad=grad)
```


### Relevant log output

```shell
2024-03-14 05:57:20.787563: F tensorflow/core/framework/tensor.cc:844] Check failed: dtype() == expected_dtype (1 vs. 2) double expected, got float
Aborted (core dumped)
```
Repository: ollama
Issue: LLava returns non-unique responses
Labels: bug

Dear Ollama,

I am using LLava with WebUI, and have already spoken to WebUi github about this, and as here is no errors in the docker error logs, they advised me to contact the Ollama team's Github.

When I type : Describe Image
LLava give me a cloned answer no matter the images I give it. The first image/response  (after a system reboot) will be unique, but all future request with new images will give the same exact answer, word for word/a clone response.


It would go off for a few minutes to think, and comeback with the prior text. Whether I use the LLava:7b or the LLava:34b
My graphics card is an AMD RX580 8GB (I understand it is on the low-end side), but nonetheless, I don't understand why it is giving a cloned answer.
Repository: PowerToys
Issue: PowerShell Microsoft.WinGet.Client module installation error
Labels: Issue-Bug,Product-CommandNotFound

### Microsoft PowerToys version

0.70

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Command not found

### Steps to reproduce

PowerShell Microsoft.WinGet.Client module installation error
I have manually installed PowerShell 7.4.1 through the [PowerShell Offcial github](https://github.com/PowerShell/PowerShell/releases/tag/v7.4.1) and [following the official instructions](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows?view=powershell-7.4) tightly there.
![image](https://github.com/microsoft/PowerToys/assets/37266092/bfd0bc50-f633-4c6c-95d3-d28e74e97fdb)

And PowerToys also detected it.
![image](https://github.com/microsoft/PowerToys/assets/37266092/f53aaac0-7866-44a8-8f5b-714a006f492a)

But, there is something wrong with the installation of [PowerShell Microsoft.WinGet.Client module](https://www.powershellgallery.com/packages/Microsoft.WinGet.Client/1.7.10661) It always throw exceptions when I install the module. Here lists my steps.
![image](https://github.com/microsoft/PowerToys/assets/37266092/18f145b1-f3c6-4858-a426-60d42c47a350)
![image](https://github.com/microsoft/PowerToys/assets/37266092/8256912e-fa35-4eed-ad77-2a4188a788b6)
![image](https://github.com/microsoft/PowerToys/assets/37266092/42362d94-abbc-4b9c-a7bf-7b90e32cc9de)

Then, the windows went out immediately with log of powertoys output the exception messages. The messages are saved into the attachment file named "exception.txt".
[exception.txt](https://github.com/microsoft/PowerToys/files/14598712/exception.txt)


I also tried installing winget by command in another powershell window. Unfortunally, failed. The reason is the same exceptions.
![image](https://github.com/microsoft/PowerToys/assets/37266092/5083be81-608f-4b6d-8de6-531d31482e40)
![image](https://github.com/microsoft/PowerToys/assets/37266092/aef4c649-3474-4e12-9a8a-8bf1ac8a4c3e)
![image](https://github.com/microsoft/PowerToys/assets/37266092/556a43c0-63b3-40d6-bfc7-bd5a725928c2)


What I don't understand is why are there errors? The official documentation says that powershell with v6.0+ comes with nuget module. So, why when installing winget module, powershell also prompts me to install nuget? I have no idea for it. Eagering for help.

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: TypeScript
Issue: Inconsistent quick info when hovering over `=>` between value and type space
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

quick info function arrow value type empty

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.5.0-dev.20240314#code/MYewdgzgLgBAbgQwDYFcCmMC8MAUBKLAPhgG8BfAKAqgE8AHDAFXo23yPhAEsATIA

### 💻 Code

```ts
const value = () => {}

type Type = () => void
```


### 🙁 Actual behavior

When hovering in value space we can see:
> function(): void

When hovering in the type space we can see an empty string

### 🙂 Expected behavior

I'd expect this empty string to not be displayed (you can see an empty quick info in the playground, VS Code doesn't display it). 

Since the value-space `=>` displays the function type, I'd probably expect the same experience in the type-space

### Additional information about the issue

_No response_
Repository: node
Issue: net.autoSelectFamilyAttemptTimeoutDefault should not be constant
Labels: net,feature request

### What is the problem this feature will solve?

I have slow Internet connection and when a domain with multiple ip appears, I always get ETIMEDOUT because the connection can not be established in default `autoSelectFamilyAttemptTimeoutDefault=250ms`. There are a lot of npm packages that use node:net, and it'not possible to wait until all of them implement a mechanism to deal with `autoSelectFamilyAttemptTimeout`.

### What is the feature you are proposing to solve the problem?

I believe it should be fixed by setting `autoSelectFamilyAttemptTimeoutDefault` in `NODE_OPTIONS`

### What alternatives have you considered?

Now, it's possible to change this parameter by calling `net.setDefaultAutoSelectFamilyAttemptTimeout`, but I can call it only in my own code, but not from other applications (e.g. yarn), so it won't help in most cases.
Alternatively, you can just increase the default parameter, but it is not flexible solution.
Repository: PowerToys
Issue: Feat: Create/Open A Sticky Note Directly from power run
Labels: Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

I often rely on sticky notes to keep track of important information. However, a recurring issue I encounter is the need to consistently right-click on the sticky notes icon to reveal all notes and then select the specific one I want to open.

It would be incredibly convenient if I could simply type the title of the sticky note into PowerToy Run to open it directly. This feature would greatly streamline my workflow.

### Scenario when this would be used?

Quickly adding and retrieving a note just by title from power run

### Supporting information

_No response_
Repository: godot
Issue: Godot 4.2(Sharp) , Custom MainLoop,Flickering occurs after startup
Labels: bug,topic:rendering,needs testing

### Tested versions

v4.2.1.stable.mono.official [b09f793f5]

### System information

Vulkan API 1.3.242 - Forward+ - Using Vulkan Device #0: NVIDIA - NVIDIA GeForce RTX 2060

### Issue description

When I define my own MainLoop type.
The window screen flickers between the black background and the Godot startup screen.
I don't know if this is a bug or if it is "reasonable". Because of this phenomenon, I suspect that my MainLoop is missing some necessary code?
![bug_0](https://github.com/godotengine/godot/assets/29698949/76897c94-4c00-4129-8143-84d1044fa166)
![bug_1](https://github.com/godotengine/godot/assets/29698949/e4cac5cc-b1c9-4e1b-b22c-2b27bc63a00b)


### Steps to reproduce

1. Create a forward+ or Mobile project
2. Create a custom MainLoop derived class
3. Modify the "MainLoop type" project settings
4. Create a main scene (the root node is Node)
5. Start the program
6. The window screen flickers between the black background and the Godot startup screen.
7. When rewriting _Initialize in CustomMainLoop, write the following code:
     DisplayServer.WindowSetSize( DisplayServer.WindowGetSize());
     (I can't find a way to get a reference to the MainWindow object)
8. Start the program again, and the flickering will disappear and turn into a stable black background.
9.I tried other codes:
     DisplayServer.WindowSetPosition( DisplayServer.WindowGetPOsition());
     This code will not cause the flicker to disappear.

### Minimal reproduction project (MRP)

N/A
Repository: deno
Issue: Any perf optimization possible for `uponPromise` in `deno_web/06_streams.js`?
Labels: perf,question,needs investigation

```
$ deno --version
deno 1.41.2 (release, x86_64-unknown-linux-gnu)
v8 12.1.285.27
typescript 5.3.3
```

I'm not sure if this is something more toward the V8 side of things (i.e. something for crbug rather than this repo), so please close if that's the case. I'm using streams like `response.body.pipeThrough(new TextDecoderStream()).getReader()` and async iterators/generators on one of my servers (to handle event streams / server-sent events), and I'm currently trying to clear out some bottlenecks to delay my eventual move to a Worker/multi-process setup, and this function is currently taking up a very sizable portion of CPU, it seems:

![image](https://github.com/denoland/deno/assets/1167575/482fdd89-9b66-4ee7-9b2a-6a8a016b17f8)


![image](https://github.com/denoland/deno/assets/1167575/7c9aa458-e28b-4cf1-abce-c7a2a3aede89)

Wondering if there are any obvious optimizations that can be done in `deno_web/06_streams.js` (or at a lower level in Deno core code) to speed up use of streams and iterators?
Repository: storybook
Issue: Build: Re-enable Storybook in Vite Ecosystem CI
Labels: bug,builder-vite,build

### Describe the bug

Once upon a time, Storybook was part of https://github.com/vitejs/vite-ecosystem-ci. At some point it broke, and was removed. Now every time Vite makes a change, maintainers don't know whether they've broken Storybook.

There is a draft PR to re-enable it: https://github.com/vitejs/vite-ecosystem-ci/pull/137. We should pick that up and take it over the line, or start again if that's easier.

## Update 30 July 2024

The initial [PR](https://github.com/vitejs/vite-ecosystem-ci/pull/137) got superseded by https://github.com/vitejs/vite-ecosystem-ci/pull/311 where we provided `scripts` for the vite-ecosystem CI inside of our monorepository. The problem is that our scripts depend on `esbuild-register,` which currently has a bug preventing us from continuing our second attempt at integrating Storybook into the Vite Ecosystem CI.

To circumvent the `esbuild-register` solution, we planned to continue @ndelangen work to move away from `esbuild-register` and to use bun instead, which is already used for some tasks. This [PR](https://github.com/storybookjs/storybook/pull/28046) tries to do the migration. 

Even after multiple attempts, we could not migrate fully to Bun at the moment. Bun has some different behaviors from Node.js. For example, we had huge issues to make `

### Third attempt

Instead of trying to integrate Storybook into Vite's Ecosystem CI via our [sandboxes repo](https://github.com/storybookjs/sandboxes) (first attempt) or by integrating Storybook by using our mono repository (second attempt), we want to initialize a fresh repository exclusively for Vite's Ecosystem CI. We want to modify our daily sandbox publishing script to release a `react-vite` sandbox into a separate repository. The `package.json` of this repo will provide scripts for Vite's ecosystem CI to install dependencies and to run the `test-runner` to execute tests.

The scripts we will provide will be the following:
- `vite-ecosystem-ci:test`: Running the `@storybook/test-runner`
Repository: PowerToys
Issue: queue and execute powertoys.Runner <enter> input 
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

I remember using some other apps like powertoys Runner ( macOS spotlight or krunner on kde or others). Some of them seem to be able to queue input of `<enter>` so that when I input some words to search and hit `<enter>` *before* the search result is shown visually. It would correctly execute the first search result afterwards. Now with powertoys if I hit  `<enter>`  before the search result is shown it would have no effect.

### Scenario when this would be used?

This could be used if you are very familiar with search results of keywords and you can access the result faster. The keywords and enter almost can be as fast as a pre defined keyboard shortcut. But the current behavior that you have to visually see the search result and then `<enter>` is effective is slower.

### Supporting information

_No response_
Repository: godot
Issue: Couldn't form plane from brush A face, (I believe there's a error that say's B instead at times.)
Labels: bug,needs testing,topic:3d

### Tested versions

4.2.Stable
4.3-Dev4

### System information

Windows 11 - 4.2 Stable - Vulkan (Forward+)

### Issue description

Can anyone help me debug why godot gives me these errors when i add a csgnode to a pre existing hierarchy?

![image-41](https://github.com/godotengine/godot/assets/29516927/a5b603bb-5b91-434f-adf6-9090099b6055)
![SPOILER_image-1](https://github.com/godotengine/godot/assets/29516927/219daec1-fb86-43c5-9673-455a71a7e8bc)
![SPOILER_image](https://github.com/godotengine/godot/assets/29516927/c3b11577-9fb4-4814-9463-5a5b4add5836)
![image-32](https://github.com/godotengine/godot/assets/29516927/2de5f4f3-067a-41e8-b278-b7d9e95beaa2)

### Steps to reproduce

1. Drop a csg combiner node on the node3d of your scene.
2. Drop a csgmesh using union and scale it up.
3. Drop another mesh using the subtraction setting, And push them into each other while making a house like this.
4. (Something I did that wasn't included) I used a triangle mesh.

### Minimal reproduction project (MRP)

[MininmalReproductionHouse.zip](https://github.com/godotengine/godot/files/14608139/MininmalReproductionHouse.zip)
Repository: storybook
Issue: [Bug]: Integrating Storybook Coverage Reports with Sonarcloud
Labels: bug,compatibility with other tools,test-runner,sev:S3

### Describe the bug

Storybook is currently being configured to generate coverage reports, which are passed to Sonarcloud.

The lcov report generated from coverage-storybook.json suggests this stories file has 100% coverage. However, on closer inspection only a select few lines of code are being picked up to test coverage against (ie. this file has 41 lines of code, but only 4 are picked up, and the coverage report returns 4/4 lines covered / 100% coverage).

![image](https://github.com/storybookjs/storybook/assets/89777779/44a514e2-88a3-4f5e-9392-3b3f00246d1b)
![image](https://github.com/storybookjs/storybook/assets/89777779/ffc0da73-3b6a-43a5-8315-83019c1c4736)

The issue lies in the integration of this report with Sonarcloud, which reports the uncovered lines, resulting in a failing quality gate.

![image](https://github.com/storybookjs/storybook/assets/89777779/79040c2b-f10d-4eaa-8de7-15397a30149c)

I have yet to find a way to configure the report to increase the number of covered lines. Is there a workaround for this?

### To Reproduce

Generating coverage report:
test-storybook --coverage && npx nyc report --reporter=lcov -t coverage/storybook --report-dir coverage/storybook

### Additional context

Dev dependencies
    "@storybook/addon-a11y": "^7.6.16",
    "@storybook/addon-essentials": "^7.6.9",
    "@storybook/addon-interactions": "^7.6.9",
    "@storybook/addon-links": "^7.6.9",
    "@storybook/blocks": "^7.6.9",
    "@storybook/test": "^7.6.9",
    "@storybook/test-runner": "^0.16.0",
    "@storybook/vue3": "^7.6.9",
    "@storybook/vue3-vite": "^7.6.9",
    "storybook": "^7.6.9",
Repository: rust
Issue: Improve the "monomorphization backtrace" for const-eval errors
Labels: A-diagnostics,T-compiler,A-const-eval

When a const fails to evaluate, if there are generics involved it can be crucial to know where and how the const got instantiated to understand the error. For this purpose `interpret::ErrorHandled` has the `emit_note` function that marks the point in the code where an erroneous constant is encountered.

However, this could be done better:
- For promoteds and inline consts, the const is defined right where it is used, so the extra note makes little sense and should probably be suppressed.
- The monomorphization collector prints similar errors related to instantiation of generic functions as "the above error was encountered while instantiating this function". It plays some tricks with the error count to ensure this is only emitted right after an actual error. We could do something similar. That would lead to less duplication of "erroneous constant used here" messages, but it means if the first evaluation of a constant is without a decent span, we'll never get the note. That may be an okay trade-off? Currently GVN evaluates constants without a decent span, but maybe that should just be fixed. (It's not trivial since GVN has its own representation for consts that doesn't hold the span -- and probably it shouldn't hold a span, probably the error should be emitted before turning a const operand into that representation.)

Fixing this will require refactoring a bit how this note is emitted; currently `emit_note` has no idea which constant it is that failed and it can't compare old and new error counts to determine if the error would be right "above".
Repository: godot
Issue: WARNING: Failed to CreateInstance in ICD 1
Labels: bug,topic:rendering,needs testing

### Tested versions

Reproduced with:
- v4.3.dev.custom_build [da945ce62]
- v4.2.stable.custom_build [74f69f7ed]

### System information

Godot v4.2.stable (74f69f7ed) - Ubuntu 22.04.4 LTS 22.04 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1070 (nvidia; 525.147.05) - Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 Threads)

### Issue description

I always get this warning at editor startup when a project is loaded. It appeared some weeks ago although I didn't update Godot 4.2 until today to test 4.3. I do regularly system updates when they are available. The warning is:

`WARNING: GENERAL - Message Id Number: 0 | Message Id Name: Loader Message
	terminator_CreateInstance: Failed to CreateInstance in ICD 1.  Skipping ICD.
	Objects - 1
		Object[0] - VK_OBJECT_TYPE_INSTANCE, Handle 94478350734896
     at: _debug_messenger_callback (drivers/vulkan/vulkan_context.cpp:264)`

Despite the presence of this warning the editor and my 3D project using forward+ works fine.

### Steps to reproduce

Load any project with forward+ and watch the logs

### Minimal reproduction project (MRP)

NA I guess
Repository: godot
Issue: Automatic build profile generation disables `MainLoop` class
Labels: bug,topic:editor,needs testing

### Tested versions

Reproducible in: [4.3-dev-4](https://github.com/godotengine/godot/commit/df78c0636d79c9545a283e0e2a926d623998cc27), [4.2 branch](https://github.com/godotengine/godot/issues/2a8c429fcc19b042aaf43a51060c571d42ca2e39), [4.2.1-sable](https://github.com/godotengine/godot/tree/4.2.1-stable)

### System information

Godot v4.2.1.stable - Debian GNU/Linux testing (gcc12) - Wayland - GLES3 (Compatibility)

### Issue description

Automatic build profile generation disables `MainLoop` class without which I get an error which isn't printed into the terminal but is showed in new floating window:

![screen-1710413598](https://github.com/godotengine/godot/assets/97330399/a6b4ff15-4b0b-4e2e-8518-1ae2d4b3430e)

It looks like `MainLoop` is one of the essential classes and engine can't work without it

### Steps to reproduce

1. Create a new project
2. Crete one scene (maybe not necessary)
3. `Project->Customize Engine Build Configuration...->Detect from Project`
4. `Save As`
5. Open the saved profile with editor and search for `MainLoop` inside `disabled_classes`

### Minimal reproduction project (MRP)

N/A