WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Summary of the new feature/enhancement

Right now, you can either remap key to a key or shortcut to a shortcut.

I'd like a way to remap shortcut to a key. Why?

Well, I have Surface Keyboard Bluetooth, which special keys. Some are usual ones like Next, Previous, Play/Pause. But some are Windows specific (like Settings or Connect external display).

I don't use the latter ones and they overlap with Fxx keys that I actually use often and have to use Fn key to access them.

So I'd like to remap them back to Fxx. Thing is, Windows does not see them as a single key, but as a strange shortcut (for example Settings are Win Left + F21). I'd like to remap this back to F12 (so I don't have to use Fn), but right now I can't.

Issue 2:
crutkas update 2020.06.17:

you can get this via WinGet

winget install PowerToys

crutkas update 2021.09.17:

You can install PowerToys in the Microsoft Store via https://aka.ms/getPowerToys

Summary of the new feature/enhancement

The Microsoft Store is a convenient way to install software (like Python 3, WSL distros, Windows Terminal Preview, Spotify, and others) and keep them up to date automatically. I feel bringing PowerToys to the Store would be useful for these reasons.

It's already available via Chocolatey, why not the Store as well?

Thank you.7
Issue 1:
Environment

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

Steps to reproduce

unable to create a fancyzone that spans mutltiple monitors

nor can I create a zone on one monitor and another on the second.

can only create on primary monitor

Expected behavior

Actual behavior

Screenshots

Issue 2:
Support zones which span several monitors

Could you please add the capability to define zones across several monitors? For instance I would like to define one single zone spanning two monitors (this is my current setup with ultramon for instance).

Thanks very much
Issue 1:
Chris Beams opened SPR-6184 and commented

Currently, JavaConfig integrates with the TestContext framework via its ContextLoader implementation, JavaConfigContextLoader:

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations="com.bank.TransferAppConfig",
loader=JavaConfigContextLoader.class)
public class TransferServiceTests {
// @Test methods ...
}

This integration works well enough but is not refactoring-friendly due to the requirement that @ContextConfiguration imposes that locations must be a String[]. It forces the fully-qualified class name to be expressed as a string, when it would clearly be superior to be able to pass it around by Class literal.

Implementing this change would require a change to core, either by adding an attribute to @ContextConfiguration that takes a Class[] (not likely), or otherwise devising a way of proving a customized annotation (e.g., @JavaConfigContextConfiguration).

Affects: 3.0 GA

Issue Links:

#13033 Introduce SmartContextLoader SPI ("is depended on by")

#12888 Document TestContext support for @Configuration classes in the reference manual ("is depended on by")

#12425 SpringJUnit4ClassRunner is not compatible with java context configuration ("is duplicated by")

#11233 Annotation configuration based TestContext ("is duplicated by")

SJC-272 JavaConfigContextLoader support with Spring 3.0 ("is duplicated by")

#13042 AnnotationConfigContextLoader should not restrict the name of default configuration classes to ContextConfiguration

#12615 TestContext framework should support declarative configuration of bean definition profiles

#12592 Support for dependency injection and initialization of test instances using classpath scanning

#10353 Provide dedicated ApplicationContext implementations for use with (JavaConfig) @Configuration classes

#12078 Support Java-Based Application Configuration

37 votes, 30 watchers

Issue 2:
Cédrik LIME opened SPR-7743 and commented

This patch exposes the properties of HttpURLConnection within SimpleClientHttpRequestFactory such as connectTimeout and readTimeout.

There will therefore be no loss of available functionality in using Spring's ClientHttpRequestFactory in place of a HttpURLConnection.

Affects: 3.0.5

Attachments:

SimpleClientHttpRequestFactory.patch (3.82 kB)

Issue Links:

#12815 Introduce FeatureSpecification for PropertyOverrideBeanDefinitionParser (context:property-override) ("duplicates")
Issue 1:
There's a small (but obvious) sizing error when .btn-lg and .input-lg are used in an input group. See below:

Relevant CSS:

.btn-lg {
// line-height: ensure even-numbered height of button next to large input
.button-size(@padding-large-vertical; @padding-large-horizontal; @font-size-large; @line-height-large; @border-radius-large);
}

link

.input-lg {
.input-size(@input-height-large; @padding-large-vertical; @padding-large-horizontal; @font-size-large; @line-height-large; @border-radius-large);
}

link

Issue 2:
Browser: Chrome 33

JSBin: http://jsbin.com/iBIPEKA/1/
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

When opening a Menu and creating a react portal, the portal that's created should reference the Node.ownerDocument of the anchorEl or something similar, to support rendering Material-UI components in a new window (such as through a library like react-popout)

Current Behavior

The portal that is created always uses the global document object to append a portal div to. See: https://github.com/callemall/material-ui/blob/08fae8c2fcd741c01cabbee38305d5ef109acfd5/src/internal/Portal.js#L45-L55

Steps to Reproduce (for bugs)

A simple example can be seen here: https://codesandbox.io/s/v09qklqkj7. You can ignore the lack of styling and what not in the popout window, just trying to show the portal issue.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.21

React
16

browser
All

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

Possibly related issue: #8353

Expected Behavior

Make change to file

Save file

React hot loader renders change without erorrs and keeps state

Current Behavior

Make change to file

Save file

React hot loader throws error "React Hot Loader: this component is not accepted by Hot Loader."

Page reloads (no saved state)

Renders change

Steps to Reproduce (for bugs)

Use https://github.com/Glavin001/react-hot-ts/tree/material-ui-demo to reproduce with the above steps.

Context

I loose usage of React Hot Loader when adding Material UI to my project.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.18

React
16.0.0

React DOM
16.0.0
Issue 1:
It appears that export assignments (export = x) when compiling amd modules for either es5 or es6 output to a single file, is broken?

For example, this file:

import { Scribe } from "../../../scribe"

/**
* Sets the default content of the scribe so that each carriage return creates
* a P.
*/

export = function(scribe: Scribe) {
// The content might have already been set, in which case we don't want
// to apply.
if (scribe.getHTML().trim() === '') {
/**
* We have to begin with the following HTML, because otherwise some
* browsers(?) will position the caret outside of the P when the scribe is
* focused.
*/
scribe.setContent('<p><br></p>')
}
}

Produces the following .d.ts output:

declare module "scribe/plugins/core/set-root-p-element" {
import { Scribe } from "scribe";
declare var _default: (scribe: Scribe) => void;
export = _default;
}

Which, when I attempt to include that, complains that declare is not allowed inside a declare module block. A nested declare statement is emitted for every export assignment.

Interestingly, if I change the module type to system, the compiler complains (at compile-time) about every export assignment - it's as though this was supposed to be supported for amd, but isn't really? I would expect it should be supported, as it's a very common pattern in amd modules in vanilla JS.

I'm using Typescript 1.8.10.

My tsconfig is set for es6 and amd output to a single file.

The resulting .d.ts output is here.

The full project is available here.

Why doesn't this work?

Is there a viable way to build amd modules with .d.ts headers with TS and package them as npm modules with typings?

I have been told I should use commonjs as my compile target, and then use grunt and browserify to single-file the module - but I don't understand why I should need a whole stack of tools on top of the language just to get it to work? (I also don't understand how this supposedly leads to a working .d.ts file...)

I really do not want a large, complicated build chain - I just want to compile my module to a file, emit the matching header file, run uglifyjs and be done.

Please advise? How should I proceed?

Issue 2:
window.fetch(...)

error TS2304: Cannot find name 'fetch'.
Issue 1:
As part of emulating shadow DOM, we have to implement a solution for loading CSS inside of components.

Embedding style rules directly into the component template is undesirable

Makes templates harder to read

Makes it much harder to use CSS pre-processors (sass, less)

Would lead to duplicating "common" styles

Problems

The <link> element (the normal way of loading CSS) is inert in shadow DOM.

