sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Getters in mixins get serialized to property accessors
Labels: Help Wanted,Fix Available,Possible Improvement

### 🔎 Search Terms

Getters, mixins, classes

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ 

### ⏯ Playground Link

https://tsplay.dev/mA0RkN

### 💻 Code

```ts
function mixin<T extends {new (...args: any[]): {}}> (superclass: T) {
   return class extends superclass {
      get validationTarget (): HTMLElement {
         return document.createElement("input")
      }
   }
}
class BaseClass {
   get validationTarget (): HTMLElement {
      return document.createElement("div")
   }
}

class MyClass extends mixin(BaseClass) {
  get validationTarget (): HTMLElement {
   return document.createElement("select")
  }
}
```



<details><summary><b>Output</b></summary>

```ts
"use strict";
function mixin(superclass) {
    return class extends superclass {
        get validationTarget() {
            return document.createElement("input");
        }
    };
}
class BaseClass {
    get validationTarget() {
        return document.createElement("div");
    }
}
class MyClass extends mixin(BaseClass) {
    get validationTarget() {
        return document.createElement("select");
    }
}

```


</details>


<details><summary><b>Compiler Options</b></summary>

```json
{
  "compilerOptions": {
    "strict": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "strictPropertyInitialization": true,
    "strictBindCallApply": true,
    "noImplicitThis": true,
    "noImplicitReturns": true,
    "alwaysStrict": true,
    "esModuleInterop": true,
    "declaration": true,
    "target": "ES2017",
    "jsx": "react",
    "module": "ESNext",
    "moduleResolution": "node"
  }
}
```


</details>

