sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Cannot highlight U+200B and unhighlight multiple languages at the same time
Labels: bug,unicode-highlight

<!-- ⚠️⚠️ 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.76.0
- OS Version: Windows 11 22H2

Steps to Reproduce:

1. Input U+200B​ and some unicode characters with multiple languages.

```markdown
U+200B->​<-U+200B

- test
- 测试
- テスト
- тест
```

2. If both .invisibleCharacters and .nonBasicASCII are true, then

![image](https://user-images.githubusercontent.com/31954237/223178946-229f9f36-7441-4397-9cef-d0a677e74eca.png)

3. However, if .invisibleCharacters is true, and .nonBasicASCII is false, then

![image](https://user-images.githubusercontent.com/31954237/223181009-c51780b3-510c-48ef-9d28-cb5fe923a124.png)

.code-workspace: 

```json
{
    "folders": [
        {
            "path": ".\\",
            "name": "Test"
        }
    ],
    "settings": {
        "editor.unicodeHighlight.includeStrings": true,
        "editor.unicodeHighlight.invisibleCharacters": true,
        "editor.unicodeHighlight.nonBasicASCII": true,
        "editor.unicodeHighlight.allowedLocales": {
            "_os": true,
            "_vscode": true,
            "zh_cn": true,
            "ja": true,
            "ja-jp": true,
            "ru": true,
            "ru-ru": true,
        },
        "editor.unicodeHighlight.ambiguousCharacters": false,
        "editor.unicodeHighlight.includeComments": true,
    }
}
```

It seems that there is no document related to `editor.unicodeHighlight.allowedLocales` standard input, so it is written according to the [Visual Studio Code Language ID](https://github.com/microsoft/vscode-loc), If there is anything wrong, please correct it.
Repository: godot
Issue: FileDialog and the Window node generally stuck in the left upper corner
Labels: bug,platform:macos,topic:editor,topic:gui

### Godot version

4.0

### System information

MacOS 13.2

### Issue description

The Filedialog window shows up at the left upper corner. Setting with custom Layout does change it on absolute , but set in a centercontainer node or set on center screen doesn't have any effect



### Steps to reproduce

Add a filedialog Node in a centercontainer
 

### Minimal reproduction project

Add later 
[Archiv.zip](https://github.com/godotengine/godot/files/10908878/Archiv.zip)
Repository: pytorch
Issue: Static size boolean masking
Labels: triaged,module: advanced indexing

### 🐛 Describe the bug

A long standing request is https://github.com/pytorch/pytorch/issues/62320 ; Executorch team has agreed to implement it.

Once this is implemented, we can also get static size boolean masking to work too. The easiest way is to convert the boolean mask into an index tensor. You can use the meta implementation for indexing to do this:

```
@register_meta(aten.index.Tensor)
def meta_index_Tensor(self, indices):
    result: List[Optional[Tensor]] = []
    for i, index in enumerate(indices):
        if index is not None:
            check(
                index.dtype in [torch.long, torch.int, torch.int8, torch.bool],
                lambda: "tensors used as indices must be long, int, byte or bool tensors",
            )
            if index.dtype in [torch.int8, torch.bool]:
                nonzero = index.nonzero()
                k = len(result)
                check(
                    k + index.ndim <= self.ndim,
                    lambda: f"too many indices for tensor of dimension {self.ndim}",
                    IndexError,
                )
                for j in range(index.ndim):
                    check(
                        index.shape[j] == self.shape[k + j],
                        lambda: f"The shape of the mask {index.shape} at index {i} "
                        f"does not match the shape of the indexed tensor {self.shape} at index {k + j}",
                        IndexError,
                    )
                    result.append(nonzero.select(1, j))
            else:
                result.append(index)
        else:
            result.append(index)
    return result

```

The main annoyance is that if there are not enough elements to fill the nonzero, it will be zero padded. For a boolean mask, a zero pad is inappropriate; instead you want an invalid index, and then to fill the indexing op with some placeholder element like 0.

### Versions

master
Repository: TypeScript
Issue: Invalid CommonJS output when transforming a single import declaration into multiple
Labels: Suggestion,Experience Enhancement

# Bug Report

I've created a TypeScript transformer that transforms a single barrel import declaration into multiple deep import declarations.

Eg changing this:
```ts
import { A, B } from 'pkg';
console.log(A, B);
```
Into something like this:
```ts
import { A } from 'pkg/a';
import { B } from 'pkg/b';
console.log(A, B);
```
This works great when emitting ES modules but not when emitting CommonJS.

### 🔎 Search Terms

Transform, import, esm, cjs

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

### 🕗 Version & Regression Information

Tested with 4.9.5 but I suspect that most versions have this behaviour.

<!-- 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:
-->
_______

### ⏯ Playground Link

Since Playground doesn't have support for transforms I don't have a playground link.
<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->

### 💻 Code

Not sure what to post here, any custom transform that replaces a single import declaration into multiple behave this way.

### 🙁 Actual behavior

When calling `ts.setOriginalNode(newNode, node)` for all new import declarations when emitted CJS code uses the same variable for all statements like this:
```ts
var pkg_1 = require('pkg/a');
var pkg_1 = require('pkg/b');
console.log(pkg_1.A, pkg_1.B);
```

That is, multiple new nodes having the same, single node as their original node.

When not calling `ts.setOriginalNode()` at all the ES output is fine but the CJS output is even more broken with something like:
```ts
var a_1 = require('pkg/a');
var b_1 = require('pkg/b');
console.log(pkg_1.A, pkg_1.B);
```


<!-- What happened, and why it was wrong -->

### 🙂 Expected behavior

I'm not sure how this should be handled but I would have liked to be able to connect multiple new nodes to a single original node and have the CommonJS transform see that and use different require variables. With output that looks something like this:

```ts
var pkg_1 = require('pkg/a');
var pkg_2 = require('pkg/b');
console.log(pkg_1.A, pkg_2.B);
```

<!-- What you expected to happen instead, and why -->
Repository: next.js
Issue: Server Components fetch() throws in page.tsx
Labels: examples

### Verify canary release

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

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home
    Binaries:
      Node: 18.14.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.2.3
      eslint-config-next: 13.2.1
      react: 18.2.0
      react-dom: 18.2.0

warn  - Latest canary version not detected, detected: "13.2.3", newest: "13.2.4-canary.4".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue
```


### Which example does this report relate to?

async/await in Server Components

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

Opera

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

_No response_

### Describe the Bug

In your page.tsx file.
fetch() always throws : TypeError: Failed to parse URL from /api/getCards
It also throws if you using axios.

### Expected Behavior

As per example on website https://beta.nextjs.org/docs/data-fetching/fetching#asyncawait-in-server-components
It uses the page.tsx file.
![error](https://user-images.githubusercontent.com/87245593/223191093-d37210e0-1ce6-43e3-8591-bc87bd6daf2f.PNG)

It should work as expected.
How it doesn't.


### To Reproduce

Create a page.tsxx 
And attempt the following code

import React from 'react';
async function HomePageChild() {
  const data = await fetch('/api/getCards') // throws "TypeError: Failed to parse URL from /api/getCards"
  return (
    <> Child</>
  )

};


export default HomePageChild
Repository: vscode
Issue: tasks.json npm script does not work with arguments on Mac
Labels: bug,tasks,macos

<!-- ⚠️⚠️ 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/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.75.1
- OS Version: macOS Monterey 12.6.3

Steps to Reproduce:

It's the same as issue #115876 except it's specifically on Mac.  The same task.json works on Windows 10.
Repository: rust
Issue: --print=native-static-libs produces no output for `#![no_std]` staticlib
Labels: A-linkage,T-compiler,C-bug

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

(spawned off of https://github.com/rust-lang/rust/issues/53281#issuecomment-1456648970 )
I tried this code:

```rust
// compile-args: -Cpanic=abort --print=native-static-libs /tmp/hello.rs
#![crate_type="staticlib"]

#![no_std]

use core::panic::PanicInfo;
#[panic_handler]
fn panic(_info: &PanicInfo) -> ! {
    loop { }
}
```

I expected to see this happen: 

A line of output that includes the prefix:

```
note: Link against the following native artifacts when linking against this static library. The order and any duplication can be significant on some platforms.

note: native-static-libs: [...]
```

Instead, this happened:

No output.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.70.0-nightly (7820b62d2 2023-03-05)
binary: rustc
commit-hash: 7820b62d20bc548096d4632a3487987308cb4b5d
commit-date: 2023-03-05
host: x86_64-unknown-linux-gnu
release: 1.70.0-nightly
LLVM version: 15.0.7
```
Repository: flutter
Issue: Optimize search for the default App bundle on macOS
Labels: platform-mac,a: desktop,P3,team-macos,triaged-macos

`+[NSBundle bundleWithIdentifier]` is slow, and scales to the size of the app.  On iOS https://github.com/flutter/engine/pull/39975 searches within the `privateFrameworksURL` where the default bundle is expected to be located first, then falls back to `+bundleWithIdentifier`. When tested internally, this improves startup of `customer: chalk` by 30% on iOS - see http://shortn/_WcifhO48X6.

I suspect macOS could benefit from the same optimization:

https://github.com/flutter/engine/blob/706fd9cc2dd83e84018e6584f0fc595b8c489457/shell/platform/darwin/macos/framework/Source/FlutterDartProject.mm#L29

@jiahaog said:
> I don't have a setup for profiling macOS apps now so I can't say for sure now, but I would expect this to also happen there – we should perhaps follow up separately. It seems like Chrome also encountered this problem on macOS - see `GetFrameworkBundlePath` (L156) of https://chromium.googlesource.com/chromium/src/+/master/chrome/common/chrome_paths_mac.mm.


https://github.com/flutter/engine/pull/39975#issuecomment-1455570897

cc @cbracken
Repository: vscode
Issue: Auto-attach remote session
Labels: feature-request,debug

I'm developing code for an external device that is not under my control. To run my code, I run a local (provided) nodejs application which packs the code, sends it to the remote device and runs it in a sandbox. stdout and stderr are forwarded to the local console.
I'm able to start a debugger session by including: `require('inspector').open(9223, address, false);` in the app startup code and I can attach to it with the vscode Javascript debugger.

I use this launch.json right now:
```
{
    "version": "0.2.0",
    "configurations": [
    {
        "name": "Launch app",
        "type": "node",
        "request": "launch",
        "cwd": "${workspaceFolder}",
        "runtimeExecutable": "homey",
        "args": ["app", "run"],
	"outputCapture":"std",
	"serverReadyAction":{
            "pattern": "Debugger listening on",
            "action": "startDebugging",
            "name": "Attach to Homey"
        }
    },
    {
        "name": "Attach to Homey",
	"type": "node",
	"request": "attach",
	"address": "192.168.55.34",
	"port": 9223,
	"localRoot": "${workspaceFolder}",
	"remoteRoot": "/"
    } ]
}
```

It works but has a few problems;
* The IP and port are hard-coded in the json file, every developer uses another IP to connect to
* Vscode doesn't automatically open the new console window for the 'attach' tab. I have to wait for the second window to show up in the drop-down list and change to it
* Without `outputCapture` set to std, all output of the original command is discarded. App crashes and some other errors are missed by the debugger. With `outputCapture` set to std, most output is duplicated in both console windows. (Though I don't think this can be fixed by the vscode debugger)

I can think a few methods to fix the first two issues;
* Allow the serverReadyAction pattern to set environment variables (to be used in the attach action) and auto-switch to the new debugger window
* Auto-attach a debugger when `Debugger listening on w[s://192.168.55.34:9223]()/4b82a989-edd5-4d28-b0df-7b4439338591` is printed in the console and switch to it. (Or allow setting a custom pattern to start the debugger)
* Use a task to start the app and allow the 'Problem Matcher' (or something similar) to start a debugging session with ip and port provided by the pattern
Repository: flutter
Issue: Gradle wrapper download failures should be classified as an infra flake.
Labels: platform-android,P1,c: flake,team-android,:hourglass_flowing_sand:

See https://github.com/flutter/flutter/issues/121711

The flakes detected in that bug were all around failures to download gradle via the gradle wrapper - the test script gets to the point where it's hitting services.gradle.org and then gets terminated on a 30 minute timeout.

I think there are two things we need to do:

1. Make these get categorized as infra flakes somehow. This is not a flake in the logic of the test, it's a flake in the ability to get build tools from third party services.
2. Consider moving gradle-7.3.3-all.zip to CIPD or GCS and pointing our gradle-wrapper.properties to that. That should be less flaky and help make these failures happen less often. @reidbaker may have thoughts on how important it is to ever have integration testing hitting services.gradle.org - right now we probably have dozens of tests doing that when we really need 1 (if any at all).
Repository: flutter
Issue: Dart-based tests in the engine use `vm:external-name` instead of using `@Native`.
Labels: a: tests,engine,P2,c: tech-debt,team-engine,triaged-engine

We've migrated dart:ui to use `@FfiNative` annotations for native calls, but tests still use the older style `@pragma('vm:external-name)` annotations and various dart_api.h calls realted to Dart_Arguments.

We should make the tests use the same mechanism as the runtime code to make sure that tests exercise the relevant parts of tonic/dart:ffi.
Repository: rust
Issue: Passing a lifetime GAT to a closure can cause the compiler to run indefinitely
Labels: T-compiler,C-bug,I-hang,fixed-by-next-solver,A-GATs

<!--
Thank you for finding an Internal Compiler Error! 🧊  If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.
http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/
-->

### Code

I tried to pair it down more, but so far this is the smallest version I could get to cause the issue:

```Rust
pub trait LendingIterator {
    type Item<'a>
    where
        Self: 'a;

    fn next<'a>(&'a mut self) -> Self::Item<'a>
    where
        Self: 'a;
        
    
    fn filter<P>(self, predicate: P) -> Filter<Self, P>
    where
        Self: Sized,
        for<'a> P: FnMut(&Self::Item<'a>) -> bool,
    {
        Filter {
            stream: self,
            predicate,
        }
    }
}

#[derive(Clone, Debug)]
pub struct Filter<S, P> {
    stream: S,
    predicate: P,
}

impl<S, P> LendingIterator for Filter<S, P>
where
    S: LendingIterator + Unpin,
    for<'a> P: FnMut(&Self::Item<'a>) -> bool,
{
    type Item<'a> = S::Item<'a> where S: 'a;

    fn next<'a>(&'a mut self) -> Self::Item<'a>
    where
        Self: 'a,
    {
        loop {
            let next = self.stream.next()?;
            if (self.predicate)(&next) {
                return Some(());
            }
        }
    }
}
```

https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=5042463788e49bf6964dfa80dcb5b9bb

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.70.0-nightly (7820b62d2 2023-03-05)
binary: rustc
commit-hash: 7820b62d20bc548096d4632a3487987308cb4b5d
commit-date: 2023-03-05
host: x86_64-pc-windows-msvc
release: 1.70.0-nightly
LLVM version: 15.0.7
```
and
```
rustc 1.67.1 (d5a82bbd2 2023-02-07)
binary: rustc
commit-hash: d5a82bbd26e1ad8b7401f6a718a9c57c96905483
commit-date: 2023-02-07
host: x86_64-pc-windows-gnu
release: 1.67.1
LLVM version: 15.0.6
```

### Error output

There isn't any error output, since the compiler runs indefinitely when encountering this issue.
Repository: flutter
Issue: [flutter_tools] allow user to configure path to cocoapods via `flutter config --cocoa-pods-dir`
Labels: c: new feature,tool,c: proposal,P2,team-tool,triaged-tool

For context see: https://github.com/Dart-Code/Dart-Code/issues/4404

TL;DR if the user installed cocoapods via homebrew, it may be on their shell path (and thus pass `flutter doctor` run from the terminal) but not on the path when they launch VSCode from their OS launcher.
Repository: go
Issue: all: test failures on `linux/s390x`
Labels: Testing,NeedsInvestigation,arch-s390x,umbrella

```
#!watchflakes
default <- goos == "linux" && goarch == "s390x" && ! (pkg ~ `x/pkgsite`)
```

I'm seeing another cluster of failures on the `linux-s390x-ibm` builder, particularly for `x/tools/gopls`. To try to reduce the number of duplicates filed by `watchflakes`, I'm filing this as a catchall default. If the failures posted here are not due to transitory builder configuration issues, separate issues should be filed for them manually.

(attn @golang/s390x)
Repository: pytorch
Issue: make_fx tracing with dynamic shapes should also disable_slice_optimization
Labels: triaged,enhancement,oncall: pt2,module: dynamic shapes,module: aotdispatch,oncall: export,module: pt2-dispatcher

### 🐛 Describe the bug

This will help remove some guards related to slicing.

Test case:

```
diff --git a/test/test_proxy_tensor.py b/test/test_proxy_tensor.py
index d1f5de669b3..d8f2d6f1c0b 100644
--- a/test/test_proxy_tensor.py
+++ b/test/test_proxy_tensor.py
@@ -970,6 +970,16 @@ def forward(self, crop_camera_1, mask_1):
     index_put_ = torch.ops.aten.index_put_.default(crop_camera_1, [mask_1], view_2);  crop_camera_1 = mask_1 = view_2 = None
     return None""")
 
+    def test_unbacked_slice(self):
+        def f(x, m):
+            x = x[m]
+            return x[slice(None, None, None), slice(None, None, None), slice(None, 2, None)]
+
+        make_fx(f, tracing_mode="symbolic")(
+            torch.randn((12, 3, 3)),
+            torch.randint(0, 2, (12,), dtype=torch.bool)
+        )
+
     @unittest.skipIf(not USE_TORCHVISION, "test requires torchvision")
     def test_unbacked_batch_resnet(self):
         mod = torchvision.models.resnet18()
```

### Versions

master

cc @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4 @wconstab
Repository: flutter
Issue: [flutter_tools] confusing log output when compiling flutter tool
Labels: tool,P2,team-tool,triaged-tool

See the following terminal session (the `^C` at the end is when I sent SIGINT to the process, as it was apparently hanging indefinitely)

```
~/git/flutter/packages/flutter_tools$ git checkout master
Already on 'master'
Your branch is up to date with 'upstream/master'.
~/git/flutter/packages/flutter_tools$ git pull upstream master
From github.com:flutter/flutter
 * branch                  master     -> FETCH_HEAD
Already up to date.
~/git/flutter/packages/flutter_tools$ git rev-parse HEAD
57c7aa53c178f722aec19a76a60552e78ad09997
~/git/flutter/packages/flutter_tools$ flutter
Building flutter tool...
Resolving dependencies... (1.3s)
Got dependencies.
^C
```