WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
VSCode Version: 1.0.0

OS Version: Ubuntu 16.04 LTS

Steps to Reproduce:

Click into a text line

Press Ctrl + Shift + Alt + UpArrow or Ctrl + Shift + Alt + DownArrow

Expected result:

line is duplicated up/down

Actual result:

nothing happens

Workaround:

run the command from the command palette

Issue 2:
Problem

When authoring a JSON file, such as a Microsoft Azure Resource Manager (ARM) JSON Template, the Visual Studio Code editor is showing all of the available properties for an object, instead of only showing the properties that the user has not yet specified.

# Expected Result

I would naturally expect that the Visual Studio Code Intellisense returns only the JSON properties that the user hasn't defined yet. I shouldn't be prompted to insert a duplicate key.

Cheers,

Trevor Sullivan

Microsoft MVP: PowerShell

http://trevorsullivan.net

http://twitter.com/pcgeek86
Issue 1:
Sorry, low quality bug report here but I'm working to a deadline.

Browser: Chrome latest

Visit this page: http://getbootstrap.com/components/

Its currently using Bootstrap 3.2.0

On my desktop 1920*1080, on a windows 8 pc, maximised window.

If I scroll down to the end of the page using either of these two methods:

1/ press END, then scroll up one mouse wheel and back down again OR

2/ manually drag the scrollbar to the end of the page

you will notice that the affix plugin "pops" and goes off the top of the page. I assume this may be intended behaviour as its being left behind as you go beyond its affix zone.

If you press HOME after that it jumps back to the top of the page but the affix is now in the wrong place and appears to be affixed to the top of window instead of its original affix top location. Scrolling at all fixes the issue and it pops back to its affix start location.

Obscure, yes. Browser issue, probably. Close the issue if you like, I'll only be mildly offended :)

I think that its actually breaking both ways, if you END down it goes further than it should. Then if you get it into my scroll bug location and HOME it does the same bug in reverse?

Issue 2:
It is possible to go to the top of the page, without the plugin assigning affix-top classname.

Here's an example:

It's really easy to reproduce by pressing end and then home buttons.
Issue 1:
remove the quote syntax from extern crate, require an identifier to be used instead - #23546

Prevent duplicate uploads of foo-bar and foo_bar to crates.io change

Automatically translate - to _ in Cargo for passing the --extern flag - rust-lang/cargo#1443

As an interim step, the compiler should continue to accept extern crate "foo-bar" as ... both in terms of quotes and in terms of matching the identifier foo_bar as well. This should help reduce the breakage a little.

triage: P-backcompat-lang (1.0 beta)

Issue 2:
We recently made most, but not all RNGs clonable. ISTM that the use cases for this are quite limited, and it creates a big opportunity for making mistakes by duplicating random numbers in scenarios where that could be a security risk (imagine accidentally deriving clone on a secure rng).

cc @aturon
Issue 1:
by ask@develooper.com:

Similar to the new TLS field with the tls.ConnectionState in the http.Response struct
it'd be useful to get access to some connection information.

For my use case I was missing the IP the client connected to (RemoteAddr); I am not sure
if there's other information in the current connection API that would be useful to
expose.

Issue 2:
Wishlist bug for what net/http would look like if we could make backwards-incompatible
changes.

Anything goes.

I'll start:

* Handler (http://golang.org/pkg/net/http/#Handler) currently takes a pointer to a 208
byte Request struct.

* The Request struct (http://golang.org/pkg/net/http/#Request) has all its fields
publicly exposed, most of which require memory allocation:

-- Method
-- URL (itself 104 bytes, with a bunch of strings requiring allocation)
-- Header map + slices + strings (even if never accessed)
-- TransferEncoding slice (even if not accessed)
-- Host string (even if not accessed)
-- RemoteAddr string (even if not accessed)
-- RequestURI (even if not accessed)
-- TLS state struct (even if not accessed)

For a lightweight handler that doesn't touch anything (say, serves some static content
from memory), this means we can't do any better than generating ~1KB of garbage per
request.

I'd prefer to make a ServerRequest interface with accessor methods which can generate
needed data on demand.

This would also simplify our docs on our doubly-abused-in-different-ways *Request, which
contains documentation gems like:

// PostForm contains the parsed form data from POST or PUT
// body parameters.
// This field is only available after ParseForm is called.
// The HTTP client ignores PostForm and uses Body instead.
PostForm url.Values

If we had byte views (issue #5376), I would also say that most fields in the
ServerRequest, URL, Header, and FormValues are all byte views with validity scoped to
the duration of the http.Handler call, instead of strings.
Issue 1:
In settings, on the "Themes" tab, when I type anything into the box labelled "Filter themes by name," all themes are filtered out, even if I type in strings that appear within the names of themes I've installed, and even if I type in the exact name of the theme.

For example, suppose I was trying to quickly get to "seti-ui." If I type in seti, nothing appears. If I type in seti-ui, nothing appears. As far as I can tell, the filter box filters out every theme, no matter what you type into it.

Running at Atom 0.209.0 on OS X 10.10.4.

Issue 2:
All packages are disappear and even if I clear the filter field they don't appears.

win 10; atom 0.207
Issue 1:
ShardingRule::

private boolean isShardingColumn(final ShardingStrategyConfiguration shardingStrategyConfig, final String columnName) {

... ...

// Case can be ignored here，May cause all tables to be manipulated！Insert statement encountered. All tables were inserted

return ((ComplexShardingStrategyConfiguration) shardingStrategyConfig).getShardingColumns().contains(columnName);

}

Issue 2:
Please answer these questions before submitting your issue. Thanks!

开源不易，我们希望将精力放在完成新功能和解决有价值的问题上，为了让大家的配合更具有效率，请填写以下列出的全部问题

Which version of Sharding-Sphere do you using?（您使用的Sharding-Sphere版本为？）

3.0.0.M1 jdk 1.7

Expected behavior （您预期的结果是）

正常运行

Actual behavior （实际运行的结果是）

org.codehaus.groovy.reflection.ClassInfo 严重占用内存，导致内存溢出

Steps to reproduce the behavior （可重现问题的操作步骤）

使用 InlineShardingStrategy 不断调用即可观察到栈内存的增长

Please provide the reproduce example codes (such as github link)，otherwise we will label the issue as Invalid and close it.（为了节省复现问题的时间，请务必提供可重现的代码，否则我们会将issue直接标记为invalid并关闭）

https://github.com/sharding-sphere/sharding-sphere-example InlineShardingStrategy demo 不断调用即可

Code should based on https://github.com/sharding-sphere/sharding-sphere-example

（代码请基于 https://github.com/sharding-sphere/sharding-sphere-example）
Issue 1:
Elasticsearch version: 5.0.0-rc1

Plugins installed: none

JVM version: jdk1.8.0_101

OS version: Windows 2012 R2 64-bit

Description of the problem including expected versus actual behavior:

Cannot install the service.

I have the following environment variables set:

JAVA_HOME: C:\Program Files\Java\jdk1.8.0_101

ES_HEAP_SIZE: 8g

I have verified that jvm.options have the following lines commented out:

## -Xms8g
## -Xmx8g

I run the following: .\elasticsearch-service.bat install elasticsearch-5.0.0-rc1

I get the following output:

Error: encountered environment variables that are no longer supported
Use jvm.options or ES_JAVA_OPTS to configure the JVM
ES_HEAP_SIZE=8g: set -Xms8g and -Xmx8g in jvm.options or add "-Xms8g -Xmx8g" to ES_JAVA_OPTS

I delete ES_HEAP_SIZE and add ES_JAVA_OPTS: "-Xms8g and -Xmx8g" (without quotes)

I run the command again and get the following:

Installing service : "elasticsearch-5.0.0-rc1"
Using JAVA_HOME (64-bit): "C:\Program Files\Java\jdk1.8.0_101"
thread stack size not set; configure via C:\elasticsearch-5.0.0-rc1\config\jvm.options or ES_JAVA_OPTS

I delete ES_JAVA_OPTS and edit jvm.options:

-Xms8g
-Xmx8g

Run again and get the following:

Installing service : "elasticsearch-5.0.0-rc1"
Using JAVA_HOME (64-bit): "C:\Program Files\Java\jdk1.8.0_101"
thread stack size not set; configure via C:\elasticsearch-5.0.0-rc1\config\jvm.options or ES_JAVA_OPTS

I leave jvm.options alone and create ES_JAVA_OPTS again. Now it see duplicate settings:

Installing service : "elasticsearch-5.0.0-rc1"
Using JAVA_HOME (64-bit): "C:\Program Files\Java\jdk1.8.0_101"
duplicate min heap size settings found

Issue 2:
Elasticsearch version: 5.0.2

Plugins installed: []

JVM version: 1.8

OS version: Ubuntu 14.04

Description of the problem including expected versus actual behavior:

Tried to install 5.0.2 after the release of 5.1.1 and it seems to be removed from the repos.

Steps to reproduce:

Try to install 5.0.2 from repos

Provide logs (if relevant):

root@packer-virtualbox-iso-1461948451:~# apt-get install elasticsearch=5.0.2
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '5.0.2' for 'elasticsearch' was not found

The repos are correct;

root@packer-virtualbox-iso-1461948451:~# cat /etc/apt/sources.list.d/elasticsearch.list
deb https://artifacts.elastic.co/packages/5.x/apt stable main
Issue 1:
ReactDOM and React are good separation of concerns. However, except for special cases, React applications almost always require the ReactDOM as well. The special cases can obviously have their own builds which can remove the unnecessary dependency. But React officially should serve a single library which includes the ReactDOM as a single resource. It absolutely makes no sense for an extra network request for a library that's 900 bytes gzipped.

This cost is even multiplied, since the official CDNs seem to already have a redirection in place. At the moment of filing this issue, a request to https://fb.me/react-0.14.7.min.js ends up with 301 to https://fbcdn-dragon-a.akamaihd.net/hphotos-ak-xfa1/t39.3284-6/12624086_185960608428874_474870377_n.js

And similar redirects for ReactDOM. That's 4 requests in place of what could be a 2. 2 requests, for a mere 900 bytes. In other words, taking the overhead of TCP/IP and HTTP, an overhead of nearly half a kilobyte with about 600ms of latency (in my geographic location) for a mere 900 bytes. Now, add to the fact that the gzip would probably nullify that 900 bytes almost entirely if its included as a part of the other 70kb file, due to binary compression.

I'm honestly quite surprised why it was even decided to separate them (Not as libraries, but in terms of deployment).

Issue 2:
I was talking with a new React user in IRC, and they were having trouble understanding the ES6 in the docs. I think using ES6 in the docs is a good idea, but what about giving the reader more ability to understand the code?

Concept:

Maybe take text from Babel's ES6+ Guide and modify it a bit to fit the surrounding content.

This could be done across the site, but it's most important in the tutorial.
Issue 1:
Q
A

Bug report?
yes

Symfony version
2.7

commit faf671d

commit c891413

These commits clear $this->refs inside the Symfony\Component\Yaml\Parser\parse method and references to anchors in previously parsed files don't work. Removing the lines solves the problem and configurations based on such overrides/includes work as expected.

Please, make a revision of the commited code and put some proper unit tests for such configurations.

Issue 2:
Hi there,

At work we wanted to check if a date (in a form) was greater than "now". The problem was that we were using annotations in our entity for the validation and (apparently) there is no "simple" way to do so.

The solutions which came to my mind were:

Use the "assert greater than" validator directly in the form type ($builder->add('foo', 'bar', array('constraints' => new \DateTime()))

Use the annotation @Assert\True on my date field and implement an isDateValid method

Create a dedicated annotation

Create an @DateTime annotation which would extends from \DateTime and could be used everywhere (in my case : @Assert\GreaterThan(value = @DateTime))

I've chosen to implement the latest of my proposal (@DateTime), it works well (IMO it is flexible, clean and reusable) and I think it could be a very good idea to implement it in symfony.

What do you think about it?

If you feel like it, I can share my work.
Issue 1:
http://pandas.pydata.org/developers.html

https://mail.python.org/mailman/listinfo/pandas-dev

Examples:

https://en.wikipedia.org/wiki/Responsible_disclosure

https://docs.djangoproject.com/en/dev/internals/security/#reporting-security-issues

Issue 2:
Part of the tidelift setup. In numpy/numpy#13475 / numpy/numpy#13485, NumPy decided to just link to https://tidelift.com/docs/lifting/security. That should suffice to us.

Only thing to decide is who all gets notified with these reports.
Issue 1:
Currently documentation builds emit many warnings. We should resolve them, then turn on -WT --keep-going to report warnings as errors so that new build problems are caught as they are created.

cc @ezyang @zou3519

Issue 2:
I've seen a multitude of warnings in the docs build that reflected incorrect formatting and/or broken docs in the docs build. We should enforce a "no-warnings-allowed" situation for the docs.

cc @ezyang @zou3519
Issue 1:
When using Deno.compile (v1.1.1), the output doesn't have the import paths with the correct ext

Compile config:

const [messages, result] = await Deno.compile(input, undefined, {
target: 'es6',
module: 'es6',
lib: ['dom', 'esnext'],
})

Source:

Output:

Issue 2:
Problem

Deno.compile() does not convert local import URLs from .ts extension to .js extension, making it impossible to use inside browser and Node.js.

Steps to reproduce

Run this file (deno run https://gist.githubusercontent.com/KSXGitHub/c94a9d7eb8e976f1126b4b9dfeba0497/raw/004a9ddb6872b9a2f05506f13f3efdfd6edd6d69/tmp.ts).

Expected behavior

All local import URLs in output JS files should have .js extension.

// foo.js should look like this
export * from "./bar.js";

All local import URLs in output TypeScript definition files (.d.ts) should have no extension.

// foo.d.ts should look like this
export * from "./bar";

Actual behavior

All local import URLs are preserved, which is incorrect.
Issue 1:
by an2048:

What steps will reproduce the problem?
Build and run the drawing example (or any other) from the Walk project
(https://github.com/lxn/walk)

What is the expected output?
The program should not panic.

What do you see instead?
throw: too many callback functions

runtime.throw+0x42 /go/src/pkg/runtime/runtime.c:102
runtime.throw(0x931e5b, 0x5)
runtime.compilecallback+0xe4 /go/src/pkg/runtime/windows/thread.c:377
runtime.compilecallback(0x6462ec, 0x4ffd87, 0x10f39501, 0x4ffab0)
syscall.NewCallback+0x39 /go/src/pkg/runtime/windows/syscall.c:26
syscall.NewCallback(0x6462ec, 0x4ffd87, 0x6462ec, 0x4ffd87)
walk.init·2+0xff
C:/devel/projects/eclipse_workspace/walk/src/pkg/walk/webview_ioleinplaceframe.go:37
walk.init·2()
walk.init+0x597 C:/devel/projects/eclipse_workspace/walk/src/pkg/walk/action.go:233
walk.init()
main.init+0x78
C:/devel/projects/eclipse_workspace/picos-order/src/cmd/picos-order/orderpoolpage.go:24
main.init()
runtime.mainstart+0x5 386/asm.s:91
runtime.mainstart()
runtime.goexit /go/src/pkg/runtime/proc.c:178
runtime.goexit()
----- goroutine created by -----
_rt0_386+0xbf 386/asm.s:80

Which compiler are you using (5g, 6g, 8g, gccgo)?
8g

Which operating system are you using?
Windows XP SP3

Which revision are you using? (hg identify)
3418f22c39eb weekly/weekly.2011-06-02

Please provide any additional information below.
The problem was introduced by 95553202a7a8 - runtime: do not garbage collect windows
callbacks

Issue 2:
-- from code review 5574063: net: disable SO_REUSEADDR and SO_REUSEPORT on openbsd
(issue #5574063) on golang-dev

Sorry, I should have been more specific here. The problem is not due
to use of SO_REUSEADDR on the listening socket - the issue is that we
are setting it on all sockets. As a result, the client performs a
connect() which results in the allocation of a randomised port number
- since SO_REUSEADDR/SO_REUSEPORT are enabled the port number is
permitted to already be in use and the normal duplication checks are
not performed. We then attempt to establish a TCP connection using
this already in use port number, which fails:

19425 test.out CALL socket(PF_INET,SOCK_STREAM,IPPROTO_IP)
19425 test.out RET socket 10/0xa
19425 test.out CALL fcntl(0xa,F_SETFD,FD_CLOEXEC)
19425 test.out RET fcntl 0
19425 test.out CALL setsockopt(0xa,SOL_SOCKET,SO_REUSEADDR,0xf84019ea00,0x4)
19425 test.out RET setsockopt 0
19425 test.out CALL setsockopt(0xa,SOL_SOCKET,SO_REUSEPORT,0xf84019ea08,0x4)
19425 test.out RET setsockopt 0
19425 test.out CALL setsockopt(0xa,SOL_SOCKET,SO_BROADCAST,0xf84019ea10,0x4)
19425 test.out RET setsockopt 0
19425 test.out CALL fcntl(0xa,F_GETFL,0)
19425 test.out RET fcntl 2
19425 test.out CALL fcntl(0xa,F_SETFL,0x6<O_RDWR|O_NONBLOCK>)
19425 test.out RET fcntl 0
19425 test.out CALL connect(0xa,0xf840186768,0x10)
19425 test.out STRU struct sockaddr { AF_INET, 127.0.0.1:43658 }
19425 test.out RET connect -1 errno 48 Address already in use

The other (and probably better) solution is to only set
SO_REUSEADDR/SO_REUSEPORT on sockets that will be listening, probably
via the addition of a func setDefaultListenSockopts(fd *netFD) that
would be called from ListenTCP() et al.
Issue 1:
I'm submitting a ... (check one with "x")

[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

Component styleUrls referred css files cannot relative loading background image.

Expected behavior

Component styleUrls referred css files load relative loading background image according css file's path.

Minimal reproduction of the problem with instructions

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

Please tell us about your environment:

Angular version: 2.0.X

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5]

TypeScript 2.0.3 ES5

Node (for AoT issues): node --version =

Issue 2:
I'm submitting a ... (check one with "x")

[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

When navigating to the current URL, the route is not reloaded and no navigation events are fired.

Expected behavior

The router should navigate to the route, firing the navigation events.

Minimal reproduction of the problem with instructions

Plunker:

http://plnkr.co/edit/TlRwYcDmV0JacgD9UgFU?p=preview

Click the link for the current page and note the events don't fire.

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

My specific case is that I have been using the router events to enable me to scroll the page back to the top when the NavigationEnd event is fired. This no longer gets fired when navigating to the current URL and so when someone is on my home page and scrolls down to the bottom, if they click a home link it doesn't scroll them back to the top. Also, if this were running as a standard website, the page would reload in this circumstance. This used to work absolutely fine but has since changed after upgrading.

At the very least it would be good to be able to have an option when initialising the routes to change this behaviour.

Angular version: 2.3.0

Browser: all

Language: all

Node (for AoT issues): node --version =
Issue 1:
Bug report

Describe the bug

If SSR occurs on a page with scss imports, client-side routing works fine. If the SSR page does not include any scss imports, client-side routing then does not take place.

To Reproduce

Steps to reproduce the behavior:

Clone and run example repo: https://github.com/kinetifex/next-sass-routing-bug

Browse to http://localhost:3000/

Click on With SCSS import link

Notice route does not change and no errors present.

Also note there is no .css downloaded in Network tab

When it works:

Run example app

Browse to http://localhost:3000/with-scss

The .css file will download in Network tab

Click on Index link

Click on With SCSS import link

Notice it works this time.

Expected behavior

Routing to pages with scss imports should work.

System information

OS: macOS

Browser: chrome, firefox, safari

Version of Next.js: 7.0.2

Additional context

This is using @zeit/next-sass plugin, though I believe the error to be next.js related, possibly with _document.js

Issue 2:
Noticied that in Safari (11.1), using the back/forward buttons with a custom express server fails to pass plain type objects via getInitialProps. This is causing errors due to running methods on undefined objects when users on Safari navigate using the back/forward buttons.

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

Expected Behavior

Objects passed from server routes through gitInitialProps should persist even when using back/forward buttons in the browser.

Current Behavior

Objects passed from server routes through gitInitialProps are not persisting when using back/forward buttons in the browser.

Steps to Reproduce (for bugs)

See this repo I created, it includes steps: https://github.com/jhoffmcd/next-test-custom-server#test-2

Context

I have a client site where a data object being passed by the server is not available on back/forward action, thus creating an error page for users. (Other types seem fine, arrays, strings, etc)

Could be related to: #2360

If custom popstate handling is a must to ensure persistant SSR, can this be added to the custom-server-express example or documented more clearly somewhere?

Your Environment

Tech
Version

next
5.0.1

node
8.9.4

OS
osx 10.13.4

browser
safari 11.1

express
4.14.0

react
16.3.0
Issue 1:
It failed twice within last 5 runs with the following error:

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/horizontal_pod_autoscaling.go:56 Nov 26 18:58:15.098: Number of replicas has changed: expected 3, got 4

http://kubekins.dls.corp.google.com/view/Critical%20Builds/job/kubernetes-e2e-gce-autoscaling/1851/

http://kubekins.dls.corp.google.com/view/Critical%20Builds/job/kubernetes-e2e-gce-autoscaling/1849/

@jszczepkowski @mwielgus @piosz @gmarek

Issue 2:
Instead of consuming 250 milli-cores, recourse consumer consumes nearly 400 milli-cores. This causes flakiness of autoscaling e2e tests:

http://kubekins.dls.corp.google.com/job/kubernetes-e2e-gce-autoscaling/1521/

Horizontal pod autoscaling [Skipped][Autoscaling Suite] should scale from 1 pod to 3 pods and from 3 to 5 (scale resource: CPU)

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/horizontal_pod_autoscaling.go:47

Oct 28 03:27:29.523: Number of replicas has changed: expected 3, got 4

Logs from controller-manager:

I1028 10:27:25.876466 6 metrics_client.go:135] Sum of cpu requested: {1.500 DecimalSI}
I1028 10:27:25.878913 6 metrics_client.go:172] Metrics available: {
"items": [
{
"metrics": [
{
"timestamp": "2015-10-28T10:25:00Z",
"value": 0
},
{
"timestamp": "2015-10-28T10:24:00Z",
"value": 180
}
],
"latestTimestamp": "2015-10-28T10:25:00Z"
},
{
"metrics": [
{
"timestamp": "2015-10-28T10:25:00Z",
"value": 227
}
],
"latestTimestamp": "2015-10-28T10:25:00Z"
},
{
"metrics": [
{
"timestamp": "2015-10-28T10:25:00Z",
"value": 122
},
{
"timestamp": "2015-10-28T10:24:00Z",
"value": 80
}
],
"latestTimestamp": "2015-10-28T10:25:00Z"
}
]
}
I1028 10:27:25.884889 6 horizontal.go:154] Successfull rescale of rc, old size: 3, new size: 4