**Playground Link:** [Provided](https://www.typescriptlang.org/play/?ts=5.4.5#code/GYVwdgxgLglg9mABAWxgDxmAPAFUQUzSnzABMBnRAbzHwHdEAKAOlYEMAnAc3IC5E2YAJ4BtALoBKflQC+MgHxNyIAA74OEADZtyfRDgnUAUIlMd8UEByRadlQsTKVlajdt3HTXxFwuIAbmyaMKRssAg4nL5QTFKIABI4ALIAMgCimvjIJDFUJt7e5pbWiKRwECDZYFDMEOZh+BlZOYwARJgqIFCtEvneMn0DA7YeAEI6+ADC7pR5XtEBQSFh8GCR3H6McYmpTVW5fV5FVkhlFfu19cR7La2kMP49g0YDRiOUSULTdgREJBQodCYRjjchTGaGOY+PyBYKhcJrKKbbbJdKZfaeMwWE6lcqVHKXfANG7VNpgzLQJ6mIZAA)
      

### 🙁 Actual behavior

The mixin creates a property accessor instead of a getter

### 🙂 Expected behavior

The mixin should create a getter and not a property accessor

### Additional information about the issue

Seems related:

https://github.com/microsoft/TypeScript/issues/54879#issuecomment-2153508179

Duplicate of: https://github.com/microsoft/TypeScript/issues/44938
Repository: PowerToys
Issue: Installer Fails When Access to Add Start Menu Shortcut is Denied.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.81.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Installer

### Steps to reproduce

Why should installer fail when it cannot add a shortcut to my Start Menu? And if that is not bad enough the installer actually removed the previous version prior to failing to install new version leaving the system without any version of Power Toys installed and causing the App Store to wrongly report application as installed which makes it impossible to re-install from the App Store.

I don't want or need a shortcut and should not be forced to keep removing it every time there is an update.

![2024-06-06_173854](https://github.com/microsoft/PowerToys/assets/17345186/c37a5376-dc0e-4b7a-bbff-ca822d156d30)


### ✔️ Expected Behavior

Installer should complete installation if Start Menu shortcut cannot be added.

### ❌ Actual Behavior

Installer failed and completely removed Power Toys when update failed. 

### Other Software

_No response_
Repository: ollama
Issue: Support Dragonfly
Labels: model request

Together.ai recently announced the Dragonfly vision-language model based on Llama3: https://huggingface.co/togethercomputer/Llama-3-8B-Dragonfly-v1
Repository: next.js
Issue: Server action returning redirect to another root route group fails
Labels: create-next-app,bug,Navigation

### Link to the code that reproduces this issue

https://github.com/trappar/next-server-action-redirect-multi-root-bug

### To Reproduce

Using the provided replication repo:

1. Run `pnpm dev`
2. Open `http://localhost:3000/1-1` in your browser
3. Click the button to "Go to another page in the same route group (1-2)".
  a. Note that this navigates to `http://localhost:3000/1-2` without issue.
4. Click the button to "Go to another page in the other route group (2-1)".
  a. Note that this navigation fails.

### Current vs. Expected behavior

Current:
* Redirecting within a server action to a route within the same root layout group works.
* Redirecting within a server action to a route within a different root layout group fails.

Expected: Both of these should work given that multiple root layouts are a supported feature. (see: [Creating multiple root layouts](https://nextjs.org/docs/app/building-your-application/routing/route-groups#creating-multiple-root-layouts))

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 20.14.0
  npm: 10.7.0
  Yarn: N/A
  pnpm: 8.10.5
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

create-next-app, Navigation

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context

I also tried updating to the Next.js 15 RC and the same issue exists there.
Repository: go
Issue: go/printer: Invalid reformatting of slice type with a /* comment.
Labels: NeedsInvestigation

### Go version

devel go1.23-7492290887

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

```shell
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOOS=windows
set GOTOOLCHAIN=auto
set GOVERSION=devel go1.23-...
```


### What did you do?

https://go.dev/play/p/ndVJVdo9nIW
Click format.

A realistic example could be formatting `var s [/*<10*/]byte`

### What did you see happen?

Formatting code with a "/*" comment and line break inside "[" "]" of a slice either fails or produces invalid code.
Clicking format fails with "24:16: expected type, found newline (and 1 more errors)".

Having multiple comments moves them 2 lines down (no error).
Line comments and multi-line comments are moved to the next position after "]" where line breaks don't insert a ";".

Setting a fake position to the same line as the element type before writing "]" changes the behavior. "go/printer/nodes.go:1049"

ast.ArrayType lacks position information about "]".
The closing "]" must be on the same line as the array length ends. On a slice type this implicit positioning spans multiple lines and the chosen line affects ;'s.

### What did you expect to see?

Comments not moving across tokens when formatted.
I would also like the ast types to have positions for more tokens. Guessing the position requires different logic for different types: last line for slice "]", first line for map "]", first line for type assert ".", unknown for <- chan "chan".
Repository: PowerToys
Issue: mouse sin bordes fail in the conexion
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.81.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

![falla01](https://github.com/microsoft/PowerToys/assets/122291781/8d41f4b5-1d65-495f-9234-ef7984e044cd)
After actualization, it is impossible to connect with another computer.

### ✔️ Expected Behavior

Connect my two computers without any problem. 

### ❌ Actual Behavior

Las computadoras no se conectaron. 

### Other Software

_No response_
Repository: pytorch
Issue: PyTorch trunk is frequently broken
Labels: high priority,module: ci,triaged

### 🐛 Describe the bug

For example looking at https://github.com/pytorch/pytorch/pull/128123 (that adds a docstring to the utils and therefore could not cause any failures other than lint) DrCI found 2 unstable job, 1 flaky and one new failure in inductor tests:

<img width="977" alt="image" src="https://github.com/pytorch/pytorch/assets/2453524/5f6cb7cc-1951-485e-b2d4-ac1bfedf5dbf">


Not sure how new developer who want to make a small contribution to PyTorch support to navigate thru those multiple layers of dilapidation...

### Versions

CI

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @seemethere @pytorch/pytorch-dev-infra
Repository: rust
Issue: const expression produces infinite compilation
Labels: T-compiler,C-bug,I-hang,F-generic_const_exprs,requires-incomplete-features,fixed-by-next-solver

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust

#![feature(generic_const_exprs)]
#![allow(incomplete_features)]
trait Foo<const N: usize> {
    type Assoc: Default;
}
impl Foo<0> for () {
    type Assoc = u32;
}
impl Foo<3> for () {
    type Assoc = i64;
}
fn foo<T, const N: usize>(_: T) -> <() as Foo<{ N + 1 }>>::Assoc
where
    (): Foo<{ N + 1 }>,
{
    let random_var2 = "example"; // New variable declaration
    let mut _q = Default::default();
    _q = foo::<_, 2>(_q);
    _q
}
fn main() {
    let random_var = 42; // New variable declaration
    Default::default()
}

```

I expected to see this happen: compilation terminates

Instead, this happened: unterminated

### 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.80.0-nightly (debd22da6 2024-05-29)
binary: rustc
commit-hash: debd22da66cfa97c74040ebf68e420672ac8560e
commit-date: 2024-05-29
host: x86_64-unknown-linux-gnu
release: 1.80.0-nightly
LLVM version: 18.1.6
```

<!--
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: electron
Issue: [Bug]: Maximized window with the "backgroundMaterial" property
Labels: platform/windows,bug :beetle:,component/BrowserWindow,component/wco,30-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

30.1.0

### What operating system are you using?

Windows

### Operating System Version

Windows 11 version 10.0.22631

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

When I want to maximize my window without a title bar and with the Windows 11 background material (mica, acrylic, etc.), I expect to see a default maximized window with these materials.

For example, I use these parameters to enable the maximize button and the background material:
```
    backgroundMaterial: "mica",
    titleBarOverlay: {
      height: 32
    },
    frame: false,
    maximizable: true,
    titleBarStyle: "hidden"
```

### Actual Behavior

When I'm trying to make a BrowserWindow with the activated title bar overlay and background material, I can maximize it (even if I can't maximize the window with the disabled title bar overlay), but the background material becomes black, and the borders lose their border radius.

**A window before maximizing:**
![A window before maximizing](https://github.com/electron/electron/assets/66649825/1add7d6b-eae9-419c-83df-f0c099f28d9d)

**A window after maximizing:**
![A window after maximizing](https://github.com/electron/electron/assets/66649825/7e13a77e-47c1-4f75-bcb4-154cba4bce9e)

**A maximized window:**
![A maximized window](https://github.com/electron/electron/assets/66649825/722b2a3e-8368-4cce-86fc-920c7d8af16d)

**A window with backgroundMaterial - mica and default title bar:**
![image](https://github.com/electron/electron/assets/66649825/b56ce638-1c67-4941-8a2a-f3288dd54627)


### Testcase Gist URL

_No response_

### Additional Information

Here's my code of the BrowserWindow init, which has the subject issue:
```
  const mainWindow = new BrowserWindow({
    width: 1280,
    height: 800,
    minWidth: 300,
    minHeight: 300,
    fullscreenable: true,
    webPreferences: {
      nodeIntegration: true,
      contextIsolation: false,
      devTools: true,
      webSecurity: false
    },
    resizable: true,
    autoHideMenuBar: true,
    show: true,

   //pay attention on this params below
    backgroundMaterial: "mica",
    titleBarOverlay: {
      height: 32
    },
    frame: false,
    maximizable: true,
    titleBarStyle: "hidden"
  });
```
Repository: flutter
Issue: [webview_flutter] Allow returning a value from JavascriptChannel handler
Labels: c: new feature,p: webview,package,team-ecosystem,has reproducible steps,P2,triaged-ecosystem,found in release: 3.22,found in release: 3.23

### Steps to reproduce

JS cannot get [webview_flutter JavascriptChannel](https://pub.dev/documentation/dt_webview_flutter/latest/webview_flutter/JavascriptChannel-class.html) return value
```dart
// dart
WebViewController.addJavaScriptChannel(
  'getFileBase64',
  onMessageReceived: (JavaScriptMessage message) async {
    final base64 = await dosomething(message.message);
    return base64;
  },
);
```
```js
// js
button.onclick = async () => {
  const base64 = await window.getFileBase64.postMessage('/cache/xx.png')
  console.log(base64)
}
```

### Expected results

Expect JS to get the return value of JavaScriptChannel.
Can you refer to [inappwebview](https://inappwebview.dev/docs/webview/javascript/communication#javascript-handlers).

If JavascriptChannel cannot return a value and I do not change to another webview library, my operation needs to be modified like this

```dart
// dart

// step 1
WebViewController.addJavaScriptChannel(
  'getFileBase64',
  onMessageReceived: (JavaScriptMessage message) {
    convert2Base64(message.message);
  },
);

// step 2
void convert2Base64(String path) async {
  final base64 = await dosomething(path);
  WebViewController.runJavaScript('''
  const event = new CustomEvent('getFileBase64', {detail: {base64: "$base64"}});
  window.dispatchEvent(event);
''');
}
```

```js
// js

// step 3
window.addEventListener('getFileBase64', e => {
  const base64 = e.detail.base64
 // dosomtting
})

// step 4
button.onclick = () => {
  window.getFileBase64.postMessage('/cache/xx.png')
}
```

### Actual results

[JavascriptMessageHandler](https://pub.dev/documentation/dt_webview_flutter/latest/webview_flutter/JavascriptMessageHandler.html) return value is empty and cannot be given to JS return value

### Code sample

<details open><summary>Code sample</summary>

```dart
[Paste your code here]
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[Paste your output here]
```

</details>
Repository: storybook
Issue: [Bug]: Tailwind CSS Styles Not Applying in Next.js Application
Labels: bug,needs triage

### Describe the bug

I've set up a Next.js application and initiated Storybook using the command npx storybook@latest init. The setup completed without issues, and the Storybook environment started successfully with npm run storybook.

Following the Tailwind CSS integration guide, I attempted to import the global.css file into the preview.tsx file as suggested.

```
import type { Preview } from '@storybook/react';
import '../src/app/globals.css';

export default {
  parameters: {
    controls: {
      matchers: {
        color: /(background|color)$/i,
        date: /Date$/i,
      },
    },
  },
} satisfies Preview;
```

Upon navigating to Storybook, I noticed that none of the Tailwind CSS styles were applied. I conducted a thorough search for a stylesheet that might contain the Tailwind class names, but my efforts were fruitless.



### Reproduction link

n/a

### Reproduction steps

1. Create a New Next.js Application:
Execute the command npx create-next-app@latest test-tailwind to generate a new Next.js app named 'test-tailwind'.
2. Initialize Storybook:
Run npx storybook@latest init within the project directory to set up Storybook.
3. Import Global Stylesheet:
In the .storybook/preview.tsx file, import the global stylesheet located at src/app/globals.css. Modify the stylesheet to observe the changes effectively.
4. Develop a Story:
Craft a story that incorporates specific styles from src/app/globals.css as well as Tailwind utility classes like .flex and .flex-col.
5. Inspect the Storybook Iframe:
Review the Storybook iframe to ensure that the styles are applied correctly.


### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.3.1
    CPU: (11) arm64 Apple M2
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.13.1 - ~/.nvm/versions/node/v20.13.1/bin/node
    npm: 10.5.2 - ~/.nvm/versions/node/v20.13.1/bin/npm <----- active
  Browsers:
    Chrome: 124.0.6367.208
    Safari: 17.3
  npmPackages:
    @storybook/addon-essentials: ^8.1.1 => 8.1.1
    @storybook/addon-interactions: ^8.1.1 => 8.1.1
    @storybook/addon-links: ^8.1.1 => 8.1.1
    @storybook/addon-onboarding: ^8.1.1 => 8.1.1
    @storybook/addon-themes: ^8.1.1 => 8.1.1
    @storybook/blocks: ^8.1.1 => 8.1.1
    @storybook/nextjs: ^8.1.1 => 8.1.1
    @storybook/react: ^8.1.1 => 8.1.1
    @storybook/test: ^8.1.1 => 8.1.1
    eslint-plugin-storybook: ^0.8.0 => 0.8.0
    storybook: ^8.1.1 => 8.1.1
```
```


### Additional context

_No response_
Repository: TypeScript
Issue: False positive ts(2373)
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

Parameter cannot reference identifier declared after it, ts(2373)

### 🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about anything related (and found nothing).

### ⏯ Playground Link

https://www.typescriptlang.org/play/?noUncheckedIndexedAccess=true&noUnusedLocals=true&noUnusedParameters=true&esModuleInterop=false&declaration=false&target=99&jsx=0&noErrorTruncation=true&pretty=true&isolatedDeclarations=true&verbatimModuleSyntax=true&useUnknownInCatchVariables=true&exactOptionalPropertyTypes=true&noFallthroughCasesInSwitch=true&noImplicitOverride=true&noPropertyAccessFromIndexSignature=true&ts=5.6.0-dev.20240606&ssl=18&ssc=1&pln=1&pc=1#code/PQKhCgAIUgVALAlgZ0gMwK4DsDGAXRAey0j3gCdCB3VAAwCUBTNR8x3RgUXMvIC5IAYQCGWLITyRhOHI2SoA5ABt2AczILIAI2aE2kRFkQFhSxAC9hBYrSmTy2AgFtGAOigRocAMqQcetnwlAE9INgAHPTw6aIAKACYAZgB2RIBKWldIQF4NwFkdj2BwRgAPSPJJfyxkSTwHRgAFQmRjRAA3RkgAXkgAHkrquAA+WIBvSABtFSx1eEgAWkgARgBdATRDUwBJPEYnABpIKZnIAF8BNmEAE2IQuHHltIFYSAAfSGxL5kNGS67ByBGUDCjDwGHIJHWWC2OycAG5wCd4eBQJ4YAgUOhsPgiCQqHoANaoSEdKxhRyIFzuaAeHzQECGMD+HiMIKhCJRGLIBIpdKZHKAOR2CkVSlE-MQBmhTMgGk0Wu0ur1+pJYMMxkcyAdJmoyPMlqt0BslNtdqdzowrjdQrB7o84K93lhPsTfp1-oDIMDQeCDVCjTD4YjwEA

### 💻 Code

```ts
/**
 * This function throws `ReferenceError: Cannot access 'length' before initialization` at runtime.
 *
 * TS correctly reports `ts(2373)`. 👍
 */
export const truePositive = <const T>({ [length - 1]: finalItem, length }: readonly T[]): T | undefined => {
  return finalItem;
};

/**
 * This function works fine at runtime.
 *
 * TS **in**correctly reports `ts(2373)`. 👎
 */
export const falsePositive = <const T>({ length, [length - 1]: finalItem }: readonly T[]): T | undefined => {
  return finalItem;
};
```


### 🙁 Actual behavior

A false positive `ts(2373)` is being reported in a situation where we can determine statically that what the report warns about is not taking place.

Ironically, the false positive `ts(2373)` might represent a real bug in TS' own modeling of declaration order.

### 🙂 Expected behavior

No false positive `ts(2373)` being reported.

### Additional information about the issue

To be clear:

In the `falsePositive` case, we can statically determine that `length` is declared prior to being used.
Repository: go
Issue: x/mobile: IOS static libaray build by go mobile make  clang++ crashed with ldflags "-Wl,-fixup_chains"
Labels: NeedsInvestigation,mobile

##  What version of Go are you using (go version)?
go version go1.22.1 darwin/arm64

##  What did you do?
First we build a go project with gomobile (https://github.com/xxf098/go-tun2socks-build) as a static library,
then linker this static library into our IOS project.

## What did you see happen?

lld crashed.

I found crash position of lld:

`SymtabSectionImpl<LP>::writeTo` of file  `lld/MachO/SyntheticSections.cpp`
Crashed on this line:           `nList->n_sect = defined->isec()->parent->index;`

I debug llvm found crash symbol is `arm64_ios_lib.ptr`

After we remove ldflags "-Wl,-fixup_chains" ,or modify llvm code crash not happed.


## What did you expect to see?

The ios static library compiled by gomobile works fine with clang link parameter "-Wl,-fixup_chains".