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

In some rare instances, and I have reported this via Windows Feedback, a window can get stuck outside of the visible desktop. The label in the taskbar may or may not be visible ( I have it set to only show from current window ) regardless of setting - this is likely due to how far off-screen it is or it could be outside the bounds of the mirrored L shape I use for my desktop environment and Windows may thing it is in a top-left monitor which doesn't exist, or somewhere else.

In these rare instances, WIN + Arrow does NOT let you move the window back onto any normal monitor.

Because Shortcut Guide draws the window which is selected, fully even if off screen, allow us to drag it while holding alt while this screen is up.

In most cases we can target the window, but the win + arrow system breaks in this rare instance. Allowing us to drag within the Win popup would help. In some cases, restarting the application does NOT fix the positioning of it either. In these instances, unplugging a monitor, or temporarily disabling it can help recover the window.

It doesn't happen often, but when it does it is more than a minor annoyance.

Proposed technical implementation details (optional)

While holding WIN key, since only the selected window is drawn fully, even if off-screen, allow us to move it with the mouse by dragging it.

Issue 2:
Move Hidden Windows to active screen

Some applications do not play nicely with multiple monitor scenarios.

They mainly the ones which remember their screen position.

Scenario

Laptop with additional monitor.

Start an affected application when you have two monitors connected and move it to monitor two, shut PC down.

Disconnect the second monitor, then start up PC and run the affected application.

All you see is a task bar icon becuse the application has blisfully unaware thet the second monitor is not preset jumped to the monitor which does not now exist.

I know there is a documented way to move such windows to an available screen, but it requires quite a bit of faffing arround. I invariably end up googling for the required key chord each time I need it becuase it does not happed that often, but often enough to cause irritation.

A hook that allowed the user to right click the task bar icon and "move to screen n" would be very much appreciated.

Some of the code in https://github.com/MikeWilliams-UK/SSMS-Window-Fixer may be of use in this.
Issue 1:
I have a login screen with 2 text fields and 2 buttons. Whenever I click on the text field key board pops up and the screen is pushed up and a red box appears that hides my button and goes away when the key board is closed. How do I avoid the red box?Do I need to realign the layout whenever the screen is pushed up? If so how do I do it whenever the screen is pushed up?

Issue 2:
In the Flutter codelab:

https://codelabs.developers.google.com/codelabs/flutter/#6

The third code listing, which starts with the comment:

// Modify the ChatMessage class definition as follows.

The "@OverRide" on the second line was added, but it is not marked as "//new"

(might be nice to explain why this directive was added).
Issue 1:
Reason of this:

Since tests are not under BC promise someone should not extend them.. You could ask "why someone to extend a test of symfony?"... I think we all have see an lot of weird stuff out there

PHPStorm improvements for autocompletion while typing MyClass extends T..... it will not show the tests..

This is a little bit different from #29677 ... because internal will be used only for stubs and will prevent them from be used in the actual code and hopefully at some point PHPStorm will improve search on this..

Let me know if I can submit a PR about this...

Issue 2:
Use case

Models:

abstract class AbstractUser
{
private $username;
private $password;
}

class ConcreteUser extends AbstractUser
{
/**
* @var UserProfile
*/
private $profile;
}

class UserProfile
{
private $name;
}

validation.xml (1)

<class name="AbstractUser">
<property name="username">
<constraint name="NotBlank">
<option name="groups">Registration</option>
</constraint>
</property>
<property name="password">
<constraint name="NotBlank">
<option name="groups">Registration</option>
</constraint>
</property>
</class>

validation.xml (2) :

<class name="ConcreteUser">
<property name="profile">
<constraint name="Valid" />
</property>
</class>

<class name="UserProfile">
<property name="name">
<constraint name="NotBlank">
<option name="groups">
<value>Profile</value>
<value>Registration</value>
</option>
</constraint>
</property>
</class>

When setting validation_groups to Registration, the error messages show twice for the UserProfile::name property.

A simple test can be adding the username validation again into ConcreteUser class constraints :

<class name="ConcreteUser">
<property name="profile">
<constraint name="Valid" />
</property>
<property name="username">
<constraint name="NotBlank">
<option name="groups">Registration</option>
</constraint>
</property>
</class>

Then validation error messages will show twice on the username as well.

