sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Unexpected position rounding in viewport coordinates
Labels: bug,topic:rendering

### Tested versions

v4.2.stable.official [46dc27791]

### System information

Godot v4.2.stable - Windows 10.0.19045 - GLES3 (Compatibility) - NVIDIA GeForce GTX 960 (NVIDIA; 31.0.15.3623) - AMD Ryzen 5 2600 Six-Core Processor (12 Threads)

### Issue description

Not sure this is intended behavior for some corner cases, but it seems the float coordinates do not round properly to viewport pixel coordinates.

I created a demo where I placed a number of 1x1 sprites with different x values in viewport mode:
![image](https://github.com/godotengine/godot/assets/16470072/8e69caa6-5d08-42b6-a111-04ebdbc65604)

The pixels on the right are just for orientation to gauge the height of the pixels on the left.

* The x-coordinates in green are as I would expect them (rounded to get the int coordinate). 
* The x-coordinates in red are not expected under any rounding scheme that I could imagine.
* The x-coordinates in yellow depends on the definition of how the rounding should be done, but it looks inconsistent.

Two questions:

1) Are the red values like this on purpose or is this a bug?
2) What about the yellow boundary case? If we apply regular rounding then the top case would be correct (`-0.5 -> -1px`) but the bottom one would be incorrect: `0.5 -> 1px`). 

### Steps to reproduce

I attached an MRP that reproduces the image above

### Minimal reproduction project (MRP)

