WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Environment

Windows build number: 10.0.18990.0
Windows Terminal version (if applicable): 0.5.2661.0

Any other software?
PowerToys

Steps to reproduce

Configure (or use a prebuilt) Fancy Zone from PowerToys, leaving shift+drag to zone enabled.

Grab Terminal by the title bar, hold shift, and drag into a zone.

Expected behavior

I would expect the zone to light up and the terminal to snap to the zone as every other app that I've tried does.

Actual behavior

The zone doesn't light up and it appears as though it's not registering that I'm even dragging a window into the zone.

This seems like an issue for here, not the PowerToys repo because this is the only app that I've seen that is having this issue.

Issue 2:
Support "Find"

This is to enable searching the console output (hopefully similar to the legacy console Find dialog.)

Proposed technical implementation details (optional)

Expect Keybinding to allow Ctrl+F to be bound to a new find command.
Issue 1:
Bug report

Using the React.StrictMode wrapper, and inside this wrapper using some dynamic import. Is throwing this warning:

Is not a "Bug", everything works. However I reported as a bug because IMO this should be fixed to work perfectly under the strict mode.

To Reproduce

Wrap your app with <StrictMode><App /></StrictMode>

Use some dynamic(import('...')) inside the app

Open the dev tools console and see the warning

Issue 2:
Bug report

Describe the bug

Starting in React 16.9.0 using 'componentWillMount' issues a deprecation warning because it has been renamed to UNSAFE_componentWillMount. Instead it is suggested to use componentDidMount.

This was discovered by using dynamic imports with react 16.9.0 (Released yesterday) and nextjs 9.0.3

Full error is

Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

Move code with side effects to componentDidMount, and set initial state in the constructor.

Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: LoadableComponent

Code Reference:

https://github.com/zeit/next.js/blob/master/packages/next-server/lib/loadable.js#L174

To Reproduce

npm install react react-dom next

Then just add a dynamic import

import React from 'react';
const DynamicComponent = dynamic(() => import(`./file`), {
loading: () => '<div>Loading Component</div>',
});
function TestComponent() {
return <DynamicComponent />
}
export default TestComponent;

Expected behavior

loadable.js should be fixed to either work with componentDidMount (See comment below) or UNSAFE_componentWillMount

Screenshots

System information

Version of Next.js: 9.0.3
Issue 1:
Hi,

I implemented the fix from #14465 into the codebase of my Symfony 2.7.0-BETA1 based appication. Now, the non required filter form choice fields work again an do not provoke form errors, when they are empty.

But in the same time, all my required choice fields (representing non nullable database columns) do not validate anymore, when I submit them empty. Insteat I get an SQL error about the missing values for the non nullable fields. Removing the fix again resolves this.

See also my comment on the fix itself: #14465 (comment)

Issue 2:
I think that's happening only on propel + postgres after @webmozart removed empty/null checks from ChoiceToValueTransformer in 1d89922

ModelChoiceList->getChoicesForValues allows to create Propel query with empty string values which are not accepted, so I'm getting:

Unable to execute SELECT statement [SELECT (...) FROM twilio_number WHERE twilio_number.id IN (:p1)] [wrapped: SQLSTATE[22P02]: Invalid text representation: 7 ERROR: invalid input syntax for integer: ""]

the code below (for propel bridge) seems to do the trick, but I'm not sure if I can create PR for the Propel1Bridge repository. Will appreciate any help.

class ModelChoiceList extends ObjectChoiceList

public function getChoicesForValues(array $values)
{
if (empty($values) || empty($first = reset($values))) {
return array();
}
Issue 1:
Is there any way to insert an optional transform as intentionally left blank? I want to set the react.inlineElements transform to only run in production but there doesn't seem to be a nice way to handle a ternary.

query: { optional: ['optimisation.react.constantElements', PROD ? 'optimisation.react.inlineElements' : null] } },

