sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Revert icons in the Inspector don't show up for @export properties when using @tool scripts on Editor launch
Labels: topic:gdscript,topic:editor,needs testing

### Tested versions

I tested this in 4.3 stable and 4.2 stable

### System information

Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1050 (NVIDIA; 31.0.15.3713) - Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz (8 Threads)

### Issue description

Revert icons in the Inspector tab, those round arrows that sit on the left side of every property with a different value from default, is missing on startup for nodes that has scripts attached to them with `@tool` annotation. So scripts that run in the Editor. It is only missing for custom properties defined by the script. Anything that starts with `@export`. What solves the missing icons is a simple save of literally ANY scene. Keep in mind, I'm not talking about editing a script and having to save to show results, I'm talking about freshly launched Editor with literally no changes made to either 2D, 3D or Script. After saving and res-electing a node, all the revert icons appear. Not just in the saved scene, but in all scenes and all nodes, even the ones opened afterwards.



### Steps to reproduce

- Create a new Godot project
- Add a Node
- Attach Script
- Write "`@tool`" on the first line
- Write "Extends Node" on the second line
- Write "`@export var example: int = 5`" on the third line
- Save everything
- Reload scene
- Select the Node
- In the inspector set exported property "example" to 10
- Save everything
- Reload project
- Select the Node
- NO REVERT ICON in the Inspector
- Save scene
- Un-select and re-select the Node
- REVERT ICON

### Minimal reproduction project (MRP)

[revert_icon_bug.zip](https://github.com/user-attachments/files/17639760/revert_icon_bug.zip)
Repository: TypeScript
Issue: Detect Typescript in Javascript editors opened and inform developer, that he is writing different syntax and it will silently fail (probably)
Labels: Needs More Info

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
It would be super helpful to have something like:
```
Warning: TypeScript syntax detected in .jsx file. 
Would you like to:
[ ] Rename to .tsx
[ ] Remove TypeScript syntax
[ ] Ignore warning
```

This kind of UX improvement could save developers (especially those transitioning between JS and TS projects) a lot of time and frustration. It seems like a relatively straightforward detection that could help a lot of people!

VSCode already does similar helpful suggestions for other cases (like offering to create files that don't exist when you import them), so this would fit right in with that philosophy.

What it would solve?

It's the classic .jsx vs .tsx gotcha! 😄 

This is such a common issue that even experienced developers run into it regularly. The file extension makes all the difference because:
- `.jsx` files are treated as regular JavaScript/React files
- `.tsx` files are treated as TypeScript/React files

So TypeScript typing just "silently fails" to work in .jsx files without any obvious error message about why the types aren't working. 

It's one of those "spend an hour debugging only to realize it's a file extension" moments that every developer has experienced!

- `.CJS` -> `.TS`, `.JS` -> `.TS`, `.JSX` -> `.TSX`

(Similar functionality could be created for `CSS` -> `SCSS`, ... .)
Repository: go
Issue: internal/trace: TestTraceStressStartStop/Default failures
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
default <- pkg == "internal/trace" && test == "TestTraceStressStartStop/Default"
```

Issue created automatically to collect these failures.

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

    === RUN   TestTraceStressStartStop/Default
        reader_test.go:112: unexpected error while reading the trace: broken trace: failed to advance: frontier:
            [gen=5]
            
            M 3764 [ProcStart time=16122150543994 p=4 p_seq=22]
            M 12168 [GoUnblock time=16122151264173 g=22 g_seq=2 stack=0]
            
            G 4 [status=Waiting seq=2 (gen=5)]
            G 5 [status=Waiting seq=0 (gen=5)]
            G 57 [status=Waiting seq=0 (gen=5)]
    ...
            String id=193
            	data="C:/Users/swarming/.swarming/w/ir/x/w/goroot/src/net/tcpsockopt_posix.go"
            String id=194
            	data="net.setKeepAlive"
            String id=195
            	data="C:/Users/swarming/.swarming/w/ir/x/w/goroot/src/net/sockopt_posix.go"
            String id=196
            	data="runtime.forcegchelper"
            
    --- FAIL: TestTraceStressStartStop/Default (3.36s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: pytorch
Issue: DISABLED test_dtensor_mm (__main__.DistMatrixOpsTest)
Labels: module: rocm,triaged,skipped

Platforms: rocm

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22distributed%2F_tensor%2Ftest_matrix_ops.py%3A%3ADistMatrixOpsTest%3A%3Atest_dtensor_mm%22%5D)).

distributed/_tensor/test_matrix_ops.py::DistMatrixOpsTest::test_dtensor_mm [GH job link](https://github.com/pytorch/pytorch/actions/runs/11692278898/job/32562714444) [HUD commit link](https://hud.pytorch.org/pytorch/pytorch/commit/59b66944d4287ca154508c25691fde95b5cecb36)

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd
Repository: pytorch
Issue: DISABLED test_tracker_with_activation_checkpointing (__main__.TestTrackerFullyShard1DTrainingCompose)
Labels: module: rocm,triaged,skipped

Platforms: rocm

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22distributed%2F_tools%2Ftest_fsdp2_mem_tracker.py%3A%3ATestTrackerFullyShard1DTrainingCompose%3A%3Atest_tracker_with_activation_checkpointing%22%5D)).

distributed/_tools/test_fsdp2_mem_tracker.py::TestTrackerFullyShard1DTrainingCompose::test_tracker_with_activation_checkpointing [GH job link](https://github.com/pytorch/pytorch/actions/runs/11692278898/job/32562714664) [HUD commit link](https://hud.pytorch.org/pytorch/pytorch/commit/59b66944d4287ca154508c25691fde95b5cecb36)

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd
Repository: rust
Issue: Double same-bound  `where` clause causes failed type inference
Labels: A-trait-system,T-compiler,C-bug,T-types,E-needs-investigation

I came across this scenario where having two functions with the same `where`-bounds causes type inference failure:

```rust
pub fn foo<S>(_: S) where String: From<S> {}
pub fn bar<S>(s: S) where String: From<S> {
    // Mismatched types error!
    foo(String::from(s)); 
}
```

I would expect the type inference to hold up and allow for calling `foo` with a `String` constructed in `bar`. Instead it fails with a mismatched types error (E0308) saying ``` expected type parameter `S`, found `String` ```

Notably, *ANY* `String` or `&str` constructed in `bar` and passed to `foo` will fail type inference. For example:

```rust
pub fn baz<S>(_: S) where String: From<S> {
    // Mismatched types error!
    foo(""); 
}

pub fn bam<S>(_: S) where String: From<S> {
    // Mismatched types error!
    let s: String = "".to_owned();
    foo(s); 
}
```

Some examples of similar scenarios that work, but show that there shouldn't be anything wrong with the actual operation (particularly `bap`):

```rust
pub fn bam<S>(s: S) where String: From<S> {
    // OK!
    foo(s); 
}
pub fn bap<S>(s: S) where String: From<S> {
    // OK!
    foo::<String>(String::from(s)); 
}
pub fn bao() {
    // OK!
    let s: String = "".to_owned();
    foo(s); 
}

// Strangely, inverting the From bound to an Into bound fixes things
pub fn foo2<S>(_: S) where S: Into<String> {}
pub fn bar2<S>(s: S) where String: From<S> {
    // OK!
    foo2(String::from(s)); 
}
```


### Meta

This occurs on stable (1.82.0), beta (1.83.0-beta.4 // 2024-11-02 67512dee7a470ea7cdd6), and nightly (1.83.0-nightly // 2024-11-03 b8c8287a229cd79604aa) in debug and release modes.

[Full Playground Link](https://play.rust-lang.org/?version=stable&mode=release&edition=2021&gist=87fc83acfd704c0cdacd4e60d073f1c9)
Repository: PowerToys
Issue: PowerToys Run history only includes calculations if you have copied or pressed Enter
Labels: Issue-Bug,Issue-Docs,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

1. type in a sum in PowerToys Run
2. do NOT select the result or press Enter
3. use !! to get a history list
4. notice that the sum does not appear despite this text in the documentation. "If you recently did some math like = 1245+6789, and you need to recall it, it will be in the history. You can find it with !! 678 or even !! 8034."

### ✔️ Expected Behavior

The documentation leads me to expect that all calculations will be accessible in history even if I didn't copy them. 

### ❌ Actual Behavior

the calculation is not shown in the history.

If this is the intended behaviour then it's an issue with the documentation rather than with PowerToys Run but it would be really useful to be able to get back to a calculation I did earlier in the day and need to look back at **because** I didn't remember to copy it at the time!

### Other Software

_No response_
Repository: next.js
Issue: Enum in types.d.ts used in useState hook crashes turbopack  
Labels: bug,Turbopack,linear: turbopack

### Link to the code that reproduces this issue

https://github.com/TijanaMazinjanin/nextjs_enum_bug

### To Reproduce

1. Clone the linked repository
2. pnpm install && pnpm run dev-turbo
3. Open localhost:3000

You will see turbopack crashing.


### Current vs. Expected behavior

The code should work the same with or without the --turbo flag. However, it currently crashes when --turbo is enabled, while it runs as expected without it. 

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 15707
  Available CPU cores: 16
Binaries:
  Node: 22.6.0
  npm: N/A
  Yarn: N/A
  pnpm: 9.7.0
Relevant Packages:
  next: 14.2.16 // An outdated version detected (latest is 15.0.2), upgrade is highly recommended!
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Turbopack

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

When I define enum in any other file except types.d.ts it's working. Latest nextjs 15.0.2 has the same issue. Linux distributions also have this issue.
Repository: go
Issue: x/build: adjust LUCI load at openbsd-ppc64 builder
Labels: Builders,NeedsFix

As agreed with @dmitshur and Michael K, add GOMAXPROCS to try reducing the load average on the builder machine.
Repository: flutter
Issue: [in_app_purchase_storekit] Add `latestTransaction` for the iOS wrapper
Labels: c: new feature,platform-ios,p: in_app_purchase,package,P2,team-ios,triaged-ios

### Use case

As a convenience method, it would be useful to have the [latestTransaction](https://developer.apple.com/documentation/storekit/product/3803206-latesttransaction) method added to the package. This allows us to get the most recent transaction for a giving product, and quickly evaluate it. For example, if we are evaluating if a subscription is still valid and how long for it to renew.

### Proposal

Add latestTransaction.
Repository: langchain
Issue: Supabase vectorstore does not support $in in a filter to match to a list of ids 
Labels: Ɑ: vector store

### 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

``` python
from langchain_community.vectorstores import SupabaseVectorStore

vector_store = SupabaseVectorStore(table_name="documents",
                                        query_name="match_documents",
                                        embedding=cached_embedding,
                                        client=supabase
)
policy_ids = ['20bac4b3-5964-47cf-a2a9-06e888c14add', '6004585c-624a-417c-91b5-ff4b9374b0fd']
vector_store.similarity_search_with_relevance_scores(
                    question,
                    filter = {"file_id": {"$in": policy_ids}},
                    )

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

None

### Description

I'm using Superbase as a vector store. I want to filter the similarity search to just the rows  where metadata-> file_id is in a list of file_ids

According to the documentation I should be able to use filter = {"file_id": {"$in": policy_ids}}, however this results in no rows being returned.

If I use filter = {"file_id": policy_ids[0} I get the match for the first policy_id

The issue seems to be $in is not supported in Superbase

### System Info

System Information
------------------
> OS:  Linux
> OS Version:  #1 SMP PREEMPT_DYNAMIC Wed, 23 Oct 2024 21:23:44 +0000
> Python Version:  3.11.2 (main, Aug 26 2024, 07:20:54) [GCC 12.2.0]

Package Information
-------------------
> langchain_core: 0.3.10
> langchain: 0.3.3
> langchain_community: 0.3.2
> langsmith: 0.1.134
> langchain_anthropic: 0.2.3
> langchain_openai: 0.2.2
> langchain_text_splitters: 0.3.0

Optional packages not installed
-------------------------------
> langgraph
> langserve

Other Dependencies
------------------
> aiohttp: 3.10.10
> anthropic: 0.36.0
> async-timeout: Installed. No version info available.
> dataclasses-json: 0.6.7
> defusedxml: 0.7.1
> httpx: 0.27.2
> jsonpatch: 1.33
> numpy: 1.26.4
> openai: 1.51.2
> orjson: 3.10.7
> packaging: 24.1
> pydantic: 2.9.2
> pydantic-settings: 2.5.2
> PyYAML: 6.0.2
> requests: 2.32.3
> requests-toolbelt: 1.0.0
> SQLAlchemy: 2.0.35
> tenacity: 8.5.0
> tiktoken: 0.8.0
> typing-extensions: 4.12.2
Repository: ant-design
Issue: TreeSelect组件单选模式添加与Select组件labelRender类似的功能
Labels: Inactive

### What problem does this feature solve?

在TreeSelect组件单选模式中选中节点后，不想直接展示node所对应的title，想要加工一下。

### What does the proposed API look like?

与Select组件labelRender函数类似，或者与TreeSelect tagRender一致。

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: next.js
Issue: Issues creating web workers `SecurityError: Failed to construct 'Worker'`
Labels: bug,Webpack,Runtime

### Link to the code that reproduces this issue

https://github.com/pantoninho/nextjs-worker-bug

### To Reproduce

(I'm getting errors creating a next-app with `reproduction-template`, so I created a regular next-app instead)

I'm able to create web workers inside a component, but a `SecurityError` is thrown when instantiating them inside a hook.

1. run `npm run dev`
2. open `localhost:3000`
3. assert there's no issues with the created webworker by clicking `send message` button
4. open `localhost:3000/issue` (or click the link in the root page) and a `SecurityError` is thrown (attached below)
5. check the code differences between `app/page.tsx` and `app/issue/page.tsx`:

```js
// this works
function Component() {
  const workerRef = React.useRef();

  React.useEffect(() => {
    workerRef.current = new Worker(new URL("./worker.ts", import.meta.url)); // <-- works
    return () => {
      workerRef.current?.terminate();
    };
  }, []);
  
  return <div />
}
```

```js
// this doesn't work
function Component() {
  const worker = useWorker('./worker.ts');
  
  return <div/>  
}

function useWorker(path) {
  const workerRef = React.useRef();

  React.useEffect(() => {
    workerRef.current = new Worker(new URL(path, import.meta.url)); // <-- SecurityError is thrown
    return () => {
      workerRef.current?.terminate();
    };
  }, [path]);
  
  return workerRef;
}


```


<img width="1019" alt="image" src="https://github.com/user-attachments/assets/52e6dd5c-7ce1-40f8-b792-5d15efb54dd9">


### Current vs. Expected behavior

I expected to be able to create web workers inside hooks.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 20.18.0
  npm: 10.8.2
  Yarn: N/A
  pnpm: 9.12.2
Relevant Packages:
  next: 15.0.2 // Latest available version is detected (15.0.2).
  eslint-config-next: 15.0.2
  react: 19.0.0-rc-02c0e824-20241028
  react-dom: 19.0.0-rc-02c0e824-20241028
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure, Runtime, Webpack

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local)

### Additional context

_No response_
Repository: rust
Issue: Hang after encountering overflow errors for huge types 
Labels: A-diagnostics,P-high,T-compiler,regression-from-stable-to-stable,C-bug,I-hang,S-has-mcve

### Code

```rs
fn main() {
    let mut x = None;
    let y = x;
    let z = Default::default();
    let mut w = (&mut x, z, z);
    let a = (&mut None::<fn(&())>, y, None::<fn(&'static ())>);
    w = z;
}
```


### Affected release channels

- [ ] Previous Stable
- [ ] Current Stable
- [ ] Current Beta
- [x] Current Nightly

### Rust Version

rustc 1.84.0-nightly (bc5cf994d 2024-11-05)
binary: rustc
commit-hash: bc5cf994db9fb46712cefd89f78ad7fc51f184a2
commit-date: 2024-11-05
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.3

### Current error output

_No response_

### Backtrace



### Anything else?
Repository: vscode
Issue: An error is displayed after the notebook line height is modified
Labels: bug,info-needed,notebook-layout


Type: <b>Bug</b>

When I use jupyter notebook, after changing the notebook's line height, the markdown cell gets an overlap error.
![Image](https://github.com/user-attachments/assets/142cbac7-3f30-4706-869a-beab398fbf2b)


VS Code version: Code 1.95.1 (65edc4939843c90c34d61f4ce11704f09d3e5cb6, 2024-10-31T05:14:54.222Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 5 5600H with Radeon Graphics          (12 x 3294)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|31.86GB (20.61GB free)|
|Process Argv|--crash-reporter-id 272d59d0-41a5-4431-b818-35228202384d|
|Screen Reader|no|
|VM|44%|
</details><details><summary>Extensions (19)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-jetbrains-icon-theme|cha|2.23.0
Fitten-Code|Fit|0.10.96
vscode-jetbrains-keybindings|isu|0.1.9
rainbow-csv|mec|3.12.0
vscode-language-pack-zh-hans|MS-|1.95.2024103009
debugpy|ms-|2024.12.0
python|ms-|2024.18.0
vscode-pylance|ms-|2024.11.1
jupyter|ms-|2024.10.0
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.21
vscode-jupyter-cell-tags|ms-|0.1.9
vscode-jupyter-slideshow|ms-|0.1.6
cmake-tools|ms-|1.19.52
cpptools|ms-|1.22.10
cpptools-extension-pack|ms-|1.3.0
cmake|twx|0.0.17
markdown-all-in-one|yzh|3.6.2
material-theme|zhu|3.17.5

(4 theme extensions excluded)

</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
f3je6385:31013174
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
nativerepl1:31139838
refactort:31108082
pythonrstrctxt:31112756
nativeloc2:31134642
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013

```

</details>

<!-- generated by issue reporter -->
Repository: ant-design
Issue: Modal Overlay scroll blocking is not compatible with the overflow-y scroll style of html elements 
Labels: Inactive,unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-5j3xtp)


### Steps to reproduce

1. Set html style `overflow-y: scroll`
2. Open Modal with scroll bars 

### What is expected?

1. Scrollbar is hidden
2. Keep current view position unchanged

### What is actually happening?

1. First the scroll bar flashes
2. Then the view position is reset to the top

| Environment | Info |
| --- | --- |
| antd | 5.21.6 |
| React | 18.3.1 |
| System | MacOS 13.3 (22E252) |
| Browser | Google Chrome 130.0.6723.92（正式版本） (arm64) |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->