sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: VoiceOver rotor actions limited to text fields with active keyboard focus
Labels: a: text input,platform-ios,a: accessibility,has reproducible steps,P2,team-text-input,triaged-text-input,found in release: 3.24,found in release: 3.26

### Steps to reproduce

As I mentioned in #151029 :
Suppose there are two text fields on an interface.
1. Double-tap to activate the first text field, and the keyboard pops up.
2. Then, use VoiceOver to focus on the second text field. Note: just focus on it, don't double-tap.
3. Finally, use the rotor to perform a paste operation.
Native behavior: The text will be pasted into the second text field.
Flutter behavior: Unable to perform the paste operation.
In other words, the native rotor operation targets the text field that VoiceOver is focused on.
However, Flutter rotor operation only targets the text field that has the keyboard activated.

Please use the latest master version for testing.

### Expected results

The text will be pasted into the second text field.

### Actual results

Unable to perform the paste operation.

### Code sample

<details open><summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(title: Text('Two Text Fields')),
        body: Column(
          children: [
            TextField(),
            TextField(),
          ],
        ),
      ),
    );
  }
}
```

</details>

### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Flutter (Channel master, 3.26.0-1.0.pre.97
```

</details>
Repository: pytorch
Issue: Can we remove @torch._dynamo_disable from torch.utils.checkpoint.checkpoint?
Labels: triaged,needs design,oncall: pt2,module: dynamo

### 🚀 The feature, motivation and pitch

`torch.utils.checkpoint.checkpoint` has a strong limitation: there must be no graph break, and if it can't be satisfied, it will fall back to eager with this decorator. then the performance is too bad.


### Alternatives

in my local test, I removed this decorator and enabled compiled_autograd (with a fix for deadlock), the performance for llama-70b finetune boosted about +35%.

### Additional context

llama-70b finetune in optimum using deepspeed zero3, which registers several hooks in the module, these hooks can't be traced by dynamo, and it's hard to fix these graph breaks in a short time.
and it call `checkpoint` function in `DecoderLayer.__call__`, so all 80 DecoderLayer fall back to eager.

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames @rec
Repository: next.js
Issue: Middleware: Cannot export config after declaration in export list format
Labels: bug,Middleware

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/nameless-hill-dt239f

### To Reproduce

Link to codesandbox is provided and it shows the issue as well.

### Current vs. Expected behavior

The config object from `middleware.ts` is loaded correctly in case 1 (exporting during declaration) while it is not loaded correctly in case 2 (exporting after decleration):

```
import { NextRequest, NextResponse } from 'next/server';

// case 1 -> works as expected
export const middleware = (request: NextRequest) => {
	console.log(request.nextUrl.pathname);

	return NextResponse.next();
};

export const config = {
	matcher: '/about',
};

// case 2 -> does not work as expected
const middleware = (request: NextRequest) => {
	console.log(request.nextUrl.pathname);

	return NextResponse.next();
};

const config = {
	matcher: '/about',
};

export { middleware, config };
```

When the config is loaded only paths with `/about` should be printed in the console. If not loaded, all paths are printed in the console. Also no error is reported (I am not sure if an error should be reported).

### Provide environment information

```bash
Sandbox is running on next.js version 15.0.0-canary-148. I encountered the same issue locally on 15.0.0-rc.0. Used app router in both instances.
```


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

Middleware

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

next dev (local)

### Additional context

Exporting the config object while declaring it solves the issue for me, but the difference should only be one of syntax and not functionality. The `middleware` function is unaffected by this issue, only the `config` object is affected.

This issue might be related but I'm not completely sure: https://github.com/vercel/next.js/issues/67169
In the case that it is feel free to remove this issue/combine both issues.
Repository: rust
Issue: Write down where all the unwind/backtrace code is
Labels: A-runtime,C-enhancement,T-compiler,A-docs,T-libs,E-tedious,A-backtrace

### Location

It's in at least three different locations, depending on how you count! That's the problem!

### Summary

Internal-facing documentation, mostly?

The problem is this, essentially: we have our internal unwinding/backtrace-related code in

- library/backtrace
- library/panic_abort
- library/panic_unwind
- library/std/src/sys/personality
- library/unwind

