sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: bitcoin
Issue: Small unspent can get removed from OutputGroup for being uneconomical probably leading to later partial spending
Labels: Bug,Wallet

Placeholder, we are still testing this. cc: @achow101.

<!-- This issue tracker is only for technical issues related to Bitcoin Core.

General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com.

For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/.

If the node is "stuck" during sync or giving "block checksum mismatch" errors, please ensure your hardware is stable by running memtest and observe CPU temperature with a load-test tool such as linpack before creating an issue! -->

<!-- Describe the issue -->

**Expected behavior**

<!--- What behavior did you expect? -->

**Actual behavior**

<!--- What was the actual behavior (provide screenshots if the issue is GUI-related)? -->

**To reproduce**

<!--- How reliably can you reproduce the issue, what are the steps to do so? -->

**System information**

<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->

<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->

<!-- GUI-related issue? What is your operating system and its version? If Linux, what is your desktop environment and graphical shell? -->

<!-- Any extra information that might be useful in the debugging process. -->
<!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->
Repository: next.js
Issue: Correct type inference when using `fallback: true`
Labels: TypeScript

# Feature request

## Is your feature request related to a problem? Please describe.

When I'm using `fallback: true` in `getStaticPaths` and using `InferGetStaticPropsType` to infer the props, it doesn't take the fact that the fallback page might load into account. It assumes that the props will always get passed to the page.

```javascript
import { InferGetStaticPropsType } from 'next'

type Post = {
  author: string
  content: string
}

export const getStaticPaths = async ({params}) => {
  const res = await fetch(`https://.../posts/${params.id}`)
  const posts: Post[] = await res.json()

  return {
    paths: [{ params: { id: '1' }],
    fallback: true
  }
}

export const getStaticProps = async ({params}) => {
  const res = await fetch(`https://.../posts/${params.id}`)
  const posts: Post[] = await res.json()

  return {
    props: {
      posts,
    },
  }
}

function Blog({ posts }: InferGetStaticPropsType<typeof getStaticProps>) {
  // will resolve posts to type Post[] although it will be undefined if router.isFallback is true
}

export default Blog
```

## Describe the solution you'd like

I'd like to have the possibility to pass the getStaticPaths as a second argument to the `InferGetStaticPropsType` type like this:
```typescript
InferGetStaticPropsType<typeof getStaticProps, typeof getStaticPaths>
```
 
The `InferGetStaticPropsType` type would infer if the props can be an empty object based upon the value of `fallback` returned from getStaticPaths.

## Describe alternatives you've considered

An alternative is to type the props manually if using `fallback: true` like this:
```javascript

function Blog({ posts }: InferGetStaticPropsType<typeof getStaticProps> | {}) {
  // will resolve posts to type Post[] although it will be undefined if router.isFallback is true
}
```
Repository: create-react-app
Issue: react-scripts v4.0.0 causes local images to not load
Labels: needs triage,issue: bug report

### Describe the bug

Upgrading from v3.4.4 to v4.0.0 (using `npm install react-scripts@latest`) causes my local images (using `src={require("../../assets/images/logo/logo-v4.png")}`) to not load, however external images load. (see [StackOverflow post here ](https://stackoverflow.com/questions/64637740/react-js-project-local-images-suddenly-stopped-loading/64653264#64653264)) Fixed by simply downgrading to v3.4.4.

### Environment

Tested using MacOS Catalina v10.15.7 and Windows 10 on Chrome Version 86.0.4240.111
Repository: flutter
Issue: Flare in Stack - disappearing when widget tree repaints
Labels: engine,platform-web,c: rendering,has reproducible steps,customer: web10,customer: thrive,P2,found in release: 3.7,found in release: 3.10,team-web,triaged-web

We had an issued filed with the Flare-Flutter library reporting animations disappearing when they are paused:
https://github.com/2d-inc/Flare-Flutter/issues/286

It turns out this only happens in a Stack (although there is some flickering in Row/Column too). Has Flutter introduced some view/widget caching that could be acting too aggressively?

We've traced through the paint calls and it seems like Flare is drawing when requested to draw. When the ListView in the stack is dragged, the Flare widget above it in the Stack no longer gets a paint call. This is when the animation disappears. Flare won't call "markNeedsPaint" until the animation changes, assuming Flutter will draw the widget on demand if it needs to repaint for external reasons (this is the behavior we used to see).

Furthermore, it seems like the issue resolves if we wrap the Flare widget in a ColoredBox with a non-transparent background (which is odd as the framework [seems to make no distinction](https://github.com/flutter/flutter/blob/88809aa24720705d1cd8de0bfc46faf932fe0b6e/packages/flutter/lib/src/widgets/basic.dart#L7557-L7574) at the Flutter level if the ColoredBox has a transparent background or not).  [Video here.](https://drive.google.com/file/d/1Pgr2xciN9wY6XyqfHZ8oS5r5pvk8OHnV/view?usp=sharing) We're wondering if there are some under the hood caching heuristics that Flare is tripping up...or somehow Flare is making Flutter think it has no content?


Doctor:
```
[✓] Flutter (Channel stable, 1.22.3, on Mac OS X 10.15.7 19H2, locale en-US)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 12.1)
[!] Android Studio (version 4.0)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] Connected device (1 available)

