sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Using RefCounted objects as thread bind parameters causes segfault on exit
Labels: bug,topic:core,crash

### Tested versions

- Reproducible in 4.3

### System information

Linux 6.12.7 and Windows 11. Appears to be system independent.

### Issue description

Binding an object that inherits from RefCounted to a callable that is passed to WorkerThreadPool.add_task() will produce a stale reference.

I am not entirely sure at which point it is missing a decrement (or if that is something I should be handling manually).  
The behavior does seem unintended.

### Steps to reproduce

```
func _ready():
	var test = TestObject.new() # empty object that extends RefCounted
	print(test.get_reference_count()) # prints 1
	var id = WorkerThreadPool.add_task(threadproc.bind(test))
	WorkerThreadPool.wait_for_task_completion(id)
	print(test.get_reference_count()) # prints 2

func threadproc(obj : RefCounted):
	print(obj.get_reference_count()) # prints 3

```

Run as a build outside of the editor, close the program -> segfault on exit. On Windows the program will crash on exit and write EventLog entries.

### Minimal reproduction project (MRP)

[Archive.zip](https://github.com/user-attachments/files/18332421/Archive.zip)
Repository: go
Issue: proposal: strings, bytes: CutLast
Labels: Proposal,LibraryProposal

### Proposal Details

A couple of times now while chopping up some strings I've happily enjoyed `strings.Cut` but had to write my own `CutLast` (the latest was implementing a subset of the `package-url` spec where some of the things you need to find from the back of the string, and some from the front). It's a silly thing but it feels like an oversight.

For reference, here is one of the `CutLast` I've implemented, verbatim. Trivial and obvious:

```go
// CutLast slices s around the last instance of sep,
// returning the text before and after sep.
// The found result reports whether sep appears in s.
// If sep does not appear in s, CutLast returns s, "", false.
func stringsꞏCutLast(s, sep string) (before, after string, found bool) {
	if i := strings.LastIndex(s, sep); i >= 0 {
		return s[:i], s[i+len(sep):], true
	}
	return s, "", false
}
```
Repository: angular
Issue: Suggested workaround for content-projection in control flow blocks does not work
Labels: hotlist: error messages,area: docs

### Which @angular/* package(s) are the source of the bug?

compiler-cli, compiler

### Is this a regression?

No

### Description

When having multiple root elements in a control flow block, the compiler gives a [friendly message](https://github.com/angular/angular/blob/b22677d761fd7af38ac27c7162837cdd9b93a750/packages/compiler-cli/src/ngtsc/typecheck/src/oob.ts#L579) suggesting to
> Split the content of the @case block across multiple @case blocks such that each one only has a single projectable node at its root.

This does however not seem to work as suggested (or it works but the message is unclear). In particular, this does not seem to work for `ng-content` with specific selector targets.

See example of reproducing [here](https://stackblitz.com/edit/stackblitz-starters-avyqjise?file=src%2Fmain.ts)



### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-avyqjise?file=src%2Fmain.ts

### Please provide the exception or error you saw

No exception.

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 18.0.0
Node: 20.14.0
Package Manager: yarn 3.4.1
OS: win32 x64

Angular: 18.2.1
... animations, cdk, common, compiler, compiler-cli, core, forms
... language-service, material, material-moment-adapter
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1802.1
@angular-devkit/build-angular   18.2.1
@angular-devkit/core            18.2.1
@angular-devkit/schematics      18.2.1
@angular/cli                    18.0.0
@schematics/angular             18.2.1
rxjs                            7.8.1
typescript                      5.5.4
webpack                         5.91.0
zone.js                         0.14.6
```

### Anything else?

_No response_
Repository: pytorch
Issue: FSDP:  How to support w8a8 quantization?
Labels: triaged,module: fsdp,oncall: pt2

### 🐛 Describe the bug

I replaced nn.Linear with QuantLinear, substituting the nn.Linear operator with an int8 quantized operator.


act_tensor_int8, pertoken_scale = torch_npu.npu_dynamic_quant(x)

quant_out = torch_npu.npu_quant_matmul(act_tensor_int8, 
                                       self.weight.to(torch.int8),
                                       self.weight_scale,         # weight scale 
                                       offset=None, 
                                       bias=self.bias, 
                                       pertoken_scale=pertoken_scale,
                                       output_dtype=torch.bfloat16)



This change has achieved performance gains on a single GPU. However, when wrapped with FSDP (Fully Sharded Data Parallel) on multiple GPUs,

model_fsdp = FullyShardedDataParallel(model, **settings)
it fails to run because FSDP performs parameter sharding and cannot handle this quantized operator. The error message is as follows:

[rank4]: RuntimeError: call aclnnQuantMatmulV4 failed, detail:E69999: Inner Error!
[rank4]: E69999: [PID: 1182939] 2025-01-07-17:15:19.281.742 op[QuantBatchMatmulV3], [InferShape] dimensions a(12608) and b(128) must be equal[FUNC:InferNDimWithBias][FILE:matmul_infer_fns.cc][LINE:322]


Do you have any good solutions for this issue?



cc @zhaojuanmao @mrshenli @rohan-varma @awgu @fegin @kwen2501 @chauhang @penguinwu
Repository: godot
Issue: Slow FPS when using Convex Shapes with move_and_slide()
Labels: discussion,topic:physics,needs testing,performance

### Tested versions

 - Reproducible in 4.3 (C#) & 4.4 dev 7 (gdscript)

### System information

Godot v4.4.dev7.mono - Windows 11 (build 26100) - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated AMD Radeon RX 6600 (Advanced Micro Devices, Inc.; 32.0.11027.1003) - Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz (4 threads)

### Issue description

Frame rate rapidly drops to 20 fps whilst moving and sliding along floor
Frame rate restores after short delay when player falls off world

Might be related to:  https://github.com/godotengine/godot/issues/93184

### Steps to reproduce

Run MRP, hit F3 to view fps

### Minimal reproduction project (MRP)

[Test4.4.zip](https://github.com/user-attachments/files/18333214/Test4.4.zip)
Repository: PowerToys
Issue: Powertoys update causes Everything plugin to error
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.85.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Always on Top

### Steps to reproduce

![Image](https://github.com/user-attachments/assets/fa7976c9-3210-4686-bd08-f7d07928d4b2)
This is the error I receive after a powertoys update. Can you please tell me how to get past this issue? Thanks Gordon



### ✔️ Expected Behavior

After an update I expect it to continue to run like normal.

### ❌ Actual Behavior

See the plug screen shot I linked, it shows the error.

### Other Software

_No response_
Repository: rust
Issue: Please lint on `a.eq(b.into())` if `a.eq(b)` would work
Labels: A-lints,T-lang,A-inference,C-feature-request

In the course of investigating crater breakage, I discovered many instances of a pattern that reduces to this:

```rust
fn main() {
    let s = String::from("hello");
    assert!(s.eq("hello".into()));
}
```

This compiles, presumably because `"hello".into()` has only one possible impl that would work. It breaks if another `From` impl is brought into scope. For instance, `cargo add bstr` and add `use bstr as _;` to the top of that example, and it breaks.

Could we lint against this?

cc @estebank; this is in the same spirit as https://github.com/rust-lang/rust/pull/129249/ .
Repository: PowerToys
Issue: FancyZones does not respect default layouts
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.87.1

### Installation method

Microsoft Store

### Running as admin

None

### Area(s) with issue?

FancyZones

### Steps to reproduce

FancyZones does not respect custom default layouts.

If I have Power Toys running, FancyZones uses the built-in default layout instead of the one I have set to the default.

I must open the FancyZones editor for it to the switch to my default layout.

### ✔️ Expected Behavior

For it to use my default layout.

### ❌ Actual Behavior

It uses the built-in default.

### Other Software

_No response_
Repository: langchain
Issue: Bug: GraphIndexCreator raises PydanticUserError when instantiated; NetworkX tutorial notebook not running.
Labels: 🤖:bug

### Checked other resources

- [X] I added a very descriptive title to this issue.
- [X] I searched the LangChain documentation with the integrated search.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I am sure that this is a bug in LangChain rather than my code.
- [X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

### Example Code

Run the following code:
```python
from langchain_community.graphs.index_creator import GraphIndexCreator
from langchain_openai import OpenAI
index_creator = GraphIndexCreator(llm=OpenAI(temperature=0, api_key=OPENAI_API_KEY))
```

Remember to use your own OpenAI API key.

### Error Message and Stack Trace (if applicable)

PydanticUserError                         Traceback (most recent call last)
[<ipython-input-8-fa0320b33b39>](https://localhost:8080/#) in <cell line: 1>()
----> 1 index_creator = GraphIndexCreator(llm=OpenAI(temperature=0, api_key=OPENAI_API_KEY))    [... skipping hidden 1 frame]

[/usr/local/lib/python3.10/dist-packages/pydantic/_internal/_mock_val_ser.py](https://localhost:8080/#) in __getattr__(self, item)
     98         # raise an AttributeError if `item` doesn't exist
     99         getattr(self._val_or_ser, item)
--> 100         raise PydanticUserError(self._error_message, code=self._code)
    101 
    102     def rebuild(self) -> ValSer | None:

PydanticUserError: `GraphIndexCreator` is not fully defined; you should define `BaseCache`, then call `GraphIndexCreator.model_rebuild()`.

### Description

Was trying to run the following networkx tutorial: https://github.com/langchain-ai/langchain/blob/master/docs/docs/integrations/graphs/networkx.ipynb.

I encountered a PydanticUserError when attempting to instantiate the GraphIndexCreator. It seems that BaseCache needs to be defined and GraphIndexCreator.model_rebuild() must be called, but this isn't mentioned in the documentation or examples.

### System Info

This was run in the usual Google Colab environment.
Repository: material-ui
Issue: [docs][material-ui][TextField] `type="number"` error
Labels: docs,component: text field,package: material-ui

### Steps to reproduce

Steps:
1. Open this link to live example: (required)
2.
3.

https://github.com/user-attachments/assets/2b10beb6-74af-4f0c-956d-940a8b9349e4



### Current behavior

Bug in Number Type Textfield if i hold increase button and rease but number is increasing.

### Expected behavior

Bug in Number Type Textfield if i hold increase button and rease but number is increasing. but it should not do.

### Context

_No response_

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: Number Type Textfied error
Repository: next.js
Issue: Middleware.ts causes `ReferenceError: self is not defined` error with `splitChunks`
Labels: Middleware

### Link to the code that reproduces this issue

https://github.com/jozef-mikusinec-kiwicom/nextjs-middleware-splitchunks

The `next.config.ts`:

```ts
export default {
  webpack: config => {
    config.optimization.splitChunks = {
      chunks: 'all',
      cacheGroups: {
        default: {
          name: 'ihaveaname',
        },
      },
    };

    return config;
  },
};
```

### To Reproduce

0. Clone the repo
1. `yarn install`
2. `next build`

### Current vs. Expected behavior

Expected behavior: no errors.

Current behavior:

```
unhandledRejection ReferenceError: self is not defined
    at Object.<anonymous> (.next/server/ihaveaname.js:1:1) {
  type: 'ReferenceError'
}
```

Note that:
* `next dev` loads OK on the initial try, but there is `Error [ReferenceError]: exports is not defined` in the console
* the error goes away if either:
  * middleware.js file is deleted
  * the `name` prop is removed from the cache group
  * `chunks: 'all'` is removed
  * a new cache group without `name` and `test` is added

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:15 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 22.12.0
  npm: 10.9.0
  Yarn: 1.19.1
  pnpm: N/A
Relevant Packages:
  next: 15.1.3 // Latest available version is detected (15.1.3).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.7.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Middleware

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

This is a minified version from a project that uses a more complex `splitChunks` config. The error appeared when the I tried to add the middleware file to the project.
Repository: ant-design
Issue: Range Picker formats quarter differently when `date-fns` is used
Labels: unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/range-picker-antd-5-23-0-forked-xm4h5w)

### Steps to reproduce

- Open your own range picker example: https://codesandbox.io/p/sandbox/k526xx
- Add `date-fns` package
- Add these lines to demo.tsx:
  ```
  import dateFnsGenerateConfig from "rc-picker/lib/generate/dateFns";
  const DateFnsRangePicker = DatePicker.generatePicker<Date>(
    dateFnsGenerateConfig
  );
  ```
- Add `<RangePicker picker="quarter" value={dayjs("2024-08-17")} />` to return section
- Add `<DateFnsRangePicker picker="quarter" value={new Date("2024-08-17")} />` to return section
- Compare default range picker quarter format with date-fns one.


### What is expected?

Formatted quarter in both fields are equal to `2024-Q3`

### What is actually happening?

- default RangePicker shows `2024-Q3`
- date-fns one shows `2024-[3]3`

![image](https://github.com/user-attachments/assets/a7e9fa3d-8d64-4dc8-8556-3e04b7d96162)


| Environment | Info |
| --- | --- |
| antd | 5.23.0 |
| React | ^18.0.0 |
| System | all |
| Browser | chrome 131.0.6778.205 |

---
It seems when you are using date-fns package - it formats quarter wrongly. It assumes that `[Q]` not just a `Q` string but it uses it to show quarter number.

P.S. instructions how to add date-fns was taken from https://ant.design/docs/react/use-custom-date-library#use-date-fns

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: node
Issue: A workflow to periodically check status for author-ready PRs opened by a non-collaborator
Labels: meta

It's quite common for PRs from non-collaborators that have gotten approval to fall through the cracks because there's no one who remember to shepherd it through. I sometimes bump into one of these, and would restart a CI when I see one, but it's very hard to remember to go back keep resuming the CI (sigh) until it's green and land it. And from time to time I also see PRs waiting for months without moving forward due to this reason (not all new contributors know that they have to specifically ping for actions to move it forward, and they could be waiting in vain). I suspect many of the open PRs are stalled this way.

It would help the situation if there is a workflow that gets trigered by the author-ready label and would periodically (e.g. weekly) ping for status if it's opened by a non-collaborator (it's more likely that they don't know how to move it forward), at least sending a notification to the collaborators involved in that PR to press whatever button needed to move it forward.
Repository: godot
Issue: When you use `new` method of a Callable, it will fail in release build.
Labels: bug,topic:gdscript

### Tested versions

4.4 dev7

### System information

W10

### Issue description

When you use `new` method of a class as a Callable, it will fail in release build.
```GDScript
extends Node

class Test:
	pass

func _ready() -> void:
	var test = Test.new.call()
	print(test)
```
Prints the object in editor/debug build, in release build it results in
```
SCRIPT ERROR: Parse Error: Cannot find member "new" in base "Test".
          at: GDScript::reload (res://2DSequel.tscn::GDScript_1egr7:7)
```

### Steps to reproduce

1. Attach the above script to a node
2. Export with release template
3. Run

### Minimal reproduction project (MRP)

N/A
Repository: storybook
Issue: [Bug]: Angular - Storybook fails to consume postcss config file
Labels: bug,angular

### Describe the bug

In order to use Tailwindcss v4 with Angular 19+ (using the new esbuild builder), it is necessary to create a `postcss.config.json` file, because Angular seemingly fails to consume *any* other variant of a postcss config (e.g. in the package.json, or using a `postcss.config.mjs`).

Installing Tailwindcss v4 with postCSS: https://tailwindcss.com/docs/v4-beta#installing-with-post-css
Trying to compile the angular app, without this postcss.config.json file present, will result in 
```
Error: It looks like you're trying to use `tailwindcss` directly as a PostCSS plugin. The PostCSS plugin has moved to a separate package, so to continue using Tailwind CSS with PostCSS you'll need to install `@tailwindcss/postcss` and update your PostCSS configuration.
```

Once the postcss.config.json is provided - and both ng serve, ng test and ng build run smoothly, Storybook fails to compile for the same reason, as the builder (under the hood) seemingly fails to consume said postcss config.
```=> Failed to build the preview
Error: It looks like you're trying to use `tailwindcss` directly as a PostCSS plugin. The PostCSS plugin has moved to a separate package, so to continue using Tailwind CSS with PostCSS you'll need to install `@tailwindcss/postcss` and update your PostCSS configuration.
```

This is using the Webpack builder. I am aware that there is a plugin that tries to get Angular to run under Storybook using vite.

### Reproduction link

https://github.com/SeraphCoding/AngularTW4SBVite

### Reproduction steps

1. Clone the repository above
2. Install dependencies (yarn berry)
3. Run `yarn run storybook`
4. Wait for the compilation

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 5.15 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
    CPU: (16) x64 AMD Ryzen 7 3800X 8-Core Processor
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 20.15.0 - /tmp/xfs-ade9681f/node
    Yarn: 4.6.0 - /tmp/xfs-ade9681f/yarn <----- active
    npm: 10.7.0 - ~/.nvm/versions/node/v20.15.0/bin/npm
  npmPackages:
    @storybook/addon-docs: ^8.4.7 => 8.4.7
    @storybook/addon-essentials: ^8.4.7 => 8.4.7
    @storybook/addon-interactions: ^8.4.7 => 8.4.7
    @storybook/addon-onboarding: ^8.4.7 => 8.4.7
    @storybook/angular: ^8.4.7 => 8.4.7
    @storybook/blocks: ^8.4.7 => 8.4.7
    @storybook/test: ^8.4.7 => 8.4.7
    storybook: ^8.4.7 => 8.4.7


**Note**
Same issues occurs on 8.5.0-beta.7
```

### Additional context / WIP Workaround
The issue does not occur when using analogjs's angular vite plugin for the Storybook - however, I haven't been able to get the analogjs plugin to run properly in it's completion. I managed to get it to compile, though it seemingly fails to load Tailwindcss and Angular Material to begin with - so that isn't really a sustainable workaround, yet. Will update this once/if I get it to run.
Repository: pytorch
Issue: [Export]  UserWarning: Attempted to insert a get_attr Node with no underlying reference in the owning GraphModule
Labels: oncall: pt2,oncall: export

### 🐛 Describe the bug

Using `torch.export` on https://github.com/MCG-NJU/VFIMamba

I got

```python
/opt/conda/lib/python3.11/site-packages/torch/export/_unlift.py:75: UserWarning: Attempted to insert a get_attr Node with no underlying reference in the owning GraphModule! Call GraphModule.add_submodule to add the necessary submodule, GraphModule.add_parameter to add the necessary Parameter, or nn.Module.register_buffer to add the necessary buffer
  getattr_node = gm.graph.get_attr(lifted_node)
/opt/conda/lib/python3.11/site-packages/torch/fx/graph.py:1801: UserWarning: Node lifted_tensor_0 target lifted_tensor_0 lifted_tensor_0 of  does not reference an nn.Module, nn.Parameter, or buffer, which is what 'get_attr' Nodes typically target
```

I think that the problem it could be in
https://github.com/MCG-NJU/VFIMamba/blob/main/model/warplayer.py

Is it safe this warning or does it require a workaround. In any case, can we improve the message?

### Versions

nightly

cc @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4
Repository: rust
Issue: `CoercePointee` doesn't tightly enforce the restriction to `#[repr(transparent)]`-only wrappers, if other proc-macros are involved
Labels: T-compiler,C-bug,F-derive_coerce_pointee

Define a proc macro that strips the `#[repr(transparent)]`.

```rust
#[proc_macro_attribute]
pub fn untransparent(_: TokenStream, item: TokenStream) -> TokenStream {
    let mut i = item.into_iter();
    drop(i.next());
    drop(i.next());
    i.collect()
}
```
use it
```rust
#![feature(derive_coerce_pointee)]
use std::marker::CoercePointee;
use …:untransparent;

#[derive(CoercePointee)]
#[untransparent]
#[repr(transparent)]
struct Foo<T: ?Sized>(Box<T>);
```

---

compiles successfully, expands to
```rust
#![feature(prelude_import)]
#![feature(derive_coerce_pointee)]
#[prelude_import]
use std::prelude::rust_2021::*;
#[macro_use]
extern crate std;
use std::marker::CoercePointee;
use …::untransparent;
struct Foo<T: ?Sized>(Box<T>);
#[automatically_derived]
impl<
    T: ?Sized + ::core::marker::Unsize<__S>,
    __S: ?Sized,
> ::core::ops::DispatchFromDyn<Foo<__S>> for Foo<T> {}
#[automatically_derived]
impl<
    T: ?Sized + ::core::marker::Unsize<__S>,
    __S: ?Sized,
> ::core::ops::CoerceUnsized<Foo<__S>> for Foo<T> {}
```

As far as I understand the RFC and intent, the intended stabilization should only stabilize allowing these (`CoerceUnsized` & `DispatchFromDyn` impls) to be generated for `#[repr(transparent)]` types.

@rustbot label F-derive_coerce_pointee

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: neovim
Issue: ":float split" opens windows a floating window (compare :tab, :vertical)
Labels: enhancement,floatwin

### Problem

Some users want floating windows instead of tabs/splits for various features. https://github.com/neovim/neovim/pull/31086 




### Expected behavior

Introduce `:float` which can modify commands similar to `:tab` and `:vertical`. It causes a split to open in a float.


However, this raises questions about how it's presented by default, what happens when showing multiple floats, etc. Thus it might be redundant/overlap with Vim's `:help preview-popup` :

- https://github.com/neovim/neovim/issues/9920
- https://github.com/neovim/neovim/issues/17434