WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Symfony version(s) affected: 4.1 and 4.2

Description

While appending new rows to a console table, content starts to be duplicated once the height of the table reaches the height of the terminal.

Here's what I get when appending 20 rows in a 15 rows tall terminal

❯ bin/console table
+----+
+----+
| 0 |
+----+
| 0 |
| 1 |
+----+
| 0 |
| 1 |
| 2 |
+----+
| 0 |
| 1 |
| 2 |
| 3 |
+----+
| 0 |
| 1 |
| 2 |
| 3 |
| 4 |
+----+
| 0 |
| 1 |
| 2 |
| 3 |
| 4 |
| 5 |
+----+
| 0 |
| 1 |
| 2 |
| 3 |
| 4 |
| 5 |
| 6 |
| 7 |
| 8 |
| 9 |
| 10 |
| 11 |
| 12 |
| 13 |
| 14 |
| 15 |
| 16 |
| 17 |
| 18 |
| 19 |
+----+

Here's what I get when appending 20 rows in a 25 rows tall terminal

❯ bin/console table
+----+
| 0 |
| 1 |
| 2 |
| 3 |
| 4 |
| 5 |
| 6 |
| 7 |
| 8 |
| 9 |
| 10 |
| 11 |
| 12 |
| 13 |
| 14 |
| 15 |
| 16 |
| 17 |
| 18 |
| 19 |
+----+

How to reproduce

Create a new Symfony project: composer create-project symfony/website-skeleton path/to/dir

Create a new file src/Command/TableCommand.php with the following content:

<?php

namespace App\Command;

use Symfony\Component\Console\Command\Command;
use Symfony\Component\Console\Helper\Table;
use Symfony\Component\Console\Input\InputInterface;
use Symfony\Component\Console\Output\OutputInterface;

class TableCommand extends Command
{
protected static $defaultName = 'table';

protected function execute(InputInterface $input, OutputInterface $output)
{
$table = new Table($output->section());
$table->render();

for ($i = 0 ; $i < 50 ; $i++) {
$table->appendRow([$i]);
}
}
}

Run bin/console table in a terminal with less than 50 rows of height.

Possible Solution

Honestly, I'm not really sure what's happening here so I can 't really help, but I would be glad to provide you with more informations if this bug is specific to my environment.

Additional context

I reproduced this in macOS terminal and iTerm2, but didn't try anywhere else.

Issue 2:
Upon clearing the cache a fatal error is thrown:

Fatal error: Uncaught Symfony\Component\Debug\Exception\FatalThrowableError: Parse error: syntax error, unexpected '\' (T_NS_SEPARATOR), expecting identifier (T_STRING) in [...]var/cache/dev/appDevDebugProjectContainer.php:7161

Here's the corresponding line:

