WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Not a major bug, but can be confusing.

Steps to Reproduce

Open https://codelabs.developers.google.com/codelabs/flutter/#4

Scroll down until you see two code listings. The first one starts with the comment:

// Modify the ChatScreen class definition to extend StatefulWidget.

The second one starts with the comment:

// Add the ChatScreenState class definition in main.dart.

The confusing part is that, other than two comments, these code listings are exactly the same.

Issue 2:
From an email: "Trying to create an emulator with Android Studio. Your instructions say to use Tools > Android > AVD Manager. But, there is no Android sub-menu in the Tools menu. (Actually, the only way I could get a Tools menu was by creating a vestigial Android project.) The Tools sub-menu items are, 1) Tasks & Contexts, 2) New Scratch File..., 3) IDE Scripting Console and 4) Create Command-line Launcher...."

(I haven't confirmed this yet, but wanted to track it)
Issue 1:
I want to run a background service that can read certain events, process and possibly record the data, and if appropriate create a notification which will launch the main app if pressed. Some examples of the events would be: new Bluetooth device in range, incoming data on a socket, incoming data from a USB device, SMS received, GPS location changed, Bluetooth device connection attempt, a certain physical button is pressed, accelerometer data exceeds a specified value, if the main app is terminated, and a lot of other things I'm not thinking of.

Can someone make a comprehensive plugin (with a free or open source license) for this that works on iOS and Android? I know that iOS is more restrictive about background execution, but the plugin could include events associated with these and their Android equivalents.

**edit: I'm aware of the new background execution feature. The problem is it's only for plugin developers, and requires a lot of platform specific code. I think there needs to be a higher level, platform independent plugin that is accessible to normal developers, not just plugin developers with experience in Android and iOS programming.

See #3671 (comment) and the responses.**

Issue 2:
Since we have background execution of dart code now, would it be possible to receive data notifications while the app is terminated?
Issue 1:
Environment

Windows build number: Windows 10 1903

Windows Terminal version (if applicable): 0.2.1715.0

Steps to reproduce

you can only drag the window when clicking on the window title that is actually colored in Windows 10 color style ([1]marked green)

click on the window title ([1]marked red) you cannot move the window

![windows terminal drag window]

![1]

(https://user-images.githubusercontent.com/45657752/59983328-9258f700-961e-11e9-9522-357b93c911b0.png)

Expected behavior

I expect that left mouse click and hold on the complete window title should allow dragging of the Windows Terminal window.

Actual behavior

The left space this is reserved ([1]marked red) for new tabs or existing tabs (black) cannot be used to move the window

Issue 2:
Environment

Windows 10.0.18362.175
Terminal version 0.2.1715.0

Steps to reproduce

Just run the application. Happens to all instances.

Expected behavior

Can move the window! :)

Actual behavior

Every window is locked to it's starting position. Can be resized however. Not sure what else I can provide, I have a triple screen setup on a 1080Ti, configuration 1920x1920 - 3440x1400 - 1920x1920 (the square monitors are the unusual Eizo ones). I'm not running any special display tools other than the LG screen split which is set to off. Setting it on (enables window snapping to various configurations to manage the desktop) other windows start snapping when moved, except terminal which still can't be moved.
Issue 1:
Please add a titled panel component to Twitter Bootstrap.

Many off-the-shelf themes have these and I find they're useful.

To see a sample, go the following link and go to the bottom.

http://themes.vivantdesigns.com/xtremeadmin/forms.html

The "panel widget" is basically a bootstrap well. What I'm asking for is the "widget".

Issue 2:
Would you consider adding a component that is not a well, thumbnail, or modal, but something in between? Especially with Modal dropping the .hide class in v3 I see a great need. For example, take a look here on GitHub at the ReadMe box. It has similarities to a modal in that it has a heading and sits "above" the page a bit. Another example is the "example" boxes here in the v2 docs.

Of course, thumbnail is inappropriate, and well loses importance to some degree. The generic term "widget" is the best name I can come up with, but there's probably a better term without quite the stigma.

I'd be more than happy to add a pull request if that helps.

Thanks for all the hard work!
Issue 1:
Prior to yesterday's update, VS code coloring in XML files (specifically web.config) had more variation between various tags and values than the screenshot included.

as a comparison, the syntax highlighting in XML under a light themed notepad++ window

Is a lot closer to the level of highlighting we used to have in XML files. DEFAULT TAGS were one color, attributes another, values a third.

Perhaps something broke in XML language parsing?

Issue 2:
Issue 1:
I'm submitting a ...

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

Component's and directive's initialization occur in declaration order. This can lead to the loss of a directives specific host binding such as @HostBinding('class.specific') classSpecific = true;, when a component "blanket" binds the same parent attribute such as @HostBinding('class') classList = '';.

Component overwrites directive specified attributes

@NgModule({
declarations: [
MyDirective,
MyComponent,
],
})

Component writes blanket attributes and directive extends these attributes

@NgModule({
declarations: [
MyComponent,
MyDirective,
],
})

Expected behavior

In my opinion directives should be treated as an extensions of a component's functionallity and therefore initialize after said component. This should also take into account modules and their declaration/import order should not change behavior.

Minimal reproduction of the problem with instructions

https://plnkr.co/edit/iOF42haUAv379suApgS4?p=preview

What is the motivation / use case for changing the behavior?

Consistency and by extension stability. In our use-case we recieve a list of classes from the back-end (or another source) which we want to bind to the component host container's class list to avoid uneccessary nesting. In addition we also want to have directives that specifically affect the component without being overwritten.

Angular version: 4.0.1

Browser: all

Language: all

Issue 2:
Say a user wants to add margin around a component:

<cool-thing class="extra-margin"> ...

But the component itself has need to set a dynamic CSS class to the host element:

@Component({
...
host: { '[class]': 'myCustomStyle' }
})
class CoolThing {
myCustomStyle: string = figureOutWhichClassToUse();
}

Doing this in the component will completely overwrite the class property, wiping away the user's classes.

In other situations, NgClass serves this purpose, but a component cannot apply a directive to its host element. Using the [class.whatever] syntax also doesn't solve this, as the whatever is the variable part.

Proposal

Each component can, conceptually, have two distinct class lists: one that is from the user and one that comes from the component itself. These could be resolved independently with Angular rendering the union. Any time the user uses ngClass or the [class.whatever] syntax, it should override whatever is set to "class".

cc @mhevery
Issue 1:
If you hover over an <a> with a tooltip within a .btn-group the border-radius will be overwritten.

Watch the right side of the second button when hovering it:

http://jsfiddle.net/gpyPX/

Issue 2:
http://jsfiddle.net/JEBdk/5/

tooltip or popover on btn-group. the btn-group is not display correctly!

the last btn have not round corners and between the btn's is a space.

my suggestion, by generating the tip or popover on the end of document .
Issue 1:
Trying out styled-jsx-postcss with the plugin postcss-cssnext - when I nest, I get an erro: node.parent.after is not a function

I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The nested css should work

Current Behavior

When I save I get this error:

Error in /home/nick/dev/Projects/FreeAdvancedMarketing/pages/index.js?entry

Module build failed: TypeError: /home/nick/dev/Projects/FreeAdvancedMarketing/pages/index.js?entry: node.parent.after is not a function

at module.exports (/home/nick/dev/Projects/FreeAdvancedMarketing/node_modules/postcss-nesting/lib/transform-nesting-rule.js:18:29)

at walk (/home/nick/dev/Projects/FreeAdvancedMarketing/node_modules/postcss-nesting/index.js:25:3)

at walk (/home/nick/dev/Projects/FreeAdvancedMarketing/node_modules/postcss-nesting/index.js:33:4)

at walk (/home/nick/dev/Projects/FreeAdvancedMarketing/node_modules/postcss-nesting/index.js:33:4)

at LazyResult.run (/home/nick/dev/Projects/FreeAdvancedMarketing/node_modules/styled-jsx-postcss/node_modules/postcss/lib/lazy-result.es6:321:20)

at LazyResult.asyncTick (/home/nick/dev/Projects/FreeAdvancedMarketing/node_modules/styled-jsx-postcss/node_modules/postcss/lib/lazy-result.es6:248:32)

at LazyResult.asyncTick (/home/nick/dev/Projects/FreeAdvancedMarketing/node_modules/styled-jsx-postcss/node_modules/postcss/lib/lazy-result.es6:260:22)

at LazyResult.asyncTick (/home/nick/dev/Projects/FreeAdvancedMarketing/node_modules/styled-jsx-postcss/node_modules/postcss/lib/lazy-result.es6:260:22)

at LazyResult.asyncTick (/home/nick/dev/Projects/FreeAdvancedMarketing/node_modules/styled-jsx-postcss/node_modules/postcss/lib/lazy-result.es6:260:22)

at LazyResult.asyncTick (/home/nick/dev/Projects/FreeAdvancedMarketing/node_modules/styled-jsx-postcss/node_modules/postcss/lib/lazy-result.es6:260:22)

Steps to Reproduce (for bugs)

https://github.com/Nick-vr/FreeAdvancedMarketing

clone

yarn

yarn dev

Context

I am trying to nest css with styled-jsx-postcss -> cssnext

Your Environment

Tech
Version

next
beta

node
v7.4.0

OS
Linux Mint

browser
Chrome

etc

Issue 2:
Currently attempting to deploy a next.js to production with dynamic imports (without using next/dynamic since we're importing a non-react library), and running into issues with 404s on the dynamically imported chunks.

The built folder structure looks like:

.next
- app.js
- BUILD_ID
- 0-cd29260af35981b4adfc.js
- ...etc

While loading the page, a javascript file at /_next/webpack/0-cd29260af35981b4adfc.js is loaded, pointing to the file 0-cd29260af35981b4adfc.js to be in the .next/chunks directory, which it's not. Moving that file manually to the chunks folder fixes it. Currently, the request 404s.

[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The request for the dynamically loaded javascript file should not 404.

Current Behavior

The request for the dynamically loaded javascript 404s.

Your Environment

Tech
Version

next
5.0.0

node
8.9.4

OS
MacOs

browser
Chrome

etc
Issue 1:
in VS2015 (beta and release) when editing a string, if I type an open parenthesis the intellisense function signature pop-up opens.

e.g.

console.log("hello");

editing in "hello(" causes log([message: any) to be displayed.

Issue 2:
Hi,

VS: 2013 Update 4 RC

TS: 1.3

Also occurs with ( and <
Issue 1:
I'm looking into customizing an installation of Bootstrap 2 for my color scheme, and the names are virtually worthless. My scheme is light-on-dark, and the default text color variable name is "gray". I can set this to white and it will work, but it's completely counter-intuitive.

Variable names shouldn't be names of colors, unless you're defining those colors. For example, defining your particular shade of gray in "gray" so you can use it is fine, but then doing "color: @gray" is bad design.

I understand that it's rather a big change, but it would be much better if it were something like:

@gray: #333;
@textColor: @gray;

body { color: @textColor; }

This way is used in most places, but there are some places that use the color-named variables directly. Ideally, this shouldn't happen anywhere outside variables.less.

Issue 2:
border-radius and box-shadow are already supported by browsers without prefixes.

Why do we need to duplicate these styles with -webkit- and -moz- vendor prefixes?
Issue 1:
I have a package of reusable components that use styled-jsx that I import into my Next.js app (version 2.4.0).

The styles of the components in the package do not get rendered on the server and results in a flash of unstyled content on page load.

Is there an approach that's taken for cases like this?

My only hack has been to import the styled-jsx files separately into my app and add the style to the render using <styled-jsx>{style}</style> but that results in duplicate styles when the component's styles get attributed by the client.

Any help would be greatly appreciated

Issue 2:
A solution for CSS-file-based styling and importing non-js files from webpack in server side rendering. I have made a package that allows us to import non-js files directly in server side code, without prebundling, and works just like babel-register. I just want to share it to improve other devs experience with SSR:

https://github.com/namnm/webpack-register

I also would like to create a PR and include a link in the section that warns users not to use webpack loaders to support for other non-js files.

Hope this can help somewhere.

I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

We can easily require non-js files from webpack bundle, like sass .scss, image .png .jpg, ... in our server rendering code.

Current Behavior

Right now, we are not recommended to use CSS-file-based styling and importing non-js from webpack in SSR, due to a bunch of practical issues...

Steps to Reproduce (for bugs)

Context

Your Environment

Tech
Version

next

node

OS

browser

etc
Issue 1:
This code compiles:

#![feature(associated_types)]

pub trait A {
type B;
fn x() -> Option<Self::B>;
}

pub fn x<T: A>() -> Option< <T as A>::B> {
A::x()
}

fn main() { }

… but remove the space from < < on the pub fn x, and it fails to parse:

<anon>:8:27: 8:29 error: expected one of `(`, `::`, or `{`, found `<<`
<anon>:8 pub fn x<T: A>() -> Option<<T as A>::B> {
^~

Issue 2:
STR

#![feature(associated_types)]

trait Trait {
type Type;

// OK
fn method() -> <Self as Trait>::Type;
// Can't parse
fn method() -> Box<<Self as Trait>::Type>;
}

fn main() {}

Output

ai.rs:9:23: 9:25 error: expected `;` or `{`, found `<<`
ai.rs:9 fn method() -> Box<<Self as Trait>::Type>;

Version

rustc 0.12.0-pre (9508faa22 2014-09-17 23:45:36 +0000)

cc @pcwalton
Issue 1:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

Electron Version:

10.1.0

Operating System:

Windows 10 (19041)

Last Known Working Electron version:

N/A

Expected Behavior

minimize() and maximize() to minimize and maximize the window respectively.

Actual Behavior

nothing changed/happened.

To Reproduce

remote.BrowserWindow.getFocusedWindow().minimize()

https://gist.github.com/IncinerateZ/9aae814bf6d3e97c474be6629d9400e3

copy paste gist files to electron fiddle.

Screenshots

Additional Information

strangely enough, close() does work.

Issue 2:
Electron version: 1.7.9

Operating system: 10.12.6

Computer: Macbook Air

I am currently working on the implementation of the Web Bluetooth selection dialog. The above event returns a huge number of duplicates. I have seen everything between 17 and 107 entries; they seem to grow when I reload the JS code and re-open the dialog.

When I remove all address duplicates, I end up with a few MAC addresses that seem to be auto-generated, because there is no vendor ID available for these addresses. This is the list of devices reported by my dialog:

"CA:14:FF:2A:37:F4" InO-Bot

"74:F9:BB:C1:60:BE" SBrick

"1F:46:52:72:D6:07" Betty

"48:F6:9B:C4:33:11" InO-Bot

"34:81:F4:15:07:D4" InO-Bot

"8C:DE:52:9A:DF:FC" Betty

Both Betty and InO-Bot have invalid (?) MAC addresses, not assigned to any vendor ID. The correct addresses are 34:81... and 8C:DE...

SBrick is a BLE-only device that has never been paired via the System Preferences. Betty and InO-Bot have been paired. After I removed the devices from the System Preferences Bluetooth dialog, I got a third entry for InO-Bot; before, I got two for both.

Both Betty and InO-Bot support BLE and the old SPP protocol. I suspect that Mac OS creates serial ports and therefore generates the additional MAC addresses.

I've attached an XML dump of my com.apple.Bluetooth system preferences.

com.apple.Bluetooth.txt

Expected behavior

List three BT devices

Actual behavior

List of devices with several duplicates and apparently generated MAC addresses
Issue 1:
Bug Report

Environment

Babel version(s): v7.2.2

Node/npm version: 9.6.0

OS

How you are using Babel: loader

Issue 2:
Bug Report

Current Behavior

I'm building a library that need to be able to work with JSX with namespaces. According to Babel documentation this should work by setting the throwIfNamespace option. However this does not seem to work.

Input Code

https://github.com/TheKnarf/babel-namespace-test

Expected behavior/code

Running babel src/index.js should transpile the test code without any errors.

Babel Configuration (.babelrc, package.json, cli command)

{
presets: ['@babel/preset-react'],
plugins: [
['@babel/transform-react-jsx', {
'pragma': 'dom',
'throwIfNamespace': false
}]
]
}

Environment

Babel version(s): 7.1.2 (@babel/core 7.1.2)

Node/npm version: v10.12.0

OS: macOS 10.13.6

How you are using Babel: cli

Additional context/Screenshots
Issue 1:
Hello,

PowerToys Run was working.

I didn’t use it because it has not yet entered my usual reflexes.

Now that I want to use it actively, it doesn't work.

I type Alt + Space and it pulls down the File menu of the active window.

I tried with other keyboard shortcuts, but it doesn't work.

Do you know this problem?

Do you know the solution?

Thank you for your attention.

Issue 2:
Environment

Windows build number: [run "ver" at a command prompt]
PowerToys version: 0.19
PowerToy module for which you are reporting the bug (if applicable): PT Run

Steps to reproduce

Remap key from alt-space to win-space

execute shortcut multiple times

Expected behavior

don't have start menu false positive executions

Actual behavior

Lots of start menu executions
Issue 1:
Hi, I've been using Electron for a few months, but autoupdate started returning an error after 0.33.4. I've been using the same endpoint hosted by Github.

Error message

2015-11-18 22:31:12.249 Electron[71075:3518387] NSURLSession/NSURLConnection
HTTP load failed (kCFStreamErrorDomainSSL, -9802)
[DeskDrive] Uncaught exception: Error: An SSL error has occurred and a secure
connection to the server cannot be made.: (null) Error: An SSL error has occurred
and a secure connection to the server cannot be made.: (null)
at Error (native)
^C

(DeskDrive is the name of the app I'm working on.)

Repro Code

const autoUpdater = require('auto-updater');
autoUpdater.setFeedURL('https://raw.githubusercontent.com/dylang/DeskDrive-releases/master/auto_updater.json');
autoUpdater.checkForUpdates();

Note: App must be built and signed for autoUpdater to show this error.

Versions

Was working in 0.33.4, but has been failing in every build up to 0.35

Testing in OS X 11.1 (El Capitan)

Tested with and without firewall/proxy/etc.

Issue 2:
Minimal repro here: https://gist.github.com/mkscrg/d56227f2b6a3a430a17d

auto-updater fails immediately after the update-available with this error:

2015-11-14 18:45:14.807 Electron[2750:121917] NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9802)
auto-updater error: An SSL error has occurred and a secure connection to the server cannot be made.: (null)

In my limited tests, I could hit this issue with Electron >= 0.34.2 && OS X >= 10.11. Dropping to 0.34.1 and/or 10.10 seemed to avoid it.
Issue 1:
Line 19 | react/docs/tutorial/tutorial.md

Links to: http://codepen.io/ericnakagawa/debug/ALxakj/auth

Issue 2:
Do you want to request a feature or report a bug?

report a bug

What is the current behavior?

broken link in the first section of https://github.com/facebook/react/blob/master/docs/tutorial/tutorial.md

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/reactjs/69z2wepo/).

N/A

What is the expected behavior?

Link should go to a working version of tic-tac-toe on codepen

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

N/A
Issue 1:
Abstract class should not be required to implement all the properties/methods of the interfaces it implements. So the following should be legal:

interface A {
p;
m();
}

abstract class B implements A {
}

class C extends B {
get p() {...};
set p(v) {...};
m() {...}
}

But currently it gives:

Error:(2, 16) TS2420: Class 'B' incorrectly implements interface 'A'. Property 'p' is missing in type 'B'.

This issue is related to proposal #3578.

Issue 2:
Some properties in JavaScript are actually read-only, i.e. writes to them either fail silently or cause an exception. These should be modelable in TypeScript.

Previous attempts to design this have run into problems. A brief exploration:

interface Point {
x: number;
y: number;
}
interface ImmutablePoint {
readonly x: number;
readonly y: number;
}
var pt: ImmutablePoint = { x: 4, y: 5 }; // OK, can convert mutable to non-mutable
pt.x = 5; // Error, 'pt.x' is not a valid target of assignment

var pt2: Point = pt; // Error, cannot convert readonly 'x' to mutable 'x'

// Possibly bad behavior
var pt3: Point = { x: 1, y: 1 };
var pt4: ImmutablePoint = pt3; // OK
pt3.x = 5; // pt4.x is also changed?

// Really bad behavior
/** This function was written in TypeScript 1.0 **/
function magnitudeSquared(v: { x: number; y: number }) {
return v.x * v.x + v.y * v.y;
}
// Now try to use it with ImmutablePoint
console.log(magnitudeSquared(pt)); // Error, cannot use readonly object in non-readonly call

Possible solutions?

Allow bivariance of mutability: this is very unsound

Something else clever? C++ did not do well with const contamination