sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: SCSS file imports break without declaring `'use client'`
Labels: bug,Runtime

### 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 21.6.0: Mon Aug 22 20:19:52 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.14.2
      npm: 9.5.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.10-canary.3
      eslint-config-next: 13.1.1
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.5
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/payloadcms/next-payload-demo

### To Reproduce

The reproduction repo is deployed in production at the following link:

https://nextjs-vercel.payloadcms.com/api/users/me

To see the issue, navigate to the `/api/users/me` route. The page will 500.

### Describe the Bug

The `/api/users/me` endpoint is a serverless function in the `/pages/api` folder which imports a Payload config, and the Payload config imports `.scss` files. The config is isomorphic and is used within server-side code as well as the client bundle.

The serverless function is unable to parse the `.scss` file, and errors, causing a 500.

This is only an issue when deployed to Vercel (in production mode, locally, this works fine.) And it used to work fine a few weeks ago (this is a new issue with no changes on our end.)

### Expected Behavior

A few weeks ago, `.scss` file imports used to not break serverless functions in the `/pages/api` folder, but now they are causing issues. It appears that adding the directive `'use client'` to the top of any files that import `.scss` will fix the problem, but I wanted to know if there was a way to just safely ignore `.scss` files within the `/pages/api` folder by using something like `null-loader` or similar.

I would also just like to understand what the underlying change was to Next that caused this issue to appear.

Thank you!

### Which browser are you using? (if relevant)

N/A

### How are you deploying your application? (if relevant)

Vercel
Repository: TypeScript
Issue: LSP: missing completions
Labels: Help Wanted,Possible Improvement

# Bug Report

### 🔎 Search Terms

### 🕗 Version & Regression Information

This exists in various versions, like 4.4.4, 5.1.6 and nightly. Bug can be reproduced in VS Code & WebStorm.

- This is a crash: **No**
- This changed between versions: **No**
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about: **Yes**
- I was unable to test this on prior versions because: **Bug is reproducible in various versions**

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?#code/KYDwDg9gTgLgBAYwDYEMDOa4DEITgbwCg44pgUATCAOyQE840IBbYANRSjgF44ByAGa4+hYnABGnABQBKIiRIIaaeELy8YACwCWaAHRwA9IbgAeALRxNwMnG3w0miAFckFRk4DucZrrTbqAHNEFjAkYBhtZTgkbQBrYAkUAC9ZOAAyOBRqCC0bAHlqYFlRBVII5yhqAiTkgC44LV09SVSZOABfMS6xVrT8HpJs3OsoQuL2gcIuoA)

### 💻 Code

```ts
export class Foo {
  readonly someVar = 'foo'

  bar(){
    const foo = this. // <- here it should show missing completions like baz() & anotherOne()

    return { baz: this.baz() }
  }

  baz() {}

  anotherOne() {}
}
```

### 🙁 Actual behavior

It is missing completions of methods like `baz()` & `anotherOne()`.

### 🙂 Expected behavior

I expect to have missing completions mentioned above. In my opinion LSP should skip that error and try to provide completions, because after I select it, it is a valid code.
Repository: storybook
Issue: [Bug]: Out-of-memory crash on some stories with Storybook 7
Labels: bug,needs triage

### Describe the bug

On some stories in an existing repo that was recently updated from Storybook 6 to Storybook 7, the browser crashes when loading a story and/or changing controls on a story. I have not been able to track down what's causing it, but I can see in the Firefox profiler that the amount of memory used steadily increases and, in Chrome, the debugger pauses before "potential out-of-memory" crash. I can also see that `prettyPrint` gets called repeatedly before the crash.

### To Reproduce

I have not been able to figure out why Storybook crashes on some stories but not others, but when it does so, it does so consistently. On my current story, every change of a control causes a memory spike and crash in both Chrome and Firefox.

### System

