sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Font preload not working as expected 
Labels: bug,Font (next/font)

### Link to the code that reproduces this issue

https://github.com/jasonthorsness/repro001

### To Reproduce

npm run build
npm run start
Navigate to localhost:3000 in dev tools in Chrome and observe the absence of a preload for the fonts in the initial HTML response

### Current vs. Expected behavior

Expected
Both the Google and Local fonts should have a link rel preload in the first HTML sent back from the server

Actual
Neither font has a preload entry in the first HTML sent back from the server and they aren't downloaded until the CSS references them.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 29438
  Available CPU cores: 16
Binaries:
  Node: 20.11.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.1-canary.67 // Latest available version is detected (14.1.1-canary.67).
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

App Router, Font optimization (next/font)

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

next dev (local), next build (local), next start (local)

### Additional context

Here is the content I see in the initial HTML response - note lack of preload for the fonts

```
    <head>
        <meta charSet="utf-8"/>
        <meta name="viewport" content="width=device-width, initial-scale=1"/>
        <link rel="preload" as="image" href="/vercel.svg" fetchPriority="high"/>
        <link rel="preload" as="image" href="/next.svg" fetchPriority="high"/>
        <link rel="stylesheet" href="/_next/static/css/be383e181a203198.css" crossorigin="" data-precedence="next"/>
        <link rel="preload" as="script" fetchPriority="low" href="/_next/static/chunks/webpack-43737e769a979b7d.js" crossorigin=""/>
        <script src="/_next/static/chunks/fd9d1056-9bd6272302a380c1.js" async="" crossorigin=""></script>
        <script src="/_next/static/chunks/54-f0a3df5edf4d335b.js" async="" crossorigin=""></script>
        <script src="/_next/static/chunks/main-app-cd149db4694c0f16.js" async="" crossorigin=""></script>
        <script src="/_next/static/chunks/407-a5a598ccc34bf6cf.js" async=""></script>
        <script src="/_next/static/chunks/app/page-339d9c829db39b7a.js" async=""></script>
        <title>Create Next App</title>
        <meta name="description" content="Generated by create next app"/>
        <link rel="icon" href="/favicon.ico" type="image/x-icon" sizes="16x16"/>
        <script src="/_next/static/chunks/polyfills-78c92fac7aa8fdd8.js" crossorigin="" noModule=""></script>
    </head>
 ```
Repository: PowerToys
Issue: Ruler pixel measurement seems off when win10 is using zoomed desktop
Labels: Issue-Bug,Needs-Triage,Product-Screen Ruler

### Microsoft PowerToys version

0.78

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Screen ruler

### Steps to reproduce

Opera or Chrome... ummm, display is 1920 x 1080 one a 4k TV.  zoom are all at default or recommened settings (150% i think).  I was trying to size my webpage images by measuring the dimensions as they appear in the broswer, and resizing the images to what powertoys screen ruler was reporting.  maybe i need to apply some math, but i think the desktop zoom made the ruler report the image larger than it really was.

### ✔️ Expected Behavior

I was expecting powertoys to allieviate all of my pet peeves and disappointments over the years with windows, and address some shortcomings and introduce handy new tools that you wouldn't want to live without.  and you guys have done nearly just that.  awesome... you can pry powertoys from my cold dead mouse hand.  thanks a bunch.

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: react-native
Issue: Fetch stuck in (pending) iOS
Labels: Platform: iOS,🌐Networking,Needs: Triage :mag:

### Description

https://github.com/apollographql/apollo-client/issues/11608

I have opened an issue with `apollo/client` as I was under the assumption that it was an issue with that library. It turns out that this might be something that is more on the `react-native` / `iOS` specific side of things.

### Steps to reproduce

1.  `git clone git@github.com:Johnsgaard/fogtown.git`
2. `npm install`
3. `npm run ios` (assuming you have expo)

### React Native Version

0.73.4

### Affected Platforms

Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.1.2
  CPU: (10) arm64 Apple M1 Pro
  Memory: 994.88 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.10.0
    path: ~/.nvm/versions/node/v20.10.0/bin/node
  Yarn: Not Found
  npm:
    version: 10.2.3
    path: ~/.nvm/versions/node/v20.10.0/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods: Not Found
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - visionOS 1.0
      - watchOS 10.2
  Android SDK: Not Found
IDEs:
  Android Studio: Not Found
  Xcode:
    version: 15.2/15C500b
    path: /usr/bin/xcodebuild
