sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: Nonsense UNKNOWN error when writing large buffers with fs.writev
Labels: fs

### Version

14.18.1

### Platform

Linux ops 5.11.0-1021-gcp #23~20.04.1-Ubuntu SMP Fri Oct 1 19:04:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linu

### Subsystem

fs

### What steps will reproduce the bug?

```js
const fs = require("fs");
const fd = fs.openSync("./test.dat", fs.constants.O_WRONLY | fs.constants.O_CREAT, 0o666);
const bufs = [Buffer.alloc(0x7FFFFFFF + 1)];
fs.writevSync(fd, bufs, 0);
```

This throws
```
Uncaught Error: UNKNOWN: unknown error, write
    at Object.writevSync (fs.js:749:3) {
  errno: -2147483648,
  syscall: 'write',
  code: 'UNKNOWN'
}
```
That errno is 0x7fffffff + 1 wrapped around.

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

Always.

### What is the expected behavior?

Should either work, since pwritev(2) works (I don't know if it has a limit less than `SSIZE_MAX`), or report a proper error before making the syscall. I did the latter recently for `fs.write` in c4e7dca8f30ff89b42e96fb8819558ed518a72dd. It would be nice if large files actually worked, but the best fix for that would require a new libuv function.

### What do you see instead?

_No response_

### Additional information

_No response_
Repository: rust
Issue: Support filtering out dependency source code from coverage counters
Labels: C-enhancement,T-compiler,A-code-coverage

Related to https://github.com/rust-lang/rust/issues/84943

> Sometimes it’s useful to only instrument certain files or functions.  

This is also true for code not in your crate but a dependency.  Some dependencies may create a large amount of coverage counters, on a closed source project I tried it on syn and serde took up the majority of the counters. Most people testing a crate aren't looking to get coverage of their dependencies as well so it makes sense to not instrument crates that aren't in the project workspace. Plus it should lead to faster run time and faster parsing of coverage reports - though for most projects I'd expect this to be negligible 

Can ignore below, I feel that even with half sized hash the chance of hash collisions on ascii strings from mangled function names is probably negligibly low :thinking: 

It's also worth noting that for function hashes llvm coverage uses a truncated MD5 hash (so 64 bits instead of 128 bits). These hashes are used to create a hashmap of records and if i recall correctly in the profdata implementation last I checked it doesn't check for hash collisions so the more records the greater the chance of coverage data being lost or erroneously linked to a source location due to hash collisions. I'm not sure of the relative risk of this (I'd have to sample a variety of crates to figure this out), but reducing the number of records would mitigate the potential risk here as well. EDIT: I'm actually very curious about the hash collision impact myself so will update if I find anything out :thinking:
Repository: flutter
Issue: Document android background platform channels
Labels: platform-android,d: api docs,P2,a: plugins,team-android,triaged-android

