sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: [DevTools Bug]: `sayHelloToBackendManager` continuously and pointlessly polls on every page
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

(all sites)

### Repro steps

From any page:

```js
const printMessage = (event) => {console.log(event)};
window.addEventListener('message', printMessage);
```

Since there isn't a place to actually describe the bug, i'll put it here:
`sayHelloToBackendManager` is set to poll here until `backendInitialized` is `true`: https://github.com/facebook/react/blob/b3003047101b4c7a643788a8faf576f7e370fb45/packages/react-devtools-extensions/src/contentScripts/proxy.js#L17-L23

The polling message has a source `react-devtools-content-script`: https://github.com/facebook/react/blob/b3003047101b4c7a643788a8faf576f7e370fb45/packages/react-devtools-extensions/src/contentScripts/proxy.js#L41

The switch to set `backendInitialized = true` checks for the message source `react-devtools-bridge`: https://github.com/facebook/react/blob/b3003047101b4c7a643788a8faf576f7e370fb45/packages/react-devtools-extensions/src/contentScripts/proxy.js#L65-L66

the `react-devtools-bridge` sourced message is sent from the backend by whatever invokes this: https://github.com/facebook/react/blob/b3003047101b4c7a643788a8faf576f7e370fb45/packages/react-devtools-extensions/src/contentScripts/backendManager.js#L127

but the `handleMessageFromPage` function returns if the `event.source` isn't the `window` object of the page. Presumably the backend does not have the same window object as the page, or else using `postMessage()` would be pointless: https://github.com/facebook/react/blob/b3003047101b4c7a643788a8faf576f7e370fb45/packages/react-devtools-extensions/src/contentScripts/proxy.js#L59

The `'react-devtools-bridge'` message never flips `backendInitialized = true`, so the polling never terminates.

This is causing the bitwarden ppl to get a decent amount of heat, and it's actually devtools causing the problem - https://github.com/bitwarden/clients/issues/7575



### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: neovim
Issue: Command line usage (`nvim -l` or `nvim --headless`) does not print into the standard output
Labels: bug,messages

### Problem

Nvim running in the head-less mode, e.g., `nvim -l <lua script>` or `nvim --headless -c <cmds>` that writes some output, actually does not write into stdout (fd=1). All the messages are written to stderr (fd=2); see also #24184.

The current behavior is a bit unexpected, and there seems no easy way to make nvim behave as a standard CLI program. This hinders using `nvim -l` as a Lua scripting engine.

### Steps to reproduce

For `nvim -l`:

```bash
# print to console
❯❯❯ echo 'print("hi")' | nvim --clean -i NONE -n -l -
hi

# try to redirect stdout, but nope
❯❯❯ echo 'print("hi")' | nvim --clean -i NONE -n -l - >/dev/null
hi
```

Same for other messages: e.g. `echomsg`:

```bash
❯❯❯ nvim --clean -i NONE -n --headless -c 'echom "echom"' -c 'qa'  > /dev/null
echom

❯❯❯ nvim --clean -i NONE -n --headless -c 'echom "echom"' -c 'qa'  2> /dev/null
```

### Expected behavior

Nvim should write to stdout, so Nvim's stdout can be piped.

Error messages should be written to stderr.

### Note (workaround)

Using direct stdio works. Because in Nvim, the global Lua function `_G.print()` and `:echom` are currently designed to write into some channel (messages), not to stdout.

```
io.stdout:write("hi")
```

So one could override `_G.print` with `io.stdout:write()`, but I think this could be a default behavior of `_G.print` in the headless mode -- at least for Lua.

For normal `:messages`, I'm not 100% sure whether it should directly write to `stdout`, but it may be reasonable to do so, so that one can read vim's message output in the headless mode -- without the use of additional APIs: e.g. `nvim_command_output()`.

### Neovim version (nvim -v)

NVIM v0.10.0-dev-2121+g06aebfa99  (in all NVIM versions so far)

### Vim (not Nvim) behaves the same?

N/A

### Operating system/version

macOS 14

### Terminal name/version

xterm

### $TERM environment variable

xterm-256color

### Installation

build from repo
Repository: pytorch
Issue: [RFC][Export] Capture module attribute/annotation in `torch.export.unflatten`
Labels: feature,triaged,onnx-needs-info,export-triage-review,oncall: export

## Motivation

