sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: puppeteer
Issue: [Feature]: A better/improved Docker Guide
Labels: feature,P3

### Feature description

We have used the current docker guide for puppeteer, and the issue I'm having is for the life of me, I can't get puppeteer to run under a non-root user with the proper sandbox setup.

We launch puppeteer using:
const browser = await puppeteer.launch({ // Launch a "browser"
      args: ['--no-sandbox', '--disable-dev-shm-usage'],
      executablePath: '/usr/bin/google-chrome',
      headless: 'new',                       // For testing only
    });
    
And our docker code follows your docker guide, however we still get the error
 
mkdir: cannot create directory '/nonexistent': Permission denied
touch: cannot touch '/nonexistent/.local/share/applications/mimeapps.list': No such file or directory

The other issues I'm having is understanding what files need to be moved from the build image over to the run image to make sure puppeteer runs smoothly.

I can easily run:
COPY --from=build /usr/bin/google-chrome /usr/bin/google-chrome

but that's not enough to get puppeteer running.

Anyway this guide could be a bit more thorough?
Repository: pytorch
Issue: Type hints on nn.Module.__setattr__ value 
Labels: module: nn,module: typing,triaged

nn.Module has the follwing type hints
`  def __setattr__(self, name: str, value: Union[Tensor, 'Module']) -> None`

although the method actually would work with other types as well, as these are delegated to a` super().__setattr__`

This is overly restrictive and would cause issues when either
 - calling` Module().__setattr__('name','value')` directly or
 - a child of nn.Module implements a __setattr__ and wants to call Module's settattr via super().__setattr__ to set non Tensor/Modules. This instead requires to explicitly object.__setattr__() which is not suitable in a deeper dependency chain where multiple classes might implement some logic on getattr that all should be called. 

I am not sure if these type hints a required or help in any circumstances, can they be relaxed?
(Maybe I am also mistaken and this is actually correct and serves a purpose)
### Versions

pytorch 2.2.1 / current main

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @ezyang @malfet @xuzhao9 @gramster
Repository: ollama
Issue: New Model Request: BioMistral model?
Labels: model request

Hi, 

I wonder if you have any plan to add BioMistral in library? 

Thanks
Repository: TypeScript
Issue: unintended escaped string for hover
Labels: Bug,Help Wanted

### 🔎 Search Terms

"lsp"

### 🕗 Version & Regression Information

version `"typescript": "5.3.3"`


### ⏯ Playground Link

_No response_

### 💻 Code

```ts
// 🦁.ts
export const foo = "bar";

// main.ts
import { bar } from './🦁.ts';
```


### 🙁 Actual behavior

The lsp message shows `Module '"./\uD83E\uDD81.ts"' has no exported member 'bar'.ts(2305)`.

### 🙂 Expected behavior

It should be `Module '"./🦁.ts"' has no exported member 'bar'.ts(2305)`.

### Additional information about the issue

<img width="524" alt="スクリーンショット 2024-02-26 10 11 39" src="https://github.com/microsoft/TypeScript/assets/41257923/7c0a935d-5f09-433c-b8af-3b785411b5bd">
Repository: pytorch
Issue: Softmax plus one for Flash attention
Labels: feature,triaged,needs research,module: sdpa

### 🚀 The feature, motivation and pitch