! Doctor found issues in 1 category.
```

We attempted to reproduce this in isolation (without Flare/Rive 1's painting) but weren't able to reproduce the issue. It seems like there's a specific combination of events that's making Flutter cache an old/empty state for this widget and we're hoping the Flutter team has insight as to what it could be.
Repository: svelte
Issue: Animation blocks transition
Labels: stale-bot,temp-stale,transition/animation

**Describe the bug**
I couldn't find an issue about it, and the docs don't mention the behaviour either. Is it expected behaviour that an animation of an element blocks a transition of it?

![bug](https://user-images.githubusercontent.com/33468089/97928478-6cda1280-1d67-11eb-8b45-6185a72f8bde.gif)

**To Reproduce**
1. Create list of elements that changes over time, e.g. with an ephemeral list store.
2. Put a transition and animation on these elements.
3. Schedule the changes such that the transition happens at the same time as the animation.

https://svelte.dev/repl/40d4bef097c645189e1a4d73d76ec79f?version=3.29.4

**Expected behavior**
I'd expect a transition of to not be blocked by an animation, the same way that two transitions don't block each other.
Repository: go
Issue: x/review/git-codereview: incomplete help documentation for `git codereview`
Labels: Documentation,NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15 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/ithuriel/.cache/go-build"
GOENV="/home/ithuriel/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/ithuriel/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/ithuriel/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/ithuriel/go/src/golang.org/x/oauth2/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=/tmp/go-build639262882=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
N/A


### What did you expect to see?
Since `git codereview mail` supports the `-nokeycheck` option, I would expect to see that documented.
### What did you see instead?
As far as I can tell, this option isn't listed anywhere in the documentation.  `git codereview help` doesn't mention it, and the [longer documentation](https://godoc.org/golang.org/x/review/git-codereview) doesn't mention it either.  I only figured out that the option exists by reading the [source code](https://go.googlesource.com/review/+/refs/heads/master/git-codereview/mail.go), which isn't ideal.


The [longer documentation](https://godoc.org/golang.org/x/review/git-codereview) does say that 

> The “git codereview mail” command requires an explicit revision argument, but note that since “git codereview mail” is implemented as a “git push”, any commits earlier in the stack are necessarily also mailed.

However, I don't think that this makes it sufficiently clear that the -nokeycheck option exists.
Repository: flutter
Issue: Add stress tests for add-to-app to find race conditions
Labels: a: tests,framework,engine,a: existing-apps,P2,team-engine,triaged-engine

We should setup and teardown FlutterEngines and FlutterViewControllers numerous times to make sure we don't introduce race conditions that wouldn't show up often in full flutter apps.
Repository: rust
Issue: CString lifetime warning incorrectly fires
Labels: A-lints,A-FFI,T-lang,C-bug

<!--
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
use std::ffi::CString;

extern "C" {
    fn gecko_profiler_register_thread(foo: *const std::os::raw::c_char);
}

pub fn main() {
    unsafe {
        gecko_profiler_register_thread(CString::new("foo").unwrap().as_ptr());
    }
}
```