Often backends need to know certain attribute values in order to run their optimizations. It would be extremely helpful to capture the annotated attributes and their values for unflattened modules.

Here is one example, where one may want to retrieve `eps` value of a layernorm module. Without this feature, to retrieve `eps` value from the unflattened graphs, one would need to perform node level analysis and pattern matching, which is messy and unstable so less than ideal.

```python
import torch

class LN(torch.nn.Module):
    eps: float

    def __init__(self, eps=1e-5):
        super().__init__()
        self.eps = eps

    def forward(self, x):
        mean = x.mean(dim=-1, keepdim=True)
        std = x.std(dim=-1, keepdim=True)
        return (x - mean) / (std + self.eps)

class Model(torch.nn.Module):
    def __init__(self, eps):
        super().__init__()
        self.ln = LN(eps)

    def forward(self, x):
        return self.ln(x)

model = Model(1e-3)
print(f"LN eps: {model.ln.eps}")

# Export and unflatten
x = torch.randn(2, 3, 4, 5)
ep = torch.export.export(model, (x, ))
um = torch.export.unflatten(ep)

# Print graph, eps is a scalar constant in the graph with no name.
um.ln.graph_module.print_readable()
# AttributeError: 'InterpreterModule' object has no attribute 'eps'
print(f"LN eps: {um.ln.eps}")

```

cc @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4 @titaiwangms , @thiagocrepaldi
Repository: material-ui
Issue: [joy-ui][Autocomplete] Occasionally doesn't drop down a list for selection when the mouse clicks on border of the AutoComplete 
Labels: on hold,component: autocomplete,package: joy-ui

### Steps to reproduce


https://github.com/mui/material-ui/assets/6795515/ab1300b7-cc63-410c-8733-8472c77e18b2



### Current behavior

_No response_

### Expected behavior

_No response_

### 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**: JoyUI AutoComplete occasionally does not drop down
Repository: ant-design
Issue: 为 `Layout.Header` 增加 `theme` 属性
Labels: help wanted,💡 Feature Request,Inactive

### What problem does this feature solve?

Stackblitz example: https://stackblitz.com/edit/vitejs-vite-zbwwhp?file=src%2FApp.tsx

我知道这个问题已经讨论过无数次了，但我看了一下，每次的解决方案几乎都是使用提供的 `token` 来解决问题。
但这实际上并不是解决这个问题的好办法。或者换句话说，这个 `theme` 的behaviour，应该是大多数人所需要的。

`Sider` 的 `theme="light"` 实际上并不是 亮色主题 的意思, 而是跟随 `algorithm`. 从我提供的例子可以看出, 如果 `theme="dark"` (default),  那他就一直是dark, 如果使用 `light`, 那么他就会跟着 `algorithm` 走. 正常来说这个真的是在有切换主题 (尤其暗黑模式) 的情况下需要的东西.

对于 `Header` 来说, 首先就是那个奇怪的颜色, 然后还有在亮色模式下默认也是接近黑色的文字颜色, 就完全啥都看不见. 然后更奇怪的是 文字颜色是随 `algorithm` 变化的, 但是背景颜色是固定的 🤣.

相对于设置 `Header` 相关的 `token`, 我真的觉得更好的解决办法是给 `Header` 一个与 `Sider` 相同的 `theme` 属性, 这样应该能解决大部分需求.

然后这个 `theme` 属性的 `light` 值可能也要商榷一下, 毕竟有点误导, 应该说是 `auto` 比较准确.

我知道这个问题真的很多人提过了, 但我没看见有人提出过我这个观点. 麻烦考虑一下 感谢.

### What does the proposed API look like?

为 `Header` 提供和 `Sider` 一样的 `theme` 属性, 行为也一致 (即 `light` 为跟随 `algorithm`)

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: Track total number of merge conflicts when cherry picking PR from master branch to release branch
Labels: P2,team-release,triaged-release

