WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
When I opened my solution, always got this error message.I am from China.

My dev-environment:

OS: Microsoft Windows 10

IDE: Visual Studio Code 0.10.5

DNX: 1.0.0-rc1-update1

The solution created by visual studio 2013.

*.csproj

�� Microsoft.Build.Shared.ProjectErrorUtilities.ThrowInvalidProject(String errorSubCategoryResourceName, IElementLocation elementLocation, String resourceName, Object[] args)

�� Microsoft.Build.Evaluation.Project.Data.InitializeForEvaluation(IToolsetProvider toolsetProvider)

�� Microsoft.Build.Evaluation.Evaluator4..ctor(IEvaluatorData4 data, ProjectRootElement projectRootElement, ProjectLoadSettings loadSettings, Int32 maxNodeCount, PropertyDictionary1 environmentProperties, ILoggingService loggingService, IItemFactory2 itemFactory, IToolsetProvider toolsetProvider, ProjectRootElementCache projectRootElementCache, BuildEventContext buildEventContext, ProjectInstance projectInstanceIfAnyForDebuggerOnly)

�� Microsoft.Build.Evaluation.Evaluator4.Evaluate(IEvaluatorData4 data, ProjectRootElement root, ProjectLoadSettings loadSettings, Int32 maxNodeCount, PropertyDictionary1 environmentProperties, ILoggingService loggingService, IItemFactory2 itemFactory, IToolsetProvider toolsetProvider, ProjectRootElementCache projectRootElementCache, BuildEventContext buildEventContext, ProjectInstance projectInstanceIfAnyForDebuggerOnly)

�� Microsoft.Build.Evaluation.Project.ReevaluateIfNecessary(ILoggingService loggingServiceForEvaluation)

�� Microsoft.Build.Evaluation.Project.Initialize(IDictionary2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectLoadSettings loadSettings) �� Microsoft.Build.Evaluation.Project..ctor(String projectFile, IDictionary2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectCollection projectCollection, ProjectLoadSettings loadSettings)

�� Microsoft.Build.Evaluation.ProjectCollection.LoadProject(String fileName, IDictionary2 globalProperties, String toolsVersion) �� OmniSharp.MSBuild.ProjectFile.ProjectFileInfo.Create(MSBuildOptions options, ILogger logger, String solutionDirectory, String projectFilePath, ICollection1 diagnostics)

�� OmniSharp.MSBuild.MSBuildProjectSystem.CreateProject(String projectFilePath)

Issue 2:
From @sporens on January 17, 2016 20:57

Hi,

The command executed by VS Code to install and resolve missing dependancies for an ASP.NET application fails with "Can't find path" when the path to the users' home folder includes a space. For example:

c:\users\joeblogs\ <- works

c:\users\joe blogs\ <- fails

Running procmon I see it's attempting to execute:

cmd.exe /c start /wait cmd.exe /c "C:\Users\joe blogs.dnx\runtimes\dnx-clr-win-x86.1.0.0-rc1-update1\bin\dnu.cmd restore & pause"

Which fails.

Thanks

Copied from original issue: microsoft/vscode#2072
Issue 1:
It's currently difficult (impossible?) to create plugins for React that use any of the stuff in lib without using crazy hacks.

What's the best way to do this? Separate modules?

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

Feature

There's a common case of having a list of items, keyed by some id, and items can be added/removed over time. For example, say we have a list of users and a button to refresh the list with new data from the server. Here, User is a simple function component.

users.map((user) => (
<User key={user.id} data={user} />
)

Say this produces the following User elements:

key: 1000, data: { name: 'foo' }
key: 1001, data: { name: 'bar' }
key: 1002, data: { name: 'baz' }

Later we get the new user list, and these are the resulting elements:

key: 1003, data: { name: 'quux' }
key: 1002, data: { name: 'baz' }
key: 1001, data: { name: 'bar' }

The operations are:

remove 1000, destroy instance and dom nodes

move 1002, update

create 1003, with instance and dom nodes

Would an option to tell React that it can reuse the instances and dom nodes make sense?

From the list diff, React has this information (as I understand it):

remove at key: 1000, type: User, index: 0

create at key: 1003, type: User. index: 0

If we signaled to React that it can reuse elements, and since the 'type' is the same, it could reduce these operations to updating the identity of the underlying instance (key: 1000 -> key: 1003) and then update the instance normally. It could also require a move, but it doesn't here.

When used, it reduces the combined create/destroy operations of instances and dom nodes from create + destroy to Math.abs(create - destroy).

Of course, this has to be opt-in behavior because some components won't clear their internal state, and some DOM nodes can hold uncontrolled state. Also in some cases this could be slower (but I'd wager this is rare).

