sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Link triggers full root layout rerender in production build / static export
Labels: bug,Output (export/standalone)

### Link to the code that reproduces this issue

https://github.com/jlhervy/test-app-nextjs/

### To Reproduce

Start the application in development, clic the navigation buttons to the left, and notice that the root layout does not rerender. 
Now, produce a static export, or a production build, serve the static files (nginx, python -m http.server) or run next start, and clic the navigation buttons. 
This time, we can see that the root layout rerenders on each navigation (the console.log triggers), even though there is no state change. 

In my real application, this is annoying since I have particles in the background that change layout at each navigation.


### Current vs. Expected behavior

I expected the root layout to not rerender as it is in development. 

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Enterprise
  Available memory (MB): 16065
  Available CPU cores: 8
Binaries:
  Node: 20.11.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.2
  eslint-config-next: 14.2.2
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: export
```


### Which area(s) are affected? (Select all that apply)

Not sure, Output (export/standalone)

### Which stage(s) are affected? (Select all that apply)

next build (local), next start (local)

### Additional context

I tried several things, multiple servers and Link configuration, server vs client components, but each time the root layout rerenders.
Repository: stable-diffusion-webui
Issue: [Bug]: After upgrading to 1.9.0, you can't start it, you will report "Expected String or Bytes-Like Object"
Labels: bug-report

### Checklist

- [ ] The issue exists after disabling all extensions
- [ ] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [ ] The issue exists in the current version of the webui
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/128731958/44007d79-8b61-4885-a199-342ae55ca523)
The problem comes from the file modules/launch_utills.py: 307

After investigation, it was found that when the Package parameter was ‘spandrel’.
So it caused abnormalities

The following is the modified code, adding a judgment that returns False if version_installed is empty

![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/128731958/59cf6e86-abb1-4d8c-8689-9886dd07be7d)


### Steps to reproduce the problem

Version updated to 1.9.0

### What should have happened?

Successfully started

### What browsers do you use to access the UI ?

_No response_

### Sysinfo

No need to provide

### Console logs

```Shell
Python 3.10.11 (tags/v3.10.11:7d4cc5a, Apr  5 2023, 00:38:17) [MSC v.1929 64 bit (AMD64)]
Version: v1.9.3
Commit hash: 1c0a0c4c26f78c32095ebc7f8af82f5c04fca8c0
Traceback (most recent call last):
  File "C:\sd-webui-aki-v4.1\launch.py", line 48, in <module>
    main()
  File "C:\sd-webui-aki-v4.1\launch.py", line 39, in main
    prepare_environment()
  File "C:\sd-webui-aki-v4.1\modules\launch_utils.py", line 421, in prepare_environment
    if not requirements_met(requirements_file):
  File "C:\sd-webui-aki-v4.1\modules\launch_utils.py", line 311, in requirements_met
    if packaging.version.parse(version_required) != packaging.version.parse(version_installed):
  File "C:\sd-webui-aki-v4.1\python\lib\site-packages\packaging\version.py", line 54, in parse
    return Version(version)
  File "C:\sd-webui-aki-v4.1\python\lib\site-packages\packaging\version.py", line 198, in __init__
    match = self._regex.search(version)
TypeError: expected string or bytes-like object