And the interrelationships are not so clean and obvious that you can simply follow imports, because sometimes the bridge is performed by raw compiler magic! Because, in fact, you do generally need compiler support to get a decent backtrace or to unwind correctly! So arguably I could also mention files like:
- rustc_codegen_ssa/src/mir/block.rs

Understanding all of these should not be the exclusive province of a few wizened sages of the dark arts. They should all backref to an index that tracks them. And if any can be eliminated and merged into others without causing horrid problems, they should be.
Repository: flutter
Issue: VoiceOver Rotor Operations Lack Feedback
Labels: platform-ios,a: accessibility,has reproducible steps,P2,team-accessibility,triaged-accessibility,found in release: 3.26

### Steps to reproduce

As I mentioned in #151029.

When using VoiceOver's rotor operations to perform actions such as paste, delete, etc., there is a lack of feedback after the operation is completed.

For example, with the native text fields, after pasting, it should read out the pasted text.
After selecting all, it should read out "XX has been selected."

However, in Flutter, there is no feedback information at all.

Please use the latest master version for testing.

### Expected results

There should be corresponding feedback information after each operation.

### Actual results

There is no feedback information at all.

### Code sample

<details open><summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(title: const Text('VoiceOver Test')),
        body: const Center(
          child: Padding(
            padding: EdgeInsets.all(16.0),
            child: TextField(
              decoration: InputDecoration(
                hintText: 'Enter text here',
              ),
            ),
          ),
        ),
      ),
    );
  }
}
```

</details>


### Screenshots or Video

_No response_

### Logs

_No response_

### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Flutter (Channel master, 3.26.0-1.0.pre.97
```

</details>
Repository: neovim
Issue: `nvim_buf_set_lines` doesn’t trigger fold update for injected TS parsers
Labels: bug,api,treesitter

### Problem

`nvim_buf_set_lines` doesn’t trigger injected tree-sitter parsers to update the fold ranges.
This only happens for injected tree-sitter parsers (not the main one attached to the buffer) when `nvim_buf_set_lines` is called before `BufWinEnter` event.

### Steps to reproduce

**minimal.lua**
```lua
vim.o.foldmethod="expr"
vim.o.foldexpr="v:lua.vim.treesitter.foldexpr()"

local bufnr = vim.api.nvim_create_buf(false, false)
vim.bo[bufnr].filetype = "lua"
local lines = {
    "vim.cmd([[",
    [[function test()]],
    [[  echom "hello"]],
    [[endfunction]],
    "]])",
}

-- set_lines from here doesn't update the injected parsers
vim.api.nvim_buf_set_lines(bufnr, 0, -1, false, lines)

vim.api.nvim_win_set_buf(0, bufnr)

-- set_lines from here updates the injected parsers
-- vim.api.nvim_buf_set_lines(bufnr, 0, -1, false, lines)
```

- `nvim --clean -u minimal.lua`
- See the `function … endfunction` is not folded

### Expected behavior

`nvim_buf_set_lines` should trigger fold updates for all injected parsers.

### Neovim version (nvim -v)

0.10.1

### Vim (not Nvim) behaves the same?

no, this is tree-sitter issue

### Operating system/version

ubuntu 22.04

### Terminal name/version

blink shell

### $TERM environment variable

xterm-256color

### Installation

build from repo
Repository: go
Issue: archive/zip: improve Zip64 compatibility with 7z
Labels: NeedsInvestigation

### Go version

go1.23.1

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/sangmin5.lee/.cache/go-build'
GOENV='/home/sangmin5.lee/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/sangmin5.lee/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/sangmin5.lee/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/sangmin5.lee/dev/go/goroot'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/sangmin5.lee/dev/go/goroot/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.23.1'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/home/sangmin5.lee/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build4058537502=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

* How to reproduce this issue

** Prepare two files with each size of 5G, 1M
$ touch test_5G
$ shred -n 1 -s 5G test_5G
$ touch test_1M
$ shred -n 1 -s 1M test_1M

** Create zipfile to have 5G file
  zipfile, err := os.Create("s5G.zip")
  zipWriter := zip.NewWriter(zipfile)
  newfile, err := os.Open("test_5G")

  fileInfo, err := newfile.Stat()
  header, err := zip.FileInfoHeader(fileInfo)

  header.Name = "test_5G"
  header.Method = zip.Deflate

  writer, err := zipWriter.CreateHeader(header)
  _, err = io.Copy(writer, newfile)

