sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: rustls refuses to establish connections to self signed TLS certificates
Labels: bug,upstream,ext/fetch,tls,ext/websocket

### Reproduction

The key chain this uses is made up of two parts. The CA (`./test_util/wpt/tools/certs/cacert.pem`) and the end entity certificate (./test_util/wpt/tools/certs/web-platform.test.pem).

To start the testing server:

```sh
deno run -A --unstable ./tools/wpt.ts setup
cd ./test_util/wpt
./wpt serve
```

See that `curl`ing the endpoint with the correct CA cert in the roots works, and without doesn't:

```sh
$ curl -v https://web-platform.test:8444/ --cacert ./test_util/wpt/tools/certs/cacert.pem
...
* Server certificate:
*  subject: CN=web-platform.test
*  start date: Apr 12 02:33:49 2021 GMT
*  expire date: Apr 12 02:33:49 2022 GMT
*  subjectAltName: host "web-platform.test" matched cert's "web-platform.test"
*  issuer: CN=web-platform-tests
*  SSL certificate verify ok.
...
<li class="dir"><a href="xslt/">xslt</a></li>
</ul>
* Connection #0 to host web-platform.test left intact


$ curl -v https://web-platform.test:8444/ 
* SSL certificate problem: unable to get local issuer certificate
* Closing connection 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
```

See that it doesn't work with Deno in any configuration:

```sh
$ deno eval --cert ./test_util/wpt/tools/certs/cacert.pem -Ldebug 'console.log(await fetch("https://web-platform.test:8444/"))'
Sending fatal alert BadCertificate
error: Uncaught (in promise) TypeError: error sending request for url (https://web-platform.test:8444/): error trying to connect: invalid certificate: UnknownIssuer
console.log(await fetch("https://web-platform.test:8444/"))
            ^
    at unwrapOpResult (deno:core/core.js:100:13)
    at async mainFetch (deno:op_crates/fetch/26_fetch.js:165:18)
    at async fetch (deno:op_crates/fetch/26_fetch.js:295:22)
    at async file:///mnt/starship/Projects/github.com/denoland/deno/$deno$eval.ts:1:13

$ deno eval -Ldebug 'console.log(await fetch("https://web-platform.test:8444/"))'
Sending fatal alert BadCertificate
error: Uncaught (in promise) TypeError: error sending request for url (https://web-platform.test:8444/): error trying to connect: invalid certificate: UnknownIssuer
console.log(await fetch("https://web-platform.test:8444/"))
            ^
    at unwrapOpResult (deno:core/core.js:100:13)
    at async mainFetch (deno:op_crates/fetch/26_fetch.js:165:18)
    at async fetch (deno:op_crates/fetch/26_fetch.js:295:22)
    at async file:///mnt/starship/Projects/github.com/denoland/deno/$deno$eval.ts:1:13
```

This same issue is reproducible with `WebSocket`, but for now lets only use `fetch` because it is easier to test with.
Repository: godot
Issue: Godot 3.3 editor locks dll for writing (GDNative)
Labels: bug,confirmed,topic:gdextension,regression

**Godot version:**
3.3

**OS/device including version:**
Windows 8.1

**Issue description:**
Godot Editor locks dll forcing user to restart editor to overwrite dll.
I think something was changed how Godot is terminating process of running scenes, cos it started to throw some memory errors at get_tree() exit() that I fixed in destructor, but this wasnt happening in older versions.

**Steps to reproduce:**
Run scene with GDNative script in Godot Editor. Close it. Now gdnative dll is locked by Godot editor and you cant change it unless you restart Godot.
Repository: pytorch
Issue: Torch FX does not work with torchvision model
Labels: triaged,module: fx

## 🐛 Bug

It seems that torch.FX does not work with MobileNet v2 from TorchVision repo. It is possible to trace the model but I could not modify it.

## To Reproduce

Steps to reproduce the behavior:

