sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: go/doc: render examples using syscall/js with referenced symbols
Labels: NeedsInvestigation

### What is the URL of the page with the issue?

N/A

### What is your user agent?

N/A

### Screenshot

_No response_

### What did you do?

Wrote an example function using `syscall/js` and rendered it with `pkgsite`.

Currently there is an [explicit check](https://github.com/golang/go/blob/6db272d2dd65202e97058cb0c4909151eed05ae6/src/go/doc/example.go#L225) to skip `syscall/js` imports, as code using `syscall/js` can't be run in the browser. This seems to cause the example to be rendered without any referenced symbols.

While understandable, this is unfortunate as it makes the examples a lot less helpful to the reader, as they miss out on a lot of context. If the author wants the context to be included in the rendered examples, they have to include all referenced types in the function body itself, which means they can't be reused between examples, and also makes the code itself less readable.

It would be helpful if examples using `syscall/js` were still rendered as standalone programs, including any referenced symbols, even if the run button is disabled/doesn't work.

### What did you see happen?

Only the function body was rendered:
![image](https://github.com/golang/go/assets/885076/502c1c0e-ee9b-434c-aba2-8cc415782560)


### What did you expect to see?

The example function to be rendered as a standalone example, with the function body in a function called `main` and any referenced symbols included, just like examples that don't make use of `syscall/js`:
![image](https://github.com/golang/go/assets/885076/cd07efc7-9fa3-4901-b870-1e21dba5162e)
Repository: pytorch
Issue: Alternative access order for the same buffer can bring big perf win
Labels: triaged,enhancement,actionable,oncall: pt2,module: inductor

Check this softmax kernel generated by inductor: https://gist.github.com/shunting314/16bf79d906bd2e929a62c0b2f3c02150  (call it k1)

If we reverse the access order for the second for loop from:
```
for roffset in range(0, rnumel, RBLOCK):
```
to 
```
for roffset in range(rnumel - rnumel % RBLOCK, -RBLOCK, -RBLOCK):
```
we get k2 (https://gist.github.com/shunting314/e749c3766757adaed729b51d38cd3169 )

k2 is 1.54 x faster than k1 (5.231ms v.s. 8.067ms). The speedup is mainly due to more cache hit.

Credit to llm.c since I learn the idea from there.  This is probably something we can apply in general in inductor.

cc @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @jansel @Chillee @eellison
Repository: godot
Issue: Godot builds normally with <PublishTrimmed> but crashes when run!
Labels: bug,topic:dotnet

### Tested versions

- Reproducible in: v4.2.2.stable.mono.official [15073afe3]

### System information

Godot v4.2.2.stable.mono - Linux Mint 21.3 (Virginia) - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 6600 (RADV NAVI23) () - 12th Gen Intel(R) Core(TM) i5-12400F (12 Threads)

### Issue description

Hello, I want to trim my game builds to potentially reduce size.
I noticed that by cherry-picking and removing unused .NET assemblies (like visual basic) godot projects would still run and not crash.

I found out that NativeAOT in Godot uses Trimming, but unfortunately NativeAOT cannot be cross-os compiled, so it's not an option for me.

This is the .csproj configuration: 
```xml
<Project Sdk="Godot.NET.Sdk/4.2.2">
  <PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    <EnableDynamicLoading>true</EnableDynamicLoading>
    <PublishTrimmed>true</PublishTrimmed>
  </PropertyGroup>
  <ItemGroup>
    <!-- Root the assemblies to avoid trimming. -->
    <TrimmerRootAssembly Include="GodotSharp" />
    <TrimmerRootAssembly Include="$(TargetName)" />
  </ItemGroup>
</Project>
```
Godot builds normally, produces 1 warning in MSBuild tab:
![image](https://github.com/godotengine/godot/assets/32240709/faac5f3f-3590-406d-9478-6d282ba0081c)

But crashes upon running the assembly:
```diff
~/d/g/B/T/Linux ❯❯❯ '/home/karmy/dev/godot/Builds/TrimmedGame/Linux/TrimmedGame.x86_64' 

Godot Engine v4.2.2.stable.mono.official.15073afe3 - https://godotengine.org
Vulkan API 1.3.255 - Forward+ - Using Vulkan Device #0: AMD - AMD Radeon RX 6600 (RADV NAVI23)
 
- ERROR: .NET: Failed to get GodotPlugins initialization function pointer
   at: initialize_hostfxr_and_godot_plugins (modules/mono/mono_gd/gd_mono.cpp:315)
- ERROR: Parameter "godot_plugins_initialize" is null.
   at: initialize (modules/mono/mono_gd/gd_mono.cpp:412)
   
fish: Job 1, ''/home/karmy/dev/godot/Builds/T…' terminated by signal SIGSEGV (Address boundary error)
```


### Steps to reproduce

1. Create new godot project
2. Add scene, node, create dummy C# file, run project in editor (select current scene)
3. Set your .csproj configuration to this:
```xml
<Project Sdk="Godot.NET.Sdk/4.2.2">
  <PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    <EnableDynamicLoading>true</EnableDynamicLoading>
    <PublishTrimmed>true</PublishTrimmed>
  </PropertyGroup>
  <ItemGroup>
    <!-- Root the assemblies to avoid trimming. -->
    <TrimmerRootAssembly Include="GodotSharp" />
    <TrimmerRootAssembly Include="$(TargetName)" />
  </ItemGroup>
</Project>
```
4. Go to ***Project -> Export...*** and export project without debug option
5. Run produced executable

*...alternatively:*

1. Download Minimal reproduction project
2. Go to ***Project -> Export...*** and export project without debug option
3. Run produced executable

### Minimal reproduction project (MRP)

[TrimmedGame.zip](https://github.com/godotengine/godot/files/15408871/TrimmedGame.zip)
Repository: flutter
Issue: Duplicate browsers start for test given on 'An introduction to integration testing' page
Labels: tool,t: flutter driver,platform-web,f: integration_test,has reproducible steps,P2,team-web,triaged-web,found in release: 3.22,found in release: 3.23

See linked issue for more context: https://github.com/flutter/flutter/issues/100447
[Web][Integration Test] Two Chrome instances launched, and the unnecessary Chrome instance breaks the foundation of the integration test [Edited]

### Page URL

https://docs.flutter.dev/cookbook/testing/integration/introduction/

### Page source

https://github.com/flutter/website/tree/main/src/cookbook/testing/integration/introduction.md

### Describe the problem

 After executing the command:

```
flutter drive \
  --driver=test_driver/integration_test.dart \
  --target=integration_test/app_test.dart \
  -d chrome
```
One Chrome is opened. Notice that it is not labeled with "chrome is controlled by automated test software".

<img width="1200" alt="image" src="https://user-images.githubusercontent.com/14213337/159384051-84080cd6-e34c-4ff6-ad71-b074d7dadd36.png">

Then try to execute the command plus arg `--no-headless`:

```
flutter drive \
  --driver=test_driver/integration_test.dart \
  --target=integration_test/app_test.dart \
  -d chrome \
  --no-headless 
```

Two Chrome instances are launched:
- One [backend one] is launched as a device [this is NOT intended for test cases execution]
- The other [frontend one] is launched via webdriver (chromedriver this case) [this is intended for test cases execution, labeled with 'chrome is controlled by automated test software']

[**Note**: Mostly, the two Chromes are overlaid, please try to drag it away (up or down), then back one would be visible.]

<img width="1641" alt="image" src="https://user-images.githubusercontent.com/14213337/159163845-67e37dfb-b21d-474d-96ee-7d4c711fa140.png">


### Expected fix

Issue code raised: https://github.com/flutter/flutter/issues/100447
[Web][Integration Test] Two Chrome instances launched, and the unnecessary Chrome instance breaks the foundation of the integration test [Edited]

Before issue 100447 is fixed. Please kindly add the above info to this page to clear the context to avoid misleading users.

### Additional context

_No response_
Repository: pytorch
Issue: [ONNX] view(dtype=dtype) is not supported by both onnx.export and onnx.dynamo_export
Labels: module: onnx,triaged,actionable

### 🐛 Describe the bug

Here, ONNX exporter should be smart enough to reinterpret constant as different type, but it's not : 

```python
import torch

class TData(torch.nn.Module):
    def __init__(
            self,
            path_cg_values: torch.Tensor,
    ):
        super().__init__()
        buf = path_cg_values.view(dtype=torch.int32)
        self.register_buffer(
            "path_cg_values", buf, persistent=False
        )

    def forward(self, x):
        return x+self.path_cg_values.view(dtype=torch.float32)

sample_input = torch.randn(8, 4)

model = TData(sample_input).eval()

# Fails with : RuntimeError: 0 INTERNAL ASSERT FAILED at "../torch/csrc/jit/ir/alias_analysis.cpp":615, please report a bug to PyTorch.                                
# We don't have an op for aten::view but it isn't a special case.  Argument types: Tensor, int,                                                                        
# Candidates:                                                                                                                                                          
#         aten::view(Tensor(a) self, SymInt[] size) -> Tensor(a)                                                                                                       
#                 aten::view.dtype(Tensor(a) self, ScalarType dtype) -> Tensor(a)                                                                                      
torch.onnx.export(model, sample_input, "tdata_legacy.onnx")

# Fails with: RuntimeError: Unhandled FakeTensor Device Propagation for aten.add.Tensor, found two different devices cpu, meta                                         
#While executing %add : [num_users=1] = call_function[target=torch.ops.aten.add.Tensor](args = (%l_x_, %detach), kwargs = {})                                          
# Original traceback:                                                                                                                                                  
#  File "/git/models/view_repro.py", line 15, in forward                                                                                                               
#      return x+self.path_cg_values.view(dtype=torch.float32)                                                                                                          
out = torch.onnx.dynamo_export(model, sample_input,)


### Versions

Pytorch nighty 20/05
Repository: react
Issue: [Compiler Bug]: Can't handle identifiers that refer to both type and value 
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [X] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEwBAwhBhggHZ4BKCAhnHmhFQQL4EBmM5BAHRAA6APR4AnlgRghAbgFVFaGghjcmCAgAU+WMEUUECMRs1ZVkpcpRr0mLNgqodFi7lCrm21itTpmjlQAFMSmDhacVroQ+gCUhuwmCHiw7FRQADaZzq5UIBxAA

### Repro steps

Apply React Compiler to 
```tsx
import { CommentReaction } from "./types";

interface Props {
  reaction: CommentReaction;
}

function CommentReaction({ reaction }: Props) {
  return null;
}
```

resulting JS issues `TypeError: Duplicate declaration "CommentReaction"` when passed through `babel-plugin-react-compiler`. The playground produces a build error.

This is easily fixable by changing the code to 
```diff
-import { CommentReaction } from "./types";
+import { type CommentReaction } from "./types";
```

The original code is actually valid TypeScript (though I would not recommend authoring it this way). Despite `CommentReaction` being both a type and value, TypeScript is able to distinguish when it's used as a value vs type.

### How often does this bug happen?

Every time

### What version of React are you using?

19.0.0-beta-04b058868c-20240508
Repository: PowerToys
Issue: Custom (non-AI) Paste Formats
Labels: Idea-Enhancement,Needs-Triage,Product-Advanced Paste

### Description of the new feature / enhancement

Being able to define a custom paste format with rules or regex. Similar to how colour picker allows custom colour formats.

### Scenario when this would be used?

For users who don't have an openAI account / credits or are offline to still be able to have paste options other than the default 3.

### Supporting information

_No response_
Repository: flutter
Issue: [process] Adjust Release Process to Include Wiki Updates for Hotfixes
Labels: team-release,d: docs/

Now that the wiki is in the `docs` directory, we need to adjust the release process to ensure that hotfixes to the stable channel are updated by cherry-pick authors with their cherry-pick PRs. This change will align the release processes between Dart and Flutter, allowing users to access hotfix details directly from their Flutter checkout.

###  Implementation steps

- [ ] **Update Contribution Guidelines**: Include a requirement for cherry-pick authors to update the docs directory with hotfix information.
- [ ] **Modify Release Process Documentation**: Reflect the new requirement in the release process documentation.
- [ ] **Automate Checks**: Implement a CI/CD check to ensure cherry-pick PRs include updates to the docs directory.
- [ ] **Communicate the Change**: Announce the change to the development community through appropriate channels.

CC: @christopherfujino @zanderso
Repository: terminal
Issue: Weird focus change after multiline paste
Labels: Issue-Bug,Area-UserInterface,Product-Terminal

### Windows Terminal version

1.21.1272.0

### Windows build number

10.0.19045.4412

### Other Software

_No response_

### Steps to reproduce

1. Enable the `rightClickContextMenu` option.
2. Enable the `multiLinePasteWarning` option.
3. Copy multiple lines of text to the clipboard from somewhere.
4. Open two cmd shell tabs.
5. In the second tab, execute the following command: `copy con somefilename.txt`
6. Right click in the terminal window and choose the paste option from the context menu.
7. When the warning dialog appears, select *Paste anyway*.
8. Once the text has pasted, press <kbd>Ctrl+Z</kbd> then <kbd>Enter</kbd>.


### Expected Behavior

You should see `1 files(s) copied` and the pasted content should be written to the file.

### Actual Behavior

The <kbd>Ctrl+Z</kbd> key press has no effect, and <kbd>Enter</kbd> switches the focus to the first tab.
Repository: deno
Issue: .npmrc: support `certfile` and `keyfile` auth options
Labels: feat,node compat

https://docs.npmjs.com/cli/v10/configuring-npm/npmrc#auth-related-configuration

Needs to be addressed after https://github.com/denoland/deno/pull/23560 lands.
Ref https://github.com/denoland/deno/issues/16105
Repository: deno
Issue: .npmrc: support `email` auth configuration
Labels: feat,node compat

https://docs.npmjs.com/cli/v10/configuring-npm/npmrc#auth-related-configuration

Needs to be addressed after https://github.com/denoland/deno/pull/23560 lands.
Ref https://github.com/denoland/deno/issues/16105
Repository: deno
Issue: .npmrc: `--reload` is broken 
Labels: feat,node compat

Currently `--reload` flag doesn't work properly when we discover `.npmrc` file.

Ref https://github.com/denoland/deno/pull/23560#pullrequestreview-2056589878
Ref https://github.com/denoland/deno/issues/16105
Repository: deno
Issue: .npmrc: support per-user and maybe global config files
Labels: feat,node compat

We should support discovering `.npmrc` files in per-user location and maybe in global location.

Most likely we will need to update https://github.com/denoland/deno_npm for that as it appears these files are "stacked" together after they are discovered to create a final configuration.

https://docs.npmjs.com/cli/v10/configuring-npm/npmrc#files
Ref https://github.com/denoland/deno/issues/16105
Ref https://github.com/denoland/deno/pull/23560
Repository: rust
Issue: `print-type-size` somtimes prints incorrect output
Labels: T-compiler,C-bug


I tried this code: `RUSTFLAGS='-Zprint-type-sizes -Zthreads=1' cargo +nightly build  |& tee /tmp/sizes`

I expected to see this happen: parseable/consistent output to be rewritten

Instead, this happened: inconsistent output.

I am occasionally seeing what appears to be scrambled output.

For example:

```
print-type-size type: `syn::punctuated::Pair<&mut syn::PathSegment, &mut syn::token::PathSep>`: 16 bytes, alignment: 8 bytes
print-type-size     variant `Punctuated`: 16 bytes
print-type-size         field `.0`: 8 bytes
print-type-size type: `alloc::collections::btree::node::InternalNode<std::string::String, (std::collections::BTreeSet<std::string::String>, syn::punctuated::Punctuated<proc_macro2::TokenStream, syn::token::Plus>)>`: 992 bytes, alignment: 8 bytes
print-type-size         field `.1`: 8 bytes ###### WRONG INDENT
print-type-size     field `.data`: 896 bytes
print-type-size     field `.edges`: 96 bytes
print-type-size type: `core::str::iter::SplitInternal<'_, &str>`: 128 bytes, alignment: 8 bytes
print-type-size type: `std::mem::ManuallyDrop<alloc::collections::btree::node::InternalNode<std::string::String, (std::collections::BTreeSet<std::string::String>, syn::punctuated::Punctuated<proc_macro2::TokenStream, syn::token::Plus>)>>`: 992 bytes, alignment: 8 bytes
print-type-size     variant `End`: 8 bytes
print-type-size     field `.value`: 992 bytes
print-type-size         field `.0`: 8 bytes  ###### WRONG INDENT
print-type-size     field `.matcher`: 104 bytes
```
(` ###### WRONG INDENT` are mine, not in the real output`)

We can see we are printing `field` with 8 indents. Looking through the code https://github.com/rust-lang/rust/blob/9cdfe285ca724c801dc9f78d22b24ea69b787f26/compiler/rustc_session/src/code_stats.rs#L171-L239, 8 indents can only happen after a `variant`. It resets back to 4 in various cases, but _definitely_ after a `type` line we should never have 8 indents like in the first case.

This seems like a concurrency issue, but I don't see where we are concurrently printing; `-Z threads=1` does not solve the issue, either.

Cleaning + rerunning seems to work, sometimes -- not always, though. 

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
$ rustup run nightly rustc --version --verbose
rustc 1.80.0-nightly (791adf759 2024-05-21)
binary: rustc
commit-hash: 791adf759cc065316f054961875052d5bc03e16c
commit-date: 2024-05-21
host: x86_64-unknown-linux-gnu
release: 1.80.0-nightly
LLVM version: 18.1.6
```
Repository: rust
Issue: Compiling this code caused the compiler to block
Labels: T-compiler,C-bug,I-hang

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
pub trait Trait<T> {
    fn f(&self) -> T;
}

pub struct S1<'a>(pub &'a Box<S3<'a>>);

pub struct S2<'a>(pub Vec<S1<'a>>);

pub struct S3<'a>(pub Vec<S2<'a>>);

impl<T> Trait<T> for S1<'_>
where
    for<'a> S1<'a>: Trait<T>,
    for<'a> S3<'a>: Trait<T>,
{
    fn f(&self) -> T {
        self.0.f()
    }
}

impl<T> Trait<T> for S2<'_>
where
    for<'a> S1<'a>: Trait<T>,
{
    fn f(&self) -> T {
        _ = self.0.iter().map(|s| s.f());
        todo!()
    }
}

impl<T> Trait<T> for S3<'_>
where
    for<'a> S2<'a>: Trait<T>,
{
    fn f(&self) -> T {
        _ = self.0.iter().map(|s| s.f());
        todo!()
    }
}

fn main() {
    S3(vec![]).f();
}
```

I expected to see this happen: *Compilation completed to obtain binary file, or compiler returns an error.*

Instead, this happened: *Increased CPU and memory usage, unable to compile or exit for a long time.*

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.78.0 (9b00956e5 2024-04-29)
binary: rustc
commit-hash: 9b00956e56009bab2aa15d7bff10916599e3d6d6
commit-date: 2024-04-29
host: aarch64-apple-darwin
release: 1.78.0
LLVM version: 18.1.2
```

`rustc +nightly --version --verbose`:
```
rustc 1.80.0-nightly (791adf759 2024-05-21)
binary: rustc
commit-hash: 791adf759cc065316f054961875052d5bc03e16c
commit-date: 2024-05-21
host: aarch64-apple-darwin
release: 1.80.0-nightly
LLVM version: 18.1.6
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

`RUST_BACKTRACE=1 cargo build`:
```
   Compiling rs_block_compile v0.1.0 (/Users/umoho/Devs/rs_block_compile)
    Building [                             ] 0/1: rs_block_compile(bin) 
```

</p>
</details>
Repository: go
Issue: time: TestLongAdjustTimers failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "time" && test == "TestLongAdjustTimers"
```

Issue created automatically to collect these failures.

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

    === RUN   TestLongAdjustTimers
    === PAUSE TestLongAdjustTimers
    === CONT  TestLongAdjustTimers
        tick_test.go:228: timer expired
    --- FAIL: TestLongAdjustTimers (60.13s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: rust
Issue: Poor interaction between NLL-borrowck, async, and c_variadic's `...` desugaring (`VaListImpl<'_>`)
Labels: T-compiler,A-async-await,AsyncAwait-Triaged,requires-nightly,F-c_variadic

#124918 made `note_and_explain_region` abort if `ReVar` occurred. Fuzzing found a test case that triggers the abort in #124973, having to do with the `c_variadic` feature:

```rust
async fn multiple_named_lifetimes(_: u8, ...) {}
```

`ReVar` was re-allowed in #125054.

@compiler-errors had the following analysis:

> So the tl;dr is:
> 
> https://github.com/rust-lang/rust/blob/9105c57b7f6623310e33f3ee7e48a3114e5190a7/compiler/rustc_borrowck/src/universal_regions.rs#L517-L520
> 
>
> We create an anonymous free region here for the `VaListImpl<'_>` that c-variadic is implicitly lowered to.
> 
> Async functions capture that var arg list (not exactly certain how they end up doing that, though), and so the lifetime ends up  being captured by the async fn's future. That ends up erroring because the future ends up capturing a lifetime that it didn't expect, which should probably not happen, but regardless is a problem because we have no way of providing a useful error message even if we don't expect it to work... the diagnostic isn't useful at all.
Repository: ui
Issue: [bug]: the Checkbox docs page manual installation section has unspecified dependency
Labels: bug

### Describe the bug

On this page: https://ui.shadcn.com/docs/components/checkbox , in the manual installation section, there is a dependency that should be installed - `lucide-react`, which is not specified on the 'packages to install' step.

### Affected component/components

Checkbox

### How to reproduce

1. Go to https://ui.shadcn.com/docs/components/checkbox
2. Go to manual installation section
3. See on step 1 that `lucide-react` is not specified as a dependency that should be installed

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Irrelevant
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues