WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Howdy!

This issue cropped up (or at least I noticed it) around 0.199, but it remains in 0.200.

I have one deprecation warning (which sticks around even in safe mode):

your local styles.less file
/Users/tylersticka/Dropbox (Personal)/Atom/styles.less
Style elements within text editors using the atom-text-editor::shadow selector or the .atom-text-editor.less file extension. If you want to target overlay elements, target them directly or as descendants of atom-overlay elements.

If I click that error, I am taken to what appears to be an empty file:

If I go to the Atom menu and select "Open Your Stylesheet," this is what it looks like:

/*
* Your Stylesheet
*
* This stylesheet is loaded when Atom starts up and is reloaded automatically
* when it is changed.
*
* If you are unfamiliar with LESS, you can read more about it here:
* http://www.lesscss.org
*/

.tree-view {

}

atom-text-editor {

}

atom-text-editor .cursor {

}

I thought maybe I had inherited this stylesheet from an older version, so I tried commenting out everything within it... but the deprecation warning remains.

(Apologies if this issue is duplicated, I swear I searched for it before creating a this one!)

Edit: I should also mention that I have my .atom directory symbolically linked to Dropbox (if you're wondering why my paths aren't simply /Users/tylersticka/.atom).

Issue 2:
There is a theme I use in Brackets that I love, however I prefer to use Atom over Brackets.

What is the easiest way to convert that over? I don't seem to 100% the mark-up of both. Obviously they will have different syntax, so I'm not sure what's the best way to try and convert it.

Any suggestions, please?
Issue 1:
Migrated issue, originally created by Denis Otkidach (@ods)

Test case:

from sqlalchemy import Column, Integer, String, ForeignKey, create_engine
from sqlalchemy.orm import relationship, sessionmaker
from sqlalchemy.ext.declarative import declarative_base

Base = declarative_base()

class DocLink(Base):
__tablename__ = 'DocLink'
id = Column(Integer, primary_key=True)
block_id = Column(ForeignKey('DocLinkBlock.id', ondelete='CASCADE'),
nullable=False)
block = relationship('DocLinkBlock',
primaryjoin='DocLink.block_id==DocLinkBlock.id')
ref_url = Column(String(250), nullable=True)
ref_doc_id = Column(ForeignKey('Doc.id'))
ref_doc = relationship('Doc', primaryjoin='DocLink.ref_doc_id==Doc.id')

class DocLinkBlock(Base):
__tablename__ = 'DocLinkBlock'
id = Column(Integer, primary_key=True)
doc_id = Column(ForeignKey('Doc.id', ondelete='CASCADE'), nullable=False)
doc = relationship('Doc')
links = relationship(DocLink, cascade='all, delete-orphan')

class Doc(Base):
__tablename__ = 'Doc'
id = Column(Integer, primary_key=True)
link_blocks = relationship(DocLinkBlock, cascade='all, delete-orphan')

engine = create_engine('sqlite://', echo=True)
Base.metadata.create_all(engine)
session = sessionmaker(bind=engine)()

ref_doc = Doc(id=1)
session.add(ref_doc)
session.commit()

doc = Doc(
id=2,
link_blocks=[
DocLinkBlock(
id=1,
links=[
DocLink(
id=1,
ref_url='url',
ref_doc=ref_doc,
),
],
),
],
)
session.add(doc)
session.commit()
assert doc.link_blocks[0].links[0].ref_url=='url'
assert doc.link_blocks[0].links[0].ref_doc is ref_doc

doc.link_blocks = [
DocLinkBlock(
id=1,
links=[
DocLink(
id=1,
ref_url=None,
ref_doc=None,
),
],
),
]
session.commit()
assert doc.link_blocks[0].links[0].ref_url is None
assert doc.link_blocks[0].links[0].ref_doc is None # Fails

There is no such problem when DocLinkBlock.links is updated directly (no nested collections).

Issue 2:
Migrated issue, originally created by Denis Otkidach (@ods)

New object with the same ID as existing one implicitly merged via cascade rules has old value of relationship property after the commit when the new value is None.

In short:

doc.doc_links = [DocLink(id=doc_link_id, link=None)]
session.commit()
assert doc.doc_links[0].link is None # fails

Full test is attached (test3 is the test case that fails).

Attachments: sa_merge_relation.py | 3060.patch
Issue 1:
The type error makes this segfault:

use std;
import std::option::*;

fn main() {
let t[int] x = none;
x = 5;
}

Looks like stack overflow. The interesting part of the backtrace:

#1019 0x080df952 in middle::ty::fold_ty ()

#1020 0x080f985f in middle::ty::unify::fixup_vars::subst_vars ()

#1021 0x0827bc13 in middle::ty::unify::fixup_vars::subst_vars::thunk3323 ()

#1022 0x080e3e7f in middle::ty::fold_ty ()

#1023 0x080df952 in middle::ty::fold_ty ()

#1024 0x080f985f in middle::ty::unify::fixup_vars::subst_vars ()

#1025 0x0827bc13 in middle::ty::unify::fixup_vars::subst_vars::thunk3323 ()

#1026 0x080e3e7f in middle::ty::fold_ty ()

#1027 0x080df952 in middle::ty::fold_ty ()

#1028 0x080f985f in middle::ty::unify::fixup_vars::subst_vars ()

#1029 0x0827be33 in middle::ty::unify::fixup_vars::thunk3333 ()

#1030 0x080e3e7f in middle::ty::fold_ty ()

#1031 0x080f9bb7 in middle::ty::unify::fixup_vars ()

#1032 0x08137e5a in middle::typeck::demand::full ()

#1033 0x0814097a in middle::typeck::check_expr ()

#1034 0x08145d44 in middle::typeck::check_expr ()

#1035 0x0813fdca in middle::typeck::check_expr::check_then_else ()

#1036 0x08145e0f in middle::typeck::check_expr ()

#1037 0x081530aa in middle::typeck::check_block ()

#1038 0x08146df7 in middle::typeck::check_expr ()

#1039 0x081530aa in middle::typeck::check_block ()

#1040 0x08146df7 in middle::typeck::check_expr ()

#1041 0x081530aa in middle::typeck::check_block ()

#1042 0x0813f85a in middle::typeck::check_expr::check_for_or_for_each ()

#1043 0x08146170 in middle::typeck::check_expr ()

#1044 0x08152ee7 in middle::typeck::check_block ()

#1045 0x08154ee0 in middle::typeck::check_fn ()

#1046 0x08156bda in middle::typeck::check_item ()

#1047 0x0829730e in middle::typeck::check_crate::thunk5452 ()

#1048 0x080fce01 in middle::walk::walk_item ()

Issue 2:
We can infinite loop if we try to unify e.g. T with option[T]. Fixing this requires implementing the occurs check. Off the top of my head, I can't think of any cases in which we'd actually trip this, but it's theoretically possible.

Tim thinks this may also be the cause of segfaulting on infinitely interior tags:

tag t1 {
a(int);
b(@t1);
}
Issue 1:
Version

2.6.11

Reproduction link

https://jsbin.com/lurayuxofo/edit?html,js,console,output

Steps to reproduce

Include inline SVG with some styles within a Vue instance

Init vue instance

What is expected?

SVG to be styled according to the style element

What is actually happening?

Vue is giving a warning "[Vue warn]: Templates should only be responsible for mapping the state to the UI. Avoid placing tags with side-effects in your templates, such as <style>. " and also stripping the style element so the SVG is appearing with no style.

I am opening the exact same issue as this one because it's been ignored and this should be fixed by now.

It's been plaguing vue since 2016.

The fix so far:

In the meantime, this can be fixed by adding this attribute xmlns:svg="http://www.w3.org/2000/svg" to your <svg> tag and writing your style as this : <svg:style type="text/css">

Issue 2:
Duplicates #3957

Vue.js version

2.1.8

Reproduction Link

https://jsfiddle.net/CinKon/qwaacqon/1/

Steps to reproduce

Open DevTools. Console-Error:

[Vue warn]: Property or method "myText" is not defined on the instance but referenced during render. Make sure to declare reactive data properties in the data option. (found in root instance)

What is Expected?

Props that are imported via mixin should render without problems.

What is actually happening?

Console throws error, prop is not transmitted.
Issue 1:
Piping a numpy array as binary data to another process works in Python2, but in Python3 the following snippet results in "OSError: first argument must be a string or open file". I tested with Python 3.4.0.

import subprocess, numpy
wc = subprocess.Popen(["wc"], stdin=subprocess.PIPE)
numpy.eye(5).tofile(wc.stdin)

Issue 2:
I am trying to write a numpy array data to a pipe opened using subprocess.Popen in Python 3.4 and numpy 1.10.4. Here is the code:

import numpy
import subprocess

myArray = numpy.arange(10000).reshape([100,100])

