sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tensorflow
Issue: Tensorflow-Quantum Module Import Error
Labels: stat:awaiting tensorflower,type:build/install,subtype: ubuntu/linux,TF 2.11

<details><summary>Click to expand!</summary> 
 
 ### Issue Type

Bug

### Have you reproduced the bug with TF nightly?

Yes

### Source

source

### Tensorflow Version

v2.11.0-0-gd5b57ca93e5 2.11.0

### Custom Code

Yes

### OS Platform and Distribution

Ubuntu 20.04.5 LTS

### Mobile device

_No response_

### Python version

3.8

### Bazel version

5.3.0

### GCC/Compiler version

gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0

### CUDA/cuDNN version

Build cuda_11.8.r11.8/compiler.31833905_0

### GPU model and memory

A100 high-mem node

### Current Behaviour?

Still trying to get TFQ to work post-py 3.10 upgrade in colab ... the TF/TFQ nightly_build route seems to be getting me closer as I no longer receive "Module Not Found" when I try importing TFQ, however, I now receive the pauli error below.

### Standalone code to reproduce the issue

```shell
import tensorflow_quantum as tfq

---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-80-0f5757594a36> in <cell line: 1>()
----> 1 import tensorflow_quantum as tfq

4 frames
/content/quantum/quantum/tensorflow_quantum/core/ops/cirq_ops.py in <module>
     23 
     24 from tensorflow_quantum.core.ops import batch_util
---> 25 from tensorflow_quantum.core.proto import pauli_sum_pb2
     26 from tensorflow_quantum.core.proto import program_pb2
     27 from tensorflow_quantum.core.serialize import serializer

ImportError: cannot import name 'pauli_sum_pb2' from 'tensorflow_quantum.core.proto' (/content/quantum/quantum/tensorflow_quantum/core/proto/__init__.py)
```


### Relevant log output

```shell
See above

FYI ... the compile from nightly takes >8 hours so getting you info may take +1 days turn around
Also, I have tried nightly_builds (for my Colab env) for several days and this is the only build where I have obtained a different error than "Module Not Found" upon attempting to import TFQ after installing the wheel.  

Are you guys trying to actually 'import tensorflow-quantum' after executing your quantum tests (./scripts/test_all.sh)? I ask because as far as I can tell, the import does not work even though the installation and smoke tests all complete successfully.

I have attempted every TF/TFQ install listed here:
https://www.tensorflow.org/quantum/install
and TFQ will not import any longer.

I cannot TFQ imported and functional ...
```
</details>
Repository: storybook
Issue: [Bug]: Angular i18n Incompatibility
Labels: bug,angular,needs triage

### Describe the bug

After adding [i18n](https://angular.io/guide/i18n-common-add-package) we will update the `angular.json` by introducing the required locales, and by that the command `ng run angular-app:storybook` will failed with this error

```
info => Using default Webpack5 setup
<i> [webpack-dev-middleware] wait until bundle finished
9% setup compilation build-angulard:\Projects\node_modules\webpack\lib\javascript\JavascriptModulesPlugin.js:151
                        throw new TypeError(
                              ^


TypeError: The 'compilation' argument must be an instance of Compilation
```

### To Reproduce

1. Create new Angular project with `ng new my-app`
2. Install Angular Localization by `ng add @angular/localize`
3. Head over to `angular.json` and add the required locales to build configuration.

```json
{
  "projects": {
    "my-app": {
      "i18n": {
        "locales": {
          "ar": "src/locale/messages.ar.xlf"
        },
        "sourceLocale": "en"
      },
      "architect": {
        "build": {
          "configurations": {
            "production": {
              "localize": true
            },
            "development": {
              "localize": [
                "en"
              ]
            }
          },
          "defaultConfiguration": "production"
        }
      }
    }
  }
}
```
4. Add storybook with `npx storybook@latest init`
5. Run the storybook with `npm run storybook`

### System

```shell
Environment Info:

  System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
  Binaries:
    Node: 18.12.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
    npm: 9.6.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (114.0.1823.43)
  npmPackages:
    @storybook/addon-essentials: 7.0.21 => 7.0.21
    @storybook/addon-interactions: 7.0.21 => 7.0.21
    @storybook/addon-links: 7.0.21 => 7.0.21
    @storybook/angular: 7.0.21 => 7.0.21
    @storybook/blocks: 7.0.21 => 7.0.21
    @storybook/testing-library: 0.0.14-next.2 => 0.0.14-next.2
```


### Additional context

- Quick fix was to introduce another build configuration for storybook with `localize: false`.

- Suggested fix would be to just update the init command to copy the development configuration and rename it to something like `storybook` and then use that configuration instead of default one.
Repository: stable-diffusion-webui
Issue: [Bug]: Bug with Settings--Defaults & Hires' UI
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

Though this is not a functional bug, I decide to raise it hoping it be fixed.

First, if you go to UI interface page and hide some cards in Hidden UI tabs, the Defaults page will not work anymore. I tried to delete all of my hidden UI tabs and it worked again and I can save my default settings as before.

Second, although the Hires. fix checkbox is checked in my t2i page, every time I launch SD WebUI, I cannot see the advanced options (Hires steps, denoising strenth, etc) and params on the page. I have to uncheck it and re-check it every time to get the Hires options displayed. I dont know if this is a bug or not, though.

### Steps to reproduce the problem

1. Go to .... Settings
2. Press .... Default
3. ... It doesn't work.


### What should have happened?

Saving default settings should be working even if some UI tags are hidden.

### Commit where the problem happens

https://github.com/AUTOMATIC1111/stable-diffusion-webui/commit/baf6946e06249c5af9851c60171692c44ef633e0

### What Python version are you running on ?

Python 3.10.x

### What platforms do you use to access the UI ?

Windows

### What device are you running WebUI on?

Nvidia GPUs (RTX 20 above)

### What browsers do you use to access the UI ?

Google Chrome

### Command Line Arguments

```Shell
--disable-nan-check --theme dark --opt-sdp-attention --autolaunch
```


### List of extensions

Config-Presets	a1111-sd-webui-tagcomplete	canvas-zoom	multidiffusion-upscaler-for-automatic1111	openpose-editor	sd-dynamic-prompts	sd-webui-additional-networks	sd-webui-controlnet	sd-webui-depth-lib	stable-diffusion-webui-state	ultimate-upscale-for-automatic1111

### Console logs

```Shell
Not found
```


### Additional information

_No response_
Repository: node
Issue: Closing filehandle after being used in a stream exits node without error message
Labels: fs

### Version

20.3.0

### Platform

Linux zuse1.efi.fh-nuernberg.de 5.4.17-2136.319.1.4.el8uek.x86_64 #2 SMP Mon Jun 5 13:39:13 PDT 2023 x86_64 x86_64 x86_64 GNU/Linux

### Subsystem

streams

### What steps will reproduce the bug?

I use a stream for writing into a filehandle (of a regular file). After closing the stream (not the filehandle!) I write to other positions in the file.
When I now close the file, node simply exists with return code 0. Following code is NOT executed.

```javascript
const fs_p     = require('node:fs').promises;
const fs       = require('node:fs');
const stream_p = require('node:stream').promises;

async function test() {
    // Create writeable filehandle
    var fh = await fs_p.open ('/tmp/ttt.txt', 'w', 0o644);

    // Create stream, use stream, end stream, wait for finish
    var st = fh.createWriteStream ({autoClose: false});
    st.on ('error', (e) => {throw e});
    // No need to test return value with this little data
    st.write ('this is a filehandle / stream test');
    st.end ();
    await stream_p.finished (st);

    // Continue using filehandle, write something a beginning of file
    await fh.write ("TEST", 0);

    // Close filehandle to flush data and reuse system ressources
    console.log ('pre-close');

    // It is supposed to work like that.
    // filehandle.close() returns a Promise that is fullfilled with undefined after closing.
    // However, node simply exits (return code 0). Following code is not executed
    await fh.close ();

    // Working alternative. But only fixes system ressources, not node ressources.
    // And it blocks.
    //   fs.closeSync (fh.fd);

    // Continue
    console.log ('post-close');
    // should throw error because fd is closed
    await fh.write ("FH", 5);
}
test();

``` 

### How often does it reproduce? Is there a required condition?

Reproduces always. Tried on v16, v18, v20.

### What is the expected behavior? Why is that the expected behavior?

**Output**:
```
pre-close
post-close
node:internal/process/promises:[...]
[Error: EBADF: bad file descriptor, write] { [...]
```
**Content of /tmp/ttt.txt:**
```
TEST is a filehandle / stream test
```

Works correctly with fs.closeSync (fh.fd); enabled instead of await fh.close();
Also works as expected, if the whole stream related block is commented out (contents of ttt.txt will differ).

### What do you see instead?

**Output:**
```
pre-close
```
**Content of /tmp/ttt.txt:**
```
TEST is a filehandle / stream test
```


### Additional information

_No response_
Repository: pytorch
Issue: MultiheadAttention should split embed_dim into four parameters
Labels: module: nn,triaged

### 🚀 The feature, motivation and pitch

The assertions around embed_dim are in `nn.MultiheadAttention` and `F.multi_head_attention_forward` too restrictive. 
The embed_dim currently seems to be a “catch-all” parameter, although the multi-head attention fundamentally supports four different dimensions to coexist, which are currently all noted as `embed_dim`:

1) The input dimension of the query - doesn’t need to be divisible by num_heads,
2) The embed_dim for query and key - this should be divisible by num_heads,
3) The embed_dim for value as well the input dimension of the out_projection - this should be divisible by num_heads,
4) The output dimension of out_proj - doesn’t need to be divisible by num_heads.

### Alternatives

Split up the embed_dim into four, i.e.
1) qdim,
2) qk_embed_dim,
3) vo_embed_dim,
4) out_dim,
and loosen the head_divisibility checks for qdim and out_dim. This would allow much more fine-grained adjustment of the MHA module, e.g. in the context of structured pruning.


### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @bhosmer @cpuhrsch @erichan1 @drisspg
Repository: next.js
Issue: `<Link>` with `href="#someexample"` will not trigger CSS target selector (`#someexample:target{...}`)
Labels: Navigation,CSS

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.6.0: Mon Aug 22 20:19:52 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.15.0
      npm: 9.5.0
      Yarn: 3.4.1
      pnpm: 8.6.0
    Relevant packages:
      next: 13.4.6-canary.7
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.5
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/tilman/nextlink-css-target-selector-bug

### To Reproduce

1.) Open the example under http://localhost:3000/ (for regular pages)
Watch the div below the links wich should turn blue during clicking the links.

Use regular anchor tags:
Click Link 1.) it to see that :target selector changed the style of a div
Click Link 2.): Reset the styling with this link by changing the target to '#'

Use next Link tags:
Click Link 3.) to see that :target selector does not change the style of a div if next/link is used
Click Link 1.)/4.) again to set the blue bg
Clink Link 5.) to reset the styling with this link by changing the target to '#'. Also does not reset the style if regular anchor tag (1./4.) was clicked before to set the style.

2.) Open the example under http://localhost:3000/appExample (for new app dir. Same behaviour)

### Describe the Bug

While using a next/link the css `:target` selector is not working. Only if we use a regular <a> tag.


### Expected Behavior

The CSS `:target` selector should work with next/link the same way as with the `<a>` tag

### Which browser are you using? (if relevant)

chrome

### How are you deploying your application? (if relevant)

localhost
Repository: material-ui
Issue: [docs-infra] Replace <DocSearch> for in-house implementation
Labels: enhancement,scope: docs-infra

### Related page

https://mui.com

### Kind of issue

Missing information

### Issue description

I was looking for how the algolia search is implemented on the homepage. As i can see it doesn't use any mui components, except for the hits that typography and badges are used. Is there any specific reasons on why this is not implemented using the mui's Autocomplete component?


### Context 🔦

We need to implement algolia in our site and thinking of how we can do this using material ui. The first option is to build it without the components that are provided from algolia (instantsearch) so that we can leverage the mui components.
Repository: PowerToys
Issue: Make the mouse pointer crosshair even better
Labels: Needs-Triage,Product-Mouse Utilities

### Description of the new feature / enhancement

The colors in the mouse pointer crosshair should be one for the left and bottom lines and another for the right and top line. This would facilitate even more the quick localization of the mouse pointer. 

### Scenario when this would be used?

I have one 32" 4K and two 23" FHD monitors. I need to use the 4K monitor at 100% scale for I work all day long with Visual Studio 2022 designing Windows Forms, and VS does not work correctly at other screen scales. This makes my life very difficult for the text is shown almost at 2 point size. 

But the main nuisance is the need to fast locate the mouse pointer in the 4K monitor. It is too small and I cannot make it too big, for it would be ridiculously big in the other two FHD monitors.

The PowerToys utility saves me a lot of time in this regard, but it could be made even better if the left and bottom crosshair colors were different from the right and top ones. This would allow me to instantly identify the correct position of the mouse pointer when it is in certain screen locations.

### Supporting information

_No response_
Repository: tauri
Issue: [bug] Failed to generate shell completions for bash
Labels: type: bug,scope: cli.rs,priority: 2 medium,status: upstream,platform: Linux,status: needs triage

### Describe the bug

For `cargo-tauri` `1.4.0`, I'm getting the following error while generating the shell completions:

```
        Info Generating completion file for bash...
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /build/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_complete-4.3.0/src/generator/utils.rs:26:39
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```

### Reproduction

Run:

```sh
cargo-tauri completions --shell bash
```

### Expected behavior

Successful shell completions generation.

### Platform and versions

```text
`1.4.0`
```


### Stack trace

```text
-
```


### Additional context

\-
Repository: TypeScript
Issue: Decorated function parameter types are not inferred
Labels: Needs Investigation

# Bug Report

When decorating a class method, the argument types are not inferred from the decorator. When using the decorator method directly, without decorator syntax, the types are inferred correctly.

### 🔎 Search Terms

decorator, infer, type, argument

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This happens for decorators introduced in 5.0

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior.
  This should have the same code as the code snippet below, and use whichever settings are relevant to your report.

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?ts=5.1.3#code/GYVwdgxgLglg9mABAEwKYTgJwIZVQCmAC5F8ZkSwQBbAI1UwEpEBeAPkQDc5yAaRDGDwAPKAH4S2MAE9GJMhURU6DZuy49kiAN6JMqKCExJgiAL4AoCxAA22AM73EAMThwdFxF8QABNBhw8T28EAnJmXQB6SMQABWwcagMGRAByclTEGGoABxsYCBgoG2lEAAsHRCk0qWlMqGkc1AA6fAB2AAYOgDZGYO9vQXs4GxabOABzBSqneyhMGDAJvoHLfsQoAHd3FhR0LFwCUEhYBA3thQj1gaGRscnpyrmFpeZoxABhBE4Ge3gkOCmBpNNLKeiYeruYGoNLPRYTTLUbClehVRDUGBzbAAa1QgDICUgAJgAzABWQkrbxmPprUZQRDANysJSoTYuNz4RgAbgsjLgzVC+AARHyhX0+c0tnBhaK3jEAIKYCY0VBCRCAjaNGGpOFLTKYpRwekOP4TMDYWijDbuHIJbBJPCYdVArWgmjg1KtEkAFlJjCAA)

### 💻 Code

<!-- Please post the relevant code sample here as well. This code and the Playground code should be the same, do not use separate examples -->
```ts
function decorate(f: (id: number) => void, context?: any): (id: number) => void { return f }

class Foo {
    @decorate
    one(id) { // Parameter 'id' implicitly has an 'any' type.(7006)
        console.log(id as string)
    }

    two = decorate(function two(id) {
        console.log(id as string) // Conversion of type 'number' to type 'string' may be a mistake… (2352)
    })
}

let foo = new Foo();
foo.one("foo")
foo.two("foo") // Argument of type 'string' is not assignable to parameter of type 'number'.(2345)
```