class VichUploaderBundleHandlerUploadHandler_000000003557d388000000006581de10da75941a549785cf26d7df71050c90e4 extends \\Vich\UploaderBundle\Handler\UploadHandler implements \\ProxyManager\Proxy\VirtualProxyInterface {

It's obvious that the error is caused by the duplicate backslashes.

#9815 seems to be related, but #9816 does not fix this behaviour since it started after the most recent composer update.
Issue 1:
Hey Guys im getting the following error in omnisharp Log it looks like its looking for the runtime in the wrong folder.

Could not find any CSX files

[ERROR:OmniSharp.Dnx.DnxPaths] The specified runtime path '1.0.0-rc1-final' does not exist. Searched locations /Users/franzsilva/.dnx/runtimes/dnx-mono.1.0.0-rc1-final

/Users/franzsilva/.dnx/runtimes/kre-mono.1.0.0-rc1-final

/Users/franzsilva/.dnx/packages/KRE-Mono.1.0.0-rc1-final

/Users/franzsilva/.k/runtimes/dnx-mono.1.0.0-rc1-final

/Users/franzsilva/.k/runtimes/kre-mono.1.0.0-rc1-final

/Users/franzsilva/.k/packages/KRE-Mono.1.0.0-rc1-final

/Users/franzsilva/.kre/runtimes/dnx-mono.1.0.0-rc1-final

/Users/franzsilva/.kre/runtimes/kre-mono.1.0.0-rc1-final

/Users/franzsilva/.kre/packages/KRE-Mono.1.0.0-rc1-final

Issue 2:
Currently the debug actions pane is always displayed at the top center position. This often blocks the file names.

It would be helpful to find a better place for the pane or add the ability to move the debug actions pane.
Issue 1:
When I hit ctrl-0 in an editor pane, I expect the font-size to reset. Instead, the tree view focus is toggled. The ctrl-= and ctrl-- keystrokes both work to increase and decrease the font size, and ctrl-0 is listed under the "View" toolbar menu as being the appropriate keyboard shortcut for resetting font size.

There are no errors in the Developer Tools. The issue appears simply to be a keystroke conflict. For .platform-win32, .platform-linux, ctrl-0 toggles tree view as well as resets font size, and tree view toggle apparently wins.

I'm using Windows 8.1 and Atom 0.207.0.

Issue 2:
The tree view seems to take precedence, so this is only a minor inconvenience when you want to reset font size. There are of course workarounds:

Use mousewheel or ctrl + and ctrl - to find appropriate size

Use command palette

Rebind on user level
Issue 1:
I'm trying to run the latest version of Next (4.3-canary1 since it fixes an issue with babel-runtime) in AWS Lambda using claudia for packaging and express combined with aws-serverless-express.

Once the package deployed, I'm getting an error when querying the proxy API, ex.

https://xxxxx.execute-api.eu-west-1.amazonaws.com/latest/

Next drops Internal Server Error and in the logs I get the following:

{ Error: Cannot find module /var/task/.next/dist/bundles/pages/_error
at _callee$ (/var/task/node_modules/next/dist/server/resolve.js:220:19)
at tryCatch (/var/task/node_modules/regenerator-runtime/runtime.js:62:40)
at GeneratorFunctionPrototype.invoke [as _invoke] (/var/task/node_modules/regenerator-runtime/runtime.js:296:22)
at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/var/task/node_modules/regenerator-runtime/runtime.js:114:21)
at step (/var/task/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)
at /var/task/node_modules/babel-runtime/helpers/asyncToGenerator.js:28:13 code: 'ENOENT' }

I pushed a simple project to reproduce that issue easily: https://github.com/jgautheron/next-serverless.

EDIT: it seems that this issue is tightly linked to 4.3, it works if I use the 4.2 and make sure that next/node_modules/babel-runtime exists.

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

Expected Behavior

next build does not include absolute path to node module

Current Behavior

next build includes absolute path in transpiled require path

Steps to Reproduce (for bugs)

Correct

yarn add next@4.2.0
next build

# Transpiled output
var _extends2 = require('babel-runtime/helpers/extends');

Incorrect

yarn add next@canary
next build

# Transpiled output
var _extends2 = require('/Users/kyle/projects/test/node_modules/babel-runtime/helpers/extends');

Context

Unable to deploy to lambda using up due to up building locally and uploading zip file to s3 rendering absolute paths invalid

Your Environment

Tech
Version

next
canary

node
8.9.0

OS
macos 10.13.2
Issue 1:
I convert my project boostrap 2.3.2 to bootstrap 3

lot of problem is

.show { display: block !important }

.hide { display: none !important }

plz change this

.show { display: block; }

.hide { display: none; }

Issue 2:
I think this is lazy implementation and it breaks when using $(elem).show() or $(elem).hide() using jQuery since the hide class get more importance since the badly (IMO) use of !important.

I think BT should not declare this so generics classes with !important, it makes difficult to customize. I don't like the idea of having another class for doing display: none because BT uses !important.

In my opinion, having a rule like : .hide { btn&, ul li&, etc.. { display:none; }} isn't much work and won't break anything. also footprint shouldn't increase a lot since the .hide pattern will be greatly gzipped.