--------
[程序异常退出，退出代码为 1 (0x00000001)]
```


### Additional information

_No response_
Repository: pytorch
Issue: TORCH_SHOW_DISPATCH_TRACE should give information about PythonDispatcher
Labels: triaged,module: dispatch

I see the following:

<img width="340" alt="image" src="https://github.com/pytorch/pytorch/assets/5652049/9053d5a0-aedb-4e68-a918-4877c2ba680f">

PythonDispatcher is picking dispatch keys to dispatch to in Python, but I don't know which
Repository: electron
Issue: [Bug]:  SIlent print resulting incorrect layout on Windows
Labels: platform/windows,component/printing,bug :beetle:,has-repro-gist,31-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

31.0.0-alpha.2

### What operating system are you using?

Windows

### Operating System Version

Windows 10 build 19045.3803

### What arch are you using?

x64

### Last Known Working Electron version

24.8.8

### Expected Behavior

It should prints the responsive HTML content nicely.

### Actual Behavior

It prints the left-aligned text but missed out the centered-aligned and right-aligned text.

### Testcase Gist URL

https://gist.github.com/mgalla10/053de2471f74277e60fb908aaa3685ff

### Additional Information

- Using Epson printer model M-T500II series https://www.epson.co.nz/pos/products/Printers/DisplaySpecs.asp?id=M-T500II.
- Work just fine with Electron 24.8.8 and below with `silent` set to `true`.
- Work just fine with Electron above 24.8.8 only when `silent` set to `false` -> not expected, I'd like to keep it set to `true`.
- It missed out all non left-aligned text with Electron above 24.8.8 (tried several version on 25.x.x and 30.x.x and 31.0.0-alpha.2).
- I have tried without luck the workaround mentioned in https://github.com/electron/electron/issues/39179 by adding `dpi:{ horizontal: 203, vertical: 203 }` (203 is the default printer resolution).
- Expecting the issue gets fixed in `31.0.0-alpha.2` but not in my case.
Repository: godot
Issue: Input.is_mouse_button_pressed(MOUSE_BUTTON_WHEEL_LEFT/RIGHT) is always returning false
Labels: discussion,documentation,topic:input

### Tested versions

- Reproducable in v4.2.2.stable.official [15073afe3]

### System information

Godot v4.2.2.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2080 Ti (NVIDIA; 31.0.15.3623) - AMD Ryzen 9 3900X 12-Core Processor (24 Threads)

### Issue description

The function `is_mouse_button_pressed()` works with mouse indices like 1 for left mouse button, it does not for 6 or 7 which are wheel left and right:
```gdscript
Input.is_mouse_button_pressed(MOUSE_BUTTON_LEFT) # Returns true if pressed, false if not
Input.is_mouse_button_pressed(MOUSE_BUTTON_WHEEL_LEFT) # Always returns false
```

### Steps to reproduce

```gdscript
func _process(delta):
    print(Input.is_mouse_button_pressed(MOUSE_BUTTON_WHEEL_LEFT))
```
Run and press your mouse wheel to the left.

### Minimal reproduction project (MRP)

[BugReport.zip](https://github.com/godotengine/godot/files/15066884/BugReport.zip)
Repository: vscode
Issue: TreeError [WatchExpressions] Data tree node not found:
Labels: error-telemetry

```javascript
Error: TreeError [WatchExpressions] Data tree node not found:

at Z.A in src/vs/base/browser/ui/tree/asyncDataTree.ts:797:10
at Z.hasElement in src/vs/base/browser/ui/tree/asyncDataTree.ts:573:36
at u.value in src/vs/workbench/contrib/debug/browser/watchExpressionsView.ts:160:32
at n.y in src/vs/base/common/event.ts:1156:13
at n.z in src/vs/base/common/event.ts:1167:9
at n.fire in src/vs/base/common/event.ts:1191:9
at T.setSelectedExpression in src/vs/workbench/contrib/debug/common/debugViewModel.ts:145:31
at le.addWatchExpression in src/vs/workbench/contrib/debug/browser/debugService.ts:974:19
at d.run in src/vs/workbench/contrib/debug/browser/watchExpressionsView.ts:521:16
at handler in src/vs/platform/actions/common/actions.ts:611:42
at fn in src/vs/platform/instantiation/common/instantiationService.ts:68:11
at S.n in src/vs/workbench/services/commands/common/commandService.ts:95:46
at S.executeCommand in src/vs/workbench/services/commands/common/commandService.ts:60:17
at $.run in src/vs/platform/actions/common/actions.ts:533:31
at I.u in src/vs/base/common/actions.ts:194:16
at I.run in src/vs/base/common/actions.ts:185:15
at D.onClick in src/vs/platform/actions/browser/menuEntryActionViewItem.ts:157:28
at HTMLLIElement.<anonymous> in src/vs/base/browser/ui/actionbar/actionViewItems.ts:151:10
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=e170252f762678dec6ca2cc69aba1570769a5d39&bH=5d24c784-08d2-1151-8b12-6b1f62d8bdf6)
Repository: vscode
Issue: AbstractContextKeyService has been disposed
Labels: error-telemetry