I get:
```
warning: getting the inner pointer of a temporary `CString`

 --> <source>:9:69

  |

9 |         gecko_profiler_register_thread(CString::new("foo").unwrap().as_ptr());

  |                                        ---------------------------- ^^^^^^ this pointer will be invalid

  |                                        |

  |                                        this `CString` is deallocated at the end of the statement, bind it to a variable to extend its lifetime

  |

  = note: `#[warn(temporary_cstring_as_ptr)]` on by default

  = note: pointers do not have a lifetime; when calling `as_ptr` the `CString` will be deallocated at the end of the statement because nothing is referencing it as far as the type system is concerned

  = help: for more information, see https://doc.rust-lang.org/reference/destructors.html


warning: 1 warning emitted


Compiler returned: 0
```
However since the CString is not deallocated until after the function call the code is fine and the warning should not trigger.

See https://rust.godbolt.org/z/vjrvGn for the assembly.
Repository: ant-design
Issue: Allow primitive values as table's datasource
Labels: help wanted,Inactive

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### What problem does this feature solve?
In complex applications where **normalized** data is managed in a global state like redux, a list component may receive an array of ids in a form of `number[]` or `string[]`.

One way is to map these ids into data objects with `useSelector` like (between some complicated relations):

```js
const dataSource = useSelector(s => props.ids.map(i => {
  const post = s.entities.posts[i];
  const author = s.entities.users[post.author];
  return {
    ...post,
    author,
  };
}));
```

This solution works as expected but has a terrible performance because it creates new post object on every run, rows and columns re-renders then.

Another way is to pass id array to Table and select data inside column's render component like:

```jsx
const AuthorEmail = ({id}) => {
  const email = useSelector(s => s.entities.users[id].email);
  return <span>{email}</span>;
};

const columns = [
  {
    title: 'Author Email',
    key: 'authorEmail',
    render(id) {
      return <AuthorEmail id={id} />
    },
  },
];

<Table columns={columns} dataSource={ids} />
```

By introducing `AuthorEmail` component to directly select a very fine-grained part of state, we can eliminate most unexpected re-renders, also this pattern works perfectly with future state management framework [recoil](https://recoiljs.org/docs/introduction/getting-started) where entity data can be managed separately in large amount of atoms, which can't be mapped from an array of id.

Currently `Table` **can** be used in the way - except typescript warns:

```
Type 'number' does not satisfy the constraint 'object'. ts(2344)
```

`Table#dataSource` is declared as `object[]` so that `number[]` can't be its value: https://codesandbox.io/s/withered-platform-t3wg0?file=/src/App.tsx

### What does the proposed API look like?
Have a loose `dataSource` type constraint so that it accepts primitive dataSource


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: ListView+Image first time  run on ios get stuck
Labels: platform-ios,framework,engine,c: performance,f: scrolling,a: images,perf: speed,P2,team-ios,triaged-ios

