sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: Deno.dlopen missleading error message / no option to provide lib search paths.
Labels: FFI

## context
I tried to map [libvips](https://github.com/libvips/libvips/releases) to Deno using `ffi`

I have downloaded the binary from [vips-dev-w32-web-8.14.1-static.zip](https://github.com/libvips/build-win64-mxe/releases/download/v8.14.1/vips-dev-w32-web-8.14.1-static.zip)

And try to load `libvips-42.dll` from a local subfolder.

And got the Error: `Uncaught Error: Could not open library: The specified module could not be found.`

After some investigation, `libvips-42.dll` depend on `libgobject-2.0-0.dll`, and try to load it from `C:\ProgramData\chocolatey\lib\deno`

----

1- The error message  `Uncaught Error: Could not open library: The specified module could not be found.` seem like `libvips-42.dll` was not found.

2- how can I force Deno to look for the lib  in the correct folder (`libvips-42.dll` and `libgobject-2.0-0.dll` are in the same directory).

3- on linux using an `apt-get install libvips` works out of the box.

----

## sample code:

```typescript
import { join } from "https://deno.land/std@0.172.0/path/mod.ts";
let libSuffix = "";
switch (Deno.build.os) {
  case "windows": libSuffix = "dll";  break;
  case "darwin":  libSuffix = "dylib";break;
  default:        libSuffix = "so"; break;
}

const libFileName = `libvips-42.${libSuffix}`;
const libPath = join('vips-dev-8.14','bin', libFileName);
// ubuntu default path: '/usr/lib/x86_64-linux-gnu/libvips.so.42'
// const libPath = '/usr/lib/x86_64-linux-gnu/libvips.so.42'
const stats = Deno.statSync(libPath);
console.log(`Stats of lib Pass, its size is: ${(stats.size/1042).toFixed(1)} KB`);
const lib = new URL(libPath, import.meta.url);
console.log(`loading ${lib}`)
const dylib = Deno.dlopen(
    lib,
  {
    vips_init: {parameters: ["buffer"], result: "i32"},
    vips__open: { parameters: ["buffer", "i32", "i32"], result: "pointer" },
    // char *vips__file_read( FILE *fp, const char *name, size_t *length_out );
     vips__file__read: { parameters: ["pointer", "buffer", "buffer"], result: "pointer" }
  } as const,
);
console.log('Try to init libvips');
const api_name = new TextEncoder().encode("vipsTest");
const result = dylib.symbols.vips_init(api_name); // 69
console.log(`vips_init return ${result}`);
```
Repository: material-ui
Issue: Codemod to migrate Box system props to sx?
Labels: docs,ready to take,support: docs-feedback

### Duplicates

- [X] I have searched the existing issues

### Related page

https://mui.com/material-ui/migration/v5-component-changes/

### Kind of issue

Unclear explanations

### Issue description

The breaking changes for the `Box` component include a section called "✅ Apply sx API". My impression is that the check box indicates that this can be done with a codemod, which would be awesome. However, I can't find a codemod (from the list [here](https://github.com/mui/material-ui/blob/master/packages/mui-codemod/README.md)) that seems to do this. The [`box-borderradius-values`](https://github.com/mui/material-ui/blob/master/packages/mui-codemod/README.md#box-borderradius-values) codemod says that it does this, but the code changes shown don't match that claim. After running that codemod, it was clear to me that it does not do the migration to `sx`. I couldn't find a codemod outside of that that mentions anything about converting the system props to `sx`, but it would be great if one exists.

Moving from system props to sx is a big change in my case, with 450+ instances of `Box` in the relatively small codebase I'm working on. A codemod would make such a change much more feasible than making these changes manually. It would be great if the docs could provide more clarity on which codemod should be used. 

### Context 🔦

I'm working on converting an MUI v4 project to MUI v5. I saved converting the system props to sx for later in the process because I knew it would be a big change, but not necessarily a hard change if a codemod is available. I ran into this issue while trying to determine how to apply just that change.
Repository: godot
Issue: Vulkan: Metallic materials appear black in screen-space reflections
Labels: enhancement,topic:rendering,topic:3d

### Godot version

4.0 Beta 13

### System information

Windows 11, Vulkan, GTX 1050 Ti 527.56

### Issue description

Objects with Metalic set to 1 appear Black in Screen Space Reflections, Unlike Objects with Metalic set to 0

### Steps to reproduce

Turn on SSR
Get a Reflective Surface to see Reflections
Make an Object that is Reflected, and switch between Metalic 0 and 1, and observe the results

### Minimal reproduction project

N/A
Repository: angular
Issue: Double slash `templateUrls` should not be allowed
Labels: area: compiler

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

compiler-cli

### Is this a regression?

Yes

### Description

It is apparently possible to write a component using a leading `//` in a `templateUrl` like so:

```typescript
// path/to/my/component/my-component.ts

@Component({
    selector: 'my-component',
    templateUrl: '//path/to/my/component/my-component.html',
})
class MyComponent {}
```

```html
<!-- path/to/my/component/my-component.html -->
<div>Hello, World!</div>
```

This shouldn't be allowed as it's not a valid path. In particular this looks like a Bazel path, which makes it seem intentional when it really isn't.

@devversion [investigated this](https://github.com/angular/components/pull/19320#discussion_r435515440) a little while ago, and it does seem to be unintentionally supported. There are a handful of usages in google3, but mostly in experimental directories. It likely would not be a difficult migration. We should also clean up [this code path](http://go/build-cleaner-ngc-leading-slashes) in Build Cleaner.

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

_No response_

### Please provide the exception or error you saw

_No response_

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

_No response_

### Anything else?

_No response_
Repository: flutter
Issue: [path_provider] Completely rethink the path_provider API
Labels: c: new feature,p: path_provider,package,team-ecosystem,P2,triaged-ecosystem

The API for `path_provider` has a number of significant issues:
- It was design before federation existed, so platform-specific paths (like `getExternalCacheDirectories`, which is highly Android-specific in practice) are mixed in with abstractions in the app-facing API.
- Some of the APIs were designed for Android APIs that have since been deprecated, and the underlying implementation changed, creating some confusing naming.
- The APIs are almost all pre-desktop, so tend to be mobile-centric.
- The desktop implementation of the documents directory (a widely-used API) is, essentially, [wrong](https://github.com/flutter/flutter/issues/77628), and we can't fix it without a breaking change.

The package's API would benefit from being redesigned from scratch. We should:
- Audit all of the existing APIs and open requests for new APIs.
- Make a matrix of all the APIs that it makes sense to support, and what platforms they make sense on.
- Decide what high-level abstractions we want core functionality for (in particular taking a look at the user-created vs. app-created-but-expensive vs app-created-and-easily purgeable, which we have as distinctions right now but in a somewhat platform-fragmented way, and not well named as abstractions).
- Create a two-tiered API system, with common abstractions in `path_provider` and platform-specific things in `path_provider_*`, with clear docs in the app-facing package about the existence of the latter, with links to implementation package readmes as examples.

Removing APIs from path_provider would be extremely disruptive as it's such a foundational plugin in the package ecosystem, but we can deprecate the old APIs and create a clean set of new APIs, like we did with `url_launcher`. That way we don't have to do it as a breaking change, so everyone in the ecosystem can switch to the new APIs gradually, without creating a lot of transitive version conflict problems.
Repository: go
Issue: sync: `sync.Mutex.*` escape `m *Mutex` argument
Labels: Performance,NeedsInvestigation,compiler/runtime

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19.5 linux/amd64

</pre>

### Does this issue reproduce with the latest release?

Yes as well as current master (2e792a8295d7c7f082cf2e3b163a3d4d30b6df7e).

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/hugo/.cache/go-build"
GOENV="/home/hugo/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/hugo/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/hugo/go"
GOPRIVATE=""
GOPROXY="direct"
GOROOT="/home/hugo/Documents/Scripts/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/hugo/Documents/Scripts/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19.5"
GCCGO="gccgo"
GOAMD64="v3"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3304808272=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

I have some type that do lazy initialization of some state, for that I use `sync.Once`, however that force my object to leak and prevents stack allocations where I use this object in a non leaky way:
Here is some minimal repro `go build -gcflags="-m" a.go`:
```go
package a

import (
	"sync"
	"fmt"
)

type A struct {
	o sync.Once
	v int
}

func (a *A) init() {
	a.o.Do(func() {
		a.v = 42
	})
}

func (a *A) Print() {
	a.init()
	fmt.Println(a.v)
}

func main() {
	var a A
	a.Print()
}
```

### What did you expect to see?

```
# command-line-arguments
./a.go:14:8: inlining call to sync.(*Once).Do
./a.go:14:9: can inline (*A).init.func1
./a.go:21:13: inlining call to fmt.Println
./a.go:24:6: can inline main
./a.go:13:7: leaking param: a
./a.go:14:9: func literal does not escape
./a.go:19:7: leaking param: a
./a.go:21:13: ... argument does not escape
./a.go:21:15: a.v escapes to heap
./a.go:25:6: moved to heap: a
```

### What did you see instead?

```
# command-line-arguments
./a.go:14:8: inlining call to sync.(*Once).Do
./a.go:14:9: can inline (*A).init.func1
./a.go:21:13: inlining call to fmt.Println
./a.go:24:6: can inline main
./a.go:13:7: a does not escape
./a.go:14:9: func literal does not escape
./a.go:19:7: a does not escape
./a.go:21:13: ... argument does not escape
./a.go:21:15: a.v escapes to heap
```

---
Depends on #16241 (note that fixing #16241 wont fully fix the problem here but is required).
Repository: pytorch
Issue: Major bug in Transformers' masks
Labels: high priority,module: nn,triaged,module: correctness (silent)

### 🐛 Describe the bug

In torch.nn.functional, line 5174 in current code:
![image](https://user-images.githubusercontent.com/4967417/213253672-3dfd0784-8b4c-4513-b1f0-d14a9a964612.png)

`attn_mask = attn_mask.masked_fill(key_padding_mask, float("-inf"))`

Fills `-inf` value wherever `key_padding_mask` is True. However, `key_padding_masks` actually contains -inf values instead of True values. So the padding mask is actually ignored. Replacing by:

`attn_mask = attn_mask.masked_fill(key_padding_mask < 0, float("-inf")`

Gives the correct expected mask.



### Versions

Current github code.  (master branch, Jan 18, 2023)

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @bhosmer @cpuhrsch @erichan1 @drisspg @saketh-are
Repository: flutter
Issue: Cannot run headless engine on Linux
Labels: c: new feature,engine,platform-linux,P3,team-engine,triaged-engine

The Flutter Linux API doesn't expose a function to run a headless flutter engine. The Flutter Linux API exposes the function to create a headless engine, but not to run it.

On Linux, the function to create a headless engine is `fl_engine_new_headless(project)` in file `shell/platform/linux/public/flutter_linux/fl_engine.h`. This function creates the engine, but doesn't run it. There doesn't seem to be a public function to run the headless engine. The private function `fl_engine_start(engine, ...)` in `fl_engine_private.h` is not publicly accessible.

On macOS, you can create a headless engine with `FlutterEngine.init(name, project, allowHeadlessExecution)` and then run it with `FlutterEngine.run(withEntrypoint)`.

On Windows, you can create a headless engine with `FlutterEngine(project)` and run it with `FlutterEngine.Run()`.

Is there a way to run a headless engine on Linux?
Repository: flutter
Issue: [Web] Accessibility focus ring disappears when it gets enabled in Chrome.
Labels: a: accessibility,platform-web,f: focus,P2,customer: huggsy (g3),team-web,triaged-web

Internal: b/292548400

Accessibility focus ring doesn't show up if there is no element on the page with `autofocus` set. (related issue: flutter/flutter#118651) The used gets stuck, and they have to go outside of the web content and come back in order to get the focus ring to appear.

## Steps to Reproduce


1. Run sample code on Chrome on desktop
2. Enable accessibility
3. Navigate to the next element using VoiceOver shortcuts.

**Expected results:** The first element in the page gets focused.

**Actual results:** The accessibility ring doesn't show up. The user can't navigate using VoiceOver unless exit web content and come back.

<details>
<summary>Code sample</summary>


```
void main(){
  runApp(const MyApp());
}

class MyApp extends StatefulWidget {
  const MyApp({super.key});

  @override
  State<StatefulWidget> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  @override
  Widget build(BuildContext context) => MaterialApp(
        home: Center(
          child: Column(
            children: [
              TextButton(
                onPressed: () {},
                child: const Text('Text 1'),
              ),
              TextButton(
                onPressed: () {},
                child: const Text('Text 2'),
              ),
              TextButton(
                onPressed: () {},
                child: const Text('Text 3'),
              ),
              TextButton(
                onPressed: () {},
                child: const Text('Text 4'),
              ),
              TextButton(
                onPressed: () {},
                child: const Text('Text 5'),
              ),
              TextButton(
                onPressed: () {},
                child: const Text('Text 6'),
              ),
            ],
          ),
        ),
      );
}
```

</details>
Repository: flutter
Issue: iOS obscureText input security features
Labels: a: text input,c: new feature,platform-ios,a: fidelity,c: proposal,P3,team-ios,triaged-ios

## Use case

It seems that since probably iOS 13+ the system actively protects users from showing obscured text like passwords and related stuff like keyboards in screenshots, recordings, screen sharing etc. I could not find some official paper with specifications, but from testing and sources like https://www.reddit.com/r/iphone/comments/eqox55/if_you_go_into_your_passwords_and_try_to/ (screenshot), https://discussions.apple.com/thread/251035283 (video), https://github.com/flutter/flutter/issues/116777, etc. I figured out:

for screenshots, recording, screen sharing on iOS the apps while obscureText=true:
1. hide keyboards
2. hide content of obscureText (passwords) inputs
3. immediately when the state of the input changes (aka user clicked on "eye" icon etc), it switches

This works for all native apps I tested including settings, Twitter, Instagram, ...

It seems that Flutter only supports the 1. thing, aka keyboard is hidden while.

## Proposal

Explore more about these features, implement hiding of text field content on these occasions and propagate the changes of obscureText.
Repository: PowerToys
Issue: add folders to File Locksmith
Labels: Needs-Triage

### Description of the new feature / enhancement

File Locksmith shows when a file is locked, but not a folder. It would also be nice to be able to determine what is using a folder, especially an empty one that cannot be deleted.

### Scenario when this would be used?

I have an empty folder but cannot delete it because some unknown process is using it. Instead of rebooting to resolve, I would like File Locksmith to find the process so I can kill it and delete the folder.

Essentially, this is the same use case as a locked file, but with a folder.

### Supporting information

_No response_
Repository: godot
Issue: [4.0-beta13] Calling popup from _ready() do nothing
Labels: bug,topic:gui

### Godot version

4.0 Beta13

### System information

Ubuntu 22.10

### Issue description

Call PopupPanel.popup() (or popup_centered()) in _ready() function of base control 
Expected result:
    Popup shown
Actual result:
    Popup not shown

Works correctly in 3.5.1

Same call works if it called from _process or other functions, like signal from button.

### Steps to reproduce

func _ready():
     $PopupPanel.popup_centered() #simple popup don't work too


### Minimal reproduction project

[popup_test.zip](https://github.com/godotengine/godot/files/10450178/popup_test.zip)
Repository: flutter
Issue: [camera] Modify availableCameras() to use CameraInfo.getLensFacing()
Labels: c: new feature,platform-android,p: camera,package,c: proposal,P2,c: tech-debt,team-android,triaged-android

### Overview
The availableCameras() method was implemented before lens facing info was exposed in the CameraX `CameraInfo` class. There is an [upcoming change](https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:camera/camera-core/src/main/java/androidx/camera/core/CameraInfo.java;l=207?q=file:androidx%2Fcamera%2Fcore%2FCameraInfo.java%20class:androidx.camera.core.CameraInfo&ss=androidx%2Fplatform%2Fframeworks%2Fsupport) to add a method that returns this lens facing info. When this change is available we should make use of it, as it is a better solution to determining the lens facing info than what we currently have.
Repository: go
Issue: proposal: time: make UnmarshalText, UnmarshalJSON enforce strict RFC 3339 semantics
Labels: Proposal

Work for #54580 made RFC3339 parsing adhere more strictly to the RFC. This was treated as a bug fix instead of a proposal, but we have evidence that it breaks at least some tests in the AWS SDK, so we've rolled it back for Go 1.20.

This new issue proposes to roll the change forward for Go 1.21, disabled by GODEBUG=timerfc3339strict=0. Thanks to #56986, this will mean that Go programs with 'go 1.20' or earlier in their go.mod files will get the lax parsing by default. Only modules that say 'go 1.21' or later will get the strict parser.
Repository: flutter
Issue: [flutter_tools] `flutter run` logs a git error to STDERR when app isn't git project
Labels: tool,a: annoyance,P3,team-tool,triaged-tool

```
~/git/tmp/delete_me_flutter$ flutter run -d linux
This application does not support sound null-safety (its language version is 2.11).
To build this application, you must provide the CLI flag --no-sound-null-safety. Dart 3 will only
support sound null safety, see https://dart.dev/null-safety.
~/git/tmp/delete_me_flutter$ flutter run -d linux --no-sound-null-safety
Launching lib/main.dart on Linux in debug mode...
fatal: not a git repository (or any of the parent directories): .git
Building Linux application...
Syncing files to device Linux...                                   386ms

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).

Running without sound null safety ⚠️
Dart 3 will only support sound null safety, see https://dart.dev/null-safety

An Observatory debugger and profiler on Linux is available at:
http://127.0.0.1:36037/7-kXLgw0gtY=/
The Flutter DevTools debugger and profiler on Linux is available at:
http://127.0.0.1:9100?uri=http://127.0.0.1:36037/7-kXLgw0gtY=/
```

Here is the relevant snippet of the verbose logs:

```
[   +7 ms] Building Linux application...
[   +3 ms] executing: [build/linux/x64/debug/] cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DFLUTTER_TARGET_PLATFORM=linux-x64 /home/fujino/git/tmp/delete_me_flutter/linux
[  +53 ms] -- Configuring done
[        ] -- Generating done
[  +68 ms] -- Build files have been written to: /home/fujino/git/tmp/delete_me_flutter/build/linux/x64/debug
[   +5 ms] executing: ninja -C build/linux/x64/debug install
[  +32 ms] fatal: not a git repository (or any of the parent directories): .git
[   +1 ms] ninja: Entering directory `build/linux/x64/debug'
```

It seems like `ninja -C build/linux/x64/debug install` is triggering the git call?

This is a counter app from templates, and grepping my project directory, I see no references to git other than a CMAKE log which has the same error as above.
Repository: PowerToys
Issue: Drag and drop files onto Power Rename window
Labels: Needs-Triage

### Description of the new feature / enhancement

Be able to add files to power rename window by dragging from windows explorer and dropping onto power rename window.

These two things are needed.
1. Clear files and folders list from power rename
2. Drag and drop files and folders from windows explorer to power rename window
3. Provide a button to browse and select files and folders to add to power rename

### Scenario when this would be used?

Right now, after using power rename to rename files, power rename must be closed and called up again from the right click option in windows explorer to rename another set of files. It is time consuming to close and open power rename for renaming different set of files.

### Supporting information

_No response_