The Background Platform Channels feature requires documentation (https://github.com/flutter/flutter/issues/91635)
Repository: vscode
Issue: Once user GitHub authenticated render the avatar in the activity bar
Labels: feature-request,authentication

Once a user logins to GitHub from VS Code we could render a nice GitHub avatar instead of the soulless authentication icon in the activity bar. I personally like how Chrome and GitHub do this.

Reasons why we should do it:

* Gives confirmation to the user that she successfully logged in. Without this the experience feels half baked.
* Makes VS Code feel more personalised
* It is possible to hide it via context menu for users that dislike seeing their avatar

![Screenshot 2021-11-10 at 19 02 56](https://user-images.githubusercontent.com/1926584/141168141-86bc090b-b7b0-4d6c-a5da-27812e501141.png)

![Screenshot 2021-11-10 at 19 04 39](https://user-images.githubusercontent.com/1926584/141168447-6ca00b79-7f97-424f-9567-c3e471b1a994.png)
Repository: vscode
Issue: Support Bitbucket.org repositories in vscode.dev
Labels: feature-request,scm,web,vscode.dev

<!-- ⚠️⚠️ 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. -->

<!-- Describe the feature you'd like. -->

It should be self-describing from the title, but it'd be great if more support for different github repository sites would be supported in vscode.dev (open a remote repository) to open things up a bit more. Thanks for considering!
Repository: excalidraw
Issue: support background removal for images
Labels: images

Support removing background from images that don't have alpha channel by themselves. Something like photoshop quick selection or magic wand selection.

Originally suggested by @vjeux
Repository: go
Issue: x/net/context: deprecate package or symbols in package
Labels: NeedsInvestigation


### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.17.1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/frew/.cache/go-build"
GOENV="/home/frew/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS="-mod=readonly"
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/frew/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/frew/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org"
GOROOT="/home/frew/go/installations/go1.17.1"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/frew/go/installations/go1.17.1/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.17.1"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/frew/code/zr0/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/run/shm/go-build2449590503=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?

Accidentally used golang.org/x/net/context

### What did you expect to see?

A deprecation warning caught by our linter.  Basically I think we should mark the package (or symbols in the package) deprecated so that linters would notice and automatically suggest people switch to `context`.

### What did you see instead?

 Nothing.
Repository: flutter
Issue: Investigate a custom shader for a blinking cursor
Labels: framework,engine,c: performance,a: desktop,P2,team-macos,triaged-macos

A possible way to reduce CPU utilization for a blinking cursor (https://github.com/flutter/flutter/issues/59327) is to implement it with a custom shader. This issue is to track investigating how we might implement that, and whether it will help.

/cc @iskakaushik @chriscraws @cbracken
Repository: go
Issue: test/fixedbugs: issue11656.go fails on Go1.17.3 for armv7l (Odroid-HC1)
Labels: OS-Android,NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
Building 1.17.3
With 
# /usr/lib/go-1.11/bin/go version
go version go1.11.6 linux/arm
On
# uname -a
Linux odroid-hc1 4.19.0-18-armmp-lpae #1 SMP Debian 4.19.208-1 (2021-09-29) armv7l GNU/Linux
</pre>

### Does this issue reproduce with the latest release?

Yes, 1.17.3 tag.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
# /usr/lib/go-1.11/bin/go env
GOARCH="arm"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="arm"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/root/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/lib/go-1.11"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.11/pkg/tool/linux_arm"
GCCGO="gccgo"
GOARM="6"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -marm -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build812163099=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

Building 1.17.3 under Debian 10 Buster using script:
```
# cat my.go.build.sh 
#!/usr/bin/env bash

set -eu

export GOROOT_BOOTSTRAP=/usr/lib/go-1.11
(
    pushd go.git/src
    ./all.bash
)
```


### What did you expect to see?

Successfull build, as 1.15.x was built before.

### What did you see instead?

```
exit status 2                                                                                                                                                
SIGILL: illegal instruction                                                                                                                                  
PC=0x20a097c m=0 sigcode=1                                                                                                                                   
instruction bytes: 0x0 0x0 0x80 0xe5 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0

...
...

FAIL    fixedbugs/issue11656.go 1.335s
2021/11/10 21:32:15 Failed: exit status 1                                                            
                             
##### API check                                                                                     
Go version is "go1.17.3", ignoring -next /root/code/golang/go.git/api/next.txt
go tool dist: FAILED
```
Repository: rust
Issue: rustdoc: Encapsulate "clean generics before args" ordering requirement in a function
Labels: C-cleanup,T-rustdoc

I discovered in #90750 that several places in rustdoc panic if a function's generics are not cleaned before its arguments. It'd be good to extract a helper function to encapsulate that requirement so it's not spread across several places in the code.

cc @GuillaumeGomez @jyn514
Repository: godot
Issue: Vulkan: DirectionalLight3D PSSM 2 Split Blending blends 2nd & non-existant 3rd split
Labels: bug,topic:rendering,confirmed,topic:3d

### Godot version

v4.0.dev.custom_build [89cf449fe]

### System information

Windows 10, Vulkan, Nvidia Quadro K2000 461.92

### Issue description

Blending is broken when using 2 splits instead of 4, as it treats the shadowmap as if it were 4 splits and not 2, resulting in the last split blending with non-existant splits that causes a Fade out effect, not related to the Fade Start.

### Steps to reproduce

Create Directional light and Enable shadows and make a shadow
Go near the end of Max Distance, with Fade start at 1
Toggle Blend Splits on and off (On will result in a Fade, Off will result in expected result.)

### Minimal reproduction project

_No response_
Repository: rust
Issue: rustdoc: Refactor `get_all_types` so `args` is fully shared between loop iterations
Labels: C-cleanup,T-rustdoc,E-medium

1. Refactor `add_generics_and_bounds_as_types ` so it handles all types, not just type parameters.
2. Remove the `!args.is_empty()` conditional in `get_fn_inputs_and_outputs`.
3. Extend `all_types` with `args` at the end of the loop.

cc @GuillaumeGomez 

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: TypeScript
Issue: Color highlight makes error messages unreadable on black-on-white screens
Labels: Suggestion,Help Wanted,Experience Enhancement

# Suggestion

Error messages generated by TSC use bright blue and bright yellow to highlight paths and line numbers.
These are too close to white to be readable on a black-on-white console.

## 🔍 Search Terms

terminal background color highlight highlighting error unreadable

## ✅ Viability Checklist

<!--
   Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
   We always recommend reviewing the TypeScript design goals before investing time writing
   a proposal for ideas outside the scope of the project.
-->
My suggestion meets these guidelines:

* [✅] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [✅] This wouldn't change the runtime behavior of existing JavaScript code
* [✅] This could be implemented without emitting different JS based on the types of the expressions
* [✅] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [✅] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

Possiblities:
1. Provide an option to just disable color highlighting.
2. (better) Provide an option to switch to a "light background" color scheme
3. (maybe too far) Allow configuration of colors used.

If http://go/gh/microsoft/TypeScript/issues/44233 were implemented, then it would provide a way to do the first option.

## 📃 Motivating Example

Run tsc on a black-on-white terminal over code that generates error messages.

## 💻 Use Cases

Primary workarounds:

1. Select the colored text to make it visible.
2. Use a terminal with a dark background and light text.
Repository: flutter
Issue: Visual Studio detection for Windows builds should be stricter about versions
Labels: tool,platform-windows,t: flutter doctor,a: desktop,a: build,P2,team-windows,triaged-windows

When VS support was originally added to the tool my approach was to assume that new versions would probably work, so we should just check for a minimum version. That was probably reasonable when projects were solution files, but as we saw with https://github.com/flutter/flutter/issues/85922 it doesn't hold up for CMake: the generator string changes with every major version, so we are essentially guaranteed a build failure until we update our version-to-generator-string mapping.

In order to make this behave more gracefully, we should have a maximum version that we allow, and update the vswhere filtering logic to only consider versions between the minimum and maximum to be supported. We can detect the case where someone *only* has a newer version, and have a new doctor message for that, similar to the one when we only find a version that's too old.

This would mean that doctor would give useful info, and `build` would gracefully direct people to `doctor` instead of giving a CMake error.

This isn't a priority in the short term, but would be good to fix sometime in the next two years 🙂 

/cc @cbracken
Repository: rust
Issue: Tests do not capture stdout() / stderr()
Labels: A-libtest,T-libs

Output capture for tests (https://github.com/rust-lang/rust/commit/d0d0e7820806bbb89a2733bae8f9aaa9c78345d0, https://github.com/rust-lang/rust/commit/11ce918c75b05d065ce3bf98b20d62465b5afc55) causes print_to (and consequently _print & macros) to redirect to OUTPUT_CAPTURE if set. IIUC, this leaves any direct usage of stdout() uncaptured.

This is inconvenient for systems which use stdout() with generic code over io::Write.

Basically a dupe of the unresolved-but-closed #12309.
Repository: javascript
Issue: [no-restricted-exports] Fails on `export { default } from ...`
Labels: semver-breaking: guide change

As the title states. Fails when re-exporting the default from another module.

```ts
export { default } from 'another-module';
```

This feels like it _should_ pass, since this is not a named export. https://github.com/airbnb/javascript/blob/master/packages/eslint-config-airbnb-base/rules/es6.js#L67
Repository: flutter
Issue: Engine licenses check failing on release branches
Labels: team,P2,team-release,triaged-release

The licenses check is always checking out master to validate the licenses causing the check to always fail on release branches.
Repository: deno
Issue: Cannot use structuredClone on CryptoKey
Labels: feat,web,ext/crypto

I am trying to create a WebWorker, and pass a CryptoKey to it. The idea is that the Web Worker should not be able to extract the key, so I generate the key with `extractable === false`. However, trying to pass a clone of a CryptoKey fails.

According to the [MDN, this should be possible](https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto).

> CryptoKey objects can be stored using the structured clone algorithm, meaning that you can store and retrieve them using standard web storage APIs. The specification expects that most developers will use the IndexedDB API to store CryptoKey objects.

Here is a small snippet that demonstrates the problem. After calling `structuredClone` an empty object is returned.

```typescript
const result = await crypto.subtle.generateKey(
  { name: 'AES-CBC', length: 256 },
  false,
  ['encrypt', 'decrypt'],
);

console.log(result);
console.log(structuredClone(result));

```
Repository: yt-dlp
Issue: [YouTube] Control characters or escape sequences are inserted as text in subtitles (\h or &nbsp)
Labels: enhancement,PR-needed,external issue,site:youtube,core:post-processor

Comment removed.
Repository: PowerToys
Issue: 2nd taskbar
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

I would find it very useful to have a 2nd taskbar available & visible on-screen, capable of having its own set of icons for starting apps, etc.

### Scenario when this would be used?

It is quite convenient and intuitive to have the current general-purpose taskbar, **and** a _2nd one_ for specific-purpose, or specific-user items.

### Supporting information

Other windowing systems allow this and it proves frequently used - and useful
Repository: pytorch
Issue: Unstable buggy calculation.
Labels: needs reproduction,module: optimizer,triaged

```python
import torch
from torch.autograd import Variable
import torch.optim as optim
l=torch.Tensor([1.01, 1.01, 3, 3])

l=Variable(l.float(), requires_grad = True)
optimizer = optim.Adam([l], lr=0.01)
optimizer.zero_grad()

while True:
    l1 = l/(torch.cat([l.mean().unsqueeze(0),l]).cummax(0).values[1:])
    t = l1>=1
    t1 = l1 <1
    diffstate = l1[0:-1]==l1[1:]
    tsum=t.cumsum(0).float()
    substate = tsum - ((tsum*torch.cat([diffstate,torch.Tensor(1)])*t1).cummax(0)).values
    t1sum=t1.cumsum(0).float()
    substate1 = ((t1sum*torch.cat([diffstate,torch.Tensor(1)])*t).cummax(0)).values - t1sum 
    c=(l1-1)*(1+torch.tanh(substate/10+substate1/10))
    loss=-c.sum()
    loss.backward()
    optimizer.step()
    print(loss,l1)
```

```
>>> optimizer.step()
>>> print(loss,l1)
tensor(nan, grad_fn=<NegBackward>) tensor([0.5135, 0.5135, 1.0000, 1.0000], grad_fn=<DivBackward0>)
>>> substate
tensor([0., 0., 1., 2.])
>>> substate1
tensor([-1., -2.,  0., nan])
>>> substate1 = ((t1sum*torch.cat([diffstate,torch.Tensor(1)])*t).cummax(0)).values - t1sum
>>> substate1
tensor([-1., -2.,  0., nan])    <--- wrong
>>> ((t1sum*torch.cat([diffstate,torch.Tensor(1)])*t).cummax(0)).values
tensor([0., 0., 2., 2.])
>>> t1sum
tensor([1., 2., 2., 2.])
>>> ((t1sum*torch.cat([diffstate,torch.Tensor(1)])*t).cummax(0)).values - t1sum
tensor([-1., -2.,  0.,  0.])      <--- this result is correct 
```
the above code would get nan loss and especially substate1 would be tensor([-1., -2.,  0., nan]) after two iteration. however if calculate substate1 mannually, the result can be evaluated correctly to tensor([-1., -2.,  0.,  0.]).
The last element should be evaluated to 0 not nan.


cc @vincentqb @jbschlosser @albanD
Repository: flutter
Issue: Device specific keyboard events on fuchsia
Labels: a: text input,framework,engine,platform-fuchsia,a: desktop,P2,team-text-input,triaged-text-input

Related: https://github.com/flutter/flutter/issues/44918

Currently it seems on fuchsia some keys are not properly "normalized", for instance the backspace key is recognized by the framework as `LogicalKeyboardKey(42 | LogicalKeyboardKey.fuchsiaPlane)`, instead of `LogicalKeyboardKey.backspace`. 
Adding this issue as a TODO in https://github.com/flutter/flutter/pull/93437.
Repository: ant-design
Issue: [Feature Request] Table 增加重设列的尺寸  API
Labels: 💡 Feature Request,Inactive

### 这个功能解决了什么问题？

希望Table组件做一个类似 fusion design 的重设列尺寸的API ， 使用 asyncResizable 和 onResizeChange 调整列宽。如果左右锁列的列宽需要调整

### 你期望的 API 是怎样的？

```jsx
const onChange = function(...args) {
    console.log(...args);
  },
  dataSource = () => {
    const result = [];
    for (let i = 0; i < 5; i++) {
      result.push({
        title: {
          name: `Quotation for 1PCS Nano ${3 + i}.0 controller compatible`
        },
        id: 100306660940 + i,
        time: 2000 + i
      });
    }
    return result;
  },
  render = (value, index, record) => {
    return <a href={`#${index}`}>Remove({record.id})</a>;
  },
  rowSelection = {
    onChange: onChange,
    getProps: record => {
      return {
        disabled: record.id === 100306660942
      };
    }
  };

class App extends React.Component {
  constructor(...args) {
    super(...args);
    this.state = {
      widths: {
        time: 300,
        [`title.name`]: 300
      }
    };
    this.onResizeChange = (dataIndex, value) => {
      const { widths } = this.state;
      widths[dataIndex] = widths[dataIndex] + value;
      this.setState({
        widths
      });
    };
  }
  render() {
    const { widths } = this.state;
    const time = widths.time;
    const name = widths[`title.name`];

    return (
      <Table
        dataSource={dataSource()}
        rowSelection={rowSelection}
        onResizeChange={this.onResizeChange}
      >
        <Table.Column lock title="Id" dataIndex="id" width={100} />
        <Table.Column
          title="Title"
          dataIndex={"title.name"}
          asyncResizable
          width={name}
        />
        <Table.Column
          title="Time"
          dataIndex="time"
          asyncResizable
          width={time}
        />
        <Table.Column cell={render} width={200} />
      </Table>
    );
  }
}

ReactDOM.render(<App />, mountNode);
```

### 其他

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: [Proposal] ChangeNotifier should have a `change((){})` method similar to `setState((){})`.
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

It saves a nice bit of boilerplate when you can single-line changes within a ChangeNotifier.

For example:
```dart
set count(int value){
  _count = value;
  notifyListeners();
}
```
Can become:
```dart
set count(int value) => change(() => _count = value);
```

3 lines shorter, and more readable as well I think. I usually do this with a custom sub-class, but seems like it would make a nice low-risk addition to the core.