Languages:
  Java: Not Found
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.4
    wanted: 0.73.4
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
```


### Stacktrace or Logs

```text
No stack trace. Network request on iOS is locked on (pending) when making a request.
```


### Reproducer

https://github.com/Johnsgaard/fogtown

### Screenshots and Videos

![Uploading Screenshot 2024-02-21 at 10.25.22 AM.png…]()
Repository: electron
Issue: [Bug]: UtilityProcess crashes when using the asar path
Labels: platform/windows,bug :beetle:,status/confirmed,has-repro-gist,28-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

28.2.3

### What operating system are you using?

Windows

### Operating System Version

windows11 23h2

### What arch are you using?

ia32

### Last Known Working Electron version

_No response_

### Expected Behavior

Should have been successfully created

### Actual Behavior

`// 载入新的模块实例
        const Modurl = C:\Users\ihanl\Desktop\ELECTRON-tl\resources\app.asar\main\ModProcess\ModMain.js
        console.log(Modurl);
        //创建模块进程
        const child = utilityProcess.fork(Modurl, ['pipe', 'pipe', 'pipe', 'ipc'], {
            serviceName: 'ModProcess',
            cwd: __dirname,
        })`





### Testcase Gist URL

_No response_

### Additional Information

_No response_
Repository: PowerToys
Issue: [FancyZones] Whatsapp not remembering position
Labels: Issue-Bug,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update, Microsoft Store, WinGet

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Drag Whatsapp to a Zone
Close WA
Open WA


### ✔️ Expected Behavior

WA should spawn inside the previously defined Zone

### ❌ Actual Behavior

It spawns somewhere else but not in the Zone previously defined

### Other Software

WSL2

#12211
#30900
Repository: PowerToys
Issue: French " - " key can't be use in Quick Accent
Labels: Issue-Bug,Needs-Triage,Product-Quick Accent

### Microsoft PowerToys version

0.78.0

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Quick Accent

### Steps to reproduce

1. Change keyboard layout in French.

2. Enable Quick Accent.

3. - Try to switch accent on " - " of the numpad : Nothing
    - Try to switch accent on " - " of the first row : you get the " ⁶ ₆ "



### ✔️ Expected Behavior

have the quick accent on the "-" of the numpad, (more general problem than the French layout). have the accent on the "-" of the first row of the keyboard. 
Another solution would be to assign the “ ) ” key for " - " the French keyboard.
This key is the equivalent of " - " on the US keyboard (in term of location) and is not used by PowerToy. This would make sense for users: no




### ❌ Actual Behavior

-  accent on " - " of the numpad : Nothing
-  accent on " - " of the first row : you get the " ⁶ ₆ "

### Other Software

_No response_
Repository: material-ui
Issue: [material-ui][Autocomplete] Add class for component when `multiple` prop is applied
Labels: waiting for 👍,package: material-ui,component: autocomplete

### Summary

It would be nice if we could get a `MuiAutocomplete-multiple` class added to the Autocomplete root element if the `multiple` prop is true. 

### Examples

_No response_

### Motivation

Would allow us to style these separately without introducing our own class names:

```tsx
<MuiAutocomplete renderInput={(params) => <TextField {...params} />} className={cx({ 'MuiAutocomplete-multiple': isMultiple })} />
```

**Search keywords**: multiple autocomplete class
Repository: next.js
Issue: Unexpected Execution of generateSitemaps Function When Commented Out During Build Process
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/elegant-surf-z8vmmj?file=%2Fapp%2Fsitemap.ts%3A7%2C25

### To Reproduce

1. Add the generateSitemaps function to your sitemap.ts file.
2. Comment out the generateSitemaps function.
3. Execute the build process and notice that the build does not succeed, suggesting that the build process is impacted by the commented-out code.

### Current vs. Expected behavior

**Expected Behavior:**
Commenting out the generateSitemaps function should not impact the build process
**Actual Behavior:**
The generateSitemaps function appears to be parsed resulting to a build error.



### Provide environment information

```bash
Relavant packages:
"next": "14.0.3",
```


### Which area(s) are affected? (Select all that apply)

Metadata Files

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

_No response_
Repository: go
Issue: proposal: go/types: adopt "defined type" terminology consistently
Labels: Proposal

The spec uses the term "defined type" for a type created by a declaration such as `type T int`; a defined type is capable of bearing declared methods. Historically, this was called a `Named` type, but the advent of type aliases made this confusing and ambiguous.

Though I was initially lukewarm about the term "defined type" (aren't all types defined?), recent work auditing dense type-checking code in x/tools as made me appreciate it, because there are now three kinds of "named" types:
- defined types (`*Named`)
- type parameters (`*TypeParam`, go1.18), and
- type aliases (`*Alias` in go1.22).

In some cases, their namedness is a meaningful commonality that can be used by tooling. For example, they all have an associated TypeName symbol that provides their location and logical name for use in a tool's UI.

I propose that we follow through with the renaming, using the name "Named" as little as possible. Obviously we can't get rid of `Named`, or make it an alias for Defined (as its reflect.Type.String would change), but we can make Defined an alias for it:
```go
// A Defined type is a type created by a declaration such as `type T underlying`,
// capable of bearing method declarations.
//
// Along with TypeParam and Alias, it is one of three types that are named
// and have an associated TypeName symbol.
// Named is a historical and deprecated term for Defined.
type Defined = types.Named
func NewDefined(obj *TypeName, underlying Type, methods []*Func) *Defined