After noticing some interesting behavior with attention in a little article i wrote [here](https://sweet-hall-e72.notion.site/Exploring-Cross-Attention-maps-in-Diffusion-Models-98a85f552fbe4e62887b896b756177f4?pvs=4): 


I wanted to see if using the method proposed [here](https://www.evanmiller.org/attention-is-off-by-one.html)
could suppress the behavior. However, memory-wise it isn't too feasible to train without flash attention, which is why I was wondering if it possible to implement their method for the kernel used in SDPA

there seems to be a cuda implementation here: https://github.com/softmax1/Flash-Attention-Softmax-N

### Alternatives

Non-flash attention although this is not feasible given token memory constraints

### Additional context

If it doesn't fit into torch, perhaps if you have any guidance on how I could make this change myself?
Repository: opencv
Issue: solvePnP SOLVEPNP_ITERATIVE falsely indicates success in simple test case
Labels: bug,category: calib3d,confirmed

### System Information

OpenCV python version: 4.9.0.80
numpy version: 1.26.4
Operating System / Platform: Windows 11
Python version: 3.9.2

### Detailed description

When using SOLVEPNP_ITERATIVE, solvePnP produces a solution with reprojection error of 4.5e18 pixels yet indicates that the solve was successful.  I would expect either the solution to be reasonably close, or solvePnP should indicate that the solve was not successful.  Specifically, the code below indicates:

```
solvePnP method SOLVEPNP_ITERATIVE produces incorrect results (off by 4.5e+18 pixels)
solvePnP method SOLVEPNP_EPNP produces incorrect results (off by 0.0145 pixels)
solvePnP method SOLVEPNP_SQPNP produces correct results
```

### Steps to reproduce

```python
import math

import cv2  # 4.9.0.80
import numpy as np  # 1.26.4


# Camera makes 1000x1000 images with perfect optical center
mtx = np.array((
    (1000, 0, 500),
    (0, 1000, 500),
    (0, 0, 0)
), dtype=np.float32)

# Camera has no distortion
dist = np.array((0, 0, 0, 0), dtype=np.float32)

# Camera is looking along +Y with +X to the right and +Z up (where "up" = smaller pixel values)
point_mapping = (
    ((0, 0, 0), (500, 500)),
    ((1, 0, 0), (600, 500)),
    ((0, 0, 1), (500, 400)),
    ((-1, 0, 0), (400, 500)),
    ((0, 0, -1), (500, 600)),
    ((0, 2, 0), (500, 500)),
)
objpoints = np.array([m[0] for m in point_mapping], dtype=np.float32)
imgpoints = np.array([m[1] for m in point_mapping], dtype=np.float32)

# A simple, correct solution exists
rvec_correct = np.array((math.pi / 2, 0, 0), dtype=np.float32)
tvec_correct = np.array((0, 0, 10), dtype=np.float32)
imgpoints_correct, _ = cv2.projectPoints(objpoints, rvec_correct, tvec_correct, mtx, dist)
assert np.max(np.abs(np.squeeze(imgpoints_correct) - imgpoints)) < 1e-6, "Simple solution isn't correct after all"

methods = ("SOLVEPNP_ITERATIVE", "SOLVEPNP_EPNP", "SOLVEPNP_SQPNP")
for method in methods:
    # Find camera position & orientation
    ret, rvec_cv2, tvec_cv2 = cv2.solvePnP(objpoints, imgpoints, mtx, dist, flags=getattr(cv2, method))
    assert ret, "solvePnP was unsuccessful"

    # Reproject world points into camera
    imgpoints_cv2, _ = cv2.projectPoints(objpoints, rvec_cv2, tvec_cv2, mtx, dist)
    if np.max(np.abs(np.squeeze(imgpoints_cv2) - imgpoints)) < 1e-6:
        print(f"solvePnP method {method} produces correct results")
    else:
        err = np.linalg.norm(np.squeeze(imgpoints_cv2) - imgpoints, axis=1)
        print(f"solvePnP method {method} produces incorrect results (off by {np.max(err):.3g} pixels)")
```

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: rust
Issue: Tracking Issue for postfix match
Labels: T-lang,C-tracking-issue,S-tracking-impl-incomplete,F-postfix_match

<!--
NOTE: For library features, please use the "Library Tracking Issue" template instead.

Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a
feature from implementation to stabilisation. Make sure to include the relevant
RFC for the feature if it has one. Otherwise provide a short summary of the
feature and link any relevant PRs or issues, and remove any sections that are
not relevant to the feature.

Remember to add team labels to the tracking issue.
For a language team feature, this would e.g., be `T-lang`.
Such a feature should also be labeled with e.g., `F-my_feature`.
This label is used to associate issues (e.g., bugs and design questions) to the feature.
-->

This is a tracking issue for the RFC "Postfix Match" (rust-lang/rfcs#3295).
The feature gate for the issue is `#![feature(postfix_match)]`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [x] Implement the RFC 
- [ ] Get consensus on design, and if we even want this feature
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Formatting for new syntax has been added to the [Style Guide] ([nightly-style-procedure])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[nightly-style-procedure]: https://github.com/rust-lang/style-team/blob/master/nightly-style-procedure.md 
[Style Guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

- **Lifetime extension**
  Method call chains will not lifetime extend their arguments. Match statements, however, are notorious for having lifetime extension. It is currently unclear if promoting these use-cases of match would cause more [subtle bugs](https://fasterthanli.me/articles/a-rust-match-made-in-hell#my-actual-bug), or if it's negligible

- **Postfix macros**
  One thing that was brought up was that it may be possible to implement this with the rust-lang/rfcs#2442 feature. But this feature has not been implemented yet, so that is yet to be seen.

### Implementation history

* #121619
Repository: transformers
Issue: OSError: You are trying to access a gated repo.
Labels: New model

### Model description

I tried to run the model on Colab and successfully logged in using huggingface cli login, but it still reported an error
<img width="534" alt="联想截图_20240226102113" src="https://github.com/huggingface/transformers/assets/83337970/4d3d95a0-98c8-4451-b696-6a70f0d6c7ce">
<img width="1202" alt="联想截图_20240226102157" src="https://github.com/huggingface/transformers/assets/83337970/565471b5-0261-4420-9480-ec99d367b239">


### Open source status

- [ ] The model implementation is available
- [ ] The model weights are available

### Provide useful links for the implementation

_No response_
Repository: godot
Issue: Hot Reload in GDExtension C++ Crashes .gdextension "reloadable = true" flag set
Labels: bug,topic:gdextension,crash

### Tested versions

Produced in Godot 4.2.1-stable with the voxel module.
https://github.com/Zylann/godot_voxel

### System information

Kubuntu Linux 22.04, Ryzen 3950x, AMD Gpu 6600XT, Vulkan

### Issue description

Activating hot reloadable modules, using .gdextension "reloadable = true" causes unpredictable crashes.

May be a similar issue to the following issue based on title, but me using a C++ extension it is not clear to me if they are the same issue: https://github.com/godotengine/godot/issues/87227

I am creating a GDExtension based off a class provided by the Godot_voxel module. It is written in C++ and runs in the modules build, but when adding "reloadable = true" to the .gdextension file godot crashes. The voxel implementation is threaded, so I thought the issue may be similar to issue 87227 above.

I had already been discussing the issue with the Voxel module developer who thought this issue should be passed along, but the setup may be too complex for repeatability.
https://github.com/Zylann/godot_voxel/issues/605


### Steps to reproduce

This is a challenge as it makes use of a threaded module being extended using a GDExtension. It seemed to make sense to report the issue, but it may be a too challenging to reproduce.

I had already been discussing the issue with the Voxel module developer and have posted information regarding stack traces to his issue board.

https://github.com/Zylann/godot_voxel/issues/605

At a high level:
1) clone https://github.com/godotengine/godot.git, git tag "4.2.1-stable"
2) clone https://github.com/Zylann/godot_voxel.git, git tag "v1.1.0"
3) build godot engine with scons adding custom_modules=(godot_voxel directory)
4) this builds the engine with the needed module
5) create a gdextension directory and include godot-cpp.
6) dump api information from the godot custom build into godot-cpp/gdextension directory to pick up the additional modules.
7) Extend VoxelGeneratorScript in C++ to create the GDExtension.
8) Build the extension, add the binary to a godot project.
9) Add the derived generator as a module to a VoxelTerrain object in the editor