The logic for the pipeline appears to be here, but it doesn't seem to handle any falsey values, instead falling through to the Module build failed: ReferenceError: Unknown transformer null specified in optional message.

Could we use some sentinel value, either '', false, or null to signify "this space intentionally left blank?

Issue 2:
An idea that came after reading about #174. What about generating the JSDoc-style comments for classes and methods?

This is very provocative, and for sure something hard to maintain. Yet an interesting idea IMHO.

Please note I don’t personally use JSDoc, but I could start using it if it was somehow auto-generated.

I still think that

/**
* A Klass
* @class Klass
* @extends Parent
*/
class Klass extends Parent {}

is a little too verbose. But if 6to5 mangled the code that follows accordingly it could be interesting.

/** A Klass */ // no need to use @class and @extends here
class Klass extends Parent {}
Issue 1:
I think there's an existing issue, but I can't find it. Currently borrowck treats nullary variants (like None) as static identifies. This doesn't make sense for generic enums and I don't think it matches up with trans. The reason it doesn't make sense for generic enums is that None::<Foo> and None::<Bar> have totally different sizes etc., so there couldn't possible be a single static constant to refer to. This is a relatively simple fix to the mem_categorization code, but it's worth investigating how trans handles enum variants and make sure that everything will be compatible.

Nominating since it is a backwards compatibility thing.

Issue 2:
I asked stackoverflow about lifetime of variable. Original link is this : http://stackoverflow.com/questions/21226942/rust-lifetime-and-calling-member-function

** Question from link **

I have a question about lifetime of varable in Rust programming language.

createTest function creates and returns r-value reference. and when it returns a reference, testValue is destroyed. But test.print() doesn't lead to crash. Why?

(Is Test::print function called as static function?)

Code

struct Test;
impl Drop for Test {
fn drop (&mut self) {
println("Dropped.");
}
}

impl Test {
fn print(&self) { println!("Print!"); }
}

fn createTest() -> &Test {
let testValue = &Test;
return testValue;
}

fn main() {
let test = createTest();
test.print();
println("Test");
}

Result

Dropped.
Print!
Test

It happened with empty struct only. Is it a really bug?
Issue 1:
For example if we have a class

class Product
{
private _prodNumber: any;
private _name: string;

constructor() {}

get prodNumber() { return this._prodNumber; }
get name() { return this._name; }
}

var prod = new Product();

if we start typing _p using the prod variable

intellisence shows _productNumber member in the properties although it is a private member.

If we have a class with a lot of members those private properties intermix with public properties and it is difficult to find a needed property in the long list of properties.

Expected: private properties are hidden from intelisense and protected properties are shown only in intellisense of derived classes and not when we use a class instance.

Issue 2:
I don't know if this is by design but outside of the class I am able to see private static members, which I don't believe I should be able to, for example:

I have a class named "NotifyChanged" (in the "Aspect" module/namespace) and it inherits from "Base" (also in the "Aspect" module/namespace). Base has a private static method named "createGet" which is only used within the Base class. In a completely different class in a completely different module/namespace I am able to type "Aspect.NotifyChanged.cre" and the intellisense pops up with createGet. If I continue, the IDE then underlines the whole line saying that createGet is a private method and is not accessible - but it still displays it as an method to call in intellisense?

Please also see attached screenshots.
Issue 1:
Environment

Windows build number: 10.0.18980.0

Windows Terminal version (if applicable): 0.4.2382.0

Steps to reproduce

Two displays setup: in my case, an LG monitor, used as the primary monitor, connected through an HDMI cable to a Dell Inspiron 14 5000.

Expected behavior

I have the following configs on my profile.json file (just a fragment of the file):

