sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: svelte
Issue: Track binding values
Labels: feature request,perf

### Describe the problem

There are many cases where knowing what values a binding could potentially hold would allow us to generate more optimal code. For example, in a situation like [this](https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAE0WNwQrCMBBEfyUuQhWE3mNa8NazV-uhtltcSJOl2RSk5N9N8OBx3sxjdpjJYgD92MENC4KGGzNcQD5cQtjQCuYcfFzHQkwYV2Jpe9eLRVHFUo06BhkET9Wdxnd1vvbO1P-hM-Q4inqRm_Q22IjNXryk6lwbbju01qsfO5ia2_y4-Ilmwgm0rBHTM30BG52stawAAAA=)...

```svelte
<script>
  let name = $state('Rich');
</script>

<input bind:value={name} />
<p>Hello {name}!</p>
```

...we don't need the `?? ""` in the generated code, because we can determine that `name` is always defined:

```js
$.template_effect(() => $.set_text(text, `Hello ${$.get(name) ?? ""}!`));
```

The same goes for references to an index (and, if we were sophisticated enough, the item itself) inside an each block:

```svelte
{#each 'abc' as l, i}
  <p>{i}: {l}</p>
{/each}
```

```diff
-$.template_effect(() => $.set_text(text, `${i ?? ""}: ${l ?? ""}`));
+$.template_effect(() => $.set_text(text, `${i}: ${l ?? ""}`));
```

Post-#13264, it would also allow us to avoid creating effects in cases where we know an expression doesn't contain state. Right now, code like this...

```svelte
<script>
  let min = 0;
  let max = 100;
  let number = 50;
</script>

<p>{Math.max(min, Math.min(max, number))}</p>
```

...yields output like this...

```js
var p = root();

p.textContent = Math.max(min, Math.min(max, number));
```

...but as of #13264 yields this unnecessary overhead:

```js
var p = root();
var text = $.child(p);

$.template_effect(() => $.set_text(text, Math.max(min, Math.min(max, number))));
$.reset(p);
```

### Describe the proposed solution

Track all the assignments (along with the scopes in which they occur) when first analysing bindings, so that we can later determine things like:

