sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Seeking to looped animation end, actually seeks to beginning.
Labels: discussion,topic:animation

### Godot version

4.2.rc (a34814b0b)

### System information

Godot v4.2.rc (a34814b0b) - Ubuntu 23.10 23.10 - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 6600 (RADV NAVI23) () - 12th Gen Intel(R) Core(TM) i5-12400F (12 Threads)

### Issue description

When you seek with code to end of looped animation it seeks to beginning.

	extends Node2D

	@onready var _sprite = $Sprite2D
	@onready var _animation = $Sprite2D/AnimationPlayer

	func _ready():
		_animation.seek(0.9, true)
		_animation.pause()


Fix: https://github.com/godotengine/godot/pull/85186

### Steps to reproduce

1. Create an animation, e.g. for scale
2. Set length to 0.9 and snapping to 0.1
3. Add a key at the beginning and end
4. Enable looping
5. run code to display last frame. but shows first

### Minimal reproduction project

[ReproductionProject.zip](https://github.com/godotengine/godot/files/13440804/ReproductionProject.zip)
Repository: PowerToys
Issue: When reassigning the key "Up" "Down" "Screen up" "Screen down" problem
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.75.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

When reassigning the key “Top” “Down” “Screen up” “Screen down”, in this mode, when entering a remote desktop, the screen of this desktop scrolls down a screen. This is in any version of your program.
And this happens when switching from your desktop to a remote desktop always, in any application. My OS is Windows 11 Pro
[PowerToysReport_2023-11-22-15-24-17.zip](https://github.com/microsoft/PowerToys/files/13440784/PowerToysReport_2023-11-22-15-24-17.zip)

https://github.com/microsoft/PowerToys/assets/111049622/045ca87b-6f07-4279-bb70-6aecf2fce1dd



### ✔️ Expected Behavior

This shouldn't happen

### ❌ Actual Behavior

When reassigning the key “Top” “Down” “Screen up” “Screen down”, in this mode, when entering a remote desktop, the screen of this desktop scrolls down a screen. This is in any version of your program.
And this happens when switching from your desktop to a remote desktop always, in any application. My OS is Windows 11 Pro

### Other Software

_No response_
Repository: next.js
Issue: Multizones (with async rewrites()) not working as expected
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/ezeamin/next-multizones-test

### To Reproduce

1. Install dependencies on global scope and inside each app folder with pnpm or npm
2. Run `pnpm dev` on the root folder
3. Go to http://localhost:3000
4. Click on "To App 3001" link
5. This will compile the app on port 3001 (see console log), but won't render it until the page gets refreshed
6. The same happens when travelling back to home

### Current vs. Expected behavior

Current:
The app recognizes the rewrite rule and redirects the route to the correct destination, but won't update the content of the page until it's refreshed. The same happens when travelling back to home.

Expected:
To show the content of the other app when changing the path.

### 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 11 Pro
Binaries:
  Node: 21.2.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.4-canary.10
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A

pnpm is 8.10.5
```


### Which area(s) are affected? (Select all that apply)

App Router, Routing (next/router, next/navigation, next/link)

### Additional context

This is not a new issue. From version 13 onwards it's been happening. I have not used NextJs before, so I can't tell if this is something recent or not.

This has been tested locally only, no deployed version. Running on Windows 11 and Chrome, latest version. Firefox behaves the same.

This has been tested with and without the `--turbo` flag. I've tried removing `node_modules` and `.next` folders from both apps, but no change.
Repository: PowerToys
Issue: Color Picker showing wrong colors
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.75.1

### Installation method

GitHub, PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

ColorPicker

### Steps to reproduce

![Screenshot 2023-11-22 154801](https://github.com/microsoft/PowerToys/assets/18054689/6a27917f-292c-40ed-8f21-929d223010a6)

As seen in the screenshot, problem happens while trying to fast pick a color without having to select an element in Figma and copying color from the right side. Color code is wrong on the picker and shows different information than the ones in Figma. Color shown in Figma is not in any way gradient, also the Rectangle element doesn't have nothing above it to conflict with color.


### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

Figma - Nov 20, 2023 update.
Repository: kubernetes
Issue: logs: check for "unhandled errors"
Labels: sig/instrumentation,triage/accepted

Once https://github.com/kubernetes/kubernetes/pull/121970 is merged and enough (all?) code is converted to `HandleErrorWithContext`, we can analyze logs from jobs like https://testgrid.k8s.io/sig-instrumentation-tests#kind-json-logging-master to find out:
- whether there are unhandled errors
- how many

With JSON output, jq might be enough to search for `logger=".*UnhandledError.*". See https://github.com/kubernetes/kubernetes/tree/master/test/integration/logs/benchmark#real-log-data for instructions on how to download those logs.

If there are none, then we might be able to add post-processing of all or at least some jobs and check that no such errors creep in. If there are some, we might need an allow list.

/cc @sttts
Repository: react-native
Issue: Calling `Keyboard.dismiss()` in a button is scrolling to focused input in iOS
Labels: Platform: iOS,Issue: Author Provided Repro,Component: Button,API: Keyboard,Needs: Triage :mag:,Newer Patch Available

### Description

I have a form with several fields (`TextField`) and in the end a button that sends the form data to a server and navigates to another screen if successful.

When I'm clicking the button, I dismiss the keyboard and that is causing the last modified input to be focused (it's scrolled into view). Even if I change the button (a `Pressable`) to only call `Keyboard.dismiss()`, this issue still happens.

From what I tested this only happens if I type characters in the input: if I only tap the input so that it has focus, it works fine; if I only delete some characters it also works fine, that is, the input is not focused (and scrolled to) when I call `Keyboard.dismiss()`.

This only happens in iOS (in Android, it works correctly, without scrolling to the input).

It also works if I click in the keyboard "Return" button before clicking the button (it closes the keyboard, but doesn't scroll to the field). If there is a way to trigger it programatically, it could be used as a workaround.

### React Native Version

0.72.7

### Output of `npx react-native info`

```
System:
  OS: Linux 5.4 Ubuntu 20.04.6 LTS (Focal Fossa)
  CPU: (4) x64 Intel(R) Core(TM) i7-3537U CPU @ 2.00GHz
  Memory: 3.02 GB / 11.57 GB
  Shell:
    version: 5.0.17
    path: /bin/bash
Binaries:
  Node:
    version: 16.20.2
    path: /usr/bin/node
  Yarn: Not Found
  npm:
    version: 8.19.4
    path: /usr/bin/npm
  Watchman:
    version: 20221204.222904.0
    path: /usr/local/bin/watchman
SDKs:
  Android SDK: Not Found
IDEs:
  Android Studio: AI-203.7717.56.2031.7621141
Languages:
  Java:
    version: 11.0.20.1
    path: /usr/bin/javac
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.72.7
    wanted: 0.72.7
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
```

### Steps to reproduce

Have a form with several `TextField` components and a button at the end. Call `Keyboard.dismiss()` in the button. Make it so that when you go to the end of the screen, the first fields are not visible.

Type anything in one of the first fields (it can be any field, as long as it's not visible in the end of the screen).

Let the keyboard open, then go to the end of the screen and tap the button (you can also tap outside of any field to close the keyboard).

If you are using iOS, the Textfield is focused (the screen will scroll and focus it).


### Snack, screenshot, or link to a repository

https://snack.expo.dev/@lucas99freelas/textfield-keyboard-ios?platform=ios
Repository: PowerToys
Issue: Remapped WIN key not working for Game Bar
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

v0.75.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

1. open keyboard manager
2. Setup Alt for Windows Key
3. Setup Windows key for Alt 
4. Pressing both win+G as alt+g opens game bar

### ✔️ Expected Behavior

Only the new set windows key should use on system shortvuts. Bascially all system shortcuts are now available with both win+KEY as alt+key. Other apps do work fine, Windows it self seems to have no resource of keyboard manager running.

### ❌ Actual Behavior

Both the new remapped key as the original work both for the shortcuts. For example WIN mapped to ALT will now both work for any system shortcut.

### Other Software

_No response_
Repository: pytorch
Issue: Improve usability of CUDA package by adding description of CUDA
Labels: module: docs,triaged,enhancement

### 📚 The doc issue

While reading through the documentation, I came to the [Torch CUDA page](https://pytorch.org/docs/stable/cuda.html#). The description explained that the package adds support for CUDA but didn't explain what CUDA is. It would be helpful for new users reading the docs to be given some background on CUDA as well.

### Suggest a potential alternative/fix

My suggestion is to add context to [Torch CUDA page](https://pytorch.org/docs/stable/cuda.html#). Something like the following text:

```
CUDA is a parallel computing platform and programming model developed by NVIDIA for general computing on GPUs.
With CUDA, developers are able to dramatically speed up computing applications by harnessing the power of GPUs.
See https://developer.nvidia.com/cuda-zone for more details.
```

I am willing to push the PR for this change.

cc @svekars @carljparker
Repository: godot
Issue: Setting up automatic exposure or glow gizmos will affect pre rendering
Labels: discussion,topic:rendering,topic:editor,topic:3d

### Godot version

4.2 RC 1

### System information

windos 11 vlukan  RTX2060 ；i5-10400

### Issue description

When Glow is on, the gizmos will produce halos, and due to changes in camera exposure values, the gizmos will also become brighter or darker
![a869a55930260664c20b255d62582887](https://github.com/godotengine/godot/assets/149220438/6ea661b1-f4ad-4465-8c25-33c945c2e367)




### Steps to reproduce

Add WorldEnvironment node add Environment open Glow and turn on camera automatic exposure adjustment. Adjust the maximum and minimum camera automatic exposure values to create a bright and dark effect on the screen. Gizmos will change the brightness and dark changes with the camera exposure value (as if Gizmos participated in the pre rendering and interacted with the model lighting. If Glow is turned on)

### Minimal reproduction project

[Uploading XiaoHu3.zip…]()
Repository: pytorch
Issue: TypeError: unhashable type: non-singleton SymInt in AOTAutograd merge_view_inputs
Labels: triaged,oncall: pt2,module: dynamic shapes,module: aotdispatch,module: pt2-dispatcher,internal ramp-up task

### 🐛 Describe the bug

I was trying some workarounds for https://github.com/pytorch/pytorch/issues/114293 and this one failed:

```
import torch
import torch._dynamo

torch._dynamo.config.capture_scalar_outputs = True

torch._logging.set_logs(recompiles=True)

@torch.compile
def accumulate(X0, start):
    start = start.item()
    result = X0[start]
    for i in range(0, 10-start+1):
        result += X0[start+1+i]
    return result


X0 = torch.randn(100, 100)

for i in range(10):
    print(i)
    accumulate(X0, torch.tensor(i))
```

fails with

```
  File "/data/users/ezyang/a/pytorch/torch/_inductor/compile_fx.py", line 1168, in compile_fx
    return aot_autograd(
  File "/data/users/ezyang/a/pytorch/torch/_dynamo/backends/common.py", line 55, in compiler_fn
    cg = aot_module_simplified(gm, example_inputs, **kwargs)
  File "/data/users/ezyang/a/pytorch/torch/_functorch/aot_autograd.py", line 5021, in aot_module_simplified
    compiled_fn = create_aot_dispatcher_function(
  File "/data/users/ezyang/a/pytorch/torch/_dynamo/utils.py", line 244, in time_wrapper
    r = func(*args, **kwargs)
  File "/data/users/ezyang/a/pytorch/torch/_functorch/aot_autograd.py", line 4561, in create_aot_dispatcher_function
    compiled_fn = compiler_fn(flat_fn, fake_flat_args, aot_config, fw_metadata=fw_metadata)
  File "/data/users/ezyang/a/pytorch/torch/_functorch/aot_autograd.py", line 2881, in aot_wrapper_dedupe
    return compiler_fn(flat_fn, leaf_flat_args, aot_config, fw_metadata=fw_metadata)
  File "/data/users/ezyang/a/pytorch/torch/_functorch/aot_autograd.py", line 3062, in aot_wrapper_synthetic_base
    flat_args_with_synthetic_bases, synthetic_base_info = merge_view_inputs(
  File "/data/users/ezyang/a/pytorch/torch/_functorch/aot_autograd.py", line 2581, in merge_view_inputs
    arg_to_old_idx_map = {arg: i for (i, arg) in enumerate(fwd_inputs)}
  File "/data/users/ezyang/a/pytorch/torch/_functorch/aot_autograd.py", line 2581, in <dictcomp>
    arg_to_old_idx_map = {arg: i for (i, arg) in enumerate(fwd_inputs)}
  File "/data/users/ezyang/a/pytorch/torch/__init__.py", line 303, in __hash__
    raise TypeError("unhashable type: non-singleton SymInt")
torch._dynamo.exc.BackendCompilerFailed: backend='inductor' raised:
TypeError: unhashable type: non-singleton SymInt
```

cc @msaroufim @wconstab @bdhirsh @anijain2305 @zou3519

### Versions

main
Repository: excalidraw
Issue: Slideshow content is invisible occasionally
Labels: E+/presentations

If I create a slideshow then start to re-order the slides, add a new empty on in, re-order etc.  Frequently I find (on Chrome) the content is invisible in the slide.   I have to "wiggle" the content to refresh the slide representation of whatever I have inside it.
Repository: flutter
Issue: [go_router] Add `onRestore` callback for `StatefulShellRoute`  to execute code when a branch is restored
Labels: c: new feature,package,P3,p: go_router,team-go_router,triaged-go_router

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

When A branch gets created gains focus. When B branch gets created gains focus. When A branch get restored it doesn't regain focus.

### Proposal

Having the possibility to execute code when a branch is restored
Repository: PowerToys
Issue: notepad not opening up at last used "fancyzone"
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.75.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

FancyZones

### Steps to reproduce

WHen i open a program it aautomatically fits into the last fanzyzone it was used in. For example i have whats app in the top right corner. I wanted to have notepad in the bottom left corner, but it never opens thé same place it was closed. 

### ✔️ Expected Behavior

Notepad to open up at last used fancyzone like the other apps

### ❌ Actual Behavior

Notepad opens up around center of the screen instead of the designated fanzyzone

### Other Software

_No response_
Repository: next.js
Issue: Error: Could not find the module ".../packages/ui/src/select/select.tsx#Select#Item" in the React Client Manifest. This is probably a bug in the React Server Components bundler.
Labels: bug

### Link to the code that reproduces this issue

https://github.com/scerelli/dot-component-bug-next

### To Reproduce

1. Given a client component that exports multiple components accessible via dot notation, like the one you see in the repo attached, next fails to load the components.

 example:
```
<Select>
 <Select.Item>Value</Select.Item>
</Select>
```
4. Next fails to import it and throws an error
```
Error: Could not find the module ".../packages/ui/src/select/select.tsx#Select#Item" in the React Client Manifest. This is probably a bug in the React Server Components bundler.
```

### Current vs. Expected behavior

I expect it to load correctly

### 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 23.1.0: Mon Oct  9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000
Binaries:
  Node: 18.16.0
  npm: 9.5.1
  Yarn: 1.22.19
  pnpm: 8.10.5
Relevant Packages:
  next: 14.0.3
  eslint-config-next: 13.4.7
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.6
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Additional context

_No response_
Repository: next.js
Issue: Regular exported arrow function client components throw "cannot access before initialization" error message
Labels: bug

### Link to the code that reproduces this issue

https://github.com/miguelSoldado1/arrow-function-components-test

### To Reproduce

1. Run the development server.
2. The error should show up immediately once the page loads.

### Current vs. Expected behavior

- Right now when importing client components to other client components using an index file, if using regular arrow functions (not hoisted at the top) and not exporting as default a reference error is thrown: "ReferenceError: Cannot access 'x' before initialization". 
- The expected behaviour is just to be able to nest these client components without the need to hoist the component to the top (it worked using either regular function syntax or "var func =() =>").
- The components are simple enough so I'll leave it here.

The "/" page server component looks like this:
```
import { ClientComponent1 } from "@/components";

const Home = () => {
  return (
    <div className="border text-center p-8 m-4">
      Server Component
      <ClientComponent1 />
    </div>
  );
};

export default Home;
```

The client component imported into the server component:
```
"use client";

import { ClientComponent2 } from ".";

export const ClientComponent1 = () => {
  return (
    <div className="border p-8 m-4">
      Client Component 1
      <ClientComponent2 />
    </div>
  );
};
```

The inner client component inside the previous one:
````
"use client";

export const ClientComponent2 = () => {
  return <div className="border p-8 m-4">Client Component 2</div>;
};
````

It might also not be a next.js problem but actually a react server components problem so let me know if that is the case.

### 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.16.0
  npm: N/A
  Yarn: N/A
  pnpm: 8.7.5
Relevant Packages:
  next: 14.0.3
  eslint-config-next: 14.0.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.2
Next.js Config:
  output: N/A
```


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

Not sure

### Additional context

- It does only happen in the development server, everything looks fine after a build.
- The repo containing the example is not in the latest canary but I did try it in 14.0.4-canary.10 elsewhere and the same error appeared.

Also, for anyone facing the same issues either not importing the inner client component from the index file, exporting as default or just hoisting at the top using regular function syntax instead of arrow functions should fix your problem.
Repository: pytorch
Issue: dynamic shapes support for __torch_dispatch__ subclasses + torch.compile
Labels: triaged,module: __torch_dispatch__,oncall: pt2,module: dynamic shapes,module: pt2-dispatcher

Dynamic shapes work with subclasses in "basic" cases (where the subclass and its inner tensor(s) have the exact same shape), but blow up in more complicated cases.

Design doc on the plan is [here](https://docs.google.com/document/d/1ipSxcTzEMMOAPvxP-YJlD5JBZZmIGgh8Q34ixtOUCRo/edit#heading=h.3px8g3br0skz), authored with @ezyang and @jbschlosser.

We should make sure that several "interesting" subclass examples work:
- NestedTensor (ragged dim is dynamic)
- Float8Tensor (scales tensor is static)
- SparseTensor (nnz dim of the values tensor is always dynamic)

cc @Chillee @ezyang @zou3519 @albanD @samdow @msaroufim @wconstab @anijain2305
Repository: go
Issue: proposal: io/fs,path/filepath: add iterator form of WalkDir
Labels: Proposal

It's often more convenient to use a for loop rather than a callback-based API, and fs.WalkDir and filepath.Walk are both callback-based APIs. I've been using [github.com/kr/fs](https://pkg.go.dev/github.com/kr/fs#Walk) for years to work around this.
The new iterate-over-func functionality (#61405) now makes it straightforward to adapt the stdlib functions into iterators, so perhaps we could provide iterator-based APIs as part of the standard library now.

Here's a straw-man implementation:

```
package fs

type WalkDirEntry struct {
	Path    string
	Entry   fs.DirEntry
	Err     error
	skipDir *bool
}

// SkipDir causes the iteration to skip the contents
// of the entry. This will have no effect if called outside the iteration
// for this particular entry.
func (entry WalkDirEntry) SkipDir() {
	*entry.skipDir = true
}

// WalkDirIter returns an iterator that can be used to iterate over the contents
// of a directory. It uses WalkDir under the hood. To skip a directory,
// call the SkipDir method on an entry.
func WalkDirIter(fsys fs.FS, root string) func(func(WalkDirEntry) bool) {
	return func(yield func(WalkDirEntry) bool) {
		fs.WalkDir(fsys, root, func(path string, d fs.DirEntry, err error) error {
			skipDir := false
			info := WalkDirEntry{
				Path:    path,
				Entry:   d,
				Err:     err,
				skipDir: &skipDir,
			}
			if !yield(info) {
				return fs.SkipAll
			}
			if skipDir {
				return fs.SkipDir
			}
			return nil
		})
	}
}
```

The main point of contention from my point of view is the semantics of the SkipDir method. Calling a method on an iterated item to determine the subsequent course of iteration seems somewhat unusual, but I don't see any other decent alternative.

[Edited to remove incorrect remarks about GC behavior].