sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Variance not computed for concrete GAT references in struct fields
Labels: C-discussion,A-variance,T-types,A-GATs

Similar to https://github.com/rust-lang/rust/issues/114221#issuecomment-1656912412.

I tried this code:

```rust
trait Foo {
    type Ref<'a>;
}

struct Bar;
impl Foo for Bar {
    type Ref<'a> = &'a u8;
}

struct Baz<'a>(<Bar as Foo>::Ref<'a>);

fn f<'a>(s: Baz<'static>) { let _: Baz<'a> = s; }

```

I expected to see this happen: lifetime check passes

Instead, this happened:
```
error: lifetime may not live long enough
  --> src/main.rs:12:36
   |
12 | fn f<'a>(s: Baz<'static>) { let _: Baz<'a> = s; }
   |      -- lifetime `'a` defined here ^^^^^^^ type annotation requires that `'a` must outlive `'static`
   |
   = note: requirement occurs because of the type `Baz<'_>`, which makes the generic argument `'_` invariant
   = note: the struct `Baz<'a>` is invariant over the parameter `'a`
   = help: see <https://doc.rust-lang.org/nomicon/subtyping.html> for more information about variance
```

Although lifetime variance does get computed when the GAT type is directly referenced in the parameter type:

```rust
fn f<'a>(s: <Bar as Foo>::Ref<'static>) { let _: <Bar as Foo>::Ref<'a> = s; } // check passes
```

Edit:

Sames limitation on types:
```rust
trait Foo {
    type GAT<T>;
}

struct Bar;
impl Foo for Bar {
    type GAT<T> = T;
}


fn f<'a>(s: <Bar as Foo>::GAT<&'static ()>) { let _:  <Bar as Foo>::GAT<&'a ()> = s; } // this passes the check

struct Baz<T>(<Bar as Foo>::GAT<T>);
fn f1<'a>(s: Baz<&'static ()>) { let _: Baz<&'a ()> = s; } // but this doesn't

```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.84.0-nightly (c1db4dc24 2024-10-25)
binary: rustc
commit-hash: c1db4dc24267a707409c9bf2e67cf3c7323975c8
commit-date: 2024-10-25
host: aarch64-apple-darwin
release: 1.84.0-nightly
LLVM version: 19.1.1
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
<backtrace>
```

</p>
</details>
Repository: langchain
Issue: DOC: The bedrock documentation is under "AWS" it needs to change to the earlier "Bedrock"
Labels: 🤖:docs,stale

### URL

https://python.langchain.com/docs/how_to/dynamic_chain/

### Checklist

- [X] I added a very descriptive title to this issue.
- [X] I included a link to the documentation page I am referring to (if applicable).

### Issue with current documentation:

https://python.langchain.com/docs/how_to/dynamic_chain/

and many others

all need to say Bedrock - because AWS is a wide scope and it includes SageMaker as well 



### Idea or request for content:

https://python.langchain.com/docs/how_to/dynamic_chain/

needs to have the documentation under "Bedrock" TAB like it was before and also can we move it towards the left side
Repository: vscode
Issue: Comments broken in markdown codeblock
Labels: feature-request,editor-comments

create markdown file:
````md
```ts
function abc() {
	return;
}
```

* ```ts
  function abc() {
  	return;
  }
  ```
````

press comment keybind (ctrl+/) on the `return;` lines

Expected:
TS comment `//` added before the `return;` ✅
![Image](https://github.com/user-attachments/assets/a259f2af-62a4-4588-9bf2-b872f1222bf9)


Actual:
`return;` surrounded with html comment `<!-- -->` ❌
![Image](https://github.com/user-attachments/assets/c976b71e-da06-457b-8708-72acc0a3ac8f)


This is due to the comment handling code
it checks for the language at the start of the line
but then places the comment after the last whitespace indent

Fix would be to check for the language after the last whitespace indent
OR place the comment at the start of the line

https://github.com/microsoft/vscode/blob/main/src/vs/editor/contrib/comment/browser/lineCommentCommand.ts

Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.94.2
- OS Version: Windows 11
Repository: rust
Issue: incorrect suggestion for `use<...>` bound that captures multiple lifetimes
Labels: A-diagnostics,T-compiler,A-suggestion-diagnostics,D-incorrect,F-precise_capturing

### Code

```rust
struct T;

impl T {
	fn iter(&self, t: &T) -> impl Iterator {
		std::iter::once((self, t))
	}
}
```

### Current output

`cargo check` currently suggests

```
error[E0700]: hidden type for `impl std::iter::Iterator` captures lifetime that does not appear in bounds
 --> src/main.rs:5:3
  |
4 |     fn iter(&self, t: &T) -> impl Iterator {
  |             -----            ------------- opaque type defined here
  |             |
  |             hidden type `std::iter::Once<(&T, &T)>` captures the anonymous lifetime defined here
5 |         std::iter::once((self, t))
  |         ^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
help: add a `use<...>` bound to explicitly capture `'_`
  |
4 |     fn iter(&self, t: &T) -> impl Iterator + use<'_> {
  |                                            +++++++++
```

if i apply that suggestion it still complains about another implicitly captured lifetime and suggests this.

```
help: add `'_` to the `use<...>` bound to explicitly capture it
  |
4 |     fn iter(&self, t: &T) -> impl Iterator + use<'_, '_> {
  |                                                    ++++
```

if i apply this suggestion the code doesn't compile either with this error

```
error: cannot capture parameter `'_` twice
 --> src/main.rs:8:47
  |
4 |     fn iter(&self, t: &T) -> impl Iterator + use<'_, '_> {
  |                                                  ^^  -- parameter captured again here
```

and it still complains about a captured lifetime that doesn't appear in the bounds with another helpful suggestion

```
help: add `'_` to the `use<...>` bound to explicitly capture it
  |
4 |     fn iter(&self, t: &T) -> impl Iterator + use<'_, '_, '_> {
  |                                                        ++++
```

### Desired output

```
help: add a `use<...>` bound to explicitly capture the lifetimes
  |
4 |     fn iter<'a, 'b>(&'a self, t: &'b T) -> impl Iterator + use<'a, 'b> {
  |            ++++++++  +++          +++                    +++++++++++++
```

### Rationale and extra context

_No response_

### Other cases

_No response_

### Rust Version

rustc 1.84.0-nightly (c1db4dc24 2024-10-25)
binary: rustc
commit-hash: c1db4dc24267a707409c9bf2e67cf3c7323975c8
commit-date: 2024-10-25
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.1

### Anything else?

_No response_
Repository: TypeScript
Issue: Should validate iteree when using `using`/`await using` in loop initializer
Labels: Needs Investigation

### 🔍 Search Terms

explicit resource management, using, await using, loop initializer, Symbol.dispose, Symbol.asyncDispose, iteration

### ✅ Viability Checklist

- [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [x] This wouldn't change the runtime behavior of existing JavaScript code
- [x] This could be implemented without emitting different JS based on the types of the expressions
- [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

In this code,
```ts
export function throwsException() {
    for (using x of [1, 2, 3]) {
        console.log(x);
    }
}
```
I expect to see an error. It doesn't currently show one ([playground link](https://www.typescriptlang.org/play/?target=99&ts=5.7.0-dev.20241026#code/KYDwDg9gTgLgBAMwK4DsDGMCWEVxgCyggHcBnAURDWDCxwAoBKOAbwCg5PFo56lTMKAOZwQcCAjgBtAIwAaOACYFAZgC6zdl21w0OUhAA2wAHSGIQ+iEYBuDlwC+bB0A))

If I did something like `using x = 3;` I would get something like `The initializer of a 'using' declaration must be either an object with a '[Symbol.dispose]()' method, or be 'null' or 'undefined'`. I think a similar error message would be appropriate here too.

### 📃 Motivating Example

```ts
export function throwsException() {
    for (using x of [1, 2, 3]) {
        console.log(x);
    }
}
```
is preventable exception-throwing code.
And validating it a logical extension of validating 
```ts
export function throwsException() {
    for (const x of [1, 2, 3]) {
        using y = x; // TS ERROR: The initializer of a 'using' declaration must be either an object with a '[Symbol.dispose]()' method, or be 'null' or 'undefined'
        console.log(x);
    }
}
```

### 💻 Use Cases

1. What do you want to use this for? Safer usage explicit resource management features.
2. What shortcomings exist with current approaches? No validation of explicit resource management declarations in loop initializers
3. What workarounds are you using in the meantime? N/A.
Repository: PowerToys
Issue: custom time stamps in PowerToys for Shamsi calendar and Lunar Hijri calendar
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.0

### Installation method

GitHub

### Running as admin

None

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

Hi, How to create custom time stamps in PowerToys Run like this for Shamsi calendar and Lunar Hijri calendar?
۱۴۰۳/۰۸/۰۵ - ۰۹:۱۸ ق‌.ظ
یکشنبه - ۶ آبان ۱۴۰۳
and
۱۴۴۶/۰۴/۲۳ 
الأحد - ٢٣ ربيع الثاني ١٤٤٦

in description for "PowerToys Run", It tells about this but when I enable PowerToys Run, I have Gregorian calendar only but I need all these dates. 
Thanks.

### ✔️ Expected Behavior

I want all calendars like Shamsi , Lunar and Gregorian in PowerToys Run.

### ❌ Actual Behavior

I have Gregorian calendar only!

### Other Software

_No response_
Repository: neovim
Issue: Setting 'winbar' on 'BufWinEnter' can unexpectedly cause window with 'winfixheight' to resize on opening/closing other windows
Labels: bug,ui,statusline

### Problem

Setting 'winbar' on 'BufWinEnter' can unexpectedly cause window with 'winfixheight' to resize on opening/closing other windows.

Screen recording:

https://github.com/user-attachments/assets/89b167bf-7725-464a-8569-047ae7edb517


### Steps to reproduce

1. Create the `minimal.lua` file:

    ```lua
    vim.api.nvim_create_autocmd('BufWinEnter' , {
      callback = function()
        vim.wo.winbar = ' '
      end
    })
    ```

2. `nvim --clean -u minimal.lua +copen +wincmd\ p`
3. Inside nvim, type `<C-w>v` to open a vertical split, then `<C-w>s` several times to observe the bug

I use quickfix window in the example but it happens to any window with 'winfixheight' set.


### Expected behavior

Window size of the quickfix window should not change.

### Nvim version (nvim -v)

v0.11.0-dev-1046+g25b53b593e

### Vim (not Nvim) behaves the same?

N/A

### Operating system/version

Linux 6.11.5

### Terminal name/version

Kitty 0.36.4 + tmux next-3.6

### $TERM environment variable

tmux-256color

### Installation

AUR
Repository: deno
Issue: `deno lint` produces unreadable output for minified files.
Labels: bug

Version: Deno 2.0.3

This came up in https://github.com/denoland/deno/issues/26519#issuecomment-2439774489. While I think https://github.com/denoland/deno/issues/26573 will minimize impact of the problem, `deno lint` should still be smarter about printing code snippets.

If the diagnostic is produced for a rather big column no (eg. `>=200`), `deno lint` should put a placeholder instead of printing out the whole code snippet with highlighted range. 

Additionally a hint should be provided that this situation suggests a minified file is being linted, which usually is not what user wanted. The hint should suggest to exclude the file in `deno.json` config.
Repository: godot
Issue: Can't color pick outside editor window in single window mode
Labels: bug,regression,topic:gui

### Tested versions

* 4.2 - works in single window mode
* 4.3 - doesn't work
* 4.4.dev  - doesn't work

### System information

Windows 11 - Vulkan (Forward+)

### Issue description

The `ColorPicker`'s doesn't pick colors when the mouse is outside the editor's windows when `single_window_mode` is enabled.
It works fine when `single_window_mode` is disabled.

Bisected, regression by 385284311ab63b787448b6387e3bd046aeb15032

### Steps to reproduce

* Enable `single_window_mode` in editor settings.
* Open the picker in any exported `Color` var and use the eyedropper.
* Move the mouse outside the editor's windows. The color doesn't change.in

### Minimal reproduction project (MRP)

N/A
Repository: ollama
Issue: Unrooted Termux install process
Labels: bug

### What is the issue?

I am endeavouring to set up an `ollama` server on my unrooted Termux host environment, please refer:

https://github.com/ollama/ollama/issues/7349#issuecomment-2439776813

and

https://github.com/ollama/ollama/issues/7292#issuecomment-2439781839

@vpnry @dhiltgen So, the process is:
## Process

1. git clone --depth 1 https://github.com/ollama/ollama.git

2. cd ollama

3. go generate ./...

4. delete the two lines of code, as per:

https://github.com/ollama/ollama/issues/7292#issuecomment-2427773036

5.  and write.

6. go build .

7. ./ollama serve &

8. and prosper!

Is that the go?

## Device details:

```zsh
❯ termux-info
Termux Variables:
TERMUX_API_VERSION=0.50.1
TERMUX_APK_RELEASE=F_DROID
TERMUX_APP_PACKAGE_MANAGER=apt
TERMUX_APP_PID=3465
TERMUX_IS_DEBUGGABLE_BUILD=0
TERMUX_MAIN_PACKAGE_FORMAT=debian
TERMUX_VERSION=0.118.1
TERMUX__USER_ID=0
Packages CPU architecture:
aarch64
Subscribed repositories:
# sources.list
deb https://packages-cf.termux.dev/apt/termux-main stable main
# sources.list.d/pointless.list
deb https://its-pointless.github.io/files/21 termux extras
# sources.list.d/ivam3-termux-packages.list
deb [trusted=yes arch=all] https://ivam3.github.io/termux-packages stable extras
# x11-repo (sources.list.d/x11.list)
deb https://packages-cf.termux.dev/apt/termux-x11 x11 main
# tur-repo (sources.list.d/tur.list)
deb https://tur.kcubeterm.com tur-packages tur tur-on-device tur-continuous
# root-repo (sources.list.d/root.list)
deb https://packages-cf.termux.dev/apt/termux-root root stable
# sources.list.d/rendiix.list
deb https://rendiix.github.io android-tools termux
Updatable packages:
command-not-found/stable 2.4.0-48 aarch64 [upgradable from: 2.4.0-47]
libgit2/stable 1.8.3 aarch64 [upgradable from: 1.8.2]
termux-tools version:
1.44.1
Android version:
14
Kernel build information:
Linux localhost 5.15.123-android13-8-28577532-abX910XXS4BXG5 #1 SMP PREEMPT Thu Jul 11 02:48:07 UTC 2024 aarch64 Android
Device manufacturer:
samsung
Device model:
SM-X910
LD Variables:
LD_LIBRARY_PATH=:/data/data/com.termux/files/home/.local/lib/ollama:/data/data/com.termux/files/usr/lib:/data/data/com.termux/files/home/install/lib
LD_PRELOAD=/data/data/com.termux/files/usr/lib/libtermux-exec.so
Installed termux plugins:
com.termux.widget versionCode:13
com.termux.x11 versionCode:14
com.termux.api versionCode:51
com.termux.window versionCode:15
com.termux.styling versionCode:1000
```


### OS

Linux

### GPU

Other

### CPU

Other

### Ollama version

_No response_
Repository: kubernetes
Issue: Cronjob's stuck job was not marked as failed and blocked new schedules
Labels: kind/bug,sig/apps,triage/needs-information,needs-triage

### What happened?

I have a cronjob that runs every 5 minutes, concurrency policy is forbidden:
```
apiVersion: batch/v1
kind: CronJob
metadata:
  name: backup-job
spec:
  concurrencyPolicy: Forbid
  startingDeadlineSeconds: 200
  schedule: "*/5 * * * *"
  jobTemplate:
    spec:
      backoffLimit: 0
      activeDeadlineSeconds: 240
      ......
      spec:
        restartPolicy: Never
        activeDeadlineSeconds: 240
```
I found that a job that has been there for 84 minutes when I was checking: 

```
$ kubectl get jobs -n zzz
NAME                COMPLETIONS     DURATION    AGE
xxxxx-job-28833075  0/1             84m         84m
```
However when I try to list pods I got nothing:
```
$ kubectl get pods --selector=job-name=xxxxx-job-28833075 -n zzz
No resources found in zzz namespace
```

I think the reason was one of the sidecar containers failed to start, however since all pods owned by this job were deleted so I could not debug into this job, my guess is because `.spec.jobTemplate.spec.activeDeadlineSeconds` is set, when job runs > 240 seconds all pods owned by the job are deleted, but in this case should not the job be marked as failed status? Why this job was actually failed but its status was neither completion nor failed?

Also, this stuck job causes 2 following schedules missed, I don't understand since with `.spec.jobTemplate.spec.activeDeadlineSeconds` is set to 4 minutes, should controller schedule a new job after this job was in active status for 4 minutes? 

### What did you expect to happen?

If any pods/containers owned by a job failed to run, the job should be marked as failed status and all pods/container should be kept (since by default `failedJobsHistoryLimit` is `1`).

### How can we reproduce it (as minimally and precisely as possible)?

I am not sure if it is expected behavior? 

### Anything else we need to know?

_No response_

### Kubernetes version

v1.28.13-eks-a737599

### Cloud provider

<details>

</details>
AWS

### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: svelte
Issue: Svelte component won't type with runes
Labels: documentation,types / typescript

### Describe the bug

If I try to use bind:this to a Svelte component in my project, the typing for the variable tosses this error when I try to type it using the component name:  'Nested' refers to a value, but is being used as a type here. Did you mean 'typeof Nested'?ts(2749)

This worked in svelte 4 and typeof causes other issues since the component is truly the type. Am I using wrong types? Is there something new needed in svelte 5? The code compiles but I'd rather not have this red in my code.

I noticed some files in my project didn't have issues but it looks like those files didn't migrate to use runes (only had eventDispatchers, which don't migrate). The ones which added $state or $props seem to show the symptom.

### Reproduction

https://svelte.dev/playground/6b78d2d389534d72b46ecc02e52ff7bd?version=5.1.3

This is the idea but the REPL doesn't really show the problem. I used `npx sv create my-app` to create a sveltekit minimal using typescript syntax project, no extras. Then I placed the code in App.svelte in routes/+page.svelte and added Nested.svelte in the same folder.

It tosses this error on the let nestedEl line in +page.svelte: 'Nested' refers to a value, but is being used as a type here. Did you mean 'typeof Nested'?ts(2749)

If I change to typeof Nested, the line is fine but anything else using the variable goes bad.

### Logs

_No response_

### System Info

```shell
System:
    OS: macOS 15.0.1
    CPU: (8) arm64 Apple M1
    Memory: 94.25 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
    npm: 10.9.0 - ~/.nvm/versions/node/v20.11.1/bin/npm
  Browsers:
    Brave Browser: 129.1.70.126
    Chrome: 130.0.6723.70
    Safari: 18.0.1
  npmPackages:
    svelte: ^5.0.0 => 5.1.3
```


### Severity

annoyance
Repository: excalidraw
Issue: feature request: add support for google fonts
Labels: enhancement
Repository: tauri
Issue: [bug] IPC fails in non-http protocol windows
Labels: type: bug,status: needs triage

### Describe the bug

When a window is created using a non-http protocol (data:text/html,) the value of Origin is empty when calling the rust backend command. However, Origin is required when parsing the call request.

https://github.com/tauri-apps/tauri/blob/7a1a3276c49320162300fbcfecec9f6a948d65e8/crates/tauri/src/ipc/protocol.rs#L503-L511

### Reproduction

Create a window using a non-http protocol (data:text/html,)

```rust
let data_url = Url::parse("data:text/plain,Hello?World#").unwrap();
let _ = tauri::WebviewWindowBuilder::new(&app_handle, "example", tauri::WebviewUrl::CustomProtocol(data_url)).build();
```

Then the front end calls the rust backend command

```javascript
const {open} = window.__TAURI__.shell;
open("https://github.com");
```

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.22635 x86_64 (X64)
    ✔ WebView2: 130.0.2849.52
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.82.0 (f6e511eec 2024-10-15)
    ✔ cargo: 1.82.0 (8f40fc59f 2024-08-21)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (environment override by RUSTUP_TOOLCHAIN)
    - node: 16.20.2
    - pnpm: 8.14.0
    - npm: 8.19.4

[-] Packages
    - tauri 🦀: 2.0.6
    - tauri-build 🦀: 2.0.2
    - wry 🦀: 0.46.2
    - tao 🦀: 0.30.3
    - tauri-cli 🦀: 2.0.1

[-] Plugins
    - tauri-plugin-fs 🦀: 2.0.2
    - tauri-plugin-autostart 🦀: 2.0.1
    - tauri-plugin-shell 🦀: 2.0.2
    - tauri-plugin-process 🦀: 2.0.1
    - tauri-plugin-single-instance 🦀: 2.0.1
    - tauri-plugin-notification 🦀: 2.0.1
    - tauri-plugin-http 🦀: 2.0.2

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../ui/dist
    - devUrl: http://localhost:8081/
```


### Stack trace

_No response_

### Additional context

_No response_