sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: async_hooks Use Case
Labels: doc,async_hooks

### Affected URL(s)

https://nodejs.org/api/async_hooks.html#async-hooks

### Description of the problem

I am not sure how I would accomplish the tracking of un-resolved async functions in this testing tool https://github.com/anywhichway/benchtest, without `async_hooks` in any kind of simple manner. The Node docs request the submission of a use case for `async_hooks` since the API is not recommended.

Currently the tool only requires a few lines of code:

```js
const asyncTracker = new Map(),
    asyncHook = async_hooks.createHook({
        init: (asyncId, type, triggerAsyncId, resource) => {
            asyncTracker.set(asyncId,{type,triggerAsyncId,resource})
        },
        destroy: asyncId => {
            asyncTracker.delete(asyncId);
        },
        promiseResolve: asyncId => {
            asyncTracker.delete(asyncId);
        },
    }),
    trackAsync = (on) => {
        if(on) {
            if(!asyncTracker.enabled) {
                asyncTracker.clear();
                asyncHook.enable();
            }
        } else if(!on && asyncTracker.enabled){
            asyncHook.disable();
        }
        asyncTracker.enabled = on;
    };
```
Repository: vscode
Issue: tasks.json - do not run other tasks until a [alpha] task is completed
Labels: feature-request,tasks

<!-- ⚠️⚠️ 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. -->
Found `dependsOn`, but I am looking for like an "alpha" task, that blocks all other tasks until it's done running. Found this issue was closed a few years ago https://github.com/Microsoft/vscode/issues/50422, opening a new one as I am hoping for a blocking task.

Here is my use case - 

- `task1` => create .venv (this is "alpha" task; a must have before doing anything else)
- `task2` => "set git defaults (a python script, that runs python exe from local .venv)" => `dependsOn = task1` and `runOn = folderOpen`
- `task3` => "poetry install" => `dependsOn = task1` and `runOn = folderOpen`

As you can see, both `task2` and `task3` are independent, but both depend on `task1`. 

Now when I combine this with `runOn = folderOpen`, both run the same `task1` at the same time, trying to create the `.venv` directory in the same location

Is it possible to add a new flag to mark a task to block other tasks until it's done running please? Hope I was able to explain properly. Let me know if you need more details
Repository: stable-diffusion-webui
Issue: [Bug]: 'NoneType' object is not subscriptable using Restore Faces
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

today i git pull the recent installation and suddenly if i use Restore Faces it gives me an error. Yesterday worked fine.

### Steps to reproduce the problem

1. Go to tex2img or anyone else
2. Select restore faces 
3. make a prompt and in the last step it stuck and gives that error in the terminal.


### What should have happened?

i updated to commit: 38b7186e

### Commit where the problem happens

38b7186e6e3a4dffc93225308b822f0dae43a47d

### What platforms do you use to access UI ?

Windows

### What browsers do you use to access the UI ?

Google Chrome

### Command Line Arguments

```Shell
--no-half --xformers --medvram
```


### Additional information, context and logs

_No response_
Repository: godot
Issue: GPUParticles3D ParticleProcessMaterial: setting scale_max to zero will cause particles to ignore further scale adjustments, when the emission_shape is different than EMISSION_SHAPE_POINT
Labels: bug,needs testing,topic:particles

### Godot version

v4.0.beta.custom_build [0abd60b95]

### System information

Windows 10, Vulkan

### Issue description

When the emission_shape of a ParticleProcessMaterial is different than 'Point' (EMISSION_SHAPE_POINT), setting scale_max to 0.0 (zero) will prevent the particles from being seen until the GPUParticles3D is restarted (toggling 'trail_enabled' will force a restart in editor), both in editor and ingame.
I've setup a scene to show it ingame but here's a vid showing it in the editor:
<video src="https://user-images.githubusercontent.com/115422160/212919021-757afaa6-cda6-4d97-a551-2b28f9bfae33.webm">


