sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: nextjs logging on docker not working
Labels: bug,Output (export/standalone)

### Link to the code that reproduces this issue

https://github.com/fabioportieri/test-nextjs-docker

### To Reproduce

1. run docker compose:
   `docker compose -f docker\app.yml up -d`

2. point to http://localhost:3005 and click button

3. check logs on docker, no logs are shown whereas log "LOG WORKING" is expected

### Current vs. Expected behavior

i expect server side logs to show up 

### Verify canary release

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

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
Binaries:
  Node: 18.19.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.4
  eslint-config-next: 14.0.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: standalone
```


### Which area(s) are affected? (Select all that apply)

Standalone mode (output: "standalone")

### Which stage(s) are affected? (Select all that apply)

Other (Deployed)

### Additional context

_No response_
Repository: go
Issue: x/pkgsite: shows the escape character in sidebar index
Labels: NeedsInvestigation,pkgsite

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

https://pkg.go.dev/github.com/GlobeMC/mcla#readme-mcla-minecraft-log-analyzer

### What is your user agent?

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36

### Screenshot

<img width="1512" alt="Screenshot 2024-01-16 at 08 24 24" src="https://github.com/golang/go/assets/91082411/7d1d9358-9442-496c-b0b9-1119c97d937f">


### What did you do?

In `README.MD`, I wrote
```md
# MCLA \| Minecraft Log Analyzer
```

### What did you see happen?

It showed `MCLA \| Minecraft Log Analyzer` in the index

### What did you expect to see?

It should show `MCLA | Minecraft Log Analyzer` which do not have the escape character `\`
Repository: vscode
Issue: Middle click on Linux can only paste from copied text, not from the Primary buffer
Labels: bug,editor-clipboard

<!-- ⚠️⚠️ 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

- VS Code Version: 1.85.1
- OS Version: Ubuntu 22.04 LTS

Steps to Reproduce:

1. Select text (do not copy)
2. Select different text and copy with CTRL+C
3. Middle click in a blank area. You either see no pasted output with `"editor.selectionClipboard": false` or you see the clipboard contents with `"editor.selectionClipboard": true`

On Linux middle click should always paste the last selected text, never the text copied with CTRL+C. This breaks the standard OS clipboard behaviour on Linux.
Repository: pytorch
Issue: Update decompositions registered to `Autograd` dispatch key to also register `CompositeImplicitAutograd`
Labels: triaged,oncall: pt2,module: decompositions,module: aotdispatch,module: python dispatcher,module: pt2-dispatcher

Some of our decompositions are registered to the Python dispatcher with `aten.[op].py_impl(DispatchKey.Autograd)` which, due to changes in `AOTAutograd` (#111347), will not be hit in inference mode. All instances where we register `Autograd` should be checked and if necessary add `CompositeImplicitAutograd` dispatch as well.

One example of this was uncovered by @vfdev-5 in investigating #116848, where upsample decompositions were not being used under inference mode and a bugged lowering was hit instead.

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @SherlockNoMad @wconstab
Repository: flutter
Issue: `flutter build` doesn't include assets added to a path dependency in between builds
Labels: tool,a: assets,platform-web,a: build,has reproducible steps,P2,team-tool,triaged-tool,found in release: 3.19,found in release: 3.20

If you are working on a package with an `example/` directory, you usually declare the parent folder as a package dependency. Making changes to the package assets and running `flutter build web` in the consumer package (example/) won't include the assets in the build. I needed to run `flutter clean` followed by `flutter build web` to see the assets included in my build folder.

Steps to reproduce
1. Create a Flutter package
1. Create new Flutter app `example/`
2. Run `flutter build web` in `example/`
3. Add an asset to `pubspec.yaml` in the parent package:
```
flutter:
  assets:
    - lib/my_script.js
