sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: Do not rely on Deno[Deno.internal].inspectArgs in 40_jupyter.js
Labels: refactor

Instead import it directly from `ext:deno_web/01_console.js`
Repository: storybook
Issue: [Tracking] React-docgen related issues
Labels: bug,Tracking,docgen

> **NOTE:** For anybody who is unaware, a workaround for many (most?) of these issues is to set `typescript.reactDocgen` to `react-docgen-typescript` in `.storybook/main.js`. [Learn more.](https://storybook.js.org/docs/api/main-config-typescript#reactdocgen)

### Describe the bug

This will serve as an umbrella issue where we document all the issues regarding react-docgen. It will be updated over time.




### React-docgen related issues

```[tasklist]
### Performance related
- [ ] https://github.com/storybookjs/storybook/issues/26543
```

```[tasklist]
### Limitations
- [ ] https://github.com/storybookjs/storybook/issues/26548
- [ ] https://github.com/storybookjs/storybook/issues/26406
- [ ] https://github.com/storybookjs/storybook/issues/26467
- [ ] https://github.com/storybookjs/storybook/issues/26407
- [ ] https://github.com/storybookjs/storybook/issues/25909
- [ ] https://github.com/storybookjs/storybook/issues/26652
- [ ] https://github.com/storybookjs/storybook/discussions/26583
- [ ] https://github.com/storybookjs/storybook/issues/26745
- [ ] https://github.com/storybookjs/storybook/issues/26780
- [ ] https://github.com/storybookjs/storybook/issues/26496#issuecomment-2049774433
```


#### Reproduction

In order to assist the React docgen maintainer to fix as many of these issues as possible, here's a reproduction that shows all these scenarios, with options to run Storybook with both react-docgen and react-docgen-typescript for comparison:

https://stackblitz.com/edit/react-docgen-issues-and-limitations
Repository: ui
Issue: [Bug]: Module '"usehooks-ts"' has no exported members 'useDebounce'
Labels: bug

### Describe the bug

_Typescript migrate to V3._
usehooks-ts bumped to version 3 and it's a major release with a lot of changes and improvements.

**Changes**
**Removed** **hooks**
Some hooks were removed from the library. The following hooks were removed:
useDebounce: Replaced by both [useDebounceValue] and [useDebounceCallback]c

**Other related hooks:** 
_Updated hook signatures_
Some hook signature have been updated introducing breaking changes.
[useCountdown]
[useDarkMode]
[useIntersectionObserver]
[useMediaQuery]
[useTernaryDarkMode]








### Affected component/components

usehooks-ts modified some hooks

### How to reproduce

Try to change the useDebounce hook to the new useDebounceValue.

### Codesandbox/StackBlitz link

please add a reproduction

### Logs

```bash
nothing
```


### System Info

```bash
3301
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: godot
Issue: Cannot Update my AndroidManifest File on Export
Labels: platform:android,needs testing,topic:export

### Tested versions

Godot 4.2.1

### System information

Windows 11

### Issue description

GooglePlay ask me to update my Android Manifest file adding this line: 
com.google.android.gms.permission.AD_ID but cannot getting updated. I have made the change in editor and also directly on Manifest, but when I reupload to GoogleStore it saids it doesn't have the permission. Help?
![Captura de pantalla 2024-03-21 105149](https://github.com/godotengine/godot/assets/103970174/1319e38a-949d-4857-b7ce-10e3aa345a15)
![Captura de pantalla 2024-03-21 110858](https://github.com/godotengine/godot/assets/103970174/9f792750-171d-459e-9846-8a075e03c3c3)
![Captura de pantalla 2024-03-21 111127](https://github.com/godotengine/godot/assets/103970174/fa9157c4-8e6f-430a-b043-16b239becdc5)

### Steps to reproduce

Add Android to project, export AAB File and try to upload to Google Store.

### Minimal reproduction project (MRP)

![Captura de pantalla 2024-03-21 105149](https://github.com/godotengine/godot/assets/103970174/1319e38a-949d-4857-b7ce-10e3aa345a15)
![Captura de pantalla 2024-03-21 110858](https://github.com/godotengine/godot/assets/103970174/9f792750-171d-459e-9846-8a075e03c3c3)
![Captura de pantalla 2024-03-21 111127](https://github.com/godotengine/godot/assets/103970174/fa9157c4-8e6f-430a-b043-16b239becdc5)
Repository: rust
Issue: `dead_code` in 1.77 lints against tuple fields with Drop implementations and suggests removing them
Labels: A-lints,A-diagnostics,T-compiler

### Code

I tried this code:
```Rust

struct SignificantDrop {
    a: usize,
}

impl Drop for SignificantDrop {
    fn drop(&mut self) {
        println!("Doing something important to {}", self.a);
    }
}                        

struct OwnsResource(usize, SignificantDrop);              

fn main() {
    let s = OwnsResource(17, SignificantDrop { a: 999 }); 

    println!("{}", s.0);
}
```


### Current output

```Shell
field `1` is never read
`#[warn(dead_code)]` on by default (rustc dead_code)
─────────────────────────────────────────────────────────────────────────────
field in this struct (rustc dead_code)
─────────────────────────────────────────────────────────────────────────────
consider changing the field to be of unit type to suppress this warning while
preserving the field numbering, or remove the field: `()` (rustc dead_code)
```


### Desired output

If the unused field has a drop implementation it should at least not suggest removing it entirely. I'm not sure what the best option is. For private types converting it to a struct and naming the field with an underscore works, but that doesn't work for public types.


### Rationale and extra context

I use this pattern in a few cases in GUI code to ensure that an event handler is cleaned up when the containing tuple gets dropped. I can avoid the finding, but if I had just accepted the suggestion I'd have accidentally cleaned up my event handlers.

### Other cases


For a struct the output is a more reasonable `field `b` is never read (rustc dead_code)` without a suggestion to remove it. I think this could, still, benefit from detecting if Drop is implemented since it might have side effects.

```rust
struct OwnsResourceTwo {
    a: usize,             
    b: SignificantDrop,   
}
```


### Rust Version

```Shell
rustc 1.77.0 (aedd173a2 2024-03-17)
binary: rustc
commit-hash: aedd173a2c086e558c2b66d3743b344f977621a7
commit-date: 2024-03-17
host: x86_64-unknown-linux-gnu
release: 1.77.0
LLVM version: 17.0.6
```


### Anything else?

_No response_
Repository: vscode
Issue: Git - VSCode ignores .gitconfig file
Labels: bug,git

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: **Yes**

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.87.2
- OS Version: Windows 11 Enterprise 23H2

Steps to Reproduce:


1. `git config --system --edit`

```
[core]
	editor = notepad
```

1. `git init`
2. `git commit --allow-empty`
3. Notepad should open, enter a commit message.
4. code .
5. Create `file.txt` in the root of the repository, content can be anything, "Hello World".
6. Use VSCode GUI to stage the file, click `Commit` without providing a commit message.

**Expected**
Notepad should open for you to provide a commit message.

**Actual**
A new editor opens in VSCode.

Something in the application is overriding the setting in my system level .gitconfig file.

## Additional Info

My team has been struggling with this for quite some time.  I've used the `core.editor` key as an example, I've seen other settings get "ignored" for lack of a better word.

Specifically, `user.name` and `user.email`.  These appear in the global config file, verified by `git config --show-origin user.name user.email`, but VSCode complains and says that a commit can't be made without a user and email provided.  When this happens, we've always been able to make a commit using a separate terminal, but not in VSCode.

The fix has been to uncheck this setting `Git: Require Git User Config`.
Repository: next.js
Issue: Error not being thrown for non-async server side arrow functions
Labels: bug,Runtime

### Link to the code that reproduces this issue

https://github.com/DiskCrasher/next-js-issue

### To Reproduce

1. Run `yarn dev`.
2. Browse to [http://localhost:3000](http://localhost:3000).
3. Observe "Server actions must be async functions" error for function `bar` in file ssc.tsx.
4. Delete or comment out `bar` function.
5. Repeat steps above and observe that similar error is not shown for `foo` function even though it's not async.

### Current vs. Expected behavior

The "Server actions must be async functions" error should appear for both functions.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home
  Available memory (MB): 8050
  Available CPU cores: 4
Binaries:
  Node: 20.11.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.0-canary.35 // Latest available version is detected (14.2.0-canary.35).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


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

Middleware / Edge (API routes, runtime)

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

next dev (local), next start (local)

### Additional context

_No response_
Repository: go
Issue: go/doc: New trashes the AST, even in PreserveAST mode
Labels: NeedsInvestigation

The [doc.New](https://pkg.go.dev/go/doc#New) function mutates the AST, even in PreserveAST mode. See https://go.dev/play/p/YSn-iNSBXsv for a minimal repro. This leads to crashes in gopls (e.g. https://github.com/golang/go/issues/66449).

Here's one culprit; there may be others:
```go
// fileExports removes unexported declarations from src in place.
func (r *reader) fileExports(src *ast.File) {
	j := 0
	for _, d := range src.Decls {
		if r.filterDecl(d) {
			src.Decls[j] = d
			j++
		}
	}
	src.Decls = src.Decls[0:j]
}
```
Repository: flutter
Issue: Web test bootstrapping needs to be migrated off the window singleton
Labels: tool,engine,platform-web,P2,team-web,triaged-web

As part of multi view support, the `window` singleton is deprecated and will be removed in the future. The `flutter/flutter` repository has been cleaned up to no longer use this property and the only remaining usage is the bootstrapping code for web tests:

https://github.com/flutter/flutter/blob/98d10b62112d663549f78528e3901250a9ba3590/packages/flutter_tools/lib/src/web/bootstrap.dart#L416

That code needs to be migrated to continue working when the `window` singleton is removed.
Repository: pytorch
Issue: DISABLED test_mm_plus_mm2_cuda_cuda_wrapper (__main__.TestCudaWrapper)
Labels: triaged,module: flaky-tests,skipped,oncall: pt2,module: inductor

Platforms: inductor, linux, slow



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

Over the past 3 hours, it has been determined flaky in 2 workflow(s) with 4 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_mm_plus_mm2_cuda_cuda_wrapper`
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_cuda_cpp_wrapper.py`

cc @clee2000 @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler @amjames @desertfire
Repository: vscode
Issue: On resinstall remove "Open with Code" context menu
Labels: workbench-os-integration

Reinstall setup should remove "Open with Code" context menu when the options isn't selected.

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.87.2
- OS Version: Windows 11 23H2

Steps to Reproduce:

1. Install VSCode and select 1 or both of:
   - Add "Open with Code" action to Windows Explorer file context menu
   - Add "Open with Code" action to Windows Explorer directory context menu
2. Install VSCode and deselect 1 or both depending on what you enabled on step 1.
Repository: vscode
Issue: Allow panel tabs on bottom of panel to align with activity bar position bottom
Labels: feature-request,workbench-views

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Now we can set the activity bar position to the bottom of the screen. To align with this, we should allow the same for panel.

Some possible ideas:



![Image](https://github.com/microsoft/vscode/assets/6561887/1385f5fe-5cad-4ea4-bbad-9c5041a4a02b)



![Image](https://github.com/microsoft/vscode/assets/6561887/02fdb42a-2bd2-4ac6-aeab-ca13feef955a)
Repository: transformers
Issue: Support batching sequence labels pairs for zero shot classification pipeline
Labels: Core: Pipeline,Feature request

### Feature request

Currently zero shot classification pipeline dose not support specifying different set of labels for each sample input when batching multiple sequences of input. We want support input of a pair of sequence and its labels so that we can run prediction on them in batch.

Following is an example of what sample input we want to specify:

```
samples = [
("Iphone 15 pro max", ["mobiles", "appliances", "toys"]),
("Iphone 15 pro max", ["Samsung", "Apple"]),
("galaxy s21 ultra", ["mobiles", "appliances", "toys"]),
("galaxy s21 ultra", ["Samsung", "Apple"])
]
```


### Motivation

By grouping labels with sequences pairs we can batch different type of labels for each sample and by batching it runs on gpu will be faster.

### Your contribution

I will work on this feature and create a pr for it then update this issue. Making the issue now just to make sure that no one is working on this while I am doing it.
Repository: rust
Issue: OSX CFI produces relocation issues
Labels: O-macos,T-compiler,A-sanitizers,C-bug,PG-exploit-mitigations

As seen when testing #122456 

I tried this code:

```rust
pub fn main() {
  let f: &fn() = &((|| ()) as _);
  f();
} 
```
compiled with `rustc --crate-type=bin -C prefer-dynamic=off -Clto -Zsanitizer=cfi -C target-feature=-crt-static -C codegen-units=1 -C opt-level=0` on OSX

I expected to see this happen: Builds successfully

Instead, this happened: Relocation issues:

```
command: RUSTC_ICE="0" "/Users/runner/work/rust/rust/build/x86_64-apple-darwin/stage2/bin/rustc" "/Users/runner/work/rust/rust/tests/ui/sanitizer/cfi-closure-fn-ptr-cast.rs" "-Zthreads=1" "-Zsimulate-remapped-rust-src-base=/rustc/FAKE_PREFIX" "-Ztranslate-remapped-path-to-local-path=no" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/.cargo" "--sysroot" "/Users/runner/work/rust/rust/build/x86_64-apple-darwin/stage2" "--target=x86_64-apple-darwin" "--error-format" "json" "--json" "future-incompat" "-Ccodegen-units=1" "-Zui-testing" "-Zdeduplicate-diagnostics=no" "-Zwrite-long-types-to-disk=no" "-Cstrip=debuginfo" "-C" "prefer-dynamic" "-o" "/Users/runner/work/rust/rust/build/x86_64-apple-darwin/test/ui/sanitizer/cfi-closure-fn-ptr-cast/a" "-A" "internal_features" "-Crpath" "-Cdebuginfo=0" "-Lnative=/Users/runner/work/rust/rust/build/x86_64-apple-darwin/native/rust-test-helpers" "-L" "/Users/runner/work/rust/rust/build/x86_64-apple-darwin/test/ui/sanitizer/cfi-closure-fn-ptr-cast/auxiliary" "--crate-type=bin" "-Cprefer-dynamic=off" "-Clto" "-Zsanitizer=cfi" "-C" "target-feature=-crt-static" "-C" "codegen-units=1" "-C" "opt-level=0"
--- stderr -------------------------------
error: unsupported symbol modifier in branch relocation
   |
note: instantiated into assembly here
note: instantiated into assembly here
  --> <inline asm>:1:2
   |
LL |     jmp __ZN4core3ops8function6FnOnce9call_once17hbd679098001308bdE.cfi@plt

error: unsupported symbol modifier in branch relocation
   |
note: instantiated into assembly here
note: instantiated into assembly here
  --> <inline asm>:5:1
   |
LL | jmp __ZN23cfi_closure_fn_ptr_cast4main17hec6d7c750d93313aE.cfi@plt

error: aborting due to 2 previous errors
------------------------------------------
```

The patch being tested only adjusts labels, so this bug is about fixing actually producing CFI executables on OSX - all the previously existing tests were codegen only.

It is likely that a much smaller program (possibly anything with an indirect call? any function?) will trigger this issue without needing the `FnPtrShim`, but I don't personally have a mac to test with.
Repository: tauri
Issue: set_activation_policy is not accessible during runtime [bug] 
Labels: type: bug,status: needs triage

### Describe the bug

`set_activation_policy` is an API that enables showing/hiding an application's icon in the doc and the application switcher. It can be set dynamically at runtime. I want to use this behavior to create an application that usually lives in the menu bar, but the menu bar can be clicked to bring up the window.

However, it's a method on App, rather than AppHandle, which means it can't be used in places I should be able to.


```rs
tauri::Builder::default()
.setup(|app| {
    app.on_tray_icon_event(move |handle, event| match event.click_type {
        _ => { // any click
           // I can't use app in here because it's been moved
           // this is what I want/should be able to do, but this API does not exist.  
           handle.set_activation_policy(ActivationPolicy::Regular);
        }
    });
    Ok(());
});
```

I think the method should be moved entirely from app to app handle. Alternatively, it should be duplicated on AppHandle in addition to App.

If the change is welcome, I'm happy to create a PR.

Right now, my workaround is duplicating the internal logic from tao:

```rs
fn manually_set_activation_policy(policy: ActivationPolicy) {
    use objc::{sel, sel_impl};
    use tao::platform::macos::{ActivationPolicy as TaoActivationPolicy};
    let cls = objc::runtime::Class::get("NSApplication").unwrap();
    let app: cocoa::base::id = unsafe { objc::msg_send![cls, sharedApplication] };
    let policy: TaoActivationPolicy = match policy {
        ActivationPolicy::Regular => TaoActivationPolicy::Regular,
        ActivationPolicy::Accessory => TaoActivationPolicy::Accessory,
        ActivationPolicy::Prohibited => TaoActivationPolicy::Prohibited,
        _ => panic!("Unsupported activation policy"),
    };
    let policy: cocoa::appkit::NSApplicationActivationPolicy = policy.into();
    unsafe { objc::msg_send![app, setActivationPolicy: policy] }
}
```

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
tauri 2.0 beta
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: godot
Issue: Touch input fires InputEventMouseButton
Labels: bug,topic:input

### Tested versions

v4.2

### System information

Windows 11, Godot v4.2, Surface 8 Pro

### Issue description

One of those moments that destroy the Godot experience. Disabling the flag "Enable mouse from touch" does not have any function. Instead, a touch input still invokes the mouse event.

### Steps to reproduce

Create new project.
Add root node of type Node.
Add this script:
```gdscript
extends Node

func _input(event: InputEvent):
	if event is InputEventMouseButton:
		print("InputEventMouseButton")
```

Set "General - Input Devices - Emulate Mouse From Touch" to disabled.
Run project.
Touch the screen.
The print message will be printed.

### Minimal reproduction project (MRP)

[TouchTest.zip](https://github.com/godotengine/godot/files/14713582/TouchTest.zip)
Repository: pytorch
Issue: Triangular matrix storage + matmul
Labels: triaged,module: linear algebra

### 🚀 The feature, motivation and pitch

Triangular matrix-vector or matrix-matrix multiplication is a useful primitive in inference (because past and present tokens are taken into account, but not future) - in theory this saves half the FLOPs and storage. This feature exists in cuBLAS [here](https://docs.nvidia.com/cuda/cublas/#cublas-t-tpmv) - though I found it to be slower than GEMM in testing. It would be great to have a format to store a triangular matrix and a function that would recognize it. 

### Alternatives

Doing normal GEMM works, but you have to store a lot of 0s and compute products with them.

### Additional context

_No response_

cc @jianyuh @nikitaved @pearu @mruberry @walterddr @xwang233 @Lezcano
Repository: rust
Issue: Add documentation to `Send` & `Sync` impls
Labels: E-mentor,E-help-wanted,A-docs,T-libs

### Location

https://github.com/rust-lang/rust/blob/0ad927c0c07b65fc0dae37105e09c877c87c296a/library/std/src/sync/mutex.rs#L186-L189

### Summary

I think it is a good idea to document `Send` & `Sync` impls in types such as `Mutex`, `RwLock` etc. especially considering they are `unsafe` traits. 

Also it's not obvious why some types have particular restrictions, for example:
- why `Mutex` is `Sync` only if the `T: Send`
- why `MutexGuard` is `!Send`

It can be done as **// SAFETY** comments or proper docs.