1. Load MobileNet v2 from torchvision
2. Use the snippet from here to modify the mobilenet v2 (replace add by mul): https://pytorch.org/docs/stable/fx.html#graph-manipulation
3. Save the model using `to_folder` API.
4. I could not load the saved model due to problems with the code of the saved model: "incorrect indent".

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

The model should be modified and successfully loaded.

## Environment

This is reproducible in Colab.



cc @ezyang @SherlockNoMad
Repository: flutter
Issue: Allow to dynamically depend on plugins based on current app flavor
Labels: c: new feature,platform-android,tool,c: proposal,a: build,P3,team-android,triaged-android

## Use case

Many Flutter applications rely on native dependencies. Often, these native dependencies use the Google Play Services, Huawei App Services or Amazon Fire APIs on Android, make use of Vendor specific APIs or rely on special APIs (such as root features). Unfortunately, it is not possible to publish an application relying on certain APIs in all different marketplaces.

We are hence looking for a way to dynamically in- and exclude certain dependencies for certain build flavors.

E.g. `myapp` depends on the fictional package `accesses_restricted_api` whereas `accesses_restricted_api` makes use of a native API being only available on app marketplace 1 and being disallowed on app marketplace 2 and app marketplace 3 as well as unwanted in regard of the marketplace's philosophy in app marketplace 4.

We are hence looking for a way to blacklist/remove the package (or, to be clear a certain class name) in one of our build flavors.

To be clear for those people usually only publishing in the major app marketplaces: it's currently not possible to use Flutter's own capabilities to publish an app making use of one of the various native Google Service Framework-dependent plugins in Google Play Store, Huawei AppGallery, Amazon Appstore and F-Droid.

## Workarounds tried

We tried to fork the fictional `acces_restricted_api` and create package-specific android build flavors too. Unfortunately, Flutter requires the native class to be present in `android/src/**main**` even if we would like to have different implementations for the different build flavors (e.g. in `android/src/**libre**`, `android/src/**marketplace1**` and `android/src/**marketplace2**`).

As this does not work, we now work around this by maintaining different branches for each app marketplace we target. This is a tremendous amount of work as every change needs to be integrated into four different code bases.

## Proposal

We can imagine two different implementations:

- ether allow flavor-specific implementations for native code on Android
- or provide a way to remove / blacklist a dependency at compile time in case a certain flavor is used
Repository: next.js
Issue: Warnings when debugging in VS Code
Labels: good first issue

### What version of Next.js are you using?

10.1.3

### What version of Node.js are you using?

v14.16.1

### What browser are you using?

Safari

### What operating system are you using?

macOS

### How are you deploying your application?

Vercel

### Describe the Bug

Debugging a starter Next.js installation shows several warnings. Even if they are benign, they make it hard to notice other warnings that may appear as the project is developed.

VS Code shows the following on the Debug Console:
```
Could not read source map for file:///Users/brey/Code/Sandbox/nextjs-test/node_modules/@next/react-refresh-utils/ReactRefreshWebpackPlugin.js: ENOENT: no such file or directory, open '/Users/brey/Code/Sandbox/nextjs-test/node_modules/@next/react-refresh-utils/ReactRefreshWebpackPlugin.js.map'
Could not read source map for file:///Users/brey/Code/Sandbox/nextjs-test/node_modules/@next/react-refresh-utils/loader.js: ENOENT: no such file or directory, open '/Users/brey/Code/Sandbox/nextjs-test/node_modules/@next/react-refresh-utils/loader.js.map'
Could not read source map for file:///Users/brey/Code/Sandbox/nextjs-test/node_modules/@next/react-refresh-utils/internal/ReactRefreshModule.runtime.js: ENOENT: no such file or directory, open '/Users/brey/Code/Sandbox/nextjs-test/node_modules/@next/react-refresh-utils/internal/ReactRefreshModule.runtime.js.map'
```

### Expected Behavior

No warnings.

### To Reproduce