### 🙁 Actual behavior

The parameter `id` for method `one` is inferred as `any`

### 🙂 Expected behavior

The parameter is inferred as `number`, similar to how it works when calling the `decorated` function directly for method `two`.
Repository: vscode
Issue: Quick info quick fixes text flashes when moving mouse over it
Labels: bug,editor-hover

Issue by @dibarbet

@sandy081 says
I can reproduce this flickering with this sample extension code

```typescript
import { readFileSync } from 'fs';
import * as vscode from 'vscode';
import * as path from 'path';

export async function activate(context: vscode.ExtensionContext) {
    const diagnosticsCollection = vscode.languages.createDiagnosticCollection('test');
    vscode.commands.registerCommand('test.helloWorld', async () => {
        diagnosticsCollection.clear();
        const document = vscode.window.activeTextEditor?.document;
        if (!document) {
            return;
        }
        const diagnostic = new vscode.Diagnostic(new vscode.Range(new vscode.Position(1, 1), new vscode.Position(1, 3)), 'first line', vscode.DiagnosticSeverity.Hint);
        diagnosticsCollection.set(document.uri, [diagnostic]);
    });
    vscode.commands.registerCommand('test.helloWorld2', async () => {
        diagnosticsCollection.clear();
    });
    vscode.languages.registerCodeActionsProvider('typescript', new TestCodeActionProvider());
}

class TestCodeActionProvider implements vscode.CodeActionProvider {

    provideCodeActions(document: vscode.TextDocument, range: vscode.Range, context: vscode.CodeActionContext, token: vscode.CancellationToken): vscode.CodeAction[] {
        const action = new vscode.CodeAction('test code action', vscode.CodeActionKind.QuickFix);
        action.command = { command: 'test.helloWorld2', title: 'test code action' };
        return [action];
    }

}
```

As @mjbvz said, `renderHoverParts` is being called by the contentsHover multiple times. 

https://github.com/microsoft/vscode/blob/4c45cff558a46f548085b6b4ca6467078790719d/src/vs/editor/contrib/hover/browser/markerHoverParticipant.ts#L93

`renderHoverParts` in turn calls `renderMarkerStatusbar` that asks for code actions. Since fetching code actions is async we are seeing this flickering.

@alexdima What is the recommended fix here?

See the following example gifs

![Picture1](https://user-images.githubusercontent.com/5749229/231588463-6d6903e6-678e-4028-ab93-04a7991b8c2e.gif)


![quick_info_jump](https://user-images.githubusercontent.com/5749229/231554549-b2127456-009b-4ef8-839b-84971fa3926a.gif)
Repository: pytorch
Issue: "Y.getIntrusivePtr()->set_storage(X.getIntrusivePtr()->storage()); " in C++ is not supported
Labels: module: cpp,triaged

### 🚀 The feature, motivation and pitch

There is no set_storage() support for getIntrusivePtr() object.
I want to copy from X to Y where X and Y are from different devices (i.e. X.device() != Y.device()).
However, two devices share the global memory address with each other, so I prefer just moving the storage point from X to Y to avoid expensive data copy.

The following code in C++ doesn't work for me, as it fails for undefined `set_storage()`:
```cpp
Y.getIntrusivePtr()->set_storage(X.getIntrusivePtr()->storage())
```

If I perform a shallow copy using:
```cpp
Y.getIntrusivePtr()->shallow_copy_from(X.getIntrusivePtr());
```

It is also not what I want, because it will change Y's device to be X's device as well, making following computation of Y not performed on original Y's expected device.

Any alternative way to share the storage link. or any supporting plans?

### Alternatives

_No response_

### Additional context

_No response_

cc @jbschlosser
Repository: transformers
Issue: SpikeGPT
Labels: New model

### Feature request

Extract the spiking nature of the LLM and port that [set] of features over for training/inference,. 

https://github.com/ridgerchu/SpikeGPT

### Motivation

the benefits would result in more efficient computational costs (x22 reduction).

### Your contribution

I am willing to test, trace down bugs, and push.  I'm still new in the world of llm backend coding.