sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Timer function doesn't work across computers in Godot V4.2 Mono
Labels: bug,topic:core,needs testing

### Tested versions

Reproducible in: 4.2 Stable Mono Official [46dc27791]
Not reproducible in: 4.1 Stable Mono Official [bd6af8e0e]

### System information

Godot v4.2.stable.mono - Windows 10.0.19045 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 1650 SUPER (NVIDIA; 30.0.14.7247) - AMD Ryzen 5 5600X 6-Core Processor (12 Threads)

### Issue description

Using a timer, or coding your own timer, doesn't work across computers. On mine it worked fine, but on another computer the timing would be off. In this case it was used as a spawn timer to spawn nodes in after 2 seconds. Testing a build on another computer results in a difference in spawn time. This issue occurred with both the timer node and hard coding my own timer in the _process() function. Reverting to Godot V4.1 Mono Stable fixed this issue.

# Code used for timer

```
func spawn_node() -> void:
    # Code to spawn node
    timerName.start()


func _on_timer_timeout():
    spawn_node()
```


# Code used for hard coded timer

```
func _process(delta):
    if spawnTimeLeft <= 0:
        spawn_node()
        spawnTimeLeft = spawnTime
    else:
        spawnTimeLeft -= delta

func spawn_node() -> void:
    # Code to spawn node
```

