sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Using force-cache prevents revalidation
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/fetchcache-issue-h6gsf2

### To Reproduce

1. Start the application
2. Refresh the page
3. Notice that it will **always** get the API call from cache and it will **never** revalidate

### Current vs. Expected behavior

The cache is never revalidated, while it should (in this case every 5 seconds). 

Note that the page is dynamic, so the issue is not that the page itself is statically rendered, but that, even when it is rendered dynamically, it uses the existing cache all the time and never revalidates.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
  Available memory (MB): 16298
  Available CPU cores: 16
Binaries:
  Node: 20.10.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: 14.2.4
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next dev (local), Vercel (Deployed)

### Additional context

Same issue on CodeSandbox, which is on NextJS 15 canary.
In general, the revalidate setting does not seem to work when using force-cache.
Repository: rust
Issue: MC/DC LLVM 19 intrinsics changes
Labels: A-LLVM,C-enhancement,T-compiler

In LLVM 19 some details about MC/DC changed, removing and updating some intrinsics:
* https://github.com/llvm/llvm-project/commit/85a7bba7d28365ff98dae74f20ebf9f53d42023a
In  instrprof_mcdc_condbitmap_update intrinsic was dropped recently:
* https://github.com/llvm/llvm-project/pull/95496

I tried naively to remove the reference to the removed intrinsic https://github.com/rust-lang/rust/pull/126582, but that's incomplete. Will need more work to adapt to this it seems:
* https://github.com/llvm/llvm-project/pull/95496#issuecomment-2173006812
Repository: ant-design
Issue: Tabs extra content raises an a11y error
Labels: help wanted,Inactive,⌨️ Accessibility,unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-r9muc3)

### Steps to reproduce

Run Lighthouse or any other a11y tool inside your browser

### What is expected?

No a11y errors

### What is actually happening?

It raises an ARIA error: 
"Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children."

The error is caused by the tabs' extra content

Same for the Remove and Add Tab buttons: https://ant.design/~demos/tabs-demo-editable-card

| Environment | Info |
| --- | --- |
| antd | 5.18.3 |
| React | 18.3.1 |
| System | N/A |
| Browser | Edge |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: mut in slice pattern: `[_, mut @ ..] = &[...]` is not needed?
Labels: A-diagnostics,T-compiler,A-slice-patterns,A-patterns

Might be related to https://github.com/rust-lang/rust/issues/123076

### Code

```Rust
fn foo(s: &[usize]) {
    let [a, b @ ..] = s else {panic!()};
    let [a, mut b @ ..] = s else {panic!()};
}
```


### Current output

```Shell
error[E0277]: the size for values of type `[usize]` cannot be known at compilation time
 --> src/lib.rs:3:13
  |
3 |     let [a, mut b @ ..] = s else {panic!()};
  |             ^^^^^^^^^^ doesn't have a size known at compile-time
  |
  = help: the trait `Sized` is not implemented for `[usize]`
  = note: all local variables must have a statically known size
  = help: unsized locals are gated as an unstable feature

For more information about this error, try `rustc --explain E0277`.
error: could not compile `playground` (lib) due to 1 previous error
```


### Desired output

```Shell
3 |     let [a, mut b @ ..] = s else {panic!()};
  |             ^^^^^^^^^^ doesn't have a size known at compile-time
                ^^^ help: remove this `mut` because ...
```


### Rationale and extra context

I use `mut b @ ..` because I would like to change b later.
But removing `mut` makes it compile. So my thoughts are misleading.

### Other cases

_No response_

### Rust Version

```Shell
Nightly version: 1.81.0-nightly

(2024-06-18 8fcd4dd08e2ba3e922d9)
```


### Anything else?

_No response_
Repository: godot
Issue: Viewport does not retain new camera settings when set via EditorPlugin
Labels: bug,topic:editor,topic:plugin

### Tested versions

Reproducible in v4.3.beta.custom_build [71699e08c], 4.2.2

### System information

Windows 10 Mobile

### Issue description

I want to write and EditorPlugin that has the ability to update the viewport camera.  While I can do this using 
```
				var view3d:SubViewport = EditorInterface.get_editor_viewport_3d(0)
				var cam:Camera3D = view3d.get_camera_3d()
				cam.global_transform = my_transform
```

as soon as I next move the camera the view snaps back to what it was before and completely ignores the new transform I set.

