sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: encoding/pem: should allow whitespace in the base64 body 
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18.3 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What did you do?

```
package main

import (
	"encoding/pem"
	"fmt"
)

func main() {

	p := `-----BEGIN CERTIFICATE-----
		MIIGATCCA+mgAwIBAgIUCn3
		 . . . valid pem data . . .
		ib7Jp7Q=
		-----END CERTIFICATE-----`

	blk, rest := pem.Decode([]byte(p))

	fmt.Printf("blk: %p\n", blk)
	fmt.Printf("rest len: %d\n", len(rest))
}
```

Paste valid PEM data in the example above. The whitespace indentation must be included. Typical output:

```
blk: 0x0
rest len: 2210
```

### What did you expect to see?

Take the whitespace out of the PEM and see something like this:

```
blk: 0xc00010e180
rest len: 0
```

Per [RFC 7468](https://www.rfc-editor.org/rfc/rfc7468) says whitespace SHOULD be ignored. It's not a bug for this module to reject whitespace. But the RFC is absolutely clear that PEMs with whitespace can exist in the world, and is tolerated by some parsers, and I would expect this general purpose module to tolerate the whitespace as well.

Further, [RFC 2045](https://www.ietf.org/rfc/rfc2045.txt) is more explicit and says non-base64 characters MUST be ignored. Since the inner body of the PEM is base64, I would expect whitespace to be ignored by the golang parser.



### What did you see instead?

Leading whitespace within the lines of the PEM octets causes the parser to fail.
Repository: pytorch
Issue: [Checkpoint] Support multiple unpack in saved tensor hooks
Labels: module: checkpoint,triaged

### 🐛 Describe the bug

Currently, if the `storage` of a particular tensor is accessed twice without recomputation being triggered in between, we raise the following error: https://github.com/pytorch/pytorch/blob/master/torch/utils/checkpoint.py#L391. However, there is a use case which requires this support.

Listing out a few things that we've currently tried:

1. Using python WeakValueDictionary for `storage` instead of a regular dict, to avoid keeping references alive to activation tensors. This turns out to not work because in some cases, the reference in the dict that needs to be returned is the only reference keeping the activation tensor alive, which is quite confusing. 
2. Clearing storage and re-running the forward pass when we're about to access a tensor which has already been returned by `unpack()`. However, this is a hacky fix and results in a performance slowdown due to re-running the forward pass potentially several times.

### Versions

main
Repository: terminal
Issue: Ctrl+clicking on profile in dropdown to open as adminstrator launches it twice (opens two windows), with a random mix of two profiles
Labels: Product-Terminal,Issue-Task,Area-Quality

### Windows Terminal version

1.14.1962.0

### Windows build number

Version 21H2 (OS Build 19044.1826)

### Other Software

_No response_

### Steps to reproduce

Click down arrow next to new tab button
Ctrl+click a profile to run it as admin

### Expected Behavior

One window of the selected profile should open as admin

### Actual Behavior

Two admin windows open, sometimes both as the selected profile, sometimes one as the selected profile and one as another. It's always either cmd or PS for me, even though I have the default Azure shell as the third option, so not sure why that one's not being opened. I can only assume because I've never run one before. As a test, I ran one, then tried it, and it still didn't open one (though I only tried once or twice), then I opened a new Azure window as admin and closed it and tried again, and then I started getting them in the random mix. I then closed the Azure tab thinking maybe it only used currently open tabs, and after several attempts I didn't get any more Azure windows, but I also seemed to stop getting PS ones (so just double cmd windows each time). But after ctrl+clicking on Azure and closing the windows that opened up, I started getting them again. Also, I didn't have any PS tabs open throughout all of this (did earlier, but they've been closed for a day or two), so it's not using current tabs.
Repository: ant-design
Issue: Ant Avatar.Group overflow item seems to be hardcoded to a circle shape and cannot be changed to square
Labels: help wanted,Inactive

### What problem does this feature solve?

When making all Avatar Square in `Avatar.Group`, the overflow component renders as a `circle` and cannot be changed to a `square` as needed by providing the `shape` property to the Group. 

In the screenshot below we can see that the `ant-avatar ant-avatar-circle` classnames are being applied to the overflow component.

The end user experience would be to maintain the consistency of the shape of Avatars across the .Group component

![image](https://user-images.githubusercontent.com/82932397/180881826-a86241f5-5742-440a-8730-5e66b17f4bf4.png)


### What does the proposed API look like?

Provide a property to specify the `shape` of the overflow to `Avatar.Group`. The `shape` property of `Avatar.Group` would accept `circle | square `

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: terminal
Issue: Add option to configure URL clicking behavior
Labels: Area-TerminalControl,Product-Terminal,Issue-Task

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement
The current behavior of the URL click option is to hold CTRL and left-click the URL. Please, please make this configurable such that we can choose our own method of opening URLs, e.g. left-click without CTRL, double-left-click, right-click, etc. Most importantly, I want to be able to single-left-click-without-holding-CTRL to open URLs.
<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: deno
Issue: Require permissions for time zone and other time-related metadata
Labels: permissions,suggestion

Currently, there is a popular npm library that displays a protest message if it detects that it is being executed in a time zone that overlaps with Russia. This has caused many downstream projects to move away from said library.  (As it turns out, many non-Russian humans happen to live in Russian-overlapping-time zones.)

One high-level observation that we can make about this story is that it would be nice to live in a world where our npm dependencies can't hot-patch in features that spy on our geographic location. (In the exact same way that our npm dependencies should not be able to hot-patch in features that arbitrarily use the file-system or arbitrarily access the network.)

My first thought upon hearing this story was:
"If we lived in a world where everyone was using Deno instead of Node/npm, then this would be a non-issue, due to the awesome permissions model."

And my second thought upon hearing the story was to actually look into the specifics. It turns out that by default, Deno allows retrieval of the time zone without any specifically required permissions, which left me surprised and disappointed.

Has this topic been previously discussed? I searched through the GitHub issues, but I didn't find anything relevant.

I think that everyone can probably agree that "time zone" should be squarely placed in a separate category than "personally identifiable information". Yet, with the previous story in mind, it still seems desirable for Deno to be able to protect the former.
Repository: node
Issue: worker: resourceLimits overridden by --max-old-space-size
Labels: worker

### Version

v19.0.0-pre (and earlier)

### Platform

Linux sylph 5.4.0-56-generic # 62-Ubuntu SMP Mon Nov 23 19:20:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

### Subsystem

worker

### What steps will reproduce the bug?

If `--max-old-space-size` is passed on the command line, it takes
precedence over `resourceLimits.maxOldSpaceSizeMb` passed to the worker
thread.

It seems to come from this code in V8:
https://github.com/nodejs/node/blob/5fad0b93667ffc6e4def52996b9529ac99b26319/deps/v8/src/heap/heap.cc#L5204

You can repro by modifying `test/parallel/test-worker-resource-limits.js`.
Adding a value for`--max-old-space-size` here (even if it is the default)
causes the test to fail.

```diff
diff --git a/test/parallel/test-worker-resource-limits.js b/test/parallel/test-worker-resource-limits.js
index f79c31b2a1..1f394eaa4a 100644
--- a/test/parallel/test-worker-resource-limits.js
+++ b/test/parallel/test-worker-resource-limits.js
@@ -1,3 +1,4 @@
+// Flags: --max-old-space-size=1000
 'use strict';
 const common = require('../common');
 const assert = require('assert');
```

I feel this is unintuitive and should be changed upstream, but it should
definitely be documented in NodeJS too.

### How often does it reproduce? Is there a required condition?

always

### What is the expected behavior?

`resourceLimits.maxOldSpaceSizeMb` should override `--max-old-space-size`.

### What do you see instead?

`--max-old-space-size` overrides `resourceLimits.maxOldSpaceSizeMb`.

### Additional information

_No response_
Repository: vscode
Issue: Git - make staged file editable
Labels: feature-request,git

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
Whenever I stage a change, I can't edit it (unless unstaging). I know this is by default, but 200k people are searching for a better solution ([Cannot edit in read-only editor VS Code](https://stackoverflow.com/questions/54856374/cannot-edit-in-read-only-editor-vs-code)). I think it should be clearer. Maybe it could show the options 'ok | unstage | always unstage'.

Suggestion: add the option to automatically unstage a locked git file when you try to change it. I see this message every day. I usually handle git conflicts using IntelliJ because it allows editing while commiting.


<!-- Describe the feature you'd like. -->
Repository: terminal
Issue: AppHost::_WindowActivated reads/writes various fields in a thread unsafe manner - maybe extra bad for ARM
Labels: Issue-Bug,Product-Terminal,Priority-3,Area-Remoting,Area-Windowing

Additionally, that function might be called through the destructor when XAML empties the remaining Win32 message queue and we get called through `IslandWindow::MessageHandler`. `_window` is set to `nullptr` before that happens and we should check it before it's used through `_CurrentDesktopGuid`.
Repository: flutter
Issue: Consider CI that prevent simultaneous changes to `go_router` and `go_router_builder`
Labels: p: tooling,package,team-ecosystem,P2,triaged-ecosystem

Capturing from Discord discussion in the wake of https://github.com/flutter/flutter/issues/108274 and https://github.com/flutter/packages/pull/2381 (see also https://github.com/flutter/flutter/issues/89518 for background, which was the solution to the same basic problem but with federated plugins in flutter/plugins).

The immediate cause of https://github.com/flutter/flutter/issues/108274 was that the CI didn't catch it because of a tooling bug (see https://github.com/flutter/flutter/issues/108274#issuecomment-1194702941, and the fix for that in https://github.com/flutter/plugins/pull/6146). However, based on past experience and Discord discussion, there's a non-trivial chance that if that bug hadn't existed, the flow would instead have been:
1. Presubmit fails on the initial version of the PR.
2. The PR is "fixed" to also update `go_router_builder` to account for the changes.
3. Both `go_router` and `go_router_builder` have new versions published.

This would have almost certainly broken *fewer* people (including not [breaking flutter/packages PRs](https://github.com/flutter/flutter/wiki/Unexpected-Plugins-and-Packages-failures#publishing)), but is actually still wrong. Step 2 is incorrect because it violates semver: `go_router` 4.2.1 would still have been published with changes that would break *existing* versions of `go_router_builder`, and there's nothing that requires that someone who updates `go_router` also update `go_router_builder` if the constraints don't say it's required (which they would not have here). And it would also be broken the other way: someone updating `go_router_builder` but not `go_router` would have been broken, because `go_router_builder` couldn't have expressed that it required >= 4.2.1 because 4.2.1 wouldn't be published to depend on.

The safest way to avoid that would be to prevent changes to `go_router_builder` in the same PR that changes anything in `go_router`'s `lib/`, as we've done with federated plugins. I'm not sure how though for this pair how often this would result in false-positives that would be problematic (e.g., you want to update code comments in one package while making actual changes to the other).

/cc @johnpryan @chunhtai @loic-sharma
Repository: pytorch
Issue: Provide error handling for ops that don't yet support Dynamic Shape
Labels: triaged,lazy

### 🚀 The feature

PyTorch to integrate a default error message in the LTC codegen to inform the user when an op misses dynamic shape support. Perhaps this goes hand-in-hand with a whitelist of ops that do support Dynamic Shape in LTC?

@wconstab @Krovatkin I am filing this ticket per our offline conversation the other week.

CC @JackCaoG @wonjoolee95
Repository: TypeScript
Issue: Overloaded function with at least one generic overload can be assigned to any function with at least the same number of parameters
Labels: Needs Investigation

# Bug Report

### 🔎 Search Terms

overload, generic, function

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about overloads and generics.

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.7.4#code/PTAEHsDsBsE8IG4FMBO1wEMAmSsCgAzAV0gGMAXASylAwAoENoikAuUAZ3JUsgHMAlOwThKWANyESFapFoMmLdpCIBbAEaohoEWMnEyVGvUbM2nbrz6gAPqBUatoAN47FSAHTlwAZUv86AVAAX0k8EAgYeD4kSFRKUilDWVB1AB4AFVAkAA9yWKwOezVNFAA+BTN2DO1dLBc3My9ffz5AkLCI8GQ0TBx6gHdKcgALUBi4nkSDGRpSSqULHn5a0Qkk2blSTOy8gqKHUorTRZrhNf1pIy2F8y5l6ztDp1cTz28-B-bQvHCwUaQHCQtBQwNQKHAKCKGCKuQADkgKLg8O0ALxlFx4UDY0DQJDkUBYdi3dgkADWkHAA0gQXROjWoFRtEkONx+OyxLepMgFKpNMZGLqjNSLJx8xU0GgAkkwV+EVGlCKHBG4CI0HqmlocnBkLweIJBE57m5vOptMFDKZpH0dAlUvEQA)

### 💻 Code

```ts
// only overloaded
function a(value: string): void;
function a(value: number): void;
function a(value: string | number) { value.toString() };

// only generic
function b<T extends number>(value: T): void { value.toString() };

// overloaded with generic
function c(value: string): void;
function c<T extends number>(value: T): void;
function c(value: string | number) { value.toString() };

// these are errors as expected
() => {
    let d: (value: unknown) => void = a;
    let e: (value: unknown) => void = b;
    c(null);
}

// this should be an error
let f: (value: unknown) => void = c;
f(null);
```

### 🙁 Actual behavior

In the example above I call `f(null)` and cause a runtime error, however typescript doesn't warn me about it.

### 🙂 Expected behavior

`c` should not be assignable to `(value: unknown) => void`.
Repository: pytorch
Issue: model.to(device) takes time forever on A40-8Q, NVIDIA. cuda11.1, torch1.9.1.
Labels: module: cuda,triaged

### 🐛 Describe the bug

model.to(device) takes time forever on A40-8Q, NVIDIA. cuda11.1, torch1.9.1.

### Versions

py3.6.9,
CUDA available:True,
GPU0: nvidia a40-8q,
nvcc: Build cuda_11.1.TC455_06.29069683_0,
gcc: ubuntu7.5.0,
Pytorch: 1.9.1+cu111,



cc @ngimel
Repository: create-react-app
Issue: npx create-react-app my-app 
Labels: needs triage,issue: bug report


Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...

npm ERR! code 1
npm ERR! path D:\myProject\minApps\test01\my-app\node_modules\coa
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c start /B node compile.js & node compile.js
npm ERR! node:internal/modules/cjs/loader:936
npm ERR!   throw err;
npm ERR!   ^
npm ERR!
npm ERR! Error: Cannot find module 'D:\myProject\minApps\test01\my-app\node_modules\coa\compile.js'
npm ERR!     at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
npm ERR!     at Function.Module._load (node:internal/modules/cjs/loader:778:27)
npm ERR!     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
npm ERR!     at node:internal/main/run_main_module:17:47 {
npm ERR!   code: 'MODULE_NOT_FOUND',
npm ERR!   requireStack: []
npm ERR! }
npm ERR! node:internal/modules/cjs/loader:936
npm ERR!   throw err;
npm ERR!   ^
npm ERR!
npm ERR! Error: Cannot find module 'D:\myProject\minApps\test01\my-app\node_modules\coa\compile.js'
npm ERR!     at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
npm ERR!     at Function.Module._load (node:internal/modules/cjs/loader:778:27)
npm ERR!     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
npm ERR!     at node:internal/main/run_main_module:17:47 {
npm ERR!   code: 'MODULE_NOT_FOUND',
npm ERR!   requireStack: []
npm ERR! }

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Administrator\AppData\Local\npm-cache\_logs\2022-07-26T02_16_21_199Z-debug.log

Aborting installation.
  npm install --no-audit --save --save-exact --loglevel error react react-dom react-scripts cra-template has failed.

Deleting generated file... package.json
Deleting my-app/ from D:\myProject\minApps\test01
Done.
Repository: vue
Issue: When using spread syntax in tsx file, will cause a type error: TS2559
Labels: 2.7,feat:types

### Version
2.7.8

### Reproduction link
[codesandbox.io](https://codesandbox.io/s/vigorous-neumann-ofdtg3?file=/src/components/A.tsx)

### Steps to reproduce
1. create two file A.tsx,B.tsx
1. A.tsx content:
```
/* eslint-disable */
import { defineComponent } from "vue";
import B from "./B";

export default defineComponent({
  props: {
    aProps: String
  },
  render() {
    const props = {
      props: {
        bProps: "bb"
      }
    };

    return <B {...props} />;
  }
});
```
1. B.tsx,content
```
import { defineComponent } from "vue";

export default defineComponent({
  props: {
    bProps: String
  },
  render() {
    return <h1>bb</h1>;
  }
});
```
1. in A.tsx, render function's return `<B` will report an error


### What is expected?
when use spread props, there is no type error

### What is actually happening?
defineComponent's return type may not support using spread props (like this: <B {...bProps}) />)

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: rust
Issue: Diagnostic for missing method `as_ptr_mut` does not mention `as_mut_ptr`
Labels: A-diagnostics,T-compiler


[Given the following code](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=c5f1905e3e5f02a3e4b974a77a107e30): 

```rust
fn main() {
    let mut v = vec![1,2,3];
    v.as_ptr_mut();
}
```

The current output is:

```
error[E0599]: no method named `as_ptr_mut` found for struct `Vec<{integer}>` in the current scope
 --> src/main.rs:3:7
  |
3 |     v.as_ptr_mut();
  |       ^^^^^^^^^^ help: there is an associated function with a similar name: `as_ptr`

For more information about this error, try `rustc --explain E0599`.
```
Ideally the output should look like:

```
error[E0599]: no method named `as_ptr_mut` found for struct `Vec<{integer}>` in the current scope
 --> src/main.rs:3:7
  |
3 |     v.as_ptr_mut();
  |       ^^^^^^^^^^ help: there is an associated function with a similar name: `as_mut_ptr`

For more information about this error, try `rustc --explain E0599`.
```

A common pattern is to append `_mut` for functions that return `&mut` references. But the pointer types use a different convention.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"vincenzopalazzo"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: terminal
Issue: Windows accessibility "text size" parameter ignored by terminal
Labels: Area-Fonts,Issue-Bug,Area-TerminalControl,Area-Accessibility,Product-Terminal

### Windows Terminal version

1.15.2002.0

### Windows build number

10.0.22622.436

### Other Software

VScode

### Steps to reproduce

- win + u => set "text size" at 150% and apply
- open windows terminal => text size did not change
- open vscode and terminal => text size did change

### Expected Behavior

when setting windows accessibility text size to 150%, it would be expected text size to change consistently across all MS apps.
ie:
- open windows terminal => text size 150%
- open terminal in VScode => text size 150%

Furthermore as text size is fixed in points inside windows terminal, it's not possible to have the same text size in windows terminal or windows terminal from VScode if accessibility texte size setting is not 100%

### Actual Behavior

- open windows terminal => text size did not change
- open vscode and terminal => text size did change