sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Cannot call static function from a static function (in the same file) with class prefix
Labels: bug,topic:gdscript

**Godot version:**
3.2.3 Stable and 3.2.4 (RC4 and RC5) 64-bit.

**OS/device including version:**
Windows 10

**Issue description:**
If you create a class with two static functions, and have one static function call the other with the class prefix Godot errors out with `Internal script error! - opcode #38`
and then this is in the console:
```
ERROR: GDScriptCompiler bug.
   At: modules/gdscript/gdscript_function.cpp:89
```

This can be resolved by not including the class prefix, but ideally it shouldn't matter if it's included or not.

**Steps to reproduce:**
Create a static function that calls another static function within the same class, with the class as a prefix. 

```
class HelloWorld:    
    static func helper_func():
        print("I'm helping!")
    
    static func do_crash():    
        # Crashes as soon as it sees `HelloWorld`
        HelloWorld.helper_func()
        
        print("Hello world!")
```

**Minimal reproduction project:**
[OpcodeError.zip](https://github.com/godotengine/godot/files/6137523/OpcodeError.zip)
Repository: vscode
Issue: Closing Bracket indentation doesn't work for some languages
Labels: help wanted,polish,editor-autoindent,visualbasic,on-unit-test

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
- VS Code Version: 1.51.1
- OS Version: Windows_NT x64 10.0.17763

<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported direct to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->

Steps to Reproduce:

1. Open a Visual Basic file (.vb)
2. Type:
```
if True then
    ' Some code  
end if
```

**Expected:** When you type "End If", the indentation will go back to the same level as the opening block ("if"), as can be seen above.

**Actual:** The "end if" stays in the wrong indentation level:
```
if True then
    ' Some code  
    end if
```

**Possible cause and solution**:
I found out that this can happen in all programming languages where a closing tag includes the opening tag as a separate word (For example: _If ... End If_, or _While ... End While_).

**Solution:** This is related to the order of the pieces as defined in [these lines of code in the richEditBrackets.ts file](https://github.com/microsoft/vscode/blob/a699ffaee62010c4634d301da2bbdb7646b8d1da/src/vs/editor/common/modes/supports/richEditBrackets.ts#L228)

- If you change the order so that first the **closing** brackets would be pushed and only then the **opening** brackets, then it will work.
- Alternatively, you can modify the _createBracketOrRegExp_ function and just add a reverse() function there.

I'm not sure if it will mess things up or not (though my initial tests look promising) and I'm not too familiar with the code to change it myself and issue a PR, so please take a look and let me know what you think.

Thank you!
Repository: rust
Issue: write_all for a single byte to a slice is turned into a memset, sometimes
Labels: I-slow

```rust
fn main() {
    let mut buf = [0u8; 64];
    ser_str(&mut buf, "test_string");
}

#[inline(never)]
fn ser_str(buf: &mut [u8], thing: &str) {
    serde_json::to_writer(buf, thing).unwrap();
}
```

As far as I can tell, the call to `Formatter::begin_string` is completely optimized away. Awesome. And it's even totally optimized away if I mark `Formatter::begin_string` as `#[inline(never)]`, which has me a bit confused. By contrast, the call to `Formatter::end_string` is turned into a `memset` for a single byte. Significantly less awesome. Especially in light of their identical definitions:
```rust
    /// Called before each series of `write_string_fragment` and
    /// `write_char_escape`.  Writes a `"` to the specified writer.
    #[inline]
    fn begin_string<W>(&mut self, writer: &mut W) -> io::Result<()>
    where
        W: ?Sized + io::Write,
    {
        writer.write_all(b"\"")
    }

    /// Called after each series of `write_string_fragment` and
    /// `write_char_escape`.  Writes a `"` to the specified writer.
    #[inline]
    fn end_string<W>(&mut self, writer: &mut W) -> io::Result<()>
    where
        W: ?Sized + io::Write,
    {
        writer.write_all(b"\"")
    }
```

### Meta

`rustc --version --verbose`:
```
rustc 1.52.0-nightly (acca81892 2021-03-13)
binary: rustc
commit-hash: acca818928654807ed3bc1ce0e97df118f8716c8
commit-date: 2021-03-13
host: x86_64-unknown-linux-gnu
release: 1.52.0-nightly
LLVM version: 12.0.0
```

`Cargo.lock`:
```toml
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
version = 3

[[package]]
name = "itoa"
version = "0.4.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dd25036021b0de88a0aff6b850051563c6516d0bf53f8638938edbb9de732736"

[[package]]
name = "ryu"
version = "1.0.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "71d301d4193d031abdd79ff7e3dd721168a9572ef3fe51a1517aba235bd8f86e"

[[package]]
name = "scratch"
version = "0.1.0"
dependencies = [
 "serde_json",
]

[[package]]
name = "serde"
version = "1.0.124"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bd761ff957cb2a45fbb9ab3da6512de9de55872866160b23c25f1a841e99d29f"

[[package]]
name = "serde_json"
version = "1.0.64"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "799e97dc9fdae36a5c8b8f2cae9ce2ee9fdce2058c57a93e6099d919fd982f79"
dependencies = [
 "itoa",
 "ryu",
 "serde",
]
```
Repository: neovim
Issue: Locally set `iskeyword` should be decoupled from command line mode
Labels: enhancement,bug-vim

<!-- Before reporting: search existing issues and check the FAQ. -->

- `nvim --version`: NVIM v0.4.4
- Operating system/version: Debian GNU/Linux bullseye/sid
- Terminal name/version: konsole
- `$TERM`: xterm-256color

### Steps to reproduce using `nvim -u NORC`
I came across this while working on a Clojure project, but traced it back to Lisp. To reproduce: 

- Open a lisp file in a sufficiently nested directory, say, `my/new/lisp/proj/test.lisp`.
- Attempt to navigate to a file in a parent directory by entering command line mode, typing `:e %:h`, expanding with `wildchar`, and deleting the previous word with `<c-w>`

### Actual behaviour
The entire path is deleted down to the space space before the `e`.

### Expected behaviour
The problem lies in `runtime/ftplugin/lisp.vim`, where `iskeyword` is locally set to admit a menagerie of other symbols. This may be the intended behavior (in which case this would be more of a feature request), but I expect the locally set variable `iskeyword` for the current buffer to be decoupled from it's value in command line mode.
Repository: flutter
Issue: [Autocomplete] Expose the latest TextEditingValue in optionsViewBuilder
Labels: c: new feature,framework,f: material design,team-design,triaged-design

This requires updating the function signature for [AutocompleteOptionsViewBuilder](https://master-api.flutter.dev/flutter/widgets/AutocompleteOptionsViewBuilder.html), but it allows users to use the current text values to customize rendering of the options UI.

This would be a breaking change. However, there is currently a workaround for this at the Flutter app level by keeping track of the `TextEditingController` value yourself to customize rendering.
Repository: flutter
Issue: [Autocomplete] Provide manual control of hiding/showing options UI
Labels: framework,f: material design,team-design,triaged-design

As titled. Suggestions in the original issue are:

1. Providing a nullable boolean parameter for showing/hiding the options UI
2. Allowing to override the _shouldShowOptions method
3. Creating an optional AutocompleteController with show/hide methods to support imperative interactions.
Repository: flutter
Issue: [Autocomplete] Theme data not correctly passed to the options UI
Labels: c: new feature,framework,f: material design,team-design,triaged-design

As titled. It is a common issue with widgets using overlays. This should be a similar problem to what used to happen with Tooltip and DropdownButton.
Repository: flutter
Issue: [Autocomplete] Clicking outside of the overlay should close the options UI
Labels: framework,f: material design,c: proposal,team-design,triaged-design

As titled. We should also provide a parameter to allow developers to decide if they want to this behavior or not.
Repository: godot
Issue: <Set albedo_texture()> in VisualScript : the thumbnail of the texture seems in the wrong place
Labels: discussion,topic:editor,usability,topic:visualscript

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->I haven't found any similar issues yet.

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
This happens in 3.2.2-stable and also in 3.2.3-stable version.

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Windows GTX-1070

**Issue description:**
<!-- What happened, and what was expected. -->
First, give a picture to the albedo_texture, then drag this property to the visual script editor, the preview of the texture is below the Instance port. 
![image](https://user-images.githubusercontent.com/63156187/111100379-a119d700-8582-11eb-8e5c-72e49d099519.png)
Maybe the values of this two ports are in a wrong order?

I think this will make people feel confusing, because when you want to set a new texture, you need to connect the texture to the value port. If you connect to the Instance port, it will not work correctly and report errors.

**Steps to reproduce:**

1. create a meshinstance node
2. add a spatial material to this node
3. give a picture to the albedo_texture
4. drag this property to the visual script editor
5. the texture is displayed below the Instance port
Repository: TypeScript
Issue: Add overload to `unshift` to catch calling it with zero elements
Labels: Suggestion,Awaiting More Feedback

# lib Update Request

I often mistake `unshift` for `shift`; calling `array.unshift()` with zero arguments is almost always a mistake, and I'd like it to tell me that.

```ts
interface Array<T> {
    /**
     * @deprecated You probably meant to use `.shift()`
     */
    unshift(): number;
    /**
     * Inserts new elements at the start of an array, and returns the new length of the array.
     * @param items Elements to insert at the start of the array.
     */
    unshift(...items: T[]): number
}
```

## Configuration Check

My compilation *target* is `ESNext` and my *lib* is `the default`.

## Missing / Incorrect Definition

`Array.prototype.unshift`

## Sample Code

```ts
const myArray = ["abc"];

// This should error / warn, as this is almost definitely a mistake
myArray.unshift()

// This should be ok even though the array might have zero elements
myArray.unshift(...myOtherArray)
```

## Documentation Link

Not fully relevant: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/unshift
Repository: electron
Issue: [Feature Request]: Add flag for creating window in maximized state
Labels: enhancement :sparkles:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

Currently, a maximized window can be created using this code:

```javascript
const createWindow = () => {
	const mainWindow = new BrowserWindow();
	mainWindow.maximize();
};
```

This method has a disadvantage: The window is first created and then maximized, which is ugly because it produces rendering artifacts, and the user can also see the screen before it's maximized.

### Proposed Solution

I think it'd be nice to have a flag that specifies that the window should be created in a maximized state.

e.g.
```javascript
const createWindow = () => {
	const mainWindow = new BrowserWindow({
		maximized: true
	});
}
```

Chrome seems to already support something like this, by passing the `--start-maximized` flag to it when launching.

### Alternatives Considered

None

### Additional Information

None
Repository: ant-design
Issue: Too slow rendering right after uploading files selection
Labels: Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-vcjj3?file=/index.js)

### Steps to reproduce
Upload 100 photos, each should have >= 5MB size

### What is expected?
Upload component immediately displays new 100 picture cards (div.ant-upload-list-picture-card-container) with progress set to zero.

### What is actually happening?
No picture cards displayed. Browser crashes.

| Environment | Info |
|---|---|
| antd | 4.13.1 |
| React | ^16.14.0 |
| System | macOS Big Sur 11.2.3 |
| Browser | Google Chrome 89.0.4389.90 (x86_64) |

---
Default previewFile implementation uses heavy window.URL.createObjectURL method.
For huge uploading photos amount with onProgress customRequest usage it also crashes browser.

I guess it would be good to:
- minimize the usage amount
- release URL object memory inside img.onload handler ( window.URL.revokeObjectURL(img.src) )


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: CDS and SpeechExec
Labels: Product-FancyZones,Area-App Compat

<!--
**Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**.
Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.
-->

## ℹ Computer information

- PowerToys version: v0.33.1
- PowerToy Utility: FancyZones
- Running PowerToys as Admin: Yes
- Windows build number: [run "winver"] 20H2 19042.867

## 📝 Provide detailed reproduction steps (if any)

1. Copernic Desktop Search does not want to fit in a custumized window.

![image](https://user-images.githubusercontent.com/80679920/111136023-93158780-857d-11eb-99aa-d2daa2a737f5.png)

### ✔️ Expected result

_What is the expected result of the above steps?_ 

Adjust to the size of the window

### ❌ Actual result

_What is the actual result of the above steps?_

CDS takes 1/1, 1/2 or 1/4 of the screen but never the size of Fancy Zones

## 📷 Screenshots

_Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form_

![image](https://user-images.githubusercontent.com/80679920/111137308-ea682780-857e-11eb-937a-b5d5d7265d75.png)

2. Philips SpeechExec Pro Dictate popups never opens in his custumized window. Only on top of all other customized windows.

![image](https://user-images.githubusercontent.com/80679920/111136984-952c1600-857e-11eb-851b-526cd28d4a69.png)

### ✔️ Expected result

_What is the expected result of the above steps?_ 

Open in his window

### ❌ Actual result

_What is the actual result of the above steps?_

Opens on top and in the middle of all windows

## 📷 Screenshots

_Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form_

Before 

![image](https://user-images.githubusercontent.com/80679920/111137478-200d1080-857f-11eb-9738-16eb4aba1dea.png)

After opening popup

![image](https://user-images.githubusercontent.com/80679920/111137410-0b307d00-857f-11eb-9c8e-897f3399a944.png)
Repository: flutter
Issue: PageView: Add parameter to specify marging between pages
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

Opening this ticket as requested in https://github.com/flutter/flutter/issues/38739#issuecomment-798976064

PageView should allow specifying a margin size for separating pages as seen in apps like Google Photos: [example](https://user-images.githubusercontent.com/1006207/111137042-a6752280-857e-11eb-897d-23883a8f4577.png).

Further examples are shown in https://github.com/flutter/flutter/issues/38739#issue-481861745
The solution proposed in that ticket of using `viewportFraction` doesn't allow fine control of the margin between pages (it will be relative to the width of the parent widget) and seems to break the `initialPage` parameter.

Ideally we would have a simple `double pageMargin` parameter that allows specifying the exact spacing between pages.

<details>
<summary>Code sample</summary>

``` dart
import 'package:flutter/material.dart';

void main() {
  runApp(
    MaterialApp(
      home: PageView(
        children: [
          Container(color: Colors.red),
          Container(color: Colors.green),
          Container(color: Colors.blue),
        ],
      ),
    ),
  );
}
```
</details>

<details>
<summary>Flutter doctor</summary>

[✓] Flutter (Channel master, 2.1.0-11.0.pre.145, on Linux, locale en_US.UTF-8)
    • Flutter version 2.1.0-11.0.pre.145 at /home/cachapa/flutter
    • Framework revision a0ba646408 (9 days ago), 2021-03-05 22:09:03 -0500
    • Engine revision f751d04fa0
    • Dart version 2.13.0 (build 2.13.0-107.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /home/cachapa/Android/Sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /usr/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_282-8u282-b08-0ubuntu1~20.10-b08)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • Ubuntu clang version 11.0.0-2
    • cmake version 3.16.3
    • ninja version 1.10.0
    • pkg-config version 0.29.2

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).

[✓] IntelliJ IDEA Community Edition (version 2020.3)
    • IntelliJ at /snap/intellij-idea-community/286
    • Flutter plugin version 53.1.5
    • Dart plugin version 203.7759

[✓] Connected device (3 available)
    • Pixel 5 (mobile) • 08081FDD4001PZ • android-arm64  • Android 11 (API 30)
    • Linux (desktop)  • linux          • linux-x64      • Linux
    • Chrome (web)     • chrome         • web-javascript • Google Chrome 89.0.4389.82

! Doctor found issues in 1 category.
</details>
Repository: godot
Issue: Error (!is_inside_tree) when modifying an instanced CPUParticleSystem scene via the inspector
Labels: bug,topic:3d

**Godot version:**
3.2.3 and latest 3.2.4rc5

**OS/device including version:**
Happens on Windows and Linux

**Issue description:**
If i modify an instanced scene consisting of only a CPUParticleSystem as root in the inspector i get this error in the console (particle system renders correctly though):

```
E 0:00:00.124   get_global_transform: Condition "!is_inside_tree()" is true. Returned: Transform()
  <C++ Source>  scene/3d/spatial.cpp:265 @ get_global_transform()

```
This happens only when the particle system uses global coordinates. As a workaround i currently modify the particle system in an attached script in the `_ready()` function, so i can be sure the node has been added to the scene already.

**Steps to reproduce:**
1) Create a CPUParticleSystem (`one shot` -> on, `Local coords` -> off) and save it as scene
2) In your main scene add the particle system scene and disable the `one shot` property. Also set `emitting` to true.
3) Start the main scene and observe the error in the logs
4) If you make the particle system scene local or enable `Local coords` the error is gone

**Minimal reproduction project:**
[NotInTreeBug.zip](https://github.com/godotengine/godot/files/6140753/NotInTreeBug.zip)
Repository: TypeScript
Issue: tsconfig.json extends field node-style resolution broken
Labels: Docs

# Bug Report

The [docs](https://www.typescriptlang.org/tsconfig#extends) say (emphasis mine):

> The value of extends is a string which contains a path to another configuration file to inherit from. *The path may use Node.js style resolution.*

This worked up until recently but is currently broken.  I can't pin down a specific version where it stopped working as I guess the code that loads the config may be from a dependency of typescript that is shared across different versions.

We've got a module that contains org-wide tsconfig that we want our projects to extend - they could be regular modules, monorepo packages, etc.

Those projects can and do get pulled in as github urls (or https://gitpkg.now.sh/ urls for monorepo packages) for other modules as dependencies during PRs.  Those projects are typically written in js but generate types from jsdoc comments using the npm `prepare` script for the current module to use, which now fails as it can't resolve the `extends` path.

You can't always predict which `node_modules` folder will contain the relevant dependency, so doing Node.js style resolution (e.g. stepping up through directories) is essential for our use-case.

### 🔎 Search Terms

- tsconfig extending npm package
- tsconfig extend node_modules
- tsconfig node_modules
- tsconfig extend resolve

### 🕗 Version & Regression Information

Not sure, it was working before Christmas, now it does not.

### 🙁 Actual behavior

Typescript does not resolve the `extends` path using Node.js style resolution.

### 🙂 Expected behavior

Typescript should resolve the `extends` path using Node.js style resolution.


References:

https://github.com/microsoft/TypeScript/issues/18865
https://github.com/microsoft/TypeScript/issues/30701