```
5. Run `flutter build web` in `example/`
6. Observe `build/web/assets/` directory doesn't contain the new asset
7. Run `flutter clean`
8. (edit by @andrewkolos) Run `flutter build web` again
9. Observe the `build/web/assets` directory now contains the asset
Repository: svelte
Issue: [transition] Wait for Keyed Block Out Transition Before Mounting Next Element
Labels: transition/animation

### Describe the problem

When trying to transition out from a keyed block, there should be a way to specify to wait for the first keyed item's transition out to finish before mounting the second element.

https://github.com/sveltejs/svelte/assets/53095479/99b65261-e9e5-4b21-a9b8-44323a928fd6

```svelte
{#key activeItem}
	<div
		in:fly={{ opacity: 0, y: 10, duration: 200 }}
		out:fly={{ opacity: 0, y: -10, duration: 200 }}
	>
		{activeItem}
	</div>
{/key}
```

One workaround is to use position absolute on both elements and use a delay on the in transition. But there should be a way to simply wait for the out transition of a keyed block before mounting the next one.

Using the position absolute and delay workaround:


https://github.com/sveltejs/svelte/assets/53095479/28a50cf7-7a40-4caf-bf0e-e9fc2825c460

```svelte
<div class="relative">
	{#key activeItem}
		<div
			class="absolute inset-0"
			in:fly={{ opacity: 0, y: 10, duration: 200, delay: 200 }}
			out:fly={{ opacity: 0, y: -10, duration: 200 }}
		>
			{activeItem}
		</div>
	{/key}
</div>
```

### Describe the proposed solution

be able to set an attribute to wait for the out transition before mounting the next keyed element.

### Importance

would make my life easier
Repository: go
Issue: proposal: net/http/httpest: add ResponseRecorder.EnableFullDuplex
Labels: Proposal

### Proposal Details

It can be difficult to test code that expects to be able to use `EnableFullDuplex` because `httptest.(*ResponseRecorder)` doesn't implement `EnableFullDuplex`.
Repository: vscode
Issue: Notebook Accessibility help view not staying open on mac
Labels: bug,accessibility

when I type Alt+F1 (Option+fn+f1 on my mac) I either get display settings or no response.

Only (and only) when I hit Option+fn+f1 at the exact time the Accessibility Help window pops up
and disappears with the next keyboard action.

_Originally posted by @kds215 in https://github.com/microsoft/vscode/issues/175743#issuecomment-1894318243_
Repository: deno
Issue: Centralize all the rustls code in ext/tls
Labels: tls,refactor,chore

Upgrading between rustls versions is made more complicated given that all of our TLS code is spread throughout various extensions and source files.

All the rustls-facing code should be in ext/tls, and we should use some lightweight newtype wrappers to insulate ourselves from upstream changes where possible.

The end result of this work will be that `rustls` itself will not be visible via crate exports to any code other than in `ext/tls`, and all code will use factory functions to create the appropriate `ClientConfig` for `reqwest`, and `TlsStream`s for `ext/net`, `ext/weboscket` and our test servers.

First TLS work:

 - [ ] Add `RootCertStore` factory functions to `ext/tls` -- load a root store from the mozilla roots, the system roots or a CA file. These will be constructed in `RootCertStoreProvider`s to avoid the overhead of TLS CA construction until they are used.
 - [ ] Add `RootCertStore` newtype to `ext/tls` -- an opaque struct that allows us to update rustls in the background.
 - [ ] Make all `rustls-*` exports private from `ext/tls` with the exception of `TlsStream` and `TlsStream{Read,Write}` and the `RootCertStore` newtype
 - [ ] Add `TlsStream` and `ClientConfig` factory functions to `ext/tls`. These must support the various options required by `ext/fetch` (root_cert_store, ca_certs, unsafely_ignore_certificate_errors, client_cert_chain_and_key and ALPN)

Remainder of work:

 - [ ] Update `file_fetcher.rs` to use RootCertStore from `ext/tls`
 - [ ] Migrate `cli/args.rs` to use `ext/tls` factory functions
 - [ ] Migrate LSP's `language_server.rs` to use `ext/tls` factory functions
 - [ ] Migrate `cert_tests.rs` to use `ext/tls` factory functions for certificates and TlsStream
 - [ ] Migrate `ext/net` `ops_tls.rs` to `ext/tls` factory functions
 - [ ] Migrate `ext/net` `raw.rs` to `ext/tls` factory functions
 - [ ] Migrate `ext/websocket` `lib.rs` to `ext/tls` factory functions
 - [ ] Make test_util and test_server depend on `ext/tls`
 - [ ] Migrate `https.rs` `grpc.rs` and `hyper_utils.rs` in `test_util` to use `ext/tls` factory functions
Repository: pytorch
Issue: Warning for unusual log sizes in CI
Labels: module: ci,triaged

If PR or commit increases log size by a lot, show some warning.

Ex build log increases dramatically, left over prints

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: next.js
Issue: App directory path-bound not-found.tsx not compiled to 404.html when using static export
Labels: bug

### Link to the code that reproduces this issue

https://github.com/nodejs/nodejs.org

### To Reproduce

Run `next export` (or `next build` with "export" as "output");

### Current vs. Expected behavior

No 404.html would have been generated for any `not-found.js` residing inside subdirectories as it works with regular builds or development server.

### 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 Thu Oct 5 21:02:42 UTC 2023
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.0.4
  eslint-config-next: 14.0.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Static HTML Export (output: "export")

### Which stage(s) are affected? (Select all that apply)

next build (local), Vercel (Deployed)

### Additional context

_No response_
Repository: vscode
Issue: indicate when action appears/ status changes to screen reader users
Labels: feature-request,accessibility,notebook-statusbar

![Screenshot 2024-01-16 at 1 08 51 PM](https://github.com/microsoft/vscode/assets/29464607/25d7ea81-1f55-4669-bed1-e26fb1897195)
Repository: angular
Issue: Run runGuardsAndResolvers within injection context of the Route its part of
Labels: feature,area: router,feature: votes required

### Which @angular/* package(s) are relevant/related to the feature request?

router

### Description

Would make implementation of non-trivial strategies simpler. Example of non-trivial strategy is one that would return true when current navigation contains specific "state" state, see https://github.com/angular/angular/issues/31843#issuecomment-1890955590, this would be step forward to making on-demand resolver resolution less hackish. Right now it only receives from/to route snapshots as args which may not be sufficient for some use cases. Especially considering that routeConfig already contains many properties which accept functions such as guards or resolvers that do run within injection context which lets one use `inject` to access the DI, it seems sensible to me to expand the list to include the `runGuardsAndResolvers`.

Would be willing to give my shot at the implementation.

### Proposed solution

Run runGuardsAndResolvers within injection context of the routeConfig its part of.

### Alternatives considered

Manage route specific references to injectors manually via APP_INITIALIZER or ENVIRONMENT_INITIALIZER.
Repository: angular
Issue: Expose strategies that correspond to string values of runGuardsAndResolvers
Labels: feature,area: router,feature: votes required

### Which @angular/* package(s) are relevant/related to the feature request?

router

### Description

Given that runGuardsAndResolvers may take a custom strategy in form of a function, it makes sense to expose the set of predefined strategies `'pathParamsChange' | 'pathParamsOrQueryParamsChange' | 'paramsChange' | 'paramsOrQueryParamsChange' | 'always'` so that consumers can compose with them, as was done in case of defaultUrlMatcher, see https://github.com/angular/angular/issues/35928. Also related https://github.com/angular/angular/issues/31843#issuecomment-1890955590

### Proposed solution

Make the strategies part of public api:

```
import { RunGuardsAndResolversStrategies } from '@angular/router';
```

Being:

```
class RunGuardsAndResolversStrategies {
   static pathParamsChange() { ... }
   static pathParamsOrQueryParamsChange() { ... }
   static paramsChange() { ... }
   static paramsOrQueryParamsChange() { ... }
   static always() { ... }
}
```

### Alternatives considered

Copy paste the code from Angular source code or reimplement said strategies.
Repository: pytorch
Issue: Add forward AD support for nn.functional.grid_sample
Labels: module: autograd,module: nn,triaged,actionable,module: forward ad

### 🚀 The feature, motivation and pitch

Hi!

I got an error when trying to use nn.functional.grid_sample in forward-mode AD context:
```
    return torch.grid_sampler(input, grid, mode_enum, padding_mode_enum, align_corners)
NotImplementedError: Trying to use forward AD with grid_sampler_2d that does not support it because it has not been implemented yet.
Please file an issue to PyTorch at https://github.com/pytorch/pytorch/issues/new?template=feature-request.yml so that we can prioritize its implementation.
Note that forward AD support for some operators require PyTorch to be built with TorchScript and for JIT to be enabled. If the environment var PYTORCH_JIT=0 is set or if the library is not built with TorchScript, some operators may no longer be used with forward AD.
```
I would appreciate it if you prioritized the implementation of this feature, as it is a must-have for various image-based applications.

Thank you for your help!

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: godot
Issue: Vulkan: Editor UI occasionally stretches on Android in certain conditions (e.g. when material preview is displayed)
Labels: bug,platform:android,topic:rendering,topic:editor,confirmed

### Tested versions

4.3.dev.2

### System information

Godot v4.3.dev2 - Android - Vulkan (Mobile) - integrated PowerVR Rogue GE8322 -  (8 Threads)

### Issue description

Literally clicking anything in the editor or when i interact with a UI element in the project and the editor it either appears in the wrong position or super stretched for 1 frame, it doesn't happen in previous versions like 4.3.dev.1 or 4.2.1, notice 0:05 or 0:01 in the video

https://github.com/godotengine/godot/assets/131946128/e8da5ce2-0517-4a34-8dda-53a54d110e88



### Steps to reproduce

interact with the UI

### Minimal reproduction project (MRP)

N/A
Repository: PowerToys
Issue: [File Explorer add-ons utility] Add preview handler for .lnk files
Labels: Idea-Enhancement,Product-File Explorer,Needs-Triage

### Description of the new feature / enhancement

Dump the contents of .lnk files as plain text to the preview pane. Example below is a slightly modified output generated by  [Nirsoft's ShortcutsMan - Shortcuts Manager for Windows](http://www.nirsoft.net/utils/shman.html):

~~~
Shortcut Name     : TeamViewer  
Broken Shortcut   : No  
Link To           : C:\Program Files\TeamViewer\TeamViewer.exe  
Arguments         : --sendto  
Start In          : C:\Program Files\TeamViewer  
Window            : Normal  
Hot Key           : None  
Comment           :   
Location          : Base Folder  
Modified Date     : 5/19/2023 9:13:00 AM  
Icon File         : C:\Program Files\TeamViewer\TeamViewer.exe  
Shortcut Filename : C:\Users\starm\AppData\Roaming\Microsoft\Windows\SendTo\TeamViewer.lnk  
~~~

### Scenario when this would be used?

I have lots of SendTo shortcuts that expect a filename or foldername to be passed and where the "Link To" (e.g., "C:\Program Files\TeamViewer\TeamViewer.exe") requires different arguments. The benefit in having a preview handler for .lnk files comes into usefulness when I want to peruse similar .lnk files to copy and create a new one with slightly different arguments to be passed.

### Supporting information

_No response_
Repository: storybook
Issue: [Bug]: Vue i18n locale changes in storybook 7.6 not working consistently
Labels: question / support,compatibility with other tools,vue3

### Describe the bug

Vue i18n isn't changing locales consistently. It seems to change correctly in the component, but not in the locale changer. So locale scope of vuei18n is changing but not global scope. when you refresh the page or if app has only one story then it will work as expected. 

My work has a bigger project where we first found this. it was working in Storybook 6.5 with Vite but now since our upgrade to 7.6, we can't get the locale working consistently in the Storybook or it's tests. 

### To Reproduce

https://stackblitz.com/edit/github-mrfmpx?file=src%2Fcomponents%2FTestOne.stories.js

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm <----- active
    pnpm: 8.14.0 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.0.0-alpha.10 => 8.0.0-alpha.10 
    @storybook/addon-interactions: ^8.0.0-alpha.10 => 8.0.0-alpha.10 
    @storybook/addon-links: ^8.0.0-alpha.10 => 8.0.0-alpha.10 
    @storybook/blocks: ^8.0.0-alpha.10 => 8.0.0-alpha.10 
    @storybook/test: ^8.0.0-alpha.10 => 8.0.0-alpha.10 
    @storybook/vue3: ^8.0.0-alpha.10 => 8.0.0-alpha.10 
    @storybook/vue3-vite: ^8.0.0-alpha.10 => 8.0.0-alpha.10 
    storybook: ^8.0.0-alpha.10 => 8.0.0-alpha.10
```


### Additional context

_No response_
Repository: godot
Issue: Models are incorrect on initial import of GLB files from Kay's Dungeon Remixed
Labels: bug,topic:import,topic:3d

### Tested versions

Does not occur in v3.5.3.stable.mono.official [6c814135b]on Win10

It does Occur in 
v4.2.1.stable.mono.official [b09f793f5] - Windows 10
v4.1.stable.mono.official [970459615] in 

### System information

v4.2.1.stable.mono.official [b09f793f5] - Windows 10, also happens in v4.1.stable.mono.official [970459615] in 

### Issue description

![image](https://github.com/godotengine/godot/assets/12405750/3eb188be-5853-425f-9487-9fca0cbfb5c4)

The image above is a screen cap of what my editor shows and what the playing scene shows for this bug.

When importing the GLB pile from https://github.com/KayKit-Game-Assets/KayKit-Dungeon-Remastered-1.0 into my project they all load correctly.  Most of the objects work as expected, but wall segments are not quite right.  They preview okay in the editor, but when I run the scene, the wrong objects are included.

If I only import one wall it works okay.  Also, if I restart or do a "reimport" on the file, it works from that point on.  It is only on first use of the files.


### Steps to reproduce

1. Start a new Godot Project in 4.1 or newer
2. Add a 3d Node
3. Add a camera Node
4. Right click in the resource list and open the directory in the file system
5. Copy the contents of Kays archive from the GLTF directory into the godot project directory
6. Click back into Godot and let the import run
7. Drag the first wall section in front of the camera
8. Run the scene.

The wall shown in the running game will be different than the one in the editor.  Please note, the difference between the first and second wall is minimal... the second has an arch inlaid a little on it.  The problem happens with most walls.

If you right click on the file you added and reimport, it will fix things.

### Minimal reproduction project (MRP)

I cannot reproduce the problem because it goes away when the project is reloaded.  Hopefully the minimal effort to reproduce it will not be that bad.
Repository: pytorch
Issue: [FSDP] more actionable error logging in meta init
Labels: triaged,module: fsdp

### 📚 The doc issue

describe model.param_name in error msg. This could save time in case of var typos in reset_parameters()

### Suggest a potential alternative/fix

_No response_

cc @zhaojuanmao @mrshenli @rohan-varma @awgu @fegin @penguinwu @kwen2501