Context: in the current [github actions to auto apply cherry pick](https://github.com/flutter/flutter/blob/master/.github/workflows/easy-cp.yml), we are not applying any resolution strategy when merge conflict happens. no resolution strategy was applied per previous discussions that we do not want to auto resolve and suggest wrong code to users.

We want to track the number of prs that would hit merge conflict when cherry picked from master to release. There are two ways to evaluate this metrics:
1. randomly pick PRs from master branch and cp them to release branch
2. when shipping releases, count the number of merge conflict PRs referenced in the cherry pick request

If using method 1 to collect this metric:
below are a list of PRs randomly selected from master branch that would hit merge conflict when cherry picked:
1. https://github.com/flutter/flutter/pull/141797&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;        [sample merge conflict](https://paste.googleplex.com/6499496492531712)
2. https://github.com/flutter/flutter/pull/141541 [merge conflict](https://github.com/flutter/flutter/actions/runs/7617807927)
3. https://github.com/flutter/flutter/pull/141910 [merge conflict](https://github.com/flutter/flutter/actions/runs/7644747566/job/20829730095)
4. https://github.com/flutter/flutter/pull/142277 [merge conflict](https://github.com/flutter/flutter/actions/runs/7674298650/job/20918625474)
5. https://github.com/flutter/flutter/pull/142904 [merge conflict](https://github.com/flutter/flutter/actions/runs/7792221696/job/21249796686)

And here is a list of PRs randomly selected from master branch that would successfully create pull request:
1. https://github.com/flutter/flutter/pull/137316  [automated workflow run](https://github.com/flutter/flutter/actions/runs/7644610462/job/20829302854).     [created pr](https://github.com/flutter/flutter/pull/142152)
2. https://github.com/flutter/flutter/pull/142336 [automated workflow run](https://github.com/flutter/flutter/actions/runs/7674312382/job/20918667749)   [created pr](https://github.com/flutter/flutter/pull/142349)
3. https://github.com/flutter/flutter/pull/142281 [automated workflow run](https://github.com/flutter/flutter/actions/runs/7674346682/job/20918763658)   [created pr](https://github.com/flutter/flutter/pull/142350)
4. https://github.com/flutter/flutter/pull/142430 [created pr](https://github.com/flutter/flutter/pull/142949#issuecomment-1928489081)
5. engine PR that succeeded https://github.com/flutter/engine/pull/50401 [created PR](https://github.com/flutter/engine/pull/50418) 

Will keep updating the list when more data points become available (where the pr has a base commit newer than our merged commit)

Summary:
The merge conflicts as manifested in workflow runs align with the merge conflicts the pr would encounter if cherry picked through the terminal. and .ci.yaml changes seems to be the pr change that hit more conflicts than others.
Repository: pytorch
Issue: Supporting custom attributes with `__torch_function__` tensor subclasses
Labels: good first issue,triaged,enhancement,module: __torch_function__,module: dynamo

### 🚀 The feature, motivation and pitch

Currently we only support accessing attributes that are defined on the base `torch._tensor` implementation. Since some torch function subclasses define custom attributes it's a good idea to support accessing these as well. 

See https://github.com/pytorch/pytorch/blob/a468b9fbdf75b2da128e5fac4284ebbb981cd31a/torch/_dynamo/variables/torch_function.py#L180C1-L215C1 for the current implementation. 

Ideally we should support two cases 1) if a user defines a custom attribute that does *not* invoke `torch_function` on access (this is the default for an arbitrary attribute) and 2) if the user explicitly adds [this decorator](https://github.com/pytorch/pytorch/blob/a468b9fbdf75b2da128e5fac4284ebbb981cd31a/torch/_tensor.py#L31) to an attribute, we should support tracing through it and dispatching appropriately or shortcutting to the dynamo handling of it to be consistent. 

### Alternatives

_No response_

### Additional context

_No response_

cc @hameerabbasi @rgommers @peterbell10 @ezyang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @aakhundov @kadeng
Repository: pytorch
Issue: DISABLED test_large_block_sizes_dynamic_shapes_cuda (__main__.DynamicShapesCudaTests)
Labels: triaged,module: flaky-tests,skipped,module: inductor

Platforms: linux

Old name of #113132

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler
Repository: pytorch
Issue: DISABLED test_large_block_sizes_dynamic_shapes_cuda (__main__.DynamicShapesCodegenCudaTests)
Labels: triaged,module: flaky-tests,skipped,module: inductor

Platforms: linux

Old name of #113136

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler
Repository: pytorch
Issue: DISABLED test_large_block_sizes_cuda (__main__.CudaTests)
Labels: triaged,module: flaky-tests,skipped,module: inductor

Platforms: linux
Old name of #113140

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler
Repository: yt-dlp
Issue: Cannot use regex quantifier {n} in an alias
Labels: bug,patch-available

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm asking a question and **not** reporting a bug or requesting a feature
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar questions **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Please make sure the question is worded well enough to be understood

I am trying to add `--parse-metadata "description:Released on: (?P<meta_date>\d{4}-\d\d-\d\d)" --parse-metadata "description: · (?P<artist>.+?)( · .+)?$"` to my yt-dlp.conf, but it gives a replacement index error I don't know how to fix.

The problem already occurs with `--alias test '--parse-metadata "description:Released on: (?P<meta_date>\d{4}-\d\d-\d\d)"'` in my configuration file. Using `--parse-metadata "description:Released on: (?P<meta_date>\d{4}-\d\d-\d\d)"` in the command-line works fine, it's when it's put in yt-dlp.conf that I get an error.

Ideally, I'd like to include these parse-metadata statements to my audio-only alias like so:
`--alias yta '-x --remux-video "webm>ogg/opus>ogg/aac>m4a" -o "%(artist,uploader)s - %(title)s.%(ext)s" --embed-metadata --parse-metadata "description:Released on: (?P<meta_date>\d{4}-\d\d-\d\d)" --parse-metadata "description: · (?P<artist>.+?)( · .+)?$"'`

### Provide verbose output that clearly demonstrates the problem

- [X] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [X] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

```shell
[debug] Command-line config: ['-vU', 'https://youtu.be/fGgsq4pwOi4', '--print', 'meta_date']

Usage: yt-dlp.exe [OPTIONS] URL [URL...]

yt-dlp.exe: error: wrong --alias OPTIONS formatting; Replacement index 4 out of range for positional args tuple
```
Repository: ant-design
Issue: antd v5 比 v4 的 Select 打开慢一秒
Labels: 🐛 Bug,Inactive

### Reproduction link

[https://stackblitz.com/edit/react-nawssr?file=demo.tsx](https://stackblitz.com/edit/react-nawssr?file=demo.tsx)

### Steps to reproduce

这是 v4 链接 https://stackblitz.com/edit/react-nawssr?file=demo.tsx

https://github.com/ant-design/ant-design/assets/7971419/883800de-297e-46e9-922a-e8b831fd1381


这是 v5 链接 https://stackblitz.com/edit/react-yqzh3r?file=demo.tsx


https://github.com/ant-design/ant-design/assets/7971419/c9b12889-5963-41c2-91a2-c0d4d897865d



### What is expected?

v4 的 Select 打开是跟随 Popover 打开立刻打开，但是 v5 会慢一秒再打开下拉框

### What is actually happening?

v5 也能跟 v4 一样，立刻打开下拉框

| Environment | Info |
| --- | --- |
| antd | 5.13.1 |
| React | latest |
| System | mac |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: A question about the `RenderViewportBase` layout algorithm
Labels: framework,f: scrolling,P3,team-framework,triaged-framework

Hi there!

When I looked at the layout algorithm for `RenderViewportBase`, it seemed like there was a slight problem with the initial value of `layoutOffset` for the reverse slivers (As the code shows below, line#1540). I think the initial value of `layoutOffset` should be calculated based on `centerOffset`, something like this: 

`layoutOffset: centerOffset < 0 ? mainAxisExtent - centerOffset : forwardDirectionRemainingPaintExtent`

which is more accurately reflects the true position of the reverse slivers after they exit the trailing edge of the viewport (although visually they are no longer visible).

In contrast, the `layoutOffset` initial value for the forward slivers is calculated based on the `centerOffset`, which is reasonable in my opinion.

I'm not sure if this was an oversight on the developer's part, but if not, what was the design consideration?

https://github.com/flutter/flutter/blob/46bbf4029a941d0df116e5285690917b55a5460d/packages/flutter/lib/src/rendering/viewport.dart#L1534-L1552
Repository: PowerToys
Issue: MWB link failed when import the setting backup 从备份恢复设置后无法使用无界鼠标
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.77.0

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

1.同局域网两台设备正常连接，Mouse Without Borders正常工作；
2.一台设备导出设置备份，另一台设备导入；（或两台设备导入同一个设置备份）
3.两台设备上的Mouse Without Borders中看对方的设备图标显示为黄蓝框闪烁，无法正常工作。
4.重新生成配对密钥尝试再次配对也无效，在IP地址映射中手动映射计算机名和IP地址依然无效；
5.多次重启软件和电脑都没有作用。
----------
1. Two devices on the same LAN are connected normally, and Mouse Without Borders works normally;
2. One device exports the settings backup and the other device imports it (or both devices import the same settings backup);
3. Mouse Without Borders on both devices show each other's device icon as a flashing yellow and blue box, and cannot work normally;
4. Regenerate the pairing key and try to pair again, it is not effective, and manually mapping computer name and IP address in IP address mapping is still not effective;
5. Reboot the software and computer several times to no avail.

Translated with DeepL.com (free version)

[PowerToysReport_2024-01-17-16-27-05.zip](https://github.com/microsoft/PowerToys/files/13983298/PowerToysReport_2024-01-17-16-27-05.zip)


### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: ollama
Issue: Add obsidian model
Labels: model request

Could you add the obsidian model to the library?
Repository: react-native
Issue: React Native Fetch Api Cause Memory Leak
Labels: 🌐Networking,Needs: Triage :mag:

### Description

just use fetch api, and use Android Studio Profiler watch memory change.

### Steps to reproduce

1. clone my reproduction repo
2. click start button to constantly fetch
3. use tool(AS Profiler) watch memory change
4. click pause button to break off fetch
5.  use tool(AS Profiler) watch memory change

### React Native Version

0.73.2

### Affected Platforms

Runtime - Android, Build - MacOS

### Output of `npx react-native info`

```text
info Fetching system and libraries information...
System:
  OS: macOS 13.0
  CPU: (8) arm64 Apple M1
  Memory: 41.33 MB / 16.00 GB
  Shell:
    version: 5.8.1
    path: /bin/zsh
Binaries:
  Node:
    version: 18.16.0
    path: ~/.nvm/versions/node/v18.16.0/bin/node
  Yarn:
    version: 1.22.19
    path: /usr/local/bin/yarn
  npm:
    version: 9.5.1
    path: ~/.nvm/versions/node/v18.16.0/bin/npm
  Watchman:
    version: 2022.11.14.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.11.3
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK: Not Found
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.1 AI-231.9392.1.2311.11255304
  Xcode:
    version: /undefined
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.9
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.2
    wanted: 0.73.2
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: false
```


### Stacktrace or Logs

```text
no crash log. Run the reproduction demo, if you watch enough time, you will see it.
```


### Reproducer

https://github.com/FE-Sadhu/rn-fetch-memory-leak

### Screenshots and Videos

![AS Profiler](https://github.com/facebook/react-native/assets/39456032/ba51bc98-332f-496d-a233-ca88ab3dbda1)
Repository: godot
Issue: _set() with @tool does not work when property is edited from 2D/3D tab
Labels: discussion,topic:editor

### Tested versions

- Reproducible in 4.2.1.stable

### System information

Godot v4.2.1.stable - Windows 10.0.19045 - GLES3 (Compatibility) - ANGLE (AMD, AMD Radeon(TM) R3 Graphics (0x000098E4) Direct3D11 vs_5_0 ps_5_0, D3D11-27.20.20906.6) () - AMD A4-9125 RADEON R3, 4 COMPUTE CORES 2C+2G (2 Threads)

### Issue description

On the provided MRP, there are several nodes for example. The Panel one. It has this code.
```
@tool
extends Panel

func _set(property, value):
	if property == "size":
		size = value
		print("Resized to %v" % value)
		return true
	return false
```
Now when you try to edit the size of said Panel with Inspector (Layout > Transform > Size), either by typing the value then press Enter, **or** dragging the number left and right, you will notice there are several text getting printed, which means the code runs fine.

However, when you resize via the 2D scene editor, by clicking the panel once, until there's orange outline, then dragging the outline to resize the Panel, there will be no print out at all, which means the code doesn't run.

It's also a the case with the Sprite2D and Marker3D example.

### Steps to reproduce

- Download the MRP, open the project in godot 4.2.1
- Open demo.tscn, navigate to the 2D editor mode
- Click the Panel node so that it's selected
- Try to modify the "size" property of the Panel from the Inspector, and inspect the print out on the Output tab below
- Now with the panel selected in 2D editor, drag one of the circle orange joints on the Panel, resize it.
- Notice that the size property in the Inspect tab with change, but there are no print out

You can try and test with other node like the Sprite2D and Marker3D.

### Minimal reproduction project (MRP)

[setget_test.zip](https://github.com/godotengine/godot/files/13983849/setget_test.zip)