I would like to be able to somehow update the viewport camera transform and have that be recognized by the viewport tumble and right-click fly tools as the new camera transform.

### Steps to reproduce

Install the addon in the attached file.  Press F3 to set the viewport camera to the identity transform.  Then try to tumble the view in the viewport or right-click fly.  The camera settings you just set are ignored and these tools will use the previous camera transform instead.

### Minimal reproduction project (MRP)

[hack-editor-viewport-camera.zip](https://github.com/user-attachments/files/15898164/hack-editor-viewport-camera.zip)
Repository: pytorch
Issue: Add comment for label_smoothing parameter in torch.nn.CrossEntropyLoss 
Labels: module: docs,module: nn,triaged

### 🚀 The feature, motivation and pitch

There should be a hint or small warning for using `CrossEntropyLoss` with the parameter `label_smoothing`. Why you ask? I think for most use cases the user defines the same loss criterion for train and test/validation loops. Which makes perfectly sense!

However when you set the parameter `label_smoothing` you need an additional criterion on the test set, since you do not want to distort your target labels. I mean you would not smooth your labels during inference as well right?

However this can be quickly overseen at the moment. I can not think of a case where `label_smoothing `would be beneficial in a test/validation loop, so hard coding it would be an option, but would also add boiler code. I think documenting it in the docs would be fine, just writing a line like "If you use this parameter, define an additional loss criterion for your test loop, so that your true target labels are not distorted".

Maybe I also have a wrong thought here, correct me if I am wrong :)

Best regards

### Alternatives

_No response_

### Additional context

_No response_

cc @svekars @brycebortree @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: neovim
Issue: autowrite when receiving SIGHUP, SIGQUIT
Labels: enhancement,complexity:low,system,events

### Problem

Currently (at least with neovim 0.10.0) when `autowrite` or `autowriteall` is set the buffers are not being written out when neovim receive a deadly signal such as SIGHUP or SIGQUIT.

### Expected behavior

Neovim should try to write out the buffers as it would with a normal exit in cases like this as this would be what one expects when they set `autowrite` or `autowriteall`.
Repository: node
Issue: Option to have a shared V8 library?
Labels: help wanted,v8 engine,feature request

### What is the problem this feature will solve?

In distros like NixOS and GuixSD, building NodeJS from scratch is a heavy computation. Building V8 seperately for NodeJS is not only computationally heavy, but it also makes caching the good parts of the library impossible for a simple failed test. It is painful having to wait for a day to have a package build, only for the tests to fail for the package maintainer to disable or patch them one by one per build.

### What is the feature you are proposing to solve the problem?

 With V8 as a shared library, it would be possible to not only cache the dependency in a functional package manager, but also use it with other packages that require them.

### What alternatives have you considered?

None, as I've read somewhere than v8 dependencies are patched, which would make it impossible to use vanilla v8 alongside.
Repository: godot
Issue: `SpinBox` and `EditorSpinSlider` do not take into account that `min_value` may have more decimals than `step`
Labels: bug,topic:gui

### Tested versions

- Reproducible in 4.3 dev.

### System information

Kubuntu 24.04

### Issue description

`SpinBox` and `EditorSpinSlider` use `step`'s decimals to round the displayed value. However, this does not take into account that `min_value` may not be a multiple of `step`, so the `value` may have more decimals than `step`:

Here `value` is snapped to 0.2, 3.2, 6.2, 9.2, ...:
![](https://github.com/godotengine/godot/assets/47700418/534f5570-1069-4257-a369-7b31192079f9)

`print($SpinBox.value)` also outputs `3.2`, not `3`.

* See also https://github.com/godotengine/godot/issues/93332#issuecomment-2178122183.

---

https://github.com/godotengine/godot/blob/9a4942f2f59af3c9a17187e0ed20ffa40d5f9514/scene/gui/spin_box.cpp#L43-L47

https://github.com/godotengine/godot/blob/9a4942f2f59af3c9a17187e0ed20ffa40d5f9514/editor/gui/editor_spin_slider.cpp#L47-L49

```c++
void SpinBox::_update_text(bool p_keep_line_edit) {
    print_line(get_value()); // 3.2
    String value = String::num(get_value(), Math::range_step_decimals(get_step()));
    print_line(value); // 3
```

### Steps to reproduce

See above.

### Minimal reproduction project (MRP)

N/A
Repository: stable-diffusion-webui
Issue: [Feature Request]: `Add number to filename when saving` gives choice between `as a prefix`/`as a suffix`
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 ?

Say one want to cherry-pick images from SD outputs (automatically or simply without using the "save" button of the webUI) and gather them in a single folder. These images comes from different times/_working sessions_ so from different folders (for example: `outputs/<date>/<filename>`) where filename is `[number]-<your_pattern>.ext`.

It means that once gathered in a single directory, images will be ordered by [number] and mixed...
If one would be able to use [number] as a suffix (`<your_pattern>-[number].ext`), one would be able to have a nice "sorted by default" content without any hassle (I'm thinking [date] especially as a pattern).

### Proposed workflow

1. Go to `Settings` > `Saving images/grids`
2. Checked by default: `Add number to filename when saving`
3. Select `as a prefix` (default) or `as a suffix`.


### Additional information

_No response_
Repository: pytorch
Issue: return type of torch.nn.functional.interpolate not working
Labels: module: typing,triaged,module: interpolation

### 🐛 Describe the bug

Despite having it in the signature, the interpolate function is shown with an unknown return type using pylance in vscode. 
I assume the reason is, that the following functions are not defined in the corresponding python file:
in torch._C._nn:
upsample_nearest1d
upsample_nearest2d
upsample_nearest3d
_upsample_nearest_exact1d
_upsample_nearest_exact2d
_upsample_nearest_exact3d
upsample_linear1d
_upsample_bilinear2d_aa
upsample_bilinear2d
upsample_trilinear3d
_upsample_bicubic2d_aa
upsample_bicubic2d
are missing.

Another suggestion is more general, should we call pass after an overloaded function? It violates the return value.
I would suggest calling such a function
```@_overload  # noqa: F811
def interpolate(input: Tensor, size: Optional[int] = None, scale_factor: Optional[List[float]] = None, mode: str = 'nearest', align_corners: Optional[bool] = None, recompute_scale_factor: Optional[bool] = None, antialias: bool = False) -> Tensor:  # noqa: F811,B950
    pass
```

with an 
    raise NotImplementedError
instead of an pass.

My type checker also shows me that `input.size(i + 2).float()` called in the interpolate function will crash when called.

### Versions

PyTorch 2.3.1

cc @ezyang @malfet @xuzhao9 @gramster
Repository: kubernetes
Issue: client-go: fake.Clientset doesn't support streaming custom logs
Labels: sig/api-machinery,kind/feature,triage/accepted

### What happened?

As part of the changes done in https://github.com/kubernetes/kubernetes/pull/91485, the `GetLogs` handler of the `FakePods` was corrected to return a constant log message of "fake logs"

As part of the `GetLogs` handler 

https://github.com/kubernetes/kubernetes/blob/d1c7f7a0e9d59aa88aa5b4d07db7e14772b3e386/staging/src/k8s.io/client-go/kubernetes/typed/core/v1/fake/fake_pod_expansion.go#L58-L66

We invoke the `c.Fake.Invokes` and discard the result from it and return a constant value back. 

This makes it impossible to return a custom log message back from the `GetLogs` handler.

[This came into view when I was experimenting something around providing an offline mechanism to invoke the](https://github.com/k8sgpt-ai/k8sgpt/pull/1162) `k8sgpt` using the extracted logs. 

I was attempting to use the fake test client to return the expected value back from the data files stored on disk and I was unable to implement  the `GetLogs` to return the actual pod logs stored on the disk. 



### What did you expect to happen?

`client-go` to provide a clean way to return custom logs from the `GetLogs` handler using either `PrependProxyReactor` or `AddProxyReactor`

### How can we reproduce it (as minimally and precisely as possible)?

Create a fake client and add a custom Proxy reactor like below. 

```golang
fakeClient.PrependProxyReactor("*", func(action testing.Action) (handled bool, ret rest.ResponseWrapper, err error) {
		if action.GetSubresource() == "log" {
			resp := &fakerest.RESTClient{
				Client: fakerest.CreateHTTPClient(func(request *http.Request) (*http.Response, error) {
					resp := &http.Response{
						StatusCode: http.StatusOK,
						Body:       io.NopCloser(strings.NewReader("my custom logs")),
					}
					return resp, nil
				}),
				NegotiatedSerializer: scheme.Codecs.WithoutConversion(),
				GroupVersion:         action.GetResource().GroupVersion(),
				VersionedAPIPath:     "/api/v1/namespaces/test/pods/test-1/log",
			}
	return fakeClient.Request()
			return true, resp.Request(), nil
		}
		return false, nil, nil
	})
```

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: rust
Issue: `-Zoom=panic` double panic due to panicking allocating
Labels: T-compiler,C-bug,A-panic

We had an abort in production from `fn begin_panic_handler`, specifically `FormatStringPayload`, allocating during an OoM panic, triggering a second OoM panic and thus abort.

https://github.com/rust-lang/rust/blob/a07f3eb43acc5df851e15176c7081a900a30a4d7/library/std/src/panicking.rs#L593-L615

From that file it looks like there may be other allocations also. Perhaps it's possible to avoid them on the OoM panic path.

cc:
* #43596
* #88098
* #115974
* https://github.com/rust-lang/unsafe-code-guidelines/issues/506

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.79.0-nightly (a07f3eb43 2024-04-11)
binary: rustc
commit-hash: a07f3eb43acc5df851e15176c7081a900a30a4d7
commit-date: 2024-04-11
host: aarch64-apple-darwin
release: 1.79.0-nightly
LLVM version: 18.1.3
```

<details><summary>Backtrace</summary>
<p>

```text
// target = wasm32-unknown-unknown

std::panicking::rust_panic_with_hook::he5ab6644a2777339
        at <unknown>
std::panicking::begin_panic_handler::{{closure}}::hbc8949711eb93f07
        at <unknown>
std::sys_common::backtrace::__rust_end_short_backtrace::h43c6e6030cfac424
        at src/sys_common/backtrace.rs
rust_begin_unwind
        at <unknown>
core::panicking::panic_fmt::hd059f920eb86b234
        at src/panicking.rs
std::alloc::default_alloc_error_hook::hf29909cb78062dee
        at <unknown>
__rg_oom
        at src/alloc.rs
__rust_alloc_error_handler
        at <unknown>
alloc::alloc::handle_alloc_error::h77f60f5703455990
        at src/alloc.rs
alloc::raw_vec::handle_error::h2651e03894002f2d
        at src/raw_vec.rs
alloc::raw_vec::RawVec<T,A>::reserve::do_reserve_and_handle::h010686df1ee1f672
        at <unknown>
<alloc::string::String as core::fmt::Write>::write_str::h78dc7b49e79e749d.23038
        at lib/rustlib/src/rust/library/alloc/src/string.rs
core::fmt::write::hebf5ad877658ea5c
        at <unknown>
<std::panicking::begin_panic_handler::FormatStringPayload as core::panic::PanicPayload>::get::h8680c05bc1165a6c
        at <unknown>
std::panicking::rust_panic_with_hook::he5ab6644a2777339
        at <unknown>
std::panicking::begin_panic_handler::{{closure}}::hbc8949711eb93f07
        at <unknown>
std::sys_common::backtrace::__rust_end_short_backtrace::h43c6e6030cfac424
        at src/sys_common/backtrace.rs
rust_begin_unwind
        at <unknown>
core::panicking::panic_fmt::hd059f920eb86b234
        at src/panicking.rs
std::alloc::default_alloc_error_hook::hf29909cb78062dee
        at <unknown>
__rg_oom
        at src/alloc.rs
__rust_alloc_error_handler
        at <unknown>
alloc::alloc::handle_alloc_error::h77f60f5703455990
        at src/alloc.rs
<generic_btree::map::binding::Binding<K,V> as core::clone::Clone>::clone::h5d7cc23d7389cd6e
        at <unknown>

```

</p>
</details>
Repository: puppeteer
Issue: [Feature]: Provide a way to debug tests when launching via ng-schematics
Labels: feature,confirmed,@puppeteer/ng-schematics,P3

### Feature description

I'd like to be able to launch the runner appropriately for debugging, e.g. via a sibling option to `testRunner` in `angular.json`.

Currently, using Jest as an example, this seems to only be possible by modifying `getCommandForRunner()`:

```
// return [`jest`, '-c', 'e2e/jest.config.js'];
return ['node', '--inspect-brk', `node_modules/jest/bin/jest.js`, '--runInBand', '-c', 'e2e/jest.config.js'];
```
Repository: terminal
Issue: Pasting multiline text not working (in shell, vi and hangs kakoune) 
Labels: Area-Input,Issue-Bug,Product-Terminal,Priority-2

### Windows Terminal version

1.21.1382.0

### Windows build number

10.0.19045.4291

### Other Software

QEMU 9.0 with FreeBSD 14.1 guest. 
vi 2.2.1 
kakoune-2024.05.18 

Evironment:
TERM=xterm-256color

### Steps to reproduce

Copy multiline text:
```
builder {
        host.hostname = "builder";
        path = "/ws/builder";
        ip4 = "inherit";
        #ip4.addr = "igb0|192.168.0.28/25";
        #ip4.addr = "lo0|127.0.3.1/24";
        allow.raw_sockets = 1;
        exec.consolelog = "/var/log/jails/${name}_console.log";
        #mount.fdescfs;
    #mount.fstab="/etc/ws/${name}.fstab";
        mount.procfs;
        allow.set_hostname = 0;
        exec.start = "/bin/sh /etc/rc";
        exec.stop = "/bin/sh /etc/rc.shutdown";
        exec.clean;
        allow.mount;
    allow.mount.zfs;
    allow.mount.nullfs;
```
1. Run `vi` editor. Press `i` for insert mode. Paste text.
2. Run `vi` editor. Press `\i`  for insert mode with no-hook processing. Paste text.

### Expected Behavior

Pasted text inside editor.

### Actual Behavior

1. `vi` editor. WindowsTerminal ask about pasting multiline text.  Then only two lines of text pasted:
![image](https://github.com/microsoft/terminal/assets/11061796/2c70ee6f-0b00-4238-a9ef-8e1d05b4dc77)

2. `kakoune` editor. WindowsTerminal do not ask about pasting multiline text. Nothing happen on screen but `kakoune` hangs in mean of not responding to any key press:

![image](https://github.com/microsoft/terminal/assets/11061796/59ffc4eb-6c99-4897-b17b-6120b5e8d6e0)

Also in a pure `sh` shell pasting behave like in `vi` (pasted only first two lines):

![image](https://github.com/microsoft/terminal/assets/11061796/8a4a15cf-f972-4f7d-b00e-94c63fc52a7a)
Repository: ant-design
Issue: aria-required does not match the role of form items
Labels: help wanted,Inactive,⌨️ Accessibility,unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-9ylnlp?file=demo.tsx)

### Steps to reproduce

Add a Form.Item with a required rule, the form component should be a Select (but some other components are affected too)

Run an a11y tool in your browser

### What is expected?

no a11y errors

### What is actually happening?

<div class="ant-select ant-select-outlined ant-select-in-form-item css-var-r6 ant-sele…" aria-required="true">

this element raises an error:
[aria-*] attributes do not match their roles

DatePicker breaks a11y rules too.

| Environment | Info |
| --- | --- |
| antd | 5.18.3 |
| React | 18.3.1 |
| System | N/A |
| Browser | Edge |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: LineEdit breaks when using circumflex or acute accent characters
Labels: bug,platform:linuxbsd,topic:porting,topic:input

### Tested versions

- Tested in v4.2.2.stable.mono.official [15073afe3]

### System information

Godot v4.2.2.stable.mono - Debian GNU/Linux trixie/sid trixie - X11 - GLES3 (Compatibility)

### Issue description

I have a German keyboad layout (QWERTZ) and there are these accent characters on the keyboard to make foreign characters like ^ or ` to make â / á or something similar.

When i type in a LineEdit and accidentally hit one of these characters the LineEdit breaks and won't react to any new input the only way to fix it is to delete and create a new LineEdit but it is not easy to detect when its broken because godot doesn't recognize these special characters (^ / ´) when i access the Text property.
![image](https://github.com/godotengine/godot/assets/75847613/24336009-d327-4df6-90a4-a2f72e8bbfe0)


### Steps to reproduce

1. Create new Project
2. Add a LineEdit / TextEdit
3. Type "hello^everything after this is not working"

### Minimal reproduction project (MRP)

[MRP.tar.gz](https://github.com/user-attachments/files/15901169/MRP.tar.gz)
Repository: go
Issue: proposal: x/tools/cmd/eg: build tags support 
Labels: help wanted,Proposal

### Proposal Details

Currently `eg` does not support custom build tags. It will be great if it could refactor files including those guarded by build tags.