sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: cmd/cgo/internal/testcarchive: TestInstall failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/cgo/internal/testcarchive" && test == "TestInstall"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8749661794485597617)):

    === RUN   TestInstall
        carchive_test.go:487: [go tool cgo -objdir /Users/swarming/.swarming/w/ir/x/t/carchive_test2618922230/_obj2378614451 -exportheader p.h p/p.go]
        carchive_test.go:489: [go install -buildmode=c-archive ./libgo]
        carchive_test.go:489: # testcarchive/libgo
            /Users/swarming/.swarming/w/ir/x/w/goroot/pkg/tool/darwin_amd64/link: running ar failed: signal: bus error
            
        carchive_test.go:489: exit status 1
    --- FAIL: TestInstall (18.52s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: material-ui
Issue: [material-ui] How to optimize the installed Material UI package?
Labels: docs,performance,package: material-ui

### Steps to reproduce

Link to live example: (required)

Steps:
1.
2.
3.


### Current behavior

_No response_

### Expected behavior

_No response_

### Context

We have react js application integrated with MUI. When application is deployed production on Kubernetes, we observed size of MUI packages taking more than 350mb space. 
packages taking extra space are @mui, @mui/icons-material
version used :5

Can you please suggest how to reduce bundle size of MUI packages, i referred below link but didn't get much help. Top level imports are used in application e.g. "import { Button, TextField } from '@mui/material';"

https://mui.com/material-ui/guides/minimizing-bundle-size/

### Your environment

_No response_

**Search keywords**: memory
Repository: go
Issue: cmd/cgo/internal/testerrors: TestToleratesOptimizationFlag/-O failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/cgo/internal/testerrors" && test == "TestToleratesOptimizationFlag/-O"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8749661794485597617)):

    === RUN   TestToleratesOptimizationFlag/-O
    === PAUSE TestToleratesOptimizationFlag/-O
    === CONT  TestToleratesOptimizationFlag/-O
        errors_test.go:158: `go build testdata/issue14669.go`: exit status 1:
            command-line-arguments: /Users/swarming/.swarming/w/ir/x/w/goroot/pkg/tool/darwin_amd64/cgo: exit status 2
    --- FAIL: TestToleratesOptimizationFlag/-O (5.02s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: PowerToys
Issue: Keyboard mapper each mapping configuration can add a note option
Labels: Product-Keyboard Shortcut Manager,Needs-Triage

### Description of the new feature / enhancement

Keyboard mapper each mapping configuration can add a note option



### Scenario when this would be used?

The shortcut keys take effect in the application. You can fill in the remarks for the functions that should be applied

### Supporting information

_No response_
Repository: go
Issue: cmd/cgo/internal/testso: TestSOVar failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/cgo/internal/testso" && test == "TestSOVar"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8749661794485597617)):

    === RUN   TestSOVar
        so_test.go:95: clang -fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/Users/swarming/.swarming/w/ir/x/t/go-build2451742577=/tmp/go-build -gno-record-gcc-switches -fno-common -shared -undefined suppress -flat_namespace -o libcgosotest.dylib cgoso_c.c:
        so_test.go:112: go build -o main.exe main.go: exit status 1
            cgosotest: clang: signal: bus error
    --- FAIL: TestSOVar (2.39s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: next.js
Issue: Values ​​sent by headers in the middleware are not accepting letters with accents
Labels: examples

### 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
  Version: ubuntu 22.04.4 lts
Binaries:
  Node: 21.7.3
  Yarn: 1.22.19
Relevant Packages:
  next: 14.0.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5
```


### Which example does this report relate to?

Runtime

### What browser are you using? (if relevant)

next dev (local), build and  production

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

Values ​​sent by headers in the middleware are not accepting letters with accents. Example: headers.set(`test`, `à preço`);
But the get headers show test: 'Ã preÃ§o'

![bug](https://github.com/vercel/next.js/assets/87545816/f73055a6-b30e-469c-a26b-3403737b4a0b)



### Expected Behavior

Result should be test: "à". In the network headers, but "Ã" appears.

### To Reproduce


Use headers.set() in a route in the middleware and check the headers value in the page's network. Ex: headers.set("test", "à") in the network should show test: "à" and not "Ã".
Repository: ui
Issue: [bug]: Input field not forwarded when it's in another wrapper/hoc file
Labels: bug

### Describe the bug

Hi, 

In my project, I created a wrapper component that consists of FormField along with Input component.
The issue is, props that I set in the custom component is not being forwarded to the wrapper component, such as the onChange method.

LoginForm.tsx
```
const LoginForm = () => {
   const form = useForm<z.infer<typeof LoginSchema>>({
    resolver: zodResolver(LoginSchema),
    defaultValues: {
      email: "",
      password: ""
    }
  });

return (
    <Form {...form}>
        <form
          onSubmit={form.handleSubmit(onSubmit)}
        >
          <FormInput
            control={form.control}
            name="email"
            label="Email"
            type="text"
            placeholder="Email"
            onChange={() => console.log("asdasd")}
            id="email"
            required
          />
      </form>
   </Form>
);
 
};
```


FormInput.tsx
```
const FormInput = (props) => {
   return (
      <FormField
        control={control}
        name={name || ""}
        render={({ field }) => (
             <FormItem>
                 <FormControl>
                   <Input
                     {...field}
                      variant={hasError ? "danger" : "default"}
                      type={type}
                      placeholder={placeholder}
                    />
             </FormItem>   
        )}
      />
   );
}
```


Anyone knows the issue? Thanks



### Affected component/components

Input

### How to reproduce

1. Create a wrapper component that consists of <Input />
2. Display that component in another component

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
MacOS, Arc Browser.
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: OSC 8 terminal hyperlinks don't work properly in Remote - WSL
Labels: bug,remote,terminal-links

Repro:

Run `printf '\e]8;;file:///home/daniel/dev/Tyriar/xterm.js/README.md\e\\file scheme\e]8;;\e\n'` using a file that exists in the workspace. 🐛 Clicking the link does not do anything

![image](https://github.com/microsoft/vscode/assets/2193314/59ebb0aa-48a9-43d4-bae9-2b976fda6045)

pwsh repro: `write-host "`e]8;;file:///home/daniel/dev/Tyriar/xterm.js/README.md`e\file scheme`e]8;;`e`n"`, ⚠ don't verify this on Windows as it's a little broken until conpty v2 (https://github.com/microsoft/vscode/issues/224488)
Repository: godot
Issue: Irreversible broken `Skeleton3D` in editable children but new instances looks fine
Labels: bug,topic:editor,confirmed,regression,topic:animation

### Tested versions

v4.3.dev.custom_build [c7f56d327]
Test with https://github.com/godotengine/godot/pull/91122 to avoid crashes while reimporting.

### System information

Windows 10 - Forward+

### Issue description

`Skeleton3D` can become irreversibly broken throughout the back-and-forth process of modifying the source model and reimporting when using `Editable Children`.

Probably, the issue happens when bone hierarch changes and the glTF reimports.
The button on the scene toolbar `Skeleton3D > Reset All Bone Poses` doesn't fix it. There are no properties in the inspector that I can modify or reset to fix it either.

New instances of the glTF look right.

![image](https://github.com/godotengine/godot/assets/1336622![image](https://github.com/godotengine/godot/assets/133662278/dd18bdae-9da5-494b-ad83-735b849537ef)78/dd18bdae-9da5-494b-ad83-735b849537ef)


### Steps to reproduce

* In the MRP, if you reimport `x/x.gltf` while `actor_x.tscn` is the focused scene in the editor, the skeleton doesn't fix.
* If you reimport `x/x.gltf` while `main.tscn` is the focused scene or `actor_x.tscn` is closed, the skeleton looks fixed in the editor but broken at runtime.
* If you reimport `x/x.gltf` while `main.tscn` is the focused scene and then change the focused scene to `actor_x.tscn`, it also fixes at runtime. This behavior is inconsistent. It can fix it or not, depending on the order in which you open the scenes, the number of iterations, or scene complexity. In my large project, for example, this or any other method I tried doesn't work and I'm stuck with the broken skeleton.

### Minimal reproduction project (MRP)

[broken-skeleton.zip](https://github.com/godotengine/godot/files/15131007/broken-skeleton.zip)
Repository: bitcoin
Issue: qa: Support git worktrees when running the linters locally via Docker
Labels: Feature,Tests

I discovered that running this command (from `test/lint/README.md`):
```
DOCKER_BUILDKIT=1 docker build -t bitcoin-linter --file "./ci/lint_imagefile" ./ && docker run --rm -v $(pwd):/bitcoin -it bitcoin-linter
```
doesn't work when trying to run it out of a git worktree:
```
fatal: not a git repository: /home/sdaftuar/bitcoin/.git/worktrees/2024-04-cluster-mempool-txgraph-rebased
```
 (Though it did work for me when I tried checking out my branch in a regular git repo).  

I don't know anything about these scripts, but if there's an easy way to support worktrees I think it would be useful!
Repository: rust
Issue: repr(C) on an enum accepts discriminants that do not fit into the default C enum size
Labels: O-windows,A-FFI,O-windows-msvc,A-repr,A-enum

Example:

```rust
#[repr(C)]
enum OverflowingEnum {
    A = 1111111111111111111,
}
```

```c
enum overflowing_enum {
    OVERFLOWING_ENUM_A = 1111111111111111111,
};
```

Rust currently gives `size_of::<OverflowingEnum>() = 8`. MSVC gives `sizeof(enum overflowing_enum) = 4`. Additionally, Rust gives `OverflowingEnum::A as usize = 1111111111111111111` and MSVC gives `OVERFLOWING_ENUM_A = 734294471`.

This should probably be a hard error (forward compatibility lint). The nomicon currently states

> `repr(C)` is equivalent to one of `repr(u*)` (see the next section) for fieldless enums. The chosen size is the default enum size for the target platform's C application binary interface (ABI).

and the reference currently states

> For field-less enums, the C representation has the size and alignment of the default enum size and alignment for the target platform's C ABI.

The nomicon is clearly wrong here: `#[repr(c_int)]` on the enum would fail to compile (where `c_int` is the correct primitive) (because of the overflowing literal). I think erroring (forward compatibility linting) and pointing the user to use `#[repr(u64)]` in this case makes sense.

([Summary by @CAD97](https://github.com/rust-lang/rust/issues/81996#issuecomment-805340241))

@CAD97 this should error on *all* targets, not just MSVC, I assume? What do non-MSVC C compilers do with such an enum?
Repository: pytorch
Issue: OpInfo testing is inadequate for `nextafter`
Labels: triaged,actionable,module: testing

### 🐛 Describe the bug

Because results opinfo produces are too small that whether it produces right or wrong results is undetectable by usual tolerance limits, see https://github.com/pytorch/pytorch/issues/124985 for example, even though current opinfo tests contains plenty of examples like that

### Versions

2.3.0, CI
Repository: next.js
Issue: Docker image ignores signals
Labels: examples

### Verify canary release

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

### Provide environment information

```bash
n/a
```


### Which example does this report relate to?

with-docker

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

_No response_

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

_No response_

### Describe the Bug

The docker container ignores all signals.

I also found the problem. Things got broken by #59756 where the main process in the docker container was replaced with a bash shell, handling the env variable. If i use the original
```
ENV HOSTNAME "0.0.0.0"

CMD ["node", "server.js"]
```

things work as expected.

My guess is the fix is not that easy, as it might reopen #58657 


IMHO, the `HOSTNAME` env variable name choice was not that good for specifying the network interface where it binds. And it might be a good time to change it to something more suitable now, since from what i understood, it was recently introduced and not documented anyway


### Expected Behavior

Current behavior: it ignores Ctrl+C
Expected: It finishes the current connections and gracefully closes

### To Reproduce

Use the example Dockerfile, create a container, run it with `-it`, then press Ctrl+C
Repository: go
Issue: time, runtime: use QueryPerformanceCounter in time.Now on Windows to improve time resolution
Labels: Performance,OS-Windows,NeedsInvestigation,compiler/runtime

Currently `time.Now` is using a low precision time, which makes a lot of duration measurements imprecise. Currently there seems to be only `QueryPerformanceCounter`, which provides sub-microsecond precision for measurements. This lead to replacing time measurement workarounds in benchmarks (https://github.com/golang/go/issues/31160).

It's clear that using in benchmarking context QPC is fine, because that's what https://learn.microsoft.com/en-us/windows/win32/sysinfo/acquiring-high-resolution-time-stamps recommends. However it's less clear whether there are problems with measuring longer durations (e.g. several years) or whether there are peculiarities with call overhead.

To summarize, the open questions that would need answering before it's reasonable to change `time.Now` behavior are:

1. What's the reasoning QueryPerformanceCounter wasn't used from the start?
    * As far as I understand, there were older Windows versions and WINE that needed more handholding and using QPC introduced problems. If that's the case, then are these problems still present in versions supported by Go.
2. Are there problems measuring long durations with QPC, e.g. 2 years. (https://github.com/golang/go/issues/8687#issuecomment-296261753 does mention it's not stable long-term)
3. Are there problems with QPC taking significantly longer on some systems (e.g. 1000ns)? e.g. maybe some system using high resolution timer. I don't know there are any such problems, but then again the documentation doesn't seem to provide guarantees.
    * The call overhead to QPC seems to be ~20ns-40ns on my system, compared to the current `time.Now` 4.5ns.
4. Are there any problems with regards to system sleeping and waking?

If this is implemented then the change in https://go-review.googlesource.com/c/go/+/557315 can be reverted.

Note, this would be only for the monotonic time measurements.

Related issue for benchmarking:
* https://github.com/golang/go/issues/31160
Repository: pytorch
Issue: Allow operators with no returns to be "out=" operations
Labels: triaged,module: custom-operators,oncall: pt2,module: pt2-dispatcher,internal ramp-up task,module: reinplacing

Users commonly write custom ops that mutate an input but do not return any outputs:
```
def sin_out(x: Tensor, out: Tensor) -> None:
   ...
```
This is the natural way to write an out= variant.

However, PyTorch (and torchgen) think that out variants should return the mutated Tensor. Executorch makes use of this.

We should allow operators with no returns to be "out=" operations when it comes to things like Executorch, which requires an out= variant for an operator. 

cc @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang @larryliu0820
Repository: react
Issue: [React 19] Removal of `ReactDOM.findDOMNode`
Labels: React 19

## Summary

React 19 removes the deprecated `ReactDOM.findDOMNode` utility. While this utility was an escape hatch and refs are the recommended way to access the DOM, in certain cases, `findDOMNode` was the only solution using a React API. Let me explain.

I maintain `@makeswift/runtime`, hosted at https://github.com/makeswift/makeswift, which is the SDK for [Makeswift](https://www.makeswift.com/), a visual editor for Next.js and React. Users of Makeswift can register React components with Makeswift so that they're available to drop in the Makeswift builder. We leverage `findDOMNode` so that we can find registered component's DOM nodes when users don't use `forwardRef` (or in React 19, handle the `ref` prop).

Here's how we use `findDOMNode`: https://github.com/makeswift/makeswift/blob/58f425cf522c23af4a71b2f07a7625b252c59a5e/packages/runtime/src/runtimes/react/find-dom-node.tsx

While we could force users to use `forwardRef`, a very important product philosophy of Makeswift is that we meet developers where they're at. We don't want them to have to make _any_ changes to their components. Their components shouldn't know about Makeswift, and if they weren't forwarding a ref then introducing Makeswift shouldn't make them do so.

In the same vein, we also don't want to alter the DOM in any way, so alternatives like using a `div` with `display: contents` are a no-go for us.

Ideally, we'd be able to use refs with a `React.Fragment`, but that API doesn't exist yet. This leaves us with the alternative of requiring users to forward refs in their components or reaching for React internals, like React DevTools does to associate a DOM node with rendered components. We'd like to avoid using internals but without `findDOMNode`, that might be what we have to do since we'd rather do that than force users to have to forward refs.

Would love to hear thoughts and guidance on what the expectation is for library maintainers to do for this use case that can't be handled with refs. Is the suggested approach to use React internals like React DevTools does? Or perhaps support for refs in `React.Fragment` is on the way?

Thanks!
Repository: vscode
Issue: Problem matcher not clearing problems
Labels: bug,tasks,debt

I'm working on hello world extension example that uses esbuild.

I'm struggling to get the problem matchers working.

- clone https://github.com/aeschli/ext-ts-esbuild.git
- install the recommended extensions, in particular 'esbuild Problem Matchers'
- add a extra `)` at the end of line 19 of `src/extension.ts`. Close the editor after making the change.
- run `Terminal> Run Task.. / npm watch
- The error is reported in the terminal, and a problem marker is also created
![image](https://github.com/microsoft/vscode/assets/6461412/243c3ebe-5108-4fa5-9c24-b7a031b4db46)
- now revert the change again
- the problem is not removed. Killing the terminal also doesn't help. I need to restart the window


The problem matcher is here and looks, IMO, fine: https://github.com/connor4312/esbuild-problem-matchers/blob/main/package.json#L28

Is there a way to debug a problem matcher?
Repository: vscode
Issue: Show suggestions for multiple languages specific settings keys
Labels: feature-request,config

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes ~~/No~~

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.88.1
- OS Version: macOS 14.4 (aarch64)

Steps to Reproduce:

1. Open a VSCode `settings.json` file such as `.vscode/settings.json`
2. Type `[` as a key of the settings object and you can see suggestions for language specific settings keys
3. Type `[` to specify a second or later language specific settings key, but no suggestions are displayed.

https://github.com/microsoft/vscode/assets/41154684/cdf1744b-9532-4638-a467-4945f1e3b947

This multiple languages specific settings feature was raised in https://github.com/microsoft/vscode/issues/51935, and seemed to be introduced in [1.63.0](https://code.visualstudio.com/updates/v1_63#_multiple-language-specific-editor-settings)
Repository: TypeScript
Issue: Trivia ownership documentation seems to be incorrect
Labels: Docs

### Acknowledgement

- [X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

### Comment

Referencing the #1678 issue and the [ast-trivia: trivia ownership](https://github.com/basarat/typescript-book/blob/master/docs/compiler/ast-trivia.md#trivia-ownership) in the typescript-book, there seems to be an error in explanation:

in the issue `@mhegazy` mentions:

> one thing that is different from the Roslyn notion of trivia, is we do not have **trailing** trivia. all triva in TypeScript is leading. so for instance [...]

in the same issue and in the wiki book however the following info is given:

> In General:
> 
> - A token owns any trivia after it on the same line *upto* the next token. 
> - Any comment after that line is associated with the following token.

So from the first cite I understand as if token owns any trivia before it up to the **previous token** (`[trivia of A][token A]...` that's why end-of-file token is always present) which seems to be the correct explanation, while the second cite describes that a token owns the trivia **after it up to next token in the same line**, which would mean that A has trailing trivia, thus not true in TS — albeit true for Roslyn.
```
[token A][trivia owned by A]<nl>
[trivia owned by B]
[token B]
```

Unless there is some misconception of what "owned" trivia means, but imo the second cite is incorrect.
Repository: terminal
Issue: [1.21] Duplicating a pane after changing the settings uses the _old_ settings?
Labels: Issue-Bug,Area-Settings,Product-Terminal

![image](https://github.com/microsoft/terminal/assets/18356694/daefbe6d-b3b7-439a-bdd7-8e517ccf924f)

At top: the first pane I opened, when I booted this portable instance of the Terminal. 

I changed a bunch of settings - scheme, scrollbar marks, font weight. That first pane got the updated settings perfectly. 

Then I split a pane - that new pane got the _original_ settings out of the pane. 

I'm _guessing_ that this was broken around #997. I'm gonna call this not blocking, but something we should service.