** Get 7z from https://sourceforge.net/projects/sevenzip/files/7-Zip/23.01/ or higher
and try to add 1M file to created zip

$ 7zz a s5G.zip test_1M


### What did you see happen?


7-Zip (z) 23.01 (x86) : Copyright (c) 1999-2023 Igor Pavlov : 2023-06-20
 32-bit ILP32 locale=en_US.utf8 Threads:96 OPEN_MAX:131072, ASM

Open archive: s5G.zip

WARNINGS:
Headers Error

--
Path = s5G.zip
Type = zip
WARNINGS:
Headers Error
Physical Size = 5370519708
64-bit = +
Characteristics = Zip64

Scanning the drive:
1 file, 1048576 bytes (1024 KiB)

Updating archive: s5G.zip

Keep old data in archive: 1 file, 5368709120 bytes (5120 MiB)
Add new data to archive: 1 file, 1048576 bytes (1024 KiB)

System ERROR:
E_NOTIMPL : Not implemented

### What did you expect to see?

Everything is OK without errs and the contents should be listed

$ unzip -l 5G.zip
Archive:  5G.zip
  Length      Date    Time    Name
---------  ---------- -----   ----
  1048576  2024-09-11 07:47   test_1M
5368709120  2024-09-11 07:50   test_5G
---------                     -------
5369757696                     2 files
Repository: godot
Issue: Functions passed as arguments cannot be called with `()` operator, but error message is insufficiently clear
Labels: enhancement,topic:gdscript

### Tested versions

v4.3.stable.official [77dcf97d8]

### System information

Windows 11

### Issue description

``` gdscript
# The following does not work. Error: Function "call_me()" not found in base self.
var fn1 = func(call_me): call_me()

 # No error. It refers to the local variable "call_me" instead of self. That's correct.
var fn2 = func(call_me): print(call_me)

# Workaround: Use call or wrap it in Callable. Not very comfortable.
var fn3 = func(call_me): call_me.call()
var fn4 = func(call_me): Callable(call_me).call()
```

I expected that the local variable (parameter) "call_me" is used. But it refers to self? Use local variable first, when fallback to class self and global. It seems to be a bug or something that can be changed.

### Steps to reproduce

Code is worth a thousand words. Please see above.

### Minimal reproduction project (MRP)

Please paste the code block above in your Godot editor.
Repository: rust
Issue: Tracking issue for future-incompatibility lint `unsupported_fn_ptr_calling_conventions`
Labels: A-lints,T-compiler,C-future-incompatibility,C-tracking-issue,A-ABI