In production environnement that's inconvenient :/

Hack, ugly but....

For now, there is a hack until this is fixed, in form theme blocks (twig) :

{% block field_errors %}
{% spaceless %}
{% if errors|length > 0 %}
<ul>
{% set lastError = null %}
{% for error in errors %}
{% if lastError != error %}
<li>{{ error.messageTemplate|trans(error.messageParameters, 'validators') }}</li>
{% endif %}
{% set lastError = error %}
{% endfor %}
</ul>
{% endif %}
{% endspaceless %}
{% endblock field_errors %}
Issue 1:
Description of the new feature/enhancement

It would be nice to have some sort of organization feature, such as a "folder", for the profiles drop down from the title bar.

Having this feature would allow the user to organize their profiles into meaningful categories. Such as "Dev", "QA", "Prod" to designate connections to different environments. This would eliminate having overly long lists of profiles to scroll through on the drop down.

Proposed technical implementation details (optional)

The ability to organize the profiles on the title bar drop down menu. I really don't care how it is implemented.

Issue 2:
Description of the new feature/enhancement

Many terminals will set different scrolling behavior within the Alternate Screen Buffer such that scrolling will send up/down key strokes. This seems to make more sense than scrolling through the main buffer's history.

xterm has this as an option (set by the 'alternatescroll' Xresource), VTE based terminals have this set as default behavior.

Please consider adding this capability to Windows Terminal.

Depends on #381.
Issue 1:
Lot of us currently using stable version and it would be much easier to migrate each component separately.

So at the start we will be able to load components separately:

import { Card, CardText, CardActions } from 'material-ui'; // 0.19.0
import { Button } from "@material-ui/button"; // ^1.0.0

Idea from material-components.