right now, having a <div id="someId" class="hide"></div> will break $('#someId').show() function of jQuery.
Issue 1:
Safari 6.0.5 / Bootstrap 3 RC2

Snippet http://jsfiddle.net/DQheE/3/

Click Dropdown (horizontal navbar)

Click Dropdown again (collapsed navbar)

Resize navbar and click Dropdown again (it get cropped)

Issue 2:
Scrollbars show for the y-overflow when moving from collapse to full width and a dropdown is open in the navbar.

To reproduce, shrink the browser window down to where the nav collapses and then open a dropdown causing the nav to overflow and show the scroll bar. Then, resize back to full width without first closing the nav. Because the collapse class is no longer on the navbar-collapse div, the navbar shows the scrollbars because its overflow-y is set to auto;

I was seeing this while using latest version of Chrome on Windows. Haven't looked in other browsers.

The following LESS Fixes the issue:

@media screen and (min-width: @grid-float-breakpoint) {
.navbar-collapse {
overflow: visible !important;
}
}
Issue 1:
STR

Head to the docs of std::rc::Rc [1]

Click the [src] link [2]

Yields a "Not Found" page [3]

Head to the docs of alloc::rc::Rc [4]

Click the [src] link [5] - this one works

Here are the full text links:

[1] http://doc.rust-lang.org/std/rc/struct.Rc.html

[2] http://doc.rust-lang.org/alloc/rc/struct.Rc.html?gotosrc=1835

[3] http://doc.rust-lang.org/alloc/rc/undefined

[4] http://doc.rust-lang.org/alloc/rc/struct.Rc.html

[5] http://doc.rust-lang.org/src/alloc/home/rustbuild/src/rust-buildbot/slave/nightly-linux/build/src/liballoc/rc.rs.html#174-180

Issue 2:
In http://doc.rust-lang.org/std/sync/struct.Arc.html

click "src". It links to http://doc.rust-lang.org/alloc/arc/struct.Arc.html?gotosrc=1343 which is forwarded to http://doc.rust-lang.org/alloc/arc/undefined
Issue 1:
For example, given the text

a a a a
^ caret here

If you hit cmd-D four times you will select all four as. But then hitting esc (mapped to "single selection") you end up with:

a a a a
^ caret

Issue 2:
There is an excellent 'select next' feature in Atom (find-and-replace:select-next, cmd + d).

After selecting a few instances of a word, and editing in 'multi-cursor mode', esc is used to leave multi-cursor mode.

Currently Atom will settle/restore the curser position for the last cursor (out of the multiple cursors), instead of of the first (from which 'select next' was initialized).

It would be better if it would instead reset to the original/first cursor position.

Let me know if I should elaborate more on the issue.
Issue 1:
Why

Recent controversy about node-ipc showcased node's security weakness. People would think that deno is bulletproof for this kind of issues, but it isn't.

Let me elaborate:

Even if you'd import non-malicious module with semver – you're fine until its time to update. You're mostly probably just updating those numbers in imports and maybe refactoring code, you don't check whether module has became dangerous.

Idea

Here comes my idea – import permissions.

By default you could take two directions:

Inherit permissions from the entry module, fully backwards compatible

Allow none of the permissions by default, breaking change

That way, we would be 100% safe that modules imported by us wouldn't do what we need them to do.

Syntax

Syntax is debatable, however I see this coming closely to import assertions, e.g.:

// static imports
import * as malicious from "https://deno.land/x/some-random-module/mod.ts" allow { read: true } // when allowing none by default
import * as malicious from "https://deno.land/x/some-random-module/mod.ts" allow { read: true, write: false, run: false } // when inheriting permissions
import * as malicious "https://deno.land/x/some-random-module/mod.ts" allow { read: "/tmp" } // allow reading only specific directory

// dynamic imports
const malicious = await import("https://deno.land/x/some-random-module/mod.ts", {
allow: {
read: true,
},
})

Issue 2:
Sorry if this has been asked or discussed before. Can't seem to find it.

Can I make sure imported scripts are in Sandbox mode even if my own script isn't.

