sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Unexpected Behavior using "after" in middleware
Labels: Middleware

### Link to the code that reproduces this issue

https://github.com/willwill96/nextjs-after-function-repro

### To Reproduce

1. Start the application
2. Fetch `http://localhost:3000` through preferred method
3. Observe Logs for the following
  - Middleware Timing - Start {time}
  - Middleware Timing - End {time} 
  - Page Timing - Start {time}
  - Page Timing - End {time}

### Current vs. Expected behavior

Current Behavior:
`after` blocks within middleware functions are executed before page render begins

Expected Behavior:
[From the docs](https://nextjs.org/docs/app/api-reference/functions/after)
> after allows you to schedule work to be executed after a response (or prerender) is finished.

Based on this, I expect `after` blocks within middleware functions to be executed after page render is finished.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Tue Nov 5 00:21:55 UTC 2024
  Available memory (MB): 47749
  Available CPU cores: 16
Binaries:
  Node: 22.12.0
  npm: 10.9.0
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.1.4 // Latest available version is detected (15.1.4).
  eslint-config-next: 15.1.4
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A
```

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

Middleware

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

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

### Additional context

Example Application Output:
```
Middleware Timing - Start 14041.842787
Middleware Timing - End 14042.483035
Page Timing - Start 14060.135459
 GET / 200 in 27ms
Page Timing - End 14069.832975
```

Relevant code:
- [src/middleware.ts](https://github.com/willwill96/nextjs-after-function-repro/blob/master/src/middleware.ts)
```ts
import { after, NextRequest, NextResponse } from "next/server";

export async function middleware(req: NextRequest) {
    if (req.url === 'http://localhost:3000/') {

        console.log("Middleware Timing - Start", performance.now())
        after(()=>{
          console.log("Middleware Timing - End", performance.now())
        })
    }
    return NextResponse.next()
}
```
- [src/app/page.tsx](https://github.com/willwill96/nextjs-after-function-repro/blob/master/src/app/page.tsx#L5-L8)
```tsx
import { after } from "next/server";

export default function Home() {
  console.log("Page Timing - Start", performance.now())
  after(()=>{
    console.log("Page Timing - End", performance.now())
  })
  return (
    <div className.....
  );
}
```
Repository: flutter
Issue: Cupertino Sheet should bounce slightly when overdragged upwards
Labels: a: fidelity,f: cupertino,P2,team-design,triaged-design

On a native iOS sheet, when you drag it above it's max height, it will move up slightly. Then on gesture release it will snap back in to place. Currently in Flutter it will only drag downwards, then stop at max height when dragged back up again.

Native:

https://github.com/user-attachments/assets/745c0c46-7a28-41bb-9265-1b92353a0f9b
Repository: flutter
Issue: Cupertino Sheet should have drag to dismiss and nested scrolling work together
Labels: a: fidelity,f: scrolling,f: cupertino,P2,team-design,triaged-design

On native iOS, when you have a sheet open with scrollable content, if you start scrolling, it will scroll normally. But then when you drag downwards, once you reach the top of the scrollable content, the sheet starts it's drag to dismiss gesture. Then if you drag back up again, once the the sheet reaches it's original height, the nested scroll starts back up again.

https://github.com/user-attachments/assets/72082b7b-414e-4093-a02a-27b8d2188dd3

In Flutter currently we can either give the nested scroll or the drag to dismiss gesture priority. And we can't switch back and forth between either animations on one drag event.
Repository: flutter
Issue: Change SystemUiOverlayStyle gradually
Labels: c: new feature,a: fidelity,f: cupertino,P2,team-ios,triaged-ios

On native iOS, there is the ability to change the brightness of the system overlay gradually, set to an animation. For example, this happens while the sheet widget is opening. The system overlay (with the time, battery indicator, etc) at the top of the screen changes gradually from dark to light text.

https://github.com/user-attachments/assets/2372e736-75ae-4b6e-8a7f-5b43c874e472

Currently if the Flutter framework we are only able to change it suddenly with the `SystemChrome.setSystemUIOverlayStyle` API.
Repository: kubernetes
Issue: Remove the MD5 hash function for FIPS compliance
Labels: sig/network,kind/feature,triage/accepted

### What would you like to be added?

For now, there seems to be a hardcoded usage of MD5 in the [source code](https://github.com/kubernetes/kubernetes/blob/master/pkg/api/v1/endpoints/util.go#L157), which is not FIPS compliant, and there is no configurable way to avoid it by declaring to use other hash functions like SHA256. When using the K8S with FIPS-compliant Go, `panic: openssl: unsupported hash function: 2` error is expected.

It would be great if the default hash function can be changed to a FIPS-compliant one, like SHA256. Or making it configurable via config files or something, that would be even better.

### Why is this needed?

This matters to people who need FIPS-compliant K8S clusters, and there is no obvious workaround at the moment.
Repository: flutter
Issue: [a11y] hotkey widget should have correct semantics
Labels: P3,team-accessibility,triaged-accessibility

When using https://api.flutter.dev/flutter/widgets/Shortcuts-class.html, the loading spinner should have following role
| OS | role |
|--------|--------|
| web |- |
| ios | - |
| macos | - |
| windows | ROLE_SYSTEM_HOTKEYFIELD |
| android | - |
Repository: flutter
Issue: [a11y][two_dimensional_scrollables] Tree view is missing semantics role
Labels: P3,team-accessibility,triaged-accessibility

https://github.com/flutter/packages/tree/main/packages/two_dimensional_scrollables/lib/src/tree_view

For Tree
| OS | role |
|--------|--------|
| web | tree |
| ios | - |
| macos | NSAccessibilityOutlineRole |
| windows | ROLE_SYSTEM_OUTLINE |
| android | - | 


for Tree item
| OS | role |
|--------|--------|
| web | treeitem |
| ios | - |
| macos | NSAccessibilityRowRole, NSAccessibilityOutlineRowSubrole |
| windows | ROLE_SYSTEM_OUTLINEBUTTON or ROLE_SYSTEM_OUTLINEITEM |
| android | - |
Repository: PowerToys
Issue: Preview not working
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

latest

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

try to peek a wav file

### ✔️ Expected Behavior

working for wav files

### ❌ Actual Behavior

not working for wav files

### Other Software

_No response_
Repository: godot
Issue: Scene lighting is bugged on integrated graphics
Labels: bug,topic:rendering,topic:3d

### Tested versions

Reproducible in:
- v4.2.2.stable.official [15073afe3]
- v4.3.stable.official [77dcf97d8]
- v4.4.dev7.mono.official [46c8f8c5c]

### System information

Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - integrated Intel(R) Iris(R) Xe Graphics (Intel Corporation; 31.0.101.5186) - 12th Gen Intel(R) Core(TM) i7-1255U (12 Threads)

### Issue description

I am working on a 3D game with a team and noticed the lighting does not work properly, but on only my computer. Meshes are way too bright and "glowy", and performance is noticeably reduced. My other team members had no lighting issues on their systems, which included:
- M4 Mac Mini Base Model
- Xubuntu 24.04.1 LTS
OpenGL API 4.6 Mesa 24.0.9-0ubuntu0.1 - Compatibility - Using Device: AMD - AMD Radeon Vega 3 Graphics (radeonsi, raven2, LLVM 17.0.6, DRM 3.57, 6.8.0-51-generic)
AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx

How the lighting looks on the 2 systems mentioned above (and what it should look like):
![Image](https://github.com/user-attachments/assets/99b40807-7446-45f7-88d4-feffa7992da2)

The bugged lighting on my system:
![Image](https://github.com/user-attachments/assets/7a465cc0-105b-4e20-b840-04263c3e6275)

The issue seems to be related to SDFGI, since the lighting looks normal after disabling it:
![Image](https://github.com/user-attachments/assets/bd264ba1-1e4a-43ec-9c81-f49d1ce6a96d)
I'm aware that SDFGI is not recommended for integrated graphics, but the extra glow coming from meshes looks unintended and more than just a performance issue.


I've also included more information about my system and hardware here:
https://gist.github.com/donodj/18ff377a020a7e0708b39156b8c34a0d

### Steps to reproduce

1. Create a new godot project on a computer with Intel(R) Iris(R) Xe Graphics (or possibly any integrated GPU) and make a new scene
2. Add any MeshInstance3D with the material.tres material from the MRP
3. Add the WorldEnvironment and DirectionalLight3D from the bugged_environment.tscn scene in the MRP
4. The mesh should now appear "glowy" from the lighting in the scene

### Minimal reproduction project (MRP)

[godot-lighting-bug-main.zip](https://github.com/user-attachments/files/18428768/godot-lighting-bug-main.zip)
Contains a scene showing the bugged lighting and a scene with Godot's default lighting (which has no problems)
Repository: PowerToys
Issue: Mouse Without Borders broken?
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

Not sure how to reproduce this, but my systems that only yesterday used to connect just fine on Mouse Without Borders now seem unable to do so. They're still on the same LAN, and even when I "Refresh connections", all that I see is yellow, orange and blue borders around the machine representations under Device layout.

<!-- Failed to upload "PowerToysReport_2025-01-15-11-41-03.zip" --> [Not sure why the upload keeps failing]

### ✔️ Expected Behavior

The systems should continue connecting as they did before.

### ❌ Actual Behavior

They don't connect anymore.

### Other Software

_No response_
Repository: godot
Issue: source_color not working properly
Labels: bug,needs testing,topic:shaders

### Tested versions

tested in 4.3 and 4.4 dev builds

### System information

Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 960 (NVIDIA; 32.0.15.6636) - Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz (4 Threads)

### Issue description

Instantiating a new `ShaderMaterial` results in the default uniform values marked `source_color` to skip the sRGB-to-linear transform.

- If the same scene is saved and reloaded, the correct color is rendered.
- If the uniform parameter is set in the inspector or by `set_shader_parameter()`, the correct color is rendered.

Workaround: manually set the uniform to it's own default after instantiating.
```gdscript
material.set_shader_parameter(p_name, RenderingServer.shader_get_parameter_default(material.shader.get_rid(), p_name))
```

### Steps to reproduce

- Create a MeshInstance3D of a plane
- Assign a new ShaderMaterial
- Assign a shader that displays a uniform vec3 of source_color
```
shader_type spatial;
render_mode unshaded;

uniform vec3 test_color: source_color = vec3(0.2, 0.5, 0.2);

void fragment() {
	ALBEDO = test_color;
}
```
Note that the color looks washed out.
Save the scene and reload, it now looks correct.

### Minimal reproduction project (MRP)

![Image](https://github.com/user-attachments/assets/8638e43c-16a6-4858-b7a4-9b90e9c650b5)
[source_color_bug.tscn.zip](https://github.com/user-attachments/files/18429610/source_color_bug.tscn.zip)
Repository: flutter
Issue: [Proposal] TabBar - allow disabled tabs
Labels: c: new feature,framework,f: material design,c: proposal,P2,team-design,triaged-design

### Use case

It would be nice to have a disabled tab feature

### Proposal

Let's have a disabled tab functionality
Repository: flutter
Issue: TabBar - spacing
Labels: waiting for customer response,in triage

### Use case

Current `labelPadding` adds padding but it does not allow to set spacing 
Also `labelPadding` is a part of active area, it would be nice to have spacing non tapable

### Proposal

Same as Row has which were added in 3.27
Repository: pytorch
Issue: TIMM cudagraphs_freezing inference regression
Labels: high priority,triaged,module: cuda graphs,oncall: pt2,pt2-pass-rate-regression

https://hud.pytorch.org/benchmark/timm_models/inductor_with_cudagraphs_freezing?dashboard=torchinductor&startTime=Mon,%2016%20Dec%202024%2020:49:27%20GMT&stopTime=Wed,%2015%20Jan%202025%2020:49:27%20GMT&granularity=day&mode=inference&model=lcnet_050&dtype=bfloat16&deviceName=cuda%20(a100)&lBranch=main&lCommit=1dab79470dbecef79ba4c7d4308d8a181091e58e&rBranch=main&rCommit=297ce776363cc4802fa74d210fced2b4128960d5

This model used to pass sometime in the last year but is now failing with an accuracy issue

cc @ezyang @gchanan @kadeng @msaroufim @mcarilli @eellison @penguinwu @BoyuanFeng @chauhang
Repository: go
Issue: x/tools/gopls: record telemetry for which settings are used
Labels: gopls,Tools

We want to use telemetry to answer questions about which settings are being customized by our users. This signal can be useful in a number of ways, for example to prioritize improvements to various optional features, suggest that certain configuration can be deprecated, or indicate that certain optional features are not working well (if they are frequently disabled).

A few considerations:
- For some settings, we just want to record whether they are used (e.g.  "buildFlags").
- For other settings, we want to bucket the actual setting values (e.g. "staticcheck:true")
- For yet other settings, there are logical sub-settings which may themselves have logical bucketing (e.g. "analyses/deprecated:false").
- Some settings can be set in multiple ways (usually in a transitional period when an old setting name is deprecated).

Therefore, this instrumentation will necessarily be customized to each individual setting.

The following schema seems pretty natural: `gopls/setting/<setting>[/<subsetting>][:buckets]`

For example, given the following configuration

```json
{
  "buildFlags": ["-tags=mytag"],
  "staticcheck": true,
  "analyses": {
    "deprecated": false,
  }
}
```

we'd record the following counts:

```
gopls/setting/buildFlags
gopls/setting/staticcheck:true
gopls/setting/analyses/deprecated:false
```

Notably, we only record the settings that are actually explicitly set by the user. We don't record the effective values of all settings. I briefly considered recording the effective values of each setting, but that is a lossy projection: it loses information about which settings are actually being explicitly set, and we may want to see when users are customizing a setting, _even if they are customizing it to the default value_.

This issue tracks only the addition of this instrumentation. Separate telemetry proposals must be filed for any collection of this data from users who have opted in to telemetry.

CC @adonovan
Repository: pytorch
Issue: Ways the HUD compilers dashboard could be better
Labels: triaged,enhancement,module: devx

I got here because I'm trying to answer the question of "which compiler benchmarks regressed in the past year?" I've spent a couple of hours on the HUD dashboard page, and I still haven't figured this out yet. Here's some of the gripes that I ran into while trying to answer this question.

1) The page seems to refresh itself every couple of minutes. This disrupts the train of thought. Also, I am not sure if the settings change when it refreshes.
2) The passrate chart and the graphs don't have all of the data. In particular, the passrate chart doesn't contain the max_autotune configs. I don't know how to actually click into the max_autotune data.

![Image](https://github.com/user-attachments/assets/f66889a3-8349-4725-b477-d8039d4cf8be)

3) https://github.com/pytorch/test-infra/issues/6173
4) There's one passrate chart but there are 3 passrate graphs. Scrolling between the graphs is kind of annoying
5) The graphs have so many series that some of them are hidden. Might be nicer to increase the height?

![Image](https://github.com/user-attachments/assets/ad10f73d-ab84-486f-989c-70f34bc86022)

6) It's not clear to me how to hack on these charts. Using our internal tools (like scuba and unidash), it's easy (and well-known) on how to look up information.

Hypothesis: If we feed the data to internal sources and use internal tooling as the UXs, then we would be more productive than trying to roll our own UX.

cc @ZainRizvi @kit1980 @huydhn @clee2000
Repository: pytorch
Issue: TorchBench mobilenet_v2 cudagraphs_freezing inference regression
Labels: high priority,triaged,module: cuda graphs,oncall: pt2,pt2-pass-rate-regression

https://hud.pytorch.org/benchmark/torchbench/inductor_with_cudagraphs_freezing?dashboard=torchinductor&startTime=Fri,%2019%20Jul%202024%2020:38:32%20GMT&stopTime=Wed,%2015%20Jan%202025%2021:38:32%20GMT&granularity=week&mode=inference&model=mobilenet_v2&dtype=bfloat16&deviceName=cuda%20(a100)&lBranch=main&lCommit=2ed4d65af0a1993c0df7b081f4088d0f3614283e&rBranch=main&rCommit=a8319698b3ba7c858fa3e4f3aac88d3fe9dc00d1

Regressed sometime in August

cc @ezyang @gchanan @kadeng @msaroufim @mcarilli @eellison @penguinwu @BoyuanFeng @chauhang
Repository: go
Issue: x/tools/gopls: show underlying type on hover over alias
Labels: help wanted,FeatureRequest,gopls,Tools

### gopls version

golang.org/x/tools/gopls v0.17.1

### go env

```shell
n/a
```

### What did you do?

Note: this is a feature request

Given
```go
// This is a dog.
type Dog struct {
    Name string `json:"name"`
    Age int `json:"age"`
}

type Hound = Dog

// A Puppy is a Dog with an age less than 2.
type Puppy = Dog
```

I hovered over `Hound` and `Puppy`

### What did you see happen?

The hover message reads

```go
type Hound = Dog
```
and respectively

```go
type Puppy = Dog

A puppy is a dog with an age less than 2.
```



### What did you expect to see?

```
type Hound = Dog

This is a dog.

type Dog struct {
    Name string `json:"name"`
    Age int `json:"age"`
}
```
and respectively

```
type Puppy = Dog

A puppy is a dog with an age less than 2.

type Dog struct {
    Name string `json:"name"`
    Age int `json:"age"`
}
```

I like the semantic that docstrings are inherited if, and only if, the alias provides no docstring of its own.

### Editor and settings

n/a

### Logs

n/a
Repository: pytorch
Issue: TIMM Training cudagraphs poolformer_m36 regression
Labels: high priority,triaged,module: cuda graphs,oncall: pt2,pt2-pass-rate-regression

Used to pass, now "eager_two_runs_differ". This probably just needs some tolerance adjustments 

https://hud.pytorch.org/benchmark/timm_models/inductor_with_cudagraphs?dashboard=torchinductor&startTime=Fri,%2019%20Jul%202024%2020:48:05%20GMT&stopTime=Wed,%2015%20Jan%202025%2021:48:05%20GMT&granularity=week&mode=training&model=poolformer_m36&dtype=amp&deviceName=cuda%20(a100)&lBranch=main&lCommit=1dab79470dbecef79ba4c7d4308d8a181091e58e&rBranch=main&rCommit=a8319698b3ba7c858fa3e4f3aac88d3fe9dc00d1

cc @ezyang @gchanan @kadeng @msaroufim @mcarilli @eellison @penguinwu @BoyuanFeng @chauhang
Repository: pytorch
Issue: DISABLED test_mismatched_global_state (__main__.GraphRegionTrackerTests)
Labels: module: rocm,triaged,module: flaky-tests,skipped

Platforms: rocm

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_mismatched_global_state&suite=GraphRegionTrackerTests&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/35666846912).

Over the past 3 hours, it has been determined flaky in 9 workflow(s) with 18 failures and 9 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_mismatched_global_state`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `dynamo/test_graph_region_tracker.py`

ConnectionTimeoutError: Connect timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/dynamo/test_graph_region_tracker.py -2 (connected: false, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0)
headers: {}

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd @clee2000 @wdvr
Repository: pytorch
Issue: DISABLED test_recompile_on_global_state_change_dynamic_shapes (__main__.DynamicShapesMiscTests)
Labels: module: rocm,triaged,module: flaky-tests,skipped

Platforms: rocm

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_recompile_on_global_state_change_dynamic_shapes&suite=DynamicShapesMiscTests&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/35670761806).

Over the past 3 hours, it has been determined flaky in 9 workflow(s) with 18 failures and 9 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_recompile_on_global_state_change_dynamic_shapes`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/pytorch/test/dynamo/test_misc.py", line 7855, in test_recompile_on_global_state_change
    assert read_state() == new_state
AssertionError
```

</details>


Test file path: `dynamo/test_dynamic_shapes.py`

ConnectionTimeoutError: Connect timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/dynamo/test_dynamic_shapes.py -2 (connected: false, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0)
headers: {}

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd @clee2000 @wdvr