• Version: v10.x
• Platform: all
• Subsystem: repl

What steps will reproduce the bug?

$ node
> function foo() {
... let n = 10n;
Thrown:
let n = 10n;
           ^

SyntaxError: Unexpected end of input
>

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

Reproduces all the time.

What is the expected behavior?

Should not cause an

So getAllowedLocations is mentioned in the Atom flight manual, but it's not mentioned elsewhere in the docs. I thought I could implement just getDefaultLocation without having to also implement getAllowedLocations, but I get the following in the developer tools:

`C:\Use

❌ to the ☕ script! ES6 is cleaner, more modern, and has a much more reliable linter—plus, people know how to read it—so we want to convert everything in the codebase. Most of the code is already there, but there are still specs written in Coffee.

When opening Alacritty with --class option it changes the window instance instead the class.
For example, if I do alacritty --class foo and I check the window properties I got:

Instance: foo
Class: Alacritty
Title: Alacritty

--title option is working as expected, although.

Infos

OS: Funtoo Linux
Window Manager: dwm
Alacritty: alacritty 0.5.0-dev (03bce99)

Issue details

While in a LibGDX environment if you press down a key and then switch to any window outside of LibGDX's scope and release that key, the LibGDX environment does not detect that release event.

Upon re-entry to the LibGDX environment, there should probably be some re-polling evaluation of the keys LibGDX thinks are pressed keys to determine if they are still pressed or not.

Versions

• Python: 3.6.3
• OS: linux
• Kivy: master
• Kivy installation method: git clone && pip install --editable in virtualenv

Description

when BorderImage's display_size option is used, it overrides the auto_scale parameter, simply because it first computes the value auto_scale would need, and then look if there is a dispaly_border setting, and overrides the values if

Bug report

Describe the bug

Here is a clear and concise description of what the problem is:

Hello, There is a bug on Kodi (tested on Windows Store version)
Using Alt+Space I can move Kodi on full-screen mode

Expected Behavior

Here is a clear and concise description of what was expected to happen:

Actual Behavior

Possible Fix

To Reproduce

Steps to reproduce t

There are only a few basic syscall tests for write(2) and pwrite(2). Here is an incomplete list of missing tests:

• bad buffer states (EFAULT).
• bad fds (wrong permission, wrong type of file, EBADF).
• check offset is incremented.
• check for EOF.
• writing to pipes, symlinks, special files.

There were some problems in the past regarding std::filesystem, MSVC 2017 and 2019 added support so we would be able to update our sources correspondingly.

std::filesystem for VS2017