sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: bitcoin
Issue: bitcoind shouldn't be shutdown automatically despite wallet synchronisation error
Labels: Wallet

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behaviour

Bitcoind startup is terminated.

### Expected behaviour

bitcoind should complete startup and keep running successfully.

### Steps to reproduce

Step:
`$ ./bitcoind`

### Relevant log output

Result (logs):
Keys: 9 plaintext, 0 encrypted, 0 w/ metadata, 9 total. Unknown wallet records: 0
Wallet completed loading in             326ms
Error: Prune: last wallet synchronisation goes beyond pruned data. You need to -reindex (download the whole blockchain again in case of pruned node)
Error: Prune: last wallet synchronisation goes beyond pruned data. You need to -reindex (download the whole blockchain again in case of pruned node)
Shutdown: In progress...
scheduler thread exit
Shutdown: done

### How did you obtain Bitcoin Core

Compiled from source

### What version of Bitcoin Core are you using?

master

### Operating system and version

Linux

### Machine specifications

_No response_
Repository: rust
Issue: const_heap feature can be used to leak mutable memory into final value of constant
Labels: P-low,A-const-eval,F-const_mut_refs,requires-incomplete-features,F-core_intrinsics,F-const_heap

Consider this code:
```rust
#![feature(core_intrinsics)]
#![feature(const_heap)]
#![feature(const_mut_refs)]
use std::intrinsics;

const BAR: *mut i32 = unsafe { intrinsics::const_allocate(4, 4) as *mut i32 };

fn main() {}
```
This code is problematic because when `BAR` is used multiple times in the program, it will always point to the same global allocation, violating the idea that consts behave as-if their initializer is inlined everywhere they are used. Furthermore, under our current interning strategy this allocation will end up being immutable in the runtime phase of the program, so writing it is UB, which could be quite surprising.

We have a safety net in the interner that catches this problem, but the safety net has a big gaping hole around shared references with interior mutability, and can hence easily be circumvented:
```rust
#![feature(core_intrinsics)]
#![feature(const_heap)]
#![feature(const_mut_refs, const_refs_to_cell)]

use std::intrinsics;
use std::cell::Cell;

const BAR: *mut i32 = unsafe {
    let launder = &*(intrinsics::const_allocate(4, 4) as *const Cell<i32>);
    launder as *const _ as *mut i32
};

fn main() {}
```
The gaping hole in the safety net is needed due to https://github.com/rust-lang/rust/issues/121610 and https://github.com/rust-lang/unsafe-code-guidelines/issues/493; also see the description of https://github.com/rust-lang/rust/pull/128543 for more context.

This seems like a pretty major blocker for the const_heap feature, unless we want to just declare this UB "ex machina".

Cc @rust-lang/wg-const-eval 
(Not something to be discussed any time soon, I am filing this because tidy forced me to have an issue number for the ICE that ensues from this mutable-ref-escape-prevention-bypass.)
Repository: excalidraw
Issue: Auto Scroll for handwriting quickly
Labels: UX/UI,tablet