The syntax is secondary; I mostly want to hear what's thought about the idea of explicitly permitting React to reuse instances, but this is the simplest idea I have.

<React.Reusable>
{users.map(...)}
</React.Reusable>

Why do this in core?

I can't think of a reasonable way to do this in user space, and the less reasonable ways require duplicating the effort of diffing the list.

It's just allowing React to simplify the operations it intends to perform.

Why do this at all?

It provides another performance hook for React code, which people can attempt to apply while optimizing their react and react-native apps, if it makes sense in their situation.
Issue 1:
📝 Provide a description of the new feature

What is the expected behavior of the proposed feature? What is the scenario this would be used?

INCLUDE SYNCTOY INTO POWERTOYS

If you'd like to see this feature implemented, add a 👍 reaction to this post.

Issue 2:
When searching for local files it could be convenient to add an option to restrict results to folders.

In part because it would make results faster, and in part because personally I've found that 90% of the times I just want to open a folder and not a file.

This could be as simple as adding a f shortcut. Eg: typing f photos in the query.
Issue 1:
Description of the problem

When i import the model it is correct.

https://gyazo.com/ff1c9b427be5ba44ab1a500bffecabeb

But with the animation on it flies off into the distance

https://gyazo.com/3ce34820e57708c86c004f7f307a332a

But it's working fine on Babylon with the same file and animation on:

https://gyazo.com/0791af74b0da7ca1f8ec7e39f8314096

Animation export settings:

https://gyazo.com/f8666858b9108691b10228caa6d29c6a

Blend file:

https://drive.google.com/file/d/1kWiWDLJ4rQ98mPha3kcss6cCl5y2iTg3/view?usp=sharing

GLB file:

https://drive.google.com/file/d/1JNY90Zvn4pxuBdQ_PivTMZpDJIpiOsOa/view?usp=sharing

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

Issue 2:
What is the easiest way to draw a long 3D tube that follows a 3D path.

I have a collection of 3D points that represent a route through my world and I want to highlight it. If I draw it as a THREE.Line it comes out 1 pixel wide which is impossible to see, so I want it as a 3D solid.

I tried extruding a shape along a path but that has a couple of issues - the path is defined in 2D and the shape (which is also 2D) doesn't rotate as it is extruded so I get thin points in my solid.
Issue 1:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce/21123/