flutter doctor -v
![image](https://user-images.githubusercontent.com/34728569/97946659-0d5f1f80-1dc6-11eb-9e27-c695c2d892ea.png)

video linke
[RPReplay_Final1604373139.zip](https://github.com/flutter/flutter/files/5479154/RPReplay_Final1604373139.zip)

this is code:
![image](https://user-images.githubusercontent.com/34728569/97946854-88c0d100-1dc6-11eb-9e78-757052baac62.png)
![image](https://user-images.githubusercontent.com/34728569/97946862-8f4f4880-1dc6-11eb-898d-5dd46c02480b.png)

this issue only ios,android is normal
Repository: rust
Issue: rustdoc: Implementations on Foreign Types are not sorted in sidebar
Labels: A-trait-system,C-discussion,T-rustdoc-frontend

See in the docs for the [`num`](https://docs.rs/num/0.3.0/num/trait.Num.html) crate:

![image](https://user-images.githubusercontent.com/37223377/97950307-502fe180-1d4b-11eb-8e18-976a7f1f345b.png)
Repository: rust
Issue: rustdoc: Strip blank lines from start and end of code blocks
Labels: T-rustdoc,C-enhancement,A-markdown-parsing

People will often use the `#` character to hide lines that aren't relevant to the example, but rustdoc will display blank lines you leave between `#`-prefixed lines and the visible lines. For example, this source:

```rust
//! ```
//! # #[cfg(any(feature = "alloc", feature = "std"))]
//! # mod test {
//!
//! use num::FromPrimitive;
//! use num::bigint::BigInt;
//! use num::rational::{Ratio, BigRational};
//!
//! # pub
//! fn approx_sqrt(number: u64, iterations: usize) -> BigRational {
//!     let start: Ratio<BigInt> = Ratio::from_integer(FromPrimitive::from_u64(number).unwrap());
//!     let mut approx = start.clone();
//!
//!     for _ in 0..iterations {
//!         approx = (&approx + (&start / &approx)) /
//!             Ratio::from_integer(FromPrimitive::from_u64(2).unwrap());
//!     }
//!
//!     approx
//! }
//! # }
//! # #[cfg(not(any(feature = "alloc", feature = "std")))]
//! # mod test { pub fn approx_sqrt(n: u64, _: usize) -> u64 { n } }
//! # use crate::test::approx_sqrt;
//!
//! fn main() {
//!     println!("{}", approx_sqrt(10, 4)); // prints 4057691201/1283082416
//! }
//!
//! ```
```

leads to this output:

![image](https://user-images.githubusercontent.com/37223377/97951363-ceda4e00-1d4e-11eb-850d-2f86ad240b40.png)

I propose that rustdoc strips blank lines from the start and end of code blocks to avoid this not-great-looking output. This would happen after the `#` lines were stripped out.
Repository: pytorch
Issue: [Feature Request] tensorboard add_graph support for multiple method
Labels: oncall: visualization

## 🚀 Feature

For a PyTorch model, `add_graph` (in `torch.utils.tensorboard.SummaryWriter`) uses `forward` method of the model to trace the graph.

I propose to support for multiple methods of the model (not only the `forward` method).

I think it only needs a small change in implementation:

- check `input_to_model` is dict or list (https://github.com/pytorch/pytorch/blob/master/torch/utils/tensorboard/writer.py#L722)
- change from `torch.jit.trace` to `torch.jit.trace_module` (https://github.com/pytorch/pytorch/blob/master/torch/utils/tensorboard/_pytorch_graph.py#L286)


### Reference

- https://pytorch.org/docs/stable/generated/torch.jit.trace.html
- https://pytorch.org/docs/stable/generated/torch.jit.trace_module.html
Repository: PowerToys
Issue: [FancyZones] Option to change precedence between "move to last known zone" and "move to active monitor"
Labels: Idea-Enhancement,FancyZones-Settings,Product-FancyZones

## ℹ Computer information

- PowerToys version: v0.25.0
- PowerToy Utility: Run + Fancy Zones
- Running PowerToys as Admin: Yes
- Windows build number: [run "winver"] 19041.572

This setting only opens on the last known zone even if it is on a different screen. 

![image](https://user-images.githubusercontent.com/72728399/97964267-c880bc00-1db8-11eb-9b54-a0db754abc19.png)

### ✔️ Expected result

With both settings enabled I am expecting "the last known zone" for that particular screen.

### ❌ Actual result

it does only open on the last known zone even if it is on a different screen.
Repository: godot
Issue: High Resouce usage in empty scenes (Profiler)
Labels: topic:editor,documentation



**Godot version:**
Godot 3.2.4 beta1 under Linux KaOS

**Issue description:**

I'm in doubt if this is normal, but this is a profiler for a empty scene:
![image](https://user-images.githubusercontent.com/58845030/97974427-530bf000-1da6-11eb-8afa-9a461075137e.png)

In my current project is worse in the same situation:
![image](https://user-images.githubusercontent.com/58845030/97974568-8e0e2380-1da6-11eb-9693-b39b764cd8a2.png)



**Steps to reproduce:**

* Open a 2D empty scene
* Start Profiler
* Run game
* Check Profiler

**Minimal reproduction project:**
N/A
Repository: node
Issue: [Proposal] Deprecate --without-intl compilation flag
Labels: i18n-api

<!--
Thank you for suggesting an idea to make Node.js better.

Please fill in as much of the template below as you're able.
-->

**Is your feature request related to a problem? Please describe.**

Currently, Node.js supports the compilation with disabled ICU. I think we would benefit from officially deprecating it:

- There are already some features that are not supported, sometimes without warnings (E.G.: https://github.com/nodejs/node/pull/35099)
- It blocks us from moving forward with the deprecation of `punycode` core module (https://github.com/nodejs/node/pull/35092)
- It blocks us from using `Intl` built-in methods in node core.
- Some of the tooling we use in core doesn't support it (E.G.: ESLint).

**Describe the solution you'd like**

Having a warning in the console when compiling using `--without-intl` flag, and document that Node.js versions compiled without ICU are expected to have some unavailable features.

Also, I think the project should allow initiatives like https://github.com/nodejs/node/pull/27662 to land even if it doesn't work on `--without-intl` `node` versions.

If you are yourself a user of non-ICU versions of Node.js, please join the discussion, I'd be interested to hear what are the use-cases.

cc/ @nodejs/tsc
Repository: kubernetes
Issue: requiredDuringSchedulingRequiredDuringExecution status
Labels: sig/scheduling,sig/node,kind/feature,needs-triage

`requiredDuringSchedulingRequiredDuringExecution` is mentioned [in the documentation](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity) as "In the future we plan to offer",
but I could not find any plan to do so in a near future. None of the workarounds I found until now could help us fixing a scheduling problem where `requiredDuringSchedulingIgnoredDuringExecution` is insufficient. We have a constraint for some replicas of a deployment to be co-located on the same node. `requiredDuringSchedulingIgnoredDuringExecution` does the job for initial deployment, but whenever one of these pods crashes, he will most probably be re-scheduled somewhere else, crashing the whole application.

What is also disturbing is that I found some resources mentioning it as working and when I tried, there was no error
when I applied it: the `affinity` section was just left blank without notice, both in the updated deployment and pods. If the feature is not 
supported, I doubt this is the intended behavior, is it?
Repository: rust
Issue: supertraits do not resolve correctly for dynamic dispatch trait bounds
Labels: T-compiler,C-bug,A-coercions,A-trait-objects

<!--
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:

https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=7e579f79329f28e5441b0291d22d60f9


where `X` is the supertrait in question.

```rust
use std::fmt;

pub trait X: 'static + fmt::Debug + fmt::Display + Send + Sync {}

impl<T: 'static + fmt::Debug + fmt::Display + Send + Sync> X for T {}


#[derive(Debug)]
enum Skippy {
    V(Box<dyn X>),
    Alpha,
    Beta,
}

impl fmt::Display for Skippy {
 	fn fmt(&self, fmt: &mut fmt::Formatter) -> fmt::Result {
		writeln!(fmt, "yak")
	}
}


// commenting out either of them makes is fail to compile

// impl From<Box<dyn X + Send + Sync>> for Skippy {
// 	fn from(e: Box<dyn X + Send + Sync>) -> Self {
// 		Self::V(e)
// 	}
// }


impl From<Box<dyn X>> for Skippy {
	fn from(e: Box<dyn X>) -> Self {
 		Self::V(e)
	}
}


#[inline(never)]
fn alpha() -> Box<dyn X> {
    Box::new(Skippy::Alpha)
}


#[inline(never)]
fn beta() -> Box<dyn X + Send + Sync + 'static> {
    Box::new(Skippy::Beta)
}

fn main() {
    Skippy::from(alpha());
    Skippy::from(beta());
}
```

I expected to see this happen: *explanation*

Work fine with just one `From<Box<dyn X>>` impl, since the traits are already included in the super trait.

Instead, this happened: *explanation*

Requirement to impl for multiple summed trait bounds.

### 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`:
```
1.47.0
```