# use xpaset to communicate with ds9
fullCmd = "xpaset DS9Test array [xdim=100,bitpix=64,arch=littleendian,ydim=100]"

mp = subprocess.Popen(
fullCmd,
shell = True,
stdin = subprocess.PIPE,
stdout = subprocess.PIPE,
stderr = subprocess.STDOUT,
bufsize = 0
)

myArray.tofile(mp.stdin)

Unfortunately I am getting the following error:

File "/Users/avigan/Work/HC-HR/FTS/test.py", line 25, in <module>
myArray.tofile(mp.stdin)

OSError: first argument must be a string or open file

However, if I do:

In [64]: print(mp.stdin)
<_io.FileIO name=71 mode='wb'>

I interpret this as a sign that the file descriptor is indeed open.

The same code was working fine in Python 2.7, so I guess it's linked to Python 3+ and the current version of numpy.
Issue 1:
Even if this example may look silly, it's the result of the simplification of a more complex structure.

There should be no reason for these constructs not to compile, should it ?

use std::sync::RwLock;

fn main() {
let a = RwLock::new(RwLock::new(String::new()));

// Fails : a does not live long enough
let len = a.read().unwrap().read().unwrap().len();

// Fails : b does not live long enough
let len = { let b = a.read().unwrap(); b.read().unwrap().len() };

// Compiles
let len = { let b = a.read().unwrap(); let c = b.read().unwrap(); c.len() };
}

The full error message for the first construct does not really show what the problem might be:

<anon>:5:15: 5:32 error: borrowed value does not live long enough
<anon>:5 let len = a.read().unwrap().read().unwrap().len();
^~~~~~~~~~~~~~~~~
<anon>:5:5: 5:54 note: reference must be valid for the destruction scope surrounding statement at 5:4...
<anon>:5 let len = a.read().unwrap().read().unwrap().len();
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<anon>:5:5: 5:54 note: ...but borrowed value is only valid for the statement at 5:4
<anon>:5 let len = a.read().unwrap().read().unwrap().len();
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<anon>:5:5: 5:54 help: consider using a `let` binding to increase its lifetime
<anon>:5 let len = a.read().unwrap().read().unwrap().len();
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error: aborting due to previous error

Issue 2:
Spawned off of #21022, #21972; see also #21657.

Tracking order of destruction for r-value temporaries would (probably) allow us to resume writing code like this from RFC 769:

for line in old_io::stdin().lock().lines() {
...
}

which is currently disallowed because the region inference system does not know that the temporary yielded by stdin() will outlive the temporary from stdin().lock().