{
"acrylicOpacity": 0.85,
"closeOnExit": true,
"colorScheme" : "Solarized Dark",
"commandline": "wsl.exe -d Ubuntu-18.04",
"cursorColor": "#FFFFFF",
"cursorShape": "vintage",
"fontFace" : "Fira Code",
"fontSize": 12,
"guid": "{2c4de342-38b7-51cf-b940-2309a097f518}",
"historySize": 9001,
"icon": "ms-appx:///ProfileIcons/{9acb9455-ca41-5af7-950f-6bca1bc9722f}.png",
"name": "Ubuntu",
"padding": "10, 0, 10, 0",
"snapOnInput": true,
"useAcrylic": true
},

The opacity would work besides the focused screen at the moment. Example: if my terminal is open on Dell display, even I move the focus to LG display, the opacity must stay working.

For reference purposes, that's like iTerm2 behaves.

Actual behavior

Actually, when I change the display focus, the terminal opacity is disabled. This recorded video capture tries to illustrate the behavior. At second 00:07 I click on the other display that leads to opacity losing. When I click again on the second display with the open terminal, the opacity is enabled.

Issue 2:
Environment

Windows build number: Microsoft Windows [Version 10.0.18362.476]

Windows Terminal version (if applicable): 0.6.2951.0

Any other software?

Nano editor

Steps to reproduce

Open new file with nano. Write "Before" New line "After". Paste any multiline string with right click or ctrl shift v.

Expected behavior

before
test
test
test
test
after

Actual behavior

before

test

after
test

test

test

Pasting adds newlines and skips existing entries. Not sure if thats only the case for nano. Works with nano on traditional cmd and bash (wsl).
Issue 1:
After closing #12344, we should think about the best strategy for replacing usage of managed boxes inside List<T>. @alexcrichton, @bill-myers and @eddyb provided good hints on how we should implement List<T> internally (i.e. instead of using an enum, use a struct-based approach with 'head' and 'tail').

Issue 2:
I am writing a Euclidean Vector class, and want to override some operations for it. However, when I try to add mul for both Vector-Vector multiplication and Vector-Scalar multiplication, the compiler complains that there is a Duplicate supertrait in trait declaration:

euclidean_vector.rs:5:0: 20:1 error: Duplicate supertrait in trait declaration
euclidean_vector.rs:5 pub trait EuclideanVector<T: Num + Algebraic> :
euclidean_vector.rs:6 Add<Self, Self> +
euclidean_vector.rs:7 Sub<Self, Self> +
euclidean_vector.rs:8 Mul<Self, Self> +
euclidean_vector.rs:9 Mul<T, Self> +
euclidean_vector.rs:10 One + Zero +
Issue 1:
Bug report

I put a React Context Provider in my custom _app.js, and used the context in my pages. This resulted in undefined context in SSR.

Describe the bug

_app.js

import React, { Fragment } from 'react';
import { Modal } from '@redq/reuse-modal';
import '@redq/reuse-modal/es/index.css';
import { MyProvider } from '../../common/src/contexts/MyContext';

export default ({ Component, pageProps }) => {
return (
<Fragment>
<Modal />
<MyProvider>
<Component {...pageProps} />
</MyProvider>
</Fragment>
);
};

_document.js

import Document, { Head, Main, NextScript } from 'next/document';
import { ServerStyleSheet } from 'styled-components';
import FavIcon from 'common/src/assets/image/favicon.png';

export default class CustomDocument extends Document {
static async getInitialProps(ctx) {
const sheet = new ServerStyleSheet();
const originalRenderPage = ctx.renderPage;

try {
ctx.renderPage = () =>
originalRenderPage({
enhanceApp: App => props => sheet.collectStyles(<App {...props} />),
});

const initialProps = await Document.getInitialProps(ctx);
return {
...initialProps,
styles: (
<>
{initialProps.styles}
{sheet.getStyleElement()}
</>
),
};
} finally {
sheet.seal();
}
}
render() {
return (
<html lang="en">
<Head>
<link rel="shortcut icon" type="image/x-icon" href={FavIcon} />
</Head>
<body>
<Main />
<NextScript />
</body>
</html>
);
}
}

Error message: TypeError: Cannot read property 'value' of undefined