- is this binding always defined? (if so, don't need the `?? ""`)
- could this binding hold a reference to a state proxy? (if not, and it's not a state binding, no need to create effects)
- do we know that such-and-such an expression is always truthy or always falsy? 
- can this binding be hoisted somewhere?

There are limits to what we can know with such an analysis — often, the answer to 'what could this value be?' is `:shrug:`. It's no substitute for knowing the entirety of your program (though we could one day augment it with knowledge of prop values and imports, for example), and nor is it a replacement for an type system (though unlike types, code can't lie about the range of possible values). But it's a relatively simple and cheap way to get a decent chunk of the benefits of a more comprehensive system.

### Importance

nice to have
Repository: vscode
Issue: 'search' option in fileLocation of problemMatcher for Task does not work in Remote Development
Labels: bug,tasks,remote

Type: <b>Bug</b>

I am using VS Code with Remote SSH, where the host PC is Windows, and the remote PC is Linux.
I created the following tasks.json and intentionally caused a warning as a test, but nothing is displayed in the PROBLEMS tab.

```json
{
    "version": "2.0.0",
    "tasks": [
        {
            "type": "cppbuild",
            "label": "Build",
            "command": "/usr/bin/g++",
            "args": [
                "-fdiagnostics-color=always",
                "-I",
                ".",
                "-g",
                "main.cpp",
                "-o",
                "test"
            ],
            "problemMatcher": {
                "base": "$gcc",
                "fileLocation": [
                    "search",
                    {
                        "include": [
                            "${workspaceFolder}"
                        ]
                    }
                ]
            },
            "group": "build"
        }
    ]
}
```

I see the following log in the developer tools console, indicating that the error occurred because the file was not found on the host PC.
The actual file path is '/home/****/workspace/gcctest'.

```
ERR Error: ENOENT: no such file or directory, scandir 'C:\home\****\workspace\gcctest': EntryNotFound (FileSystemError): Error: ENOENT: no such file or directory, scandir 'C:\home\****\workspace\gcctest'
    at P.create (C:\Users\*****\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:63:3704)
    at w (C:\Users\*****\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:63:3824)
    at k.hb (C:\Users\*****\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:69:30688)
    at k.readdir (C:\Users\*****\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:69:23364)
```

When I placed the files in the path indicated on the host PC, the warning was successfully displayed in the PROBLEMS tab.
It seems that the correct behavior should be to search for the files on the remote PC.


VS Code version: Code 1.93.1 (38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40, 2024-09-11T17:20:05.685Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 5.15.153.1-microsoft-standard-WSL2

<details><summary>Extensions (6)</summary>

Extension|Author (truncated)|Version
---|---|---
remote-ssh|ms-|0.114.3
remote-ssh-edit|ms-|0.86.0
remote-wsl|ms-|0.88.3
remote-explorer|ms-|0.4.3
vscode-language-pack-ja|MS-|1.93.2024091109
cpptools|ms-|1.21.6


</details>
<!-- generated by issue reporter -->
Repository: rust
Issue: rustc since 1.36 accepts invalid code after return
Labels: T-lang,T-compiler,C-discussion

<!--
Thank you for filing a regression report! 🐛 A regression is something that changed between versions of Rust but was not supposed to.

Please provide a short summary of the regression, along with any information you feel is relevant to replicate it.
-->

### Code

I tried this code:

```rust
fn foo() -> u8 {
    return 0;
    let a: u8 = 1;
    a = 2; // error: second write to an immutable variable
    return a;
}
fn main() -> () {
    println!("{}", foo());
}
```

**rustc-1.35 rejects the code and says:**
```
error[E0384]: cannot assign twice to immutable variable `a`
 --> <source>:4:5
  |
3 |     let a: u8 = 1;
  |         - first assignment to `a`
4 |     a = 2;
  |     ^^^^^ cannot assign twice to immutable variable
```

**Current rustc accepts the code**

I acknowledge that the invalid write happens in a dead region, but still report it as all rustc versions reject the following code:
```rust
fn foo() -> u8 {
    if true {
        return 0;
    }
    let a: u8 = 1;
    a = 2; // error: second write to an immutable variable
    return a;
}
fn main() -> () {
    println!("{}", foo());
}
```
Repository: rust
Issue: Testing under bootstrap does not work on x86_64 macOS 10.14
Labels: A-testsuite,O-macos,T-bootstrap,C-bug

I tried running this test on 02b1be16c65e5716ade771afde7116ebdfbf9b4a:

```rust
uv run --python 3.10 ./x.py test tests/run-make/apple-deployment-target
```

The compiler builds fine, but the test fails with the following message:

```
thread 'main' panicked at $WORKSPACE/tests/run-make/apple-deployment-target/rmake.rs:56:9:
failed to get output of finished process: Os { code: 2, kind: NotFound, message: "No such file or directory" }
```

Which is really weird, because every file it uses is clearly available when I look through the directory.

I'm not yet sure if this is due to something specific to my setup, perhaps bootstrap doesn't like `uv`? Filing this bug mostly for myself to keep track of.

@rustbot label O-macos
Repository: ui
Issue: [bug]: unable to get local issuer certificate
Labels: bug

### Describe the bug

PS C:\Users\mr63\OneDrive my-app> npx shadcn@latest init
✔ Preflight checks.
✔ Verifying framework. Found Next.js.
✔ Validating Tailwind CSS.
✔ Validating import alias.


Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

request to https://ui.shadcn.com/r/styles/index.json failed, reason: unable to get local issuer certificate


### Affected component/components

all

### How to reproduce

npx shadcn@latest init

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
windows
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: pytorch
Issue: Dynamo: warning when we incorrectly inline autograd.Function.backward due to subclass gradients
Labels: triaged,tensor subclass,oncall: pt2,module: dynamo,module: pt2-dispatcher

(originally reported by @bdhirsh. Below quoted verbatum)

More details + repro in [internal xpost](https://fb.workplace.com/groups/1075192433118967/posts/1368547360450138/?comment_id=1368580870446787).

Today, when dynamo sees an autograd.Function it runs speculate_subgraph() on the backward. The backward takes in extra grad_output arguments that do not exist at compile time, so dynamo constructs fake inputs on the fly by assuming that they have the same metadata.

This can be a problem: if a user has a backward function that specializes a conditional on that (subclass) metadata, then dynamo can burn in the wrong side of the conditional. At runtime of the backward, we don't really have any way of "undoing" dynamo's wrong decision. But one thing we can look into is figuring out how to warn when this situations happens. The user has a few levers at their disposal, like allow_in_graphing their autograd.Function to prevent inlining by dynamo.

There is some nuance in how we should decide to emit this warning:

(1) At compile time in AOTDispatch: AOTDispatch "also" has to guess (subclass) metadata of the backward, but it only needs to guess at the graph boundary: the actual gradients that get plumbed into the user's custom autograd.Function.backward() when we trace out a joint graph will be whatever metadata gets "propagated" into the backward given AOTAutograd's initial guess. For subclasses that have a very short life-time in the graph like StructuredSparseTensor (inputs/outputs of the graph are all dense, sparsity shows up very briefly as an intermediate), this makes AOTAutograd's guess a bit "better", as long as you capture a large enough graph. So one option is to warn if dynamo and AOTAutograd came to different conclusions at compile time about what the subclass-ness of the gradient was. This is a bit easier to implement, but has the slight risk of our warning being wrong (both false positive and false negative)

(2) At runtime: when the backward is running, we have "true" information about whether the value that dynamo chose to inline with was right/wrong. This will give us a fully correct warning, but will be a bit more work to implement. At compile time, we need to figure out how to get "given dynamo's guess about the subclass-ness of its autograd.Function.backward input, what would be a correct/incorrect subclass metadata for the backward graph's grad_outputs".

If we are going through the work of emitting a warning, (2) probably seems better.

cc @ezyang @albanD @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames @rec @bdhirsh
Repository: deno
Issue: Config path not included when using deno install --config but added a default name instead
Labels: bug,config

From https://github.com/denoland/deno/issues/17834#issuecomment-1438861398

Version: Deno 1.46.3

Let suppose my project name is `cat`, when running the following script:

`deno install -g -c /some/absolute/path/to/deno.json mod.ts`

The generated installed file looks like this:

```zsh
#!/bin/sh
# generated by deno install
exec deno run --config /home/my_user/.deno/bin/.cat.deno.json 'file:///path/to/my/project/mod.ts' "$@"
```

Basically the path provided in `--config`/`-c` is not taken into account. Is this expected? Should I make a copy of my deno.json into the deno bin folder named `.cat.deno.json`?

Thanks
Repository: vscode
Issue: URI not properly serialized when sent to webworker
Labels: feature-request,debt,engineering,uri

1. open vscode.dev and open a local folder.
2. Set a breakpoint in `localFileSearch.ts`, on the first line of `$searchDirectory` 
3. Run a search.
4. Notice that, when the `folderQuery` arrives at `$searchDirectory`, it does not have a `$mid` field in its `folder` field. This causes `revive(folderQuery)` to not properly deserialize the URI. 

I found this when debugging https://github.com/microsoft/vscode/issues/227742. I have a workaround for this linked bug, but for more long-term support, we should figure out what's happening here.
Repository: flutter
Issue: `total_ui_gc_time:dynamic_path_tessellation_perf_ios__timeline_summary` 46% regression 
Labels: c: performance,P2,team-engine,triaged-engine

There has been a regression in `total_ui_gc_time` introduced in https://github.com/flutter/flutter/pull/155194.

## dashboard
https://flutter-flutter-perf.skia.org/e/?keys=Xc1b21aeae1d1cb98303548111d2f8ac3&selected=commit%3D42577%26name%3D%252Carch%253Dintel%252Cbranch%253Dmaster%252Cconfig%253Ddefault%252Cdevice_type%253DiPhone_11%252Cdevice_version%253Dnone%252Chost_type%253Dmac%252Csub_result%253Dtotal_ui_gc_time%252Ctest%253Ddynamic_path_tessellation_perf_ios__timeline_summary%252C&xbaroffset=42577
Repository: godot
Issue: changing the mesh in a meshinstance in a remote scene makes it empty
Labels: bug,topic:editor,confirmed

### Tested versions

4.2.2 stable, 4.3 stable

### System information

Windows 10

### Issue description

Trying to change the mesh in a mesh instance while the game is running from the remote tab, removes the mesh / resets its state to empty in the game. Setting it in the 'local' tab works as expected.

I wanted to test a different mesh at runtime, in my original project the scene was instanced by code and expected that the remote changed mesh would be the mesh that I selected (at least in the game window, and back no normal on the next start)

https://github.com/user-attachments/assets/ee260b4c-db64-4f0d-bd49-c7d359b327e4



### Steps to reproduce

 try to change the mesh in the mesh instance when remote debugging, it could even be the same obj as already in there

### Minimal reproduction project (MRP)

Originally experienced with my current game project in godot 4.2.2 stable, tried then with 4.3 stable and finally with a brand new project
Repository: PowerToys
Issue: Allow "Ctrl+Shift+Alt+Win" combination in Keyboard Manager - Remap a shortcut.
Labels: Needs-Triage

### Description of the new feature / enhancement

The combination "Ctrl+Shift+Alt+Win" is not allowed in Keyboard Manager - Remap a shortcut.
The program expects another "neutral" key to form a valid combination, although this combination is valid by itself and triggers a bloatware app by default.

### Scenario when this would be used?

I have a Microsoft bluetooth keyboard (similar to [this one](https://m.media-amazon.com/images/I/61sDEUU00CL._AC_UF894,1000_QL80_.jpg)) with an annoying button near the rightmost Alt key.
It is actually mapped to the following combination - "Ctrl+Shift+Alt+Win", which opens up the "Microsoft 365 (Office)" program.
This key is always pressed by accident (because why otherwise) and the window that pops up interferes with my work, so using PowerToys to disable this key/remap to another useful program would be very nice!


### Supporting information

_No response_
Repository: godot
Issue: Godot runs the game when exporting.
Labels: bug,platform:windows,needs testing,topic:export

### Tested versions

v4.4.dev2.official [97ef3c837]
But it happens in 4.3 too

### System information

Godot v4.4.dev2 - Windows 10.0.19045 - OpenGL 3 (Compatibility) - NVIDIA GeForce GTX 960 (NVIDIA; 32.0.15.5612) - Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8 Threads)

### Issue description

Godot runs the game when I export.
Happens on all buttons, debug / no debug. Compatibility, Forward+ and Mobile.

### Steps to reproduce

1) In the export menu under Application, turn on Modify Resources
2) Export

(I don't have rcedit set up)

![image](https://github.com/user-attachments/assets/377f31b2-87a9-4ec1-8575-625defcd1646)


https://github.com/user-attachments/assets/e672c32a-b337-4366-8e99-7855ac12d22f



### Minimal reproduction project (MRP)

[mrp.zip](https://github.com/user-attachments/files/17017027/mrp.zip)
Repository: excalidraw
Issue: Duplication of element while dragging with switching other software on Windows (because Alt + Tab)
Labels: good first issue


https://github.com/user-attachments/assets/474d6ffa-1fa9-4599-af79-95ff9a7fae30

whenever i select element, drag that element and switch between software ( for window ALT + TAB ) at the same time, it duplicate.
Repository: go
Issue: proposal: go/types: add Import, Export functions
Labels: Proposal

[Status: WORK IN PROGRESS. Do not review yet.]

**Background:** The package [golang.org/x/tools/go/gcexportdata](https://pkg.go.dev/golang.org/x/tools/go/gcexportdata) provides two functions, Write and Read. As described in https://github.com/golang/go/issues/68898, they serve two purposes:

1. a serialization mechanism for types.Package values. They assume that writer and reader are compiled from the same source code; there is no protocol stability.
2. a mechanism to read export data written by last "tip + 2" releases of the Go compiler.

These two purposes are quite independent, and the actual protocols they use are unrelated. (The first uses "indexed" form, the second "unified".) Much of the challenge of maintaining go/types and x/tools/go/gcexportdata comes from version skew between std and x/tools: witness the number of delicate changes to both made recently to support materialized Alias types, and then the addition of type parameters to aliases. In this instance, the skew is unnecessary as the codec can be tightly coupled go/types and needn't support any other versions.

**Proposal:** We propose to add the read and write functions to go/types itself:

```go
package types // "go/types"

// Export returns a serialized form of pkg that can be read by the same version of [Import].
// The encoding is not specified and may change at any time.
func Export(fset *token.FileSet, pkg *Package, opts ExportOptions) ([]byte, error)

type ExportOptions struct {
    Deep bool // encode information about dependencies too
}

// Import returns the package described by data,
// which must have been produced by the same version of [Export].
// It calls importDeps at most once to obtain all needed direct dependencies (perhaps in parallel).
func Import(fset *token.FileSet, data []byte, importDeps importDepsFunc, path string, opts ImportOptions) (*Package, error)

type ImportOptions struct { /* for future use */ }

type importDepsFunc = func(packagePaths []string) ([]*types.Package, error)
```

This API is a synthesis of gcexportdata and internal/gcimporter.{Im,Ex}portShallow, which are used by gopls for "shallow" encodings.

Open questions:
- The implementation of Export and Import depend on objectpath. How would this work in go/types?
- Assuming the legacy uses of Read for files produced by Write (not cmd/compile) would be supported by (eventually) delegating to types.Import, that would break the implicit promise that newer versions of Read can consume files produced by older versions of Write, which is not something that `types.Import,Export` would guarantee. How disruptive is that likely to be? I suspect that no existing tools rely on this implicit promise because we often temporarily break it during the course of normal development (e.g. adding generics, type aliases) over many CLs.

@griesemer @findleyr @timothy-king

@znkr (for shallow export data)
Repository: flutter
Issue: `CupertinoAlertDialog` and `CupertinoActionSheet` should update highlight area upon reparenting or relayouting
Labels: framework,f: cupertino,P3,team-framework,triaged-framework

`CupertinoAlertDialog` and `CupertinoActionSheet` uses a private class, `_TargetSelectionGestureRecognizer`, to recognize the widgets that a pointer moves into, which basically reimplements a simplified `MouseTracker`.

However, it misses the following features from `MouseTracker`:
* If the app is relayouted, then the pointer should reperform hit testing, since the widgets might have moved around.

This shouldn't be problem in typical usage of dialogs and action sheets, but might matter for customized cases.

In fact, we should probably reuse the code of `MouseTracker` for `_TargetSelectionGestureRecognizer`, or allow touch pointers to calculate hovering when needed. This is not done for now due to the complexity it might involve, and the performance cost that it might introduce.
Repository: go
Issue: x/tools/gopls: no completions provided in some seemingly straightforward cases
Labels: gopls,Tools,gopls/parsing,gopls/completion

### gopls version

```
Build info
----------
golang.org/x/tools/gopls v0.16.2
    golang.org/x/tools/gopls@v0.16.2 h1:K1z03MlikHfaMTtG01cUeL5FAOTJnITuNe0TWOcg8tM=
    github.com/BurntSushi/toml@v1.2.1 h1:9F2/+DoOYIOksmaJFPw1tGFy1eDnIJXg+UHjuD8lTak=
    github.com/google/go-cmp@v0.6.0 h1:ofyhxvXcZhMsU5ulbFiLKl/XBFqE1GSq7atu8tAmTRI=
    golang.org/x/exp/typeparams@v0.0.0-20221212164502-fae10dda9338 h1:2O2DON6y3XMJiQRAS1UWU+54aec2uopH3x7MAiqGW6Y=
    golang.org/x/mod@v0.20.0 h1:utOm6MM3R3dnawAiJgn0y+xvuYRsm1RKM/4giyfDgV0=
    golang.org/x/sync@v0.8.0 h1:3NFvSEYkUoMifnESzZl15y791HH1qU2xm6eCJU5ZPXQ=
    golang.org/x/telemetry@v0.0.0-20240829154258-f29ab539cc98 h1:Wm3cG5X6sZ0RSVRc/H1/sciC4AT6HAKgLCSH2lbpR/c=
    golang.org/x/text@v0.16.0 h1:a94ExnEXNtEwYLGJSIUxnWoxoRz/ZcCsV63ROupILh4=
    golang.org/x/tools@v0.22.1-0.20240829175637-39126e24d653 h1:6bJEg2w2kUHWlfdJaESYsmNfI1LKAZQi6zCa7LUn7eI=
    golang.org/x/vuln@v1.0.4 h1:SP0mPeg2PmGCu03V+61EcQiOjmpri2XijexKdzv8Z1I=
    honnef.co/go/tools@v0.4.7 h1:9MDAWxMoSnB6QoSqiVr7P5mtkT9pOc1kSxchzPCnqJs=
    mvdan.cc/gofumpt@v0.6.0 h1:G3QvahNDmpD+Aek/bNOLrFR2XC6ZAdo62dZu65gmwGo=
    mvdan.cc/xurls/v2@v2.5.0 h1:lyBNOm8Wo71UknhUs4QTFUNNMyxy2JEIaKKo0RWOh+8=
go: go1.23.0
```

### go env

```shell
not relevant
```


### What did you do?

I have a text file like this, where `|` represents the cursor position:

```
package main

func main() {
	foobar := []int{1, 2, 3}
	if len(foo|
}
```

### What did you see happen?

I invoked completion (the LSP action is `textDocument/completion`) and got zero results.

I also used the gopls rpc trace log to verify that gopls got the request and was sending back zero items, so it's not related to some editor integration issue.

### What did you expect to see?

I want to see `foobar` as a suggested completion (probably the only one).

Here are some similar situations where `foobar` *is* the suggested completion:

```
package main

func main() {
	foobar := []int{1, 2, 3}
	foo|
}
```

```
package main

func main() {
	foobar := []int{1, 2, 3}
	len(foo|
}
```

```
package main

func main() {
	foobar := []int{1, 2, 3}
	if foo|
}
```

```
package main

func main() {
	foobar := []int{1, 2, 3}
	if len(foo|)
}
```

### Editor and settings

_No response_

### Logs

The completion trace request/response looks like this:

```
[Trace - 11:52:32.791 AM] Sending request 'textDocument/completion - (22)'.
Params: {"position":{"character":12,"line":8},"textDocument":{"uri":"file:\/\/\/..path elided...\/x\/x.go"}}


[Trace - 11:52:32.792 AM] Received response 'textDocument/completion - (22)' in 0ms.
Result: {"isIncomplete":true,"items":[]}
```