sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Set a default fancy zone for X resolution. 
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

I would like to set a default fancy zone canvas for any external monitor that uses X resolution.

### Scenario when this would be used?

I use hot desks at work, and every time I move to a new hot desk, I need to open fancy zones and set the canvas again. If I can set a default for a particular resolution, then switching desks shouldn't matter. 

### Supporting information

_No response_
Repository: go
Issue: proposal: os: Add `SysConfigDir()` Function
Labels: Proposal

## Abstract

This proposal suggests adding a new function, `SysConfigDir()`, to the `os` package in the Go standard library. This function will help Go applications find the default directory for system-wide configuration data in a consistent way across different operating systems.

## Background

Right now, `os` package has a function called `UserConfigDir()` that's good for getting the directory for user-specific configuration data. But there's no similar function for getting the directory for system-wide configuration data. Many Go apps need this to store configuration files that should be shared among all users on a system.

## Proposal

I propose adding a new function, `SysConfigDir()`, to the `os` package. This function will return the directory path for system-wide configuration data. It will work the same way on all supported operating systems, just like `UserConfigDir()`. The way it works will be different depending on the operating system, following the conventions of that system.

## Rationale

Here's why we need to add `SysConfigDir()`:

1. **Consistency**: Having a standard way to get the system-wide configuration directory makes things simpler for developers. It keeps things the same no matter which operating system you're on.

2. **Best Practices**: It encourages developers to follow the best practices for managing configuration. It guides them to use the right directories and avoid problems like hardcoded paths or conflicts.

3. **User-Friendly**: Just like `UserConfigDir()`, `SysConfigDir()` gives developers an easy way to find system-wide configuration directories, even on systems with different ways of doing things.

## Compatibility

Adding `SysConfigDir()` won't mess up existing code. It's a new feature that we're adding to the `os` package, so it doesn't affect anything that's already there.

## Implementation

Here's how we'll make `SysConfigDir()` work:

1. Figure out which operating system you're using (like Windows, Unix, Plan9).
2. Use the right way to find the system-wide configuration directory based on how that operating system does things.
3. Give you the directory path, or return error if couldn't figure it out.
Repository: angular
Issue: Static attributes are not hydrated, causing refetching of external resources
Labels: area: core,core: hydration

### Which @angular/* package(s) are the source of the bug?

platform-browser

### Is this a regression?

No

### Description

There's a hydration issue when static attributes are set again during Angular's client-side rendering. This can lead to problems with `src` attributes that load external resources. Browsers consider each change to the `src` attribute as a new request to load the specified resource.

For example, when the server returns `<iframe src="..."` pointing to a YouTube video that starts playing after the browser has rendered the content but before `bootstrapApplication` is called, an issue arises. When `bootstrapApplication` is invoked, Angular initiates its 'initialization' flow, during which it calls `setAttribute` on this `iframe` once more. Consequently, the video may flicker as the browser attempts to reload it.

### Please provide a link to a minimal reproduction of the bug

https://github.com/arturovt/hydration-iframe-src-issue

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 16.2.7
Node: 18.13.0
Package Manager: yarn 1.22.19
OS: linux x64