Failed: BeforeSuite {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:154
Aug 4 06:39:58.074: Failed to setup provider config: Error building GCE/GKE provider: Get https://www.googleapis.com/compute/v1/projects/k8s-jkns-e2e-gce/global/networks?alt=json: net/http: TLS handshake timeout
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:151

Previous issues for this test: #26135 #26236 #27920 #28492 #29970

Issue 2:
We have two sets of labels on internal node object: one is on the object (Minion.Labels), one is on object meta (Minion.ObjectMeta.Labels). We should remove Minion.Labels and fix the conversion properly?
Issue 1:
Pekka Enberg opened SPR-1607 and commented

With Hibernate 3.1, you can set multiple event listeners per type but Spring 2.0 M1 does not support that. Please see the following Hibernate Javadoc: http://www.hibernate.org/hib_docs/v3/api/org/hibernate/cfg/Configuration.html#setListeners(java.lang.String,%20java.lang.Object[])

Affects: 2.0 M1

Issue Links:

#6440 Improve Hibernate3 LocalSessionFactoryBean support for event listeners ("is duplicated by")

Issue 2:
korey shronts opened SPR-7662 and commented

Can multipart request support be added to portlet ResourceRequest processing? Current implementation of DispatcherPortlet only processes multipart requests for ActionRequest(s).

Affects: 3.0.4

Issue Links:

#12565 Handling Multipart request that is not an Action request ? ("is duplicated by")

3 votes, 3 watchers
Issue 1:
Recently updated to 0.12.2 and a checkbox element hooked up to this.props is dynamically updating in the browser. Using the React inspector for Chrome, this.props.item.isActive seems to be toggling fine, but for some reason the changes don't propagate into the DOM. Not sure if this is specific to the update, or I've messed something up that I don't realize.

Here's my render function:

render: function() {
let className = '';
if (this.props.item.isActive) className = 'is-active';

return (
<li className={className}>
<div className="view">
<input
className="toggle"
type="checkbox"
checked={this.props.item.isActive}
onChange={this.toggleActive}
/>
<span>{this.props.item.text}</span>
<button className="destroy-item" onClick={this.destroyItem}></button>
</div>
</li>
);
}

Issue 2:
When using AMD, a component might use React as a dependency. This poses a problem when another instance of React has already manipulated the DOM. The wrong events get fired, or ID collisions occur (Invariant Violation: ReactMount: Two valid but unequal nodes with the same data-reactid: .0).

jsbin here: http://jsbin.com/riqotavoxa/11/edit?js,output

SO here for internet points: http://stackoverflow.com/q/28685857/614523

Google Group post here: https://groups.google.com/forum/#!topic/reactjs/RRDUaF19CM0
Issue 1:
Hi,

I'm trying to make a component where I want to reuse the same projected 'ng-content' but it doesn't seem to be possible. It would be nice if angular could iterate through all the unnamed ng-contents and replace them.

Here is a use case example.

@Component({
selector: 'wt-link',
template: `
<a *ngIf="!isRouteActive() [routerLink]="routerLink">
<ng-content></ng-content>
</a>
<div *ngIf="isRouteActive()">
<ng-content></ng-content>
</div>
`
})
class LinkComponent {
...
}

<wt-link [routerLink]=...>My Link Name</wt-link>

The link is displayed in another way if the route is active and I want more changes than simple CSS.

Is there any workaround?

Issue 2:
version: ng2-beta12

For some reason the order in which templates are defined is causing issues with transclusion.

Doesn't Work for buttons but works for link

<template [ngIf]="href ===''">
<button [ngClass]="cssClassList">
<ng-content></ng-content>
</button>
</template>
<template [ngIf]="href !==''">
<a [ngClass]="cssClassList" href="href">
<ng-content></ng-content>
</a>
</template>

Works for buttons but not for links

<template [ngIf]="href !==''">
<a [ngClass]="cssClassList" href="href">
<ng-content></ng-content>
</a>
</template>
<template [ngIf]="href ===''">
<button [ngClass]="cssClassList">
<ng-content></ng-content>
</button>
</template>
Issue 1:
TypeScript Version:

1.8.7

Code

function func(val: "Test") {
console.log(val);
}

func("Test");

Expected behavior:

Should work normally and print "Test".

Actual behavior:

A compile-time error is reported (highlighting func):

A signature with an implementation cannot use a string literal type.

In my code I had a function that accepted an argument with a type including only two possible string literal values: say "Value1" and "Value2", e.g function func(val: "Value1" | "Value2"), which worked OK. At some point I decided that "Value2" should not yet be supported so I removed it as an option. This left me with a unary string literal type, e.g. function func(val: "Value1"), but the compiler doesn't seem to like it?

Issue 2:
Specialized signatures needing to be compatible with an overload was an artificial requirement due to issues in #943. Now that we've fixed that, we should consider what we're going to do with this rule.

Could we remove it wholesale? That would potentially be a breaking change, but it seems like good one. Basically, the situations you'd run into this would be where you have something like the following...

function doThing(x: "dog"): Dog;
function doThing(x: "cat"): Cat;
function doThing(x: string): Animal;
function doThing(x: string, y?: string): Moose {
}

Where now we'd check if the implementation was assignable to the specialized signatures and give an error. That seems like a good change.
Issue 1:
Ansible Version - 2.0, 2.0.0.2

Module - File

Description - Trying to create directories more than 1 level deep gives following error:

There was an issue creating /dir1/dir2 as requested: 'module' object has no attribute 'EEXISTS'

If i remove dir2, it works. This command use to work with ansible version 1.9.2

Issue 2:
Issue Type:

Bug Report

Component Name:

file module

Ansible Version:

Ansible devel

Ansible Configuration:

Default ansible.cfg

Environment:

Debian, Ubuntu, unprivileged account

Summary:

file module cannot create private directories with mode 0600 more than two levels deep.

Steps To Reproduce:

- hosts: all
become: False

tasks:

- name: Create private directory
file:
path: '~/var/lib/private'
state: 'directory'
mode: '0600'

Expected Results:

Directories are created without issues.

Actual Results:

PLAY ***************************************************************************

TASK [setup] *******************************************************************
ok: [localhost]

TASK [Create private directory] ************************************************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "There was an issue creating /var/local/drybjed/var/lib/private as requested: 'module' object has no attribute 'EEXISTS'", "path": "/var/local/drybjed/var/lib/private", "state": "absent"}

PLAY RECAP *********************************************************************
localhost : ok=1 changed=0 unreachable=0 failed=1
Issue 1:
I have an iOS app.