At this point it will execute and generate a voxel object.

10) Modifying .gdextension under in the bin directory to use "reloadable = true" causes godot to crash.

Gdb does not consistently generate a backtrace. There appears to be some memory corruption.

### Minimal reproduction project (MRP)

N/A
Repository: tauri
Issue: [bug] window position and visible issue
Labels: type: bug,status: needs triage

### Describe the bug

I wanna make my app show at the top right corner on the primary monitor during startup with the following code snippet.
```
let mut builder = tauri::Builder::default()
    .setup(move |app| {
        let app_handle = app.handle();
        let main_window = tauri::WebviewWindowBuilder::new(app_handle, "main", tauri::WebviewUrl::App("index.html".into()))
            .fullscreen(false)
            .maximizable(false)
            .resizable(false)
            .visible(false)
            .title(app.package_info().name.as_str())
            .inner_size(330.0, 620.0)
            .build()?;
        let primary_monitor = app_handle.primary_monitor()?.unwrap();
        let scale_factor = primary_monitor.scale_factor();
        let screen_width = primary_monitor.size().width as f64 / scale_factor;
        let screen_height = primary_monitor.size().height as f64 / scale_factor;
        let window_size = main_window.outer_size()?;
        let window_width = window_size.width as f64 / scale_factor;
        let window_height = window_size.height as f64 / scale_factor;
        info!("screen_width: {}, screen_height: {}, window_width: {}, window_height: {}", screen_width, screen_height, window_width, window_height);
        main_window.set_position(tauri::LogicalPosition{
            x: screen_width - window_width - 100,
            y: 100,
        })?;
        main_window.show()?;
}
```
But hit two issue:
1. On Windows, if I launch my app by double clicking the executable file through the `File Explorer` on my secondary monitor, the app would display in the middle of my prmiary monitor. (my primary monitor is 3840x2400 with scale of 250%, secondary monitor is 1920x1080 with scale of 100%). It works fine if launched through `File Explorer` on the primary monitor or from start menu. 
2. On MacOS, it seems that even initial `visible` is set to be false, but it is not working. I can see that the window moves from middle to the top right corner during startup.

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.22000 X64
    ✔ WebView2: 121.0.2277.128
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 18.16.0
    - yarn: 1.22.19
    - npm: 9.5.1