Angular: 16.2.10
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1602.7
@angular-devkit/build-angular   16.2.7
@angular-devkit/core            16.2.7
@angular-devkit/schematics      16.2.7
@angular/cli                    16.2.7
@nguniversal/builders           16.2.0
@nguniversal/express-engine     16.2.0
@schematics/angular             16.2.7
rxjs                            7.8.1
typescript                      5.1.6
zone.js                         0.13.3
```


### Anything else?

_No response_
Repository: vscode
Issue: Investigate WordHighlighter & WordHighlighterContrib listeners
Labels: under-discussion,editor-highlight

Stemming from https://github.com/microsoft/vscode/issues/196949, the wordHighlighter is having `positionChanged` events fired while scrolling throughout the notebook regardless of the location of the active cell. This causes the occurrences to be recomputed based on a disposed text model.

Several listeners appear to be somewhat contradictory, ie listening for a `modelChange` event within WordHighlighter, then also listening and disposing of a WordHighlighter instance when there is a model change event.

Relevant code:
- Within the ctor for `WordHighlighter` https://github.com/microsoft/vscode/blob/540180098a63d237a10dad7a806be30af6cf298e/src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts#L307-L315
- Within the ctor for `WordHighlighterContrib` https://github.com/microsoft/vscode/blob/540180098a63d237a10dad7a806be30af6cf298e/src/vs/editor/contrib/wordHighlighter/browser/wordHighlighter.ts#L784-L792
Repository: rust
Issue: False sharing issue for std::sync::RwLock
Labels: I-slow,C-bug,T-libs

While benchmarking the Hugging Face tokenizer, which uses std::sync::RwLock for managing read/write access to shared data, we've observed a false sharing issue.
 
In the current implementation of RwLock, the inner lock is positioned adjacent to the data field. In most cases, these elements are placed within a single cache line (typically 128 bytes in x86 systems).
https://github.com/rust-lang/rust/blob/master/library/std/src/sync/rwlock.rs#L80-L84
 
```
pub struct RwLock<T: ?Sized> {
   inner: sys::RwLock,
   poison: poison::Flag,
   data: UnsafeCell<T>,
}
```
 
 
When a reader thread attempts to access data that isn't being altered but shares the same cache line as a lock that is being altered (e.g., when a new reader acquires the read lock), the caching protocol necessitates the first reader thread to reload the entire cache block, despite a lack of logical necessity. This significantly impacts performance, especially when the number of readers exceeds the number of writers.
 
To address this issue, one practice is to move the data to a new cache line by adding some padding. One quick fixing, which use `#[repr(align(128))]` to align each field to 128 bytes, has shown more than a 10% increase in throughput in our benchmark. However, it's important to note that this change might have a detrimental impact on throughput when the number of readers is less than the number of writers, since a writer has to write data and lock to two different cache lines.
 
An instinctive solution suggested by @pingzhaozz  is split the inner RwLock into two fields, one is used for write access control which resides in the same cacheline with data field, the other lock for reader will be placed in another cacheline to avoid unnecessary reload data cacheline caused by another reader acquired the read lock.

Any comments would be appreciated.


<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: godot
Issue: 4.2 beta 4 in linux openSUSE Tumbleweed wayland
Labels: bug,platform:linuxbsd,topic:rendering,needs testing

### Godot version

4.2 beta 4

### System information

Godot v4.2.beta4.mono - openSUSE Tumbleweed 20231026 - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 6600 (RADV NAVI23) () - AMD Ryzen 7 5700G with Radeon Graphics (16 Threads)

### Issue description

* My project is in 3D
1) Sometimes shows a vulkan warning, and sometimes Godot closes.
```sh
W 0:00:00:0066   _load_pipeline_cache: Invalid/corrupt pipelines cache.
  <C++ Source>   drivers/vulkan/rendering_device_vulkan.cpp:9180 @ _load_pipeline_cache()
```
To solve this:
```sh
rm -rf ~/.local/share/godot/shader_cache
```

2) In the FileSystem, if Right click, press a up or down arrow in keyboard, moves to `Copy Path` or `Rename...` and dont to `Create New`

3) In the FileSystem: Change to Split mode (vertical), constantly closes Godot.

* Just for fun working with 2D
1) Working with tilemaps, messing around with maps ( at start I did not know how to apply collisions ), closes Godot.

### Steps to reproduce

* Vulkan issue:
  * Don't know how to achieve, just appears and I have to remove those files.

* FileSystem: Just right click, press up/down key arrows.
* FileSystem: Click in the Split Mode, start working with Godot.

* 2D with tilemap
* Just working with tilemaps: adding a sprite sheet, adding collisions.

### Minimal reproduction project

The vulkan thing, don't know if appears in 2d or a new 3d project. The other ones, cant be applied even in a new project.
Repository: ant-design
Issue: 下拉框有焦点时，按下键盘任意一个键都会打开下拉框
Labels: Inactive,improvement

### Reproduction link