// Named is the historical term for a Defined type.
// Use Defined in new code.
type Named struct { ... }

// Deprecated: use NewDefined.
func NewNamed( ... ) { return NewDefined ... }
```
Repository: ollama
Issue: Ollama serve fails silently when an input is too long
Labels: bug

When I use `ollama serve` and provide a context of ~30k tokens with a mistral model that has a max context window of 32768, the server doesn't show any error and proceeds to return as usual. That gave me the impression that it successfully took in the entire context.

But after digging a bit deeper, I see it's not.
![SCR-20240221-lpyt](https://github.com/ollama/ollama/assets/4860545/8caef175-f97d-4304-9f19-1a8103770427)

So when I do this below it started working fine

```
ollama run <model>
/set parameter num_ctx 32768
/save
```

Perhaps it's because there are flags to set with `ollama serve` which I don't know about after reading the docs. Is there a better way to set the context window for `ollama serve`?

In my mind, the expected behavior is to show an error message when the input is exceeding the set context window length. LM Studio does this

<img width="1426" alt="SCR-20240221-lsnn" src="https://github.com/ollama/ollama/assets/4860545/ee4f2408-bbce-4fb8-bd74-6306aca08b3c">

Please let me know if it's because I'm not using it with the right flags or if this is a legit concern.
Repository: go
Issue: runtime: investigate replacing per-thread CLOCK_THREAD_CPUTIME_ID with per-process CLOCK_PROCESS_CPUTIME_ID
Labels: NeedsInvestigation,compiler/runtime

Linux 6.4+ include https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bcb7ee79029dcaeb09668a4d1489de256829a7cc, which makes CLOCK_PROCESS_CPUTIME_ID prefer to deliver to the thread that caused timer overflow.

We should check whether CLOCK_PROCESS_CPUTIME_ID suffers from the same multi-expiration problem from #35057. I think it probably does, in which case there is nothing to do. But if it _doesn't_, going back to a single per-process timer would be a nice simplification.

cc @rhysh @golang/runtime
Repository: flutter
Issue: Come up with a plan with how `ui.FrameTiming` should work in multi-view
Labels: engine,P2,team-engine,triaged-engine

Currently the `ui.FrameTiming` data that is reported is structured based on the assumption that there is a one-to-one-to-one correspondence between vsync, building a scene and rasterizing a scene. Multi-view, however, calls this assumption into question since we may have multiple scenes built and rendered per frame, and the building and rendering could be interleaved with each other. At least on web, I'm pretty sure the frame timings that are reported will be incorrect under multi-view. We should have a discussion on the best way to move forward with these metrics in a multi-view world.
Repository: vscode
Issue: [SUGGESTION] Test Explorer is able to be grouped
Labels: feature-request,testing

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

### Describe the feature you'd like

Im basing the Feature Request from what I see in Visual Studio 2022, where there are many additional option to group your tests into. 
![image](https://github.com/microsoft/vscode-dotnettools/assets/102629432/f2bf7d8b-b876-43ad-b2ed-58d446634750)

### Benefits

1. Improved Organization: It helps keep your tests neatly organized and easy to locate. This can be particularly useful when dealing with a large number of tests.
2. Efficient Navigation: Testers can quickly navigate to the specific category they are interested in, saving time that would otherwise be spent scrolling through unrelated tests.
3. Easier Maintenance: When tests are grouped by category, it’s easier to maintain and update them. If a change is made that affects a specific category of tests, you can quickly locate and update these tests as needed.
4. Better Understanding: It provides a better understanding of what each test is supposed to validate by grouping related tests together.
5. Enhanced Collaboration: When multiple testers are adding to the repo, having tests grouped by category can help prevent duplication of effort and make it easier to divide work among team members.

Effective test management is maintaining a balance between granularity and simplicity. Too many categories can make the system confusing and difficult to navigate, while too few can lead to disorganization and inefficiency.


### Alternatives considered

_No response_

### Environment Information

![image](https://github.com/microsoft/vscode-dotnettools/assets/102629432/e70dc2c5-e8a9-47b5-be86-456e56420600)
Repository: TypeScript
Issue: Move to new file refactoring ignores "typescript.preferences.importModuleSpecifier": "relative" when `baseUrl` is specified in tsconfig.json
Labels: Possible Improvement

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.86.1
- OS Version: OS: Darwin arm64 21.6.0

Steps to Reproduce:

1. Clone https://github.com/pboyer/vs-code-bug-repro
2. Open in VS Code
3. Note `.vscode/settings.json` specifies `"typescript.preferences.importModuleSpecifier": "relative"`
4. Open `lib/file.ts` and move `someFunction` to a new file using the "Move to new file" refactoring
<img width="445" alt="Screen Shot 2024-02-14 at 11 10 12 AM" src="https://github.com/microsoft/vscode/assets/916345/87121dc6-1703-42f3-a87d-07040dc1b48b">

5. Observe that the import of the new file in `index.ts` is not longer a relative import. That is,
```
import { someFunction } from "./lib/file";
```

Turns into:

```
import { someFunction } from "lib/someFunction";
```

I expected it to become a relative import: 

```
import { someFunction } from "./lib/someFunction";
```

Removing the `baseUrl` field from `tsconfig.json` causes the system to behave as expected.
Repository: flutter
Issue: [Impeller] nodecal fallback for the blur looks wrong
Labels: P2,e: impeller,team-engine,triaged-engine

 https://github.com/flutter/engine/pull/50790 made `impeller_Play_AiksTest_GaussianBlurWithoutDecalSupport_Metal` look worse.  It however was not correct go begin with.  There is some banding after the PR and there is a hard edge before the PR.  We should fix this and I suspect it never worked correctly.
 
<img width="1522" alt="Screenshot 2024-02-21 at 2 00 11 PM" src="https://github.com/flutter/flutter/assets/30870216/a2179bb0-c6d2-480c-956b-275ac4ef0e55">
Repository: node
Issue: Support for WICG Observable
Labels: feature request,never-stale,web-standards

### What is the problem this feature will solve?

This new proposal adds `.on` method to `EventTarget`, then we can control event handling using Observable API.

Example from the spec:

```js
// Filtering and mapping:
element
	.on('click')
	.filter((e) => e.target.matches('.foo'))
	.map((e) => ({ x: e.clientX, y: e.clientY }))
	.subscribe({ next: handleClickAtPoint });
