WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
In Bootstrap 3.2.0 it is at the moment possible to have more accordion items at once open. But normally only entry should be open.

How i made this:

Normal Click on accordion item "Collapsible Group Item #3"

Fast Click on accordion item "Collapsible Group Item #2"

Fast Click on accordion item "Collapsible Group Item #1" (as soon as possible after step 2))

Result (Image below -> two open accordion items):

Issue 2:
Step 1. Navigate to this page: http://getbootstrap.com/javascript/#collapse

Step 2. Click on one of the links that trigger opening of the accordion sections (ie. Collapsible Group Item #1)

Step 3. Before the section's opening animation has a chance to complete (the one from 'Step 2' above) click on a different link to trigger opening a second panel (ie. Collapsible Group Item #2)

At this point you should see that you have two accordion panels open at the same time.
Issue 1:
Electron version: 1.1.0

Operating system: Windows

This release contains the Visual C++ 2013 runtimes instead of Visual C++ 2015 runtimes.

Issue 2:
Electron version: 1.8.4

Operating system: Windows 10 version 1803

Expected behavior

Frameless applications without a titlebar should have the context menu (accessible with Shift+Right Click) on the taskbar:

Actual behavior

Due to the lack of the titlebar on frameless applications, this menu does not appear. There also doesn't seem to be any API that would let devs add the context menu while keeping the app frameless.

Shift + right clicking on frameless apps doesn't show anything and prevents the end user from restoring the window or move the app around when it is off screen (desktop/desktop#2311)

How to reproduce

Shift + Right Click on a frameless app on the taskbar
Issue 1:
Tabs colors aren't prominent in Windows Terminal. It could bring errors/ambiguity while working in multiple tabs.

Issue 2:
From @srv-code in #3386:

Text font looks little bold (a difference noticed in comparison to cmd font even after keeping the same font properties).

@srv-code Could you maybe see some screenshots of the difference you're seeing? I'm sure there are going to be slight differences between GDI (the conhost renderer) and DX (the Terminal renderer), but they shouldn't be that significant.

Maybe this has to do with how we're antialiasing? #1298 has some discussion there.
Issue 1:
It seems like using glob on use statements ends up generating twice the documentation for Impl and Traits of this Struct.

If I use:

pub use foo::bar::*;

All Impl and Traits of each Struct in foo::bar::* will be duplicated in the doc.

If symbols are listed one by one it works well:

pub use foo::bar::baz;
pub use foo::bar::boz;

Issue can be seen when generating the doc from https://github.com/NewbiZ/rgb/tree/2d3d077120d51bdef42f2e6a83595d2b26a6e04c

If you change in src/lib.rs:

pub use self::cpu::*;

by

pub use self::cpu::Cpu;
pub use self::cpu::Flag;

it will work.

Issue 2:
small snippet called arg0.rs:

fn main ()
{
let args : ~[~str] = ::std::os::args();
::std::io::println(args[0]);
}

$ rustc -Z debug-info arg0.rs
$ gdb arg0
GNU gdb (GDB) 7.6.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/asamoilov/work/projects/rust-sandbox/my-rust/arg0...done.
(gdb) l
1 arg0.rc: No such file or directory.
(gdb) quit

i.e. expects arg0.rc instead of arg0.rs

Thanks
Issue 1:
When I run this code:

N, C = 1, 1
criterion = nn.NLLLoss()
model = nn.Conv2d(C, 3, (3, 3)).cuda()
inp = Variable(torch.randn(N, 1, 3, 3)).cuda()
pred = model(inp)
target = Variable(torch.from_numpy(np.array([3]))).view(1, 1, 1).cuda()
criterion(pred, target)

I get this error:

cuda runtime error (59) : device-side assert triggered at /opt/conda/conda-bld/pytorch_1518244421288/work/torch/lib/THC/generic/THCTensorCopy.c:70

Due to the value of target being 3, and not in the set of {0, 1, 2}. It took me a while to figure out and I was wondering this is an easy to fix issue, and if it is I was wondering how I would get started as I'm quite eager to contribute to Pytorch

Issue 2:
Hi

I have written the following code to train my model, after a few iterations it stops throwing a similar error as shown in the image. Note that error is similar but not same, it changes everytime. I have read all the answers here and pytorch forum for the similar errors, none of them works. Please help ...

Note that it is running for few iterations hence the starting few outputs

Thank you.
Issue 1:
There is another bug by the same name, but that one was fixed. After searching about 10 minutes, I couldn't find any duplicates.

The code

fn main () {
let arr: ~[u8] = ~[ 1, 2, 3 ];
let iter = &arr.iter() as &Iterator<&u8>
}

Fails to compile with the following error

task 'rustc' failed at 'index out of bounds: the len is 1 but the index is 1', /home/username/dload/code/rust/src/librustc/middle/ty.rs:1432
error: internal compiler error: unexpected failure
This message reflects a bug in the Rust compiler.
We would appreciate a bug report: https://github.com/mozilla/rust/wiki/HOWTO-submit-a-Rust-bug-report
note: the compiler hit an unexpected failure path. this is a bug
note: try running with RUST_LOG=rustc=1 to get further details and report the results to github.com/mozilla/rust/issues
task '' failed at 'explicit failure', /home/username/dload/code/rust/src/librustc/lib.rs:398

I am running rustc 0.9-pre (e5f4904 2013-12-13 07:51:42 -0800) on Fedora 19 (Linux 3.11.6-200.fc19.x86_64 #1 SMP). This is latest git HEAD as of about an hour ago.

Issue 2:
I get a huge performance regression since #8328 landed (revision a8c3fe4) on all my projects. Things are 50 to 75% slower. I’m pretty sure #8328 is in cause since when I revert the compiler to the version right before (revision 67c954e) performances go back to normal.

For what it’s worth, the concerned projects are 100% generic, and rely a lot on cross-crate inlining. They do a lot of numeric computations and array indexing. Sorry if I am a bit vague but I cannot valgrind my projects because my valgrind started to segfault a few days ago (perhaps since the re-enabling of jemalloc)…

I tried to come up with a small bench exhibiting the problem. It is not that significative, but the following shows some noticeable performances regression already:

extern mod extra;

use std::hashmap;
use extra::test::BenchHarness;

#[bench]
fn bench_insert_std(bh: &mut BenchHarness) {
let mut m = hashmap::HashMap::with_capacity(32);

do bh.iter {
for i in range(0u, 500) {
m.insert((i, i), i);
}
}
}

#[bench]
fn bench_insert_find_remove_std(bh: &mut BenchHarness) {
let mut m = hashmap::HashMap::with_capacity(32);

do bh.iter {
for i in range(0u, 200) {
m.insert((i, i), i);
}

for i in range(0u, 200) {
assert!(*m.find(&(i, i)).unwrap() == i)
}

for i in range(100u, 200) {
m.remove(&(i, i));
}

for i in range(100u, 200) {
assert!(m.find(&(i, i)).is_none())
}

for i in range(0u, 100) {
m.insert((i, i), i * 2);
}

for i in range(0u, 100) {
assert!(*m.find(&(i, i)).unwrap() == i * 2)
}

for i in range(0u, 100) {
m.remove(&(i, i));
}

for i in range(0u, 100) {
assert!(m.find(&(i, i)).is_none())
}
}
}

fn main() {
}

Compiled with --opt-level=3.

With the (new) compiler a8c3fe4, I get:

test bench_insert_find_remove_std ... bench: 89242 ns/iter (+/- 3605)
test bench_insert_std ... bench: 46177 ns/iter (+/- 1555)

With the (old) compiler 67c954e, I get something more than 10% faster. The asm dump is smaller too:

test bench_insert_find_remove_std ... bench: 73939 ns/iter (+/- 2872)
test bench_insert_std ... bench: 38482 ns/iter (+/- 1005)
Issue 1:
Migrated issue, originally created by Anonymous

I found difference in client|server cursors behaviour:[BR]

client - side cursor fills cursor.description after execute(), and server-side cursor leave description 'None' after execute() until call of fetch...().[BR]

I found it both on windows and linux, with postgres 8.1.2 and psycopg 2-2.0.51 (last stable version).[BR]

SA looks in cursor description before calling fetch - see base.py line 562.

Attachments: test_pg.py

Issue 2:
Migrated issue, originally created by Markus Meskanen (@Mahi)

Django has a get_or_create() method for times when you don't know if data for an entity already exists. There are multiple implementations available for SQLAlchemy at http://stackoverflow.com/questions/2546207/does-sqlalchemy-have-an-equivalent-of-djangos-get-or-create/, but I thought it would be nice to have a native support for such widely used feature.

I'm not sure of the ideal implementation, but one that pleases my eye is to add a keyword arugment for one() etc:

session.query(Player).filter_by(id=my_player_id).one(create=True)

Or simply add a new method:

session.query(Player).filter_by(id=my_player_id).get_or_create()
Issue 1:
The recent changes in variables.less comment styling has led to Visual Studio 2013 (and maybe others) to mess up the interpretation, as you can see in the screenshot below.

The problem lies in the comment style (which has changed for some unknown reason, correct me if I'm wrong). Would be great if someone could fill me in on that.

//** Comment

Simple fix would be adding a space:

// ** Comment

Issue 2:
I'm not sure why the comments in the variables.less got changed to this style //**, but it my opinion it was a brave move.

For me at least it prevents compilation when using the nodejs compiler lessc.

At also breaks the syntax highlighting in my IDE, Visual Studio 2013
Issue 1:
Consider following form:

<form action="/">
<input type="hidden" name="option" value="default">
<input type="radio" name="option" value="A">
<input type="radio" name="option" value="B">
<input type="hidden" name="settings[1]" value="0">
<input type="checkbox" name="settings[1]" value="1" id="setting-1">
<button>klickme</button>
</form>

Form generated by CakePHP and Laravel automatically. This works the way that when no radio button was selected or checkbox was checked a value from hidden field with same name attribute used in POST and getValue method of corresponding FormField in DomCrawler.

Right now this results in Fatal Error with radio button (because hidden field which is discovered first in considered as radio button, when a radio button with same name is found), see Behat/Mink#349:

Fatal error: Call to undefined method Symfony\Component\DomCrawler\Field\InputFormField::addChoice() in ./vendor/symfony/dom-crawler/Symfony/Component/DomCrawler/Form.php on line 412

and has no effect (default value from hidden field isn't used), when we're dealing with checkbox, see Behat/Mink#595 .

Related issues:

Behat/Mink#349

Behat/Mink#595

Issue 2:
This is actually a duplicate ticket from silexphp/Silex-WebProfiler#22 but thought I best put it here as well incase it gets missed in the Silex-WebProfiler repo.

The Web Profiler seems to trigger this error since this method was added 4 days ago.
Issue 1:
I am using the modal dialog on a Grails based application. The first time I click a link (using the <a> tag) my action is fired as I can see in my debugger and I'm able to operate on data. Any link clicked afterwards is no longer 'loading' the URL specified by data-remote so the same dialog from the first attempt is displayed over and over.

I am assuming that this would work correctly in the javascript version. Is there no way for this to work with the data api version?

Issue 2:
After closing and opening same modal it will not request content. Adding $.ajaxSetup({ cache: false });

not helped. Is it but or there is some trick to avoid it?
Issue 1:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

webpack2 causes this bug in redux-form. I think the reason is two copies of SubmissionError classes are created and can be referenced separately, causing instanceof confusions.

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

Please see the error demonstration here:

https://github.com/aq1018/webpack2-redux-form-submission-error-weirdness

What is the expected behavior?

instanceof should return true from instance of classes imported from either import methods.

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

Issue 2:
I asked this question over on StackOverflow but I figured I might get a better response here.

I am trying to switch from using browserify to webpack. One thing browserify handled nicely was dependency management inside dependencies. Let me give an example:

Main app project:

var util1 = require('shared-components/util1');
var util2 = require('shared-components/util2');

Inside shared-components/util1.js

var util2 = require('../util2');

Browserify would realize that the reference to util2 in both scenarios was the same but it appears that Webpack does not which creates duplicate entries for util2.

Is there a configuration setting or plugin I can use to resolve this?
Issue 1:
This program is currently accepted:

use A::B;

mod A {
pub struct B { n: int }
fn B() { }
}

fn main() {
}

but this program, which adds a use of B(), is not:

use A::B;

mod A {
pub struct B { n: int }
fn B() { }
}

fn main() {
let _ = B();
}

Issue 2:
When there is a single import statement that imports multiple idents, and one of them is not found, then the resulting error points to the use site, not the import site.

import http_parser::{http_parser, http_parser_settings, http_parser_execute}; // http_parser_execute is not in the http_parser module

....

http_parser_execute(addr_of(self.parser));

./parser.rs:68:12: 68:31 error: unresolved name: http_parser_execute
./parser.rs:68 http_parser_execute(addr_of(self.parser),
Issue 1:
BottomNavigation throws an error if one child is null.

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

Expected Behavior

Since inline if with logical && operator (https://reactjs.org/docs/conditional-rendering.html#inline-if-with-logical--operator) is a popular technique to achieve conditional rendering, I think that BottomNavigation should support this, instead of throwing an error.

I think this could be achieved by filtering out children that are null at https://github.com/callemall/material-ui/blob/v1-beta/src/BottomNavigation/BottomNavigation.js#L66 before mapping them.

Current Behavior

BottomNavigation throws an error if one child is null, such as is the case with inline if with logical && operator for conditional rendering.

Steps to Reproduce (for bugs)

<BottomNavigation selectedIndex={0}>
<BottomNavigationItem
label="One: OK"
/>
<BottomNavigationItem
label="Two: OK"
/>
{
condition &&
<BottomNavigationItem
label="Three: Will throw error when condition is false"
/>
}
</BottomNavigation>

Context

I'm using conditional rendering to show select options in the bottom navigation.

Your Environment

Tech
Version

Material-UI
0.19.4

React
15.4.2

browser
Firefox 52.2.0 (64-bit), Version 60.0.3112.113 (Official Build) (64-bit)

etc

Issue 2:
Following the guide about server side rendering, I tried to use the jss-default-preset (as jss-compose and jss-extend are really awesome 🥇 )

My server code is the following:

import { create } from "jss";
import jssPreset from "jss-preset-default";

const jss = create(jssPreset());

When my server render the css, everything is fine. But for the client part, it does not execute the extra plugins (jss-extend and jss-compose).

In the guide, the client part doesn't wrap the app with a JssProvider.

So I don't know how to configure the client side to also use the jss-preset-default.

I have searched the issues of this repository and believe that this is not a duplicate.
Issue 1:
React version: 16.13.1

Steps To Reproduce

Create a component using a conditional hook

Wrap the component with a HOC, e.g. mobx observer

Example

function HOC<T>(c: T): T { return c; }

const ConditionalHookComp = HOC(
({ flag }): JSX.Element => {
if (flag) {
useEffect(() => console.log("something"));
}
return <></>;
});

The current behavior

The linter does not issue a warning/error for the conditional use of hooks, unless you remove the HOC.

The expected behavior

The linter issues a warning/error for the conditional use of hooks regardless whether the component is wrapped by an HOC or not.

Issue 2:
React version: 17.0.1

my component file is like:

`export default function(props) {

if (props.data > 1) {

useEffect(function() {

})

}

return (

data

)

}`

my .eslintrc.json file like this:

{ "extends": [], "plugins": [ "react-hooks" ], "rules": { "react-hooks/rules-of-hooks": "error", "react-hooks/exhaustive-deps": "error" }, "parser": "babel-eslint" }
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.6.x

Operating System version: all

Java version: 1.6+

Step to reproduce this issue

mvn clean package

Expected Result

BUILD SUCCESS

Actual Result

BUILD FAILED

Issue 2:
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.6.x

Operating System version: centos

Java version: 1.8

原因：

1.数据包大小不确定

2.经常出现网络耗时比较长的原因

如何 监控dubbo的传输数据包的大小，有那个地方能看到吗
Issue 1:
In ES6 spec in section in Let and Const Declaration

LexicalDeclaration : LetOrConst BindingList ;

It is a Syntax Error if the BoundNames of BindingList contains "let".

It is a Syntax Error if the BoundNames of BindingList contains any duplicate entries.

currently we allow

let let = 10;
const let = 30;

which should be syntax error regardless of strict-mode.

Note: below shouldn't be a syntax error unless it is in strict-mode

let = 10
var let = 20;

Issue 2:
The following examples should trigger an early error in JS:

let let = 10;

const let = 10;

Note: a similar test exists in tests/cases/conformance/es6/for-ofStatements/for-of56.ts) for the following 3 examples

for (var let of [1,2,3]) {
}

for (let let of [1,2,3]) {
}

for (const let of [1,2,3]) {
}

I'm not sure if the following should trigger an error:

var let = 10;
for (let of [1,2,3]) {
}

13.2.1.1 Static Semantics: Early Errors

LexicalDeclaration : LetOrConst BindingList ;

It is a Syntax Error if the BoundNames of BindingList contains "let".

13.6.4.1 Static Semantics: Early Errors

IterationStatement :

for ( ForDeclaration in Expression ) Statement

for ( ForDeclaration of AssignmentExpression ) Statement

It is a Syntax Error if the BoundNames of ForDeclaration contains "let".
Issue 1:
after restoring from minimize the size expands about 10 pixel .

I set min width and min height and use getCurrentWindow().minimize(); function .

I have frame less windows and run app in windows 10

if windows was set to min width and min height after recovering from minimize state it expands the size about 10 pixel

same issue while maximizing and restoring window

applications like what's app which is written by electron has same problem

I use electron 9.1.0

Issue 2:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Electron Version

15.3.1

What operating system are you using?

Windows

Operating System Version

Windows11 version 22000.346

What arch are you using?

x64

Last Known Working Electron version

13.0.0

Expected Behavior

Normal start

Actual Behavior

gpu-process-crashed

Testcase Gist URL

No response

Additional Information

Crashpad.zip
Issue 1:
Updated from Next@2.2.0 to Next@latest and when I run the app I get this error:

Error: _document.js is not exporting a React element 3 times in the terminal.

Latest updated from testing is that the issue arises when I try and use redux in the _document.js - if I don't init redux in document.js it works.

Any help is greatly appreciated!

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

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Here is my repo with next@2.2.0 - you can just download and change it to next@latest in package.json: https://github.com/spencersmb/Font-Popper-Client

npm install

npm run watch

Context

Trying to upgrade my version of next to the latest.

Your Environment

Tech
Version

next
3.0.6

node
v8.2.1

OS
Sierra 10.12.5

browser
chrome

etc

Issue 2:
The route /posts/ renders on the server but then the store on the client subscribe is undefined. In the chrome dev tools, it shows an error on the import for isPlainObject from lodash. I've done this before and I have no idea whats wrong. I'm sure its something I am doing, but I can't put my finger on it.

Basically I create in my hoc folder in src/ a pageWrapper that just partially applies the store and is waiting for the component. I then have my Posts component in features/ connected. I can't seem to figure out whats wrong with the store and why its broken on the client.

Initially I see the basic text appear before the error pops up which leads me to believe the store is working on the server but not the client.

Code here, https://github.com/ryanbas21/blog .

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

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Your Environment

Tech
Version

next

node

OS

browser

etc
Issue 1:
Given the following code:

restoreState() {
var iLastState = this.stateStack[ stateStack.length - 1 ];
this.restoreState( iLastState );
}

restoreState( aState: TransformerState ) {
this.state = aState
}

And the following call:

popState() {
var iState = this.stateStack.pop();
this.restoreState( iState ); // Error on this line
}

The compiler complains:

error TS2346: Supplied parameters do not match any signature of call target.

Language like C++ or JAVA support no argument function overloads; typescript seems not to.

Issue 2:
TypeScript Version:

1.8.10

Hi.

I still have the error code TS1127 when I try to compile a file.

I use the code from the quick tutorial.

Code

// A self-contained demonstration of the problem follows...
function greeter(person: string){
return "Hello, " + person;
}
var user = [0, 1, 2];
document.body.innerHTML = greeter(user);

Expected behavior:

_greeter.ts(7,26):Supplied parameters do not match any signature of call target

Actual behavior:

greeter.ts(1,1): error TS1127: Invalid character.

greeter.ts(1,2): error TS1127: Invalid character.

greeter.ts(1,3): error TS1127: Invalid character.

greeter.ts(1,4): error TS1127: Invalid character.