sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tauri
Issue: [help] getting a basic example of using Tauri driver and testing invoked commands working
Labels: type: question,scope: webdriver

I am trying to test a full demo application with Selenium.  By "full" I mean not just the testing as demonstrated by the [Hello Tauri app](https://tauri.app/v1/guides/testing/webdriver/example/selenium) which references [this example code](https://github.com/chippers/hello_tauri) but instead something that invokes a command in Rust.  I am using the app I made by following [this tutorial](https://tauri.app/v1/guides/getting-started/setup/vite#invoke-commands), and it runs normally with cargo tauri dev --release, but when I try to test it with Mocha and Selenium, the application does not appear to start properly.  That is, the binary gets run, and it pops up a Tauri app that says "Could not connect: Connection refused".

I have two questions:  

1. Should it be possible to test a Tauri app with Selenium, including the invoking of Rust commands? 
2. If the answer to question 1 is "yes", do you know what I am doing wrong?  I made [this repo](https://github.com/stephen-h-d/tauri_driver_usage_demo) which contains all the relevant code.  I can provide more details if needed.

(I previously opened a support post in the Tauri Apps discord server but haven't gotten a response yet.)
Repository: godot
Issue: Polygon2D UVs are never available to canvasitem shader materials
Labels: discussion,topic:rendering,documentation,topic:shaders,topic:2d

### Godot version

4.1.1

### System information

LIinux Mint; RTX 3050

### Issue description

When using Polygon2D with a shader material, UV always comes back as zero, in spite of UVs being set in the appropriate array.

![image](https://github.com/godotengine/godot/assets/7585255/1b414cb0-b551-4900-b3b6-5eb9a3fb8f71)
![image](https://github.com/godotengine/godot/assets/7585255/b636c2b2-9a8b-4ea6-a630-51e7360ad57e)

As you can see here, UV is set to appropriate values in the array, but this does not carry over to the shader. All references to UV return zero. I tried incrementing my UVs from [0-1] to [1-2], as well, but got the same result.

This unfortunately makes things like outline shaders very difficult.

In the best case, I'm just missing a checkbox somewhere which someone will politely tell me about; but I'm starting to feel like this might be an internal issue?

Thank you.

Reproduction source code:

```
shader_type canvas_item;

uniform sampler2D screen_texture : hint_screen_texture, repeat_disable, filter_nearest;


void fragment() {
//	COLOR = textureLod(screen_texture, SCREEN_UV, 0.0);
//	COLOR = mix(COLOR, vec4(UV, 0.0, 1.0), 0.5);
	
	//DEBUG
	COLOR = vec4(UV, 0.0, 1.0);
//	COLOR.x = 0.0;
//	COLOR.y = UV.y;
//	COLOR.z = UV.y;
//	COLOR = vec4(1.0, 0.0, 0.0, 1.0);
}

```

This is on any Polygon2D with UVs defined. It should provide a UV visualization, but instead returns black.

### Steps to reproduce

Place the above shader code in a ShaderMaterial for a Polygon2D, after defining the points for it, and their UVs; observe the result.

### Minimal reproduction project

I believe the above instructions should be sufficient to highlight the issue, but am open to providing more files directly. Included are the files which this particular bug has presented in.

[Bug Report.zip](https://github.com/godotengine/godot/files/12601435/Bug.Report.zip)
Repository: kubernetes
Issue: OOMKill test for memory usage beyond Node Allocatable is failing
Labels: sig/node,priority/important-longterm,kind/failing-test,lifecycle/rotten,needs-triage

### Which jobs are failing?

https://testgrid.k8s.io/sig-node-kubelet#kubelet-gce-e2e-swap-ubuntu-serial
https://testgrid.k8s.io/sig-node-containerd#cos-cgroupv1-containerd-node-e2e-serial

### Which tests are failing?

OOMKiller for pod using more memory than node allocatable

### Since when has it been failing?

8/29/2023

### Testgrid link

https://testgrid.k8s.io/sig-node-kubelet#kubelet-gce-e2e-swap-ubuntu-serial

### Reason for failure (if possible)

_No response_

### Anything else we need to know?

_No response_

### Relevant SIG(s)

/sig node
Repository: Web-Dev-For-Beginners
Issue: ray
Labels: no-issue-activity

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
 - OS: [e.g. iOS]
 - Browser [e.g. chrome, safari]
 - Version [e.g. 22]

**Smartphone (please complete the following information):**
 - Device: [e.g. iPhone6]
 - OS: [e.g. iOS8.1]
 - Browser [e.g. stock browser, safari]
 - Version [e.g. 22]

**Additional context**
Add any other context about the problem here.
Repository: next.js
Issue: NextCustomServer overwrites req.url with internal NextJS path
Labels: bug,Navigation

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

https://github.com/tills13/nextjs-req-url-reproduction

### To Reproduce

1. install deps (`npm ci`)
2. build next (`npx next build`)
3. run server (`node server.js`)
4. navigate to `http://localhost:3000` (any path)
5. note that the URL is the internal NextJS URL instead of the expected user-facing URL

### Current vs. Expected behavior

The expected behaviour is that, for Custom Servers, at least, the request URL is untouched as you might want to render a page at a different path than what the URL path is e.g. /blog/some-slug/ -> `/pages/blog_post.js` 

Our sites do not have uniform URLs (both /blog/some-slug/ and /some-slug/ might refer to a blog post or a static page and we don't know until we resolve the object from our CMS) so we cannot use file system routing.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Fri Jan 27 02:56:13 UTC 2023
    Binaries:
      Node: 16.20.0
      npm: 8.19.4
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.27
      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) are affected? (Select all that apply)

Routing (next/router, next/navigation, next/link)

### Additional context

Seems like the issue was introduce in https://github.com/vercel/next.js/pull/49805 or https://github.com/vercel/next.js/pull/53523
Repository: go
Issue: runtime/debug: TestStack fails when GOROOT_FINAL or GOROOT  is not clean
Labels: NeedsInvestigation,compiler/runtime

[same environment as #62620]

$ cd src
$ GOROOT_FINAL=/final/destination/ ./all.bash
```
[...]
ok      runtime/coverage        0.003s
allocating objects
starting gc
starting dump
done dump
--- FAIL: TestStack (0.00s)
    stack_test.go:73: found GOROOT "/src/go" from environment; checking embedded GOROOT value
    stack_test.go:116: in line "\t/final/destination/src/runtime/debug/stack.go:24 +0x5e", expected prefix "\t/final/destination//src/runtime/debug/stack.go"
    stack_test.go:117: in line "\t/final/destination/src/runtime/debug/stack_test.go:31", expected prefix "\t/final/destination//src/runtime/debug/stack_test.go"
    stack_test.go:118: in line "\t/final/destination/src/runtime/debug/stack_test.go:34", expected prefix "\t/final/destination//src/runtime/debug/stack_test.go"
    stack_test.go:119: in line "\t/final/destination/src/runtime/debug/stack_test.go:56 +0x2c", expected prefix "\t/final/destination//src/runtime/debug/stack_test.go"
    stack_test.go:120: in line "\t/final/destination/src/testing/testing.go:1595 +0xff", expected prefix "\t/final/destination//src/testing/testing.go"
FAIL
FAIL    runtime/debug   0.073s
[...]
```

Notice the expected prefix' double path separator, `/final/destination//src/`, removing the trailing `/` from the environment variable works.
Repository: material-ui
Issue: [joy-ui] Change background color name scale
Labels: package: joy-ui,design: joy

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

After a Discord discussion, I wondered if the background scale naming that we currently have on Joy UI is the best one.

Today, the scale works linearly from light to dark, when in dark mode, and from dark to light when in dark mode. We have 7 surface levels, where the `body` is the first level, and `level3` being the last. `Body`, as the name says, is meant for the `<body>`, like the base background. In turn, the surface level is used by the components, like the first layer above the `<body>`, and level1 to 3 subsequently.

The biggest problem is that some names have a semantic approach (body, surface, tooltip, popup) and some have non-semantical names (level 1, level 2 and level 3). This ends up providing a bad DX since it's non-intuitive to know that this is meant to be a linear scale.

### Examples 🌈

For instance, these are the scales we currently have for light background:

```
background: {
        body: getCssVarColor('palette-common-black'),
        surface: getCssVarColor('palette-neutral-900'),
        popup: getCssVarColor('palette-common-black'),
        level1: getCssVarColor('palette-neutral-800'),
        level2: getCssVarColor('palette-neutral-700'),
        level3: getCssVarColor('palette-neutral-600'),
        tooltip: getCssVarColor('palette-neutral-600'),
}
```

### Proposal

As I see, a better experience for this would be:

```
background: {
        level-0: getCssVarColor('palette-common-black'), //to be used for body
        level-1: getCssVarColor('palette-neutral-900'), //to be used on components
        level-2: getCssVarColor('palette-neutral-800'),
        level-3: getCssVarColor('palette-neutral-700'),
        level-4: getCssVarColor('palette-neutral-600'),
}
```
Repository: tensorflow
Issue: XLA compiled `tf.reshape` throws ValueError: Shape must be rank 1 but is rank 0
Labels: stat:awaiting tensorflower,type:bug,comp:xla,TF 2.13

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

tf2.13, 2.15.0-dev20230913

### 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?

The following model calls `tf.reshape` on an input tensor, and throws ValueError when compiled with XLA. Without XLA compilation, it runs smoothly. 

This issue is observed on TF 2.13 and also nightly. See the [gist](https://colab.research.google.com/gist/dengyinlin/d9368054f16a011f9d1fed3cede96b95/xla-compiled-tf-reshape-throws-valueerror-shape-must-be-rank-1-but-is-rank-0.ipynb) for more detail.


### Standalone code to reproduce the issue

```python
class Model(tf.keras.Model):

  def __init__(self):
    super(Model, self).__init__()

  @tf.function(jit_compile=True)
  def call(self, x1):
    x2 = tf.reshape(x1, (2, 2))
    return tf.reshape(x2, (4))

m = Model()

input_shape = (4)
x1 = tf.constant([4.,5.,6.,7.], shape=input_shape)

y = m(x1)
print(y)
```


### Relevant log output

```shell
ValueError: Shape must be rank 1 but is rank 0 for '{{node Reshape_1}} = Reshape[T=DT_FLOAT, Tshape=DT_INT32](Reshape, Reshape_1/shape)' with input shapes: [2,2], [].
```
Repository: storybook
Issue: [Documentation]: `includePrimary` note in Stories doc block is incorrect
Labels: documentation,needs triage

### Describe the problem

In the [documentation for the `includePrimary` option](https://storybook.js.org/docs/7.0/react/api/doc-block-stories#includeprimary), there is this note:

>💡 If a stories file contains only one story and includePrimary={true}, the Stories block will render nothing to avoid a potentially confusing situation.

Sadly, this is simply not true. The [code for the Stories block](https://github.com/storybookjs/storybook/blob/next/code/ui/blocks/src/blocks/Stories.tsx) has no logic that could ever produce this effect, and as far as I can tell by looking through the Git history, it _never_ did anything like this.

This is a major shame, because this feature is exactly what I wanted. I've updated the documentation template in my storybook to 

```mdx
<Meta isTemplate />
<Title />
<Subtitle />
<Description />
<Stories />

## Component reference

<Primary />
<Controls />
```

and so if there is only one Primary story, it basically renders the same story twice (once under Stories > Primary, and then again under Component Reference alongside the controls). Unfortunately, I can't really justify opening this issue as a bug report given that it seems to be like this behavior has never existed in the history of ever, _and_ implementing the behavior that the docs describe would be a breaking change. https://x.co/sadtrombone

### Additional context

If anyone knows of a workaround that can achieve this behavior without needing to write a custom doc template for every component I have that only has a primary story, I'm all ears. All I can think of is to change my template to pass `includePrimary={false}`, but then I sort of expect I'll need to add a Primary2 in a lot of cases so that my examples are correct.
Repository: next.js
Issue: pages unable to resolve using CustomServer + useFileSystemPublicRoutes: false 
Labels: bug,Navigation

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

https://github.com/tills13/nextjs-req-url-reproduction/tree/custom-server-use-file-system-public-routes

### To Reproduce

1. install deps (npm ci)
2. build next (npx next build)
3. run server (node server.js)
4. navigate to http://localhost:3000
5. notice the 404 despite the custom server _always_ rendering /custom_page


### Current vs. Expected behavior

I expect /custom_page to render.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Fri Jan 27 02:56:13 UTC 2023
    Binaries:
      Node: 16.20.0
      npm: 8.19.4
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.27
      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) are affected? (Select all that apply)

Routing (next/router, next/navigation, next/link)

### Additional context

_No response_
Repository: go
Issue: proposal: x/debug/trace: add package for parsing execution traces
Labels: Proposal

As part of #60773 (tracking issue #57175) I've been working on a new parser for the execution tracer, and to save work down the line I've also been trying to come up with a nice API that would work well.

The goals of such an API would be to:
- Enable custom analyses of traces.
- Allow for streaming traces and performing on-line analyses.
- Be both backward- and forward- compatible with new Go versions and trace wire formats.

Here are the requirements I have for such an API:
- The API should be stream-based, regardless of whether the underlying trace format supports it.
- Parsing a single trace in parallel is unsupported (part of the point of parsing is to serialize the stream anyway).
- The API should expose _some_ model of the Go scheduler explicitly. (This comes from an insight from @rhysh about the `internal/trace` API that doesn't actually expose e.g. the state machine goroutines go through (even though it already has to know about it), leaving users to figure it out again.)
- The API should at least allow for an extension for efficient random access from local storage (e.g. loading from an `mmap`'d trace file).

Any such API is likely to have a fairly large surface. Rather than try to list the full API and debate its merits, we should experiment.

https://go.dev/cl/527875 is my first attempt at such an experiment to support the work done for #60773. The implementation is not quite fully baked (there may be bugs, and there's still some validation missing) but it already seems to work for non-trivial traces produced by https://go.dev/cl/494187 (with `GOEXPERIMENT=exectracer2`). (I'll update this section when it's ready, including with instructions on how to try it out.)

I plan to take this API and vendor it and/or copy it into the standard library to work as the implementation for supporting new traces in `internal/trace`. That'll help move #60773 along but it'll also give us some experience with using the API.

Once I get this API landed in x/exp, and the first cut of the new tracer for #60773, I'd like to invite people to experiment to both shake out bugs but also to identify deficiencies in the API.

For the proposal committee: there's nothing actionable here yet, but I figured I'd create an issue to track work and start a discussion.

Related to #62461.

CC @prattmic @aclements @dominikh @felixge @nsrip-dd @bboreham @rhysh
Repository: flutter
Issue: Run only affected targets when .ci.yaml file is updated
Labels: team-infra,P2,triaged-infra

Currently all targets will be scheduled whenever there is a change in .ci.yaml file, even for a simply property change which affects only one specific target. 

This has been a huge waste of resources, and may cause potential errors like github rate limit/quota issues.

Ideal world:
1) if the change affects only one target, schedule that target only
2) if the change is on platform level, schedule only the targets belonging to that platform

We can start from presubmit and then experiment how to enforce in postsubmit.
Repository: ant-design
Issue: Add swipe props for drawer for mobile interactions
Labels: 💡 Feature Request,Inactive,📱Mobile Device

### What problem does this feature solve?

I can open a drawer on mobile, but I can't control its size. I lose visibility of the main window completely, when I need to see both at once to complete my sub-task with the relevant context. Instead I have to close the drawer to reveal the main window.

Provides ability for smartphone users to easily minimise or close a drawer from anywhere on the screen, rather than finding the close button (or a minimise button). Also for users to keep the drawer open while checking other stuff on the obscured screen. 

### What does the proposed API look like?

I'm not a dev so don't know how to answer this. Maybe:
swipe: [close, minimize, minimize to 50%, minimize to x%, maximise, maximize to x%...]

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: [FSDP] Simplify `_fully_sharded_module_to_handle`
Labels: triaged,module: fsdp

It looks like `_fully_sharded_module_to_handle` contains at most 1 element, so there is no reason for it to be a `Dict`.

This can also be simplified to only insert the state on the fully sharded module if not already inserted (by the `None` check):
https://github.com/pytorch/pytorch/blob/dbddf1816a847382a9e110a1ed2dfb245495df41/torch/distributed/_composable/fully_shard.py#L115-L124

cc @zhaojuanmao @mrshenli @rohan-varma @fegin @penguinwu
Repository: material-ui
Issue: [docs] Update all demos of the docs to include "use client" when needed
Labels: docs,enhancement

### Summary 💡

The nominal user experience for a developer starting with Material UI is the following:

1. Start with an example https://mui.com/material-ui/getting-started/example-projects/

<img width="527" alt="Screenshot 2023-09-16 at 17 46 59" src="https://github.com/mui/material-ui/assets/3165635/58b22a91-726d-4c41-91c0-7a7af11ddaa4">

https://analytics.google.com/analytics/web/#/analysis/p353089763/edit/IBVRQAiCT2mrgZwzpg9fFQ

2. 28% are going with Next.js App router
3. Install it, use the first template.
4. Go to https://mui.com/material-ui/react-select/#basic-select copy the first demo
5. ❌

<img width="1004" alt="Screenshot 2023-09-14 at 01 20 45" src="https://github.com/mui/material-ui/assets/3165635/ca63ca81-0bed-4cd1-9a76-ea2dd78766e0">

So I think we should update all the demos in the docs to have "use client" where needed.

### Examples 🌈

- https://mui.com/base-ui/react-modal/#system-UseModal.tsx

<img width="533" alt="Screenshot 2023-09-14 at 01 24 44" src="https://github.com/mui/material-ui/assets/3165635/5d9795e8-df1c-4b5a-a359-1bd46565208f">

- https://ui.shadcn.com/docs/components/switch#form

<img width="384" alt="Screenshot 2023-09-14 at 01 24 48" src="https://github.com/mui/material-ui/assets/3165635/c748571a-163a-4999-9b83-6f0b1aa82789">

### Motivation 🔦

Better DX

### Benchmarks

- https://flowbite-react.com/docs/components/button-group

<img width="504" alt="SCR-20240402-tgeh" src="https://github.com/mui/material-ui/assets/3165635/8c2de6ac-518d-4ed8-bf70-8296f865bdba">
Repository: PowerToys
Issue: Keyboard Manager - Remap keys - List of F keys could be better sorted
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager,Needs-Triage

### Description of the new feature / enhancement

Currently, the list of F keys in the Keyboard Manager's Remap keys section is displayed like this

- F1
- F10
- F11
- F12
- F13
- F14
- F15
- F16
- F17
- F18
- F19
- F2
- F20
- F21
- F22
- F23
- F24
- F3
- F4
- F5
- F6
- F7
- F8
- F9


GIF of it in action on my computer
![PowerToys - Keyboard Manager - List](https://github.com/microsoft/PowerToys/assets/1947062/3aa90952-56aa-4ba2-9a53-3ba4e49192ce)


Considering that the F keys on the keyboard left to right goes from 1 to 9 and then F10, F11, F12, it would be nice to see the list display as 

- F1
- F2
- F3
- F4
- F5
- F6
- F7
- F8
- F9
- F10
- F11
- F12
- F13
- F14
- F15
- F16
- F17
- F18
- F19
- F20
- F21
- F22
- F23
- F24

### Scenario when this would be used?

Users wishing to map a key such as F9 wouldn't be confused when they see "F1" followed by "F10" in the current list.

### Supporting information

_No response_