I have set a launch screen image in xCode.

I set the same image in a container in the main scaffold.

But I see a brief flash of white (or whatever color the scaffold background is) between the launch image and scaffold image. How can I get rid of that?

Issue 2:
I am trying to figure out this blank screen that shows up between the LaunchImage and my app's first screen. Has anyone noticed that. this is the code I wrote for a simple test.

void main() => runApp(
new MaterialApp(
debugShowCheckedModeBanner: false,
title: "Sample App",
theme: new ThemeData(
primarySwatch: Colors.yellow,
),
home: new Scaffold(
backgroundColor: Colors.red,
body:new Container(
child: new Center(
child: new Text (" Sample App ",
style: new TextStyle( fontSize: 20.0, color: Colors.white ),
)
)
)
)
)
);

Here is a video of what happens .,.. see the bklack screen between the launch screen (with logo) and the red screen ... (from 1 secs to about 4 secs.)

https://youtu.be/EpB_AdekLNc

The Android equivalent of this issue is #22007.
Issue 1:
Electron version:1.3.3

Operating system:Windows7

Why in renderer process the webContents.session Event 'will-download' callbacks params DownloadItem Method setSavePath('path') it had no effect. But in main process is all right

// In the renderer process.
const {BrowserWindow} = require('electron').remote
let win = new BrowserWindow()
win.webContents.session.on('will-download', (event, item, webContents) => {
// Set the save path, making Electron not to prompt a save dialog.
item.setSavePath('/tmp/save.pdf')
// Then Electron still pop prompt a save dialog.
})

Issue 2:
Hello,

DownloadItem.setSavePath() is supposed to prevent the save dialog, which is exactly what I need. However, this doesn't work in a renderer process. The save dialog still appears. In fact, the "will-download" event handler is called after the save dialog appeared and had been closed. The code was contracted for this issue:

require("electron").remote.getCurrentWebContents().session.on("will-download",
function(event, item, webContents) {
item.setSavePath(`C:\\Path\\${item.getFilename()}`);
});

Although, this does work in allowing you to cancel requests:

require("electron").remote.getCurrentWebContents().session.webRequest.onBeforeRequest(
function(...) { ... });

Also, DownloadItem.setSavePath() in the main process works as expected. It prevents the save dialog:

let window = new require("electron").BrowserWindow();
...
window.webContents.session.on("will-download", function(event, item, webContents) {
item.setSavePath(`C:\\Path\\${item.getFilename()}`);
});

Further, having a "will-download" event handler function in both processes basically works, because you can successfully use the DownloadItem in the renderer process to print the download status every second.

Unfortunately, I couldn't think of a workaround. I don't think there's any possibility to call a function of the renderer process from the main process synchronously and get a result which, then, could be used for setSavePath() to be called from the main process. Is there still some way to get the setSavePath() logic into the renderer process while this bug persists?
Issue 1:
See http://jsbin.com/taxat/1/

Tested on MacOS 10.8.5, Firefox 26 and Chrome 32.

Using

<div class="hidden-md hidden-lg">XS and SM - via hidden</div>

the content is shown in both xs and sm resolutions. Correct.

But using

<div class="visible-xs visible-sm">XS and SM - via visible</div>

the content is only shown in sm resolution. Not correct, content should show in xs as well.

Probably similar issue with other resolution combinations.

Issue 2:
https://dl.dropboxusercontent.com/u/37682778/error/index.html
Issue 1:
TypeScript Version:

1.8.10

Code

import Symbol from './Symbol';

export interface Iterable<T> {
[Symbol.iterator](): Iterator<T>;
}

In Dojo 2, we provide a shim for Symbol. One of the things we have decided to do as a matter of principal is not modify the global namespace with any of our shims, but provide them as modules where the consumer has to make an explicit dependency on that shim. At runtime, we offload to the native API if present, otherwise we provide replicate functionality.

This pattern works effectively, even when targeting ES6, except for Symbol because of the TypeScript's compiler's insistence that we reference the native one.

Is there a good reason why TypeScript disallows this when targeting ES6? If so, is there any way to provide a transparent shim without modifying the global namespace anyone can think of?

Expected behavior:

No errors when targeting es6.

Actual behavior:

When target is es6 we get the following error:

'Symbol' reference does not refer to the global Symbol constructor object.

Issue 2:
TypeScript Version:

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

Code

// try augmenting the SymbolContructor to have some expected symbol on it.
// in RxJS5's case, it'll be the Symbol.observable symbol from the es-observable spec.
interface SymbolConstructor {
observable: symbol;
}

