sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: BBCode effects text kerning in RichTextLabels when it shouldn't
Labels: bug,topic:gui

### Tested versions

Tested in 4.3-stable

### System information

Tested on Windows 10 and Fedora Linux 40

### Issue description

Simply changing this line:

```
[color=gray]Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.[/color]
```

To this line:

```
[color=white]Lorem[/color] [color=gray]ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.[/color]
```

Results in alteration of the kerning for text rendered in a RichTextLabel.



### Steps to reproduce

Pretty much what was stated in the description. 

### Minimal reproduction project (MRP)

An example project reproducing this issue can be found here: https://github.com/SamInTheShell/godot-bbcode-richtextlabel-kerning-bug

Press spacebar to toggle the text value.
Repository: kubernetes
Issue: Creation fails when the CRD property is ServiceAccount
Labels: kind/bug,needs-sig,needs-triage

### What happened?

My CRD property use the ServiceAccount type, When I use `kubelet apply -f <crds>` to create CRDs generated by controller-gen, get an error message: 
```text
Required value: this property is in x-kubernetes-list-map-keys, so it must have a default or be a required property.
```

This is because ServiceAccount.Secret.Name property is in x-kubernetes-list-map-keys, but it is not have a default and not be a required property.

Structure definition:
```go
// +genclient
// +k8s:deepcopy-gen:interfaces=k8s.io/apimachinery/pkg/runtime.Object
// +kubebuilder:...
type Foo struct {
    ServiceAccount corev1.ServiceAccount `json:"serviceAccount,omitempty"`
    ....
}
```

### What did you expect to happen?

I expect to generate CRDs that can be created successfully.

Solutions:
- Set ObjectReference.Name to required. I think the name is required in most scenarios.
- Add default value annotations  (`//+default=""` and `//+kubebuilder:default=""`) for ObjectReference.Name.
- Modify the ServiceAccount.Secrets type to []SecretReference and set SecretReference.name to required.

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

Refer to "What happened"

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

v1.30+

</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: langchain
Issue: AgentType.STRUCTURED_CHAT_ZERO_SHOT_REACT_DESCRIPTION
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

sugesstion: STRUCTURED_CHAT_FORMAT_INSTRUCTIONS(input->uotput).  Action:
```
{{{{
  "action": "Final Answer",
  "action_input": "Final response to human."
}}}}   --->  ```
{{{{
  "action": "Final Answer",
  "action_output": "Final response to human."
}}}}

### Error Message and Stack Trace (if applicable)

In practice, it is found that llm is easy to interpret "Final Answer" as an input that leads to a bad final result

### Description

STRUCTURED_CHAT_FORMAT_INSTRUCTIONS

### System Info

STRUCTURED_CHAT_FORMAT_INSTRUCTIONS
Repository: stable-diffusion-webui
Issue: [Feature Request]: 请问下，webui是放弃更新了吗？感觉已经好久没有更新了！
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 ?

 请问下，webui是放弃更新了吗？感觉已经好久没有更新了！

### Proposed workflow

请问下，webui是放弃更新了吗？感觉已经好久没有更新了！

### Additional information

 请问下，webui是放弃更新了吗？感觉已经好久没有更新了！
Repository: pytorch
Issue: Possible race condition found in TailLogTest.test_tail
Labels: oncall: distributed,module: tests,module: elastic

### 🐛 Describe the bug