(But note that it might also have fallout, potentially worse than that of #21657)
Issue 1:
After implementing a file PowerRename, can the app window be given an option to stay open so that multiple renames can be done on the files without re-opening the app,

Issue 2:
Environment

Windows build number: Microsoft Windows [Version 10.0.17763.864]
PowerToys version: v0.13.0
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce

After long time of running PowerToys as background (not using any features of PowerToys at all), number keyboard above querty (not keypad; keypad works fine) goes not working at all. If I press Shift + number to type special character like !@#$%, it delays like few second and special character is typed, yet number will never be typed.

I even didn't notice PowerToys causes problem; I restart computer and work fine for some hours, yet problem arises again; I killed recent installed process one by one and find PowerToys was source of problem.

Expected behavior

number keyboard above querty (not keypad; keypad works fine) must not be interrupted and continued to work.

Actual behavior

number keyboard goes dumb.

Screenshots
Issue 1:
It seems like this was broken as a result of the recent change to make newtypes structs immediate in certain cases.

struct TestNode(@int);

fn mm(_x: &TestNode) {}

fn main() {
let x = &TestNode(@21);
mm(x);
}

% rustc foo.rs
error: internal compiler error: drop_ty_immediate: non-box ty

Issue 2:
Minimal test case:

struct Wrapper(~str);

impl Wrapper {
pub fn new() -> Wrapper {
Wrapper(~"Bob")
}

pub fn say_hi(&self) {
println(fmt!("hello %s", **self));
}
}

impl Drop for Wrapper {
fn drop(&mut self) {}
}

fn main() {
{
// This runs without complaint.
let x = Wrapper::new();
x.say_hi();
}
{
// This fails to compile.
// error: internal compiler error: drop_ty_immediate: non-box ty
Wrapper::new().say_hi();
}
}

I originally ran accross this when wrapping a *T, but it also fails when I try to wrap int and other numeric types, bool, Option<T>, ~T, and other structs that also wrap a single value of those types.
Issue 1:
#11045 contained a still-extant announcement of removal of deprecated functionality by 1.7; let's do it for 1.9 at least.

CC @rlucas7

Issue 2:
When working on porting some scipy.special functions to CuPy, I noticed that there was a scheduled deprecation for SciPy 1.7 that has not yet been carried out. Specifically, the unsafe double->int casting for the n or k inputs to binomial distribution functions bdtr, bdtrc and bdtri leads to the following warning:

scipy/scipy/special/_legacy.pxd

Lines 39 to 43
in
b5d8bab

cdef inline void _legacy_deprecation(char *func_name, double x, double y) nogil:

with gil:

PyErr_WarnEx_noerr(DeprecationWarning,

"non-integer arg n is deprecated, removed in SciPy 1.7.x",

1)

I thought about making a PR to complete the deprecation, however, I am not sure how best to proceed with that as it seems inconsistent with other functions in that same file. For example the functions related to negative binomial distributions (nbdtr, nbdtrc and nbdtri) and others instead raise a RuntimeWarning and do not indicate that the unsafe casting is deprecated. Shouldn't the approach for bdtr and nbdtr be the consistent? Please advise.
Issue 1:
I tried using the @types/xxxx package and had problems.

I tried using the latest stable version of tsc. https://www.npmjs.com/package/typescript

I have a question that is inappropriate for StackOverflow. (Please ask any appropriate questions there).

Mention the authors (see Definitions by: in index.d.ts) so they can respond.

Authors: @yortus @baxtersa @marvinhagemeister @bcherny

I would like to have/add types for at least some of the @babel/* packages but before I start creating PR(s), I want to get other peoples opinions.

@babel/core in its current state can be just an alias to/copy of babel-core for now. Can I just do something like this or do I need to copy/paste it?

// @babel/core
export * from "babel-core";

The version of babel-types on NPM is 6 but the version mentioned in the types is 7. The version of @babel/types is 7 so what's going on here? Also @babel/core types will depend on @babel/types types or should I just import babel-types?

I am not really sure on how to move forward so I like to get some thoughts on this.

Issue 2:
I want to talk about react-router/history.d.ts.

The authors of that type definition are cc/ @sergey-buturlakin @ngbrown

We have history/history.d.ts. Why isn't react-router using this?

This file was added by #6073, but history/history.d.ts predates that PR. I don't see a reason why it was duplicated.

Can we get rid of react-router/history.d.ts? Unfortunately the two files seem to have diverged, so this won't be easy. But they reference the same project, and have the same authors listed.
Issue 1:
Hi, I got a small issue using horizontal definition lists. When a definition description <dd> is empty, the next <dd> (if any) takes the place of the first. See in action: http://jsfiddle.net/2R2Pb/1

This happens using Firefox and Bootstrap 2.3.1.

Issue 2:
When an empty or self-closing <dd> tag is used in a horizontal <dl>, the <dd> tags following it are mis-aligned with the matching <dt> tags.

<dl class="dl-horizontal">
<dt>Title 1</dt>
<dd>Description 1</dd>

<dt>Title 2</dt>
<dd></dd>

<dt>Title 3</dt>
<dd>Description 3</dd>
</dl>

Here is a jsFiddle: http://jsfiddle.net/xjQX3/

In the above example, "Description 3" will sit beside "Title 2". It should sit beside "Title 3". If the <dl> is not horizontal, then they appear as expected.
Issue 1:
Electron version: v1.3.5

Operating system: win7 x64

I have created a simple example here: there are only two files in the directory: package.json and main.js. I'm sured that they are saved by UTF-8 encoding.

There are only two keys in package.json: name and main, just like this

{
"name":"simple-example",
"main":"main.js"
}

the main.js has only one line:

console.log("中文")

When I run electron . under that directory, the output on console is not right.

While if I run node main.js, I can see the expected result:

I think there are something wrong with encoding, can anyone here tell me how to fix it and why?

Issue 2:
I noticed that I cannot print characters such as 'ρ' or 'β' from Electron to the console on Windows (works fine on Linux and OS X). I tried this using the default command prompt and power shell; also made sure both terminals were printing the characters otherwise (works fine with node -e "console.log('β')"). When printing from Electron it does not work (tested in both Main and Renderer with console.log and process.stdout.write).

Possibly related to #2311

Electron version: 1.1.3

Operating system: Windows 8.1
Issue 1:
I'm submitting a feature request

The current behavior is that @query don't return inherited components

The expected behavior should be that the injected Query will find the Inherited components .

The current behavior is not making any sense .

I want to create components that inherit base component, and I want to find them in my

Component.

Angular version: 2.0.0-beta.5

Browser: all

Language: TypeScript

Issue 2:
Assuming the following markup:

<my-list>
<my-item>...</my-item>
<my-fancy-item>...</my-fancy-item>
<my-super-fancy-item>...</my-super-fancy-item>
<my-item>...</my-item>
</my-list>

where my-item, my-fancy-item and my-super-fancy-item are directives such that:

class MyItem {
...
}

class MyFancyItem extends MyItem {
...
}

class MySuperFancyItem extends MyItem {
...
}

I would like to query all directives of type MyItem like so:

@ContentChildren(MyItem) allItems: QueryList<MyItem>;

and allItems should contain all instances of my-item, my-fancy-item and my-super-fancy-item (as all of them are passing the foo instanceOf MyItem test.

cc.: @mhevery @tbosch
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.3

Operating System version: win10

Java version: 1.8

Steps to reproduce this issue

场景：

1、zookeeper针对dubbo节点设置了访问控制；

2、dubbo使用curator作为zk客户端；

3、当我从2.6.3升级到2.7.3之后发现，服务无法在zookeeper里注册，异常提示： NoAuth

问题分析：

之后通过文档，发现dubbo 2.7 之后增加了配置中心和元数据中心，并默认采用服务注册中心的配置；但是对于username/password属性并没有继承使用； 导致服务注册过程中提示没有权限。

疑问？

配置中心和服务注册中心的配置是独立的， 但实际上配置中心的如果不设置zk的用户密码，却会导致服务注册失败；

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

[1] I have checked the FAQ of this repository and believe that this is not a duplicate.

Pls. provide [GitHub address] to reproduce this issue.

http://dubbo.apache.org/en-us/docs/user/references/registry/zookeeper.html

Reference from above url as below:

Description on registration procedure:

When service provider boots up: write service URL address under directory /dubbo/com.foo.BarService/providers

When service consumer boots up: subscribe to /dubbo/com.foo.BarService/providers for provider's URL addresses. At the same time, write consumer's URL address under /dubbo/com.foo.BarService/providers.

Expect:

When service consumer boots up: subscribe to /dubbo/com.foo.BarService/providers for provider's URL addresses. At the same time, write consumer's URL address under /dubbo/com.foo.BarService/consumers.
Issue 1:
In Symfony 2.7 only, works fine in 2.6.*

$builder->add('typeVoie', 'entity', array(
'class' => 'MyBundle:TypeVoie',
'query_builder' => function(EntityRepository $er) {
return $er->createQueryBuilder('u')
->orderBy('u.weight', 'DESC');
},
'property' => 'typeVoieLower',
'label' => 'Type de voie',
'label_attr' => array('id' => 'label_typevoie'),
'required' => false
)

Despite the option required => false the form does not accept null values and returns

SQLSTATE[22P02]: Invalid text representation: 7 ERROR: invalid input syntax for integer: ""

The entity definition has the option nullable=true set on this field.

Thanks

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:
Hello,

I would like to know if it's possible to have a prototype with multiple reference inside of it's definition.

service: ServiceTest
version: 7

request:
class: MyModel
properties:
# other conf..
Field3:
type: collection
field: fieldCollection
properties:
Field1:
type: string
field: fieldString
Field2:
type: collection
field: fieldCollection
properties:
Field1:
type: boolean
field: fieldBoolean
Field2:
type: collection
field: fieldCollection
properties:
# ...

I start to write my Configuration but i don't know if it's possible to do what i want.

$rootNode
->children()
->scalarNode('service')
->isRequired()
->end()
->scalarNode('version')
->isRequired()
->end()
->arrayNode('request')
->isRequired()
->children()
->scalarNode('class')->end()
->arrayNode('properties')
->children()
->useAttributeAsKey('name')
->prototype('array')
->children()
->enumNode('type')
->values(array(
ServiceProperty::TYPE_STRING,
ServiceProperty::TYPE_INTEGER,
ServiceProperty::TYPE_BOOLEAN,
ServiceProperty::TYPE_COLLECTION
))
->end()
->scalarNode('field')->isRequired()->end()
// Refers to the prototype
->end()
->end()
->end()
->end()
->end()
->end()
->end()
;

Issue 2: