sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: http2.connect() doesn't support self-signed cert in `ca` field
Labels: bug,node compat

```
deno 1.42.4 (release, aarch64-apple-darwin)
v8 12.3.219.9
typescript 5.4.3
```
Bug
```
➜  http2 deno run -A client.mjs 
Error: invalid peer certificate: Other(CaUsedAsEndEntity)
    at async node:http2:279:11
error: Uncaught (in promise) Error: invalid peer certificate: Other(CaUsedAsEndEntity)
    at async node:http2:569:24
```
To reproduce the bug, you can follow the instructions from https://nodejs.org/api/http2.html#server-side-example. I'm pasting code converted to ES modules for convenience:
1. generate certs using the following command:
```
openssl req -x509 -newkey rsa:2048 -nodes -sha256 -subj '/CN=localhost' \
  -keyout localhost-privkey.pem -out localhost-cert.pem
```
2. create server.mjs
```js
import { createSecureServer } from 'node:http2';
import { readFileSync } from 'node:fs';

const server = createSecureServer({
  key: readFileSync('localhost-privkey.pem'),
  cert: readFileSync('localhost-cert.pem'),
});
server.on('error', (err) => console.error(err));

server.on('stream', (stream, headers) => {
  // stream is a Duplex
  stream.respond({
    'content-type': 'text/html; charset=utf-8',
    ':status': 200,
  });
  stream.end('<h1>Hello World</h1>');
});

server.listen(8443);
```
3. create client.js
```js
import { connect } from 'node:http2';
import { readFileSync } from 'node:fs';

const client = connect('https://localhost:8443', {
  ca: readFileSync('localhost-cert.pem'),
});
client.on('error', (err) => console.error(err));

const req = client.request({ ':path': '/' });

req.on('response', (headers, flags) => {
  for (const name in headers) {
    console.log(`${name}: ${headers[name]}`);
  }
});

req.setEncoding('utf8');
let data = '';
req.on('data', (chunk) => { data += chunk; });
req.on('end', () => {
  console.log(`\n${data}`);
  client.close();
});
req.end();
```

Run the below command to test nodejs
```
➜  http2 node server.mjs & node client.mjs
[1] 5576
:status: 200
content-type: text/html; charset=utf-8
date: Mon, 22 Apr 2024 01:36:06 GMT

<h1>Hello World</h1>
```

Then run the below command to test deno (assuming that you didn't kill the server)
```
➜  http2 deno run -A client.mjs 
Error: invalid peer certificate: Other(CaUsedAsEndEntity)
    at async node:http2:279:11
error: Uncaught (in promise) Error: invalid peer certificate: Other(CaUsedAsEndEntity)
    at async node:http2:569:24
```
Repository: godot
Issue: Godot mass file importing issues if project files are being synced with Google Drive
Labels: discussion,topic:editor,topic:thirdparty,needs testing

### Tested versions

- Reproducible in v4.2.1-stable and v4.3-dev5

### System information

Godot v4.2.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 Ti (NVIDIA; 31.0.15.5222) - AMD Ryzen 9 3900X 12-Core Processor (24 Threads)

### Issue description

When a Godot project has many images (in my case, I had ~1600) and it is being synced by Google Drive (on the G drive), Godot will open a blank project and not import anything, as well as crash if you try to close it. While the project is open and you remove the folder with all the images, Godot will instantly work again. Also moving your project to one of your local drives and re-importing will resolve issue.

### Steps to reproduce

1.) Create a Godot project on the Google Drive drive
2.) Via File Explorer, drag in your folder with a lot of images (mine had ~1600)
3.) Tab into Godot, nothing will happen. Try to close, it will crash. Reopen it, it will open blank project and not work

### Minimal reproduction project (MRP)

Due to the nature of this issue, I cant upload to Git due to going above 25mb. Below is a project that is bare bones with nothing except the images:
https://drive.google.com/file/d/1EH1P05vsax9YvFN2qkPmOV9569L3TZDU/view?usp=sharing
Repository: tensorflow
Issue: Denial of Service in tf.raw_ops.Unstage
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.16

### Issue type

Bug

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

No

### Source

source

### TensorFlow version

tf 2.16.1

### 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

12.0

### GPU model and memory

_No response_

### Current behavior?

Hi,
When using `tf.raw_ops.Unstage`, a `Denial of Service` was encountered under normal invocation, with all passed parameters meeting the requirements of the API documentation.
After a long wait, there was still no response.

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

tensor = tf.constant([1.0, 2.0, 3.0])
stage_op = tf.raw_ops.Stage(values=[tensor])
print(tensor.dtype)  # <dtype: 'float32'>

unstage_op = tf.raw_ops.Unstage(dtypes=[tensor.dtype])  # Hang

with tf.compat.v1.Session() as sess:
    print("here")
    sess.run(stage_op)
    result = sess.run(unstage_op)

print(result)  # Expected output: [1. 2. 3.]
```


### Relevant log output

```shell
2024-04-22 02:23:12.166249: I tensorflow/core/util/port.cc:113] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2024-04-22 02:23:12.166825: I external/local_tsl/tsl/cuda/cudart_stub.cc:32] Could not find cuda drivers on your machine, GPU will not be used.
2024-04-22 02:23:12.169923: I external/local_tsl/tsl/cuda/cudart_stub.cc:32] Could not find cuda drivers on your machine, GPU will not be used.
2024-04-22 02:23:12.215234: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 AVX512F AVX512_VNNI FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-04-22 02:23:13.066132: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
2024-04-22 02:23:13.789282: W tensorflow/core/common_runtime/gpu/gpu_device.cc:2251] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
Skipping registering GPU devices...
<dtype: 'float32'>
```
Repository: ui
Issue: [bug]: slow performance with array list form after validation
Labels: bug

### Describe the bug

slow performance with array list form after validation,
it seems to trigger all input filed after call validation even if you change 1 field value.

### Affected component/components

FormField

### How to reproduce

1. https://ui.shadcn.com/docs/components/form
2. create array list of the form

### 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: godot
Issue: move_and_slide can not set delta
Labels: discussion,topic:physics,needs testing

### Tested versions

godot 4.2

### System information

win10 fps30,physics pre frame 30.

### Issue description

1.move_and_slide can not set delta.so how a server mode program to move for special delta.the move and colide has some bug on 3d(like not set is_on_floor, slide not stop, and so more).
2.when charcaterbody3d near the wall.move and slide slow the fps very much.(30->1).and it preform 30fps if not near wall

as server mode.the best way is,in a timer to delta call process and physicsprocess.
different world3d may use different starttime to avoid same time busy.
but some function like move_and_slide.animation tree.trainsition request and so on, use the next process or the next engine delta.it is uncontrolable

### Steps to reproduce

move_and_slide can not set delta.so how a server mode program to move for special delta.the move and colide has some bug on 3d.

### Minimal reproduction project (MRP)

move_and_slide can not set delta.so how a server mode program to move for special delta.the move and colide has some bug on 3d.
Repository: ui
Issue: [bug]:  files constantly change 
Labels: bug

### Describe the bug

.gz and webpack files constantly change when adding a new component or writing a page

### Affected component/components

Button, Command

### How to reproduce

when i add a component with npm immediately files are changing
<img width="347" alt="image" src="https://github.com/shadcn-ui/ui/assets/9107178/bcb9ba51-420b-446c-8203-4d5b33e112c0">

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
edge, macos
```


### Before submitting

- [x] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ollama
Issue: Error: Models based on 'Qwen2ForCausalLM' are not yet supported
Labels: bug

### What is the issue?

When I ran a this command:- ollama create qwen-14b-quant -f /home/vidyasagar/rr/ModelFile.txt

the text file consists of:-
FROM /home/user/rr/quantized_14_b_awq

TEMPLATE """{{ if .System }}
system
{{ .System }}
{{ end }}
user
{{ .Prompt }}


assistant
"""

SYSTEM """"""

PARAMETER stop 

PARAMETER stop 



This is the terminal output:-
transferring model data 
unpacking model metadata 
Error: Models based on 'Qwen2ForCausalLM' are not yet supported


But I see there are the Qwen 1.5 supported models, Then why mine is not working?
can someone explain this? am I doing anything wrong?





### OS

Linux

### GPU

Nvidia

### CPU

AMD

### Ollama version

0.1.32
Repository: storybook
Issue: [Bug]: `csf-plugin` fails to read stories with names not matching hardcoded regex
Labels: bug,has workaround,sev:S3

### Describe the bug

If a user change `stories` option from `main.ts` config(https://storybook.js.org/docs/api/main-config-stories), the `addon-docs` can't detect the stories file anymore because `csf-plugin` assumes CSF file should match with the pattern which is hardcoded, means there is no way to configure it from outside.

https://github.com/storybookjs/storybook/blob/479b8e919fccf12d3def4470d455682bb3965c45/code/lib/csf-plugin/src/index.ts#L9

### To Reproduce

To reproduce, I simply added custom CSF patterns to `main.ts`.

```ts
const config: StorybookConfig = {
  // ...
  stories: ["../src/**/*.mdx", "../src/**/*.stories.@(js|jsx|mjs|ts|tsx)", "../src/**/*.custom-stories.@(js|jsx|mjs|ts|tsx)"],
  // ...
};
```

You can find reproduction code at here: https://github.com/abiriadev/sb-csf-plugin-regex

As a short summary, the JSDoc comment inside `*.custom-stories.ts` does not render, while the same comment inside `*.stories.ts` renders without any issue.

![image](https://github.com/abiriadev/sb-csf-plugin-regex/assets/72962900/494d538f-97fa-49d6-92d9-3482d37e3161)

There is also Stackblitz URL for the same code: 
https://stackblitz.com/github/storybookjs/sandboxes/tree/next/react-vite/default-ts/after-storybook?file=.storybook%2Fmain.ts

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 6.8 Arch Linux
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
    Shell: 3.7.1 - /bin/fish
  Binaries:
    Node: 20.6.1 - /run/user/1000/fnm_multishells/123756_1713749574530/bin/node
    Yarn: 1.22.22 - /run/user/1000/fnm_multishells/123756_1713749574530/bin/yarn <----- active
    npm: 9.8.1 - /run/user/1000/fnm_multishells/123756_1713749574530/bin/npm
    pnpm: 8.10.2 - ~/.local/share/pnpm/pnpm
  npmPackages:
    @storybook/addon-docs: ^8.0.8 => 8.0.8
    @storybook/addon-essentials: ^8.0.8 => 8.0.8
    @storybook/addon-interactions: ^8.0.8 => 8.0.8
    @storybook/addon-links: ^8.0.8 => 8.0.8
    @storybook/addon-onboarding: ^8.0.8 => 8.0.8
    @storybook/blocks: ^8.0.8 => 8.0.8
    @storybook/react: ^8.0.8 => 8.0.8
    @storybook/react-vite: ^8.0.8 => 8.0.8
    @storybook/test: ^8.0.8 => 8.0.8
    eslint-plugin-storybook: ^0.8.0 => 0.8.0
    storybook: ^8.0.8 => 8.0.8
    storybook-addon-remix-react-router: ^3.0.0 => 3.0.0
```


### Additional context

A quickfix I can currently come up with is, to add `stories` field to `EnrichCsfOptions` type and use that value instead of `STORIES_REGEX` (or use `STORIES_REGEX` as a fallback).

https://github.com/storybookjs/storybook/blob/479b8e919fccf12d3def4470d455682bb3965c45/code/lib/csf-tools/src/enrichCsf.ts#L7-L10

https://github.com/storybookjs/storybook/blob/479b8e919fccf12d3def4470d455682bb3965c45/code/lib/csf-plugin/src/index.ts#L16-L18

But it would be ideal for `addon-docs` to automatically extract `stories` field from `main.ts`, since `@storybook/addon-essentials` should work with zero-config.
Repository: kubernetes
Issue: Provide Zip archive for downloads of Windows binaries
Labels: kind/feature,area/release-eng,help wanted,sig/release,triage/accepted

Windows download link should be provided with zip file. Most of the organization restrict exe download.
Repository: transformers
Issue: Update `make-fixup` to make sure image processor tests present
Labels: Core: Modeling,Feature request

### Feature request

Update `make-fixup` to make sure image processor tests present

See [this comment](https://github.com/huggingface/transformers/pull/30136#issuecomment-2068884321)



### Motivation

Make `make-fixup` more robust

### Your contribution

I can work on it
Repository: go
Issue: proposal: sync/atomic: Add Chan atomic channel
Labels: Proposal

### Proposal Details

Add a generic Chan type, analog to other types:

```go
// A Chan is an atomic channel of type chan T. The zero value is a nil channel.
type Chan[T any] struct {
	/// ...
}

// Load atomically loads and returns the value stored in c.
func (c *Chan[T]) Load() chan T

// Store atomically stores ch into c.
func (c *Chan[T]) Store(ch chan T)

// Swap atomically stores new into c and returns the previous value.
func (c *Chan[T]) Swap(new chan T) (old chan T)

// CompareAndSwap executes the compare-and-swap operation for c.
func (c *Chan[T]) CompareAndSwap(old, new chan T) (swapped bool) 
```

Sample implementation in [fillmore-labs.com/lazydone/atomic](https://pkg.go.dev/fillmore-labs.com/lazydone@v0.0.1/atomic).

### Motivation

Go has a “[zero-value-is-useful](https://go.dev/doc/effective_go#data)” mindset, but structures containing channels need to initialize them lazily. It is a [well-known problem](https://github.com/golang/go/issues/28366) for struct types to require non-nil channels. If you do not want to go through a mutex every time a channel is accessed (also, the mutex increases the structure size), candidates are [`atomic.Value`](https://pkg.go.dev/sync/atomic#Value) or [`atomic.Pointer`](https://pkg.go.dev/sync/atomic#Pointer).

The first approach [is used](https://github.com/golang/go/blob/go1.22.2/src/context/context.go#L425) by [context.WithCancel](https://pkg.go.dev/context#WithCancel) and [requires casting](https://github.com/golang/go/blob/go1.22.2/src/context/context.go#L550-L555):
```go
	d, _ := c.done.Load().(chan struct{})
	if d == nil {
		c.done.Store(closedchan)
	} else {
		close(d)
	}
```

The second approach by [`lazydone.SafeLazy`](https://pkg.go.dev/fillmore-labs.com/lazydone#SafeLazy) requires [some pointer arithmetic](https://github.com/fillmore-labs/lazydone/blob/v0.0.1/pointer.go#L32-L34):
```go
	if ch := l.done.Swap(&closedChan); ch != nil && ch != &closedChan {
		close(*ch)
	}
```


Internally, a Go channel [is a pointer to a `hchan`](https://github.com/golang/go/blob/go1.22.2/src/runtime/chan.go#L72) structure. So, the second approach uses a pointer to a pointer, which is wasteful.

A channel (`*hchan`) can be cast [from](https://github.com/fillmore-labs/lazydone/blob/v0.0.1/atomic/chan.go#L57) and [to](https://github.com/fillmore-labs/lazydone/blob/v0.0.1/atomic/chan.go#L52) an [unsafe.Pointer](https://pkg.go.dev/unsafe#Pointer) with:

```go
	var ch chan T
	var ptr unsafe.Pointer
	ch = *(*chan T)(unsafe.Pointer(&ptr))
	ptr = *(*unsafe.Pointer)(unsafe.Pointer(&ch))
```

But nothing in the Go specification guarantees this.
Repository: PowerToys
Issue: File Explorer File Preview Awesome but very slow to start - add in background thread
Labels: Issue-Bug,Product-File Explorer,Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

The File Explorer File Preview is awesome and very useful, but it prevents me from using the File Explorer effectively. With it it is difficult to select files and delete them. Sometimes I even delete the wrong file because of it, because there is lag in the selecting. Can it not run on a background thread and show the preview when done leaving me to operate normally in the foreground thread.

### Scenario when this would be used?

When selecting and deleting/copying files

### Supporting information

_No response_
Repository: pytorch
Issue: DISABLED test_causal_mask_float32 (__main__.TestTemplatedSDPA)
Labels: triaged,module: flaky-tests,skipped,module: inductor

Platforms: linux, slow

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_causal_mask_float32&suite=TestTemplatedSDPA&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/24086275793).

Over the past 3 hours, it has been determined flaky in 2 workflow(s) with 2 failures and 2 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_causal_mask_float32`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `inductor/test_templated_attention.py`

cc @clee2000 @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang
Repository: tensorflow
Issue:  Repository '@python' is not defined
Labels: stat:awaiting tensorflower,type:build/install,subtype: ubuntu/linux,TF 2.16

### Issue type

Build/Install

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

No

### Source

source

### TensorFlow version

2.16.1

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 22.04.1

### Mobile device

_No response_

### Python version

3.10.12

### Bazel version

5.4.1

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

while building a tool with tensorflow v2.16.1, it gives build error as "The repository '@python' could not be resolved: Repository '@python' is not defined."


### Standalone code to reproduce the issue

```shell
It seems issue is due to Hermatic Python from tensroflow 2.14.0 onwards. 
This commit creates the issue - https://github.com/tensorflow/tensorflow/commit/e85860e8382a460a0dd8547a536e5eaaf9096a9f

Reproduction env - TBD
```


### Relevant log output

```shell
ERROR: /home/ronn/ronn_wrapper/BUILD:34:11: While resolving toolchains for target //ronn/ronn_wrapper:ronn_wrapper: invalid registered toolchain '@local_execution_config_python//:py_toolchain': error loading package '@local_execution_config_python//': Unable to find package for @python//:defs.bzl: The repository '@python' could not be resolved: Repository '@python' is not defined.
ERROR: Analysis of target '//ronn/ronn_wrapper:ronn_wrapper' failed; build aborted:
INFO: Elapsed time: 3.515s
```
Repository: TypeScript
Issue: Document link for reference types and path
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

In js, we can have

```
/// <reference types="tree-sitter-cli/dsl" />
// or
/// <reference path="node_modules/tree-sitter-cli/dsl.d.ts" />
/// <reference types="@types/firefox-webext-browser" />
```

Can we have a document link for `file://$PWD/node_modules/tree-sitter-cli/dsl.d.ts` and `file://$PWD/node_modules/@types/firefox-webext-browser/index.d.ts`?

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

Add document link for LSP

### 📃 Motivating Example

Easier to jump the path by document link

And maybe we can have completion for `/// <reference types="|" />`, where `|` is cursor.

### 💻 Use Cases

1. What do you want to use this for?
2. What shortcomings exist with current approaches?
3. What workarounds are you using in the meantime?
Repository: next.js
Issue: /manifest.webmanifest not cached by browser and reloaded on every page transition
Labels: bug,Metadata

### Link to the code that reproduces this issue

https://github.com/cbratschi/nextjs-issues/tree/manifest

### To Reproduce

1. npm run dev
2. navigate between pages
3. manifest.webmanifest is loaded on every page

### Current vs. Expected behavior

Ideally a hash would be added to the manifest URL (current first):

```HTML
<link rel="manifest" href="/manifest.webmanifest">
<link rel="manifest" href="/manifest.webmanifest?hash">
```
This allows using immutable versions of the manifest.

In addition the cache-control value should be modified (current first):

```
public, max-age=0, must-revalidate
public, max-age=31536000, immutable
```

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:37 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6031
  Available memory (MB): 65536
  Available CPU cores: 16
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.2.2 // Latest available version is detected (14.2.2).
  eslint-config-next: 14.2.2
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Metadata

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

I tried to set cache-control in next.config.js to get at least a max-age of one hour but ended with two cache-control headers being returned:

```JavaScript
    async headers() {
        return [{
            //cache the manifest file (default: public, max-age=0, must-revalidate)
            //FIXME output contains now two header (ours is the first one)
            headers: [{
                key: 'cache-control',
                value: 'public, max-age=3600'
            }],

            source: '/manifest.webmanifest'
        }];
```