```

Spec: https://github.com/WICG/Observable
Standard Tracking: https://github.com/WICG/observable/issues/93

This is something that makes sense to implement on Node?

### What is the feature you are proposing to solve the problem?

Basically implements the new `.on` method at:

https://github.com/nodejs/node/blob/a0ac8bd4d85e5614f43e4fed3e0c73641cd45fa8/lib/internal/event_target.js#L551


### What alternatives have you considered?

The @benlesh (contributor of the spec) looks like he already tried to implement this new spec at https://github.com/nodejs/node/pull/51065
Repository: flutter
Issue: [Flutter GPU] Standardize a message error pattern.
Labels: engine,c: proposal,P2,team-engine,triaged-engine,flutter-gpu

Part of https://github.com/flutter/flutter/issues/130921

Right now, we have a mix of error handling that may be confusing to users.
- Sometimes a success boolean is returned.
- Sometimes an exception is thrown if there's a problem.
- Sometimes Impeller validation will catch problems and rendering will fail.
- Sometimes the Impeller backend will allow something invalid to happen and rendering will silently fail unless the user has Metal or Vulkan validations enabled.

Recommendation: Bias heavily towards exception throwing.
Repository: flutter
Issue: [Flutter GPU] Add comprehensive docstrings to all public Dart API symbols.
Labels: engine,d: api docs,c: proposal,P2,team-engine,triaged-engine,flutter-gpu

Part of https://github.com/flutter/flutter/issues/130921.

All public classes, methods, and members/fields should be documented following the Flutter style guide.
Repository: flutter
Issue: [Flutter GPU] Design a mechanism to force compatibility between Flutter GPU's Dart runtime and the engine binary.
Labels: engine,c: proposal,P2,team-engine,triaged-engine,flutter-gpu

Part of https://github.com/flutter/flutter/issues/130921
Repository: flutter
Issue: [Flutter GPU] Build an updated example.
Labels: engine,d: examples,c: proposal,P2,team-engine,triaged-engine,flutter-gpu

Part of https://github.com/flutter/flutter/issues/130921

Place this example in the Flutter GPU documentation. Maintain as a repo (like https://github.com/bdero/flutter-gpu-examples).
Repository: go
Issue: x/tools/go/analysis/passes/asmdecl: Test failures
Labels: NeedsInvestigation,Tools

```
#!watchflakes
default <- pkg == "golang.org/x/tools/go/analysis/passes/asmdecl" && test == "Test"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/d8af021aab036d229124626b070e77ebc7c022ff)):

    --- FAIL: Test (22.34s)
        --- FAIL: Test/linux/ppc64 (0.03s)
            analysistest.go:344: loading [a]: err: signal: broken pipe: stderr: 


— [watchflakes](https://go.dev/wiki/Watchflakes)