// I'd like to make sure this imported script doesn't have access to disk or network even though my code is networking

import { SomeFeature} from "https://url.com/some-small-library.ts";
Issue 1:
TypeScript Version:

master

Code

interface F {
(g: () => void): number; // if this line is removed, tsc gives a correct error.
(g: (i: (p: number) => number) => void): number;
}
var f: F;
f(i => h(i));
function h(i: (p: string) => string): string {
return i('');
}

Expected behavior:

index.ts(6,10): error TS2345: Argument of type '(p: number) => number' is not as signable to parameter of type '(p: string) => string'.
Types of parameters 'p' and 'p' are incompatible.
Type 'string' is not assignable to type 'number'.

Actual behavior:

pass

Issue 2:
Motivation

Libraries such as Knockout use overloaded functions, for example:

var x = new MyKnockoutModel();
console.log(x.customerName()); // string
x.customerName('bob'); // OK
x.customerName(42); // Error, 42 is not a string

We can model these in TypeScript:

interface KnockoutElement<T> {
// Getter
(): T;
// Setter
(value: T): void;
}

However, these overloads turn out to not be safe when used in callbacks. For example:

function readFile(finished: (contents: string) => void) { /*... */ }
var ko: KnockoutElement<number>;
readFile(ko); // No error, but passes a string to a number-expecting setter!

This is because we look at all the candidate source signatures, reject the (x :number) => void signature for having an incompatible type, and accept the () => T signature because it has fewer parameters (an acceptable variance).

This behavior does not map to any actual runtime behavior. The invoker's side might check the .length property of the function to determine what kind of arguments to pass, and the invokee's side might check arguments.length to determine which overload was intended, but the invoker cannot tell what the expected parameter type of the function is, and the invokee reasonably expects to be called with the correct type given a certain arity.

Proposal

As an example, if a callback declaration says it’s going to invoke f with two parameters, we should not consider overloads of f which take zero arguments if an overload with one or two arguments exists.

In 3.8.3 / 3.8.4:

M is a non-specialized call or construct signature and S’ contains a call or construct signature N where […]

Change to

M is a non-specialized call or construct signature and S’ contains a call or construct signature N where no other call or construct signature in S’ has more parameters than N but not more than M, and […]

Analysis

A sample implementation of this rule breaks no existing tests. Check stopParameterNeglect branch for code/tests.
Issue 1:
Electron version: 1.8.2-beta.5

Operating system: Mac OS X 10.13.2 17C88

Expected behavior

Actual behavior

Electron crashes

How to reproduce

Haven't found reproduction steps yet, when I do I'll update this issue. I do have a symbolicated crash report.

Issue 2:
Electron version: 1.8.2-beta.5

Operating system: Mac OS X 10.13.2 17C88

Expected behavior

Actual behavior

Electron crashes

How to reproduce

Haven't found reproduction steps yet, when I do I'll update this issue. I do have a symbolicated crash report.
Issue 1:
Setting a custom data attribute such as data-test="" works, whereas data-0="" would fail.

Is this expected behaviour?

Issue 2:
If the data attribute is formatted as data-{number}-*, then it won't be rendered into the HTML.

Example:

http://jsfiddle.net/1etmp5fn/

Notice that data-100-bucks does not show up in the rendered result, while data-bucks-100 does.
Issue 1:
If the developer has modified the flutter repo, "flutter upgrade" will fail. Right now it's a bit ugly:

Flutter from https://github.com/flutter/flutter.git (on master)
flutter revision: 0494801b173a69121cc36dc32b27b6d68ffa77cf (12 hours ago)
engine revision : 9e1e1fba5474b458458b65f1aa1d0d730af2705b

Upgrading Flutter...
From https://github.com/flutter/flutter
1dd74a3..dc68728 master -> origin/master
fatal: Not possible to fast-forward, aborting.

It should probably just say something like "Cannot upgrade while you have local changes.".

We should also provide a way to force the upgrade anyway, saving any local changes to a patch file (--force or something).

