sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Particles 2D animation ignore AtlasTexture bounding
Labels: bug,topic:rendering,topic:2d,topic:particles

### Tested versions

- reproductible in 4.2.1.stable

### System information

Windows 10, 4.2.1.stable, every rendering backend (Forward+, Compatibility,Mobile)

### Issue description

Particle 2D (both CPUParticles2D and GPUParticles2D) ignore their AtlasTexture's region/bounding when using particle animation.
![particle_atlas_screenshot](https://github.com/godotengine/godot/assets/7129807/10e425b3-11ac-4f93-b4ca-7c135359643f)

in the example, red-yellow stripes are out of the AtlasTexture's region and should not be visible :
![atlas_demo](https://github.com/godotengine/godot/assets/7129807/5a304ab0-b9ae-4897-b02b-121755de43db)


### Steps to reproduce

1. Create a **Particles2D** Node
2. Set texture to an **AtlasTexture** with a region
3. Add a **CanvasItemMaterial**
4. enable **particles_animation** in the material
5. set **particles_anim_h_frames** and **particles_anim_v_frames**

### Minimal reproduction project (MRP)

[particle_atlas_bug_repro_project.zip](https://github.com/godotengine/godot/files/14236296/particle_atlas_bug_repro_project.zip)
Repository: material-ui
Issue: The "AppsRounded" icon isn't rounded at all (@mui/icons-materia)
Labels: bug 🐛,package: icons

### Steps to reproduce

1. Go to https://mui.com/material-ui/material-icons
2. Search "Apps"

### Current behavior

This is the "Apps" default icon
![image](https://github.com/mui/material-ui/assets/89807193/6a703eb4-8d2a-4515-bf69-697ce1bde2f0)

This is the "Apps" rounded icon
![image](https://github.com/mui/material-ui/assets/89807193/7c18beb2-b1ec-4177-8373-a9a5b3cafb47)

### Expected behavior

The "AppsRounded" icon should look like the icons to the left and right of t oin the screenshot

### Context

I'm building a app for my employer. We use the rounded icons only.

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
 System:
    OS: Windows 10 10.0.19045
  Binaries:
    Node: 21.6.1 - C:\Program Files\nodejs\node.EXE
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.11.0 - ~\AppData\Local\pnpm\pnpm.EXE
  Browsers:
    Chrome: Not Found
    Edge: Chromium (121.0.2277.112)
  npmPackages:
    @emotion/react: ^11.11.3 => 11.11.3
    @emotion/styled: ^11.11.0 => 11.11.0
    @mui/base:  5.0.0-beta.36
    @mui/core-downloads-tracker:  5.15.9
    @mui/icons-material: ^5.15.9 => 5.15.9
    @mui/material:  5.15.9
    @mui/private-theming:  5.15.9
    @mui/styled-engine:  5.15.9
    @mui/system:  5.15.9
    @mui/types:  7.2.13
    @mui/utils:  5.15.9
    @types/react: ^18.2.55 => 18.2.55
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^5.2.2 => 5.3.3

```
</details>


**Search keywords**: AppsRounded, Icon, Apps, Rounded
Repository: puppeteer
Issue: [Bug]: Locator click outputs Timeout, when using a variable instead of a fixed
Labels: feature,confirmed,P3

### Minimal, reproducible example

```TypeScript
import puppeteer from 'puppeteer';

(async () => {

    const browser = await puppeteer.launch();
    const page = await browser.newPage();

    const searchURL = 'someUrlWith'
    const dynamicValue = 'searchingForValue'


    await page.goto(searchURL, { waitUntil: 'networkidle0' });

    await page.screenshot({ path: 'debug-screenshot-1.png', fullPage: true });

    await page.locator(' .searchedClass')
        .filter((div: { innerHTML: string | any[]; }) => div.innerHTML.includes(dynamicValue))
        .click();

    await page.waitForNavigation({waitUntil: "domcontentloaded"});

    await page.screenshot({ path: 'debug-screenshot-2.png', fullPage: true });
})
```


### Error string

TimeoutError: Timed out after waiting 30000ms

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Background

I want to use filter in order to get a specific div with the class 'searchedClass', that has dynamicValue as a text within the html of the div. I also want to click on it in order to land to the next page

### Expectation

I would get to the next page and get the current url after the click

### Reality

I got this TimeoutError

```
TimeoutError: Timed out after waiting 30000ms
at path-to-project-root\node_modules\puppeteer-core\src\common\util.ts:311:17
at path-to-project-root\node_modules\puppeteer-core\lib\cjs\third_party\rxjs\rxjs.js:3:59978
at t.f._next (path-to-project-root\node_modules\puppeteer-core\lib\cjs\third_party\rxjs\rxjs.js:3:11821)
at t.next (path-to-project-root\node_modules\puppeteer-core\lib\cjs\third_party\rxjs\rxjs.js:3:6459)
at t.<anonymous> (path-to-project-root\node_modules\puppeteer-core\lib\cjs\third_party\rxjs\rxjs.js:3:71381)
at t._execute (path-to-project-root\node_modules\puppeteer-core\lib\cjs\third_party\rxjs\rxjs.js:3:28234)
at t.execute (path-to-project-root\node_modules\puppeteer-core\lib\cjs\third_party\rxjs\rxjs.js:3:28057)
at t.flush (path-to-project-root\node_modules\puppeteer-core\lib\cjs\third_party\rxjs\rxjs.js:3:32540)
at listOnTimeout (node:internal/timers:573:17)
at processTimers (node:internal/timers:514:7)
```

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

22.0.0

### Node version

20.7.0

### Package manager

npm

### Package manager version

10.4.0

### Operating system

Windows
Repository: storybook
Issue: [Bug]: @storybook/react-vite framework changes in MUI theme file are not reflected in hot reload
Labels: bug,help wanted,react,mui,builder-vite,sev:S3

### Describe the bug

When use `@storybook/react-vite` framework and I have used themes from MUI in storybook components, while making changes in the theme file, the changes are not reflected in hot reload.
I have investigated and the problem is the files that are created in `node_modules/.cache/sb-vite/deps`
I have tried to make the cache disable but I have not been able to fix this problem.

When I delete node_modules/.cache/sb-vite/deps manually and restart the change appears in storybook

### To Reproduce

_No response_

### System

```bash
System:
    OS: macOS 13.6
    CPU: (10) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.5.1 - /opt/homebrew/bin/node
    npm: 9.8.0 - /opt/homebrew/bin/npm <----- active
  Browsers:
    Chrome: 121.0.6167.160
    Safari: 16.6
```


### Additional context

**I'm using this packages of Storybook:**
  
  "@storybook/builder-vite": "^7.4.2",
    "@storybook/client-api": "^7.4.2",
    "@storybook/addon-actions": "^7.4.2",
    "@storybook/addon-essentials": "^7.4.2",
    "@storybook/addon-links": "^7.4.2",
    "@storybook/addon-styling": "^1.3.7",
    "@storybook/addons": "^7.4.2",
    "@storybook/mdx1-csf": "^1.0.0",
    "@storybook/react": "^7.4.2",
    "@storybook/cli": "^7.4.2",
    "@storybook/react-vite": "^7.4.2",

**main.js file:**


module.exports = {
    stories: [
      "src/**/*.stories.mdx",
      "src/**/*.stories.@(js|jsx|ts|tsx)"
    ],
    docs: {
      autodocs: true
    },
    addons: [
      "@storybook/addon-links",
      "@storybook/addon-essentials",
      "@storybook/addon-styling",
      "@storybook/mdx1-csf"
    ],
    features: { buildStoriesJson: true, legacyMdx1: true },
    framework: {
      name: "@storybook/react-vite",
      options: {}
    },
  };
Repository: svelte
Issue: svelte stores are greedy and have no equivalent of <svelte:options immutable={true} />
Labels: feature request,runtime

### Describe the problem

Currently, sveltes stores use a greedy comparator to determine if a value has changed:
```js
/**
 * @param {any} a
 * @param {any} b
 * @returns {boolean}
 */
export function safe_not_equal(a, b) {
	// eslint-disable-next-line eqeqeq
	return a != a
		? // eslint-disable-next-line eqeqeq
			b == b
		: a !== b || (a && typeof a === 'object') || typeof a === 'function';
}
```

This makes sense as a default as it matches the nature of reactive blocks in svelte 4.

Svelte 4 also supports immutable reactivity ([<svelte:options immutable={true} />](https://svelte.dev/docs/special-elements#svelte-options)).  see: [example](https://svelte.dev/examples/immutable-data)

It would be useful if the stores had a similar parallel, allowing the ability to specify an alternative equality checker such as a strict equality checker.



### Describe the proposed solution

Update the store api/implementation to allow a configurable comparison function which would override the default `safe_not_equal`.

e.g.

```js
/**
 * @param {any} a
 * @param {any} b
 * @returns {boolean}
 */
export function strict_not_equal(a, b) {
	return a !== a;
}
```

possible apis:

*extend the current implementation*
```js
const w1 = writable({ value: 1 }, { comparator: strict_not_equal });
const w2 = writable({ value: 1 }, () => {}, { comparator: strict_not_equal })
const r1 = readable({ value: 1 }, { comparator: strict_not_equal })
const r2 = readable({ value: 1 }, () => {}, { comparator: strict_not_equal })
const d1 = derived(w1, w1 => {}, undefined, { comparator: strict_not_equal })
const d2 = derived([w1,w2], ([w1, w2]) => {}, undefined, { comparator: strict_not_equal })

```
*offer an alternative import*
```js
import { readable, writable, derived } from 'svelte/immutable-stores';
```

### Importance

nice to have
Repository: next.js
Issue: Revalidation in SSG 
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/ssg-notfound-routes-9hsd4l

### To Reproduce

1. build and serve application (`yarn build && yarn start`)
> Make sure the build is served not the default dev-mode in port 3000 ([kill if needed](https://stackoverflow.com/a/76916598/10321531))
2. visit the `/posts/something` it will face 404

I've tested with the next `canary (in codesandbox), 14.1.0, 13.5.6)`

### Current vs. Expected behavior

I expect that the page which has the `revalidate` not indexed in  `notFoundRoutes` in `prerender-manifest.json` so I can make it make generated on next visit by me




### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:27 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T8103
Binaries:
  Node: 18.19.0
  npm: 10.2.3
  Yarn: 1.22.21
  pnpm: 8.15.1
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: standalone


warn  - Latest canary version not detected, detected: "14.1.0", newest: "14.1.1-canary.48".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next build (local), next start (local)

### Additional context

We are serving `'standalone'` but it doesn't change in normal build too, also clearing `"notFoundRoutes"` before resolve the issue.

> Why this happen and why I need this
- Imagine api is down for some time, so I return not-found for build stage, but need this page to be visible to user, when the api comes back for that page.
Repository: vscode
Issue: Integrate multi diff editor better into the workbench
Labels: debt,workbench-editors,multi-diff-editor

While looking into https://github.com/microsoft/vscode/issues/204076, I noticed that the multi diff editor misses to implement some of the methods of `EditorPane` that will result in better integration. Specifically:
* [ ] minimum width and size constraint changes (see for example in [`mergeEditor`](https://github.com/microsoft/vscode/blob/983a3bc0aecfc0772dd7b37919d7da36c89a6f2d/src/vs/workbench/contrib/mergeEditor/browser/view/mergeEditor.ts#L137-L144)
* [ ] the scoped context key service for the editor (see in [`mergeEditor`](https://github.com/microsoft/vscode/blob/983a3bc0aecfc0772dd7b37919d7da36c89a6f2d/src/vs/workbench/contrib/mergeEditor/browser/view/mergeEditor.ts#L490-L493))
* [ ] propagation of pane visibility (see in [`mergeEditor`](https://github.com/microsoft/vscode/blob/983a3bc0aecfc0772dd7b37919d7da36c89a6f2d/src/vs/workbench/contrib/mergeEditor/browser/view/mergeEditor.ts#L470-L482)
* [ ] setting boundary sashes to allow to resize a bottom sash and the sash of the diff at the same time (probably only applies to the last diff editor, see in [text diff editor](https://github.com/microsoft/vscode/blob/983a3bc0aecfc0772dd7b37919d7da36c89a6f2d/src/vs/workbench/browser/parts/editor/textDiffEditor.ts#L378-L380))
Repository: vscode
Issue: Merge editor: set boundary sashes
Labels: feature-request,workbench-editors,workbench-editor-grid,merge-editor

Sashes in VS Code are capable of connecting even elements within grids: you can for example open a diff editor and a panel and resize both the panel and the diff editor at the same time even though the grid is nested:

![Recording 2024-02-12 at 11 07 48](https://github.com/microsoft/vscode/assets/900690/edf30eb5-09c0-4b2a-a9a6-4ae01885e66a)

I think for the merge editor we could offer the same at this junction between sidebar and horizontal sash:

<img width="804" alt="image" src="https://github.com/microsoft/vscode/assets/900690/2e220d00-205f-46c7-b289-2a1fa7e82681">

I think for an editor to adopt this, it needs:

https://github.com/microsoft/vscode/blob/983a3bc0aecfc0772dd7b37919d7da36c89a6f2d/src/vs/workbench/browser/parts/editor/editorPane.ts#L166-L168

But @joaomoreno would know for sure.
Repository: rust
Issue: How should const generics with references work around pointer identity and padding?
Labels: A-const-eval,T-opsem,F-unsized_const_params

Const generics currently completely deconstruct the value into a valtree and then reconstruct it, which destroys pointer identity. As long as this is just about purely immutable `const` values we might be able to argue that they "don't have pointer identity" (though it is entirely unclear to me what exactly that should mean). But if consts can [point to statics](https://github.com/rust-lang/rust/issues/119618), that doesn't really work any more.

Example:
```rust
#![feature(const_refs_to_static)]
#![feature(adt_const_params)]

static FOO: usize = 42;
const BAR: &usize = &FOO;
fn foo<const X: &'static usize>() {
    if std::ptr::eq(X, &FOO) {
        println!("activating special mode");
    }
}

fn main() {
    foo::<BAR>();
}

```
Arguably this should print, but [currently it does not](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=19072469cd8ddab79da2252616fe8684).

Cc https://github.com/rust-lang/rust/issues/95174, https://github.com/rust-lang/rust/issues/119618

Similarly, this example demonstrates that padding is lost when passing an `&(u8, u16)`  as a const generic, which is not how passing a reference usually behaves:
```rust
#![feature(const_refs_to_static)]
#![feature(adt_const_params)]

static FOO: u32 = 0x01020304;
const BAR: &(u8, u16) = unsafe { std::mem::transmute(&FOO) };

fn foo<const X: &'static (u8, u16)>() {
    let val: &u32 = unsafe { std::mem::transmute(X) };
    println!("{val:#x}"); // prints 0x1020004
}

fn main() {
    foo::<BAR>();
}
```
Repository: tauri
Issue: [bug] FS Doesn't Work on IOS
Labels: type: bug,status: needs triage,platform: iOS

### Describe the bug

FS's readDir() (being called from JS front-end) is giving me "No such file or directory" for any path I've tried on an IOS simulator.

I have set the permissions correct, but **it appears fs cannot access any files in the IOS filesystem**

ERROR"\"failed to read directory at path: / with error: No such file or directory (os error 2)\""

Is the error shown in the web console (inspected via safari).

### Reproduction

Create a Tauri 2.0 app

Add 
`
{
      "identifier": "fs:scope",
      "allow": [
        {"path":"$HOME/**"},
        {"path":"**"},
        {"path":"$HOME"}
      ]
    },
`
to capabilities

install fs plugin 
[](https://github.com/tauri-apps/tauri-plugin-fs)

Then call the readDir() function from JS 

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 14.1.2 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 20.10.0
    - npm: 10.2.3
    - bun: 1.0.18

[-] Packages
    - tauri [RUST]: 2.0.0-beta.2
    - tauri-build [RUST]: 2.0.0-beta.1
    - wry [RUST]: 0.35.2
    - tao [RUST]: 0.25.0
    - @tauri-apps/api [NPM]: 2.0.0-beta.0
    - @tauri-apps/cli [NPM]: 2.0.0-beta.1

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist/test/browser
    - devUrl: http://localhost:1420/
    - framework: Angular
    - bundler: Webpack

[-] iOS
    - Developer Teams: REDACTED
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: godot
Issue: Constant warning 'XCreateIC couldn't create wd.xic' when new editor popups are shown
Labels: bug,platform:linuxbsd,topic:porting,confirmed

### Tested versions

- Reproducible pretty much on all Godot 4 versions

### System information

Godot v4.2.1.stable - Ubuntu 22.04 - X11 - Mesa Intel(R) Graphics (RPL-P) () - 13th Gen Intel(R) Core(TM) i7-13700H (20 Threads)

### Issue description

Whenever a popup is shown in the editor, this warning appears in the `Output` console :

 `platform/linuxbsd/x11/display_server_x11.cpp:5575 - XCreateIC couldn't create wd.xic`

This happens on all Godot 4 versions for me, up to the current master, on all 3 renderers.

However, it does not happen when enabling `Single Window Mode`.

There are a few issues mentioning this message, but all of them are related to crashes. In my case, this is just a warning, and there are no crashes. The editor functions as it should be.

### Steps to reproduce

- Open the editor
- Disable `Single Window Mode` in editor settings
- Move around the editor and open some of the main menu items : `Scene`, `Project`, `Help` ...
- The warning shows up in the `Output` console for each new Popup.



![Screenshot_20240212_120032-1](https://github.com/godotengine/godot/assets/3624853/9c978e36-9f10-4f1f-aed4-f571d564a810)


### Minimal reproduction project (MRP)

N/A. This happens in the editor, even in a blank project.
Repository: angular
Issue: Produce an error or warning if not deferrable dependency is used within @defer block
Labels: feature,area: core,feature: votes required,core: defer

### Which @angular/* package(s) are relevant/related to the feature request?

compiler

### Description

Right now if not deferrable dependency is provided, angular will load it eagerly without any information which is not obvious.

It would also be nice to at least produce an error or warning so that developers know they've done something wrong

### Proposed solution

No response

### Alternatives considered

No response
Repository: PowerToys
Issue: [FancyZones] Automatic dynamic tiling option
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

Support Linux style dynamic tiling similar to popular window managers such as AwesomeWM.  

For a Windows example, see:

https://github.com/LGUG2Z/komorebi

This feature could be an optional extension to FancyZones which already manages window placement and layouts.  

For a simple starting point, the Pop!_OS approach has a small set of GUI options and a simple set of defaults which may be a good starting point that fits with PowerToys better than the configuration files used by most tiling window managers.

### Scenario when this would be used?

Placing windows manually is slow and tedious, it’s much more efficient for them to automatically place in a selected layout on launch with quick keyboard based adjustments to layout position.

### Supporting information

_No response_
Repository: storybook
Issue: [Bug]: You (or an addon) are using the 'config' preset field. This has been replaced by 'previewAnnotations' and will be removed in 8.0
Labels: bug,needs more info,needs triage

### Describe the bug

Following step by step: https://github.com/storybookjs/storybook/discussions/25502


In console.log I got the following addons: 

- storybook-stylesheet-toggle,
- @storybook/react
- @storybook/addon-links
- @storybook/addon-essentials
- @storybook/addon-a11y
- @storybook/addon-interactions


### To Reproduce

_No response_

### System

_No response_

### Additional context

_No response_
Repository: opencv
Issue: use standard C++ types in API
Labels: feature,cleanup

### Describe the feature and motivation

For OpenCV 5, where we have a good chance to repair certain things, even if it slightly breaks API, it would be nice to replace some "home-brewed" names with somewhat more standard:

* uchar => uint8_t
* schar => int8_t
* short => int16_t
* ushort => uint16_t
* unsigned => uint32_t (where it makes sense)
* int64 => int64_t
* uint64 => uint64_t
* cv::String => std::string (some functions may take std::string_view for slightly better efficiency)
* cv::Ptr => std::shared_ptr

'int' is a special story - it's used very often in API and probably we should keep it as-is in API (except when int means int32_t, not just "integer with sufficiently large value range")

the old definitions may be put into a dedicated header that may be included by default in OpenCV 5 and not included by default in OpenCV 6+

### Additional context

_No response_
Repository: opencv
Issue: Remove OpenVX
Labels: feature,cleanup

### Describe the feature and motivation

OpenVX contains very little functionality and seems to be an almost abandoned standard. All external OpenCV accelerators (except (maybe!) OpenCL's T-API) should go through our HAL interface and be put outside. Since OpenVX does not contain much stuff, in OpenCV 5 we can just remove it without creating dedicated HAL backend. It could be added later once more useful API is added there.

The most affected modules are core and imgproc

### Additional context

_No response_
Repository: opencv
Issue: Move IPP to opencv/3rdparty (just like Carotene)
Labels: feature,cleanup

### Describe the feature and motivation

It's time to clean up OpenCV code and move 3rd-party accelerators outside of the main code. It's suggested to move IPP-based acceleration (i.e. multiple insertions, mostly in core, imgproc, where checks for Intel IPP are performed and IPP functions are called when appropriate) to opencv/3rdparty where Carotene already resides.  At the same time, by OpenCV 5 we need to finalize and publish somewhere HAL API spec that will allow further OpenCV+IPP cooperation via HAL mechanism.

### Additional context

_No response_
Repository: angular
Issue: SSR server crashes when HttpClient receives 5xx 
Labels: area: router,area: server

### Command

serve

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

Hi. Currently, both dev and built SSR servers are crashing when HttpClient receive 5xx response. This is annoying, because i always have to restart dev server (or deployed instance restarts itself on each error) and scroll giant log to see what happened (it prints full HttpErrorResponse class).

### Minimal Reproduction

ng serve/node server.mjs

### Exception or Error

_No response_

### Your Environment

```text
latest 17.1
```


### Anything else relevant?

_No response_