1. `npx create-next-app nextjs-test --use-npm`
2. Add to `packages.json` in `scripts`: `"debug": "NODE_OPTIONS='--inspect' next dev",`.
3. Create `.vscode/launch.json` with:
``` json
{
	"version": "0.2.0",
	"configurations": [
		{
			"type": "node",
			"request": "attach",
			"name": "Launch Program",
			"skipFiles": ["<node_internals>/**"],
			"port": 9229,
			"cwd": "${workspaceFolder}/Server"
		}
	]
}
```
4. `npm run debug`
5. Run this command in VS Code: `Debug: Start Debugging`.
Repository: rust
Issue: Weird error in trait with HRTB for the same trait on `Self` in a method. Also bad diagnostic with nonsensical suggestion.
Labels: A-diagnostics,A-lifetimes,A-trait-system,T-compiler,A-suggestion-diagnostics,D-confusing,A-higher-ranked

<!--
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.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur. 
-->

Given the following code: <!-- Please provide a link to play.rust-lang.org -->

```rust
trait Trait<'a>: Sized {
    fn method(self)
    where
        for<'b> Self: Trait<'b>;
}
```
([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=87e8a1b1bd0f1588a08cdd7e0fe7face))

The current output is:

```rust
   Compiling playground v0.0.1 (/playground)
error[E0283]: type annotations needed
 --> src/lib.rs:1:1
  |
1 | trait Trait<'a>: Sized {
  | ^^^^^^^^^^^^^^^^^^^^^^
  | |
  | cannot infer type for type parameter `Self`
  | required by this bound in `Trait`
  |
  = note: cannot satisfy `Self: Trait<'a>`
help: consider specifying the type arguments in the function call
  |
