sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: runtime, cmd/compile: share more constants
Labels: compiler/runtime

[CL 462115](https://go.dev/cl/462115) merged a few constants that were duplicated between several runtime-related and toolchain-related packages into a single `internal/abi` package. This is an internal cleanup tracking issue for merging more of these constants.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Supports multi-machine deployment，Amortize the GPU computing pressure
Labels: enhancement

### Is there an existing issue for this?

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

### What would your feature do ?

Supports multi-machine deployment，Amortize the GPU computing pressure

### Proposed workflow

1. service registration
2. service discovery
3. map reduce


### Additional information

_No response_
Repository: next.js
Issue: _error is treated as a serverless function even though the edge runtime is specified (in Pages)
Labels: bug,Runtime

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.16.0
      npm: 8.11.0
      Yarn: 1.22.15
      pnpm: 6.11.0
    Relevant packages:
      next: 13.3.1-canary.9
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue

https://github.com/dario-piotrowicz/nextjs-_error-edge-demo

### To Reproduce

Run `npm run build` and view the `.next/server/middleware-manifest.json` file

### Describe the Bug

the `_error` is not present in the middleware manifest thus it is being treated as a serverless function instead of an edge route, basically ignoring the user provided config

### Expected Behavior

`_error` should be present as a field of the functions object inside the middleware manifest thus it will be deployed as an edge route as requested by the user provided config

### Additional Information

- Seems like this only happens with the Pages routing, App routing seems to be fine

- By looking at the Vercel cli source code (specifically [here]( https://github.com/vercel/vercel/blob/ec89436417c0bead4bf750192b19e9a0137d3b83/packages/next/src/index.ts#L2692)) it looks to me like the way of discerning if a function is a serverless one or an edge one is to check their presence in the middleware manifest, so I based the details above on this assumption

- Regardless on the middleware manifest I noticed the issue when running `vercel build` since, as you can see from the following screenshot generates a node serverless function instead of an edge one:
![Screenshot 2023-04-17 at 14 34 21](https://user-images.githubusercontent.com/61631103/232540590-a0bc0be6-76f9-4006-bc9b-fef90710bc8e.png)
Repository: next.js
Issue: Prod server fails with ipv6 when using middleware
Labels: bug

### Verify canary release

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

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.2.0: Fri Nov 11 02:03:51 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.15.0
      npm: 9.5.0
      Yarn: 1.22.18
      pnpm: 7.30.5
    Relevant packages:
      next: 13.3.1-canary.9
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


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

_No response_

### Link to the code that reproduces this issue

https://github.com/ferdinandhummel-gph/next-middleware-ipv6.git

### To Reproduce

Create project
```
pnpm create next-app ip6-middleware
cd ip6-middleware
``` 

Add middleware
``` 
echo "export function middleware() { console.log('hello from middleware') }" > middleware.ts
``` 

Build & run on ipv6
``` 
pnpm build
pnpm start --hostname ::
``` 



### Describe the Bug

The presents of middleware does break when serving via ipv6. When present the response will always result in a 404 page. There is no error showing in the terminal, also the middleware function does not run.

`next start --hostname 0.0.0.0` without middleware.ts -> http://localhost:3000/ ✅
`next start --hostname 0.0.0.0` with middleware.ts ->http://localhost:3000/ ✅ 
`next start --hostname ::` without middleware.ts -> http://[::1]:3000/ ✅
`next start --hostname ::` with middleware.ts -> http://[::1]:3000/ ❌ 404

### Expected Behavior

middleware should work as expected when using ipv6

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

_No response_

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

_No response_
Repository: go
Issue: x/benchmarks/cmd/bent: some canned benchmarking scripts lack local-machine hooks
Labels: NeedsFix

The "nightly" script references a possibly-present script "localfix" that can modify the environment to make benchmarking better.  For example, `localfix-odroid-n2` contains
```
NUMACTL='numactl -C 2-5 --'
export GOMAXPROCS=4
B=3
N=15
BUILDER_TYPE="Odroid-N2-arm64"
```
which default-reduces the benchmarking numbers to a size more appropriate for a small arm64, but more importantly, defines NUMACTL so that benchmarking is entirely on the big processors of a BIG.little arm64.

Unfortunately, not all the scripts check localfix or reference NUMACTL.
Repository: flutter
Issue: Use `toolchain` to set Java source compatibility
Labels: platform-android,tool,package,P3,a: plugins,team-android,triaged-android

Currently we're using the `sourceCompatibilty` option in [our template](https://github.com/flutter/flutter/blob/bfd92a86197a289fdccaad85c9179ea73f049734/packages/flutter_tools/templates/plugin/android-java.tmpl/build.gradle.tmpl#L28-L29), and [all of our 1P plugins](https://github.com/flutter/packages/pull/3715), to say what version of Java the source requires.

According to [Gradle docs](https://docs.gradle.org/current/userguide/java_plugin.html#toolchain_and_compatibility) the preferred way to set this is now via the `toolchain` option. We should investigating updating the template, and our 1P plugins, to use that. However, support for that option was added [in Gradle 6.7](https://blog.gradle.org/java-toolchains), so we shouldn't update plugins or the template until we have `flutter` tool enforcement of a minimum gradle version of 6.7 or later in all projects, otherwise plugins will be broken on older versions of Gradle.

(cc @reidbaker)
Repository: go
Issue: x/benchmarks/sweet: improve benchmark set
Labels: Performance,NeedsFix

There are only a handful of benchmarks in sweet, we should collect more representative benchmarks.

At the same time, some existing benchmarks (notably tile38) are extremely slow, making benchmark runs take an annoyingly long time.
Repository: TypeScript
Issue: file and folder with same name shows only file in requiring/importing in JS/TS
Labels: Bug,Help Wanted,Domain: Completion Lists

<!-- ⚠️⚠️ 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.77.3
- OS Version: Windows 10

Steps to Reproduce:

1. create a file, folder with same name
2. done

![image](https://user-images.githubusercontent.com/91016099/232327453-8ff6769f-77fc-499e-9638-1cacfaeda608.png)
Repository: rust
Issue: Pessimization on clearing LSB when unpacking enum
Labels: A-LLVM,I-slow

I have code that unpacks an enum into one of two variants depending on the LSB, clearing the LSB for the variant data:

```rust
pub enum Foo {
    First(u32),
    Second(u32),
}

fn make_assumption(value: u32) {
    if value % 4 != 0 {
        unsafe { std::hint::unreachable_unchecked(); }
    }
}

fn make_first(value: u32) -> Foo {
    //make_assumption(value);
    Foo::First(value)
}

fn make_second(value: u32) -> Foo {
    //make_assumption(value);
    Foo::Second(value)
}

pub fn unpack_foo(packed: u32) -> Foo {
    if packed & 0b1 == 0 {
        make_first(packed)
    } else {
        make_second(packed & !0b1)
    }
}
```

When compiled as written in 1.68 ([godbolt](https://rust.godbolt.org/z/n8EG76oz4)) and 1.69 (beta at time of writing; [godbolt](https://rust.godbolt.org/z/jxnrhhEnY)), the result is:

```
example::unpack_foo:
        mov     eax, edi
        and     eax, 1
        and     edi, -2
        mov     edx, edi
        ret
```

However, if the lines with `make_assumption` are uncommented ([1.68 godbolt](https://rust.godbolt.org/z/n55vb7b3W), [1.69 godbolt](https://rust.godbolt.org/z/j8z33Kxd3)) then the result is:

```
example::unpack_foo:
        mov     edx, edi
        and     edx, -4
        mov     eax, edi
        and     eax, 1
        cmove   edx, edi
        ret
```

Which is slightly worse. It seems that the assumption of the two lower bits being clear causes the mask to become wider unnecessarily, just because it can. (In the original code, this came from a debug-checked hint to the optimizer.)

On nightly, a conditional move is always used. The only difference between the assumption being absent ([godbolt](https://rust.godbolt.org/z/Kr39KK9sW)) or present ([godbolt](https://rust.godbolt.org/z/qW5bb96df)) is the mask value.

Strangely, if `make_first` and `make_second` are inlined then nightly will avoid the conditional move with the assumption absent, like in 1.68 and beta. ([godbolt](https://rust.godbolt.org/z/PGxPzczos))

---

For now I have removed the unreachable_unchecked to retain the smaller code. Let me know if this belongs directly to LLVM, but my entry point is Rust.
Repository: neovim
Issue: winbar disappears when changing the buffer in a window
Labels: statusline,options

### Problem

When setting a window-local `winbar`, this option is lost when changing the currently displayed buffer.

### Steps to reproduce

* `nvim -Nu NONE`
* `:e a`
* `:setlocal winbar=foo`
* `:e b`

---

Then

* `:bu a`

### Expected behavior

Winbar `foo` is displayed in the window when both `a` and `b` buffers are displayed.

Actual behaviour:

winbaar is removed when switching to `b`
winbaar is returned when switching back to `a`

I.e. the option seems to be buffer-local not window-local, or `setlocal` is setting it in the buffer not the window.

From the help:

```
'winbar' 'wbr'          string (default empty)
                        global or local to window global-local
```

### Neovim version (nvim -v)

NVIM v0.10.0-dev-111+g9e5f9c25d

### Vim (not Nvim) behaves the same?

Vim behaves as expected when using nnoremenu WinBar.foo

### Operating system/version

macOS

### Terminal name/version

iTerm2

### $TERM environment variable

xterm-256color

### Installation

build from source, brew
Repository: rust
Issue: rustc: Gives inconsistent error messages if a dependency's dependency rlib has an unexpected filename
Labels: A-metadata,T-compiler,C-bug

Note that the following can only happen when calling `rustc` directly instead of going through `cargo` as `cargo` uses an rlib filename scheme that works and AFAIU doesn't allow overriding that anyway.

I tried this code:

* `a/lib.rs`:

```rust
pub fn foo() -> i32 {
    123
}
```

* `b/lib.rs`:

```rust
pub fn bar() -> i32 {
    some_a::foo() * 2
}
```

* `c/main.rs`:

```rust
fn main() {
    //use b::bar;
    println!("{}", b::bar());
}
```

When compiling this as follows it will fail on the third `rustc` invocation.

```shell
mkdir -p builddir
rm -f builddir/liba.rlib
rm -f builddir/libb.rlib
rm -f builddir/c
rustc --crate-type rlib --edition=2021 --crate-name some_a --emit link -o builddir/liba.rlib a/lib.rs
rustc --crate-type rlib --edition=2021 --crate-name b --emit link -o builddir/libb.rlib --extern some_a=builddir/liba.rlib -L builddir b/lib.rs
rustc --crate-type bin --edition=2021 --crate-name c --emit link -o builddir/c --extern b=builddir/libb.rlib -L builddir c/main.rs
```

This gives the following error with latest stable (1.68.2) and also 660c966ff941ddf995d3251df32508b383cd4cee

```
error[E0463]: can't find crate for `some_a` which `b` depends on
 --> c/main.rs:3:20
  |
3 |     println!("{}", b::bar());
  |                    ^ can't find crate

error: aborting due to previous error
```

**Note** that the crate name of a is `some_a` while the rlib file is called `liba.rlib`. If changing either the crate name to `a` or the filename to `libsome_a.rlib` it works.

More confusingly, when using 660c966ff941ddf995d3251df32508b383cd4cee and uncommenting the `use b::foo` line, it gives a different error

```
error[E0519]: the current crate is indistinguishable from one of its dependencies: it has the same crate-name `b` and was compiled with the same `-C metadata` arguments. This will result in symbol conflicts between the two.
 --> c/main.rs:2:9
  |
2 |     use b::bar;
  |         ^

error[E0519]: the current crate is indistinguishable from one of its dependencies: it has the same crate-name `b` and was compiled with the same `-C metadata` arguments. This will result in symbol conflicts between the two.
 --> c/main.rs:3:20
  |
3 |     println!("{}", b::bar());
  |                    ^

error: aborting due to 2 previous errors
```

I would expect

  1. both cases to give the same error message
  2. either using an "invalid" rlib name should fail directly (i.e. first `rustc` invocation above), or compilation of the above testcase should work fine
Repository: pytorch
Issue: we should make semantically meaningless positional arguments positional only in our operator API
Labels: feature,triaged,actionable,module: python array api,module: python frontend

### 🚀 The feature, motivation and pitch

See #99265 for an example of some of the chaos this causes. Position-only arguments were added in Python 3.8 and we recently dropped support for 3.7 so now is the first opportunity to do this.

Prior art: the Python array API is aggressively using position only arguments.

Removing this will be BC breaking, so here is a rough idea for how it should be done.
1. add support for doing this in our codegen
2. add a linter to prevent new uses of things like tensor1, tensor2, etc.
3. add a warning that fires when calling existing functions with named arguments
4. remove warning and migrate to position only arguments after a release


@mruberry @rgommers 

### Alternatives

_No response_

### Additional context

_No response_

cc @mruberry @rgommers @pmeier @asmeurer @leofang @AnirudhDagar @asi1024 @emcastillo @kmaehashi @albanD
Repository: pytorch
Issue: add `-std=c++20` build-only CI job
Labels: module: build,module: ci,triaged,module: devx

### 🚀 The feature, motivation and pitch

We won't be adopting C++20 any time soon, but we do have users who wish to build with it. We should keep our code at least building with C++20, using whatever CI config is the cheapest to keep it working.

I'm happy to get the code working if someone else can contribute the CI job.

See #99013 #85703 #98917 for some related issues/changes.

### Alternatives

_No response_

### Additional context

_No response_

cc @malfet @seemethere @pytorch/pytorch-dev-infra @ZainRizvi @kit1980 @huydhn @clee2000
Repository: neovim
Issue: Validate code samples in docstrings in CI
Labels: enhancement,documentation,ci

### Problem

Many function docstrings, particularly in Lua, use code examples of the form:

```lua
--- Example:
--- <pre>lua
--- local x = vim.foo.bar()
--- </pre>
```

However, these can become outdated or contain errors.

### Proposal

A useful feature would be to run these samples automatically in CI to validate them (make sure they actually run). If we can decide on a format, we could even run them and validate their output. For example, one format we could use is:

```lua
--- <pre>lua
--- some_function()
--- -- expected output when printing
--- </pre>
```

Some script in CI would see this snippet in the docstring, run `some_function()` and verify that its output is `expected output when printing`.

This is not always possible of course, and may not be sophisticated enough to cover all cases, but hopefully it communicates the concept.
Repository: flutter
Issue: Deeplink set up in flutter create template.
Labels: tool,P2,team-framework,triaged-framework

If developers want to setup deeplink using flutter's default deeplink handler, they would need to add a meta-data tag in Androidmanifest file
```
<meta-data android:name="flutter_deeplinking_enabled" android:value="true" />
```

There is also a similar set up required for iOS.

This was originally added because people have been using third party plugin like https://github.com/avioli/uni_links to handle deeplink prior to we implementing the default deeplink handler, and we didn't want to break them.

However, even now that we can't work around the issue for newly created package without consequences. Here are some options we can take, each with their own pros/cons

1. Automatically add flutter_deeplinking_enabled in flutter create

This opts every new app into default deeplink handler. However, this would reduce the usability of third-party package. uni_link for example, developer will need to manually remove this meta data tag in the newly created app to use the plugin.

2. Deprecate flutter_deeplinking_enabled and refactor FlutterPlugin.

Take Android for example, ideally if we know plugin will be handling the deeplink we can decide whether we want to call the default deeplink handler or not. The issue is that plugin uses onNewIntent to extract the uri when deeplinked. This method is too generic so we can't tell whether the a plugin implements this method is handling deeplink or something else.

It is also unclear in what case a plugin can safely return true to stop other plugin from handling this method.

To solve this issue, we may need a more explicit API in FlutterPlugin.

3. Keep things as-is

People would still need to add the meta-data tag. Since it is just one line and they would need to modify the android manifest anyway, it would probably be fine.
Repository: vscode
Issue: Goto line picker should not announce the line content
Labels: debt,accessibility,quick-open

From https://github.com/microsoft/vscode/pull/179469

There is code such as:

https://github.com/microsoft/vscode/blob/ec468246c16ab345dbec16d2fb8be7077f075c42/src/vs/editor/contrib/quickAccess/browser/editorNavigationQuickAccess.ts#L150-L153

This seems like a hack to me:
* why would the picker deal with accessibility the editor should be taken care of
* what about a line that is minified and 10MB in size, do we want to announce it?
* should we announce just the line and not the contents?

//cc @isidorn
Repository: vscode
Issue: Markdown iframe scrolling issue 
Labels: bug,notebook-output

When I add an Iframe into a VS Code Jupyter markdown cell, it renders correctly.
However, as soon as I hover the mouse over this iframe and try to scroll up and down, the notebook does not scroll anymore.
I tried to set the parameter `scrolling="no"` but that did not work eighter.
Here is the markdown cell code for reproducing this bug:
```
<iframe src="https://twitframe.com/show?url=https://twitter.com/code/status/1643989447346892800" width = "300px" height="600px" scrolling="no" overflow="hidden"></iframe>
```

https://user-images.githubusercontent.com/44469195/230721845-c331aad8-d9fa-4cad-b772-f6905054739a.mov

<br>

Additional note: iframes are not at all shown in jupyterlab notebooks at all:
https://github.com/ipython/ipython/issues/5711

## Environment data

-   VS Code version: latest
-   Jupyter Extension version (available under the Extensions sidebar): latest
-   Python Extension version (available under the Extensions sidebar): XXX
-   OS (Windows | Mac | Linux distro) and version: Mac
-   Python and/or Anaconda version: XXX
-   Type of virtual environment used (N/A | venv | virtualenv | conda | ...): XXX
-   Jupyter server running: Local | Remote | N/A
Repository: pytorch
Issue: [c++17] Replace lock_guard with scoped_lock 
Labels: module: internals,triaged

@voznesenskym  pointed out that `lock_guard` is deprecated in C++-17 and we should move to `scoped_lock`.


cc @ezyang @bhosmer @smessmer @ljk53 @bdhirsh
Repository: terminal
Issue: Move to OSC 8 hyperlinks with keyboard in mark mode
Labels: Help Wanted,Issue-Bug,Area-TerminalControl,Product-Terminal

# Description of the new feature/enhancement

Currently you can cycle through URLs in the scrollback buffer with tab and shift+tab in mark mode. It would be nice if this also worked with OSC 8 hyperlinks.

Right now this:
```bash
printf '\e]8;;http://example.com\e\\This is a link\e]8;;\e\\\nhttp://example.com\n'
```
only lets you shift+tab back to the plain text link, not the OSC 8 one, which you would have to navigate to using the arrow keys.