Issue 2:
This is what you see when you run flutter upgrade but have a conflict:

sethladd-macbookpro:flutter_gallery sethladd$ flutter upgrade
Upgrading Flutter from /Users/sethladd/Code/flutter...
From https://github.com/flutter/flutter
244a7a02b..d2abdf8e6 master -> origin/master
error: Your local changes to the following files would be overwritten by merge:
examples/flutter_gallery/.idea/modules.xml
Please commit your changes or stash them before you merge.
Aborting
Updating 657a4c3fc..d2abdf8e6

Note the "Updating ..." which I thought meant "update complete!"

Actually, due to the conflict when merging, the update didn't complete. :/

Can we print out a clearer message when the update fails? Something like: "Upgrade failed. Please see output above, or run flutter upgrade -v for more info."

Thanks!
Issue 1:
In cases where one wants to run multiple iterations of density back to back, we really need to make sure a pervious iteration's load doesn't leak into this one. 2 main culprits are:

Deleting the namespace will return in a moment, when really it takes like ~15m to delete all events (~20,000 events for 3000 pods). These deletes actually have a bad effect on the next run.

We should make sure the pods are actually gone on the kubelet before staring a new run by using the proxy to poll /pods or something. Otherwise we're effectively putting > 30 pods on a node and the kubelet is known to be slow during pod deletes.

This is obviously not a problem if we tear down the entire cluser between iterations.

@gmarek

Issue 2:
#10225 refers

Copy of my notes from there:

This just all looks terribly wrong (not this particular PR, but the code around it). Note to myself to understand it properly and fix it up soon. Specifically:

The function deleteTestingNS() does nothing of the sort. It just polls until all namespaces with some magic prefix are not in deleting state. It would seem that that simply doesn't work if there are parallel test runs in flight.

If the comments in this PR are true, then we're deleting the contents of namespaces in a rather bizirre way. I'd like to understand that.

Having namespace deletion take up to 60 minutes to complete is simply untenable in automated tests. Isn't this called for every test invocation? Or perhaps it's once per test run. Either way, it's way too long.

Q
Issue 1:
Electron version: 1.4.1

Operating system: Windows 10

I open a window with ({fullscreen: true}) property and it load the URL just fine

but when i press F11 to leave Fullscreen mode the window not responding and when i click on the window to get focus, it (the window) disappear and the npm session in the console keep to run

Issue 2:
Electron version: 1.2.0, 1.2.1, 1.2.2

Operating system: Windows

If you start an browser window in fullscreen and then attempt to toggle to windowed mode, the window will just black out and become unresponsive. Attempting to toggle back again still results in a black screen.

However, if you start the window in windowed mode and then toggle to fullscreen, it works as expected.

This maybe related to the fixes made to the fullscreen API in 1.2.x. It only occurs on Windows. It does not happen on 1.1.3.

You can reproduce easily with the electron-api-demos application and 1.2.2.

https://github.com/electron/electron-api-demos

Update window-options to set fullscreen: true

https://github.com/electron/electron-api-demos/blob/master/main.js#L22

var windowOptions = {
width: 1080,
minWidth: 680,
height: 840,
title: app.getName(),
fullscreen: true
}

Start the application and hit F11 to switch to windowed mode and you'll get a black screen.
Issue 1:
It would be nice to split .atom into .config/atom and .local/shared/atom (respectively AppData/Roaming and AppData/Local for Windows). There are more details on freedesktop.org spec for corresponding environment variable and use cases.

For example "compile-cache" would rather go to .local/shared and "snippets.cson, keymap.cson" to .config.

This clean separation would really help for backups (.local can usually be ignored, .config is important)

Issue 2:
Hiya,

Since I updated to 189, I have this really strange bug with chrome. Whenever I run chrome and atom together, I loose the ability to cut and paste in chrome, in fact right click menu doesn't always work in chrome either.

This has only happened since I upgraded atom to 189 and only when I run the two together (I notice chrome version in atom was updated in 189).

I have had to go back to using ST2 since this shows it's face at the worst moments, timing is random but it always happens at least once a day requiring a re start, or complete kill of chrome and all processes.

I am running Ubuntu Gnome 64bit, chrome Version 41.0.2272.118 (64-bit) and atom 189. Problem happens at least once a day and completely screws chrome browser. I have ran ST2 for a few days now and am no longer getting the issue so atom is definitely causing this since i updated to 189.

ta

Paul
Issue 1:
See the derived implementations at the bottom of http://doc.rust-lang.org/1.0.0-beta.3/std/num/struct.Wrapping.html for example.

impl<T> Clone for Wrapping<T> where T: Clone + Clone

Issue 2:
This is now a tracking issue for RFC 1240, "Taking a reference into a struct marked repr(packed) should become unsafe", but originally it was a bug report that led to the development of that RFC. The original miscompilation did not involve references, but it has been fixed; the reference case is the one that remains open. A lot of the discussion is hence outdated; this is the current state.

Original Issue Description

(This code actually works fine on today's nightly.)

#![feature(simd, test)]

extern crate test;

// simd types require high alignment or the CPU faults
#[simd]
#[derive(Debug, Copy, Clone)]
struct f32x4(f32, f32, f32, f32);

#[repr(packed)]
#[derive(Copy, Clone)]
struct Unalign<T>(T);

struct Breakit {
x: u8,
y: Unalign<f32x4>
}

fn main() {
let val = Breakit { x: 0, y: Unalign(f32x4(0.0, 0.0, 0.0, 0.0)) };

test::black_box(&val);

println!("before");

let ok = val.y;
test::black_box(ok.0);

println!("middle");

let bad = val.y.0;
test::black_box(bad);

println!("after");
}

Will print, on playpen:

before
middle
playpen: application terminated abnormally with signal 4 (Illegal instruction)

The assembly for the ok load is:

movups 49(%rsp), %xmm0
movaps %xmm0, (%rsp)
#APP
#NO_APP

But for the bad one, it is

movaps 49(%rsp), %xmm0
movaps %xmm0, (%rsp)
#APP
#NO_APP

Specifically, the movups (unaligned) became a movaps (aligned), but the pointer isn't actually aligned, hence the CPU faults.
Issue 1:
Issue Type: Bug Report

Ansible Version: ansible 2.0.0 (devel b2a9111) last updated 2015/11/11 15:03:24 (GMT +200)

Environment: Ubuntu 15.04

Summary: Ansible will not copy but move a file when called with force=no and remote_src=true

Steps to reproduce:

copy: src=/usr/share/php5/php.ini-production dest=/tmp/test.conf remote_src=true

Expected Result: /usr/share/php5/php.ini-production will be copied to /tmp/test.conf

Actual Result: /usr/share/php5/php.ini-production will be moved to /tmp/test.conf; source file is removed. Ansible will fail when source file system is read-only as it cannot remove the file (/usr is mounted read-only in this example):

fatal: [removed]: FAILED! => {"changed": false, "failed": true, "msg": "{\"msg\": \"Could not replace file: /usr/share/php5/php.ini-production to /tmp/test.conf: [Errno 30] Read-only file system: '/usr/share/php5/php.ini-production'\", \"failed\": true}\r\nException OSError: (2, 'No such file or directory', '/tmp/.ansible_tmp8zPmHVtest.conf') in <bound method _TemporaryFileWrapper.__del__ of <closed file '<fdopen>', mode 'w+b' at 0x7f241188c4b0>> ignored\r\n", "parsed": false}

Issue 2:
ISSUE TYPE

Bug Report

Feature Idea

COMPONENT NAME

AWS EC2 External Inventory Script

SUMMARY

Switching the AWS_PROFILE does not invalidate the cache. So its possible to load inventory from one AWS profile and then switch to another and have the same results.

STEPS TO REPRODUCE

AWS_PROFILE=staging ec2.py --list

AWS_PROFILE=staging ec2.py --list

EXPECTED RESULTS

Two different lists of resources

ACTUAL RESULTS

Duplicate list of resources