```shell
Environment Info:

  System:
    OS: macOS 13.4.1
    CPU: (8) x64 Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz
  Binaries:
    Node: 16.20.1 - ~/.nvm/versions/node/v16.20.1/bin/node
    npm: 9.8.0 - ~/.nvm/versions/node/v16.20.1/bin/npm
  Browsers:
    Chrome: 114.0.5735.198
    Safari: 16.5.1
  npmPackages:
    @storybook/addon-a11y: ^7.0.22 => 7.0.26
    @storybook/addon-actions: ^7.0.22 => 7.0.26
    @storybook/addon-controls: ^7.0.22 => 7.0.26
    @storybook/addon-docs: ^7.0.22 => 7.0.26
    @storybook/addon-links: ^7.0.22 => 7.0.26
    @storybook/addon-styling: ^1.3.0 => 1.3.2
    @storybook/addon-viewport: ^7.0.22 => 7.0.26
    @storybook/addons: ^7.0.22 => 7.0.26
    @storybook/blocks: ^7.0.22 => 7.0.26
    @storybook/react: ^7.0.22 => 7.0.26
    @storybook/react-webpack5: ^7.0.22 => 7.0.26
```


### Additional context

_No response_
Repository: godot
Issue: Calling call_deferred on a Callable will fail silently if the arguments passed don't match the function signature
Labels: bug,topic:core

### Godot version

4.1.0

### System information

Godot v4.1.stable - Windows 10.0.19045 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 2080 (NVIDIA; 31.0.15.3179) - Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 Threads)

### Issue description

Calling call_deferred on a Callable will fail silently if the arguments passed don't match the function signature.



### Steps to reproduce

```gdscript
func _ready():
        # print_message_arg1 won't be called, but an error will be logged
        call_deferred("print_message_arg1")
        # print_message_arg1 won't be called, and no error will be logged
	print_message_arg1.call_deferred()
	print_message_arg1.call_deferred({type_mismatch = true})

func print_message_arg1(arg1: String):
	print("i'm called with %s" % [arg1])
```

### Minimal reproduction project

N/A
Repository: storybook
Issue: [Bug]: Running a `Play` function in Jest does not re-render after state update
Labels: bug,needs triage

### Describe the bug

There's a problem using storybook interactions and storybook jest when updating a state. When updating the state inside a play function, the component does not re-render and thus does not get the state update.

It works perfectly in the browser, but not when running it via jest.

### To Reproduce

I made a small reproduction here: https://github.com/Itrulia/storybook-play-state-problem

The stories can be found here: https://github.com/Itrulia/storybook-play-state-problem/blob/main/apps/storybook-play-state-problem/components/abc.stories.tsx

### System

```shell
Environment Info:
(node:67889) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

  System:
    OS: macOS 13.1
    CPU: (8) arm64 Apple M1 Pro
  Binaries:
    Node: 18.0.0 - ~/.nvm/versions/node/v18.0.0/bin/node
    Yarn: 1.22.18 - /opt/homebrew/bin/yarn
    npm: 8.6.0 - ~/.nvm/versions/node/v18.0.0/bin/npm
  Browsers:
    Chrome: 114.0.5735.198
    Safari: 16.2
  npmPackages:
    @storybook/addon-essentials: ^7.0.24 => 7.0.26
    @storybook/addon-interactions: ^7.0.26 => 7.0.26
    @storybook/core-common: ^7.0.24 => 7.0.26
    @storybook/core-server: ^7.0.24 => 7.0.26
    @storybook/jest: ^0.1.0 => 0.1.0
    @storybook/nextjs: ^7.0.24 => 7.0.26
    @storybook/testing-library: ^0.2.0 => 0.2.0
```


### Additional context

You can also checkout the test logs here: https://github.com/Itrulia/storybook-play-state-problem/actions/runs/5522120336/jobs/10071232832

You will see that only the initial state is ever `console.log`ed
Repository: godot
Issue: @export_node_path reset after reload project
Labels: topic:core,topic:gdscript,needs testing

### Godot version

4.1.stable

### System information

Win 10, i5-11400H, 16GB RAM, RTX3050M

### Issue description

My plugin has the following code:
```
@export_node_path("RailWay") var real_railway = null :
	set = tool_real_railway_event
func tool_real_railway_event(railway):
	if not Engine.is_editor_hint() or railway == null or get_node(railway) is RailWay:
		real_railway = railway
		if Engine.is_editor_hint() and real_position_railway>=get_node(railway).length_path()-CAR_LENGTH:
			tool_real_position_railway_event(get_node(railway).length_path()-(CAR_LENGTH+1))
```
And if you set a variable value through the inspector, save and then restart the project, the variable is reset, and the following message appears in the console:
```
  editor/editor_node.cpp:3304 - Condition "p_enabled && addon_name_to_plugin.has(addon_path)" is true.
  Node not found: "../Train API/railway2" (relative to "Carriage").
```