Where user can install whole lib from material-components-web repo or each component separately from @material/*.

See lerna.

Issue 2:
The input fields in MUI should allow props lang: string and spellcheck: boolean

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

Expected Behavior

I would expect this to be default allowed props

Current Behavior

Typescript throws error that props are not allowed on component:

in [at-loader] TS2339: Property 'spellchecker' does not exist on type 'IntrinsicAttributes & { autoComplete?: string | undefined; autoFocus?: boolean | undefined; input...'.

Steps to Reproduce (for bugs)

In this codepen I have created a basic html example. https://codepen.io/doff3n/pen/GOrjwN

Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.17

React
16.0.0

browser
All
Issue 1:
I'm submitting a ...

bug report

feature request

support request => Please do not submit support request here, see note at the top of this template.

Current behavior

angular/modules/@angular/upgrade/src/angular_js.ts

Line 141
in
bb89766

if (window.hasOwnProperty('angular')) {

window.hasOwnProperty('angular') is false

!!window.angular is true

Had to change the code manually in order to use the upgrade adapter.

Expected/desired behavior

window.hasOwnProperty('angular') is true

!!window.angular is true

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via

https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

What is the expected behavior?

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

Please tell us about your environment:

Angular version: 2.0.0-rc.1

Browser: tested in Chrome and Firefox latest versions

Language: TypeScript 1.9.0-dev.20160605-1.0 with SystemJS module loader

Related: #6165

Issue 2:
In upgrade.js (Line 284 in 2.0.0-beta.0), there is a hasOwnProperty check that alone, causes a TypeError if you use Object.defineProperty to define a setter function on window.angular:

var angular = {
bootstrap: noNg,
module: noNg,
element: noNg,
version: noNg
};
try {
if (window.hasOwnProperty('angular')) {
angular = window.angular;
}
} catch (e) {}
exports.bootstrap = angular.bootstrap;
exports.module = angular.module;
exports.element = angular.element;
exports.version = angular.version;

Because of this, window.hasOwnProperty returns true even if angular is actually 'undefined' and the local angular object is now also undefined when it really should be the local copy declared just above.

Here is a jsfiddle to demonstrate an example: https://jsfiddle.net/uko7uuvL/

I propose that this actually just be a null & undefined check instead:

if (window.angular) {
angular = window.angular;
}

This would make it safe to use Object.defineProperty to add a setter function to listen for when angular is initialized.
Issue 1:
Vue.js version

2.0.5

Reproduction Link

https://jsfiddle.net/e2c6y887/2/

Steps to reproduce

Click on 'test2'

What is Expected?

Test1 link should not have 'active' class and thus no red color.

The reason I'd want to combine class and v-bind:class (with both 'active' class) is, that the initial active class is added by JSP code and the second by Vue. If I don't have this initial class logic, the button gets the 'Vue active class' to late which causes a not very nice jump in the page.

What is actually happening?

Both test1 and test2 have 'active' class and are 'red'.

When clicking 'test1' again, and inspect the element, 'test1' have 2 'active' classes instead of one.

With Vue1 it works a bit different: https://jsfiddle.net/pfu2dw3j/1/

When clicking 'test2' both links have 'active' class. When clicking test 1 and test 2 again, it works correct from that point.

Do I use it wrong, or is it a bug?

Issue 2:
Version

2.5.16

Reproduction link

https://jsfiddle.net/1jz3wrfc/

Steps to reproduce

iterate a slot.

What is expected?

I want to be able to use a separator slot in a v-for iteration.

What is actually happening?

[Vue warn]: Duplicate presence of slot "separator"
Issue 1:
Bug Report

Current Behavior

The following code throws an error that bar is not defined (no error in babel@6).

Input Code

async function foo() {
await (async function bar() {
await bar();
})();
}

foo();

Expected behavior

The code inside an async self-executing named function is able to refer to the function by name.

Babel Configuration (.babelrc)

{
"presets": [
["@babel/env", {
"modules": "cjs",
"useBuiltIns": "entry"
}],
"@babel/typescript",
"@babel/react"
]
}

Environment

Babel version(s): @babel/core@7.1.2, @babel/preset-env@7.1.0, @babel/preset-typescript@7.1.0, @babel/preset-react@7.0.0

Node/npm version: node v10.10.0, npm@6.4.1

OS: OSX 10.13.6

Monorepo: no

How you are using Babel: webpack (loader) / parcel

Possible Solution

This is probably caused by asyncToGenerator / regenerator. bar is eventually located not inside bar itself and the function bar is not transpiled into a function declaration (this was in babel@6 and therefore there was no error present), but rather is still a function expression.

Issue 2:
Bug Report

Current Behavior

When trying to upgrade to Babel 7. Calling async function from within self-invoking function now causes ReferenceError: poll is not defined.

Input Code

(async function poll() {
console.log(await Promise.resolve('Hello'))
setTimeout(poll, 1000);
})();

Transformed Code

(function () {
var _poll = _asyncToGenerator(
/*#__PURE__*/
regeneratorRuntime.mark(function _callee() {
return regeneratorRuntime.wrap(function _callee$(_context) {
while (1) {
switch (_context.prev = _context.next) {
case 0:
_context.t0 = console;
_context.next = 3;
return Promise.resolve('Hello');

case 3:
_context.t1 = _context.sent;

_context.t0.log.call(_context.t0, _context.t1);

setTimeout(poll, 1000);

case 6:
case "end":
return _context.stop();
}
}
}, _callee, this);
}));

return function poll() {
return _poll.apply(this, arguments);
};
})()();

Error