Update: Fixed MRP
[pixel_grid.zip](https://github.com/godotengine/godot/files/13853182/pixel_grid.zip)
Repository: opencv
Issue: imgcodecs: Support Quite OK Image format(QOI)
Labels: feature

### Describe the feature and motivation

Motivation
------------
Quite OK Image format ( ".qoi" ) is the faster lossless compression format.

Reference implementation is released with MIT license.
Details is https://github.com/phoboslab/qoi 

I tried to support QOI encoder/decoder in imgcodecs.
It seems to be faster than libpng about 3x.

Test result
------------
Test result on i7-4790S (VMware, Ubuntu 23.10)

- Image is 3840x2160x3
- QOI(System) is used with apt-package.
- QOI(Modified) is custom version, which is contained into 3rdparty.

| Format | Method | mean time(ms) | Comment |
|:-:|:-:|-:|-:|
| PNG           | Decode |  74.14 | x1.0 |
| QOI(System)   | Decode |  22.59 | x3.3 |
| QOI(Modified) | Decode |  22.59 | x3.3 |
| PNG           | Encode | 108.79 | x1.0 |
| QOI(System)   | Encode |  29.86 | x3.6 |
| QOI(Modified) | Encode |  24.05 | x4.5 |

Limitation
-----------
- QOI doesn't support single channel image(it supports only CV_8UC3 or CV_8UC4)
- QOI Reference implementation seems no version information.

### Additional context

```plaintext
QOI(System)
[ RUN      ] CodecsCommon.Decode/6, where GetParam() = (1, 3840x2160, ".png")
[ PERFSTAT ]    (samples=100   mean=74.48   median=74.35   min=73.78   stddev=0.55 (0.7%))
[       OK ] CodecsCommon.Decode/6 (7643 ms)
[ RUN      ] CodecsCommon.Decode/7, where GetParam() = (1, 3840x2160, ".qoi")
[ PERFSTAT ]    (samples=100   mean=22.59   median=22.55   min=21.28   stddev=0.29 (1.3%))
[       OK ] CodecsCommon.Decode/7 (2384 ms)
[ RUN      ] CodecsCommon.Encode/6, where GetParam() = (1, 3840x2160, ".png")
.
[ PERFSTAT ]    (samples=100   mean=107.40   median=107.06   min=105.98   stddev=0.92 (0.9%))
[       OK ] CodecsCommon.Encode/6 (10919 ms)
[ RUN      ] CodecsCommon.Encode/7, where GetParam() = (1, 3840x2160, ".qoi")
[ PERFSTAT ]    (samples=100   mean=29.86   median=29.84   min=29.55   stddev=0.16 (0.5%))
[       OK ] CodecsCommon.Encode/7 (3078 ms)

QOI(Modified)
[       OK ] CodecsCommon.Decode/5 (136 ms)
[ RUN      ] CodecsCommon.Decode/6, where GetParam() = (1, 3840x2160, ".png")
[ PERFSTAT ]    (samples=100   mean=74.14   median=74.04   min=73.42   stddev=0.46 (0.6%))
[       OK ] CodecsCommon.Decode/6 (7602 ms)
[ RUN      ] CodecsCommon.Decode/7, where GetParam() = (1, 3840x2160, ".qoi")
[ PERFSTAT ]    (samples=100   mean=22.59   median=22.61   min=21.42   stddev=0.22 (1.0%))
[       OK ] CodecsCommon.Decode/7 (2375 ms)

[ RUN      ] CodecsCommon.Encode/6, where GetParam() = (1, 3840x2160, ".png")
.
[ PERFSTAT ]    (samples=100   mean=108.79   median=108.76   min=106.51   stddev=0.71 (0.7%))
[       OK ] CodecsCommon.Encode/6 (11055 ms)
[ RUN      ] CodecsCommon.Encode/7, where GetParam() = (1, 3840x2160, ".qoi")
[ PERFSTAT ]    (samples=100   mean=24.05   median=23.96   min=23.69   stddev=0.24 (1.0%))
[       OK ] CodecsCommon.Encode/7 (2486 ms)

```
Repository: rust
Issue: Misleading "`match` arms have incompatible types" when match expression used in unimplemented operation
Labels: A-type-system,A-diagnostics,T-compiler,D-confusing,T-types

### Code

```Rust
pub struct Instant(chrono::NaiveDateTime);

pub fn example() {
    use std::ops::Bound;
    use std::ops::RangeBounds;

    let hours = Instant(chrono::NaiveDateTime::MIN)..=Instant(chrono::NaiveDateTime::MAX);

    let total_hours = match hours.end_bound() {
        Bound::Included(a) => a,
        _ => unreachable!(),
    } - match hours.start_bound() {
        Bound::Included(a) => a,
        _ => unreachable!(),
    };
}
```


### Current output

```Shell
error[E0308]: `match` arms have incompatible types
  --> src/lib.rs:22:14
   |
20 |       } - match hours.start_bound() {
   |  _________-
21 | |         Bound::Included(a) => a,
   | |                               - this is found to be of type `&Instant`
22 | |         _ => unreachable!(),
   | |              ^^^^^^^^^^^^^^ expected `&Instant`, found `!`
23 | |     };
   | |_____- `match` arms have incompatible types
   |
   = note: expected reference `&Instant`
                   found type `!`
   = note: this error originates in the macro `$crate::panic::unreachable_2021` which comes from the expansion of the macro `unreachable` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0308`.
```


### Desired output

```Shell
error[E0369]: cannot subtract `&Instant` from `&Instant`
   --> src/lib.rs:20:7
    |
20  |    } - match hours.start_bound() {
    |      ^ no implementation for `&Instant - &Instant`
    |
note: an implementation of `Sub` might be missing for `Instant`
   --> src/lib.rs:9:1
    |
9   | pub struct Instant(chrono::NaiveDateTime);
    | ^^^^^^^^^^^^^^^^^^ must implement `Sub`
note: the trait `Sub` must be implemented
   --> /home/lily/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/arith.rs:184:1
    |
184 | pub trait Sub<Rhs = Self> {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0369`.
```


### Rationale and extra context

The error goes away if `std::ops::Sub` is implemented for `&Instant`

### Other cases

```Rust
Output is identical on latest stable, beta, and nightly toolchains
```


### Anything else?

I think this might be related to [this issue](https://github.com/rust-lang/rust/issues/24157) (actually I initially thought it was the same, but that issue appears to have been fixed in the latest beta and nightly releases, while this has not).
Repository: PowerToys
Issue: DisplayFusion Breaks WindowWalker
Labels: Issue-Bug,Product-PowerToys Run,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.76.2

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

* Have [Binary Fortress' DisplayFusion](https://www.displayfusion.com/) installed, with multi-monitor taskbar enabled
* Have PowerToys installed, with PowerToys Run and WindowWalker enabled
* Activate PowerToys run and attempt to use WIndowWalker with `<`

### ✔️ Expected Behavior

Results matching entered text to be displayed

### ❌ Actual Behavior

No results displayed

### Other Software

DisplayFusion Pro 10.1.2
Repository: go
Issue: x/crypto/acme/autocert: handle short cert lifetimes
Labels: Proposal,Proposal-Accepted,Proposal-Crypto,FixPending

### Go version

n/a (x/crypto v0.17.0, latest at time of writing)

### Output of `go env` in your module/workspace:

```shell
n/a
```


### What did you do?

Use autocert with step-ca as ACME server (https://smallstep.com/docs/step-ca/) for internal testing. I created an acme.Client with a DirectoryURL pointing to step-ca, but I did not change autocert.Manager.RenewBefore.

### What did you see happen?

Autocert retrieved a certificate, so that is working as intended.

However, autocert immediate starts and keeps refreshing the certificate. That's because the default RenewBefore is 30 days, which is sensible for Let's Encrypt's 90 day certificate validity period. However, step-ca hands out short-lived certificates valid for 1 day. So when a new certificate is retrieved, it is refreshed immediately, ad infinitum.

### What did you expect to see?

No refresh loop.

Of course, I should have set autocert.Manager.RenewBefore to match the default 1 day certificate validity period of a new step-ca instance. That would have prevented this problem. However, I hadn't made RenewBefore configurable in my application, so instead I changed the step-ca config to issue certificates with a lifetime of 31 days. I suspect more people could run into this when configuring alternative ACME providers in the future.

I think it would be helpful to change the behavior of a zero RenewBefore value. Instead of using 30 days, we can set the time at which to renew to 2/3 of the certificate validity period. For Let's Encrypt, that would still be 30 days before expiration. For a 1 day certificate, it would be 8 hour before the expiration. If a certificate is valid for 12 months, it would be at 4 months before expiration (which feels like it may be too early, but not harmful, and also not likely: one of the advantages of ACME is enabling shorter-lived certificates, desirable due to revocation issues).

At the very least, we should probably add a check to not renew an issued certificate immediately. E.g. have a minimum "next refresh delay" of 1 hour.

I can make a CL if there is any interest in the idea.
Repository: stable-diffusion-webui
Issue: [Bug]: launch.py
Labels: bug-report

### Checklist

- [x] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [x] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [x] The issue exists in the current version of the webui
- [X] The issue has not been reported before recently
- [x] The issue has been reported before but has not been fixed yet

### What happened?


![Zrzut ekranu 2024-01-07 101723](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/154015567/6cc47729-0a6f-42b0-b522-e1401d26203c)


### Steps to reproduce the problem

I don't know how to do what

### What should have happened?

I'm seeing these errors and I don't know what to do

### What browsers do you use to access the UI ?

_No response_

### Sysinfo

@echo off

set PYTHON=
set GIT=
set VENV_DIR=
set COMMANDLINE_ARGS=--skip-torch-cuda-test --autolaunch --skip-version-check

call webui.bat


### Console logs

```Shell
Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]
Version: v1.7.0
Commit hash: cf2772fab0af5573da775e7437e6acdca424f26e
Launching Web UI with arguments: --skip-torch-cuda-test --autolaunch --skip-version-check
Traceback (most recent call last):
  File "C:\Users\urbus\Desktop\ai ;)\stable-diffusion-webui\launch.py", line 48, in <module>
    main()
  File "C:\Users\urbus\Desktop\ai ;)\stable-diffusion-webui\launch.py", line 44, in main
    start()
  File "C:\Users\urbus\Desktop\ai ;)\stable-diffusion-webui\modules\launch_utils.py", line 460, in start
    import webui
  File "C:\Users\urbus\Desktop\ai ;)\stable-diffusion-webui\webui.py", line 13, in <module>
    initialize.imports()
  File "C:\Users\urbus\Desktop\ai ;)\stable-diffusion-webui\modules\initialize.py", line 14, in imports
    import torch  # noqa: F401
  File "C:\Users\urbus\Desktop\ai ;)\stable-diffusion-webui\venv\lib\site-packages\torch\__init__.py", line 133, in <module>
    raise err
OSError: [WinError 126] Nie można odnaleźć określonego modułu. Error loading "C:\Users\urbus\Desktop\ai ;)\stable-diffusion-webui\venv\lib\site-packages\torch\lib\caffe2_nvrtc.dll" or one of its dependencies.
Press any key to continue . . .
```


### Additional information

Help :(
Repository: next.js
Issue: App dir: notFound() in metadata is ignored with page.tsx
Labels: bug

### Link to the code that reproduces this issue

https://github.com/steebchen/nextjs-repro-metadata-404

### To Reproduce

1. clone https://github.com/steebchen/nextjs-repro-metadata-404
2. pnpm install
3. pnpm build && pnpm start
4. curl http://localhost:3000/poll/asdf -> returns 404 correctly -> ✅
5. curl http://localhost:3000/user/1 -> returns 200 even with notFound() -> ❌

### Current vs. Expected behavior

I expected the /user/[id] route (aka the `user/[id]/page.tsx` file) to also return a 404, even with streaming enabled, because `notFound` is returned in `generateMetadata()`.

The generateMetadata function looks like this for both routes:

```
export async function generateMetadata() {
  return notFound()
}
```

### 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: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:53:18 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6000
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.19
  pnpm: 8.10.0-0
Relevant Packages:
  next: 14.0.5-canary.42
  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)

App Router

### Which stage(s) are affected? (Select all that apply)

next start (local)

### Additional context

_No response_
Repository: rust
Issue: E0716 proposes `let` binding to invalid places in the code
Labels: A-diagnostics,T-compiler,D-incorrect

### Code

```Rust
use async_trait::async_trait; // async-trait 0.1.76;
struct A;

#[async_trait]
pub trait Trait1 {
    async fn func() -> ();
}

#[async_trait]
impl Trait1 for A {
    async fn func() -> () {
        let p = std::convert::identity(&("".to_string()));
        let _q = p;
    }
}
```


### Current output

```Shell
error[E0716]: temporary value dropped while borrowed
  --> src/lib.rs:12:41
   |
12 |         let p = std::convert::identity(&("".to_string()));
   |                                         ^^^^^^^^^^^^^^^^ - temporary value is freed at the end of this statement
   |                                         |
   |                                         creates a temporary value which is freed while still in use
13 |         let _q = p;
   |                  - borrow later used here
   |
help: consider using a `let` binding to create a longer lived value
   |
11 ~     async fn func() -> () let binding = ("".to_string());
12 ~     {
13 ~         let p = std::convert::identity(&binding);
   |
```


### Desired output

```Shell
...

help: consider using a `let` binding to create a longer lived value
   |
11 ~     async fn func() -> ()
12 ~     {
13 ~         let binding = ("".to_string());
14 ~         let p = std::convert::identity(&binding);
   |
```


### Rationale and extra context

_No response_

### Other cases

_No response_

### Rust Version

```Shell
local environment

rustc 1.75.0 (82e1608df 2023-12-21)
binary: rustc
commit-hash: 82e1608dfa6e0b5569232559e3d385fea5a93112
commit-date: 2023-12-21
host: x86_64-unknown-linux-gnu
release: 1.75.0
LLVM version: 17.0.6

I have confirmed that this issue also occurs in Rust Playground.

- Stable channel: 1.75.0
- Beta channel: 1.76.0-beta.1 (2023-12-21 0e09125c6c3c2fd70d7d)
- Nightly channel: 1.77.0-nightly (2024-01-06 b6a8c762eed0ae038365)
```


### Anything else?

_No response_
Repository: stable-diffusion-webui
Issue: high vram usage with inpaint with SDXL and SDXL_inpaint
Labels: bug-report

### Checklist

- [X] The issue exists after disabling all extensions
- [ ] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [X] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

i know SDXL_inpaint models not yet fully implemented but its happened also with normal SDXL model


### Steps to reproduce the problem

load a model
go to im2img
inpaint-tab
paste an image (take a large one >1400x1000)
draw a mask
write somewhat in the prompt
take over resolution
all other standard
watch GPU-Z Vram usage
with an SDXL model  ~9GB
first 2sec 12GB
last 3sec >16GB 
if you have a fast GPU rase up sampling steps too 200 too get it



### What should have happened?

-
ok fooocus control has another way to use the models but never use more than 9GB   ;)

### What browsers do you use to access the UI ?

Mozilla Firefox

### Sysinfo

Win10
RTX 4060-16GB

### Console logs

```Shell
no error
```


### Additional information

i only mention this because if i have another program running which uses e.g. 2GB VRam then the last 3sec -> 10sec
Repository: go
Issue: x/tools/gopls: ctrl-click should jump to source, not to autogenerated code
Labels: FeatureRequest,gopls,Tools

### gopls version

(does not matter here)

### go env

```shell
(does not matter here)
```


### What did you do?

I use Go, vscode and [templ.guide](//templ.guide)

The tool `templ` creates Go code from templates.

I am looking at my Go file and I use a function which was auto-generated by `templ`:

If I ctrl-click on `page()` then ...

![image](https://github.com/a-h/templ/assets/414336/37f0e991-0125-4609-8ced-2f9061561442)

then I get to the autogenerated Go code:

![image](https://github.com/a-h/templ/assets/414336/7f927b64-7fbe-4eae-8977-7f0fcbcfdbbc)

It would be great if I could get to the templ-file instead:

![image](https://github.com/a-h/templ/assets/414336/d418e9f7-e5c9-4f00-b36a-9359e9cf649f)


As a user, the experience is not great, because I would like to jump to the original source (the templ template).

Does gpls provide hooks, which templ could implement, so that ctrl-click jumps directly to the templ template?

Related issue: https://github.com/a-h/templ/issues/387
Repository: godot
Issue: Matrix transform error when displaying TabBar
Labels: bug,needs testing,topic:gui

### Tested versions

v4.3.dev.custom_build [c8c483cf5]

### System information

Windows 11 Lenovo laptop

### Issue description

I was getting this problem when developing an addon, but then realized it was being caused by the Godot editor itself as well.  Basically whenever a TabBar is first shown, either when first added to a tree or when the user foregrounds the Godot application, this error occurrs.  It's caused by Transform2D.affine_inverse failing due to a 0 determinant.

### Steps to reproduce

Compile Godot in Visual Studio and place a breakpoint at /core/math/transform_2d.cpp line 51.  Run Godot with debugging enabled.  Before the project select screen even shows, the debugger will halt on this line.  The breakpoint will also be hit if you switch to another window and then switch back.

### Minimal reproduction project (MRP)

Just compile and run Godot v4.3.dev.custom_build [c8c483cf5] with debugging enabled and a breakpoint at /core/math/transform_2d.cpp line 51.  This will trigger the error.
Repository: TypeScript
Issue: error in Variadic Tuple Types , if i reverse the partial function
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

 Type '[...any[], number]' is not assignable to type '[a: number, b: number, c: number]'.
      Target requires 3 element(s) but source may have fewer.ts(2345)

### 🕗 Version & Regression Information

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


### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.4.0-dev.20240107#code/PTAEFsEsDtPBDANqATgUwA4oPYBMCuAxmgFAkAuAnhmqAIIoqgC8qa8u20ilo80lANoBdMgDN80QuUhdQGeChlIAwkkQAeACqg0AD3JpouAM71GAGlABVXQaOnzKKwCUAfAAoSoUGIBcoB4AdCGKAOYmAYIhQVpWMdbCAJQsbqAuFt6gMQAW7LgMEQFaJCkA3lno5Pgo0IEx5PCQiIWRNinMaWLBIXkcrfEhjc2tSSQAvuKS0rJ1CkqQquouaABu2naGxmYMzjabDjuW6Z5Z-vWhKEWg0SHWg7HJqemZPg1NLVdtJeWVaNW1C5BPoFL4BawdLo9YH5AbZIYfUYTMhUGigZCsaD4cAAIzQKCmUhkckMHngAUQVhxFKshApSQCWNx+NAFR8VRqdXgoAA1KAcbzQIRkSRCFwTOQ+Cx5IplIg1IhEB5DFYAIxjMXQCX86XzOUKxArVbKtBqpJAA

### 💻 Code

```ts
// minimal reproduce

type Arr = readonly any[]

function partialCall<T extends Arr, U extends Arr, R>(
  f: (...args: [...T, ...U]) => R,
  ...headArgs: T
) {
  return (...tailArgs: U) => f(...headArgs, ...tailArgs)
}

function partialCallRev<T extends Arr, U extends Arr, R>(
  f: (...args: [...U, ...T]) => R,
  ...tailArgs: T
) {
  return (...headArgs: U) => f(...headArgs, ...tailArgs)
}

type l = number

function te(a: l, b: l, c: l): number {
  return a + b + c
}

const a = partialCall(te, 1)
const b = partialCallRev(te, 1)// error
```


### 🙁 Actual behavior

When I changed the order of parameters in the partialCall function, what I meant was that I wanted to first store the trailing parameters, but an error occurred.

### 🙂 Expected behavior

i expected it work

### Additional information about the issue

_No response_