Here is the full console log:
```
Godot Engine v4.1.stable.official (c) 2007-present Juan Linietsky, Ariel Manzur & Godot Contributors.
  modules/gltf/register_types.cpp:73 - Blend file import is enabled in the project settings, but no Blender path is configured in the editor settings. Blend files will not be imported.
Train API: plugin.gd: START
Train API: Язык редактора: РУССКИЙ
Train API: plugin.gd: _make_visible() -> editor gui visible is false
  editor/editor_node.cpp:3304 - Condition "p_enabled && addon_name_to_plugin.has(addon_path)" is true.
"Train API" : ON
  Node not found: "../Train API/railway2" (relative to "Carriage").
Train API: Carriage: tool_car_length_reset() -> update to 80
Train API: railway: event_gui_way() -> update
Train API: railway2: event_gui_way() -> update
Train API: railway3: event_gui_way() -> update
Train API: plugin.gd: _make_visible() -> editor gui visible is false
Train API: Язык редактора: РУССКИЙ
Train API: plugin.gd: _make_visible() -> editor gui visible is false
Train API: plugin.gd: _make_visible() -> editor gui visible is true
Train API: plugin.gd: _make_visible() -> editor gui visible is true
Train API: plugin.gd: _make_visible() -> editor gui visible is false
Train API: Carriage: tool_car_length_reset() -> update to 80
Train API: railway: event_gui_way() -> update
Train API: railway2: event_gui_way() -> update
Train API: railway3: event_gui_way() -> update
Train API: plugin.gd: _make_visible() -> editor gui visible is true
Train API: plugin.gd: _make_visible() -> editor gui visible is true
```

### Steps to reproduce