[https://ant-design.antgroup.com/components/select-cn](https://ant-design.antgroup.com/components/select-cn)

### Steps to reproduce

官方文档就有这个问题 https://ant-design.antgroup.com/components/select-cn
1. 点击下拉框展开下拉选项
2. 同样的位置点击收起下拉选项（这两步后下拉框依旧会有焦点）
3. 然后点击任何一个键盘按键，下拉选项会展开
（疑惑 按回车能展开收起合理，任何按键都能展开很不合理）

### What is expected?

点击除enter的其他按键，下拉选项不展开

### What is actually happening?

点击任何一个键盘按键，下拉选项会展开

| Environment | Info |
| --- | --- |
| antd | 5.10.2 |
| React | 18.0.0 |
| System | win10 |
| Browser | chrome114.0.5735.110 |

---
https://ant-design.antgroup.com/components/select-cn 文档中第一个例子第一个下拉框就可以复现
rc-select 也有同样的问题

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: Peek - Releasing of Personal Macro Workbook resource when Previewing Excel files
Labels: Issue-Bug,Resolution-External

### Microsoft PowerToys version

v0.75.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Peek

### Steps to reproduce

1. Create a [Personal Macro Workbook](https://support.microsoft.com/en-au/office/create-and-save-all-your-macros-in-a-single-workbook-66c97ab3-11c2-44db-b021-ae005a9bc790) in Microsoft Excel.
2. Open PowerToys, and use Peek on any Excel file.
3. As long as the same instance of PowerToys remains running, it will never release the Personal.xlsb resource...
4. Launch Microsoft Excel, and you get this File in Use warning:
![Personal.xlsb File in Use Warning](https://github.com/microsoft/PowerToys/assets/5472716/4da30fe6-ba25-4e81-b880-412bd849329f)

[PowerToysReport_2023-10-31-21-36-42.zip](https://github.com/microsoft/PowerToys/files/13223504/PowerToysReport_2023-10-31-21-36-42.zip)


### ✔️ Expected Behavior

Upon closing of the Peek window, the Personal.xlsb file should be released.

### ❌ Actual Behavior

Peek fails to release the Personal.xlsb resource until PowerToys is terminated.

### Other Software

Microsoft Excel (via Microsoft 365 Apps for business) Version 2310 Build 16924.20106 Click-to-Run)
Repository: deno
Issue: Useful output when logging `AtomicOperation`s
Labels: good first issue,feat,ext/kv

I have an atomic transaction that is failing, and I'm trying to figure out why. My first step was to try understanding what's the exact data that I'm trying to commit. There isn't a single place where I can add a `console.log`, but I have to manually log all the variables that I'm using to build my transaction.

To add such logging, I have to modify my transaction:
```diff
  const res = await kv
    .atomic()
    .check({ key: ["companies", data.companyId], versionstamp: companyStamp })
    .check({
      key: ["stations", data.departureStationId],
      versionstamp: departureStationStamp,
    })
    .check({
      key: ["stations", data.arrivalStationId],
      versionstamp: arrivalStationStamp,
    })
    .check({ key: ["trips", trip.id], versionstamp: tripStamp })
    .set(["trips", trip.id], serializeTripTime(trip))
    .commit();
```

```diff
+ const serializedTrip = serializeTripTime(trip)

+ console.log({
+   companyId: data.companyId,
+   companyStamp,
+   departureStationId: data.departureStationId,
+   departureStationStamp,
+   arrivalStationId: data.arrivalStationId,
+   arrivalStationStamp,
+   tripId: trip.id,
+   tripStamp: tripStamp,
+   serializedTrip,
+ });

  const res = await kv
    .atomic()
    .check({ key: ["companies", data.companyId], versionstamp: companyStamp })
    .check({
      key: ["stations", data.departureStationId],
      versionstamp: departureStationStamp,
    })
    .check({
      key: ["stations", data.arrivalStationId],
      versionstamp: arrivalStationStamp,
    })
    .check({ key: ["trips", trip.id], versionstamp: tripStamp })
-   .set(["trips", trip.id], serializeTripTime(trip))
+   .set(["trips", trip.id], serializedTrip)
    .commit();
```

It would be great if instead I could log the `AtomicOperation` object, and get some sort of string serialization. Effectively, it means that my code change is reduced to
```diff
- const res = await kv
+ const transaction = kv
    .atomic()
    .check({ key: ["companies", data.companyId], versionstamp: companyStamp })
    .check({
      key: ["stations", data.departureStationId],
      versionstamp: departureStationStamp,
    })
    .check({
      key: ["stations", data.arrivalStationId],
      versionstamp: arrivalStationStamp,
    })
    .check({ key: ["trips", trip.id], versionstamp: tripStamp })
    .set(["trips", trip.id], serializeTripTime(trip))
+ console.log(transaction);
+ await transaction
    .commit();
```

The current logged output is just `AtomicOperation {}`, but something like this would be much more helpful:
```
AtomicOperation
  check({ key: ["companies", "aaaa"], versionstamp: 1111 })
  check({ key: ["stations", "bbbb"], versionstamp: 2222 })
  check({ key: ["stations", "cccc"], versionstamp: 3333 })
  check({ key: ["trips", "dddd"], versionstamp: 4444 })
  set(["trips", "dddd"], { x: 2 })
```

(and it would be even better if I could just add a `.log()` before `.commit()`, rather than having to manually split my statement in three)
Repository: excalidraw
Issue: Image upload doesn't work(ImageBlobReduce: failed to create Image() from blob error)
Labels: images

I'm trying to upload an image to https://excalidraw.com(also on a self hosted app).
Same error: Uncaught (in promise) Error: ImageBlobReduce: failed to create Image() from blob. It's a 8kb png image.
Using Firefox, I'm getting the 'Couldn't insert image. Try again later...' popup. There's no popup on Chrome, Safari, Opera, Brave.
I've managed to upload an image(also png) and I saved the content of the canvas in a mysql database table. When loading back the content images are blank. The same base64 string displays correctly used on img src in a simple html file. The files{} object contains the image element and has the same id with the one from elements array.
Repository: godot
Issue: Cannot change size of a control node with a negative scale
Labels: needs testing,topic:gui

### Godot version

v4.2.beta2.mono.official [f8818f85e]

### System information

Windows 11 - Godot v4.2.beta2.mono - Forward Mobile - .NET 7

### Issue description

Cannot change size of a control node which has a negative scale

### Steps to reproduce

Add a control node.
Assign a negative scale to it.
Try changing the size

### Minimal reproduction project

N/A
Repository: godot
Issue: When adding a new action in the Input Map tab, all closed inputs will reopen
Labels: bug,topic:editor,topic:input

### Godot version

v4.2.beta4.official [93cdacbb0]

### System information

Godot v4.2.beta4 - Windows 10.0.22621 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 3080 (NVIDIA; 31.0.15.4584) - AMD Ryzen 9 5950X 16-Core Processor (32 Threads)

### Issue description

When adding a new action in the Input Map tab, all closed inputs will reopen

### Steps to reproduce

1. Open Input Map
2. Create new input action
3. Close that input action
4. Create new input action
5. Every closed input action will reopen again...

### Minimal reproduction project

N/A
Repository: flutter
Issue: Resizing parameters are not supported for multi-frame images in the engine.
Labels: engine,a: images,P2,team-engine,triaged-engine

`instantiateImageCodecFromBuffer` not supported resize webp animation.
* `instantiateImageCodecFromBuffer` need to support resizing of image animation (Flutter engine  not supported);
* `ImmutableBuffer` allows constructing from native ptr, This can improve performance;
Repository: rust
Issue: nvptx abi adjustment may keep PassMode::Direct for small aggregates in conv `extern "C"`
Labels: T-compiler,O-NVPTX,A-ABI

              @kjetilkjeka I had to disable this test on nvptx64 since the `extern "C"` ABI uses `Direct` pass mode in invalid ways. I think that's caused by this code:

https://github.com/rust-lang/rust/blob/b75b3b3afecfb6638c7c75ad665f8f3091aab1ae/compiler/rustc_target/src/abi/call/nvptx64.rs#L10-L14

That's invalid since it doesn't say what to do for smaller aggregates, and they default to the (bad) `Direct`. Instead you have to say which register they are supposed to be passed in. You can check what the other targets are doing. Targets are expected to set an explicit pass mode for *all* aggregate arguments.

This should be easy to reproduce by having a function like
```rust
#[repr(C)]
struct ReprC1<T: ?Sized>(T);

extern "C" fn myfn(x: ReprC1<i32>) {}
```
which will likely ICE on the current compiler already.

_Originally posted by @RalfJung in https://github.com/rust-lang/rust/pull/117351#discussion_r1375418626_
Repository: go
Issue: cmd/vet,cmd/compile: failures with `not a Go object file`
Labels: help wanted,NeedsInvestigation,compiler/runtime

```
#!watchflakes
post <- log ~ `could not import .* \(not a [Gg]o object file`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/00e6f36a7f74e7c782e671526c20ec3b7fbdfb0f)):

    ../../../../pkg/mod/github.com/go-pdf/fpdf@v0.6.0/svgbasic.go:20:2: could not import encoding/xml (not a go object file: )<arch>
    )


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: next.js
Issue: useFormState causes an infinite loop when disabling javascript with a binded action
Labels: bug,linear: next

### Link to the code that reproduces this issue

https://github.com/raphaelbadia/useFormState-causes-an-infinite-loop-when-disabling-javascript-with-a-bounded-action

### To Reproduce

1. install the repo (yarn)
2. Start the application in development (yarn dev)
3. open the app on chrome, and disable javascript
4. click on the third button "trigger infinite loop"


### Current vs. Expected behavior

Following the steps above, I expected an action to be triggered, but I instead saw my server become stuck. Even restarting the server won't fix it: I have to comment the <DoesntWork> component otherwise I'll get an infinite loop.

When javascript is enabled, it works properly.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:39:46 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6020
Binaries:
  Node: 18.18.2
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.9.2
Relevant Packages:
  next: 14.0.2-canary.3
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


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

Not sure

### Additional context

_No response_

<sub>[NEXT-1714](https://linear.app/vercel/issue/NEXT-1714/useformstate-causes-an-infinite-loop-when-disabling-javascript-with-a)</sub>
Repository: flutter
Issue: Add support for fixed accent colors
Labels: c: new feature,framework,f: material design,P2,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

[Part of #91605 ]
Material 3 has introduced a set of new color roles that retain the same color in the light and dark themes collectively referred to as fixed accent colors See: https://m3.material.io/styles/color/the-color-system/color-roles#232e7275-6ef2-4b93-afa6-c5f76e378ced

New surface color roles have also been added: (See #137679)
These changes appear to be part of a wider set of updates to the color system, see [this](https://youtu.be/vnDhq8W98O4?t=649). 


### Color Roles

#### Fixed Accent Colors
See: https://m3.material.io/styles/color/the-color-system/color-roles#232e7275-6ef2-4b93-afa6-c5f76e378ced
| Color Role         | Tone: Light | Tone: Dark |
| ------------------ | ----------- | ---------- |
| Primary Fixed      | P-90        | P-90       |
| Primary Fixed Dim  | P-80        | P-80       |
| Secondary Fixed    | S-90        | S-90       |
| Secondary Fixed Dim| S-80        | S-80       |
| Tertiary Fixed     | T-90        | T-90       |
| Tertiary Fixed Dim | T-80        | T-80       |

#### On Fixed Accent Colors
See: https://m3.material.io/styles/color/the-color-system/color-roles#6a242aff-e606-43d5-a7de-988facc90968
| Color Role                 | Tone: Light | Tone: Dark |
| -------------------------- | ----------- | ---------- |
| On Primary Fixed           | P-10        | P-10       |
| On Primary Fixed Variant   | P-30        | P-30       |
| On Secondary Fixed         | S-10        | S-10       |
| On Secondary Fixed Variant | S-30        | S-30       |
| On Tertiary Fixed          | T-10        | T-10       |
| On Tertiary Fixed Variant  | T-30        | T-30       |


### Proposal

Update `ColorScheme` to include the above roles. The current `ColorScheme.fromSeed` implementation uses the `Scheme` class underneath which is planned to be deprecated. For more info, see #137679.