Applications.js:64 Uncaught (in promise) ReferenceError: poll is not defined
at _callee$ (Applications.js:64)
at tryCatch (runtime.js:62)
at Generator.invoke [as _invoke] (runtime.js:296)
at Generator.prototype.(anonymous function) [as next] (webpack:///./node_modules/regenerator-runtime/runtime.js?:114:21)
at asyncGeneratorStep (Applications.js:19)
at _next (Applications.js:21)

Expected behavior/code

Recursively calls async function.

Babel Configuration (babel.config.js, webpack.config.js)

module.exports = function (api) {
api.cache(true)
const presets = [ '@babel/preset-env', '@babel/preset-react' ];
const plugins = [ '@babel/plugin-proposal-class-properties' ];

return {
presets,
plugins
};
}

Using @babel/polyfill in webpack.config.js

entry: {
react: ['@babel/polyfill', './index.js']
},

Environment

Babel version(s): v7.0.0

Node/npm version: v8.9.0

OS: OSX 10.12.6

Monorepo: no

How you are using Babel: loader

Additional context/Screenshots
Issue 1:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-slow/211/

Failed: [k8s.io] Networking [k8s.io] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/networking.go:175
Nov 23 16:49:33.756: Failed to find expected endpoints:
Tries 0
Command timeout -t 15 curl -q -s --connect-timeout 1 http://104.155.27.64:30504/hostName
retrieved map[default backend - 404:{}]
expected map[netserver-0:{} netserver-1:{} netserver-2:{}]

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/networking_utils.go:263

Previous issues for this test: #33730

Issue 2:
K8s on GCE will be using the upgraded version of container-vm. Testing for the new container-vm is not adequate as-is. Specifically the following tasks are critical:

Add per-pr tests that use the new container-vm

Add relevant tests that validate the new container-vm to the submit queue as non-blocker initially.

Add relevant per-pr and CI test that validate the new container-vm as submit-queue blockers. We might want to wait for at-least a week and ensure that the flake %tage with the new container-vm is not higher than the older version before making this change.

What is needed to clone an existing test to run with the new container-vm image?

Set KUBE_OS_DISTRIBUTION=gci instead of KUBE_NODE_OS_DISTRIBUTION=debian.

Per-pr test configs are located in the test-infra repo here.

The relevant tests are the ones that run e2e. Builds, unit & integration tests do not matter.

The submit-queue configs are here. Changes to submit-queue might have to be pushed manually.

@mtaufen @matchstick @dchen1107

cc @lavalamp in case he has more thoughts on how tests needs to be added to the submit queue.
Issue 1:
Problem description

display:flex is an object, instead of a string. Which breaks the flow of the UI. Any idea why? In the example of the documentation flex is a string.

Versions

Material-UI: 0.15.0

React: 15.0.1

Browser: Chromium 50.0

Issue 2:
Problem description

I'm trying out Badge component and run into an 'invalid property value' error for CSS for Badge's display property when userAgent is 'all'

cause : when userAgent is set to 'all', Material UI transforms display:flex into display:-webkit-box,-moz-box,-ms-flexbox,-webkit-flex,flex

Steps to reproduce

(1) set userAgent property in muiTheme

userAgent: 'all'

(2) add a Badge compponent to your site

<Badge badgeContent={4} primary={true} style={{paddingTop:5}} badgeStyle={{top: 0, right: 15}}>
<IconButton tooltip="checkout">
<FontIcon className="material-icons" color={grey500}>shopping_cart</FontIcon>
</IconButton>
</Badge>

Versions

Material-UI: 0.15.4

React: 15.3.1

Browser: Chrome Version 52.0.2743.116 m
Issue 1:
For our step-style challenges, many campers are confused and don't realize that they just need to click the "open link in new tab" button to enable the "next step" button.

We should add a small "skip step" button so that campers can keep going if, say, they already have a GitHub account.

Issue 2:
In the Waypoints, there's only Go to next step option. There's no previous step to go back if I wanted to.

Browser's back button takes me to the start not the previous page.

Also, a skip button would be great. I had to click 'open link in new tab' every time to go to next step. What if I already had a github account. What if I already finished the chapter and I'm revisiting.

Back / Previous and Skip buttons would be of great help and make a better UX.
Issue 1:
the ui is shown for less than a second and then disappearing

Issue 2:
Environment

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

Steps to reproduce

Launch Powertoys - right click to bring up settings

Expected behavior

See the settings dialog

Actual behavior

The dialog area is blank. As it opens on the desktop, it briefly flashes the content but then becomes blank

Screenshots
Issue 1:
When loading an obj file such as the following:

v 0 1 1
v 1 1 0
v 1 0 1
v 1 1 1
f 1 2 3
f 1 2 4

The resulting THREE.Geometry contains 10 vertices, rather than the expected 4. This is because a new set of vertices are created for every face, rather than the same vertex reused.

r62

Issue 2:
If you load a model using OBJLoader -- a Stanford Bunny for example -- and apply a matrix translation like so:

geometry.applyMatrix( new THREE.Matrix4().makeTranslation( 0, -0.01, 0 ) );

this is what you get:

Poor bunny.

There are two issues here:

Issue 1. In this example, 2503 vertices in the data file result in 14904 vertices in the mesh.

This is because vertices are replicated -- each face is assigned three unique vertices:

geometry.vertices.push(
vertices[ parseInt( result[ 1 ] ) - 1 ],
vertices[ parseInt( result[ 2 ] ) - 1 ],
vertices[ parseInt( result[ 3 ] ) - 1 ]
);

geometry.faces.push( face3(
verticesCount ++,
verticesCount ++,
verticesCount ++
) );

So the question is: Should we really be doing this?

Issue 2. The vertices are not unique Vector3s -- multiple vertices reference the same Vector3. This is why there is distortion when a matrix is applied to "each vertex".

It is important that geometry.vertices be an array of unique objects.

(This is not to be confused with "duplicated" vertices, in which two or more vertices have the same location. Duplicated vertices are OK.)
Issue 1:
Seth Ladd opened SPR-1247 and commented

Hello again,

As I was browsing the AbstractFormController source, I noticed what seemed to be some duplication of code. It's quite possible this can be cleaned up a small bit.

Inside handleRequestInternal, there is this logic:

if (isSessionForm()) {

HttpSession session = request.getSession(false);

if (session == null || session.getAttribute(getFormSessionAttributeName(request)) == null) {

return handleInvalidSubmit(request, response);

}

}

Which is essentially duplicated in getCommand() of the same class.

I'd like to propose that getCommand() throw some error-specific exceptions when the session doesn't exist, or when the form doesn't exist in the session. This way, the code in handleRequestInternal can merely attempt a call to getCommand() and see if there are exceptions like NoExistingSessionException. If handleRequestInternal sees that exception, it can then forward the call to handleInvalidSubmit().

At this point, the checking of the session and the checking if the form bean is in the session is in two different places that are called twice in a row. I think with just a bit of code moving, we can do the checking of the session once.

Thanks!

Seth

Affects: 1.2.4

Issue 2:
Marcel Overdijk opened SPR-9380 and commented

I have the blow AppConfig class in my project:

@Configuration
@ComponentScan(basePackages = { "my.project" })
@PropertySource({ "classpath:/META-INF/config.properties", "classpath:/META-INF/config-${my.runtime.environment}.properties" })
public class AppConfig {

private static Log LOG = LogFactory.getLog(AppConfig.class);

@Bean
public static PropertySourcesPlaceholderConfigurer propertySourcesPlaceholderConfigurer() {
return new PropertySourcesPlaceholderConfigurer();
}

Resolving the ${my.runtime.environment} in the @PropertySource does not work anymore in Spring 3.1.1 while I was just upgrading from 3.1.0.

The same code works fine in 3.1.0 but gives this error in 3.1.1:

Failed to load bean class: mt.project.config.AppConfig; nested exception is java.io.FileNotFoundException: class path resource [META-INF/config-${my.runtime.environment}.properties] cannot be opened because it does not exist

The config file exists and the system property is set (I logged that as well), and just to mention it again. In 3.1.0 this works fine.

Affects: 3.1.1

Issue Links:

#13772 Fix regression in @PropertySource placeholder resolution ("duplicates")

#13766 @PropertySource annotation with multiple values and a name fails to register all property sources ("duplicates")
Issue 1:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DHAVE_CONFIG_H' '-D_DARWIN_USE_64_BIT_INODE=1' '-DNDEBUG' -I../../../../src/libuv/include -I../../../../src/libuv/src -Os -gdwarf-2 -fvisibility=hidden -Wnewline-eof -arch i386 -Wall -Wendif-labels -W -Wno-unused-parameter -fstrict-aliasing -MMD -MF ./.deps/obj.target/libuv/src/fs-poll.o.d.raw -DRUST_DEBUG -fno-omit-frame-pointer -O2 -fPIC -std=gnu99 -c -o obj.target/libuv/src/fs-poll.o ../../../../src/libuv/src/fs-poll.c
In file included from ../../../../src/libuv/src/fs-poll.c:22:
In file included from ../../../../src/libuv/include/uv.h:48:
../../../../src/libuv/include/uv-errno.h:25:10: fatal error: 'errno.h' file not found

errno.h is at /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS7.0.sdk/usr/include/errno.h. This include path is defined in mk/platform.mk via CFG_IOS_FLAGS.

How can we pass the include-path down to libuv?

Issue 2:
I’m pretty sure that some macros used to be documented at http://doc.rust-lang.org/std/macros/index.html , but this page is now empty.