sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Dynamic properties are not '.' accessible when accessing external Nodes.
Labels: bug,topic:gdscript,confirmed

**Godot version:**
Godot 3.1 alpha: a92e885

**Issue description:**
When using `_get`, `_set`, and `_get_property_list` to expose a property dynamically, I have found that it functions inconsistently.

- Works
    - Test scene 3) A node exposes its own dynamic property and then prints said property using `self.<property>`.
    - Test scene 2) A node has an exposed Resource property with a script assigned in the Inspector. The Resource script then exposes a dynamic property. The Node prints the resource variable's dynamic property.
- Doesn't work
    - Test scene 1) The *exact* same code from scene 3 is used (without the print statement), but it's placed on a child node. The parent node then attempts to get the child and print the dynamic property.

I am unable to identify the reason that this occurs, so I've concluded that it is likely a bug of some kind.

Note that using `.set(<property>, <value>)` and `.get(<property>)` still works, but not using dot notation.

**Minimal reproduction project:**
[test_dynamic_properties.zip](https://github.com/godotengine/godot/files/2703594/test_dynamic_properties.zip)
Repository: flutter
Issue: WidgetTester.getSemantics should deal better with force-merged semantics
Labels: a: tests,framework,a: accessibility,has reproducible steps,P2,found in release: 3.3,found in release: 3.6,team-framework,triaged-framework

`WidgetTester.getSemantics` [1] is not really aware of the semantics behind `MergeSemantics` [2], which force-merged individual SemanticsNodes into one. Instead of returning a SemanticsNode that contains the force-merged data, it returns individual un-merged SemanticsNodes. This makes it very hard to test the code that does the force-merging in [3].

We need to change `getSemantics` to better deal with force-merging. The individual nodes it currently returns are meaningless after force-merging. And accessing the forceMerged data in a test is .. awkward right now.

Example:

```dart
testWidgets('force-merge', (WidgetTester tester) async {
    final SemanticsTester semantics = SemanticsTester(tester);
    final Key key = GlobalKey();

    await tester.pumpWidget(MaterialApp(
        home: Card(
          elevation: 10.0,
          child: Column(
            children: <Widget>[
              const Text('abs. elevation: 10.0'),
              MergeSemantics(
                child: Semantics(
                  explicitChildNodes: true, // just to be sure that it's going to be an explicit merge
                  child: Column(
                    children: const <Widget>[
                      Card(
                        elevation: 15.0,
                        child: Text('abs. elevation 25.0'),
                      ),
                      Card(
                        elevation: 5.0,
                        child: Text('abs. elevation 15.0'),
                      )
                    ],
                  ),
                ),
              ),
            ],
          )
        )
    ));


    final SemanticsNode node = tester.getSemantics(find.text('abs. elevation 25.0'));
    // The following line fails because we're getting back the unmerged node...
    expect(node.label, 'abs. elevation 25.0\nabs. elevation 15.0');

   // ... instead we have to do the following awkward workaround to get the merged data:
    SemanticsData mergedChildData;
    elevation10.visitChildren((SemanticsNode child) {
      expect(mergedChildData, isNull);
      mergedChildData = child.getSemanticsData();
      return true;
    });

    expect(mergedChildData.label, 'abs. elevation 25.0\nabs. elevation 15.0');

    semantics.dispose();
  });
```

[1] https://master-docs.flutter.io/flutter/flutter_test/WidgetTester/getSemantics.html
[2] https://master-docs.flutter.io/flutter/widgets/MergeSemantics-class.html
[3] https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/semantics/semantics.dart#L1652-L1708
Repository: bitcoin
Issue: Fail on unknown config file options
Labels: Utils/log/libs

A solution would be to either make all binaries be aware of each other's options, or to permit config file options that only apply to specific binaries (`bitcoind`, `bitcoin-qt`, `bitcoin-cli`) or the wallet. (https://github.com/bitcoin/bitcoin/pull/13799#issue-204717028)
Repository: pytorch
Issue: LibTorch: include cmake files for all distributed headers
Labels: module: cpp,triaged

I'm planning to add libtorch support to a project that already uses pybind11, and I got a few errors because libtorch also bundled pybind11, which is automatically added to the include path.

While it's easy enough to use the bundled pybind11 in our project, there is no clean way to reference this in cmake since the libtorch distribution does not include a cmake config file for pybind11. I would suggest adding it, so that one can properly reference the bundled pybind11 version.
Repository: TypeScript
Issue: output declaration type not as expect
Labels: Bug

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.3.0-dev.201xxxxx

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

im not sure whats wrong

- node: v11.5.0
- ts: Version 3.3.0-dev.20181214
- [tsconfig.json](https://github.com/bluelovers/novel-travis-test/blob/master/tsconfig.json)

[init.ts](https://github.com/bluelovers/novel-travis-test/blob/master/script/init.ts#L24)
```ts
import { loadCacheConfig, loadMainConfig, loadConfig } from '@node-novel/task/lib/config';

export let CacheConfig = loadCacheConfig(PROJECT_ROOT);

export let CLONE_DEPTH = process.env.CLONE_DEPTH || 50;
```

@node-novel/task/lib/config
```ts
import { IConfig } from '../index';
export declare function loadMainConfig(cwd?: string): {
    config: IConfig;
    filepath: string;
};
export declare function loadCacheConfig(cwd?: string): {
    config: {
        last: string | number;
        last_from?: string | number;
        done?: number;
        last_push_head?: string;
    };
    filepath: string;
};
export declare function transform(result: any): any;
export declare function loadConfig<T>(name: string, options?: any): {
    config: T;
    filepath: string;
};
export default loadConfig;

```

**Expected behavior:**

init.d.ts
```ts
export declare let CacheConfig: {
    config: {
        last: string | number;
        last_from?: string | number;
        done?: number;
        last_push_head?: string;
    };
    filepath: string;
};

export declare let CLONE_DEPTH: string | number;
```

**Actual behavior:**

init.d.ts
```ts
export declare let CacheConfig: {
    config: {
        last: import("node-novel-info").INumber;
        last_from?: import("node-novel-info").INumber;
        done?: number;
        last_push_head?: string;
    };
    filepath: string;
};

export declare let CLONE_DEPTH: import("node-novel-info").INumber;
```

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: javascript-algorithms
Issue: Provide use cases for the abstraction
Labels: enhancement

I suppose this falls under a feature request..

I think there is a lot of great content here. However, honestly they would become far more valuable (to me, at least) if there were use cases detailed in the README.md of each algorithm.
Repository: go
Issue: x/build/maintner: GitHub issue events are not consistent with API values
Labels: help wanted,Builders,NeedsInvestigation

Moved from #28226…

There are some issues that have events missing within the maintner corpus. This makes it impossible to create an accurate milestone burndown chart where you want to query for the state of an issue at a particular time window.

A few examples of issues in maintner that have incomplete event lists:
```
=== Issue events for golang.org/issues/28559
             labeled	milestone:         	label:Testing
             labeled	milestone:         	label:help wanted
             labeled	milestone:         	label:OS-OpenBSD
             labeled	milestone:         	label:Builders
             labeled	milestone:         	label:NeedsInvestigation
          milestoned	milestone:   Go1.12	label:
```
It does not record the final “closed” event: https://api.github.com/repos/golang/go/issues/28559/events

```
=== Issue events for golang.org/issues/28306
           mentioned	milestone:         	label:
          subscribed	milestone:         	label:
           mentioned	milestone:         	label:
          subscribed	milestone:         	label:
            assigned	milestone:         	label:
             labeled	milestone:         	label:Documentation
             labeled	milestone:         	label:NeedsInvestigation
          milestoned	milestone:   Go1.12	label:
             renamed	milestone:         	label:
```
The above event log is missing a few milestone-related events: https://api.github.com/repos/golang/go/issues/28306/events
Repository: TypeScript
Issue: Void parameter still required when type extends generic
Labels: Bug

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.2.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
void parameter type extends generic
**Code**

```ts
function works1(n: number, b: void) { }

works1(12);

function works2(n: number, b: 1 extends 1 ? void : number) { }

works2(12);

function fails<T>(n: number, b: T extends 1 ? void : number) { }

fails<2>(12, 2);  // works, requires both params
fails<1>(12);  // fails, requires 2 parameters even though second param is void

```

**Expected behavior:**
That I can ignore the second parameter since its void

**Actual behavior:**
Ts tells me I am missing a parameter


https://www.typescriptlang.org/play/index.html#src=function%20works1(n%3A%20number%2C%20b%3A%20void)%20%7B%20%7D%0D%0A%0D%0Aworks1(12)%3B%0D%0A%0D%0Afunction%20works2(n%3A%20number%2C%20b%3A%201%20extends%201%3F%20void%20%3A%20number)%20%7B%20%7D%0D%0A%0D%0Aworks2(12)%3B%0D%0A%0D%0Afunction%20fails%3CT%3E(n%3A%20number%2C%20b%3A%20T%20extends%201%3Fvoid%3Anumber)%20%7B%20%7D%0D%0A%0D%0Afails%3C2%3E(12%2C2)%3B%20%20%2F%2Fworks%2C%20requires%20both%20params%0D%0Afails%3C1%3E(12)%3B%20%20%2F%2F%20requires%202%20parameters%20even%20though%20second%20param%20is%20void%0D%0A
Repository: go
Issue: fmt: Fscan might not work on tracefs "id" files
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.11 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Use `fmt.Fscan` on a tracefs `id` file. For example
`/sys/kernel/debug/tracing/events/tcp/tcp_set_state/id`

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/elazar/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/elazar/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
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 -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build929178475=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?

https://play.golang.org/p/sKRnsBHZ6Gc


### What did you expect to see?

The same event ID I see when `cat`ing the file.

### What did you see instead?

Just the first digit, `1`.

For the record "id" in tracefs is not implemented by `seq_file`:

```C
static ssize_t
event_id_read(struct file *filp, char __user *ubuf, size_t cnt, loff_t *ppos)
{
	int id = (long)event_file_data(filp);
	char buf[32];
	int len;

	// Elazar: This is probably the culprit. Can be removed, simple_read_from_buf handles it.
	if (*ppos)
		return 0;

	if (unlikely(!id))
		return -ENODEV;

	len = sprintf(buf, "%d\n", id);

	return simple_read_from_buffer(ubuf, cnt, ppos, buf, len);
}
```

Still relevant in `master` [branch](https://github.com/torvalds/linux/blob/master/kernel/trace/trace_events.c#L1315)

It seems that `simple_read_from_buffer` somehow doesn't keep track of  the `ppos`, though it should.

For example

```C
#include <stdio.h>
#include <stdint.h>

#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>

int main(int argc, char **argv) {
  if (argc < 2)
    return 1;
  int fd = open(argv[1], O_RDONLY);
  char c;
  read(fd, &c, 1);
  printf("Got %c\n", c);
  read(fd, &c, 1);
  printf("Got %c\n", c);
}
// output:
// Got 1
// Got 1
```

While this might be a kernel bug per se, one might consider a workaround, since it's pretty widespread.
Repository: rust
Issue: [idea] Add an option put the metadata in a separate file
Labels: A-metadata,T-compiler,C-feature-request

# Detailed design

When `-Zsplit-metadata` is passed to rustc, it will put the metadata normally inside a `rlib` or `dylib` in a separate `rmeta` file. The `rlib`/`dylib` will contain the SVH to prevent accidentally mixing the `rmeta` and `rlib`/`dylib` of different compilations.

# Advantages

This would make the increase in size of #56987 easily fixable by deleting the `rlib` files, while keeping the `rmeta` files. Those are not necessary anyway, because `rustc_driver.so` already contains the code.

This will decrease `staticlib`, `dylib` and `cdylib` compilation time, because there is no need to copy all object files to a new archive to remove the `rust.metadata.bin` file from the `rlib`.
https://github.com/rust-lang/rust/blob/6d9640b6f6275a4b59e2a59705e18807329b9300/src/librustc_codegen_llvm/back/link.rs#L1340-L1342

# Disadvantages

Rustc and cargo get a bit more complex.
Repository: go
Issue: x/text: support error and fmt.Stringer values
Labels: NeedsDecision,FeatureRequest

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.11.4 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes, this is the latest release

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/fgm/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/fgm/src/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
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 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/0g/p780bc554njc4qj110_8rmbr0000gn/T/go-build831580697=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

- Tried to produce translated custom errors.
- https://play.golang.org/p/liw_jlauDmw (won't run on playground because of imports)

### What did you expect to see?

- string values for `err` are extracted and translations running displays the error in french.

### What did you see instead?

- "panic: key argument is not a Reference"

### Diagnostic

This happens because `message.lookupAndFormat()` can only handle plain strings and message.key (unexported type) as translation keys. It would make it easier to have translatable errors and other higher-level data if the switch handled `error` and `fmt.Stringer` values.

- Values of type `error` could be converted to strings using their `Error()` method, and thereafter handled as strings (`id, mgs = v, v`)
- Values implementing `fmt.Stringer` could be converted to strings using their `String()` method, and handled the same way.
Repository: flutter
Issue: Feature Request: Show/hide splashscreen in dart
Labels: c: new feature,framework,engine,P2,team-engine,triaged-engine

When launching my Flutter application, the splashscreen is shown. After the first Flutter frame is rendered, the splashscreen will be hidden and the Flutter view will be loaded and shown.

However during loading the Flutter view it needs some time to store a big asset image in the image cache. The asset image is actually the same as the splashscreen image, but now as background image loaded from the assets folder.

I can preload this image like this:

```dart
preloadBackground() async {
    final ImageConfiguration config = createLocalImageConfiguration(context);
    Image image = Image.asset('assets/background.jpg');
    Completer<ui.Image> completer = new Completer<ui.Image>();
    image.image.resolve(config).addListener((ImageInfo info, bool _) {
        completer.complete(info.image);
    });

    await completer.future;
}
```

However it needs the BuildContext for this, and once we can pass the buildContext it also renders the page. So it shows a white screen for some seconds even with preloading.

I also tried lowering the resolution of the background image, but then you can see a big quality difference between the splashscreen and the AssetImage.

This is just an example but I can image other useful scenarios, for example if you want to preload images or data from the internet before the Flutter view is shown.

So it would be great if we can show/hide the splash screen after launching the flutter application, like in Cordova:
`navigator.splashscreen.show();`
`navigator.splashscreen.hide();`

And then we also need a settings like:

```
<meta-data
                android:name="io.flutter.app.android.HideSplashScreenAfterFirstFrame"
                android:value="false" />
```

And the equivalent setting in the plist file for iOS.

What do you guys think?
Repository: TypeScript
Issue: Missing 'used before declaration' error with IIFE
Labels: Suggestion,In Discussion

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.2.1

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

```ts
class C {
    a = (() => this.b)();
    b = '';
}
```

**Expected behavior:**

Error `Property 'b' is used before its initialization.`
Control flow analysis inlines IIFEs, but it seems the use-before-declare check doesn't.

**Actual behavior:**

No error

**Playground Link:** https://agentcooper.github.io/typescript-play/#code/MYGwhgzhAEDC0G8BQ1XTNAvNAFDglFgHzQAuAFgJYQB0ARvgQNwpp1bQDknLAvkA

**Related Issues:** Found while investigating https://github.com/Microsoft/TypeScript/issues/29125
Repository: TypeScript
Issue: missing 'used before declaration' error within computed name of accessor or method
Labels: Bug

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.3.0-dev.20181222

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

Taken from the tests added in https://github.com/Microsoft/TypeScript/pull/29136

```ts
class D {
    static A = class extends D.B {
        [D.D]() {} // should be an error
    }
    static B = class {}
    static C = {
        [D.D]: 1,
        ...{get [D.D]() {return 0;}} // should be an error
    };
    static D = '';

    [foo]() {} // should have an error
} 

let bar = {
    [foo]() {} // should have an error
}
let foo = 1;
```

**Expected behavior:**

The lines marked with `// should be an error` should have an error.

**Actual behavior:**

Currently there's no error at all. After #29136 lands the lines with the comments are missing an error.

**Playground Link:** https://agentcooper.github.io/typescript-play/#code/MYGwhgzhAEAi0G8BQ1XQgFzBglsaAgtALzSiQwCmAHhpQHYAmMsAdAEKIpo8DabsALoAKAJSIAvtAD009AAsA9gFcQjaACNK0MPWiUATgcUHuqCWfRZc+TqXJRJlzNjzQAwiS48+AwQC5oAEYAGkseVkiEAHNKDGh+ViExRAM45QM9AAYAbgkpWQUVNU1tXX0jE0sJHOdrN3hSAHIm2qkgA

**Related Issues:** #29135