sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: type error while importing `svelte 5` component due to recent change in `svelte-check`
Labels: bug,help wanted,typescript,svelte,sev:S3

### Describe the bug

Due to recent [change](https://github.com/sveltejs/language-tools/pull/2517) in `svelte-check` v4.0.3, following type error occurs while importing Svelte 5 component in svelte storybook file. This also ends up causing multiple type errors in the story args definition.

```typescript
Error: Type 'Component<Props, {}, "">' is not assignable to type 'ComponentType<Component<Props, {}, "">, any>'.
  Type 'Component<Props, {}, "">' provides no match for the signature 'new (options: ComponentConstructorOptions<Component<Props, {}, "">>): { [x: string]: any; $destroy: () => void; $on: <K extends string>(type: K, callback: (e: any) => void) => () => void; $set: (props: Partial<...>) => void; }'. 
```

As per [PR](https://github.com/sveltejs/language-tools/pull/2517), In svelte 5, components are functions. Hence with this PR only function type is exported in runes mode.

I tried to supply svelte 5 component to `Meta` as `Meta<ReturnType<typeof Button>>`. However, it throws following error after that change.

```typescript
Error: Type '{ $on?(type: string, callback: (e: any) => void): () => void; $set?(props: Partial<Props>): void; }' is not assignable to type 'ComponentType<{ $on?(type: string, callback: (e: any) => void): () => void; $set?(props: Partial<Props>): void; }, any>'.
  Type '{ $on?(type: string, callback: (e: any) => void): () => void; $set?(props: Partial<Props>): void; }' provides no match for the signature 'new (options: ComponentConstructorOptions<{ $on?(type: string, callback: (e: any) => void): () => void; $set?(props: Partial<Props>): void; }>): { ...; }'. 
  title: "Example/Button",
  component: Button as ReturnType<typeof Button>,
  tags: ["autodocs"],
```


### Reproduction link

https://codesandbox.io/p/devbox/8p9rrz

### Reproduction steps

1. Run pnpm install
2. Run pnpm check
3. Type error will be thrown
4. If `svelte-check` is reverted to `4.0.2`, svelte-check passes with no errors.

### System

```
  System:
    OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (2) x64 AMD EPYC
    Shell: Unknown
  Binaries:
    Node: 20.9.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn <----- active
    npm: 9.8.1 - /usr/local/bin/npm
    pnpm: 8.10.2 - /usr/local/share/npm-global/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.3.5 => 8.3.5 
    @storybook/addon-interactions: ^8.3.5 => 8.3.5 
    @storybook/addon-links: ^8.3.5 => 8.3.5 
    @storybook/addon-svelte-csf: ^4.1.7 => 4.1.7 
    @storybook/blocks: ^8.3.5 => 8.3.5 
    @storybook/svelte: ^8.3.5 => 8.3.5 
    @storybook/sveltekit: ^8.3.5 => 8.3.5 
    @storybook/test: ^8.3.5 => 8.3.5 
    storybook: ^8.3.5 => 8.3.5 
```
### Additional context

_No response_
Repository: godot
Issue: Import options do not change if all options get reset to default.
Labels: bug,topic:editor,topic:import

### Tested versions

4c4e67334412f73c9deba5e5d29afa8651418af2

### System information

Windows 11

### Issue description

In the Advanced Importer, if physics/collision is added to a mesh, then reimported, then you go back into the importer and remove it and attempt to reimport, the physics will still be assigned. This appears to be due to utilization of the _subresources parameter in the .import file which only gets overwritten if it contains data, meaning that if you revert an imported scene to a state where it has no custom parameters, it will be perpetually stuck.

### Steps to reproduce

* Import a FBX/GLTF file.
* Open the advanced import settings.
* Add physics to one mesh in the scene.
* Reimport the scene.
* Go into the advanced import settings again and remove the physics.
* Reimport the scene.
* Go into the advanced import settings yet again and observe how the physics are still assigned when the should be removed.

### Minimal reproduction project (MRP)

N/A
Repository: rust
Issue: static_mut_refs lint fires on `assert_eq`
Labels: A-diagnostics,T-compiler

### Code

```rust
static mut S: i32 = 0;

fn main() {
    unsafe {
        assert!(S == 0);
        assert_eq!(S, 0);
    }
}
```

### Current output

```
warning: creating a shared reference to mutable static is discouraged
 --> src/main.rs:6:20
  |
6 |         assert_eq!(S, 0);
  |                    ^ shared reference to mutable static
  |
  = note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2024/static-mut-references.html>
  = note: shared references to mutable statics are dangerous; it's undefined behavior if the static is mutated or if a mutable reference is created for it while the shared reference lives
  = note: `#[warn(static_mut_refs)]` on by default
```

### Desired output

(none)

### Rationale and extra context

The two macro invocations do the same thing, but in the first case we recognize that the reference created for `==` is a "short-lived reference" and suppress the warning. In the second case, we do show a warning -- I suspect it has to do with the formatting? Indeed `println!("{}", S);` also triggers a warning. Maybe formatting macros where we know that the reference does not outlive the macro could be recognized by the lint?

An alternative would be to suggest using `{ S }` in these cases which will also avoid the warning.

### Other cases

_No response_

### Rust Version

current nightly

### Anything else?

_No response_
Repository: go
Issue: x/build: update OpenBSD builders to 7.6
Labels: OS-OpenBSD,Builders,NeedsFix,new-builder

OpenBSD 7.6 has just been released (https://www.openbsd.org/76.html) - this means that the only two supported OpenBSD releases are now 7.5 and 7.6. The current openbsd-amd64 and openbsd-386 builders are running 7.2 which is unsupported. As such, these should be updated to run 7.6.
Repository: PowerToys
Issue: Send multiline text
Labels: Needs-Triage

### Description of the new feature / enhancement

Hello,
is it possibel to send multiline text with the keyboard manager?
e.g. press Win+Ctrl+S to send a signature text?

### Scenario when this would be used?

...

### Supporting information

_No response_
Repository: TypeScript
Issue: Iterator Helpers: `return` method typing is weaker than ideal
Labels: Suggestion,Awaiting More Feedback

### ⚙ Compilation target

ESNext

### ⚙ Library

esnext.iterator.d.ts

### Missing / Incorrect Definition

The `return` method always exists on iterators returned by `Iterator.from` (`iter` in below code) and iterators returned by Iterator Helpers methods (`iter2` in below code).

However, it is defined as optional in the current definition. This could be improved.

Please note that you can't just add a non-optional `return` method definition to the `IteratorObject` type -- iterators returned by builtin methods other than Iterator Helpers don't have that method (`iter3`).

_P.S. if you are interested in a motivating example, I don't have one. Sorry 🤪_

### Sample Code

```ts
const iter = Iterator.from({ next() { return { done: false, value: 0 }} });

iter.return(); // should not error

const iter2 = iter.map(x => x);

iter2.return(); // should not error

const iter3 = [].values();

iter3.return(); // Note: this error IS correct
```

[Playground](https://www.typescriptlang.org/play/?target=99&ts=5.6.2#code/MYewdgzgLgBAllApgJxgXhgSScghlEZAOgDNkQBbACgG8YxEAPKKgShjuUSgFdkwOMACbhEALhglcAGwiIANDABuMnuJgAGGAF9tO1gG4AUEYQoiXXvzYGYAejswIACxA9pQ+iFgpyyE6CQsGbIAEzo8DhEFLgADlSM6AB8MIyGJiGhFtx8YDb2ji5uHl4+yH4B4NCRKADMEQDaALpEKtJqEDYZOLXZVnmGBTAAct7qUM5wEDC+hFgAyjCg5YjAUCZAA)

### Documentation Link

https://tc39.es/proposal-iterator-helpers/

Spec states that below objects always have the `return` method:

- %WrapForValidIteratorPrototype%
- %IteratorHelperPrototype%
Repository: tensorflow
Issue: Tensorflow Distributed AlltoAll
Labels: type:feature,comp:ops

### Issue type

Feature Request

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

No

### Source

binary

### TensorFlow version

Tf 2.9

### Custom code

Yes

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Hi,

I am trying to find a workaround, or ideally an implementation of the MPI [AlltoAll](https://www.mpich.org/static/docs/v3.4/www3/MPI_Alltoall.html) primitive.

As far as I can tell, Tensorflow has an AlltoAll op, but only for TPUs: https://www.tensorflow.org/api_docs/python/tf/raw_ops/AllToAll.

In a distributed setup with 4 devices, this would allow me to go from
```bash
PerReplica:{
  0: [0 1 2 3],
  1: [0 1 2 3],
  2: [0 1 2 3],
  3: [0 1 2 3]
}
``` 
to 
```
PerReplica:{
  0: [0 0 0 0],
  1: [1 1 1 1],
  2: [2 2 2 2],
  3: [3 3 3 3]
}
```
with a single communication call. I have managed to get this working by sharding with DTensor, but I'm trying to stay within the `tf.distribute` setting. Is there an easy workaround?





### Standalone code to reproduce the issue

```shell
import tensorflow as tf
import numpy as np
# tf.debugging.set_log_device_placement(True)
tf.config.set_visible_devices([], device_type='GPU')
# Create sharding mesh
def configure_virtual_cpus(ncpu):
    phy_devices = tf.config.list_physical_devices('CPU')
    tf.config.set_logical_device_configuration(phy_devices[0], [
        tf.config.LogicalDeviceConfiguration(),
    ] * ncpu)

ndev = 4
configure_virtual_cpus(ndev)
devices = [f'CPU:{i}' for i in range(ndev)]
strategy = tf.distribute.MirroredStrategy(devices)

arr = np.arange(0,4)
arr_total = np.stack([arr]*4)


def value_fn(ctx):
    return arr_total[ctx.replica_id_in_sync_group]


arr_tf = strategy.experimental_distribute_values_from_function(value_fn)
print(arr_tf)
# How to achieve the AllToAll operation here?
```


### Relevant log output

```shell
PerReplica:{
  0: [0 1 2 3],
  1: [0 1 2 3],
  2: [0 1 2 3],
  3: [0 1 2 3]
}
```
Repository: rust
Issue: `assert_eq!` is not 100% hygienic
Labels: A-diagnostics,A-macros,T-compiler,C-bug,D-confusing,D-terse,T-libs,A-hygiene

Not sure if this should be considered a bug or a diagnostic issue.

Having a `const left_val` or `const right_val` declared breaks `assert_eq!`. This has to do with its expansion and Rust's rules for macro hygiene: https://sabrinajewson.org/blog/truly-hygienic-let

Consider this code
```rust
fn main() {
    let x: u8 = 0;
    assert_eq!(x, 0);
}
```

according to `cargo expand` it expands to

```rust
#![feature(prelude_import)]
#[prelude_import]
use std::prelude::rust_2021::*;
#[macro_use]
extern crate std;
fn main() {
    let x: u8 = 0;
    match (&x, &0) {
        (left_val, right_val) => {
            if !(*left_val == *right_val) {
                let kind = ::core::panicking::AssertKind::Eq;
                ::core::panicking::assert_failed(
                    kind,
                    &*left_val,
                    &*right_val,
                    ::core::option::Option::None,
                );
            }
        }
    };
}
```
Since `assert_eq!` wants to use the value of the provided expressions twice (once for comparison, once for printing the result on failure), but it only wants to evaluate each expression once, it does a `match` to bind them to a pattern `(left_val, right_val)`. However, having a `const` named `left_val` or `right_val` in scope changes the meaning of the pattern.

```rust
fn main() {
    let x: u8 = 0;
    const left_val: i8 = -123;
    assert_eq!(x, 0);
}
```

```
error[E0308]: mismatched types
 --> src/main.rs:4:5
  |
3 |     const left_val: i8 = -123;
  |     ------------------ constant defined here
4 |     assert_eq!(x, 0);
  |     ^^^^^^^^^^^^^^^^
  |     |
  |     expected `&u8`, found `i8`
  |     this expression has type `(&u8, &{integer})`
  |     `left_val` is interpreted as a constant, not a new binding
  |     help: introduce a new binding instead: `other_left_val`
  |
  = note: this error originates in the macro `assert_eq` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0614]: type `i8` cannot be dereferenced
 --> src/main.rs:4:5
  |
4 |     assert_eq!(x, 0);
  |     ^^^^^^^^^^^^^^^^
  |
  = note: this error originates in the macro `assert_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
```

The error message, admittedly, is not very helpful.

Thankfully, you can't use this to make `assert_eq` pass/fail when it shouldn't. The worst you can achieve is a cryptic error message from the compiler. I think. So this "bug" is not really exploitable, plus chances of *accidentally* breaking this are probably pretty low (`const`s are usually named in `UPPER_CASE` in Rust), but the diagnostic is admittedly not very helpful. 

The article I've linked above (https://sabrinajewson.org/blog/truly-hygienic-let) offers a potential solution for this. TL;DR: due to shadowing shenanigans having a function named `left_val` will prevent `left_val` from being interpreted as a const in patterns.

@rustbot label A-macros A-diagnostics C-bug D-confusing D-terse
Repository: godot
Issue: Android Editor: Loading indicator is not visible in compatibility renderer
Labels: bug,platform:android,topic:editor

### Tested versions

- Reproducible in 4.4.dev2, 4.4.dev3, 4.4.beta1

### System information

Godot v4.4.dev3 - Android - Single-window, 1 monitor - OpenGL ES 3 (Compatibility) - Mali-G52 -  (8 threads)

### Issue description

AFAIK there was a loading indicator. The loading screen when exporting from the Android Editor seems to be missing same for when installing Export template. It feels like the Editor is unresponsive without the loading indicator

https://github.com/user-attachments/assets/50ab969a-30f2-435b-9d44-14ac05a08bdb



### Steps to reproduce

Just export anything project from the Android Editor 

### Minimal reproduction project (MRP)

N/A
Repository: vscode
Issue: [json] support 'CodeActionContext.only'
Labels: bug,json

<!-- ⚠️⚠️ 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.94.1
- OS Version: Ubuntu24.04

Recently see that whenever we save any json file and it gives below wanring in **Output**

```log
2024-10-09 19:11:08.851 [warning] vscode.json-language-features - Code actions of kind 'source.fixAll' requested but returned code action is of kind 'source.sort.json'. Code action will be dropped. Please check 'CodeActionContext.only' to only return requested code actions.
2024-10-09 19:11:08.855 [warning] vscode.json-language-features - Code actions of kind 'source.organizeImports' requested but returned code action is of kind 'source.sort.json'. Code action will be dropped. Please check 'CodeActionContext.only' to only return requested code actions.

```

![Image](https://github.com/user-attachments/assets/3f225824-9972-4b08-8556-8c60f535bbce)


Steps to Reproduce:

1.  Open _settings.json_ 
2.  Add below settings in settings.json
```json
{
 "files.autoSave": "afterDelay",
"[json][jsonc]": {
    "editor.defaultFormatter": "vscode.json-language-features"
  },
 "editor.codeActionsOnSave": {
    "source.fixAll.eslint": "explicit",
    "source.fixAll": "explicit",
    "source.organizeImports": "explicit"
  }
}
```
4. Open Output Panel and select extension host
5. Open any json file and press Ctrl+S ( Save )
6. you can see the warning.

even one of warning coming from vscode-eslint extension
Repository: godot
Issue: Nested `CSGShape3D`' doesn't update aabb gizmo if visibility is disabled
Labels: needs testing,topic:3d

### Tested versions

4.3, current master

### System information

Godot v4.3.stable - Debian GNU/Linux trixie/sid trixie - Wayland - GLES3 (Compatibility) - Mesa Intel(R) HD Graphics 520 (SKL GT2) - Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz (4 Threads)

### Issue description

If the **nested** `CSGShape3D` has disabled visibility it doesn't update it is aabb gizmo while it happens when it is visible


https://github.com/user-attachments/assets/cb3212c1-7434-437b-9db2-3994f81d9036



### Steps to reproduce

1. Create scene with two CSGShape's one inside another
2. Disable visibility of nested one
3. Select the nested one (to see aabb gizmo)
4. Change it is size

You expect to see size change

### Minimal reproduction project (MRP)

[csg_test.zip](https://github.com/user-attachments/files/17309230/csg_test.zip)
Repository: flutter
Issue: The pub roll is blocked by build failures
Labels: team-infra,P1,triaged-infra

The roll here https://github.com/flutter/flutter/pull/156440

Caused failures like https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8734597920760676097/+/u/run_platform_views_scroll_perf_ad_banners__timeline_summary/stdout

```
[2024-10-08 18:00:22.743431] [STDOUT] stdout:                Resolving dependencies of `Podfile`
[2024-10-08 18:00:22.743457] [STDOUT] stdout:                  CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only performed in repo update
[2024-10-08 18:00:22.743485] [STDOUT] stdout:                  CDN: trunk Relative path: all_pods_versions_5_9_a.txt exists! Returning local because checking is only performed in repo update
[2024-10-08 18:00:22.743515] [STDOUT] stdout:                  CDN: trunk Relative path: Specs/5/9/a/Google-Mobile-Ads-SDK/11.2.0/Google-Mobile-Ads-SDK.podspec.json exists! Returning local because checking is only performed in repo update
[2024-10-08 18:00:22.743591] [STDOUT] stdout:                  CDN: trunk Relative path: all_pods_versions_4_2_c.txt exists! Returning local because checking is only performed in repo update
[2024-10-08 18:00:22.743630] [STDOUT] stdout:                  CDN: trunk Relative path: Specs/4/2/c/FlutterMacOS/3.16.0/FlutterMacOS.podspec.json exists! Returning local because checking is only performed in repo update
[2024-10-08 18:00:22.743647] [STDOUT] stdout:                [!] CocoaPods could not find compatible versions for pod "Google-Mobile-Ads-SDK":
[2024-10-08 18:00:22.743695] [STDOUT] stdout:                  In Podfile:
[2024-10-08 18:00:22.743718] [STDOUT] stdout:                    google_mobile_ads (from `.symlinks/plugins/google_mobile_ads/ios`) was resolved to 5.2.0, which depends on
[2024-10-08 18:00:22.743859] [STDOUT] stdout:                      Google-Mobile-Ads-SDK (~> 11.10.0)
```
Repository: ollama
Issue: CORS (Cross-Origin Resource Sharing)
Labels: bug,api

### What is the issue?

please enable CORS (Cross-Origin Resource Sharing) in rest api
Repository: godot
Issue: Nested `CSGShape` aabb gizmo isn't visible if the node invisible upon scene open
Labels: bug,topic:editor,needs testing,topic:3d

### Tested versions

4.3, current master

### System information

Godot v4.3.stable - Debian GNU/Linux trixie/sid trixie - Wayland - GLES3 (Compatibility) - Mesa Intel(R) HD Graphics 520 (SKL GT2) - Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz (4 Threads)

### Issue description

If the **nested** `CSGShape3D` has disabled visibility it doesn't show aabb gizmo when selected after opening scene


https://github.com/user-attachments/assets/8044e0d4-095f-4fe4-b4ed-965edcdcb9df



### Steps to reproduce

1. Create scene with two CSGShape's one inside another
2. Disable visibility of nested one
3. Close scene
4. Open scene
5. Select the nested shape (in the scene tree dock)

You expect to see aabb gizmo but there is no

6. Make the shape visible
7. Make shape invisible

Now you see aabb gizmo


### Minimal reproduction project (MRP)


[csg_test.zip](https://github.com/user-attachments/files/17309484/csg_test.zip)
Repository: vscode
Issue: Modified image attachments don't update the thumbnail/hover
Labels: bug,panel-chat,chat

Repro:

1. Open chat
2. Attach an image file
3. Edit and save the image, 🐛 the thumbnail and hover aren't changed
Repository: go
Issue: x/tools/go/packages: support for fake GOROOTs
Labels: NeedsInvestigation,Tools

This issue is the continuation of discussions in [CL 615396](https://go-review.googlesource.com/c/tools/+/615396/comments/454f8fb1_42f3239b). 

When I tried to migrate x/tools/go/ssa/interp away from the deprecated loader package in its test cases in [CL 615016](https://go-review.googlesource.com/c/tools/+/615016), I attempted to create a fake GOROOT with [some mocked std libs](https://github.com/golang/tools/tree/master/go/ssa/interp/testdata) so `packages.Load` could load the faked std libs, which will be complemented by the `go/ssa/interp` interpreter later.

Even though @adonovan has provided a better approach to use overlay and custom GOROOT in `x/tools/go/ssa/interp` doesn't make sense, however, there isn't a conclusion regarding "whether we should support the usage of fake GOROOTs." Probably we can discuss here more about whether we should support/recommend the usage of fake GOROOTs.

For me, I have tried to add some libraries with my own toolchain under GOROOT because I want to use internal std package features but do not want to use the go linkname directive (which is locked down in 1.23 and higher versions, #67401).

The second point to discuss (related to the custom GOROOT) is whether it's desirable for users to add new packages under GOROOT and let the compiler treat them as standard libraries as well?

@timothy-king @matloob @adonovan
Repository: tauri
Issue: [feat] add some twain scanner support
Labels: type: feature request

### Describe the problem

There is no standard API to scan document from scanner. For some apps it's crucial to have something like scan invoice\print invoice.

### Describe the solution you'd like

I would like to have some native plugin, that will grant access to scan feature of host system

### Alternatives considered

there are some paid solutions, like: https://www.dynamsoft.com/codepool/tauri-document-scanning-desktop-app.html

### Additional context

https://twaindirect.org/twain-direct/
Repository: kubernetes
Issue: SharedIndexInformer not calling event handlers during the first resync
Labels: sig/api-machinery,triage/accepted

This issue is the root cause for https://github.com/argoproj/argo-workflows/issues/10947

Based on my tests, the issue was introduced between client-go `v0.24.0-alpha.1` and `v0.24.0-alpha.2`.

Seems like when the first resync happens (20 minutes in case of argo-workflows), the event handlers are not being called.

I was able to identify a potential change that introduced this: https://github.com/kubernetes/client-go/commit/54928eef9f824667b23a938188498992d437156a#diff-dbac68d65bbc9814c2336df6ee91f22e807d84a9127a4d34a8b39c5657d0e447L551

Looking at the code, there is small behavior change when evaluating the isSync flag:
- resource version was checked only when `d.Type == Replaced`. Now it's being evaluated on all updates
- the `d.Type == Sync` set the isSync to true
- for any other cases: isSync is false

All an in one, there might be a chance of falsely setting isSync to true.

This flag is being used in `distribute`, which conditionally calls the listeners.

The issue also reproduces with latest client-go version: v0.29.0-alpha.2