sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Support for command URIs in JSON schema hover cards
Labels: feature-request,settings-editor,confirmation-pending

<!-- ⚠️⚠️ 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. -->

I am unsure if it is a feature or bug, but I wanted to implement some command URIs in my `package.json` configuration settings so that it would be easier for the user to open the docs in their browser or Visual Studio Code.

What I did is the following:

- In the `markdownDescription` description of a configuration property, I added the following text:
```markdown
Specify the list of projects to load in the Front Matter CMS. [Docs](https://frontmatter.codes/docs/settings/overview#frontmatter.projects) - [View in VS Code](command:simpleBrowser.show?%5B%22https://frontmatter.codes/docs/settings/overview%23frontmatter.projects%22%5D)
```
- When I test this out in the settings UI, it works as expected:

https://github.com/microsoft/vscode/assets/2900833/bbb205a9-93d6-4444-a9ec-8639dad851f7

- While testing it out in the `settings.json` file, I noticed the command URIs are not rendered:

![image](https://github.com/microsoft/vscode/assets/2900833/15fb7aa8-3d79-45f0-9357-ed47db461143)

- Same for rendering those links from a JSON schema:

![image](https://github.com/microsoft/vscode/assets/2900833/a9059cb4-0b3e-4023-b94b-90092e478a7c)

It would be handy to support command URIs set from within JSON schemas in those hover cards.
Repository: vscode
Issue: Breakpoint classes have no property for triggered breakpoints
Labels: feature-request,api,debug

<!-- ⚠️⚠️ 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. -->
When creating a new triggered breakpoint and handling `debug.onDidChangeBreakpoints` events, there's no breakpoint property that allows distinguishing between a unconditional breakpoint and a triggered breakpoint so that a language extension can perform any required actions. This could be solved by adding a `waitFor` ~string~ location property, similar to the existing properties for the other types of breakpoints.
Repository: godot
Issue: Engine.get_singleton_list() does not include autoload scripts defined in the project settings.
Labels: discussion,topic:core,documentation

### Tested versions

v4.2.2.stable.custom_build [0cfe9491e]

### System information

Windows 10

### Issue description

[Autoload Scripts are also called Singletons in the docs](https://docs.godotengine.org/en/stable/tutorials/scripting/singletons_autoload.html) but I do not see them in `Engine.get_singleton_list()` thus I cannot get them with `Engine.get_singleton()` when I probably should be able to.

I only see the inbuilt singletons when I print the singleton list:
```
["Performance", "TextServerManager", "PhysicsServer2DManager", "PhysicsServer3DManager", "NavigationMeshGenerator", "ProjectSettings", "IP", "Geometry2D", "Geometry3D", "ResourceLoader", "ResourceSaver", "OS", "Engine", "ClassDB", "Marshalls", "TranslationServer", "Input", "InputMap", "EngineDebugger", "Time", "GDExtensionManager", "ResourceUID", "WorkerThreadPool", "ThemeDB", "JavaClassWrapper", "JavaScriptBridge", "DisplayServer", "RenderingServer", "AudioServer", "PhysicsServer2D", "PhysicsServer3D", "NavigationServer2D", "NavigationServer3D", "XRServer", "CameraServer"]
```

### Steps to reproduce

Create some Autoload Scripts in the project settings and see if they show up in `Engine.get_singleton_list()`.

### Minimal reproduction project (MRP)

N/A
Repository: kubernetes
Issue: DRA: kubelet: support permanent and transient errors
Labels: priority/important-soon,sig/node,kind/feature,needs-triage

### What would you like to be added?

Some checks made by the kubelet and/or a DRA driver might determine that a problem is permanent. In that case it makes no sense to keep retrying, which is what the current code does.

We need:
- a way to indicate permanent errors in the gRPC interface
- support in the kubelet for marking the pod as permanently failed


### Why is this needed?

- surface permanent errors more obviously
- avoid wasting resources
Repository: flutter
Issue: [Android: In-App-Subscription] Get all plans from a Subscription and buy them.
Labels: platform-android,p: in_app_purchase,package,P2,team-android,triaged-android

### Steps to reproduce

As im implementing In App Subscription in my app with [Googles New subscription model](https://support.google.com/googleplay/android-developer/answer/12154973?hl=en) thats desiged like:
> Subscriptoin1
       >> Base plan1
       >> Base plan2  
       
I'm trying to extract these base plan details and buy them.

Is that supported by package [in_app_purchase](https://pub.dev/packages/in_app_purchase) or not?

I did not found any documentation about these implementation.

I already checked this [issue](https://github.com/flutter/flutter/issues/110909) but did not found exact answer.


### Expected results

Want to get base plan details from subscription as a `ProductDetails` object.

### Actual results

Getting `SubscriptionOfferDetailsWrapper` instead of `ProductDetails` 

### Code sample

I'm trying to get something like this:

<details open><summary>Code sample</summary>

```dart
     ProductDetailsResponse response = await _iap?.queryProductDetails({"<subscription_id>"});
     ProductDetails productDetails = response.productDetails.first;
        if (productDetails is GooglePlayProductDetails) {
              List<SubscriptionOfferDetailsWrapper>? offerWrapperList = productDetails.productDetails.subscriptionOfferDetails;
        }
     
     // How to get ProductDetails object from above subscription base plan?   
     ProductDetails productDetails =  ?   
        
     final PurchaseParam purchaseParam = PurchaseParam(productDetails: productDetails);
    _iap?.buyNonConsumable(purchaseParam: purchaseParam); 
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Flutter 3.19.6 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 54e66469a9 (9 weeks ago) • 2024-04-17 13:08:03 -0700
Engine • revision c4cd48e186
Tools • Dart 3.3.4 • DevTools 2.31.1
```

</details>
Repository: ant-design
Issue: Design Tokens Documentation
Labels: 📝 Documentation,Inactive,unconfirmed

### What problem does this feature solve?

On my team, we want to use Ant Design as our main design library. However, one of the most irritating issues that we are going through is how Design Tokens exactly work. In the documentation, it is clear the differences between the different types of tokens but there isn't anything about how the Map Token algorithm works or how to implement them (We know it is via ConfigProvider). 
So this request is to improve the documentation on the Design Tokens so new users can understand better the functioning of the tokens. 


### What does the proposed API look like?

The proposal we give is to propose examples of usage of the Map Token using Seed Tokens or Alias Tokens using Map Tokens. 
Also explain what's the meaning of using Map Tokens with "theme.algorithm", we aren't very clear with that either.

Thank you very much for your time.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: ant-design
Issue: FormItem的shouldUpdate方法能否将触发的字段名给暴露出来？
Labels: 💡 Feature Request,Inactive

### What problem does this feature solve?

在大数据可编辑表格表单下，总表单数量可能会来到几千，大部分字段间都有shouldUpdate来做交互依赖，对应的每次表单变动时，shouldUpdate都会调用几千次，如果能将触发shouldUpdate的字段暴露出来，就能够以更快的方法去处理shouldUpdate逻辑，不用自己再去从全量数据中比较是不是该字段的依赖变动了。



**为何我不用dependencies?**

手动setFields不会触发对应添加了dependenceies字段的更新，不知道这个bug v5版本修复没，且shouldUpdate能够适应更多的场景

### What does the proposed API look like?

shouldUpdate = (prevValues, currValues, triggerFieldName) => {}

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Input does not change its style when closing the tab
Labels: topic:editor,needs testing

### Tested versions

- Reproducible in Godot v4.3 beta1 and Godot v4.2.2 stable.

### System information

Godot v4.3.beta1 - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1050 Ti (NVIDIA; 31.0.15.4633) - Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 Threads)

### Issue description

When closing a property tab inside the inspector the values being changed do not change their style. For example: when you click on layout.transform.x the input goes from `x [value] px` to `[value]`. When you finish editing the value, it goes back to `x [value] px`. If you close any of the parent tabs (layout or transform) before finishing the edit, the input will lose focus but will stay in the input state (`[value]`). However if you change the tab from Inspector to something else the value both lose focus and go into the normal state (`x [value] px`).

### Steps to reproduce

1. Create a new project or use an existing one.
2. Highlight a node in the tree.
3. Open any of the tabs that contain a stylized value (like the coordinates, `[something] [value] [unit]`).
4. Start editing the value.
5. Close the parent tab.
6. Open it back.

After opening back the tab you will see the value stay in the input state.

### Minimal reproduction project (MRP)

N/A.
Repository: storybook
Issue: [Bug]: The storybook 7.6.* version depends on the highly vulnerable ip package
Labels: bug,security

### Describe the bug

 I am encountering a high vulnerability issue flagged by npm audit related to the ip package. This issue is present in the storybook core-server dependency. I noticed that this vulnerability has been addressed in the latest release of Storybook (version 8.1.9). and it got fixed in https://github.com/storybookjs/storybook/issues/26014 
 
can we reroll the path to 7.6.* which will be helpful for users who are on 7.6.*

### Reproduction link

https://github.com/storybookjs/storybook

### Reproduction steps

![Screenshot 2024-06-17 at 10 28 38 AM](https://github.com/storybookjs/storybook/assets/145736430/a81e96e8-d30d-47f3-9655-ac24af2fbe32)


### System

```bash
npx storybook@latest info

Storybook Environment Info:

  System:
    OS: macOS 14.5
    CPU: (10) arm64 Apple M1 Max
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.2 - /opt/homebrew/opt/node@20/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 10.5.0 - /opt/homebrew/opt/node@20/bin/npm <----- active
  Browsers:
    Chrome: 125.0.6422.142
    Edge: 126.0.2592.56
    Safari: 17.5
  npmPackages:
    @storybook/addon-a11y: 7.6.17 => 7.6.17
    @storybook/addon-actions: 7.6.17 => 7.6.17
    @storybook/addon-controls: 7.6.17 => 7.6.17
    @storybook/addon-designs: 7.0.9 => 7.0.9
    @storybook/addon-docs: 7.6.17 => 7.6.17
    @storybook/addon-storysource: 7.6.17 => 7.6.17
    @storybook/addon-toolbars: 7.6.17 => 7.6.17
    @storybook/addon-viewport: 7.6.17 => 7.6.17
    @storybook/addons: 7.6.17 => 7.6.17
    @storybook/api: 7.6.17 => 7.6.17
    @storybook/cli: 7.6.17 => 7.6.17
    @storybook/client-api: 7.6.17 => 7.6.17
    @storybook/components: 7.6.17 => 7.6.17
    @storybook/core-client: 7.6.17 => 7.6.17
    @storybook/core-events: 7.6.17 => 7.6.17
    @storybook/core-server: 7.6.17 => 7.6.17
    @storybook/html: 7.6.17 => 7.6.17
    @storybook/manager-api: 7.6.17 => 7.6.17
    @storybook/preview-api: 7.6.17 => 7.6.17
    @storybook/source-loader: 7.6.17 => 7.6.17
    @storybook/theming: 7.6.17 => 7.6.17
    @storybook/web-components: 7.6.17 => 7.6.17
    @storybook/web-components-webpack5: 7.6.17 => 7.6.17
    storybook: 7.6.17 => 7.6.17
```


### Additional context

_No response_
Repository: pytorch
Issue: Windows builds with VS2022
Labels: module: build,module: windows,triaged

Pytorch core is build with VS2019 while domains are build with VS2022.  We want to try to switch core to MS VS2022 build and document possible issues and problems.  

~~Test can be added here: https://github.com/pytorch/pytorch/blob/main/.ci/pytorch/check_binary.sh (need to make this works on Windows as the script is only invoked for Linux atm https://github.com/pytorch/test-infra/blob/main/.github/scripts/validate_binaries.sh#L90-L94)~~

A follow-up task is to remove VS2019 afterwards:

* PyTorch https://github.com/pytorch/pytorch/blob/main/.ci/pytorch/windows/internal/vc_install_helper.bat#L1
* Windows AMI https://github.com/pytorch/test-infra/blob/main/aws/ami/windows/windows.pkr.hcl#L71-L87



cc @malfet @seemethere @peterjc123 @mszhanyi @skyline75489 @nbcsm @vladimir-aubrecht @iremyux @Blackhex @cristianPanaite
Repository: rust
Issue: Lint against using `libc::c_*` types in std if they're also avaliable in `core::ffi`
Labels: C-enhancement,A-lints,T-compiler,T-libs

We should prefer to consistently use `core::ffi::{c_char, c_void, ...}` over their libc equivalents because `core::ffi` should be the source of truth for std and libc may not always be used on all targets (e.g. windows or `linux-unknown-unknown`).

So it would be good to lint on this if it's possible.
Repository: tauri
Issue: [feat]: Reduce boilerplate for command definitions in Tauri v2
Labels: type: feature request,priority: 2 medium

### Describe the problem

I am currently updating a large project to Tauri v2, which involves around 100 commands. While doing so, I have encountered a significant amount of boilerplate code that I need to maintain across multiple files. Specifically, for each command, I need to:

- Define the command in the plugin's init functiopatn:
```rs
.invoke_handler(tauri::generate_handler![auth_get_default_user, auth_set_default_user])
```
- Include the command in `build.rs`:
```rust
.plugin(
    "auth",
        tauri_build::InlinedPlugin::new().commands(&["auth_get_default_user", "auth_set_default_user"]),
)
```
- Allow for usage of my commands in `capabilities.json`: 
```yml
"auth:allow-auth-get-default-user",
"auth:allow-auth-set-default-user"
```
This process is not only repetitive but also makes it challenging to maintain and scale the project. 

### Describe the solution you'd like

Anything that reduces boilerplate, for example:
- New macro that works like `tauri::generate_handler!`, but also generates all permissions
- Allowing for all plugin's commands (for example `plugin:allow-all` or `plugin:allow-*`)

### Alternatives considered

_No response_

### Additional context

I initially discussed this problem on [Discord](https://discord.com/channels/616186924390023171/1251869086980247642)

### Current "sub" problems:
- [ ] There is no `builder.plugins`
- [ ] `InlinedPlugin` requires `&'static [&'static str]` which requires using a lot of `Box::leak`
Repository: rust
Issue: `std::process::exit` is not thread-safe in combination with C code calling `exit`
Labels: I-unsound,C-bug,T-libs

The current implementation of `std::process::exit` is unsound on Linux and possibly related platforms where it defers to libc's `exit()` function. `exit()` [is documented to be](https://man7.org/linux/man-pages/man3/exit.3.html#ATTRIBUTES) not thread-safe, and hence `std::process::exit` is not thread-safe either, despite being a non-`unsafe` function.

To show that this isn't just a theoretical problem, here is a minimal example that segfaults on my machine (Ubuntu with glibc 2.37):

```rust
use std::thread;

fn main() {
    for _ in 0..32 {
        unsafe { libc::atexit(exit_handler) };
    }
    for _ in 0..2 {
        thread::spawn(|| std::process::exit(0));
    }
}

extern "C" fn exit_handler() {
    thread::sleep_ms(1000);
}
```

The example contains `unsafe` code, but only to install exit handlers. AFAICT nothing about the `libc::atexit` call is unsafe. The UB is introduced by calling `std::process::exit` concurrently afterwards.

If you are curious, https://github.com/MaterializeInc/database-issues/issues/6528 lays out what causes the segfault (it's a use-after-free). That's not terribly relevant though, given that glibc has no obligation to ensure `exit()` is thread safe when it's clearly documented not to be. Instead, Rust should either mark `std::process::exit` as `unsafe` (which is something it could do for the 2024 edition), or introduce locking to ensure only a single thread gets to call `exit()` at a time.


----

### Current status

Mitigation on our end (only covers pure Rust programs): #126606

The current status is that the specification language stems from a time when C did not specify multithreading and the intent was to forbid reentrancy. External discussion indicates that there's intent to fix it both in libc implementations and the specs:

- glibc: https://sourceware.org/bugzilla/show_bug.cgi?id=31997
  - patch: https://sourceware.org/pipermail/libc-alpha/2024-July/158579.html
- POSIX: https://austingroupbugs.net/view.php?id=1845
   - also [a comment](https://austingroupbugs.net/view.php?id=1845#c6853) mentioning taking it to the C committee.
- libc-coord (including musl author): https://www.openwall.com/lists/libc-coord/2024/07/24/4
- musl patch: https://git.musl-libc.org/cgit/musl/commit/?id=8cca79a72cccbdb54726125d690d7d0095fc2409
- freebsd patch: https://reviews.freebsd.org/D46108
- bionic: https://android.googlesource.com/platform/bionic.git/+/089f4d17265480a5ad9311bcbd8890bc9f361801%5E%21/
Repository: flutter
Issue: Add way to change DraggableScrollableSheet snap animation curve
Labels: c: new feature,framework,f: scrolling,c: proposal,P3,team-framework,triaged-framework

### Use case

Hello! 

There's currently a way to control DraggableScrollableSheet's snap animation duration, but no way to set different animation curve.

In search of information ran into similar issue, https://github.com/flutter/flutter/issues/107033, but although it was accepted, only snapAnimationDuration was added.

### Proposal

Would be really nice to have an ability to control DraggableScrollableSheet's snaps animation curve, as default one doesn't suit might needs.
Repository: kubernetes
Issue: [Flaking test] TestPolicyAdmission/.v1.bindings/create
Labels: sig/api-machinery,kind/flake,triage/accepted

### Which jobs are flaking?

pull-kubernetes-integration

### Which tests are flaking?

TestPolicyAdmission [link](https://github.com/kubernetes/kubernetes/blob/efef32652af0af08a0b9c9bc547a4dce4a95f9f5/test/integration/apiserver/cel/admission_policy_test.go#L411)

### Since when has it been flaking?

I don't know:
![image](https://github.com/kubernetes/kubernetes/assets/10359181/ce432cd1-ddae-46a3-9114-ee2af4b35afc)


### Testgrid link

https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-integration&include-filter-by-regex=cel.cel

### Reason for failure (if possible)

```
    admission_test_util.go:354: version: v1alpha1, phase:validation, converted:true error: no request received
    admission_test_util.go:354: version: v1beta1, phase:validation, converted:true error: no request received
    admission_test_util.go:354: version: v1alpha1, phase:validation, converted:false error: no request received
    admission_test_util.go:354: version: v1beta1, phase:validation, converted:false error: no request received
        --- FAIL: TestPolicyAdmission/.v1.bindings/create (0.02s)
=== FAIL: test/integration/apiserver/cel TestPolicyAdmission/.v1.bindings (0.02s)
    --- FAIL: TestPolicyAdmission/.v1.bindings (0.02s)
=== FAIL: test/integration/apiserver/cel TestPolicyAdmission/.v1.configmaps/create (0.00s)
```

### Anything else we need to know?

_No response_

### Relevant SIG(s)

/sig api-machinery
Repository: deno
Issue: ext/node: executionAsyncResource is not a function
Labels: bug,node compat

Encountered a new error when running dd-trace example with https://github.com/denoland/deno/pull/24229
```
error: Uncaught TypeError: executionAsyncResource is not a function
    at AsyncResourceStorage._executionAsyncResource (file:///Users/sr/c/satyarohith/deno_dd_trace_example/node_modules/.deno/dd-trace@5.17.0/node_modules/dd-trace/packages/datadog-core/src/storage/async_resource.js:104:12)
    at AsyncResourceStorage.getStore (file:///Users/sr/c/satyarohith/deno_dd_trace_example/node_modules/.deno/dd-trace@5.17.0/node_modules/dd-trace/packages/datadog-core/src/storage/async_resource.js:45:27)
    at withNoop (file:///Users/sr/c/satyarohith/deno_dd_trace_example/node_modules/.deno/dd-trace@5.17.0/node_modules/dd-trace/packages/dd-trace/src/log/writer.js:17:25)
    at error (file:///Users/sr/c/satyarohith/deno_dd_trace_example/node_modules/.deno/dd-trace@5.17.0/node_modules/dd-trace/packages/dd-trace/src/log/writer.js:65:3)
    at Channel.publish (node:diagnostics_channel:140:9)
    at Object.error (file:///Users/sr/c/satyarohith/deno_dd_trace_example/node_modules/.deno/dd-trace@5.17.0/node_modules/dd-trace/packages/dd-trace/src/log/index.js:67:20)
    at Tracer.init (file:///Users/sr/c/satyarohith/deno_dd_trace_example/node_modules/.deno/dd-trace@5.17.0/node_modules/dd-trace/packages/dd-trace/src/proxy.js:153:11)
    at file:///Users/sr/c/satyarohith/deno_dd_trace_example/main.mjs:3:9
```

Reproducible:
```js
import { open } from 'node:fs';
import { executionAsyncId, executionAsyncResource } from 'node:async_hooks';

console.log(executionAsyncId(), executionAsyncResource());  // 1 {}
open(new URL(import.meta.url), 'r', (err, fd) => {
  console.log(executionAsyncId(), executionAsyncResource());  // 7 FSReqWrap
});
```
Current output:
```
➜  ~ node a.mjs
0 {}
11 FSReqCallback { oncomplete: [Function (anonymous)] }
➜  ~ denod run -A a.mjs
error: Uncaught SyntaxError: The requested module 'node:async_hooks' does not provide an export named 'executionAsyncResource'
import { executionAsyncId, executionAsyncResource } from 'node:async_hooks';
                           ^
    at <anonymous> (file:///Users/sr/a.mjs:2:28)
```

Ref: #23744
Repository: rust
Issue: compiletest: `./x test <test-name>.stderr` (or existing non-`.rs` file) should warn or error
Labels: E-hard,T-bootstrap,C-bug,A-compiletest

Noticed by @WaffleLapkin, if you write

```
./x test tests/ui/parser/bad-let-else-statement.stderr
```

then compiletest will silently pass but run 0 tests, because `bad-let-else-statement.stderr` is a tracked stderr file associated with the actual `.rs` ui test but not a test itself. This might be surprising or give a false sense of security to the person who's running the test suite thinking that the test passed, whereas it actually didn't even run.

- If the path doesn't exist, compiletest will report the non-existent test error.
- However, if the path does exist, but it's not an actual test (whatever consitutes a "test" file under the relevant test suite), compiletest currently seems to silently ignore and pass.

We should probably warn or error if the path exists (and has an extension) but is not a valid test file.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->