[-] Packages
    - tauri [RUST]: 2.0.0-beta.6
    - tauri-build [RUST]: 2.0.0-beta.4
    - wry [RUST]: 0.37.0
    - tao [RUST]: 0.26.0
    - tauri-cli [RUST]: 1.3.1
    - @tauri-apps/api [NPM]: 2.0.0-beta.3
    - @tauri-apps/cli [NPM]: 2.0.0-beta.4

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: deno
Issue: Temporal toLocaleString() causes V8 crash
Labels: bug,upstream

Version: Deno 1.41.0

Running the following line in some machines

```ts
Temporal.PlainDate.from("2024-02-25").toLocaleString();
```

V8 would crash with an error start with the following lines, [download complete stack trace](https://github.com/denoland/deno/files/14399841/deno-temporal-v8-dump.txt).


```bash
#
# Fatal error in , line 0
# Check failed: IsString(*time_zone_obj).
#
```
Repository: next.js
Issue: ESM build with standalone output and custom directory outputs CommonJS code instead of ESM
Labels: bug,Module Resolution

### Link to the code that reproduces this issue

https://github.com/zollf/nextjs-standalone-esm-bug

### To Reproduce

1. Add `"type": "module"` in `package.json` for ESM
2. Add `output: 'standalone'` in next config
3. Rename or add a custom directory to build from
4. Build using custom directory `npm run build custom-dir`
5. Run standalone server `node custom-dir/.next/standalone/custom-dir/server.js`

### Current vs. Expected behavior

When trying to run a standalone server it will result in a reference error:`ReferenceError: require is not defined in ES module scope, you can use import instead`. Upon inspection `server.js` is using CommonJS, not ESM code.

Looking at the build utils this potentially could be the cause:

https://github.com/vercel/next.js/blob/bef716ad031591bdf94058aaf4b8d842e75900b5/packages/next/src/build/utils.ts#L1948-L1950

Our package.json location is one more directory away. 

The expected outcome is for standalone output to be ESM code with a custom directory

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:28:31 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T8112
Binaries:
  Node: 18.17.1
  npm: 9.6.7
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.1.0
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: standalone
```


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

Module resolution (CJS / ESM, module resolving)

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

next build (local)

### Additional context

_No response_
Repository: pytorch
Issue: floating point exception on `torch.fmod` when x is large negative integer and y is `-1`
Labels: module: crash,triaged,actionable

### 🐛 Describe the bug

Here is the code to reproduce the issue:

```
import torch

x = torch.tensor([-9223372036854775808], dtype=torch.int64)
y = torch.tensor([[-1]], dtype=torch.int64)
out = torch.fmod(x, y)
```

Running this code on torch 2.1.0+cu121 will lead to a floating point exception, however, the value of x is within the range of 64-bit integer. 
More interestingly, this issue only occurs when y is -1.


### Versions

Versions of relevant libraries:
[pip3] numpy==1.25.2
[pip3] torch==2.1.0+cu121
[pip3] torchaudio==2.1.0+cu121
[pip3] torchdata==0.7.0
[pip3] torchsummary==1.5.1
[pip3] torchtext==0.16.0
[pip3] torchvision==0.16.0+cu121
[pip3] triton==2.1.0
[conda] Could not collect
Repository: deno
Issue: deno compile doesn't handle node unstable flags
Labels: bug,compile

Version: Deno 1.41.0
```
deno compile --no-check --unstable-sloppy-imports --unstable-bare-node-builtins
```
Running the executable that uses this fails with 
```
error: Module not found:
```

also here is a repo to test it, https://github.com/sigmaSd/helix-gpt/
- use the deno branch 
- compile with 
```
deno compile --no-check --unstable-sloppy-imports --unstable-bare-node-builtins --allow-env src/app.ts
```
- run ./app
it errors with 
```
error: Module not found: file:///home/mrcool/dev/others/helix-gpt/src/deno-compat
```
Repository: PowerToys
Issue: Fullscreen app pinned on top can become unresponsive and prevents using Task Manager to close it.
Labels: Issue-Bug,Product-Always On Top,Needs-Triage

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Always on Top

### Steps to reproduce

I had XYplorer pinned on top in full-screen, it became unresponsive and I couldn't unpin, close, or minimize it.
Ctrl+Alt+Del opened the task manager, but I couldn't access it to close the app as it was hidden behind the other app.

Exiting PowerToys in the tray didn't help, nor did attempting to close the window from the task bar.

### ✔️ Expected Behavior

Possible Solutions:
1) Allow Always On Top to be paused/disabled from the tray icon.
2) Automatically give Task Manager on top status and priority when fullscreen apps use AOT.
3) Ctrl+Alt+Del disables or pauses Always On Top.

### ❌ Actual Behavior

Described above. Log file attached.
[log_2024-02-25.txt](https://github.com/microsoft/PowerToys/files/14401027/log_2024-02-25.txt)


### Other Software

XYplorer
Repository: TypeScript
Issue: Wrong elementwise error location on optional object property that allows arrays too
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

error location elementwise elaboration array optional object

### 🕗 Version & Regression Information

- This is a crash
- This changed between versions ______ and _______
- This changed in commit or PR _______
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
- I was unable to test this on prior versions because _______


### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.5.0-dev.20240225#code/C4TwDgpgBAyglgOwOYBsIHkBOBBTmCGIAPACoB8UAvFCVAD5SYT4AmA9giiDQNoC6AbgBQQ0JCgAFTGwBucFhBbYAxsDaYqUAN5CoUAM6ZlALgPBMiJML2IwAV2AB+U3YQBrBGwDuCYQF9hUXBoAFl8ZQALRAgAYQ4AMzgkUhU1TH0oCAAPYAgEFgypWXlFVPUKah0bBBk2NwhnWEs0LFwCYhIy9LJ-QIVlFHwmKHjXVTgOAwhgOzAU1XUM7Nz8wuk5BSUFzDIACgBKUyqoZSZ8XLDI6NNd5QSk00uohFj75M7t-TJ9qgpa+V6In001mRC0BiMpgARPFppEAKrAzBQgRQWwOUz6cyWKB+Pb7AB0p2YF3Czwgu2OiFq9SOuj0EJMUBhcIiiIgyIANPTqvZgKYAIwABm5ej83L8+2EQA

### 💻 Code

```ts
type SingleOrArray<T> = T | readonly T[];

type ProvidedActor = {
  src: string;
  input?: unknown;
};

type MachineConfig<TActors extends ProvidedActor> = {
  invoke?: SingleOrArray<TActors>;
};

declare function setup<TActors extends ProvidedActor>(): {
  createMachine: (config: MachineConfig<TActors>) => void;
};

setup<{ src: "fetchUser"; input: string }>().createMachine({
  invoke: {
    src: "fetchUser",
    input: 10,
  },
});
```


### 🙁 Actual behavior

`invoke` property gets highlighted

### 🙂 Expected behavior

`input` property should get highlighted as it's the one that it's not correct and it's more specific than `invoke`

### Additional information about the issue

we can observe the error location to change when:
1. we remove optionality from `invoke`
2. we make the provided type argument a union
Repository: excalidraw
Issue: Add importing PDFs
Labels: enhancement

I wish I could at the minimum import it like you can an SVG, but it would be nice if you could open PDFs, or something like that. This is the only web drawing editor thing that is not a pain to use, I wish I could use it for PDFs too.