Here is the script itself:
[carriage.gd.zip](https://github.com/godotengine/godot/files/12016637/carriage.gd.zip)



### Minimal reproduction project

If you need a complete project, download my "Train API" repository.
Repository: tensorflow
Issue: tf.image.adjust_contrast fails on the tf.half data type
Labels: awaiting review,type:bug,comp:apis,comp:ops,TF 2.13

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

2.13.0

### Custom code

Yes

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

I was trying tf.image.adjust_contrast but I find that it fails when I set the input tensor's data type to be `float16 (tf.half)`, this API raises error. However, if I set the input data type to be `bfloat16`, this API works properly. 

### Standalone code to reproduce the issue

```shell
import tensorflow as tf
import numpy as np
np.random.seed(1234)
t = tf.constant(np.random.rand(1,2,1), dtype=tf.float16)
i = tf.image.adjust_contrast(t, 2.)
print(i)
```
```


### Relevant log output

```shell
NotFoundError: Could not find device for node: {{node AdjustContrastv2}} = AdjustContrastv2[T=DT_HALF]
All kernels registered for op AdjustContrastv2:
  device='XLA_CPU_JIT'; T in [DT_FLOAT, DT_HALF]
  device='CPU'; T in [DT_FLOAT]
  device='GPU'; T in [DT_HALF]
  device='GPU'; T in [DT_FLOAT]
  device='XLA_GPU_JIT'; T in [DT_FLOAT, DT_HALF]
 [Op:AdjustContrastv2] name:
```
Repository: next.js
Issue: App router: Components in root layout rerender on navigation
Labels: bug,Navigation

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home
    Binaries:
      Node: 18.16.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.10-canary.3
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router, Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/jk1x8/App-router-issue

### To Reproduce

1. Clone the repo [https://github.com/jk1x8/App-router-issue](url)
2. After installing dependencies run `npm run build` and `npm start`, then open the app and navigate between pages. You will see (in the console) that navbar component that is placed in root layout rerenders on every route change.
3. Run `npm run dev`, open app and you will see no rerenders of navbar during navigation, in dev mode  components placed in root layout don't change.

### Describe the Bug

Client components in root layout are re-rendering on every navigation change **in production mode**. When React.memo is added it's even worse, the not only rerender but loose their state on route change. In dev mode everything is fine, they don't re-render when the page is changed. I have a client-component Navbar that is shared accros the whole app
![image](https://github.com/vercel/next.js/assets/139253153/e949b643-f009-4334-8145-38bfa1a766cd)
 and should not rerender on page change. In dev mode  it work's fine but there are problems after building the app. React StrictMode is disabled.
![image](https://github.com/vercel/next.js/assets/139253153/7020a1e9-e037-4394-9b5a-dc1edc5b39bf)


### Expected Behavior

Components, even client components placed in layout should not rerender on navigation.

### Which browser are you using? (if relevant)

Chrome

### How are you deploying your application? (if relevant)

_No response_
Repository: next.js
Issue: Include inline JS script in head tag
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.16.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.10-canary.3
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: N/A
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/ajaz-thiscar/nextjs-js-in-head

### To Reproduce

1. git clone https://github.com/ajaz-thiscar/nextjs-js-in-head
2. cd nextjs-js-in-head
3. run **npm install**
4. Open src/app/layout.js and src/app/page.js to verify google js code that should appear in head tag. Screenshots both files attached below.
5. run **npm run dev**
6. Navigate to localhost:3000
7. Veiw HTML source to verify that google js code not appearing in head except for js url https://www.googletagmanager.com/gtag/js?id=GA_MEASUREMENT_ID

![image](https://github.com/vercel/next.js/assets/139249653/b1caa018-85b8-4f8c-b0b1-648632b507b2)
![image](https://github.com/vercel/next.js/assets/139249653/593073e4-73ac-4f28-9b55-ee21b7b85b43)



### Describe the Bug

In order to add google tracking code snippet in head of html document, we followed normal Script component in layout.js and a solution provided by [NextJS webiste](https://nextjs.org/docs/messages/next-script-for-ga) . The Script component is not placing js snippet in head tag.

### Expected Behavior

The Next Script component should place the JS snippet in head tag instead of body tag.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: godot
Issue: Omni light  shadow softness exhibits  more aliasing than spot light soft shadows
Labels: discussion,topic:rendering,topic:3d

### Godot version

4.2 dev #61834  4.1 stable

### System information

Windows 11 amd radeon Tm graphics , 8gb ram, vulkan clustered

### Issue description

It seems like while  the spot light shadows  can benefit significantly from the softness filtering(pcf)  from this images, showing it correctly applied in the screenshots below.

Hard filter(no softness)

![editor_screenshot_2023-07-11T182327](https://github.com/godotengine/godot/assets/97898580/524eb2ed-f250-465f-b321-96f33efb41cd)

Soft low
![editor_screenshot_2023-07-11T183622](https://github.com/godotengine/godot/assets/97898580/1becc979-e656-40c8-8e69-3ee3a3e421c7)

Soft ultra 
![editor_screenshot_2023-07-11T183740](https://github.com/godotengine/godot/assets/97898580/62c2c634-12ab-4c3a-ba1f-e6c131ce16c7)

As seen the soft filter is well applied and it possitively affected on the spot light shadows, while in the case of the omni light shadows(cubemap), the pcs doesn´t make much effect on hiding the aliased edge, even though it 4048 resolution as seen.

Hard filter(no softness)

![editor_screenshot_2023-07-11T184230](https://github.com/godotengine/godot/assets/97898580/8fdc0143-cddc-46f7-9380-edeb8d2707ba)

Soft low

![editor_screenshot_2023-07-11T184319](https://github.com/godotengine/godot/assets/97898580/ba3bb396-a4aa-4e1a-bbd7-e7f8c8bc0af6)

Soft ultra

![editor_screenshot_2023-07-11T184402](https://github.com/godotengine/godot/assets/97898580/d49a80ab-a913-4a23-8d6e-2abbf2143da0)

Even though it applies here the smoothness it does not seem to hide the aliasing that are on the shadows  unlike the spotlight, it specially noticeable when you are close to  the shadows that it tries to hide it, but it doesn´t match at all .

### Steps to reproduce

1 Open the MRP

2 switch between enabling spot or omni lights  visibility to seeing their specific look, to not confuse between them.

3 You can compare the shadows look changing the filter sethings at the lights and shadows tab from the project  sethings.

### Minimal reproduction project

[shadows_test.zip](https://github.com/godotengine/godot/files/12017134/shadows_test.zip)
Repository: vscode
Issue: Scrollback position toggle in Interactive Window
Labels: bug,interactive-window

Just the ability to toggle whether new output resets scroll position.

Sometimes I have a long-running job with periodic log output and finding / yanking old output can be almost impossible
Repository: next.js
Issue: Unexpected middleware response headers present on headers() in app router
Labels: bug,Runtime,linear: next

### 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 22.5.0: Thu Jun  8 22:22:23 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6020
    Binaries:
      Node: 16.19.1
      npm: 8.19.3
      Yarn: 1.22.19
      pnpm: 7.30.3
    Relevant Packages:
      next: 13.4.10-canary.3
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router, Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/gaspar09/set-set-headers-middleware-nextjs

### To Reproduce

visit https://set-set-headers-middleware-nextjs.vercel.app/header?h=2
See the headers:
> x-vercel-header-request = 2
> x-vercel-header-response = 2

### Describe the Bug

A response header `x-vercel-header-response` is set in middleware. 
That header is available on an app router page via `import { headers } from "next/headers";`

### Expected Behavior

Expected that `x-vercel-header-response` is not present on `headers()`

### Which browser are you using? (if relevant)

Chrome

### How are you deploying your application? (if relevant)

Vercel

<sub>[NEXT-1435](https://linear.app/vercel/issue/NEXT-1435/unexpected-middleware-response-headers-present-on-headers-in-app)</sub>
Repository: PowerToys
Issue: Microsoft publisher PUB file thumbnail view and file preview in Explorer
Labels: Needs-Triage

### Description of the new feature / enhancement

A thumbnail and preview window preview function for publisher [PUB] files.

If you research there are many people out there that are rather upset that of all the files, Microsoft Publisher has no longer a file preview in "Explorer". This is absurd in its own way considering that the publisher is essentially an app used to create visual documents.
The alternate "solutions" offered on the web are equal to tearing down the house and rebuilding it when the front door jams...
Microsoft's "answer" is equal to that famous uncivilized silent greeting with a hand...



### Scenario when this would be used?

Like many, clients and myself work with publisher and have a lot of publications it would be enormously beneficial and truly all help to increase "productivity" if any publisher files can be previewed in Explorer!
After all, many other files can be previewed including all within the Microsoft Office 365 package, except of course the included publisher!

### Supporting information

_No response_
Repository: go
Issue: os/signal: TestTime killed with SIGQUIT on netbsd
Labels: help wanted,OS-NetBSD,NeedsInvestigation,compiler/runtime

```
#!watchflakes
post <- pkg == "os/signal" && test == "TestTime" && goos == "netbsd" && `SIGQUIT`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/784486787f286a4ee61a63cf1dd0ff462fdfbfa1)):

    SIGQUIT: quit
    PC=0x200167e2c m=10 sigcode=0
    
    r0      0x4
    r1      0x0
    r2      0x0
    r3      0x0
    r4      0x400003bb40
    r5      0x0
    r6      0x4000122820
    ...
    
    runtime.gopark(0x4000032e68?, 0x200104d98?, 0x78?, 0x2e?, 0x20010ca8c?)
    	/var/gobuilder/buildlet/go/src/runtime/proc.go:363 +0xe4 fp=0x4000032df0 sp=0x4000032dd0 pc=0x200137e84
    runtime.chanrecv(0x40001921e0, 0x0, 0x1)
    	/var/gobuilder/buildlet/go/src/runtime/chan.go:583 +0x47c fp=0x4000032e80 sp=0x4000032df0 pc=0x20010608c
    runtime.chanrecv1(0x4000192180?, 0x37768e5f1?)
    	/var/gobuilder/buildlet/go/src/runtime/chan.go:442 +0x14 fp=0x4000032eb0 sp=0x4000032e80 pc=0x200105bd4
    os/signal.TestTime(0x4000184680?)
    	/var/gobuilder/buildlet/go/src/os/signal/signal_test.go:689 +0x21c fp=0x4000032f60 sp=0x4000032eb0 pc=0x2001ccdbc
    testing.tRunner(0x4000184b60, 0x2002404c0)


— [watchflakes](https://go.dev/wiki/Watchflakes)