sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ant-design
Issue: [RFC] Divider custom gutter margin
Labels: Inactive

### What problem does this feature solve?

My team uses Ant Design for our component library. We use the Divider component in many places and we tend to override the gutter margin quite a bit using the style prop. As a team we've all mentioned that it would be nice and seems intuitive that the Divider component would have a prop similar to the `orientationMargin` prop that would adjust the gutter margin.

### What does the proposed API look like?

I propose adding a property to the Divider component called `gutterMargin`

This property would set the `margin-inline` for vertical dividers and the `margin` for horizontal dividers

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: opencv
Issue: Opencv logger memory leak
Labels: wontfix

https://github.com/opencv/opencv/blob/459a9c60eda7ad28c4b41eac6ae3a42b67810750/modules/core/src/logger.cpp#L105

Here the singleton only have new but no delete. Is there any concern to add a delete or just forget it?
Repository: ui
Issue: [bug]: Select under a Form doesn't fous on error
Labels: bug

### Describe the bug

A Select component inside a Form doesn't focus when the validation method is called (default onSubmit) and the field is invalid.

Expected behavior is have the window scroll/focus the invalid field when the validation method is called.
A quick and easy way to test this is on the [example form](https://ui.shadcn.com/examples/forms).

If you fill in the username text input and hit submit the form doesn't focus the select element which is calling for an error validation if a user doesn't select one of the options.

### Affected component/components

Select, Form

### How to reproduce

1. Go to https://ui.shadcn.com/examples/forms
2. Fill in the Username field.
3. Click on "Update profile".
4. Select element does not get focused, even though it's on an error state.

### Codesandbox/StackBlitz link

https://github.com/shadcn-ui/ui/blob/main/apps/www/app/(app)/examples/forms/profile-form.tsx

### Logs

_No response_

### System Info

```bash
OS: Linux Mint 21.3 x86_64
Browser: Firefox 128.0 (64-bit)
Dependencies: 
-"@radix-ui/react-select": "^2.0.0"
-"react-hook-form": "^7.50.1"
-"next": "14.1.0"
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: deno
Issue: Using fs on a network drive requires more permissions on Windows than Mac, and it's unclear what the extra permission is.
Labels: bug,permissions,windows

Version: Deno 1.45.3

I have a NAS, say the server name is `MY_NAS`, and it shares a folder `foo` over SMB.

On mac, to visit `foo` in Finder, I should press ⌘K and input `smb://MY_NAS/foo`. To visit in CLI, I need to use the path `/Volumes/foo`.

On Windows, `\\MY_NAS\foo` can be used in both File Explorer and CLI.

The problem is when I want to operate on it using fs with deno, the permission required seems to differ on Windows and Mac.

```js
// test.ts
if (Deno.build.os === 'windows') {
  Deno.writeTextFileSync('\\\\MY_NAS\\foo\\hello.txt', 'Hello World');
}
if (Deno.build.os === 'darwin') {
  Deno.writeTextFileSync('/Volumes/foo/hello.txt', 'Hello World');
}
```
`deno run -A test.ts` will succeed on both Windows and Mac.
`deno run --allow-write test.ts` will fail on Windows, succeed on Mac.
`deno run test.ts` will ask for `--allow-write`, pressing `y` will fail on Windows, succeed on Mac.

Error message on Windows:
>  Uncaught (in promise) PermissionDenied: permission denied: writefile '\\\MY_NAS\foo\hello.txt'
>  at writeFileSync (ext:deno_fs/30_fs.js:899:3)
>  at Object.writeTextFileSync (ext:deno_fs/30_fs.js:962:10)
Repository: transformers
Issue: Support `from_pretrained` of `FlaxPretrainedModel` from sharded `.safetensors` weights
Labels: Feature request

### Feature request

Currently `FlaxPretrainedModel` only supports loading pretrained models from sharded PyTorch weights or single-file `.safetensors`. It's worth adding support for loading sharded `.safetensors`.

### Motivation

Recent open-source language models trained with PyTorch are likely only to release sharded `.safetensors` weights. The lack of support for loading from the dominating paradigm makes it troublesome to use these models in Jax.

### Your contribution

I'm relatively new to the implementation of the saving & loading mechanism of `transformers`, but I'd love to try to work with this feature if the core team doesn't have enough bandwidth.
Repository: PowerToys
Issue: Alt+Tab window not disappearing on Windows after key remapping with PowerToys on Apple keyboard
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.82.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

### Steps to Reproduce

1. **Open PowerToys:**
   - Ensure PowerToys is running on your Windows machine.

2. **Remap Keys:**
   - Open the "Keyboard Manager" in PowerToys.
   - Remap the `Win` key to `Left Alt (LAlt)`.
   - Remap the `Left Alt (LAlt)` key to `Win`.

3. **Use Alt+Tab:**
   - Press and hold the remapped `Alt` (now the `Win` key) and press `Tab` to open the window switcher.

4. **Observe the Issue:**
   - Release both keys (`Alt` and `Tab`).
   - Notice that the window switcher remains open instead of disappearing.

5. **Additional Note:**
   - The window switcher disappears only if another key is pressed after releasing `Alt` and `Tab`.
   - This issue does not occur if the keys are not remapped (i.e., it works normally and the window switcher disappears upon releasing both keys).

### Additional Information

- It is impossible to take a screenshot while reproducing this issue because using the window switcher and taking a screenshot simultaneously is not feasible. That's why I filmed it on my phone, sorry for that:

https://github.com/user-attachments/assets/b5a7c348-094e-4668-abf3-cd0de41df794



### ✔️ Expected Behavior

- When using `Alt+Tab` with remapped keys, the window switcher should disappear as soon as both `Alt` and `Tab` keys are released, without needing to press any additional keys.
- This behavior should be consistent with how `Alt+Tab` operates without key remapping.


### ❌ Actual Behavior

- When using `Alt+Tab` with remapped keys, the window switcher remains open after both `Alt` and `Tab` keys are released.
- The window switcher only disappears if an additional key is pressed after releasing `Alt` and `Tab`.
- This behavior is particularly inconvenient when using multiple monitors. If working on a secondary monitor, it can be easy to miss the window switcher not closing. Attempting to use `Alt+Tab` again results in cycling through the previous window order, rather than starting from the beginning of the updated list of open windows, leading to unintended window selection.

Attaching the app bug report zip file.
[PowerToysReport_2024-07-24-19-25-52.zip](https://github.com/user-attachments/files/16366450/PowerToysReport_2024-07-24-19-25-52.zip)


### Other Software

_No response_
Repository: go
Issue: testing: TestBenchmarkSubRace failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "testing" && test == "TestBenchmarkSubRace"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8741514157355889617)):

    === RUN   TestBenchmarkSubRace
        testing_test.go:609: C:\b\s\w\ir\x\t\go-build666637562\b1145\testing.test.exe -test.run=^BenchmarkSubRacy$ -test.bench=BenchmarkSubRacy -test.v -test.parallel=2 -test.benchtime=2x: exit status 1
            goos: windows
            goarch: amd64
            pkg: testing
            cpu: Intel(R) Xeon(R) CPU @ 2.20GHz
            BenchmarkSubRacy
            BenchmarkSubRacy/non-racy
            BenchmarkSubRacy/non-racy-16         	       2	       750.0 ns/op
            BenchmarkSubRacy/racy
    ...
                  C:/b/s/w/ir/x/w/goroot/src/testing/benchmark.go:193 +0x19c
              testing.(*B).run1.func1()
                  C:/b/s/w/ir/x/w/goroot/src/testing/benchmark.go:215 +0x7b
            ==================
                testing.go:1399: race detected during execution of test
            --- FAIL: BenchmarkSubRacy/racy
            --- FAIL: BenchmarkSubRacy
            FAIL
        testing_test.go:619: got 1 race reports; want 2
    --- FAIL: TestBenchmarkSubRace (0.04s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: net: TestDialParallelSpuriousConnection failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net" && test == "TestDialParallelSpuriousConnection"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8741507863266319601)):

    === RUN   TestDialParallelSpuriousConnection
        dial_test.go:421: got read tcp4 127.0.0.1:54318->127.0.0.1:54320: read: connection reset by peer; want EOF
    --- FAIL: TestDialParallelSpuriousConnection (138.38s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: vscode
Issue: Ability to set log levels by output channel
Labels: feature-request,log

<!-- ⚠️⚠️ 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 been working on an extensions that utilizes the `OutputChannel` API for logging things into the output view for different log levels such as: `INFO`, `ERROR`, etc...

Each of these loggers output independent information from each other, let's call this logger A and logger B. My feature request is the possibility to allow setting an individual log level at a per logger basis, so for example logger A could have a `DEBUG` level and logger B could have a `TRACE` level logging occur. This could be further enanced by using the set log level (as it works today) if the log level is not specified for that specific logger upon creation.

This is what I envision this API to look like:

```TypeScript
// Case where log level is defined
const outputChannel = vscode.window.createOutputChannel('loggerA', { log: true }, 'DEBUG');

// Case where log level is not defined (will use default log level)
const outputChannel = vscode.window.createOutputChannel('loggerB', { log: true });
```

And even perhaps add a way to update this later with something like:

```TypeScript
outputChannel.setLogLevel('TRACE');
```

For setting these log level a user can perhaps even use this enumerator from VS Code's docs: https://code.visualstudio.com/api/references/vscode-api#LogLevel
Repository: ollama
Issue: Slow Model Loading Speed on macOS System
Labels: bug

### What is the issue?

I am experiencing slow model loading speeds when using Ollama on my macOS system. Here are the specifications of my setup:

macOS Version: 14.5
Processor: M3 Max
Memory: 128GB
Storage: 2TB (with performance on par with the 8TB version)
Ollama version: 0.2.8

Despite having sufficient hardware capabilities, the model loading speed typically hovers around 700MB/s. During the loading process, I do not observe any component (CPU, Disk, Memory, GPU) being fully utilized or experiencing high usage. Could you please help me understand the reason for this bottleneck and suggest any potential solutions or optimizations?

Thank you for your assistance.

### OS

macOS

### GPU

Apple

### CPU

Apple

### Ollama version

0.2.8
Repository: rust
Issue: Cleanup: add named helpers for e.g. `llvm_object` in `run_make_support`
Labels: C-cleanup,T-compiler,A-run-make

Something like

```rs
llvm_objdump().arg("-t")
```

is *completely opaque* when written in rmake.rs to contributors who aren't familiar with llvm-objdump and you have to go read [llvm-objdump docs](https://llvm.org/docs/CommandGuide/llvm-objdump.html) to see that `-t` means "display the symbol table".

We should add named helper methods to `llvm_objdump` for the common flags such as `-t`.
Repository: pytorch
Issue: Drop Connect Layer
Labels: feature,module: nn,triaged

### 🚀 The feature, motivation and pitch

I was reading the Yann LeCun's Drop Connect paper:
[drop connect](https://proceedings.mlr.press/v28/wan13.html)
And didn't find any implementation on the internet.

### Alternatives

So I created my own, here: 
[repository](https://github.com/mr-raccoon-97/drop-connect/tree/main)

The implementation of DropConnect layers is here:
[drop connect implementation](https://github.com/mr-raccoon-97/drop-connect/blob/main/model/dropconnect.py)

But also made an alternative version that disables the weight drops during the evaluation phase, like the dropout.
[batched weight drop](https://github.com/mr-raccoon-97/drop-connect/blob/main/model/batched_dropweight.py)

### Additional context

The are no papers avaliable of the usage of drop connect layers, because there isn't any implementation avaliable on the internet. There are some implementation of weight drop saying they are drop connect, but the don't implement the layers as stated in the paper. 

My solution works, and works well.

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: pytorch
Issue: TCP socket keeps trying IPv6 address and doesn't try IPv4
Labels: oncall: distributed,triaged

### 🐛 Describe the bug

We see the following consistent log message which eventually ends with an error:

```
The IPv6 network addresses of (host, port) cannot be retrieved (gai error: -2 - Name or service not known).
The IPv6 network addresses of (host, port) cannot be retrieved (gai error: -2 - Name or service not known).
The IPv6 network addresses of (host, port) cannot be retrieved (gai error: -2 - Name or service not known).
The IPv6 network addresses of (host, port) cannot be retrieved (gai error: -2 - Name or service not known).
The IPv6 network addresses of (host, port) cannot be retrieved (gai error: -2 - Name or service not known).
The IPv6 network addresses of (host, port) cannot be retrieved (gai error: -2 - Name or service not known).
The IPv6 network addresses of (host, port) cannot be retrieved (gai error: -2 - Name or service not known).
The IPv6 network addresses of (host, port) cannot be retrieved (gai error: -2 - Name or service not known).
The IPv6 network addresses of (host, port) cannot be retrieved (gai error: -2 - Name or service not known).
The IPv6 network addresses of (host, port) cannot be retrieved (gai error: -2 - Name or service not known).
torch.distributed.DistNetworkError: The client socket has timed out after 1800s while trying to connect to (host, port).
```

The intention of this code seems to be to try IPv4 if IPv6 fails: https://github.com/pytorch/pytorch/blob/main/torch/csrc/distributed/c10d/socket.cpp#L785, but IPv4 is never tried and an exception is thrown.

### Versions

PyTorch 2.3

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: deno
Issue: error importing npm:@raydium-io/raydium-sdk-v2
Labels: bug,node resolution

Version: deno 1.45.3+fcd9bbe

deno.json:
```
{
  "nodeModulesDir": true
}
```

bot.js:
```
import * as rayd from 'npm:@raydium-io/raydium-sdk-v2'
```

deno run -A bot.js

```
bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?)
error: Uncaught (in promise) TypeError: (0 , codecs_1.getStringCodec) is not a function
    at Object.<anonymous> (file:///C:/Users/Michele/Desktop/crypto-bot/node_modules/.deno/@solana+spl-token-metadata@0.1.4/node_modules/@solana/spl-token-metadata/lib/cjs/state.js:10:42)
    at Object.<anonymous> (file:///C:/Users/Michele/Desktop/crypto-bot/node_modules/.deno/@solana+spl-token-metadata@0.1.4/node_modules/@solana/spl-token-metadata/lib/cjs/state.js:54:4)
    at Module._compile (node:module:730:34)
    at Object.Module._extensions..js (node:module:744:10)
    at Module.load (node:module:655:32)
    at Function.Module._load (node:module:523:12)
    at Module.require (node:module:674:19)
    at require (node:module:785:16)
    at Object.<anonymous> (file:///C:/Users/Michele/Desktop/crypto-bot/node_modules/.deno/@solana+spl-token-metadata@0.1.4/node_modules/@solana/spl-token-metadata/lib/cjs/index.js:20:14)
    at Object.<anonymous> (file:///C:/Users/Michele/Desktop/crypto-bot/node_modules/.deno/@solana+spl-token-metadata@0.1.4/node_modules/@solana/spl-token-metadata/lib/cjs/index.js:22:4)
```
Repository: godot
Issue: Unexpected behaviour of set_process(false)
Labels: topic:core,documentation

### Tested versions

4.2.stable

### System information

Godot v4.2.2.stable.mono - Ubuntu Core 22 - Wayland - Vulkan (Forward+) - integrated Intel(R) Graphics (ADL GT2) - 12th Gen Intel(R) Core(TM) i5-12500H (16 Threads)

### Issue description

I found out post about the same problem: https://github.com/godotengine/godot/issues/7894
As I understood the answer from [reduz](https://github.com/reduz)
```
We could add an extra check i guess
```
It was considered as bug. Let me know if not, please. 
Issue was closed as completed. 

### Steps to reproduce

I created 2D Scene (Main) and added main.gd:
```gdscript
extends Node2D

var _active = false

func _process(delta):
	print("_process here!")

func _enter_tree():
	set_process(_active)
	print("Parent entered!")
```
Output:
![image](https://github.com/user-attachments/assets/3e537332-919c-4dad-aef6-19eaf5510111)

### Minimal reproduction project (MRP)

[bug.zip](https://github.com/user-attachments/files/16367228/bug.zip)
Repository: godot
Issue: SDF values have significant jitter with moving camera
Labels: bug,topic:rendering,usability,topic:2d

### Tested versions

Reproducible in:
- 4.2 [stable] 
- 4.3 beta 2

### System information

Windows 10, Godot 4.3 beta 2

### Issue description

As you can see in the preview below, the SDF is sampled at a lower resolution than the screen which can cause the values to jitter as the camera moves. This is a fundamental limitation of sampling sdf at a lower resolution of course, but I think the problem can easily be mitigated.

https://github.com/user-attachments/assets/733f65f2-a1b7-4907-a8ae-bb27aaa9f2cb

While increasing the SDF resolution helps reduce the visual jitter, the jittering is still noticeable even at full sdf resolution. Unfortunately, we will always get jittering edges for SDFs on dynamically moving `LightOccluder2D`s, however, the issue should be avoidable for static geometry.

# Suggested Fix

If there was a property or a function exposed in the rendering server which allowed us to offset the sdf sampling positions by a specified x and y, that would allow us to work around this issue, however as far as I know, there is no way to do this, and therefore no way to mitigate this issue.

### Steps to reproduce

Visualize sdf with shader, add static non-moving Occluder2D node, add movement to camera, jittering of sdf values will be apparent.

### Minimal reproduction project (MRP)

Attached is a MRP with all the reproduction steps already done, so the bug should be apparent as soon as the project is run.
[sdf-stutter-bug.zip](https://github.com/user-attachments/files/16367020/sdf-stutter-bug.zip)
Repository: pytorch
Issue: Keep pytorch/pytorch-canary's main branch in sync with pytorch/pytorch's viable strict
Labels: module: ci,triaged,enhancement

Today, the canary repo is kept in sync on an ad-hoc basis.  Let's automate it

The one complicating factor is that there are a couple commits that are pytorch-canary specific and need to be reapplied on top of whatever commits are pulled in from pytorch/pytorch

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: pytorch
Issue: [tracker] Open issue with inline_inbuilt_nn_modules
Labels: triaged,oncall: pt2,module: dynamo

### 🐛 Describe the bug

We are planning to turn on the inline_inbuilt_nn_modules flag to True by default. There are a few hiccups here and there, but we will turn on the flag and fix these issues later. This is the issue to track.



cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
```[tasklist]
### Tasks
- [ ] https://github.com/pytorch/pytorch/issues/130859
- [ ] https://github.com/pytorch/pytorch/issues/131693
- [ ] https://github.com/pytorch/pytorch/issues/131929
- [ ] https://github.com/pytorch/pytorch/issues/132373
- [ ] https://github.com/pytorch/pytorch/issues/132470
- [ ] https://github.com/pytorch/pytorch/issues/132714
- [ ] https://github.com/pytorch/pytorch/issues/132872
```
Repository: flutter
Issue: [Impeller] Screen flickers when frame is canceled during hybrid composition thread merging with AHB swapchains.
Labels: P2,e: impeller,team-engine,triaged-engine

To reproduce, run flutter with impeller enabled on a device that supports AHB swapchains. For this I'm using the wonderous app configured to use HC platform views with the following diff:

```
diff --git a/lib/main.dart b/lib/main.dart
index 67105669..572c8196 100644
--- a/lib/main.dart
+++ b/lib/main.dart
@@ -11,6 +11,9 @@ import 'package:wonders/logic/timeline_logic.dart';
 import 'package:wonders/logic/unsplash_logic.dart';
 import 'package:wonders/logic/wonders_logic.dart';
 import 'package:wonders/ui/common/app_shortcuts.dart';
+import 'package:google_maps_flutter_android/google_maps_flutter_android.dart';
+import 'package:google_maps_flutter_platform_interface/google_maps_flutter_platform_interface.dart';
+
 
 void main() async {
   WidgetsBinding widgetsBinding = WidgetsFlutterBinding.ensureInitialized();
@@ -21,6 +24,14 @@ void main() async {
   // Start app
   registerSingletons();
 
+  // Require Hybrid Composition mode on Android.
+  final GoogleMapsFlutterPlatform mapsImplementation =
+      GoogleMapsFlutterPlatform.instance;
+  if (mapsImplementation is GoogleMapsFlutterAndroid) {
+    // Force Hybrid Composition mode.
+    mapsImplementation.useAndroidViewSurface = true;
+  }
+
   runApp(WondersApp());
   await appLogic.bootstrap();
 
```

As you scroll from the carosel to the view that has the platform view, the screen with flash black. I believe this is because the first frame after merging the threads gets canceled, so we are letting a SurfaceFrame handle die without presenting it. 

https://github.com/flutter/engine/blob/main/shell/platform/android/external_view_embedder/external_view_embedder.cc#L94-L103