1 | trait Trait<'a>: Sized::<Self, 'a> {
  |                       ^^^^^^^^^^^^

error: aborting due to previous error
```

I would’ve expected this code to compile. Even if there is a reason why it shouldn’t compile, the error message is about the most confusing/nonsensical error message I’ve ever seen. The “best” part is how it suggests adding arguments to `Sized`.
Repository: storybook
Issue: Failed to fetch dynamically imported module: GlobalScrollAreaStyles, OverlayScrollbars, WithTooltip
Labels: bug,has workaround,needs triage

I'm trying to upgrade Storybook to the latest version 6.2.8

Had multiple issues upgrading through `yarn upgrade` so the final solution was to remove all old packages and run `npx -p @storybook/cli@ sb init`. We discarded our old configuration (Storybook hasn't been modified too much prior to this upgrade) and now we're using the default config which came with the install, just used custom logic to load all of the stories still relying on the `storiesOf` api.

main.js
```js

const path = require("path")

const toPath = (_path) => path.join(process.cwd(), _path)

module.exports = {
  "stories": [
    "./load-stories.js",

  ],
  "addons": [
    "@storybook/addon-links",
    {
      name: '@storybook/addon-essentials',
      options: {
        docs: false,
      }
    }
  ],
  // https://github.com/storybookjs/storybook/issues/13277
  webpackFinal: async (config) => {
    return {
      ...config,
      resolve: {
        ...config.resolve,
        alias: {
          ...config.resolve.alias,
          "@emotion/styled": toPath("node_modules/@emotion/styled"),
          "@emotion/provider": toPath("node_modules/@emotion/provider"),
          "@emotion/core": toPath("node_modules/@emotion/react"),
          "emotion-theming": toPath("node_modules/@emotion/react"),
          "babel-plugin-emotion": toPath("node_modules/@emotion/babel-plugin"),
        }
      }
    };
  }
}

```
The issue is that in 2 out of 3 runs, Storybook ui will throw an error in the browser:

![Screenshot 2021-04-22 at 15 13 48](https://user-images.githubusercontent.com/16742525/115712489-80148500-a37d-11eb-9377-6648d737f78f.png)


The error persists until I reinstall the storybook packages. The first run goes well, then if I restart the server it usually fails with the aforementioned error.

"@babel/core": "^7.13.15",
@storybook/addon-actions: ^6.2.8 => 6.2.8 
@storybook/addon-essentials: ^6.2.8 => 6.2.8 
@storybook/addon-links: ^6.2.8 => 6.2.8 
@storybook/react: ^6.2.8 => 6.2.8 
"react": "^16.9.0" => 16.9.0
"react-dom": "^16.9.0" => 16.9.0
"typescript": "^3.5.3" => 3.8.3
"webpack": "^4.17.1" => 4.46.0
Repository: godot
Issue: Gui duplicated when not full screen (regression in 3.2.4 beta 1) [Linux, Optimus]
Labels: bug,platform:linuxbsd,topic:rendering,topic:porting,confirmed,regression

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
3.3 mono stable

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Debian 10 x11

**Issue description:**
<!-- What happened, and what was expected. -->
When not full screen
![image](https://user-images.githubusercontent.com/13235119/115723476-4ee98400-a380-11eb-8417-23a737941e7b.png)
When I try to resize the window
![image](https://user-images.githubusercontent.com/13235119/115723665-7dfff580-a380-11eb-9dc3-74c79c1cf806.png)

I guess I need to roll back to 3.2.3?

**Steps to reproduce:**
See before

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
NA
Repository: pytorch
Issue: [structured] at::cpu_unchecked functions
Labels: triaged,module: structured kernels

These would be like at::cpu but all meta computations would be skipped (the user would be expected to have precomputed what's necessary). This would make it possible to compose structured kernels out of other structured kernels. This might not be so easy to do because some structured kernels rely on state setup in the meta function to actually proceed properly (however, this is only TensorIterator).
Repository: pytorch
Issue: PyTorch 1.8.0 / 1.8.1 CUDA memory corruption on oddly sized tesnor sections of strided tensor
Labels: module: cuda,triaged

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->
PyTorch 1.8 introduced a CUDA memory corruption oddly sized tensor sections. This is a regression in 1.8, 1.7.1 did not have the issue and never did early 1.8 *alpha* versions.

## To Reproduce

Steps to reproduce the behavior:

0. start python with CUDA memcheck
1. make a 1x48x576x960 GPU tensor float16 "x" with strides like (26542080, 1, 46080, 48)
2. take f = [:,:23,...] section
3. make some ops like torch.sum(f, dim=1, keepdim=True)
4. check the crash and/or memory corruption.


<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

<!-- A clear and concise description of what you expected to happen. -->
This should just work. 

## Environment
python3 /h/roast/juri/collect_env.py
Collecting environment information...
PyTorch version: 1.8.1+cu102
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A

OS: Ubuntu 18.04.4 LTS (x86_64)
GCC version: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Clang version: Could not collect
CMake version: version 3.10.2

Python version: 3.6 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: Could not collect
GPU models and configuration:
GPU 0: Tesla P100-SXM2-16GB
GPU 1: Tesla P100-SXM2-16GB
GPU 2: Tesla P100-SXM2-16GB
GPU 3: Tesla P100-SXM2-16GB
GPU 4: Tesla P100-SXM2-16GB
GPU 5: Tesla P100-SXM2-16GB
GPU 6: Tesla P100-SXM2-16GB
GPU 7: Tesla P100-SXM2-16GB

Nvidia driver version: 455.23.05
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.18.2
[pip3] torch==1.8.1
[pip3] torch-tb-profiler==0.1.0
[conda] Could not collect



 - PyTorch Version (e.g., 1.0):1.8.1
 - OS (e.g., Linux): Lunux
 - How you installed PyTorch (`conda`, `pip`, source): pip, torch=1.8.1
 - Build command you used (if compiling from source):
 - Python version: 3.6


## Additional context
Obvious workaroumd is to use x.contiguous(), but finding such issue in complex environment is time consuming.

<!-- Add any other context about the problem here. -->


cc @ngimel
Repository: pytorch
Issue: Avoid no-op suggest_memory_format call in SparseCsrTensorImpl::resize_as_sparse_csr_tensor_
Labels: module: sparse,triaged,open source,better-engineering

As in title, originally raised in https://github.com/pytorch/pytorch/pull/50937#discussion_r603537183

Replace `suggest_memory_format()` calls in
https://github.com/pytorch/pytorch/blob/76214bb4641fd75fe4ab0e87b05f90462de85fdc/aten/src/ATen/SparseCsrTensorImpl.cpp#L75-L86
with `at::MemoryFormat::Contiguous`.

cc @aocsa @nikitaved @pearu @mruberry
Repository: node
Issue: Workaround for DEP0148: Use of deprecated folder mapping "./" in the "exports" field
Labels: module,deprecations

<!--
Thank you for reporting an issue.

This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help


Please fill in as much of the template below as you're able.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or output of `"$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })"` in PowerShell console (Windows)
Subsystem: if known, please specify affected core module name
-->

* **Version**: 16.0
* **Platform**: Linux foxbat 5.11.15-200.fc33.x86_64 #1 SMP Fri Apr 16 13:41:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

### What steps will reproduce the bug?

```sh
npm i postcss
echo "let list = require('postcss/lib/list')" > index.js
node index.js
```

The output:

```
(node:12793) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /home/ai/test-cjs/node_modules/postcss/package.json.
Update this package.json to use a subpath pattern like "./*".
```

But replacing `exports` in PostCSS’s `package.json` to `"./*": "./*.js"` will break old Node.js.

<!--
Enter details about your bug, preferably a simple code snippet that can be
run using `node` directly without installing third-party dependencies.
-->

### How often does it reproduce? Is there a required condition?

Always

### What is the expected behavior?

1. Not show deprecation warning until we have active Node.js without `*` support.
2. Suggest a solution to support both syntaxes.

### Additional information

https://github.com/postcss/postcss/issues/1561

The warning was disabled in Node.js 15.
Repository: rust
Issue: Tracking Issue for panic::always_abort()
Labels: T-libs-api,C-tracking-issue

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(panic_always_abort)]`

This is a tracking issue for `std::panic::always_abort()`.

This function causes all future panics to abort.  It is useful in the child after `libc::fork`, and `Command` uses it for that.

### Public API

```rust
// std::panic

pub fn always_abort();
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] Implementation: #81858
- [ ] Final commenting period (FCP)
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final commenting period
(FCP) is always needed before stabilization. This works as follows:

A library team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
commenting period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilzation PR can be opened by anyone.
-->

### Unresolved Questions


<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.
Repository: godot
Issue: Bootsplash in landscape mode ignored
Labels: bug,platform:android,topic:porting

**Godot version:**
 v3.3.stable.official

**OS/device including version:**
Tested on android emulator and on real device Meizu m2 mini. GLES2 and GLES3.

**Issue description:**
Bootsplash in landscape mode ignored.  In portrait mode work as expected.
Related: #21824
**Landscape:**
![landscape](https://user-images.githubusercontent.com/1049442/115726383-81a57380-a3a4-11eb-86fb-d037a53bd0ad.gif)
**Portrait:**
![portrait](https://user-images.githubusercontent.com/1049442/115726534-9f72d880-a3a4-11eb-8da4-ca41b4948cd2.gif)

**Steps to reproduce:**
Export to Android and look at bootsplash.

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
For MRP i used godot demo: sprite shader, but changed bootsplash color to more contrasted.
[sprite_shaders.zip](https://github.com/godotengine/godot/files/6358707/sprite_shaders.zip)

CC @m4gr3d
Repository: go
Issue: x/crypto/sha3: superfluous rate in state struct
Labels: NeedsInvestigation

https://github.com/golang/crypto/blob/master/sha3/sha3.go#L27

Rate is always 200 - (outputLen * 2), and therefore is superfluous.  I think the code would be cleaner if rate is derived from outputLen.  The rate member is not exposed in the public API, and therefore can be removed.