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

We can currently select text in the terminal by dragging mouse with key pressed. Linux terminals and Windows command prompt allows you to select text by also Shift + arrow keys. I have tried this in the Windows terminal and instead of selecting the texts it just prints characters (Shift + right arrow prints 'D' for me).

Would be great to have the keyboard method for text selection for windows users. Would be very helpful for keyboard heavy users

Update

I checked that powershell on terminal works as expected

cmd on terminal doesn't print extra characters, the cursor just moves instead of selection

WSL prints extra characters (shift + right => D, Shift + left => C, etc)

Issue 2:
Hello,

I'm using tmux on Linux machines and ConEmu on Windows machines and I really love that I can do text selection with the keyboard.

In ConEmu, there is a keybinding for "Start text selection (like text editors)", whereas in tmux there is the same thing with <prefix><b> (I think that is default), where I get a cursor that I can move with the arrow keys around the console window.

While doing this, I can select text while holding shift and (in case of ConEmu) press ENTER to copy the text into the clipboard and end the text selection.

It can also be compared with Vim's visual mode.

It would be nice if the new Windows Terminal could support this out of the box, so I can use it in e.g. PowerShell :-)
Issue 1:
I am using Neo4j 1.9.1. I am getting an incorrect node count in the red bubble which shows the number of nodes with a given relationship and this behaviour occurs after I select one of the nodes from that bubble.

To show this, I downloaded the Cineeast database from here. I went to to the data browser and searched for node 431. That node has 14 nodes with relationship ACTS_IN coming into it. I clicked on the red bubble with 14 nodes written in it. I selected node number 434 from the pop-up list. After selecting that node, the node count displayed went down to 12 instead of 13. When I click on that red bubble again, I can see that the list has 13 nodes in it. So the error is in the node count text.

cheers

Issue 2:
The properties count on the front page of the webadmin GUI does not actually report the total number of properties, which is what anyone would assume. It instead reports the number of property blocks, where every node and relationship has at least one block, and each block holds up to four properties.

For example, I recently imported a data set containing 6,645 nodes with one property each, and 11,469 relationships with two properties each. I expected the total number of properties to be 29,583 (6,645 + (11,469 * 2)). Instead it was 18,114 (6,645 + 11,469).
Issue 1:
Bug report

What is the current behavior?

When a webpack configuration includes resolve: { symlinks: false }, dependencies that are linked into the node_modules folder as symlinks do not get watched properly by webpack-dev-server: changes to those dependencies do not trigger a rebuild or browser refresh.

It is my understanding that using the resolve.symlinks property in this way is valid and shouldn't cause this issue. In the real application where this was discovered, we are using resolve.symlinks to avoid errors resulting from the symlinked module pulling in duplicate copies of other dependencies (React specifically).

If the current behavior is a bug, please provide the steps to reproduce.

Please see https://github.com/rpokorny/webpack-link-bug for a reproduction of the issue.

What is the expected behavior?

When a file in the symlinked dependency is modified, the change should automatically get picked up resulting in a rebuild of the bundle and a refresh of the webpage if it is open in a browser.

Other relevant information:

webpack version: 5.24.3

Node.js version: 12.18.0

Operating System: Linux 5.10.14-arch1-1

Additional tools: webpack-dev-server 3.11.2

Issue 2:
Bug report

What is the current behavior?

I install deps with npminstall(it can install faster), but the file tree in node_modules is special bacause npminstall install pkgs with symbol link to download and write less files.

The file tree looks like this

app
├── index.js
└── node_modules
├── _a@1.0@a(real dir)
| ├── index.js
| └── node_modules
| └── b(symbol link to app/node_modules/_b@1.0@b)
├── _b@1.0@b(real dir)
| ├── index.js
| └── node_modules
| └── a(symbol link to app/node_modules/_a@1.0@a)
├── a(symbol link to app/node_modules/_a@1.0@a)
└── b(symbol link to app/node_modules/_b@1.0@b)

Because of a,b is reference by each other, contextTimestampQueue and contextHashQueue in FileSystemInfo will never reach the end.

If the current behavior is a bug, please provide the steps to reproduce.

The minimal reproduction repo is here.

The reproduce step is

git clone git@github.com:killagu/npminstall_webpack.git
cd npminstall_webpack
npm i -g cnpm
# must use cnpm install
cnpm i
npm run build

Build snapshow will fail.

What is the expected behavior?

Use fs.lstat to get file info, and use target path to process.

Skip files if has been processed

Other relevant information:

webpack version: 5.11.0

Node.js version: 12.16.3

Operating System: macOS Big Sur 11.0.1 (20B29)

If it is ok, I'm happy to make a pr to fix it.
Issue 1:
Describe the feature:

it would be great if the API documentation (the stuff on the web) had a "newbie" mode that would show query components within the context of a complete query. for example, on https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-common-terms-query.html, there are examples of the "common" block, but it's not clear (to me at least) where the "common" block fits in the query.

I realize that adding that information to every page would be noisy for experienced users, so I'd suggest a way for newbies to say "show me this in the context of the ENTIRE query". That would also be helpful as a learning tool, because by seeing lots of different examples, the newbie learns the structure of queries by osmosis.

Issue 2:
Describe the feature:

#18075 will merge soon, testing all the // CONSOLE snippets in our docs. But lots of our docs aren't annotated with it! We should annotate more snippets so we test more of the docs.

Edit: // CONSOLE has replaced // AUTOSENSE. The sense application is named console in 5.0.0.
Issue 1:
From @maciej on 2016-11-07T17:28:08Z

ISSUE TYPE

Bug Report

COMPONENT NAME

docker_container

ANSIBLE VERSION

ansible 2.2.0.0
config file = [redacted]/ansible.cfg
configured module search path = Default w/o overrides

CONFIGURATION

[defaults]
host_key_checking=False

OS / ENVIRONMENT

Running ansible from: macOS Sierra

Provisioning: CentOS 7.2, Docker installed from https://yum.dockerproject.org/repo/main/centos/7

SUMMARY

docker_container module fails with:

fatal: [default]: FAILED! => {"changed": false, "failed": true, "msg": "Error pulling image httpd:latest - pull() got an unexpected keyword argument 'decode'"}

while pulling an image

STEPS TO REPRODUCE

Execute ansible-playbook with the following play:

- name: "Start container"
docker_container:
name: whatever
image: "httpd"
pull: true

Copied from original issue: ansible/ansible-modules-core#5515

Issue 2:
ISSUE TYPE

Bug Report

COMPONENT NAME

docker_container

ANSIBLE VERSION

ansible 2.2.1.0
config file = /usr/home/sean/work/ansible/ansible.cfg
configured module search path = Default w/o overrides

CONFIGURATION

Nothing.

OS / ENVIRONMENT

N/A

SUMMARY

The docker_container documentation says it requires a docker-py>=1.7.0. However, as of 2.2.1.0, the minimum version is actually 1.8.0 because of the addition of the decode argument to the pull method. That keyword argument was added for docker-py 1.8.0-rc1.

STEPS TO REPRODUCE

Use docker_container with a remote host that has 1.7.x, such as CentOS 7.2's 1.7.2.

EXPECTED RESULTS

Work.

ACTUAL RESULTS

failed: [host.example.com] (item=worker) => {"failed": true, "item": "worker", "msg": "Error pulling image imagename:latest - pull() got an unexpected keyword argument 'decode'"}
Issue 1:
What problem does this feature solve?

I have a trouble with template bugs. The vue warning identifies the file but not the specific location of the error. For example when I access some property of undefined object I receive the name of property and that is all. If this property has multiple occurences it is hard to find which is the root cause. The source map unfortunatelly does not apply for template code.

[Vue warn]: Error in render: "TypeError: Cannot read property 'since' of undefined"
found in
---> <Profile> at src/views/Profile.vue
<App> at src/App.vue
<Root>

This error from the error handler is useless too:

TypeError: Cannot read property 'since' of undefined
at Proxy.render (Profile.vue?08f5:69)
at VueComponent.Vue._render (vue.runtime.esm.js:3548)
at VueComponent.updateComponent (vue.runtime.esm.js:4066)
at Watcher.get (vue.runtime.esm.js:4479)
at Watcher.run (vue.runtime.esm.js:4554)
at flushSchedulerQueue (vue.runtime.esm.js:4310)
at Array.<anonymous> (vue.runtime.esm.js:1980)
at flushCallbacks (vue.runtime.esm.js:1906)

I prepared minimum reproducible project: https://wwww.github.com/literakl/vue-errors

What does the proposed API look like?

The error can look this way:

[Vue warn]: Error in render at line 35: "TypeError: Cannot read property 'since' of undefined"
found in
---> <Profile> at src/views/Profile.vue
<App> at src/App.vue
<Root>

Issue 2:
What problem does this feature solve?

I don't want to add mixin to every route page, and I don't want to add global mixin to affect all components even with third parties

let's do this with one single code ok ?

What does the proposed API look like?

this.$keepalive[id].purge(Component) // purge the cache of the Component's instance if exists
Issue 1:
Similar to #318 , I am unable to make a post request with axios on node. But on browser the same piece of code seems to work fine.

const fdata = new FormData();
fdata.append('user', u);
fdata.append('hostnames', n.join(' '));
const host = localStorage.getItem('host');
const port = localStorage.getItem('port');
axios({
url: `http://${host}:${port}/hosts/remove`,
method: 'post',
data: fdata
}).then(response => {
if (response.status === 200) {
console.log(response.data);
console.log('Removed host successfully');
}
return null;
}).catch(er => console.log(er));

With unirest it works:

unirest.post(`http://${host}:${port}/hosts/remove`)
.headers({ 'Content-Type': 'multipart/form-data' })
.field('user', u)
.field('hostnames', h.join(' '))
.end(response => {
console.log(response.body);
});

axios version: v0.16.2

Environment: node v8.0.0, windows 8.1

Issue 2:
From the documentation of axios it seems that nodejs doesn't natively support FormData objects

// data is the data to be sent as the request body // Only applicable for request methods 'PUT', 'POST', and 'PATCH' // When no transformRequest is set, must be of one of the following types: // - string, plain object, ArrayBuffer, ArrayBufferView, URLSearchParams // - Browser only: FormData, File, Blob // - Node only: Stream data: { firstName: 'Fred' },

So if I want to use axios in a jasmine test running with nodejs, then how would I go ahead and post a multipart/formdata object to a website?

Thanks for your help..
Issue 1:
Issue Details

Electron Version:

7.1.8

Operating System:

macOS 10.13.6

Last Known Working Electron version:

N/A

Expected Behavior

titleBarStyle: 'customButtonsOnHover' should only affect the buttons and not change the shape of the window to be a rectangle

Actual Behavior

The buttons are rendered properly, but the window loses its rounded corners

Here's a sample of the upper-right corner of a window with each mode:

Left - 'hidden'

Right - 'customButtonsOnHover'

To Reproduce

Create a BrowserWindow with titleBarStyle: 'customButtonsOnHover' and observe the lack of rounded borders

Additional Information

customButtonsOnHover didn't work at all in 4.1.5, so it's really awesome to see it working so close to perfectly!

All glory to the Electron Team

Issue 2:
Electron version: 1.7.5

Operating system: macOS 10.12.6

Expected behavior

The corners should be rounded like they were in 1.6.x

Actual behavior

The browser windows corners are no longer rounded when running with electron 1.7.5

How to reproduce

git clone https://github.com/emilylaguna/electron-quick-start.git
cd electron-quick-start
npm install
./node_modules/.bin/electron .
Issue 1:
Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

Searched open and closed GitHub issues.

Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details.

If no response anymore and we cannot reproduce it on current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Which version of ShardingSphere did you use?

7928296

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-Proxy

Expected behavior

SS have same performance

Actual behavior

proxy

DB

Reason analyze (If you can)

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

case like #22170

test=> \d t_ssdb_tb
Table "public.t_ssdb_tb"
Column | Type | Modifiers
--------+---------------+-----------
id | integer |
c_id | integer |
a | integer |
b | character(10) |

Example codes for reproduce this issue (such as a github link).

Issue 2:
The IT result is different with load data from database.

Case name: SELECT AVG(user_id) AS user_id_avg FROM t_order

Expected: is "19"

but: was "19.5000"

Please see:

dql-integration-test-cases.xml and search FIXME #15593

BaseDQLIT and search // FIXME #15593 verify accurate data types, please remove the try catch to reproduce the issue
Issue 1:
Bug report

Describe the bug

Page with a router (both useRouter, withRouter) calls the page component two times, one without router params and the second time with them. It doesn't work in static export

A clear and concise description of what the bug is.

To Reproduce

I've used your example for new routers, add static export config and got the same results as on my project.

Steps to reproduce the behavior, please provide code snippets or a repository:

git clone https://github.com/ondrejsika/nextjs--router-bug-example
cd nextjs--router-bug-example/examples/dynamic-routing
yarn

Dev Server

See two runs of page component in console.

Static Export

yarn static

see out/post/first/index.html there is no post.id rendered

Expected behavior

Run the component only one time and export propper static page.

System information

OS: macOS

Browser (if applies) chrome

Version of Next.js: 9.1.1

Issue 2:
Because of the way Next.js does initial render of the pages, and that the initial render on client-side and server-side has to be the same (see https://reactjs.org/docs/react-dom.html#hydrate ), sometimes when a page is rendered, its' query (returned i.e. by useRouter() hook) will be empty, even though it actually has query params. After the initial render, soon after there will be another render in which the query will be then populated with proper query params. ( Example described also in i.e. #7880 )

My code relies on those query params very heavily and we need to know "are those the real current query params or not yet?". (i.e. because if query params are missing or incorrect, we'd like to redirect the user to another page)

Describe the solution you'd like

I think that either:

query should be always populated with the current query params (even on initial client-side hydration that happens after a server-side render)

or, (IMO better), add a ready: boolean flag to Router, so the component can listen to this using i.e. useEffect and ignore the query params when they aren't parsed yet.

Describe alternatives you've considered

I think we'll have to go with some setTimeout or sth for now until a better solution is found.
Issue 1:
Environment

Windows build number: Version 10.0.18362.356
Windows Terminal version 0.4.2382.0

Any other software? yes, **mine** (also a terminal emulator)

Steps to reproduce

Best way to see this (if you don't have key tracing on in our own terminal app),

fire up a TMUX session, have it configured with at least one more line, like this:

bind ^space next-window

which basically states, that Ctrl+Space will cause the terminal to switch to the next window.

Except, that on Windows Terminal (or my terminal emulator, using ConPTY), it doesn't. :-)

Expected behavior

TMUX windows switching (i.e.: NUL-byte sent to PTY slave)

Actual behavior

Action Ignored.

Issue 2:
Your Windows build number: (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.18362.86]

What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

vim /some/large/document.txt

Ctrl+F

Ctrl+B

What's wrong / what should be happening instead:

Ctrl+F should cause page down

Ctrl+B should cause page up

These work fine in existing cmd, powershell, etc. but don't work as expected in Terminal.

vim --version

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 3 2014 09:06:12)

MS-Windows 32-bit console version

Included patches: 1-493

(I believe I installed the above through chocolatey at some point.)
Issue 1:
Using display:inline-block (instead of display:block) on responsive utilities (.visible-x and -hidden-x) would expand its usage to inline elements.

Currently, when using them on inline elements, the problem is that when the element becomes visible again, it gets display:block applied, usually generating undesirable line breaks.

Issue 2:
related to issues #8500 , #7808 , #4929 ; using .hidden-sm to hide span within .nav > li > a . Because class is display: block above -sm then text wraps to new line. Would you consider .hidden-* classes to be display: inline-block instead ?

Here's a jsfiddle of the two cases - but the repercussions could be greater outside of this situation so probably needs more consideration... http://jsfiddle.net/jholl/P86yf/
Issue 1:
class X {
foo = 1
constructor( setup? : ( obj : this ) => void ) {
if( setup ) setup( this )
}
}

var x = new X( obj => {
obj.foo = 2 // Ok, allowed
// obj.bar = 3 // Ok, not allowed
} )

A 'this' type is available only in a non-static member of a class or interface.

Issue 2:
TypeScript Version:

1.8.9 / nightly

Code

abstract class Abstract {
protected name: string;

constructor () {
this.abstractMethod();
}

protected abstract abstractMethod (): void;
}

class Concrete extends Abstract {
protected name: string = 'Concrete';

protected abstractMethod () {
console.log(this, this.name); // Concrete, undefined
}
}

new Concrete();

Playground: link

Expected behavior:

this.name inside abstractMethod() realization must be pointed at name property of Concrete class.

Actual behavior:

this.name inside abstractMethod() realization is pointed at name property of Abstract class.
Issue 1:
Assigning to field of recarray is not working correctly. Example script is below.

import numpy as np

rec = np.recarray(1, dtype=[('x', float, 5)])

# Bug behaviour
rec[0].x = 1
print rec[0] # should print: (array([ 1., 1., 1., 1., 1.]),)
# but prints uninitialized float values

# Correct behaviour
rec.x = 2
print rec[0] # prints: (array([ 2., 2., 2., 2., 2.]),)

Issue 2:
When assigning arrays inside structured arrays without a left sided [:], only the first element gets actually assigned. This is shown in the following code snippet, where a structured array is initialized with zeros, and then filled by assignment of an array, and the assignment of a structured array. The assignment of the array only assigns the first value, where the assignment of the structured array assigns all values:

In [2]: np.__version__
Out[2]: '1.7.0'
In [3]: struct_dt = np.dtype([
...: ('elem', 'i4', 5),
...: ])
In [4]: dt = np.dtype([
...: ('field', 'i4', 10),
...: ('struct', struct_dt)
...: ])
In [5]: x = np.zeros(1, dt)
In [6]: x[0]['field'] = np.ones(10, dtype='i4')
In [7]: x[0]['struct'] = np.ones(1, dtype=struct_dt)
In [8]: x
Out[8]:
array([([1, 0, 0, 0, 0, 0, 0, 0, 0, 0], ([1, 1, 1, 1, 1],))],
dtype=[('field', '<i4', (10,)), ('struct', [('elem', '<i4', (5,))])])

The expected result is that all elements of x[0]['field'] are 1.

However, x[0]['field'] "recognizes" some part of the assigned array, as it will complain about broadcasting problems for wrong sizes:

In [9]: x[0]['field'] = np.ones(9, dtype='i4')
---------------------------------------------------------------------------
ValueError Traceback (most recent call last)
<ipython-input-9-80d7cbce6711> in <module>()
----> 1 x[0]['field'] = np.ones(9, dtype='i4')

ValueError: could not broadcast input array from shape (9) into shape (9,10)

As mentioned in the beginning, adding [:] on the left side (In [6]) will correctly set all elements to 1. If the shown assignment is not allowed, I would have expected that an exception gets raised?
Issue 1:
What problem does this feature solve?

This solve the issue where multiple root components is not allowed like for instance

i'm trying to do this with slots using my own component for page loading and checking if its on loading and not loading state and checking if its valid to render the main component

<template lang="pug">
v-progress-linear.ma-0(v-if="loading" color="secondary")
div(v-else-if="loaded")
slot
v-container(fluid fill-height v-else)
v-layout(justify-center align-center)
slot(name="no-result")
h1.text-xs-center No Result
</template>

<script>
export default {
name: "Page",
props: {
loading: {
type: Number,
default: 0
},
valid: {
type: Boolean
}
},
computed: {
loaded() {
return this.valid && !this.loading;
}
}
};
</script>

So in this part of the template makes another div to just prevent the multiple root issue

div(v-else-if="loaded")
slot

so doing it like this would help

slot(fragment) Fall back content

I know this thing can be done somehow on render functions

but its not vueish anymore :)

What does the proposed API look like?

so in slots

we can do

<slot fragment></slot>

and in template syntax

<template fragment> </template>

Got the idea here https://reactjs.org/docs/fragments.html

Issue 2:
Vue version 0.11.4

encounter below error :

vue.js:4467 Uncaught TypeError: Cannot read property 'update' of undefined vue.js:4467

p.notify vue.js:6958

Object.defineProperty.setvue.js:1489

proxySetterrecordMainPage.js:49

Vue.component.methods.onRecordChangevue.js:1894

(anonymous function)VM58885:3

(anonymous function)vue.js:4622

handler vue.js:3415

handler

it happens only once. if click other dropdown it works as well.

if jsfiddle example needed, i will extract one.
Issue 1:
Migrated issue, originally created by Anonymous

If we define many-to-many relation in base class with secondary table s1, and then re-define it with secondary table s2 in inherited class, it will try to use both relations and insert records in both s1 and s2.

So in provided example we get

deleted_posts -> deleted_post_files <- files AND deleted_posts -> post_files <- files, so object from base class with same primary index gets incorrectly associated to files table.

Attachments: sa_test3.py

Issue 2:
Migrated issue, originally created by paj (@paj)

The MSSQL module supports three different DBAPIs. It should be possible for the user to specify which one they want, ideally using a string, so this can be done from a framework's configuration file. Although there's code that tries to support this, it doesn't work at present, primarily because the MSSQLDialect.new doesn't see the constructor arguments, which would tell it which DBAPI to use.

Fixing this may require a bit of a refactor, possibly beyond the MSSQL module.