CSS @import is generally frowned upon for performance reasons.

Opportunity

Since Angular will control how styles are actually rendered for a component (because of shadow DOM emulation), we can extend There are other ideathe process to give component authors more power.

Proposal

Angular core implements a directive to include a style file via URL. For discussion's sake, let's call this <ng-style> (it will probably end up being something like <style> or <link>, though):

<!-- fancy-button.html -->
<ng-style src="../my/style/file.css">
<button class="super-fancy">...</button>

When ng-style is used in a Component with native shadow DOM, the output <style> element is rendered inside of the shadow DOM for each component. When using emulated shadow DOM, one common<style> element is added to the document head for all component instances.

ng-style can also be used to provide component authors a means through which to apply some arbitrary transformation to the embedded style. This could look vaguely something like:

<!-- fancy-button.html -->
<ng-style src="../my/style/file.css" transform="MaterialThemeTransformer">
<button class="super-fancy">...</button>

class MaterialThemeTransformer {
transform(input: string): string {
// do some transformation
}
}

This is purposefully hand-waving a lot of details, but I just want to get the idea across. The main use-case I have in mind for this is creating style rules that are defined in terms of some theme (e.g, background-color: {{primaryColor}})

This would let people do whatever arbitrary transformation on the incoming rules, including applying sass or less on the fly (if you wanted to do that for some reason). If CSS shimming is enabled, that process would occur after any user-defined transformations. The CSS shim itself could potentially just be another transform.

Other notes

It's possible that this mechanism doesn't have to be so tightly coupled to styles, and could instead just be a part of how interceptors/transforms work for all http requests, depending on how http support looks when it's built.

Issue 2:
So having to use ngOnIinit, ngOnChange etc etc is a required changed so I think it should appear on breaking changes.

Cheers.
Issue 1:
When writing code using Typescript, too many 'this...' needs to be used.

In most places, it should be automatically inferred. Makes code look lot nicer

TypeScript Version:

1.7.5 / 1.8.0-beta / nightly (1.9.0-dev.20160217)

Code

// A self-contained demonstration of the problem follows...

Expected behavior:

Actual behavior:

Issue 2:
The need to prefix all calls to methods and variables in the class body with the this keyword makes the code harder to read and look cluttered.

Instead the TypeScript compiler could add the this keyword automatically during the compilation to JavaScript. This would make code that looks like this…

var something = this.doSomething(this.getSomething());
this.addSomething(something);

look like..

var something = doSomething(getSomething());
addSomething(something);

If I’m not mistaken it should be easy to determine if the this keyword should be prefixed or not. I know that TypeScript tries to resemble the ES6 syntax. But to me code clarity feels more important.
Issue 1:
Fresh application, made by create-react-app (4.0.3)

Launching DevServer via npm run start.

White screen, and error at

react-refresh/cjs/react-refresh-runtime.development.js

line number 465:

hook.renderers.forEach

hook.renderers is undefined.

hook object has only "_renderers" empty object property

If write this line with hook.renderers&&hook.renderers.forEach, page appears, live reload works.

React version:

17.0.2

react-refresh version:

0.8.3 / 0.10.0

Chrome version:

89.0.4389.114

Steps To Reproduce

just run dev server via "npm run start."

I can reproduce it only at my enterprice workstation.

At my home pc, this works without issue.

The current behavior

White screen

The expected behavior

Working dev server

Issue 2:
Website or app

http://bestellen-a.cito.nl

Repro steps

Just opening the console and going to Components or Profiler shows this error.

I noticed that in the console there are two warnings for contentScript.js (I am assuming this file is part of this extension):

﻿

contentScript.js:113 [Violation] 'message' handler took 210ms

contentScript.js:113 [Violation] 'message' handler took 891ms

How often does this bug happen?

Sometimes

DevTools package (automated)

react-devtools-extensions

DevTools version (automated)

4.24.0-82762bea5

Error message (automated)