https://twitter.com/hata6502/status/1604471663462330368
[![Image from Gyazo](https://i.gyazo.com/571b5e987c6c7cdb100c9b3007701ee3.gif)](https://gyazo.com/571b5e987c6c7cdb100c9b3007701ee3)
Full-scratched demo app (touch devices only)
https://hata6502.github.io/handled/

When using a tablet for **study purposes**, we like to take handwritten notes as quickly as **with pen and paper**.
However, with the short width of a tablet, alternating between writing and manual scrolling may seem cumbersome.

Scrolling automatically and smoothly handwrite makes note-taking a little easier.
Repository: godot
Issue: All BoneAttachment3D stays in Skeleton3D's origin until pose is updated
Labels: bug,topic:animation

### Tested versions

- Reproducible on v4.3.stable.official [77dcf97d8]

### System information

Win11 - v4.3.stable.official [77dcf97d8] - Renderer independent

### Issue description

BoneAttachment3D does not initially update it's pose until very first bone pose update and stays at `Skeleton3D`'s origin. However, in `.glb` preview it shows up normally - Refer project & demonstration video below on MRE.

### Steps to reproduce

Either:
  - Load gltf from blender that has armature and bone-parented object
  - Add BoneAttachment3D in runtime

### Minimal reproduction project (MRP)

[armaturetest.zip](https://github.com/user-attachments/files/16648655/armaturetest.zip)

Demonstration: https://www.youtube.com/watch?v=yAywnXm9cEw
Repository: ui
Issue: [bug]: Select Component Value Not Persisting After Page Reload
Labels: bug

### Describe the bug

The Select component is not maintaining its selected value after a page reload, even when the value is being saved to and retrieved from localStorage.

### Affected component/components

Select

### How to reproduce

1- Create a new component using the Select component from shadcn/ui.
2- Implement localStorage to save and retrieve the selected value.
3- Select a value from the dropdown.
4- Reload the page.

**Expected Behavior:**

The Select component should display the previously selected value after page reload. 

**Actual Behavior:**

The Select component resets to its default state (showing the placeholder) after page reload, even though the correct value is being retrieved from localStorage.

Code Example:
```js
"use client";

import { useEffect, useState } from "react";
import {
  Select,
  SelectContent,
  SelectItem,
  SelectTrigger,
  SelectValue,
} from "@/components/ui/select";

const TestComp = () => {
  const [mode, setMode] = useState<string | undefined>(undefined);

  useEffect(() => {
    const keyMode = localStorage.getItem("keyMode");
    if (keyMode) {
      setMode(keyMode);
    }
  }, []);

  useEffect(() => {
    if (mode !== undefined) {
      localStorage.setItem("keyMode", mode);
    }
  }, [mode]);

  return (
    <div>
<form>
      <Select value={mode} onValueChange={(value) => setMode(value)}>
        <SelectTrigger className="w-[180px]">
          <SelectValue placeholder="Select mode" />
        </SelectTrigger>
        <SelectContent>
          <SelectItem value="fast">Fast ⚡</SelectItem>
          <SelectItem value="quality">Quality 💎</SelectItem>
        </SelectContent>
      </Select>

      <div>Mode: {mode || "Not selected"}</div>
    </div>
  <Button type="submit">Submit</Button>
      </form>
  );
};

export default TestComp;
```


### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Next.js version: 14.2.3
React version: 18
Browser: Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: godot
Issue: Visual shader curve node displays different result while dragging
Labels: bug,topic:gui,topic:2d

### Tested versions

4.3

### System information

Godot v4.3.stable - Nobara Linux 40 (GNOME Edition) - Wayland - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 3050 Ti Laptop GPU - 11th Gen Intel(R) Core(TM) i7-11370H @ 3.30GHz (8 Threads)

### Issue description

I've tested this in various projects in both Linux and Windows, and I see similar behavior. While you are dragging in the curve node, a different result is displayed compared to when you finally release the mouse button/trackpad.


https://github.com/user-attachments/assets/33565fdb-0d96-451c-ac6d-18176590a982


https://github.com/user-attachments/assets/69e41896-ea93-40bf-89ef-0bf7b66d28b7


I hope it's obvious that the 3D viewport looks quite different depending on when I'm moving the mouse, vs when I'm releasing the mouse.

Also, the first time I drag the mouse button in the corner I get the weird light colors, but the second time I drag it into the corner I get the "good" colors, so that's a workaround (but I don't think it should be necessary).

### Steps to reproduce

1. Open the example project
2. Drag around a bit in the graph node and observe the behavior

### Minimal reproduction project (MRP)

[CurveTest.zip](https://github.com/user-attachments/files/16648809/CurveTest.zip)
Repository: rust
Issue: `-Zthreads` is slower the more cores I add
Labels: WG-compiler-performance,S-needs-repro

In my crates I haven't actually gotten a speedup from more threads. In fact, quite the opposite! 
The more threads I add the slower it becomes, `1` being the fastest.
```
rustc --version
rustc 1.82.0-nightly (91376f416 2024-08-12)
```
Repository: rust
Issue: `std::fs::canonicalize` failed to process path mounted with cppcryptfs/dokan under windows
Labels: O-windows,C-bug,T-libs,A-io

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
use std::fs::canonicalize;

pub fn main() {
    println!("{}", canonicalize("F:\\gofs").unwrap().display());
    // Where F:\gofs is a path mounted with cppcryptfs which use Dokan library.
}
```

I expected to see this happen:  
print `\\?\F:\gofs`.

Instead, this happened:
```
thread 'main' panicked at src/main.rs:5:45:
called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "系统找不到指定的文件。" }
```

I have double checked that `F:\gofs` is exist and accessible.

### 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.80.1 (3f5fd8dd4 2024-08-06)
binary: rustc
commit-hash: 3f5fd8dd41153bc5fdca9427e9e05be2c767ba23
commit-date: 2024-08-06
host: x86_64-pc-windows-msvc
release: 1.80.1
LLVM version: 18.1.7
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library\std\src\panicking.rs:652
   1: core::panicking::panic_fmt
             at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library\core\src\panicking.rs:72
   2: core::result::unwrap_failed
             at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library\core\src\result.rs:1679
   3: enum2$<core::result::Result<std::path::PathBuf,std::io::error::Error> >::unwrap
             at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23\library\core\src\result.rs:1102
   4: test_dunce::main
             at .\src\main.rs:5
   5: core::ops::function::FnOnce::call_once<void (*)(),tuple$<> >
             at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23\library\core\src\ops\function.rs:250
   6: core::hint::black_box
             at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23\library\core\src\hint.rs:338
```

</p>
</details>
Repository: godot
Issue: Cannot download export template from macOS editor
Labels: bug,platform:macos,needs testing,topic:network

### Tested versions

Godot 4.3 stable

### System information

Godot v4.3.stable - macOS 14.6.1 - Vulkan (Mobile) - integrated Apple M1 - Apple M1 (8 Threads)

### Issue description

I am trying to download the android build template for Godot but get an error saying Can't connect to the mirror



### Steps to reproduce

Create a Godot Project. Click Project => Install Android Build Template => Click Manage Templates => Click Download & Install

### Minimal reproduction project (MRP)


https://github.com/user-attachments/assets/f4eea114-d009-4d11-98b4-1348cb844ddf
Repository: pytorch
Issue: torch._dynamo.utils.istype type inference is broken
Labels: module: typing,triaged,OSS contribution wanted,oncall: pt2,module: dynamo

### 🐛 Describe the bug

```
@overload
def istype(
    obj: object, allowed_types: Type[T]
) -> TypeIs[T]: ...
  
@overload
def istype(
    obj: object, allowed_types: Tuple[Type[Unpack[Ts]]]
) -> TypeIs[Union[Unpack[Ts]]]: ...
```
it should be more something like this. Currently, it is not narrowing correctly.

Everything is being overladed by the non-typeguarded iterable boolean overload which is breaking everything unfortunately.

### Versions

master

cc @ezyang @malfet @xuzhao9 @gramster @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
Repository: node
Issue: server.listen's bind argument does not accept [::] for ipv6
Labels: dns,net

### Version

22, 20

### Platform

```text
Darwin the-beast-kitten.local 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:46 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6031 arm64
```


### Subsystem

net or dns

### What steps will reproduce the bug?

```js
require('http').createServer((req, res) => {
  res.statusCode = 200;
  res.end("OK");
}).listen(4001, '[::]');
```

Outputs:

```
node:events:497
      throw er; // Unhandled 'error' event
      ^

Error: getaddrinfo ENOTFOUND [::]
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26)
Emitted 'error' event on Server instance at:
    at GetAddrInfoReqWrap.doListen [as callback] (node:net:2132:12)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:17) {
  errno: -3008,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: '[::]'
}

Node.js v20.16.0
```

(also reproducible on 22.2.0, same error)

### How often does it reproduce? Is there a required condition?

Always

### What is the expected behavior? Why is that the expected behavior?

Should listen on all interfaces for ipv6.

### What do you see instead?

Server fails to start with an error.

### Additional information

Using `bind` of `::` works, so the following succeeds:

```
require('http').createServer((req, res) => {
  res.statusCode = 200;
  res.end("OK");
}).listen(4001, '::');
```

This causes compatibility issues if you've configuration that has a BIND parameter that needs to be passed to Node.js and another process, such as the Ruby on Rails built-in server, which doesn't accept `bind` of `::` but does accept `[::]`
Repository: tauri
Issue: [docs] WebDriver (Selenium and WebdriverIO) e2e testing does not work.
Labels: type: documentation,scope: webdriver

I'm trying to setup end-to-end tests for Tauri. I've followed the [official documentation](https://tauri.app/v1/guides/testing/webdriver/example/selenium) but when I try to start my tests I get the following error:

```
** (pulsar:12894): WARNING **: 06:38:47.744: Disabled hardware acceleration because GTK failed to initialize GL: Unable to create a GL context.

** (pulsar:12894): WARNING **: 06:38:47.751: webkit_settings_set_enable_offline_web_application_cache is deprecated and does nothing.
  1) "before all" hook in "{root}"
  2) "after all" hook in "{root}"

  0 passing (741ms)
  2 failing

  1) "before all" hook in "{root}":
     SessionNotCreatedError: Failed to match capabilities
      at Object.throwDecodedError (node_modules/selenium-webdriver/lib/error.js:521:15)
      at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:514:13)
      at Executor.execute (node_modules/selenium-webdriver/lib/http.js:446:28)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

  2) "after all" hook in "{root}":
     TypeError: Cannot read properties of undefined (reading 'quit')
      at Context.<anonymous> (test/test.js:47:16)
      at process.processImmediate (node:internal/timers:483:21)
```

The application starts correctly when I launch it manually. But fails without a reason in the selenium test. Any idea what could be wrong or how can I get a more descriptive error? Are the docs up-to-date? Migration to v2 is not possible for us at the moment, just need to get the tests running, any help is much appreciated.
Repository: terminal
Issue: Incorrect `DECRQM` for Win32InputMode
Labels: Product-Conpty,Area-Input,Area-VT,Issue-Bug

### Windows Terminal version

Commit 9b21b78feea9ff0a0b9ff2c8fa4b4aa5602d3889

### Windows build number

10.0.19045.4780

### Other Software

_No response_

### Steps to reproduce

1. Checkout and build a recent commit of Windows Terminal (I'm assuming it needs to be 450eec48de252a3a8d270bade847755ecbeb5a75 or later).
2. Open a tab with a WSL bash shell.
3. Toggle Win32 input mode with `printf "\e[?9001h"; sleep 1; printf "\e[?9001l"; read`
4. You'll likely see the keyup event for the <kbd>Enter</kbd> key that you just pressed.
5. Wait a second and press <kbd>Enter</kbd> again to return to the prompt.
6. Execute `showkey -a`
7. Try pressing <kbd>Esc</kbd> or <kbd>Alt</kbd>+<kbd>[</kbd>.


### Expected Behavior

You should see the VT codes for those keys like this:

```
^[       27 0033 0x1b
^[[      27 0033 0x1b
         91 0133 0x5b
```


### Actual Behavior

Neither of those keys are picked up. And I think the problem is the heuristic we're using here:

https://github.com/microsoft/terminal/blob/9b21b78feea9ff0a0b9ff2c8fa4b4aa5602d3889/src/terminal/parser/stateMachine.cpp#L2055-L2056

That works fine if win32 input mode is always on, or always off, but when it's toggled the `_encounteredWin32InputModeSequence` flag is never reset, so that branch is always skipped.

I don't think this was an issue prior to the new VT passthrough because we never forwarded win32 input mode changes to conpty, so it should have been permanently enabled (assuming it was supported at all).
Repository: material-ui
Issue: [joy-ui][Select] Export SelectListbox 
Labels: on hold,component: select,package: joy-ui,enhancement

### Summary

Could you export SelectListbox component like AutocompleteListbox component?

### Examples

_No response_

### Motivation

_No response_

**Search keywords**: SelectListbox
Repository: tauri
Issue: [bug] [v2] [iOS] Manual Xcode build fails with `cargo: command not found`
Labels: type: bug,status: needs triage,platform: iOS

### Describe the bug

I generate an Xcode project through `cargo tauri`. When I then open it and try to build in Xcode manually, the script execution phase fails with the following error (long line, scroll to the end):

```
/Users/stijn/Library/Developer/Xcode/DerivedData/temp-epvdqgocduaasecmmqocxpzwtttl/Build/Intermediates.noindex/temp.build/debug-iphoneos/temp_iOS.build/Script-6BC118688969AAE7C46FEBA4.sh: line 2: cargo: command not found
Command PhaseScriptExecution failed with a nonzero exit code
```

I looked at the script it tries to execute, which is only this:

```sh
#!/bin/sh
cargo tauri ios xcode-script -v --platform ${PLATFORM_DISPLAY_NAME:?} --sdk-root ${SDKROOT:?} --framework-search-paths "${FRAMEWORK_SEARCH_PATHS:?}" --header-search-paths "${HEADER_SEARCH_PATHS:?}" --gcc-preprocessor-definitions "${GCC_PREPROCESSOR_DEFINITIONS:-}" --configuration ${CONFIGURATION:?} ${FORCE_COLOR} ${ARCHS:?}
```

That's weird, because `cargo` is obviously installed on my system. The shell listed is `/bin/sh`, and when I manually open a terminal by running `/bin/sh`, I can run e.g. `cargo --version` just fine.

Replacing `cargo` in the script with `/Users/stijn/.cargo/bin/cargo` does the trick, so there's probably something wrong with the `PATH`.

### Reproduction

1. Create a new project. I used `pnpm` + Svelte + TS, but I guess this fails with any combination.
1. I also ran `pnpm install` for good measure
1. `cargo tauri ios init`
1. `cargo tauri ios dev --open --host`
1. When Xcode has opened, hit Cmd + B and see the failure

### Expected behavior

I expect the Xcode build to finish

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 14.6.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.80.1 (3f5fd8dd4 2024-08-06)
    ✔ cargo: 1.80.1 (376290515 2024-07-16)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-apple-darwin (environment override by RUSTUP_TOOLCHAIN)
    - node: 20.14.0
    - pnpm: 9.6.0
    - yarn: 1.22.22
    - npm: 10.7.0

[-] Packages
    - tauri [RUST]: 2.0.0-rc (no lockfile)
    - tauri-build [RUST]: no manifest (no lockfile)
    - wry [RUST]: no manifest (no lockfile)
    - tao [RUST]: no manifest (no lockfile)
    - tauri-cli [RUST]: 2.0.0-rc.4
    - @tauri-apps/api [NPM]: 2.0.0-rc.1
    - @tauri-apps/cli [NPM]: 2.0.0-rc.4

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../build
    - devUrl: http://localhost:1420/
    - framework: Svelte
    - bundler: Vite

[-] iOS
    - Developer Teams: <redacted>
```
```


### Stack trace

```text
N.A.
```


### Additional context

N.A.
Repository: rust
Issue: Refining generic bounds in trait method
Labels: A-trait-system,T-lang,C-discussion,T-types

This issue documents an aspect of #100706 (refined trait implementations) that to my knowledge has not been previously discussed or documented: refining generic bounds on trait methods.

It also documents the current rustc behavior, which seems to be quite surprising based on conversations I've had with a half dozen very experienced Rustaceans.

## Code example

Consider the following setup in a fictional `upstream` crate:
```rust
pub trait Super {}

mod private {
    pub trait Marker: super::Super {}
}

pub trait Subject {
    fn method<IM: private::Marker>(&self);
}
```

In this case, rustc allows both of the following generic type refinements with no errors or warnings:
```rust
struct First;
impl upstream::Subject for First {
    fn method<IM: upstream::Super>(&self) {}
}

struct Second;
impl upstream::Subject for Second {
    fn method<IM>(&self) {}
}
```
[playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=61560cc45f224196a0437365d69e3f9a)

## Surprising current behavior

In the above code, `First` refines the generic bound from `IM: upstream::private::Marker` to `IM: upstream::Super`, a supertype of `Marker`. `Second` refines the bound away completely, allowing any type.

It's quite surprising that a bare `<IM>` generic is accepted! It's completely unused and trivially satisfied, and unbounded generics are usually not accepted elsewhere in Rust. Consider for example that `PhantomData` marker fields must be added if a type declares, but does not use, a generic type.

## Relying on the refinement fails at point of use, not declaration

Attempting to rely on either refinement when calling the refined function fail with `the trait bound '<type>: Marker' is not satisfied` errors:
```rust
fn use_first() {
    <First as upstream::Subject>::method::<()>(&First);
}

impl upstream::Super for () {}
fn use_second() {
    <Second as upstream::Subject>::method::<()>(&Second);
}
```
[playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=aa0ba03dc6f247630d47b21ad43f20c7)

A warning similar to the one for refined return types (`impl trait in impl method signature does not match trait method signature`) would be good. An example of that warning can be seen in [this playground link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=1d364a825ccd532bd76177ad71fe71bc).

Related to #121718, #100706

@rustbot label +F-refine +T-lang