interface Observablesque<T> {
[Symbol.observable]: () => Subscribable<T>
}

or

// try importing some symbol reference (I get why this might not work)
import {$$observable} from './symbol/observable';

interface Observablesque<T> {
[$$observable]: () => Subscribable<T>
}

Expected behavior:

I should be able to enforce types that have symbols on them, custom or otherwise.

Actual behavior:

I get really confused and go get myself a coffee.
Issue 1:
I'm not hugely familiar with CLI standards, but I don't think I've ever run in to the requirement that --flags precede the positional arguments. I spent a long while trying to get --allow-net to work before realising this was necessary.

deno run --allow-net something.ts vs deno run something.ts --allow-net

Is there any reason not to support both forms?

Alternately, a warning that the arguments were being ignored as invalid would have helped me understand.

Issue 2:
The order of the CLI flags should not be of importance. Check this example

Shouldn't

deno test.ts --config tsconfig.json

be the same as

deno --config tsconfig.json test.ts

or maybe I'm wrong?
Issue 1:
Is there an existing issue for this?

I have searched the existing issues

This issue exists in the latest npm version

I am using the latest npm

Current Behavior

I am unable to install angular CLI after changes --location=global in node module.

Please look i this issue

Expected Behavior

NPM should be installed without any error and support Angular CLI to install

Steps To Reproduce

In this environment...

With this config...

Run '...'

See error...

Environment

npm: 8.11

Node.js: 16.16

OS Name: Window 10

System Model Name:

npm config:

; copy and paste output from `npm config ls` here

Issue 2:
Is there an existing issue for this?

I have searched the existing issues

This issue exists in the latest npm version

I am using the latest npm

Current Behavior

current version of npm (8.11.0, node 16.15.1) writes a warning to STDERR on every command, that is a warning about using deprecated options. The message is...

npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

The message is written to STDERR regardless of whether or not the command run uses the --global or --local options. For example, the command...

npm -v

outputs the message, even though -v is the only option used, and writes to STDERR, even though it states it's purpose to be a warning, not an error, and the command still executes successfully.

The result for my organization is to break our nightly builds. Our builds need to monitor STDERR for REAL build errors, which also use STDERR to capture a variety of aberrant build conditions including security vulnerabilities that are reported back to the build pipeline via STDERR in a script that runs "npm audit" and analyzes the results.

Expected Behavior

IMHO, this warning should only be written if the deprecated options are used, and should be written to STDOUT since it is not an error, just a warning.

Steps To Reproduce

In Windows...

Running node 16.15.1 and npm 8.11.0

Run any npm command, i.e. npm -v

See results...

Environment

npm: 8.11.0

Node.js: 16.15.1

OS Name: Windows 10

System Model Name: Dell Precision 5500 series

npm config:

; "user" config from C:\Users\xxxx\.npmrc

cafile = "C:\\cert\\OGS_int_CA.pem"

; node bin location = C:\Program Files\nodejs\node.exe
; node version = v16.15.1
; npm local prefix = C:\Users\xxxx
; npm version = 8.11.0
; cwd = C:\Users\xxxx
; HOME = C:\Users\xxxx
; Run `npm config ls -l` to show all defaults.
Issue 1:
>>> cv2.__version__
'4.5.1'
>>> cv2.minAreaRect(np.array([[1,1],[1,10],[10,10],[10,1]]))
((5.5, 5.5), (9.0, 9.0), 90.0)

>>> cv2.__version__
'4.2.0'
>>> cv2.minAreaRect(np.array([[1,1],[1,10],[10,10],[10,1]]))
((5.5, 5.5), (9.0, 9.0), -90.0)

Shouldn't the angle information returned be [-90,0)? 4.5.1 is different from 4.2.0

Issue 2:
System information (version)

OpenCV => branch 3.4

Operating System / Platform => Ubuntu 18.04

Compiler => g++ 7.4.0

Detailed description

This issue aims at discussing and inviting suggestions for supporting string data type in Constant layer. Currently, getMatFromTensor only supports few data types from this list.

Also, see #16370 (comment)

Steps to reproduce

Code,

#include<opencv2/dnn.hpp>
#include<vector>
#include<iostream>

int main()
{
const std::string model = "model.onnx";
cv::dnn::Net net = cv::dnn::readNet( model ); // error
}

model.onnx available here.

Apply the commits in #16424 before executing the above code. You will be able to see an error conveying that the tensor is empty and will be thrown by getMatFromTensor.