```javascript
Error: AbstractContextKeyService has been disposed
at g.contextMatchesRules in src/vs/platform/contextkey/browser/contextKeyService.ts:319:10
at h.createActionGroups in src/vs/platform/actions/common/menuService.ts:239:33
at u.getActions in src/vs/platform/actions/common/menuService.ts:407:25
at b in src/vs/platform/actions/browser/menuEntryActionViewItem.ts:50:22
at M in out/vs/workbench/workbench.desktop.main.js:773:142408
at updateToolbar in src/vs/platform/actions/browser/toolbar.ts:336:4
at p.y in src/vs/base/common/event.ts:1156:13
at p.fire in src/vs/base/common/event.ts:1187:9
at p.resume in src/vs/base/common/event.ts:1335:12
at <anonymous> in src/vs/base/common/event.ts:1374:10
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=e170252f762678dec6ca2cc69aba1570769a5d39&bH=5e44a0a4-e951-1dda-8bd8-e9e9e22787e0)
Repository: bitcoin
Issue: guix: SOURCE_DATE_EPOCH is already set in some environments
Labels: Build system

The environment variable `SOURCE_DATE_EPOCH` allows overriding the date that will be used inside the archives for guix-built binaries. This is an intentional feature, as documented in `contrib/guix/README.md`:

> * _**SOURCE_DATE_EPOCH**_
> 
>   Override the reference UNIX timestamp used for bit-for-bit reproducibility,
>   the variable name conforms to [standard][r12e/source-date-epoch].
> 
>   _(defaults to the output of `$(git log --format=%at -1)`)_

However, some environments, as apparently Nix, set `SOURCE_DATE_EPOCH` by default. This can be extremely confusing, as it results in mismatches. i see three options:

- Show a big red warning when the Guix build scripts are called with an existing `SOURCE_DATE_EPOCH`. Most likely it's not what the user wanted, but they can continue if they wanted.
- Disallow overriding `SOURCE_DATE_EPOCH` - unset it at start.
- Rename our `SOURCE_DATE_EPOCH` to something non-standard that doesn't conflict with Nix.

The first one has my preference.

See bitcoin-core/guix.sigs#1201 which prompted this.
Repository: flutter
Issue: Evaluate Chromium's clang toolchain
Labels: P2,team-engine,triaged-engine

The hypothesis is that the Fuchsia clang toolchain is only necessary for building the Fuchsia engine, and that the Chromium toolchain may be a better match for our use case.

The Chromium clang toolchain is pulled from google storage by this script in the Chromium tree: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/tools/clang/scripts/update.py. We can either wire that up to the DEPS file directly as a gclient hook as Chromium does, or use it to create a CIPD package in the flutter namespace.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Backwards compatibility for txt2img and img2img API calls in 1.9.x versions
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 ?

Provide backwards compatibility for the txt2img and img2img APIs

### Proposed workflow

Make the API backwards compatible for people who are already using the API in their applications by making the `txt2img` and `img2img` API calls accept the previous sampler names and automatically split the legacy sampler names into their new `sampler` and `scheduler` settings instead of failing with 404 sampler not found.

This will help people who are using the API to seamlessly upgrade to 1.9.x versions without having to rewrite any of their existing code for the API calls to function correctly.



### Additional information

_No response_
Repository: pytorch
Issue: torch.Tensor.remainder raises a floating point exception when divisor is -1
Labels: module: crash,triaged,module: edge cases

### 🐛 Describe the bug

`torch.Tensor.remainder` will raise a floating point exception when running the following code:

```python
import torch
divisor = torch.tensor(-1, dtype=torch.int32)
input = torch.tensor((-2147483648, -2147483648), dtype=torch.int32)
torch.Tensor.remainder_(input,divisor)
```

Note that if I change the input to a 1 element array `torch.tensor(-2147483648, dtype=torch.int32)`, this API can expectedly output the result. If I change the divisor to be not `-1`, this floating point exception will also not occur.


### Versions

Versions of relevant libraries:
[pip3] numpy==1.26.2
[pip3] torch==2.2.2
[pip3] triton==2.2.0
[conda] numpy                     1.26.2                   pypi_0    pypi
[conda] torch                     2.2.2                    pypi_0    pypi
[conda] triton                    2.2.0                    pypi_0    pypi
Repository: pytorch
Issue: Registering function that takes `const SymInt&` to op that accepts `SymInt` leads to cryptic error
Labels: triaged,module: custom-operators,module: dynamic shapes,module: pt2-dispatcher

```
torch::Tensor add(torch::Tensor x, const torch::SymInt& y) {
  return x + y;
}

TORCH_LIBRARY(extension_cpp, m) {
  m.def("add(Tensor x, SymInt y) -> Tensor");
}

TORCH_LIBRARY_IMPL(extension_cpp, CPU, m) {
  m.impl("add", &add);
}
```

Gives:
```
terminate called after throwing an instance of 'c10::Error'
  what():  Inferred operator schema for a C++ kernel function doesn't match the expected function schema.
  operator: extension_cpp::add
  expected schema: extension_cpp::add(Tensor x, int y) -> Tensor
    registered at /home/rzou/dev/opt-cuda1/extension-cpp/extension_cpp/csrc/lltm.cpp:95
  inferred schema: (Tensor _0, SymInt _1) -> Tensor _0
    registered at /home/rzou/dev/opt-cuda1/extension-cpp/extension_cpp/csrc/lltm.cpp:103
  reason: Type mismatch in argument 2: int vs SymInt.