### Steps to reproduce

Add a GPUParticles3D node.
Add a QuadMesh to first pass.
Add a ParticleProcessMaterial, change the emission_shape to Sphere (or anything that isn't the default Point).
Change the scale_max to 0.0, change it back to 1.0, no more particles.

Alternatively, run the MRP.

### Minimal reproduction project

[particles bug.zip](https://github.com/godotengine/godot/files/10435611/particles.bug.zip)
Repository: godot
Issue: Inconsistent comparison of JSON numeric values
Labels: bug,topic:gdscript

### Godot version

3.5.2.rc

### System information

Arch Linux

### Issue description

JSON parses all numbers as real/floats. However there are still scenarios where this may confuse users:
```gdscript
func _ready():
	var json = "[1, 2]"
	var arr = JSON.parse(json).result

	if 1 in arr: # <---
		arr.erase(1)

	print(arr)
```
`if 1 in arr` evaluates to `true`, but further usage of that value in other scenarios will silently fail (`e.g. arr.erase(1) or arr.find(1)` because of the type mismatch (integer/float). Maybe this is doing an implicit conversion?

This seems to happen only on Godot 3; in Godot 4 this condition fails as expected.

### Steps to reproduce

1. Use supplied example code
2. Place a breakpoint at `if 1 in arr:`
3. Step execution. The condition evaluates to `true`, executing inner code

### Minimal reproduction project

N/A
Repository: godot
Issue: FileSystem Dock not updating after "Save Branch as Scene" in Remote Scene Tree Dock
Labels: bug,topic:editor,usability

### Godot version

Both 4.0 and 3.x

### System information

 6.0.14-1-MANJARO

### Issue description

"Saving Branch as Scene" only from Remote Tree Scene has this bug. not Local Tree Scene.
You can force update the FileSystem Dock by double tapping Alt-Tab and solve the bug.

### Steps to reproduce

1. create Node2D
2. create another node2D below.
3. save and run the Scene
4. Click `Remote` Tree Scene and `Save Branch as Scene`
5. Obverse that new saved scene file doesn't show up in the FileSystem Dock

### Minimal reproduction project

N/A
Repository: flutter
Issue: Add missing m3 max width/height constraints
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

These components currently don't correctly limit how wide they can be:
- [x] [Bottom sheets](https://m3.material.io/components/bottom-sheets/specs) should have a max width of 640dp
- [ ] [Dialogs](https://m3.material.io/components/dialogs/specs) should have a max width & height of 560dp
Repository: flutter
Issue: Tweak m3 snackbar enter/exit animation
Labels: f: material design,P2,team-design,triaged-design

Expected | Actual
--- | ---
<video src=https://user-images.githubusercontent.com/6655696/212926733-92ac6883-df38-4611-8ec1-13e1f769841e.mp4/> | <video src=https://user-images.githubusercontent.com/6655696/212927571-8a62bf1e-3b09-416e-ad66-95e958e07a6a.mov />

The spec looks like a smoother animation in, and a fade out.


cc @esouthren
Repository: vscode
Issue: [CustomTextEditor extensions] Editors of untitled files open twice when restarting.
Labels: bug,custom-editors

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version:  1.74.3
- OS Version: Windows 10

Description:
When a built Extension containing a custom editor is installed and a new untitled document is opened with a custom editor it will open twice when restarting Visual Studio Code. Once in the custom editor and once in a Texteditor.

I extended the custom-editor sample with an easy way to reproduce the issue in my fork.

Steps to Reproduce:

1. Clone https://github.com/Thomas-Grimmeisen/vscode-extension-samples 
2. Navigate to the custom-editors sample
3. Build the .vsix
4. Install the cat-customs-0.0.1.vsix
5. Execute the 'Create new Cat Scratch Document'
6. Add some scratches
7. Close Visual Studio Code
8. Open Visual Studio Code 

Now the file will be opened twice.

---

This could be related to https://github.com/microsoft/vscode/issues/150257 which has the same effect but since the steps to reproduce the issue are a bit different I decided to create this issue in case of different root cause.
Repository: node
Issue: Reconsider adding FFI to the core
Labels: feature request

### What is the problem this feature will solve?

Call foreign functions

### What is the feature you are proposing to solve the problem?

the API is provided directly by node, without the help of addons

### What alternatives have you considered?

FFI and FFI-NAPI addons have been chronically under-maintained. Both Deno and Bun already support FFI directly. Java has been testing the FFM API since JDK17. I know node's ffi feature was once rejected, but now is it possible to reconsider
Repository: go
Issue: x/net: frequent test timeouts on android-amd64-emu builder
Labels: NeedsInvestigation,mobile

```
#!watchflakes
post <- builder ~ `^android-.*` &&  pkg ~ `^golang\.org/x/net` && `Test killed with quit: ran too long`
```
Repository: go
Issue: x/net/ipv4: TestPacketConnReadWriteUnicastUDP failures with `i/o timeout`
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "golang.org/x/net/ipv4" && test == "TestPacketConnReadWriteUnicastUDP" && `i/o timeout`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/bdb07358d70afd81bf6ca45df0b402770b276ac3)):

    --- FAIL: TestPacketConnReadWriteUnicastUDP (0.10s)
        unicast_test.go:79: read udp 127.0.0.1:65493: raw-read udp4 127.0.0.1:65493: i/o timeout


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/net/ipv4: TestPacketConnReadWriteUnicastICMP failures with `destination unreachable`
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "golang.org/x/net/ipv4" && test == "TestPacketConnReadWriteUnicastICMP" && `got type=destination unreachable`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/bdb07358d70afd81bf6ca45df0b402770b276ac3)):

    --- FAIL: TestPacketConnReadWriteUnicastICMP (0.01s)
        unicast_test.go:175: got type=destination unreachable, code=3; want type=echo reply, code=0


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: vscode
Issue: Bug in background color rendering for Persian text in `monaco-diff-editor`
Labels: diff-editor

## VS Code Version: 1.74.3
### Issue Description

I have encountered a bug related to the `monaco-diff-editor` in VS Code.

Please refer to the screenshot attached below:
![image](https://user-images.githubusercontent.com/45296858/212946176-d5ab8e42-2512-4d6c-8ed6-a20056a0b668.png)

The issue is that the background color for inserted and removed text is not rendering correctly. As you can see in the screenshot above, there is coloring in the space where there are no changes. For a more detailed view, please see the following screenshot:
![image](https://user-images.githubusercontent.com/45296858/212946874-f1c8b8b7-22b4-4104-bbfe-a319302fc516.png)

I believe that the possible cause of this bug is related to the handling of RTL languages (or possibly the Persian language specifically).

### Steps to Reproduce

1. Write an English text, save and commit
2. Write an RTL text and save the file
3. Compare it with another text
4. Observe the rendering background of the RTL text in the diff editor

I would appreciate if someone could look into this and help me fix it. Thanks!
Repository: go
Issue: runtime: timeouts on netbsd-arm64-bsiegert builder
Labels: OS-NetBSD,NeedsInvestigation,compiler/runtime

```
#!watchflakes
post <- pkg == "runtime" && builder ~ `netbsd-arm.*-bsiegert` && (log ~ `SIGQUIT` || log ~ `test timed out` || `failed to start: context deadline exceeded` ||  `panic: finalizer started .* ago .*, but did not return`)
```

(attn @bsiegert @golang/netbsd; CC @golang/runtime)

Pulled out from #57636 and others.
Repository: pytorch
Issue: [Releng] Windows AMI needs to be pinned for release
Labels: oncall: releng,triaged

### 🐛 Describe the bug

Windows AMI  needs to be pinned for release. 

Research task mainly to find possible way of achieving pinning

### Versions

nightly, test

cc @ezyang @gchanan @zou3519
Repository: rust
Issue: Clipboard button should copy version for crate, not just the name
Labels: T-rustdoc,C-enhancement,E-mentor,E-medium

Take https://docs.rs/tokio/1.24.1/tokio/index.html as an example: clicking the clipboard will copy `tokio` to the clipboard, but ideally it would copy `tokio = "1.24.1"`, like https://docs.rs/crate/tokio/latest does. Rustdoc already has this information because it shows the crate version in the sidebar.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: go
Issue: proposal: archive/tar, archive/zip: add NewReaderOptions with directory traversal defenses
Labels: Proposal,Proposal-Hold

This is another attempt at hardening the `archive/tar` and `archive/zip` packages against file traversal attacks, fixing #25849.

Naive handling of archives containing filenames such as `../../../etc/passwd` leads to security vulnerabilities. (See #55356 for a bunch of reference CVEs.) In #55356, I proposed changing `archive/tar` and `archive/zip` to return an `ErrInsecurePath` error when encountering an unsafe filename. Unfortunately, we subsequently discovered that Docker images frequently include filenames with absolute paths, making this change infeasible.

I propose adding new safe-by-default functions to `archive/tar` and `archive/zip`.

```
package tar

type ReaderOptions struct {
	AllowAbsolutePaths          bool
	AllowRelativePathComponents bool
}

// NewReaderWithOptions creates a new reader reading from r.
//
// The Reader's Next method will return ErrInsecurePath and a valid
// *Header if the next file's name is:
//
//   - absolute and opts.AllowAbsolutePaths is not set;
//   - contains a ".." path component and opts.AllowRelativePathComponents is not set; or
//   - on Windows, a reserved file name such as "NUL".
func NewReaderWithOptions(r io.Reader, opts ReaderOptions) *Reader
```

```
package zip

type ReaderOptions struct {
	AllowAbsolutePaths          bool
	AllowRelativePathComponents bool
}

// NewReaderWithOptions returns a new Reader reading from r,
// which is assumed to have the given size in bytes.
//
// 
// NewReaderWithOptions will return ErrInsecurePath and a valid
// *Reader if the archive contains file names that are:
//
//   - absolute and opts.AllowAbsolutePaths is not set;
//   - contains a ".." path component and opts.AllowRelativePathComponents is not set;
//   - contain a backslash (\) character; or
//   - on Windows, a reserved file name such as "NUL".
func NewReaderWithOptions(r io.ReaderAt, size int64, opts ReaderOptions) (*Reader, error)
```

The `NewReaderWithOptions` functions will provide the same functionality as proposed in #55356, but in a new API to avoid breaking existing users. In addition, these functions provide an easy way for users who want to accept some forms of unsafe path to do so while still defending against unexpected cases: For example, permitting absolute filenames while rejecting ones containing unexpected backslash characters.

I further propose that we update the `NewReader` documentation to encourage all users to migrate to `NewReaderWithOptions`. Once all supported Go versions include `NewReaderWithOptions`, we can go further and deprecate `NewReader`. We might also consider changing `NewReader` to be safe by default at some point, although that decision is out of scope for this proposal.
Repository: storybook
Issue: [Proposal]: Improve the design of Storybook errors
Labels: feature request,ui

### Is your feature request related to a problem? Please describe

@ghengeveld pointed out that our redbox errors are fairly scary and don't include actionable feedback to help resolve the issue and proposed we move to a format similar to the error style in the Interactions addon panel:

![image](https://user-images.githubusercontent.com/1123119/212969092-f0b18437-b005-4f38-b610-29c36676bf84.png)

I think this is an excellent proposal so I mocked up what that could look like.

### Describe the solution you'd like

I propose we have an error system that looks something like this:

![known error](https://user-images.githubusercontent.com/1123119/212969459-1cf48f07-cfcc-42b1-9482-e63983dd1278.jpg)

The above is an example of a known error where:
1. We provide a short description of the error followed by details and instructions on what steps to take to resolve it.
2. We provide a formatted version of the error (if feasible) to improve readability in addition to some syntax highlighting.
3. We provide a link to related docs (if available) and an action to copy the error for sharing.
4. OS, Browser, viewport, and branch details - this is not necessary for a V1

If the error is something we don't have suggestions for, it would look like this:

![unformatted error](https://user-images.githubusercontent.com/1123119/212970764-45e58563-e11e-448a-8a86-f32ca504497d.jpg)

Here is what a totally unformatted error might look like:

![formatted error](https://user-images.githubusercontent.com/1123119/212970755-0e06f787-8b3a-4190-88e9-5624212235f3.jpg)

If you are interested in working on this, please send me a message on the Storybook Discord and I will provide Figma assets.
Repository: rust
Issue: Lint against `Iterator::map` receiving a callable that returns `()`
Labels: A-lints,A-diagnostics,T-compiler,D-papercut,D-newcomer-roadblock

### Code

```Rust
fn foo(items: &mut Vec<u8>){
    items.sort();
}

fn main() {
    let mut x: Vec<Vec<u8>> = vec![
        vec![0, 2, 1],
        vec![5, 4, 3],
    ];
    x.iter_mut().map(foo);
    println!("{x:?}");
}
```


### Current output

```Shell
Passes
```


### Desired output

```Shell
warning: `Iterator::map` call that discard the iterator's values
   |
LL | fn foo(items: &mut Vec<u8>) {
   |    --- this function returns `()`, which is likely not what you wanted
...
LL |     x.iter_mut().map(foo)
   |                  --- ^^^ called `Iterator::map` with callable that returns `()`
   |                  |
   |                  after this call to map, the resulting iterator is `impl Iterator<Item = ()>`, which means the only information carried by the iterator is the number of items
   |
   = note: `Iterator::map`, like many of the methods on `Iterator`, gets executed lazily, meaning that its effects won't be visible until it is iterated
help: you might have meant to use `Iterator::for_each`
   |
LL -     x.iter_mut().map(foo)
LL +     x.iter_mut().for_each(foo)
   |
```


### Rationale and extra context

Mapping to `()` is almost *always* a mistake. The `for_each` suggestion should only be emitted if it would make sense with `foo`, like if it modifies the argument or has side-effects like printing or logging (the later would be hard to check for).

### Other cases

_No response_

### Anything else?

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: storybook
Issue: [Proposal]: Improve the design of "story not found" error
Labels: feature request,ui

### Is your feature request related to a problem? Please describe

I was taking a look at improving [the design of Storybook errors](https://github.com/storybookjs/storybook/issues/20657) and tangentially looked at the "story not found" error seen here:

![story-not-found-og](https://user-images.githubusercontent.com/1123119/212971761-a6415d15-977e-425e-b290-559cb0a755a6.png)

@ghengeveld pointed out this error is a bit scary. To me, this seems to effectively be a Storybook 404 page so I approached an iteration on the design in a similar fashion to how I would approach a 404 page.

### Describe the solution you'd like

I propose we take the information shown in the above error and reformat it a bit to feel a bit more like a Storybook empty state.

![story not found](https://user-images.githubusercontent.com/1123119/212972536-c384c097-4dcc-454a-b553-6c3ee5db4787.png)

What do you think?

If you are interested in taking this on, please message me on Discord and I will provide you with design assets.
Repository: PowerToys
Issue: Relógio com segundos / Clock with seconds
Labels: Needs-Triage

### Description of the new feature / enhancement

Podem incluir Relógio com segundos / Can you create Clock with seconds

### Scenario when this would be used?

Podem incluir Relógio com segundos / Can you create Clock with seconds

### Supporting information

Podem incluir Relógio com segundos / Can you create Clock with seconds