Cannot add node "1" because a node with that id is already in the Store.

Error call stack (automated)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26326:41
at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24400:22)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24566:14
at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:54300:39)

Error component stack (automated)

No response

GitHub query string (automated)

https://api.github.com/search/issues?q=Cannot add node because a node with that id is already in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
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 a feature request that matches the one I want to file, without success.

Electron Version

10.3.2

What operating system are you using?

Windows

Operating System Version

Windows 10

What arch are you using?

x64

Last Known Working Electron version

None

Expected Behavior

Electron should respect to the OS's date/time format settings.

Actual Behavior

Electron only uses the date/time format for the OS's current locale.

Testcase Gist URL

No response

Rehash of #13023.

Issue 2:
Is your feature request related to a problem? Please describe.

I think Tray icons shouldn't be restricted to PNG & JPG

SVG support can provide dynamic icon generation in Tray on the fly for use cases like #13500

Describe the solution you'd like

new Tray("/path/to/svg")

Describe alternatives you've considered

Alternatives are static PNGs or JPGs for every Icon. Suppose we have 30 types of Tray Icons with 30 different colours, then with PNGs or JPGs we have to add 30 static icons but if we have SVG support, we can just have 1 icon that adapts to 30 different colors

Additional context

Related #9642 & #9661
Issue 1:
When using the following string:

query = "INSERT INTO `#{testTable}` ( d_id, job_id, created_at, updated_at, first_name, last_name, phone, zip, start_time, duration, recording ) VALUES ( #{d.id}, #{job.id}, '#{escapeIt(body.start_time)}', '#{escapeIt(body.start_time)}', '#{escapeIt(body.first_name)}', '#{escapeIt(body.last_name)}', '#{escapeIt(body.caller_id)}', '#{escapeIt(d.zip)}', '#{escapeIt(body.start_time)}', #{escapeIt(body.call_duration)}, '#{escapeIt(recording)}' )"

and selecting Coffeescript for the syntax highlighting, it thinks I have an open string somewhere in that line. When I go to the next line, my syntax highlighting is still showing green like there's a string I haven't closed. JS2Coffee and Coffeescript.org both say the code is valid, which leads me to believe this is a bug.

Issue 2:
I opened a Python file with the following line (#963):

PrintAndLog(u"SSID: " + RememberedNetwork["SSIDString"].decode("utf-8") + u" - BSSID: " + RememberedNetwork["CachedScanRecord"]["BSSID"] + u" - RSSI: " + str(RememberedNetwork["CachedScanRecord"]["RSSI"]) + u" - Last connected: " + str(RememberedNetwork["LastConnected"]) + u" - Security type: " + RememberedNetwork["SecurityType"] + u" - Geolocation: " + Geolocation, "INFO")

Which led to the following bug:

You can find this as the main file in osxauditor.py.
Issue 1:
It seems like a common problem I am seeing developers new to ES struggling with is how to fit the pieces of the query DSL together. Returning more structured feedback about what the query DSL is expecting feels like it would help.

Some examples from helping someone recently:

'filter' : {
'not' : {
'post_id' : [ 1, 2 ]
}
},

Problem here is the NOT filter should have a filter inside of it rather than a field name

If the error response could return the type of expected data at each level that would aid debugging. For example this could return:

"filter": { "not" : "error: expects a filter" } }

Another case:

'filter' : {
'and' : {
'terms' : {
'post_type' : ['post']
},
'not' : {
'terms' : {
'post_id' : [1, 2]
}
}
}
},

Error:

"filter": { "and": "error: expects an array of filter objects" } }

With more complex nesting:

'filter' : {
'and' : [
{
'terms' : {
'post_type' : ['post']
}
},
{
'not' : {
'post_id' : [1,2]
}
}
]
}

Error:

"filter": { "and": [{"terms" : "ok"}, {"not" : "error: expects a filter"} } }

Not entirely sure how feasible this is, or if there is better syntax or a more standard method for reporting such structured errors.