```

Fix is to change `const torch::SymInt&` to `SymInt` (i.e. pass by value), but error message is pretty opaque to the user

cc @ezyang @bdhirsh
Repository: go
Issue: cmd/go: TestScript/build_cwd_newline failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/go" && test == "TestScript/build_cwd_newline"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8749944411124129025)):

    === RUN   TestScript/build_cwd_newline
    === PAUSE TestScript/build_cwd_newline
    === CONT  TestScript/build_cwd_newline
        script_test.go:136: 2024-04-22T15:43:03Z
        script_test.go:138: $WORK=/Users/swarming/.swarming/w/ir/x/t/cmd-go-test-1388592555/tmpdir4131018923/build_cwd_newline2817444750
        script_test.go:160: 
            PATH=/Users/swarming/.swarming/w/ir/x/t/cmd-go-test-1388592555/tmpdir4131018923/testbin:/Users/swarming/.swarming/w/ir/x/w/goroot/bin:/Users/swarming/.swarming/w/ir/x/w/goroot/bin:/Users/swarming/.swarming/w/ir/x/w/goroot/bin:/Users/swarming/.swarming/w/ir/cache/tools/bin:/Users/swarming/.swarming/w/ir/bbagent_utility_packages:/Users/swarming/.swarming/w/ir/bbagent_utility_packages/bin:/Users/swarming/.swarming/w/ir/cipd_bin_packages:/Users/swarming/.swarming/w/ir/cipd_bin_packages/bin:/Users/swarming/.swarming/w/ir/cipd_bin_packages/cpython3:/Users/swarming/.swarming/w/ir/cipd_bin_packages/cpython3/bin:/Users/swarming/.swarming/w/ir/cache/cipd_client:/Users/swarming/.swarming/w/ir/cache/cipd_client/bin:/Users/swarming/.swarming/cipd_cache/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
            HOME=/no-home
            CCACHE_DISABLE=1
            GOARCH=amd64
    ...
            > [GOOS:plan9] skip 'filesystem disallows \n in paths'
            [condition not met]
            # If the directory path containing a package to be built includes a newline,
            # the go command should refuse to even try to build the package. (0.002s)
            > env DIR=$WORK${/}${newline}'package main'${newline}'func main() { panic("uh-oh")'${newline}'/*'
            > mkdir $DIR
            > cd $DIR
            > exec pwd
        script_test.go:160: FAIL: testdata/script/build_cwd_newline.txt:11: exec pwd: exec: "pwd": executable file not found in $PATH
    --- FAIL: TestScript/build_cwd_newline (0.01s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: proposal: time: add a non allocating way to marshal Time in the binary format
Labels: Proposal

### Proposal Details

Hi,

I wrote a zero allocation marshaller with [mus-go](https://github.com/mus-format/mus-go) for a struct that contains a lot of `time.Time`. Unfortunately, it still allocates because of `time.MarshalBinary()`.

I played a bit with the standard library and implemented another version of `time.MarshalBinary() ([]byte, error)` that does not allocate (see: https://github.com/sylr/go/commit/384f060cc8da29846bc381beadbd6881010ebb3f).

Here are the results:
```
goos: darwin
goarch: arm64
pkg: utils/nats
cpu: Apple M2
                   │    old.txt    │              new5.txt               │
                   │    sec/op     │   sec/op     vs base                │
Encoders/mus/raw-8   15.259µ ± 91%   6.268µ ± 0%  -58.92% (p=0.000 n=10)

                   │   old.txt    │             new5.txt             │
                   │    bytes     │    bytes      vs base            │
Encoders/mus/raw-8   4.001Ki ± 0%   4.001Ki ± 0%  ~ (p=1.000 n=10) ¹
¹ all samples are equal

                   │   old.txt    │               new5.txt                │
                   │     B/op     │     B/op      vs base                 │
Encoders/mus/raw-8   1.562Ki ± 0%   0.000Ki ± 0%  -100.00% (p=0.000 n=10)

                   │  old.txt   │              new5.txt              │
                   │ allocs/op  │ allocs/op  vs base                 │
