sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Support filtering in builtin notebook variable view
Labels: feature-request,notebook-variables

<!-- ⚠️⚠️ 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. -->

The builtin Variable View for notebook now lists all "variables" from the Jupyter kernel right now, most of which are contributed by Jupyter extension or the Kernel

![image](https://github.com/microsoft/vscode/assets/876920/9f058e5a-d04f-4d71-baf4-e66937e22367)

It would be great if we can support filtering the variables:

* Support "My Variables Only"
* Support filtering based on types (Module, Class, etc)
* Exclude the builtin function/modules contributed by Jupyter extension (e.g., `chat`)
Repository: flutter
Issue: [ios][platform_view]Optimize the double for loop in platform view overlay computation
Labels: platform-ios,a: platform-views,P2,team-ios,triaged-ios

There's a double loop in the overlay computation logic which can be expensive: 

https://github.com/flutter/engine/blob/5a12de1beab71c44692e7b12e7fdf3f5f3702f06/shell/platform/darwin/ios/framework/Source/FlutterPlatformViews.mm#L698-L705

For example, some of the intermediate rect structs can be cashed for re-use. 

More context: https://github.com/flutter/engine/pull/51687#issuecomment-2021803125

CC @flar 

Creating a separate issue since it's the existing behavior. We should keep the original PR atomic, and have a separate PR for this, so that we can measure the improvement.
Repository: ui
Issue: [bug]: Blocks Dashboard Link re-render Home Page
Labels: bug

### Describe the bug

If you go to Blocks Page, and scroll down to Dashboard 2
Click on the Acme Inc (shown in picture), it will re-render the Home Page again
![image](https://github.com/shadcn-ui/ui/assets/50576944/f9c594e7-95ce-4df4-b779-a29a36271c81)

You can follow the process as many times as you want, and it will keep rendering the Homepage inside the Block, and it will look something like: 

![image](https://github.com/shadcn-ui/ui/assets/50576944/1ea34809-82ca-4712-8cd8-baa1f4ab4757)


### Affected component/components

Blocks

### How to reproduce

Mentioned above 😄 

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
I don't think it's relevant, but still:

OS: macOS 14.2.1 23C71
Host: Mac14,3
CPU: Apple M2
GPU: Apple M2
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ant-design
Issue: Antd theme is not working with nextjs module federation and nextjs 14.
Labels: Inactive

### Reproduction link

[Demo link](https://antd-theme-root-app.vercel.app/)
[Root app repository](https://github.com/prakashmallow/antd-theme-root-app)
[Child app 1 respository](https://github.com/prakashmallow/antd-theme-child-app-1)
[Child app 2 respository](https://github.com/prakashmallow/antd-theme-child-app-2)

### Steps to reproduce

1. Clone the above three Next.js app repositories locally.
2. Install npm packages on all apps.
3. First, run both child apps, ensuring they are running successfully before starting the root app.
4. After running the root app open the URL of the root app in a web browser.
5. You will notice that the primary colour of the buttons is applied from the theme configuration on the Home page (root app component). However, when navigating to the Services or About Us pages, the buttons display with the default primary colour of Antd instead of the configured theme's primary colour.

### What is expected?

Next.js v14x and @module-federation/nextjs-mf v8.x. With this configuration, Antd theme changes should work correctly in both root and child Next.js apps.

### What is actually happening?

When using Next.js v14.x along with @module-federation/nextjs-mf v8.x, I encountered an issue with the Ant Design (Antd) theme configuration. In this setup, the root Next.js app successfully provides the theme changes to child Next.js apps. However, while the root Next.js app consumes the theme changes, the child Next.js app only displays the default theme without incorporating the Antd theme changes.

As a workaround, I downgraded to Next.js version 13.4.7 and @module-federation/nextjs-mf v7.x. With this configuration, the Antd theme changes are functioning correctly on both the root and child Next.js apps

| Environment | Info |
| --- | --- |
| antd | 5.15.4 |
| nextjs | 14.1.4 |
| React | 18 |
| @module-federation/nextjs-mf | 8.2.0 |
| System | Mac |
| Browser | Chrome latest version |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Stop optimizing under the assumption of default denormal behavior
Labels: T-compiler,T-libs,A-floating-point,C-discussion

On some platforms (QNX on Arm comes to mind, but there are probably others) flush-to-zero and denormals-are-zero are turned on by default and cannot be disabled.  Furthermore, PipeWire turns on FTZ and DAZ because it is the only way to get realtime behavior (otherwise, denormals are handled by microcode assists or traps that are far too slow).

Right now, this means that one cannot use Rust for realtime code that performs floating point operations, which I think is silly.  Instead, I think Rust should treat compile-time operations on floating-point numbers as partial functions.  When a denormal or NaN is hit, Rust should defer the operation until runtime, when the actual behavior is known.
Repository: godot
Issue: Scenes preview icon (not thumbnail image) may be wrongly set when the root node has no script
Labels: bug,topic:editor

### Tested versions

v4.3.dev.custom_build [7d151c838]

### System information

linux

### Issue description

- may be related to (didn't investigate) https://github.com/godotengine/godot/pull/77932

| the scene (root has no script). The first child has a custom icon | the scene thumbnail (notice the icon) |
|-|-|
|![image](https://github.com/godotengine/godot/assets/71937306/b72aeafe-5bbb-4655-9d31-5882323d6756)|![image](https://github.com/godotengine/godot/assets/71937306/7121e82f-f400-43fc-8867-469157c05664)|

- if a child of a scriptless root has a custom icon, the scene thumbnail will show the child's icon as a type.
- adding an empty script to the root solves the problem.


### Steps to reproduce

- create scene with no script on the root
- add a child node with any custom icon
- save it and look at the file icon

### Minimal reproduction project (MRP)

any
Repository: stable-diffusion-webui
Issue: [Feature Request]: 'Put Stable Diffusion checkpoints here.txt' change file name
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Change the name of 'Put Stable Diffusion checkpoints here.txt' to 'Put Stable Diffusion checkpoints here, unless you specify the data-dir commandline argument.txt'

### Proposed workflow

1. Add "--data-dir data" to COMMANDLINE_ARGS in webui-user.sh
2. Put a new checkpoint in the same directory as 'Put Stable Diffusion checkpoints here, unless you specify the data-dir commandline argument.txt'
3. Start webui.sh
4. See no change in the checkpoint dropdown.
5. Move the checkpoint to the data/models/Stable-diffusion directory
6. Click the "checkpoint: refresh" button
7. Find your new checkpoint in the dropdown list


### Additional information

Without wich you can spend a day searching why automatic1111 is not picking up any of the new checkpoints you spent hours waiting to download already.
Alternatives: put this hint inside the existing file, add a README to that directory ...
Repository: flutter
Issue: ColorFiltered is difference between Flutter v3.7.2 and v3.19.4
Labels: engine,has reproducible steps,P3,team-engine,triaged-engine,found in release: 3.19,found in release: 3.21

Recently，i upgrade Flutter to 3.19.4 from 3.7.2 , 

Framework • revision 32fb2f948e (1 year, 2 months ago) • 2023-02-08 07:30:10 -0800
Engine • revision f40b73f8a4
Tools • Dart 2.19.2 • DevTools 2.20.1

Flutter 3.19.4 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 68bfaea224 (6 days ago) • 2024-03-20 15:36:31 -0700
Engine • revision a5c24f538d
Tools • Dart 3.3.2 • DevTools 2.31.1


i found the problem about ColorFiltered： 

the test code：


```
class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key});

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Container(
        color: Colors.green,
        child: const TestColorFilteredPage(),
      ),
    );
  }
}

class TestColorFilteredPage extends StatelessWidget {
  const TestColorFilteredPage({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return ColorFiltered(
      colorFilter: const ColorFilter.mode(Colors.yellow, BlendMode.srcOut),
      child: Stack(
        children: [
          Positioned.fill(
              child: Container(
            color: Colors.transparent,
          )),
          Positioned(
            top: 100,
            left: 100,
            child: Container(
              color: Colors.black,
              height: 100,
              width: 100,
            ),
          )
        ],
      ),
    );
  }
}
```

| v3.7.2 | v3.19.4 |
| --------------- | --------------- |
<img width="400" src="https://github.com/flutter/flutter/assets/22768714/65b57dff-f680-4e17-a097-ea2d68d5b0f3"> | <img width="400" src="https://github.com/flutter/flutter/assets/22768714/a60180e7-a7ad-4c01-8765-3d3a504a0e24">



How can i get the same result in v3.19.4 like v3.7.2?
Repository: godot
Issue: Proximity Fade broken in Compatibility (OpenGL)
Labels: bug,topic:rendering,topic:3d

### Tested versions

- v4.3.dev5.official [89f70e98d]

### System information

Godot v4.3.dev5 - macOS 13.6.0 - GLES3 (Compatibility) - Apple M1 Pro - Apple M1 Pro (8 Threads)

### Issue description

The Proximity Fade in StandardMaterial3D does not work with Compatibility renderer. The produced code assumes Vulkan Z range 0.0 to 1.0 instead of OpenGL -1.0 to 1.0. The fix is to remap the depth_tex as follows:

```glsl
// Proximity Fade: Enabled
	float depth_tex = textureLod(depth_texture, SCREEN_UV, 0.0).r;
        depth_tex = depth_tex * 2.0 - 1.0; // <-- For OpenGL
	vec4 world_pos = INV_PROJECTION_MATRIX * vec4(SCREEN_UV * 2.0 - 1.0, depth_tex, 1.0);
	world_pos.xyz /= world_pos.w;
	ALPHA *= clamp(1.0 - smoothstep(world_pos.z + proximity_fade_distance, world_pos.z, VERTEX.z), 0.0, 1.0);
```

### Steps to reproduce

- Use Compatibility renderer.
- Add a cube on a plane, or two intersecting cubes, etc. 
- Apply a new standardMaterial3D and enable Proximity Fade.

### Minimal reproduction project (MRP)

N/A
Repository: ollama
Issue: Pull a model on start or without requiring serve
Labels: feature request,docker

### What are you trying to do?

To enhance the user experience when deploying Ollama with models in a containerized environment, it would be beneficial to enable pre-embedding a model into the image through a custom Dockerfile or pulling a model upon starting Ollama by specifying an argument or environment variable. This eliminates the need for an API request after the container starts.

### How should we solve this?

- `ollama serve --pull [models]`
- `OLLAMA_PULL=model1,model2 ollama serve`
- `ollama pull` without `ollama serve` (a bit harder to implement option, but improves the ability to create custom images with custom models beyond pulling)

### What is the impact of not solving this?

This is a significant improvement for hosting Ollama. Without it, deploying Ollama, especially in a production environment, would be more challenging.

### Anything else?

Related:
- https://github.com/ollama/ollama/issues/1322
- https://github.com/ollama/ollama/issues/358#issuecomment-2022394098
Repository: rust
Issue: Suboptimal register allocation across loops
Labels: A-LLVM,I-slow,A-codegen,T-compiler,C-bug,I-heavy,C-optimization

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

This is inspired from https://github.com/rust-lang/rustc-hash/pull/34.

When several loops (or I guess conditionals) modify a common 1-word variable one after the other, this variable gets written too much to memory.

A MRE is

```rust
#[no_mangle]
pub fn foo(x: &mut u64, y: u64, z: &[u64]) {
    *x *= y;
    for &z in z {
        *x *= z;
    }
}
```

which is codegened (on nightly) to 

```asm
foo:
        imul    rsi, qword ptr [rdi]
        mov     qword ptr [rdi], rsi
        test    rcx, rcx
        je      .LBB2_4
        shl     rcx, 3
        xor     eax, eax
.LBB2_2:
        imul    rsi, qword ptr [rdx + rax]
        add     rax, 8
        cmp     rcx, rax
        jne     .LBB2_2
        mov     qword ptr [rdi], rsi
.LBB2_4:
        ret
```

where both `mov     qword ptr [rdi], rsi` could be replaced by a single one right before the ret.

On the other hand, this code forces the `x` to be kept in a register.

```rust
#[no_mangle]
pub fn bar(x: &mut u64, y: u64, z: &[u64]) {
    let mut xx = *x;
    xx *= y;
    for &z in z {
        xx *= z;
    }
    *x = xx
}
```
Repository: angular
Issue: Unique ID generation for component instances
Labels: feature,area: core,core: DOM rendering

### Which @angular/* package(s) are relevant/related to the feature request?

core, elements

### Description

In Angular, the reusability of components is a core feature but leads to potential conflicts with HTML standards regarding the uniqueness of id attributes within a document. It particularly impacts accessibility (with aria-labelledby attributes expecting unique id values) and form handling (where label elements use the for attribute to reference input elements by id). 

### Proposed solution

Introduce a new field in the component decorator to enable automatic ID uniqueness on a per-instance basis. When this boolean field is set to true, would instruct Angular to automatically prefix id, for, aria-labelledby, and any other attributes that reference IDs, with a unique component instance identifier, ensuring that every instance of a component has uniquely identifiable elements without additional effort from developers.

### Alternatives considered

1. Currently, developers can manually manage unique IDs by incrementing an identifier for each component instance. This approach is simple but prone to human error.
```ts
@Component({
  selector: 'app-tracked',
  standalone: true,
  template: `
    <p [id]="instance + 'tracked'">Im tracked.</p>
  `,
})
export class TrackedComponent {
  private static instance = 0;
  instance = TrackedComponent.instance++;
}
```
2. Another workaround involves creating custom directives (e.g., [uid] and [ufor]) that communicate through a service to ensure ID uniqueness within the same component instance. Due to the lack of direct references to component instances, this method requires implementing a custom mechanism to track and associate directive instances with their respective component instances. This adds a layer of complexity, as developers must ensure accurate tracking and synchronization across component lifecycles, making it a less than ideal solution.
Repository: node
Issue: node-addon-api addons broken by default on Node.js 20.12+
Labels: c++,node-api

### Version

v20.12.0

### Platform

Linux 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

### Subsystem

node-api

### What steps will reproduce the bug?

`cd /tmp && nvm install 20.12.0 && npm i --build-from-source kerberos` (or any other node-addon-api addon that uses `ObjectWrap` or similar APIs)

### How often does it reproduce? Is there a required condition?

Consistently.

### What is the expected behavior? Why is that the expected behavior?

Addon builds like it did prior to 0ac070ccb79f779390bb9944f4b802c6fc4c42aa.

### What do you see instead?

```
npm ERR! In file included from ../node_modules/node-addon-api/napi.h:3189,
npm ERR!                  from ../src/kerberos.h:11,
npm ERR!                  from ../src/kerberos.cc:1:
npm ERR! ../node_modules/node-addon-api/napi-inl.h: In instantiation of ‘Napi::ObjectWrap<T>::ObjectWrap(const Napi::CallbackInfo&) [with T = node_kerberos::KerberosClient]’:
npm ERR! ../src/kerberos.cc:64:22:   required from here
npm ERR! ../node_modules/node-addon-api/napi-inl.h:4414:21: error: invalid conversion from ‘void (*)(napi_env, void*, void*)’ {aka ‘void (*)(napi_env__*, void*, void*)’} to ‘node_api_nogc_finalize’ {aka ‘void (*)(const napi_env__*, void*, void*)’} [-fpermissive]
npm ERR!  4414 |   status = napi_wrap(env, wrapper, instance, FinalizeCallback, nullptr, &ref);
npm ERR!       |            ~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR!       |                     |
npm ERR!       |                     void (*)(napi_env, void*, void*) {aka void (*)(napi_env__*, void*, void*)}
npm ERR! In file included from /home/addaleax/.cache/node-gyp/20.12.0/include/node/node_api.h:12,
npm ERR!                  from ../node_modules/node-addon-api/napi.h:13,
```

### Additional information

This was introduced in 0ac070ccb79f779390bb9944f4b802c6fc4c42aa / https://github.com/nodejs/node/pull/50060. From the PR description, this _seems_ like intentional breakage, so it may need a solution in node-addon-api, not here. If it was intentional breakage, calling this out more explicitly somewhere in the release notes would have been helpful imo. @gabrielschulhof
Repository: storybook
Issue: While hitting tab key from the "skip to sidebar" button the keyboard focus is landing on the entire default page.
Labels: bug,needs triage

### Describe the bug

Environment (OS, Application, Versions): 
OS: Windows 11
OS version: 23H2 (OS Build 22631.3296)
Edge Version: 122.0.2365.80 (Official build) (64-bit)

### To Reproduce

1. Open the URL " [Overview - Docs ⋅ Storybook (windows.net)](https://nam06.safelinks.protection.outlook.com/?url=https:%2f%2fvivacommonstorybooktest.blob.core.windows.net%2f%24web%2findex.html?path%3D%2fdocs%2foverview--docs&data=05%7c02%7cv-subaku%40microsoft.com%7cd6da722d9e2e4ff05a3108dbf64b2d01%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c638374574975455585%7cUnknown%7cTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7c3000%7c%7c%7c&sdata=8I%2BzczSVmrIV8p%2B5PqlBwMXECqn%2BaeHPTKdF5UpbtDc%3D&reserved=0)".
2. Navigate to the "Task branding" in the left pane and expand it.
3. Navigate to the "default" and invoke it.
4. Navigate to the "skip to sidebar" and hit tab key.
5. Observe the issue.

[900f66b1-8c70-4396-869a-4e4358e1b948.webm](https://github.com/storybookjs/storybook/assets/93735775/391b08c0-9cd4-4ba7-a003-03b2775ae058)


### System

```bash
Actual Results: 

While hitting tab key from the "skip to sidebar" button the keyboard focus is falling on the entire default page.

Expected Results: 

While hitting tab key from the "skip to sidebar" button the Keyboard focus should land on the next interactive element i.e. controls.
```


### Additional context

_No response_
Repository: PowerToys
Issue: Fanzy Zones resizes Windows Calculator to maximised when it's added to the excluded apps list
Labels: Issue-Bug,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.76.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

It took me a long time to work out Fancy Zones was causing this bug.  Whenever I open Windows Calculator it opens fully maximised inside one of my fancy zone layouts, way too big.  I resize the app but it always opens like this, really annoying.  Years ago I added calculatorapp.exe (Formally calc.exe) to the Fancy Zones excluded apps section because it was annoying that it wanted to snap my little calculator into a fullsize fancy zone.  But by adding it to the excluded list it creates this bug where it makes it fill the size of the entire screen whenever I open it.  Once I have deleted it from excluded apps this behavior stopped and calc opens in a normal size.

### ✔️ Expected Behavior

Calc should open in the same size it was last closed in but not snap when excluded.

### ❌ Actual Behavior

It opens in the full size of a fancy zone on my 49" screen.  It does stop the snapping behavior though.
[PowerToysReport_2024-03-27-21-22-09.zip](https://github.com/microsoft/PowerToys/files/14772520/PowerToysReport_2024-03-27-21-22-09.zip)


### Other Software

_No response_
Repository: bitcoin
Issue: release: ship codesigned MacOS arm64 binaries
Labels: macOS

[Since MacOS 11.0.1](https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-universal-apps-release-notes#New-Features), the operating system enforces that any executable must be signed before it’s allowed to run.

When a user downloads and tried to run a MacOS arm64 binary (e.g. for [26.0](https://bitcoincore.org/bin/bitcoin-core-26.0/bitcoin-26.0-arm64-apple-darwin.tar.gz)), the first interaction they get is the error that `“bitcoind” is damaged and can’t be opened. You should move it to the Bin.`

<img width="260" alt="image" src="https://github.com/bitcoin/bitcoin/assets/69010457/97ed147e-aa74-484c-a56e-1c3014aedaf4">

Even though this is quickly resolved by running `codesign --sign - ./bitcoind`, the error message does not provide any such directions, and is quite confusing for users.

I would suggest that we, in order of my preference:
1. ship codesigned binaries by default, and keep unsigned binaries available at https://bitcoincore.org/bin/ for those that need/want it
1. include a README.txt in the tar.gz with codesigning instructions (which cli users should be reasonably used to / familiar with anyway). An install shell script would be an option too but is probably more controversial.
1. add clear instructions on bitcoincore.org and bitcoin.org

I'm unsure if any similar issues exist for the Windows binaries, but if so, we should probably take a similar approach there (if anyone with a Windows machine can confirm this, that would be great).
Repository: rust
Issue: Enum variants can't be imported via type alias
Labels: A-type-system,T-lang,C-bug,S-has-mcve,T-types

In chrono 0.4.36 we renamed a `LocalResult` enum to `MappedLocalTime`, and added a type alias with the name `LocalResult`.
This turned out to be a breaking change because enum variants can't be imported through a type alias.

```rust
enum MappedLocalTime {
    Single,
    Ambiguous,
    None,
}

type LocalResult = MappedLocalTime;

use LocalResult::*;
```

Gives the error:

```
    Checking alias v0.1.0 (C:\Users\dicke\Documents\alias)
error[E0432]: unresolved import `LocalResult`
 --> src\main.rs:9:5
  |
9 | use LocalResult::*; // fails
  |     ^^^^^^^^^^^ `LocalResult` is a type alias, not a module

For more information about this error, try `rustc --explain E0432`.
error: could not compile `alias` (bin "alias") due to previous error
```

I expected the type alias to behave identical to the enum.

Maybe related to [RFC 2338 Type alias enum variants](https://rust-lang.github.io/rfcs/2338-type-alias-enum-variants.html).