Issue 2:
Errors returned by the REST API are not easily human readable due to the way the data is stored in the error property.

Eg. https://gist.github.com/missinglink/e3cb9b127ae00e8c561c

You can 'prettify' the results, but it is still un-readable.

Eg. https://gist.github.com/pecke01/5956684

Note: (this specific error was caused by invalid syntax, the outer curly brackets were missing)

This issue makes it difficult for beginners to understand syntax errors and for advanced users to debug quickly when they make silly errors.

Ideally usage of ?pretty=1 would return "developer friendly" messages.

Any thoughts / suggestions? Maybe there is a tool which may help?
Issue 1:
Environment

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

Steps to reproduce

Expected behavior

Actual behavior

Screenshots

Issue 2:
Environment

Windows build number: [run "ver" at a command prompt] Microsoft Windows [Version 10.0.19041.329]
PowerToys version: v.0.19.1
PowerToy module for which you are reporting the bug (if applicable): Shortcut Guide

Steps to reproduce

I have no Idea it suddenly stopped working now for days. even as Administrator it doesn´t work anymore

Expected behavior

The Shortcut Guide working

Actual behavior

The Shortcut Guide not working

I have no clue. even If I change the duration until it gets shown doesn´t matter

Screenshots
Issue 1:
Environment

Windows Terminal (Preview)

Version: 0.5.2681.0

PowerShell

Platform ServicePack Version VersionString

Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0

Steps to reproduce

Scenario 1 (via RDP)

From Windows Terminal Windows PowerShell shell running in a Windows Remote Desktop (RDP) Session:

clear

ls c:\ -recurse

Use 2 finger scroll gesture on touchpad -> Vertical scrolling works

Scenario 2 (via native Windows Desktop, i.e. no RDP session)

From Windows Terminal Windows PowerShell shell running in a Windows Remote Desktop (RDP) Session:

clear

ls c:\ -recurse

Use 2 finger scroll gesture on touchpad-> Vertical scrolling does not work.

Also, note that both standard "non-Windows Terminal (beta)" legacy built-in CMD and PowerShell terminals work as expected in both scenarios. I.e. All four test cases.

Expected behavior

Two-finger scroll gesture on the touchpad should work as expected just like in legacy PowerShell and CMD terminals

Actual behavior

Scrolling does not function except if one is using a Remote Desktop session.

Issue 2:
Description of the new feature/enhancement

It would be great to be able to set a fixed window position for the terminal, like "top", "topLeft", "left", "bottomLeft" ... and the size.

Kind of like iTerm2 for macOS behaves.

Let's say, I'd like to have the terminal window on the bottom of the screen, using the screen's full width, and 20% of the screen's height, or even 300px of the screens height.

"windowPosition": "bottom",

"windowSize: "20%" // or "300px"
Issue 1:
.hidden-sm should be display: inline; and not display: block; so that you can have an element inline with another element when screen is wide and hidden when small.

Issue 2:
related to issues #8500 , #7808 , #4929 ; using .hidden-sm to hide span within .nav > li > a . Because class is display: block above -sm then text wraps to new line. Would you consider .hidden-* classes to be display: inline-block instead ?

Here's a jsfiddle of the two cases - but the repercussions could be greater outside of this situation so probably needs more consideration... http://jsfiddle.net/jholl/P86yf/
Issue 1:
Environment

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

Microsoft Windows [Version 10.0.18363.836]

Steps to reproduce

Alt+space and type a file on system

Expected behavior

Should search file and display result.

Actual behavior

Not searching files, only searching programs

Screenshots

Issue 2:
Summary of the new feature/enhancement

Copy an existing custom fancy zone layout, edit it, and save it as a new layout. I would like NOT to have to create from a blank template just to modify one section. I have 10 zones on a 4k that I just want to edit to make 9 but keep both so I can switch them based on what project I'm working on.

PS. Love Fancy Zones, greatest enhancement I'm seen in a while. much needed for 4k monitors.

Proposed technical implementation details (optional)