### Error message
```bash
 Time: 12/20/2024 10:05:37, Level: 40000, Log: Traceback (most recent call last):
  File "/opt/py3.10/lib/python3.10/unittest/case.py", line 59, in testPartExecutor
    yield
  File "/opt/py3.10/lib/python3.10/unittest/case.py", line 591, in run
    self._callTestMethod(testMethod)
  File "/opt/py3.10/lib/python3.10/unittest/case.py", line 549, in _callTestMethod
    method()
  File "/torch/src/pytorch/test/distributed/elastic/multiprocessing/tail_log_test.py", line 83, in test_tail
    self.assertEqual(
  File "/opt/py3.10/lib/python3.10/unittest/case.py", line 845, in assertEqual
    assertion_func(first, second, msg=msg)
  File "/opt/py3.10/lib/python3.10/unittest/case.py", line 1144, in assertDictEqual
    self.fail(self._formatMessage(msg, standardMsg))
  File "/opt/py3.10/lib/python3.10/unittest/case.py", line 675, in fail
    raise self.failureException(msg)
AssertionError: {'[writer0]': {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 1[156927 chars]999}} != {'[writer1]': {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 1[156922 chars]999}}
Diff is 722560 characters long. Set self.maxDiff to None to see it.
```
### Possible root cause
Some woker threads of `TailLog` might open their log files later than when they receive the stop signal? It's difficult to reproduce, and I have only encountered it once.

### Versions

main

cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o @mruberry @ZainRizvi @dzhulgakov
Repository: react
Issue: Bug: StrictMode remount element that only update
Labels: Status: Unconfirmed

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.0.0

## Steps To Reproduce

1. use StrictMode
2. render a list in any way
3. change the order of the list

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example: [codesandbox](https://codesandbox.io/p/sandbox/4pxf28)

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

When change the order of the list, the list item unmounted and then mounted, except for the first element.

## The expected behavior

It should not remount during the update phase.

I test the same code on react 18, which has no problem.
Repository: ant-design
Issue: [tabs] clicking the folded item button will result in an error
Labels: improvement,⌨️ Accessibility

### Reproduction link

[https://ant.design/~demos/tabs-demo-slide](https://ant.design/~demos/tabs-demo-slide)

### Steps to reproduce

click collapse item button
![image](https://github.com/user-attachments/assets/4a6ca0ce-9dd6-4aac-a0f9-eaec3cf5d682)


### What is expected?

null

### What is actually happening?

`Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden.
Element with focus: button
Ancestor with aria-hidden:  <button type=​"button" class=​"ant-tabs-nav-more ant-tabs-dropdown-open" tabindex=​"-1" aria-hidden=​"true" aria-haspopup=​"listbox" aria-controls=​"rc-tabs-1-more-popup" id=​"rc-tabs-1-more" aria-expanded=​"true" style>​…​</button>​`

![image](https://github.com/user-attachments/assets/7bc5ec12-0130-4c9b-b80f-92693b041626)

| Environment | Info |
| --- | --- |
| antd | 5.22.6 |
| React | ^18.3.0 |
| System | win11 |
| Browser | 版本 131.0.6778.205（正式版本） （64 位） |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: Linux_pixel_7pro platform_views_scroll_perf_impeller__timeline_summary is 2.20% flaky
Labels: P2,c: flake,team-engine,triaged-engine

<!-- meta-tags: To be used by the automation script only, DO NOT MODIFY.
{
  "name": "Linux_pixel_7pro platform_views_scroll_perf_impeller__timeline_summary"
}
-->

The post-submit test builder `Linux_pixel_7pro platform_views_scroll_perf_impeller__timeline_summary` had a flaky ratio 2.20% for the past (up to) 100 commits, which is above our 2.00% threshold.

One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_pixel_7pro%20platform_views_scroll_perf_impeller__timeline_summary/5593
Commit: https://github.com/flutter/flutter/commit/8ad15cd81e4cd2ad86524a8afa7021ea51c09169

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_pixel_7pro%20platform_views_scroll_perf_impeller__timeline_summary/5593
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_pixel_7pro%20platform_views_scroll_perf_impeller__timeline_summary/5549

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_pixel_7pro%20platform_views_scroll_perf_impeller__timeline_summary

Please follow https://github.com/flutter/flutter/blob/master/docs/infra/Reducing-Test-Flakiness.md#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).
Repository: flutter
Issue: Windows framework_tests_widgets is 2.17% flaky
Labels: P1,c: flake,team-framework,triaged-framework

<!-- meta-tags: To be used by the automation script only, DO NOT MODIFY.
{
  "name": "Windows framework_tests_widgets"
}
-->

The post-submit test builder `Windows framework_tests_widgets` had a flaky ratio 2.17% for the past (up to) 100 commits, which is above our 2.00% threshold.

One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20framework_tests_widgets/20011
Commit: https://github.com/flutter/flutter/commit/5c7d9d01bae7b279b7d95a37577f782c51847d5b

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20framework_tests_widgets/20011
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20framework_tests_widgets/19923

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Windows%20framework_tests_widgets

Please follow https://github.com/flutter/flutter/blob/master/docs/infra/Reducing-Test-Flakiness.md#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).
Repository: TypeScript
Issue: Cannot export both types and values from CJS
Labels: Suggestion,In Discussion

### 🔎 Search Terms

verbatimModuleSyntax, commonjs, require, export, export type,

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about [CJS export syntax](https://www.typescriptlang.org/docs/handbook/modules/reference.html#export--and-import--require) and [verbatimModuleSyntax release notes](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-5-0.html#--verbatimmodulesyntax).


### ⏯ Playground Link

https://www.typescriptlang.org/play/?moduleResolution=99&target=99&module=199&verbatimModuleSyntax=true&ts=5.8.0-dev.20241225#code/KYDwDg9gTgLgBDAnmYcBiEJwLxwM4xQCWAdgOZwA+cJArgLYBGwUA3AFDsDGANgIZ48cAEJ8ocAN4BfTqEiwcIsayA

### 💻 Code

I wanted to convert a *.ts file that gets interpreted as CJS (due to package.json "type" field) to use `verbatimModuleSyntax` for explicitness. 

The file previously looked like this
```ts
// index.ts
export type Foo = string | number;
export const Bar = 42;
```
and could be imported like so
```ts
// foo.ts
import { type Foo, Bar } from './index';

const x: Foo = 42;
const y = Bar;
```

After enabling `verbatimModuleSyntax`, it seems no longer possible to export both `Foo` and `Bar` from index.ts. Some attempts:
```ts
type Foo = string | number;
const Bar = 42;

export = { Foo, Bar }; // error; Foo is a type but used as a value
```
This is ok, 
```ts
export type Foo = string | number;
const Bar = 42;
```
but this is not
```ts
export type Foo = string | number;
const Bar = 42;
export = { Bar }; // An export assignment cannot be used in a module with other exported elements. (TS2309)
```
nor this
```ts
type Foo = string | number;
const Bar = 42;
export type { Foo };
export = { Bar }; // An export assignment cannot be used in a module with other exported elements. (TS2309)
```

***

tsconfig:
```json
{
    "compilerOptions": {
        "verbatimModuleSyntax": true,
        "target": "ESNext",
        "module": "NodeNext",
        "strict": true,
    }
}
```
package.json: has `"type": "commonjs"`

### 🙁 Actual behavior

Can't find a way to export both types and values using CJS import/export syntax required by verbatimModuleSyntax

### 🙂 Expected behavior

There is a way to export both types and values using CJS import/export syntax

### Additional information about the issue

Perhaps this is possible, and if so I'd ask it be added to the documentation. Without this, a currently-functioning CJS module cannot straightforwardly be converted to use verbatimModuleSyntax.

FWIW, if it's not possible, I don't see why at least one of the following wouldn't be allowed (specifically due to the use of `export type` to ensure only one _value_ export exists)
```ts
export type Foo = string | number;
const Bar = 42;
export = { Bar }; // not a problem; only one value export
```
or
```ts
type Foo = string | number;
const Bar = 42;
export type { Foo };
export = { Bar };
```
Repository: rust
Issue: Compile Error on AVR atmega328p with global_asm! in lib.rs
Labels: A-LLVM,A-inline-assembly,T-compiler,C-bug,E-needs-mcve,O-AVR,A-target-feature,C-external-bug

This is my first issue, so I'm not sure if this is the right place to report or if it is reported already.

Also formatting this issue is new to me ...

I'm on Rust with AVR atmega328p, using

```
nightly-2024-11-12-aarch64-unknown-linux-gnu (default)
rustc 1.84.0-nightly (81eef2d36 2024-11-11)
```

I use "global_asm!" macro which compiles Ok in a bin main.rs and gives a compile error in a lib lib.rs.

The error is

```
error: <inline asm>:2:5: instruction requires a CPU feature not currently enabled
    x:
    jmp x
   ^
```

The source in both, main.rs and lib.rs is

```rust
//
global_asm!(r#"
   x:
   jmp x
"#);
```

To test, I have two crates, one to test as --bin with main.rs, one to test as --lib with lib.rs

Both crates have .cargo/config.toml

```toml
[build]
target = "avr-atmega328p.json"

[target.avr-atmega328p]
rustflags = [
    #
    "-Clink-arg=-nostartfiles",
]

[unstable]
build-std = ["core"]
```

Both have Config.toml

```toml
[package]
name = "..."
edition = "2021"

[dependencies]

[profile.release]
panic = "abort"
lto = true
```

The main.rs in the bin test crate :

```rust
//!
#![no_std]
#![no_main]
//
#![allow(unused_imports)]
//
#![feature(asm_experimental_arch)]

use core::arch::{ asm, global_asm };

//
global_asm!(r#"
   x:
    jmp x
"#);

///
use core::panic::PanicInfo;
#[panic_handler]
fn panic(_panic: &PanicInfo<'_>) -> ! {
    loop {
    }
}
```

... compiles and links fine !


The lib.rs in the lib test crate :

```rust
//!
#![no_std]
//
#![allow(unused_imports)]
//
#![feature(asm_experimental_arch)]

use core::arch::{ asm, global_asm };

//
global_asm!(r#"
   x:
   jmp x
"#);
```

... and gives compile error

```
error: <inline asm>:2:5: instruction requires a CPU feature not currently enabled
    jmp x
    ^
```

Command for both crates is cargo build --release

```
./home/rust/rust-repos/rustc/rust/src/llvm-project/llvm/lib/Object/ModuleSymbolTable.cpp
```

I've tracked it down to llvm :


```
llvm-project/llvm/lib/Object/ModuleSymbolTable.cpp
```

```cpp
static void initializeRecordStreamer(...) 
{
...
  std::unique_ptr<MCSubtargetInfo> STI(
      T->createMCSubtargetInfo(TT.str(), "", ""));
...
}
```

The ("","") forces the feature map to go to the lowest for AVR and does not honor, that "atmega328p" features should be used.

Ich I patch it to

```cpp
  std::unique_ptr<MCSubtargetInfo> STI(
      T->createMCSubtargetInfo(TT.str(), "atmega328p", ""));
```

it compiles fine :) But this is not a Solution

So here I stuck ...


br
xjn
Repository: PowerToys
Issue: Always on Top: Mouse cursor becomes "loading" when hovering over the border of a pinned window
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Always on Top

### Steps to reproduce

1. Open PowerToys and enable the "Always on Top" feature.
2. In the settings, check the option "Show a border around pinned windows."
3. Pin a window using the shortcut (default: Win + Ctrl + T).
4. Move your mouse over the border of the pinned window.

### ✔️ Expected Behavior

The mouse cursor should remain unchanged when hovering over the border of the pinned window.

### ❌ Actual Behavior

The mouse cursor changes to the "loading" (spinning circle) icon when hovering over the border of the pinned window.

### Other Software

N/A
Repository: ant-design
Issue: List 移动设备在列表区域双指滑动后，滑动效果直接失效了
Labels: 📱Mobile Device

### Reproduction link

[https://ant.design/~demos/list-demo-virtual-list](https://ant.design/~demos/list-demo-virtual-list)

### Steps to reproduce

在移动设备中，使用双指在列表区域滑动

### What is expected?

双指滑动之后，列表区域仍然可以正常滑动

### What is actually happening?

双指滑动之后，列表区域无法滑动

| Environment | Info |
| --- | --- |
| antd | 5.22.6 |
| React | 18.2.0 |
| System | MacOS |
| Browser | 版本 131.0.6778.205（正式版本） （64 位） |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: Modules get disabled
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

TextExtractor, FancyZones

### Steps to reproduce

Often, but not always, some modules go back to disabled after reboots.  For example, I use text extractor and fancy zones often so they're typically toggled enabled.  They don't stay that way.  I often find them in the lower disabled section after most reboots (of Windows).

### ✔️ Expected Behavior

If a module is enabled, should it not stay enabled until it's manually disabled?

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: pytorch
Issue: After pth is converted into ptl, the prediction result is very different from pth
Labels: oncall: jit

### 🐛 Describe the bug

# 加载原始配置和模型
    checkpoint = torch.load(checkpoint_path, map_location='cuda')
    args = checkpoint['args']
    args.num_classes = 250

    # 构建模型
    model, _, _ = build_model(args)
    model.load_state_dict(checkpoint['model'])
    model.eval()

    wrapped_model = DETRWrapper(model)
    original_model = wrapped_model  # 保存原始模型的引用

    # 准备示例输入
    example_input = torch.randn(1, 3, 448, 448)

    # 测试前向传播
    with torch.no_grad():
        try:
            semantic_map = wrapped_model(example_input)
            print("Model test forward pass successful")
            print(f"Output shape: semantic_map {semantic_map.shape}")
        except Exception as e:
            print(f"Error during test forward pass: {e}")
            return

    try:
        # 使用TorchScript跟踪模型
        traced_model = torch.jit.trace(wrapped_model, example_input)
        
        # 确保模型在CPU上
        traced_model = traced_model.cpu()
        
        # 添加详细的验证步骤
        def validate_outputs(pth_model, ptl_model, test_input):
            with torch.no_grad():
                pth_output = pth_model(test_input)
                ptl_output = ptl_model(test_input)
                
                # 确保输出类型一致
                if pth_output.dtype != ptl_output.dtype:
                    print(f"Warning: Output dtype mismatch - PTH: {pth_output.dtype}, PTL: {ptl_output.dtype}")
                
                # 比较预测结果
                match_percentage = (pth_output == ptl_output).float().mean() * 100
                print(f"Prediction match percentage: {match_percentage:.2f}%")
                
                # 检查类别分布
                pth_classes = torch.unique(pth_output, sorted=True)
                ptl_classes = torch.unique(ptl_output, sorted=True)
                print(f"PTH unique classes: {pth_classes}")
                print(f"PTL unique classes: {ptl_classes}")
                
                return match_percentage > 95  # 要求95%以上的预测匹配
        
        # 在保存模型前进行验证
        if not validate_outputs(wrapped_model, traced_model, example_input):
            print("Warning: Model conversion validation failed!")
            return
        
        # 保存模型
        traced_model.save(output_path)

### Versions

2.1.0+cu118

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: PowerToys
Issue: [Settings-QuickAccent] "Choose a character set" even though you can choose more than one.
Labels: Issue-Bug,Product-Settings,Resolution-Fix Committed,Area-User Interface

### Microsoft PowerToys version

0.87.1

### Installation method

Dev build in Visual Studio

### Running as admin

None

### Area(s) with issue?

Settings

### Steps to reproduce

Quick Accent settings
![Image](https://github.com/user-attachments/assets/ce623827-4186-4757-bc63-928a8eeb596b)
Choose a character set (singular), even though you can now select more than one. It should be something like "Choose character sets".

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_