sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Child animatableBody2D offset from animated parent
Labels: bug,topic:animation,topic:2d

### Godot version

4.1.1

### System information

Win11

### Issue description

When animating the transform of an animatableBody2D's parent node using an animationPlayer, the body will have an incorrect transform if it is using sync to physics and the animationPlayer is using autoplay on load. the processmode of the animationPlayer doesn't seem to have an effect.
I have sometimes been able to correct the issue by calling advance(-dt) exactly once in the animationPlayer's _physics_process, but this doesn't always work, and i can't diagnose what the difference is.

### Steps to reproduce

open the repro project, enable visible collision shapes, and run.
you can also open the scripts attached to the animation players and try uncommenting the commented line to see how it fixes the issue in one case but not the other.

### Minimal reproduction project

[animatableBodyBug.zip](https://github.com/godotengine/godot/files/12728278/animatableBodyBug.zip)
Repository: terminal
Issue: Double check how we reflow for a huge height delta
Labels: Product-Conhost,Area-Output,Issue-Task

Yes, exactly that. I did it for this test specifically:
https://github.com/microsoft/terminal/blob/fc4a37ee9189f2f7335ab942d50381a38a03acf2/src/buffer/out/ut_textbuffer/ReflowTests.cpp#L294-L315

`$` is the cursor. `false` in each line means that it has an explicit newline (`true` = force wrap).
It has a lot of comments about bugs in the old implementation, which is why the entire text past the cursor fits into the new buffer. In the new, fixed implementation the `false` = explicit newlines are correctly handled and so it doesn't fit anymore:
https://github.com/microsoft/terminal/blob/6374aece11edbf8b1329d56ab963e6ea2089f83d/src/buffer/out/ut_textbuffer/ReflowTests.cpp#L294-L315

Basically I had to make a choice over whether I:
* continue copying until all text in the old buffer has been consumed.
  If the new cursor position is now somewhere at a negative Y, we just put it at (0,0).
* stop copying at some point to prevent the cursor from being lost.

I chose the latter. What do you think we should do?

_Originally posted by @lhecker in https://github.com/microsoft/terminal/pull/15701#discussion_r1332947703_
            
            
> > continue copying until all text in the old buffer has been consumed.
> > If the new cursor position is now somewhere at a negative Y, we just put it at (0,0).
> 
> Probably that one, right? Like, the priority should be to keep the newest text, right?
> 
> ... this is currently a 1.19 candidate. I'm okay to say merge as is and iterate in the first hotfix since
> 
> 1. we're out of time and I'm about to log out for the day
> 2. this is a RARE edge case
> 3. this is more goodness than badness)



> This is an interesting case. I'm honestly not sure how to handle it -- we should look at how other terminals that do reflow handle it?
Repository: go
Issue: proposal: syscall,x/sys/windows: deprecate CommandLineToArgv due to inappropriate return type
Labels: Unfortunate,OS-Windows,NeedsInvestigation

### What version of Go are you using (`go version`)?

https://pkg.go.dev/golang.org/x/sys@v0.12.0/windows#CommandLineToArgv

### What did you do?

Fuzz test `windows.DecomposeCommandLine`, which used to use `windows.CommandLineToArgv` as follows:
```go
	var argc int32
	argv, err := CommandLineToArgv(&utf16CommandLine[0], &argc)
	if err != nil {
		return nil, err
	}
	defer LocalFree(Handle(unsafe.Pointer(argv)))
	var args []string
	for _, v := range (*argv)[:argc] {
		args = append(args, UTF16ToString((*v)[:]))
	}
	return args, nil
```


### What did you expect to see?

A return type from `CommandLineToArgv` that is consistent with its `argc` return value, and matches the signature documented in https://learn.microsoft.com/en-us/windows/win32/api/shellapi/nf-shellapi-commandlinetoargvw.


### What did you see instead?

Go's `CommandLineToArgv` wrapper hard-codes the bounds on the return value at 8192 entries of 8192 characters each:
```go
func CommandLineToArgv(cmd *uint16, argc *int32) (argv *[8192]*[8192]uint16, err error)
```

The hard-coded bound is incorrect, and can cause callers to panic when attempting to index into `argv` by `argc`.

(attn @golang/windows)
Repository: go
Issue: x/playground: cannot scroll to end of code
Labels: NeedsInvestigation

### What did you do?