ctx.renderPage
./pages/_document.js:11
8 | const originalRenderPage = ctx.renderPage;
9 |
10 | try {
> 11 | ctx.renderPage = () =>
| ^ 12 | originalRenderPage({
13 | enhanceApp: App => props => sheet.collectStyles(<App {...props} />),
14 | });

Issue 2:
Bug report

Describe the bug

In Next.js 8.1.0 React Context.Consumer receives value of undefined

Only on server side

UPDATE: Only in production, not in npm run dev

To Reproduce

Reproduce repository - link

const MyContext = React.createContext();

function Home() {

return <MyContext.Provider value={{ x: "123" }}>
<MyContext.Consumer>
{value => value.x}
</MyContext.Consumer>
</MyContext.Provider>
}

export default Home;

Expected behavior

MyContext.Consumer value should receive object from MyContext.Provider

System information

Version of Next.js: 8.1.0

Additional context

Also an issue for many Antd components
Issue 1:
Hi, next is great, thnx.

I have a big project based on lerna monorepo with next, and custom next server as a different packages. For production build we use few stages docker build, lerna build building all packets in monorepo, after this i wanna take custom server package and builded .next folder for the run next on server, but for the disk space economy, i wanna include using in next node_modules to next server bundle. I try customize webpack config for chose config.externals, or next-plugin-transpile-node-modules, but i dont have a luck.

Maybee you have example proj, example config, actual plugin or any advice for this?

Thnx.

Next version 7.0.1

https://spectrum.chat/thread/2a07bd86-895c-41f9-a610-392765a845df

Issue 2:
I'm trying to upgrade from v5 to v6. And I encountered a build error which caused from the _document.js as the following screenshot. Once I remove the _document.js the error was gone. In additional even that I used the example the error still occurs.

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

Expected Behavior

Upgraded to v6 and build success with _document.js.

Current Behavior

Upgraded to v6 but build failed with _document.js.

Steps to Reproduce (for bugs)

Upgraded to v6 via this instruction.

Run yarn dev and build success.

But build failed due to Module build failed: ReferenceError: Unknown helper getPrototypeOf which caused from _document.js.

Your Environment

Tech
Version

next
v6

node
v9.11.1

OS
MacOS

browser
Google Chrome
Issue 1:
[ ] bug report
[ x ] feature request
[ ] support request

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

Currently null or empty value passed to routerLink adds current page href value to link that is not useful. There is a lot of usecases for 'disabled' links that should not navigate anywhere and should not has href attribute at all.

It would be useful to have null/empty value support by routerLink that will results with no href attribute on link at all to prevent any navigation/link copying.

Issue 2:
I'm submitting a ... (check one with "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

Angular app is not loading all of its component after updating to latest version.

Expected behavior

Angular app is working the same thing as the previous version.

Minimal reproduction of the problem with instructions

I'm trying to load a angular app using @angular/router@3.4.6 and all works fine, However when I tried to update my packages using "npm update" all packages which are outdated are updated as expected, but when I tried to run again the angular app it fails (no error on inspect element in browser).

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

During the investigation, I tried to update the packages 1by1 and found out that the error occurred in @angular/router@3.4.8. Trying to downgrade the version of @angular/router@3.4.6 will fix the issue.

However, I just want to confirm if this is a issue in 3.4.8?
Issue 1:
Version

2.6.14

Reproduction link

[https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPCFET0NUWVBFIGh0bWw XG48aHRtbD5cbiAgPGhlYWQ XG4gICAgPG1ldGEgY2hhcnNldD1cInV0Zi04XCI XG4gICAgPG1ldGEgbmFtZT1cInZpZXdwb3J0XCIgY29udGVudD1cIndpZHRoPWRldmljZS13aWR0aCxpbml0aWFsLXNjYWxlPTEuMFwiPlxuICAgIDx0aXRsZT7opb/mioDmnK88L3RpdGxlPlxuICAgIDwhLS0gYnVpbHQgZmlsZXMgd2lsbCBiZSBhdXRvIGluamVjdGVkIFRPRE8gQ0RO5LyY5YyWIC0tPlxuICAgIDxsaW5rIHJlbD1cInN0eWxlc2hlZXRcIiB0eXBlPVwidGV4dC9jc3NcIiBocmVmPVwiaHR0cDovL3VucGtnLmNvbS92aWV3LWRlc2lnbi9kaXN0L3N0eWxlcy9pdmlldy5jc3NcIj5cblxuICAgIDxzY3JpcHQgc3JjPVwiaHR0cHM6Ly91bnBrZy5jb20vdnVlQDMuMC41L2Rpc3QvdnVlLmdsb2JhbC5qc1wiPjwvc2NyaXB0PlxuICAgIDxzY3JpcHQgc3JjPVwiaHR0cHM6Ly91bnBrZy5jb20vdnVlLXJvdXRlckA0LjAuMy9kaXN0L3Z1ZS1yb3V0ZXIuZ2xvYmFsLmpzXCI PC9zY3JpcHQ XG5cbiAgICA8c2NyaXB0IHR5cGU9XCJ0ZXh0L2phdmFzY3JpcHRcIiBzcmM9XCJodHRwOi8vdW5wa2cuY29tL3ZpZXctZGVzaWduL2Rpc3QvaXZpZXcubWluLmpzXCI PC9zY3JpcHQ XG5cbiAgPC9oZWFkPlxuICA8Ym9keT5cbiAgICA8ZGl2IGlkPVwiYXBwXCI PC9kaXY XG4gIDwvYm9keT5cbjwvaHRtbD5cbiJ9](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPCFET0NUWVBFIGh0bWw XG48aHRtbD5cbiAgPGhlYWQ XG4gICAgPG1ldGEgY2hhcnNldD1cInV0Zi04XCI XG4gICAgPG1ldGEgbmFtZT1cInZpZXdwb3J0XCIgY29udGVudD1cIndpZHRoPWRldmljZS13aWR0aCxpbml0aWFsLXNjYWxlPTEuMFwiPlxuICAgIDx0aXRsZT7opb/mioDmnK88L3RpdGxlPlxuICAgIDwhLS0gYnVpbHQgZmlsZXMgd2lsbCBiZSBhdXRvIGluamVjdGVkIFRPRE8gQ0RO5LyY5YyWIC0tPlxuICAgIDxsaW5rIHJlbD1cInN0eWxlc2hlZXRcIiB0eXBlPVwidGV4dC9jc3NcIiBocmVmPVwiaHR0cDovL3VucGtnLmNvbS92aWV3LWRlc2lnbi9kaXN0L3N0eWxlcy9pdmlldy5jc3NcIj5cblxuICAgIDxzY3JpcHQgc3JjPVwiaHR0cHM6Ly91bnBrZy5jb20vdnVlQDMuMC41L2Rpc3QvdnVlLmdsb2JhbC5qc1wiPjwvc2NyaXB0PlxuICAgIDxzY3JpcHQgc3JjPVwiaHR0cHM6Ly91bnBrZy5jb20vdnVlLXJvdXRlckA0LjAuMy9kaXN0L3Z1ZS1yb3V0ZXIuZ2xvYmFsLmpzXCI PC9zY3JpcHQ XG5cbiAgICA8c2NyaXB0IHR5cGU9XCJ0ZXh0L2phdmFzY3JpcHRcIiBzcmM9XCJodHRwOi8vdW5wa2cuY29tL3ZpZXctZGVzaWduL2Rpc3QvaXZpZXcubWluLmpzXCI PC9zY3JpcHQ XG5cbiAgPC9oZWFkPlxuICA8Ym9keT5cbiAgICA8ZGl2IGlkPVwiYXBwXCI PC9kaXY XG4gIDwvYm9keT5cbjwvaHRtbD5cbiJ9)

Steps to reproduce

Use @ vue/cli 4.5.6.

With vue3, introduce the following in the < head > of index.html:

< script src= ".vue @ 3.0.5/dist/vue.global.js" > < / script >.

< script src= "... vue-router@4.0.3/dist/vue-router.global.js" > < / script >.

Then configure in webpack.base.conf.js.

Externals: {.

'vue': 'Vue'

'vue-router': 'VueRouter'

}.

What is expected?

expected reduce the size of the package after build

What is actually happening?

Then report an error:

Ncaught TypeError: Cannot read property 'version' of undefined.

(version = Vue.version.split ('.') .map (Number)).

And.

Dom.js:2 Uncaught TypeError: Cannot read property 'prototype' of undefined.

At Object. < anonymous > (dom.js:2)

Issue 2:
source:

<div class="icon icon-{{test}}"></div>

expect:

<div class="icon icon-test"></div>

result:

<div class="icon icon- icon-test"></div>

here's the code:

https://jsfiddle.net/10ons60y/

是我的使用姿势不对吗 (:3」∠)
Issue 1:
Currently we collect the JSON Docker container logs and ingest them without further processing into either Elasticsearch or Cloud Logging. It would be useful to add fields to identify the name of the pod that corresponds to a specific Docker container log file (line) and perhaps also the hostname too. Relating the Docker container ID to a pod name might be possible by speaking to the kubelet during log ingestion time and this would require us to write a suitable filter in Ruby as part of our Flueuntd setup. However, we also need access to historical information because we may need to tag a log file for a Docker container for which the pod is not currently running -- perhaps by looking at events? This then also impacts one of the decisions we are trying to make about where events should be stored -- esp. if we decided to also store them as log files ingested by the same flow.

This would then allow users to query "all logs for a pod" and enable the query "all logs for a service".

@a-robinson @dchen1107 @lavalamp @thockin

Issue 2:
All of the labels attached to the container whose logs are being collected should be added on to the logs. For example, if logs are being collected for container foo with the labels env=prod and service=backend, those labels (env=prod, service=backend) should be attached such that someone querying logs later can ask for all logs with those labels to easily aggregate across containers.

IIRC both elasticsearch and Google Cloud Logging support arbitrary labels, so the only work needed should be getting the container's labels into Fluentd and attaching them.

cc @satnam6502
Issue 1:
Electron version: 1.4.5

Operating system: win 10

Expected behavior

window.open() always opens a visible window.

Actual behavior

window.open() opens an invisible window if run new BrowserWindow({ show: false }); before.

How to reproduce

index.html

<button type=button onclick="window.open('index.html')">Open</button>

index.js

const {app, BrowserWindow} = require('electron');
app.once('ready', () => {
let win = new BrowserWindow({ show: false }); //create a invisible window and show it later
win.maximize();
win.show();
win.loadURL(__dirname + '/index.html');
});

Run the app, click the Open button, the new window is not visible.

Issue 2:
Follow-up to #2771.

If:

you create a BrowserWindow with the show option set to false,

you show that window

JavaScript in that page calls window.open

nothing will happen—no window will appear.

My hypothesis is that the new window is inheriting the show option. This is corroborated by #2771. (However I tried selecting the "Bring All to Front" menu option (with role set to 'front') and that didn't cause any hidden windows to appear—perhaps that's a separate bug.)

I think it's reasonable for a new window to inherit show: false if the parent window is hidden—but after the parent window is shown, child windows should also be shown, no? Otherwise window.open is forever broken in the parent window.

(The parent window could call window.open with show=true, but IMO even if Electron chooses to hide child windows, in-page JavaScript loaded from a remote server should not have to be aware of this.)

As far as the rest of the options that child windows inherit, I'm undecided whether I think that the child windows should inherit the up-to-date options or the original options. It'd probably simplify the implementation to have everything be up-to-date. On the other hand, perhaps the original options are better defaults for new windows.