Encoders/mus/raw-8   100.0 ± 0%    0.0 ± 0%  -100.00% (p=0.000 n=10)
```

I'm wondering if we could merge something like this, possible implementations I could think of are:

 - `func(t time.Time) Read(p []byte) (int, error)` (what I implemented in https://github.com/sylr/go/commit/384f060cc8da29846bc381beadbd6881010ebb3f)
 - `func(t time.Time) ReadBinary(p []byte) (int, error)` (same as previous but does not satisfy io.Reader to avoid implementing a known interface for a specific encoding)
 - A separate wrapper.
   - `type BinaryReader struct { Time }`
   - `func(r BinaryReader) Read(p []byte) (int, error)`
Repository: go
Issue: internal/trace/v2: TestTraceWaitOnPipe failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "internal/trace/v2" && test == "TestTraceWaitOnPipe"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/55708007996602d9cf6f7eaac08915febdb982be)):

    --- FAIL: TestTraceWaitOnPipe (0.00s)
        --- FAIL: TestTraceWaitOnPipe/Default (0.00s)
            trace_test.go:575: context deadline exceeded


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: neovim
Issue: Windows: treesitter language parsers are not released, preventing reinstallation
Labels: bug,system,treesitter,filesystem

### Problem

Neovim opens language parsers in a way that blocks other processes from overwriting them, and does not release the associated file handle until Neovim closes. This prevents the reinstallation and upgrade of language parsers on Windows after the parser has been loaded.

### Steps to reproduce

These reproduction steps use `lazy.nvim` and `nvim-treesitter`, but manually installing a parser where Neovim can pick it up will trigger the error as well.

1. Install a language parser like `:TSInstall rust`, or manually by installing it in the correct directory for Neovim to find it.
2. Close Neovim if it was open, then open a file that uses an installed parser.
3. Inspect the tree with `:InspectTree` (this is just one way of being sure the language parser was loaded)
4. Close the tree and the buffer if you want, but keep the same instance of Neovim open.
5. Attempt to reinstall the language parser (or manually replace it).
6. Observe an error indicating access is denied.

I'm not sure why, but reinstalling immediately after the initial installation results in no message at all.

For reference, I reproduced this initially with a simple `init.lua`:

```lua init.lua
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not (vim.uv or vim.loop).fs_stat(lazypath) then
	vim.fn.system({
		"git",
		"clone",
		"--filter=blob:none",
		"https://github.com/folke/lazy.nvim.git",
		"--branch=stable", -- latest stable release
		lazypath,
	})
end
vim.opt.rtp:prepend(lazypath)

require("lazy").setup({
	"nvim-treesitter/nvim-treesitter",
	branch = "main",
	build = ":TSUpdate",
	lazy = false,
})
```

Then I tried to rule out the involvement of `nvim-treesitter` and even `lazy.nvim` by cleaning out the configuration and data files, leaving behind only `C:\Users\User\AppData\Local\nvim-data\site`, which held the parser in `parser\rust.so`. Then I just used a sanity-check `init.lua`:

```lua init.lua
print("Hello, world!")
```

The problem still occurred.

Windows has a way of [locking files](https://superuser.com/questions/1500604/why-cant-you-change-the-name-of-an-open-file-in-windows), depending on how they are opened, so it seems like that is causing the problem, which is made worse because they don't seem to be closed until Neovim itself is closed.

### Expected behavior

I would expect treesitter language parsers to be replaceable, even when in use, so they can always be upgraded from within Neovim.

### Neovim version (nvim -v)

0.10.0-dev-2976+g208852126

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

no?

### Operating system/version

Windows 10 Pro 22H2

### Terminal name/version

Windows Terminal 1.19.10821.0

### $TERM environment variable

N/A - it's empty

### Installation

Downloaded `nvim-win64.zip` from the repository's release assets, but it also exists in 0.9.x versions installed with `winget`, including 0.9.5.
Repository: flutter
Issue: Support privacy manifests for non-plugin packages calling required reason APIs directly via FFI
Labels: tool,a: build,P2,team-ios,triaged-ios

We have a privacy manifest system in place for plugins that allows plugin developers to declare [required reason API](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api) usage. However, I didn't consider the case of a non-plugin, pure-Dart package that uses FFI to directly call required reason APIs; we should have a way for packages doing that to declare a manifest and have it bundled into App.framework.

We could probably do this in the Flutter tool, by having it create privacy manifest bundles in App.framework (like what Cocoapods does for static linking). We'd need a way for package developers to declare a manifest that we would bundle; probably a `flutter:` sub-entry in `pubspec.yaml` is the best option?

In the meantime, the workaround for this (hopefully very rare) case would be either:
- As the package developer, declare your package as a plugin instead—the native code can be essentially a no-op—and use the podspec (or later, SPM) to bundle a manifest.
- As an app developer, include the reasons at the app level.