Visit a playground link. Arbitrary example: https://go.dev/play/p/wwvMPANaBh4

Scroll down as far as possible

### What did you expect to see?

The end of the text.

### What did you see instead?

Somewhere before the end of the text. The end of the text is not displayed.
I can use the arrow keys to move to the end of the text to see it, but this is annoying!

I'm using Chrome 117.0.5938.62 (Official Build) (64-bit).
Repository: vscode
Issue: Make terminal tab toolbar configurable
Labels: help wanted,feature-request,terminal-tabs

* Show terminal tabs
* Right click to hide its items isn't supported (Split, Delete)

I would really like to hide split because I never use it and because takes away space on hover - which makes me click it accidentally  all the time

<img width="248" alt="Screenshot 2023-09-26 at 16 10 07" src="https://github.com/microsoft/vscode/assets/1794099/c6bc1cfc-3ae1-47c8-bff8-bce1be64e9b0">
Repository: material-ui
Issue: [material-next][Chip] Implement slots pattern and improve focus state
Labels: component: chip,enhancement,design: material you

Implement slots pattern in `material-next`'s Chip, deprecating `avatar`, `icon`, and `deleteIcon` props (but still supporting these). It should follow [Joy UI's Chip](https://github.com/mui/material-ui/blob/master/packages/mui-joy/src/Chip/Chip.tsx) slot implementation as closely as possible.

It might also be worth looking into following Joy's action slot implementation, which would help us improve the Material UI Chip's focus management. Before starting this work, we should design how the focus should work on deletable and clickable-and-deletable chips. This is a gap we need to fill as Material You's specs are not really specific: https://m3.material.io/components/chips/accessibility#ac07be63-3071-41fe-aef3-ccce6bdaf7a4. 

**For deletable Chips**, should the focus:
  1. Land on the entire deletable chip and be deleted with `backspace`/`delete` (this is how v5 works)
  2. Land only on the delete icon and be deleted with `space`/`enter`
  3. Land only on the delete icon and be deleted with `space`/`enter`/`backspace`/`delete`
  4. Land on both, deleting with `backspace`/`delete` if the focus is on the entire chip and with `space`/`enter` if the focus is on the delete icon

And with that in mind, how should the clickable-and-deletable chips focus work?

This issue includes both the slots and focus work, as they're closely related in the API, UI, and UX design phase, but maybe after that, we can split it.

Implementing Joy's chip architecture could also help with accessibility issues: https://github.com/mui/material-ui/issues/20470
Repository: material-ui
Issue: [material-next][Chip] Improve color prop usage and options
Labels: enhancement,design: material you

A gap to fill as the Material You specs do not specify how to use other colors for the chip component. How it works right now is similar to v5:

- If no `color` prop is provided, then the specs defined color is used:
  - outline color for the outlined variant
  - secondary color for the filled variant
  - surface container low color for the elevated variant
- If the `color` prop is provided, that one is used. Right now this only supports [accent colors](https://m3.material.io/styles/color/the-color-system/color-roles#8d13949e-aafc-47bc-81e1-a4daf8cba548).

Points of improvement:
- Feels weird that when no `color` prop is provided, different colors are used for different variants. This is the less confusing way I could come up with on initial implementation but I think there should be a better way
- Supporting other colors? The difficult part here is that not all variants should support all colors
  - Supporting other surface container colors might be useful for the elevated variant
  - Supporting outline variant color might be useful for the outlined variant
  - Adding a "high-contrast" option which is similar to v5 might be useful for the filled and elevated variants, e.g. using the `primary` and `onPrimary` tokens instead of the `primaryContainer` and `onPrimaryContainer` colors
- Restricting colors? The color specs mention that [chips should use only secondary color](https://m3.material.io/styles/color/the-color-system/color-roles#904230ec-ae73-4f0f-8bff-4024a036ca66). That feels restrictive, but maybe an option we want to explore?
Repository: go
Issue: proposal: crypto/x509: Allow to pass flags to syscall.CertGetCertificateChain, when using TLS Transport under Windows
Labels: OS-Windows,Proposal,NeedsInvestigation,Proposal-Crypto

<!--
Our proposal process is documented here:
https://go.dev/s/proposal-process
-->

Before writing the proposal here, I ask the community. However we found no solution for this issue.

Ref: https://stackoverflow.com/questions/77098977/disable-certificate-revocation-check-for-specific-https-connections-on-windows

---

I'm working on a internet restricted environment. Since our internal services we are using Let's Encrypt certificates to avoid the overhead with an internal PKI.

I'm writing a go program which collects informations from all systems and sent the data to a central system. While this works fine for Linux systems, have I have trouble on Windows system.

It seems like that go is using the os native libraries to establish a secured connection for HTTPS requests.

With using the program below

```go
package main

import (
    "fmt"
    "io"
    "log"
    "net/http"
    "os"
)

func main() {
    resp, err := http.Get(os.Args[1])
    if err != nil {
        log.Fatalln(err)
    }

    defer resp.Body.Close()
    htmlData, err := io.ReadAll(resp.Body)
    if err != nil {
        log.Fatalln(err)
        return
    }
    fmt.Printf("%v\n", resp.Status)
    fmt.Printf(string(htmlData))
}
```

I got this
 
> 2023/09/13 16:19:03 Get "https://google.de": net/http: TLS handshake timeout

It seems like the native libraries tries to contact the CRLs (which are not allowed) and the connection fails here. I inspect the traffic with Wireshark and see HTTP connection to r3.c.lencr.org with User-Agent CryptoAPI.

I also can verify such behavior, if I'm using curl

```
curl https://google.de
curl: (35) schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.
```

However curl has the option `--ssl-no-revoke` to skip the specific revoke check. Running curl with the option works fine.

Looking at the source code of CURL

https://github.com/curl/curl/blob/8e74c0729d0cace00a202fc6c33c1b35703e220a/lib/vtls/schannel.c#L474-L492

they are passing flags like

* SCH_CRED_IGNORE_REVOCATION_OFFLINE (**When checking for revoked certificates, ignore CRYPT_E_REVOCATION_OFFLINE errors. For additional restrictions, see Remarks.**)

Source: https://learn.microsoft.com/en-us/windows/win32/api/schannel/ns-schannel-schannel_cred

I would like have an option the set the flag on go, too.

Also RUST has the support to define such os native flags https://github.com/rust-lang/cargo/blob/3ea3c3a27f49f4926ff32befe48f8b652cd755b2/src/cargo/sources/git/oxide.rs#L291
Repository: deno
Issue: Use node resolution and globals in any folder with a node_modules directory component
Labels: suggestion,node compat

This will allow us to better support things like npm/yarn workspaces.
Repository: next.js
Issue: Image warning issue - If you use CSS to change the size of your image, also include the styles 'width: "auto" or 'height: "auto"' to maintain the aspect ratio
Labels: bug,Image (next/image)

### Link to the code that reproduces this issue

demo - https://ominous-space-broccoli-9qgwx9pqq6p2pxvq-3000.app.github.dev/

mvp - https://ominous-space-broccoli-9qgwx9pqq6p2pxvq.github.dev/
mvp codesandbox - https://codesandbox.io/p/devbox/mvp-warn-img-aspect-ratio-md683h

github - https://github.com/nicitaacom/acc2-image-warning-to-maintain-the-aspect-ratio

### To Reproduce

1. Paste this code in page.tsx
```tsx
        <Image
      className="cursor-pointer max-h-[32px] w-auto h-auto"
      src={"/23_store-dark.png"}
      alt="logo"
      width={300}
      height={32}
      priority
    />
```
    
   See this 
   
![image](https://github.com/vercel/next.js/assets/39565703/58210a4d-52e1-485f-8974-604cf4caaec2)

I already use width auto and height auto

### Current vs. Expected behavior

I don't want to see useless warnings in my console

Now I see useless warning that impossible to fix (I tried add some tailwind classes - issue persists)

### 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 PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.19
      pnpm: 7.1.0
    Relevant Packages:
      next: 13.5.1
      eslint-config-next: 13.5.1
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: N/A
```


### Which area(s) are affected? (Select all that apply)

Image optimization (next/image, next/legacy/image)

### Additional context

I tried it with next 13.5.3 - the same result

### For search engines
Image with src "/success-checkmark.gif" has either width or height modified, but not the other. If you use CSS to change the size of your image, also include the styles 'width: "auto"' or 'height: "auto"' to maintain the aspect ratio.
Repository: pytorch
Issue: Devices API
Labels: feature,triaged,needs design,topic: new features,module: python frontend

### 🚀 The feature, motivation and pitch

Hi,

I would like to propose a new device API that is device-type (cuda, xla, npu, …) agnostic. For example, you could do:
```
torch.devices.count(type='cuda')
torch.devices.is_available(type='npu')
torch.devices.seed(42, type='xla')
```

Instead of:
```
torch.cuda.device_count()
torch_npu.npu.is_available()
torch_xla.set_rng_state(42)
```

This would greatly help with making 3rd party code device-type agnostic because, at the moment, each device type has its own API.

I would be happy to implement such an API if there is support from the community.

#108046 is loossly related and could be put under the same API namespace

(cc team: @AnthonyBarbier @HMellor)

### Alternatives

_No response_

### Additional context

_No response_

cc @albanD
Repository: stable-diffusion-webui
Issue: [Feature Request]: 
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

tab to convert text_to _image trained stable diffusion checkpoint to .safetensors

the request is a script from
checkpoint-10000
|-- unet
|-----config.json
|-----diffusion_pytorch_model.safetensors
|-----index.html
|---unet_ema
|-----config.json
|-----diffusion_pytorch_mdoe.safetensors
|-----index.html
|--index.html
|--optimizer.bin
|--random_states_0.pkl
|--scheduler.bin

to
model_10000.safetensors

### Proposed workflow

1. Go to  convert_model tab
2.  insert checkpoint dir path 
3. insert output folder .safetensors path 
4. click convert

allow also batch if you have multiple checkpoints

### Additional information

_No response_
Repository: go
Issue: net: test timeout on `linux-mips64le-rtrk` builder
Labels: Builders,NeedsInvestigation,arch-mips

```
#!watchflakes
post <- builder ~ `linux-mips.*-rtrk` && pkg == "net" && `panic: test timed out`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/ff25aef9dba7f2b2c04f8070a0de6cd936f7f981)):

    panic: test timed out after 12m0s
    running tests:
    	TestDNSSRVUniformity (0s)
    
    net.byPriorityWeight.shuffleByWeight({0xc000446e60, 0x2, 0x2})
    	/tmp/gobuilder-mips64le/go/src/net/dnsclient.go:168 +0x1c fp=0xc000046d18 sp=0xc000046d18 pc=0x1201c9564
    net.checkDistribution(0xc00040bd40, {0xc000342960, 0x2, 0x2}, 0x3fa999999999999a)
    	/tmp/gobuilder-mips64le/go/src/net/dnsclient_test.go:23 +0x1a8 fp=0xc000046ef8 sp=0xc000046d18 pc=0x12021eb30
    net.testUniformity(0xc00040bd40, 0x2, 0x3fa999999999999a)
    	/tmp/gobuilder-mips64le/go/src/net/dnsclient_test.go:45 +0x160 fp=0xc000046f48 sp=0xc000046ef8 pc=0x12021ef30
    net.TestDNSSRVUniformity(0xc00040bd40)
    	/tmp/gobuilder-mips64le/go/src/net/dnsclient_test.go:49 +0x58 fp=0xc000046f68 sp=0xc000046f48 pc=0x12021ef98
    testing.tRunner(0xc00040bd40, 0x1203601e0)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: flutter
Issue: Golden image results not matching local results
Labels: engine,dependency: skia,P2,team-engine,triaged-engine

## Description 

The `https://github.com/flutter/engine/pull/46167#issuecomment-1734648742` comment mentions the correct hash but these incorrect results could also be explained by the test having run on a previous commit.  Either skiagold got goofed about what code it was testing after a rebase or there are some fundamental differences between playgrounds and the skiagold harness.

Seen in: https://github.com/flutter/engine/pull/46167

## Local results

<img width="578" alt="Screenshot 2023-09-26 at 8 50 09 AM" src="https://github.com/flutter/flutter/assets/30870216/b6082999-db41-4b70-ad59-2ecc806da4f9">

## Skia gold results

<img width="862" alt="Screenshot 2023-09-26 at 9 05 39 AM" src="https://github.com/flutter/flutter/assets/30870216/08e8c39a-43ee-4167-9e3b-e5466a333ecc">
Repository: pytorch
Issue: scatter_add: Mixing 0-dim and 1-dim tensors
Labels: module: docs,triaged,module: python frontend,module: edge cases

### 🐛 Describe the bug

scatter_add currently allows 0-dim and 1-dim tensors to be mixed together

```
import torch
op = torch.ops.aten.scatter_add.default

op(torch.zeros([1]), 0, torch.zeros([], dtype=torch.long), torch.ones([2]))
op(torch.zeros([]), 0, torch.zeros([2], dtype=torch.long), torch.ones([3]))

torch.zeros([1]).scatter_add_(0, torch.zeros([], dtype=torch.long), torch.ones([2]))
torch.zeros([]).scatter_add_(0, torch.zeros([2], dtype=torch.long), torch.ones([3]))
```

However, documentation explicitly says that all three tensors should have the same number of dimensions
https://pytorch.org/docs/stable/generated/torch.Tensor.scatter_add_.html

Code comments and error messages also state that the tensors should have the same dimensionality.

The behavior is caused by the use of `ensure_nonempty_dim` in line 73 here:
https://github.com/pytorch/pytorch/blob/main/aten/src/ATen/native/ScatterGatherChecks.h#L66-L74
Notice code comment (line 66) and error message (line 74) stating number of dimensions must be the same

Is this behavior desired? If so, then we need to update code comment/error message/documentation.


### Versions

.

cc @svekars @carljparker @albanD
Repository: godot
Issue: C# exports show an error when no C# solution exists in the project
Labels: bug,topic:dotnet

### Godot version

4.2.dev5.mono

### System information

Godot v4.2.dev5.mono - macOS 10.15.7 - Vulkan (Forward+) - integrated Intel HD Graphics 5000 - Intel(R) Core(TM) i5-4250U CPU @ 1.30GHz (4 Threads)

### Issue description

On at least mac exports, exporting a project on mono godot with no C# solution in there shows an error saying it can't find .NET assemblies directory, forcing you to create it yourself or players see this error.

### Steps to reproduce

1. Create a project with no C# solution
2. Create a build for mac
3. Open the build and wait

### Minimal reproduction project

N/A
Repository: flutter
Issue: Update or document RefreshIndicator behavior on desktop
Labels: framework,f: material design,f: scrolling,P2,team-design,triaged-design

The [RefreshIndicatorExamples](https://api.flutter.dev/flutter/material/RefreshIndicator-class.html), notably the second example, fail on desktop and web because they don't respond to drag gestures. 

Presumably this is related to, https://github.com/flutter/flutter/pull/81569, introduced in Flutter 2.5, and documented in https://docs.flutter.dev/release/breaking-changes/default-scroll-behavior-drag.

Similar issue: https://github.com/flutter/flutter/issues/135188
Repository: ant-design
Issue: flushSync warning when displaying a modal with a button wrapped in tooltip with trigger on focus
Labels: help wanted,Inactive,improvement

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/internationalization-antd-5-9-3-forked-hnqfct?file=/demo.tsx)

### Steps to reproduce

1. Click on Confirm button
2. Click on Cancel or Ok to close modal
3. Notice there's a flushSync warning in console.  For React 16.x, the flushSync warning becomes flushSync error.

### What is expected?

No flushSync warning or error

### What is actually happening?

There's a flushSync warning in console.  For React 16.x, the flushSync warning becomes flushSync error.

| Environment | Info |
| --- | --- |
| antd | 5.9.3 |
| React | 16.x |
| System | Windows |
| Browser | Chrome |

---
This only happens if the button is wrapped in a tooltip with trigger containing focus.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: [Impeller] Skiagold tests use white as clear color
Labels: engine,good first issue,P2,e: impeller,team-engine,triaged-engine

Whereas the playgrounds use black.  This can lead to surprising results when uploading patches.

Example:
skiagold:
<img width="839" alt="Screenshot 2023-09-26 at 10 02 35 AM" src="https://github.com/flutter/flutter/assets/30870216/e901da2a-c440-44e7-baa1-a17906ce6061">

playgrounds:
<img width="578" alt="Screenshot 2023-09-26 at 8 50 09 AM" src="https://github.com/flutter/flutter/assets/30870216/64cf8246-2b49-4e1e-970c-ef5f465c9b02">
Repository: vscode
Issue: F7 does not work consistently in diff view when there are comments
Labels: diff-editor,under-discussion

Testing #194012

Here's the recording. F7 only works sometimes if there's a comment in the diff range, I didn't really see a pattern to it.


https://github.com/microsoft/vscode/assets/2230985/ce222ec0-d04f-4072-8ca8-6159f44e597d