# Settings for timer
![image](https://github.com/godotengine/godot/assets/25846972/87b2a381-9eb4-40ad-939b-eb6b3ddf64e3)


### Steps to reproduce

- Create timer node
- Mark as one shot, auto start not on
- Create script that starts timer when player starts the game
- Set wait time for timer when player starts game
- Connect signal timeout to script
- Call spawn node function when timeout is called
- Start timer again when spawn node function finishes

![image](https://github.com/godotengine/godot/assets/25846972/98143ed1-902c-4202-addb-81fd4ac1af1a)


### Minimal reproduction project (MRP)

Shouldn't be project dependent, but just in case here's the files as well as an exe version to run (timers are under game_loop scene found under res -> Scenes folder):

[BUG-REPORT-Fiverr-pegasus-mobile-game-source-code.zip](https://github.com/godotengine/godot/files/13596422/BUG-REPORT-Fiverr-pegasus-mobile-game-source-code.zip)

[BUGREPORT.zip](https://github.com/godotengine/godot/files/13596435/BUGREPORT.zip)
Repository: PowerToys
Issue: Multiline and control characters text and [pause] in Keyboard Manager 
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager,Needs-Triage

### Description of the new feature / enhancement

Hi, 

I would love to have following possibilities in keyboard manager text

- use control characters like tab, CR/LF
- insert multiline text (Windows and Linux)
- pause between 2 blocks of thext

### Scenario when this would be used?

I get multiple new labs with SSMS installed, which sometimes are short lived. 
most of these labs are isolated and protected, so I can't upload / download configuration files and hence export | import settings.
if I can make multi line and control keys combinations and pause, I would be able to group configuration settings like keyboard shortcuts, language defaults, etc. 

### Supporting information

_No response_
Repository: rust
Issue: Add parallel front-end test set to compiler-test
Labels: A-testsuite,WG-compiler-parallel

Parallel front end need some tests in CI, to prevent certain changes from making it unavailable. (e.g. #113730)
```[tasklist]
### Tasks
- [ ] Modify compiler test harness to support repeated testing
- [ ] Testing with many threads
- [ ] use parallel front end in UI tests
```
Repository: create-react-app
Issue: Critical Security Vulnerability in @babel/traverse@7.22.8
Labels: needs triage,issue: bug report

<!--
    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please use this template and fill in as many fields below as you can.

    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.
-->

### Describe the bug
react-scripts@5.0.1 is using @babel/traverse@7.22.8 which has a critical vulnerability and was reported by Synk.

**Introduced through:**  react-scripts@5.0.1 › @babel/core@7.22.9 › @babel/traverse@7.22.8
**Introduced through:**  react-scripts@5.0.1 › @babel/core@7.22.9 › @babel/helpers@7.22.6 › @babel/traverse@7.22.8
**Introduced through:**  react-scripts@5.0.1 › jest@27.5.1 › @jest/core@27.5.1 › jest-config@27.5.1 › @jest/test-sequencer@27.5.1 › jest-runtime@27.5.1 › jest-snapshot@27.5.1 › @babel/traverse@7.22.8

The package @babel/traverse@7.22.8 used in react-scripts@5.0.1 has a critical security vulnerability reported by Synk. This vulnerability is introduced through multiple dependencies, including @babel/core@7.22.9, @babel/helpers@7.22.6, and indirectly through Jest dependencies (jest@27.5.1, @jest/core@27.5.1, jest-config@27.5.1, @jest/test-sequencer@27.5.1, jest-runtime@27.5.1, jest-snapshot@27.5.1).

**Vulnerability Details:**

Vulnerable Package: @babel/traverse
Vulnerable Version: 7.22.8
Affected Dependencies:
react-scripts@5.0.1
@babel/core@7.22.9
@babel/helpers@7.22.6
jest@27.5.1
@jest/core@27.5.1
jest-config@27.5.1
@jest/test-sequencer@27.5.1
jest-runtime@27.5.1
jest-snapshot@27.5.1

**Recommended Fix:**
Update the @babel/traverse package to the latest non-vulnerable version.
Repository: bitcoin
Issue: fuzz: Fix stability, determinism issues
Labels: Brainstorming,Tests

It would be good to track fuzz "stability" and determinism, and fix any issues.

Is there an easy way to generate a table for this metric for each fuzz target, maybe as a side effect of CI, or in another way?

edit: oss-fuzz link https://oss-fuzz.com/fuzzer-stats?group_by=by-fuzzer&fuzzer=afl&job=afl_asan_bitcoin-core&project=bitcoin-core
Repository: pytorch
Issue: [memory] extend CUDAPluggableAllocator to support caching algorithms of segments, blocks and calling frames
Labels: triaged,module: CUDACachingAllocator

### 🚀 The feature, motivation and pitch

The current implementation does not allow re-use pytorch memory pool caching strategy over external allocator:

```
void CUDAPluggableAllocator::cacheInfo(int dev_id, size_t* largestBlock) {
  TORCH_CHECK(
      false,
      "CUDAPluggableAllocator does not yet support cacheInfo. "
      "If you need it, please file an issue describing your use case.");
}
```

The **CUDAPluggableAllocator** just allocates what a person requests and no caching is applied :

<img width="650" alt="calling custom allocator" src="https://github.com/pytorch/pytorch/assets/89890040/9aa9b3f5-1938-49fc-8bbc-f4f97b908a84">

Hence for a new allocator, such as tracer allocator,  AMD **unified memory allocator** (#107605), we have to do memory management by ourselves :  pieces/segments, bins/blocks, and frames. 

Moreover, the **aten IR** has a very deep path to associate tensor, or op identities with the underlying allocation info (timeline, bytes, streamId, deviceId).

### Alternatives

The first solution involves inspecting aten IR such that memory timeline and liveness info can be directly attributed to aten IR and upper python calling frame.

The second solution still separates allocator and aten Ir but leaves a allocator an interface to interactively modify **AllocInfo**. This later should be added to python wrapper or hooks, so that users will not sense the existence of this modification.

### Additional context

_No response_
Repository: PowerToys
Issue: Update availabe - quick access to it
Labels: Idea-Enhancement,Product-Settings,Needs-Triage

### Microsoft PowerToys version

0.76

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

Wait until offered O:-)

### ✔️ Expected Behavior

If shown anywhere - a click on it may instantlly start an update. That is usial case an behaviour. Looking out to more informaton sounds uncommon. Woud make life easier.

### ❌ Actual Behavior

Hop and hop and hopto hot update button.

### Other Software

_No response_
Repository: rust
Issue: Make `std::env::{Args, ArgsOs}` `Send` and `Sync`
Labels: T-libs-api,C-feature-request

#48004 requests to make these 2 types `!Send` and `!Sync` and #48005 implements it.

From this [comment](https://github.com/rust-lang/rust/pull/48005#issuecomment-362947861), at that time, they were really not `Send` and `Sync`, but now, it seems both Unix and Wndows are defining `Args` as:

```rs
struct Args {
     args: vec::IntoIter<OsString>
}
```

which has no reason to be `!Send` and `!Sync`, I am not sure about that `cloudabi` platform though given that I didn't find it in the source code.

If the Std allocates for these types on all the platforms(i.e., basically a `Vec<OsString>`), we can probably make them `Send` and `Sync`
Repository: opencv
Issue: How to prohibit changing the aspect ratio of opencv window?
Labels: feature

### Describe the feature and motivation

At first I worked with the WINDOW_AUTOSIZE parameter when creating the window and I liked it, but I needed to zoom in, so I started experimenting with WINDOW_NORMAL and WINDOW_KEEPRATIO. Unfortunately, I didn't get the result I was expecting. The user can change the aspect ratio of the window. I tried to execute the resize function in a while loop on each iteration when one of the sides changes, keeping the aspect ratio unchanged, but it is only called when the left mouse button is released, not immediately when the user starts pulling the edge. It feels like the window is blocked for the main program until the left mouse button is released. Question: what should be changed so that the resize function is always called if the width or height of the window has changed, even if the left mouse button is still held down. 

std::string const begin_window = "Hello";
cv::namedWindow(begin_window, cv::WINDOW_NORMAL);
cv::imshow(begin_window, begin_image);
...
...
HWND hWnd = FindWindow(NULL, "Hello");
RECT begin_window_rect;
GetWindowRect(hWnd, &begin_window_rect);
int begin_window_width = begin_window_rect.right - begin_window_rect.left;
int begin_window_height = begin_window_rect.bottom - begin_window_rect.top;
float ratio = begin_window_width / (float)begin_window_height;
...
...
while (!(GetAsyncKeyState(0x51) && 0x01)) //  Q
	{
		std::cout << "\n\nleft: " << begin_window_rect.left << "\nright: " << begin_window_rect.right << "\ntop: " << begin_window_rect.top << "\nbottom: " << begin_window_rect.bottom;
		GetWindowRect(hWnd, &begin_window_rect);
		//cv::Rect new_begin_window_rect = cv::getWindowImageRect(begin_window);
		if ((begin_window_rect.right - begin_window_rect.left) != begin_window_width)
		{
			begin_window_width = begin_window_rect.right - begin_window_rect.left;
			begin_window_height = (int)((float)begin_window_width / ratio);
			MoveWindow(hWnd, begin_window_rect.left, begin_window_rect.top, begin_window_width, begin_window_height, TRUE);
		}
		else if ((begin_window_rect.bottom - begin_window_rect.top) != begin_window_height)
		{
			begin_window_height = begin_window_rect.bottom - begin_window_rect.top;
			begin_window_width = begin_window_height * ratio;
			MoveWindow(hWnd, begin_window_rect.left, begin_window_rect.top, begin_window_width, begin_window_height, TRUE);
		}
		cv::imshow(begin_window, begin_image);
		cv::waitKey(1);
	}

### Additional context

_No response_
Repository: flutter
Issue: Integrate Flutter in GitHub Advisory Database 
Labels: c: proposal,team-infra,P3,triaged-infra

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

In the past months we've had two critical security fixes released ([CVE-2023-4863](https://github.com/flutter/flutter/wiki/Hotfixes-to-the-Stable-Channel#3134-september-13-2023) and [CVE-2023-6345](https://github.com/flutter/flutter/wiki/Hotfixes-to-the-Stable-Channel#3163-december-5-2023)). However, unless you carefully read the Hotfixes to the Stable Channel release notes you would not know about these security fixes.

It would be great if Flutter would integrate with the [GitHub Advisory Database](https://github.com/advisories) so that security fixes are automatically reported to users that have their Flutter apps repositories in GitHub (which I assume is a large percentage).

For example, in the [CVE-2023-4863 GitHub Advisory report](https://github.com/advisories/GHSA-j7hp-h8jx-5ppr) Electron was listed as affected package. So all GitHub repositories that had electron as a dependency were automatically notified about the security fix.

### Proposal

Integrate Flutter in GitHub Advisory Database. 

I guess the integration is not as simple as just listing Flutter as an affected package in the reports, because currently GitHub doesn't detect [repositories that depend on Flutter](https://github.com/flutter/flutter/network/dependents), so first that needs to be addressed. But I think it would be worth the effort to improve the security of the Flutter ecosystem.
Repository: pytorch
Issue: Add support for measuring elapsed time in cuda-graphs
Labels: feature,triaged,module: cuda graphs

### 🚀 The feature, motivation and pitch

In order to measure elapsed time between events in cuda graphs, they need to be recorded with 
[cuEventRecordWithFlags](https://docs.nvidia.com/cuda/cuda-driver-api/group__CUDA__EVENT.html#group__CUDA__EVENT_1ge577e0c132d9c4961f220d79f6762c4b) using the `CU_EVENT_RECORD_EXTERNAL` flag.

This is a minor change that can be triggered automatically, by setting the flag if `torch.cuda.is_current_stream_capturing()`, requiring no change in any user-facing api.

Cheers

### Alternatives

This can currently be achieved  by bypassing pytorch, using [cuda-python](https://developer.nvidia.com/cuda-python) instead: 

```
if __name__ == "__main__":
    from cuda import cuda
    import torch

    torch.cuda.synchronize()

    success, a = cuda.cuEventCreate(0)
    success, b = cuda.cuEventCreate(0)

    m = torch.randn(128, 128, device="cuda")
    if True:
        g = torch.cuda.CUDAGraph()

        for _ in range(10):
            m @ m

        with torch.cuda.graph(g):
            stream = torch.cuda.current_stream().cuda_stream
            cuda.cuEventRecordWithFlags(a, stream, 1)
            m @ m
            cuda.cuEventRecordWithFlags(b, stream, 1)

    g.replay()

    time = cuda.cuEventElapsedTime(a, b)

    print(time)
```

But would be nicer to do directly in pytorch

### Additional context

_No response_

cc @mcarilli @ezyang
Repository: PowerToys
Issue: Quick Accent vs. repeat of pressed key
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response,Product-Quick Accent

### Microsoft PowerToys version

0.76

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Quick Accent

### Steps to reproduce

Issue of handling - timing of pressing text’s key an Activation Key.
As old OS user, setting keyboard to quick and fast repeat of pressed key became normal standard. Now, key’s repeating here may be a little too fast to Quick Accent.

### ✔️ Expected Behavior

Anything to get Quick Accent faster - and solw enough to hit Activation Key. Maybe an offer to change timeout of auto reperat to start.
And, I may say, quick typing can collide with Activation Key, space bar. Result is to lose pressed key but get first choice, at last instead of key an blank. Not optimal in handling.
Someone to need often special characters may use keyboard layouts matching that language or other tools to deliver often used characters (e.g. PharseExpress). Quick Accent’s activation is not really fluent

### ❌ Actual Behavior

Keyboard vs. Quick Accent  1:0
There shöould be more control or e.g. any other activation but not pressing and hoding (!) key plus then pressing Activation Key.
My solution (PhraseExpress) is giving a double minus as activation. Shift+D and Then Shift + double minus  (D__) brings me my Δ - Greek Delta, uppercase.  Quick Accent my beenfit from, as additional option, such a kind of activation.
All this assuming, someone does somtimes need Qick Accet but file getting it launchedas need. Trying an o I got «o » or «ò» quite immediate, but not the list. (And - there is no choice in list to reject ist if mis-typed; you need to press Esc to got back since releasing tht o gives ó but not Nohting)

### Other Software

_No response_
Repository: vscode
Issue: The "View Problem" positioning error in the code diagnosis pop-up window #926
Labels: feature-request,under-discussion,languages-diagnostics

Extension sample

lsp-user-input-sample

VS Code version

1.80.0

What went wrong?

Implement the code diagnosis plug-in and set the severity of Diagnostic to DiagnosticSeverity.Information. However, the "View Problem" of the code diagnosis pop-up window is incorrectly positioned and will jump to the error prompt box of other plug-ins (such as eslint).

![34e8e8b39e6542ea97798ed997dc1463](https://github.com/microsoft/language-server-protocol/assets/46375922/e4ddedd9-b019-4553-881d-a3976ad7979c)

After clicking, it will jump to the error report location of eslint.

![2d9b85bd06644cb287733d57926f1e44](https://github.com/microsoft/language-server-protocol/assets/46375922/18e2f156-6192-4e44-87a6-cb7ff74b91d0)

How should I deal with this?
Repository: neovim
Issue: Add `SnippetEnter` and `SnippetLeave` events
Labels: enhancement,lsp,events

### Problem

Currently there is no proper enough way for users (plugins) to act when snippet session is started or ended. This is useful, for example, in the following cases:
- Set mapping to be active only when snippet session is active.
- Create autocommand to be active only when snippet session is active. Like to stop snippet session when exiting to `Normal` mode by using `ModeChanged` event (created on `SnippetEnter`, deleted on `SnippetLeave`).

Both these use cases *can* be worked around by having `if vim.snippet.active()` check inside of them, but it seems very wasteful to have mapping/autocommand all the time when it is only needed during active snippet session.

### Expected behavior

`SnippetEnter` and `SnippetLeave` `User` events which trigger when snippet session starts and ends. Ideally, with some snippet parsing data parsed in `data` of autocommand's callback.
Repository: ant-design
Issue: allowClear=true on any component is not clickable when viewed on mobile 
Labels: Inactive,📱Mobile Device,unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-jyh2k9)

### Steps to reproduce

- create any component that supports the allowClear property
- try to click the "x" on a mobile device
- can't remove value

### What is expected?

- the value should be removed as it does on desktop

### What is actually happening?

- value doesn't get removed

| Environment | Info |
| --- | --- |
| antd | 5.12.1 |
| React | v18 |
| System | macos |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: When a `proc_macro` has a stack overflow, rustc crashes and errors confusingly
Labels: I-crash,T-compiler,C-bug,A-error-handling,A-proc-macros

### Code

```Rust
// --- macro_crate/src/lib.rs ---
use proc_macro::TokenStream;

#[proc_macro_derive(Trait)]
pub fn derive_trait(tokens: TokenStream) -> TokenStream {
    if true {
        derive_trait(tokens)
    } else {
        TokenStream::new()
    }
}


// --- my-crate/src/main.rs ---
#[derive(Trait)]
struct S;

fn main() {}
```


### Current output

```Shell
error: rustc interrupted by SIGSEGV, printing backtrace

~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/librustc_driver-fd05879751a9d790.so(+0x3104966)[0x7f5e85f04966]
/lib64/libc.so.6(+0x3e9a0)[0x7f5e82ac49a0]
.../test-issue/target/debug/deps/libmacro_crate-a1b04264bf77fcce.so(+0x21420)[0x7f5e79482420]

### cycle encountered after 3 frames with period 4
.../test-issue/target/debug/deps/libmacro_crate-a1b04264bf77fcce.so(+0x21425)[0x7f5e79482425]
.../test-issue/target/debug/deps/libmacro_crate-a1b04264bf77fcce.so(+0x21425)[0x7f5e79482425]
.../test-issue/target/debug/deps/libmacro_crate-a1b04264bf77fcce.so(+0x21425)[0x7f5e79482425]
.../test-issue/target/debug/deps/libmacro_crate-a1b04264bf77fcce.so(+0x21425)[0x7f5e79482425]
### recursed 63 times

.../test-issue/target/debug/deps/libmacro_crate-a1b04264bf77fcce.so(+0x21425)[0x7f5e79482425]

note: rustc unexpectedly overflowed its stack! this is a bug
note: maximum backtrace depth reached, frames may have been lost
note: we would appreciate a report at https://github.com/rust-lang/rust
error: could not compile `test-issue` (bin "test-issue")

Caused by:
  process didn't exit successfully: `~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc --crate-name test_issue --edition=2021 src/main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=212 --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 -C metadata=10df6c618bb41553 -C extra-filename=-10df6c618bb41553 --out-dir .../test-issue/target/debug/deps -C incremental=.../test-issue/target/debug/incremental -L dependency=.../test-issue/target/debug/deps --extern askama=.../test-issue/target/debug/deps/libaskama-a71517d66164d0f1.rlib --extern macro_crate=.../test-issue/target/debug/deps/libmacro_crate-a1b04264bf77fcce.so --extern serde=.../test-issue/target/debug/deps/libserde-916cd61b435466f2.rlib -C link-arg=-fuse-ld=lld` (signal: 11, SIGSEGV: invalid memory reference)
```


### Desired output

```Shell
Macro at `#[derive(Trait)]` has overflowed.

Or something that specifies the place where the macro overflowed, its crate, and that doesn't imply the issue is with rustc.
```


### Rationale and extra context

_No response_

### Other cases

_No response_

### Anything else?

_No response_