This is the **summary issue** for the `unsupported_fn_ptr_calling_conventions` future-compatibility warning. The goal of this page is describe why this change was made and how you can fix code that is affected by it. It also provides a place to ask questions or register a complaint if you feel the change should not be made. For more information on the policy around future-compatibility warnings, see our [breaking change policy guidelines](https://rustc-dev-guide.rust-lang.org/bug-fix-procedure.html#tracking-issue-template).

### What is the warning for?

The `unsupported_fn_ptr_calling_conventions` lint is output whenever there is a use of a target dependent calling convention on a target that does not support this calling convention on a function pointer.

For example `stdcall` does not make much sense for a x86_64 or, more apparently, powerpc code, because this calling convention was never specified for those targets.

### Example

```rust,ignore (needs specific targets)
fn stdcall_ptr(f: extern "stdcall" fn ()) {
    f()
}
```

This will produce:

```text
warning: use of calling convention not supported on this target on function pointer
  --> $DIR/unsupported.rs:34:15
   |
LL | fn stdcall_ptr(f: extern "stdcall" fn()) {
   |               ^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
   = note: for more information, see issue #130260 <https://github.com/rust-lang/rust/issues/130260>
   = note: `#[warn(unsupported_fn_ptr_calling_conventions)]` on by default
```

### Explanation

On most of the targets the behavior of `stdcall` and similar calling conventions is not defined at all, but was previously accepted  due to a bug in the implementation of the compiler.

### Recommendations

Use `#[cfg(…)]` annotations to ensure that the ABI identifiers are only used in combination with targets for which the requested ABI is well specified.

### When will this warning become a hard error?

At the beginning of each 6-week release cycle, the Rust compiler team will review the set of outstanding future compatibility warnings and nominate some of them for Final Comment Period. Toward the end of the cycle, we will review any comments and make a final determination whether to convert the warning into a hard error or remove it entirely.

Implemented in #128784

See also #87678 for the similar `unsupported_calling_conventions` lint.
Repository: ui
Issue: [bug]: vertical separator not rendering
Labels: bug

### Describe the bug

When using the separator with a "vertical" orientation it does not render properly. Looking at the browser dev tools it appears to have a size of 1x0 pixels. 

Changing the default style here to use `min-h-full` instead of just `h-full` seems to fix this.

Seems to be the same as this [issue](https://github.com/huntabyte/shadcn-svelte/issues/1149) encountered in the shadcn-svelte port

### Affected component/components

Separator

### How to reproduce

1. Place a Separator in a flex parent with two other components and orientation "vertical"
```javascript
<div className="flex flex-row flex-nowrap gap-4 h-fit">
          <p>Foo</p>
          <Separator orientation="vertical" />
          <p>Bar</p>
 </div>
```
2. The separator will not appear
3. Change style within components/ui/separator.tsx
```javascript
<SeparatorPrimitive.Root
      ref={ref}
      decorative={decorative}
      orientation={orientation}
      className={cn(
        'shrink-0 bg-border',
        orientation === 'horizontal' ? 'h-[1px] w-full' : 'min-h-full w-[1px]',
        className
      )}
      {...props}
    />
```
4. Separator will now render

### Codesandbox/StackBlitz link

https://stackblitz.com/edit/stackblitz-starters-t7h9sc?file=components%2Fui%2Fseparator.tsx

### Logs

_No response_

### System Info

```bash
M2 Mac,
Firefox
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: rust
Issue: Diagnostic on missing "?" suggests to ignore the error entirely, which can be problematic
Labels: A-diagnostics,T-compiler

### Code

```Rust
fn fallible() -> Result<i32, ()> {
    Ok(42)
}

pub fn caller() -> Result<(), ()> {
    fallible();
    Ok(())
}
```


### Current output

```Shell
warning: unused `Result` that must be used
 --> src/lib.rs:6:5
  |
6 |     fallible();
  |     ^^^^^^^^^^
  |
  = note: this `Result` may be an `Err` variant, which should be handled
  = note: `#[warn(unused_must_use)]` on by default
help: use `let _ = ...` to ignore the resulting value
  |
6 |     let _ = fallible();
  |     +++++++
```


### Desired output

```Shell
Rust should suggest to add the missing `?`, not to ignore the error entirely.
```


### Rationale and extra context

See https://github.com/rust-lang/miri/issues/3855 for an example where ignoring the error with `let _ =` can lead to critical bugs.

### Other cases

_No response_

### Rust Version

```Shell
1.81.0
```


### Anything else?

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"roife"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: pytorch
Issue: (L)-BFGS with Hager-Zhang line-search
Labels: module: optimizer,triaged

### 🚀 The feature, motivation and pitch

I am working on PINNs (and variations of them) and it is often the case that BFGS performs better than its limited memory version. However, there is no official implementation of BFGS in Pytorch, only the limited memory version is available. Moreover, the Hager-Zhang line-search is often more effective than `strong-wolfe` when you get close to machine precision, as one would hope when solving PDEs.

I have a self-implemented version of BFGS and Hager-Zhang line-search. However, I am not good at writing well-factored code, tests or documentation. Anyone willing to help to add this feature, starting from my code?

This is partially related to: #55279, #80553

### Alternatives

I considered using [pytorch-minimize](https://github.com/rfeinman/pytorch-minimize), but BFGS is not efficiently implemented and Hager-Zhang line-search is not available.

### Additional context

_No response_

cc @vincentqb @jbschlosser @albanD @janeyx99 @crcrpar
Repository: TypeScript
Issue: Fail to infer Indexed access to the intersection type when it includes an union derived from a generic input
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

"indexed access on union", "generic index"

### 🕗 Version & Regression Information

5.6.2, and it seems never worked for every ts versions.

### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.6.2#code/C4TwDgpgBAKhDOwA8MoQB7AgOwCbykQCcBLbAcwD4oBeKAbwG0BpKM2AXQC4GBrCED2YBfYYxgcoAMgbAAhkXIRgPYmXLCAUJoDGAe2yIoAMz17aUFGkw58hYKQqUAFAvI84iFJQCUtavSaUMFQ+obAUABucgA2AK4QHgjIMNR0bgDcQSFhRtHxEABMSV6pjADk-CDlkumKFVU1WSGhBnmxCQDMJSmUFfKKyjUWbv1uQxwZUAD001AAokREekSawkA

### 💻 Code

```ts
type Test<T extends string> = {[K in T]: {key: K}}[T] & {target: string}

const foo = <T extends string>(arg: Test<T>) => {
    const value: Test<T> = arg; 
    const value2: Test<T>['key'] = arg['key']; 
    const value3: Test<T>['target'] = arg['target']; // Error
}
```


### 🙁 Actual behavior

The declaration of `value` and `value2` works well, but ts emit an error saying `Type 'string' is not assignable to type '{ [K in T]: { key: K; }; }[T]["target"] & string'` for `value3`. 

### 🙂 Expected behavior

The `Test<T>['target']` should equal to `string` and assume the type of `'{ [K in T]: { key: K; }; }[T]["target"] ` as `any` before intersection, as it does when I give non-generic type in the same place. It seems even weird because it well infers the type of `Test<T>['key']`.

### Additional information about the issue

With additional experiment, I found that it always happens when I generate an union type with generic input. For instance, 
```ts
type Test<T> = (T extends string ? {key: number} : {key: string}) & {target: string}

const foo = <T extends string>(arg: Test<T>) => {
    const value: Test<T> = arg;
    const value2: Test<T>['key'] = arg['key'];
    const value3: Test<T>['target'] = arg['target']; // Error
}
```

it also does not work in the case above
Repository: PowerToys
Issue: Copy on selection of text
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

An option to enable copy on selection as in X11/Linux systems. I.e. put text that is selected automatically on the clipboard.

I constantly find myself selecting text and pasting something different on Windows. 

### Scenario when this would be used?

Any text handling application like Notepad, VSCode, in browsers, Word+++

### Supporting information

There are some posts about this feature around, but they seem to be pretty misunderstood by none Linux users. E.g.:

https://answers.microsoft.com/en-us/windows/forum/all/automatically-copy-selected-text/4d2b0fc3-207b-404c-9468-2156266cb85a
Repository: kubernetes
Issue: [Flaking Test] [EventedPLEG] Containers Lifecycle should continue running liveness probes for restartable init containers and restart them while in preStop
Labels: priority/backlog,sig/node,kind/flake,triage/accepted

### Which jobs are flaking?

ci-crio-cgroupv1-evented-pleg
- https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-crio-cgroupv1-evented-pleg/1834117609461649408

### Which tests are flaking?

E2eNode Suite.[It] [sig-node] [NodeConformance] Containers Lifecycle when a pod is terminating because its liveness probe fails should continue running liveness probes for restartable init containers and restart them while in preStop [NodeConformance]

### Since when has it been flaking?

8/24


https://storage.googleapis.com/k8s-triage/index.html?date=2024-09-12&job=ci-crio-cgroupv1-evented-pleg&test=%20Containers%20Lifecycle%20when%20a%20pod%20is%20terminating%20because%20its%20liveness%20probe%20fails%20should%20continue%20running%20liveness%20probes%20for%20restartable%20init%20containers%20and%20restart%20them%20while%20in%20preStop%20



### Testgrid link

https://testgrid.k8s.io/sig-node-cri-o#ci-crio-cgroupv1-evented-pleg

### Reason for failure (if possible)

```
{ failed [FAILED] Expected an error to have occurred.  Got:
    <nil>: nil
In [It] at: k8s.io/kubernetes/test/e2e_node/container_lifecycle_test.go:903 @ 08/23/24 18:16:25.131
}
```


### Anything else we need to know?

_No response_

### Relevant SIG(s)

/sig node